[Q] Which ROM for a stable flash/torch app? - Samsung Galaxy S Blaze 4G

I recently got the Blaze4G and it is stock, but in the past I had the Samsung Fascinate and I would flash CM and AOKP onto it and the camera flash and torch apps didn't work with the camera LED. I read on the CM 10 development thread that there is also an issue with the camera flash. Are there any non-stock roms that do not have issues with the flash/torch working well?

tmar89 said:
I recently got the Blaze4G and it is stock, but in the past I had the Samsung Fascinate and I would flash CM and AOKP onto it and the camera flash and torch apps didn't work with the camera LED. I read on the CM 10 development thread that there is also an issue with the camera flash. Are there any non-stock roms that do not have issues with the flash/torch working well?
Click to expand...
Click to collapse
You could just install an app from the play store that would give you that functionality. Power toggles is one that comes to mind that works on stock that has a working torch toggle.

anactoraaron said:
You could just install an app from the play store that would give you that functionality. Power toggles is one that comes to mind that works on stock that has a working torch toggle.
Click to expand...
Click to collapse
No, I mean with the aftermarket ROMs, do any others besides CM 10 have issues with the flash or toggle? I have no problems with the stock Blaze 4G torch

I'm on the latest CM10 Nightly and the included Torch works fine.

LBN1 said:
I'm on the latest CM10 Nightly and the included Torch works fine.
Click to expand...
Click to collapse
Thanks, I'm going to try the stable CM10

tmar89 said:
Thanks, I'm going to try the stable CM10
Click to expand...
Click to collapse
No. Don't use the 'stable' build. It's not that stable. Use the latest nightly 3/18.

anactoraaron said:
No. Don't use the 'stable' build. It's not that stable. Use the latest nightly 3/18.
Click to expand...
Click to collapse
dammit.. and I just flashed and loaded my apps and settings..

anactoraaron said:
No. Don't use the 'stable' build. It's not that stable. Use the latest nightly 3/18.
Click to expand...
Click to collapse
Why do you say that the stable build isn't that stable? I've been running it and it works fine for me. It's randomly rebooted on me a total of 2 or 3 times though, and I feel like the battery should last longer so I'm keen to hear what you have to say.

keiichidono said:
It's randomly rebooted on me a total of 2 or 3 times though, and I feel like the battery should last longer so I'm keen to hear what you have to say.
Click to expand...
Click to collapse
That's why I say it's unstable. Random reboots are no longer present and battery life is improved among other things.
Random reboots = unstable lol
I don't fully recall but I believe the SoD was present on the 'stable build' too.

anactoraaron said:
That's why I say it's unstable. Random reboots are no longer present and battery life is improved among other things.
Random reboots = unstable lol
I don't fully recall but I believe the SoD was present on the 'stable build' too.
Click to expand...
Click to collapse
2 random reboots in a few months isn't so bad in my opinion. It's not completely rock solid stable but at least I've never gotten a screen of death. I'm thinking of trying out the nightly but while better battery life does sound very enticing, the screen of death seems like a show stopping problem. It seems safer to just flash the lightning zap kernel to see if it'll improve my battery life. When you say you get the screen of death in the nightly, how often do you get it? How often do others say they get it?

