Database Info

[Q] g2x wont run any oc/uv kernels

I have flashed all of the eagles blood Tom's even some other Tom's and they work with the exception. Of the new 1.05 eaglesblood that has Caucasian kernel cooked in. I tried flashing fauxs kernels separately and the only one that works is the stock voltage kernels eveeytime I try to do something that undervolts it wont take when I flash it. Is there any way to fix this or fwt it to work or does my g2x suck? Thanks for any help!

facadewithin said:
I have flashed all of the eagles blood Tom's even some other Tom's and they work with the exception. Of the new 1.05 eaglesblood that has Caucasian kernel cooked in. I tried flashing fauxs kernels separately and the only one that works is the stock voltage kernels eveeytime I try to do something that undervolts it wont take when I flash it. Is there any way to fix this or fwt it to work or does my g2x suck? Thanks for any help!
Click to expand...
Click to collapse
Tom's...... Lol
Caucasian.... Lmao
More info...what rom you got?what kernel?what you trying to uv by?
G2X

facadewithin said:
I have flashed all of the eagles blood Tom's even some other Tom's and they work with the exception. Of the new 1.05 eaglesblood that has Caucasian kernel cooked in. I tried flashing fauxs kernels separately and the only one that works is the stock voltage kernels eveeytime I try to do something that undervolts it wont take when I flash it. Is there any way to fix this or fwt it to work or does my g2x suck? Thanks for any help!
Click to expand...
Click to collapse
umm just turn in your g2x to someone that is qualified to use it.

What is a Caucasian kernel?
That ladies and gentlemen, is signature worthy.
Edit: Forgot to even answer your question amidst all this racial kernel profiling. Your G2x can't handle the OC/UV kernel, nothing you can do about it.

dligon said:
umm just turn in your g2x to someone that is qualified to use it.
Click to expand...
Click to collapse
It's not that he's not qualified. A known issue is that some of the phone's can't support some of the features of other kernels so the phones won't boot. I started a thread about this and Faux chimed in affirming what I thought. It's a fault in the chip. Some can OC/UV, some can't.

Thanks hiko I thought I read something about that but what I don't get now is I flashed the Trinity kernel nd it sees the UV 1.1 in set CPU lol . Ill have to do more testing. As for the Caucasian kernel I blame racist correct lol
Sent from my LG-P999 using XDA App

hiko36 said:
It's not that he's not qualified. A known issue is that some of the phone's can't support some of the features of other kernels so the phones won't boot. I started a thread about this and Faux chimed in affirming what I thought. It's a fault in the chip. Some can OC/UV, some can't.
Click to expand...
Click to collapse
Yup. I have this problem. My broken G2x can run custom kernels on Stock. But my replacement G2x can't even get past the boot screen after flashing one. I can't run EB Froyo, and I can't flash faux's kernel unless it's on a Gingerbread ROM. It's pretty lame.
Sent from my LG-P999 using XDA App

darbear5610 said:
Yup. I have this problem. My broken G2x can run custom kernels on Stock. But my replacement G2x can't even get past the boot screen after flashing one. I can't run EB Froyo, and I can't flash faux's kernel unless it's on a Gingerbread ROM. It's pretty lame.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
yeah i wonder if getting another one would be any better though. im sure if i complain enough i could get a bvetter one, although the screen bleed on mine is actually pretty low compared to what ive seen so i might just hang on to it not sure

facadewithin said:
yeah i wonder if getting another one would be any better though. im sure if i complain enough i could get a bvetter one, although the screen bleed on mine is actually pretty low compared to what ive seen so i might just hang on to it not sure
Click to expand...
Click to collapse
If you get a replacement, nothing says you have to keep it. Feel free to send that one back.
Sent from my HTC Glacier

Dear OP. Wish I could help you. I do want to thank you for the laugh. Nothing personal. The typos made me spit out my coffee. It's been a long morning already, so I appreciate humor where I can find it.
As a couple have already said, not all phones are created equal. One of my phones would not OC and UV at the same time. I was able to hit 1300 stable on mine, but my wife, which has an identical setup, had issues at 1100. Faux released an overclock kernel without the undervolting. Have you tried that?

