Cm14 nightlys / Lineage OS are officially available through your update setting or through www.get.cm!
Known Bugs:
Camera sometimes not working with third party camera apps (snap camera tested, works fine)
No Sim Card - resolved
Flashlight not turning on/off seemingly at random
CM 14 Nightlies changelog :
https://www.cmxlog.com/14.1/hiaeuhl/
https://www.cmxlog.com/14.1/hiaeul/
testing... firts bug, no sim card detected on A9 USA unlocked.
=(
What firmware does this require? And is force encryption still enabled? I haven't updated in months...
djsubtronic said:
What firmware does this require? And is force encryption still enabled? I haven't updated in months...
Click to expand...
Click to collapse
From 1.5x onwards. Encryption is enforced, the boot patcher to disable it still works.
ultramal said:
testing... firts bug, no sim card detected on A9 USA unlocked.
=(
Click to expand...
Click to collapse
Yes, i Suspect it has something to do with the modem firmware Hope it gets fixed in the next nightly,
presumably they will start occurring daily again?
The_scam said:
Yes, i Suspect it has something to do with the modem firmware Hope it gets fixed in the next nightly,
presumably they will start occurring daily again?
Click to expand...
Click to collapse
Intervigil compiled a couple earlier builds of cm 14/14.1 and the radio worked fine on both so I'm sure it's something fairly minor broke in this first official build.
Sent from my HTC One A9 using Tapatalk
The_scam said:
Yes, i Suspect it has something to do with the modem firmware Hope it gets fixed in the next nightly,
presumably they will start occurring daily again?
Click to expand...
Click to collapse
scott8281 said:
Intervigil compiled a couple earlier builds of cm 14/14.1 and the radio worked fine on both so I'm sure it's something fairly minor broke in this first official build.
Click to expand...
Click to collapse
Most likely because this was built by the bot, the one for hiaeuhl didn't even build.
Jenkins is not working quite well, no builds for a couple of days and stopped again now.
Ultramanoid said:
Most likely because this was built by the bot, the one for hiaeuhl didn't even build.
Jenkins is not working quite well, no builds for a couple of days and stopped again now.
Click to expand...
Click to collapse
Are you sure it has stopped? The last build was not 24 hours ago...
Does anyone know when the hiaeuhl version of 14.1 comes out ?
In the device wiki it already shows that 14.1 is supported, but there is no new nightly build to download.
The_scam said:
Are you sure it has stopped? The last build was not 24 hours ago...
Click to expand...
Click to collapse
It builds alphabetically, and it was stopped at bullhead. It seems to be building now again.
It's easy to check at any time : https://jenkins.cyanogenmod.org
It says no SIM for everyone apparently, I would wait to flash. Here's the strange thing: cell standby is using extreme amounts of battery
Update: I did a dirty backflash to an unofficial version, Cell DID not work. Hmm.
The Buildbot is back to work, but just in case, I'm gonna try to build, depends on how much space I have left.
Steve just posted this. I'm hoping he's simply referring to Cyanogen Inc. It looks as though CyanogenMod is progressing along just fine.
Sent from my HTC One A9 using Tapatalk
Why no love for the Sprint version? How hard is it to port it over from the GSM source? I've never tried building a ROM before but I'm willing to learn. Read this page: https://wiki.cyanogenmod.org/w/Doc:_porting_intro and plan on getting a VM set up and working through it this weekend.
The_scam said:
It says no SIM for everyone apparently, I would wait to flash. Here's the strange thing: cell standby is using extreme amounts of battery
Update: I did a dirty backflash to an unofficial version, Cell DID not work. Hmm.
Click to expand...
Click to collapse
Really? I used the unofficial build of cm14.1 for about a solid month without a sim error, how strange...
MGfusion said:
Really? I used the unofficial build of cm14.1 for about a solid month without a sim error, how strange...
Click to expand...
Click to collapse
Yes, but it was dirty.. and a backflash. so some components were most likely ineligible for downgrade
The_scam said:
Yes, but it was dirty.. and a backflash. so some components were most likely ineligible for downgrade
Click to expand...
Click to collapse
Ah, that makes sense. I read to quickly, missed the part that said "dirty flashback"
MGfusion said:
Ah, that makes sense. I read to quickly, missed the part that said "dirty flashback"
Click to expand...
Click to collapse
Yes,
Also, my own build got stopped so I'm gonna use the on being built through the Jenkins buildbot its about 95% done and then gonna upload later
The_scam said:
Yes,
Also, my own build got stopped so I'm gonna use the on being built through the Jenkins buildbot its about 95% done and then gonna upload later
Click to expand...
Click to collapse
I think I'm just going to wait until the builds become a bit more stable, and hang around on the stock sense ROM for a bit
Related
Important!
It is strongly recommended that you flash clockwork recovery via NVFlash. If for some reason this or a future nightly build causes your phone to not boot up, you will not be able to boot into recovery unless you have it flashed via NVFlash.
NVFlash for Linux
NVFlash for Windows
To clear up some confusion, if you flashed your recovery via ROM Manager, you didn't actually flash a recovery. It is what we call a fakeflash, you should still probably flash with NVFlash.
Instructions
Download from http://download.cyanogenmod.com/?device=p999 and flash like you would any other ROM (via recovery or ROM Manager).
Be sure to backup before flashing, and of course a wipe is necessary when coming from stock.
Gapps are available from the usual places, however do not download the version that says it is for Tegra, even though this is a tegra device, as it will not flash.
Mod Edit:
Mikey1022 said:
Google Addon: http://goo-inside.me/google-apps/
Check the lastest package available on top
Click to expand...
Click to collapse
ChrisSoyars Edit:
After skimming some of the posts in this thread, here are some things that you can expect.
What to expect
- Everything working including Wifi, GPS, Audio, Camera, Front Facing Camera
- Screen off animation is not enabled, therefore it isn't broken.
- Occasional audio problems (as far as I know they have not been fixed). If audio does not play just reboot.
- Automagical brightness weridness, this is controlled by the kernel and not userspace, even having it working is very hacky.
are the battery drivers still borked?
jumaaneface said:
are the battery drivers still borked?
Click to expand...
Click to collapse
yes, yes they are
What exactly is a nightly? Is it just like an alpha build or something? I never understood the term.
booch137 said:
What exactly is a nightly? Is it just like an alpha build or something? I never understood the term.
Click to expand...
Click to collapse
Exactly what the name implies....they make a build nightly. Consider it beta.
booch137 said:
What exactly is a nightly? Is it just like an alpha build or something? I never understood the term.
Click to expand...
Click to collapse
They are also usually buggy; so if that isn't your thing, I would avoid flashing CM 7 (or 7.1) until it's final release.
Interesting... thanks for the reply.
thanks for this. I was syncing my repo and was going to compile from source, any reason as to not continue?
Ducter said:
thanks for this. I was syncing my repo and was going to compile from source, any reason as to not continue?
Click to expand...
Click to collapse
ChrisSoyars tweeted half an hour ago that he is about to do the first nightly build.
Does this fix the reboot problem?
Sent from my LG-P999 using XDA App
MWBehr said:
Exactly what the name implies....they make a build nightly. Consider it beta.
Click to expand...
Click to collapse
I'd call it more in the pre-alpha to alpha stages myself
momentarylapseofreason said:
I'd call it more in the pre-alpha to alpha stages myself
Click to expand...
Click to collapse
We don't do nightly builds until most everything is working, our nightly builds are "beta" status. We don't externally "alpha" test.
ctso said:
We don't do nightly builds until most everything is working, our nightly builds are "beta" status. We don't externally "alpha" test.
Click to expand...
Click to collapse
Is bluetooth and wifi working on this build?
Google Addon: http://goo-inside.me/google-apps/
Check the lastest package available on top
CM7!!!!!!!!!!! <3 thanks!!!!
Just downloaded it ... CANT WAIT !!! ill keep you guys updated with any bugs or issues
First build it up!!!!
AHAHAHHAAHAH Im 2 !!! yeeaaaaaaaaaaaa
every BODY FLASH FLASH lol
graffixnyc said:
First build it up!!!!
Click to expand...
Click to collapse
damn dude u first !!!
I'm in the middle of downloading and the damn thing reboots...
Important!
It is strongly recommended that you flash clockwork recovery via NVFlash. If for some reason this or a future nightly build causes your phone to not boot up, you will not be able to boot into recovery unless you have it flashed via NVFlash.
NVFlash for Linux
NVFlash for Windows
To clear up some confusion, if you flashed your recovery via ROM Manager, you didn't actually flash a recovery. It is what we call a fakeflash, you should still probably flash with NVFlash.
Instructions
Download from http://download.cyanogenmod.com/?device=p999 and flash like you would any other ROM (via recovery or ROM Manager).
Be sure to backup before flashing, and of course a wipe is necessary when coming from stock.
Gapps are available from the usual places, however do not download the version that says it is for Tegra, even though this is a tegra device, as it will not flash.
Mod Edit:
Mikey1022 said:
Google Addon: http://goo-inside.me/google-apps/
Check the lastest package available on top
Click to expand...
Click to collapse
ChrisSoyars Edit:
After skimming some of the posts in this thread, here are some things that you can expect.
What to expect
- Everything working including Wifi, GPS, Audio, Camera, Front Facing Camera
- Screen off animation is not enabled, therefore it isn't broken.
- Occasional audio problems (as far as I know they have not been fixed). If audio does not play just reboot.
- Automagical brightness weridness, this is controlled by the kernel and not userspace, even having it working is very hacky.
Any reference to the first thread you need too look up, it's linked here:
http://forum.xda-developers.com/showthread.php?t=1058131
Changelog:
http://cm-nightlies.appspot.com/?device=p999
Thanks!!! Flashing
Is the server still down? The latest I see is 2011-5-25.
gamefreakgcb said:
Is the server still down? The latest I see is 2011-5-25.
Click to expand...
Click to collapse
I don't know whether it is still down or not, but yeah, that's still the latest build
Hrmm awesome, what about the battery stats? Anyone know if that has been fixed?
G2X & Nexus S
brian6685 said:
Hrmm awesome, what about the battery stats? Anyone know if that has been fixed?
G2X & Nexus S
Click to expand...
Click to collapse
Not on cm7 but Faux has made good progress with the help of debauchedsloth
So does this mean nightlies will resume soon?
edit, nvm oops
G2x with faux AOSP and faux orange kernel. [email protected] 5107 quadrant.
For anybody interested this is a build I just compiled about an hour ago
http://www.multiupload.com/6WEZDZMGSX
WHy a new thread? what is new?
aim1126 said:
For anybody interested this is a build I just compiled about an hour ago
http://www.multiupload.com/6WEZDZMGSX
Click to expand...
Click to collapse
How is your compile different from the gigglebread one from this morning?
jawknee530 said:
How is your compile different from the gigglebread one from this morning?
Click to expand...
Click to collapse
I dot think there's any really maybe one or two commits that got merged throughout the day. I just like compiling my own builds
Sent from my LG-P999 using XDA App
I see this thread kinda senseless as there isn't a newer nightly that was available before using the old thread. Although 2 pages seems more manageable then 300+ (which will happen eventually to this thread.)
Being a website developer I know these threads add up pretty quickly (hurray xda!)
I haven't flashed an actual CM rom in almost a week since the server crash. Hopefully the new thread is a sign that the server was repaired and new nightlies are on the way. Using the latest KANGS to get my fix, I know there is lots of progress. Running the latest KANG from today I think the rom is almost ready for a stable release after a few bugs get worked out.
I think the work you guys are doing is fantastic and much appriciated, although it may seem all we do is ***** half the time. Android wouldn't be the same without all of the developers leading the way. Big props. Hope all is well and I plan to continue to follow your work.
aim1126 said:
For anybody interested this is a build I just compiled about an hour ago
http://www.multiupload.com/6WEZDZMGSX
Click to expand...
Click to collapse
Just installed, cheers!
And thanks CM, I'm coming from #34 and just five minutes in its obvious there's been quite a bit of work done. Status Bar brightness slider is sweet.
i see a build 36 but it won't let me download? says its not found...
shniggies said:
i see a build 36 but it won't let me download? says its not found...
Click to expand...
Click to collapse
Probably still being built. Give it some time and check again.
Sounds like buildbot may be back up... this would be nice. <3
reisaru said:
Probably still being built. Give it some time and check again.
Sounds like buildbot may be back up... this would be nice. <3
Click to expand...
Click to collapse
ho ho... i must have checked riiiiiiight when it was uploading... because its downloading now
How did you find build 36 when 35 isn't out yet?
Sent from my LG-P999 using XDA App
This thread is for updates of temasek cm12.1 built by myself. I will be building for hlte and hltespr.
Temasek made this all possible and it is all his work I am just taking the time to build and upload.
V19.3+ root removed, you will need to flash SuperSU zip to achieve root.
Downloads:
Hlte or Hlte on my BasketBuild
Hltespr or Hltespr on my BasketBuild
Credits: @temasek
XDA:DevDB Information
Temasek cm-12.1 unofficial cyanogenmod, ROM for the Samsung Galaxy Note 3
Contributors
trader418, Temasek
Source Code: https://github.com/temasek/
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: Cyanogenmod
Version Information
Status: Beta
Created 2016-03-26
Last Updated 2016-03-26
Thanks for keeping support for the Note 3 alive.
Great, good to see 12.1 back alive. Anything I can do to help, just say so.
Thanks again! Always willing to help however I can.
BTW, really good job on creating the thread using just your phone! I've seen FAR worse.
Buslova said:
Thanks again! Always willing to help however I can.
BTW, really good job on creating the thread using just your phone! I've seen FAR worse.
Click to expand...
Click to collapse
Haha thank you, I try my best
Glad to see all of you guys showing support. If I ever don't see temasek updated the version and any of you do just post here and I'll build, however I think most of the time I should be okay. I'm going to set up a straw poll in the include root vs not include. I also could start to use the ota app if you guys really would like that
Straw poll whether to include root in the build here http://strawpoll.me/7191529
trader418 said:
Haha thank you, I try my best
Glad to see all of you guys showing support. If I ever don't see temasek updated the version and any of you do just post here and I'll build, however I think most of the time I should be okay. I'm going to set up a straw poll in the include root vs not include. I also could start to use the ota app if you guys really would like that
Click to expand...
Click to collapse
I will always use root however I understand some people's need for it to be rootless and well, let's be honest, it ain't hard to flash supersu right after flashing the rom. lol.
OTA is a nice lazy option for the USER but I've gathered from past posts in other threads that it's not always so easy for the dev since the OTA app is maintained/owned by another dev and sometimes has issues. Again, we're talking about a community here who is flashing custom roms on their devices. Manually downloading and flashing shouldn't be a major issue.
Having said all that, if i were to vote I'd say:
Built-in root: No
OTA: Yes (if it's not a headache)
Buslova said:
I will always use root however I understand some people's need for it to be rootless and well, let's be honest, it ain't hard to flash supersu right after flashing the rom. lol.
OTA is a nice lazy option for the USER but I've gathered from past posts in other threads that it's not always so easy for the dev since the OTA app is maintained/owned by another dev and sometimes has issues. Again, we're talking about a community here who is flashing custom roms on their devices. Manually downloading and flashing shouldn't be a major issue.
Having said all that, if i were to vote I'd say:
Built-in root: No
OTA: Yes (if it's not a headache)
Click to expand...
Click to collapse
Ota isn't too bad, I'll probably use it soon tbh, but I won't promise anything
hey guys, I have been having trouble with tema's cm 13 builds so i decided to give 19.1 a shot. Unfortunately, I haven't had any luck with the rom. The rom just boot loops after every installation. I have tried with gapps aroma and pico with different wipes with no luck. continues to bootloop as soon as I reboot and i never get into the rom. I am back on tema's for now but would love to switch to 19.1 if I could get some help. Sorry for being a noob, Im probably messing something up somewhere and I thank you for your help in advance!
redfuryjr55 said:
hey guys, I have been having trouble with tema's cm 13 builds so i decided to give 19.1 a shot. Unfortunately, I haven't had any luck with the rom. The rom just boot loops after every installation. I have tried with gapps aroma and pico with different wipes with no luck. continues to bootloop as soon as I reboot and i never get into the rom. I am back on tema's for now but would love to switch to 19.1 if I could get some help. Sorry for being a noob, Im probably messing something up somewhere and I thank you for your help in advance!
Click to expand...
Click to collapse
Start with which device you have
trader418 said:
Start with which device you have
Click to expand...
Click to collapse
haha sorry! htlespr!
redfuryjr55 said:
haha sorry! htlespr!
Click to expand...
Click to collapse
I'm not sure mate, has anyone else got any suggestions?
There has been reports of multiple wipes and reboots and then flashing the ROM helps but I cannot say it will help
trader418 said:
I'm not sure mate, has anyone else got any suggestions?
There has been reports of multiple wipes and reboots and then flashing the ROM helps but I cannot say it will help
Click to expand...
Click to collapse
hmmm.. well I managed to get booted by installing temasek's last build (12.9 i think, the one from jan) along with his kernel. It booted fine and made it into setup. I then rebooted to recovery and dirty flashed you 19.1. Got bootlooped and said fk it and re-flashed the kernel and got into 19.1! Now that is great and all, but super weird/inconsistent. Also, once I got everything set up I could not turn on wifi or bluetooth; is this a known issue with a fix? Also, are there recommended installation instructions or is there a recommended kernel for you build? Thanks in advance for your help and patience with my noobness! Again I am on htlespr!
redfuryjr55 said:
hmmm.. well I managed to get booted by installing temasek's last build (12.9 i think, the one from jan) along with his kernel. It booted fine and made it into setup. I then rebooted to recovery and dirty flashed you 19.1. Got bootlooped and said fk it and re-flashed the kernel and got into 19.1! Now that is great and all, but super weird/inconsistent. Also, once I got everything set up I could not turn on wifi or bluetooth; is this a known issue with a fix? Also, are there recommended installation instructions or is there a recommended kernel for you build? Thanks in advance for your help and patience with my noobness! Again I am on htlespr!
Click to expand...
Click to collapse
All I know is that all my hlte builds are tested with a clean wipe and then a flash and reboot. I have no problems. I am using temaseks device tree so the only difference between his and my build should technically be root and ota app. Other than that it should be identical
trader418 said:
All I know is that all my hlte builds are tested with a clean wipe and then a flash and reboot. I have no problems. I am using temaseks device tree so the only difference between his and my build should technically be root and ota app. Other than that it should be identical
Click to expand...
Click to collapse
I am using this as my daily Rom, the only problems I get are the weather widget doesn't update and it wont connect to the wifi in my local hospital, I am using build v19.0 build date 17th of march, even my s-pen works !
I will test this later and post back results
swukjay said:
I am using this as my daily Rom, the only problems I get are the weather widget doesn't update and it wont connect to the wifi in my local hospital, I am using build v19.0 build date 17th of march, even my s-pen works !
I will test this later and post back results
Click to expand...
Click to collapse
Either change weather provider to another or customize your location. Sometimes yahoo weather isn't working well.
As for WiFi, check your dev options.
redfuryjr55 said:
haha sorry! htlespr!
Click to expand...
Click to collapse
Just in case - have updated your Modem and Bootloader to the latest? All wireless related problems might be connected to it.
eseregin said:
Just in case - have updated your Modem and Bootloader to the latest? All wireless related problems might be connected to it.
Click to expand...
Click to collapse
what modem/baseband should i use for htlespr? what is tested and working, does anyone know?
redfuryjr55 said:
what modem/baseband should i use for htlespr? what is tested and working, does anyone know?
Click to expand...
Click to collapse
Hmm, still no luck eh? I tried helping ya last night in the other thread. I'm also a hltespr user. I'm still running OH1 baseband however OK2 is the latest. Also, as I told you last night, I'm using an older version of TWRP recovery (ver. 2.8.7) however the latest is 3.0.0.
What baseband are YOU running? Go to settings, "About phone", and look for "Baseband version" and let us know. =)
redfuryjr55 said:
what modem/baseband should i use for htlespr? what is tested and working, does anyone know?
Click to expand...
Click to collapse
Sorry, I have different phone..
Might be the latest here
https://idlekernel.com/flash-tools/firmware/hltespr_SM-N900P/N900PVPUEOK2/
But I am far away from sure
Are there any actual stable 7.1.2 roms? I've tried lineage os 14.1 and it gave me random reboots quite often. Is everything that is based on lineage os having these problems? Are there any not based on lineage? Or are there any stable ones with very few problems? Cheers.
OathYvne said:
Are there any actual stable 7.1.2 roms? I've tried lineage os 14.1 and it gave me random reboots quite often. Is everything that is based on lineage os having these problems? Are there any not based on lineage? Or are there any stable ones with very few problems? Cheers.
Click to expand...
Click to collapse
Try RR man.
Sent from my Honor 8 using XDA Labs
Honestly, no. All give me random reboots and none that I've seen take pictures as well as stock. As RR is also based on OpenKirin's device tree, it will also result in reboots to erecovery.
I'm sticking to stock at the moment.
Skeletor916 said:
Honestly, no. All give me random reboots and none that I've seen take pictures as well as stock. As RR is also based on OpenKirin's device tree, it will also result in reboots to erecovery.
I'm sticking to stock at the moment.
Click to expand...
Click to collapse
try
AOKP and LEGEND ROM
Skeletor916 said:
Honestly, no. All give me random reboots and none that I've seen take pictures as well as stock. As RR is also based on OpenKirin's device tree, it will also result in reboots to erecovery.
I'm sticking to stock at the moment.
Click to expand...
Click to collapse
Did you even try the latest updates? I've been using RR for over a month. Zero random reboot.
Sent from my Honor 8 using XDA Labs
adriansticoid said:
Did you even try the latest updates? I've been using RR for over a month. Zero random reboot.
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
Did you even read the comments on the thread over there? Did you even see that there are many reports of other people with those exact same issues? Did you, even?
Glad it's working for you.
Skeletor916 said:
Did you even read the comments on the thread over there? Did you even see that there are many reports of other people with those exact same issues? Did you, even?
Glad it's working for you.
Click to expand...
Click to collapse
Did you even get my point? I'm not the only one having it working properly. Yeah there are many complaints, but not 100% of the users who flashed it have the problems. Might as well try it yourself. It's better than reading the comments.
Sent from my Honor 8 using XDA Labs
adriansticoid said:
Did you even get my point? I'm not the only one having it working properly. Yeah there are many complaints, but not 100% of the users who flashed it have the problems. Might as well try it yourself. It's better than reading the comments.
Click to expand...
Click to collapse
Apparently you don't even read your own comments... OP's question is about STABLE roms... In your own words, the rom you mentioned has "many complaints" about it...
....
....
And again, as I said, many OTHER people mention having those same problems. As in, I had them as well. Stop making assumptions about what I have or haven't done, especially when it's there in my words. I'm going to go back to lurking now, not that I imagine that will stop you.
Skeletor916 said:
Apparently you don't even read your own comments... OP's question is about STABLE roms... In your own words, the rom you mentioned has "many complaints" about it...
....
....
And again, as I said, many OTHER people mention having those same problems. As in, I had them as well. Stop making assumptions about what I have or haven't done, especially when it's there in my words. I'm going to go back to lurking now, not that I imagine that will stop you.
Click to expand...
Click to collapse
please don't be so rude
OathYvne said:
Are there any actual stable 7.1.2 roms? I've tried lineage os 14.1 and it gave me random reboots quite often. Is everything that is based on lineage os having these problems? Are there any not based on lineage? Or are there any stable ones with very few problems? Cheers.
Click to expand...
Click to collapse
Try the latest carbon rom ..
https://forum.xda-developers.com/honor-8/development/rom-carbon-rom-honor8-t3636749
You will love it for sure..
OathYvne said:
Are there any actual stable 7.1.2 roms? I've tried lineage os 14.1 and it gave me random reboots quite often. Is everything that is based on lineage os having these problems? Are there any not based on lineage? Or are there any stable ones with very few problems? Cheers.
Click to expand...
Click to collapse
Yes, the ALL unstable if you have GPS enabled. Some of them don't allow you to switch between 3G/4G (the switch just doesn't do anything), none of them can show the actual GSM signal strength and none of them even close as fast as EMUI 5.
So if you are 22+, you have a job, use you phone for calls, use navigation in a car or Uber to call taxi (thus, live in a city), none of them can be considered as stable.
And if our honorable developers would write all this it there OPs, rather "fast and stable" or "BUGS - you tell me", they would save me several hours.
I've installed a variety of custom ROMs on my OP9 (EvolutionX, Nameless, Extended) and they all have the exact same problem: audio doesn't work properly, buggy, randomly would not connect to my Google account, etc. Since they all had the exact same issues, my guess is that it's a problem with my phone and not the ROMs themselves.
Does somebody know anything about the problem and what can I do to fix them? I'm fed up with OOS and would really like to use another ROM.
Ok everything you have listed is built from Lineage aosp. Therefore everything is gonna have same bug. If you notice the lemonade/p official lineage builds have stopped around the 12th and 14th of February .New ones are coming soon with merged patch that fixes all issues. Then devs from other roms will build on new fixed source and so on. Like throwing a pebble in a pond. Takes time for the ripple to get out. Watch lineage os website/downloads/op9
rodri_rebag5 said:
I've installed a variety of custom ROMs on my OP9 (EvolutionX, Nameless, Extended) and they all have the exact same problem: audio doesn't work properly, buggy, randomly would not connect to my Google account, etc. Since they all had the exact same issues, my guess is that it's a problem with my phone and not the ROMs themselves.
Does somebody know anything about the problem and what can I do to fix them? I'm fed up with OOS and would really like to use another ROM.
Click to expand...
Click to collapse
maybe you flashing over incompatible firmware
mattie_49 said:
Ok everything you have listed is built from Lineage aosp. Therefore everything is gonna have same bug. If you notice the lemonade/p official lineage builds have stopped around the 12th and 14th of February .New ones are coming soon with merged patch that fixes all issues. Then devs from other roms will build on new fixed source and so on. Like throwing a pebble in a pond. Takes time for the ripple to get out. Watch lineage os website/downloads/op9
Click to expand...
Click to collapse
That makes a lot of sense. I was wondering how the same issues presented with every ROM I installed. Thanks for the reply, I will wait for the new builds to start rolling out and then test them again.
Eric_Lev said:
In progress ... Be patient !
https://review.lineageos.org/c/LineageOS/android_kernel_oneplus_sm8350/+/349350
Workaround : https://forum.xda-developers.com/t/rom-official-lemonade-13-lineageos-20.4536697/post-88176351
Edit about workaround : 4 days of uptime without the binder issue.
Click to expand...
Click to collapse
Try the workaround until the fix is included.
downhere said:
Try the workaround until the fix is included.
Click to expand...
Click to collapse
This looks very promising, apparently it solves most of the issues I was experiencing. The only thing I'm scared of is that issues such as my Google account not loading would not be fixed.
rodri_rebag5 said:
This looks very promising, apparently it solves most of the issues I was experiencing. The only thing I'm scared of is that issues such as my Google account not loading would not be fixed.
Click to expand...
Click to collapse
That setup with cached_apps_freezer fixes the Google issues. No issues for me any more.
downhere said:
That setup with cached_apps_freezer fixes the Google issues. No issues for me any more.
Click to expand...
Click to collapse
Then it's a miracle, I genuinely thought this was unfixable. Thanks a lot.
Just to clarify, do I run the command in stock OOS or once I've installed the ROM?
rodri_rebag5 said:
That makes a lot of sense. I was wondering how the same issues presented with every ROM I installed. Thanks for the reply, I will wait for the new builds to start rolling out and then test them again.
Click to expand...
Click to collapse
It's binder issues
rodri_rebag5 said:
Then it's a miracle, I genuinely thought this was unfixable. Thanks a lot.
Just to clarify, do I run the command in stock OOS or once I've installed the ROM?
Click to expand...
Click to collapse
After you've installed build.
rodri_rebag5 said:
Then it's a miracle, I genuinely thought this was unfixable. Thanks a lot.
Just to clarify, do I run the command in stock OOS or once I've installed the ROM?
Click to expand...
Click to collapse
You can use Developer Options of the custom ROM.
Thanks for all the answers, I will flash a ROM probably later tonight and try the cached_apps_freezer fix.