Develop Bugs

[Q]How to wake up w/o battery removal?

How to wake up the phone without battery removal? I have Virtuous 1.0.1 ROM with advanced kernel and from time to time I have wake up issue. I would like to avoid removing battery because I have otterbox case on my phone.
Do you know any other way to wake up yhe phone?

Well if you can't wake it up with the button on top it is a problem. Are you overclocked? Try lowering it.
Sent from my T-Mobile G2

Open the keyboard....lol
Sent from my HTC Vision using XDA Premium App

wake up
I have seen the same behaviour with the stock htc latest (1.82.whatever).
top switch -- othing
opening kbd -- noting.
only a removal of the battery seems to help.
Of course it hasn't happened in a convenient place e.g. to see if I can still access it or if charging works etc.

If u installed trackpad wakeup, it seems to distort virtuous roms and keep the device from waking up all together.....there are posts about it in the developers forum
Sent from my HTC Vision using XDA Premium App

Also in some cases this is caused by underclocking with a screen off profile. I actually gave up on virtuous untill that problem gets solved. I havnt tried the latest version though.
Sent from my HTC Vision using XDA App

There are 2 distinct "screen on" issues with slightly similar symptoms.
One is the "screen wake issue" what is common with Virtuous, and typically caused by certain combinations of overclocking, and screen off profiles.
The screen wake issue is very well discussed in the Virtuous thread, and commonly/easily solved with the proper screen off settings.
http://forum.xda-developers.com/showthread.php?t=967153
But the screen wake issue, as far as I have experienced, manifests with screen sometimes flickering on for a second, and sometimes responding to multiple presses of the power button, or by opening the keyboard. There is a different issue, some have called "SOD" (screen of death) where the phone seems completely dead until you pull the battery and reboot. This seems to be more what you are describing, but I'm not sure. The cause of the SOD has not conclusively been discovered, and there is currently no known surefire solution. But it may be hardware and GPS related, maybe kernel related. Personally, I've experienced this across several custom ROMs (Virtuous, CM7), kernels, as well as stock. The only luck I have had, is that the stock DZ ROM with the Godspeed kernel is the only combination which seems completely free of SODs. One person sent his phone into HTC due to SODs, and they said it was caused by a faulty GPRS module, and fixed it by replacing the mainboard. Another person send this phone in, and it was returned untouched, with the same problem still present.
http://forum.xda-developers.com/showthread.php?t=857584&highlight=pulling+battery
http://forum.xda-developers.com/showthread.php?t=908095

shortlived said:
Also in some cases this is caused by underclocking with a screen off profile. I actually gave up on virtuous untill that problem gets solved. I havnt tried the latest version though.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Why people still do this just boggles my mind. All current kernels drop the processor down when the screen is off. There's no need - at all, for a screen off profile. It creates a wakeup issue as you can tell since SetCPU has to refresh the phones state then switch profiles in order to allow the processor to move into a higher state. That takes a lot of time (in computer time) thus creating this 'bug' that doesn't actually exist. The OC bug however does exist and is present no matter what you do aside from keeping it at 1.1GHz or less.

KCRic said:
Why people still do this just boggles my mind. All current kernels drop the processor down when the screen is off. There's no need - at all, for a screen off profile. It creates a wakeup issue as you can tell since SetCPU has to refresh the phones state then switch profiles in order to allow the processor to move into a higher state. That takes a lot of time (in computer time) thus creating this 'bug' that doesn't actually exist. The OC bug however does exist and is present no matter what you do aside from keeping it at 1.1GHz or less.
Click to expand...
Click to collapse
I had the screen wake issue on Virtuous, with NO screen off profile and OC'ed to 1 GHz. Making a screen off profile, but leaving a wide range for the CPU speed (not underclocking it) and interactive governor solved the issue in my case.

That might work better since most people I've seen tend to use the conservative or powersave gov. in their screen off profile. I'll correct myself too, what I said was from a CM standpoint since I've yet to use Virtuous.

Yeah, the screen wake issue on Virtuous is different from the one on CM7. If I remember properly, on Virtuous, using the advanced kernel results in screen wake issues for everyone or most people, unless you make some SetCPU/CPU Tuner setting adjustments.

Do you have SetCPU, or another program capable of CPU clock control installed? If not, install one of them and bring the max clock down... the Advanced Virtuous kernel boots at 245min/1516max - I noticed this after a fresh install of Virtuous 1.0.1/2 and the Advanced kernel