jcbofkc said:
Dear OP. Wish I could help you. I do want to thank you for the laugh. Nothing personal. The typos made me spit out my coffee. It's been a long morning already, so I appreciate humor where I can find it.
As a couple have already said, not all phones are created equal. One of my phones would not OC and UV at the same time. I was able to hit 1300 stable on mine, but my wife, which has an identical setup, had issues at 1100. Faux released an overclock kernel without the undervolting. Have you tried that?
Click to expand...
Click to collapse
I have not as the overclocking was not as big of an issue as undervolting was for me. I cant get a single of fauxs kernels to run etx/GB/FR thats does oc/uv but the stock one does it just fine thats goes 1.0sv/1.2oc. the whole reason why i am confused though is i flashed morfics trinity kernel thats oc/uv at the same rate 1.1uv/1.5oc and it loads perfectly fine on my phone. Setcpu sees the standard at 1.1ghz max on autodetect, howeer i have not tried overclocking to anything more than that as i do not have any experience with making the textfile for setcpu to overclock it manually. im going to work on this soon but im hoping someones already made and posted this elsewhere on xda =D
PS: im on a computer this time and ill say this is better than my blackberry who decided to autocorrect "heterosexual" in place of "hey" everytime i tried talking to one of my friends but glad its good for laughs lol

I've consistently gotten Morfic to work as well. Faux said that Morfic hasn't released his source so he can't compare notes and see what's causing the issue.

hiko36 said:
I've consistently gotten Morfic to work as well. Faux said that Morfic hasn't released his source so he can't compare notes and see what's causing the issue.
Click to expand...
Click to collapse
i hope he does soon as i would love to try fauxs kernel as i hear more about it than morfics. morfics for now works fanfriggintastic for me though. m g2x ocs to 1400 without any problems at all on morfics however has some stability issues randomly at 1500 and i undervolt it always under 1.1 by 75 and runs perfect. battery life is currently at 60% still after 30hrs of use even after phone calls texts and internet usage. no games or heavy downloads yet though. <3uv and juicedefender

CM7 MR2.5 bat issues

Hello to all you great people! I am not new to this site but I havent posted much or at all. This site is increadible and has taught me a ton about what a droid can do once you know how to use it. Thanks everyone! Anyway I have a question that I would of posted in the CM7 dev thread but I dont have permission since I havent posted much. Is anyone having bat drain issues with the newest build (RC1.1 MR2) using the GB radio 2.5? I have lost over 10% bat life in 25 mins while in airplane mode, no data including wifi and the screen was only on for maybe 2 or 3 mins. It may be a problem on my end but I just wanted to see if anyone else is having an issue with this. Oh and thanks to all you devs for doing all the hard work and dealing with angry wifes or girlfriends! We all appreciate it!

spider366 said:
Hello to all you great people! I am not new to this site but I havent posted much or at all. This site is increadible and has taught me a ton about what a droid can do once you know how to use it. Thanks everyone! Anyway I have a question that I would of posted in the CM7 dev thread but I dont have permission since I havent posted much. Is anyone having bat drain issues with the newest build (RC1.1 MR2) using the GB radio 2.5? I have lost over 10% bat life in 25 mins while in airplane mode, no data including wifi and the screen was only on for maybe 2 or 3 mins. It may be a problem on my end but I just wanted to see if anyone else is having an issue with this. Oh and thanks to all you devs for doing all the hard work and dealing with angry wifes or girlfriends! We all appreciate it!
Click to expand...
Click to collapse
On mr2 it did feel like my battery was draining faster than normal.. with the stock kernel at least. Glad I'm not the only one try switching kernels
Sent from my Incredible using XDA Premium App

I actually had this problem too with the stock kernel, and once I overclocked with the Dream kernel it actually stopped draining my battery, strange.

I did try using Imoseyon's CM7 leankernel but had the same effect. Ill try the dream kernel and report back. Thank guys!!

I'm on my first day with this build of CM7, with MR2.5 and noticed my battery has drained way faster than it did with gingeritis.

Did you try wiping battery stats?
Sent from my ThunderBolt using XDA Premium App

