[ROM][OFFICIAL][pioneer][11] LineageOS 18.1

[malerocks]

Magisk 22.0 works as it should (with the latest UNOFFICIAL build of LOS18.1).

samhhmobil

Using hide in v22, I am able to prevent apps from detecting that my phone is rooted. However I am unable to grant superuser access to the apps that I want to give this to. Any suggestions?

 

[samhhmobil]

Using hide in v22, I am able to prevent apps from detecting that my phone is rooted. However I am unable to grant superuser access to the apps that I want to give this to. Any suggestions?

Sorry, no idea, what's wrong in your configuration. For me it works without issues.

samhhmobil

 

[ElLibertador]

Thanks Luk. What you say makes sense but if you look at the comments, I am not the only one facing the issue. I wonder what the common factor is between the ones facing it.

For me:
Used mindthegapps
Magisk v22
No other modules

Same issue here after upgrading from 17.1, no charging issues before. Chaging only works once after every restart.

Magisk 22
microG

 

[Merlin K]

Same issue here after upgrading from 17.1, no charging issues before. Chaging only works once after every restart.

Magisk 22
microG

I had similar issue on 17.1 some time ago. It was possible to charge only by connecting phone during restart, before LOS loaded. Issue was related to USB settings and I thought it is hardware related. In a few days I took my phone and went to service but when I tried to replicate issue there - it started to work fine. How no idea what that was...

 

[malerocks]

Same issue here after upgrading from 17.1, no charging issues before. Chaging only works once after every restart.

Magisk 22
microG

Thanks. Since you are using microg, atleast it proves that it's not the gapps I used. Wonder if its magisk?

Is there anyone without magisk facing the issue?

 

[samhhmobil]

Thanks. Since you are using microg, atleast it proves that it's not the gapps I used. Wonder if its magisk?

Is there anyone without magisk facing the issue?

Sorry, I haven't that strange behaviour (maybe it depends on the firmware?).

Charging cable plug in, plug off, plug in, plug off, ..., ..., ..., ... charging works as it should. No issues here.

- Phone model: H3113
- Firmware 50.2.A.3.77 (2020-07-22)
- LOS 18.1, build of 2021-04-02
- OpenGapps-TEST, nano, of 2021-01-30
- Magisk v22.0

samhhmobil

 

[emc02]

I've got also the charging issue yesterday.
Did anyone face any issues during OTA Update? Is it safe?

 

[malerocks]

I've got also the charging issue yesterday.
Did anyone face any issues during OTA Update? Is it safe?

I did an ota update today. No issues yet.

 

[emc02]

I did an ota update today. No issues yet.

I am getting a bootloop after OTA, installing with TWRP works
Are you using magisk 22 and NikGapps?

 

[malerocks]

I am getting a bootloop after OTA, installing with TWRP works
Are you using magisk 22 and NikGapps?

Magisk 22. I used mindthegapps when I first installed

 

[samhhmobil]

Did anyone face any issues during OTA Update? Is it safe?

Even here no issues. OTA to 2021-04-08 did update cleanly and safe.

samhhmobil

 

[Andy_2639]

Edit: VoLTE works! I talk on the phone and the service is still LTE. I am using Vodafone Germany (Lidl Connect).

Does VoLTE work for incoming and outgoing calls? For me, VoLTE (and WiFi-Calling) works only for incoming calls. Outgoing calls fall back to GSM/UMTS.
(I tested it by forcing my phone to LTE/disabling radio power).

Does your phone register to IMS?

• Dial *#*#4636#*#* (*#*#info#*#*)
• Tap Phone information
• In the 3 dots menu, select IMS Service Status

I'm using Aldi Talk (Telefonica Germany)

Thanks for the update on your VoLTE status

 

[Andy_2639]

Thanks. Since you are using microg, atleast it proves that it's not the gapps I used. Wonder if its magisk?

Is there anyone without magisk facing the issue?

I'm also experiencing charging issues with 18.1 - with 17.1 no problems.
I'm using a USB Battery Charging device (basically 5V PSU with shorted data lines: https://en.wikipedia.org/wiki/USB_hardware#USB_Battery_Charging ).

The first time I read about the charging issue, I tried charging: pluggin cable in, out, in ... averything worked.
Then I really needed to charge it and it displayed: chager connected but no charging. After a restart, charging worked. Now, I tried to charge again and same problem: ohne detects charger but doesn't charge the battery.

I measured the current and it seems that the phone uses the charger to power itself (and not draining the battery) but does not charge the battery. This also complies with my experience: during a map update of OSMand, the battery level didn't fall despite a long time loading data via WiFi.

Phone model: H4113
Baseband: 20191108_BY12O_Daily
LineageOS: 18.1-20210402-NIGHTLY-pioneer
No root, no magisk, no Goole Apps/Services - just plain LineageOS as far as I can tell.

Updated form 17.1 without factory reset.

 

[LuK1337]

