Post/list ongoing device ports with status and install instructions etc (only for ongoing ports)
Voice-speaker is using bottom speaker and voice-speaker-mic is using top mic. Is it correct? I would expect top speaker and bottom mic.
@fredldotme I didn't notice it when listening to mp3 music but when listening to flac music, the sound is popping. I'm using bigger latency again to avoid this and I think we should use deep buffer flag as the default setting for suzu if you agree.
@Giampy What kind of problems with the sim card data connection? What kind of notifications?
Maybe you could adopt him in a "device porting team", if you have one ^^
Anyway, good news, androïd 9 based devices are recent and numerous now (let's hope this will be done with all GSI compatible androïd versions).
@ignne I read somewhere that karin's chipset works as rome one so that it can be backported, as experienced by some xiaomi porters. I need to find some time to apply patches and try to backport for better compatibility with blue 5.x or later
The reason is that I passed the argument 'rate=44100' to the module module-droid-discover in the file touch.pa, which in turn means that this argument gets passed in the correct way.
However, the effect should be that that the sampling rate gets set to this value, but that does not happen, and I do not understand why, since I can set it correctly from the command line using pactl
@poVoq well, I have not, but according to the wikipedia article, the Nokia N1 received only LP 5.1 - so will likely be stuck on DDK 1.4 as well.
Also, it is really unlikely that it runs on x64 Android (because that would require different blobs from Imgtech et al. which are expensive - and I can't think of any reason why they would do it for that device).
But if you can grap a copy of the Nokia firmware (filename appears to be A5CN701_update .zip) you can check with the "file" command if the libs are 32 or 64 bits...
Thanks - but is there a way to retrieve those instructions? Someplace where they might be archived? We do have an issue with the installer - well, we don't know for sure what is going on... - but a step by step installation might prove useful to find out why and when the installer isn't working correctly in that particular case.
Definitely too old. We are struggling to support Kernel 3.4 and Android 5.1 stick devices. Nexus 4 is I think the only exception where an even older device was made usable, but it has at least kernel 3.4 - You wont get much help with anything older than that.