[Q] Link to bodivas repack kernel for 6810 - Galaxy Tab 7.7 Q&A, Help & Troubleshooting

Hi, does anyone have a link to the bodivas repack kernel for the 6810? The link is missing from UTIA's second post in the thread for his kernel. I want to give his kernel a whirl. Thanks, Matt

Ignore this request. I flashed UITA's kernel but my hardware and his ROMs/kernels do not get along :'(
Reverting back to my backup...
Matt

mattbuffey said:
Ignore this request. I flashed UITA's kernel but my hardware and his ROMs/kernels do not get along :'(
Reverting back to my backup...
Matt
Click to expand...
Click to collapse
I'll upload it later today. Forgot all about it sorry.
Firstly, did you flash the SkyHigh kernel after first boot of any ROM? Don't flash directly after ROM flash. Otherwise boot loop. Only after ROM full boot.
Secondly, make sure that you have no tweaks or tweaking apps etc installed.
For the ROM, you need to follow the installation instructions EXACTLY, using correct recovery version and full wipe install.
Other than that, unfortunately, your hardware may not like some of the kernel tweaking or UV etc.
BTW, I'm working on a SkyHigh kernel update. Maybe try that in future "IF" I ever get to release stage.....
Sent from my GT-I9500 using XDA Premium 4 mobile app

It's weird, I had the same problem with your ROM on ICS. I was hoping JB would be different, but I got exactly the same stability problem. As you say, it must be something to do with the tweaks that upsets my tab. I can report that CIFS works fine with your kernel though!

Related

[Q] Updating Kernel

I was just wondering that if I am going to update my kernel is it necessary to re-install the rom or do I just install the zip with clockwork and away i go? I've searched the forum and couldn't find anything regarding it, I would appreciate the help! Thanks.
you can just use CWM to installed the kernels without installing the rom but there might be some compatibility issues, so check before doing it.
Ok because the reason I'm asking is because I have SupeAosp with the Trinity kernel but I'm thinking on either upgrading for Trinity 12 to 14 or trying out James Bond Kernel and I thought that there might be some prep work involved.
xmatrix13 said:
Ok because the reason I'm asking is because I have SupeAosp with the Trinity kernel but I'm thinking on either upgrading for Trinity 12 to 14 or trying out James Bond Kernel and I thought that there might be some prep work involved.
Click to expand...
Click to collapse
just flash the newer kernel on top. be sure its compatable with the rom. if you do have issues, just reflash the rom(that will bring you back to the roms "stock" kernel).
In this case you can test out different kernels but make sure you have the trinity kernel file in the root folder in case which ever kernel you do flash doesn't work out.
In such a case you would just boot into CWM and re-flash the morfic kernel.
Sent from my Nexus S using XDA Premium App
Thanks for the insight, I look forward to testing out many kernels!

[Q] Faux123 stock ov kernal & paul's patch

hey everyone,
does anybody know if these two are compatible to work together or is it something where it's either or? i've been looking through the threads but haven't manage to find any answer for it. i appreciate any answers.
THANKS!
All reports say there is no reason for Pauls patch on custom roms.
oh alright. thanks for responding
jcbofkc said:
All reports say there is no reason for Pauls patch on custom roms.
Click to expand...
Click to collapse
Faux kernel is not a ROM. He is using it on that ROM - so the question was not specifically answered.
I had Paul's patch on stock kernel when I first flashed faux kernel, but don't know for sure if it is needed (ie - is the patch of the kernel or something else?).
gaww said:
Faux kernel is not a ROM. He is using it on that ROM - so the question was not specifically answered.
I had Paul's patch on stock kernel when I first flashed faux kernel, but don't know for sure if it is needed (ie - is the patch of the kernel or something else?).
Click to expand...
Click to collapse
Let me be more specific in case the OP did not get it. No, you do not need Pauls patch for custom kernels or roms. It is strictly designed for the stock rom to fix a mistake by LG.
jcbofkc said:
Let me be more specific in case the OP did not get it. No, you do not need Pauls patch for custom kernels or roms. It is strictly designed for the stock rom to fix a mistake by LG.
Click to expand...
Click to collapse
The patch was an updated services.jar messed up by lg in the stock ROM. Do kernels also include a services.jar?
If so, then no need when kernels are flashed either, as it would be overwritten. This would be the clarification he (and I) was looking for. If not ??
Note - when I look in a whole ROM zip file - I can find it. Cannot when I open a kernel zip file.
gaww said:
Faux kernel is not a ROM. He is using it on that ROM
Click to expand...
Click to collapse
What does that mean.so is the kernel baked into the rom: when we install faux's rom, we automatically get the kernel .
Sent from my LG-P999 using XDA App
ashman3000 said:
What does that mean.so is the kernel baked into the rom: when we install faux's rom, we automatically get the kernel .
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Yes - if you flash faux ROM - you get his kernel as part of it.
But the OP was about using faux (with) stock kernel on the stock froyo ROM. The stock ROM had some messed-up up stuff by LG in the (I have read) services.jar file in the stock ROM.
He asked if he could (should) use the paul patch with this combination. Since the services.jar is (I also believe) not changed by the kernel only, it appears that it should be flashed on top of the stock ROM once (unless you wipe and it is then gone), and then flash the kernel (I did that).
For ALL CM ROMs - different services.jar - no problem. But for EB and other stock based froyp ROM's - I am not sure. If the Dev's built paul's fix into the services.jar -then they are OK. If not, they might be able to use the fix also.
Would REALLY like to hear from one of the Dev's on this. Been all over the forums, and with respect to the kernel only and other than stock froyo ROM's - it has not been clearly spelled out.
its for STOCK roms not custom kernels dont matter in this pauls patch fixes a problem with lg stock rom all custom roms should have this fixed

Flashing kernals causes boot loops

I just got the Captivate yesterday and I'm in love with it. I've been modding my Backflip for a while and I'm fairly certain I know what I'm doing. I've been trying different ROMs and I've currently settled on a rooted stock 2.2 ROM.
I want to change my kernel though, so I put my phone in download mode and flashed the Galaxian kernel via Odin, it finished and then my phone started boot looping. So I one clicked it and tried again with SGS flasher, boot loop. One click restored, tried with CWM, boot loop.
I've also tried Talon, Speedmod, Setiron and a stock kernel with all 3 methods. Nothing will flash without boot looping.
That kernel is designed for reoriented i-9000 roms
Sent from my SAMSUNG-SGH-I897 using XDA App
What about all of the other ones that were supposedly for 2.2 ROMs?
AbaddonVH said:
What about all of the other ones that were supposedly for 2.2 ROMs?
Click to expand...
Click to collapse
It needs to be a true captivate 2.2 kernel a lot are i9000's you just need to read the op for whichever kernel you are looking at thoroughly. 90% of the time the dev states if its an i9000 kernel.
The speed mod kernel here, forum.xda-developers.com/showthread.php?t=893880 SHOULD work just make sure to wipe cache and dalvik cache in recovery after install and it should boot.
Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
You will have to read the description in the first post on the kernel you want to install, and the kernel you were installing was a gingerbread kernel
Sent from my SAMSUNG-SGH-I897 using XDA App
holeindalip said:
You will have to read the description in the first post on the kernel you want to install, and the kernel you were installing was a gingerbread kernel
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Yeah. You were trying to install a gingerbread kernel on a froyo ROM. That won't work.
Thanks guys! I think I downloaded the wrong version of SpeedMod the first time, it worked this time. Firstly I didn't know that the difference between i-9000 and i897 meant that much. Secondly, I'm not really sure how to read the kernel topics, they're confusing to say the least :S.
I'll learn sooner or later but thanks for your help everyone.
AbaddonVH said:
Thanks guys! I think I downloaded the wrong version of SpeedMod the first time, it worked this time. Firstly I didn't know that the difference between i-9000 and i897 meant that much. Secondly, I'm not really sure how to read the kernel topics, they're confusing to say the least :S.
I'll learn sooner or later but thanks for your help everyone.
Click to expand...
Click to collapse
Yeah some are very confusing the biggest help Is to learn the difference in firmware revision codes. Most captivate roms/kernels begin with k. like kh3, kf1 that sort of thing and from what I remember j is for I9000 eg jv1 etc...
Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.

[Q] Best kernel to go with Android Revolution HD 3.2.1?

I'm not terribly good with kernels, and the only thing I understand is that if I have a custom one, I can overclock on SetCPU and do a few other things. I have ARHD 3.2.1 right now, but I don't know how kernels really work.
Sorry if this is a bit of a nooby question, but I am a noob C:
Thank You.
Try TastyMeh (in my signature)
Or Guevors test kernel (dev forum)
Both are similar, have awesome fixes, and oc to 1.7Ghz
You just got to try them out. Every unit is different so what may work for me might not work for you. +1 for guevors. 11b tends to still work best for most people.
Sorry for abusing this thread for a noobish question.
I was on stock ICS, rooted and installed guevor's test13 kernel for a while. Then switched to test15.
Yesterday I downloaded Full Wipe Script and Revolution ROM from dev thread, and used them:
1. Full Wipe
2. Install Revolution
My questions are ...
* Which kernel do I have now?
* Did the ROM installation change the kernel to the one that is included with the ROM?
* Maybe the ROM doesn't include a kernel, so I am still on test15?
BTW, I already checked on system info but I wasn't able to extract any useful info from that. I think that now I am using whatever kernel Revolution includes, but I am not sure.
Thanks in advance.
CalvinH said:
My questions are ...
* Which kernel do I have now?
* Did the ROM installation change the kernel to the one that is included with the ROM?
* Maybe the ROM doesn't include a kernel, so I am still on test15?
Click to expand...
Click to collapse
It will be the stock kernel that comes with the rom. Flash the test kernel again if you want it.
kokopopz said:
It will be the stock kernel that comes with the rom. Flash the test kernel again if you want it.
Click to expand...
Click to collapse
Thank you very much. I'll keep the stock Revolution kernel for a while.

HTC One XL oc tools

Hi. Wich tools can be used to overclock a little the cpu, and/or gpu?
I've noticed some performance drop in 3d since sense 5, comparing with sense 4. Specially with WAZE app.
Thanks all.
You first need a custom kernel to OC. Then you can use apps like Trickster Mod, Kernel Tuner, and others to tune the kernel settings.
Sent from my Evita.
Can you give me some help to go with a custom kernel? Does they improve a lot over the default ones? I was looking at BEASTMODE rld 3.5...
There are only two available for Sense 5, Beastmode and Elemental. Asking for a suggestion isn't allowed so I can't do that. They're both pretty good though.
Sent from my Evita.
OC'ing HTC One X
Google and/or YouTube Beastmode. Plenty of info available.
FedericoUY said:
Can you give me some help to go with a custom kernel? Does they improve a lot over the default ones? I was looking at BEASTMODE rld 3.5...
Click to expand...
Click to collapse
If you are looking to overclock, then a custom kernel is a must, so in that way its an "improvement" (at least more features) than stock kernel. On a stock kernel, CPU frequencies over the "official" spec will not be available (not even appear) on overclocking tools/apps. Also, custom kernel will generally give more choice of governors, if you are into such things.
Ok, after I get a solution with the connectivity problem I'll try to switch kernel. But what about 3d performance loss with this now rom, particulary with sense 5 I guess? Is that normal?
I never noticed a performance loss with 3d on Sense 5, but you can OC both 2d and 3d with the Beastmode kernel.
Sent from my Evita.
Ok, the kernel installation is just from twrp like a rom choosing wich one to install right? Are there any noticeable gains with them? Whether it is beastmode or elemental x?
FedericoUY said:
Ok, the kernel installation is just from twrp like a rom choosing wich one to install right? Are there any noticeable gains with them? Whether it is beastmode or elemental x?
Click to expand...
Click to collapse
Yes, kernels are flashed in recovery. Beastmode is s-on friendly, but Elemental requires s-off according to the top post of that thread.
Whether you notice any gains will probably depend on how you use your phone and how you tweak, so I don't think there is any blanket response to that question. If you have given this much thought to it, just go ahead and flash. You can always dirty flash the ROM to go back to stock kernel, if you don't like the results. Or make a nandroid backup before you flash the kernel, which I recommend before flashing anything, anyway.
If I flash a kernel, whether elemental or beastmode, is there a way to return to orginal kernel only without flashing the entire rom?
You only need to dirty flash the ROM, that's flashing the ROM again without wiping anything except cache and dalvik. All of your settings, apps, and so on will remain, you'll actually not notice any changes at all. If for some reason you don't want to do that you can just flash the boot.img from the ROM zip to get the stock kernel back.
Sent from my Evita.
That's just what I needed to know. Thanks for the thousanth time timmaaaa. Cheers!
You're welcome, glad to help.
Sent from my Evita.
FedericoUY said:
If I flash a kernel, whether elemental or beastmode, is there a way to return to orginal kernel only without flashing the entire rom?
Click to expand...
Click to collapse
Dude, I already answer that question before you even asked it. Did you read my previous post?
Sent from my HTC One XL using xda app-developers app
redpoint73 said:
Dude, I already answer that question before you even asked it. Did you read my previous post?
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
I made a different question later, about just returning to previous kernel WITHOUT flashing the entire rom. I've read your post, and was helpful as well. Thank you.
Hi again. If I backup my current rom (system/data/boot) with the stock kernel, then I flash a moded kernel, and then I restore my backup (maybe because I'm not comfortable with the new flashed kernel for example), the kernel will be restored as it was on the moment of the backup right?
That's correct, but you don't necessarily need to restore the backup to get the stock kernel back. You can just flash the boot.img from the ROM zip, or dirty flash the ROM.
Sent from my Evita.
So flashing the boot.img will only flash the kernel.... Intresting. Thanks!
FedericoUY said:
I made a different question later, about just returning to previous kernel WITHOUT flashing the entire rom..
Click to expand...
Click to collapse
I don't think you understand what a "dirty flash" is. Flash without doing a factory reset (but wipe cache and Dalvik, which you shoud pretty much do with any significant system change). It retains all your settings, apps, etc. which are contained in the user data partition. It only touches the partitions where the ROM itself and kernel are located. It doesn't take any more time than flashing the stock boot.img.
---------- Post added at 10:17 AM ---------- Previous post was at 10:15 AM ----------
FedericoUY said:
So flashing the boot.img will only flash the kernel.... Intresting. Thanks!
Click to expand...
Click to collapse
Actually, there are other contents in boot.img besides just the kernel. But for practical purposes, nothing that significant.

Categories

Resources