Database Info

Kernel's?

Can someone explain to me how kernel's work and if I flash one will I be able to get rid of it? Say flash a stock one? Someone please explain.

Make a nandroid before flashing the kernel

Darrien13 said:
Can someone explain to me how kernel's work and if I flash one will I be able to get rid of it? Say flash a stock one? Someone please explain.
Click to expand...
Click to collapse
The kernel provides the subsystem on which the OS itself operates. It is the interface to the physical hardware, handling access to physical devices as well as memory management. An optimized kernel can make a significant difference over a "vanilla" configuration.
Make a nandroid before you flash any kernels to go back easily. Otherwise you could reflash the full 2.3.3 rom.

thank you guys

If you're using CM7 and want to flash a kernel over it. You can just reflash CM7 without wiping anything and it would override your kernel with stock. CM7 includes stock kernel in it.

Yarr when I upgraded from 2.3.2 to CM7 RC1, my netarchy 1.2.5 resetted back to stock as I lost my Overclock. I just wasn't sure it was a stock kernel or a modified one specifically for CM7 that happened to not have an OC.

Aria807 said:
Yarr when I upgraded from 2.3.2 to CM7 RC1, my netarchy 1.2.5 resetted back to stock as I lost my Overclock. I just wasn't sure it was a stock kernel or a modified one specifically for CM7 that happened to not have an OC.
Click to expand...
Click to collapse
its stock. if you use SetCPU and check the info, its labeled as google.com
or about phone it says #google

Issues with installing certain ROMS [SUCCESS!!!]

Some of the user's here, myself included, have been having issues installing any ROMs/ kernels built by Faux. What I'm trying to do is pinpoint the exact cause of this and hopefully rectify the issue.
I'm currently downloading all available ROMs and will install each to determine which are flashable and which are not.
Flashing Procedures
0. Boot into CMW Recovery: External with EXT 4 support using volume down + power method
1. Wipe Data
2. Wipe Cache
3. Wipe Dalvik
4. Format /System
5. Flash ROM
6. Select Power Down from CMW Menu
7. Power on phone without wall charger plugged in
ROM List:
Bionix- Confirmed as working
EagleBlood GB- Confirmed as working
EagleBlood FR- Confirmed as working
Ultimate- Confirmed as working
Light&Sinister- Confirmed as working
Dark&Sinister- Confirmed as working
Faux AOSP-NOW WORKING!!
CM7- Confirmed as working
LG Stock- Confirmed as working
Observations:
Bionix converts /system and /data to ext3. I figured that if the issue we were having with Faux was due to format errors then I could just flash Faux over Bionix and it would boot. In testing, it seems like Faux gets further when flashed this way but still refuses to boot. Before I would only get the initial LG screen and then it would black out. Now I can get to the second LG screen with blue background but it hangs there. Will run logcat to see what is causing the freeze once I get logcat running again.
My current theory is that there is a difference in the boot.img that Faux has built for his ROM that will not boot correctly. I have the same issue with his kernels as well. They boot to the first LG splash screen and then the screen shuts off. Still struggling with my logcat issue so I'm at a standstill until that is fixed.
Development:
I was finally able to get pure AOSP to boot by flashing Faux's AOSP and then flashing Morfic's CM7 kernel. I personally believe this definitely proves that there is something in Faux's boot.img that doesn't function properly on all devices.
At Faux's suggestion, I flashed his Stock Voltage kernels in order to see if I could get the phone to boot.
Kernel:
[ Start @ 1.0 GHz, Stock Voltage, Max @ 1.2 GHz ]
(Official LGE/Tegra Voltage Values, Same as STOCK LGE Kernel)
CM7 Kernel Version 0.1.9- Boots to second LG splash screen then freezes.
CM7 Kernel Version 0.1.9 With EXT4-Booted fine but still displayed Morfic boot animation for some reason. Kernel version shows as Faux's in about phone, though.

I want to flash my first ROM, any suggestions on which one is the most stable and better with battery life than the Stock ROM?

Mikeglongo said:
I want to flash my first ROM, any suggestions on which one is the most stable and better with battery life than the Stock ROM?
Click to expand...
Click to collapse
I didn't test any of the ROMs for quality but I would personally stick with a Froyo based ROM for now. Gingerbread is simply too buggy and missing a lot of features.

[B][U]SUCCESS!!![/U][/B]
I was finally able to get pure AOSP to boot by flashing Faux's AOSP and then flashing Trinity's CM7 kernel. I personally believe this definitely prooves that there is something in Faux's boot.img that doesn't function properly on all devices. That would explain why I am unable to flash any of his kernels, either.

