Related
Given the recent explosion of nightly users, there is a need for a place to discuss them, and/or ask if other users are having similar issues as you...this is that place
DO NOT: Post to the bug tracker
DO NOT: Open another thread (Please)
DO NOT: Think of this as official forum support; this thread will be strictly user to user support. Don't expect CM-dev help.
Code:
** These CyanogenMod builds are highly experimental and unsupported.
**
** Please refrain from submitting bug reports for any issues
** you may encounter while running one of these builds.
**
** Submitting bug reports on nightly builds is the leading
** cause of male impotence.
Download: link
Google Apps addon:
Mirror: link
Mirror: linkChangelog: @cmsrc
Ah, and the daily flashing addiction begins again... like smack, but for geeks
Thanks guys! Downloading nightly #0 now
Sorry, I'm noob in CM story, what is nightlies? The intermediate version between stable versions? Why no bug repports? There is official forum where bugs are reported?
200mpx said:
Sorry, I'm noob in CM story, what is nightlies? The intermediate version between stable versions? Why no bug repports? There is official forum where bugs are reported?
Click to expand...
Click to collapse
Nightly builds are published test builds and unsupported. They always have been. They are experimental, volatile and too many issues come and go to be clogging up the bug tracker (intended for releases) with them. These are NOT primarily for users; they are to test the build process and for developers and device maintainers to evaluate. They are shared with users under these conditions, so you can use them or not, but issues with nightly builds are categorically rejected in the bug tracker. Hence; threads like this.
If I'm running the RC0 now, do I just flash it on top or do a clean install? And are the subsequent nightlies flashed on top or clean install every time?
Sent from my Incredible S using XDA App
The nightlies aren't for everyday use, and they can also not work at all (i.e bootloop). If you need to ask questions, chances are you should probably stick with RC0
Like attn said the nightlies are for devs and device maintainers, and more advanced users who are interested in the very, very latest code but they are totally unsupported releases, hence the no bug reports & questions angle. If a particualr nightly gives good performance increase or a new feature that is sought after, you will probably hear about people using a particular nightly n the forums, in which case it tends to be safe to flash it like a normal ROM (yet still totally unsupported)
Cardiiiii said:
If I'm running the RC0 now, do I just flash it on top or do a clean install? And are the subsequent nightlies flashed on top or clean install every time?
Sent from my Incredible S using XDA App
Click to expand...
Click to collapse
I thiink this one is safe to flash over RC0.
It should fix the flashlight issue.
attn1 said:
I thiink this one is safe to flash over RC0.
It should fix the flashlight issue.
Click to expand...
Click to collapse
Yes and yes, flashed straight over RC0 and torch works on high brightness without breaking screen backlight
One more small bug in rc0 theusing the defaultv videos app when I play a video the keyboard light turns off..
Sent from my HTC Incredible S using XDA Premium App
Had issue #1 in the nightly #1 (06/24) as well. On Nightly #2 (06/25) and I still have that issue and have noticed another one. Can someone confirm if they have it too?
1) Switching cameras (front to back and vice versa) freezes camera. Camera doesn't work until I reboot. Once rebooted, the camera shows the image from the camera you selected fine. Might be an issue with the code not properly initializing the camera from which data is to be taken or not properly releasing the camera being used first.
2) In the music player, the progress bar seems a bit off.. there is a disconnect. If someone can tell me how to take a good screenshot, I will
A (rather) lame way to show it in ASCII would be..
---------__O-------------
when it should be..
-----------O-------------
Can anyone confirm?
Yeah there is some camera bug in the latest nightly, worked fine the first time after flashing, but black screen and crashing since then.
Sent from my Incredible S using XDA App
Cardiiiii said:
Yeah there is some camera bug in the latest nightly, worked fine the first time after flashing, but black screen and crashing since then.
Sent from my Incredible S using XDA App
Click to expand...
Click to collapse
Bizarrely, I can still make the camera work if I launch it using WidgetLocker (my custom lockscreen replacement app) but I suffer the blackout bug if I try and launch it from the drawer or a homescreen shortcut.
FYI, Nightly #3 is out.. time to go grab it!
http://download.cyanogenmod.com/?device=vivo
John Anderton said:
FYI, Nightly #3 is out.. time to go grab it!
http://download.cyanogenmod.com/?device=vivo
Click to expand...
Click to collapse
Seems that I have battery drain with this version. Also my camera started to crash after some time
Sent from my Incredible S using Tapatalk
200mpx said:
Seems that I have battery drain with this version. Also my camera started to crash after some time
Sent from my Incredible S using Tapatalk
Click to expand...
Click to collapse
Nice to know it wasn't just me.
It lasted me 19 hours 50mins from 100% to 48%. 3 hours later, it went to 8% and needed a charge
Flashed RC1. Let's hope it does well Charging up the battery now
Camera works well.. No issues with it so far in a brief test.
Had noticed another issue in Nightly 3. Was playing music and the phone auto switched off for power save. A couple of mins later I hit vol up for vol increase and the player skipped to the next song
Wasn't able to reproduce it since.
John Anderton said:
Nice to know it wasn't just me.
It lasted me 19 hours 50mins from 100% to 48%. 3 hours later, it went to 8% and needed a charge
Flashed RC1. Let's hope it does well Charging up the battery now
Camera works well.. No issues with it so far in a brief test.
Had noticed another issue in Nightly 3. Was playing music and the phone auto switched off for power save. A couple of mins later I hit vol up for vol increase and the player skipped to the next song
Wasn't able to reproduce it since.
Click to expand...
Click to collapse
Haha, I had that strange pattern too, 18h and 55% left, and suddenly it started to discharge like a mofo, on Nightlies 4 now, will report if it's any better.
Flashing Nightlies is such an addiction, and the battery life seems stable and the decrease is steady, no drastic reduction.
Cardiiiii said:
Haha, I had that strange pattern too, 18h and 55% left, and suddenly it started to discharge like a mofo, on Nightlies 4 now, will report if it's any better.
Click to expand...
Click to collapse
Had the same issue with RC1 today Will get Nightly 5 now and check
Could you also play a music track and skip half way and check if the seek bar line is a misaligned? I've had that issue from Nightly 2 as well
John Anderton said:
Could you also play a music track and skip half way and check if the seek bar line is a misaligned? I've had that issue from Nightly 2 as well
Click to expand...
Click to collapse
Was that in the default player? I only ask cause Fede's Ubermusic got a fix in beta to fix this exact problem
l0st.prophet said:
Was that in the default player? I only ask cause Fede's Ubermusic got a fix in beta to fix this exact problem
Click to expand...
Click to collapse
The default player. The one which launches when I click "Music".
I've kinda settled on Nightly 5. 36 hours gone and I'm still at 68% charge Will let the run keep going until I have to charge it again
There seems to be plenty of us still suffering sleep deaths on our cappies and I figured an up-to-date list of possible remedies would be nice, just in case there's been any progress in figuring out what causes the problem and how one could go about fixing it.
So far the solutions I've tried that did not work for me...
-Increased minimum clock speed
-Increased voltage of minimum clock speed
-Removed Titanium Backup
-Removed all third party apps
-Disabled deep idle
-Removed/didn't use task killers
-Tried various ICS & JB ROMs
-Tried various ICS and JB kernels, including baked-in versions
-Tried i9000 bootloaders
These are pretty much all the details I have so far on these SoDs, hopefully they add up to a possible cause or explanation...
-SoDs happen anywhere from 1-2 times an hour to 1-2 times a day and only when screen is locked/phone is idle
-Having GrooveIP or Skype running doesn't prevent SoDs, but Pandora Radio running seems to prevent it
-Sometimes on a fresh ROM install I can go about 24-36 hours before the first sleep death, but after that they occur normally
-If I unlock the screen every few minutes it seems to stay on. If I let it sit anywhere from 15-30 minutes or longer then it will usually shut off.
-The only time I can get this phone to not suffer an SoD is on stock software(GB KK4). Not sure what this means, but it is aggravating because I would like to have better software.
What remedies have you tried, and what worked/didn't work for you?
johnnyrichter said:
There seems to be plenty of us still suffering sleep deaths on our cappies and I figured an up-to-date list of possible remedies would be nice, just in case there's been any progress in figuring out what causes the problem and how one could go about fixing it.
So far the solutions I've tried that did not work are...
-Increase minimum clock speed
-Increase voltage of minimum clock speed
-Remove Titanium Backup
-Remove all third party apps
-Oneclick back to stock with most recent GB bootloaders
-Disable deep idle
-Remove/don't use task killers
My sleep-deaths are random, almost always occur over night while I'm asleep, can sometimes happen within seconds or minutes after locking the screen. Leaving apps running also doesn't stop the problem(GrooveIP is always running, Skype is running most of the time).
The only thing that stops sleep deaths on my phone is leaving it plugged in.
What remedies have you tried, and what worked/didn't work for you?
Click to expand...
Click to collapse
The first thing I'd try after disabling deep idle is to change kernel. Also, usually sleep deaths happen even when plugged so yours is kinda special lol.
BWolf56 said:
The first thing I'd try after disabling deep idle is to change kernel. Also, usually sleep deaths happen even when plugged so yours is kinda special lol.
Click to expand...
Click to collapse
I've used all sorts of different kernels and ROMs, get SoDs with everything. Some might result in a day or maybe three days of no sleep deaths, but they eventually start right back up without any sort of a "trigger" to cause it...like changing a certain setting or installing a certain app.
I was hoping someone would have determined the actual cause by now but it seems it's still an unknown factor causing it.
johnnyrichter said:
I've used all sorts of different kernels and ROMs, get SoDs with everything. Some might result in a day or maybe three days of no sleep deaths, but they eventually start right back up without any sort of a "trigger" to cause it...like changing a certain setting or installing a certain app.
I was hoping someone would have determined the actual cause by now but it seems it's still an unknown factor causing it.
Click to expand...
Click to collapse
SoD doesn't happen much with JB, it's usually due to deep idle or bad kernel user config (not saying this is the case here).
Have you tried flashing back to stock KK4 and do a clean flash of whichever ROM you want to use?
If you could narrow down what causes it or get some sort of logcat of when it happens, that would probably help. Although, flashing back to stock still seems like the best bet.
Also, you're running on a nightly build (as per your signature). Ever concidered using a daily (stable) ROM?
BWolf56 said:
SoD doesn't happen much with JB, it's usually due to deep idle or bad kernel user config (not saying this is the case here).
Have you tried flashing back to stock KK4 and do a clean flash of whichever ROM you want to use?
If you could narrow down what causes it or get some sort of logcat of when it happens, that would probably help. Although, flashing back to stock still seems like the best bet.
Also, you're running on a nightly build (as per your signature). Ever concidered using a daily (stable) ROM?
Click to expand...
Click to collapse
I've wiped back to stock numerous times and have used many different stable ICS/JB kernels and ROMs. I've tweaked almost every kernel setting possible, tried all sorts of different overclocks, tried deep idle on and off, etc.
The only time I never had SoDs is when the phone was originally stock. Ever since the first time I rooted and ROM'd it I've been getting sleep deaths. I have not tried actually using stock software again to see if the SoDs go away mainly because I don't want stock software.
johnnyrichter said:
I've wiped back to stock numerous times and have used many different stable ICS/JB kernels and ROMs. I've tweaked almost every kernel setting possible, tried all sorts of different overclocks, tried deep idle on and off, etc.
The only time I never had SoDs is when the phone was originally stock. Ever since the first time I rooted and ROM'd it I've been getting sleep deaths. I have not tried actually using stock software again to see if the SoDs go away mainly because I don't want stock software.
Click to expand...
Click to collapse
That's very unusual. If I were you I'd still try to use stock for testing purpose. Oh and I'm sure you already tried this but don't OC/UV.
If you don't get SoD on stock, try flashing something else that people haven't reported SoD on (like AoCP on stock kernel). Which makes me wonder, have you used a JB rom with it's stock kernel (CM10/AoKP)?
BWolf56 said:
That's very unusual. If I were you I'd still try to use stock for testing purpose. Oh and I'm sure you already tried this but don't OC/UV.
If you don't get SoD on stock, try flashing something else that people haven't reported SoD on (like AoCP on stock kernel). Which makes me wonder, have you used a JB rom with it's stock kernel (CM10/AoKP)?
Click to expand...
Click to collapse
Most ROMs I've tried I kept the stock kernel. I'm also on the stock kernel for CM10 at the moment.
I have tried two different AOSP ROMs with their stock kernels and had SoDs on those as well.
I have also tried no OC with at least three different kernels/ROMs.
johnnyrichter said:
Most ROMs I've tried I kept the stock kernel. I'm also on the stock kernel for CM10 at the moment.
I have tried two different AOSP ROMs with their stock kernels and had SoDs on those as well.
I have also tried no OC with at least three different kernels/ROMs.
Click to expand...
Click to collapse
I'm really running outta ideas here.. This doesn't seem normal. Only other thing I can really think of is either that it's coming from a app or it's a hardware problem (maybe battery but somehow doubt it).
So yeah, only thing I could suggest other than stock KK4 and AoCP is to clean flash without restoring your apps (Gapps are fine of course) and use stock kernel.. After that, I'm all outta ideas.
You got some testing to do, I'll be looking forward to the results.
BWolf56 said:
I'm really running outta ideas here.. This doesn't seem normal. Only other thing I can really think of is either that it's coming from a app or it's a hardware problem (maybe battery but somehow doubt it).
So yeah, only thing I could suggest other than stock KK4 and AoCP is to clean flash without restoring your apps (Gapps are fine of course) and use stock kernel.. After that, I'm all outta ideas.
You got some testing to do, I'll be looking forward to the results.
Click to expand...
Click to collapse
The only apps that have been consecutive across all my different software installations have been...
-Gapps
-Gmail
-Facebook
-Pandora
-GrooveIP
-Heywire
-Skype(Only been using this for a couple of weeks so I can probably rule it out)
I could try a fresh CM10 nightly and only run gapps. Maybe wait a few days and then install GrooveIP, wait a few days and then install Skype, etc until I can maybe get an app install to trigger the SoDs.
You mentioned logcats...what are those? Is this some sort of debug log? If so, do you think it could actually pick up any events leading up to an SoD or even log the SoD itself? I'd imagine if that was possible someone would have posted the results by now.
johnnyrichter said:
The only apps that have been consecutive across all my different software installations have been...
-Gapps
-Gmail
-Facebook
-Pandora
-GrooveIP
-Heywire
-Skype(Only been using this for a couple of weeks so I can probably rule it out)
I could try a fresh CM10 nightly and only run gapps. Maybe wait a few days and then install GrooveIP, wait a few days and then install Skype, etc until I can maybe get an app install to trigger the SoDs.
You mentioned logcats...what are those? Is this some sort of debug log? If so, do you think it could actually pick up any events leading up to an SoD or even log the SoD itself? I'd imagine if that was possible someone would have posted the results by now.
Click to expand...
Click to collapse
A Logcat is simply a log of everything your phone does (Logcat Extreme is a good app for it). You'd have to set it to run in background until a SoD happen and then you'd see w/e your phone did before the SoD happened. Could help narrow down the problem. The only thing I'm not sure is if it will save the log before your phone shuts down but that could be something to look into. If not, then it won't be any help eh.
BWolf56 said:
A Logcat is simply a log of everything your phone does (Logcat Extreme is a good app for it). You'd have to set it to run in background until a SoD happen and then you'd see w/e your phone did before the SoD happened. Could help narrow down the problem. The only thing I'm not sure is if it will save the log before your phone shuts down but that could be something to look into. If not, then it won't be any help eh.
Click to expand...
Click to collapse
I'll check out that app right now and report back with any findings.
johnnyrichter said:
I'll check out that app right now and report back with any findings.
Click to expand...
Click to collapse
Booted phone up just now after an SoD and the only log available is the one it just started. So if it logged anything before it looks like it didn't save it. Crap.
One-clicked back to stock GB KK4 and after a few hours I have yet to get a sleep death so far, but overnight idling will be the final test for that. That's with the following installed...
-GoLauncherEX
-Skype
-Gmail
-Facebook
-Opera
-GrooveIP
-Heywire
While installing all my apps I realized that the GrooveIP installation I was using was an apk I got ages ago, one that I don't think has been automatically updating. I thought maybe that could be the issue so I went with a fresh install from the market.
If it turns out that SoDs only appear when rooted/ROM'd then I'll probably toss this phone once I find a replacement because I can't be without my CM10 and devil kernel. I really wish someone could figure out the cause and a possible solution for this.
johnnyrichter said:
One-clicked back to stock GB KK4 and after a few hours I have yet to get a sleep death so far, but overnight idling will be the final test for that. That's with the following installed...
-GoLauncherEX
-Skype
-Gmail
-Facebook
-Opera
-GrooveIP
-Heywire
While installing all my apps I realized that the GrooveIP installation I was using was an apk I got ages ago, one that I don't think has been automatically updating. I thought maybe that could be the issue so I went with a fresh install from the market.
If it turns out that SoDs only appear when rooted/ROM'd then I'll probably toss this phone once I find a replacement because I can't be without my CM10 and devil kernel. I really wish someone could figure out the cause and a possible solution for this.
Click to expand...
Click to collapse
CM10 features can be found in other ROMs. As for Devil, it could be the problem. Hopefully KK4 will be fine, at least we'll have a start point to work from. If you get SoD on it, get rid of GrooveIP and heywire. We'll then know if it's app related.
Sent from my SGH-I897 using xda app-developers app
BWolf56 said:
CM10 features can be found in other ROMs. As for Devil, it could be the problem. Hopefully KK4 will be fine, at least we'll have a start point to work from. If you get SoD on it, get rid of GrooveIP and heywire. We'll then know if it's app related.
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
Still no SoD and that's with/without Skype running. GrooveIP boots with phone.
If it won't SoD on stock software then I wonder what the problem could be? It's SoD'd with every kernel and ROM I've ever tried.
Sorry for the extreme noob moment here, how do I tell if my device went into SoD? Is it when it gets so extremely slow that even the power button seems to have no effect?
I get that a lot when I've been browsing for a few minutes (even on stock browser) or when playing some games.
Sent from my SGH-I897 using xda app-developers app
JoeCastellon said:
Sorry for the extreme noob moment here, how do I tell if my device went into SoD? Is it when it gets so extremely slow that even the power button seems to have no effect?
I get that a lot when I've been browsing for a few minutes (even on stock browser) or when playing some games.
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
SoD means, while idle, that it randomly turns itself off. It was a defect in X amount of phones produced up to a certain IMEI number, and ATT/Samsung at one point offered an exchange program so people can turn theirs in for a model that didn't have the issue.
What you're suffering from is low memory. You probably have apps running in the background that are utilizing X amount of RAM, and your browsing/gaming is eating up the rest which slows down the phone. Some ways to fix this...
-Use a kernel that allows you to increase maximum memory. I think Devil kernel allows up to 396mb with no downsides, and 413mb at the cost of something that has to do with playing a certain video resolution IIRC.
-Use a task killer. This lets you kill running tasks except for those you choose to "lock." Some advise against using a task killer, but honestly I've yet to have a problem with any of them. My favorite is the one you can get for GOLauncherEX.
-Use Titanium Backup to delete(or freeze if you buy the pro version) apps that you don't use that you can safely remove, specifically items that constantly run in the background eating up your RAM.
-Use a different ROM. There's plenty of ROMs out there including slim/aosp/etc releases that are faster and arguably better-performing.
I believe you tried this already but using the I9000 bootloaders seems to have fixed the SoD issue for many people on JB.
I'm not sure if that would change anything, but try flashing Mosaic.
BWolf56 said:
I believe you tried this already but using the I9000 bootloaders seems to have fixed the SoD issue for many people on JB.
I'm not sure if that would change anything, but try flashing Mosaic.
Click to expand...
Click to collapse
I don't think I've tried the i9000 bootloaders. Any time I flash back to stock I use the link in my sig(one-click w/ bootloaders) and those are the GB version. My phone still hasn't SoD'd on stock software/GB bootloaders so I wouldn't think those bootloaders are the problem, but on the other hand I suppose it's possible that a third party kernel/rom clash with them on my phone.
Are there any downsides to using the i9000 bootloaders? Would you happen to have a link to this mosaic thing you mentioned?
ETA: If it matters any, when I got the phone I believe it was on GB KK4 and was never modded before. When I got it I used the easy-root to corn 7.0a method and first ran Legend5 ICS ROM. That was the first time I started suffering sleep deaths. Ever since then I have used the one-click back to stock w/ GB bootloaders before using any other kernel or rom.
I've used several different kernels/cwm versions to obtain root, at least 6 different ROMs, several different versions of gapps, and numerous other kernels after ROM installation. I've also used the baked-in kernel of each ROM for at least several days before upgrading to something like Devil or Sema. SoDs on everything, both ICS and JB.
I have also tried one-clicking back to stock with what I believe were "up-to-date" GB bootloaders. This was posted by another member that did it and fixed his SoD problem. It didn't produce any sort of a change for me.
I have not tried checking for SoDs on just a root(without ROM). I suppose if I did this I could figure out if it's the root or the ROM that is triggering the sleep deaths, but even if I did get any results from that I'm still not sure how to figure out exactly what's causing the problem since this event apparently can't be logged.
johnnyrichter said:
I don't think I've tried the i9000 bootloaders. Any time I flash back to stock I use the link in my sig(one-click w/ bootloaders) and those are the GB version. My phone still hasn't SoD'd on stock software/GB bootloaders so I wouldn't think those bootloaders are the problem, but on the other hand I suppose it's possible that a third party kernel/rom clash with them on my phone.
Are there any downsides to using the i9000 bootloaders? Would you happen to have a link to this mosaic thing you mentioned?
Click to expand...
Click to collapse
Mosaic is a ROM that was made by The Family; http://forum.xda-developers.com/showthread.php?t=1061203
It is I9000 based so I'm thinking you won't get any SoD on it. Thing is that it's not JB based. Devs aren't porting from I9000 anymore so you won't find a I9000 ported JB ROM. (Hoping I'm not wrong on this lol)
And yeah, many users reported that flashing the I9000 bootloaders with a JB ROM fixed their SoD problem. Back in GB, it wasn't suggested to have I9000 bootloaders and run a I897 ROM (music player wouldn't work and some other little things) but it seems fine now.
EDIT: I highly doubt root is the problem.
Hi all,
I've searched on this forum and in Cyanogenmod's forum about the stable release of Cyanogenmod version 10.1.2 (latest stable I think), but couldn't find an answer about this. Are there any known issues or shortcomings of this ROM? Is everything working fine? (internal/external storage, NFC, WiFi, etc.)? I live in Chile, are there any concerns about baseband, ie. will telephony/3G work just fine?
I want to try CM asap, but I'd like to find some reassuring info that everything will work fine afterwards
Thanks in advance for any help on this,
UPDATE: I'll list here a summary of known issues I'm aware of; thanks a lot to all who have replied! Please correct me if I got anything wrong, I want to document known issues for the LATEST STABLE CM version only! Nightlies don't count!
- Issues with MHL (Not working? working poorly?)
- No screen wake with volume key (my stock v20A doesn't do that, either, for the record
- No FM Radio
- WiFi during sleep drains battery quickly
- Having NFC on drains battery quickly
- Camera app sometimes corrupts pictures on best quality settings
- Can't connect to WEP-protected WiFi networks (found this elsewhere on the forums)
Everything works perfectly fine from my experience. Apart from the MHL issue, which I recently discovered, everything is perfectly done
there is no volume wake... in stock when lock screen offs.. volume key wakes the screen. its not bug just a tip!
there is no lg hidden menu too and lg fm radio
but there is a lot of other things in cm
wifi during sleep no very good (drains battery, but stays better with iodak kernel)
some also say nfc drains battery, havent tested myself.
camera app little bug when putting pictures to excelent quality (becomes corrupt if to many details on picture)
Thanks a lot for all your replies. I've added an update to the original post with all known issues I've been able to gather, from replies to this thread and looking on the forums.
I had issues
e_jim said:
Hi all,
I've searched on this forum and in Cyanogenmod's forum about the stable release of Cyanogenmod version 10.1.2 (latest stable I think), but couldn't find an answer about this. Are there any known issues or shortcomings of this ROM? Is everything working fine? (internal/external storage, NFC, WiFi, etc.)? I live in Chile, are there any concerns about baseband, ie. will telephony/3G work just fine?
I want to try CM asap, but I'd like to find some reassuring info that everything will work fine afterwards
Thanks in advance for any help on this,
UPDATE: I'll list here a summary of known issues I'm aware of; thanks a lot to all who have replied! Please correct me if I got anything wrong, I want to document known issues for the LATEST STABLE CM version only! Nightlies don't count!
- Issues with MHL (Not working? working poorly?)
- No screen wake with volume key (my stock v20A doesn't do that, either, for the record
- No FM Radio
- WiFi during sleep drains battery quickly
- Having NFC on drains battery quickly
- Camera app sometimes corrupts pictures on best quality settings
- Can't connect to WEP-protected WiFi networks (found this elsewhere on the forums)
Click to expand...
Click to collapse
I don't know, but I had to go back to the LG ROM, after install the CM 10.1.2 on my LG 4X the battery life was the worst I've ever seen, I had to recharge it at least 3 times per day. When I let the phone completely charged at night, in 6 hours the phone drained up to 20% of the battery, I mean, the phone just standing by drained 20%!!! I think that's crazy!!... I let it with 100% and when I woke up the phone had only between 85% and 80%... when with the LG ROM it just drained at most 4% (96% for use). And when I was using the phone, the screen process used up to 50% of the battery. I had to go back to the original rom.
I have to say that the phone ran so much better in every aspect than with the LG ROM, but I prefere battery life. Has anyone had the same problem that me? I would like to go back to the CM but for me is very important the battery life.
Thank you so much!
I was about to change to it but then I wad told that there's battery problems so I thought it is not worth it.
Sent from my Lg p-880 using xda premium
In all cm based roms i had lockscreen notification bar drop issue i think it's the only annoying bug.
Not sure if it's in 10.1.2.
Just two words... Absolutely Fantastic!
Afer being a CyanogenMod user for many months, the only usable version for me was 10.1.3 RC2. After trying all existing versions including latest CM11 nightly. All had some issue or another.
Then I tried different modified stock ROMS (including Rizal Lovins's modified JB4.3 leaked version -which is close to being one of the best ROMS out there), but none have the fluidity of a CM based rom.
Last night I gave a try to CyanFox, after all, the Tsubasa version was requested by myself. And they did deliver.
What an amazing Rom, love how fast it is and how 98% of the apps I use on a daily basis work perfectly.
I have only found a few issues, but I can live with them.
- Battery life is not as good as with stock rom, but it ain't that bad either
- Camera doesn't let me change location of photos, no option to select external SD card.
Anyway I automatically send all photos to Dropbox, so it doesn't bother me that much.
Having said all this, I strongly recommend everyone to give the rom a try.
You can find the links here...
http://www.cyanfox-rom.com/
I do recommend using Mr Rizal Lovins Z1 keyboard ports, they are a lot better than AOSP stock keyboard
http://forum.xda-developers.com/showthread.php?t=2196653
Good luck
And I thank all you amazing creators for the excellent work you are doing, my wife doesn't understand how I can fiddle for hours with my phone, but I'm sure you do, and I have to thank you for the great effort you guys put into all this!
:fingers-crossed:
The website isn't very clear about the benefits of this ROM. Would you mind explaining a bit?
downloading now will test and report now
paxy97 said:
The website isn't very clear about the benefits of this ROM. Would you mind explaining a bit?
Click to expand...
Click to collapse
Its based on CM11, but with more 'extras', and so far its working really well.
I got from play store a Z1 theme for Cyanogen, plus Rizal Loving Z1 keyboard and it just works as it should. No FC's yet at all (and strangely it is based on a nightly version of CM11.
I also tried LG Cybershot camera that was ported from Rizal Lovins (fantastic work in all he does). But the CM stock camera works really well and fast. So I'm happy with the stock one.
Best anyone can do is try for themselves. After all, we all have different opinions and views of what we need on a phone.
Installation instructions
Guys, don't forget you'll need the Gaps from CyanFox for it to work properly.
Instructions are here
http://forum.xda-developers.com/showthread.php?t=2472657
How's it if comparing with Rizal's KK 4? The only two issues with are random reboots and battery drain, just as the CM11 nightly
Sent from my Xperia V
alexbo said:
Just two words... Absolutely Fantastic!
Click to expand...
Click to collapse
How good is the stability when the phone is stressed? like running game and have gps on? Like ingress?
Instability is the only reason why I am on stock based rom.
phhuang said:
How's it if comparing with Rizal's KK 4? The only two issues with are random reboots and battery drain, just as the CM11 nightly
Sent from my Xperia V
Click to expand...
Click to collapse
I haven't got any random reboots yet... so it is a bit more stable.
Battery drain is high, but last night when I woke up only went down 3.4% per hour, according to Better battery stats:
http://forum.xda-developers.com/showthread.php?t=1179809
So when not in use, its not that bad... with stock I would get in sleep mode between 1.5% - 2% per hour.
But the rom is faster and more configurable than stock.
it shows me staus 7 error
any guess whats happening...???
i have not backed up any thing
now reveting to flash back ftf
rinkulsk said:
it shows me staus 7 error
any guess whats happening...???
i have not backed up any thing
now reveting to flash back ftf
Click to expand...
Click to collapse
What does the error EXACTLY say?
phhuang said:
How's it if comparing with Rizal's KK 4? The only two issues with are random reboots and battery drain, just as the CM11 nightly
Sent from my Xperia V
Click to expand...
Click to collapse
Ahahah not just those
Camera is flickering (green line) and poor quality;
BT is slow and if you try to use BT headphone and listen to the music the quality is poor;
BT Mic quality is terrible;
ART is not working properly (cause FC and reboot);
NO EXTERNAL SD.
IMHO it's not ready to be a daily use ROM
alfanumerica said:
Ahahah not just those
Camera is flickering (green line) and poor quality;
BT is slow and if you try to use BT headphone and listen to the music the quality is poor;
BT Mic quality is terrible;
ART is not working properly (cause FC and reboot);
NO EXTERNAL SD.
IMHO it's not ready to be a daily use ROM
Click to expand...
Click to collapse
I haven't had any issues with BT, quality seems good to me, been using it in the car and with PowerAmp and sounds just as any other...
But I just had my first Blue Screen... for no reason really, so it isn't as stable as I thought.
Seems there are still issues... I apologize for being so eager to tell everyone how well it goes.
And yes, battery drain is huge... just like CM11 nightly. After all it is based on it.
I will use it a few more days and keep hoping for a Stable, robust and reliable ROM.
when i installed the rom it installed and when i first time used thje rom all going preety okay but when i turn of the screen the display gone blue and restared just like rizal lovins 4.4.2 any idea whats the problem is
Just found out that on 4.4 the WiFi cost more battery drain than 3G. It doesn't let the phone be into deep sleep. So when I turn it off, the battery drain status is better.
phhuang said:
Just found out that on 4.4 the WiFi cost more battery drain than 3G. It doesn't let the phone be into deep sleep. So when I turn it off, the battery drain status is better.
Click to expand...
Click to collapse
Will give this a try. You might be right, it could be a temporary solution.
Sent from my Xperia V using Tapatalk
rinkulsk said:
it shows me staus 7 error
any guess whats happening...???
i have not backed up any thing
now reveting to flash back ftf
Click to expand...
Click to collapse
You can't flash KK ROM on jellybean ROM directly through cwm, to solve this :
Just flash this ROMs kernel with fastboot, then reboot to recovery and do a clean install.
The rom sure is fast, no bsod or random reboot for 16 hours usage.. The battery usage i think its normal if u think it drain too much revert the brightness to manualy adjust.. For who cant detect the external card.. U can install the CM 10.2 first then install this CF (wipe cache and data only) dont ever wipe system it'll make ext card can't read by ROM
Sent from my Xperia V using XDA Premium 4 mobile app
Hi everyone,
Has anyone tried out this latest Nightly from Cyan-fox?? 29-January2014
http://cyanfox-rom.com/downloads/?folder=tsubasa/
Was hoping some brave pirate could give it a try... I am exhausted of trying different nightlies (CM, AOKP, PAC, etc...) and having to revert back to the most stable rom for me (CM 10.1.3 RC2) while waiting for the final release of the OFFICIAL XPERIA V 4.3!!
Which for some reason, Sony keeps delaying eternally.
Thanks in advance!!
Thank you for the sharing. I will still waiting for the more stabel version. Currently im happy with Xperia Revelation rom
What are bug?
Q&A for [ROM][4.4.4][golden] SlimKat
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
the same to me - jstath1972
jstath1972 said:
Again everything is fine for me except Slim Launcher. FC when i try to enter to Settings / Homescreen, Dock, Drawer etc. Am i doing something wrong ? Maybe it's time for a clean install ???
Click to expand...
Click to collapse
@jstath1972
the same to me. In addition, if rightones are located in external SD then there are lost after swith on/off the phone. Probably it's a bug in slimROM
so question to
@andriod-Andi from which device the rom is ported?
Then we can talk to slimROM comunity.
YanecXDA said:
@jstath1972
the same to me. In addition, if rightones are located in external SD then there are lost after swith on/off the phone. Probably it's a bug in slimROM
so question to
@andriod-Andi from which device the rom is ported?
Then we can talk to slimROM comunity.
Click to expand...
Click to collapse
I hope that helps you: move the ringtones to Ringtone folder in internal SD. The same and with Notification ringtones (to Notification folder).
solution
please, download slimlauncher3.apk from download sections.
works ok, for me
I have two problems, maybe someone can help:
1) PacPerformance won't keep statistics of the CPU frequencies reset, even when I press the button multiple times. After waiting a little (usually around 30 minutes) it adds the recent frequencies to the formerly deleted ones..
2) My phone goes to deep sleep quite rarely (~10%), even in the night, airplane mode on. WLD doesn't detect anything above 10mins wakelock, Battery statistic say phone wasn't active.. is PacPerformance wrong?
Thanks in advance!
Jkay7 said:
I have two problems, maybe someone can help:
1) PacPerformance won't keep statistics of the CPU frequencies reset, even when I press the button multiple times. After waiting a little (usually around 30 minutes) it adds the recent frequencies to the formerly deleted ones..
2) My phone goes to deep sleep quite rarely (~10%), even in the night, airplane mode on. WLD doesn't detect anything above 10mins wakelock, Battery statistic say phone wasn't active.. is PacPerformance wrong?
Thanks in advance!
Click to expand...
Click to collapse
Try this PacPerformance alternative http://forum.xda-developers.com/showthread.php?t=2401988 and report back please:good:.
jstath1972 said:
Try this PacPerformance alternative http://forum.xda-developers.com/showthread.php?t=2401988 and report back please:good:.
Click to expand...
Click to collapse
Okay will try.
Also one more thing:
Double tapping the status bar locks the screen, is there any option to disable it?
Edit: Oh pardon: sakuravtive, sio
Results from Performance Control in the last night and WLD for the last 15 hours:
And the lowbat_wake_lock is the only significant wake lock, in CPU wakelock there is nothing above 30 minutes..
Battery shows no active CPU for the time of charging, so why does it stay up?
Shall I try to freeze the apps one by one looking for the right one or is it more probable that the kernel causes it?
Couldn't add this in the other post:
Jkay7 said:
Results from Performance Control in the last night and WLD for the last 15 hours:
And the lowbat_wake_lock is the only significant wake lock, in CPU wakelock there is nothing above 30 minutes..
Battery shows no active CPU for the time of charging, so why does it stay up?
Shall I try to freeze the apps one by one looking for the right one or is it more probable that the kernel causes it?
Click to expand...
Click to collapse
To freeze the apps one by one is one of the solutions. It could be many things and many conditions that cause the problem (3G always open, GPS always open, WiFi always open, bad install, gapps, some apps etc). I suggest you first to close all the connections and check if the problem persists. If it does reflash the rom and new gapps (avoid full gapps and prefer the pico pa gapps) with full wipe (Dalvik Cache/System/Cache/Data/Internal Storage) and without your apps. Five minutes after make a check with Pac Performance to see if you got the proper deep sleep value. If everything is ok install your apps one by one to see which cause the problem.
Btw try this combination: smartassV2 CPU Governor with deadline I/O Scheduler.
At night I have it in airplane, GPS is perma off, wifi only on when at home..
I let it run for the day now, as seen on the pictures..
Anyway thanks for the help, I think I will start freezing anything I don't use daily..
Hey guys. I'm thinking to flash a kernel. Would you suggest any kernel by android andi or cropol kernel or stock slimkat kernel is good for better battery life?
And if i update my baseband, would it help? And if i back up a nandroid and restore it later, will my baseband turn back to normal? I have xxamg4 baseband atm.
Thank you so much and im sorry for too many questions.
Sent from my GT-I8190 using XDA Free mobile app
AnyKernel is similar to the built-in Kernel. Cropol and F_Kernel from Fred68... are interesting alternatives because of OverClocking and min frequency. I made very good experience with F_Kernel, specially for battery savings.
Baseband is diffcult. Depends somtimes on your provider and location. After testing several Basebands I'm back on AMG4. With others I had often Problems with Wakelocks which ends in Battery drain.
Thank you . I'll keep my baseband as same and will try f_kernel then. I checked other roms but guess slimkat is the best about battery life. Just having a bit issue when I have my Wifi on. I'll check f_kernel. Thanks again. It helped me a lot.
Sent from my GT-I8190 using XDA Free mobile app
Not work on SlimKat 1150 MHZ ?
For life of battery i concur, this is obvious
Sorry i can't post in the original thread. So i will post it here. @Fred6681: 1150 MHz and SlimKat is no problem for me. No reboots, no force close[emoji3].
Greetings K.
Link to f_kernel from fred68? I wasn't able to find it for some reason..
Jkay7 said:
Link to f_kernel from fred68? I wasn't able to find it for some reason..
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-s3-mini/development/kernel-fkernel-4-4-x-roms-f2fs-t2898666
ersersoy said:
Hey guys. I'm thinking to flash a kernel. Would you suggest any kernel by android andi or cropol kernel or stock slimkat kernel is good for better battery life?
And if i update my baseband, would it help? And if i back up a nandroid and restore it later, will my baseband turn back to normal? I have xxamg4 baseband atm.
Thank you so much and im sorry for too many questions.
Sent from my GT-I8190 using XDA Free mobile app
Click to expand...
Click to collapse
iwogu said:
AnyKernel is similar to the built-in Kernel. Cropol and F_Kernel from Fred68... are interesting alternatives because of OverClocking and min frequency. I made very good experience with F_Kernel, specially for battery savings.
Baseband is diffcult. Depends somtimes on your provider and location. After testing several Basebands I'm back on AMG4. With others I had often Problems with Wakelocks which ends in Battery drain.
Click to expand...
Click to collapse
1-Andi said in the original thread that the built in kernel of the rom is better and newer than any kernel, by himself. So, you might just keep it or try others like cropol (for oc)
2- I had ANA2 baseband atm I flashed the rom and experienced some 2g - 3g issues. Then I updated to ANE 2, much better now
3- Other than that, anyone alse having the clock freeze bug? Mine had the minutes ok, but one hour late, i just change the 12-24hs box twice and it was fixed.
4- My AOSP keyboard and google keyboard do not recognize when I longpress the "." button to use the ¡? etc... symbols.
Hi! Loving this ROM. Just a question. Is by any chance a possibility to have Netflix running in it? The only one thing missing to me. Thanks!
juliomm64 said:
Hi! Loving this ROM. Just a question. Is by any chance a possibility to have Netflix running in it? The only one thing missing to me.
Click to expand...
Click to collapse
I second this, Netflix running would be awesome!