Is there an official name for this kernel, or someplace to get it? I tried a quick Google search for "htc thunderbolt dream kernel", and it didn't bring up anything definite.
I noticed the battery drain too. CM7 7.1.0 RC1 with the MR2.5 radio. It seems to be "cell standby" that's using the highest percentage of the battery. I have it set to CDMA / EvDo auto.

What programs do you have running? Are you overclocked? I an running mr2.5 cm7.1 rc1.1 and still have 22% on 18 hours unplugged. 3 hour screen on, lots of texting, xda browsing, market updates, and an hour of plans vs zombies. On stock kernel, no overclocking. Using interactive governor.
Sent from my ThunderBolt using Tapatalk

I do have things set to run in the background, but they don't even register a high enough percentage in the battery usage to show there. I was not having battery issues with the 7.0.1 RC 6 on MR1 (the last build).

I've tried two of the utkanos kernels (not the OC one), and the dream kernel. On both of the utkanos kernels, I had no data. I tried rebooting several times, switching data on and off, and changing the network mode. No luck. The dream kernel took several minutes, but data finally came on. I haven't used it long enough to comment on any battery life differences between stock CM7 and this.

Running BAMF getting 1 1/2 on battery easy on 2.5
I am currently running the 2.5 on my BAMF sense 3 2.3.2 dream kernal. My battery is lasting very nicely currently. See the post below I have had better times the best was 1 day and 19 hours.
http://webdiyhosting.com/BAMFsense3.jpg
http://webdiyhosting.com/BAMFsense3a.jpg
http://webdiyhosting.com/BAMFsense3b.jpg
Cheers,
Azbobs

Ok so here's the news on my end. With the dream kernel things seem much better! However I was watching my ma usage and it went from 48ma to 240ma something after turning on wifi. Then after turning wifi off it never dropped. I rebooted and things went back to a cool 48ma. I'm guessing my original problem was with the stock kernel. But now that I'm on the new one the phone wont power down the wifi or something and made me burn thru my bat till I rebooted. Any ideas gents? Reboot did fix but that usually kills a good 4 to 10% of my bat everytime. I have next to nothing running in the background too.
Sent from my ThunderBolt using XDA App

Guess I should add that now after reboot I'm around 100 ma usage and steady with wifi on. Maybe a reboot once a day might do the trick till CM is finalized. Was thinking bout trying the mr2 radio stead of 2.5. Anyone know if there's a difference or advantage to either?
Sent from my ThunderBolt using XDA App

I was having trouble until i started using the KangBang kernel, that one seems to be the best for me

[Q] Fix for G2X sleep of death?

The main problem with my G2X is the sleep of death, which happens a lot. I get occasional reboots too, but not too often. I tried flashing EaglesBlood 1.05 and then CM7 nightly (7/6), which I'm on now, and I still get sleeps of death and reboots, with perhaps reduced frequency but still bad. Maybe it's the battery, though I don't have overheating/charging/battery drain issues, so I'm not sure what the problem is and if it's hardware or software. Any advice on what I should do would be appreciated - thanks!

I enabled "stay awake" and flashed faux's oc kernel and haven't had an sod in weeks on the stock rom.

regP said:
I enabled "stay awake" and flashed faux's oc kernel and haven't had an sod in weeks on the stock rom.
Click to expand...
Click to collapse
Wouldn't that drain your battery much faster?
Also, I only seem to get the SOD when the phone is charging overnight, and I have a damn screen off profile set to underclock too, not even the lowest frequencies either so it cant be the freeze that that causes sometimes. Tho when it does and I figure out it is frozen asleep, it is usually hot. Might have to either get new battery or replacement. Tho what seems to heat up the most is the area around the camera, so I don't know if the battery or CPU are to blame.

No. Stay Awake only takes effect when your phone is plugged into a power source. Give it a try. I used to get 1 SOD per day. Since i made those changes I've had none in over a month. I posted the same thing in other SOD related threads but no one seems to care.

