Related
I have recreated the romer tool. The purpose of this tool is to replace certain files to make D2 roms work on the droid 2 global. To use simply install my file after installing a droid 2 rom via recovery. This version is designed for ginger-blur based roms such as apex and liberty. Do not flash over aosp roms such as cyanogenmod and liquid. I am currently working on creating a aosp romer tool. Do not use on froyo eaither, as this will temporarily brick your phone. I have tested on both apex and liberty, and sensors,gsm,data, and phone are all working. Please enjoy
Disclaimer: I am not responsible for what you do to your phone. If your phones does not do what you like, becomes 100% useless, or explodes killing your wife and children, it is not my fault. I can garauntee that my file is safe, and works perfectly for what it is designed. Make sure to check before you flash a d2 rom that it does not contain a d2 kernel. This could permanently brick your phone! Just be careful
Download v2.2:
http://dl.dropbox.com/u/46535328/D2G-GingerBlur-Romerv2.2.zip
Thanks:
Thanks goes to fabolous for apex , which is were the majority of the files for my romer comes from.
ChangeLog:
V1.0: original, based off of GRD Rommer.
V2.0:completely remade with no more GRD remains.
V2.1:Liberty tweaks put in build.prop.
V2.2:moto boot logo and boot animation added. I can remove this if it is disliked.
Comments:
Has anyone tested out the aosp romer. I would be happy to fix things or add things as people like. I will gladly update this if anyone wants, I have just been working on other things. I have been taking a look at cm source code, and app development. Also eaither one of these will work on Droid X roms. Haptic feed back will not work though.
P.S. If you download this, and enjoy it, please press the thanks button.
**********************************************************************************************************************
This section is for my romer tool having to do with porting the new 2nd init roms or anything that is based off cyanogenmod 7 or aosp that is originaly designed for the droid 2 or Droid X. I have tested it and can approve that it will work for miui,liquid, and cm. I am not liable if this does anything negative to your phone. To use just flash over an aosp rom for the droid x or droid 2 and enjoy on your global. For now the only thing that does not work is gsm. If i can fix it I certainly will.
Thanks: I thank revnumbers for his cyanogenmod builds, as this is were I took the proprietary files for the d2g from.
Comments:
If any of you want me to add something, or try to fix something, please post and I will see what I can do.
Download/Aosp Romer V1.1:
http://dl.dropbox.com/u/46535328/D2G-Aosp-Romer_V1.1.zip
Thanks:
Thanks goes to RevNumbers for his cyanogenmod 7 build, which is were the majority of the files come from.
Change log:
V1.0: Original, fixes phone,cdma data,keyboard,camera,sensors,etc...
V1.1:Fixes su/root permission error.
Comments:
Don't worry if the phone does not receive signal immediately. It takes it a minute.
I accidently set the permissions for su binary wrong. V1.1 fixes this.
! I would HIGHLY not recomend using anything built of of the D2G's romer !
The reason for that is because that method of porting is considered vastly inferior AND because it had many bugs in it because of it. The romer team from Get R Done also had a lot of strife in it and a lack of knowledge. A straight update of the files will not work well.
It needs redone, not updated.
Thanks for the advice aceoyame . I have tested it, and it works, but I do not know what problems may arise from it. I will work on redoing it
also, if you have the time could you describe the problems into more depth of what is wrong with team get-r-done's flashing process. I am not quite as well educated in the art of writing an updater script as you are I am sure.
Well the biggest issue with a romer vs natively porting is that you have too many files that are for one type of rom vs working for others. The romer will only do Gingerblur based as you have it (that's if sensors and everything else works). It will not do any aosp based roms (liquid, CM, MIUI, etc.) The libs are way too different. If you wanted you could make an AOSP romer and Gingerblur romer. Just pointing out the flaws in it.
Thanks for replying ace. I natively ported liberty on another forum. The reason why I made this is so people can just flash it over any liberty gb rom, instead of me having to make an update for each individual version. I have only tested it on liberty, and on liberty sensors,backlights,gsm,phone,keyboard,and data are all working. I would guess that would apply to any gingerblur based rom. I knew that it would not work on cm,liquid, and miui, and did not really care since thanks to you and other devs we already have those roms made for are phone. This is for those roms that only exist on the d2 and not the d2g
Well grats on fixing the sensors then! Rewriting the romer is something we've been wanting to do but could never get around to it. If it is 100% bug free on liberty than it should work for any gingerblur rom. You got sensors to work which was the big issue with the GRD one then you at least fixed something! I would just test the hell out of it and if it works then you probably hammered out any bugs they had with it. An AOSP one would be nice for the other roms. Feel free to put this on Rootzwiki and the other forums.
Thanks, I will make a asop version when I get the time.
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
The NookieDevs are pleased to announce the CyanogenMod 10.1.3.2 stable release for the Nook Color!
As the "stable" label suggests, all major features of the hardware work and the release should be suitable for day-to-day use on your Nook Color. As the "stable" label also suggests, updates (if any) will be primarily to fix bugs -- new features and big changes should not be expected.
Highlights: (mostly not news if you've been keeping up with CM10/10.1/10.2 nightlies)
Linux kernel 3.0.8, plus hardware support from TI OmapZoom's android-omap3-3.0 branch and board support forward-ported from BN kernel releases.
All of the features of CyanogenMod 10.1, based on Android 4.2.2.
Full 2D and 3D graphics acceleration using the GPU.
Unofficial Bluetooth support, including support for a wider variety of BT peripherals than in previous releases. (The Nook Color lacks a proper Bluetooth antenna, so range will be somewhat limited.)
10.1.3: significantly improved graphics performance and improved battery life over previous CM10.1 releases.
10.1.3: various bug fixes, including fixes for Bluetooth tethering, Adobe Flash Player, and a nasty hardware bug affecting the internal storage of some Nook Colors.
10.1.3.1: fix for a security bug reported upstream which potentially allows an attacker to obtain local root (see the dev thread for details). Thanks to Nico Golde and Fabian Yamaguchi for reporting, Ivaylo Dimitrov and Pavel Machek for working on a fix, and dhiru1602 for reporting a bug in that fix.
10.1.3.2: fix crash when opening "About tablet" in Settings. Thanks to CM's Ricardo Cerqueira for the fix and the rebuild.
Known issues:
Current releases of Netflix do not work with CM10.1 -- version 1.8.1 is the last version known to work. If you want/need a newer release of Netflix, look into the Xposed mod, which provides a workaround for Netflix -- pastordl has done a nice writeup of the process here.
The CyanogenMod Updater app may crash when checking for new updates. Deleting /sdcard/cmupdater and/or clearing the app's data may help.
Download:
https://download.cyanogenmod.org/get/jenkins/51847/cm-10.1.3.2-encore.zip
Code:
MD5: 72d6978a754d5637f28f3c031367781a
SHA1: 316da5997232bb641240c2378fdaa634ce5d50eb
SHA256: b9391d37418322b1960db8edd2a738a44ac2ea12cdeb02a80628c6f95efaa67f
Source code:
https://github.com/CyanogenMod/android_device_bn_encore/tree/cm-10.1.3 (device-specific source)
https://github.com/CyanogenMod/android_kernel_bn_encore/tree/cm-10.1.3 (kernel)
https://github.com/CyanogenMod/android/tree/cm-10.1.3 (manifest for the rest of the CyanogenMod source)
Build instructions (discussion of build issues belongs in the development thread)
This release is the product of much effort by many people over a considerable period: many thanks to fattire, keyodi, eyeballer, krylon360, dalingrin, verygreen, iomonster, nemith, cicadaman, deeper-blue, thedude, mad-murdock, j4mm3r, unforgiven512, scepterr, rebellos, ryands, kmobs, tonsofquestions, hashcode, arcee, hacdan, drmarble, mateor, dhiru1602 and many more. Thanks are also due to the CyanogenMod project, upon which we are building, and Texas Instruments, which provides excellent support for its embedded platforms to the open-source hacking community. (TI's exit from the consumer electronics SOC market is a loss for all of us.)
XDA:DevDB Information
CyanogenMod 10.1 Stable, a ROM for the Barnes & Noble Nook Color
Contributors
steven676, keyodi, fattire, The CyanogenMod Project, NookieDevs, many others (see post)
ROM OS Version: 4.2.x Jelly Bean
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Stable
Current Stable Version: 10.1.3.2
Stable Release Date: 2013-12-18
Created 2013-09-05
Last Updated 2013-12-19
Reserved
Google Apps; other CyanogenMod builds
Google Apps
http://goo.im/gapps
As of 2013/10/09, the latest release for CM10.1 is 20130812, but please check the linked page for updates.
Please make sure that you have the correct Google Apps flashed before reporting problems involving the Google Apps (Play Store, Google Keyboard, etc.).
Other CyanogenMod builds
This is the thread for CM10.1 stable releases. There are other official CyanogenMod builds for Nook Color available:
CM11 nightly builds -- these experimental builds, based on Android 4.4, contain the latest changes to CyanogenMod and to hardware support for the Nook Color. As the name suggests, new builds are made and posted (roughly) every day; these builds are fully automatic, with no testing done before posting.
CM10.2 stable releases -- while the state of the Nook Color-specific hardware support should be nearly identical to that of CM10.1, you may find this Android 4.3-based release more (or less!) stable than this Android 4.2-based one.
Archived nightly builds for CM10.2, CM10.1, and CM10. You may find the last CM10 nightly (20130421) faster than the later releases, particularly during playback of HD 720p video.
Please check that your questions are in the appropriate thread. (If you're interested, there's lots of past discussion in those threads, as well as the development thread.)
Frequently Asked Questions and Troubleshooting
The soft keyboard keeps crashing!
The Play Store is acting up!
Did you flash the correct Google Apps?
What happened to the "Developer options" and "Performance" screens in Settings?
They're hidden by default now in CM10.1 and later. To show them, go into "About tablet" and tap the build number (for CM10.1 stable releases, JDQ39) seven times.
How do I get the Honeycomb/ICS tablet UI?
You want to use the Auto-Patcher to modify your ROM for the tablet UI. (Don't forget to thank Caldair for maintaining the Tablet UI mod, and mateorod and the rest of the Auto-Patcher developers for building that tool.)
I'm having a problem with my Nook Color running CM10.1.
That's not a question
Okay, I'm having a problem with my Nook Color running CM10.1 -- is there something I can do to troubleshoot?
Glad you asked! Please check the following:
Does the problem occur with a clean install of CM10.1? This means wiping /data and not restoring a Nandroid backup afterwards. Don't restore system apps and/or their data in Titanium Backup either (user apps/data are okay).
Are you overclocking? If so, does the problem occur when you set the maximum clock speed to 1000 MHz or below? To be clear, we are not interested at this point in bug reports of any kind that happen if you have the maximum CPU speed set above 1000 MHz. If you're experiencing system crashes or "sleep of death" (SOD), you may also wish to try capping the CPU clock speed to 800 MHz (but if this helps, please report your problem here and fill out the hardware survey).
Do you have any patches, custom kernels, or other tweaks applied? If you do, does the problem occur without those applied? (We're not necessarily going to ignore bug reports from patched or tweaked systems outright, but it can make our job harder, and we do need to know what changes you have applied to judge whether or not the change might be relevant to your problem.)
I'm having no luck with the suggestions above. What information should I include with my bug report?
When reporting a problem, please include the following information if at all possible:
Full description of the problem -- "it crashes" doesn't count. How do you trigger the problem (or does it occur by itself)? What exactly happens when the problem occurs? How often does it happen?
For problems with apps or specific pieces of the system software: we'll almost certainly ask for a logcat of the event, so you'll save everyone some time by including it.
For problems involving system freezes, crashes, or SOD: if you can connect to the tablet via adb while it's "unresponsive", please provide dmesg and logcat output from that time. If you cannot, try power-cycling it while it's still plugged into USB, and provide dmesg output from immediately after the reboot, plus the contents of /proc/last_kmsg if that file exists (let us know if it doesn't).
For unexpected reboots: provide the contents of /proc/last_kmsg from after the reboot.
Edit: Used these instructions for installing 10.1 on a SDCard.
http://forum.xda-developers.com/showthread.php?t=1941858
Great thanks!
Sent from my NookColor using Tapatalk 4 Beta
Congrats and thanks again Steven and the other NookieDevs, this is running very well, at least on my NC, somehow seems a little more responsive/smoother (especially when background apps/downloads are running - new WiFi tweak?) than the recent nightlies/RC's. Great job, but, there is a new nightly calling, or I've sort of been wanting to try Mateorod's AOSP, besides, my schedule is beginning to settle back down enough that I will probably try to increase my "Android Ninja" experience, so I probably won't be stable long. Keep up the great work, glad to hear that you will still be tweaking it.
Question, are your latest WiFi and/or Graphics tweaks merged yet?
NC crashing hard with clean CM10.1 install
Hi,
great to see CM10.1 on NC. I have just made a clean install on my Nook and generally impressed. Unfortunately my Nook started crashing hard, something that I never experienced before It seems to be correlated with Gallery application, I can reproduce crash only after I open Gallery and then return to home page. Here is what happens:
open Gallery, look at one or few pictures
go back to Home
wait a bit, one minute or so, maybe go to other app or settings
screen goes blank, navigation buttons and status bar are still visible but display area gets dark
no response to touch or nook button
after ~30 seconds Nook reboots
I managed to catch dmesg output right before reboot, attaching it here, there are two files in archive, first is dmesg output before I run gallery, second is dmesg right before it reboots. Logcat and /proc/last_kmsg are also in the archive. I could get more info if anybody wants to look at it and can tell me how to get it.
I ran CM7.2 on the same device for quite some time and had no troubles with that. CM10.1 install is from final, wiped both data and cache, no google apps installed yet, no other apps restored, virgin clean :angel: No overclocking, and no other settings changed, no patches.
Thanks,
Andy
andy1001 said:
Hi,
great to see CM10.1 on NC. I have just made a clean install on my Nook and generally impressed. Unfortunately my Nook started crashing hard, something that I never experienced before It seems to be correlated with Gallery application, I can reproduce crash only after I open Gallery and then return to home page. Here is what happens:
open Gallery, look at one of few pictures
go back to Home
wait a bit, one minute or so, maybe go to other app or settings
screen goes blank, navigation buttons and status bar are still visible but display area gets dark
no response to touch or nook button
after ~30 seconds Nook reboots
I managed to catch dmesg output right before reboot, attaching it here, there are two files in archive, first is dmesg output before I run gallery, second is dmesg right before it reboots. Logcat and /proc/last_kmsg are also in the archive. I could get more info if anybody wants to look at it and can tell me how to get it.
I ran CM7.2 on the same device for quite some time and had no troubles with that. CM10.1 install is from final, wiped both data and cache, no google apps installed yet, no other apps restored, virgin clean :angel: No overclocking, and no other settings changed, no patches.
Thanks,
Andy
Click to expand...
Click to collapse
I can confirm this - I have been experiencing this for a long time now but since nobody else mentioned it I thought it could be just me (although I was doing clean installs). So this problem really exists.
I cannot reproduce this, but I flash the Picassa compatible gallery app - gapps-jb-picasa-20121011-signed.zip - after GAPPS
andy1001 said:
I managed to catch dmesg output right before reboot, attaching it here, there are two files in archive, first is dmesg output before I run gallery, second is dmesg right before it reboots. Logcat and /proc/last_kmsg are also in the archive. I could get more info if anybody wants to look at it and can tell me how to get it.
Click to expand...
Click to collapse
Mmm, that's pretty spectacular -- the system basically runs out of memory and the kernel goes nuts killing things to try to keep the system alive. It looks like the 720p video codec is eating the memory, and I believe we tracked that one down to the same root cause as the Flash issues. Can you try a CM10.1 nightly from June 25 or later (EDIT: or flash the patch in the next post on top of your existing CM10.1 install) and see if the problem still happens? (That reminds me, I promised to respin the binary patch for CM10.1 stable ... I should really do that when I get a minute.)
Patch for 720p codec issues (Flash, video thumbnailing)
As promised, here's the patch fixing Flash, video thumbnailing in the Gallery app, and potentially other 720p video codec issues for the CM10.1 stable release series. (The previous one I posted works as well, but is missing a couple of other potentially useful bugfixes in libstagefright.)
Usage: flash the attached ZIP file over your CM10.1 build from recovery. CM10 users: do not flash this -- use the patch in this post instead. Note that if you're on the CM10.1 nightlies, this patch was merged and should be included in builds starting from June 25.
(Source code: https://github.com/CyanogenMod/android_frameworks_av/tree/cm-10.1.0/media/libstagefright with https://github.com/CyanogenMod/android_frameworks_av/commit/c58721cbdcbfc46f550954a1c258d9b0529e4d81 applied on top.)
steven676 said:
As promised, here's the patch fixing Flash, video thumbnailing in the Gallery app, and potentially other 720p video codec for the CM10.1.0 stable release. (The previous one I posted works as well, but is missing a couple of other potentially useful bugfixes in libstagefright.)
Usage: flash the attached ZIP file over your CM10.1 build from recovery. CM10 users: do not flash this -- use the patch in this post instead. Note that if you're on the CM10.1 nightlies, this patch was merged and should be included in builds starting from June 25.
(Source code: https://github.com/CyanogenMod/android_frameworks_av/tree/cm-10.1.0/media/libstagefright with https://github.com/CyanogenMod/android_frameworks_av/commit/c58721cbdcbfc46f550954a1c258d9b0529e4d81 applied on top.)
Click to expand...
Click to collapse
It is really a damn shame we got that merged just after 10.1 Final was sent to the servers.
steven676 said:
Mmm, that's pretty spectacular -- the system basically runs out of memory and the kernel goes nuts killing things to try to keep the system alive. It looks like the 720p video codec is eating the memory, and I believe we tracked that one down to the same root cause as the Flash issues. Can you try a CM10.1 nightly from June 25 or later (EDIT: or flash the patch in the next post on top of your existing CM10.1 install) and see if the problem still happens? (That reminds me, I promised to respin the binary patch for CM10.1 stable ... I should really do that when I get a minute.)
Click to expand...
Click to collapse
I have tested both cm-10.1-20130627-NIGHTLY-encore.zip and final CM10.1 with your patch libstagefright-omxcodec-patch-for-cm-10.1.0-encore.zip, they both seems to be working OK, I could not make them crash in the same way as unpatched CM10.1 does :victory: Thanks a lot for the fix, much obliged!
Andy
Still having issues with the nook color.
Check the dmesg file for Cm10.1 stable.
Thanks for the patches <steven> Seems to help.
My stable is still holding up good on my NC.
mhzrus said:
Still having issues with the nook color.
Check the dmesg file for Cm10.1 stable.
Click to expand...
Click to collapse
This is what I encounter with Nook Color CM 10.1.2 stable version.
CMUpdater cannot download new Nightly!!!
Battery went flat no indicator.
Wifi issues, network error! For Nothing!
Touch Screen still having issues. The left hand side and right hand side of the screen cannot response to any touches! (About 2 inches thick!)
I come to know that there is issues with Nook Color Touch screen.
http://forum.xda-developers.com/showthread.php?t=1385896
CM10.1.2
A quick heads-up: CM10.1.2 was released last week (check the links in the first post), including important security fixes. (The Flash fix didn't go in and looks unlikely to go into the 10.1 stable series at this point -- you'll have to continue flashing the patch above for now.)
cm-10.1.2-encore stable vs nightly - Patch for 720p codec issues?
steven676 said:
A quick heads-up: CM10.1.2 was released last week (check the links in the first post), including important security fixes. (The Flash fix didn't go in and looks unlikely to go into the 10.1 stable series at this point -- you'll have to continue flashing the patch above for now.)
Click to expand...
Click to collapse
Thanks for that info steven676; so that patch will work for cm-10.1.2-encore stable?
What's the easiest way to tell if the patch is or isn't working on my NC?
Lastly, is it necessary or included with any of latests cm-10.1.2-encore nightlies?
:good:
eltrkbrd said:
Thanks for that info steven676; so that patch will work for cm-10.1.2-encore stable?
Click to expand...
Click to collapse
Yes, it'll work for CM 10.1.2 stable (or any other CM10.1 release).
eltrkbrd said:
What's the easiest way to tell if the patch is or isn't working on my NC?
Click to expand...
Click to collapse
Install Flash, enable plugins in the browser, then open Flash Player Settings -- if the bug is still present, the page will lock up and you'll eventually be prompted to kill the tab.
eltrkbrd said:
Lastly, is it necessary or included with any of latests cm-10.1.2-encore nightlies?
Click to expand...
Click to collapse
As noted in the post with the patch, the fix should be included in CM10.1 nightlies starting with the June 25 build.
THIS BUILD IS ONLY FOR PEOPLE WHO WAN'T TO POINT OUT BUGS AND OTHER ISSUES THAT I HAVE NOT MENTIONED PLEASE DON'T COMMENT AND SAY ZOMG WHY DOESN'T CALL WORK OR STUPID CRAP LIKE THAT! AGAIN TESTING ONLY!!
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
IMPORTANT INFORMATION
We'll not support users and answer questions from users which:
- are running a custom kernel
- have flashed mods
- modified system files
- didn't follow our intructions word by word
- are unfriendly
Even if you tell us that your problem is not related to your custom kernel /mod / magic => WE DON'T CARE!
Your mod => your problem!
CHECK KNOWN ISSUES IN SECOND POST
Official CyanogenMod Wiki: http://wiki.cyanogenmod.org/
First time installing CyanogenMod 10.2 to your ONE X+, or coming from another ROM:
- Read known issues ans FAQs
- Make sure you're running a proper working ClockworkMod-Recovery
- Copy GApps and CM10.2 ZIPs to your SDCard
- Boot into HBOOT (hold Volume Down at boot)
- Flash the boot.img
- Fastboot flash boot boot.img
- Reboot into recovery via the bootloader menu
- Flash CM10.2 zip from SDCard
- Flash GApps zip from SDCard
- DO A DATA WIPE / FACTORY RESET (otherwise your device will be stuck at boot)
- Reboot
- Don't restore system data using Titanium Backup!
- Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
DOWNLOAD:
Google Apps:
http://goo.im/gapps
ClockworkMod Recovery:
http://forum.xda-developers.com/showthread.php?t=2074396
If you're going to reuse our work, which we're doing for free, be fair and give proper credits.
This is the only payment we're really demanding and we deserve it to be mentioned because of the countless hours we've put into this project.
Open-Source doesn't mean Out-of-Respect!!!
XDA:DevDB Information
[ROM] CM10.2 AT&T/TELUS , ROM for the HTC One X+
Contributors
Lloir, h8rift
Source Code: https://github.com/evitareul
ROM OS Version: 4.3.x Jellybean
ROM Kernel: Linux 3.1.x
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2013-11-28
Last Updated 2014-11-19
List of stuff that IS working currently (not released and no eta)
Display
Audio
MTP
Camera
Microphone
GPS Borked
Ril\GSM
WIFI Now borked
Bluetooth
NFC
Reserved
CHANGELOG
Code:
18/2/14
Fixed call audio, all it was, was a super hard to find error which said which permission it was
Fixed Data\gsm
28/11/13
inital testing release
In call is 100% buggered
GPS is trashed
Camera works (if gps is turned off)
Most recent CM source
PLEASE enable the Xda 2013 theme to view this thread correctly, as it is a DEVDB thread.
which enables you to see the downloads section
Q&A
Bug reports
Reviews
Screenshots
ALL questions > Q&A and NOT into this thread
Bug reports > Bug reports tab, with a logcat
Once all the kinks are sorted, this will be pushed to OFFICIAL CM.
If we stumble onto an issue, you want us to send the report?
Update: Been using it for a little under 3 hours, with a mix of Wi-Fi and can confirm that Data works in San Antonio Texas, it's been amazing. After everything settled in and downloaded all my apps, I installed TricksterMod to use the Interactive Governor, it runs very smooth. In addition, will confirm that both SMS & MMS Text messaging works, and Wi-Fi Tethering works. Thank you SO Much LLoir and everyone who is working on this. It really is amazing. I can't say that enough. Okay, just got done trying my Bluetooth headset, audio on games works as for music as well, but alas sadly not for calls, however, I am going to try a wired headset to see if that works.
sledgeharvy said:
If we stumble onto an issue, you want us to send the report?
Update: Been using it for a little under 3 hours, with a mix of Wi-Fi and can confirm that Data works in San Antonio Texas, it's been amazing. After everything settled in and downloaded all my apps, I installed TricksterMod to use the Interactive Governor, it runs very smooth. In addition, will confirm that both SMS & MMS Text messaging works, and Wi-Fi Tethering works. Thank you SO Much LLoir and everyone who is working on this. It really is amazing. I can't say that enough. Okay, just got done trying my Bluetooth headset, audio on games works as for music as well, but alas sadly not for calls, however, I am going to try a wired headset to see if that works.
Click to expand...
Click to collapse
yes please ALL bugs, please make sure you have the xda 2013 theme on (bottom left corner on the site) so you can see the bug report tab. Also you will be able to see the Q&A section CM10.2 ATT thread, where you can ask questions
all questions should go to that section please
thanks
Data/WiFi working great (no lte here so can't test), messaging too, and whole ROM seems to be running very smoothly. Almost faster than stock I'd say and the phone seems to run at about the same temperature - though not as hot as usual when using a lot of data. Didn't encounter any unmentioned bugs and not had any crashes in my day of use, seems pretty stable. Nice job Lloir, honestly the only thing keeping me from using this is the call/audio issue. You've got an awesome start here, thanks for all the hard work!
guys please use the Q&A section or even the review tab (you need the XDA 2013 theme on)
thanks
Any update on the status? I'm itchy to try this out but would really like phone audio before I do.
loftwyr said:
Any update on the status? I'm itchy to try this out but would really like phone audio before I do.
Click to expand...
Click to collapse
Updates will be posted by the OP. FYI, that's a no no question too. Rest assured lloir is working on it unless otherwise stated by lloir.
Sent from my HTC One X+ using XDA Premium HD app
I'm currently running new builds, based on the AT&T X+ 4.2.2 leak
right now i'm updating lib's
Lloir said:
I'm currently running new builds, based on the AT&T X+ 4.2.2 leak
right now i'm updating lib's
Click to expand...
Click to collapse
is there a link to the leak??
TheJokah said:
is there a link to the leak??
Click to expand...
Click to collapse
if you can get access to my pc? sure, but i'm not going to be the target of a HTC c&d notice
short answer no.
Keep us updated. So excited!
later today, i will upload a build purely to see if people pre-4.2.2 can still flash + boot the rom with the old hboot...as i cannot use previous builds with the new 4.2.2 hboot
so yea....in a few hours check the downloads tab for a new download
Lloir said:
later today, i will upload a build purely to see if people pre-4.2.2 can still flash + boot the rom with the old hboot...as i cannot use previous builds with the new 4.2.2 hboot
so yea....in a few hours check the downloads tab for a new download
Click to expand...
Click to collapse
Still running Solomon's PA 4.2.2 build from Feb 19th. I'll assume I'm using the old hboot, then, so I'll try the build when it's posted!
Having a few issues with ril (data/gsm) at the moment, along with WIFI
the plus side looks like GPS is fixed, but can't confirm it 100%
more soon
don't go quoting this damned post here, but post in Q&A
Working as of now:
Camera
Video Camera
GPS (not sure if 100% yet)
GSM
Audio
Lights
Touch Screen
BT
MTP
Borked :
Not tested in call audio yet
WIFI (50% borked)
DATA (Kind of, doesn't connect to the interwebs)
SELinux (will be the last thing i fix)
Dialer app (phone.apk)
Thread Cleaned and Members please report vice posting against others, and I will ask any & all to watch their language, regarding profanity.
Thank You.
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