Most likely scenario is that you have a "weaker" chip which cannot handle the default OC to 1.1 and Under volting. Because of your case and a few others like you with the "weaker" chips, I have decided from next version on to include LG STOCK VOLTAGE version of my kernel as default kernel for the ROM and it's up to the users to install the OC/UV version themselves afterwards.
My solution is while in CWM, after you flashed the ROM, before you reboot, FLASH my STOCK VOLTAGE (SV) version of the kernel, then reboot. You should have NO ISSUES with STOCK VOLTAGE kernels.
So far for MT4G and G2x, I have been lucky with my phones. Both phones I can Undervolt and overclock AT the SAME TIME with very aggressive settings and remain stable with multiple runs of stress tests and benchmarks.

faux123 said:
Most likely scenario is that you have a "weaker" chip which cannot handle the default OC to 1.1 and Under volting. Because of your case and a few others like you with the "weaker" chips, I have decided from next version on to include LG STOCK VOLTAGE version of my kernel as default kernel for the ROM and it's up to the users to install the OC/UV version themselves afterwards.
My solution is while in CWM, after you flashed the ROM, before you reboot, FLASH my STOCK VOLTAGE (SV) version of the kernel, then reboot. You should have NO ISSUES with STOCK VOLTAGE kernels.
So far for MT4G and G2x, I have been lucky with my phones. Both phones I can Undervolt and overclock AT the SAME TIME with very aggressive settings and remain stable with multiple runs of stress tests and benchmarks.
Click to expand...
Click to collapse
The only problem with that theory, Faux, is that Morfic's kernel undervolts as well. Flashing his kernel on top of your ROM is the current workaround that I've found.

hiko36 said:
The only problem with that theory, Faux, is that Morfic's kernel undervolts as well. Flashing his kernel on top of your ROM is the current workaround that I've found.
Click to expand...
Click to collapse
I don't know what Morphic is doing with his under volting, theres no source code to compare. My source is based on CM7 with my tweaks added and its available via github for inspection.

faux123 said:
I don't know what Morphic is doing with his under volting, theres no source code to compare. My source is based on CM7 with my tweaks added and its available via github for inspection.
Click to expand...
Click to collapse
Please don't view my opinions as doubting your ability. This has just been a frustrating journey for a lot of us because we want to use your kernels/ROMs. I couldn't find anywhere where this had been addressed so I decided to take it upon myself. At this time, the two options we have are flashing your stock voltage kernel or Morfic's. Now that it's booted and running, I can say that you've built a beautiful ROM and I hope you continue to support it. Amazing work.

hiko36 said:
Please don't view my opinions as doubting your ability. This has just been a frustrating journey for a lot of us because we want to use your kernels/ROMs. I couldn't find anywhere where this had been addressed so I decided to take it upon myself. At this time, the two options we have are flashing your stock voltage kernel or Morfic's. Now that it's booted and running, I can say that you've built a beautiful ROM and I hope you continue to support it. Amazing work.
Click to expand...
Click to collapse
I took NO offense of your investigation or posts. I am actually glad you did all these. You have provided me reason for using stock voltage kernel as default. I was contemplating about this change a while back, but since your post, I decided to do it so more people can try my ROM without having random reboots or issues due to UV/OC combination.
I am simply posting what I can and cannot do. I can do only what I can read and see.

faux123 said:
I took NO offense of your investigation or posts. I am actually glad you did all these. You have provided me reason for using stock voltage kernel as default. I was contemplating about this change a while back, but since your post, I decided to do it so more people can try my ROM without having random reboots or issues due to UV/OC combination.
I am simply posting what I can and cannot do. I can do only what I can read and see.
Click to expand...
Click to collapse
Glad I could help and especially glad I finally figured out a way to boot your ROM. I was feeling left out haha.

Doh! He said rectify lol
Sent from my Xoom using XDA Premium App

Overclocking in ICS?

I have been having issues getting my TF101 to overclock in ICS. I have tried Codename Android, CM9, TeamEOS, and Revolver, and ALL of them I could not overclock in. I have tried SetCPU, No-Frills, and (if applicable) the built in frequency control. They all show that the maximum frequency is 1000MHz. I have no clue what is going wrong here. They all were able to gain Superuser, so that isn't the problem. Any and all help would be highly appreciated. I just have no clue what I could be doing wrong.