qzfive said:
Do you have SetCPU, or another program capable of CPU clock control installed? If not, install one of them and bring the max clock down... the Advanced Virtuous kernel boots at 245min/1516max - I noticed this after a fresh install of Virtuous 1.0.1/2 and the Advanced kernel
Click to expand...
Click to collapse
Completly agree.
I am shocked and appauled that most don't seem to understand that the os and it does not matter which(I.e. android,ios,windows) or platform (I.e. smartphone,tablet,desktop,etc) when you overclock more than just ur cpu speed is changed. If u have any experiance overclocking cpus on your home computer, you know u cannot let your system hibernate because it will not wake up. All operating systems allow the cpu to completly turn of in hibernation until it recieves an electrical pulse from the board. But if ur cpu goes from off to high it pulls way to much electricity and can't process then commands because all the recouces went to waking. If you have sleep parameters set with a narrower range the system will have enough resources left to process ur intial command...when it comes to sleep to wake there are no in between frequencies.
Sent from my HTC Vision using XDA Premium App

[Q] on ER3BUS XL2.2.5

Little question on ER3BUS XL2.2.5
To JSL, great job with this ROM.
Just one problem, I setup powersaving at 15%, and when the battery arrived at that point, the powersaving profile didn’t kick in.
No lower brightness, no animations off, no vibration off, no Wi-Fi off, yet they were checked in powersaving menu.
The ROM is clean, no TBKP restore, only tweaks applied are your contacts fix and the full GPU rendering explained by mike1981 and hamdir.
I posted here, as I’m a noob and I can’t post in developer thread.
Thanks

Check your power mode settings. They should be something like high performance, normal, economy. Switch this to economy and it should work.

Ronin_2 said:
Check your power mode settings. They should be something like high performance, normal, economy. Switch this to economy and it should work.
Click to expand...
Click to collapse
Thanks Ronin_2 for the reply, there is no such option in this ROM. Yet, in the “power” menu the power saver option was checked (turn on to reduce power consumption), which should be the economy profile you mentioned.

Could someone mention this to JSL?
Thanks in advance!
And by the way Happy New Year to all XDA developers and members!

Already did that. I think it's a bug indeed, but he will release a new rom tomorrow. The next version uses a new base. Maybe it's fixed
Sent from my Desire HD using XDA App

Ronin_2 said:
Check your power mode settings. They should be something like high performance, normal, economy. Switch this to economy and it should work.
Click to expand...
Click to collapse
that was when still on 1.05 as a base, 1.11 doesnt have it.
@ OP: It should have popped up a notice. If you dismissed it, it'll continue as normal, if you clicked the button that allows it to go to power save mode, it will do this. I have mine set to 20% and it works fine.
But tomorrow (or later today, depending on where you are in the world) I'll be releasing v3.0 based on 1.22 which also will fix a few issues there was with 1.11, and because of the nature of 1.22, arabic is already present in the rom, and I've also included zh_tw, which I bleieve is Thai.
But as of right now, I'm off to get my new years party on. T-minus 3 hours and 14 minutes. Happy New Years Everyone!

Thank you all for the replys.
@ JSL – The notice popped up, I pressed ok, yet powersaving did not kicked in.
Now I installed ER3BUS XL3.0 , thank you for the release.
I will reply after my battery drains.

Well finally my battery arrived at 15 %, the notice popped up, I pressed ok, yet still nothing happened.
I tried flashing “Er3BuS_3.x_Stock_framework-res”, same result as above.

[Q] Screen Wake Delay?

So I searched around in this forum but I can't find an answer. My Note 2 (AT&T obv) takes almost a full second to wake after pressing the unlock button. It's been like this through 2 roms and was the same way on my stock rom. Literally I press the button and it takes a good 1/2 to a full second to wake up to the lock screen. Am I the only person having this issue? I tried removing my SD card and it slightly lowered the wake time but it's still significant. I went from my Inspire 4G to this and even with the perseus kernel and both on cleanROM and Jedix6 or whatever it's called the problem persists and the phone doesn't seem as snappy as my OC'd Inspire. I mean the inspire had little to no lag at all after pressing the button to see the lock screen but it seems odd to have to wait as long as I do on a newer, faster phone. Maybe I'm just being nit picky... Any ideas?

Bliznade said:
So I searched around in this forum but I can't find an answer. My Note 2 (AT&T obv) takes almost a full second to wake after pressing the unlock button. It's been like this through 2 roms and was the same way on my stock rom. Literally I press the button and it takes a good 1/2 to a full second to wake up to the lock screen. Am I the only person having this issue? I tried removing my SD card and it slightly lowered the wake time but it's still significant. I went from my Inspire 4G to this and even with the perseus kernel and both on cleanROM and Jedix6 or whatever it's called the problem persists and the phone doesn't seem as snappy as my OC'd Inspire. I mean the inspire had little to no lag at all after pressing the button to see the lock screen but it seems odd to have to wait as long as I do on a newer, faster phone. Maybe I'm just being nit picky... Any ideas?
Click to expand...
Click to collapse
Ive noticed it as well. Got used to it and it don't bother me anymore but a solution would be nice
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

