[ROM][dumpling][9.0.X] LineageOS 16.0 (Pie) for Oneplus 5T

[JR Bautista]

there's a possible to get lineage os 17.1 for dumpling/cheeseburger?

 

[Eric_Lev]

Delete

 

[Larsn_Rinnstroem]

Delete please

 

[libove]

First, many thanks to codeworx, for this and everything else!
I switched my OnePlus 5T from OnePlus' OxygenOS to LineageOS 16.0 official for dumpling about two months ago.
Ever since, from time to time, when the screen will turn off either due to a natural timeout, or due to me closing the flip cover, when I turn the screen back on again (either by opening the flip cover, or tapping the power button), the screen will stay frozen at whatever was last displayed on it.
The phone is NOT frozen. It IS sensing and responding to whatever inputs that I'm (dangerously, since I can't see the results) making.
If I tap the power button to turn the screen off and tap it again to turn the screen back on, the screen displays what the phone is really currently doing, and responds normally again.
Interestingly, I saw a post just now in a thread about a very, very different, much older, much lower end device, also LineageOS 16.0, doing what appears to be the same thing - the Wileyfox "Swift" phone ("crackling" branch of LineageOS).
Here is a link to that thread and post: https://forum.xda-developers.com/wi...-0-wileyfox-swift-t3921639/page8#post82456639
Any ideas how to get LineageOS 16.0 on dumpling (and perhaps also on crackling) to fully notice when the screen has been turned back on and continue live updating?
thanks.

 

[droidsometimes]

First, many thanks to codeworx, for this and everything else!
I switched my OnePlus 5T from OnePlus' OxygenOS to LineageOS 16.0 official for dumpling about two months ago.
Ever since, from time to time, when the screen will turn off either due to a natural timeout, or due to me closing the flip cover, when I turn the screen back on again (either by opening the flip cover, or tapping the power button), the screen will stay frozen at whatever was last displayed on it.
The phone is NOT frozen. It IS sensing and responding to whatever inputs that I'm (dangerously, since I can't see the results) making.
If I tap the power button to turn the screen off and tap it again to turn the screen back on, the screen displays what the phone is really currently doing, and responds normally again.
thanks.

I've been having that exact problem since ages, even before LOS 16, on most if not all of my LOS devices, including OP5T, and never managed to get to the bottom of it.
Some days it's happening a lot, other days not so much, some apps are affected, some are not.

Double tapping the recents button also 'unsticks' the screen for me btw.


Do you by any chance have OpenGapps (Pico?) installed?
Furthermore, did you freeze some or all of the Google Framework system apps?
Because that's what I always do, after I have installed all the apps I normally use, and I only ever unfreeze the Google system apps for updating apps via playstore.
And I got the feeling that it somehow is related to the stuck screen problem.

Do you have root on your device, and/or have you looked at the logcats when this is happening?
If so, did you see 'googlequicksearchbox' being mentioned?

Unfortunately, during my time with LOS 15.1/16.0 I never got around to installing LOS without Gapps, to see if it fixes things.
Also, I never let the Google Play services just run without freezing them, because I value my privacy more than a stuck screen from time to time.


About two weeks ago, I started migrating two of my phones to LOS 17.1, and I decided to ditch Google Play from now on, and so far - no stuck screen. Now that might be just coincidence, or because Android 10, but still...

 

[libove]

I've been having that exact problem since ages, even before LOS 16, on most if not all of my LOS devices, including OP5T, and never managed to get to the bottom of it.
Some days it's happening a lot, other days not so much, some apps are affected, some are not.

Double tapping the recents button also 'unsticks' the screen for me btw.


Do you by any chance have OpenGapps (Pico?) installed?
Furthermore, did you freeze some or all of the Google Framework system apps?
Because that's what I always do, after I have installed all the apps I normally use, and I only ever unfreeze the Google system apps for updating apps via playstore.
And I got the feeling that it somehow is related to the stuck screen problem.

Do you have root on your device, and/or have you looked at the logcats when this is happening?
If so, did you see 'googlequicksearchbox' being mentioned?

