EDIT: Should you experience this issue on a stock kernel while there are no wakelocks generated by any apps, a fix has been developped by HomerSp and can be found here. All custom kernels available on XDA integrate it as far as I know. You will find plenty of information about the fix in this thread, however please note no app can solve this because this is a kernel issue. Should you have applied the fix and the issue persists, try doing a factory reset to start fresh.
Got the edge yesterday (SM-G925F version) and rooted it immediately (after receiving OTA), so I'm not sure if it's a bug or rooting that's causing it. I already tried disabling edge screen, and factory reset, but it had no effect.
The standby drain is about 1.5%/h with no deep-sleep. For comparison my old Nexus 6 was draining 1.4%/h with stock kernel and about 0.2%/h with Faux123 kernel as seen on screenshots. I'm pretty sure it's going to be great once the device goes in deep-sleep, but couldn't find any particular culprit except the OS itself!?
Anyone experienced this and managed to solve it?
I read in the root thread that the lack of deep sleep is due to root itself. If you can show me how to check for deep sleep on a non rooted device id be happy to check for you.
I didn't root my phone, and last night I lost 20% over night during sleep
If my calculation is correct I lost almost 3% per hour while my phone not in use
I guess my phone don't know how to sleep properly
mrnovanova said:
I read in the root thread that the lack of deep sleep is due to root itself. If you can show me how to check for deep sleep on a non rooted device id be happy to check for you.
Click to expand...
Click to collapse
You can use most CPU apps, even though they won't be able to change CPU settings because of lack of root, they will show you CPU times, and most importantly offline mode. I use my own app for that, allowing to track battery history as well and also showing CPU times. You can try the following apps which will definitely show you deep-sleep: 3C CPU Manager or System Tuner or 3C Toolbox, all 3 are free (with ads).
In 3C CPU Manager, in first tab, called CPU, you'll see a 'Sleep' meter on top of the 3 graphs. That will indicate actual sleep time, versus run time. Mine is (was) showing nothing (eg 0 deep-sleep). In second tab called Times, you can check each CPU frequencies time used, it should show offline time, if not that means no deep-sleep! Screenshots were attached in OP.
MrHardplastic said:
I didn't root my phone, and last night I lost 20% over night during sleep
If my calculation is correct I lost almost 3% per hour while my phone not in use
I guess my phone don't know how to sleep properly
Click to expand...
Click to collapse
This seems to suggest this has nothing to do with rooting in the first place. I've only got one rooted app on my device, as always and never seen this caused by root. I've seen it caused by bugged ROMs, bugged kernels and more rarely by recovery issues, but not with my setup.
Anyway, I just rebooted less than an hour ago, and just realized it's going into deep-sleep now! Didn't change recovery which eliminate this as the culprit. Was only developping some new notification for the edge screen all afternoon. Didn't uninstall anything or changed any particular settings either except Edge screen feeds, disabling all feeds except notification and my own new feeds. Maybe that helped?
Also activated the panel left of the home screen with minimal news feeds, tech and science, but I don't see how it would relate to this.
3c said:
You can use most CPU apps, even though they won't be able to change CPU settings because of lack of root, they will show you CPU times, and most importantly offline mode. I use my own app for that, allowing to track battery history as well and also showing CPU times. You can try the following apps which will definitely show you deep-sleep: 3C CPU Manager or System Tuner or 3C Toolbox, all 3 are free (with ads).
In 3C CPU Manager, in first tab, called CPU, you'll see a 'Sleep' meter on top of the 3 graphs. That will indicate actual sleep time, versus run time. Mine is (was) showing nothing (eg 0 deep-sleep). In second tab called Times, you can check each CPU frequencies time used, it should show offline time, if not that means no deep-sleep! Screenshots were attached in OP.
This seems to suggest this has nothing to do with rooting in the first place. I've only got one rooted app on my device, as always and never seen this caused by root. I've seen it caused by bugged ROMs, bugged kernels and more rarely by recovery issues, but not with my setup.
Anyway, I just rebooted less than an hour ago, and just realized it's going into deep-sleep now! Didn't change recovery which eliminate this as the culprit. Was only developping some new notification for the edge screen all afternoon. Didn't uninstall anything or changed any particular settings either except Edge screen feeds, disabling all feeds except notification and my own new feeds. Maybe that helped?
Also activated the panel left of the home screen with minimal news feeds, tech and science, but I don't see how it would relate to this.
Click to expand...
Click to collapse
Did you use cf auto root? That's how I rooted my tmo 32gb edge and it hasn't been in deep sleep since last Tuesday. I didn't install that ota update people are talking about and have no idea that there was an update and I didn't install or mess with the recovery at all after root and my phone still stays awake.
3c said:
You can use most CPU apps, even though they won't be able to change CPU settings because of lack of root, they will show you CPU times, and most importantly offline mode. I use my own app for that, allowing to track battery history as well and also showing CPU times. You can try the following apps which will definitely show you deep-sleep: 3C CPU Manager or System Tuner or 3C Toolbox, all 3 are free (with ads).
In 3C CPU Manager, in first tab, called CPU, you'll see a 'Sleep' meter on top of the 3 graphs. That will indicate actual sleep time, versus run time. Mine is (was) showing nothing (eg 0 deep-sleep). In second tab called Times, you can check each CPU frequencies time used, it should show offline time, if not that means no deep-sleep! Screenshots were attached in OP.
This seems to suggest this has nothing to do with rooting in the first place. I've only got one rooted app on my device, as always and never seen this caused by root. I've seen it caused by bugged ROMs, bugged kernels and more rarely by recovery issues, but not with my setup.
Anyway, I just rebooted less than an hour ago, and just realized it's going into deep-sleep now! Didn't change recovery which eliminate this as the culprit. Was only developping some new notification for the edge screen all afternoon. Didn't uninstall anything or changed any particular settings either except Edge screen feeds, disabling all feeds except notification and my own new feeds. Maybe that helped?
Also activated the panel left of the home screen with minimal news feeds, tech and science, but I don't see how it would relate to this.
Click to expand...
Click to collapse
If offline means sleep then she sleeps like a newborn.
To make things more weird, I just dumped the currently held wakelocks, and at first sight it appears there is no actively held wakelock keeping the device alive. Which implies a kernel issue, but that is beyond my expertise. Needs some further research.
(Terminal emulator, disconnect USB, "sleep 30 && cat /d/wakeup_sources", turn off screen, wait a minute, turn it back on, and you get a wakelock list with 0 active wakelocks - that's shouldn't even be possible)
Either way I maintain that recovery should have nothing to do with this (binary status though, perhaps?)
FWIW, we've been discussing this a lot over in the T-M section, and the recovery seems to fix it. We've also found that a clean install from Smart Switch seems to be helpful.
http://forum.xda-developers.com/tmobile-galaxy-s6-edge/help/rooting-deep-sleep-t3079385
Thanks for all of your work Chainfire!
Yeap all you guys have to do is flash ur stock recovery and deep sleep will be back...... For some reason this root is getting rid of our recovery all together just flash the stock recovery and deep sleep will be fine
dc/dc said:
FWIW, we've been discussing this a lot over in the T-M section, and the recovery seems to fix it. We've also found that a clean install from Smart Switch seems to be helpful.
http://forum.xda-developers.com/tmobile-galaxy-s6-edge/help/rooting-deep-sleep-t3079385
Thanks for all of your work Chainfire!
Click to expand...
Click to collapse
Too many posts there of people CAPsing random gospel in red letters to make it more of the truth.
Some further (preliminary, non-extensive, quick) testing seems to indicate that it is indeed the binary status flag rather than the recovery itself that triggers this.
- After CFAR you end up with an official recovery (not necessarily from the matching firmware you were using)
- Binary status: custom, deep sleep issue
- Use root to pull that recovery from the device, trim it so it ends with the correct signature, tar it, flash it via ODIN
- Binary status: official, deep sleep works
- Use root to pull that same recovery again, blank out the signature, push it back (not via ODIN, just DD), reboot into recovery, then back to Android
- Binary status: custom, deep sleep issue is back again
Further testing still required for any real conclusions can be drawn. If this is true (end I certainly hope I end up being wrong) this means custom recoveries like TWRP (which also trigger the custom binary status) would also cause the deep sleep issue. It is the question if the problem is inside the stock kernel, and whether this is intentional (which would be very disturbing indeed) - guess checking out the kernel sources would be in order. On the other hand, it also seems like flashing any properly signed kernel will treat the symptom, it doesn't necessarily need to be the one matching your firmware (maybe not even exact model ?).
This recovery for the N925T is based on cyanogen mod with the ability to install zips but not backup and also DOESN'T have the deep sleep issue (supposedly)
Going to test myself tomorrow before work. Will edit with link
Edit: http://forum.xda-developers.com/showthread.php?p=60072372
^ already posted lol
Chainfire said:
Some further (preliminary, non-extensive, quick) testing seems to indicate that it is indeed the binary status flag rather than the recovery itself that triggers this.
- After CFAR you end up with an official recovery (not necessarily from the matching firmware you were using)
- Binary status: custom, deep sleep issue
- Use root to pull that recovery from the device, trim it so it ends with the correct signature, tar it, flash it via ODIN
- Binary status: official, deep sleep works
- Use root to pull that same recovery again, blank out the signature, push it back (not via ODIN, just DD), reboot into recovery, then back to Android
- Binary status: custom, deep sleep issue is back again
Further testing still required for any real conclusions can be drawn. If this is true (end I certainly hope I end up being wrong) this means custom recoveries like TWRP (which also trigger the custom binary status) would also cause the deep sleep issue. It is the question if the problem is inside the stock kernel, and whether this is intentional (which would be very disturbing indeed) - guess checking out the kernel sources would be in order. On the other hand, it also seems like flashing any properly signed kernel will treat the symptom, it doesn't necessarily need to be the one matching your firmware (maybe not even exact model ?).
Click to expand...
Click to collapse
https://github.com/eousphoros/android_kernel_samsung_exynos7420 If you want kernel source with some git history.
eousphoros said:
https://github.com/eousphoros/android_kernel_samsung_exynos7420 If you want kernel source with some git history.
Click to expand...
Click to collapse
It is interesting that you have noted you do not see the issue with a kernel compiled from source and a custom recovery. Is that kernel using the exact Samsung sources, or a transplant between CM and Samsung, or?
I'm not seeing any clearly relevant code in the kernel sources, though if it is deliberate they could have left it out (also I only looked really quickly, I don't have much time at the moment to dedicate to this). If the problem is even inside the kernel, that is. Note that binary official status is communicated between the bootloader and the kernel / KNOX via the cordon= and connie= in /proc/cmdline, if anyone else is looking.
Deep sleep issue is also present with the official TWRP (at least, in 20 minutes of testing there hasn't been deep sleep yet).
Chainfire said:
It is interesting that you have noted you do not see the issue with a kernel compiled from source and a custom recovery. Is that kernel using the exact Samsung sources, or a transplant between CM and Samsung, or?
I'm not seeing any clearly relevant code in the kernel sources, though if it is deliberate they could have left it out (also I only looked really quickly, I don't have much time at the moment to dedicate to this). If the problem is even inside the kernel, that is. Note that binary official status is communicated between the bootloader and the kernel / KNOX via the cordon= and connie= in /proc/cmdline, if anyone else is looking.
Click to expand...
Click to collapse
Linode 3.10.61 -> android 3.10 -> samsung sources is the merge order for those kernel sources i posted. One interesting thing I noted is the custom kernel is signed after the build process is done.
Also keep in mind im not even close to stock right now. Custom recovery, custom boot, most of the bloat from ms, ig, fb removed. Removed stock gapps, etc. So im probably not a good study case.
So I'm rooted, and installed stock recovery (SM-G925I) and deep sleep has come back, but since last night (~11hours total) it has only been in deep sleep for 24% of the time (around 2hrs 45mins) and it drained 15% battery in the first 6 hours, which is really really ****.
I checked better battery stats for kernel wakelocks/partial wakelocks, and it is saying that "PowerManagerService.Wakelocks" are accounting for ~75% of this... anyone have any idea how to reduce that?
Chainfire said:
Deep sleep issue is also present with the official TWRP (at least, in 20 minutes of testing there hasn't been deep sleep yet).
Click to expand...
Click to collapse
I can confirm testing the unofficial TWRP for Tmo S6 Edge that I do indeed get deep sleep. Also custom kernel.
---------- Post added at 11:44 PM ---------- Previous post was at 11:43 PM ----------
eousphoros said:
Linode 3.10.61 -> android 3.10 -> samsung sources is the merge order for those kernel sources i posted. One interesting thing I noted is the custom kernel is signed after the build process is done.
Also keep in mind im not even close to stock right now. Custom recovery, custom boot, most of the bloat from ms, ig, fb removed. Removed stock gapps, etc. So im probably not a good study case.
Click to expand...
Click to collapse
This man is a S6 Edge Genius
Again, a custom kernel. More pointers at the kernel being the culprit.
Related
About a month ago some of you may remember my posts that I was working on a kernel. Here is my first public release. The whole thing works at about 95% or so.
==============
The advantages I notice while using it besides the normal issues associated with Eclair are as follows:
1. Memory management has changed (has good and bad effects) Good: when you fly through 45 websites the browser does not crash as it eats memory. Bad: when you blow through 45 websites the browser will hang (easy fix hit home, and use app killer to free memory from apps you are not using) (Personally I like not losing my place as I get lost in the web, it also will prevent apps from dieing in the background when you are using multiple apps at the same time, if memory gets low enough the OS WILL KILL the offending apps). I personally found Eclair for Fascinate to handle memory available worse than this kernel, and I find this kernel handles memory more like Eclair on the Moto Droid did, and the Moto Droid had far less memory to work with.
2. UI has a faster response vs stock kernels, the kernel is also running AS scheduling vs BFQ but I updated BFQ to run as well if you want to revert.
3. Internet Connectivity appears to be faster with those apps that properly use the API. Web browsing, CheezeBurger, youtube etc all load content faster (efficiently? / Maybe related to memory management?)
Want something added to this list? Post your requests, just please be reasonable If I like the idea I will try to implement it. Remember this is for kernel features not system ROM modifications.
==============
Issues to fix (ToDo List, I am working to fix these issues / Updated 01/30/11):
1. Investigate and address bluetooth connection issues [ Confirmed that this issue does not affect everyone / or all bluetooth devices ]
2. Investigate and address remaining data connection issues (Orbot activates and test show as using tor on normal websites, tor addresses fail to connect to servers, also Orbot is unable to de-activate [Confirmed]
3. Investigate and address remaining camera crash issues [ Please zip and send in logs from /proc/kmsg, specify if you used the volume control zoom or pinch to zoom ]
4. Improve on touchscreen timing for quick flicks on the first attempt without burning up processor time.
5. Investigate and fix stutter/crash on camera zoom followed by attempt to take photo.
Notice something that should be in this list? Please make a post describing your issue, remember to include the kernel version/rom and the steps you performed to reproduce the issue.
==============
For those doubting, this IS 2.6.29.6, I personally merged the code myself, IT IS NOT 100% COMPLETE. Some drivers still need merging, and the V4L2 code is not completely converted because Fascinate uses different (updated?) V4L code (compare Fascinate's Eclair to Eclair on AOSP)
If anyone wants to help bug hunt I will forever be grateful. I would like to finish squashing bugs in this in the next 2 weeks as I really want to attempt to work on a Froyo for Fascinate. Even if it uses Eclair code to run the only RIL code we have.
I also semi-blindly fixed about 50-100 coding problems in the Eclair Kernel, varied from not returning data from a function that should have, simple void definitions that were returning when they had no data to return and no function collected it. Correcting order of operations in if statements. Declaring data types that were vague (unsigned vs signed). You will notice it compiles a lot cleaner...attempting to fix the camera code nearly kills the camera completely, I am thinking the broken code dumps variables by accident that the corrected code does not.
Edit: I wanted to share a few things every dev (some of it specific to kernels) should remember when nights are long and sleep is a half world away.
1) Keep a backup of your most recent WORKING work safe, because it is too easy to....uh oh *[email protected]$
2) If you edit the config file, remember to make clean and make mrproper before you make, otherwise your still on your original config file (a copy of the one you actually edit .config)
3) Do not put comments to the right of options in the kernel config file...apparently they will be discarded (the entire option line, not the comment, you'll see it in your compile error message logs).
4) Automate the mundane, I have a nice build environment setup, I type one line and it will make a brand new kernel from scratch (I'll be sharing that later, keep an eye on this post)
5) Work with what you have, don't wait for someone else too. Somewhere, someone is working on something better, and tomorrow it will be out.
6) Laugh...at something...anything because lets face it, you make better decisions in a good mood, in a bad mood...entire trees (code) die, either from rm -Rf /work/crap//* or a sledgehammer to the motherboard. Which brings us back to the first thing to remember, where did you put that backup...different drive I hope?
Attached is a working kernel, it will have issues using DI01 (such as no vibrations), it works great with DJ05 ROMS and maybe DL09 system roms. At this time I can not recommend a DL09 system rom with this kernel, during my initial tests it appears to drop GPS and cell data connectivity frequently resulting in having to relock on GPS satillites, and losing data connections in networked applications.
I highly recommend the setup I am running, DL09 Radio, Son Of Skywalker Blackhole v2.4 and this kernel (if you can handle the few bugs that is, it is beta).
Please feel free to post bug reports please include detailed information about the issues, I AM NOT FIXING APP PROBLEMS. Please remember to only report kernel issues and information specific to the kernel crash. If an app crashes on other kernels and not just this one please do not submit a report. This kernel is NOT setup for debug info, I will post one setup with debug turned on later. Right now, play around with it and report your results! Enjoy and have a great time :-D
GITHUB: https://github.com/sirgatez/
Edit 1: I thought I would mention that I originally started with the JT1134 kernel source from late Nov. - mid Dec. and the Samsung Fascinate stock source (from Samsung's Opensource website) then I merged in source from 2.6.29.6 from www.kernel.org and from Cyanogen's 2.6.29.6 Eclair kernel. I stopped on 2.6.29.6 instead of moving higher because of 1 reason, once you step in to 2.6.30 there are major driver changes requiring a lot of double verification and back trekking....In a few words, it is lots and lots of work, and I think that jumping from 2.6.29 to 2.6.29.6 will help transition to the 2.6.30 (Froyo?) series of kernels because then the majority of the work is in restructuring the driver code (which would likely best be done backwards, from the system .h files, to the .c handlers, down to the device drivers) from Samsung to match that in the stock 2.6.30 set. Complexity will be reduced by a measurable amount
Notes 1: Samsung's Android code has some significant differences under the hood from AOSP Android code, I have not sorted it all out yet, but it is possible that without an AOSP stock system that a full kernel update to the current AOSP code may not be possible. There is a built in virtual CD driver for what appears to be hosting the ISO built into the base Samsung system image, I have not opened the image yet but it appears to perhaps be drivers? Also it does not sleep the SD card like standard AOSP does, attempts to do so will disable the SD card from use with no ability to remount without a battery pull. (This is in 3 of 4 lines of code that AOSP had that must be commented out from the Samsung kernel for this SD issue to be prevented). For those wanting it, CIFS and NFS are compiled modules in this kernel. The current kernel is not over-clocked, and does not have voodoo. It does support both with a kernel configuration edit required for voodoo with the proper init scripts, and over-clocking requires changing just a few files and recompiling, I did neither as I wanted a true comparison to compare changes against the original stock kernel. The kernel does have the BLN notification code built in. BLN, Voodoo, and Over-clocking code are not my own creation they are pulled from their respective creators.
REMOVED ALL OLDER KERNEL INFORMATION
Update RC3 v2.2.4-VooDoo/NoVooDoo: This is a minor/major (depending who you ask) bug fix to adjust the processor throttles. Think I've got it too set to a good sweet spot now, the peaks are steep and a little harder to climb but the falls are also quicker. After turning it my phone on with it last night and about 2 hours of use I went to sleep, wake up a couple times to silence various alarms (I wake to wake up, but I want to sleep a little more, can't I do both?), and these are the numbers that setcpu reports for time in state:
1.2Ghz = 0 (Had the phone thottled to 1.0Ghz for this test, but with 1.2 on it only uses it when it needs it, might could leave it on?
1.0Ghz = 164978 (Not such a big a number as before)
0.8Ghz = 292008 (much more reasonable than before, could be a little lower)
0.6Ghz = 117672
0.4Ghz = 114250
0.2Ghz = 104715
0.1Ghz = 2965562 (This is what I was aiming for proportionally for 0.1Ghz)
Remember these times are mostly from idling, the idea was to reduce clockspeed when not in use to save some juice. The phone might take a moment to wake up from idle, but once it is going you shouldn't feel hardly any difference between this and RC2. Bootup clockspeeds from your first 3-4 minutes will almost always remain in the top tier due to applications still loading, media scanner running, etc.
Update v2.2.4-VooDoo/NoVooDoo: This is a major fix kicking us out of RC status and into actual release. Now for the menu, prepare your appetite, for the appetizer we'll be serving a much demanded voodoo color fix, and voodoo sound fixes. Followed by a main coarse of throttle tweaks, throttle shift updates (these are new they decide what the next cpu speed will be when a throttle is exceeded up or down, every kernel to my knowledge including my last used the default for a 5 slot kernel, here is a true 8 slot), and for desert a reduction in logged touch screen data from the touch screen, and an additional surprise to everyone, a reduced cpu load when using the touch screen!
Apparently the touch screen had authority to force the cpu into any slot it wants, it defaulted to slot 1 (which was 1.0Ghz for Blazed, now it's 1.2Ghz). The result of which meant that if you pressed the touch screen your cpu load catapulted up to 1Ghz for as long as you touched it even if you only held your finger in one place with no apps open. I have changed that to only go to 400Mhz, we'll see how this goes, if anything we might bump it to 600Mhz, so far besides a slightly slower response when first touch my touchscreen after leaving it alone for a long period it doesn't effect normal use from one app to another. If your processor is already at 400Mhz or higher it will not up it further. You will find this kernel will likely end up being the most battery conscious you have ever seen, once you get things moving the speed follows. If you find this kernel has a slower response than you feel it needs let me know, because when I fixed the touch screen from blasting the cpu load through the roof, it through off my throttle settings some, now they may be too conservative, report back and we'll fix them if it is a problem. Ah yes, please don't forget to tip your waiter if you enjoyed the service... [ REMOVED - Aggressive throttles not configured for use without aggressive touchscreen driver ]
Update v2.2.4R2-VooDoo/NoVooDoo: This is a minor fix to correct the choppy feeling that v2.2.4 had, the choppiness was due to aggressive throttles to fight off the excessive high speeds the touch screen forced on. This should correct those issues. Unless I have another bugfix for 2.2.4, I will be adding 1.1Ghz in the next release making it a total of 9 slots. The higher speeds still need some tweaking, if your looking to hit benchmarks please set min and max to the speed you are testing, otherwise the throttle is trying to save you power that doesn't need to be used. But for everyday use, these settings should be good
Update v2.2.5-VooDoo/NoVooDoo: Voodoo sound is still broken, anyone have the patched files I could compare to? The screen should be about 15% dimmer than it usually is on the lowest setting (and scaled up from there to 100% at max), I found the dimmest setting just too bright in the dark for my self, and hopefully it will help me save a little extra juice because I usually use my phone on the lowest brightness setting anyway. Major fix to throttles, now they are better tailored to this many slots. Slots updated to 9, 100Mhz, 200Mhz, 400Mhz, 600Mhz, 800Mhz, 1.0Ghz, 1.1Ghz, 1.2Ghz, and 1.3Ghz. Increased processor voltages (my ultra low voltage was about 25uv lower in most slots than everyone else who has a uv kernel...I was a little too aggressive on that one). Update bluetooth driver, it should remain connected now, could someone please verify this? Stability has improved alot with the higher voltages and better handling of throttling for different situations. Several other pieces of hardware discover that have authority to play with processor. I capped highest touch screen processor forced at 600Mhz (the higher I set it the faster your battery goes, default stock is 1Ghz), and all other hardware at 1Ghz (not very many requests, but this is where rouge 1.2 use came from). If you had issues before except for camera zoom or data connectivity in apps give Blazed another try. The slightly higher voltages should improve a lot of the random issues people were having. You may see an improvement in cellular signal now, 1.3Ghz is also stable, but I wouldn't run it all day either due to heat generated etc...Well I hope everyone enjoys, this should be the best release of Blazed Yet!
Update v2.2.6-VooDoo/NoVooDoo: This is a major fix for cellular signal issues many people have been having, the issue again was related to timing and the kernel modules not waiting long enough for the modem to respond before proceeding with action resulting in errors that caused a disconnect or forced a modem reset (requiring a phone reset to regain signal). I found waiting too long only slowed the entire phone down, so I opted to go with nanosecond wait times, waits that short however are active and will warm the phone up some, please report back if it becomes an issue as I am looking for a better wait device than udelay, preferable more like sleep that doesn't keep the processor busy. There is some performance stutter in the phone on the high end of internet connectivity speeds, but your not going to be losing your connection either, I'll continue to attempt to improve on this issue later on. [ REMOVED - Timing further improved in v2.2.7 ]
Update v2.2.7-VooDoo/NoVooDoo: This is a minor for that makes a major difference. Improved timing for communication with GPIO/modem this should be the end of the majority of network connection issues. It was entirely a mailman problem, put package in box, check for package, package still there? no=do other stuff/yes=...wait,repeat at package still there?, etc. The fix is put package in mailbox, wait long, check is package still there? no=do other stuff,yes=short wait and check again...Hope this helps alot of you out, I am aware the touch screen is a little slow to respond and I will be looking into that issue. This little fix should also improve usable speed over v2.2.6 because the waits are better timed.
Update v2.2.8-VooDoo/NoVooDoo: Timing is everything with electronics and this post...as promised today before 11:59pm is v2.2.8. Working Voodoo Sound v4, updates to the dpram/dpio communications again improving connection stability, if you lose your connections please report back (permanent loss requiring a restart only, fluctuations are different issue). Throttles set a little more aggressive about 5% so (helps ease on light loads), stepped up the first throttle jump from 100mhz to 400mhz (touch screen snaps back now). Dropped the 1Ghz permission for misc hardware to 400mhz if you have issues let me know, touch screen retains it's 600mhz permissions. Also screen brightness is reducible to gamma 1 brightness 10, typically reserved for battery about to fail status (I found the lowest setting just too dang bright). Enjoy everyone! I've been hammering away on this since 7am this morning and only had voodoo sound working about 9am. Thanks to JT1134 for his prebuilt kernel containing voodoo sound v2 working, adding v3 & v4 was a snap after that. Please report if you have any issues with it and remember you MUST be using the new voodoo sound app from the market.
Update v2.2.8R2-VooDoo/NoVooDoo: Another dpram timing adjustment (will lower your upload speed a little but will be more stable in operation, down speeds should be around 200KB down 44KB up on a good connection). Adjusted 1.1Ghz dividers per nemesis (not sure that it looks right, appears to get better benchmarks than 1.2 now will follow up on it). Made throttles a little more aggressive, 2.2.8 looked all over the place and having difficulty controlling processor use.
Update v2.3.0-VooDoo/NoVooDoo: Alot of work went into fixing dpram.c and multipdp.c it seems they were incompatible from the very beginning resulting in alot of ril issues and stability problems not just on my kernel but others as well, especially with nonstandard clocks and multiple slot kernel. I also added a fix to the framebuffer courtesy of JT1134 that has long since been overdue but a rare bug most probably have never seen. I fixed all the timing in dpram.c I also fixed the non-matching buffer sizes for multipdp and dpram (they talked to each other using different sized buffers...come on?!) There are still some bluetooth compatibility problems and the camera may still crash on zoomed photo, but I'd say it's 100% out of Beta! Enjoy! :-D I will be working on a Froyo kernel so stay tuned folks!
Update v2.3.0R2-VooDoo/NoVooDoo: Minor fix to help prevent dpram crash by handling and disposing of invalid commands sent to dpram, should fix seeming random lockup. [ Edit: corrected incorrect version numbers in original v2.3.0 series xda posts, thanks to s44 who caught the error, this does not affect kernel downloads, this were named correctly ]
Update v2.3.1-VooDoo/NoVooDoo: I reduced the delays in the ce147 camera driver, repairing the dpram driver resolve many of the seemingly random issues that had once plagued Blazed. Also a special treat for all you Blazed users, a new voodoo sound option that I have named "HEADPHONE_STICK" essentially the option when enabled (per boot) will force all audio directed to the external speaker to be instead directed to the headphone jack if the headphone jack has a plug in it. I find it excellent for not disturbing others around me with notifications when I would rather the phone be silent but I have headphones plugged in. Also excellent for using that awesome amp you have in combination withr you fascinate to wake you up in the morning. I will be contacting the maker of the Voodoo sound app in the market to get this option added to his application for quick and easy access. Also a major rework in the way kernel modules are loaded, all modules non-essential to booting are now stored in /system/kmodules. So if you reflash your system folder reflash your kernel or it may not boot, a quick browse will reveal what modules are kept there, I have more readily compiled and will release a separate "modules only" update.zip for those interested. By moving the modules it will allow for more options that are only available for including in the kernel boot image.
Update v2.3.1R2-VooDoo/NoVooDoo: Reverted some of the CE147 delay changes, reducing all of them caused some minor camera instabilities. EXT3/EXT4 moved back into the kernel, for some reason even with it's depends loaded ext4 doesn't load correctly as a module (resulted in broken boot on voodoo, now fixed). Also You MUST USE RED CLOCKWORKMOD TO FLASH IF USING VOODOO, you may use green clockwork only if Voodoo is NOT enabled due to the fact that some modules required for bootup are now stored on the system partition and if your using Voodoo only red clockworkmod has access to it. Also if you flash a different system or restore a backup you must reflash the kernel to ensure your modules are up to date. Also is a new file KMODULES-FULL contains all of the modules I have been compiling for Blazed thus far, several nifty ones but I have not setup any of the configs to use them, anyone versed in Linux command line can utilize them or setup scripts to use them, have a look inside the zip too see what there is to play with, request and I will add more if the module could prove useful to others. Several of the modules in FULL are also in the Kernel due to being required for startup redundancy (such as the 3D video/LCD drivers etc, which without a Android system folder, Android won't boot, nor will it boot without these modules so system seemed like a reasonable place to store them. The kernel/initramfs file is less than 6MB with Voodoo due to moving these modules to the system folder. I plan to add ClockworkMOD as soon as I have time to test it, then Blazed will also work for Recovery.
The Great Voodoo Debate: I have also been benchmarking Blazed against stock, to determine the difference Voodoo has on the kernel, so far it would appear Blazed has modifications either in the file system handling or the manipulation layers that are nearly equal to negating the speed lost to RFS's use before Voodoo or EXT4 is even brought into the equation. Just compare Stock vs Blazed (novoodoo) using 'RL Benchmarks SQLite Performance" from the market. A difference of 33.246 seconds in favor of Blazed, my preliminary results are (124.944 Seconds Blazed-NoVoodoo) (158.19 Seconds Stock) using the same exact system install less than 20 minutes apart between boots, with over 300 applications installed and several running like any other day. Based on this alone I find Quadrant is at least partially flawed at measuring proper I/O transfer timing, and I would NOT rely on it for an accurate benchmark in regards to I/O at this time until the issue is resolved by the Quadrant team. Voodoo does not produce the outlandish high scores that Quadrant makes out that it does, and Blazed is plenty fast in I/O even with RFS in use as shown by these preliminary results that any one of you can verify on your own using the "RL Benchmarks SQLite Performance" application, Voodoo does improve transfer compared to RFS in my tests but I am still putting together the results on Blazed NoVoodoo vs Blazed Voodoo. But as far as a 1800+ or 2000 score, so far my results say it just doesn't look realistic...sorry guys. On the flip side, if there is an error in my kernel causing a misread on the score you guys are welcome to help me find it and I will push the correction, but right now it looks like the issue is in how Quadrant measures I/O time, and I think non-atomic disk writes are the reason for the high scores, theoretically they would return claiming data is written to disk almost immediately when in reality it is still in memory and the kernel will write it to the disk at later time without the write time being considered as part of the benchmark (Google: write-caching, also known for providing significant performance improvements over atomic-writes).
If you appreciate Blazed and enjoy using it, please consider making a donation. Thank you for trying it out and have fun!
My initial impression after playing around with it for 15 minutes:
Seems to have given my phone new life/snappiness back that it had when I first installed super dark rom and stupidfast 1.54. My phone seemed to be bogging down lately. The internet definitely feels quicker too.
So far so good!
will try, thank you for the release.
Great work!
Sent from my Galaxy-S Fascinate
I don't want to turn you away from your work, but have you considered heading over to IRC and joining the guys working on Gingerbread? I'd assume that the more competent people working on it, the better.
Great work, the kernel seems to have given new life to my test fascinate! ADB does however appear to be dead (I got error device not found every time I tried to connect) Other than that I have no complaints, keep up the good work
That is very odd, as I have not had any issues using adb. Please reload your drivers to be safe and double check debug mode has not accidently become disabled. I wired up my fascinate just now and confirmed that ADB is working. (It was invaluable in working with the camera crashes). Also it maybe related to a conflict in the system rom vs the kernel. I personally have not have any issues with DI01 Fascinate stock, and everything worked great using DL09 radio, DJ05 system from SonOfSkywalker (BlackHole 2.4). Right now I am running DL09 Radio, DL09 System Rom from SonOfSkywalker v3, and my kernel from this post, thus far no issues. I am using Ubuntu v9.04 to test right now, and not windows to confirm that ADB is working. I will check on windows later today when I have a chance.
anyone else having an issue with bluetooth? It says "Turning On" but does not turn it on just reverts back to "off" status.
I still have DJ05 modem and on blackhole 2.3 something but updated market and swype maunally.
Camera force closes when you go to zoom in.
Sent from my SCH-I500 using XDA App
I assume disabling voodoo would be a prerequisite to installing this kernel? Though I'm curious what partition scheme are you using for this? Is it using samsung's default filesystems for /system /data etc?
EDIT: Forgot to say, this is re-gosh-darn-diculously awesome, thanks for your hard work.
wizang said:
I assume disabling voodoo would be a prerequisite to installing this kernel? Though I'm curious what partition scheme are you using for this? Is it using samsung's default filesystems for /system /data etc?
EDIT: Forgot to say, this is re-gosh-darn-diculously awesome, thanks for your hard work.
Click to expand...
Click to collapse
Yes, you MUST disable voodoo before using this kernel. I will put together a voodoo and OC flavor of this for those interested later. As of now I have only been working with non-OC and non-Voodoo in this kernel to gauge how the work changed the experience.
Edit: Oh yes, it uses the default partition scheme. It is a goal of mine to eventually change the formats of partitions (similar to voodoo) but keep the layout, it is my thought that doing so provides the largest window of compatibility between stock Samsung/VZW Roms and custom Roms. With a proper recovery, the change could be performed and backups and restores would work no matter the format of the internal media as the layout remains the same.
I tried this kernel briefly. I couldn't get my computer to recognize that the phone was plugged into it. I use my phone for tethered net access. Deal breaker for me. It would beep once like it was going to work as normal when plugging in an accessory and then beeped three more times in quick succession like the cord was being pulled.
Sent from my SCH-I500 using XDA App
bwheelies said:
I tried this kernel briefly. I couldn't get my computer to recognize that the phone was plugged into it. I use my phone for tethered net access. Deal breaker for me. It would beep once like it was going to work as normal when plugging in an accessory and then beeped three more times in quick succession like the cord was being pulled.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Yea my phone is not recognized by the computer either, even after a restart.
Naturally I double checked usb debugging and the drivers (adb connected to my white fascinate just fine and I made a jump back to Geeknik's test kernel to double check that something hadn't died in ole blacky and it registered there as well) I wonder if its just this fascinate (as it has had a laundry list of its own issues). This phone is running Superclean DJ05 completely stock and was fresh off a complete wipe and restore
bwheelies said:
I tried this kernel briefly. I couldn't get my computer to recognize that the phone was plugged into it. I use my phone for tethered net access. Deal breaker for me. It would beep once like it was going to work as normal when plugging in an accessory and then beeped three more times in quick succession like the cord was being pulled.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I can confirm that I am unable to access the phone via Samsung's drivers using Windows XP. [Added this too my list]
Wireless tether does work in case you need it, that is why I hadn't noticed this issue. Good catch!
I really like the transparency of your work. It's refreshing to actually read about the process you're working on and the way you explain it definitely makes seems like you have a good grasp of what's going on. I can never quite tell with the other devs. Anyway good luck!
FDro said:
I don't want to turn you away from your work, but have you considered heading over to IRC and joining the guys working on Gingerbread? I'd assume that the more competent people working on it, the better.
Click to expand...
Click to collapse
Agreed! If they can get GB running nobody is going to be interested in Eclair or Froyo.
I like the sound of this kernel. Imma flash it when i get home. Looking forward to seeing the OC version
SCH I500 Super Clean v.9 DJ05 Revolution 3.6 OTB oc'd lv1200 Voodoo5
2 SirGatez.
It sounds like you are pushing towards performance optimizations. Have you checked supidfast sources? I tried it before geeknik left and it was significantly faster then stock. May be you can get something from him.
I really appreciate what devs do here, cool stuff! However I do not understand why that much talent spend in vain... Every developer has his own build, mods and bug fixes. Is this real open source spirit to have so many versions? Looks like brownian motion to me.
Now, you can say that I'm free to do it on my own etc, as other devs pointed here. But, full fledged development it not for everybody by various reasons. I hope it is obvious. Would be nice to see some consolidated development! Then it will be much more easy for mere mortal to contribute to that product. We all have same phone!
Once again I do not want to upset anybody.
bendbowden said:
Great work!
Sent from my Galaxy-S Fascinate
Click to expand...
Click to collapse
Also, great write up! I will report back if I notice any bugs not mentioned above.
Hello everybody
since 2 or 3 days my S3 doesn't enter deep sleep anymore.. i wans on checkrom V4 ... already tried to:
- factory reset/full wipe
- Flash again ROM and also tried different ROMs with different bases
- Used different kernels
- used ODIN to put original firmware
everything was unsuccessfull... i dont know what to think anymore
never happend before and i tried really a lot of different ROMs..
any suggestion?
Thanks
baurog said:
Hello everybody
since 2 or 3 days my S3 doesn't enter deep sleep anymore.. i wans on checkrom V4 ... already tried to:
- factory reset/full wipe
- Flash again ROM and also tried different ROMs with different bases
- Used different kernels
- used ODIN to put original firmware
everything was unsuccessfull... i dont know what to think anymore
never happend before and i tried really a lot of different ROMs..
any suggestion?
Thanks
Click to expand...
Click to collapse
How did you check that is not entering deep sleep?
Did you restore/reinstall your apps before checking?
If you used BetterBatteryStats you can view what is waking up you device and how often/long.
If you didn't restore your apps then I don't have any idea what is going on. If you did probably one of them is at fault and you should get a tool to check which is. If you don't want to buy an app like the one mentioned before you could remove recent installed apps one by one and check if the problem in gone.
dav_991 said:
If you don't want to buy an app like the one mentioned before you could remove recent installed apps one by one and check if the problem in gone.
Click to expand...
Click to collapse
BetterBatteryStats is available free to XDA members here.
You can also still buy it from Google Play to support the developer, which is what I did.
well I could see no deep sleep using CPU spy but ot was the only app I installed, to avoid other apps to interfere...
no deep sleep at all.... 200Mhz instead of deep sleep...
Just checking bbattery stats...
The most using in "partial wakelocks" is "PhoneWindowManager.mBroadcastWakelock" .. what is it?.. no app istalled but CPUspy and Bbattery stats
baurog said:
Just checking bbattery stats...
The most using in "partial wakelocks" is "PhoneWindowManager.mBroadcastWakelock" .. what is it?.. no app istalled but CPUspy and Bbattery stats
Click to expand...
Click to collapse
There's one app or device calling for a wakelock and due to a possible malfunction it doesn't get released. My programming skills are very limited, maybe there's something wrong with the hardware itself, maybe try disabling Wifi and your GPS module and observe BetterBatteryStats.
more2come said:
There's one app or device calling for a wakelock and due to a possible malfunction it doesn't get released. My programming skills are very limited, maybe there's something wrong with the hardware itself, maybe try disabling Wifi and your GPS module and observe BetterBatteryStats.
Click to expand...
Click to collapse
Thanks for answer ... hope no hardware failure but i fear it is... i deep cleaned my S3 but problem still here
I have been having the same problem on my S3, running an unmodified, non-rooted factory stock ROM.
I've done a full factory reset a few times with no improvement, although I am guilty of not running without any downloaded apps to eliminate that variable.
I did manage to make this problem go away for a few days and get normal awake time vs. screen on time ratios. PhoneWindowManager.mBroadcastWakeLock even disappeared from BetterBatteryStats' Partial Wakelocks list, instead of being at the top of this list as the worst offender by a large margin.
This happened after I "disabled" a number of unwanted, seemingly safe to disable built-in apps using Settings/Application Manager/All. I first had to uninstall any updates that had loaded over the built-in apps I was trying to disable, since the Uninstall Updates button replaces the Disable button. After that, most of these built-ins then gave me a choice to disable, although some ended up with a disabled Disable button once updates were uninstalled. Those that didn't have a disable option were allowed to redownload their updates, if any.
While the Google Play Books and Google Play Movies & TV apps were re-enabled right away (my guess is that the Google Play Store app re-enabled them, but there could be some other safeguard doing so), the other built-ins that allowed me to disable them stayed disabled.
At this point, I'm not sure why this problem has returned.
Because I didn't log which apps I ended up disabling, I can't tell if one re-enabled itself as the Google apps did. I tend to doubt that this is the case; if an app was going to do this, I doubt it would wait beyond the first reboot at the latest to do so.
Since I haven't downloaded any apps to cause PhoneWindowManager.mBroadcastWakeLock to suddenly resume keeping my phone awake, all that I can think of is either an automatically downloaded update or a changed setting.
The most significant setting change that I made before this problem resume was in BetterBatteryStats (purchased version). I had previously not enabled the watchdog settings, and had recently turned them on. (One benefit of having done that is getting Kernel Wakelocks captured for the first time since moving from Gingerbread on a Droid X to ICS on my Galaxy S3.)
This isn't a "phantom" problem in reported awake time only. While this problem was fixed, I had very noticeably improved battery life.
As much as I hate factory resetting my phone, and would hate even more not having my usual stable of apps loaded for a while, I may be forced into doing some organized research and experimentation if nobody else comes up with a fix.
I hope the above helps shed some light on what is happening so that we can get rid of this problem.
BTW: Any suggestions of what tests should be included if I decide to do a deep dive on this?
Any and all help with this problem is greatly appreciated.
Best regards,
Simcha-Yitzchak Lerner
This is what i get. Stock kernel but i think it can do more. But do i have to always have data on?
Sent from my GT-I9300 using xda premium
Don't know whist to try anymore...
Do you think it cold be an hardware issue?
Maybe i could try to unroot my device and root it back?
Any other ideas?
Thanks
Just another consideration...
If i enable airplane mode deepsleep works...
?..
Really first time i face such a strage problem and i ha ve ISEF and flashed hundred of roms on a lot of devices
May be a solution ...
Hi everyone,
I got the same problem for a long time : phonewindowmanager.mbroadcastwakelock (seen on better battery stats) and no more deep sleep
or sometimes my phone was in deep sleep and another time it did not. I wasn't able to know exactly why ...
May be you'll think my solution is a little bit 'funny' but I'm convinced that my case is guilty !
I explain myself ...
I got a Sena Case made in real good leather and it fits perfectly to the SGS3 ... so perfectly that when I listen to music, the 'Volume Down' button
is 'pressed' by the side of this pouch and it's not possible to listen music anymore 'cause volume goes down to zero ...
And I fortuitously I made the connection between those 2 facts this morning : when my phone is out the pouch, no more partial wakelocks due to phonewindowmanager.mbroadcastwakelock ! And it goes normally in deep sleep mode.
I tested it by another way : I noticed the time spent in partial wakelocks, I put the phone in standby and pressed the 'vol down' button : the time spent in wakelock of type "phonewindowmanager.mbroadcastwakelock" incresead !
Same thing without pressing the volume button and no wakelock ...
My conclusion is that my Sena case continually press this button and causes those wakelocks. Since this morning (from 6.30 to 11.30) battery is at 77% ... Usually, it was between 50 and 60 % max.
Sorry for my poor english and all the mistakes I made.
I don't know if my experience could help someone .. let me know !
Hi xda Community,
at first - BIG THANKS TO ALL OF YOU ACTIVE CUSTOM ROM GUYS!!
With all your FAQs, Videos and postings, you made it possible - and easy - for me, to get rid of the annoying Sony ROM by rooting and installing a custom rom.
Currently I am running CM10 FXP230 on my Xperia U. I know it is not a stable version, but still a great improvement in speed for me and also the first ROM i discovered during my internet research for an alternative to the slow stock sony stuff.
However, i am facing some problems during the daily usage of my phone, perhaps one of you can support me during finding a solution for some of them.
1. Updating ROM
Pretty basic question, just need a confirmaton that i understood it the right way. I download the new Version of the custom rom (e.g.fxp232), copy the zip onto the smartphone and reboot into recovery mode. There i use CMW to first wipe cache and delvik cache, then select and install new version from zip.
Correct way so far?
What about the Google Apps? Do i have to reinstall them too?
Do i have to backup the SD card data and my apps,?
2. The Camera Fix
At the beginning i thought that i could live with an inverted camera due to the fact, that i am not taking many of them with my phone. but during the last weeks i had to face the facts - its important from time to time :cyclops:
During my search in this forum i found a user linking to a file called "FXP231_CM10_CamReverse_Fix".
Does this work only with FXP231, or also earlier and later versions?
How do I install it, like gApps in CMW?
3. Alarm Clock
I am using my phone as an alarm clock almost every day. Its plugged in to recharge during the night. Sometimes the phone crashes during the night time and the alarm is not going off. The display turns dark, no reaction to any button i plress, only the little signal light at the top right is glowing constantly. I have to take out the battery every time and make the same changes in settings over and over again.
Is this the "deepsleep" problem everyone is talking about? Is it connected to the cpu settings - I did select "conservative" there. Whats causing the problem?
4. Dial Pad
Every time i am dialing an unknown number the touchpad is hardly responding. It can take up to 5 minutes to enter all numbers and dial. I already deactivated the T9 contact search, still no improvement. Anyone any similar expieriences?
5.General Custom ROM Question
During my journey through this Community I found out, that there are a lot of different roms available. Some - with only minor changes - based on other custom roms, some based on sony.....whatever. Right now i am totally confused that ROM to use (if the above mentioned problems cant be solved!!)
I just need a quiet fast and reliable ROM to use in daily life - well this is everyones wish i guess......
So what am I doing with my phone? Basically I am just using my phone to call people, use whatsapp, check mails, manage my appointments and take a spontaneus picture from time to time. No Video, Twitter, Facebook, Games and what else is out there...........and no big experiments and time to backup, upgrade and reset my phone stuff every week.
Should I go back to CM9?
Cant I install a "normal google android" rom? Might sound stupid, but isnt there some kind of "pure" rom for all phones, that gives you the same comfort as the sony stock rom (-> update and functionality) ?
Even if there is not THE correct answert to this question, maybe some of you can at least suggest some interesting ROMs, that might fit
uff.....long wall of text, hopefully I could point out my problems good enough to motivate you to spent your time to answer them.
phil.star said:
Hi xda Community,
at first - BIG THANKS TO ALL OF YOU ACTIVE CUSTOM ROM GUYS!!
With all your FAQs, Videos and postings, you made it possible - and easy - for me, to get rid of the annoying Sony ROM by rooting and installing a custom rom.
Currently I am running CM10 FXP230 on my Xperia U. I know it is not a stable version, but still a great improvement in speed for me and also the first ROM i discovered during my internet research for an alternative to the slow stock sony stuff.
However, i am facing some problems during the daily usage of my phone, perhaps one of you can support me during finding a solution for some of them.
1. Updating ROM
Pretty basic question, just need a confirmaton that i understood it the right way. I download the new Version of the custom rom (e.g.fxp232), copy the zip onto the smartphone and reboot into recovery mode. There i use CMW to first wipe cache and delvik cache, then select and install new version from zip.
Correct way so far?
What about the Google Apps? Do i have to reinstall them too?
Do i have to backup the SD card data and my apps,?
2. The Camera Fix
At the beginning i thought that i could live with an inverted camera due to the fact, that i am not taking many of them with my phone. but during the last weeks i had to face the facts - its important from time to time :cyclops:
During my search in this forum i found a user linking to a file called "FXP231_CM10_CamReverse_Fix".
Does this work only with FXP231, or also earlier and later versions?
How do I install it, like gApps in CMW?
3. Alarm Clock
I am using my phone as an alarm clock almost every day. Its plugged in to recharge during the night. Sometimes the phone crashes during the night time and the alarm is not going off. The display turns dark, no reaction to any button i plress, only the little signal light at the top right is glowing constantly. I have to take out the battery every time and make the same changes in settings over and over again.
Is this the "deepsleep" problem everyone is talking about? Is it connected to the cpu settings - I did select "conservative" there. Whats causing the problem?
4. Dial Pad
Every time i am dialing an unknown number the touchpad is hardly responding. It can take up to 5 minutes to enter all numbers and dial. I already deactivated the T9 contact search, still no improvement. Anyone any similar expieriences?
5.General Custom ROM Question
During my journey through this Community I found out, that there are a lot of different roms available. Some - with only minor changes - based on other custom roms, some based on sony.....whatever. Right now i am totally confused that ROM to use (if the above mentioned problems cant be solved!!)
I just need a quiet fast and reliable ROM to use in daily life - well this is everyones wish i guess......
So what am I doing with my phone? Basically I am just using my phone to call people, use whatsapp, check mails, manage my appointments and take a spontaneus picture from time to time. No Video, Twitter, Facebook, Games and what else is out there...........and no big experiments and time to backup, upgrade and reset my phone stuff every week.
Should I go back to CM9?
Cant I install a "normal google android" rom? Might sound stupid, but isnt there some kind of "pure" rom for all phones, that gives you the same comfort as the sony stock rom (-> update and functionality) ?
Even if there is not THE correct answert to this question, maybe some of you can at least suggest some interesting ROMs, that might fit
uff.....long wall of text, hopefully I could point out my problems good enough to motivate you to spent your time to answer them.
Click to expand...
Click to collapse
First of all, this is a long question and you must donate me for answering. Haha. Just joking but you need to consider yourself and get experiences.
1. Reboot CWM and install the ROm amd Gapps needs to be reinstalled.
Wipe dalvik cache and cache then reboot. You're updated.
2. It is for FXP231 and so you must install 231 in order to have fixed
3. Go to deepsleep so much in CM10. Some said pretty awesome because it saves battery but it is in deep sleep so you can't really control your phone no more. Like you can't awake in the morning because you are in deep sleep.so hard to wake up. And yes your problem is deep sleep.
4. Use Go Dialer or Touchpal Dialer. Download from Play Store. It will make you better. Stock is still laggy and under development.
5. I run SlimCM which is CM9 and everything works except sound bug and FM Radio. Sound bug can be fix with Viper4Android. Run CM9 which is great, fast and stable.
And I really want to advice you is find out more yourself. It's more getting trouble but you will become more awesome I answer your question short so don't mind me about that but if you need anything, just quote and ask. Bye.
Sent from my Xperia U using Tapatalk 2
Sorry for asking again, but most times i just dont have the needed phrase to search for - combines with 50+ pages of results it really drives me crazy sometimes. After making a, lets say really stupid mistake, installing the rom in the beginning, it took me almost ages to find the threat to return to the beginning and reinstall it properly.
Little Zed said:
First of all, this is a long question and you must donate me for answering. Haha. Just joking but you need to consider yourself and get experiences.
3. Go to deepsleep so much in CM10. Some said pretty awesome because it saves battery but it is in deep sleep so you can't really control your phone no more. Like you can't awake in the morning because you are in deep sleep.so hard to wake up. And yes your problem is deep sleep.
Click to expand...
Click to collapse
^
Thanks a lot for reading and answering my questions anyway, you got yourself a honest "thanks button klick" as a reward :laugh:
Okay, so now i know that "my deepsleep problem" is kind of a reversed version of almost everyone eleses deepsleep problem. Everyone wants his phone to enter deepsleep, i want to prevent that.
Will this app solve the problem? Deep Sleep Battery Saver
I mean, if I can set the phone to "wake up" short before my alarm time it might work, right?
I read something about Apps causing the problem, especially messenger apps. Can anyone verify that information, or is it some random guess?
Edit:
Also I found out, that the Phone should not enter deepsleep while being charged. Unfortunately this seems to happen to mine over and over again.
phil.star said:
Sorry for asking again, but most times i just dont have the needed phrase to search for - combines with 50+ pages of results it really drives me crazy sometimes. After making a, lets say really stupid mistake, installing the rom in the beginning, it took me almost ages to find the threat to return to the beginning and reinstall it properly.
^
Thanks a lot for reading and answering my questions anyway, you got yourself a honest "thanks button klick" as a reward :laugh:
Okay, so now i know that "my deepsleep problem" is kind of a reversed version of almost everyone eleses deepsleep problem. Everyone wants his phone to enter deepsleep, i want to prevent that.
Will this app solve the problem? Deep Sleep Battery Saver
I mean, if I can set the phone to "wake up" short before my alarm time it might work, right?
I read something about Apps causing the problem, especially messenger apps. Can anyone verify that information, or is it some random guess?
Edit:
Also I found out, that the Phone should not enter deepsleep while being charged. Unfortunately this seems to happen to mine over and over again.
Click to expand...
Click to collapse
DS battery saver is the one for some phones that cannot go into deepsleep. It force the phone to Deep Sleep with some profiles to make your phone not deaf. Good app and I'm using it.
Blah blah blah, anyway, it's the ROM problem I think but you can simply reply FXP's CM10 about the fix No worries. I think you can fix nothing at this stage. And also I thought Alarm app crashing amd screen not waking up is not only the Deep Sleep issues but also the rom bug of excessive Deep Sleep or alarm app not fully functional. Please reply to the rom thread and wait for answer! High Five!!
Sent from my Xperia U using Tapatalk 2
Hello friends,
I'm using Xperia Go with stock JB version(6.2.A.1.100). The battery life of this stock rom is way too much annoying with 3G on. Example: Last night, charge was up to 82% & at morning it came down to 25%. Now think what if i use data traffic at day
I want a custom JB rom for Xperia Go with a good battery life with 3G on for some hours(which may last one day) & of course with a good ram where less important system apps are not preloaded & as much as low bug possible.
Well! The main problem is I'm not expert in these processes. So if anyone gives me a nice guideline, i will be very grateful
IMPORTANT: MY PHONE HAS LOCKED BOOTLOADER,I saw many people install CWM in their stock JB with locked bootloader & then convert into custom JB rom. I want to use that process, because I don't want to downgrade into ICS as I'm not an expert to do many things right
Seems that i want everything
My Phone: Xperia Go rooted with doomlord kit version 14
Build number: 6.2.A.1.100
Kernel version: 3.0.8+ (I think its the stock kernel)
My pc operating system: Windows 8
One question: When I will install CWM in my xperia before installing custom rom, will I loose every data & does unlocking bootloader wipe data?
@Pias94
In principle, unlockicking bootloader does not wipe any data, however I have seen a few posts that claimed it did.
Rooting should not wipe data waht so ever.
With that said, always backup your phone before making any changes. In any case data on internal storage will not be wiped. only data on device memory (contacts, sms, etc.)
Now to the real issue.
I tend to believe your problem is not the ROM itself, I use stock JB on my XP with decent baterry life.
First check your battery stats to see what takes most of it (no rom will change your screen battery consumption).
Second install Wakelock Detector and see which apps cause wakelocks, especialy screen wakelocks..
Rooting your device should be sufficient to let you tune it for good battery life and performance.
I see DooMLoRD Easy Rooting Toolkit is compatible with your device and firmware version and it is indeed easy rooting toolkit
Well, there are plenty of JB rom's you could try it all depends on you taste.
Regarding battery life, try checking if any apps run in the background.
You can use greenify too, it's an app that hibernates apps so that they don't run all the time
or they don't run on their own and just end up wasting resources and battery.
You could also try different kernels that have different governors.
Underclocking your device below the average helps too, by allot during the long run actually.
Look around the forums, just beyond the first page, sometimes you can find some really neat stuff you might like
ChikeD said:
@Pias94
In principle, unlockicking bootloader does not wipe any data, however I have seen a few posts that claimed it did.
Rooting should not wipe data waht so ever.
With that said, always backup your phone before making any changes. In any case data on internal storage will not be wiped. only data on device memory (contacts, sms, etc.)
Now to the real issue.
I tend to believe your problem is not the ROM itself, I use stock JB on my XP with decent baterry life.
First check your battery stats to see what takes most of it (no rom will change your screen battery consumption).
Second install Wakelock Detector and see which apps cause wakelocks, especialy screen wakelocks..
Rooting your device should be sufficient to let you tune it for good battery life and performance.
I see DooMLoRD Easy Rooting Toolkit is compatible with your device and firmware version and it is indeed easy rooting toolkit
Click to expand...
Click to collapse
My friend,
I uploaded some screenshots. The first two photos, i uploaded the app use right after charging my mobile & in the next pair of photos are next mornings'. In between i just make a call for 10 min. Nothing else. Now say what should I do?
btw, bt the wake lock detector, i found just facebook,messenger & whatsapp which might drain some extra battery.
Pias94 said:
My friend,
I uploaded some screenshots. The first two photos, i uploaded the app use right after charging my mobile & in the next pair of photos are next mornings'. In between i just make a call for 10 min. Nothing else. Now say what should I do?
btw, bt the wake lock detector, i found just facebook,messenger & whatsapp which might drain some extra battery.
Click to expand...
Click to collapse
Are facebook,messenger & whatsapp always on in stamina prefs?
I have whatsapp, viber. facebook, tahoo messenger, and talk, set to always on in stamina prefs and I only get about 1% per hour standby drain.
Is your movile data on or are you using wifi?
I can see in battery stats the phone is awake most of the time which it' shouldn't be in standby.
Below my stats for today, you can see there very little drain for standby time. I had 5 minutes calls and a bit of data on time, and still only about 35% drain for 12, while you had 40% drain for standby time only, this need to be fixed.
I must note though I have the 98screenstate_script that cap CPU speed when screen is off.
As I said, can't change screen on drain, you can set adaptive brightness or manually low to save some juice, not much though.
We need a bit more detail to know what cause drain.
In WakelockDetector check :"statistics since unplug" in prefs.
Charge battery full, no calls or nothing till next morning, or at least a few hours with no calls or screen on, take screen shots for all 3 wakelocks (screen, cpu and wakeup triggers, battery stats + graph + screen on time.
CPU Spy plus may also help if you install it, reset timers just before you unplug the charger, and take screen shot in the morning.
Hello,
I tried to use two thing.
1."First You Setting--->APPS--->All Tab---->ECO Mode Controller (Click Clear Data and Force Stop)
Then Again you Go Setting--->APPS--->All TAP---Setting.apk (Click Clear Data and Force Stop)
Charge Your Mobile 4 to 5Hours
After 4-5 Hours While Charging That Time You Click Vol Up+Power Button( after 3 times Vibrate)
Remove Your Charger and Again Plugin Your Mobile The Sony Logo With Comes And Charging Logo has been Shown
Then Power On Your Mobile While Charging
Then Go Setting--->Power Management TURN ON BATTERY STAMINA MODE"
After that I saw that charge duration came from 10 Hour to 3 day. But i think still charge is leeching, but a little bit slow.
2. I added whatsapp, facebook, messenger & one other app(360 mobile security) to the stamina prefs as u said.
But though charge leeched from 100% to 64%.
I must say a little improvement. Because is usually go down below 50 sometimes.
My mobile data is 24/7 on.
I've added the screenshots you want.
Note: Just one call came up that time. I couldn't receive though
Mobile data can cause some drain, but I think all traffic goes through wifi if wifi is available, and stamina mode supposed to turns it off when in deep sleep.
Can't make definitive conclusion, but I don't like this messenger, 490 times wakelocks. Why do you need it anyway, you can chat with facebook itself. Is the messenger in stamina active apps?
The active apps that require network can only work if wifi is connected, which apps you have there?
CPU stats look reasonable with 86% at deep sleep, and only 5% above 200MGHz.
Are you rooted, we can try and even lower that if you are.
Force stop the messanger for one day and see how it goes.
The see if turning off mobile data make a change, but don;t do both things at once so we can indentify which cause the drain, or cause most of it.
EDIT: I'll install the messenger on my phone and see if there's a change.
ChikeD said:
Mobile data can cause some drain, but I think all traffic goes through wifi if wifi is available, and stamina mode supposed to turns it off when in deep sleep.
Can't make definitive conclusion, but I don't like this messenger, 490 times wakelocks. Why do you need it anyway, you can chat with facebook itself. Is the messenger in stamina active apps?
The active apps that require network can only work if wifi is connected, which apps you have there?
CPU stats look reasonable with 86% at deep sleep, and only 5% above 200MGHz.
Are you rooted, we can try and even lower that if you are.
Force stop the messanger for one day and see how it goes.
The see if turning off mobile data make a change, but don;t do both things at once so we can indentify which cause the drain, or cause most of it.
EDIT: I'll install the messenger on my phone and see if there's a change.
Click to expand...
Click to collapse
Yes,the messenger is added in stamina mode. The messenger app is so cool you know & easy to use
I have facebook, whatsapp, messenger, 360 mobile security & play services are in stamina mode.
Yes,the phone is rooted. But i don't know how to make the system lower.
Ok, I will stop the messenger while again full charging my phone.
You should try messenger
Thanks1
Pias94 said:
Yes,the messenger is added in stamina mode. The messenger app is so cool you know & easy to use
I have facebook, whatsapp, messenger, 360 mobile security & play services are in stamina mode.
Yes,the phone is rooted. But i don't know how to make the system lower.
Ok, I will stop the messenger while again full charging my phone.
You should try messenger
Thanks1
Click to expand...
Click to collapse
The attached flashable zip adds init.d support and install the S98screenstate_scaling_mini, a modified version of S98screenstate_scaling.
This script caps CPU frequency and twaek CPU governor parameters. Help saving some battery when screen is off.
If you experiance problems delete the file from /etc/init.d and reboot.
ChikeD said:
The attached flashable zip adds init.d support and install the S98screenstate_scaling_mini, a modified version of S98screenstate_scaling.
This script caps CPU frequency and twaek CPU governor parameters. Help saving some battery when screen is off.
If you experiance problems delete the file from /etc/init.d and reboot.
Click to expand...
Click to collapse
Sorry my friend, i'm a rookie in those case. What shall i do with this file & how?
Rather I could use this apk file easily. So will this apk work?
https://play.google.com/store/apps/details?id=com.mhuang.overclocking
Pias94 said:
Sorry my friend, i'm a rookie in those case. What shall i do with this file & how?
Rather I could use this apk file easily. So will this apk work?
https://play.google.com/store/apps/details?id=com.mhuang.overclocking
Click to expand...
Click to collapse
Yes it works, I have used it before but you wil have to set the conditions at parameters yourself, and for some reason not all parameters changed as I wanted them too, but it may be governor issue rather than the app.
I rather a simple script doint it instead.
All yuu need is to flash it in recovery.
ChikeD said:
Yes it works, I have used it before but you wil have to set the conditions at parameters yourself, and for some reason not all parameters changed as I wanted them too, but it may be governor issue rather than the app.
I rather a simple script doint it instead.
All yuu need is to flash it in recovery.
Click to expand...
Click to collapse
Sorry, I've no recovery installed so I guess i have to use that apk file :/
Can you tell which recovery should i use for my stock doomlord rooted JB kernel?
Note: You are really helping me! Thanks!
Pias94 said:
Sorry, I've no recovery installed so I guess i have to use that apk file :/
Can you tell which recovery should i use for my stock doomlord rooted JB kernel?
Note: You are really helping me! Thanks!
Click to expand...
Click to collapse
I have an adb version of it too, not sure how good i tested it
Extract and run install
USB debugging must be enabled of course.
ChikeD said:
I have an adb version of it too, not sure how good i tested it
Extract and run install
USB debugging must be enabled of course.
Click to expand...
Click to collapse
Thanks!
but did u try facebook messenger yet?
Pias94 said:
Thanks!
but did u try facebook messenger yet?
Click to expand...
Click to collapse
Yes I have installed it, but only had 53 alarm wakeups., facebook is on top with 76.
I had an excess drain today.... 15% for 10 hours standby normally Google+ won't wake so much but today its on top of CPU wakelocks with over 1 minute, second is facebook with half a minute, but I think it's an app I made that caused soe of it.
/!\FOUND ONE FIX FOR SCREEN OFF BATTERY DRAIN - BOTTOM OF THE POST/!\
Hello, and thank you for reading my thread.
1. Introducing of me and my problem
I am the proud owner of a SGS3, but I'm not english so excuse my poor level of speaking. Hope you can understand me. My problem may seem quite familar, but after hours of reading I still did not find anyone with the same problem than me (I read on german, french and english - especially XDA - forums without any actual answer). Like I allready said I have a SGS3 but I had a SGS2 and a Note 1 before. Being a "Flash-addict", and tired of TouchWizz, I flashed a lot of roms, and of course CM. And here is the problem : on every CM installation I have I have terrible battery issues. Here you may think "Pfff... another n00b who didn't read the fu***** manual. (RTFM -- joke -- understood ?) So let's introduce part II :
2. My config'
If my problem is in a new thread and not in a general "Problem" thread, it is because it seems very 'unique' to me. I have :
- GPS totally off (localisation OFF in settings)
- WiFi constant refreshing OFF too
- NFC and AndoBeam OFF even if I read it has no impact on battery life
- I ALWAYS enter multi-tasking and close all apps
- WiFi and Data OFF (Data always OFF because I only have 50MB of mobile internet / month (Viva la france !) - WiFi only ON at home )
- Brightness on AUTO
- CPU governor on 'PEGASUSQ' or 'POWERSAVE' depending on usage
- Talking about usage :
- SMS and Facebook
- Apollo (sorry but I can't live without a7x or black sabbath)
- Bash (u know that weird app that eats your time)
- Internet via Chrome or default browser (at home)
- That's all (+ some games at home)
3. What I have tried
On SGS2 :
- Buying a new battery (talking about battery do you know how do be 1000000% sure you have an original battery ? Some people say about the 'Made in Taiwan / Made in Korea" etc... but I have friends why an original SGS4 w/ battery made in Korean and some w/ battery made in Japan...)
On GN :
- Buying a new battery
On SGS3 (my current one, as you may guess)
- I read it is better not to use Titanium Backup so I tried without (sooooooo long restoring all apps from Play Store)
- I read extSDcard can cause problems so I put it away - do you know where you can unmount extSDcard in CM settings ? I know this option exists in TouchWizz based roms.
- I tried all the placebo solutions like wiping battery stats and so on...
- I installed Boefla (sorry for misspeling) Kernel and used an "Extreme Battery Yank" presset.
- Always upgrading to last CM Nightly (and re-flashing Boeffla Kernel)
- Flashing Mods for battery life
- See last part for SCREEN OFF fix !!!
4. Extra Notes :
- I have no battery issues on Stock ROMs and most of Sammy based roms
- I use a 1A battery charger, Samsung Official or very well done Chinese Export
- I have an extBattery with 2A charging possibility if needed.
- I really enjoy CM11 and really wanted to use it as daily-usage ROM (and not another KK rom like SuperNexus)
- My phone heats a little bit more than on Sammy Roms
- Current Widget says my battery status is Good (not dammaged battery)
- Oh and I have the stock 2100 mAh Battery
Best stats reached : ~5 % in one night (pretty good for me) and 3% in 30 minutes video with Wifi on, samsung headsets, AUTO brightness, PowerSaving governor and synchronisation and all the stuff off.
When playing games like "Worms 2 Armaggedon" or just watching videos on YouTube in HQ by charging the phone with my 1A charger, the battery level does not move (+1 % per 40 minutes)
Thank you for reading my thread and being so awesome in modding our devices !
Edited : Solutions found
Applied this solution (from Reddit) :
After much experimentation, I realized that it is not GP services app itself that is causing the wakelocks, it's the google search app pinging the GP services app for location all the time! Especially now with the Google now launcher, google search app is always or almost always active. This setup seem to create excessive wakelocks for NlPCollectorWakeLock from the google search app (Google Now), which in turn shows up as GP services wakelocks.
The solution is to take away 2 permissions: the Google search app permissions to keep the device awake, and access location. This gets rid of the wakelocks, and still appears to keep google now etc. functional. You can do this using App Ops from the play store (needs root), or if you are on custom ROMs, through "App Privacy" menu setting. Additionally you could also turn off location history and reporting, to be on the safe side. Google Now still works, but now without the wakelocks!
Click to expand...
Click to collapse
another method for same fix is this one :
I know a great fix, if this can get to the top it will help a lot of people. It requires the Xposed framework and the module Wakelock Terminator. The free version lets you block 1 app, and that's all we need. Open up Wakelock Terminator, choose to block Google Play services, and filter it with the following: NlpCollectorWakeLock NlpWakeLock CheckinService NetworkLocationLocator
Click to expand...
Click to collapse
Here is an additional fix (thanks to ivek81cro)
Ok, i did what post said and it didn't help, then i went into Privacy guard and set deny for Keep awake for Android system. Phone then cooled down and battery drain stopped. I didn't notice that anything else changed on phone (i think i didn't messed up anything with that). Today i returned permissions to default and all is ok now, no bat. drain or heating up.
Click to expand...
Click to collapse
I will upload images and links as soon as I am authorized
After this "fix", I had my phone SCREEN OFF two hours without loosing any percentage, with GSM on, WiFi, BT and NFC off. (just like during night)
Still looking for solutions for SCREEN ON, will tell you !
I also have the battery problems. No matter what I do it still drains fast. When I use original 1amp charger and do something on phone my battery actually dies while charging... No idea on what's going on
Sent from my toaster
foggydisaster said:
I also have the battery problems. No matter what I do it still drains fast. When I use original 1amp charger and do something on phone my battery actually dies while charging... No idea on what's going on
Sent from my toaster
Click to expand...
Click to collapse
OK so I am not the only one, this is already a good (bad ?) thing...
up ?
+1
-2% in 50 min. in standby, screen off, data off. :crying:
Tried everything.
Principal post eddited : Added a solution from Reddit (I can't post links because of XDA's security) for exeptional battery economy when screen is OFF :highfive:
I have same issue since yesterday, i9305, CM-11-20140531-nightly, com.android.systemui takes allmost 50%+ of battery and drains it 5%/h when in "sleep mode", testing solutions posted above, will tell you if it worked. Thanks
Ok, i did what post said and it didn't help, then i went into Privacy guard and set deny for Keep awake for Android system. Phone then cooled down and battery drain stopped. I didn't notice that anything else changed on phone (i think i didn't messed up anything with that). Today i returned permissions to default and all is ok now, no bat. drain or heating up.
Principal post eddited : Added a solution from ivek81cro based on solutions already given :highfive:
battery drain cm11
Try this...
Developer options enabled
Settings...performance...CPU frequency...minimum...make sure its set to lowest...tick apply on boot box.
After clean install mine was set to 2 knotches from max...set to 300 and immediately fixed all problems with battery drain.
NOTE III
SPRINT
CM11 (ALWAYS CURRENY NIGHTLY)
The below link shows the tip mentioned above about the privacy guard.