Starship Kernel is being developed in conjunction with the not yet posted Starship Rom. Like I had done with the KK incarnation of the Starship Rom I am also posting the Kernel separately for anyone who may not like the Rom's Theme. Though unlikely as that may sound because I have spent much time and effort with the Kernel am posting the Kernel separately so it can be used with other Roms and not just Starship.
If you are looking for new features to play with this will not be the Kernel for you. It is designed to improve the overall experience as if it was not there. At this point and probably never you wont find over clocking or voltage controls to play with but rather just a more efficient overall experience.
Each Kernel Download section contains a link to the commit list for both the purpose of following rules about posting links to Kernel Sources as well as serving as a change log. You will find in the main branch all Linux Kernel Increment Updates are grouped into one commit. This is to easily distinguish what commits have been made as part of the Linux Kernel Increment Updates from other additions/optimizations that are not part of the Linux Version Updates. You can find descriptions of each change made as part of the Increment Updates in the staging branch. In other words the second link below the download links will give a description off the changes made in the Linux Version Updates .
Downloads
AOSP/Stock (Android Version 5.1.1)
AOSP/Stock Kernel is compiles using Google's GCC 4.8 toolchain and tested tested on the Stock 5.1.1 Rom as well as AOSP compiled Rom using unmodified pure 5.1.1 Source code. The Kernel may or may not work on custom Roms based on 5.1.1 depending on what changes have been made by the Roms developer and how far the Rom has strayed from the original source code. In most cases if the Rom is AOSP based the Kernel will work but provide no guarantee as am not testing with every ROM available. If you do find a Rom the Kernel does not work with feel free to comment but please include what Kernel was used that did not work as I may be able to shed light on reasons why and provide a workaround if possible. Most of incompatibility will find that the Kernel is not the issue rather what is included inside the boot.img like Ramdisk iinit.rc files that set permissions and create the Rom file-system.
Starship-lollipop-5.1_Kernel-3.4.91_r1
https://www.androidfilehost.com/?fid=24052804347767806
Starship-lollipop-5.1_Kernel-3.4.88_r1
https://www.androidfilehost.com/?fid=24052804347766347
Starship-lollipop-5.1_Kernel-3.4.86_r1
https://www.androidfilehost.com/?fid=24052804347760505
Starship-lollipop-5.1_Kernel-3.4.83_r1
https://www.androidfilehost.com/?fid=24052804347756685
Source / Change-log
https://github.com/Starship-Android/android_kernel_lge_hammerhead-starship/commits/lollipop
Including individual explanation of changes included as part of Linux version increment update patches.
https://github.com/Starship-Android/android_kernel_lge_hammerhead-starship/commits/lollipop_staging
CM-12.1
CM-12.1 Kernels may be updated more frequently without posting a new date so don’t be surprised to see multiple release number increments. In most cases there has been no change in the Kernel itself but update frequently as development is fast moving. Because of this some of the files that get packaged into the boot.img along with the Kernel may change and cause issues. Because of this will update as frequently as I can to insure everything packaged into the boot.img is up to date.
Starship-CM-12.1_Kernel-3.4.88_r1
https://www.androidfilehost.com/?fid=24052804347766796
Starship-CM-12.1_Kernel-3.4.86_r1
https://www.androidfilehost.com/?fid=24052804347760507
Starship-CM-12.1_Kernel-3.4.80_r1
https://www.androidfilehost.com/?fid=23991606952613802
Source / Change-log
https://github.com/Starship-Android/android_kernel_lge_hammerhead-starship/commits/cm-12.1_staging
Donations
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=MMEVCWUX83SXJ
I am not responsible for any effect using the downloads from this forum my have on any device and you download and use at your own risk.
Just decided to include the CM-11 Kernel for anyone who may be using CM-11. Is a nice Kernel and gave me an extra hour or two battery so recompiling with a few new commits I have been using in both CM-12 & AOSP. Will post in a few. Checking nothing else may have changed on the CM side with the rest of the boot.img and will post in a bit.
I will try out the AOSP kernel tonight or tomorrow, we are under blizzard conditions right now and can't mess with phone because of work (boss & I texting back and fourth)
Thanks for your work
Sent from my rooted RCT6203W46 using xda-dev app
Downloading now!
Sent from my Nexus 5 using XDA Free mobile app
rickballs said:
Downloading now!
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Sorry about this then but have uploaded an update. I had intended on holding off until reaching Linux version 3.4.40 as it is the version I had left off with for Kit-Kat and have just been modifying each version increment patch from the Kit-Kat 3.4 Kernel for Lollipop. Anyhow last night before bed had used my Bluetooth Headset with the current version and sounded like I had gone out and bought a brand new higher end set so decided to post the update now. Found in the past Android can have a completely different experience when it comes to different BT devices like for example the same headset had become completely unusable on my N7 with constant skips and pauses on 4.4.4 after working beautifully on 4.4.3 so hope others can hear the same boost in overall audio quality including BT headsets.
Updated Kernels with a few new optimizations and 3.4.36 version update
Ok will try it
Can't download from devhost. Anyone else is having problema?
gengi said:
Can't download from devhost. Anyone else is having problema?
Click to expand...
Click to collapse
Looks to be up and running. Can try direct links though.
updated so links are no longer current.
Well it feels like with all the side track projects been talking Starship L long enogh maybe some of those who have sent PM's asking about the lollipop update are starting to become doubters so decided to post up a few screen shots. Was going to finish a few things then go over the theme image by image and color by color but think instead after finishing up a few things will post and then start going over each apk over again for touching up, fixing and adding missed optimizations including Kernel updating along the way. Once again not for everyone so haters can hate and I just keep doing it because its what I like doing.
Made new boot.img for Stock / AOSP 5.1.0 as old image used in 5.0 - 5.0.2 caused boot loops.
The MultiROM not work with this kernel? :-O
dado70 said:
The MultiROM not work with this kernel? :-O
Click to expand...
Click to collapse
Honestly have been meaning but have not tried MultiROM. Looked over at the thread and see allot of mention about the boot.img and modifications. If I had to guess with the limited knowledge I have would say if not working is not so much the Kernel but the boot.img in the same way that both the Stock / AOSP zips posted are the same exact Kernel inside but changes made to files like the init.rc inside the 5.1.0 boot.img that creates the file system and sets permissions among a score of other things caused 5.1.0 from booting properly after updating and flashing the boot.img. As developers we use the name Kernel but there is much more inside than the actual Kernel. In some cases can be more than a dozen other scripts and other files inside. Will need to try and learn a bit about MultiROM. Out of curiosity was it Stock or CM giving you issues?
Little more reading and looks like not everyone including CM has updated to include new bootloader version checks to include new bootloader from the 5..1.0 update. So for example I needed to change the bootloader version in CM source or nightly builds will not flash in TWRP without errors.
Maybe an update on this if flashing CM version, seems latest CM12 is receiving errors flashing with some recovery versions and must be installed via adb / fastboot. Article was not specific on the reason but may be the cause.
Added updates to version 3.4.42 for both 5.1.0 and under. The 5.0.2 zip should work for all stock and AOSP Roms from 5.0 - 5.0.2. Because of changes in 5.1.0 boot.img 5.1.0 will not boot when used with a lower Android Version.
Slightly disappointed as today had planned on posting full Starship Rom but now updating for 5.1.0 so maybe another week maybe two
So any details on what this kernel does? Or is our just close to stock?
CM12 Kernel is on hold until 5.1.0 version update. No reason testing anything new until can confirm everything will still work next week. Also figures the same week I had planned on posting the full Starship Rom the 5.1.0 update hit so now am back in testing optimizing phase for a bit longer.
3.30.2015 update
Linux version has been updated to version 3.4.55
All MR1 changes added to the 5.1.0 AOSP Kernel have been merged into the Kernel
https://github.com/Starship-Android...mmit/8ed8c47ff15f1c5fdd6707f7a52f76110aed6cbf
4.6.2015 update
Not much on the AOSP/Stock side. Wanted to post a cm12 update so decided to post the AOSP/Stock kernel earlier than I would normally with a few Linux version update patches. With that said updating the Kernel only takes a minute or so and not like asking to flash a new Rom. Kernels are easy and these days faster to flash than g-apps. Also used the 5.1.0_r3 source to compile the boot image for 5.1 instead of 5.1.0_r1 source I had been using. Honestly though did not check if anything changed that is packed into the boot.img along with the Kernel between r1 & r3 so may or may not make any difference what so ever.
Forgot, marked the cm-12.1 kernel as beta just because cm-12.1 is pretty much beta. Otherwise the Starship 12.1 Kernel is the Starship CM12 Kernel merged with the Cyanogen 12.1 Kernel . Not that the two had been far apart to start but the 12.1 CM Kernel merged into the Starship cm12 kernel clean as a whistle with 0 conflicts. Was pretty happy about that so going foreword will just be working on the 12.1 Kernel with the Starship cm-12 Kernel soon going the way of the 5.0 - 5.0.2 Stock/AOSP Starship Kernels.
Now finally since the actual Starship Rom I have been working on since the darn preview release ending as mostly caf based with CM-12.1 coming together can start updating from 5.0.2 into 5.1 as had just finished going over the first draft and was about to post when the 5.1 update hit. Otherwise wanted to post the first draft and then go over the entire Rom a second time looking over the theme images, features and optimizations with a magnifying glass.
Have updated both Stock / AOSP and cm-12.1 Kernels up to Linux 3.4.65 with a few other additions and weeding. Has and been running pretty sweet on both so far.
Stock / AOSP 3.4.65 Kernel boot.img has been compiled using the 5.1.1 AOSP Source and tested on both 5.1.0 & 5.1.1 with no issue and as mentioned above running pretty sweet.
I cant install on aicp 5.1.1
Sent from my Nexus 5 using XDA Premium HD app
Related
As usual, pointing to the post concerning this ROM from its main team HERE
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CarbonRom is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look at, build, and use our code on CarbonDev GitHub.
We would like to thank CyanogenMod for their device trees, framework/settings mods and their code that was incorporated into this project. We also extend our gratitude to the devs whose code that we have incorporated. Proper authorship has been maintained and can be viewed on our repository.
Special thanks also go to Slim Rom for some of their features, PA, AOKP, and anyone else we may have borrowed commits from that hasn't been mentioned here. If you feel you have been unfairly left out, please - let us know.
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! If you have questions, ask your fellow users or ask us in #teamcarbon on freenode IRC.
1.6 is a pretty big update for us! Check out the changelog on our goo.im page for more, but here are the highlights:
-We've fixed PIE! It no longer decides to be invisible from time to time.
-We fixed the battery charge light! None of us use it but apparently you guys are just nuts for it!
-Dark Carbon! Huge props to Slim Roms for coming up with this unique and awesome feature.
-Lockscreen theming
-CM skinny battery is back!
-Volume key lock on silent mode option
-Backup tool - if you're flashing a new version of Carbon and already have the required version of gapps installed, it will be backed up and restored during install. This applies to system apps and custom host files as well. Please note that you should only dirty flash from Carbon to Carbon. It's ok if it's another version or a nightly - just not over other roms. Super handy for you crack flashers. Make sure you've got the most recent Gapps though, and if you're flashing from a factory reset, you'll still need to install it after install of course.
-Long pressing the "clear recents" button clears the cache
-3.4 kernel on D2xxx devices. It's finally stable enough where we're comfortable with this - remember to only flash other 3.4 kernels or it will not boot as there are rom-level dependencies.
-AOKP's awesome new navbar settings
-NFC polling mode for when you want to keep your screen off and scan tags
-MMS and call "breathe" feature. Makes the notification icon fade in and out.
-Mute dings when changing volume
-Disable/enable CRT effect on screen on/off.
-3rd party keyboard bug fixed
-deodexed again
-stability and speed enhancements
-a million other little things as well - we basically don't even sleep anymore.
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Carbon Updates
Join us on these Social Media Channels to keep yourself up-to-date on all the latest Carbon news, updates, contests, and more! Join our completely open Google+ community for insider conversation with devs and other users!
Who is Team Carbon?
andros11
BigShotRob
dg4prez
Kejar31
mattmanwrx
morfic
nocoast
pixeldotz
slick_rick
winner00
Change Log
Carbon change log HERE
6.02.13 -
Initial release "nightly" build
Fixed Camera
Fixed GPS
6.09.13 -
Synced to Chad0989's trees
Synced sources
Uses chad's -chad branch not fb branch kernel, crpalmer's kernel may work with this build.
6.11.13 -
HALO implemented
6.30.13
Code:
Synced back up with chad's trees
Synced with Carbon source
-Removed for space, post is to long
7.15.13
Code:
Device tree:
Updated with *SOME* of chad/flyhalf/crpalmer's recent work:
https://github.com/CM10DNA/android_device_htc_dlx/commit/b18cbc01baf535de447b44675727ca91b7548bea - cleanup more inline with cm *note* not all changes were done, it was causing issues with Carbon.
https://github.com/CM10DNA/android_device_htc_dlx/commit/9a01d0428755502b17cd2d5854fd293da9b6f143 - updates from m7
Kernel:
To many to list one by one, however visit here https://github.com/CM10DNA/android_kernel_htc_dlx/commits/cm-10.1-chad
And look back to june 30th which was my last pull.
Change log removed for space reasons (post is to long now)
8.06.13:
Tried out the BT fixes from Chad's CM10.2 stuff, so it may or may not work.
Current sources, should be the same as the 8.1.13 final stable releases for Nexus devices.
Change Log 8.06.13
The post is to big for XDA posts now, so instead I'll include a link to the changelog itself!
From here on ONLY use 4.3 gapps, I don't want to see any reports of broken cameras, keyboards or locking up if you are on anything besides a 4.3 gapps!
8.09.13
Fully updated to 4.3 Jellybean source
Fully updated to chad and crew's latest work on kernel/vendor/device
Use only the included kernel for now, crpalmer's 3.1.2 kernel is not fully compatible and will cause display and camera glitching.
Use only gapps for 4.3
A complete revamp of Carbon, they're starting over from the ground up so you may notice a lot of features missing, such as halo, expect these to return soon. What you can also expect is a smooth fast ROM with a solid foundation to build upon!
8.12.13
Updated source
BlueTooth now turns on (how well it works I can't test)
Single build, for now GSM is at least somewhat working on the CDMA build, so for now, pending further investigation, only a single "unified" version is available.
8.19.13
Updated souce
Updated with Chad and company's latest awesomeness
Features are beginning to trickle back in, Halo is back, etc.
Compatible with crpalmer's latest kernel (and .torrented's should also work)
Change Log 8.19.13
8.26.13
Updated Carbon source (ribbons?)
Updated with chad and groups work:
Device:
- Use correct mic for Google Search and other voice apps (bottom, not the top)
- Change back to HTCQualcommRil (from HTCCDMAQualcommRil) * CDMA build only
- Custom recovery graphics
- Sim hotswap will no longer prompt for reboot
- Everything from the 17th to today
https://github.com/CM10DNA/android_d...ommits/cm-10.2
Kernel:
- Hardware VSync support
- Missing clocks added
- ROW Scheduler added
- Everything done for the 14th to today, I'm not typing that all out
https://github.com/CM10DNA/android_k...ommits/cm-10.2
ROM:
- Carbon Fibers updated with a new swype style
- Ribbons returns from AOKP
- See change log on the site as usual
8.29.13
- Updated source
- Removed default showing of the overflow menu button, most hardware key map this and prefer to save the screen space.
- GSM Only: Changed default to WCDMA preferred from GSM/LTE: Should help with initial issues with calling/sms/mms maybe not working on some networks.
- Device, Kernel, Vendor trees otherwise untouched from last build.
- Listview Animations and Interpolator (Carbon Fibers > Interface)
9.13.13
- Updated source
- Built against the M7 kernel
- Includes everything done up to a couple of hours ago.
- NOT Global, CDMA and GSM versions will be needed still.
- CM's enhanced NFC added, I can't test it so any reports would be appreciated.
- MUST CLEAN FLASH THIS NO MATTER WHAT
- Compatible with crpalmer's 4.x.x kernels as far as I know.
9.13.13- B2
Removed qcom keystore to prevent hot reboot on display off.
9.13.13- CDMA B3
Correct issue causing bootlooping on the CDMA build, GSM didn't have it.
9.15.13
Updated source build:
Halo updates from PA
Add color support to text only battery
Fix network speed statusbar indicator traffic color on reboot
Fix reboot menu not being themed
Minor changes
9.16.13
Updated Carbon source:
Small stuff
Corrected QCOM keystore issue (thanks crpalmer)
9.23.13- Part Deux
Update 9.23.13
Updated Carbon source
All updates for the device/kernel sources.
Things that were messed with include the GPS HAL, some display stuff, camera stuff, and more. If you're interested in the details...
Device:
dlx: Import GPS HAL from jf
dlx: HTC camera expects insecure MM heap
dlx: enable option to set button brightness
Kernel:
Large amount, so I'll post the commits from last update, not each one. Not all concern the dna directly. Quite a few concerning bcmdhd, kgsl, msm_fb and other goodies
FROM HERE
TO HERE
Apparently the blank display was due to changes Carbon made to msm8960-common that I hadn't thought to look in on, and it changes quite a few things concerning the display. For now I have reverted to the CM common tree to correct the display issue.
12.5.13:
Initial bringup to KitKat 4.4
UNTESTED, CDMA Version only for now.
New folder for the 4.4 ROM here http://pio-masaki.com/DroidDNA/Carbon-KK
Please use an updated 4.4 GApps package!
Please CLEAN FLASH this only!
Please flash this with the latest 4.4 compatible recovery!
12.10.13:
CDMA only
Updated source and trees
I still can't test so those who had pervious issues (data, MMS) please give this a try and report when you have time.
1.22.14:
CDMA only, may be Global.
Updated build, untested as I lack the device now, please report any issues!
1.29.14:
Updated sources
Camera should work now
Please see if the Settings>Carbon Fibers> Interface FC still occurs.
As usual use the 4.4 GApps that has worked for you so far.
Not on pio-masaki.com yet, you can nab it now here http://d-h.st/Zsj
2.2.14:
Updated sources.
Camera and Interface FCs were corrected last build, should also be alright here.
4.4 GApps that you usually use.
Available on pio-masaki.com
2.5.14:
Updated sources.
Check that the carrier, date/day/whatever is proper and that the data connection icons are correct (IE no more roaming in 3G etc)
For those with speed issues, a report on that would be appreciated.
4.4 GApps that you used last time.
Available on pio-masaki.com
2.9.14:
Updated sources
Built because I was already on my 8th build of the day, why not?
4.4 GApps that you used last time.
Available on pio-masaki.com
2.20.14:
Updated sources
Built because my wife hates me and the couch sucks
4.4 GApps as usual
Available on pio-masaki.com
3.8.14:
Updated sources
Built because why not, its been awhile.
4.4 GApps as usual
Available on pio-masaki.com
4.7.14:
Updated sources
Built because its been a damn month, that's why!
4.4 GApps as usual
Available on pio-masaki.com
6.23.14:
4.4.4
Updated sources
JustArchi optimizations implemented
FULL 100% -03 built ROM, not just portions
Linaro 4.8 toolchain
Built as user instead of userdebug, odexes the ROM and disables some of the background logging
Updated Adreno candies
Peek
Available on pio-masaki.com in the usual place, however look in the SS folder as this is no longer just Carbon.
Instructions:
Please clean flash this, there's so many extra settings that dirty flashing will likely cause problems. If you dirty flash, please don't report any issues until you flash clean and the issue occurs again!
Please use a proper 4.2.2 Gapps package, using inversed or any modded versions can and likely will cause issues, please use the current 4.2.2 from goo.im, if you use inverted or modded Gapps, please don't report issues until you clean flash with a proper package from goo.im!
If you are not S-OFF you will need to extract the boot.img and flash it separately, either flashGUI or fastboot, your choice, needs done.
S-OFF:
Download the ROM for your needs, CDMA or GSM.
Download the current 4.2.2 Gapps from goo.im or pio-masaki.com
Place files someplace useful
Boot into recovery
This part assumes you know how to operate your installed recovery
Wipe system
Factory reset
Wipe dalvik
Flash CarbonROM
Flash Gapps
Reboot
Let settle for a few minutes after booting
Setup phone as usual
If you have issues on first boot, flash the ROM only, then after it boots, reboot and flash Gapps then manually setup your phone in settings.
CDMA version: for use with Verizon, NOT for any other network.
GSM version: for use with GSM carriers, NOT for Verizon.
Global verison: for use with BOTH Verizon and GSM, no different build required
FAQS
If you didn't read the bugs list in the first post, go back up and read that now, asking the same questions over and over is a trademark of xda and I hate it, please read the change log and bug list before posting questions or reporting issues.
Q. I want to report an issue, can I just post it in your thread without reading or doing any basic troubleshooting, googling, reading or wiping?
A. Well you CAN, you may be ignored or flamed for it. Please read above, and please read the Bugs and Change Log lists before reporting anything. Please flash a clean download, flash a clean wipe, and don't restore stuff from TiBu, that's basic troubleshooting, check if the issue persists, if it does, then feel free to post about it.
Q. Is this daily driver ready?
A. Can't answer that, what a person needs from their phone varies from person to person, what I may consider fine for my use may be 500 kinds of broken for another user. Example, I don't use my camera often, maybe once a month, and my BT has never been turned on for the last 5 devices, for me broken BT audio and camera doesn't make it a non daily driver ROM. Please read and decide for yourself if features included outweigh the broken, or if broken things are required for your comfortable use of your device.
Q. How can I build my own versions?
A. For now you can use the existing CM tree and build it that way. Any further help can be asked as needed.
Q. Can I use -insert kernel name here-?
A. No. Well ok you can, but please don't report any issues while running anything besides what came with the ROM.
Q. Your files all download as index.php!
A. This happens on certain browsers, namely the stock browser and Chrome. You can either use another browser (naked and dolphin don't do this) or simply rename the file to something useful, like "piostotallyepicawesomesaucedrizzledromthatrocksyourass.zip"
Q. Can we do random bantering and good natured fun poking in your thread?
A. Sure, feel free to go OT on occasion, I'm all for having FUN on xda, even if some are not. I would like users to feel completely comfortable in my thread with no worries of me coming down on any thing not ROM or development related, I don't run a strict thread as many know by now. What I don't want is flame wars, though. Please keep a limiter on what is good natured fun as we all know things can get out of hand quickly. If someone is taking offense to something going on and its made known, please end it there with no hard feelings.
Bugs:
None specific to Carbon
Downloads:
Please visit pio-masaki.com for all my ROM builds
Kernel source used:
https://github.com/CyanogenMod/android_kernel_htc_m7
Whoop!!!! I heard rumors! I'm about to no sleep and flash this tonight...thanks so much for your hard work!
I downloaded this from your server and running it now. Seems very smooth and I like the breathing effect of notifications. You need to rest!
So I see this is based off the Cyanogen Mod tree. Does that mean the ROM has the same bugs as it such as bluetooth?
Also, how does one download it?
Shamrock13 said:
So I see this is based off the Cyanogen Mod tree. Does that mean the ROM has the same bugs as it such as bluetooth?
Also, how does one download it?
Click to expand...
Click to collapse
Didn't notice the placeholder post? I was still making the posts lol
And yes, generally it will have whatever issues CM currently has.
Shamrock13 said:
So I see this is based off the Cyanogen Mod tree. Does that mean the ROM has the same bugs as it such as bluetooth?
Also, how does one download it?
Click to expand...
Click to collapse
Goto www.pio-masaki.com and download from there
@pio,
Really nice work man.
Using it for the last 2 days and I can say that its the smoothest ROM out there. Paired with crpalmers kernel its SWEEEEEEEEEEET.
Tapatalked from TF300T with AOKP goodness
Pio is a ROM building machine! He probably dreams about code and bug fixes...lol
Websites going down at 3am CST for update and backup...only be down about 20 mins
Updates and backup done. Websites up.
Sent from my Nexus 7 using Tapatalk 2
pio/guys,
I just want to ask, since I have to wait until my battery charges before I flash... How are you liking this ROM compared to PAC/Revolt? Also since it's CM10.1 based it should have all multi-touch issue fixed right? ( I would hate to flash & find out my kid can't play his Gunman Clive again, that would mess him up. lol )
Also I read that maybe we should keep the STOCK Kernel on this ROM instead of using the AOSP Kernel. Did I read right or misunderstand?
pio, you are the Gandalf of the HTC Droid DNA, you indeed are working some sweet magic.
THANK YOU! Ohh and like everyone is saying..... Get some REST! :cyclops:
Epic 4g said:
pio/guys,
I just want to ask, since I have to wait until my battery charges before I flash... How are you liking this ROM compared to PAC/Revolt? Also since it's CM10.1 based it should have all multi-touch issue fixed right? ( I would hate to flash & find out my kid can't play his Gunman Clive again, that would mess him up. lol )
Also I read that maybe we should keep the STOCK Kernel on this ROM instead of using the AOSP Kernel. Did I read right or misunderstand?
pio, you are the Gandalf of the HTC Droid DNA, you indeed are working some sweet magic.
THANK YOU! Ohh and like everyone is saying..... Get some REST! :cyclops:
Click to expand...
Click to collapse
Unless you are flashing bootloaders it is extremely hard to screw up. I flash ROMs with less than 10% without even thinking twice and never had a problem. Do what you feel comfortable doing, anything over 20% would be fine IMHO.
I personally prefer the other all in one ROMs he has released. PAC is my favourite as it has every feature I want. If you don't care about Paranoid Android's Hybrid Properties then flash Carbon as it runs smoother for some users.
uppon2 said:
Unless you are flashing bootloaders it is extremely hard to screw up. I flash ROMs with less than 10% without even thinking twice and never had a problem. Do what you feel comfortable doing, anything over 20% would be fine IMHO.
I personally prefer the other all in one ROMs he has released. PAC is my favourite as it has every feature I want. If you don't care about Paranoid Android's Hybrid Properties then flash Carbon as it runs smoother for some users.
Click to expand...
Click to collapse
Cool I hear that, it's just that I want to be able to play with the ROM after I flash. If I flash a ROM at 10% or so then that REALLY limits my time with the ROM, because then I would have to put the phone to charge.
I just went to pio's website & downloaded Carbon but the file I downloaded is called "index-1.php" instead of "CARBON-JB-UNOFFICIAL-20130602-dlx-CDMA.zip".
Is that OK or is there a problem here? I am not going to flash that file until I get confirmation that it's supposed to be like that.
Thanks to anyone who can verify & help. This is the first time this has happened to me on one of pio's ROMS.
Epic 4g said:
Cool I hear that, it's just that I want to be able to play with the ROM after I flash. If I flash a ROM at 10% or so then that REALLY limits my time with the ROM, because then I would have to put the phone to charge.
I just went to pio's website & downloaded Carbon but the file I downloaded is called "index-1.php" instead of "CARBON-JB-UNOFFICIAL-20130602-dlx-CDMA.zip".
Is that OK or is there a problem here? I am not going to flash that file until I get confirmation that it's supposed to be like that.
Thanks to anyone who can verify & help. This is the first time this has happened to me on one of pio's ROMS.
Click to expand...
Click to collapse
Rename the file to something.zip . it does that with chrome or stock browser, user Firefox on android for downloads to fix the filename issue. Other than being named wrong, the file is fine.
Sent from my Nexus 7 using Tapatalk 2
diesburg said:
Rename the file to something.zip . it does that with chrome or stock browser, user Firefox on android for downloads to fix the filename issue. Other than being named wrong, the file is fine.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
OK I will rename it "something.zip" as you said with out the quotations marks & flash. Thank you for the heads up. You are the man! :good:
Awesome going to flash this now! Does this include the halo framework or is that not released yet?
My head is spinning! Which way to I turn? Thanks pio!!
Sent from my HTC6435LVW using Tapatalk 2
I added the index.php issue to the FAQs last night.
Personally I use crpalmers kernel with this ROM, its great, by all means use it.
Personally I use carbon because I don't use PA features. Second is ReVolt, then PAC, though since the recent apps fix in PAC its a little harder to say lol
No halo in this, its in the works, though. The carbon team has released a special halo version for some devices a couple weeks ago, so it may happen once halo matures a little more.
Tapatalked from my HTC DNA - Carbon
Hey pio is the 20130602 build the same build from a couple days ago? Or did you update it? Just wondering because my WiFi isn't working. I saw yesterday you said you where going to upload new builds with WiFi fixed. Thanks again for the awesome ROM
Sent From My HTC DNA Carbon
I clean flashed this coming from a Sense 5 rom and cant find any of my old data anywhere. The free space on the card has not gone up but I cant see to find my stuff. I tried storage/emulated/0, storage sdcard0, everywhere i can think of.
coachcrey said:
Hey pio is the 20130602 build the same build from a couple days ago? Or did you update it? Just wondering because my WiFi isn't working. I saw yesterday you said you where going to upload new builds with WiFi fixed. Thanks again for the awesome ROM
Sent From My HTC DNA Carbon
Click to expand...
Click to collapse
It was fixed, also if you flash crpalmers kernel wifi will work as well.
Budwise said:
I clean flashed this coming from a Sense 5 rom and cant find any of my old data anywhere. The free space on the card has not gone up but I cant see to find my stuff. I tried storage/emulated/0, storage sdcard0, everywhere i can think of.
Click to expand...
Click to collapse
Its in /data/media, this is discussed numerous times in various threads so I won't get into much detail, but copy from /data/media to /0 and it'll work fine in 4.2 ROMs. To go back to a sense ROM move back from /0 to /data/media. After you can delete /0 but don't they to delete /data/media, just what may be in it as that's your internal SD card.
Tapatalked from my HTC DNA - Carbon
I posted this originally in the E973 forum, but there's no traffic there anymore...
Yet another unofficial Cyanogenmod 11 ROM, this one with working LEDs for Canadian phones.
Sources are mostly chadouming's with haze028's device repo. LED driver is courtesy of paulicat. I've also included an init.d script by paulicat to tweak some governor/audio/video settings.
thanks to mathsz for his support, paulicat for his LED driver, chadouming for his repo's, houstonn for his modified frequency tables and haze for his putting up with my dumb questions.
Sources are here: link
Latest ROM will be on my androidfilehost
I personally use PA stock gapps with the banks camera addon.
I'll try to update this semi-regularly, I'm not a coder but I'll try and fix any bugs that are found.
I know the official nightlies are out, but I'm not happy with them, so here ya go!
CHANGELOG:
12/19/2013 - latest build added 192 MHz min CPU frequency, torch FC's fixed.
12/31/2013 - lockscreen HW button customization is working
01/02/2014 - reverted to stock frequency tables, was seeing some soft reboots on my phone.
01/04/2014 - made a few additional kernel tweaks for stability (explicitly disable modules and gpu overclock), equivalent of M2 build.
01/05/2014 - cherry picked commit for status bar settings, as well as lockscreen hw buttons. At this point, this should have feature parity with any 10.2 build (I think). This build seems to be rock solid stable and snappy.
01/09/2014 - Increase default voltages to be identical to stock, removed a kernel tweak for increased bus speed. Stability is more important than benchmark performance to me. Anyway, very stable now and CM seems to be adding in features/bringing up stuff from 10.2 pretty quickly. I've still just added the HW button cherry pick and everything is working as intended. Give it a try, especially for E971/3.
03/27/2014 - Back to building for geeb... kernel is updated with a lot of linaro patches, ROM and kernel are now built with linaro 4.8 toolchain. Low cpuclocks (162 MHz minimum frequency). I haven't enabled any overclock, but everything is smooth and battery seems to be excellent, at least for my use case. Enjoy!
04/22/2014 - new build is up on androidfilehost, new kernel (thanks mathsz and brothaedhung!) - it's a pretty straight up port from faux's latest with some cherry-picks for battery. low cpu clocks are enabled and battery is amazing. the bootimage blanks out partway through boot, but other than that it's really good. I included the nav bar/hard key disable from official cm, and google camera works perfect
05/28/2014 - So, I've been running builds, but haven't been updating the OP... Anyway, I've got a new kernel and the 0528 build is based on the latest changes to stable/cm-11.0 branch. It's M6 but with any commits CM has made recently, since they're still updating their github apparently. Kernel has fast charge, voltage control, battery life extender, low clocks, sound control. Governor is defaulted to ondemand, scheduler is noop, and hotplug is Qualcomm's mpdecision daemon. You should see battery life in excess of 4 hours SOT, depending on gapps package (I use PA stock, and get 4 hours no problem). Kernel is based on paulicat's port of the google stock kernel. No other frills in the kernel, no intellidemand, intellithermal, intelli*
This one is my DD, it's stable and everything works as intended.
06/22/2014 - Up to 4.4.4, latest nightly is in CM-11.0/Nightlies folder on androidfilehost.
06/30/2014 - Latest nightly has a fix for linaro 4.8 and ART, ART now works fine on this ROM. Battery life is amazing.
07/01/2014 - CM updated the stable/cm-11.0 branch today, so I did a build. ROM is up on androidfilehost, under CM-11.0/Milestones. I updated the kernel with the latest commits from CM as well.
07/08/2014 - Updated based on latest stable/cm-11.0 branch commits.
07/13 - CM keeps updating the stable branch, so I keep cranking out builds
07/15 - The most recent ROM has working storage encryption thanks to a commit by shelnutt. I've also uploaded a flashable zip of the kernel I use for this ROM here
10/07 - New build based off stable/cm-11.0 branch is up. Very stable and smooth so far.
CM-12.0
I've started building unofficial geeb CM-12 builds. They're up on androidfilehost. Starting this coming week, I'll be posting builds with my own kernel, brought up from kitkat. The builds that are currently posted are using a modified version of brothaedhungs lp kernel.
02/03/2015 - Sorry guys, I've been slacking off on updating this post. All current builds are using my KK kernel brought up for LP, with stock frequencies instead of low_cpuclocks. I'll be posting a new build later this morning. As far as I know, this is the only CM build still using mako sources.
02/26/2015 - New build. CM resync.
03/03/2015 - New build. I hacked up sepolicy to allow init.d scripts access to sysfs, and all of my custom tweaks are working. I also cherry picked "launch default music player when headphones connected". Also CM resync.
CM-12.1
04/16/2015 - Started building CM-12.1, using updated mako device and vendor tree.
04/20/2015 - cm re-sync, added some fixes to kernel and device (from cm)
04/23/2015 - posted 04/22 build. cm re-sync, updated to 5.1.1
r.asimi said:
So I see there's a few downloads, but no comments in-thread. I hope that means everything is working well for you guys!
Just a heads up, there's a commit on cyanogenmod's gerrit for hardware buttons on the lockscreen. I'm going to cherry pick it and upload a new build for 12/31 as a New Year's Eve present for everyone!
Click to expand...
Click to collapse
Didn't see this thread, but sometimes a quiet one can mean they have no issues haha. Also Happy New Year to you too!
Sent from my LG Optimus G
Torch issue might be a f up in my device overlay, running a new build and will upload shortly. Torch tile is also missing and I found a commit from shelnutt that *should* fix it.
r.asimi said:
I posted this originally in the E973 forum, but there's no traffic there anymore...
Yet another unofficial Cyanogenmod 11 ROM, this one with working LEDs for Canadian phones.
Sources are mostly chadouming's with haze028's device repo. LED driver is courtesy of paulicat. I've also included an init.d script by paulicat to tweak some governor/audio/video settings.
thanks to mathsz for his support, paulicat for his LED driver, chadouming for his repo's, houstonn for his modified frequency tables and haze for his putting up with my dumb questions.
Sources are here: link
Latest ROM will be on my androidfilehost
I personally use PA stock gapps with the banks camera addon.
I'll try to update this semi-regularly, I'm not a coder but I'll try and fix any bugs that are found.
I know the official nightlies are out, but I'm not happy with them, so here ya go!
CHANGELOG:
12/19/2013 - latest build added 192 MHz min CPU frequency, torch FC's fixed.
12/31/2013 - lockscreen HW button customization is in, but for some reason no option for torch (the reason I cherry picked in the first place)
Click to expand...
Click to collapse
12/31/2013 - fixed the torch issue, torch tile and HW lock screen button is working. Build is uploading now (14:18 EST) and should be done shortly.
Running 31st rom.. Rock solid and stable!! Great battery life and working LEDs!! Awesome job! Thank you and happy new years!
Sent from my Optimus G e973
Who says the LG devices don't have huge choices. ?? Here's one more reason to negate that statement. Thank you , for this rom. Now , we have one more to choose from.
Happy New year.
Hey guys, I just wanted to post an update in-thread. There is a battery drain issue with PA gapps, so what I've been doing personally is flashing the ROM, flashing the PA stock gapps, then flashing banks standard gapps overtop, then flashing the banks camera addon. It's annoying, but it fixes the battery drain.
Also, I f'ed up the 01/02 build by including some stuff in the 99kerneltweaks file in init.d, the problems aren't going to keep you from running the ROM but it makes the min frequency kind of random. I've attached my current 99kerneltweaks, and will include it in builds from now on. Remove the .txt extension, I had to add it because otherwise the forum wouldn't let me upload it.
Removing the 192 MHz setting from the kernel has resolved the soft reboots I was getting, and doesn't seem to impact battery life very much, I was getting way more drain from the PA gapps issue.
Just a heads up for anyone using my ROM, CM merged a lot of features from CM 10.x back in this morning. I'm running a new build now and will post it later today/this evening.
I hope this is a small request, but is it possible to have a flashable version of your kernel?
Mainly because your kernel fixes my problem with wifi tethering on CM11.
btw, love the rom. seems to be more stable than the official nightlies.
sucsss said:
I hope this is a small request, but is it possible to have a flashable version of your kernel?
Mainly because your kernel fixes my problem with wifi tethering on CM11.
btw, love the rom. seems to be more stable than the official nightlies.
Click to expand...
Click to collapse
I'll try and make a zip for you tonight.
I just uploaded a nightly with most of the 10.2 features merged back in. There is a bug w/ emulated storage, after Koush merged in an updated superuser the CM file manager won't see /storage/emulated/0 in root mode. The workaround is to set CM file manager to prompt mode, and then you'll never even see an issue. /storage/emulated/legacy is available in root mode, though I don't know why you'd need root for your internal storage. I think it's an SELinux/zygote conflict but I haven't figured out the fix just yet.
There's a new build up - 20140123, which has a fix for autofocus. I need anyone running it to keep an eye on battery drain and let me know if they see anything out of the usual... I'm running it myself and haven't seen any problem so far, but there's one report of an issue with the patch on geeb.
Thanks!
everything works great!
Thank you very much!
I would like that kernel too please
connect phone to USB. Start adb. Put device in bootloader. Fastboot flash boot. Boot.img
Sent from my Geeb using Tapatalk
I've uploaded a flashable kernel zip to my androidfilehost. Please keep in mind, it's just the zimage, no ramdisk or drivers so LEDs etc will not work the same.
Battery life is still great.
The only minor issue I see is the ambient light sensor dies after awhile. This is the same with official cm11 and the PA 4.0 releases. Not a big issue but it's interesting that it's across 3 roms.
mathsz said:
connect phone to USB. Start adb. Put device in bootloader. Fastboot flash boot. Boot.img
Sent from my Geeb using Tapatalk
Click to expand...
Click to collapse
I'm retarded. I forgot that you can easily do this.
sucsss said:
I'm retarded. I forgot that you can easily do this.
Click to expand...
Click to collapse
nah, it's easy to forget. Unless you play with roms all the time, play in the source a bit or are just flash-happy, it's realllllly easy to forget.
FPBug: Meet the very first stable kernel for the Galaxy S2 i9100, S2 AT&T i777, S2 Epic 4G Touch d710 and Note n7000 since Gingerbread days
Every single Android 4.x kernel for these devices has had a serious bug (FPBug) that randomly corrupts the state of processes, starting with Samsungs's stock ICS and JB and spanning every custom kernel out there newer than Gingerbread.
STATS: 500+ kernel downloads in 2 days, wow!
RELATED: Make sure you check out my TRIM-enabled kernels updated with the FPBug fix.
UPDATE: A fix for FPBug has been merged into CyanogenMod's cm-11.0 branch! The fix has not made it to the stable/cm-11.0 and cm-12.0 branches yet. Changes: this one and the previous 12. Commits: this one and the previous 12. The 20150111 nightlies are the first official CM 11 nightlies to incorporate the fix.
A little bit of history
As Android got more complex, the effects of this bug grew more visible, to the point of making the platform completely unstable for some users. Complex apps would fail for no reason, GSM, 3G and WiFi connectivity would randomly be lost, music playback would stop and require a reboot, camera would fail, internal storage and SD cards would become inaccessible, installed apps would disappear, users would experience battery drain issues ranging from inability to enter deep sleep all the way to phones becoming very hot, and the list goes on and on.
These failures all seemed unrelated and their cause was very hard to track down. Partly because events happened randomly and were not reproducible, but mostly because the bug undermines the very assumptions programmers deal with when creating any kind of code. And so years passed and the common cause of all this pain was never identified. Many ROM developers abandoned the platform out of frustration.
Then finally this past March, when analyzing the random loss of access to storage, user cgx observed a corruption event for the first time, and a connection between all these unrelated issues, sometimes hypothesized, was suddenly found. The corruption seemed to have happened in the stack, but it was later suspected then confirmed that the corruption actually happened directly in the registers of the floating point unit of the CPU. Yet processes that did not use floating point at all were also affected, because the GCC compiler typically spills registers into the FPU and uses FP and NEON instructions for optimization.
These findings allowed the creation of a stopgap fix for the "music bug" that shielded the FUSE process (which manages access to storage) from corruption in the FPU. The fix was widely applied and effectively eliminated all bugs resulting from sudden loss of storage access and returned the platform to pre-Android 4.3 stability levels: ie, sort of stable enough to be used as a daily driver. Later a working detector for the elusive bug was made and it was confirmed that all kernels since Gingerbread were affected (a thing that was already suspected given that the FirefoxOS people had described similar symptoms in 2012 under stock Samsung ICS). Finally enough of a root cause was hypothesized and a fix was worked out. And if this were not good enough news, user Entropy512, the exynos platform hero who saved us all from brickbug, has hinted that official Lollipop from Omni is now a possibility.
A short description of what the fix does can be found here.
Update
User zeitferne worked non-stop throughout this weekend and made amazing progress. He found a couple of missing commits that are apparently needed for the FPU state tracking to work through power state changes, he discovered that the FPU in CPU0 is the one that actually gets the corruption, he found an explanation why this bug never affected the 4412 platform (Galaxy S3, Note 2, etc), he narrowed down the conditions for the corruption, and finally output an alternative patchset that apparently fixes the FPU state restore optimization rather than just disabling it as mine does.
Kernel developers are encouraged to merge his changes in lieu of mine once enough testing is done and @zeitferne green-lights the patches. This is important as it might fix as-of-yet undetected bugs or prevent bugs arising from future changes. In the meantime, eager maintainers can merge my fix which is by now well tested. Users will only see a small (<< 1% ?) performance increase with zeitferne's patchset and don't really need to bother with this; my advice for them would be to wait for the changes to trickle into their kernel of choice. AMAZING JOB ZEI!!!
2nd UPDATE: @zeitferne has green-lit his patchset! Kernel maintainers merging it please take note: 1) Make sure my fix is removed before applying his, otherwise there will be a small performance hit in the resulting kernel. 2) Both our fixes also affect the 4412 platform (i9300, n7100, etc) in slightly different ways, and the effects of this have not been properly tested. I must recommend that some testing be done before distributing FPBug-fixed 4412 kernels. Please report your test results back to this thread.
WARNING: A problem was reported with zeitferne's patchset.
FOLLOW UP: @zeitferne made some changes to his patchset and initial testing looks good.
AND FINALLY: The patchset was merged into cm-11.0! (See this change and the 12 previous ones.)
Downloads
You will find kernels for various CyanogenMod releases, M-snapshots and nightlies here. These kernels are guaranteed to work only with the exact matching version of CM specified in the last part of their filenames. But in reality they should work with most versions of CM that are close enough. (Don't ask me about this, I don't know, I don't even have any of these phones! Just try them and see for yourself if you are feeling a little adventurous.) For other ROMs i expect this fix to be merged in a matter of days after some more testing is done. Please be patient, and KitKat users can flash my music bug fix in the meantime.
FAQ
Q. I have flashed your music bug fix in the past. Can I flash your kernel?
A. Yes! The music bug fix has no downsides. In fact, as a side effect, that fix makes your phone slightly faster and saves some battery so it should be merged in all ROMs IMHO. If you already have it installed leave it in place, but do not flash it again the next time you upgrade the OS. Please do not flash it just for the sake of optimization: since it is based on CM11 M10, it would actually be a downgrade.
XDA:DevDB Information
FPBug-i9100, Kernel for the Samsung Galaxy S II
Contributors
Lanchon
Source Code: https://www.androidfilehost.com/?w=files&flid=22853
Kernel Special Features:
Version Information
Status: Testing
Created 2014-12-19
Last Updated 2015-01-14
(reserved)
Is the BLN included ?
Lanchon said:
And if this were not good enough news, user Entropy512, the exynos platform hero who saved us all from brickbug, has hinted that official Lollipop from Omni is now a possibility.
Click to expand...
Click to collapse
It's not about i9100 ? Right ?
Can't wait till testing is complete and you merge the fix into your trim kernel for the i9100 lanchon. Thanks to all the programmers, testers and commenters in the bug thread for their hard work.
Sent from my GT-I9100 flowing on SwiftKey in Tapatalk
DarkJohn said:
Is the BLN included ?
It's not about i9100 ? Right ?
Click to expand...
Click to collapse
yes, he refers to the i9100 and the n7000
DarkJohn said:
Is the BLN included ?
It's not about i9100 ? Right ?
Click to expand...
Click to collapse
these are all standard CM kernels. please request features on the CM thread.
Lanchon said:
yes, he refers to the i9100 and the n7000
Click to expand...
Click to collapse
Oh God ! Lollipop
I am anxious
@Lanchon thank you very much for ur hard work [emoji122] [emoji122] [emoji108]
Dammit... Never wanted to use CM again... I think I will have to at least for now until it gets integrated in other kernels
Great Job @Lanchon
i never had any GPS problems on my i9100 before ICS. Since JB it has gotten sooooo much worse. I tried atleast 20 different ROMs (JB, KK) and 5 different Navigation Apps. Nothing helps. Currently i am on CM11 M12 Snapshot. Still not better...
Could this kernel also help me with the GPS Problem??
so no bad battery life any more?
Vidura Dissanayake said:
so no bad battery life any more?
Click to expand...
Click to collapse
Yes exactly. With a little more testing a final version should be coming soon. What an awesome Christmas gift!
Thindboy said:
i never had any GPS problems on my i9100 before ICS. Since JB it has gotten sooooo much worse. I tried atleast 20 different ROMs (JB, KK) and 5 different Navigation Apps. Nothing helps. Currently i am on CM11 M12 Snapshot. Still not better...
Could this kernel also help me with the GPS Problem??
Click to expand...
Click to collapse
No it won't solve gps problems. I've had good luck using GPS status https://play.google.com/store/apps/details?id=com.eclipsim.gpsstatus2 and Faster GPS https://play.google.com/store/apps/details?id=org.fastergps from the Google play store. GPS status will download assistance data (A-GPS) and faster GPS setups the proper ntp server for your area. I get fixes in about 10 seconds now.
Sent from my GT-I9100 flowing on SwiftKey in Tapatalk
Everything is somehow faster with this kernel. I flashed the music bug fix with this kernel. Waiting for trim kernel, it will further accelerate the phone.
I noticed that the phone is not heated as before.
You're a genius because you've done a lot for us, s2 community ... And we know that you do not own this legendary phone
Thank you @Lanchon
Sent from my GT-I9100 using Tapatalk
I dont understand does this feature going to be added to cm11 or do i have to flash a zip to add it?
Alucard said:
I dont understand does this feature going to be added to cm11 or do i have to flash a zip to add it?
Click to expand...
Click to collapse
im not part of the cm team and my crystal ball is acting up lately so i cant answer Q1.
this is a kernel, you need to flash it. please read the downloads section.
DarkJohn said:
Is the BLN included ?
It's not about i9100 ? Right ?
Click to expand...
Click to collapse
Cm12 is available?
Alucard said:
I dont understand does this feature going to be added to cm11 or do i have to flash a zip to add it?
Click to expand...
Click to collapse
Waiting for your review for Spirit ROM once you've flashed it.
Lanchon said:
im not part of the cm team and my crystal ball is acting up lately so i cant answer Q1.
this is a kernel, you need to flash it. please read the downloads section.
Click to expand...
Click to collapse
OK so FPBug-V1-src.zip is a flashable zip for fpbug fix for every rom stock jb and kk?And cm-11-M10-i9100-music-bug-fix.zip is for cm11 m10 only?
---------- Post added at 12:36 PM ---------- Previous post was at 12:33 PM ----------
x3dnd3x said:
Waiting for your review for Spirit ROM once you've flashed it.
Click to expand...
Click to collapse
Im on neatrom now ,will be on kk once a stable kk apolo kernel comes out!
What recovery does this kernel has built in? I use 11.15 cm11 custom build my markox and I want to mare sure that I can reflash the rom in a recovery if it screws up. I never used Odin since I got this phone.
Mockingbird said:
What recovery does this kernel has built in? I use 11.15 cm11 custom build my markox and I want to mare sure that I can reflash the rom in a recovery if it screws up. I never used Odin since I got this phone.
Click to expand...
Click to collapse
Lanchon bases his kernel on stock cm kernel, so cwm recovery is built in.
So it has been a long time in the works and feels like have been working on this forever. First it was an AOSP Rom, then Caf and at some point both. For now the Rom is AOSP 5.1.1 based.
Is still not 100% but have decided to just go ahead and post the Rom and improve and update.
If you have seen the Test Flight CM based version that had been posted with the Starship Kernel the overall theme is pretty much the same.
The mission now is to first go over a few parts of the theme that bug me or did not translate well in the CM to AOSP Transition such as lightening up some text so is easier to read with darker backgrounds. Second mission is go over every APK one by one and fine tune the theme and add in any extra features. Will post an update as each APK has been completed. Most of the work is done in some form or another but have spent ages nitpicking everything to death and have an external drive filled with already completed images, Colour XML's and lots of uncommitted features so updates will come rather quickly. Honestly at this point am just going to start with the APK's in Alphabetical order so if you like the Rom and theme but a few particular things bug you just let me know and I will not mind jumping ahead. Also with each Rom update not only expect app and theme improvements but kernel and other system enhancements as most are already lined up and just need to be tested in the Rom's new incarnation. It has probably seen some better days but with my constant picking and changing have gone back and forth with so many things I think its best to just post so Starship is out there and now start finalizing. What is currently posted is bare bones themed and featuring a Kernel I have also spent almost a year working on. If you had used the Kit-Kat version of Starship then already know how fast the Rom will be improved and updated based on legitimate feedback. I know I am making things out like this is an incomplete Rom but have been using and been very happy with what is posted as my daily. Yes still need to improve a few things but the truth is I am never happy with anything I do and would have kept changing direction until Android N.
Until next time keep looking up!!
Installing
This version was not compiled using the new block based zip format so will take a bit longer when flashing the Rom. Just a warning for anyone who may think something is wrong. It Just takes a minute longer to flash.
Otherwise besides first performing the usual Wipe of Caches, System and Data also recommend flashing the Rom first, Gapps second and SuperSU last.
Downloads
Starship Rom
https://www.androidfilehost.com/?fid=24052804347762130
G-Apps
I recommend using the Banks 5.21.15 version of Gapps and have posted a link below. I don’t like reposting someone else’s work but just now discovered the 6.17.15 version seems glichy during the set-up wizard sometimes needing to be in landscape mode when making a selection so have reposted the version used during testing. Have also posted a link to the 6.17.15 version but found for example during the restore option selecting done will only register the selection in landscape mode.
BaNkS-dynamic-gapps-L-5-21-15
https://www.androidfilehost.com/?fid=24052804347762124
BaNkS-dynamic-gapps-L-6-17-15
http://fitsnugly.euroskank.com/?rom=banks&device=gapps
SuperSU
https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
Kernel
I will continue keeping a separate thread for Starship Kernels that may update faster than the Rom so can keep a look out here.
http://forum.xda-developers.com/goo...t/kernel-starship-kernels-01-08-2014-t2997470
In staying with the Rules will find Source for the Kernel that is included here
https://github.com/Starship-Android/android_kernel_lge_hammerhead-starship/commits/lollipop
Starship Github
https://github.com/Starship-Android
Donations
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=MMEVCWUX83SXJ
I am not responsible for any effect using the downloads from this forum my have on any device and you download and use at your own risk.
Screen Shots
Hello, I'm newbie dev trying to build CM13 for Lenovo Phab plus.
I think I'm almost finished with device and vendor, but I cannot figure it out what to do with kernel.
The circumstance is,
I have a stock kernel source which runs in 5.1.1 LP, with version of 3.10.49.
What I want is to make kernel compatible with 6.0.1.
I already know that linux kernel version doesn't have to be exactly same with new Android OS versions and I can just make a few patches in order to run kernel in higher OS.
So I googled and studied(?) for 2-3weeks, but got not many useful informations and I still cannot figure out where to find required patches for 6.0.1 .
So here's what I am not sure about.
1. I found that I can either upstream, merge, cherry-pick kernel sources from higher OS. For instance, if I merge kernel patches (starting from 3.10.50 to 3.18 step by step) and check if the kernel compiles successfully, is this a right thing to do? I am confused whether merging or cherry-picking is required for my situation.
2. I see lots of commits when comparing with other kernel sources in github. How do you find those kinds of patches? -> just keep compiling kernel and if error comes out->search->commit
Always this pattern goes again and again till boot properly?
3. i'm quite curious with backports. What i know is that "backports" are the files which is compatible for lower version kernels. For example, backported audio driver originally based on 4.9 can be used in kernels with version below 4.9. Is it right?
4. If there is an useful links, anything could be helped a lot.
THANKS IN ADVANCE.