Unfortunately, during my time with LOS 15.1/16.0 I never got around to installing LOS without Gapps, to see if it fixes things.
Also, I never let the Google Play services just run without freezing them, because I value my privacy more than a stuck screen from time to time.


About two weeks ago, I started migrating two of my phones to LOS 17.1, and I decided to ditch Google Play from now on, and so far - no stuck screen. Now that might be just coincidence, or because Android 10, but still...

Hi droidsometimes,
I flashed either OpenGApps pico or mini - I'm not sure which.
Next time it happens to me, I'll try double tapping 'recents' - depending on exactly what was on the screen (as in some apps those soft buttons do not appear until the screen is tapped somewhere) it may not be so easy to see/remember :-}.
The device is rooted; I had not thought to try a logcat. My developer years are so far in the past that I'm not sure what I'd look for, or notice if I did see something (especially as I wouldn't know what should/n't be there in the log).
I'm feeling like half of my brain is on holiday - I _may_ have frozen some GApps, but then again since I started quite small, I hopefully didn't have any junkware (like Google Play Music, Google Play Movies) TO freeze. How would I see what apps I have frozen? (Sorry for the stupid question).
However, the _Framework_ apps (Google Play Services, Google Pay, ..) I definitely have not frozen.

By the way, back over on the Wileyfox Swift (crackling) thread, we've determined that what the other user is experiencing on his Swift is NOT this issue. He's seeing a single app window freezing, not the whole screen like this.

cheers.

 

[libove]

So, the double-tap recents does work. Also, the problem occurred withOUT the screen ever having turned off; I'd not remembered that it could do that. (I have the developer option "Screen will never sleep while charging" enabled, and the phone was on my desktop, plugged in to a charger, with the flip cover open).
I got a logcat shortly afterwards.
The only occurrence of 'googlequicksearchbox' is this, which is probably 10 to 15 minutes before the issue occurred - though I don't recall how long before the issue occurred this time I had last actually interacted with the device, so that's not very diagnostic, I apologise:

05-02 18:19:10.606  1323  1349 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.speech.action.GET_LANGUAGE_DETAILS flg=0x10 } to com.google.android.googlequicksearchbox/com.google.android.voicesearch.intentapi.IntentApiReceiver

I'm hesitant to post a whole logcat, as I don't know whether it might contain sensitive data.
What might I look for to debug the problem?
thanks,

Hi droidsometimes,
I flashed either OpenGApps pico or mini - I'm not sure which.
Next time it happens to me, I'll try double tapping 'recents' - depending on exactly what was on the screen (as in some apps those soft buttons do not appear until the screen is tapped somewhere) it may not be so easy to see/remember :-}.
The device is rooted; I had not thought to try a logcat. My developer years are so far in the past that I'm not sure what I'd look for, or notice if I did see something (especially as I wouldn't know what should/n't be there in the log).
I'm feeling like half of my brain is on holiday - I _may_ have frozen some GApps, but then again since I started quite small, I hopefully didn't have any junkware (like Google Play Music, Google Play Movies) TO freeze. How would I see what apps I have frozen? (Sorry for the stupid question).
However, the _Framework_ apps (Google Play Services, Google Pay, ..) I definitely have not frozen.

By the way, back over on the Wileyfox Swift (crackling) thread, we've determined that what the other user is experiencing on his Swift is NOT this issue. He's seeing a single app window freezing, not the whole screen like this.

cheers.

 

[droidsometimes]

I'm hesitant to post a whole logcat, as I don't know whether it might contain sensitive data.
What might I look for to debug the problem?
thanks,

Maybe do what I did:
Configure the status bar clock to show the seconds, set a short screen timeout, and a long lock timeout.
Then keep using the device normally, but let the screen reach the timeout often, and try to wake up the screen immediately after it goes black - e.g. double tap to wake.
Once the screen gets stuck, memorize or write down the minute and the second of the status bar clock (immediately taking a screenshot might work too) - that way you should get a clue what timestamps to look for in the logcat.
After that has happened several times, compare the relevant sections of the collected logcats, and see if anything sticks out, or is similar across all the collected parts.

Regarding sensitive info in the logcats, for example the app SysLog (F-Droid store) has an option to 'scrub potentially personal information from the logs'.
I've never used that option though, so not sure if it's reliable.

 