I'm also experiencing charging issues with 18.1 - with 17.1 no problems.
I'm using a USB Battery Charging device (basically 5V PSU with shorted data lines: https://en.wikipedia.org/wiki/USB_hardware#USB_Battery_Charging ).

The first time I read about the charging issue, I tried charging: pluggin cable in, out, in ... averything worked.
Then I really needed to charge it and it displayed: chager connected but no charging. After a restart, charging worked. Now, I tried to charge again and same problem: ohne detects charger but doesn't charge the battery.

I measured the current and it seems that the phone uses the charger to power itself (and not draining the battery) but does not charge the battery. This also complies with my experience: during a map update of OSMand, the battery level didn't fall despite a long time loading data via WiFi.

Phone model: H4113
Baseband: 20191108_BY12O_Daily
LineageOS: 18.1-20210402-NIGHTLY-pioneer
No root, no magisk, no Goole Apps/Services - just plain LineageOS as far as I can tell.

Updated form 17.1 without factory reset.

You can try boot.img I uploaded here: https://xdaforums.com/t/rom-official-pioneer-11-lineageos-18-1.4169357/post-84789249
I assumed that someone would care to try it and drop their results here but I guess that was just my wishful thinking.

 

[Andy_2639]

You can try boot.img I uploaded here: https://xdaforums.com/t/rom-official-pioneer-11-lineageos-18-1.4169357/post-84789249
I assumed that someone would care to try it and drop their results here but I guess that was just my wishful thinking.

Can you please tell me how can I try it?
Do I have to install it permanently or just boot with it (like TWRP).
What command do I have to use? fastboot boot boot.img?
(How can I restore the current state of my phone?)

Sorry for the questions but I'm not really deep into this Android stuff - I'm using LineageOS mainly to extend the phone life after Sony drops security updates and to live without Google account.

 

[LuK1337]

Can you please tell me how can I try it?
Do I have to install it permanently or just boot with it (like TWRP).
What command do I have to use? fastboot boot boot.img?
(How can I restore the current state of my phone?)

Sorry for the questions but I'm not really deep into this Android stuff - I'm using LineageOS mainly to extend the phone life after Sony drops security updates and to live without Google account.

You can just boot it. Confirm in settings that kernel build date roughly matches the post time.

 

[Andy_2639]

You can just boot it. Confirm in settings that kernel build date roughly matches the post time.

I started the phone into bootloader (blue LED) and run that command:

C:\Users\User\XA2\platform-tools>fastboot boot C:\Users\User\XA2\boot.img
Sending 'boot.img' (22781 KB)                      OKAY [  0.915s]
Booting                                            OKAY [  5.286s]
Finished. Total time: 6.270s

The phone rebooted and showed the battery symbol (like when charging a powered off phone). Then, I pressed the power button and - after showing the unlocked warning and the sony logo - the phone booted into Android.
I guess that it loaded the boot image from the phones memory instead of the one I provided with fastboot as it seemed to do a full reboot after pressing the power button.

The charging issue still is present.

 

[LuK1337]

I started the phone into bootloader (blue LED) and run that command:

C:\Users\User\XA2\platform-tools>fastboot boot C:\Users\User\XA2\boot.img
Sending 'boot.img' (22781 KB)                      OKAY [  0.915s]
Booting                                            OKAY [  5.286s]
Finished. Total time: 6.270s

The phone rebooted and showed the battery symbol (like when charging a powered off phone). Then, I pressed the power button and - after showing the unlocked warning and the sony logo - the phone booted into Android.
I guess that it loaded the boot image from the phones memory instead of the one I provided with fastboot as it seemed to do a full reboot after pressing the power button.

The charging issue still is present.

Unplug usb as soon as it says finished.

 

[mhier]

You can try boot.img I uploaded here: https://xdaforums.com/t/rom-official-pioneer-11-lineageos-18-1.4169357/post-84789249
I assumed that someone would care to try it and drop their results here but I guess that was just my wishful thinking.

I have the issue, too, and just now flashed the modified boot.img. I will report in one or two days if the problem reappears. For me it appears always after a while (some hours), and a reboot cures it.

Btw: I observed a similar, yet more drastic issue with my wife's phone, a Sony X Compact (F5321). I tried an unofficial non-LineageOS Android 11 (https://xdaforums.com/t/rom-11-0-4-9-aosp-kugo-explosive-lobster.4214465/). Charging the phone was then entirely impossible, even when switching it off or while being in recovery. I had to switch to the latest available LineageOS before the battery went down completely. Not sure if this is connected in any way, but maybe this gives a useful hint?

 

[mx82]

Looks like I have also the charging issue. Every charging since the second one after rebooting is not possible.

Good news for GPS location:
Looks like it will be fixed next Thursday:

https://review.lineageos.org/c/LineageOS/android_vendor_lineage/+/305449/

Allow unified location provider as possible location provider (not as used location provider)

This error only appears if you install Gapps or MicroG (only a problem of ~95% of the users ;-) )
On my opinion it's up to the user to decide if he want to use Gapps and Unified / MicroG. But in the first place this patch is needed to make it possible.