Development [ROM][OFFICIAL][lemonadep][11] LineageOS 18.1
- Thread starter LuK1337
- Start date
Dear developers, please fix problem with video, if I play video in browser, after press button stop and press button play image in video freeze but sound and timer work normally, in YouTube after I press button stop, after 3 seconds video play again without my press button play.
p.s. in Nameless ROM with vendor OSS 12 don't have this bug.
(I use last build LineageOS 19.1, vendor Oxygen OS c. 48 global, don't install magisk.)
p.s. in Nameless ROM with vendor OSS 12 don't have this bug.
(I use last build LineageOS 19.1, vendor Oxygen OS c. 48 global, don't install magisk.)
Last edited:
Development has "moved on" for OnePlus 9 Pro from LineageOS 18.1 to LineageOS 19.1 now, so I doubt you will see any updates to 18.1 to fix this problem.
It may not even really be a LineageOS problem but rather something with the app.
FWIW I use SkyTube app for YouTube since I have no Google services (by choice) on my 18.1 LOS 9 Pro and have been quite happy with it. You can get it from F-Droid repository.
If there IS a prob with LOS needing a code change I'm pretty sure the answer from the developers would be try it on 19.1, that is where current dev is going on.
(yeah I am still on 18.1 too, waiting to be crystal clear on stability etc. of 19.1)
At&t SIM. Card through straight talk works fine for me, but no 5g. Straight talk tech support lies to customers calling in, and will often say a device isn't supported, even if it actually is. I think they do this to wrap up the calls quicker. If I get an agent that says it's not compatible, I ask to get transferred to the porting department, or hang up and call back in.
At&t has been very ****ty about not supporting phones on their network, forcing you to upgrade. But the OnePlus 9 pro works just fine, as long as it is an American varient. Supposedly they block international phones, like my S10 lite (g770f)
dunno what to tell you but AT&T is the absolute worst customer service or support I have ever dealt with in my entire life. Only advice I can give you is vote with your feet - get out ASAP.
I have T-Mobile, not a great fan of them either -- obvious political and security issues -- but at least they're not fascists about what devices you can use on their network and don't force you to go under contract or create one without your permission like AT&T does routinely (has happened to us with TV/Inet/digphone - now the only business we give them is for internet).
When we got LE2125's (unlocked phones) all we had to do was pull our nano-sims out of our old LG V20's and pop them into the LE2125's, and bam, all the features just started working including VoLTE, WiFi calling etc. We did not have to bring our phones to a T-Mobile store.
Last edited:
speaking of T-Mobile... I understand 18.1 is water under the bridge for lemonadep and I am not asking for support on this. I am just curious if anybody else happened to run into this with T-Mobile service. We have LE2125's (Global/NA Unlocked).
Things were great for the first few months of having these phones, running the last nightly release of 18.1 for lemonadep (5/24/22) rooted with magisk, but all the sudden one day I was out in town driving around and my phone crashdumped. This is the message:
It continued to happen from that point on pretty much whenever I was out driving. Didn't really happen at home.
I suspected from the name of C code files and presumably function names, etc. that this had something to do with negotiation/handshake failure during switching towers. T-Mobile probably fubar'd something with tower software/firmware updates... *shrug*
At any rate through process of elimination I discovered that by setting preferred network type to LTE service ONLY rather than 5G + LTE, it stopped happening. So, something 5G-specific was broken.
It started happening to my wife also not too long ago. Same workaround (LTE only) helped her as well.
Maybe this will help someone if you are stuck on 18.1 for some reason and this is happening to you.
Doesn't happen to us with 19.1 or 20.0 with 5G enabled in preferred network type.
cheers...
Things were great for the first few months of having these phones, running the last nightly release of 18.1 for lemonadep (5/24/22) rooted with magisk, but all the sudden one day I was out in town driving around and my phone crashdumped. This is the message:
Code:
nr5g_m11_asdiv_exec.c:1062:Assert 0 failed: Could not find the chain which was selected by TRM as new primary
subsys_err_fatal_intr_handlernr5g_m11_rfmgr_stm.c:6720:Step 0x2 : RF returned fatal RFSW execution ERROR
subsys_err_fatal_intr_handlerIt continued to happen from that point on pretty much whenever I was out driving. Didn't really happen at home.
I suspected from the name of C code files and presumably function names, etc. that this had something to do with negotiation/handshake failure during switching towers. T-Mobile probably fubar'd something with tower software/firmware updates... *shrug*
At any rate through process of elimination I discovered that by setting preferred network type to LTE service ONLY rather than 5G + LTE, it stopped happening. So, something 5G-specific was broken.
It started happening to my wife also not too long ago. Same workaround (LTE only) helped her as well.
Maybe this will help someone if you are stuck on 18.1 for some reason and this is happening to you.
Doesn't happen to us with 19.1 or 20.0 with 5G enabled in preferred network type.
cheers...
Last edited:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
32
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions :
Downloads :
Reporting Bugs
- DO NOT Report bugs if you're running a custom kernel or you installed Xposed
- Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
- If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
- If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Code: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:8LineageOS 19/19.1 might be coming, just tried a repo sync and it's grabbing source for SM8350
Definitely not quite ready yet though...
65
There's always night somewhere in the world during the time they are compiled.4
We only claim to support retail devices. While carrier branded devices will likely work just fine, we don't have instructions for these nor do we guarantee them working.
New posts
-
[Tutorial] Crossflash, Bypass OPID Mismatched Error- Latest: micallan_17