http://forum.xda-developers.com/showthread.php?p=33492447
Sent from my SAMSUNG-SGH-I317 using xda premium

have you tried to increase your minimum deep sleep cpu frequency from 200mhz to maybe 350mhz or so?
a shot in the dark would be reducing the animation scale in developer settings but this is only if it's considered an animation when you turn on the phone

battery life is amazing on this phone and if you agree and want to try it. There is a app called soft locker on the market that will fix the delay. I dont notice that much of a drain on the battery even though I know it has to have some. Basically the CPU in samsung phones go into a very deep sleep and that helps battery but if you use the above app it creates wakelocks that keep it from deep sleep and fixes the issue.
This can make battery life less but like I said I have used it for over a month and still get over a day out of my phone and I usually have 4 hours or more screen on time and still end day with 25%-50% battery left.

http://forum.xda-developers.com/showpost.php?p=35617276&postcount=2096
Apen83 in the Jedi ROM thread says to do this:
"Settings > developer options > window animations off / transition off / animator duration off"
Looks like its working for them.
If it works for you, hit the link and thank his post.

This doesn't help as it's not an animation.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

It's a characteristic of Exynos processors. It sucks, but what can ya do?

I'm using asylum rom and kernel and see nowhere near the delay that stock had. It's almost instant on for me

Its probably the pegasusq governor, but that's what you have to go with to be able to hotplug CPU cores. This is the price you pay for battery life.

You did not search well enough. There is no solution, and nothing you can do about it other than the aforementioned Soft Locker, which will negatively impact your battery life.
More info here: http://forum.xda-developers.com/showthread.php?t=1983697&highlight=wake+lag
It sucks, but I guess it's a sacrifice I have to live with on an otherwise awesome device.

CPU possibly defective

I've been noticing something with my cpu that seems strange to me. I run an app called system panel to monitor my phone for various things and I've noticed for the past few days that my second core is constantly sleeping, even under a full load it stays at 100% idle and system panel says that cpu 1 is asleep. I downloaded kernel tuner and it says that cpu 0 is active but cpu 1 is offline. Was running stock rooted with no tweaks or other things added so i tried using odin to go back to stock but I still get the same info. The first screenshot is from kernel tuner with root and the sceond is from system panel with no root. Could my phone be defective?
Sent from my SGH-T989 using xda premium

Try system tuner in the play store. It has an option in settings to force the second core online, all the time. Set it to always on, and set it to boot that way. At least you can test it to see if it can be forced online. It is normal for the second core to be sleeping most of the time. In your first screenshot I see a toggle for cpu1 on/off at the bottom. You accidently toggle that?
Also, what's up with your CPU temp being 32°F? Are you in the arctic tundra?
You could also try flashing a new kernel. I believe there are a few for touchwiz based ROMs. IMO you should go aosp based ROMs. Slimbean4.1.2 with asdk kernel is the best performing rom/kernel combination I've ever flashed
there is no spoon.....

I tried flashing other kernels when my phone was rooted but it kept giving me the same thing. I tried the toggle in kernel tuner to see if I could turn the second core on after noticing the issue but it did nothing. System tuner was able to force the second core on for a bit but about 30mins after boot, the core went offline and has not come back on since.
Update: found out why core went offline. Apparently, if I touch any frequency settings such as core speed or governor for either core, the processor doesn't like it and shuts down the second core. Not sure if that's normal or not. Once phone is charged enough, gonna try flashing a different kernel to see if the same thing happens when I try to change the speed and governor.
Sent from my SGH-T989 using xda premium

