AOSP is running newer kernel so it's likely working because of that. I really have no interest in trying to figure out why it works there but if you manage to get it working with upstream lineage device / kernel tree let me know.I've build AOSP 11, and adoptable storage works fine here. Any chance it might get fixed in LOS as well?
Right now getting my hands on source code to try various options. But perhaps this option might be a culprit? I've looked at LineageOS repos for that prop, it returned some devices, but not ours.AOSP is running newer kernel so it's likely working because of that. I really have no interest in trying to figure out why it works there but if you manage to get it working with upstream lineage device / kernel tree let me know.
This prop will do nothing on lineage kernel.Right now getting my hands on source code to try various options. But perhaps this option might be a culprit? I've looked at LineageOS repos for that prop, it returned some devices, but not ours.
Plus 3 more.
I've got 20200722_BY12O_Daily with firmware H4113_Customized CE1_50.2.A.3.77-R1B downloaded with xperifirm and flashed with newflasher (as usual I just wasted some time trying to get flashtool to work with no luck).Mine is 2019 as well. Did you get the later baseband by using a later firmware? If so, which one? I have flashed the pioneer_modem_bt_dsp_50.2.A.3.22.zip
dead // 636865636b20746f6d6f72726f77203a5e29
Why?
As it's already tomorrow and a new build is released, I dare to give a hint:
I went through the same process. I noticed that the stock firmware prompted me to "reboot the phone to optimize for your network provider" a short while after finishing the setup process.Thanks. I updated to H4113_Customized DACHBLX_50.2.A.3.77-R5B (XperiFirm for download and newflasher). Sadly, still no working IMS registration with Aldi Talk / Telefonica Germany.
The update of the original Sony firmware updates the baseband.
Yesterday, I updated my baseband with the instructions from https://xdaforums.com/t/rom-official-pioneer-10-lineageos-17-1.3979989/post-80469769 (the "flash whole firmware package" part).
Result: after the boot, the SIM PIN prompt came and after that "no SIM card" ...
I remembered that others wrote about that problem - it seems to appear if you install LineageOS without booting into the original Sony firmware at least once before.
So I took newflasher a second time to flash everything of the firmware (except the persist_* files) - which also erases all user data, which means a "nice" factory reset. Then booting into original firmware, clicking through the setup-dialog at the beginning. After that, reinstalled LineageOS as described in https://wiki.lineageos.org/devices/pioneer/install ...
Yeah again a working phone ... and a forgotten backup of the phonebook ...
Much fun for still not really working VoLTE.
Edit: my baseband version is now 20200722_BY12O_Daily .
So it wasn't only me with a proximity sensor issuesI went through the same process. I noticed that the stock firmware prompted me to "reboot the phone to optimize for your network provider" a short while after finishing the setup process.
I managed to save most of my data by performing a TWRP backup of the whole system before flashing the stock rom, re-installing LineageOS, booting into it once and then restoring system and user data (though I'm not sure if that exact sequence is successful, I went through quite some trial and error until my phone was booting again).
I did however learn the hard way that all Signal messages are lost, because TWRP cannot backup/restore the Android key store. I also had to reinstall some other apps that relied on it.
VoLTE and Wifi-Calls work now at least incoming for AldiTalk.
The newer firmware makes the proximity sensor work less reliably. Often the screen does not turn back on, even if the phone is not close to any surface. This usually can be resolved with some "handwaving".
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
for f in FILE_*; do unzip $f; done
unzip boot.zip -d boot
As it's already tomorrow and a new build is released, I dare to give a hint:
Let me know if it still works on April 13th.So I tried it and it seems to fix the issue. I had now two nights in which the phone charged properly without reboot, while before I had to reboot every evening to make it charge again.
Please let me know if there is anything else I can do to help debugging!