There seems to be several people, previously including myself, who were or are having great difficulty flashing either custom kernels or roms that include custom kernel's. Some can't flash anything with a custom kernel in it, while others can flash one or two, but not all. The failed attempts often result in either freezing at or right after the LG screen at boot. I had previously had no trouble on my droid eris with custom kernels, so I found it hard to believe that it was simply due to me not following the correct procedure. Nonetheless, I sought help from various sources, and tried any number of methods to get a kernel to flash correctly. None of these methods worked, and I began to suspect that those of us having difficulties may have a hardware issue. I have since acquired a replacement g2x from t-mobile, and attempted to flash a kernel using the exact same methods I had done in the past. The kernel booted up perfectly, and I am able to flash any kernel I want with relative ease, using the same exact methods that failed on my previous handset.
I'm not going to say that everyone who can't successfully flash a kernel has a hardware issue; there's a good chance some are just incorrectly flashing it. However, if you have read up on the correct process, and are still unable to get a custom kernel to flash, you may be having the same issue I had, in which case you'll need to decide how important custom kernels are for you. If you decide you really need them, you may need to consider swapping your current handset for a new one.
When flashing kernals, the phone may or may not support it due to the chip that's inside. Although everybody has a 1ghz dual core Tegra2 chip, all are not 100% the same. At stock settings everybody's chip will be able to handle the 1ghz, some that could OC to 1.5, maybe even more. Sorta just comes down to if you are lucky enough to get a chip that can handle all the stuff you throw at it.
hukkguai said:
When flashing kernals, the phone may or may not support it due to the chip that's inside. Although everybody has a 1ghz dual core Tegra2 chip, all are not 100% the same. At stock settings everybody's chip will be able to handle the 1ghz, some that could OC to 1.5, maybe even more. Sorta just comes down to if you are lucky enough to get a chip that can handle all the stuff you throw at it.
Click to expand...
Click to collapse
The problem isn't in regards to not being able to handle a higher clockspeed, its in flashing a custom kernel in the first place. Some of the custom kernels and roms still come originally set at the normal clockspeed of 1ghz, yet those suffering from this problem, including myself, are still unable to load them. If it were a problem with the chip just not being able to handle being oc'd, then it should still be able to load, just not be oc'd with whatever program you're using (ie pimpmycpu).
I got a replacement as well, this one flashes correctly.
Odd how we both had the same issues and folks kept insisting it was us not wiping and/or installing these roms and kernels correctly
So the only fix for this issue is doing a replacement?
For me it was. I flashed every possible combo, nothing worked on my old g2x.
Sent from my LG-P999 using Tapatalk
My vote is for hardware issue. I was unable to flash any of the AOSP ROMs or kernels until I got my phone exchanged for the many other problems.
Now I have flashed them with no problem at all.
Still not happy with the phone overall but it's too late to return it.
Related
I'm sure almost all (if not all) of you that have obtained root on your Incredible (which this app requires) know what this app is and possibly have even used it in the past. There doesn't appear to be any Incredible specific modifications made to the app yet, but I just wanted to throw this out there. As always, be VERY careful with overclocking, esp. with this CPU (I personally wouldn't try anything over 1.2ghz). If you feel your phone getting hot, don't keep running it! Also neither the author, XDA or I take any responsibility in the case that you toast your Incredible.
http://www.pokedev.com/setcpu/
I thought we'd need a modded kernel to run it over 1.2 Ghz? How can we do that with just rooting the phone and installing setcpu?
Or I'm way off and I have no idea what I'm thinking lol..
andrew53517 said:
I thought we'd need a modded kernel to run it over 1.2 Ghz? How can we do that with just rooting the phone and installing setcpu?
Or I'm way off and I have no idea what I'm thinking lol..
Click to expand...
Click to collapse
no, you are correct. i have built the kernel (HTC release) w/ the required changes. but have not been able to flash
Wow I wasn't aware of the kernel limits, or maybe I subconsciously read it somewhere since I threw 1.2ghz out there (over the last couple weeks I've been dealing with a cold I can't seem to shake so I blame a combination of insomnia+Nyquil... mmm Nyquil).
Id say its worth some green to get that kernel. I have been looking high and low to find one. seems that the demand is there but not the development. Let me know if you get it up and running and I'll donate to the cause.
Just wish I could develop it at this point, but getting the phone rooted was a task for me. Even with video instructions....
hey guys.. i guess im kinda new with androids but all i have is a question... now the i learned how to flash a rom.. its very cool but why do we need kernels what does it mean? just flashing a rom thats not all there are kernels and other stuff but i dont know what they are and what for
Kernels are the core system. Sort of like drivers. Custom Kernels affect stuff like Overclocking for speed, Undervolting the processor to save battery, GPS locks, WiFi range, etc.
They can increase stability, speed, and battery.
The big thing, I think, that most people sought after is the Overclocking/Undervolting (OC/UV). This overclocks the processor while lowering the power usage of the chip at the same time. So you get a faster phone while saving battery. Brilliant. It is my understanding that custom kernels come with normal settings by default. They only ALLOW overclocking abilities using programs like SetCPU and the likes. I think the voltage is lowered on all speeds though, so flashing an UV rom will save you battery even if running 1ghz stock speed. I've seen people go up to 1.4ghz.
It is best to test a rom first for a few days. Figure out what bugs you encounter, if any. Get a feel for the rom so when you flash a new kernel you can see if it will work for you. If you do too much at once and you encounter bugs it will be hard to pinpoint.
I've flashed custom kernels but don't do it often. I know CM roms have their own custom kernels that I believe are flashed back when flashing the rom. This is why CM7 differs from stock in a lot of ways. One example is stock G2x won't work with Wii remotes. The bluetooth stack in the kernel is a custom LG one and doesn't work. CM uses a more common bluetooth stack so you not only gain this functionality but also others.
The list goes on and on. I think most of the custom kernels are BASED off CM7 and are only compatible with CM7. I think a custom kernel on top of a stock LG rom will cause bootloops. So the kernel and rom have to work together.
I am not an expert but I think I've touched the bases. Someone correct me if anything is untrue or misinformative. Technicalities aside, this is the gist of it.
player911 said:
Kernels are the core system. Sort of like drivers. Custom Kernels affect stuff like Overclocking for speed, Undervolting the processor to save battery, GPS locks, WiFi range, etc.
...<snip>
Click to expand...
Click to collapse
excellent explanation, i've kinda been wondering about all this myself. Thanks!
player911 said:
Kernels are the core system. Sort of like drivers. Custom Kernels affect stuff like Overclocking for speed, Undervolting the processor to save battery, GPS locks, WiFi range, etc.
They can increase stability, speed, and battery.
The big thing, I think, that most people sought after is the Overclocking/Undervolting (OC/UV). This overclocks the processor while lowering the power usage of the chip at the same time. So you get a faster phone while saving battery. Brilliant. It is my understanding that custom kernels come with normal settings by default. They only ALLOW overclocking abilities using programs like SetCPU and the likes. I think the voltage is lowered on all speeds though, so flashing an UV rom will save you battery even if running 1ghz stock speed. I've seen people go up to 1.4ghz.
It is best to test a rom first for a few days. Figure out what bugs you encounter, if any. Get a feel for the rom so when you flash a new kernel you can see if it will work for you. If you do too much at once and you encounter bugs it will be hard to pinpoint.
I've flashed custom kernels but don't do it often. I know CM roms have their own custom kernels that I believe are flashed back when flashing the rom. This is why CM7 differs from stock in a lot of ways. One example is stock G2x won't work with Wii remotes. The bluetooth stack in the kernel is a custom LG one and doesn't work. CM uses a more common bluetooth stack so you not only gain this functionality but also others.
The list goes on and on. I think most of the custom kernels are BASED off CM7 and are only compatible with CM7. I think a custom kernel on top of a stock LG rom will cause bootloops. So the kernel and rom have to work together.
I am not an expert but I think I've touched the bases. Someone correct me if anything is untrue or misinformative. Technicalities aside, this is the gist of it.
Click to expand...
Click to collapse
Ya, thanks for putting the time into explaining. I was wondering the same thing..
Wow that was briliant thank you...
Sent from my LG-P999 using XDA Premium App
Hello,
I am running stock ROM with S-oFF and rooted. Ive got setCPU running via the methods used for temp root. (Basically pulled the code from the BAT files everyone used to overclock and temp root). It works alright, but after a reboot, I have to redo it.
I see people are running ROMs that include setCPU. How does a custom ROM manage to keep setCPU "set" after a reboot? Can the methods be used for the stock ROMers?
Also, I see that setCPU requests SU hundreds of times a day when I look at the SuperUser logs. Why is this? Is it bad?
Thanks,
Matt
They are using custom kernels and oc daemon.
Behold_this said:
They are using custom kernels and oc daemon.
Click to expand...
Click to collapse
thank you for the reply! Is this something that a stock rom could implement in its own? Or, should I consider flashing a custom rom?
Thanks,
Matt
Its a little hit and miss right now unfortunately. The kernels can still be buggy on some devices, though they, in theory, should work on a stock device. If you have issues you can always just flash the stock kernel back. Some love it and have no issues, others not so much. In fact some devs have stopped bundling their kernels with their roms and leave them as optional add ons because of issues.
Is cm7 expected do implement overclocking? If so, I may just wait for them to finish.
Matt
Not sure...they are playing cm7 for the sensation very close to the chest, lol, but I don't think so. Just a guess though.
Behold_this said:
Not sure...they are playing cm7 for the sensation very close to the chest, lol, but I don't think so. Just a guess though.
Click to expand...
Click to collapse
Ahh...I guess that only time will tell what sort of advancements come in the way of overclocking (reliably and efficiently).
My theory is that setCPU is the cause for my headaches and may be the cause of most others using it as well. (Crappy battery despite conservative governors as well as phone freezes and data connectivity issues). Seeing setCPU request SU a few thousand times a day seems suspicious. I have it frozen for now, well see how things go.
Matt
I don't know for sure either, but I suspect you might be right, at least to an extent.
Hello,
FIRST OFF!
This thread is NOT for discussing whether or not benchmarking is useful. If you feel the need to flame me or anyone here for CARING about benchmarks, then go find another thread to piss in! I made this thread to clean up Faux's thread as it was taking over.
Ever since moving to any of the newer CM7 updates, I have noticed extremely low benchmark scores on CF Bench. When on CM7-1 with one of faux's kernels, everything is fine. (Cf Bench = 7000)
When I say low, Im talking 4000 on CF Bench despite OCing to 1.56Ghz. That is far below what the Sensation STOCK is measured at...
Notes:
1-Scores can be all over the place. At one point, I got a 6400. This would immediately become a 5000, and then back to 4000 range.
2-I have tried using three different methods of controlling the clock. (System tuner by 3c and fauxclock, both recommended by faux for his kernels, and then the CM7 performance settings). Fauxclock had the best outcome, but EXTREMELY unstable!
3-I have done NUMEROUS restarts along with cache clearing and dalvik clearing. I even pulled the A-Bomb out and used the superwipe script to start fresh. After the a-bomb, I DL only what I needed to test with...
4-My phone feels laggy, which goes along with the crappy scores.
At this point, I am restoring to my trusty Alpha 1 + faux kernel. While that works, I feel I will wind up getting left behind.
What could cause this? What are some things I may have overlooked? Others DONT have this problem, at all.
Matt
well i will say benchmarking isnt a totally conclusive. although there isnt any other method of tangible scoreing as of yet. However i will say that if your phone is laggy then your benchmarks are a good way to test why.
scoreing varies when you have active apps in the background unknowingly.
also if you flashed a new rom and kept your old kernel that will dramatically reduce your scores. check out some other kernels for your new rom and see if that makes a difference.
try flashing back to stock and deleting the kernel, then flash the CM7 rom without the kernel in your system and run a test.
theres a lot of things that will change your scoreing.
let me know what you get out of this.
rddocke said:
well i will say benchmarking isnt a totally conclusive. although there isnt any other method of tangible scoreing as of yet. However i will say that if your phone is laggy then your benchmarks are a good way to test why.
scoreing varies when you have active apps in the background unknowingly.
also if you flashed a new rom and kept your old kernel that will dramatically reduce your scores. check out some other kernels for your new rom and see if that makes a difference.
try flashing back to stock and deleting the kernel, then flash the CM7 rom without the kernel in your system and run a test.
theres a lot of things that will change your scoreing.
let me know what you get out of this.
Click to expand...
Click to collapse
I came from ARHD with fauxs kernel. I did a superwipe and then flashed cm7-1 and then flashed fauxs kernel. Everything was great until I tried any of the new CM7's...Just tried cm7-6 and got a WHOPPING 3000!!!!!!!!! YAY!!!!!!!!
I knew it would be low, just playing with the phone. I find it so weird that going back to cm7-1 fixes everything.
Either their new updates kill my performance for whatever reason, or going from one cm7 build to another is a no go. (I did a superwipe just to be sure when going from alpha1 to alpha 5).
Damnit.
If it werent for seeing others with good scores, I would blame cm7 or faux's kernel. Its got to be some little quirk with my phone. (And a few others).
Matt
I'm sorry about the long post if you want to get straight to my question, skip the first paragraph
I was avoiding this because it is a fairly noob question set (and I've seen a history of new members on XDA being berated for questions that could have been answered by any amount of research and I'm unsure whether my question set will fall into that category), but I just can't do anymore research since most information I'm finding is not in one place and I can't seem to find a full feature list for any of the ROMs and Kernels I research and look into, and on top of that there are SOOO many.... I'm about to pull my hair out of my head and my skull along with it, and every search engine I use is contemplating homicide (google has divorced me and is planning my murder for the life insurance money, and duck-duck-go is biting my heels with its bill) and firefox is planning a suicide bombing taking the 50 or more tabs with it along with my RAM, and I'm not terribly sure any of those actions aren't justified (and also, as you can probably tell, I'm going NUTS!). Just the amount of information and the amount of digging I have to do to find a single answer for the MANY questions I have regarding these ROMs and Kernels is staggering (I remember having similar problems searching to find the right linux distribution for me, but it wasn't this hard and after 2 or more weeks of searching, I didn't find myself not having any substantial answer, nor did it actually take two weeks)
anyways, enough with the crazy intro to the question
My current phone is a Nexus S 4g (sprint) currently running the stock ROM and Kernel, gingerbread 2.3.7 (build GWK74). I have it rooted and I have clockwork mod recovery flashed as well as ROM manager installed. I'm looking for ROM and Kernel recommendations (and combinations, I want to make sure they're compatible) as well as reasons why they might fit my needs
I need a ROM and Kernel that:
1. Won't reduce any of the current features I have on the Stock ROM/Kernel I have (though I don't use NFC so if google wallet isn't applicable, that's not a loss)
2. Will allow more steps in frequencies on my CPU (so CPUtuner won't tell me it can only go between 100Mhz and 1Ghz when I attempt to manually change the frequency, I can get one governor to get me 400mhz, but that only adds one more step to the 2 current steps, and performance and powersave governors don't work with the stock kernel, not that it's a big deal, I prefer conservative and ondemand)
3. will allow voodoo control & voodoo color (or any other feature that might be useful, though BLN isn't a big deal to me)
4. Has better battery life (while in use, use being things similar to internet browsing) than stock ROM/Kernel (so UI flare isn't completely necessary, and underclocking and/or undervolting would be great, as long as it doesn't sacrifice speed)
5. The UI should be less jittery than I'm seeing the stock react half the time (though that might be an effect of the CPU tuner)
6. I would like overclocking (however if that interferes with battery life, then I can live without it as long as it doesn't make the speed worse than stock)
7. this coincides with #1, but I think it should be said anyways: I don't want any connectivity (besides maybe NFC) to be affected adversely, so I want 4g, 3g (given), wifi, tethering, etc...
a few questions I have that I can't seem to clear up:
1. I'm beginning to develop software for android, so I'm wondering if any ROM and/or Kernel will affect ADB or any connection to my PC at all
2. What advantages do CM7.1 nightlies have over the CM7.1 stable, and any disadvantages (because I would prefer stable unless there's something on the nightlies I might want)
3. And any advantages ICS ports might have to anything listed above? and compatible kernels?
well, I have done some research, and the two ROMs I'm currently considering are Oxygen and CM7.1 (stable). I like Oxygen because it's a barebones rom with a few extra features that (from what I've seen thus far) don't interfere with performance or battery life. I like CM7.1 because it seems to be fairly quick and has a good feature set.
now I know that the performance might be more affected by the kernel than the ROM, so the kernels I've been most interested in are Netarchy and Trinity. Netarchy has decent speeds (though I'm unsure of its effect on battery life) and has a great list of features (such as voodoo control). Trinity is fast (depending on which version, I was debating on the overclocked version that doesn't go to the highest clock setting and the undervolted version which stayed at 1ghz but had great powersaving) because of its speed and/or powersaving, but I'm unsure of all of the features it has)
I had read that CM has its own kernel, but I can't find any substantial evidence to it besides a few short forum posts on various forums. I can't find anything on the CM site that backs up those claims (I could have just missed it though)
I was considering MIUI but I had heard that it had some translation problems from chinese into english and I'm not sure if you can get the text to read from left to right (and be alligned that way). Not sure if that has been fixed and if the features on there are necessary and/or make it difficult to use
I'm asking here because I'm sure I've barely scratched the surface on all of the ROMs and Kernels that might be helpful to me (and hope to get info from more knowledgeable people)
I have been referring to this thread
http://forum.xda-developers.com/showthread.php?t=1067813
I'm sure somethings I want aren't possible or if they are, there's negligible gain (I'm starting to thing that about battery life with the more I read)
once again, I apologize for the extremely long post, as you can tell I'm verbose (as it's really the only way I know how to get my point across)
if you need further information, feel free to ask. If any information needs to be cut off (especially if this needs to be cut shorter) let me know
I hate to do this but
BUMP
my main problem with this is that most of these roms and kernels seem to do the same thing but all have different problems
I've also found that some versions are more buggy then others which has thrown yet another curve ball into my research (not as bad as ICS but bad enough). I should have expected it but it's just one more thing to go digging for
an answer at all would be nice, other than just the views with no post. Even if the next person's answer is "this is stupid" or something of the like
even that would help me believe it or not
Honestly, your answer is the same one everyone else gets. Try them out and see. Most of the kernels out there should work with any of the ROMs, even the stock ROM. Personally, I have had no real issues with any ROM/kernel combo I have tried. I use CM because I am so used to the features they add and I dislike the stock GB theme. I'm using the last nightly cm7 had because there was something they didn't have in the stable but I don't recall what that was. But most any ROM or kernel you get for gB is likely done being developed for. The combination in my signature serves me very well. A lot of people do like oxygen. I just missed cm too much. Most of the kernels should allow for all of the wants you have.
I also ran cm9 with the glados kernel and honestly, it ran perfect for me. My only issue was with a few apps i use not wanting to cooperate.
Sent from my Nexus S 4G running CM7/franco.Kernel
Sent from my Nexus S 4G running CM7/franco.Kernel
alright thanks (which the button did for me)
I understand that (and some threads I looked over had answers like that, so I figured someone might say something along the lines of "try it out") I was mostly looking for input from past users about some ROM or kernel
I just don't want to end up with a broken phone before I leave for a week or two (to a rural area for a couple of days)
thanks for the answer, all I really need to know now is have there been any problems with any of them running ADB or transferring files from PC to phone?
EDIT: well I'm going to continue trying to get android SDK working on my linux OS, and I'm going to install and run a few ROMs and Kernels
ROMs I'm going to try: CM7.1 Stable, Oxygen, CM9
Kernels: Netarchy, Trinity, matri1x, and glados (with CM9)