Here is a long story, but please read it all as I really think it will help explain how the two cores work together.
I had/have the same thing. Exactly as you described it. Here is what I found (What I think anyway). I ODIN'd to stock, rooted, and installed Trickster MOD. That app showed only one core working. From reading up on Trickster MOD changing any CPU settings will apply to both cores. I changed the speed, and check the info panel. It showed both cores at the same speed that I changed it to, but the second core was still not moving. I reset Trickster MOD to default, uninstalled it, and installed Kernel Tuner. Same thing. Only one core was working. I started to think it was the stock kernel, so I flashed Tiberius, Jedi, and am now on Faux123. All kernels are doing it. It's not a kernel issue, but a kernel/Stock ROM function. Here is why I say that. I installed CPU Stats, and enabled it to display the CPU cores in the status bar. 99.9% of the time only one core was working (When I mention "99.9% of the time" I mean only one core would be working for about five minutes at a time. Which would lead a person to think somethings wrong since they normally wouldn't stare for ten minutes at the phone's kernel stats trying to catch the second core come on, and think only one was working.). I did catch the second core come on very briefly, so I knew it was working even for a split second. When I did see the second one on I tried to quickly open whatever kernel tuner I had to see what the cores were set to, and what they were doing, but by the time I opened the app only one core was working. I did some thinking, and I opened Lookout and ran a full scan, opened a couple more apps that use a lot of CPU. Then I opened, and kept on top my kernel tuner. To my surprise again 99.9% of the time only one core was working. Even if the CPU load was at 100%. The second core never came on, BUT it was because the first core wasn't at 100%. The CPU load would get to 90% when the first core would hit 100% under heavy load, but no second core was working at all. I finally watched it long enough to see a pattern (Like 15 minutes). The second core will only come on when the first core is at 100% AND the CPU load is at 100%. Then the second core kicks in. Once both cores were working at the same time the CPU load quickly dropped back under 100%, and once it did the second core shut right off to leave the first core do the work. So long story short your phone is not broken. That's the way it's meant to work. In my finding anyway. I'm running the stock ROM from ODIN with Faux123 JB release 1 kernel. That's all my mods are, and running quadrant I get an average score of 3730, so I'm thinking both cores have to be working to get a score like that. Here is the Play link to the CPU Stats app: https://play.google.com/store/apps/details?id=jp.takke.cpustats
And here is what it looks like in the status bar (The last icon on the left showing both cores at max in one screen shot, and the second screen shot showing only one core working. Just to show it does show both cores working separately.):

Thanks for the explination. I watched everything like you did and same results as you. I'm grateful for everyone's input. It puts my mind at ease knowing that everything is like it should be.
Sent from my SGH-T989 using xda premium

That's a good score. What frequency and governor you running?
there is no spoon.....

ctrlaltdeln said:
That's a good score. What frequency and governor you running?
there is no spoon.....
Click to expand...
Click to collapse
It's easier to show in pics that type all the stats. Here you go:

Not sure if me forcing my second core to be on constantly did something or what but I just ran quadrant twice and I got a score of 5661 the first time and 5981 the second.
Sent from my SGH-T989 using xda premium

damn dude. Now that's a score. Obviously your battery life will suffer with that kind of performance. If still using system tuner u definitely want to turn that second core back to default. You dont need all that muscle. I run at 1.18ghz/ lag free governor monday - Friday and 1.67ghz on the weekend. Battery life is more important to me. And everything is still buttery smooth. Glad all is well, your phone is back baby.
there is no spoon.....

[HELP] Panic - CPU seems broken, I need help!

First of all, Hi everyone - chefs, users and admins!
I am writing this post with a really heavy heart now, almost bleeding experience happened to me from nowhere about 2 months ago. I feel quite an advanced "flashoholic", however I've broke up with that few years ago. In 2013 I sold my Note 2 and started "new life" with Android, bought a DSLR and engaged into photography. This year, in february I have bought a tablet as I needed really something for business purposes, and I have chosen a Tab S 10.5 LTE. I didn't ever hear about any Knox tripping or anything, and as soon as it arrived I flashed a AOSP ROM to my thingie as I love AOSP overall. Than strange things started to happen with my CPU. As I recall I have noticed it first after installing Xposed to the tablet - it started heating pretty badly. When I checked my CPU states through ROM Toolbox etc I noticed it sometimes freezes at frequencies around 1.7-1.9 GHz, and during this behavior max frequencies could even fluctuate from 1.7 to 1.8, 1.9 and so on. It looks like "something" changes max frequency setting of CPU as it wants, whenever it wants to and pushes usage to the maximum.
Now, I started to look for a fix - uninstalled Xposed, every root apps etc. Nothing stopped it. I was "pretty sure" the cause is in AOSP thing and the conflict between my hardware and custom AOSP Roms. So after 2 months of tryouts to solve the problem, I today reflashed TW to "finally" get rid if this and save my battery life. What shocked me was... the bug is still here! Even with 0 apps installed, all ROM stock and clean, my CPU goes crazy, the back is hot, and CPU monitoring apps show a hard usage of 1.9 and 1.8 GHz frequencies. At this point I started to panic.
To mention - before I posted this here, tried to search over xda, googling it and so on, but it seems noone has such problem anywhere! As long as I know I can't get my warranty back, and I feel really panic and don't know what to do. I am asking experienced devs or anyone who faced it before for some help, on my knees. This tablet is great, but pretty useless when my battery hits 20% after 4 hours!
EDIT
I snapped a screenshot of some kernel options I don't understand, however someone maybe would find any wrong input here (as I can change them thanks to the app). Thanks. PS. I have changed max fr tp 550 in order to avoid heating and battery drainage, to this moment thayt's the only way I know to stop it.
Thank you very much for any help and advices, and sorry for my bad english.
/K.Z.

