Related
Hello all. Kinda new here, but I've been flashing my hero with roms from here for a while now. My latest attempt at a good rom is the VillainROM 12.0.0, this is my first time with a VillainROM, and I don't know if this bug exists in previous versions. In my opinion it is a very minor issue, but maybe not for someone else. I'm not a developer, so I don't know what could be causing it, and I don't know if I should be reporting bugs on the VillainROM site, or here, so I'm going to start here...
I downloaded the ROM from the VillainROM12.0.0 thread...
Install was flawless, worked perfectly.
The ROM runs extremely well in all functions, so no complaints there.
The only issue is a slight (10+ seconds) hang when I press the power button to turn on the screen to unlock it and the WiFi connection has timed out. Other ROMs I've used, including the stock ROM would come out of this sleep mode, and then try to reconnect to the WiFi, and they've done so with flawless success. However, this ROM does not, at least not for a minute or so.
This is how I can reproduce the problem, and it takes a while. I usually plug my phone into a charger at night and let it charge over night, and unplug it in the morning to head off to work or whatever. Once the screen turns on on its own after the external power source is disconnected (which all ROMs have done) the screen is unresponsive, and all buttons are unresponsive. The screen remains lit up on the lock screen stuck for at least 10 seconds, then goes black, then pressing the power button to turn the screen back on will restore the phone to an unlocked state (assuming it remembered the swipe action from when the screen was locked and stuck) but takes about another 5 seconds to come back on. This only happens if I have the WiFi radio on while the phone is sitting idle for an extended period of time (long enough for the radio to automatically go into its sleep mode perhaps?).
Here's the info from my phone...
Firmware Version: VillainROM9.0.0
Baseband Version: 63.18.55.06JU_6.35.09.26
Kernel Version: 2.6.29-ninpo-freqtwk{AT}titan-dirty-b7a296faninpo{AT}titan #39
Build Number: VillainROM12.0.0
Software Number: 3.32.405.1
Browser Version: 3.1
I'm not sure if this is just a fluke, if I should reflash and see if the problem persists. Anyone else able to reproduce this?
Again, if this is the wrong forum, please feel free to move it, and thanks XDA, this site is an awesome resource!
PS... I had to replace the at sign with {AT} in the Kernel Version due to Forum restrictions (It thinks it's an outside URL and I'm too green to be able to do that...)...
Are you running setCPU or OC Widget?
It look likes the lower CPU frequency is too low. Open SetCPU or Overclock Widget and increase it a little.
If you use profiles, in SetCPU:
> Check if you have a "Sleep Profile"
> Check if its frequences are too low.
> If yes, increase it.
It normaly happens when you have a 19Mhz - 2XXMhz on-demand sleep profile.
Increasing that 2XXMhz to 3XX or 4XX may solve the issue.
If not, try to reflash, or use VillainROM IRC at their website.
First your radio is a bit old. Try upgrading to the latest radio from here:
http://villainrom.co.uk/viewtopic.php?f=24&t=323
Second, especially regarding the wakeup issues, try my kernel for VR12 from here:
http://villainrom.co.uk/viewtopic.php?f=97&t=1928
It has no wake-up problems even @ 691/160 (what I used) as well as better battery life and performance....
Turn up your minimum set cpu speed.
erasmux said:
It has no wake-up problems even @ 691/160 (what I used) as well as better battery life and performance....
Click to expand...
Click to collapse
Pulser has no problems waking up at 19MHz with my kernel. Stable Min/Max frequencies are unique to each phone it has nothing to do with the kernel.
In theory I agree with you completely. But in practice with each kernel I get a different wakeup "performance" using the exact same frequencies. I always prefer setting the min to 160Mhz, but like many many others, in most kernels - including your kernel which comes with VR12 I get heavy wakeup issues which disappear only @ min 480. In other kernels (such as those by Radu) these wakeup issues still exist but are less pronounced (very very rare).
For me and others which have given my kernel a shot there have been no wake up issues @ min 160Mhz. Battery life and responsiveness also improved according to those who have tried my kernel (and optimizations).
BTW "my" kernel is just the HTC official kernel release + OC enable, so its more HTC's kernel than mine.
Like you said it is device dependent, ROM dependent, user dependent, everything.... I am just saying that until now I have not gotten any negative feedback on my kernel, and I think people should give it a shot and decide for themselves. Hopefully they will also be kind enough to share their experiences with me, so if there are problems I can try to fix them.
Thank you all for the suggestions. I do not use any OC utilities, it's the ROM as it was when I downloaded it. Barely any applications installed (some games, auto task killer, handcent...).
I've updated the radio to a version I found in a SenseHero 2.1 thread, but that radio broke MMS and some other data network features. I am in the US, on AT&T (I know, no 3G, but I'm ok with that ), will the radios listed work propperly on this network?
I was also able to reproduce the hanging issue by turning on the WiFi, browsing around the Market, and then exiting the market and turing off the WiFi. It seems that during the switch to the mobile network from WiFi is when something funky happens. Is there a way to get logs to show what might be going on?
First of all try the newest radio from here:
http://villainrom.co.uk/viewtopic.php?f=24&t=323
If 6.35.15.14 does not work well for you, try either 6.35.15.11 or 6.35.15.01 - If I am not mistaken they are all from the latest HTC release from different parts of the world, so one of them should work well for you.
If you want to get a log for the problem, use the adb logcat. Another simpler option to try and isolate the problem is check if reflashing the ROM (after a backup and a full wipe) solves the problem. Also check if the problem exists in other ROMs.
I have flashed the radio with the latest from the site as suggested (6.35.15.01 was no good when I flashed with that one before, caused all kinds of problems with MMS/SMS, and other network fuctions, but I didn't try that radio with the VillainROM). MMS and such still work, so that is good. I'm going to try to reproduce the other issue tonight, but that may have fixed the issue... I'll update the thread with the results.
Looks like the new radio did not solve the problem. Is the next step the new Kernel?
Sorry for the long delay in response...
The problem is still happening. I have now flashed with a different ROM (Chronos Droid 2.1.2) and the problem persists. However, the lockup doesn't seem to be as bad... Am I the only one with this problem? Should I change my wireless network settings to GSM only? Or leave it on Auto? I'll play around with that and see what happens. It just seems that changing from the mobile network to the WiFi network (and vise versa) is when the problem happens...
Nope, that didn't help. When I went to GSM only, I had no data network connection, and when I went to WCDMA only I had no connection at all. On GSM/WCDMA Only I have both... I wonder if it is something with this phone and the .29 kernel? But then wouldn't everyone here have this problem?
I have this issue too, using ninpo's kernel. I am going to increase my min freq but it's already at 3xx - fingers x'd
I don't see this being a kernel issue, I have a feeling its just a wifi issue on the new rom bases.
m4rk84 said:
I have this issue too, using ninpo's kernel. I am going to increase my min freq but it's already at 3xx - fingers x'd
Click to expand...
Click to collapse
Please let me know what happens.
I did not have these problems using the SenseHero ROMs (older Kernel), only Villain and now Chronos... :S I don't use any OC apps, just leave it all stock from the ROM. If I use one and increase the speed at sleep, (probably an obvious answer) will this drain the battery faster?
Still hanging. Does this have anything to do with wifi's android default sleep behaviour?
I'm having all kinds of lag issues when network queries are starting, especially during MMS/SMS operations. Could be a Handcent update, but the default messager thinger is also quite slow. I'm tempted to go back to an older ROM, this is getting frustrating...
Just rooted my phone a week ago and installed setcpu and a new kernel (made for 4.0.2 - and I quadruple checked that 1) I am definitely on 4.0.2 and 2) the kernel is definitely made for 4.0.2 (it's Faux's 4.0.2 kernel).
With that out of the way, here's my issue: with SetCPU installed, my phone is a slow, laggy mess. When I uninstall the application, my phone is fast, zippy, and all is well. It doesn't make sense given the context. More details below.
Specific things that lag especially bad are the following: 1) very slow screen wake/unlock (without any screen-off profile set/enabled and with the phone at stock min/max CPU frequency and ondemand and interactive governors, and also when underclocked and overclocked and in any combination you can think of); 2) homescreen performance; 3) typing; 4) switching between apps; 5) answering phone calls
I have tried using Setcpu with and without screen off profiles set and enabled, I have tried using the phone at stock clock, overclocked to 1.35ghz, and underclocked to 920mhz, and in all situations and combinations, the phone is slow, jerky, and a bit laggy. I also played with different scaling governors (interactive and ondemand mostly), and had the issue regardless of the governor used. I have not messed with voltage or anything else.
This issue has persisted over three days now, it happens regardless of how many times I've rebooted the phone and uninstalled/reinstalled the SetCPU application, etc. In short, there seems to be nothing I'm doing wrong on my end (or so I think) to explain this issue. And every single time I uninstall SetCPU, my phone is a speed demon again.
I have never had this issue on any previously rooted phone using Setcpu. Also, yes, I wiped cache AND dalvik cache before flashing Faux's kernel. I am not new to Android, cell phones, rooting, flashing kernels, etc. I can even use ADB without problems.
So, hopefully I covered all my bases. Anyone have any thoughts on why I might have been experiencing this issue?
hey,
i've just done some kernal updates (infinityPLAY) and (Jacobs). I installed the infinity kernal...all seemed fine, smooth running, better oc capabilities, better signal (i think)
then to test which one was better, i installed jacobs kernal, which brought up a few issues, mainly a crashing phone.
It now crashes when ever i try to open applications or settings and I get a FC i've never seen before to do with the hotmail app.
I've restored a previous nandroid and reverted back to infinityplay to no avail.
The phone freezes up about 30 seconds into any app then reboots.
havent tried to reflash ROM yet, will do this after work, then restore nandroid again and see if this works......
Any other ideas?
Have you tried lowering the CPU limit ?
UTID
yeah that was one thing on jacobs kernal the settings were UC 19MHz and OC 768MHz and not changable. Now i've reverted back to infinityplay, i cant get into settings because the phone crashes before the settings load so i dont know what my settings are. I've been running at 658-691 on the CM7 nfinity kernal since xmas with no issues
the only other thing i've done recently is installed launcher pro (paid version)
Not sure then sorry,maybe do the fresh Rom like you said.
UTID
Sorted. OC was still at 768 was eventually let me into CPU settings without crashing. Persistence paid off. Back at 652 now...looking better. ill increase to 691 on the morrow.
I notice that whenever I play music (Pandora or Google Music) with the screen off and a bunch of recent applications, the sound will skip and stutter. This only happens when the screen is off AND when I have a bunch of recent applications open. It sounds like an issue with how JB is handling RAM, but I have 80-90% ram usage at most when it happens; or perhaps is an issue with the wakelock under heavy RAM usage. If I clear all the recent applications by holding the home button down and clicking the trash icon, this problem goes away.
Phone Info:
- Teshxx's stock T-889 rom odexed (03-05-13) 4.1.2
- Baseband T889UVALK8
- Model: GT-N7105 (I could rename to T-889 but I believe this is relevant to the issue)
Attempts to resolve:
- Wiped dalvik cache and regular cache
- Installing newer versions of Teshxx's stock odexed rom
- Wiped app data from Google Music and Pandora
Potentially related:
- I deleted the stock music player and musicFX app
- I deleted some other miscellaneous apps
- I have some tasker profiles that address both Pandora and Google Music (one is a trigger to open Pandora, the other is to increase volume of Google Music)
- I have not tried and would like to avoid doing a full system wipe
Im completely stock and listen to pandora several hours a day. Usually while driving to and from work.
No issues for me.
Could be an issue with your ROM.
IAmSixNine said:
Im completely stock and listen to pandora several hours a day. Usually while driving to and from work.
No issues for me.
Could be an issue with your ROM.
Click to expand...
Click to collapse
Do you usually have the screen off and have a bunch of recent apps?
Same happens to me with LG O3D in every music player (only while screen off). Even If I Use only 70 % of ram
Sent from my LG-P920 using xda app-developers app
Jinra321 said:
Do you usually have the screen off and have a bunch of recent apps?
Click to expand...
Click to collapse
Screen is off when im driving.
Ive gone days with out rebooting my phone, and i dont go in and stop them. So yes recent apps has what ever has been opened in between reboots.
Probably a ROM issue. I am back onto stock with my gs3 (Waiting on note 2) and have never had those issues. O have had them on different ROMS though.
I can have tons of apps open and screen off and no issues on stock. Shouldn't be a RAM issue either as 2G is plenty.
Sent from a galaxy far away!
I encountered a simular problem on my Samsung infuse tracked it down to cpu throttling I'd check governer and scheduler may be some screen off power save bias built in to rom maybe
Sent from my SGH-T889 using xda app-developers app
SIGMAxB said:
I encountered a simular problem on my Samsung infuse tracked it down to cpu throttling I'd check governer and scheduler may be some screen off power save bias built in to rom maybe
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
I do believe it may be related to CPU throttling as well. I do not have powersaving enabled and also do not have have any governing apps. I have better battery stats to track my CPU speeds and battery stuff, but I'm not sure how to set governing without an app.
Jinra321 said:
I do believe it may be related to CPU throttling as well. I do not have powersaving enabled and also do not have have any governing apps. I have better battery stats to track my CPU speeds and battery stuff, but I'm not sure how to set governing without an app.
Click to expand...
Click to collapse
With a script
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Are you using voodoo sound?
Could be ROM, kernel, CPU settings, etc. This happened to me last week with the CM nightlies. I installed an update & my music started stuttering like crazy when the screen was off. Turns out I had the CPU settings customized for a special kernel but hadn't reinstalled that kernel, so the phone was trying to manage the stock CM kernel with settings for the custom kernel.
This used to happen to me before I switched to Perseus kernel. Since then I don't have the issue. Could you try that?
Sent from my SGH-T889 using xda app-developers app
I tried doing a full wipe and installed teshxx's N7105 t-mo rom (4/09/13) and did not use any throttling apps (everything else stock). The music was still skipping with the screen off, but I tried setting my minimum CPU speed to 400mhz (from 200mhz) and the skipping stopped (300mhz still skips). So I'm positive it's a problem with CPU throttling now. Since it's a full wipe and I'm still having this issue, I feel that it's a hardware issue. Perhaps I should just warranty my phone.
Changed governor to on demand and all is good.
Music skipping when screen turns off
Hey guys, I didn't realize how many other people were having this problem too....
My phone is rooted and I used ROM Toolbox Pro to turn up the min CPU value from 200mhz to 400mhz and it seems to work so far. So if you can find any type of app that can up your minimum value on your CPU it might do the trick. Because that stutter is super annoying....
I will keep you guys up to date if this doesn't work. But so far so good.
I noticed the same thing on my note 10.1 tab. Fully stock, first day i got it it did that with Google play music. Only noticed it that one time though. I'll report back if it happens again.
As the title says, I have this problem where the big cluster frequency stays at 2361MHz and doesn't drop down to its idle frequency. It occasionally goes down to about 2000MHz, but rises back to its max frequency within a second.
I tried clean flashing OOS 5.0.3 (zip from OP website), I'm not rooted, no custom kernel (all stock basically). It seems to happen after a few hours and not as soon as the device is turned on.
I'm wondering if it's a kernel problem/bug or something else (play services for example). I'd really like to know if anyone else experienced it and if anyone got it fixed.
are you using a custom kernel or root?
if so download elementalx or any kernel editing tool and change the cluster back to 300mhz
i find i have to do this for the cluster to scale back down
You can try New Kernel by @jgcaap.
It's probably the best kernel for this phone with amazing performance/smoothness/battery.
In the latest build the idle freqs are back to normal after OnePlus mess/faulty optimisation in OB2.
https://forum.xda-developers.com/oneplus-5t/development/newkernel-t3710363
If your CPU doesn't idle it can also be an app running in background and hogging cpu time.