Well yesterday I updated my GN using CWM from 4.0.4 to 4.1.1 takju.
This morning I rooted and flashed TWRP wiped cache and dalvik cache and flashed franco.kernel r217 512GPU
every time phone reboots does not turn on and start a boot loop.
I did a battery pull and now is runing but it rebooted 3 times before started properly
Is this an issue of my phone or with the kernel?
I do hope you can help me...
I'm new in this kind of topics
Regards
Using #217-384mhz gpu, no looping or random reboots. Do you have any kind of uv set on boot?
Flashed from cwm 6.x
Sent from my i9250
Do a full wipe in recovery instead of only cache & dalvik... Running franco myself and no issues here with 4.1.1
Have you tried re downloading the kernel and reflashing?
Sent from my Galaxy Nexus using Tapatalk 2
bk201doesntexist said:
Using #217-384mhz gpu, no looping or random reboots. Do you have any kind of uv set on boot?
Flashed from cwm 6.x
Sent from my i9250
Click to expand...
Click to collapse
I downloaded r217 384GPU flashed and now works properly
Gunthy` said:
Do a full wipe in recovery instead of only cache & dalvik... Running franco myself and no issues here with 4.1.1
Click to expand...
Click to collapse
Mmm but it's the 512GPU version?
theoreticaljerk said:
Have you tried re downloading the kernel and reflashing?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
No but i will
Thanks everyone for your help
gowmimx said:
Mmm but it's the 512GPU version?
Click to expand...
Click to collapse
Some devices can't bear it, others can.
Sent from my i9250
gowmimx said:
Mmm but it's the 512GPU version?
Click to expand...
Click to collapse
No, I'm running the 384Mhz now, but I did first try out the 512Mhz version. Worked fine except it drains the battery a lot faster. Since I don't use my GN for gaming or other GPU intensive tasks I don't really need the higher speed one .
Related
I have a big problem. Today I installed a new rom (CM7) new radio and ril (the newest one) and recalibrated the battery.
Since then I have a really high battery drain (about 200-400 just on homescreen) and my phone gets really hot.
Does anybody know what to do?
thx for your help
Sent from my Desire HD using XDA App
Hi Lord_Schrotty
Did you flash CM7 with the recommended CWM version? Flashing using a not recommended can cause such issue.
In addition, did you do a full wipe before flashing?
superstick1 said:
Hi Lord_Schrotty
Did you flash CM7 with the recommended CWM version? Flashing using a not recommended can cause such issue.
In addition, did you do a full wipe before flashing?
Click to expand...
Click to collapse
yes did a full wipe, and i flashed it with the newest cwm version
Lord_Schrotty said:
yes did a full wipe, and i flashed it with the newest cwm version
Click to expand...
Click to collapse
has you got the cm7.0.0 or 7.0.2?
7.0.2 has very very better bat. drain... if all goes well...
are you overclocking the proccessor?
SERGI.3210 said:
has you got the cm7.0.0 or 7.0.2?
7.0.2 has very very better bat. drain... if all goes well...
are you overclocking the proccessor?
Click to expand...
Click to collapse
i'm on 7.0.2 overclocked to 1.3 ghz with lordmod kernal 4.6
Lord_Schrotty said:
i'm on 7.0.2 overclocked to 1.3 ghz with lordmod kernal 4.6
Click to expand...
Click to collapse
1.3 ghz is not soo much...
when i was tried CM7.0.2 i was staid with his stock kernel... my batt drain was well...
maybe you should re-flash the rom... you did this when flashed?:::
1-full wipe (fact. reset, cache and dalvik)
2-all formats (in mounts & storage paragraph)but NO FORMAT SD-CARD
3-FLASH cm7.0.2 and reboot the phone...
4-THEN GO BACK TO cwm and wipe battery status... reboot again
5- turn to cwm AND FLASH THE KERNEL
5-reboot & try
It is exactly what I would do
Lord_Schrotty said:
i'm on 7.0.2 overclocked to 1.3 ghz with lordmod kernal 4.6
Click to expand...
Click to collapse
To rule it out as the issue, drop max clock to 1GHz and see if that helps. They will get warmer running at higher clocks (that's why my PC has a HUUUOOOWWWWGGE heat sink and fans!).
[EDIT] Sorry Sergi, jumped on this before seeing your reply. Have a free "thanks".
Mr_JMM said:
To rule it out as the issue, drop max clock to 1GHz and see if that helps. They will get warmer running at higher clocks (that's why my PC has a HUUUOOOWWWWGGE heat sink and fans!).
[EDIT] Sorry Sergi, jumped on this before seeing your reply. Have a free "thanks".
Click to expand...
Click to collapse
don´t worry buddy your posts always are soo useful!
thank´s for your thank´s LOL
SERGI.3210 said:
1.3 ghz is not soo much...
when i was tried CM7.0.2 i was staid with his stock kernel... my batt drain was well...
maybe you should re-flash the rom... you did this when flashed?:::
1-full wipe (fact. reset, cache and dalvik)
2-all formats (in mounts & storage paragraph)but NO FORMAT SD-CARD
3-FLASH cm7.0.2 and reboot the phone...
4-THEN GO BACK TO cwm and wipe battery status... reboot again
5- turn to cwm AND FLASH THE KERNEL
5-reboot & try
It is exactly what I would do
Click to expand...
Click to collapse
that's exactly what i did
i think i'll flash another radio tomorrow, maybe that was the problem.
Lord_Schrotty said:
that's exactly what i did
i think i'll flash another radio tomorrow, maybe that was the problem.
Click to expand...
Click to collapse
Sorry but could you lower the clock speed to see if it helps.
You have to be mindful that not all CPU's are made equal. Some aren't as good as others and it really is pot luck.
Try changing voltages if am option on your Kernel
Lord_Schrotty said:
that's exactly what i did
i think i'll flash another radio tomorrow, maybe that was the problem.
Click to expand...
Click to collapse
SOO strange... please post your results here when you flash a new radio...for to learn
but i continue believing that you will end reflashing the rom.. maybe something went out badly...
SERGI.3210 said:
SOO strange... please post your results here when you flash a new radio...for to learn
but i continue believing that you will end reflashing the rom.. maybe something went out badly...
Click to expand...
Click to collapse
ok tomorrow i'll flash a new radio and reflash the rom. hope it will fix it
i reflashed now the newest radio, after that i wiped everything out and flashed rcmix hd rom, because of the official gingerbread coming. i hope it works now. i'll post my experience in a few hours.
Lord_Schrotty said:
i reflashed now the newest radio, after that i wiped everything out and flashed rcmix hd rom, because of the official gingerbread coming. i hope it works now. i'll post my experience in a few hours.
Click to expand...
Click to collapse
okay man...
one question? what´s the baseband version that you are using now exactly?
Has anyone downgraded from CM7.2 to CM7.1? For some reason CM7.1 seems much more stable on my phone. Is downgrading as easy as upgrading?
Nytmarez said:
Has anyone downgraded from CM7.2 to CM7.1? For some reason CM7.1 seems much more stable on my phone. Is downgrading as easy as upgrading?
Click to expand...
Click to collapse
You need to install a stock rom, flash clockworkmod, then flash cm7.1.
But you can make a backup, wipe data cache and dalvik and flash cm7.1, without stock rom flashed..
But why would you?
I think 7.2 is better..
Sent from my GT-S5660 using xda premium
Well, I tried 7.2 on my phone and it is not as stable as 7.1 for me. I am constantly having problems connecting to my home wifi network (have to enable/disable the wifi adapter a couple of times), phone restarts from time to time for no reason, unlock screen blinks one time before it t actually appears on screen and some other minor issues. Didn't have any of these issues with CM 7.1 so I think of going back to it. I'll probably go go for the wipe cache/dalvik solution in that case. Thanks for your reply.
Sent from my GT-S5660 using Tapatalk
Did you patch CM 7.2 with patch 4? The patch fixes most of the things and the rom is the most stable for me.
Yes, I did. Did I need to wipe something before or after applying it?
Sent from my GT-S5660 using Tapatalk
Update: I've just tried to wipe the cache partition plus the dalvik cache and it seems that most of the problems are gone now. I would recommend doing this to anyone with the same issues as mine.
Sent from my GT-S5660 using Tapatalk
You always have to wipe the cache/factory reset and dalvik cache before installing a new rom otherwise problems will obviously occur.
Glad that you solved the problem. If you still face some problems then wipe the cache/factory reset and the dalvik cache and flash the rom again with patch 4 and gapps.
I use stock rom, better than CM7.2/7.1. No lags in games, no screen flicker, no f****n problems. Same performance and better battery life.
LegoGabi said:
I use stock rom, better than CM7.2/7.1. No lags in games, no screen flicker, no f****n problems. Same performance and better battery life.
Click to expand...
Click to collapse
Stock rom with custom kernel??
Sent from my GT-S5660 using xda premium
Nope, just stock rom with root and some stock apps deleted, that's all. Maybe i will flash the kernel for stock roms, maybe.
LegoGabi said:
Nope, just stock rom with root and some stock apps deleted, that's all. Maybe i will flash the kernel for stock roms, maybe.
Click to expand...
Click to collapse
What benchmark results do you get with the stock ROM (either Quadrant or Antutu)?
Sent from my GT-S5660 using Tapatalk
Nytmarez said:
Has anyone downgraded from CM7.2 to CM7.1? For some reason CM7.1 seems much more stable on my phone. Is downgrading as easy as upgrading?
Click to expand...
Click to collapse
Assuming you really want to downgrade to CM7.1 I think you can format /system, /data and such from CWM, then apply CM7.1 zip file. No need to install stock ROM first.
BTW I saw in CM-related instructions that when you have some problem with CM that you don't know how to fix try first doing wipe, usually that helps. It seems it helps in your case as well
Yeah, that's right
Dude, leave the f***in benchmarks, my phone is faster in games. With CM 7.2 last time my result in quadrant was 2600, but it was bulls**t cause i had lag in games.
Yup, I also find benchmarks are useful for bragging only. They almost never tell anything real about phone performance in a real application.
So you have to try different ROMs to find the one that would suit you.
Well, I guess it depends on what one uses his phone for I don't play any games and my phone is definitely faster with CM7.2. But as JustVass said everyone has to find the one that best suits him
Please help, I installed ROM - Jellybean JRN84D 4.1: Rooted Stock Deodexed busybox - v2
When an incoming call display does not respond to me and I can not answer the phone.
I tried to phone back to factory settings, but always with me after a while the problem occurs again.
Thank you in advance for your help.
zek9
Flash other Radio Baseband and use stock Kernel, if this does not work then flash back ICS.
Edit: Did you wiped cache and dalvik cache when you flashed JB?
Yes, I did wipe Dalvik cache and cache and still the problem appeared again.
manumanfred said:
Flash other Radio Baseband and use stock Kernel, if this does not work then flash back ICS.
Edit: Did you wiped cache and dalvik cache when you flashed JB?
Click to expand...
Click to collapse
The question is not if Dalvik and cache was wiped but if you did a full wipe when flashing jb rom?
Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
eqjunkie829 said:
The question is not if Dalvik and cache was wiped but if you did a full wipe when flashing jb rom?
Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
Yes, I have used before installing I superwipe.
same problem
Mine started doing the same thing after no problems for few days. Did wipe and all that. I'm thinking it might be app related. The ones I installed right before I noticed this are
Automateit pro
Lux
Set CPU
intenselyinsane said:
Mine started doing the same thing after no problems for few days. Did wipe and all that. I'm thinking it might be app related. The ones I installed right before I noticed this are
Automateit pro
Lux
Set CPU
Click to expand...
Click to collapse
Thank you very much, after uninstalling apk Lux problem is removed
Zek
Hey fellow gnex community! I recently left stock rom due to freezes and random reboots. I've tried out various rom and kernel combinations this week such as xylon/AK, Purity/AK, AOKP/franco/lean, CM10.1/trinity/franco, Rasbean/trinity, PA/lean/franco/trinity/AK and Xenon.
The problem is they all freeze and reboot constantly after 2 minutes of use. I never changed the kernel settings and this is only happening on 4.2.1 roms. My favorite rom/kernel combo would be purity/AK, Xylon/AK but they freeze, wifi disconnects and never connects back and reboots constantly.
So the question is why is this happening to my phone recently and are there specific kernel settings that will stabilize the roms or is it just my phone?
Any help would be great,
thanks.
I haven't had that problem before, and I have flashed several roms (though not a custom kernel in a while)
Faulty hardware perhaps?
Sent from my Transformer Pad TF300T using Tapatalk HD
Lord Yurij said:
I haven't had that problem before, and I have flashed several roms (though not a custom kernel in a while)
Faulty hardware perhaps?
Sent from my Transformer Pad TF300T using Tapatalk HD
Click to expand...
Click to collapse
but this never happened on 4.1, 4.0.4 etc. That's what's worrying me.
4.2.1 isn't exactly highly regarded for its stability....
I reccomend going back to a good 4.1.2 rom. You aret missing anything anyway
nav200 said:
but this never happened on 4.1, 4.0.4 etc. That's what's worrying me.
Click to expand...
Click to collapse
I would do a full wipe and fastboot flash the stock images from Google to see if this helps. Mind you, your internal memory will be wiped so back up all of your photos etc..
crixley said:
4.2.1 isn't exactly highly regarded for its stability....
I reccomend going back to a good 4.1.2 rom. You aret missing anything anyway
Click to expand...
Click to collapse
but I heard people change the kernel settings and the phone will become smoother/stable? I really love some of the features from 4.2.1 that's the reason I'm a bit hesitant to go back to 4.1.2
Try a full wipe, and fast boot a stock image on and proceed from there.
Sent from my A100 using xda app-developers app
plznote said:
Try a full wipe, and fast boot a stock image on and proceed from there.
Sent from my A100 using xda app-developers app
Click to expand...
Click to collapse
I've done that twice already and usually wipe after it freezes but then still happens
Are you sure you know how to flash? Not trying to offend but it saves a lot of time if your a noob.
I currently wipe dalvik cache 3x, cache 3x, and factory reset 3x in twrp. I read somewhere its safer to wipe like this or use super wipe scripts or w.e
I am running the latest rasbeanjelly with latest rasbean gapps and latest lean kernel. I haven't had any resets and haven't tweak anything. May I also add that when I do get errors with roms normally when I flash extra mods I always go back to recovery and hit fix permissions. Idk why but it does solve some issues.
Good luck
Sent from a slice of Galaxy Nexus with some Rasbean Jelly!
lol. Ya I've been flashing roms for like a year and it's only recently these issues are popping up. I do pretty much what everyone does - wipe data, wipe cache, wipe dalvik, flash rom, flash gapps and flash kernel. I never use mods so nothing to worry about there.
Try flashing rom and gapps only without a custom kernel.
If you've fully formatted your drive, have updated recovery, and are positive you have good downloads then your problem is most likely hardware related
Try the kernel cleaner script before flashing/changing between kernels.
It's a cwm flashable .zip.
Alright will do as suggested
How about fastboot flashing the stock rom's .img-es? (Galaxy Nexus ToolKit is the easiest way to do it)
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Alright so it seems like the rom HumberOS with built in kernel did the job. Been using the phone for about 4 hours non stop and no freezes or reboots so far. Finally something stable for my phone! Thanks for the help everyone!
update: After a day without any hiccups on the humber os rom, my phone finally froze and rebooted. Since I was using cwm, I decided to see if twrp would solve the problem. I restored my phone to stock and started from scratch by installing twrp. Then I decided to give PA a try and to my surprise no reboots or freezes at all but will have to wait a day to confirm.
nav200 said:
update: After a day without any hiccups on the humber os rom, my phone finally froze and rebooted. Since I was using cwm, I decided to see if twrp would solve the problem. I restored my phone to stock and started from scratch by installing twrp. Then I decided to give PA a try and to my surprise no reboots or freezes at all but will have to wait a day to confirm.
Click to expand...
Click to collapse
You did restore the factory images by running the update script included in the package right? This will make sure all data is up to date.. Fastboot erase all partitions first as well..
Sdobron said:
You did restore the factory images by running the update script included in the package right? This will make sure all data is up to date.. Fastboot erase all partitions first as well..
Click to expand...
Click to collapse
yup did all that and everything seems to be going fine so far
So... what would be causing the problem you think?
You installed TWRP and PA both at the same as I can read in the previous posts?
So that way we will never know if it's a recovery problem, or ROM problem...
Well, as long as your device doesn't freeze and/or reboot we should be happy I guess.
I had just installed this kernel http://forum.xda-developers.com/showthread.php?t=2139055
After I installed the kernel I rebooted and then I get this black screen and it has been stuck for about 15+ minutes now. Whats funny is when I touch the screen the menu buttons illuminate, and I can hear the touch sounds, of my phone.
-Thanks for any help
Most likely have a ROM that is incompatible with that kernel. I flashed this to with milestone 1 of AOKP. Had to redo everything. Factory wipe and restore your last nandroid.
Sent from my SGH-I747 using xda premium
thegodsquirrel said:
Most likely have a ROM that is incompatible with that kernel. I flashed this to with milestone 1 of AOKP. Had to redo everything. Factory wipe and restore your last nandroid.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
Does cyanogenmod 10.1 m3 work with this kernel?? I may switch back.
just boot into recovery, wipe cache, flash the rom you're running, flash gapps, reboot. eat cake
xBeerdroiDx said:
just boot into recovery, wipe cache, flash the rom you're running, flash gapps, reboot. eat cake
Click to expand...
Click to collapse
Thats what i did to fix the problem, but dang i really want that kernel so bad.
galaxys3world said:
Thats what i did to fix the problem, but dang i really want that kerneld.
Click to expand...
Click to collapse
What is you're ROMs release date and kernel version? Locate and download the BMS release with similar details.