Try installing Watchdog, and in the setting include phone and all other process monitoring, see if it can locate what is taxing your cpu.
https://play.google.com/store/apps/details?id=com.zomut.watchdoglite&hl=en_GB
John.

Tinderbox (UK) said:
Try installing Watchdog, and in the setting include phone and all other process monitoring, see if it can locate what is taxing your cpu.
https://play.google.com/store/apps/details?id=com.zomut.watchdoglite&hl=en_GB
John.
Click to expand...
Click to collapse
Thank you, I will try it. Very helpful. I'll post how it's gone.

Tinderbox (UK) said:
Try installing Watchdog, and in the setting include phone and all other process monitoring, see if it can locate what is taxing your cpu.
https://play.google.com/store/apps/details?id=com.zomut.watchdoglite&hl=en_GB
John.
Click to expand...
Click to collapse
Hi John, it looks like that option doesn't work. I see that none of apps exceeds CPU usage over 10%, but the clock still goes on 1.7GHz etc. Sometimes it cools down, but it happens rarely.

Did you adjust the setting to monitor all phone processes, even if you have an wifi only tablet still do this.
John.
Thejungle said:
Hi John, it looks like that option doesn't work. I see that none of apps exceeds CPU usage over 10%, but the clock still goes on 1.7GHz etc. Sometimes it cools down, but it happens rarely.
Click to expand...
Click to collapse

Tinderbox (UK) said:
Did you adjust the setting to monitor all phone processes, even if you have an wifi only tablet still do this.
John.
Click to expand...
Click to collapse
Sure, but the app doesn't seem to have any options button anywhere, just 3 tabs... sorry. However I can see it is monitoring all system apps also, if it helps.

it`s been a while, i will install it on my T800
John.
Thejungle said:
Sure, but the app doesn't seem to have any options button anywhere, just 3 tabs... sorry. However I can see it is monitoring all system apps also, if it helps.
Click to expand...
Click to collapse
---------- Post added at 10:40 PM ---------- Previous post was at 10:37 PM ----------
Hold the button left of the home button down to get the settings, the left touchkey button hold it down to get settings.
John.

Thanks but umm.. nothing happens. Tried holding down task switch capacitive button for few seconds on every tab, but it just goes to task switch view.

Strange, I just hold the button down and within 2 seconds the strip along the bottom of the display appears, maybe you are in the wrong mode, there are three section on the top of the screen, you need to select the far left one called STATS.
John.

Tinderbox (UK) said:
Strange, I just hold the button down and within 2 seconds the strip along the bottom of the display appears, maybe you are in the wrong mode, there are three section on the top of the screen, you need to select the far left one called STATS.
John.
Click to expand...
Click to collapse
VERY strange. I did it on all 3 tabs, just nothing happens. Is it possible that app changes maximum frequency of my CPU? I don't believe any app has possibility to do it on it's own...

Have you tried it again with watchdog on the same screen in my screenshot then press the button, watchdog does not change cpu frequency.
John.

I used to have the same problem on AOSP roms and some Touchwiz roms! When you first flash it and set things up, CPU usage is fine. But after a few days maybe hours, CPU would do the same exact thing like yours! Then my device gets hot and drains battery.
I found this to be a problem with AOSP 5.1.1 roms. Resurrection remix, CM12, PAC ROM and yeah. Never had problems on Cm11. The only ROM that solved my heating issues and no cpu problems are AOSP roms on 5.0.2 or Liquid Smooth rom. 5.0.2 was bug free. Liquid Smooth ROM has an custom kernel which helps cool down the device and reduce the high CPU usage. Seems to be the only ROM without issues for me on 5.1.1. For Touchwiz roms, I just install skyhigh kernel and turn on hotplugging and CPU multicore power saving to solve heat issues. But really on Touchwiz roms, CPU is fine most of the time for me.
My device is SM-T800 BTW. This is what I found out from flashing many roms.
Sent from my SM-T800 using Tapatalk