I've recently tried the new Beanstalk ROM, my first custom since trying the stock AT&T JB for several weeks. I'm finding that I have a perpetual NFC wakelock that cannot be corrected by freezing the Nfc Service, and turning off NFC via settings isn't possible (those options are disabled and cannot be changed.) Logcat is showing failures with firmware downloads ... see attached.
Is anyone aware of issues with the stock JB release that causes custom ROMs to freak out after using it? Has anyone had any luck using other CM 10.1-based ROMs after trying the stock JB? I haven't seen others reporting this issue that I could find, but I did find some similar reports from other devices on previous versions of CM.
I'm ready to accept this is an isolated incident but wanted to see if others have had luck before I spend hours trying other ROMs to rule it out. Thanks a ton.
Wallcrawler77 said:
I've recently tried the new Beanstalk ROM, my first custom since trying the stock AT&T JB for several weeks. I'm finding that I have a perpetual NFC wakelock that cannot be corrected by freezing the Nfc Service, and turning off NFC via settings isn't possible (those options are disabled and cannot be changed.) Logcat is showing failures with firmware downloads ... see attached.
Is anyone aware of issues with the stock JB release that causes custom ROMs to freak out after using it? Has anyone had any luck using other CM 10.1-based ROMs after trying the stock JB? I haven't seen others reporting this issue that I could find, but I did find some similar reports from other devices on previous versions of CM.
I'm ready to accept this is an isolated incident but wanted to see if others have had luck before I spend hours trying other ROMs to rule it out. Thanks a ton.
Click to expand...
Click to collapse
I've also had similar issues with persistent NFC Wakelocks. The only resolution for me was replacing the NFC.apk with a modified version from here. Hopefully that does the trick for you. It's improved my battery life dramatically and I've used it on countless CM 10.1-based ROMs.
mrfeuss said:
I've also had similar issues with persistent NFC Wakelocks. The only resolution for me was replacing the NFC.apk with a modified version from here. Hopefully that does the trick for you. It's improved my battery life dramatically and I've used it on countless CM 10.1-based ROMs.
Click to expand...
Click to collapse
Thanks for this info, I appreciate it. I'm holding off on CM10.1-based builds for a while until they get stable again, but will keep this in my back pocket if I encounter the same. It sounds like only a few folks had this wakelock and it wasn't widespread after all. Weird.
I have received my 1+1 a couple of days ago. Straight away I realised the poor battery life. Well, by poor I mean comparing it to some people and how they praise it.
I have flashed Lollipop but I totally hated the Ui - it seemed so small (status bar) I think it was the slim kat ROM. Battery life still wasn't phenomenal. Using both, stock cm11s and few Lollipop custom roms I came to a conclusion that right now, there is not even a single STABLE ROM. By stable i mean no FCs and decent battery life. I surely can't be right, don't know if my phone is faulty or if I'm doing something wrong. I also came across different versions of CM11s? Something like 44s or something like that. Could someone explain it to me since I can't find the answer anywhere to what it's referring to? Also apparently one version is "better" than the other? Here are my questions relating to my problems. As of today, what is the most stable ROM for our fantastic device? Be it kit kat or Lollipop (though I prefer kit kat) What is the difference between cyanogenmod 11s and cyanogenmod 11? Am I better off (stability and battery wise) flashing cm12 nightlies or stay on stock 11s? I will add that i have searched and browsed through the forum for answers but I simply couldn't find anything either specific enough or simple to understand. I know that I should be trying all the ROMs by myself but it would take me forever to decide which one is the best for me. Many of you guys have tried most if not all of them and can give me a feedback I hope which I appreciate very much. Thanks for your time.
dav-rmd said:
I have received my 1+1 a couple of days ago. Straight away I realised the poor battery life. Well, by poor I mean comparing it to some people and how they praise it.
I have flashed Lollipop but I totally hated the Ui - it seemed so small (status bar) I think it was the slim kat ROM. Battery life still wasn't phenomenal. Using both, stock cm11s and few Lollipop custom roms I came to a conclusion that right now, there is not even a single STABLE ROM. By stable i mean no FCs and decent battery life. I surely can't be right, don't know if my phone is faulty or if I'm doing something wrong. I also came across different versions of CM11s? Something like 44s or something like that. Could someone explain it to me since I can't find the answer anywhere to what it's referring to? Also apparently one version is "better" than the other? Here are my questions relating to my problems. As of today, what is the most stable ROM for our fantastic device? Be it kit kat or Lollipop (though I prefer kit kat) What is the difference between cyanogenmod 11s and cyanogenmod 11? Am I better off (stability and battery wise) flashing cm12 nightlies or stay on stock 11s? I will add that i have searched and browsed through the forum for answers but I simply couldn't find anything either specific enough or simple to understand. I know that I should be trying all the ROMs by myself but it would take me forever to decide which one is the best for me. Many of you guys have tried most if not all of them and can give me a feedback I hope which I appreciate very much. Thanks for your time.
Click to expand...
Click to collapse
I have tried BlissPop, but basically came up to same conclusions as you, battery life was worse than stock, and the UI still feels a little quirky. Switched back to stock. I believe the most stable ROM would be the current stock CM 11S:
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Also, OnePlus team is working on getting CM 12S released soon:
CM 12S: The official OTA update for the OnePlus One will be released on or before March 30, 2015
Click to expand...
Click to collapse
Ah thank you. Looks like I'll be staying on the stock then until the release of oxygen os and cm12s.
dav-rmd said:
Ah thank you. Looks like I'll be staying on the stock then until the release of oxygen os and cm12s.
Click to expand...
Click to collapse
Slim ROM has a smaller status bar because it uses a lower DPI, therefore fitting more onto the display at once. Anyway, I run Vanir-Exodus and my battery life is fantastic.
Transmitted via Bacon
Cyanogen worked with OnePlus to release a dedicated version for OnePlus One (CM11S)
I believe Cyanogen released themselves Cyanogemod 11 that is compatible with OnePlus One (CM11). Im not 100% sure.
There are slight differences between them.
There wont be a CM12S. It will be released simply as CM12 and be compatible with the OnePlus One.
In theory, CM11S should be the most stable. The source is available: https://github.com/CyanogenMod/android_device_oneplus_bacon
timmaaa said:
Slim ROM has a smaller status bar because it uses a lower DPI, therefore fitting more onto the display at once. Anyway, I run Vanir-Exodus and my battery life is fantastic.
Transmitted via Bacon
Click to expand...
Click to collapse
Is it stable though? I am back on stock and can't really complain other than battery life everything else seems fine. Funny thing : I'm not even using LTE! :/
riahc3 said:
Cyanogen worked with OnePlus to release a dedicated version for OnePlus One (CM11S)
I believe Cyanogen released themselves Cyanogemod 11 that is compatible with OnePlus One (CM11). Im not 100% sure.
There are slight differences between them.
There wont be a CM12S. It will be released simply as CM12 and be compatible with the OnePlus One.
In theory, CM11S should be the most stable. The source is available: https://github.com/CyanogenMod/android_device_oneplus_bacon
Click to expand...
Click to collapse
What are you talking about? Firstly, CM11 and CM11S are the same ROM except for a couple of proprietary apps. Secondly, there is going to be CM12S, it's being released later this month.
Transmitted via Bacon
---------- Post added at 08:47 ---------- Previous post was at 08:47 ----------
dav-rmd said:
Is it stable though? I am back on stock and can't really complain other than battery life everything else seems fine. Funny thing : I'm not even using LTE! :/
Click to expand...
Click to collapse
Yes. As stable as a ROM can get.
Transmitted via Bacon
Thanks guys! Though I'm still confused about the versions of software. The whole 44s thing confuses me. Any ideas?
dav-rmd said:
Thanks guys! Though I'm still confused about the versions of software. The whole 44s thing confuses me. Any ideas?
Click to expand...
Click to collapse
What about it confuses you? 44S is a build build number of CM11S, they were released like this: 22R > 25R > 30O > 33R > 38S > 44S > 05Q
Transmitted via Bacon
timmaaa said:
What are you talking about? Firstly, CM11 and CM11S are the same ROM except for a couple of proprietary apps.
Click to expand...
Click to collapse
Wait; How can you say they are the same ROM and then say "except for a couple of proprietary apps"? That automatically means its not the same ROM :S
Here is the thing CM11 started to roll out around end of 2013. CM11S is based on a CM11 that was released in April 2014. There are fixes, proprietary apps, etc. you mentioned. CM11, at the end of 2013, was released for all devices at the same time and the code is exactly the same. It isnt exactly the same as CM11s
timmaaa said:
Secondly, there is going to be CM12S, it's being released later this month.
Click to expand...
Click to collapse
I really have my doubts on that. I know that was announced but....I think its gonna be CyanogenMod 12 period, released for S5, M8, etc........and OnePlus One (bacon). I dont think they are going to make another specialized for OnePlus One (unless of course there is a legal obligation, and even so, I wont trust it too much)
Oh cheers. I've read that say 05q has a terrible battery life, where as 44s is best of them all. The part that confused me was that I didn't know it was referring to cm11s. Thanks for clearing that out.
riahc3 said:
Wait; How can you say they are the same ROM and then say "except for a couple of proprietary apps"? That automatically means its not the same ROM :S
Here is the thing CM11 started to roll out around end of 2013. CM11S is based on a CM11 that was released in April 2014. There are fixes, proprietary apps, etc. you mentioned. CM11, at the end of 2013, was released for all devices at the same time and the code is exactly the same. It isnt exactly the same as CM11s
I really have my doubts on that. I know that was announced but....I think its gonna be CyanogenMod 12 period, released for S5, M8, etc........and OnePlus One (bacon). I dont think they are going to make another specialized for OnePlus One (unless of course there is a legal obligation, and even so, I wont trust it too much)
Click to expand...
Click to collapse
You're splitting hairs there. Apps don't make a ROM. The real difference between CM11S and CM11 is that the nightlies (CM11) are ahead in terms of commits (and therefore possibly bugs). CM11S is the "stable" version of CM11, much like a milestone release. Only the first build of CM11S (22R) was based on the CM11 of April 2014. Each successive build of CM11S is based on the state of CM11 nightlies (commits etc) at the time of release of each CM11S build. They are the same ROM. This is a well known fact.
You can have your doubts all you like but it's pure speculation, and it isn't actually based on any facts or verified information. It's just false information spread by baseless rumours. CM12S is currently in the process of being authorized by Google to be released officially. This information is all readily available if you keep up with the information being provided by CM.
battery life
Stick to CM11. I used to get 3.5hr of screen time.
Now that I switched to CM12 nightlies 20150316, I'm down to 2.5hrs of screen time, so 2 full days vs 1.5 days now.
I think 12S will be similar to 11S
CM + extra apps like camera, maxxaudio + hardware specific optimizations like touchscreen, bionic (if that still exists on art)
See Battery in settings to see which app is draining battery
If you havn't already checked which apps are hogging your battery then go over to Settings-->Battery
and then see the apps which are draining your battery.
If Google Play Services is occupying the no.1 spot thne Enable Privacy Guard for it and disable the option for Keep Awake and Wake Up by it.
You can find this in Settings-->Privacy
Another fix is that you disable Gestures(all 3) and also disable 'Wake on double tap'.
https://code.google.com/p/android-developer-preview/issues/detail?id=2556#c104
A google team member states in the issue tracker: "In investigating the bug-reports shared in this tracker we discovered and fixed an issue where the device was waking up unnecessarily.There are some fixes for additional improvements. This particular fix will ship in Android M, and is just one in a number of efforts to improve battery life."
This is for the mobile radio active bug in Android M, which has a few hundred stars. They still have not made a statement or even raised the priority level above low for the mobile radio active bug in Lollipop, despite having thousands of stars.
I will believe it when I see it.
It seems it's currently possible to fix it with a Xposed module. Do you know whether CM and other custom rom teams fixed it in their roms?
DeX1009 said:
It seems it's currently possible to fix it with a Xposed module. Do you know whether CM and other custom rom teams fixed it in their roms?
Click to expand...
Click to collapse
You could also use the app "Mobile Radio PWN"
Those apps don't completely fix it - PWN just stops it from happening when WiFi is on but the radio gets active unnecessarily when there's no WiFi and that's the major issue.
Use tasker to turn it off while screen off or WiFi on...
Sent from my bacon!!!!!
NickosD said:
Use tasker to turn it off while screen off or WiFi on...
Sent from my bacon!!!!!
Click to expand...
Click to collapse
No, that's not what the bug is about. It also includes background processes. You can't turn them all of can you?
Actually with my way, the bug has gone away. It only appears when I am on data and not WiFi to browse Internet. Then I notice the bug, mostly at android os and system.
Sent from my SM-T320
DeX1009 said:
It seems it's currently possible to fix it with a Xposed module. Do you know whether CM and other custom rom teams fixed it in their roms?
Click to expand...
Click to collapse
As I recall, the Xposed module did not fix the issue, and the thread for it was closed almost immediately as a result. I see a lot of messages in various places mentioning this fix, but as far as I know, nobody ever successfully fixed the issue...
http://forum.xda-developers.com/xperia-zl/general/cm12-1-cell-standby-mobile-radio-active-t3188147
People are starting to report their MM battery stats. Some say it is much better than LP and some say there is little difference since they are still only getting 3.5 hours SOT before the battery dies due to the mobile radio active bug. Me - I am happy since a new version of SlimKat was released for the Oneplus One about a month ago. It works fine which is good since I may be using it until Android N is released next year.
Hi
I have not jumped ship from CM 12 to 13 yet and was holding off until little bugs have been fixed.
Thinking of doing a full back up and then updating to 13 and get the weekly updates.
Are all the issues around CM 13 been resolved as initially battery drain was bad. I will look at each developers ROMS and see what's the best but any recommendations welcome
So is it best to stay on 12 or bite the bullet and go onto 13?
Only thing I miss from 12 to 13 is the text apps which is crap on 13 (no more search, no delayed sending, no original timestamps).
Aside from this CM13 is pretty stable and better on every point
Hi,
One big functionnality I am missing from CM12 is the possibility for the alarm to turn on the device.
On CM13 if your device is off, you miss your alarms.
I am also wondering this, I'm on Sultans CM12.1 build, and I tried Sultans CM13 but I was getting bad signal which I think was related to doze and also occasional crashes so I moved back to 12. I'm getting the urge to upgrade to Marshmellow again but the signal issues were a problem last time. It may be down to the modem choice though.
hello, someone has already had the opportunity to test this version or has information on this firmware? The build number suggests a fairly significant jump.
It's only a small update, 85.6MB if I remember correctly, so I'm assuming it's just a security update.
I'm a light user and the only real issue I have with the phone is the fingerprint scanner; that still seems to be the same to me.
Why always useles threads like this ?
Its only security patch update with minor fixes but Sony never post that !!
Edit:
Fw 8.1 feels way more faster en snappier ?
All is damn fast and no issues ?
Jitsi Meet after update don't work properly
Jitsi Meet after update don't work properly