[libove]

Maybe do what I did:
Configure the status bar clock to show the seconds, set a short screen timeout, and a long lock timeout.
Then keep using the device normally, but let the screen reach the timeout often, and try to wake up the screen immediately after it goes black - e.g. double tap to wake.
Once the screen gets stuck, memorize or write down the minute and the second of the status bar clock (immediately taking a screenshot might work too) - that way you should get a clue what timestamps to look for in the logcat.
After that has happened several times, compare the relevant sections of the collected logcats, and see if anything sticks out, or is similar across all the collected parts.

Regarding sensitive info in the logcats, for example the app SysLog (F-Droid store) has an option to 'scrub potentially personal information from the logs'.
I've never used that option though, so not sure if it's reliable.

*grrr* Wouldn't you know it? The status bar does update - it's just the home page that forgets to update. So I don't get to see a timestamp of when stuff froze. The clock keeps ticking merrily along...
I did take another logcat, and if I have time I'll try to look for clues in there, though it's really needly-in-a-haystack at this point

 

[Thimoteo]

Frequent reboots without reason

I wonder if anyone can help me troubleshoot this problem.

With nightlies downloaded since late 2019 or early 2020, my OnePlus 5T reboots mysteriously, without any action on my part. It might go three days without rebooting this way, or might reboot three times in one day. It happens when the phone is idle, sitting on the table. No calls, no internet use. Just, all of a sudden: reboot.

No Gapps. I'm now on firmware 9.09 and nightly 20200421, version 16.

 

[Thimoteo]

Update: I did a fresh install with the 0421 nightly, experienced new rebooting problems, then installed the 0407 nightly. It is still rebooting a couple of times a day, but now only does so when I'm doing something with the phone: looking at a web page or configuring a program.

 

[Eric_Lev]

No sweat on my side.
FW 9.0.11 / latest official build / nano open gapps / magisk 20.4
I formatted data (to remove the encryption) then wiped cache, dalvik, vendor and system (ext4 for all) via TWRP (twrp-3.3.1-20190908-0-codeworkx) before flashing build + gapps + los addon su.

 

[Thimoteo]

Thanks for the response, Eric. My steps were almost the same, but I hadn't formatted data or used the codeworkx recovery, so figured I'd start over and follow your steps exactly. I installed the codeworkx recovery, formatted data, wiped cache, dalvik, vendor and system. All ext4.

