I have an issue with any custom ROM's I've tried, when the phone sleeps my cell radio turns off and I cant receive phone calls, sms's and the like.. The service comes back after a minute of having the screen on, but its a real hassle. I dont have this issue with either of the stock roms, both 4.0.1 and 4.0.2 but anything custom causes me issues.. I wipe data, cache and dalvik and take care not to install any apps and the issue still arises.. I noticed there are a few other people having similar issues, but unlike them I do not have to reboot to get my cell radio working and its not just data, I have also tried the gamut of radio's but I am hesitant to flash radios constantly since my understanding is flashing them has a greater risk to brick your phone should something happen. Does anyone know anything I could try? I dont understand how custom roms all do this but a stock one wont..
set minimum CPU frequency to 700 mhz.
also try other radios (UGLA4 works very well)... flashing a radio won't brick your phone as long as its for your phone.. which in this case, just dont flash I515 radios (verizon)
what rom? kernel?
yannisthegreek has a thread about this; not uncommon by the sounds of it.
Purely conjecture on my part, but I think it's a power issue, i.e. your phone isn't supplying the radio with enough power to kick start it from sleep. Basing this on the fact that a particular kernel (Fugo IIRC?) or upping your min freq to 700 seems to fix the issue. I've yet to experience this however.
I'm going to try setting it to 700mhz right now, I've flashed CM9, Modaco, Codename Android, Revolution, used the Kernel that was provided with those ROMS and Franco's and Trinity, I have also tried every radio as well with the same results.. it does make sense the way mudferret explained it and also explains why it will start up after my phones out of sleep mode and running faster, the weird thing is that this just happened one day, my phone was fine running a custom rom and Franco's kernel and then one day I notice that I had calls going right to voice mail..
So glad I found this thread. I've been dealing with the same issue. People tell me when they try to call they get a fast busy signal. If I wake my phone for about a minute everything works again. I am going to try Fugo IIRC? kernel and see what that does.
Looks like setting my kernel to 700mhz did the trick.. using Franco Kernel and Modaco custom rom, this was driving me nuts.. I'm a happy camper now, thanks for the help guys..
flindil said:
Looks like setting my kernel to 700mhz did the trick.. using Franco Kernel and Modaco custom rom, this was driving me nuts.. I'm a happy camper now, thanks for the help guys..
Click to expand...
Click to collapse
Glad to see it up and running. I never had this problem but I always had my minimum frequency set to 700 MHz because I think I heard franco say something about it helps battery blah blah blah... it was a while back but I don't remember the full details
Yeah, I read that he said the difference on battery use was negligible.. that could have been why custom ROMS and kernels were working for me previously.
Sent from my Galaxy Nexus using xda premium
I don't believe that setting min freq to 700mhz solves anything that relates to ril.
If you were talking about voltages, that would be another story...
bk201doesntexist said:
I don't believe that setting min freq to 700mhz solves anything that relates to ril.
If you were talking about voltages, that would be another story...
Click to expand...
Click to collapse
What's the voltage differential between the 350 and 700 slots, if any?
Edit: I ask because I can't see my voltages on my current kernel
Have same problem post 4.0.4 update
I started seeing this too after a manual 4.0.4 update to my GSM Nexus. The phone is still stock (and was prior to the flash) with ClockWorkMod the only thing added. Still troubleshooting.
----------------------------------------------------
UPDATE: Noticed that this does not happen while phone is being charged. I've tried playing around with a CPU speed program, but I haven't yet figured out if the settings are taking properly.
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...
Hi
I have permroot and s/off my phone using gfree method and i flashed a kernal
that i downloaded (Cyanogen Kernel v1.3) the kernal allows overclocking upto over 1400 mhz ,at 1094 mhz everything is fine and my phone is stable but as soon as i set the frequency over that using setCPU my phone freezes ,i dont know what i am doing wrong this is the first time i tried overclocking a phone ,i hope i am wrong but i am thinking since every cpu is unique maybe thats the max mine can handle ??? i apprentice any tips, advise , help ,suggestions
Thanks.
i have also tried EZDZ_Godspeed_update03 but using this kernal my phone doesnt even boot up it crashes immediately when i turn my phone on.
bahmanxda said:
Hi
I have permroot and s/off my phone using gfree method and i flashed a kernal
that i downloaded (Cyanogen Kernel v1.3) the kernal allows overclocking upto over 1400 mhz ,at 1094 mhz everything is fine and my phone is stable but as soon as i set the frequency over that using setCPU my phone freezes ,i dont know what i am doing wrong this is the first time i tried overclocking a phone ,i hope i am wrong but i am thinking since every cpu is unique maybe thats the max mine can handle ??? i apprentice any tips, advise , help ,suggestions
Thanks.
i have also tried EZDZ_Godspeed_update03 but using this kernal my phone doesnt even boot up it crashes immediately when i turn my phone on.
Click to expand...
Click to collapse
You might be right. Not every CPU is created equal and since the phone is only supposed to run 800Mhz you can't exactly complain that it "only" does ~1.1ghz
On the other hand a little more juice can make a reluctant CPU run a little faster. I'm not sure how the voltage tables work out for different Kernels but you might want to look in to that. The higher the voltage, the better the chance your OC will work, typically.
That's true, every cpu is unique. But for now, since the kernels are still going through development, I would assume it's perfectly fine that overclocked speeds are still quite unstable
Thanks for the replys i am not really complaining i just wanna make sure that i havnt messed up somewhere i thought the crashing might be happening because i messed something up or maybe it happend to others and its a common problem or there is a fix for it .
Also i would appreciate it if someone could put me in the right direction in regard to changing the voltage.
Sent from my HTC Vision using XDA App
just wipe my original stock sense rom and flashed it with virtuous-vision_froyo_rom-v0.8.0 and applied all the patches but still the same problem
my phone freezes instantly as soon as i change it to just over 1100 mhz
its so strange its very very stable at 1094 mhz hasnt crashed even once.
any ideas?
The current overclock kernel that Flippy has over in Development (1.4) causes my phone to freeze when I'm trying to play Angry Birds. CyanogenMod's kernel runs it at 1.4Ghz, and I'm using an older, more stable version of Flippy's kernel.
bahmanxda said:
just wipe my original stock sense rom and flashed it with virtuous-vision_froyo_rom-v0.8.0 and applied all the patches but still the same problem
my phone freezes instantly as soon as i change it to just over 1100 mhz
its so strange its very very stable at 1094 mhz hasnt crashed even once.
any ideas?
Click to expand...
Click to collapse
It could be simply that your CPU isn't capable of over-clocking that high. Its hard to say as the kernels are still being developed but the ability to overclock a processor can vary greatly from unit to unit...
I have CM 6.1 and the last few days I have been running my phone at 1017 to compare the performance difference against the 1497 and thus far, I haven't really seen a drastic difference... That may change as the Gingerbread based ROMS start to trickle out but for now 1ghz seems like plenty of power.
You could always try a different kernel and see if it yields different results.
bahmanxda said:
Hi
I have permroot and s/off my phone using gfree method and i flashed a kernal
that i downloaded (Cyanogen Kernel v1.3) the kernal allows overclocking upto over 1400 mhz ,at 1094 mhz everything is fine and my phone is stable but as soon as i set the frequency over that using setCPU my phone freezes ,i dont know what i am doing wrong this is the first time i tried overclocking a phone ,i hope i am wrong but i am thinking since every cpu is unique maybe thats the max mine can handle ??? i apprentice any tips, advise , help ,suggestions
Thanks.
i have also tried EZDZ_Godspeed_update03 but using this kernal my phone doesnt even boot up it crashes immediately when i turn my phone on.
Click to expand...
Click to collapse
you should check/edit the overclock scripts..
I found wrong configuration script (650 Mhz using Androidiani OR)
Ok so for the past 2 AOKP builds (the latest nightly and M1 both Jellybean) i have had this weird issue where upon boot, the CPU would be capped at 700Mhz. so i went into ROM control, set it to 1200 and made sure "set on boot" was on.
eventually, even without a reboot, it woud revert back to 700 MHZ. so i checked my other apps that can controll OC/UC. Franko kernal app, and ROM toolbox were both set at 1200 and not set on boot. so ROM control was in charge of the CPU.
yet, no matter what i do, after about 4 hours on use it reverts back to 700 mhz.
this happened on the included Faux kernel and Franko's latest milestone kernel.
anyone else experiencing this? know what causes it?
On CNA and get the same thing. It's horrible because it will lock up my phone.
Bumping Cuz it happened again. This is the most annoying thing I have come across.
Some of these phones are really picky. Try another rom and see if the problem persists.
tgyberg said:
Some of these phones are really picky. Try another rom and see if the problem persists.
Click to expand...
Click to collapse
*whimpering* b...b....but... I.. like this rom...
BTW, I am on CNA with popcorn kernel which is different than the op so I feel like it's a deeper issue.
CNA kangs literally everything from everyone (not saying that in a derogatory sense).
AOKP has this bug as well, and I'm sure it's being worked on on their side...which CNA will then cherry pick.
I had this before,Download nofrills cpu from play store and set the desired freq,your problem will
Be solved.
Sent from my Galaxy Nexus using Tapatalk 2
I've been using CNA 3.5 and had no problem with the max CPU setting to 700Mhz until i started playing around with all of the settings in the start-up tweaks, Kernel controls, color hack presets, and color gamma tuning. I changed all of the settings back to default and have not had the issue since then (18 hours). I have slowly started enabling all of the tweaks one at a time to see what was causing the max CPU to set at 700MHz.
max boot speed to 700mhz is defined in init.tuna.rc, if i recall it correctly.
Sent from my i9250
tried changing the kernel !
I used CNA 3.5 and 3.6.6 Still the same issue.
Tried Trinity Kernel too it did help for sometime but still it reverts back to 700mhz..
Is there any fix yet.... I really Love CNA so i prefer to stay on this rom.
My friend using PARANOID ANDROID has never experienced such an issue.
Hope it is fixed soon
Thanks
I'm having the same issue on CNA 3.6.6. Even when I set it back to 1200mhz it still never goes above 700 mhz.
I'm having the same problem. On CNA 3.8 right now, but have had the same problem on other custom rooted ROMs based off of cm. I finally figured out that it reverts back to 700 MHz during phone calls--or maybe not every phone call, not sure on that part. All my calls recently have bumped it down. At least now I know when it's switching. Just installed the no frills cpu--hopefully that'll help until this bug gets fixed.
Ok I have gsm Gnex with AOKP jelly bean build 1 with Franco kernel overclocked to 1.4 GHz and I am experiencing a random reboot problem starting today around 1 am.
I do have cpu undervolted, but it was undervolted for some time now, but just to make sure, I increased the voltage just in case. No luck.
Next thing I though that might have been a problem is the fact that I dirty flashes the AOKP build 1 from the nightly of AOKP, but I flashed it for a time now and never had that problem until today.
Another thing I changed is that I changed the boot animation from AOKP one to cyanogenmod 10 one. That, I flashed yesterday.
One thing I do like to mention is that I think there might be something to do with SetCPU profiles, because I set the profiles so it underclocks when phone screen is off or if the phone cpu or battery heats up, and one reboot was when I was unlocking the screen and another one was when I was watching youtube, and the third one was when I was playing a game, which heats up my phone. The thing is though, I have set those profiles since day 1 and never have encountered any reboots until today
Can anyone help me? Is it something that I should care about, or something that is temporary? Any recommended actions? I hate factory wiping, so that is the last thing I wanna do. Thanks in advance!
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz
kyokeun1234 said:
Ok I have gsm Gnex with AOKP jelly bean build 1 with Franco kernel overclocked to 1.4 GHz and I am experiencing a random reboot problem starting today around 1 am.
I do have cpu undervolted, but it was undervolted for some time now, but just to make sure, I increased the voltage just in case. No luck.
Next thing I though that might have been a problem is the fact that I dirty flashes the AOKP build 1 from the nightly of AOKP, but I flashed it for a time now and never had that problem until today.
Another thing I changed is that I changed the boot animation from AOKP one to cyanogenmod 10 one. That, I flashed yesterday.
One thing I do like to mention is that I think there might be something to do with SetCPU profiles, because I set the profiles so it underclocks when phone screen is off or if the phone cpu or battery heats up, and one reboot was when I was unlocking the screen and another one was when I was watching youtube, and the third one was when I was playing a game, which heats up my phone. The thing is though, I have set those profiles since day 1 and never have encountered any reboots until today
Can anyone help me? Is it something that I should care about, or something that is temporary? Any recommended actions? I hate factory wiping, so that is the last thing I wanna do. Thanks in advance!
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz
Click to expand...
Click to collapse
Tough one. Myself I'd start off by disabling all OC/undervolt settings & disable SetCPU profiles. If that doesn't resolve the issue, temporarily flash back stock kernel.
Petrovski80 said:
Tough one. Myself I'd start off by disabling all OC/undervolt settings & disable SetCPU profiles. If that doesn't resolve the issue, temporarily flash back stock kernel.
Click to expand...
Click to collapse
For some reason, when I cleared the cache and dalvik, It doesn't seem to reboot anymore. But if it ever happens again, I'll do what you told me
Thanks!
Hi, this happened again today, but I noticed that it isn't a full reboot. (no Google splash screen)
Any ideas?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
I've been having this problem for some time now and let me tell you, it is so god damn annoying.
For some reason at least once a day the phone just constantly reboots by itself in a loop until the battery is pulled out and put back in, then the next day it just does the same old thing.
I know for a fact it is not kernel related because I've tried Franco, AK, and Lean Kernel, all have the same issue.
I've also tried stock rom and Xylon rom.
I turned off SR and the problem is still there, no underclocking no undervolting, completely stock rom/kernel.
Does anyone know how I can fix this? Is this app related?
Any help would be appreciated.
Thanks
I can see how that would be very irritating. There are a lot of possibilities for the cause, but I think the first thing I would do is use Trickster app or equivalent to set my cpu frequency down to about 1000 MHz and see if that makes it stop rebooting for a few days. If so, then you might have a device that can't tolerate a normal level of heat. In that case I'd try to get it replaced, or just live with a lower maximum frequency. Or you could try turning up the voltage for 1200 MHz a little, maybe 10 mV, and see if that makes it stop.
If neither of those worked, I would start looking for a rogue app or leftover script from a previous installation. Try wiping /system as well as cache, dalvik, and factory reset next time you install a ROM.
I guess I figured out the problem.
This only happens if I restart the phone while it is connected to the charger.
Sent from my Galaxy Nexus using Tapatalk 2