AOKP 4.3 is here and I am back at it with SmoothAOKP builds! These are being built with the latest Linaro 4.7.4 toolchain with -o3 optimization flags enabled for that extra smooth taste =P I also sprinkle in the bleeding edge stuff that is being tested or simply parked at the AOKP gerrit. I always do my best to test these new features out before I do a release with them in place. I want to thank everyone who has been using these builds and have been great support in this whole crazy learning process and the awesome feedback I get from you. I have learned a lot and I am learning more all the time. Big thanks to Team Kang for giving us such an awesome ROM to begin with, the Linaro toolchain and -o3 optimizations are simply icing on the cake!
This is the final 4.3.1 build. NOT the final SmoothAOKP build. AOKP kitkat is an ever evolving beast and I am slowly getting back into doing work on it after being a BF4 addict for a while and spending time with the rents over the christmas holidays. Stay tuned!
Code:
[COLOR="Red"]*DISCLAIMER*[/COLOR] Flash my builds at your own risk. If you are able to flash this
your warranty is already void anyways. I will always test my builds before I
post them, but I am not responsible if your phone explodes into a thousand pink
unicorns and your mom gets pissed that they pooped all over the house.
I am not a "dev" (yet!) I am more of a merger/tweaker/builder aka Kanger. I
am taking AOKP's source code, pulling bits from AOKP's gerrit of unmerged
code and bits from other roms and merging to source. When you do run into
problems please let me know and I will try and help/fix to the best of my
ability. [B][U]DO NOT[/U][/B] take issues directly to AOKP or any other ROM I may have
pulled things from.
Features
AOKP 4.3.1 FINAL!
Built with the latest 2013.12 Linaro 4.7.4 toolchain
Google JB4.3 boot animation.
NOTE* If you see features removed from this list it is likely because they have been officially merged into AOKP.
Installation
Backup current ROM in recovery (I personally use TWRP 2.5.0.2)
Do full wipe. System/Data/Dalvik/Cache.
Flash SmoothAOKP build.
Flash 4.3 Gapps from HERE
OPTIONAL Flash Faux's kernel from HERE. m=mainline (stock) u=ultimate (overclocking)
What's Broke
Video Camera has been broke on AOKP 4.3 since september.
Data does not work on dev edition phones.
Thanks/Credits!
AOKP
CyanogenMod
BMC08GT for maintaining our device for AOKP
IAmTheOneTheyCallNeo For being more awesome at android than me, and willing to help out.
apophis9283 For generally being awesome help, and a new friend.
Optional Faux kernel settings
Faux has an awesome app on the play store HERE that allows total control of his kernel. Suggested settings for both perfomance and battery saving can be found HERE. I personally use battery saving settings with some other tweaks since this rom usually runs so smoothly anyways! My settings are below.
Code:
CPU Control
Max clock - 1.566 GHz
Min clock - 594 MHz
CPU Governor - Intellidemand
mpdecision - Off
Snake Charmer - On
Eco Mode - Off
Set On Boot - On
Voltage Control
Set on Boot - On
Global CPU Voltage -50 mv (the click apply global)
SOC Control
Set On Boot - On
C0 - On
C1 - On
C2 - On
intellidemand gov control
Up Threshold - 75
Boost Frequency - 0
Two Phase Freq - 1350000
Sampling Rate - 50000
Optimal Freq - 1566000
Synchro Freq - 702000
Set On Boot - On
GPU Control
GPU Governor - ondemand
GPU Clock - 320 Mhz (leave stock if you do 3d gaming)
GPU Vsync Toggle - On
Set On Boot - On
I/O Scheduler Control
I/O Scheduler (eMMC) - FIOPS
Readhead Size (eMMC) - 1024
Set On Boot - On
SDCard Entropy - off
Misc Control
Dynamic File Sync - On
TCP Congestion Control - Westwood
Thermal Control
Intellithermal - On
Recommended settings for all.
Z-Control
Set On Boot - On
ZRAM Disk size - 150 Megabytes
ZRAM Enable/Disable - Enable if you mult-task often
Clear VFS Cache After Boot - On
Auto FS Writeback Delay Mode - On
Swappiness - 100%
VFS Cache Pressure - 100%
Dirty Ratio - 20%
Dirty Background Ratio - 5%
Current Build
1/7/2014
MD5: 0d0b214532fa722c013d7098e6cc0bbc
smoothaokp_jfltevzw_jb-mr2_final.zip - 200 MB
* Don't forget to grab the 4.3 Gapps package from HERE.
* This is the final 4.3.1 build. Their are no extras or changes. Changes to jb-mr2 have long ceased on AOKP so this is it!
* By default network mode is set wrong, Needs to be manually changed to "CDMA+LTE/EVDO" for 4gLTE to operate. Has been this way since the many changes to telephony recently.
Looking for a previous build? Look HERE!
Reserved
Interesting will be flashing soon.
Sent from my SCH-I545 using xda app-developers app
Dope. I think a couple other people were putting out AOKP builds, but no one else was putting in the IR.
Sent from my SCH-I545 using Tapatalk 4 Beta
Chuckleb0ne said:
Interesting will be flashing soon.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Welcome, and hope you like it, I have some other things I am going to play with this weekend to build into this. Feel free to toss ideas around.
jova33 said:
Dope. I think a couple other people were putting out AOKP builds, but no one else was putting in the IR.
Sent from my SCH-I545 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I'm assuming the same jova33 from RootzWiki? to answer your question from there, the lockscreen wallpaper had been pulled out by AOKP.. there are replacements in the works I have seen on the gerrit. I will look into merging it if it seems stable. Ive figured out a few other things I want to try and incorporate this weekend anyways so I'll add it the list.
I've been looking for an AOKP build to come along since I was on the Galaxy Nexus. Thanks for this. Working IR is great.
Glad to be of service. I'm having a good ole time with this. My sleep schedule is suffering haha. I'm leaving a build to compile while I goto bed with some things I've been playing with today. So hopefully some new features to play with in the morning. If there is something you might like to see incorporated let me know.
Next up: Linaro toolchain!
Sent from my SCH-I545 using xda app-developers app
Working good here thanks dev
Sent from my SCH-I545 using Tapatalk 4
Just a correction, he's not the dev. You can compile AOKP from source. I would if I had something better than a cheap laptop. And people on XDA can be real a-holes about things like giving credit to the appropriate people.
OP, I've seen some of threads start off with, "FIRST OFF I am not the dev.... yada yada yada.... all credit goes too ......, I just compiled from source." Just because people get confused about who actually makes the stuff.
Edit: and thanks for putting these builds together, not many people are.
Sent from my SCH-I545 using Tapatalk 4 Beta
OP Updated with a new build with some new features to play with! Tested the features real quick. Except for the Quiet hours stuff, I will test when my gf gets home and I can use her phone to call/send txts to mine ect. I did not run into any problems.
Custom lockscreen wallpaper.
Toggles vibrate on click.
QuietHours AutoSMSReply && QuietHours Bypass.
Remove taps to enable dev settings.
jova33 said:
Just a correction, he's not the dev. You can compile AOKP from source. I would if I had something better than a cheap laptop. And people on XDA can be real a-holes about things like giving credit to the appropriate people.
OP, I've seen some of threads start off with, "FIRST OFF I am not the dev.... yada yada yada.... all credit goes too ......, I just compiled from source." Just because people get confused about who actually makes the stuff.
Edit: and thanks for putting these builds together, not many people are.
Sent from my SCH-I545 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yea, I should probably put something up in the disclaimer to that effect. BTW custom lockscreen wallpaper in today's build for you.
DaMadOne said:
Yea, I should probably put something up in the disclaimer to that effect. BTW custom lockscreen wallpaper in today's build for you.
Click to expand...
Click to collapse
FWIW, for those that read the OP its obvious that you're not claiming to have developed AOKP. Problem is, people don't read or people use the term developer loosely (not really a problem).
BTW, I just built my first CM build from source. I would love to pick your brain about linaro once you dive into it. I've started looking and reading but I believe you have more coding experience than I and your help would be appreciated.
Sent from my SCH-I545 using Tapatalk 2
mlin said:
FWIW, for those that read the OP its obvious that you're not claiming to have developed AOKP. Problem is, people don't read or people use the term developer loosely (not really a problem).
BTW, I just built my first CM build from source. I would love to pick your brain about linaro once you dive into it. I've started looking and reading but I believe you have more coding experience than I and your help would be appreciated.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Haha yea, it's pretty obvious. I did have to "fix" the "toggles vibrate on click", So I'm learning as I go
Absolutely, I spent a few hours sifting through outdated and/or misinformation on setting up the Linaro chain and modifying the build part of the source to actually build with it. I got it building but at least with AOKP there is quite a few things in the actual source that will need to fixed in order for it to compile without throwing a temper tantrum. I wanted to get some new things built in and tested so I reverted back to normal. It's on the list of things to do today or tomorrow.
So... Pretty sure I just ****ed myself with this one.
Tried flashing the ROM, got most of the way through flashing and all of the sudden it gave me a fail while flashing the partitions. Now it's stuck at the "Samsung" screen and wont boot at all. Pretty sure I have no way to get it into recovery.
Literally the first time I've ever had something happen like this.
GTX1 said:
So... Pretty sure I just ****ed myself with this one.
Tried flashing the ROM, got most of the way through flashing and all of the sudden it gave me a fail while flashing the partitions. Now it's stuck at the "Samsung" screen and wont boot at all. Pretty sure I have no way to get it into recovery.
Literally the first time I've ever had something happen like this.
Click to expand...
Click to collapse
which build did you download? check the MD5 of the the zip you downloaded and make sure it matched the posted MD5. It's always a good Idea to check just to be sure.
turn the phone all the way off.. pull the battery if you have to. hold power and volume up until you see the samsung logo then let go of power. and hopefully you will see the blue "reovery booting" in the corner.
EDIT: you can check MD5 with this tool HERE
DaMadOne said:
which build did you download? check the MD5 of the the zip you downloaded and make sure it matched the posted MD5. It's always a good Idea to check just to be sure.
turn the phone all the way off.. pull the battery if you have to. hold power and volume up until you see the samsung logo then let go of power. and hopefully you will see the blue "reovery booting" in the corner.
EDIT: you can check MD5 with this tool HERE
Click to expand...
Click to collapse
MD5 matched. I always check it. I have no idea why it failed-AND YOU ARE A MAGICAL PERSON IT FINALLY BOOTED INTO RECOVERY.
Oh my god. You have no idea.. I'm in the middle of downloading the original MDK ROM to ODIN flash it and then you give me that little tip with the power + volume up. Why have I never seen that before? I've only seen power + volume down for download mode.. Now I'm going to go ahead and power it off, take out the MicroSD, load that into my CPU and try and get the old AOKP ROM I running on it and see if that flashes.
GTX1 said:
MD5 matched. I always check it. I have no idea why it failed-AND YOU ARE A MAGICAL PERSON IT FINALLY BOOTED INTO RECOVERY.
Oh my god. You have no idea.. I'm in the middle of downloading the original MDK ROM to ODIN flash it and then you give me that little tip with the power + volume up. Why have I never seen that before? I've only seen power + volume down for download mode.. Now I'm going to go ahead and power it off, take out the MicroSD, load that into my CPU and try and get the old AOKP ROM I running on it and see if that flashes.
Click to expand...
Click to collapse
COOL! ill tell ya what.. its a crappy feeling when you are new to putting out builds and someone says something went wrong. ALWAYS have a full backup on your SD card of a working system. I have the backup of TouchWiz from just after rooting and flashing TWRP, as well as an AOKP backup from a few weeks ago, JUST IN CASE!
I just downloaded the 8/8 build and the 8/10 build from d-h.st and they both match the MD5 of the local ones in my build folder. I have flashed them all, so im assuming it was a fluke.. maybe something went wrong when it transferred it to SD.
DaMadOne said:
COOL! ill tell ya what.. its a crappy feeling when you are new to putting out builds and someone says something went wrong. ALWAYS have a full backup on your SD card of a working system. I have the backup of TouchWiz from just after rooting and flashing TWRP, as well as an AOKP backup from a few weeks ago, JUST IN CASE!
I just downloaded the 8/8 build and the 8/10 build from d-h.st and they both match the MD5 of the local ones in my build folder. I have flashed them all, so im assuming it was a fluke.. maybe something went wrong when it transferred it to SD.
Click to expand...
Click to collapse
So I just went through some crazy stuff in recovery. I think it's the recovery to be honest(TWRP 2.5.0.2).. I put BMC's 7-14 build back on the SD because that was what I have been running since 7-14 and it ran very smoothly without a single bug. I never updated because he lost IR support after 7-14(then I saw your post with the cherry pick from CM and I decided to give it a go). Anyways, I put 7-14 back on the SD card and loaded it up into recovery mode on my phone. I wipe data, cache, and dalvik being a little cautious and wanting everything to go alright.
Mid way through the flash of the ROM and it does the exact same thing that happened while flashing your ROM. Stated it failed flashing binaries during the partition or something like that, same thing that happened while flashing your ROM. I saved the recovery log to my SD this time and I can PM it to you if you would like. After that, I went into wipe and decided to wipe data, system, cache, and dalvik. I go back to flash the ROM again and give it another go.. This time it worked. Flashed GApps and it worked. Flashed the custom kernel I used and it worked.
Have no idea why it messed up twice on me with two different ROM's with the exact same error. Then all of the sudden after flashing system + factory reset it decides it's going to work. Crazy. Now I'm setting my phone up again and I don't think I'll be flashing anything for a while now.. 7-14 build has been nice to me. No bugs, IR support, good battery life.. Don't know why I tried updating in the first place.
This was too much drama for a Saturday afternoon.
GTX1 said:
So I just went through some crazy stuff in recovery. I think it's the recovery to be honest.. I put BMC's 7-14 build back on the SD because that was what I have been running since 7-14 and it ran very smoothly without a single bug. I never updated because he lost IR support after 7-14(then I saw your post with the cherry pick from CM and I decided to give it a go). Anyways, I put 7-14 back on the SD card and loaded it up into recovery mode on my phone. I wipe data, cache, and dalvik being a little cautious and wanting everything to go alright.
Mid way through the flash of the ROM and it does the exact same thing that happened while flashing your ROM. Stated it failed flashing binaries during the partition or something like that, same thing that happened while flashing your ROM. I saved the recovery log to my SD this time and I can PM it to you if you would like. After that, I went into wipe and decided to wipe data, system, cache, and dalvik. I go back to flash the ROM again and give it another go.. This time it worked. Flashed GApps and it worked. Flashed the custom kernel I used and it worked.
Have no idea why it messed up twice on me with two different ROM's with the exact same error. Then all of the sudden after flashing system + factory reset it decides it's going to work. Crazy. Now I'm setting my phone up again and I don't think I'll be flashing anything for a while now.. 7-14 build has been nice to me.
This was too much drama for a Saturday afternoon.
Click to expand...
Click to collapse
hahaha I feel ya on the drama. Yea, PM me the log just I can take a look. I can say that EVERY TIME I flash a new build I ALWAYS wipe system/cache/dalvik. that way the new build is flashing to a clean system partition. It still keeps my settings after flash because they are stored on the internal sd anyways.
Anyone able to add a yahoo email account on 8-10 build?
Don't know if it's me or the build or yahoo.
Sent from my SCH-I545 using Tapatalk 2
Related
I'm currently running cm7.1, and really love it. I'm also really curious about trying out the ics roms and don't know which one to try. has anyone run both? which one did you like most and why? also, if I do a nandroid backup, is that the same as a windows image backup? ...meaning I can reinstall cm7 and glitch kernel, then flash my nandroid backup and be right where I was before I changed anything?
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
Yes you can restore a nandroid like you said as long as you are on the same ROM.
This is kind of an opinion, but I prefer Teamhacksung, as it is clean and bug-free.
ok cool. sorry about being in the wrong forum at first. so one for team hacksung, anyone else? I just want opinions as I don't think I have the time to try all the ics roms right now
aokp is by far the most solid ICS rom. its more how cyanogen use to be....lots of options to customise. THS cm9 is vanilla, meaning barebones.
droidstyle said:
aokp is by far the most solid ICS rom. its more how cyanogen use to be....lots of options to customise. THS cm9 is vanilla, meaning barebones.
Click to expand...
Click to collapse
+10!
Sent from my SGH-I897 using xda premium
This subject is opinionated and the OP should install both for a day to determine what he likes better.
Personally I used AOKP for the last six months, Yesterday I switched to CM9 experimental Linaro Build.. In my views way better than aokp..
Gearrion said:
This subject is opinionated and the OP should install both for a day to determine what he likes better.
Personally I used AOKP for the last six months, Yesterday I switched to CM9 experimental Linaro Build.. In my views way better than aokp..
Click to expand...
Click to collapse
Why?
i have the infuse but i started off using aokp switched to cm9 its been about a month.. goin back 2 aokp as of now cm9 isnt like cm7, i like tweaking and customizing as much as possible and i love the navigation bar aokp has..
Ok cool I think I'm about ready to try some out. One last question, I keep seeing things about how it's not easy to got back to cm7 from ics? Can someone give me some insight on this incase I don't like ics? Something with the different file types? I also want to keep my eh03 radio if I do end up going back to cm7
I'm now a little confused, after reading the guide for installing ROMS, in particular the ICS ones, arent all the ICS Roms based on what is stated- MTD CM9? So is there a difference aokp vs cm9? I guess what would be the large differnces between any two for example? Different kernels?
---------- Post added at 04:49 PM ---------- Previous post was at 04:32 PM ----------
username8611 said:
I also want to keep my eh03 radio if I do end up going back to cm7
Click to expand...
Click to collapse
Here check out this link to the guide for Installing a Rom/CWM recovery/Root or going back to Stock. Go to the fifth section. You can revert to stock gingerbread with EH03 radio from any rom.
http://forum.xda-developers.com/showthread.php?t=1238070&highlight=odin
well i got impatient and went ahead and did it lol. i went with aokp 40.1 and devil kernel .79. the first try was a disaster, what seemed to work went straight to crash and reboot when waking from the lockscreen. i thought it was my oc i was messing with so i turned it back to stock volts and frequencies. low and behold it did it again but this time would not boot up, would not flash anything from recovery, would not format anything from recovery, it was totally bricked. i even tried reflashing cwm though odin and it was a no go.
finally after a few hrs of gathing info, i flashed the stock froyo rom and it unbricked it and i tried aokp again. this time i used aokp build 40, and devil kernel v.72 and everything is beautiful and works perfect, rock solid stability with 1200mhz multiplier oc, 110% fsb oc on liveoc totaling 1362mhz i think. the ics launchers suck and are laggy for me, i dunno why but go launcher is smoooootthhh and so is everything else on the phone. i cant find anything that doesnt work, im not regretting this or looking back at all, thanks a bunch for the help guys. im also pretty sure its snappier and quicker than cm7.2 was for me on my 1.3ghz overclock and glitch 13.1
username8611 said:
well i got impatient and went ahead and did it lol. i went with aokp 40.1 and devil kernel .79. the first try was a disaster, what seemed to work went straight to crash and reboot when waking from the lockscreen. i thought it was my oc i was messing with so i turned it back to stock volts and frequencies. low and behold it did it again but this time would not boot up, would not flash anything from recovery, would not format anything from recovery, it was totally bricked. i even tried reflashing cwm though odin and it was a no go.
finally after a few hrs of gathing info, i flashed the stock froyo rom and it unbricked it and i tried aokp again. this time i used aokp build 40, and devil kernel v.72 and everything is beautiful and works perfect, rock solid stability with 1200mhz multiplier oc, 110% fsb oc on liveoc totaling 1362mhz i think. the ics launchers suck and are laggy for me, i dunno why but go launcher is smoooootthhh and so is everything else on the phone. i cant find anything that doesnt work, im not regretting this or looking back at all, thanks a bunch for the help guys. im also pretty sure its snappier and quicker than cm7.2 was for me on my 1.3ghz overclock and glitch 13.1
Click to expand...
Click to collapse
try devil_0.85, this build works the best on my device.
droidstyle said:
try devil_0.85, this build works the best on my device.
Click to expand...
Click to collapse
will do, thanks
edit: im having a hard time finding that version, do you have a link?
http://android.encounterpc.com/stevespear426/tests/Devil3_0.85_fascinate_CFS_BLN_CMC_20120625.zip
username8611 said:
will do, thanks
edit: im having a hard time finding that version, do you have a link?
Click to expand...
Click to collapse
droidstyle said:
http://android.encounterpc.com/stevespear426/tests/Devil3_0.85_fascinate_CFS_BLN_CMC_20120625.zip
Click to expand...
Click to collapse
Is there a voodoo color version?
There is color options in the galaxy s settings menu.
Devil98.3AOKPMilestone6Test Fassy Unicorn!
XxStechxX said:
There is color options in the galaxy s settings menu.
Devil98.3AOKPMilestone6Test Fassy Unicorn!
Click to expand...
Click to collapse
ive seen it but was a little wary of it lol. for those wondering and addicted to voodoo color... at first i was worried i would loose the deep color and gamma control that i have with voodoo color, but the device color options do a really good job with it and there is a gamma control and it works great, no washed out colors or anything of that nature. im pretty hardcore on my vivid colors so i have the gamma maxed out minus a tad of green but it looks great.. to me.
for the guy who originally mention v0.85, so far its working great, cleared cache, dalvik, and ran ultimate kernel cleaning script then installed and it seems to be running great. the only thing now is the long term stability test, over a week ive had zero freezes FCs, or any issues with .72, i hope i can get this with .85. it seems a little snappier and nandroid is working again. thanks a bunch for the link, a few hours of searching for it and google still didnt help me. ill get back to everyone on the stability of it for me, running 110% fsb oc on nstools and slightly undervolted. im sure theres a ton of info already on other threads but ill still report back. thanks guys
edit: im still having issues with bln, is there a quick fix with it? it worked right away with my botched install of 40.1 and .79 kernel, witch was completely unstable, but now on 40, and .85 its still not working, any ideas? also on first boot from cold soft keys were unresponsive but seem to be working now. im not complaining as i know there are newer versions of the devil kernel but im trying to find a very good balance of functionality and stability.
Hello People,
This time i bring you a cm10 build from the man it self "Hashcode" for our beloved Nook Tablet.
He is the one who took at his shoulders the Kindle Fire kernel and rom development and skyrocket their sales(Amazon).
I think no more needs to be said about the awesomeness behind this developer but to show our appreciation for finding the time to compile a test release from Nook Tablet Git.
We all expect more to come from this great day forward but nothing is promised and we all need to give our feedback and report issues from this ROM in this thread.
SUPPORT
You get none. Zero. Zip. We obligate ourselves to providing nothing further. You are on your own and will have to help each other via this thread. This is provided “as-is”, and if you don’t like it... there is always stock and CM7.
New Rom Link:
http://goo.im/devs/Hashcode/acclaim/cm10/cm-10-20130123-UNOFFICIAL-acclaim.zip
Changelog:
- Added SIO and V(R) I/O Schedulers
- Sync with CM10 (a lot of changes)
- Disabled SR v3 and enable SR V1P5 as default.
- Patched Sensor(KXTF9) timing for faster response in games (from 100ms to 40ms)
http://goo.im/devs/Hashcode/acclaim/cm10/cm-10-20121207-UNOFFICIAL-acclaim.zip
Includes:
- 3 new CPU governors (LAZY-DYNAMIC_INTERACTIVE-WHEATLEY)
- Added safeboot settings for Silicon Performance (1.2Ghz)
- Added actual OSWR logic for mpu when turned on
P.s
Forgot to re-enable SR V1P5 Next time
http://goo.im/devs/Hashcode/acclaim/cm10/cm-10-20121128-UNOFFICIAL-acclaim.zip
- Deep Sleep really fixed this time, sorry guys
- I/O Tweaks for speed
- Better memory timings
- More Logical values added to CPU idle code
- Better Battery Life expected.
- 1.2Ghz CPU as default.
http://goo.im/devs/Hashcode/acclaim/cm10/cm-10-20121121-UNOFFICIAL-acclaim.zip
Includes:
- Reverted Kuzma's Emif changes so device can deep sleep again
- Removed SmartReflex 1P5 and downgraded to SmartReflex V3 for more compatibility with troublesome nooks
- Added O3 flag on compile for speed optimization
- Silicon Performance Enabled = 1.2GHZ CPU
http://goo.im/devs/Hashcode/acclaim/cm10/cm-10-20121115-UNOFFICIAL-acclaim.zip
Includes:
- 10 touch driver taken from Nook HD and adjusted to Multitouch compatibility by Mik_os
- New Backilight Led driver taken from Nook HD and adjusted to our github compatibility by Mik_os
- Still CM10(4.1.2) (JB4.2=CM10.1) sync
- Kuzmas excellent new drivers from Nook HD Source
- Bug fixes
All credits goes to our development team Kudos guys for an exceptional work!
In my opinion this is considered daily driver rom because:
Known Issues:
-None
http://goo.im/devs/Hashcode/acclaim/cm10/cm-10-20121107-UNOFFICIAL-acclaim.zip
Mirror:
http://celticstorage.co.uk/cm10/cm-10-20121107-Hashcode-acclaim.zip
Includes:
-New PVR Driver DDK [email protected]
-New WLAN firmware R5.SP3.03
-Greatly improved kernel thanks to all the nice developers in here
-All fixes Implemented:Touch/Accelerometer/PVR Graphics/LG Panel.
ROM Link:
http://goo.im/devs/Hashcode/acclaim/cm10/cm-10-20121023-UNOFFICIAL-acclaim.zip
Mirror:
http://celticstorage.co.uk/cm10/cm-10-20121023-Hashcode-acclaim.zip
Flashable Recoveries(Put into sdcard and flash from recovery like a rom)
http://celticstorage.co.uk/cm10/CWM_v6.2.7_emmc.zip
http://celticstorage.co.uk/cm10/TWRP_v2.3.3_emmc.zip
Thanks goes to Succulent (HD)
Gapps:
http://goo.im/gapps/gapps-jb-20121011-signed.zip
And as always,
Enjoy your Nook.
Added a flashable package from a new code implemented into rom by Mik_os
This will give you peace of mind in touch controller firmware flashing as it is very user friendly and straight forward.
Just flash this with recovery and you will find a new package in android app drawer that can test and see what firmware version you are at and offer you the opportunity to flash the other. Other can be 2 or Multitouch and depends on what firmware you are at the moment you run the application.
Nice!!!!!
* DISCLAIMER *
To be perfectly clear: This was a flash .zip built straight from the device/kernel sources that the current NT devs have worked very hard on.
I built it as a test case to see if there were compile issues and/or other external problems with the existing builds compared to the Kindle Fire builds which don't show the same issues.
THIS ROM IS NOT NEW. I didn't do anything but sync down the 2 acclaim projects press "go" on the compile.
Only issue I see of now is apps on SD card still disappear when nook reboots. I will report any other issues as I see them.
Thanks for all your hard work devs on the nook. To think I was about to give it up for a nexus 7. No way now I love this thing. :thumbup:
Sent from my Barnes & Noble Nook Tablet using xda app-developers app
Hey,
loving the development on the Nook!
I have flashed this ROM after full wipes, etc etc..
Everything seems to work..however, a big difference between this ROM and the 12/10 release from the other thread has been lots of choppyness/lag. Sometimes things lag so badly they crash..ie when in Settings. I'm not the most tech-savvy person so forgive me.
ps. it might be just me, but the colors seems sharper/cleaner/nicer!! And despite my comment about lag..when there is no lag, it is very responsive and even faster than 12/10 release..odd
Very nice otherwise
Mike
Downloading , i'll flash this rom
thanks u so much.
mikenexus said:
Hey,
loving the development on the Nook!
I have flashed this ROM after full wipes, etc etc..
Everything seems to work..however, a big difference between this ROM and the 12/10 release from the other thread has been lots of choppyness/lag. Sometimes things lag so badly they crash..ie when in Settings. I'm not the most tech-savvy person so forgive me.
ps. it might be just me, but the colors seems sharper/cleaner/nicer!! And despite my comment about lag..when there is no lag, it is very responsive and even faster than 12/10 release..odd
Very nice otherwise
Mike
Click to expand...
Click to collapse
the same felling with you. and.... Mic does not work...
Note:12/10 build had a workable Mic (SGT7+CM10+Cherry Picks,By meghd00t)
http://forum.xda-developers.com/showthread.php?p=31400856 this has the mic fix. Search around a little and you can find answers
Sent from my Droid using xda app-developers app
createpassword said:
Anyone? Its a pretty simple question...
Click to expand...
Click to collapse
I think is a simple flash to find out. The truth is out there.... (drums)
So my friend has the 16gb Nook Tablet.. will this work on it? And really? Everything works?!?!?! No more screen of death? Mic works too??!?! Netflix?!?!
I wanted to comment i tried this one and i have the same problem with all cm10 roms....after a few minutes....it wont let me download anything...like i try to download and it reaches 100% but says still in progress and freezes everything because once that hapens and you try to reboot or power off it just loads but does not reboot or power off....
Sent from my Nook Tablet using xda app-developers app
createpassword said:
From your post 1 in this thread, you say "I will try to give support where due in this thread."
Well, IT IS DUE.
Click to expand...
Click to collapse
I don't think anyone owes you anything at all. Such entitlement....
Sent from my Barnes & Noble Nook Tablet using xda premium
createpassword said:
It is not "simple" to mess with my wife's tablet. Nor is an experiment of this nature CONCLUSIVE. I have no interest in "trying" something that is well known to be broken/useless. Much better to leave it stock in that case, alter only when known functional.
And no, the answer is NOT "out there". That's why I asked.
From your post 1 in this thread, you say "I will try to give support where due in this thread."
Well, IT IS DUE.
Click to expand...
Click to collapse
This is a development rom in the development section of the forums. It seems to me it would be better for you to return your wife's nook to stock. This rom was posted for testing and bug reporting.
Sent from my DROID RAZR using xda premium
createpassword said:
I haven't seen any mention of it lately in any of the threads, but what is the status of things like random reboots and failures to wake from sleep?
Click to expand...
Click to collapse
I haven't had any reboots or hangs on my NT 16 GB, but it's only been 12 hours. I'll test it over the weekend more to see if I can make the permanent jump from CM7.
this rom have mixer or not.
createpassword said:
I haven't seen any mention of it lately in any of the threads, but what is the status of things like random reboots and failures to wake from sleep?
Click to expand...
Click to collapse
No. I put it on my mother's 16GB Nook Tablet and it's miles better than CM7 was. Not perfect but no serious flaws.
Has anyone experienced download problems that cause lag that doesnt allow you to reboot or poweroff or do anything?
Sent from my Nook Tablet using xda app-developers app
I have rooted every device I own. I also have a Nexus 7 and a Nook Tablet. In somewhat of defense of the guy earlier working 10 hours, wife and 4 kids sometimes it is easier to ask rather than "just flash it". I want to use my Nook so my kids ages 2 and 4 can watch Netflix on long car trips. The Nook is much more of a tank than the Nexus 7 and would bee much less bummed if the Nook gets broken over my Nexus.
I'm not saying my time it's any more important than yours. And it doesn't take any more effort to answer a simple question than it does to tell someone Rio flash back to stock.
I would like to know if Netflix works on this build? If so I will flash it ASAP. If not I will not get my Nook out of my nightstand and will keep checking back once and a while.
Thanks.
Sent from my DROID SPYDER using Xparent ICS Blue Tapatalk 2
Random reboots seems to be fixed.
createpassword said:
It is not "simple" to mess with my wife's tablet. Nor is an experiment of this nature CONCLUSIVE. I have no interest in "trying" something that is well known to be broken/useless. Much better to leave it stock in that case, alter only when known functional.
And no, the answer is NOT "out there". That's why I asked.
From your post 1 in this thread, you say "I will try to give support where due in this thread."
Well, IT IS DUE.
Click to expand...
Click to collapse
My deepest apologies.
It was an error from my part so i went and fixed my statement in Official post.
Thanks again for pointing out my huge mistake.
Here's a bit of info you may want on this project for how we do things differently:
CLICK HERE to find out more about the new team working on this project since our TeamEOS merger.
No features you don't need which slow the device down, or put your data at risk of being stolen. If you want to give it away, it should be your decision.
A fast and clean install with no UX decisions made for you. You make the ROM whatever you would like.
A team constantly exploring totally new feature sets and optimizations geared toward you, the user
We utilize a plethora of optimizations in a build system unlike any other:
Each build has a toolchain built for your device at the time of build. No more generic toolchain android builds.
Consistently updated upstream toolchain module source with our custom backports, fixes, and optimizations applied in a patch at build time.
Fully built utilizing Link Time Optimization (another custom ROM first). Feel free to google this one a bit to get an idea of the performance gain.
Many repositories have code fixes, cleanups, and many minor optimizations which are too generous to even speak of here.
Optimizations are toggled on and off based on device for the best experience we can acheive for your device without sacrificing any stability
Many Qcom optimizations and AOSP master (upstream) optimizations and fixes using device specifications to determine usage.
Fully built utilizing strict aliasing and isognu++11 mode.
Full "-O3" build. To those who don't know, this is the highest "optimization level" available in gcc that sets many other flags.
Important Links:
Download Nightlies - We have a very in depth review system, so these should be considered stable.
Download Weeklies - These are built once a week on Monday.
Download GApps
Download SuperSU installer
Kernel Source
Interactive and Rolling Changelog
Bug Tracker
Instructions:
In the same recovery session, flash the following:
Flash rom
Flash GApps
Flash Superuser zip
Reboot
Thank you for choosing codefireXperiment,
Yippee! First AOSP build with fully functional IR Blaster! I use the HTC implementation so any IR control app must use the HTC IR api. I tested with this app.
http://forum.xda-developers.com/showthread.php?t=2271113
Blaster mode and Learn mode are fully functional and stable. This is the first non-Nexus device I've done AOSP on so bear with me for a bit. The build is rock solid stable and I dare any build to try and out-benchmark me ;D
one more for good measure
This is truly a wonderful suprise!!
This is truly a wonderful suprise!!
Welcome bigrush!
This sounds cool! Thanks for the hard work. Im gonna give this a shot tomorrow.
gunna take this for a spin. sounds pretty solid.
or so i thought.
AAAARG...
keeps spittin out "Warning: no file_contextsassert failed.....Followed by various prop errors about the phones model"
anyone got any idea whats goin on?
Are the APN for ATT in this ROM or do I have to put them in myself
Sent from my HTC One using Tapatalk 2
Does cfx have the same janky animation and sluggishness of other AOSP roms for the One when compared against a Sense or GE ROM?
If anyone could fix aosp/optimize for device specific hw on non-nexus devices its you.
Sieze said:
gunna take this for a spin. sounds pretty solid.
or so i thought.
AAAARG...
keeps spittin out "Warning: no file_contextsassert failed.....Followed by various prop errors about the phones model"
anyone got any idea whats goin on?
Click to expand...
Click to collapse
I'm getting this same error too. Anybody know what's up yet? Probably something simple lol
Are you guys flashing with cw or twrp? Don't worry about the file context warning. I may have to disable device assert in installer script.
bigrushdog said:
Are you guys flashing with cw or twrp? Don't worry about the file context warning. I may have to disable device assert in installer script.
Click to expand...
Click to collapse
im using CW touch 6.0.3.3
running a backup atm but once finished il flash TWRP and see if it works.
Ok. So it fails to flash on cw then?
bigrushdog said:
Ok. So it fails to flash on cw then?
Click to expand...
Click to collapse
yup. it flashed with out a hitch on TWRP...
Sieze said:
yup. it flashed with out a hitch on TWRP...
Click to expand...
Click to collapse
Ya we compile the project with twrp recovery. I'll confer with my associates about tweaking or killing device assert in release tools. Also, I gotta drop a global device build too. First aosp build with IR Blaster and this board gets hardly any traffic! I personally run the build on my m7tmo so any derp gets my attention. There's little minor issues here and there but nothing major. Bluetooth OBEX is derped project wide but should be fixed soon.
bigrushdog said:
Ya we compile the project with twrp recovery. I'll confer with my associates about tweaking or killing device assert in release tools. Also, I gotta drop a global device build too. First aosp build with IR Blaster and this board gets hardly any traffic! I personally run the build on my m7tmo so any derp gets my attention. There's little minor issues here and there but nothing major. Bluetooth OBEX is derped project wide but should be fixed soon.
Click to expand...
Click to collapse
well initial response to laying my finger and moving it on the screen. amazing. i didnt think id feel or tell much a difference in response. but holy S#!7 so smooth and stuff happens when its supposed to aka as soon as i touch the icon its open...
(ノ^_^)ノ also the boot animation is pretty frickin sweet.
also the benchmark has me drooling.
Quadrant Standard: 6749
also im really frickin liking this ROM
Hahaha don't lie! The boot anim sucks ass man! Ya all this ui jitter talk I hear, I'm just not getting all that with our build. If the build sucked I wouldn't run it. And I sure as hell wouldn't publish it. Thanks for the kind words. More win in the pipeline.
bigrushdog said:
Hahaha don't lie! The boot anim sucks ass man! Ya all this ui jitter talk I hear, I'm just not getting all that with our build. If the build sucked I wouldn't run it. And I sure as hell wouldn't publish it. Thanks for the kind words. More win in the pipeline.
Click to expand...
Click to collapse
well hey credits due where its earned right? but yea im still crappin my pants at how there is absolutely no lag at my finger tip.
Hands down the best android experience ive ever had. i can trully feel the power of my device in my hand in all its glory.
Grab that IR app and program your TV man. Dude dropped source for the app so maybe I'll do some IR toggles or something
Sieze said:
yup. it flashed with out a hitch on TWRP...
Click to expand...
Click to collapse
I will also try with twrp tomorrow morning. I personally don't prefer one over the other so if twrp is what works then twrp it is!
mikexmayhem said:
I will also try with twrp tomorrow morning. I personally don't prefer one over the other so if twrp is what works then twrp it is!
Click to expand...
Click to collapse
Flashed with twrp. Still gave error but said successful. After reboot everything looks just fine. Great ROM!
BETA TESTER NEEDED:
I've released this ROM on the other 3 8960 devices already and now that cm10.2 has gone into nightlies here I thought I'd bring this ROM over. Here's a preview build for those that are interested. I do not have this device to test with, however I had great success on the ville and jewel (I have the Evita) and expect nothing less here. If the feedback here is positive I'll merge this into official nightlies with the other devices.
This is built using the CM device trees so all current device specific CM issues will be issues here as well. Screen flicker and sim card warnings are the major ones I see in mdmowers thread.
full_fireball-cfxe-OPENMASTER-20131019.112802.zip - 178.63 MB
GAPPS
UPDATE-SuperSU-v1.51.zip - 1.14 MB - needed for root, rom does not give root access by default so if you want rooot flash this as well
Check out codefirex.com for more info on the ROM and the team. Basically this is the closest thign to PURE AOSP you will find anywhere, highly optimized and built with a custom built GCC-4.8.2 toolchain.
This uses the 3.4 CM kernel tweaked for gcc-4.8 builds and as such follows all the same requirements as CM-10.2. NEWEST FIRMWARE/HBOOT are required. S-on still? You will need to fastboot flash the boot.IMG after flashing the ROM.
This will be updated more in a week or so when the official builds start up.
Thanks to the CM team for all their work on this family of devices, especially mdmower for his work on fireball for all of us to enjoy.
Most of you guys here on the Incredible 4G don't know me but I've been deving for Evita for a while now, since there was no support for this ROM on any of the other devices in the 8960 family I decided to branch out with this Rom and bring it to all of them.
***I DO NOT OWN A INCREDIBLE 4G AND THEREFORE CANNOT TEST THESE MYSELF. ***
DISCLAIMER: I will not be held responsible for any damages caused to your device by flashing this ROM. Your warranty is now void.
By proceeding you accept the risks involved with flashing ROMS. While I test everything on my own device, I cannot garauntee yours will not explode into kittens and rainbows.
Source: https://github.com/codefireXperiment
Sent from my One Xl using Tapatalk 2
KNOWN ISSUES:
ROOT ACCESS : On-going disscusion within the team but as of right now root is not available to userspace. Root currently works over adb only. Flash the superSU.zip and carry on if you need root access for apps like TiBu or root file explorers. Otherwise you really don't need it
BOOT ANIMATION : i'ts just full of struggle, it's an old animation made for smaller screens. It freezes and goes blank screen on first boot. Don't be alarmed, it'll be OK. New custom boot ani is being designed now by a fellow team member
BROWSER : Ocassional FC on embedded browser streaming video. You tube and links that open a video player are fine, just embedded video.
FIREBALL SPECIFIC ISSUES:
Somebody tell me something...I need a tester for this!!!
I expect the same CM issues :
Screen flicker ( if you get this flash something else asap)
Possible Data connectivity/sim card issues
ROM is still under construction so i'm sure more will surface but this should be more than ready to be a daily driver.
Sent from my One Xl using Tapatalk 2
Mine too
Sent from my One Xl using Tapatalk 2
Wow its quiet in this forum...I know the user base is relatively small here compared to the other devices in the family but I figured there'd be at least a couple brave souls that could test this out for me
Sent from my One Xl using Tapatalk 2
Can you give some more details about what's in this rom? I went to the website but couldn't see anything besides status updates. Is it a stripped down CM?
Sure thing, its basically straight AOSP compiled with a custom 4.8.2 toolchain (compiled w/ROM for each device) and all the linaro type build flags and -03 flags. Highly optimized, slim and efficient. You won't find a lot of the mods and features all the other ROMs out there have, just what Google gave us.
You may find that doesn't fit your style and if so cool, its not for everybody. What I'm really interested in is hardware testing since I do not own this device(I have the one xl).
Is camera/WiFi/data/calls working... That kind of thing. I know this device is having some issues that the other 3 HTC 8960 devices are not on cm10.2.
Sent from my One Xl using Tapatalk 2
chupajr said:
Can you give some more details about what's in this rom? I went to the website but couldn't see anything besides status updates. Is it a stripped down CM?
Click to expand...
Click to collapse
Wow your right that info page isn't so great, I had just copied the verbage from another devices thread when I made mine. I'll get with the team about that. See my post above for some more info.
Sent from my One Xl using Tapatalk 2
Okay.. gave it a try. The rom itself seems to run really snappy and quick. My 4G took a bit to connect and never turned blue but I did have internet. Camera and all seemed to work fine. After trying a few things I realized I never installed gapps so I rebooted back to recovery and flashed them. That was as far as I got. The phone went into boot loops. Pulled the battery and wiped it clean, tried to restore my cm10.2 backup and it locked up upon rebooting itself. Pulled the battery again and attempted to get to recovery which took 3 tries. Wiped the phone again and restored one more time and cm10.2 seems to be working fine now.
Maybe it didn't take cause I flashed gapps afterwards.. I dunno. I'll try to flash both rom and gapps together when I get another chance.
Pete02 said:
Okay.. gave it a try. The rom itself seems to run really snappy and quick. My 4G took a bit to connect and never turned blue but I did have internet. Camera and all seemed to work fine. After trying a few things I realized I never installed gapps so I rebooted back to recovery and flashed them. That was as far as I got. The phone went into boot loops. Pulled the battery and wiped it clean, tried to restore my cm10.2 backup and it locked up upon rebooting itself. Pulled the battery again and attempted to get to recovery which took 3 tries. Wiped the phone again and restored one more time and cm10.2 seems to be working fine now.
Maybe it didn't take cause I flashed gapps afterwards.. I dunno. I'll try to flash both rom and gapps together when I get another chance.
Click to expand...
Click to collapse
Finally got somebody! Yay! Thanks for trying...to be honest this build is almost a month old now and quite a bit of the data issues I think have been resolved since then.
I can't speak to your boot looping deal, that is defiantly strange behavior. It should not matter when or if you flash gapps. At this point I'm happy to known it boots. Ive held off doing anything with this one as I haven't had anybody to test. I've got a few other things going but I'll get a more current build up in a few days.
Sent from my One Xl using Tapatalk 2
jrior001 said:
Finally got somebody! Yay! Thanks for trying...to be honest this build is almost a month old now and quite a bit of the data issues I think have been resolved since then.
I can't speak to your boot looping deal, that is defiantly strange behavior. It should not matter when or if you flash gapps. At this point I'm happy to known it boots. Ive held off doing anything with this one as I haven't had anybody to test. I've got a few other things going but I'll get a more current build up in a few days.
Sent from my One Xl using Tapatalk 2
Click to expand...
Click to collapse
Yeah.. I know I'm a bit late to the party since I've been following CM's builds and they're working really well for me I haven't really checked many other threads. Take your time and I'll check back to test again for you when your ready. Thanks for bringing another rom to our fireball btw!
New beta build ready
full_fireball-cfxe-OPENMASTER-20131004.000114.zip - 167.01 MB
This is current to last nights official nightlies. If any one gives it a try could post some feedback it would be much appreciated. Thanks, and enjoy!
Sent from my One Xl using Tapatalk 2
Flashed the latest release and here's what I've got so far. The first boot took some time, as expected, and when it was done my phone was roaming so I couldn't log in. I remembered this problem with previous versions of cm so I just rebooted. 2nd boot went much quicker and my phone was now on lte. I checked all the settings for radio and the network, system and CDMA were all correct.
Upon trying to reconfigure the hardware keys it seems that they were set up for a different phone. There was home, menu and search keys listed but not back, home and recents buttons like we have. The camera and video seem to work as well as any normal cm version would. I couldn't find the swipe function for the keyboard if there is one.
The 4gLTE, WiFi and GPS all seem to work fine. I had no trouble locking into satellites or routers. Text messaging works fine also but I didn't have a chance to test calling yet. I'm working right now. I decided to install all my apps and play for awhile until TiBu told me there's no root and that's when I realized there no Superuser installed. Other than that the ROM works smooth and fast. I'll be back if I find anything else.
Su zip in op will fix root. Long argument among the team but for now this is how it is.
Keep forgetting to fix the overlay for that hw key. "Menu key " is our "app switch key". I had to hack it to get the buttons I wanted before we added hw key remapping and forgot to remove the hack.
Thanks again for testing it out.
Sent from my One Xl using Tapatalk 2
jrior001 said:
Su zip in op will fix root.
Click to expand...
Click to collapse
Thanks for the zip, I'll continue to play and let ya know how it goes.
Pete02 said:
Thanks for the zip, I'll continue to play and let ya know how it goes.
Click to expand...
Click to collapse
FYI I fixed those hw keys locally for the next round. Let me know how it goes after a bit and if its solid I'll merge it it for nightlies with the rest of the 8960 family
Sent from my One Xl using Tapatalk 2
The zip you provided worked great. Restored all my apps no problem. Came across a bug though. Tried to play Apollo but got no sound. The app seemed to be working fine, just no sound. So I tried Pandora and the sound came on but for only one song then went out again. I was using my headphones. I've used BT for calls and that works fine but I haven't tried streaming audio to my car yet to see if that works.
Pete02 said:
The zip you provided worked great. Restored all my apps no problem. Came across a bug though. Tried to play Apollo but got no sound. The app seemed to be working fine, just no sound. So I tried Pandora and the sound came on but for only one song then went out again. I was using my headphones. I've used BT for calls and that works fine but I haven't tried streaming audio to my car yet to see if that works.
Click to expand...
Click to collapse
Yeah thats fixed too now as well, one step ahead so far. Will run a new build over night to get you caught up. Will upload in the am.
Sent from my One Xl using Tapatalk 2
full_fireball-cfxe-OPENMASTER-20131006.090117.zip - 167.05 MB audio and hwkeys fixed up right
Been running this for a couple of days now and it seems to work very well. :thumbup: The only requests that I could think of would be swipe for the keyboard and the option to have the volume keys control fast forward/rewind for the music player but other than that this rom seems pretty solid right now. Great work guys and thanks again!
I'll be heading to France in a couple of days and plan on buying a Sim card when I get there for the local network so I'll let you know how it works when I get back.
Pete02 said:
Been running this for a couple of days now and it seems to work very well. :thumbup: The only requests that I could think of would be swipe for the keyboard and the option to have the volume keys control fast forward/rewind for the music player but other than that this rom seems pretty solid right now. Great work guys and thanks again!
I'll be heading to France in a couple of days and plan on buying a Sim card when I get there for the local network so I'll let you know how it works when I get back.
Click to expand...
Click to collapse
Volume button controls and long press back are 2 things on my radar to get added eventually. Thanks again for testing.
Sent from my One Xl using Tapatalk 2
[KERNEL] Starship-Kernel The Next Generation Stock/AOSP & CM-13 04/25/16 (Linaro 4.9)
Welcome to Starship Kernel The Next Generation (TNG) for the Nexus 6 Shamu. Not much else to say other than more than ever the Kernel is by design light wait, power efficient and moves at Warp Speed. There are no special features to play around with but instead designed to just be installed and just work. If looking for things to play around with may as well just move on as this is probably not the kernel for you.
Have shed some light on a few names below but really need to thank all the Nexus 6 Kernel Developers as could not have done much of anything without them. Before this project I had limited Kernel knowledge. Have been developing since I guess my first Rom had been CM6 based but never had much Kernel dealings. Have always worked joining up with a team to get CM or other AOSP like Roms up and running on TouchWiz,. Sense and other devices far from the Stock Android Experience. In working in groups and teams have for the most part always been the Device File & Vendor Blob guy. Everything I have learned about Kernels has honestly come from sifting through other Kernels and researching the hell out of out of commits until being able to stand on my own 2 feet and think so far have done a dam good job putting together a hell of a Kernel for the Nexus 6 that is extremely stable and performs well beyond expectation besides the big ol Jinx I just through out there.
This is now the new and improved Next Generation moving from say warp 6 to warp 9. Would say 10 but some funky stuff goes down at ten and if you dont know lets just say its not a place you wana go.
Definitely need to throw up thanks to Flair2, Imoseyon and Neoboddy89 as have used a decent amount of their commits in particular..
Features Worth Noting
Have placed features into either groups or single commits that make rather large improvements but are welcome to sift through the Kernels Commit History below as there are many individual changes to numerous to mention in a single post or even page . As mentioned most come from just sifting over and reading commits from every Kernel I could find. Most from Shamu but also some carefully selected from other devices with similar hardware
Kernel Version 3.10.101
Fast USB Charging
LZ4 Compression
Sio & Bfq i/o Schedulers - "bfq" used as default scheduler
ExFAT Support
Power Efficient Workqueues
KGSL Optimixations
Audio Codec Optimizations
Video Firmware Optimizations
CPU Idle Optimizations
GPU Power saving Optimizations
Adreno_Idler
Color Temperature Interface Using PCC
Frandom Support
LED Support (Rom must also Support)
MSM Vidc: Optimizations
Net: Wireless Bcmdhd, Various Optimizations
PM Enhancements.
F2FS 3.10
Starship Kernel, Nough Said!!
Source / Commit History aka change log
https://github.com/Chairshot215/starship_kernel_moto_shamu/commits/mm-mr1?page=1
Download Starship-Kernel_Class_SMTNG7_(Linaro-4.9) (04.16.2016)
Marshmallow 6.0.1 Stock/AOSP
https://www.androidfilehost.com/?fid=24499762636007231
CM-13.0
https://www.androidfilehost.com/?fid=24499762636007230
Again I am not responsible for any negative effects using any of the files on this thread or any post that has been linked in this thread so using is all at your own risk.
seems like nexus 6 development just blew up with new ROMs and kernels, thank you pal
Sent from my Nexus 6 using Tapatalk
Yup!
Does this kernel bypass force encryption?
Team Octos -Nexus 6
force encryption is disabled in the r_2 boot.img but so far is still showing that my N6 is Encrypted. With that said have not performed the recommended factory reset when going from a force encrypted boot.img to one that is not.
System UI Crash
Perhaps I've misinterpreted the OP, but I seem to have a major issue. Assuming this kernel is meant for 5.1.1 AOSP builds, upon flashing the kernel and wiping caches I get System UI crashes that do not allow me to actually start Android... am I at fault here?
That is odd I have flashed on AOSP many a time and have not had any issue. This is pure AOSP I compile without any modifications though. Is it a Rom on the forum, can maybe take a look see what might be the issue.
chairshot215 said:
That is odd I have flashed on AOSP many a time and have not had any issue. This is pure AOSP I compile without any modifications though. Is it a Rom on the forum, can maybe take a look see what might be the issue.
Click to expand...
Click to collapse
An issue like this is usually directed at the ramdisk. You may want to look into moving to an any kernel installer instead.
Sent from my Nexus 6 using Tapatalk
I was unencrypted, flashed the kernel and it booted up and told me encryption failed so I had to wipe and start over and decrypt again. If its disabled why did it encrypt again?
Sent from my Nexus 6 using Tapatalk
I like Starship ROM since my Nexus 5. :laugh::laugh::laugh:
ps000000 said:
I like Starship ROM since my Nexus 5. :laugh::laugh::laugh:
Click to expand...
Click to collapse
I hope you are referring to the Kit-Kat version and not the test flight Lollipop Rom I had up for a few days, lol.
Had pretty much put most of a year counting the L-Previews into that thing but was honestly not happy and did not think it measured up to what I had been releasing under Starship since Froyo so took it down and decided it was time for some off time. May pick it up again with M, Lollipop version had a few nice things could probably use. Think I had just about changed every hex color throughout the entire source. Took me for a loop when Google started using the Teal coloring I was using for a few versions.
calaeb08 said:
I was unencrypted, flashed the kernel and it booted up and told me encryption failed so I had to wipe and start over and decrypt again. If its disabled why did it encrypt again?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Sorry had a hectic week, maybe you can save me some time. Honestly was trying to stay away from forums for a bit once got my N6. Was not till deciding to post something I looked around. Don't know how long I had only unlocked the bootloader so could fastboot the Kernel. Wanted over weekend to fix this and above mentioned any kernel so is more versatile than stock and pure AOSP. If could save me time and tell me what had done wrong would be a helpful thing. Am all about helpful and not so much smartest in the room syndrome so anyway committed the "fstab" had used if you see the issue at a glance. Otherwise think tomorrow is going to be a couch bound day so will read more into it.
https://github.com/Starship-Android...mmit/5f101827c8a0317d489134de756aacc534215d48
chairshot215 said:
I hope you are referring to the Kit-Kat version and not the test flight Lollipop Rom I had up for a few days, lol.
Had pretty much put most of a year counting the L-Previews into that thing but was honestly not happy and did not think it measured up to what I had been releasing under Starship since Froyo so took it down and decided it was time for some off time. May pick it up again with M, Lollipop version had a few nice things could probably use. Think I had just about changed every hex color throughout the entire source. Through me for a loop when Google started using the Teal coloring I was using for a few versions.
Sorry had a hectic week, maybe you can save me some time. Honestly was trying to stay away from forums for a bit once got my N6. Was not till deciding to post something I looked around. Don't know how long I had only unlocked the bootloader so could fastboot the Kernel. Wanted over weekend to fix this and above mentioned any kernel so is more versatile than stock and pure AOSP. If could save me time and tell me what had done wrong would be a helpful thing. Am all about helpful and not so much smartest in the room syndrome so anyway committed the "fstab" had used if you see the issue at a glance. Otherwise think tomorrow is going to be a couch bound day so will read more into it.
https://github.com/Starship-Android...mmit/5f101827c8a0317d489134de756aacc534215d48
Click to expand...
Click to collapse
I myself know nothing about developing roms or kernels, that's why I'm here to ride on the bus with the smart kids lol. I do know that you can just leave it the way it is, but you gotta let people know it's forced encryption so they don't have to start all over. They can flash that zip that disables it before booting up.
What's the point of a sig anyways?
Well Definitely it for Lollipop, Probably. One thing that bothered me moving from the N5 to N6 is my BT Headset sounded like a warped and scratched record. I had lucked out with that pair in that had been reasonable priced and sounded amazing previously. Have added a few choice commits, well almost 2 pages but the things work like a charm. Decided for that and a few other reasons for one last post until 6.0.
I remember you from the galaxy victory forums :3 thanks for trying with CM. We were SOL, but theres still development going on there!
Sent from my Nexus 6 using Tapatalk
NolenUmar said:
I remember you from the galaxy victory forums :3 thanks for trying with CM. We were SOL, but theres still development going on there!
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yeah I actually am still receiving emails about the Victory. Not that I could ever return to either the screen size or Touchwiz but wish I still had the device. Still feel like that SOB defeated me. Had been I think the 3rd device I worked on developing from the CM source and was so dead set on doing everything crazy proper so it could be an officially supported device. Wish I still had the device as do not like the feeling of spending countless hours on something and then leave unfinished. Think in the end all but GPS, Camera and that dang reboot when switching from Wifi to LTE. Think I used the Apexq as a template for getting everything else going. Otherwise wish the community luck. The phone was nice for the Price just a shame it has been years and everyone is still stuck on Stock with last I checked a bunch of out dated Kernels. Anyhow thats my Victory, rather defeated Rant. Remember at one point had got so frustrated used some command I don't remember off the top of my head and a lib decompiler and made the below list of all the files and their dependencies when trying to put together a vendor blob list.
http://pastebin.com/SFyJ14kv
Whats crazy about just pulling up this list is that I see the creation date was todays date but in 2013. Just had to mention that SOB device. Now I’m all worked up, lol.
Updated the M Kernel to r1.2 as works fine with SuperSU 5.1
This is an Encrypted Kernel. Will probably change with next update but for now it is Encrypted.
Now 2.0 with a few optimizations. Forgot about encryption but again looking for next update,lol.
Eill give it a try when it doesnt force enycrption
Sent from my Nexus 6 using Tapatalk
calaeb08 said:
Eill give it a try when it doesnt force enycrption
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yeah will need to look at that again. I use the same any-kernel installer for Lollipop-r_3.0-Kernel and M-6.0-r_2.0-Kernel.
With the L Kernel either flashing with an already un-encrypted Rom or flashing and performing a data wipe / factory reset with an encrypted Rom all works fine without encryption being forced.
Could be I just messed up the test with the M-6.0-r_2.0-Kernel and it actually does not enforce encryption as it uses the same fstab.shamu as the L version . Just did not feel like going through a data wipe to double check so am putting it off until the next release. Otherwise if you are not encrypted and remove the fstab.shamu file from the Ramdisk folder in the M-6.0-r_2.0-Kernel zip before flashing the Rom should still stay un-encrypted. I have at least not seen or read anything stating there is a difference between L&M when it comes to encryption.
Otherwise this is the anykernel installer used in both L&M. The only difference is the zImage-dtb I use.
https://github.com/Starship-Android/anykernel
chairshot215 said:
Yeah will need to look at that again. I use the same any-kernel installer for Lollipop-r_3.0-Kernel and M-6.0-r_2.0-Kernel.
With the L Kernel either flashing with an already un-encrypted Rom or flashing and performing a data wipe / factory reset with an encrypted Rom all works fine without encryption being forced.
Could be I just messed up the test with the M-6.0-r_2.0-Kernel and it actually does not enforce encryption as it uses the same fstab.shamu as the L version . Just did not feel like going through a data wipe to double check so am putting it off until the next release. Otherwise if you are not encrypted and remove the fstab.shamu file from the Ramdisk folder in the M-6.0-r_2.0-Kernel zip before flashing the Rom should still stay un-encrypted. I have at least not seen or read anything stating there is a difference between L&M when it comes to encryption.
Otherwise this is the anykernel installer used in both L&M. The only difference is the zImage-dtb I use.
https://github.com/Starship-Android/anykernel
Click to expand...
Click to collapse
You'd probably be better off using hellsgods anykernel scripts. Though, I'm not sure why yours isn't working to disable it. Theres also a fed patcher that should fix it. It kinda defeats the purpose of anykernel if your replacing files in the ramdisk instead of editing them.
Sent from my Nexus 6 using Tapatalk