keiichidono said:
2 random reboots in a few months isn't so bad in my opinion. It's not completely rock solid stable but at least I've never gotten a screen of death. I'm thinking of trying out the nightly but while better battery life does sound very enticing, the screen of death seems like a show stopping problem. It seems safer to just flash the lightning zap kernel to see if it'll improve my battery life. When you say you get the screen of death in the nightly, how often do you get it? How often do others say they get it?
Click to expand...
Click to collapse
I don't get the SoD in the nightly. Didn't say I did. But I think the issue surrounding the SoD is present in the 'stable' build.
I believe the SoD had something to do with the BLN but I'm not 100% on that. I know a lot went into getting rid of the SoD and I don't think those efforts started until after the 'stable' build. I also had issues (what seems like) back in the day where when I would receive a call the phone would freeze and hot boot (reboot to cyanogenmod bootanimation). I also recall having major battery drain compared to previous nightlies with the stable build and posted my results somewhere - maybe in the CM10 thread. Something like an additional 20-40% faster drain even in standby compared to the nightly just before the stable release - using the same kernel too. Something in the stable release seemed to be the cause, and the very next nightly the issue was addressed (which I think I pointed out in the CM thread also).
I also believe that the 'default' kernel with CM10 has added the interactive governor since the stable build. I don't remember having that before either.
You can flash the LZ kernel (it's awesome) but I think there is or may be an issue with the davlik. I do believe Thomas is already on this - read the LZ thread for more info. I was getting reboots quite often using it with both PA and CM10 - sometimes immediately after boot. That doesn't mean you won't run it just fine 100%, just something to be aware of. Make sure you nandroid before flashing in case you run into any instability.

anactoraaron said:
I don't get the SoD in the nightly. Didn't say I did. But I think the issue surrounding the SoD is present in the 'stable' build.
I believe the SoD had something to do with the BLN but I'm not 100% on that. I know a lot went into getting rid of the SoD and I don't think those efforts started until after the 'stable' build. I also had issues (what seems like) back in the day where when I would receive a call the phone would freeze and hot boot (reboot to cyanogenmod bootanimation). I also recall having major battery drain compared to previous nightlies with the stable build and posted my results somewhere - maybe in the CM10 thread. Something like an additional 20-40% faster drain even in standby compared to the nightly just before the stable release - using the same kernel too. Something in the stable release seemed to be the cause, and the very next nightly the issue was addressed (which I think I pointed out in the CM thread also).
I also believe that the 'default' kernel with CM10 has added the interactive governor since the stable build. I don't remember having that before either.
You can flash the LZ kernel (it's awesome) but I think there is or may be an issue with the davlik. I do believe Thomas is already on this - read the LZ thread for more info. I was getting reboots quite often using it with both PA and CM10 - sometimes immediately after boot. That doesn't mean you won't run it just fine 100%, just something to be aware of. Make sure you nandroid before flashing in case you run into any instability.
Click to expand...
Click to collapse
Ah, the way you worded it I thought you got the SoD. I definitely notice the battery draining quite fast, even on standby just as you said. Sometimes I fully charge it before I go to sleep and unplug it; I wake up and the battery is at 90% (Estimate off the top of my head). Other times I fully charge it to 100% and unplug it, only to have it immediately drop down to 99% and within minutes go down even lower. I'm using the default kernel in the CM10 stable build and I have the Interactive governor (It's default), and my scheduler is CFQ (Also default).
You've certainly convinced me to try out the nightly, I'll have to flash it soon. I'd also like to try out the LZ kernel as it does seem really cool. In what areas did you see an improvement and was it a big difference?

keiichidono said:
Ah, the way you worded it I thought you got the SoD. I definitely notice the battery draining quite fast, even on standby just as you said. Sometimes I fully charge it before I go to sleep and unplug it; I wake up and the battery is at 90% (Estimate off the top of my head). Other times I fully charge it to 100% and unplug it, only to have it immediately drop down to 99% and within minutes go down even lower. I'm using the default kernel in the CM10 stable build and I have the Interactive governor (It's default), and my scheduler is CFQ (Also default).
You've certainly convinced me to try out the nightly, I'll have to flash it soon. I'd also like to try out the LZ kernel as it does seem really cool. In what areas did you see an improvement and was it a big difference?
Click to expand...
Click to collapse
Racings unofficial AOKP + lightning zap = WIN
Snappy snappy, stable(no reboots period), best battery life for any jelly bean ROM I've tried, and the built-in toggle torch works perfectly.
just my 2 cents
Sent from my AOKP Blaze

Related

CM7 vs stock android - benefits?

