Hello,
I took the opportunity since no one bothered to develop an up2date kernel for HD+/Ovation to release it my self :highfive:
Since am developing this for Acclaim/Nook Tablet the code is 99% straight forward.
My kernel is kinda ...awesome imo always, so i thought it worth the trouble to bring it on our soul brothers forum
I might do a hummingbird/HD in due time but as if i had to buy 1 of these i would pick HD+ i compiled it for that one first.
As you already guessed i don’t own the tablet so i expect some feedback from you guys.
Special thanks to verygreen and Hashcode for making these omap4 babies part of cm11 family.
Kernel is updated all the way from 3.031 to latest 3.0101.
If you want leave some feedback in this thread +/- is all welcome and appreciated.
Source code is here:
https://github.com/Ntemis/android_kernel_bn_omap
You can take it and use it in whatever rom/project freely but please first have in mind to give appropriate credits. :good:
Download Link here:
http://d-h.st/Jsj
MD5 is: 464f41c00186d13c6af4df70c5e62bb5
And if you find my work useful there is a thank you button, use it! :highfive:
And the usual this stays mine thread
Any special features?
Sent from my PC36100 using xda app-developers app
Expect speed increase and better battery life too.
Στάλθηκε από το Barnes & Noble Nook Tablet μου χρησιμοποιώντας Tapatalk
Bexus
For me, coming from Succulents ROM, it hangs at the Cyanoboot screen and doesn't advance. I was able to reboot and enter TWRP to reinstall prior ROM. Appreciate the effort, something isn't quite right just yet.
so cool wait one for hd:laugh:
Hung at Cyanoboot for me, too. But I could not reinstall my old ROM. It kept failing. Had to install stock ROM but that doesn't want to finish booting, for some reason.
Sent from my SCH-I535 using Tapatalk
I built using your kernel and the standard cm source tree. It boots up fine and works fine. It is faster than stock. I find it about the same as succulent's kernel which is also 3.0.101 (https://github.com/succulent/android_kernel_bn_omap). I don't know why it doesn't seem to boot when flashed over other builds, maybe a difference in kernel headers? I didn't try just flashing your kernel but cloned your github instead.
Thre are now several different omap4 android kernels floating around. Some have lots of kernel.org patches for stuff we don't need (x86 etc). Some are more stripped down. Some are newer. Some old (and slow, like our 3.0.31 version). Some are train wrecks created by applying every patch out there. It's a shame that TI gave up around 3.0.72. The omapzoom kernel was a nice base to use. I wish I was better at kernels. Thanks for your work. I'll keep testing it.
Good try but does not work, hangs at boot loader
Stuck at cynoboot for me too.had to go back to cm 10 nightly after complete wipe.
Sent from my BN NookHD+ using xda app-developers app
Stuck here as well
Unfortunately it hung at cyanoboot for me as well. @Demetris do you want a last kmesg?
Edit: forgot to say I was running an official cm11 nightly when I tried it out.
finally a custom kernel for our nook hd+ ??? cool
I was really excited to try this after your kernel totally rocked my original NT, but I didn't have much luck, sadly.
Just hung on CM logo. Flashed over a CM11 nightly (022114). Restored CWM backup, so no big deal. Just depressing.
Wish you had one of these - must be hard to write ROMs for a device that's not in front of you.
Sent from my Samsung Galaxy Note 2
I"all see what I can do about it.
Sorry for the delay guys, not enough free time lately
Sent from my LG-P880 using Tapatalk
Yup no go bootloops
Can someone compile a CM11 package till Demetris fixed it?
I haven't set up a building environment yet, else I would've done this...
Jann F said:
Can someone compile a CM11 package till Demetris fixed it?
I haven't set up a building environment yet, else I would've done this...
Click to expand...
Click to collapse
Just an FYI, I built this with PAC and it still hung at Cyanoboot.
DarkStarr said:
Just an FYI, I built this with PAC and it still hung at Cyanoboot.
Click to expand...
Click to collapse
Ok, thought I may have done something wrong, compiled it with recent CM11 and it hung...
Related
Important!
It is strongly recommended that you flash clockwork recovery via NVFlash. If for some reason this or a future nightly build causes your phone to not boot up, you will not be able to boot into recovery unless you have it flashed via NVFlash.
NVFlash for Linux
NVFlash for Windows
To clear up some confusion, if you flashed your recovery via ROM Manager, you didn't actually flash a recovery. It is what we call a fakeflash, you should still probably flash with NVFlash.
Instructions
Download from http://download.cyanogenmod.com/?device=p999 and flash like you would any other ROM (via recovery or ROM Manager).
Be sure to backup before flashing, and of course a wipe is necessary when coming from stock.
Gapps are available from the usual places, however do not download the version that says it is for Tegra, even though this is a tegra device, as it will not flash.
Mod Edit:
Mikey1022 said:
Google Addon: http://goo-inside.me/google-apps/
Check the lastest package available on top
Click to expand...
Click to collapse
ChrisSoyars Edit:
After skimming some of the posts in this thread, here are some things that you can expect.
What to expect
- Everything working including Wifi, GPS, Audio, Camera, Front Facing Camera
- Screen off animation is not enabled, therefore it isn't broken.
- Occasional audio problems (as far as I know they have not been fixed). If audio does not play just reboot.
- Automagical brightness weridness, this is controlled by the kernel and not userspace, even having it working is very hacky.
Any reference to the first thread you need too look up, it's linked here:
http://forum.xda-developers.com/showthread.php?t=1058131
Changelog:
http://cm-nightlies.appspot.com/?device=p999
Thanks!!! Flashing
Is the server still down? The latest I see is 2011-5-25.
gamefreakgcb said:
Is the server still down? The latest I see is 2011-5-25.
Click to expand...
Click to collapse
I don't know whether it is still down or not, but yeah, that's still the latest build
Hrmm awesome, what about the battery stats? Anyone know if that has been fixed?
G2X & Nexus S
brian6685 said:
Hrmm awesome, what about the battery stats? Anyone know if that has been fixed?
G2X & Nexus S
Click to expand...
Click to collapse
Not on cm7 but Faux has made good progress with the help of debauchedsloth
So does this mean nightlies will resume soon?
edit, nvm oops
G2x with faux AOSP and faux orange kernel. [email protected] 5107 quadrant.
For anybody interested this is a build I just compiled about an hour ago
http://www.multiupload.com/6WEZDZMGSX
WHy a new thread? what is new?
aim1126 said:
For anybody interested this is a build I just compiled about an hour ago
http://www.multiupload.com/6WEZDZMGSX
Click to expand...
Click to collapse
How is your compile different from the gigglebread one from this morning?
jawknee530 said:
How is your compile different from the gigglebread one from this morning?
Click to expand...
Click to collapse
I dot think there's any really maybe one or two commits that got merged throughout the day. I just like compiling my own builds
Sent from my LG-P999 using XDA App
I see this thread kinda senseless as there isn't a newer nightly that was available before using the old thread. Although 2 pages seems more manageable then 300+ (which will happen eventually to this thread.)
Being a website developer I know these threads add up pretty quickly (hurray xda!)
I haven't flashed an actual CM rom in almost a week since the server crash. Hopefully the new thread is a sign that the server was repaired and new nightlies are on the way. Using the latest KANGS to get my fix, I know there is lots of progress. Running the latest KANG from today I think the rom is almost ready for a stable release after a few bugs get worked out.
I think the work you guys are doing is fantastic and much appriciated, although it may seem all we do is ***** half the time. Android wouldn't be the same without all of the developers leading the way. Big props. Hope all is well and I plan to continue to follow your work.
aim1126 said:
For anybody interested this is a build I just compiled about an hour ago
http://www.multiupload.com/6WEZDZMGSX
Click to expand...
Click to collapse
Just installed, cheers!
And thanks CM, I'm coming from #34 and just five minutes in its obvious there's been quite a bit of work done. Status Bar brightness slider is sweet.
i see a build 36 but it won't let me download? says its not found...
shniggies said:
i see a build 36 but it won't let me download? says its not found...
Click to expand...
Click to collapse
Probably still being built. Give it some time and check again.
Sounds like buildbot may be back up... this would be nice. <3
reisaru said:
Probably still being built. Give it some time and check again.
Sounds like buildbot may be back up... this would be nice. <3
Click to expand...
Click to collapse
ho ho... i must have checked riiiiiiight when it was uploading... because its downloading now
How did you find build 36 when 35 isn't out yet?
Sent from my LG-P999 using XDA App
Andromadus - Test Builds
To start with here you will find test versions of ROMs built by me from the Andromadus github repo http://github.com/Andromadus, think of them along the same concept as nightly builds just not every night These are development ROM's, if you want to run bleeding edge development ROM's and at least know how to use adb and logcat then you might find something of interest here. If you require something that works 100% of the time all of the time then this might not be for you. That said you can always give it a try and if it doesn't work restore your previous nandroid backup!
What IS Andromadus?
Initially it was a group of people who got together to make ICS work on the HTC Desire Z because nobody else seemed to want to support devices with physical hardware keyboards/trackpads. Whilst the idea stays the same It has grown slightly to support some other hardware and some of the work we have done is now used in many other devices. Andromadus builds of CM10 or CM10.1 are basically CM sources with a few additional tweaks or additions to support our phones.
1. New versions will be added as and when I feel there are enough changes to warrant one, don’t ask when the next version is coming.
2. If we decide to release a "Stable" version of these roms they will be published in another Andromadus thread.
Direct all your queries with release versions to that thread and in the same vain do not discuss these releases anywhere but here.
3. I will do as best I can to answer questions but if you don't get an answer from me I'm sure somebody else will be along to help. Help each other and I have more time to spend fixing things!
4. Don't ask for what's changed since the previous version, have a look at the recent submits on the Andromadus github if you want to know or wait for the mini changelogs when I post a new release.
5. If there is something in particular to test it'll be mentioned!
6. As always if you didn't wipe between installations then at least verify that the problem exists on a clean install before posting here. Nandroid/superwipe/install/check at the end of the day you can always restore your nandroid if the problem is reproducible on a clean installation. If you can't be bothered to try this then I really can't be bothered to try to help you :>
7. All that said ensure you make a nandroid/backup before hand. I take no responsibility for what you do to your phone with these ROM.
8. Whilst I can't stop you I would rather these builds were not used as a base for any ROM/MOD/ETC. The source is all available if you want to do your own builds with which you can do whatever you like.
9. Tell us what works/what's worse/what's better but don't ***** when something breaks or isn't fixed yet, report it and move on.
10. Sometimes people forget that we do this for fun, for ourselves, and sometimes your super important issue is way down on our personal list of things to be fixed.
If you ignore any of the above you will in turn be ignored.
Now that's all out of the way as always have fun
As usual you need to flash the ROM then GAPPS.
Checkout http://andromadus.flinny.org for links/files/previous changelog's
This a team/community effort, I'll not list everyone who has helped along the way here that list is in the beta thread but I will say thanks to all of them again and obviously anyone that has been missed.
Current Version changelog
CM10 build 133
There was an issue with the backup tool in the last build that will break gapps and your account's etc when flashing this build, the solution is to re-flash gapps at the same time as the rom and you should be fine. This build should fix it so that the next build will work as it should
Changes.
Synced with CM - Again not many changes upstream.
Basically everything relevant to our phones up to the 4th of February in the following has been merged
http://review.cyanogenmod.org/#/q/status:merged+branch:jellybean,n,z
Kernel updated to Andromadus Current - 3.0.62
might need this
First
Its Awsome, Running it since last 3 days
Great
And maybe I didn't go to sleep. Maybe
Sent from a device waiting for the Kernel 3 source code. WAKE UP HTC !!!!!
I get one more rom to base..
BTW my camera fix can be a temp fix for camera
Great :good:
- EDIT -
Wait ! Does It Says Kernel 3
the camera issue atm is kernel, i dont think it will help your fix, you can try...
Edit:
Yeah, it says kernel 3
Yup, this ROM is based off the kernel 3 source by Andromadus. Who needs HTC?
Sent from a device waiting for the Kernel 3 source code. WAKE UP HTC !!!!!
Woah?! I thought i was in the wrong section for a moment! Great work!
Alternative upload than goo.im?
What the HELL!? Superkid is back, with Kernel 3!
Does I understand it right, that this is a real Kernel 3 compiled for desire s? Not a port? From wich source?
Unbelievable!! Will testing right now!
Andromadus team took the primou source and changed it to work with our device
Guys, remember, its all on alpha/beta.. kernel and rom!
After all, is the first aosp rom with kernel 3 for saga
Is the jerkiness normal? I flashed over CM10. Will a full wipe fix it?
Sent from my Desire S using Tapatalk 2
Good job man! Keep it up!
Iztipkano sa Dizajr S BRE!
Nice
Nice!
The third JB Rom.
I MUST try it!
But I need my cam. So if this work I will flash it.
Source of kernel released :
http://forum.xda-developers.com/showthread.php?p=29552861#post29552861
https://github.com/Flemmard/htc7x30-3.0
have fun and push fixes!
My congrats on that Rom.
I have a little Problem with play store...my apps arent there and bought Jones are like not bought.
Other than that.....
WOW
Sent from my Desire S using xda app-developers app
Guss one of the legends is back.........with a bang working his magic.......
Sent from my HTC Desire S using xda premium
dan-fish said:
Is the jerkiness normal? I flashed over CM10. Will a full wipe fix it?
Sent from my Desire S using Tapatalk 2
Click to expand...
Click to collapse
You can try.
This is because the kernel 3 is not optimized yet
Tapatalked from a Desire S waiting for Kernel 3 sources. WAKE UP HTC!!!!!!
The first Kernel 3,:good:,thanks
OMG!!! Kernel 3... That's cool.
Must be a tremendous amount of work by the dev.
Thx to dev and superkid. :good:
So I've given up on working on ROM's as last time I learned C, the internet didn't exist and it was all UNIX and I too many beers have made my forget all of it, but I've been playing around with porting.
I've tried the automated tools, the only guide for our phone is very old and deals with Froyo, so does anyone have any tips? I tried posted an Si9000 Remics touchwiz S4 based ROM to our phones, and it boots to the lockscreen, data/wifi is enabled, there is a signal but after 5 seconds it reboots to the bootlogo again and stays there. A reboot, does the same thing, I can see the S4 lockscreen/background/connection is fine, then reboots. Any help ideas or better ways to port to our phone? I've been working off Airflip's CM 10.1 with aries, which should help as most other S based ROM's are CM 10.1 and aries based, just can't figure out the bootloop.
Hi getochkn
I've had some tries with MIUI JB and HellyBean and also reached up to this point.
I used no automated tools and be happy to hear about such.
I swapped the regular files and performed "Beyond Compare" on all framework classes, adding the missing lines from the source CM (but I used Erik's CM with no aries then).
I think at this stage it's just a matter of logcats, but yet again I did not get beyond that.
Wish I could help you...
I have been trying for a month
to port ProvisionMod.
I am almost at the same spot.
It boots to the lock screen for maybe 3 seconds.
Then goes back to the boot ani..
Using Beastmode's CM 10 as base.
I have tryed automated and manual porting guides.
Its close but a no go..kinda stuck now.
It will be interesting to see what responses
are to your call for help..maybe help for all 3 of us.
Good Luck..I hope you figure it out..
Sent from my Nexus 7 using xda premium
Least I don't feel so alone with others getting the same results. lol. Time for some googling and testing and playing around I guess. I like the Remics/Ultragen fully Sammy themed ROM's, so that's my goal. Tried with a SI9000 and a Vibrant one and get either boot animation and nothing or the lockscreen flash for a few seconds.
Maybe Dau can chime in when he's around, as he has ported all those ROM's to ICS before, so maybe he can offer some tips/hints/etc.
Thank you guys for making an effort.
Erik builds it from source, so it is irrelevant I think. Dao gave me some ideas but I didn't get much further. We should form a new team - Team Frustration
I started a mobile application development course and once i finish it (in a few months) i will start messing with kernels, building from source and all that sheet, so I can promise you I will be around for a long long time, no intentions to trade this beauty.
sent from me
Ya, I was so happy when I saw the lockscreen bootup with signal, thinking I had a 4.2.2. Remics working with all the S4 goodies until it rebooted. lol. Now I can't even get a port to do that again and just get stuck at the boot logo. lol.
Going to keep googling and plugging away though and see what happens.
itzik2sh said:
Erik builds it from source, so it is irrelevant I think. Dao gave me some ideas but I didn't get much further. We should form a new team - Team Frustration
sent from me
Click to expand...
Click to collapse
LOL...Thats a good one..
how about Team Bootloop
Sent from my Nexus 7 using xda premium
Team CPU - Common People Unified...
Had another bootloop attempt last night, but can't get ADB to connect during that time, so can't get any logs to know what's doing it. Still going to look into things more. For now, just been collecting S4 things and integrating them into CM 10.1 by hand and manual pushes and then screwing up and starting over, but right now have a Touchwiz 5 based CM 10.1, with Touchwiz launcher, icons, Transparent Acuweather widget that works, S4 sounds, Ringtones, Wallpapers, few of the other Sammy Apps, etc. It's a learning process, but I'm enjoying it anyways.
23 different port attempts, flashes, guides, nothing. lol.
I think I'm going to install the stock ROM, and the ROM I want to port and just push the files manually bit by bit to see whats causes the crash and then undo it in recovery, and go from there and see what why those files are crashing or bootlooping it. The Remic JB v5 is the closest, I can get the lockscreen up, unlock it, get to the homescreen or an app, and then reboot, so I'll try with that one just doing a bit at a time over a running ROM and see what happens.
Try using my beanstalk kernel it should have debugging from boot as its an insecure kernel get some logs and post thrm here
Sent from my SCH-I545 using xda app-developers app
Beastmode said:
Try using my beanstalk kernel it should have debugging from boot as its an insecure kernel get some logs and post thrm here
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Thanks, that may help a lot. It's so frustrating to see the lockscreen, it boots, it loads, you get an app started, then you get the boot logo booting again, it's like soooo close. lol.
Thx, your kernel worked, and the logcat just stops itself right before the reboot. Here is the logcat though from boot till it stops itself.
http://pastebin.com/rYxwE210
EDIT: After the first boot and that log, ADB won't even connect anymore.
Ahh, i'll look into your github source, but I never remember what I need to enable in config to get insecure kernel.
---------- Post added at 08:50 PM ---------- Previous post was at 08:16 PM ----------
edit: still don't know how to make insecure boot image, can someone help?
airfluip1 said:
Ahh, i'll look into your github source, but I never remember what I need to enable in config to get insecure kernel.
---------- Post added at 08:50 PM ---------- Previous post was at 08:16 PM ----------
edit: still don't know how to make insecure boot image, can someone help?
Click to expand...
Click to collapse
ro.secure=0
Sent from my SCH-I545 using xda app-developers app
Since Erik posted the full source for herring CM10 so if u want it, u can build it actually, it would be not so hard because this RemICS is just an overlay-on-top-of-CM ROM so all u have to do is syncing exactly the Cyanogen Mod 10 n apply the overlay patch on top of it, look at here for more info: https://github.com/blackmamba97/Remics-JB-Overlay Switching between aries and herring is just a matter fact of addition ~500MB for kernel and vendor n device tree source so just try it w herring first.
Beastmode said:
ro.secure=0
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
I got that, but where do i put it?
Default.prop?
TwitchyEye said:
Default.prop?
Click to expand...
Click to collapse
yep yep exactly
*** Latest Build 10-11-2013 ***
For d2vzw! Note the forum you're in!
If you're as big of a fan as I am of KToonsez's KT747 kernel then you'll be happy to know there is now an updated version.
This is a forked version of KToonsez's KT747 kernel with commits pulled from the CM10.2 branch of the d2 kernel.
Disclaimer: Standard disclaimer goes here. I nor KToonsez are responsible for the actions you take when working with your phone. I've done a significant amount of testing and so have others but situations arise where a hiccup could cause data loss, IMEI loss, or phone failure. You, the flasher, assume these risks. Please make sure you backup/nandroid, use nvbackup, etc.
Note:
It has been reported that this kernel will not work with 4.3.1 ROMs, notably the latest nightlies of PAC-MAN. If you're on a 4.3.1 ROM flash with extra caution. If you find otherwise please alert me.
Branch "currentCherry" (my cherry picking branch) CI status:
Branch "mr2" (KT's 4.3 branch) CI status:
Instructions:
There seems to be an odd permissions issue that we've uncovered. Follow these exact steps so when you boot you'll have working cell data:
Reboot Recovery
Clear Caches
Flash your current ROM
Flash kernel
Reboot
Profit!!!
I'm working on clearing this up. I've verified the above process against mastamoon's unofficial CM10.2 10/07 build.
Download Link:
10-11-2013
A big thanks to shane269 for helping me test this from a bootlooper to working kernel!
Thanks!
KT747's sources can be found here:
https://github.com/ktoonsez/KT747-JB
Visit the official KT747 thread here:
http://forum.xda-developers.com/showthread.php?t=1853816
Visit kt's original, ORIGINAL kernel thread here:
http://forum.xda-developers.com/show....php?t=1756776
Also if you like this kernel then please consider donating to the dev that made it all happen, ktoonsez: http://forum.xda-developers.com/donatetome.php?u=4325945
Previous Builds
10-10-2013
10-09-2013
XDA:DevDB Information
KT747 For D2VZW Cherry Picked, a Kernel for the Verizon Samsung Galaxy S III
Contributors
mikejr83, KToonsez
Kernel Special Features: KT747 kernel with latest CM10.2 commits
Version Information
Status: Beta
Created 2013-10-09
Last Updated 2013-10-16
Change log:
-10/11/2013
* Merged the commit for touchscreen optimizations
* Cherry-picked commit for reverting portions of the touchscreen optimizations which may cause us camera issues.
* Changed updater-script to hopefully resolve issue with no data after flashing (still researching issue)
First?
Looking forward to this
tapped from a carbonized d2vzw
ktoonsez gave the OK. Download link is now up. Please follow the instructions or you'll get no data. If you accidently goof and do this just reflash your ROM and then in the same session flash the kernel.
Thanks!
Mike
Thanks for this I've been using this without issues pacman ROM.
Sent from my SCH-I535 using Tapatalk 2
Just flashed on Slim 1.6 weekly and set my kernel settings. No initial issues, thanks for the update. I was going through kernel flashing withdrawals.
Sent from my SCH-I535 using Tapatalk 4
Well @mikejr83 so far so good, thanks for the update!
sent from a custom s3 powered by pacman, ROM ,KT747 kernel w/mods by team kernelizers ,themed by blackout1911,Pimped by the candyshop, and modded by all!
Is anyone not seeing OC working? I have mine set to 1728 but I'm still seeing 1510 in BBS.
Sent from my SCH-I535 using xda app-developers app
mikejr83 said:
Is anyone not seeing OC working? I have mine set to 1728 but I'm still seeing 1510 in BBS.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I normally don't overclock my phone doesn't do well with it. I tried 1728 and it wasn't ever using it. Then I bumped it up to 1809 and it instantly rebooted. As expected, my processor just won't do it. After the reboot the phone was still set at 1728 and it was using that frequency. So maybe requires a reboot work?
Sent from my SCH-I535 using Tapatalk 2
Rebooting seems to make it stick or show up in the apps where I see freq values.
Sent from my SCH-I535 using xda app-developers app
OP Updated
Went through my cherry pick branch and realized I missed some commits. I missed about 2 days worth of merges at the end of August. These are now all added.
There is a gerrit reviewed commit for touchscreen optimizations (and a subsequent fix for camera issues). I'm having trouble merging this commit into my branch. I'll try to get that into the build for tomorrow.
Thanks!
Mike
Can I ask why there is a unofficial version of KT kernel? Did he drop support for s3?
Followed instructions to the letter and re-attempted 2x and still getting no data when running this kernel. Running liquidsmooth 2.10 final release. Thanks!
Rinkle McBally said:
Can I ask why there is a unofficial version of KT kernel? Did he drop support for s3?
Click to expand...
Click to collapse
He's just been really busy and this guy wanted to put a more recent build out since there have been many commits to cm 10.2
Sent from my SCH-I535 using Tapatalk 4
---------- Post added at 06:20 AM ---------- Previous post was at 06:19 AM ----------
Are we able to flash the kernel separately yet?
Sent from my SCH-I535 using Tapatalk 4
no cigar said:
Followed instructions to the letter and re-attempted 2x and still getting no data when running this kernel. Running liquidsmooth 2.10 final release. Thanks!
Click to expand...
Click to collapse
Shoot! Ok. Just want to ask a couple of questions to make sure I'm on the same page and I can collect some info to try and figure this out.
10/10 build? Probably a silly question since you posted after I posted the new build, but just checking.
Are you using CWM? If you are what version?
Just to be clear, are you flashing ROM and then the kernel in the same recovery session?
I'm not familiar with liquidsmooth. Is the 2.10 release version 4.3 of Android? I'm assuming it is otherwise you probably would have gotten a bootloop instead of no data.
Thanks for the feedback. It's important that I see these. I've been worried sick that there are people downloading this, having this problem, and immediately thinking that I through out something that is bunk. I want this effort to live up to the expectations that everyone has for KT's kernel. Last thing I want to do is turn people off to his great work!
jamminjon82 said:
He's just been really busy and this guy wanted to put a more recent build out since there have been many commits to cm 10.2
Sent from my SCH-I535 using Tapatalk 4
---------- Post added at 06:20 AM ---------- Previous post was at 06:19 AM ----------
Are we able to flash the kernel separately yet?
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
I was able to flash 10/10 over 10/09 without having to flash the ROM and still have data. I have not gone from sans KT to ROM with KT on the 10/10 build.
I'm going to try to get some input from some devs. I originally thought it was the updater-script applying the wrong permissions during the flash. I did, however, change the script to mimic more how LeanKernel does its flash but that fix was put in 10/09. This along with the touchscreen fixes are my top priorities to get fixed.
See responses below. Thanks!
mikejr83 said:
Shoot! Ok. Just want to ask a couple of questions to make sure I'm on the same page and I can collect some info to try and figure this out.
10/10 build? Probably a silly question since you posted after I posted the new build, but just checking.
Yep 10/10 for sure.
Are you using CWM? If you are what version?
Yes. 6.0.4.3
Just to be clear, are you flashing ROM and then the kernel in the same recovery session?
Yes, all in the same session
I'm not familiar with liquidsmooth. Is the 2.10 release version 4.3 of Android? I'm assuming it is otherwise you probably would have gotten a bootloop instead of no data.
Correct. I'm running android 4.3
Thanks for the feedback. It's important that I see these. I've been worried sick that there are people downloading this, having this problem, and immediately thinking that I through out something that is bunk. I want this effort to live up to the expectations that everyone has for KT's kernel. Last thing I want to do is turn people off to his great work!
I was able to flash 10/10 over 10/09 without having to flash the ROM and still have data. I have not gone from sans KT to ROM with KT on the 10/10 build.
I'm going to try to get some input from some devs. I originally thought it was the updater-script applying the wrong permissions during the flash. I did, however, change the script to mimic more how LeanKernel does its flash but that fix was put in 10/09. This along with the touchscreen fixes are my top priorities to get fixed.
Click to expand...
Click to collapse
Eclipse build 6
I flashed the new version 10/10 on my Eclipse build 6 which is 4.3. I cleared cache, flashed rom, flashed kernel, and rebooted. No data at all. I then flashed the rom back over the top to get the other kernel and everything is fine. I am using the newest CWM.
Quie2TP said:
I flashed the new version 10/10 on my Eclipse build 6 which is 4.3. I cleared cache, flashed rom, flashed kernel, and rebooted. No data at all. I then flashed the rom back over the top to get the other kernel and everything is fine. I am using the newest CWM.
Click to expand...
Click to collapse
^
SAME
New build in the OP.
Also, changelog is in the second post.
no cigar said:
Followed instructions to the letter and re-attempted 2x and still getting no data when running this kernel. Running liquidsmooth 2.10 final release. Thanks!
Click to expand...
Click to collapse
Quie2TP said:
I flashed the new version 10/10 on my Eclipse build 6 which is 4.3. I cleared cache, flashed rom, flashed kernel, and rebooted. No data at all. I then flashed the rom back over the top to get the other kernel and everything is fine. I am using the newest CWM.
Click to expand...
Click to collapse
grislieber said:
^
SAME
Click to expand...
Click to collapse
Thanks for the reports guys. Researching this issue is proving difficult as no one seems to have documented it in the "usual" places. The only suggestion I have so far is checking to make sure the permissions are correct on everything that is flashed. I took a look at a couple of other kernel dev's updater-scripts and tried to modify this one accordingly. Flashing from 10/10 to 10/11's still gave me working data. I'm trying to follow up with a few other devs so please don't think that I'm not working on this. If you flash 10/11 please report your findings!
Thanks!
OmniROM Unofficial Builds
As you all know, OmniROM has been announced yesterday. This brand new ROM contains a lot of new, exciting functionality. One of these new functions is the multi-window support! Just like ROMs on some Galaxy Notes, or the ancient Cornerstone, you can run two applications simultaneously! Aside from that, the best thing about this ROM is the focus on the community: while the ROM itself is not available yet, the developers behind it really seem to be willing to listen to the community, which is a really good thing.
As the team of OmniROM states on their website:
Omni is what custom ROMs used to be about – innovation, new features, transparency, community, and freedom. We offer you an alternative to other ROMs that may choose to water down their distribution at the expense of providing options for the user.
Click to expand...
Click to collapse
And the list of features as listed by XpLoDWilD in this topic:
Flippable Quick Settings
Roadrunner mode
Multi-window(!)
Daydream enhancements
Integrated Performance Control
Multi-workspace
Color-changeable, 3D depth Phase Beam
And a bunch more
Click to expand...
Click to collapse
Unofficial builds
However, builds are not available yet. Logically, the ROM probably has not been thoroughly tested yet and that's why they are not building their source on a nightly basis. If you are as impatient as I am, you probably want to get your hands on this ROM as soon as possible! That's why I compiled OmniROM from source, for the Nexus 7 (grouper).
This flashable ZIP has not been tested yet by myself, but it should be OK. Compiled on Ubuntu 13.04 x86_64, completely as-is from the repository of OmniROM. Let me say again that this ROM is not modified by me; it is directly compiled from source and packaged into a ZIP. All credits go to the team behind OmniROM at http://omnirom.org.
Downloads
The builds below will probably be updated about every three days. I recompile from source whenever significant modifications are added to the multi-window functionality.
16/10 (working fine, with multi-window)
custom_grouper-ota-eng.chaoszx.zip (145.9 MB)
https://mega.co.nz/#!yEsHkDSa!PtTVqVPcvFY3FqP20M-1Vnq87rkVMPKJJ4aPuJA0IH8
14/10 (does not boot):
omnirom-4.3-20131014-NIGHTLY-grouper-unofficial.zip (138.7 MB)
https://mega.co.nz/#!HVF3DDAY!FveJvAE2Wffm2WNcezemTAwHYAleOKf13-zg82cZ118
Thank you
If you appreciate the time I spend to compile these ROMs from source for you, a donation would be appreciated as it would cover a bit of my expenses on power. Aside from that, I am hoping to save some money before I go to university next year, so any donation is much appreciated! PayPal donations can be sent to [email protected]. Thank you in advance for your support.
Notes
Multi-window can be activated by opening an app. Then go back to the launcher by pressing Home. Load up another app. Press the Multitask button, long-press the app you opened previously, and hit 'Split View'.
The Back button is not working at boot. To fix it, go to Settings > Language and Input > Default (under Keyboard & Input Methods) > Google Keyboard. The force closes of the AOSP keyboard won't happen now, and your Back button will work fine.
Reserved.
Reserved as well.
Flashing failed :/ Will try again.
Hypercaine said:
Flashing failed :/ Will try again.
Click to expand...
Click to collapse
Hang on, I am about to flash it on my Nexus 7. If it doesn't flash, I'll check what's wrong and fix it within an hour
Flashing right now, this is gonna be great!
Sent from my SCH-I535 using xda app-developers app
FAILED
set_perm: some changes failed
E:Error executing updater binary in zip ´/sdcard/
Error flashing zip
Same problem here
Confirmed that there is something wrong. Hang in there guys, working on a solution as we speak
chaosz-x said:
confirmed that there is something wrong. Hang in there guys, working on a solution as we speak
Click to expand...
Click to collapse
f5...f5...f5...f5...f5...f5...f5...f5...f5...f5...f5...f5...f5...f5...f5...f5...f5...f5...
The issue with the flashing is resolved. Before uploading the new ZIP, I am investigating the ROM itself. Check back in about an hour at least
Eagerly waiting
Sent from my Nexus 7 using XDA Premium HD app
Chaosz-X said:
Check back in about an hour at least
Click to expand...
Click to collapse
This looks suspiciously like an ETA, if I ever saw one...
When installing, flashing failed. Also, upload to a site that is android-friendly? Mega is hard for me to use. Maybe mediafire?
Failed for me also.
Sent from my SCH-I545 using Tapatalk now Free
flash fails because it says tilapia,mako,flo/deb.........no grouper is mentioned
podagee said:
flash fails because it says tilapia,mako,flo/deb.........no grouper is mentioned
Click to expand...
Click to collapse
I take it you get a set_perm (status 7 error)? This has to do with the updater script trying to give permissions to a file that doesn't exist, it is relatively easy to resolve. I'll take a look once I get home. BTW, tilapia, mako and flo are probably officially supported, which is why they are mentioned, as this is an unofficial build, it isn't (yet) mentioned
Sent from my Nexus 7 using xda app-developers app
Grouper is mentioned in the post of OmniROM, Grouper is available in the device tree of OmniROM, and this build is meant for Grouper.
The ZIP has been corrected to flash correctly. It was doing some set_perms on non-existing files. Those issues have been resolved now. However, the ROM fails to boot for some reason. I don't know why it is not booting as this is a completely unmodified build. I am going to sync the repository again now and do a new build. This afternoon I'll have a new build to try.
Chaosz-X said:
Grouper is mentioned in the post of OmniROM, Grouper is available in the device tree of OmniROM, and this build is meant for Grouper.
The ZIP has been corrected to flash correctly. It was doing some set_perms on non-existing files. Those issues have been resolved now. However, the ROM fails to boot for some reason. I don't know why it is not booting as this is a completely unmodified build. I am going to sync the repository again now and do a new build. This afternoon I'll have a new build to try.
Click to expand...
Click to collapse
FWIW I'm having the exact same problem with my build....it won't boot. Using sources synced as of yesterday morning.
I'm also re-syncing to see if that helps.
Thank you for your efforts! Waiting to try it
God I hate this new ADB system in Jelly Bean. Only allows a logcat if you grant access through Android itself. But when your device doesn't boot, it is impossible to get live logcats atm. Still working on a fix and progress is being made though