stompysan said:
I have been having issues getting my TF101 to overclock in ICS. I have tried Codename Android, CM9, TeamEOS, and Revolver, and ALL of them I could not overclock in. I have tried SetCPU, No-Frills, and (if applicable) the built in frequency control. They all show that the maximum frequency is 1000MHz. I have no clue what is going wrong here. They all were able to gain Superuser, so that isn't the problem. Any and all help would be highly appreciated. I just have no clue what I could be doing wrong.
Click to expand...
Click to collapse
Antutu CPUMaster Free works for me on Revolver4_1.3.1 and Blades_meh kernel. You have to manually go into it after installing a OC kernel and set the min and max frequencies and choose a governor and there's a checkbox to tell it to set these at boot. After that it works all day everyday for me up to 1680MHz and deep sleep works, too.

sidneyk said:
Antutu CPUMaster Free works for me on Revolver4_1.3.1 and Blades_meh kernel. You have to manually go into it after installing a OC kernel and set the min and max frequencies and choose a governor and there's a checkbox to tell it to set these at boot. After that it works all day everyday for me up to 1680MHz and deep sleep works, too.
Click to expand...
Click to collapse
Just tried Antutu CPU Master. Same issues. It says that my max frequency is 1000MHz.

Have you manually loaded a new kernel to replace the stock one? Setcpu and the like only modify settings that a kernel exposes, and the default kernel does not allow anything higher then 1000.

Tekfrog said:
Have you manually loaded a new kernel to replace the stock one? Setcpu and the like only modify settings that a kernel exposes, and the default kernel does not allow anything higher then 1000.
Click to expand...
Click to collapse
Yes. After doing so, I also go into my settings and clear the cache and data from SetCPU, so I could set it up again. Still, I am getting max 1000MHz.

stompysan said:
Yes. After doing so, I also go into my settings and clear the cache and data from SetCPU, so I could set it up again. Still, I am getting max 1000MHz.
Click to expand...
Click to collapse
Which kernel are you running now?

Tekfrog said:
Which kernel are you running now?
Click to expand...
Click to collapse
Thanks for trying to help, but I have found my problem. My recovery was still borked from when I tried flashing the official one in Rom Manager. Wiped my recovery, installed the roach recovery, reflashed all of my files, and now I am good to go. I feel like a derp now. LOL