I've had my NS for over 2 months now - love it. Since I bought it, I've been running completely stock android 2.3.3
Like most on this forum, I like to tweak settings and make improvements.
I just want to know if that if I were to root and load CM7 rom on the NS would it improve the speed/battery? (they are the most important factors to me)
Yes it would improve your battery life. Especially when you flash a custom kernel. With this combination, I currently get 24 hours+ with maybe ~30% remaining.
http://www.cyanogenmod.com/about/features are some of the highlights of the features.
Some benefits on top of my head:
Flashing custom kernel (I suggest you do, its easy)
- Voodoo Sound (Better sound quality, you'd be amazed)
- Voodoo Color (Don't like 2.3.3 colors? Change it back to <2.3.3)
- Overclock (If you're into that) or Underclock
- CFS or BFS
Kernel.. i'd go with Netarchy's 1.2.8 CFS
CM7 Benefits
- Widget Folders (When you add a widget, no more 5 widgets showing Beautiful Widgets.. instead its in a folder; better organization)
- Power Widgets (Notification Pulldown)
- If you use your NS as a music player, it adds a lot of features such as lock screen controls. Using volume rocker to adjust volume while phone screen not on.
- Custom Boot Screens
- Sync with Facebook
Rest are here: http://wiki.cyanogenmod.com/index.php?title=CyanogenMod_Settings
Thanks for your tips. Before I had my NS I had modded my Hero beyond belief!
Would it be easy to send the phone back to a stock ROM and stock kernel? Lets say I had to send the phone back to Samsung to get warranty repaired.
Following on to that question, which is the best way to root?
How's the stability of CM7 on the NS. I just upgraded from my G1 to the NS yesterday, and I was thinking of just running stock until CM7 goes final.
JTopaz said:
Thanks for your tips. Before I had my NS I had modded my Hero beyond belief!
Would it be easy to send the phone back to a stock ROM and stock kernel? Lets say I had to send the phone back to Samsung to get warranty repaired.
Following on to that question, which is the best way to root?
Click to expand...
Click to collapse
Yes all you have to do is download a nandroid backup of 2.3.3 or whatever that is stock unrooted. And thats it.
Root: http://forum.xda-developers.com/showthread.php?t=895545
@Apre: It's stable. The latest nightly (#19) is more stable than RC2 itself. And dang G1 lol, I upgraded from a G1 last year in Juneish. Looking back on that phone now, the screens so small.
I have CM7 RC2 and i find that my battery drains faster. How do I flash Netarchy kernel?
Put it in SD and update it? or do I do it the ADB way by putting the kernel in the tools folder and with command prompt?
I ran stock for quite awhile after buying this phone because I didn't see any need for custom ROMs with vanilla Android. But I finally decided to give it a shot, and I'd never go back. Vanilla is great, but CM7 and all the other Custom Roms for the Nexus S (Axura, Modaco, etc) all bring more great features and customizations. If nothing else, however, I'd at least root and flash a custom kernel with stock - so you can have some overclock goodness
Edit: In specific reference to your post's questions, I run Axura, and I get both better battery life AND what seems to be a snappier phone (Axura has Netarchy 1.2.5 kernel baked right in). On CM7 I didn't notice much of a speed boost, and I think my battery life might have actually been a little worse, but CM7 packs in a lot of extra features. So it all comes down to preference.
apreichner said:
How's the stability of CM7 on the NS. I just upgraded from my G1 to the NS yesterday, and I was thinking of just running stock until CM7 goes final.
Click to expand...
Click to collapse
CM7 will never go final, until its time for CM8. its always being inproved.
cyberdentist said:
I have CM7 RC2 and i find that my battery drains faster. How do I flash Netarchy kernel?
Put it in SD and update it? or do I do it the ADB way by putting the kernel in the tools folder and with command prompt?
Click to expand...
Click to collapse
yes. put it in SD, boot into CWR
flash .zip
and you're done.. its the same as flashing a ROM
and as far as battery life.. make sure you disabled latitude (automatic and that other feature) in CM7.. not sure if its still working even though if latitude is disabled, id disable it anyway
apreichner said:
How's the stability of CM7 on the NS. I just upgraded from my G1 to the NS yesterday, and I was thinking of just running stock until CM7 goes final.
Click to expand...
Click to collapse
I was so happy with my stock NS that I'd not bothered with CM (my ROM of choice on Nexus 1) until just two days ago. In the first 24 hours I had two issues that I've not had, or at least not seen in a very long time.
First issue - I was at 84% battery after about 4 hours. Put the phone to the side of my desk and 3 hours later it was 100% drained to 0 battery juice. Status graph showed nothing unusual, not long wakelocks, no time without cell signal, screen on only 1.5 hours.
Second issue - 24 hours after install, while listening to a podcast with my long time app for those that's not given crash issues, the playback goes into a constant stutter loop for about 30 seconds, then the phone rebooted.
EDIT: a third issue, happening right as I type this. I'm happily tethered away on my laptop via the NS with CM7, but I just went to check something on the screen and the phone is locked up...won't respond to power button. Screen is black, menu buttons are lit. Still tethering me, though.
Seems there are still some slight issues. I did full wipe/format before installing and am on the stock CM7 kernel still.
cyberdentist said:
I have CM7 RC2 and i find that my battery drains faster. How do I flash Netarchy kernel?
Put it in SD and update it? or do I do it the ADB way by putting the kernel in the tools folder and with command prompt?
Click to expand...
Click to collapse
It's an update.zip file you flash from CW recovery. I agree CM7 appears to be harder on the battery.
simms22 said:
CM7 will never go final, until its time for CM8. its always being inproved.
Click to expand...
Click to collapse
I suppose that you're technically correct that CM mods never go final because they're always improved, but all prior iterations of CM at least got out of BETA/ReleaseCandidate status at some point.
I fully expect that CM7 will eventually see a version that doesn't have a beta, nightly or RC tacked on to the end of it. Then we'll see all the .x releases with their betas/rc, etc.
I was going to hold off on CM7 until it was past RC stage because I feared it would have some issues, despite all the glowing reports, and it does, but not enough for me to go back to stock. Probably time to flash netarchy on top of this.
zephiK said:
yes. put it in SD, boot into CWR
flash .zip
and you're done.. its the same as flashing a ROM
and as far as battery life.. make sure you disabled latitude (automatic and that other feature) in CM7.. not sure if its still working even though if latitude is disabled, id disable it anyway
Click to expand...
Click to collapse
I haven't even activated latitude . I don't have background data enabled either. Not sure what is killing the battery life in CM7 ..
Also, if you're interested. Check out frank707's "NS Collab" ROM. It's basically CM7 without ADW launcher, which is good if you like using CM7 but miss the stock launcher or just frankly don't like ADW.
cyberdentist said:
I haven't even activated latitude . I don't have background data enabled either. Not sure what is killing the battery life in CM7 ..
Click to expand...
Click to collapse
hence why i said.. not sure if its still working even though if latitude is disabled, id disable it anyway
I have tried CM7 and felt that its bugs and constant state of upgrading and updating to fix things caused me too many issues for daily use.
I do think that CM7 does perform a bit better than the other ROMS due to it being AOSP based but i feel thats why there are also some of these bugs.
I have been using AXURA by Master and its been flawless for me, the one issue I had with a reboot was due to testing a new overclock, but now I keep it at 1200 max ondemand and it hasn't gave me any issues, The lack of full easy theme support like CM7 is a con but the performance is up there with CM7 and the stability is sooo much better for me, I feel this is because its the Stock 2.3.3 ROM that has been decomplied and tweaked and then compiled again.
Its worth looking at some of the other options as well.

[Q] Fix for G2X sleep of death?

The main problem with my G2X is the sleep of death, which happens a lot. I get occasional reboots too, but not too often. I tried flashing EaglesBlood 1.05 and then CM7 nightly (7/6), which I'm on now, and I still get sleeps of death and reboots, with perhaps reduced frequency but still bad. Maybe it's the battery, though I don't have overheating/charging/battery drain issues, so I'm not sure what the problem is and if it's hardware or software. Any advice on what I should do would be appreciated - thanks!
I enabled "stay awake" and flashed faux's oc kernel and haven't had an sod in weeks on the stock rom.
regP said:
I enabled "stay awake" and flashed faux's oc kernel and haven't had an sod in weeks on the stock rom.
Click to expand...
Click to collapse
Wouldn't that drain your battery much faster?
Also, I only seem to get the SOD when the phone is charging overnight, and I have a damn screen off profile set to underclock too, not even the lowest frequencies either so it cant be the freeze that that causes sometimes. Tho when it does and I figure out it is frozen asleep, it is usually hot. Might have to either get new battery or replacement. Tho what seems to heat up the most is the area around the camera, so I don't know if the battery or CPU are to blame.
No. Stay Awake only takes effect when your phone is plugged into a power source. Give it a try. I used to get 1 SOD per day. Since i made those changes I've had none in over a month. I posted the same thing in other SOD related threads but no one seems to care.
Thanks regP - I enabled Stay Awake and it seems to help. I've only had one SoD since. My new theory is that it relates to heat (leaving phone in the sun, running too many apps etc.). I've also noticed I don't get an SoD at work, where I get no reception and it's air-conditioned...might be related.
You also need to flash Faux's OC kernel. Even if you dont OC it gets rid of the faulty 300hz frequency that is believed to be part of the problem. Do that along with stay awake and you should not see any more SOD or reboots.
I've noticed I only ever got SOD when using any different kernel than what's in the original ROM. I have been on CM7 since RC1 and have been updating each nightly since and not touched the kernel and have not had a single SOD since, even when charging overnight. Only when I would try Faux kernel or Trinity kernel I would get SOD's.
I dunno then. completely stock for mean means sod and reboots. gingerbreak leak means sod and reboots. stocks + days kernel and stay awake means no sod or reboots. buddy of mine also cured his problems the same way.
For me stock froyo and gingerbread solves the problem.Initially when there was a call waiting sods used to occur, not in any other situation.I tired latest cm7 nightly with fauxs kernel,MIUI with fauxs kernel (and yes wiped cache , wiped dalvik cache and fix permissions and stay awake) but still sods.Then the stock froyo / gingerbread solves the problem for me.Hope this helps somebody.But my point is can I install the stock kernel with cm7 or MIUI ?.
viraj071 said:
For me stock froyo and gingerbread solves the problem.Initially when there was a call waiting sods used to occur, not in any other situation.I tired latest cm7 nightly with fauxs kernel,MIUI with fauxs kernel (and yes wiped cache , wiped dalvik cache and fix permissions and stay awake) but still sods.Then the stock froyo / gingerbread solves the problem for me.Hope this helps somebody.But my point is can I install the stock kernel with cm7 or MIUI ?.
Click to expand...
Click to collapse
no, miui and cm7 are both built from AOSP code and thus won't work with the stock kernel.
I guess I got lucky... never encounter the SOD or Reboot. Running cm nightly 163... I only update nightly when I notice major change only from change log.
Sent from my LG-P999 using XDA App
regP said:
no, miui and cm7 are both built from AOSP code and thus won't work with the stock kernel.
Click to expand...
Click to collapse
So can you suggest any other kernel I should try to stop the sleep of death ?
I have two G2x - Stock Froyo and kernel, manually restart once per day - no SOD or async reboots. Both G2x did suffer from SOD (with or without heat) and reboots. Manual restarts are not as sexy as 3rd party kernels and roms, but it works.
My wife uses her G2x as an alarm clock - she gets in beds, manually shutsdown the G2x, restarts it, plugs into the charger, and it wakes her up in the morning. EVERY DAY.
viraj071 said:
So can you suggest any other kernel I should try to stop the sleep of death ?
Click to expand...
Click to collapse
my sod issues stopped when I enables "stay awake". never used anything but the included kernel of whatever Tom I decide to use.
What is the best solution for this? Makes me think i wasted good money on getting 2, for me and my girl. I tried that "stay awake" and same, shuts off out of nowhere. Ive flashed both faux kernel, same results. I dont experience it with CM but for me, stock its just more responsive BESIDES the shutoff. And Weapons rom just has too much addons.. Now people are saying that the SGS2 isnt all that because of benchscores.. And i wanted that phone.. But they make it seem like it isbt a big step forward.
Sent from my LG-P999 using Tapatalk
noodles2224 said:
What is the best solution for this? Makes me think i wasted good money on getting 2, for me and my girl. I tried that "stay awake" and same, shuts off out of nowhere. Ive flashed both faux kernel, same results. I dont experience it with CM but for me, stock its just more responsive BESIDES the shutoff. And Weapons rom just has too much addons.. Now people are saying that the SGS2 isnt all that because of benchscores.. And i wanted that phone.. But they make it seem like it isbt a big step forward.
Sent from my LG-P999 using Tapatalk
Click to expand...
Click to collapse
Our phone at 1 ghz has surpassed the gs2 and 1.2 ghz
Sent from my LG-P999 using XDA App
If missing with software and settings dont work you may just have a bad phone.
regP said:
I enabled "stay awake" and flashed faux's oc kernel and haven't had an sod in weeks on the stock rom.
Click to expand...
Click to collapse
Thanks for this. I'll be sure to use the "Thanks" button when i have enough posts. I'd been leaving the phone screen on in my pocket (using an alarm clock app) because it would SOD anytime i used the lock button. Working better already.
I keep on getting SODs ONLY when there is a call waiting in the background and this happens only with CM7,MIUI.When I flash the stock gingerbread or even weapons G2x,EaglesBlood ROM the sods that occur during call waiting vanish. Can anyone help me here ? I tried fauxs kernel along with Stay awake and increasing the minimum CPU frequency but failed. Any help will be appreciated.
For the people that SOD occurs on the charger, try another charger (instead of stock LG charger). I tried the Motorola micro USB charger which put out only 550mA (which came with the H730 bluetooth) and the SOD vanished.
Probably over heating with the LG charger which puts out 1000mA

CM7 - post your best choice nightly here

To help sort out good nightlies from buggy ones, please post your best choice CM7 nightly here. This will help others who want to test nightlies to try out good ones for best time utilization.
CyanogenMod-7-110819-1459-NIGHLY-Jordan
I prefer this one.
Battery consumption is very high, 12 hours maximum.
-rsp1
Happily using 0826, no issues. Its pretty hard to have a decisive recommendation as users are running so many different apps and configurations..
last boot179-4 1650-i forgot date...august ???
This seems to the correct thread to ask this question. I have tried few nighties randomly dome are very stable and some are not. But none of them have given exceptional battery life. Has anyone come across a stable nightly with great battery life.
Sent from my MB525 using Tapatalk
have you Undervolted? That can give you the battery life you are looking for.
cm7-110716-0105-BOOT179-Jordan.zip
Hi,
I can recommend this version:
cm7-110716-0105-BOOT179-Jordan.zip
This version runs perfekt with very long battery life and works perfekt for me (cam, gps, wlan, battery...). But it is only version 2.3.4. I use this rom since a few weeks and I have no problems.
sg3707 said:
..
Has anyone come across a stable nightly with great battery life.
..
Click to expand...
Click to collapse
Ok, even am hunting for that, and i found 110814 wrking very good for me.
Its 2days,5hr, still 55% left
In my case, my sim was 6yrs old, so replaced it with new1 and that has given me better battery.
my configuration: check this thread
http://forum.xda-developers.com/showthread.php?t=1105506&page=9
And thanks to cm7defy devs for making such a wounderful rom.
...110822 boot179-4 nightly, very stable, works like a charm!
From main CM7 thread:
sentree said:
Besides that, I've tested the 110822-1650 nightly for a week now and I get 4d6h37m (4% left) on battery, love it!
3G and sync always on, a few calls, some surf, mail und sms, say normal use
Click to expand...
Click to collapse
I really doesn't understand this "myth" of the "best nightly"...
As far as I can tell the development is pretty much straight forward, and the best version is always the last - with bugfixies and new features who will get their bugfixies in a later version.
the best version is not necessarily the last one, we all have seen pretty screwed up nightlies. but now im using 110822 boot179, and i havent noticed any bugs yet, and it runs smooth, no lags, very good battery life.
sent from my cm7 defy...
Software dev is not that straight forward. With an OS it is actually hugely complex and anything changed might have unexpected consequences. The idea of posting here is to ID those ones that get a consistent good report.
I am currently on 110826-2119- NIGHTLY-Jordan.
Can I flash 0822 boot179-4 nightly directly on top of this and clear Dalvik and cache or is there any other procedure.....
sg3707 said:
I am currently on 110826-2119- NIGHTLY-Jordan.
Can I flash 0822 boot179-4 nightly directly on top of this and clear Dalvik and cache or is there any other procedure.....
Click to expand...
Click to collapse
sure.. boot builds are made for that.. like Rc
rainbowsixpro1 said:
CyanogenMod-7-110819-1459-NIGHLY-Jordan
I prefer this one.
Battery consumption is very high, 12 hours maximum.
-rsp1
Click to expand...
Click to collapse
jep, can confirm the high battery consumption on this nightly...
but would say that it's not the best rom at all
Well... I wait everyday for the latest nightly... And I can say I'm happy everyday. Haven't seen a sensive decrease in battery life ou system stability in any of the nightlys, only improvements
I update my defy with latest nightly version every ten days; I can't find any obvious issue yet.
lycheejet said:
I update my defy with latest nightly version every ten days; I can't find any obvious issue yet.
Click to expand...
Click to collapse
not me when 179-4 is uploaded wifi is better, the last have a fix for SD Card .
But it's my Nightly i prefer because i can use Total Recall
i have to correct myself: 110822 boot179 nightly has battery drain issues, i only could last about 14 hours w/ normal use in the last 2 days... but i hear the 110830 is very good. can somebody pls confirm that?
sent from my cm7 defy...

[Q] CM 11 with ION by sultanxda stability problems

installed newest
(date 27.1.2014 with GAPPS modular mini from: http://forum.xda-developers.com/showthread.php?t=2530073)
did full wipe (factory reset, system, cache) as in info
have some major problems with stability, looks like system degrades quickly after leaving screen off mode
After restart I can set up everything fine, can use network, launch apps, change system settings etc
but after first turning off and turning on lock screen starts to show first problems, dots (I'm using pattern unlock) sometimes start to activate on their own, not always but sometimes this happens, but I'm still able to logon...
after second 'screen off' and 'screen on' I'm having big problems trying to unlock screen - sometime dot's don't react to touches, sometimes they do not end connecting after taking away finger from screen...
after third off/on I'm unable to pass unlock screen - it becomes unresponsive, dots start to connect randomly, sometime even 'emergency calls' gets activated...
what can cause this? full phone restart appears to fix problems for short time, but after few off/on have problems agains...
this did not happen in builds from few months ago
tried to set higher min cpu frequency to 384MHz but that doesn't help
other things that I chaged are:
- cpu governor -> badass
- i/o -> noop
- active 'allow purging of assets'
anyone got ideas what could cause this? and how to fix
phone:
htc sensation xe, unlocked
hboot 1.29, radio 11.24a.3504.31_m
can provide other info if needed
It's easy to be fixed, install stock rom.
nlooooo said:
It's easy to be fixed, install stock rom.
Click to expand...
Click to collapse
thank you, very helpful
What firmware are you on? Did you experience any of these problems on any other rom?
You say the dots connect themselves. As if the touchscreen is used? Sounds somehow like a broken digitizer.
zodi79 said:
thank you, very helpful
Click to expand...
Click to collapse
Do you know how many threads like yours have been opened recently? Is it that hard to search and why do you expect flawless rom?
When will people learn, it's unofficial, it's custom, it's a new android version tied to the old hardware with the old drivers, it will, probably never be perfect.
nlooooo said:
Do you know how many threads like yours have been opened recently? Is it that hard to search and why do you expect flawless rom?
When will people learn, it's unofficial, it's custom, it's a new android version tied to the old hardware with the old drivers, it will, probably never be perfect.
Click to expand...
Click to collapse
I must have missed all of these threads. There were some threads about cm11 but they had other issues.
This phone is 3 years old and you're using Badass. Since you want more performance, set your CPU governor to Ondemand and set I/O scheduler to BFQ or SIO.
Sent from my Nexus 5 using xda app-developers app
Sultanxda said:
This phone is 3 years old and you're using Badass. Since you want more performance, set your CPU governor to Ondemand and set I/O scheduler to BFQ or SIO.
Click to expand...
Click to collapse
ok, will try
atm had to move back to previous cm 10.1 based on 4.2.2 prepared few months ago, it appears to work much better but still have some stability issues. Doesn't look like problem with touch screen as most (now like 97%) it works flawlessly... yeah, not 100% so it could be hardware problem, just that didn't happen before
and yeah, I know these are unstable, beta like, etc roms - I like to test new features on my sens xe and one prepared by sultanxda is atm the best for me, keep up great work and thank you for time spent working on this rom.
zodi79 said:
ok, will try
atm had to move back to previous cm 10.1 based on 4.2.2 prepared few months ago, it appears to work much better but still have some stability issues. Doesn't look like problem with touch screen as most (now like 97%) it works flawlessly... yeah, not 100% so it could be hardware problem, just that didn't happen before
and yeah, I know these are unstable, beta like, etc roms - I like to test new features on my sens xe and one prepared by sultanxda is atm the best for me, keep up great work and thank you for time spent working on this rom.
Click to expand...
Click to collapse
Why not try my CM10.2 ROM? CM10.2 is far more stable than CM11, and, personally, CM10.2 feels smoother than CM11.
first of all - sorry for misinformation but I found cause of my problems with interface... looks like minimal amount of water must have got under the cover when I few days ago applied new screen protection, yesterday I got this idea of what could cause this sudden problems... few hours phone stayed on the room heater (not too hot ofc) and touch screen problems are gone! yeah, tbh I love this phone and was very angry thinking I'd have to replace it, now I don't have to
back to rom - atm back to your (sultan) rom based on CM 11 with update from 29.1.2014, it has some small problems but I like to test new features
problems I've found so far:
- less responsive and smooth
- launcher3 doesn't allow to create new home screens on the left, had to create new to the right then make some rearangments before I got things right
- some widget resize problems under launcher3
- other small problems all I can live with
but I like more available memory and better battery life, going to test ART soon
and it is good that messanging is back, hangouts is just... not for me
Why cant i find my phone contacts on SIM ??? Its say no contacts found? When i import some numbers from vCard from SD why cant i move them to SIM???
cm10.2 - cm11
Sultanxda said:
Why not try my CM10.2 ROM? CM10.2 is far more stable than CM11, and, personally, CM10.2 feels smoother than CM11.
Click to expand...
Click to collapse
funny ... i tried a lot of rom and i dont have real problem except with your latest rom ([ROM][Android 4.3.1][Camera works] CM10.2 with ION [Jan 30, 2014]) : lags, reboot , ...
Now i use your latest rom on CM11 ([ROM][Android 4.4.2][Camera works] CM11 with ION [Jan 29, 2014]), realy good no problem, thank's for all.
romadd said:
funny ... i tried a lot of rom and i dont have real problem except with your latest rom ([ROM][Android 4.3.1][Camera works] CM10.2 with ION [Jan 30, 2014]) : lags, reboot , ...
Now i use your latest rom on CM11 ([ROM][Android 4.4.2][Camera works] CM11 with ION [Jan 29, 2014]), realy good no problem, thank's for all.
Click to expand...
Click to collapse
I tested it for 3 hours and it was working well
Sultanxda said:
I tested it for 3 hours and it was working well
Click to expand...
Click to collapse
I had fresh install, but configured cpu clock speed 1674 mhz (maybe the problem ?)
And i had the same symptom describe by Firehawk989 http://forum.xda-developers.com/showpost.php?p=49938883&postcount=3341
Any way i run already with your CM11 and it seem more stable for me except a little problem
http://forum.xda-developers.com/showpost.php?p=49353701&postcount=1
This is another story

FXP Cyanogenmod 11 lockscreen

So I just installed CM 11, it runs really good, but there's a significant problem.
The phone wakes up really slowly, and sometimes it never does. And when it does, there's often a slow scanning effect.
The Omnirom builds had the same issue, but it happened less frequently.
Is there a way to fix that? Honestly, it gets on my nerves, and I can't return to stock.
stuckbootloader said:
So I just installed CM 11, it runs really good, but there's a significant problem.
The phone wakes up really slowly, and sometimes it never does. And when it does, there's often a slow scanning effect.
The Omnirom builds had the same issue, but it happened less frequently.
Is there a way to fix that? Honestly, it gets on my nerves, and I can't return to stock.
Click to expand...
Click to collapse
Try this rom here
http://forum.xda-developers.com/xperia-l/development/rom-aosb-project-1-3-7-t2873337
This rom is built on CM11 but has more and more feature than CM11
I've been using this rom for about two months and until now everything run smoothly ,SO give it a try.
I don't know.. That ROM you suggested has a lot of features, but I won't be using half of them.
stuckbootloader said:
I don't know.. That ROM you suggested has a lot of features, but I won't be using half of them.
Click to expand...
Click to collapse
Lol
Just try and you can customize your phone and add tweaks to kernel and yhe battery life is awsome.

Categories

Resources