Thanks regP - I enabled Stay Awake and it seems to help. I've only had one SoD since. My new theory is that it relates to heat (leaving phone in the sun, running too many apps etc.). I've also noticed I don't get an SoD at work, where I get no reception and it's air-conditioned...might be related.

You also need to flash Faux's OC kernel. Even if you dont OC it gets rid of the faulty 300hz frequency that is believed to be part of the problem. Do that along with stay awake and you should not see any more SOD or reboots.

I've noticed I only ever got SOD when using any different kernel than what's in the original ROM. I have been on CM7 since RC1 and have been updating each nightly since and not touched the kernel and have not had a single SOD since, even when charging overnight. Only when I would try Faux kernel or Trinity kernel I would get SOD's.

I dunno then. completely stock for mean means sod and reboots. gingerbreak leak means sod and reboots. stocks + days kernel and stay awake means no sod or reboots. buddy of mine also cured his problems the same way.

For me stock froyo and gingerbread solves the problem.Initially when there was a call waiting sods used to occur, not in any other situation.I tired latest cm7 nightly with fauxs kernel,MIUI with fauxs kernel (and yes wiped cache , wiped dalvik cache and fix permissions and stay awake) but still sods.Then the stock froyo / gingerbread solves the problem for me.Hope this helps somebody.But my point is can I install the stock kernel with cm7 or MIUI ?.

viraj071 said:
For me stock froyo and gingerbread solves the problem.Initially when there was a call waiting sods used to occur, not in any other situation.I tired latest cm7 nightly with fauxs kernel,MIUI with fauxs kernel (and yes wiped cache , wiped dalvik cache and fix permissions and stay awake) but still sods.Then the stock froyo / gingerbread solves the problem for me.Hope this helps somebody.But my point is can I install the stock kernel with cm7 or MIUI ?.
Click to expand...
Click to collapse
no, miui and cm7 are both built from AOSP code and thus won't work with the stock kernel.

I guess I got lucky... never encounter the SOD or Reboot. Running cm nightly 163... I only update nightly when I notice major change only from change log.
Sent from my LG-P999 using XDA App

regP said:
no, miui and cm7 are both built from AOSP code and thus won't work with the stock kernel.
Click to expand...
Click to collapse
So can you suggest any other kernel I should try to stop the sleep of death ?

I have two G2x - Stock Froyo and kernel, manually restart once per day - no SOD or async reboots. Both G2x did suffer from SOD (with or without heat) and reboots. Manual restarts are not as sexy as 3rd party kernels and roms, but it works.
My wife uses her G2x as an alarm clock - she gets in beds, manually shutsdown the G2x, restarts it, plugs into the charger, and it wakes her up in the morning. EVERY DAY.

viraj071 said:
So can you suggest any other kernel I should try to stop the sleep of death ?
Click to expand...
Click to collapse
my sod issues stopped when I enables "stay awake". never used anything but the included kernel of whatever Tom I decide to use.

What is the best solution for this? Makes me think i wasted good money on getting 2, for me and my girl. I tried that "stay awake" and same, shuts off out of nowhere. Ive flashed both faux kernel, same results. I dont experience it with CM but for me, stock its just more responsive BESIDES the shutoff. And Weapons rom just has too much addons.. Now people are saying that the SGS2 isnt all that because of benchscores.. And i wanted that phone.. But they make it seem like it isbt a big step forward.
Sent from my LG-P999 using Tapatalk

noodles2224 said:
What is the best solution for this? Makes me think i wasted good money on getting 2, for me and my girl. I tried that "stay awake" and same, shuts off out of nowhere. Ive flashed both faux kernel, same results. I dont experience it with CM but for me, stock its just more responsive BESIDES the shutoff. And Weapons rom just has too much addons.. Now people are saying that the SGS2 isnt all that because of benchscores.. And i wanted that phone.. But they make it seem like it isbt a big step forward.
Sent from my LG-P999 using Tapatalk
Click to expand...
Click to collapse
Our phone at 1 ghz has surpassed the gs2 and 1.2 ghz
Sent from my LG-P999 using XDA App

If missing with software and settings dont work you may just have a bad phone.

