Hi guys, I urgently need your help! Yesterday my phone drastically slowed down, I don't know what may have been.
I was using cyanogenmod 10 with Franco kernel (I was testing 512 GPU version). So I tried restoring a backup, but no use, slooooow!
I did all the wipes and reflashed CM10 from scratch, with gapps. Problem still exists! Tried reflashkng Franco Kernel (380 GPU) and still the same. At first I thought I might have fried my GPU, but Franco kernel updater app shows gpu working.
So I think this may require a total wipe (including sdcard) and a stock good image reflash from the gn toolkit.
I'm attaching a log right after boot (which took AGES). It seems to me that something's not right.. by I need HELP!
Thank you guys...
http://db.tt/k3dz0aP9
I am not an expert of reading logs yet so probably another member will help you more regarding that.
It seems you have already done a full wipe and tried installing/flashing again but I am not sure which procedure you followed. So my suggestion is to put on your SD card a ROM and kernel, maybe Trinity just for a change, then do full wipe and install the ROM and the kernel so it will be all fresh with a new kernel as well.
If it is still slow, then download any app that would control the CPU and GPU speed to ensure of their speeds running now.
At worst case, returning to stock should help a lot in determining if it is a software or (hopefully not) hardware problem.
Good Luck
I found out that other people have this problem, so I'm asking in the already open threads. Close this please.
Sent from my Galaxy Nexus
Related
So I had my phone previously overclocked to 1.9ghz back when it was new and hot stuff but then decided to install bacon bits to get my led notification working. Totally overlooked that the bacon bits would replace my OC with the 1.5ghz... I was ok with it since I just want 1Ghz. Shortly after I realized my wifi tether was not working with baconbits and reverted to my previous backup which is pretty much a stock root.
A bit later I attempted to do the kernel flash again and it just sent me to a boot loop. Reverted back again.
Tried OC Neon got a boot loop...
Reverted.
Tried the flippys new zip...boot loop...
Reverted....
Tried new OC neon...Boot loop...
what the sh!t!
Any suggestions I may have overlooked would be greatly appreciated!
Thanks
EDIT: Just noticed that restoring the boot & system only, brings the device to working order... If anyone requires any extra info about what I am running on, I'd be more than happy to share.
bump for some help?
Not sure what is going on here, but how were you overclocked previously? Had you already successfully flashed a custom kernel before or were you running a script. If you were using a script, perhaps it modified a system file that is incompatible with new kernels (causing the boot loop).
On my successful overclocking, I flashed flippys first 1.9ghz kernel using adb.
Well, I'm not sure what could help then. Did you try wiping the cache/dalvik-cache when flashing a new kernel (don't expect it to do anything, but you never know)? Maybe try restoring a backup from before you installed the 1.9GHz kernel just to see if flashing a new kernel works when everything is stock...
Oh, just thought of something that maybe should have been obvious (if it is the cause anyway). Are you using a script or app like SetCPU to overclock? The kernels you are trying do not support 1.9 GHz, so trying to set that at boot with them may cause your boot loop. Try setting your max frequency lower (maybe back to 806 MHz to be safe) before flashing a new kernel to see if that fixes thing...
yeah I'm not using a script or anything right now. I've tried a full wipe and nothing seems to be taking. I'm gonna try to flash the older kernels and see what happens later tonight. Hoping for the best :]
Hey guys,
Just went to reboot my phone, and it is now stuck on the HTC Quietly Brilliant screen.
Any ideas what could be causing this? I am running ARHD 3.3. I had a few problems with it just freezing on the normal HTC screen.
Now it is stuck on the next screen, and it constantly refreshes itself. Really starting to get to me. First phone I have had such major reboot problems with.
Should I send it back for repair you think?
You have got yourself a bootloop. Go to clockworkmod recovery and flash a ROM that does not have OC/UV, it should fix the issue. For example Raidroid Stockify series ROMs should work. Some CPUs cannot handle the tightened CPU voltage values which custom ROMs have.
To get to the recovery, pull your battery out, put it back in and connect charger. Do not touch power button.
jkoljo said:
You have got yourself a bootloop. Go to clockworkmod recovery and flash a ROM that does not have OC/UV, it should fix the issue. For example Raidroid Stockify series ROMs should work. Some CPUs cannot handle the tightened CPU voltage values which custom ROMs have.
To get to the recovery, pull your battery out, put it back in and connect charger. Do not touch power button.
Click to expand...
Click to collapse
Ok thanks. Do you think I should simply ARHD 3.3 again, and then revert to a stock kernel?
Just to add, it doesn't always happen. This is the first time I have rebooted my phone for a day or two, but it does get very frustrating if every reboot you do crashes your entire phone and you need to reinstall the entire thing. Bit annoying! Also, it has only started happening in the past week or two. Before then, everything ran fine.
You can try arhd again for sure. Try to wipe cache and dalvik cache first, then flash the rom. Maybe this will fix your problem.
Otherwise try a fullwipe and flash the rom again.
I don't think that the cpu causes this problem. Should be only a bad flash or incompatibility with your old rom if you didn't wiped before flashing it
Tapatalked with Tapatalk from my Desire HD using Tapatalk.
Unfortunately you cannot use stock kernel with ARHD 3.3, you should ask mike to compile you a custom made EXT3 & stock kernel package. Your another choice is to ask Apache to build a kernel without UV.
Something else might cause this issue, too, so it might not be the voltages.. But usually too low voltages cause problems like this, especially as it hangs only sometimes. That tells us that something in the system is unstable. Try full wipe and reflash the ROM, see if that helps.
jkoljo said:
Unfortunately you cannot use stock kernel with ARHD 3.3, you should ask mike to compile you a custom made EXT3 & stock kernel package. Your another choice is to ask Apache to build a kernel without UV.
Something else might cause this issue, too, so it might not be the voltages.. But usually too low voltages cause problems like this, especially as it hangs only sometimes. That tells us that something in the system is unstable. Try full wipe and reflash the ROM, see if that helps.
Click to expand...
Click to collapse
Cool thanks. I had a problem with Busybox for a while, and managed to fix that (the latest stable version was messing the ROM on reboot).
It might be worth asking Apache to build a kernel without UV for sure, especially as people can have this problem as all CPUs are indeed different
I'm hoping that someone might be able to help me with a problem I'm having with the Franco Kernel. I have a rooted Galaxy Nexus, running on stock Android 4.0.2. I have a bit of experience running various custom ROMs and kernels with a OG Droid and HTC Thunderbolt. Until now, I've been content to run stock ICS on the GNex, along with the stock kernel.
I was impressed with the amount of praise I have recently read (I'm a habitual lurker on a number of Android forums) about the Franco kernel, however, and thought I would give it a go. If it can improve performance and battery life, that is fantastic. So, I bought the franco.Kernel updater from the Market, downloaded the zip file (#15), proceeded to recovery and installed it.
That seemed to all go smoothly. The problem is that when I rebooted, the phone got hung up on the black and white "Google" screen. I know sometimes, it can take a while for the phone to do what it needs to do under the hood before it boots up, but after ten minutes on the "Google" screen I did a battery pull, went straight to recovery and reverted to my latest backup.
I've done some searching for anyone who's had a similar issue, but I can't seem to find what the problem might be. Most likely, I'm simply missing something small but critical to the successful installation of this kernel. I'm hoping someone with more experience than me might recognize what it is I'm doing wrong.
Any patient assistance or advice would be heartily appreciated. Cheers!
I could be wrong, but Franco works for 4.0.3, not 4.0.2.
Which could be precisely the one small thing I am missing. I will check this out. Thanks for the suggestion.
Im using franco 14.4, not yet upgraded because when you flash a new kernel, you have always to wipe everything and i'm lazy now ..
P4p3r1n0 said:
Im using franco 14.4, not yet upgraded because when you flash a new kernel, you have always to wipe everything and i'm lazy now ..
Click to expand...
Click to collapse
Where are you getting this information from?
Not once did I have (nor have other people) wipe everything on kernel updates. You do not have to wipe everything for a kernel flash...
bowsersoulstar said:
Where are you getting this information from?
Not once did I have (nor have other people) wipe everything on kernel updates. You do not have to wipe everything for a kernel flash...
Click to expand...
Click to collapse
cool! thanks! good to know I read a bit everywhere.
I mean, I know how a kernel is, and thinking about it it's true that is not needed to wipe, but if he has some problems he could try this out :/ maybe a fresh installation of everything could be good
I have a Gnex rooted and unlocked - DroidModderX - I'm currently running Android Revolution HD very simple mod, barely has anything changed. This mod is 4.0.2. I have tried installing gummy, AOSP, a bunch of other ones. it always says error installing it. Anybody have any advice. Any way to get my Rogers Gnex to 4.0.3?
Thank you
does the error say something like a word i think its like outset or something (100% sure this is not the word) then alot of numbers after? that happens with mine too, but the rom installs fine.
Do you have the latest Clockwork Recovery Mod installed?
Also are you doing a full wipe before you attempt to flash the ROM?
doublea500 said:
does the error say something like a word i think its like outset or something
Click to expand...
Click to collapse
I have seen it say "offset" when I was using the Codename Android ROM.
I did not wipe my cache and data, I was scared that if I did that and it didn't work... I would have to start over again. Download all my programs. configure
Sometimes it doesn't download any of my programs. I restarted it and installed my old OS three times to get it to download my contacts.
I will see the exact thing it says to me soon. thanks guys
You *must* do a full wipe before going to a 4.0.3 ROM. Since your /system is still there, that is what is causing the issue.
However, use the Backup feature in CWM and you can restore it if anything goes bad.
The wipe will knock out your /system, /cache, and /dalvik but will not touch anything on your SD card which holds you photos, etc.
Wish me luck...
I already did a backup - FULL - in Galaxy Nexus Toolkit.
I'm thinking of going with AOKP M3. Let me know if you have any other suggestions.
I hope that is enough to get my phone back to the way it was...
I would like to change the Kernel too. Do you recommend any? I was thinking about franco kernel.
Thanks guys
Good luck!
I have tried three ROMs now and I greatly prefer AOKP the most. Currently I am on AOKP M3 using Faux's kernel but I was running AOKP M3 with Leankernel 1.9.0 with great results.
My battery drain seems a *little* bit more on Faux's but I have only been running it for one day.
Every kernel I try, the battery life improves over a couple days or more so I am going to let it settle.
I tried doing the change. I wiped everything that you could choose and it still gave me the same error. Didn't do it. I have no idea what the problem is. I have no idea how to get my phone to 4.0.3. F***
How about actually mentioning the error you're seeing as opposed to just winging?
It will work so it has to be something you're doing that's wrong
Apparently I can't post, its the first time I've tried to and I'm sure I can articulate my question better than many so its agrivating i can't ask you and Persieus via the forum.
Here goes. I can get long winded so...
(short version)
d2tmo, cleaned up and TitanBU all apps removed mostly, giving me a spaciaous 50% Internal or so with ExtSD getting full.
Used Mobile Odin Pro to first upgrade the Baseband to current T999UVUENC2.
I was on the MD5 and rocking CM11 m2 forever..., I didn't notice any issues at all after the basband and called girlfriend and clashed with clans abit via wifi I presume.
Then came....
NANDRIOD. 3GB transferred to my EXTSD (I've a stockpile of them, nands that is)
and MOBILE ODIN PRO KT747 with DATA/CACHE and Dalvik all wiped, rebooted into recovery, looked up after unable to find fix permissions, CWM apparently took it out in newest versions as people used it like a placebo. thats that and I reboot. KT splash, CM 11 m2 animation. and ALL is Well, except my WIFI won't come on.
I'm convinced that somewhere in the thread I had read from recent posts of people with similar problems. with an Easy fix...
1)I'm fully prepped with SuperSU1.99, CM11 m6 and next 4 nightly's and nandroids ufff course
2)I don't USE TouchWiz yukk, and having found a .zip of the TW 4.4.2 on my SD along with the 5/13/2014 and the 5/12/2014 AOSP's
Basically I question weather I'm a retard and put the TW on my device and its causing this. (My first ROM flash was a rom for another Phone) embarrassingly enough a long long time ago...lmao SO i have a history of boneheaded mistakes.
How should I go about this? My sincerest Appreciation in advance for your time.
Kernel Version
3.4.89-cyanogenmod-g2a5ecd4-dirty
[email protected]#1
Tue May 13 21:30:31 MST 2014
Is that the AOSP installed?
if so...howcan i fix my wifi then?
Good Day to you sirs,
and Ma'aMs?
Sincerely,
Smashing Atoms
Its 12 o clock here, I'm gonna go drink patiently while I eagerly await the verdict if i'm dumb or not.
Just so I understand your Current State.
You had Flashed the TW 4.4.2 along with KT747 AOSP Kernel. Now everything else worked but no WiFi. Is this right ?
Assuming the above is correct, I bet you got the TW 4.4.2 Rom from Docholiday77's thread. That rom comes with its own version of KT747. So don't flash anything else if that's the Rom you want. So reflash the Rom and then wipe Dalvik+Cache. All will be well.
Now if you do want to go back to CM or you had CM all along, then just Flash the latest CM you have followed by KT747. Don't forget to wipe Dalvik & Cache. All will be well again. Otherwise restore one of your Nandroids.
Perseus71 said:
Just so I understand your Current State.
You had Flashed the TW 4.4.2 along with KT747 AOSP Kernel. Now everything else worked but no WiFi. Is this right ?
Assuming the above is correct, I bet you got the TW 4.4.2 Rom from Docholiday77's thread. That rom comes with its own version of KT747. So don't flash anything else if that's the Rom you want. So reflash the Rom and then wipe Dalvik+Cache. All will be well.
Now if you do want to go back to CM or you had CM all along, then just Flash the latest CM you have followed by KT747. Don't forget to wipe Dalvik & Cache. All will be well again. Otherwise restore one of your Nandroids.
Click to expand...
Click to collapse
yes, I'm not exactly in a rough spot, suppose I would just like to know what went wrong. there is some misccomunication (i get carried away).
Had CM11 m2 installed, made a nand, flashed a kernel, My 64GB ExtSD is almost full, you must imagine an occasional zip here or there not in its place. When flashing I try to leave the bare essentials at root. After apparent successful flash of KT747 which I aquired from ktoonsez's threads. It became apparent quickly that I did not have Wifi enabled. a little reading and a little verifiying. and I found 3 kernels on my root ExtSD, 20140512, 20140513 both AOSP (for CM of course) but I found a 5-13 KT TW in the same directory.
alot of info to describe either
a) I should just start again cause wifi didn't take. (this time I'll flash m2 to m6 cache/data dalvik, restart, kernel)
b)It was caused beacuse I'm running a TWKernel with CM.
either way it raised concern and i felt the need to collaborate. sorry my previous message confusingly had your name in it. I was looking for actives in the thread and was PM them the same message, but at the 2nd person not recieving PM I figured whatever, put it in the Q n' A. My only problem is that I figured the names that i seen the most giving answers weren't going to see my message.
The last time I made a mistake of wrong file for wrong device...It was a bloody chrismas miracle i brought the device back with my lack of knowledge and experience at the time with what i know now to be a simple bootloop, at the time it scared me though.
I kinda got an immediate uh-oh fearful feeling from this too, just seeing the TW kernel in my inventory *scary* I'll let you know how it goes. gonna NAND now., find 8 places to post "Awesome" and then go to the thread and boast my kernel probably fixes my MPDecision logcat errors.
Hoorah
I'd delete the KT747 TW zip file.
Your Point B is correct / Valid.
Follow Point A. Except Do it this way.
Flash CM > Flash KT747 20140513 AOSP > Wipe Dalvik & Cache > Reboot & Profit.
Everything you said is valid and makes sense. Don't beat yourself too much about it. We all do it at one time or another. My name or not, I'd have helped you here. I do know without having 10 Post Score, you can't PM XDA Members. I do encourage this forum rather than PM as that allows others to help or profit from our discussion.
EDIT - If the MPDECISION error repeats after all this, please elaborate on the details.
Perseus71 said:
I'd delete the KT747 TW zip file.
Your Point B is correct / Valid.
Follow Point A. Except Do it this way.
Flash CM > Flash KT747 20140513 AOSP > Wipe Dalvik & Cache > Reboot & Profit.
Everything you said is valid and makes sense. Don't beat yourself too much about it. We all do it at one time or another. My name or not, I'd have helped you here. I do know without having 10 Post Score, you can't PM XDA Members. I do encourage this forum rather than PM as that allows others to help or profit from our discussion.
EDIT - If the MPDECISION error repeats after all this, please elaborate on the details.
Click to expand...
Click to collapse
I sit golden with WIFI access, updated CM and a new Kernel. thanks again. When I peep a logcat here in a bit, I will jump for joy if the MPdecision errors are gone, I wasted so much time and effort troubleshooting that wascawy wabbit. I could be mistaken but I believe i saw in update log for the kernel improved or updated MPdecision. If i feel the need to collaborate on the issue I'm sure you'll see me around those threads real soon.
Thanks again
If you intend to use KT747 Kernel, you HAVE to delete MPDECISION. that file interferes the Kernel's Hotplugging.
Perseus71 said:
If you intend to use KT747 Kernel, you HAVE to delete MPDECISION. that file interferes the Kernel's Hotplugging.
Click to expand...
Click to collapse
That I had no idea, but I'm not surprised. I haven't been able to do a log yet :/ I'm just getting to removing excessively excessive gigs from extSD. I've been extremely patient with my device while it allows TitanBU to hang for seemingly eternity attempting to restore youtube+data.
I think You tube stopped downloading user defined videos while on wifi for offline viewing a lil' while ago...don't know why i need it at all then. Thanks for PRO tip on MP, I'll have to do much more reading on the papers before I yank it, but I'm sure its a worthy cause. MakePoor decisions has fruitlessly occupied my attention long enough!!!
I haven't had to deal with so much restoring/reinstall (due to my mishap) since I went from 10.2rc to 11.
Is the MP Decisions surgery invasive? I'll have to lookup the Hotplug to refresh exactly what its doing. but I know it interferred plenty with my tasker Profile based govorner switcher. effectively the reasoning behind MP coming to my attention to begin with (tasker logs).
The mpdecision file runs in our system as a vendor executable file and it controls the governor for cpu. This file is very important as it defines performance of your cpu1, the file gets executed every time your screen goes off, hence cpu1 control operations are useless because the mpdecision file overwrites the cpu1 governor settings to userspace and ondemand, userspace is the governor when cpu1 is online and ondemand when offline.
The above meddles with the Hotplugging by the Kernel. It will also interfere if you are switching the CPU by Tasker. Since you have Nandroid Backups, I suggest you rename the file to mpdecision.bak. That way it will still be there but just won't be executed.
Now some Food for thougth. KT747 includes several Governors that incorporate Hotplugging. For others you have ability to force Hotplugging.
The point about Hotplugging is that it will disable secondary CPUs when the system is very idle, and enable them again once the system becomes busy. This is achieved by averaging load over multiple sampling periods; if CPUs were online or offlined based on a single sampling period then thrashing will occur.
Within the KTweaker app, you have option of setting several Governer Parameters. (See the link about OverClocking / Undervolting in my signature). This makes Sysfs entries for “hotplug_in_sampling_periods” and for “hotplug_out_sampling_periods” which determine how many consecutive periods get averaged to determine if secondary CPUs should be onlined or offlined. Defaults are 5 periods and 20 periods respectively. Otherwise the standard sysfs entries you might find for “ondemand” and “conservative” governors are there.
Source - Link
If you want to know more about Hotplugging, you will need to read up on how Linux introduced and does Hotplugging of CPU Cores. Here's a link.
http://forum.xda-developers.com/nexus-4/development/guide-android-governors-explained-t2017715