The codeworkx 20090908 recovery wouldn't install the 20200421 nightly; it insisted my phone is cheeseburger, a OnePlus 5, and not a dumpling, 5T! I checked the receipt and even measured the screen; my phone is definitely a dumpling 5T. First time I've ever seen anything like this. (Edit: the back sticker says it's a model A5010.)

I downloaded and installed the twrp.me recovery for the 5T. It installed the 20200421 nightly without problems ... but the phone started acting up again almost immediately, with a 'Phone is starting ...' loop during the boot.

If you have any ideas, I'd love to hear them.

 

[Eric_Lev]

Thanks for the response, Eric. My steps were almost the same, but I hadn't formatted data or used the codeworkx recovery, so figured I'd start over and follow your steps exactly. I installed the codeworkx recovery, formatted data, wiped cache, dalvik, vendor and system. All ext4.

The codeworkx 20090908 recovery wouldn't install the 20200421 nightly; it insisted my phone is cheeseburger, a OnePlus 5, and not a dumpling, 5T! I checked the receipt and even measured the screen; my phone is definitely a dumpling 5T. First time I've ever seen anything like this. (Edit: the back sticker says it's a model A5010.)

I downloaded and installed the twrp.me recovery for the 5T. It installed the 20200421 nightly without problems ... but the phone started acting up again almost immediately, with a 'Phone is starting ...' loop during the boot.

If you have any ideas, I'd love to hear them.

XDA for cheeseburger and LOS 16.0 : https://forum.xda-developers.com/oneplus-5/development/rom-lineageos-16-0-pie-oneplus-5-t3843064
Recommended TWRP (codeworkx) : https://sourceforge.net/projects/ch...signed-forcedecrypt-cheeseburger.img/download
Firmware : https://sourceforge.net/projects/cheeseburgerdumplings/files/16.0/cheeseburger/firmware/

PIS issue is well known and has been reported by several people on several phones (e.g. OP3/3T).
On my side, I was faced PIS more often with Magisk (OP3T and OP5T with LOS 17.1) than with LOS addon su (OP3T and OP5T with LOS 16.0).

 

[Thimoteo]

Thanks again for the efforts to help, Eric. I hadn't looked up the PIS issue. I'm not alone.

"About phone" also says that my cell is an A5010 5T, and not a 5. The screen dimensions match the 5T, and not the 5. I think I started with Lineage 15 on this phone before upgrading to 16, and never saw any messages before reporting that I'm actually running a dumpling. So I'm reluctant to install a cheeseburger TWRP or ROM.

I installed a Blu Spark TWRP, did a fresh install that way and will try some other steps on my own.

 

[Eric_Lev]

Thanks again for the efforts to help, Eric. I hadn't looked up the PIS issue. I'm not alone.

"About phone" also says that my cell is an A5010 5T, and not a 5. The screen dimensions match the 5T, and not the 5. I think I started with Lineage 15 on this phone before upgrading to 16, and never saw any messages before reporting that I'm actually running a dumpling. So I'm reluctant to install a cheeseburger TWRP or ROM.

I installed a Blu Spark TWRP, did a fresh install that way and will try some other steps on my own.

OnePlus 5T = A5010 ... so your driver is a OnePlus 5T ... dumpling and not cheeseburger !

==> Don't install/flash TWRP and build for cheeseburger (OP5) ... only for dumpling (OP5T) ... of course.

 

[Thimoteo]

OnePlus 5T = A5010 ... so your driver is a OnePlus 5T ... dumpling and not cheeseburger !

==> Don't install/flash TWRP and build for cheeseburger (OP5) ... only for dumpling (OP5T) ... of course.

I've got everything configured again with the Blu Spark TWRP, and will wait to see if it holds up without frequent crashes.

It's weird that the Codeworkx TWRP (twrp-3.3.1-20190908-0-codeworkx) insisted that my A5010 5T is actually a 5 cheeseburger.

 

[Eric_Lev]

Awaiting the official builds to come back (https://status.lineageos.org/) :

No need to flash a migration_keys script.
Tested from official to unofficial (and vice-versa) on my OP5T (BL unlocked and encrypted) and my OP3T (BL locked and unencrypted).

From official build to unofficial build:
Boot to TWRP
Flash/install my unofficial build (https://androidfilehost.com/?a=show&w=files&flid=309544 - Not signed builds)
Restart to System

roomservice.xml

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
  <project name="TheMuppets/proprietary_vendor_oneplus" path="vendor/oneplus" remote="github" revision="lineage-16.0" />
  <project name="LineageOS/android_device_oneplus_dumpling" path="device/oneplus/dumpling" remote="github" />
  <project name="LineageOS/android_device_oneplus_msm8998-common" path="device/oneplus/msm8998-common" remote="github" />
  <project name="LineageOS/android_device_oppo_common" path="device/oppo/common" remote="github" />
  <project name="LineageOS/android_kernel_oneplus_msm8998" path="kernel/oneplus/msm8998" remote="github" />
  <project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" />
</manifest>

From unofficial build to official build:
Delete your fingerprints and screen lock before flashing official build.
Boot to TWRP
Flash/install official build (https://download.lineageos.org/dumpling)
Restart to System

Edit : if your screen lock (for me, a pattern) and fingerprints are not restored after flashing official build, a well-known workaround using TWRP terminal or file manager if rooted, is to delete :
the lock screen files
/data/system/gatekeeper.*
/data/system/locksettings.*
and if using fingerprints,
/data/system/users/0/fpdata
/data/system/users/0/settings_fingerprint.xml

 

[aftnoon2]

Hi
Where we can find out the latest firmware?

On Sourceforge the latest is 9.0.9, dated back on 2019...

Thanks!

PS Forget it, I've found out.

 

[ctag]

It looks like the build system is back up and running. Has anyone installed the latest? Is it good to go?