regP said:
I enabled "stay awake" and flashed faux's oc kernel and haven't had an sod in weeks on the stock rom.
Click to expand...
Click to collapse
Thanks for this. I'll be sure to use the "Thanks" button when i have enough posts. I'd been leaving the phone screen on in my pocket (using an alarm clock app) because it would SOD anytime i used the lock button. Working better already.

I keep on getting SODs ONLY when there is a call waiting in the background and this happens only with CM7,MIUI.When I flash the stock gingerbread or even weapons G2x,EaglesBlood ROM the sods that occur during call waiting vanish. Can anyone help me here ? I tried fauxs kernel along with Stay awake and increasing the minimum CPU frequency but failed. Any help will be appreciated.

For the people that SOD occurs on the charger, try another charger (instead of stock LG charger). I tried the Motorola micro USB charger which put out only 550mA (which came with the H730 bluetooth) and the SOD vanished.
Probably over heating with the LG charger which puts out 1000mA

Shutting Down

Anyone having issues with their Thunderbolt shutting off and the only way to turn it back on is to do a battery pull? I'm rooted running Ginger3DTh3ory 6.2, but it did this also when I was running Bamf 3.0. Any thoughts on how to fix this?

No idea, are you oc'd?
Sent from my TBolt using my f***king thumbs...

Let me describe what mine has done a few times and you tell me if that's what you're talking about. Twice, in the last 2 days, it's just locked up with the screen off. It doesn't respond to power or volume buttons. Only way to get it to work again it to pull that battery.
BUT... the weirdest thing happened the last time. It did it while I was in a call. I could answer with my bluetooth, talk, and hang up with my bluetooth, but the phone wouldn't respond to anything I did to it.
Is this what you're talking about?

Sound like SOD = Sleep of Death. It doesn't happen to much but a pain in the rear...switch Ur govenor from interativex to ondamandx see if that fixes it
Sent from my ADR6400L using XDA App

I've had this problem quite a bit lately with the same roms. I switched to Gingeritis3D beta 6 and the problem seems to have gone away. Gingeritis and some other roms are starting to claim they are using an official build of GB and not the alpha leak version. That could be the issue.

adoublearonn said:
I've had this problem quite a bit lately with the same roms. I switched to Gingeritis3D beta 6 and the problem seems to have gone away. Gingeritis and some other roms are starting to claim they are using an official build of GB and not the alpha leak version. That could be the issue.
Click to expand...
Click to collapse
the official build's kernel is a piece of crap that is leading to a whole new batch of reboots.
OP, that is usually an issue where your phone is not getting enough voltage. I would do what the other poster suggested and switch your governor. It will give the phone a little more juice so it doesn't do that.
All phones are different when it comes to that stuff.

Thanks forvthe responses. I'm not OC'd and I'm not sure where in this rom I can change my governor. Its only happened once with those rom so far, hoping its just a fluke.

Mines running fine. Maybe try reflashing?

jeck77 said:
Thanks forvthe responses. I'm not OC'd and I'm not sure where in this rom I can change my governor. Its only happened once with those rom so far, hoping its just a fluke.
Click to expand...
Click to collapse
you have to open terminal emulator (I think its preinstalled on gingertheory, if not there is a free one in the market).
type su (hit enter), it might drop your keyboard, pressing menu will let you reopen it.
type speedtweak.sh
This will open script fusion, there you can change the governor to ondemandx.

ICS and SoD, going through solutions! Build 1006 phones

Hi!
I have spent a long time testing ROMs, Kernels and modem combination and first of all must say THANK YOU!, all of you are doing a great job with kernels and roms and modems, it really amazing see your old phone working better than brand new.
My investigation with different combination make me go into 1 conclusion, finding the most compatible modem to your phone could prevent most or all SoD problems. I make different test and find that my phone totally lost signal and can't go back until restart the phone (also going to flight mode don't work), the most compatible modem I test the less this bug happen and less SoD.
Still don't know when start this signal bug but is the first problem I could see. Usually happens early in the morning.
PS: I've confirm this with others devices with SoD as well and people are having better results changing modems.
PS2: All cappy test was done on a 2010 build 1006 phone with SoD over 80% battery charge on stock rom (build over 1006 should not experience this problems) stock as possible.
PS3: wake lock app totally prevent SoD, but at the cost of some battery drain when not using the phone, specially at night ( this can be solved just leave the charger plug in )
Hope this could help someone
Best regards to everyone!

