Is there a 3.0 Kernel for the droid inc, 2.x.x.x.x is just not working.
And aokp doesn't even boot up...
There are no 3.0 kernels that I'm aware of. I can tell you now that the kernels being on 2.6 is not the problem. If you're running the wrong kernel for the ROM it won't boot or will boot but not run properly. What ROM or ROMs have you tried and what kernels have you run with them? What is the build date on the kernels? (incredikernel has the build date in the zip file).
Also you can try flashing the ROM without a kernel - it would use the included kernel in this case - and that should boot. Not working or not booting is not specific enough as it doesn't indicate what you tried flashing.
tiny4579 said:
There are no 3.0 kernels that I'm aware of. I can tell you now that the kernels being on 2.6 is not the problem. If you're running the wrong kernel for the ROM it won't boot or will boot but not run properly. What ROM or ROMs have you tried and what kernels have you run with them? What is the build date on the kernels? (incredikernel has the build date in the zip file).
Also you can try flashing the ROM without a kernel - it would use the included kernel in this case - and that should boot. Not working or not booting is not specific enough as it doesn't indicate what you tried flashing.
Click to expand...
Click to collapse
Basically, Everything works, BUT, aokp.
ericerk said:
Basically, Everything works, BUT, aokp.
Click to expand...
Click to collapse
Later aokp builds had issues booting. I cant remember the last build that did. Which one did you try? If you look in the aokp thread there's a fix to get the later ones to boot. Also note that aokp is no longer supported by the aokp team for the inc.
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
Later aokp builds had issues booting. I cant remember the last build that did. Which one did you try? If you look in the aokp thread there's a fix to get the later ones to boot. Also note that aokp is no longer supported by the aokp team for the inc.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I keep forgetting that its been discontinued
I've tried m4- m6
ericerk said:
I keep forgetting that its been discontinued
I've tried m4- m6
Click to expand...
Click to collapse
Try this fix for builds 38 and later.
http://forum.xda-developers.com/showthread.php?p=27836781
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
Try this fix for builds 38 and later.
http://forum.xda-developers.com/showthread.php?p=27836781
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'll try that thanks!
Related
This is an unofficial AOKP build for the tf300t.
Basically it is current AOKP with loganmc10s device files.
Thanks to termleech for helping me fix the boot.blob issue!
Changelog
2012/08/26
Updated to latest AOKP commits (2012/08/26)
Working toggles thanks to http://gerrit.sudoservers.com/#/c/2896/
2012/08/18
boot.blob is now flashed correctly, you don't need to install CM10 prior to this ROM anymore
Instructions
Download ROM
Download GAPPS
Wipe
Flash ROM
Flash GAPPS
...
Profit!
Device tree here: https://github.com/loganmc10
AOKP Source here: https://github.com/aokp
Known issues
Navbar cannot be customized (except icon transparency)
GPS not working
Nice, will try this out today!
Boot animation keeps looping. Do you have to be stock before flashing this?
Turbojugend said:
Nice, will try this out today!
Boot animation keeps looping. Do you have to be stock before flashing this?
Click to expand...
Click to collapse
Don't have to be much of anything besides rooted w/ custom recovery. It should operate fine unless there's something wrong with the boot.img
I was running Hydro, wouldn't boot, went back to stock, will flash recovery and try flashing again.
Edit - Don't know what else I can be doing wrong. I went back to stock, flashed TWRP 2.2.1.3 and wiped, installed this rom, and it stays on the boot animation. Any ideas?
Turbojugend said:
I was running Hydro, wouldn't boot, went back to stock, will flash recovery and try flashing again.
Edit - Don't know what else I can be doing wrong. I went back to stock, flashed TWRP 2.2.1.3 and wiped, installed this rom, and it stays on the boot animation. Any ideas?
Click to expand...
Click to collapse
Check out Term's AOKP JB thrad to see if he posted a boot.img/flashable kernel. That sounds like what your issue is. I have heard that TWRP doesn't properly restore/wipe boot partition.
doesn´t boot with CWM here.
Stuck on the AOKP bootanimation
mikaole said:
doesn´t boot with CWM here.
Stuck on the AOKP bootanimation
Click to expand...
Click to collapse
Yeah I knew it wasn't me, every other ROM has worked fine.
---------- Post added at 07:20 PM ---------- Previous post was at 07:15 PM ----------
NYCHitman1 said:
Check out Term's AOKP JB thrad to see if he posted a boot.img/flashable kernel. That sounds like what your issue is. I have heard that TWRP doesn't properly restore/wipe boot partition.
Click to expand...
Click to collapse
But that is irrelevant if you go back to stock.
It's fantastic, thanks man.
Thanks for this. I just dove in! Everything seems buttery. :thumbup:
Sent from my Transformer Pad TF300T using Tapatalk 2
Flashed from CM10 this time and it worked. Buttery smooth rom, good job!
even GPS works?
Im also intrested on knowing if the GPS works.
BTW thanks for the rom, alwyas appreciate the developement on this device.
fromanbr said:
even GPS works?
Click to expand...
Click to collapse
Negative... as the same with other JB roms for this pad.
Sent from my Transformer Pad TF300T using Tapatalk 2
The reason it works fine for those who already have jb is aokp still doesnt make the boot.blob correctly. So unless the OP switches it out with one built from a working build those not already on jb will not boot.
@karodee I'm gonna send you a DM later you can continue the AOKP builds. Ive got my own ROM I'll be releasing here soon so I'll give you ant help you want or need on the aokp stuff.
Sent from my Nexus 7 using Tapatalk 2
termleech said:
The reason it works fine for those who already have jb is aokp still doesnt make the boot.blob correctly. So unless the OP switches it out with one built from a working build those not already on jb will not boot.
@karodee I'm gonna send you a DM later you can continue the AOKP builds. Ive got my own ROM I'll be releasing here soon so I'll give you ant help you want or need on the aokp stuff.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Figured it had to be something like that, since I used your builds before without issue.
NYCHitman1 said:
Check out Term's AOKP JB thrad to see if he posted a boot.img/flashable kernel. That sounds like what your issue is. I have heard that TWRP doesn't properly restore/wipe boot partition.
Click to expand...
Click to collapse
The boot restore was actually fixed two versions of TWRP ago. The most recent update also fixed external SD card support.
First off. Thanks I love AOKP. Is anyone else having notification toggle problems? I had preview two on before and they worked fine. I did a full wipe and flashed this and the toggles don't work at all. They don't even show up. Any ideas?
Sent from my Galaxy Nexus using xda app-developers app
wheelerr said:
First off. Thanks I love AOKP. Is anyone else having notification toggle problems? I had preview two on before and they worked fine. I did a full wipe and flashed this and the toggles don't work at all. They don't even show up. Any ideas?
Click to expand...
Click to collapse
Do you mean you can't customize the toggles displayd in the notification area? I think that is currently not implemented in AOKP, they just recently merged the battery icon for the tablet navbar. Or do you mean the toggles that are there by default do not work? I tried them and they work for me :-/ Could you give a logcat?
Regards
karoodee said:
Do you mean you can't customize the toggles displayd in the notification area? I think that is currently not implemented in AOKP, they just recently merged the battery icon for the tablet navbar. Or do you mean the toggles that are there by default do not work? I tried them and they work for me :-/ Could you give a logcat?
Regards
Click to expand...
Click to collapse
I do mean those toggles. They were in the previous preview. That's why Im confused. The OLD preview was working fine. This latest one doesnt work.
Oh well, we'll see what happens.
I like the boot animation, but this appears to be a port of cm10, not the aokp that is based on stock. What sucks is it doesn't have some of the cm features like battery percentage.
I'm running Slim Bean 3.1.0 on my SGS3. Recently, I've been trying to flash the AGAT and KT747 kernels on my phone, but with no success.
I've tried flashing kernel,wipe cache/dalvik, rebooting, and then installing the Slim Rom file over it.
Anyone have an idea what I'm doing wrong?
grainyrice said:
I'm running Slim Bean 3.1.0 on my SGS3. Recently, I've been trying to flash the AGAT and KT747 kernels on my phone, but with no success.
I've tried flashing kernel,wipe cache/dalvik, rebooting, and then installing the Slim Rom file over it.
Anyone have an idea what I'm doing wrong?
Click to expand...
Click to collapse
98% Sure you are trying to mix an AOSP based ROM with a TW (Stock) type Kernel. That doesn't typically work. There is an option for the AOSP version of Ktoonsez kernel though that _should_ be a better fit with that ROM.
Have fun and continue to read up *Grin*
The thing is, I'm almost positive I downloaded the AOSP version for the KT747 kernel
grainyrice said:
The thing is, I'm almost positive I downloaded the AOSP version for the KT747 kernel
Click to expand...
Click to collapse
That's a good start, the AGAT says LJ7 based in the Post, leading one to believe it is for TW ROMS. And on the Ktoonsez it does have a download link for either TW or AOSP. One you are looking for should be named "KT747-Kernel-AOSP-JB-SPR-12-11-2012.zip". Verify that and speak up again if you are still having issues.
Yes, I'm certain that was the file I flashed, because I remembered noting that the file was 7.72MB prior to downloading.
Also, I'm sure that the Slim Rom is compatible with the KT747 kernel because several posts were made on the thread saying that
the battery life was amazing, which made me wonder if I was doing something wrong.
grainyrice said:
Yes, I'm certain that was the file I flashed, because I remembered noting that the file was 7.72MB prior to downloading.
Also, I'm sure that the Slim Rom is compatible with the KT747 kernel because several posts were made on the thread saying that
the battery life was amazing, which made me wonder if I was doing something wrong.
Click to expand...
Click to collapse
Reading your original post, The order should go 1) ROM then 2) Kernel ... Then Wiping Cache and Dalvik-Cache (And other wipes if needed). Reason for this is if you flash the Kernel first, then the Rom you are over writing the custom Kernel with whatever is packaged with the ROM.
That is the only other obvious thing I see at this point. Hope that helps..
Did you flash the kernel fix that slim says you need to flash in order to run another kernel? Guess you didn't...
Sent from my SPH-L710 using xda app-developers app
pastert33 said:
Did you flash the kernel fix that slim says you need to flash in order to run another kernel? Guess you didn't...
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
See that now, thanks and sorry for the inconvenience.
Please report back on how you like it, and if you really notice any differences.
It dropped 1% in approximately 30 minutes, half of the time the screen was just on, other half I left it on my desk (all while connected to Wifi).
My settings are 96/1998 on ktoonservative.
In my opinion, so far its amazing as compared to other AOSP roms I've tried.
hi guys! i've got the same problem, can't change the kernel in my i9300.. could you please tell me where i can find the kernel fix that you mentioned above?? Thanks!
panoramix30 said:
hi guys! i've got the same problem, can't change the kernel in my i9300.. could you please tell me where i can find the kernel fix that you mentioned above?? Thanks!
Click to expand...
Click to collapse
If your using the I9300, i would check the thread for that phone. Otherwise you risk bricking it flashing something from this one.. This is for the US Variant SPH-L710.
Go here for all the I9300 stuff, Please save yourself a bricked phone. Thanks! http://forum.xda-developers.com/forumdisplay.php?f=1563
Will do, thank you!
Sent from my GT-I9300 using xda app-developers app
I use cm10 build 6, can I go ahead and pick a kernel to flash over the stock cm kernel?
Well the kernel you want must be compatible with the rom you are using and your device. For example if you are on CM10 you must flash kernels built for CM10/jelly bean. Otherwise you will get boot loops.
There might be some kernels for CM10 in the development section of Galaxy wonder.
Sent from my GT-I8150 using xda app-developers app
If kernel is for your Custom ROM that you have, you obv can.
flash the kernel that is exactly for ur ROM
kernel that is for CM10
kernel that is for CM9
dadat0 said:
I use cm10 build 6, can I go ahead and pick a kernel to flash over the stock cm kernel?
Click to expand...
Click to collapse
It's better to stay with the same Kernel, from my point of view, I guess if you shared with us why do you wanna change the Kernel, there might be a solution for your problem, a friend of mine Flashed a different kernel and it was supposed to be compatible, but still he had problems and he flashed everything back again.
I wanted to use other governors. Btw I flashed a new kernel and it seems fine as of now
dadat0 said:
I wanted to use other governors. Btw I flashed a new kernel and it seems fine as of now
Click to expand...
Click to collapse
Good for you, as long as everything is working smoothly, then good luck with the new Kernel:good:
is it really just limited by CM9/CM10? Like if I am using acro's cm9 RC6 and the kernel was released after RC7 was released, maybe some of the extra features in RC7 causes a slightly different coding for the kernel which of course may cause problems if you use it on RC6?
also i suppose there's no need for clearing data/cache, fixing permission etc when flashing kernel right?
sorry if I'm not supposed to ask questions in a question. I just feel this is relevant to the title and i feel that it is better when people can just read this post and learn more about kernels. The list of how-tos in the dev section has not much details on kernels
egagah said:
is it really just limited by CM9/CM10? Like if I am using acro's cm9 RC6 and the kernel was released after RC7 was released, maybe some of the extra features in RC7 causes a slightly different coding for the kernel which of course may cause problems if you use it on RC6?
also i suppose there's no need for clearing data/cache, fixing permission etc when flashing kernel right?
sorry if I'm not supposed to ask questions in a question. I just feel this is relevant to the title and i feel that it is better when people can just read this post and learn more about kernels. The list of how-tos in the dev section has not much details on kernels
Click to expand...
Click to collapse
Nope no problem at all. You can even flash R7 kernel on every previous version of arco cm. as long it is for the same android version
No need to do that. But just to play everything save it is better to do wipe cache and dalvik no need to wipe data
Sent from my HTC Sensation using xda premium
reddvilzz said:
Nope no problem at all. You can even flash R7 kernel on every previous version of arco cm. as long it is for the same android version
No need to do that. But just to play everything save it is better to do wipe cache and dalvik no need to wipe data
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
just adding on to your post, i've tried flashing hurtsky's 2.2 fixed without wiping anything, not a single problem =)
egagah said:
just adding on to your post, i've tried flashing hurtsky's 2.2 fixed without wiping anything, not a single problem =)
Click to expand...
Click to collapse
I don't say you "must" i just said to play it save. Is it too much if we try prevent something from happening better than facing it?
Not all phone are the same as your's sir. Sometimes other phone need to do that so that there aren't any problems with it.
Sent from my HTC Sensation using Xparent Green Tapatalk 2
This is just an extremely clean build based off of the Latest AOSP release. It's compiled with linaro. The only real differences from stock AOSP are that I added the embedded superuser. I figure that Android is such a good base to build other things off so of why not leave it be.
http://www.mediafire.com/?d5zo8s1g6ltm2bd
ill give it a run i been looking for a clean rooted stock with the superuser in the settings lol oddly enough no joke thankx
Do you think, I can install it on Maguro?
freezer2000 said:
Do you think, I can install it on Maguro?
Click to expand...
Click to collapse
No. Unless you don't mind not having data or voice/sms. Recovery normally fails on roms cross device on purpose.
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
No. Unless you don't mind not having data or voice/sms. Recovery normally fails on roms cross device on purpose.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
OP can you in that case do a maguro build too... I can be the tester
This is the simplest ROM op I've ever seen xD
nitsua98 said:
This is the simplest ROM op I've ever seen xD
Click to expand...
Click to collapse
BAHAHAHA, yeah I usually flash CM or AOKP for a week and then say screw it I just want to go back to AOSP. Once I get back to my computer this week it'll probably be rebased on Master. It's not a complicated thing. Simply AOSP builds with LatinIMEGoogle being the only difference. ThinkFree is in there too I believe.
freezer2000 said:
OP can you in that case do a maguro build too... I can be the tester
Click to expand...
Click to collapse
I don't have a GSM so I'm a little scurred about building for something that I can't test out myself. Sometime this week I'll have a ROM that's built off of the Master repo and I'll get the Maguro Proprietaries and build that if you'd like.
I may just build once and provide a flashable to add the CDMA or GSM Proprietary files depending on what the person needs.
doobie711 said:
BAHAHAHA, yeah I usually flash CM or AOKP for a week and then say screw it I just want to go back to AOSP. Once I get back to my computer this week it'll probably be rebased on Master. It's not a complicated thing. Simply AOSP builds with LatinIMEGoogle being the only difference. ThinkFree is in there too I believe.
Click to expand...
Click to collapse
So this is like baldwinguy's shiny rom but built with linaro?
This thread is dedicated to my CM11.0 builds that will be built whenever I get around to it which will be at least weekly.
When I build it, it's always synced to the latest CM source along with a few additional cherry picks that either add functionality or are bug fixes/improvements.
Download ROM
There are several gapps packages floating around. Since there are none at http://goo.im/gapps for Kitkat, I use these:
http://www.androidfilehost.com/?a=show&w=files&flid=10306
As of the 12/18 buid, ART works with Banks' Gapps listed above.
Mirror (thanks MBQ_ for hosting space):
http://mbqonxda.net/tiny4579/gnex/cm11.0
You can help MBQ_ with hosting costs by donating to him.
Credits/Thanks
CyanogenMod team for the ROM
IAmTheOneTheyCallNeo for his tips and GCCFreedom build script
sparksco for his optimized Sabermod GCC 4.7 and 4.8 toolchains
Features
CM11.0
Sabermod GCC optimizations and commits (ROM built with 4.8/Kernel built with 4.7)
TODO
Add goo.im update support and instructions to github repo
MMS fix?
swarlesbarkely said:
MMS fix?
Click to expand...
Click to collapse
I don't know. I didn't include any special fixes. Can you link a source for this fix?
If it's synced from the latest repos, I'd imagine it's included.
Sent from my Galaxy Nexus using Tapatalk 4
I think he is referencing this commit. To fix mms and the about phone being unknown in the settings.
underwaterjr said:
I think he is referencing this commit. To fix mms and the about phone being unknown in the settings.
Click to expand...
Click to collapse
I believe you're right. Guess it hasn't been merged yet. fitsnugly must have cherry picked it for his CM builds.
modernbummer said:
I believe you're right. Guess it hasn't been merged yet. fitsnugly must have cherry picked it for his CM builds.
Click to expand...
Click to collapse
Nope. I don't have it yet.
http://review.cyanogenmod.org/#/q/status:merged,n,z
It's been merged.
So theoretically MMS should work fine?
MMS fix was just merged today not that long ago
Thank you tiny, love your 4.2.2 in my main driver and can't wait to try this one
Sent from my Galaxy Nexus using Tapatalk 4
swarlesbarkely said:
So theoretically MMS should work fine?
Click to expand...
Click to collapse
The MMS fix wasn't merged as of the time I built earlier today so the initial build doesn't have the fix. The next build will have the fix though.
The tuna kernel doesn't seem to play nicely with the Sabermod toolchain. Whether I compile CM's or mine with the toolchain, it always reboots right when it's about to finish booting the ROM.
tiny4579 said:
The tuna kernel doesn't seem to play nicely with the Sabermod toolchain. Whether I compile CM's or mine with the toolchain, it always reboots right when it's about to finish booting the ROM.
Click to expand...
Click to collapse
Maybe you could apply this fix to your ROM? I flashed it on a different ROM and it fixed MMS along with other framework issues
http://forum.xda-developers.com/showthread.php?t=1840666&page=364
Scroll down a little and you'll see non flashable and flashsble zip
antwong45157 said:
Maybe you could apply this fix to your ROM? I flashed it on a different ROM and it fixed MMS along with other framework issues
http://forum.xda-developers.com/showthread.php?t=1840666&page=364
Scroll down a little and you'll see non flashable and flashsble zip
Click to expand...
Click to collapse
As soon as I flash a kernel again the reboots stop. Are you able to flash the ROM without flashing the kernel afterwards and boot fine?
Sent from my One using Tapatalk 4
tiny4579 said:
As soon as I flash a kernel again the reboots stop. Are you able to flash the ROM without flashing the kernel afterwards and boot fine?
Sent from my One using Tapatalk 4
Click to expand...
Click to collapse
I'm not running this ROM right now, waiting to get home for WiFi to download.
I was just suggesting a fix for MMS problems.
Installed this last night, been playing with it all morning.
No problems so far... performs just as well as Tiny's 4.2.2 ROM. In other words, I love it.
tiny4579 said:
As soon as I flash a kernel again the reboots stop. Are you able to flash the ROM without flashing the kernel afterwards and boot fine?
Sent from my One using Tapatalk 4
Click to expand...
Click to collapse
Flashing without a different kernel causes a bootloop to the CM account setup screen. Flashing with your kernel works fine.
Sent from my Galaxy Nexus using Tapatalk 4
modernbummer said:
Flashing without a different kernel causes a bootloop to the CM account setup screen. Flashing with your kernel works fine.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Yep. I'm going to switch kernel toolchains. Do people want CM's kernel or mine built in?
Sent from my One using Tapatalk 4
tiny4579 said:
Yep. I'm going to switch kernel toolchains. Do people want CM's kernel or mine built in?
Sent from my One using Tapatalk 4
Click to expand...
Click to collapse
I, for one, am fine with either one.