Same issue w/ OC...but wipe recovery?
Your issue sounds exactly like the one I am currently having.
I would like to try your fix...but I am not understanding how the "wipe recovery" process goes. Would you mind please explaining that in more detail? Im pretty sure it IS NOT as simple as just doing a complete cache/data wipe then flashing the recovery over itself is it?
I am:
ViperMOD Prime rooted
ClockworkRecoveryMOD installed (but I think I may have fubar'd it doing the same thing you did trying to recover stock recovery)
FROZN 1.0.9 rom w/ included Guevor kernel and NoFrills CPU app
...but none of the CPU apps will let me OC...wether I flash the kernel seperate from the ROM or use the one included w/ the ROM.
Hope you can help me.

UPDATE: apparently this inability to OC the kernel in any way is happening to those of us experiencing the CWM bootloop issue...so since the loader goes immediately to CWM it never runs the flashed kernel.
So in these forums is a thread to fix the CWM bootloop and if you follow the instructions carefully, you fix the bootloop and thus allowing the flashed kernels a chance to actually install. I chose the Roach method which you can install the code using Terminal Emulator pretty intuitively. I didnt choose the other method because I didnt want to mess w/ setting up an ADB terminal on my PC, which seemed MUCH more difficult.
So...now FINALLY
ViperMOD Prime rooted
ClockworkMOD Touch Recovery 5.8.8
FROZN 1.0.9 ROM (w/ built-in Guevor kernel @ 1.2 default) and am OCd @ 1.54 (np's at all so far, lightning fast, havent even tried 1.6 or 1.7).
Only issue so far is File Manager app crashes on startup...which isnt good because now the other file manager app I tried doesnt see my ext_SDcard...the stock File Manager did.

I've tried using both tastyMEH and Blades using Revolver, CM9 and Android HD, and the stock ICS ROM, using Set CPU and ROM Toolbox pro to try and overclock. I've flashed the ROM first and then the Kernel, and the Kernel and then the ROM. Nothing I've done thus far has enabled me to set the CPU sliders past 1000 mhz. I know people are running these combos and getting 1.6-1.8 clocks. What am I screwing up? I'm using Clockwork Mod recovery to flash. I couldn't even get CM9 to boot.
Thanks so much in advance
Teh Wuss

WU55 said:
I've tried using both tastyMEH and Blades using Revolver, CM9 and Android HD, and the stock ICS ROM, using Set CPU and ROM Toolbox pro to try and overclock. I've flashed the ROM first and then the Kernel, and the Kernel and then the ROM. Nothing I've done thus far has enabled me to set the CPU sliders past 1000 mhz. I know people are running these combos and getting 1.6-1.8 clocks. What am I screwing up? I'm using Clockwork Mod recovery to flash. I couldn't even get CM9 to boot.
Thanks so much in advance
Teh Wuss
Click to expand...
Click to collapse
Please see above solution...I know it seems unrelated but it is the fix for both CWM bootloop AND being able to accept and install a flashed kernel.
If you need additional help, please ask. I am willing to share my solution in more detail to help others out.

WU55 said:
I've tried using both tastyMEH and Blades using Revolver, CM9 and Android HD, and the stock ICS ROM, using Set CPU and ROM Toolbox pro to try and overclock. I've flashed the ROM first and then the Kernel, and the Kernel and then the ROM. Nothing I've done thus far has enabled me to set the CPU sliders past 1000 mhz. I know people are running these combos and getting 1.6-1.8 clocks. What am I screwing up? I'm using Clockwork Mod recovery to flash. I couldn't even get CM9 to boot.
Thanks so much in advance
Teh Wuss
Click to expand...
Click to collapse
When you flash the kernel go to the about section in android and make sure the flash was actually successful.

fwbflash said:
Please see above solution...I know it seems unrelated but it is the fix for both CWM bootloop AND being able to accept and install a flashed kernel.
If you need additional help, please ask. I am willing to share my solution in more detail to help others out.
Click to expand...
Click to collapse
Thanks, this may be a step in the right direction. However I've tried 3 times now to flash the 5.8 touch to no avail. Everytime I reboot I end up with standard 5.5.0.4. I tried flashing with CWM. What am I doing wrong? If it helps ever since I flashed CWM, if the tablet retboots for any reason it automatically boots into CWM, and I have to cold boot into Android manually using the power and volume rocker.
Thanks again-
Teh Wuss

WU55 said:
Thanks, this may be a step in the right direction. However I've tried 3 times now to flash the 5.8 touch to no avail. Everytime I reboot I end up with standard 5.5.0.4. I tried flashing with CWM. What am I doing wrong? If it helps ever since I flashed CWM, if the tablet retboots for any reason it automatically boots into CWM, and I have to cold boot into Android manually using the power and volume rocker.
Thanks again-
Teh Wuss
Click to expand...
Click to collapse
Because your version of CWM is bad. You need to read this thread: http://forum.xda-developers.com/showthread.php?t=1530337
It's on the front page of general discussion, how did you even not see it yet.

horndroid said:
Because your version of CWM is bad. You need to read this thread: http://forum.xda-developers.com/showthread.php?t=1530337
It's on the front page of general discussion, how did you even not see it yet.
Click to expand...
Click to collapse
Thanks, this was it, I didn't see it, because I was a noob and didn't look for it.

Installing cleanrom on ICS is weird

Wow, this device is a lot different from any other android device i've used. Rooting, unlocking, downgrading to unlock...bla bla bla.
Well i am really motivated to install clean rom and so far this is what i've done:
I was on officiel lock and unrooted JB. So i downgraded to ICS, unlocked it, rooted, installed CWM and usually, on any other device i would just flash any rom. But since asus are so freaking strick with their warranties, i rather look like a newb and ask then brick my machine.
So, on the pre-requesites of cleanrom it says
Bootloader: Official Asus Jellybean bootloader
Recovery: TWRP 2.3.1.0 or ClockworkMod 6.0.1.4
I'm not sure, but now that im unlocked and rooted on ICS, can't i just flash cleanrom from recovery or do i really need to be on JB bootloader. Also, since i walready was on JB, did i keep my JB bootloader or did i downgrade it at the same time i reverted back to ICS?
I'm sorry to be such a newb, but with my galaxy S3 i can pretty much do anything to it and i'm not scared a bit of bricking, its so easy to unbrick, but with the tf700, im stressed and rather take my time than rush it.
Thanks for the help!

Lol
Well Fortunately I have made that mistake for you.
It's best to flash clrom whilst on the JB boot loader.
I ran into problems when I flashed clemsyns kernel with clean on ICS.
Sooo yes CleanROM on JB.
Sent from the inside out...

The problem is that clemsyns kernel requires the JB bootloader in order to work correctly. No risk, but it just won't get above 1.3 or 1.4 mhz because the voltage tables between the kernel and bootloader are incompatible.
Easiest way is to do a system restore with a stock JB image from the Asus website. You may lose custom recovery doing this, but since you are unlocked, you can then flash custom recovery via fastboot...

thank you guys, youve been veru helpful! +1

latest ICS bootloader
danger-rat said:
The problem is that clemsyns kernel requires the JB bootloader in order to work correctly. No risk, but it just won't get above 1.3 or 1.4 mhz because the voltage tables between the kernel and bootloader are incompatible.
Easiest way is to do a system restore with a stock JB image from the Asus website. You may lose custom recovery doing this, but since you are unlocked, you can then flash custom recovery via fastboot...
Click to expand...
Click to collapse
please allow me one question. as far as know, the bootloaders of latest ICS version .30 is equal to JB version .18. if so why is JB mandatory?

dc_01 said:
as far as know, the bootloaders of latest ICS version .30 is equal to JB version .18.
Click to expand...
Click to collapse
They are not equal at all. The file size is rather different, and also the version number, which strangely changed from 2.10 to 1.00 in the newer version:
Android cardhu-user bootloader <2.10 e> released by "WW_epad-9.4.5.30-20120907"
Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.4.4.18-20121012"

well, I've installed JB and now am runnin cleanrom. I love it! Its fast, snappy and does not lag like the stock rom. I've also installed Clemsyn's kernel but had to revert back to reinstalling cleanrom because I HATED the higher DPI and use DPI modder to reduce it back to 120 and then the tablet didn't want to get past Asus screen where it said "this device is unlocked"
I have higher DPI on this tablet, I thing the stock is perfect and I despise the fast that it comes with the kernel with no option to set it back. Unless I didn't find it. But is it really worth to have that kernel cause as really satisfied with the rom by itself

polish_pat said:
well, I've installed JB and now am runnin cleanrom. I love it! Its fast, snappy and does not lag like the stock rom. I've also installed Clemsyn's kernel but had to revert back to reinstalling cleanrom because I HATED the higher DPI and use DPI modder to reduce it back to 120 and then the tablet didn't want to get past Asus screen where it said "this device is unlocked"
I have higher DPI on this tablet, I thing the stock is perfect and I despise the fast that it comes with the kernel with no option to set it back. Unless I didn't find it. But is it really worth to have that kernel cause as really satisfied with the rom by itself
Click to expand...
Click to collapse
To bring the resolution back to stock you have to bring the DPI to 240 (not 120). Simple change by editing the build.prop (just look for number 160 and change it to 240).

buhohitr said:
To bring the resolution back to stock you have to bring the DPI to 240 (not 120). Simple change by editing the default.prop (just look for number 160 and change it to 240).
Click to expand...
Click to collapse
by default.prop you must mean build.prop because de default has almost nothing in it...

polish_pat said:
by default.prop you must mean build.prop because de default has almost nothing in it...
Click to expand...
Click to collapse
Yes, build.prop, look for the number 160 and change it to 240 save then reboot.
location:
/system/build.prop
before:
ro.sf.lcd_density=160
change to:
ro.sf.lcd_density=240

Had problems getting 240 to stick.
Using ES File explorer the permissions needed to be set rw-rw-rw then back to rw-r-r not sure why.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

My S7 BSOD'd, should I install a custom ROM?

My S7's firmware kicked the bucket yesterday and had the black screen of death. Currently out the house so I had no way to recover anything and ended up factory resetting via the recovery menu.
I was planning to root before all this happened but I was waiting for Samsung Pay in UK since I wanted to try it out, but I don't really want my device locking up again and having to reset it again.
I'm thinking of installing a custom ROM since it would prevent the issue from occuring again but I'm wondering if theres anything I should know before I do, since I've seen people say that the stock Samsung camera app is the best and that any stock custom ROM camera makes the quality bad. Is there anything else I should know?

Just install a different stock based ROM, BSODs are caused by a myriad of reasons ranging from Kernel instability to a system modification gone wrong.
Just make sure to stick with a stock-friendly kernel or the stock based kernel to avoid BSODs

Revontheus said:
Just install a different stock based ROM, BSODs are caused by a myriad of reasons ranging from Kernel instability to a system modification gone wrong.
Just make sure to stick with a stock-friendly kernel or the stock based kernel to avoid BSODs
Click to expand...
Click to collapse
Alright, thanks!
I'll probably install superstock ROM or some other de-bloated stock ROM then.

Superstock ROM + Superstock Kernel make for a killer combo, go for it

Revontheus said:
Superstock ROM + Superstock Kernel make for a killer combo, go for it
Click to expand...
Click to collapse
Sounds good! I'll install it tomorrow when I get back home
Would rather not lose my data than have access to Samsung Pay, so it's all good.