rophiroth said:
Hi!
I have spent a long time testing ROMs, Kernels and modem combination and first of all must say THANK YOU!, all of you are doing a great job with kernels and roms, it really amazing see your old phone working better than brand new.
My investigation with different combination make me go into 1 conclusion, finding the most compatible modem to your phone could prevent most or all SoD problems. I make different test and find that when phone lost signal or where without sim card it take just some minutes (even less sometimes) to SoD or just restart, the most compatible modem I test the less SoD.
This probably mean that many of our cappy can't stay on idle while no signal (probably enter on a state similar to deep idle).
People, if you can, please test your cappy with ICS without sim card, put on idle and look if go SoD in less than 10 min.
PS: I've confirm this with others devices with SoD as well and people are having better results changing modems.
PS2: All cappy test was done on a 2010 phone with SoD over 80% battery charge on stock rom
PS3: wake lock app totally prevent SoD, but at the cost of some battery drain when not using the phone, specially at night ( this can be solved just leave the charger plug in )
Hope this could help someone
Best regards to everyone!
Click to expand...
Click to collapse
Deep Idle doesn't work well with Captivate bootloaders and causes SoD. Use Devil with devil idle, or no idles at all because the phone will still sleep. Deep idle only benefits music playing and barely. It's not the kernels, or modems, it is the idle itself. Also, what is the point of running tests without the sim card in, modem tests should be done with the sim card in.
tl;dr: Deep idle never worked well, and should be combined with i9000 boot loaders if you want it to work well.

I don't use deep idle and use i9000 bootloader
Sent from my SGH-I897 using XDA

I always turn on flight mode all night, and never had a SOD
Slim ISC 4.0 + devil 0.71 + devil idle (no Deep Idle)

xtmp said:
I always turn on flight mode all night, and never had a SOD
Slim ISC 4.0 + devil 0.71 + devil idle (no Deep Idle)
Click to expand...
Click to collapse
and without flight mode did SoD?

rophiroth said:
and without flight mode did SoD?
Click to expand...
Click to collapse
no, all fine. Can try without sim, but I think result will be the same.

It's not the modems, SoD depends on the build of the phone, the kernel, the bootloaders etc;

nygfan760 said:
It's not the modems, SoD depends on the build of the phone, the kernel, the bootloaders etc;
Click to expand...
Click to collapse
Not what my experience tells with my phone, different builds and bootloader dont really make any significant change

left my phone more than 1 hour without sim card. No SOD happens.

Some one of you have a 1006 i897 build phone too, because I don't have sod in moderns i897?
Sent from my SGH-I897 using XDA

rophiroth said:
Some one of you have a 1006 i897 build phone too, because I don't have sod in moderns i897?
Sent from my SGH-I897 using XDA
Click to expand...
Click to collapse
No, like I am telling you, the modem doesn't cause SoD. By testing without a sim, you are proving that point to be even more true.

But you tell me you don't have an 1006 he build phone. So as I say this can be a bug with this phone that make random reboot and sod.
Sent from my SGH-I897 using XDA

rophiroth said:
But you tell me you don't have an 1006 he build phone. So as I say this can be a bug with this phone that make random reboot and sod.
Sent from my SGH-I897 using XDA
Click to expand...
Click to collapse
That would be a hardware problem.

nygfan760 said:
That would be a hardware problem.
Click to expand...
Click to collapse
Yea and not at same time, build 1006 as know for been bugged from factory but with new builds of kernels, modem,roms and also many tips I have take over most of the problems that make my phone shutdown. Today my phone was all day on idle and just check now to see if still alive and yes!

Bug post
Sent from my SGH-I897 using XDA

Edit OP for better explication of tests and results

I've install an app called "singal reset" and activate deep idle, mincpu to 100. Actually the phone never goes to didle state(not top on or off huehue) but in all day long my phone dont SoD. Will see what happen this night