Related
Hello World!
I just got this phone on monday from the OG Epic on my Dresser to The...
Moving Right Along. Follow at your own risk I am not responsible for your lover joining the military and having raunchy sex tapes of everynight in bootcamp ran on the internet for weeks labeled and tagged with their phone number in description or destroying your phone trying to dial it so BEWARE of Dragons And Crackheads on Angel Dust that may say otherwise!
the wiki
I wanted A One Stop Shop Kinda Thread for us who Love CM9 and since as of 10:50 am on the 23rd this is still at alpha3_1 and links to it can be found here:
Alpha 3.1
http://tinyw.in/8z1l
and the Gapps here:
http://tinyw.in/eMf7
ICS Gapps here:
http://tinyw.in/871H
Dev Thread which is currently closed is here:
http://forum.xda-developers.com/showpost.php?p=22057365&postcount=1
How to Install?
thats the Question my Experience had to answer because i couldn't find a thread with Detailed Info on this. I will Use my Method as The Just-Another-Work-A-Round Method. Any Better Suggestions will lead to Me Updating this Post! Okay Shall we Begin?
you'll need:
Epic Touch 4G SGSII
CM9 Alpha 3.1 zip
Gapps [choose either one from above]
CM7 here: click/tap me
Mobile Odin Pro [linked in Part 2]
Patience & Strippers
Part One is assuming you are on fb17 with kernel and fb21 modem already installed...
If not, Please proceed to Part Two after Part One. Otherwise hopefully you are set!
PART ONE
Lets get Started:
1. BACK UP EVERYTHING!!!!! Nandroid is Your Friend! Do that!
2. Wipe Everything except battery stats!!
3. Flash CM7
4. Reboot fully then from OS reboot back to recovery
5. flash CM9 & then Gapps
*5b. wipe cache and/or wipe data factory reset
**5c. advanced restore data from latest backup
6. reboot the device and wait
7. You Should Now Be On CM9
* wiping data has been said to allow GPS to Work
**have yet to recieve any fc's but if you lose your recovery after flashing cm9 this step will have gotten you your data before hand
Now Lets Talk...
PART TWO
Youve already got yourself on Cm9 But Have no FB17 Kernel Or FB21 Modem:
youll need these items then as well:
Things Needed are:
1. Mobile Odin Pro its paid app so ??? pay up Or Use PC ODIN LINK:CLICK ME
2. FB17 Kernel
3a. FB15 Mobile Odin or Normal Odin
3b. FB21 Modem Mobile Odinor normal Odinor Zip Flash in Recovery
Note: Mobile Odin Link is just the bin file so it needs to be extracted first. if on Pc just extract zip and place bin in root directory of internal sdcard.
Process:
Once all files are On Your SDcard lets begin:
Since You just recently Flashed CM9 and probably have no recovery, i wont say back up but if you can shoot, that'll save time getting you back to cm9 if a fail.
1. Open Mobile Odin:
Scroll to Modem and select it, then internal sdcard, then locate modem.bin and select it. Now back at Odin Menu just
2. Scroll to Open File and select it, locate directory for FB17 kernel should be labled rouge et 1.2.1-rc2.tar and select it, Now back at Odin Menu finally
3. Scroll further down and select Flash Firmware
4. continue
5. continue your device should be rebooting and there you are!
The above is also mentioned by krazyflipj with a simplistic touch in Post 7
Also: Fresh Network has helped others restore LOS if they get it and that can be found here:
PART 3
Can't Get that Darned [extrenal] SDcard to mount?
you'll need:
1. this
its the vold.fstab file from FB17 and its a temp fix. Word is that it will be fixed in the next release and you wont need it after alpha3.1
2. I use root explorer or astro file manager so if you have either one continue, if not read the whole thing first and i will report a free fix other than adb push to the /system/etc folder cause i didnt use that method but it should suffice.
process:
1. unzip the vold.zip and put the contents someplace you can find easy[i chose root of internal sdcard]
2. now within root explorer i long pressed and selected copy from context menu,
scrolled up to the [ ... ] until you get back to root device dir., now select system then etc. once in etc folder make sure your folder is set to r/w not r/o and paste. once complete, reboot and your directory for external sdcard is located /sdcard/external sdcard/
Note: there are some error pop ups after this that say media or android ??? idk
i always choose wait and i havent had any real notable issues.
POST #3 has
Bug Lists{known}
Change Log
Post #4
Tips & Tricks
this is just a beginning of tips & tricks: I look forward to any and all sound advice and comments. Please Share as this is a collective thread I will Update OP as needed. I mixed very little of my own stuff. if links die, just let me knowW! Credit Goes to The CM9 Experts Devs which I know not all the names of yet except: sbrissen for the Epic Touch 4G buy him beers here his info here
Please Correct with Tested and Proven Methods if I am Incorrect but I am On Cm9 with mere seconds of LOS when waking from sleep while On Charge. Running Cm9 and FB17 Kernel as well as FB21 Modem and have access to my sdcard s0oo ???
Thanks! and fyi there should be an update coming very soon!
Lol at first part
Change Log & Bug Lists
The Change Log for Alpha 3.1:
ALPHA 3.1[2/18] http://tinyw.in/8z1l
-Fix 4G reboot
ALPHA 3 [2/18]: http://tinyw.in/WJy5
--YOU WILL LOSE CWM WITH THIS
-- FLASH GAPPS RIGHT AFTER THE ROM BEFORE A REBOOT
-Fixes BT
-Fixes Camera (preview is jumpy)
-Fixes pixelation
- GPS is better
- Heat issue is better
- if you get LOS leave 4G on
ALPHA 2 [2/16]: http://tinyw.in/ZFKd
--Flash same way as before
--If you get a bootloop, WIPE DATA!
--Still has tendencies to get warm, if it happens grab a logcat and reboot
--Occasionally hangs on reboot
-WIFI fixed
-4G's fixed (Turn on by going to Settings->More... -> 4G settings )
-Heat issue MUCH better
-Notification LED fixed
-MMS sends but doesn't always download
-youtube is broken :-/ but browser and gmail work!
-Screen occasionally gets pixelated
-Signal Bars are not accurate still
-Fixed wireless ADB
ALPHA 1 [2/1]: http://tinyw.in/mcyM
****Bug List for Alpha 3.1****
- usb (phone will charge and you have adb access but it will not mount)
- Signal bars are not accurate
- Youtube = NoTube
- and I'm sure there are others I'm missing
Tips & Tricks Thanks krazyjflip
krazyflipj said:
Few tips Im sure has been mentioned :
- Vol down + power takes screenshots
- tap and hold on a suggested word with 3 dots underneath opens a pop up of more suggested words in stock kb
Sent from my Epic Galaxy S2
Click to expand...
Click to collapse
More shall be added!
justlovejoy said:
assuming you are on fb17 with kernel and fb15 modem already installed...
[/COLOR]
Click to expand...
Click to collapse
This is great! Is it possible to add what those of us without FB17 kernel and FB15 modem should do? So, starting from any rom/kernel/modem... (For example, I'm on Calk's 2.8.1 on EL29 modem and kernel)
This might be too much to ask, but it sure would be nice to have everything in one place (you've got most of everything already which is very impressive!). Thank you!
DaisyPlucksta said:
This is great! Is it possible to add what those of us without FB17 kernel and FB15 modem should do? So, starting from any rom/kernel/modem... (For example, I'm on Calk's 2.8.1 on EL29 modem and kernel)
This might be too much to ask, but it sure would be nice to have everything in one place (you've got most of everything already which is very impressive!). Thank you!
Click to expand...
Click to collapse
thats where part two begins! I will specify clearer!
Part One is assuming you are already there and part two is where you go if not already on fb17/15 mixture and are the steps to get there!
DaisyPlucksta said:
This is great! Is it possible to add what those of us without FB17 kernel and FB15 modem should do? So, starting from any rom/kernel/modem... (For example, I'm on Calk's 2.8.1 on EL29 modem and kernel)
This might be too much to ask, but it sure would be nice to have everything in one place (you've got most of everything already which is very impressive!). Thank you!
Click to expand...
Click to collapse
First, make sure to make a backup then follow steps below (Method has worked for me but YMMV). You will need the following files which most is in the op:
- CM7 rom
- CM9 rom
- Gapps
- Flashable FB15 Modem
- Flashable Rogue Kernel
1) Go into recovery and wipe data
2) Flash FB15 modem (Might take longer than usual)
3) reboot system
4) Boot back into recovery and wipe data
5) flash CM7
6) Reboot system
7) Once phone boots to home screen, reboot back to recovery. You should be in stock cwm (Blue letter)
8) Wipe data (Factory reset)
9) Flash CM9, Gapps, and kernel one after the other.
10) Reboot system and enjoy
Noob question but how do i mount the phone to get this vold.fstab file on internal storage? I never had a problem before and yes I have Kies installed. All I get for storage is MTP and camera and I have debugging enabled. Sorry for such a noob question....
1st off, Great post, great information all in one place.
Having said that sbrissen says there is a release today om CM9. I'm really hoping that release makes this post useless and all the extra steps (beyond step 2) are not needed!
nice job putting all this together!
only 1 thought; in part 1, item 5c, saying you can use advanced restore to restore your data; I never tried that with this rom, and, since most folks will be coming from a non AOSP rom, won't restoring data from a TW rom cause problems with an AOSP rom?
Like I said, I never used advanced restore data, unless I am upgrading or moving from one EL29 rom to another, so I can't say for sure if this would work..
Hopefully, BETA 1 drops soon, and Scott has his new phone by now!
woodsdog said:
1st off, Great post, great information all in one place.
Having said that sbrissen says there is a release today om CM9. I'm really hoping that release makes this post useless and all the extra steps (beyond step 2) are not needed!
Click to expand...
Click to collapse
me too but i never ask for eta unless i am mixing in my own magic!
hence yellow text, ik but agree! I will gladly ask for this thread i spent a while creating to be closed if it proves unnecessary in a heartbeat but until then, I will try my best to roll with the punches and provide all that i can with each release if needed.
I despise confusion when android provides me with Google! lol2daBank
wase4711 said:
nice job putting all this together!
only 1 thought; in part 1, item 5c, saying you can use advanced restore to restore your data; I never tried that with this rom, and, since most folks will be coming from a non AOSP rom, won't restoring data from a TW rom cause problems with an AOSP rom?
Like I said, I never used advanced restore data, unless I am upgrading or moving from one EL29 rom to another, so I can't say for sure if this would work..
Hopefully, BETA 1 drops soon, and Scott has his new phone by now!
Click to expand...
Click to collapse
Thanks!
+ i have used this method when transferring from my epic to my epic touch without problems and I also applied the same method as a rule of thumb on my Vibrant as to most updates in those days were all complete wipes and on random builds but worked. still got my texts, call logs and other things everytime. It is a shot in the dark for most but thats one of my tricks that has yet to fail. I've used restores from 09 that i had restored on my friends tablet to show off android capabilities before so i am pretty confident.
but for proof of concept is:
http://forum.xda-developers.com/showpost.php?p=13973966&postcount=1
has mms download been fixed?
ajaholic said:
has mms download been fixed?
Click to expand...
Click to collapse
Good question, it's not on my phone but have you tried go SMS
Touched by an Epic 4G w/Cm9 & Fueled by the NY Giants 2012
Edit: I can say that mms isnt working in my own theory is because 3g isnt working for me. not in 4g area but i use wifi
wait: phone alert and i sent my mms with go sms but no download on the return. Go sms has some mms settings that can be tweeked to though. I am really hungry and havent ate so i will return with more mms info after a fridge raid!
Is there a trick to mounting this rom on my phone to my computer so that I can put the vold.fstab file on my internal storage? I never had this problem. Like I said I have usb debugging enabled and Kies installed on my computer. Am i missing something? i searched to no avail. I also uninstalled and reinstalled drivers and rebooted phone and computer.
BigJPNut said:
Is there a trick to mounting this rom on my phone to my computer so that I can put the vold.fstab file on my internal storage? I never had this problem. Like I said I have usb debugging enabled and Kies installed on my computer. Am i missing something? i searched to no avail. I also uninstalled and reinstalled drivers and rebooted phone and computer.
Click to expand...
Click to collapse
dang'bro' you did too much!
well adb push has been said to work but i downloaded it via the phone from the link and it went to download folder
Edit: Update: MMS issues arent app related so don't think thats a fix, its somewhere else. where idk still looking! :]
justlovejoy said:
dang'bro' you did too much!
well adb push has been said to work but i downloaded it via the phone from the link and it went to download folder
Edit: Update: MMS issues arent app related so don't think thats a fix its somewhere else. where idk still looking! :]
Click to expand...
Click to collapse
Cool, I started over this time I put the file on internal storage after the flash cm7 part. Thanks for the quick reply. Now lets see how it goes....
How come CM9 doesnt have the option to remove Voicemail notifications like CM7 did? (that was one of the cheap easy methods to remove fake voicemail notification icon bug)
Shoulon said:
How come CM9 doesnt have the option to remove Voicemail notifications like CM7 did? (that was one of the cheap easy methods to remove fake voicemail notification icon bug)
Click to expand...
Click to collapse
Probably hasn't been pushed upstream yet. There are still many features that hasn't been ported to CM9 yet. I'm sure the CM team will get many features implemented soon
Sent from my Epic Galaxy S2
Shoulon said:
How come CM9 doesnt have the option to remove Voicemail notifications like CM7 did? (that was one of the cheap easy methods to remove fake voicemail notification icon bug)
Click to expand...
Click to collapse
That my friend I have no other clue except that from my experience with cm, it just hasn't got that far yet in development. I wasn't here for Cm7 to know the difference but I am giving up on mms issues because I've been looking to no avail and I believe it's a build issue and without my refund I have no new computer to start a new build with. I will now visit the screen density issue for a workaround that prevents breaking the phone. The More I look for fixes the more i feel they are all build related. I feel a update coming soon. If I had access to the git I would be trying different things that I can't try now from a win PC. Hope I'm right.
Touched by an Epic 4G w/Cm9 & Fueled by the NY Giants 2012
Shiny ROM: Android 4.4.4, KTU84P for VZW Galaxy Nexus (Toro)
Skip right to the downloads (if you dare )
Hello there XDA GNex community! I'll admit this is a pretty spontaneous post; I've been building ROMs from the Android Open Source (Project) for awhile now, but I've never "published" any of them. I myself own a Verizon Galaxy Nexus, so I've always built from AOSP to make sure I'm as up to date as possible. Well, that's a little background so let's get going with the overview of the ROM itself:
Overview
This ROM is Android KitKat 4.4.4, build KTU84P. The ROM is built directly from source, that is, the Android source code published by Google available for download to all of us developers. The reason I say the ROM is "OTA-like" is because I make VERY few modifications to it, aside from the things that it takes to get the ROM working. I'll go into detail about those things below, but basically I just want the ROM to make your phone feel stable and shiny and new as if it has just received a new OTA update. That being said, it's clear that the landscape of Nexus devices is changing as new ones are released. Therefore, the other primary goal of this ROM is to keep our Galaxy Nexus as close to the modern Nexus design as possible. This means that I will also add in features that will still be stock, but will also make our phones as close to a current Nexus as possible.
As for how I handle the forum side of things, I'm always open to comments, questions, suggestions, requests, etc. I know that most of those things will often be in the form of criticism, but it's okay, I think I can handle it That being said, I do also have a life and am a college student, so I may not get to come on here ALL the time. I will check back as frequently as possible, and I'm hoping that you guys will help each other out as much as possible! Keep it friendly! So now for the details...
Features
Stock Android 4.4.4, build KTU84P
Source (AOSP) built kernel (boot.img)
Easily rootable (see information below)
G-Apps (GMail, Play Store, etc.) included in build along with Nexus apps
Stock browser replaced with Google Chrome
Shiny restart options - access them by holding down the power button and then long pressing on "Power Off"
All the crazy Google proprietary app stuff has been taken care off
Updated frequently
Everything works!
So what do I mean when I say "Everything works!"?
I'm sure by now you all know that when someone says that, it usually ends up not being true. This ROM is not an exception to that rule, but I can say that I've tested most of the things that would be expected to work in stock Android, such as...
WiFi Tethering (no subscription check)
Bluetooth streaming
Google account sign-in and auto-restore of apps and settings
Google Wallet
Location Services (pretty fast GPS lock in my area also)
Photosphere
Android beam
Photo editing with the new filters
Email
Exchange support
Like I said, the normal stuff (data, voice, hardware acceleration, etc.)
More things that aren't important enough to mention here - check out the changelog for a more comprehensive list
Possible Bugs
It's impossible for me to test for and notice EVERY single possible bug in the operating system, so as of right now I can't say that there are any, although I'm sure you will find some. If you do, report them here!
Other IMPORTANT Information
Root
But wait, nothing in this post said anything about root!!!11!!1!1!!! That's right, my ROM does NOT have root built in! (I don't use any root apps, and it's important to the whole "OTA-like" theme). That being said, the ROM is easily rootable; I made sure of this because I know that many, many of you will use root for many useful purposes. If you want to root the ROM, it's as easy as installing Chainfire's new superuser control app/su with this ZIP file. More detailed information can be found in the "Installation Instructions" section. **NOTE** If you are rooted and upgrading to a new build, you should not have to reflash the rooting flashable ZIP because the ROM will keep root for you.
Updates
Now that the ROM has gotten to this stage, the update policy needs a bit of editing Based on the stats I have access to from the website host and data that I collect myself, it seems like Shiny ROM is currently (as of May 27, 2014) stable for at least 80% of the users who have downloaded it. Based on this, and because the ROM is stock, Nexus-like, it doesn't really make sense to update the ROM as frequently as before. The ROM will still be updated as soon as possible after new versions of Android are released. In between Android versions, I will work on making things 100% stable, although that goal isn't always attainable with older devices and aging hardware support. If we decide to explore other paths for the ROM, you will see many more updates If/when the time comes for me to stop updating Shiny ROM, I will let everyone know in a clear way.
Radios
This ROM will (most likely) work with any toro radios; however, I of course recommend using the most recent, Verizon-approved radios which are the FK01 and FK02 radios. My ZIP installation package for these radios can be downloaded here.
Bootloader
Once again, I'm assuming that this ROM will work with all tuna/toro bootloaders; BUT for optimal experience and performance, use the newest Google-approved bootloader, PRIMEMD04. My ZIP installation package for that bootloader can be downloaded here.
ClockworkMod Recovery
I personally recommend using ClockworkMod Recovery as it has always worked well for me with no quirks. Android 4.2 messed up a few aspects of recoveries because of its multi-user system. ClockworkMod Recovery has been updated to correct some of these issues, and I recommend updating to the most recent version, 6.0.4.3. You can flash either the touch recovery or non-touch recovery image through fastboot OR you can download my flashable recovery update ZIP (touch/non-touch) and flash it in recovery. Check out the installation instructions for more details on this.
Some Other Not-so-important Information
Naming Conventions
All of my ROM ZIP files are automatically generated by my build computer. The file name for all builds up to and including the 11/10/13 build always begins with baldwinguy77_toro_aosp so you know that it's my build for toro. All builds after 11/10/13 begin with the prefix ShinyROM_toro_aosp. That prefix is always followed by the date in mmddyy format (e.g. 112212), a hyphen ("-"), and the time in 24-hour, hhmmss format (e.g. 153945). Finally, all builds end with the "signed" suffix - it just helps me know which packages have finished building and which have not. Hopefully this helps everyone to know which update is newest; I stay away from version numbers because I let Google do all of the version control.
Source
In keeping with the spirit of open-source, all relevant Shiny ROM code can be viewed on Github. I'm not extremely experienced with Github, so bear with me as I learn! Thank you!
File Hosting
I've switched over from using Dev-host to a privately hosted site, graciously and generously given to me by user Goofball. Dev-host is still an amazing service, but it's much more convenient for me to use a privately hosted site, plus I get my own suburl and FTP access! HUGE thanks to Goofball! The private hosting will definitely help me deliver a better experience to you guys as far as downloading goes. You can view all of my uploaded, public files here: http://shinyrom.goofball.org/
Also, if anyone ever wants to mirror for me, please feel free so long as you keep the file name and the file itself intact. As for everyone who downloads from a posted mirror: BE CAREFUL! Always use a virus scanner and be careful with what you are putting on your device!
Installation Instructions (VERY IMPORTANT - Note: You can flash all of these ZIPs in CWM or TWRP*)
*Android 4.4 KitKat builds must be installed using the latest version of your preferred recovery!
ROM
1. Download the latest version of the ROM from the download post. (Also download any other files you will need to install, such as Chainfire's SuperSU Root ZIP, the radios installation ZIP, the bootloader installation ZIP, etc.)
2. Put the file(s) you downloaded in step 1 on your phone's internal storage (sdcard).
3. Turn off your phone.
4. Boot into the bootloader of the phone by holding down both volume buttons and the power button simultaneously until you feel a vibration and see a large arrow that says "Start".
5. Use the volume keys to change the arrow until it says "Recovery," then press the power button to boot into recovery.
6. Because of differences in recovery types, I will make the following steps rather generic.
7. Wipe cache.
8. Wipe dalvik cache.
9. If you want to be 100% sure there are no problems, wipe data. If you are coming from another ROM or Android version, wipe data. If you do not wipe data and something goes wrong, repeat this process but wipe data - this step is not necessary if you are simply upgrading.
10. If you are updating your radios, flash FK01_FK02_Radios-signed.zip
11. If you are updating your bootloader, flash PRIMEMD04-signed.zip
12. Flash the ROM (ShinyROM_toro_aosp...signed.zip)
13. If you are rooting, flash Chainfire's SuperSU ZIP file - this step is not necessary if you were rooted on the previous build and are simply upgrading.
14. Reboot your phone, and enjoy!
**Note: If you are simply upgrading to a new version of the ROM and want to keep root, follow the exact instructions above, and do not format /system. It really is not necessary to format /system at any time (unless specifically noted), as the ROM installer has this function built in.
Mods
1. Download the latest version of the mod(s) you wish to install from the download post.
2. Put the file(s) you downloaded in step 1 on your phone's internal storage (sdcard).
3. Turn off your phone.
4. Boot into the bootloader of the phone by holding down both volume buttons and the power button simultaneously until you feel a vibration and see a large arrow that says "Start".
5. Use the volume keys to change the arrow until it says "Recovery," then press the power button to boot into recovery.
6. Because of differences in recovery types, I will make the following steps rather generic.
7. Wipe cache.
8. Wipe dalvik cache.
9. Install the mod(s) you downloaded in step 1.
10. Fix permissions (not really necessary)
11. Reboot and enjoy!
**Note: You can remove all mods you've installed by dirty flashing the latest version of the ROM.
ClockworkMod Recovery (Fastboot method - must have an unlocked bootloader and fastboot in your path)
1. Download either the CWM touch recovery image or non-touch recovery image to your computer and rename it to "recovery.img".
2. Power off your phone.
3. Boot into the bootloader of the phone by holding down both volume buttons and the power button simultaneously until you feel a vibration and see a large arrow that says "Start".
4. Plug your phone into your computer using the standard USB cable.
5. Open the command prompt/terminal and navigate to the folder where your "recovery.img" is saved.
6. Type "fastboot devices" to make sure your phone is recognized; a serial number should show up on the screen.
7. Type "fastboot flash recovery recovery.img" and wait for the process to complete (should be quick).
8. You're done! Use the volume keys to select "Recovery" and boot into your new recovery!
ClockworkMod Recovery (Flashable ZIP method - easier)
If you are updating your recovery before flashing a ROM, these steps should ALL be completed PRIOR to flashing the ROM.
1. Download either the touch recovery flashable ZIP or the non-touch recovery flashable ZIP.
2. Place the ZIP file downloaded in step 1 on your internal storage/sdcard.
3. Turn off your phone.
4. Boot into the bootloader of the phone by holding down both volume buttons and the power button simultaneously until you feel a vibration and see a large arrow that says "Start".
5. Use the volume keys to change the arrow until it says "Recovery," then press the power button to boot into recovery.
6. Choose "Install update from sdcard"
7. Select "Choose file from sdcard"
8. Find the flashable recovery ZIP file you downloaded and install it
9. Back up to the root menu of recovery
10. Select "advanced"
11. Select "reboot recovery"
12. The phone should boot up into your new recovery!
Credits
As with most ROMs, I only did a small part to get everything together. Also, a note that should be made here is that when I am using someone else's file, I ALWAYS host files on the Shiny ROM server to ensure that I don't put any unnecessary stress on their servers. Any file, however, still belongs to and is accredited to its original creator as listed below:
Willyjay - For providing us with lots of amazing and innovative mods for the ROM!
Inmanster - Another great modder who we are fortunate to have here in the thread. He works in collaboration with Willyjay and his mods for many things, but also does some of his own unique mods!
Chainfire - For their SuperSU app and su binary, as well as the convenient ZIP update package, which was previously used and recommended. Check out their website, http://www.chainfire.eu/
Groupers - My new buddy who helped me out with a GPS issue that popped up in 4.2.
Google - Without their amazing staff and willingness to share the source code of their operating system, I wouldn't have been able to build this ROM! Of course, all of the Google apps are theirs, along with the Play Store and system apps. They really are the true owners of all of this.
Samsung - We all may have some mixed feelings about them, but in the end they gave us the amazing, hackable phone that is the Galaxy Nexus.
XDA - By providing such a great Android community, ROMs like this one are able to easily connect with users and get their work out there
Dev-Host - The file-sharing service with virtually no limits on sharing - kudos to them and their hard work. d-h.st
Koush and the ClockworkMod/ROM Manager Team - They make the best recovery that's been around for longest, and their constant updates allow us to keep making ROMs! Also, Koush's recently released open source Superuser control app is the best available and the one linked to in the thread. Thanks Koush! clockworkmod.com
Kevdliu - Huge thanks to this dev and their amazing quick settings mod!
The CyanogenMod Team - For a working implementation of DSPManager on Android which can be ported to any AOSP-based ROM! Without them and Bigwavedave25, the DSP manager mod would not be available! Be sure to thank them and to check out the CyanogenMod website! Also, for their feature-filled version of the stock Messaging app which is available as a mod for my ROM!
bouchigo - a user who has helped to make the CM10 Messaging app available as a mod for my ROM in conjunction with Willyjay for bringing it to my attention.
Schoat333 - A user who helped out Willyjay with the bubble styled MMS mods. The credit for the screenshots to go along with the mods goes to him!
Yarly - The most experienced admin I've ever had the pleasure of talking with, who taught me some new debugging tricks and answered some of my questions.
Razorloves - Another admin who helped me out with a few problems and answered a lot of my questions!
Tiny4579 - A kernel dev who also took the time to talk with me and answer a few of my questions.
Thanks to everyone for their hard work and sharing that work with others!
DISCLAIMER
Come on guys, it's a Galaxy Nexus, to what extent could it really get messed up? Nonetheless, in case someone flashes this then puts their phone in the microwave or something and tries to blame it on me, I am not directly responsible for anything that occurs, either negative or positive, from flashing this ROM to your phone. Despite that, I am posting in the spirit of the Android community, a community that I have embraced and belonged to for several years, and I would never try to hurt any of your innocent, beautiful phones. Also, none of the original source for Android belongs to me, nor do any of Google's apps. All preinstalled applications are property of Google, Inc. and I make no claim of ownership to them.
Okay that's about it! THE ROM DOWNLOAD LINK AND A SUMMARY OF ALL FILE DOWNLOADS CAN BE FOUND BELOW!
ROM Download & Changelog
ShinyROM_toro_aosp_080914-125720-signed.zip
MD5: 5844c6e48fb30bbafc976199c5c1effd
Fixes/Changes Included So Far
(older changes)
6/21/14 CHANGES
Updated to Android 4.4.4, KTU84P
8/9/14 CHANGES
Added system-side support for native screen casting
Added Italian translations for the Shiny restart menu (courtesy of XDA user lparcshinoda)
Switched to prebuilt version of CellBroadcastReceiver in an attempt to fix issues with it on toro
Mods
Before installing any of the packages below, please be sure to check out the mod installation instructions in the OP!
Key
To make mod installation more convenient, all mod links will now be color-coded based on the files they change. The key shows what each color corresponds with:
Red - SystemUI.apk
Blue - framework-res.apk
Purple - SystemUI.apk & framework-res.apk
Green - Other
If you install mods that are in the same color group, it is likely that they will overwrite each other. It is OK to overwrite a previously installed mod, but please note that the originally installed mod will no longer be there. If you want to completely revert to stock, flash the "Back to Stock ZIP" mod under the baldwinguy77 mod section. This mod replaces your SystemUI.apk and framework-res.apk files with ones from the stock ROM.
Developer-specific Mods
All of these mods have been provided by some really awesome mod developers who take the time to continue to make updated mods for my newest ROM builds. That being said, they have lives and can't always get the mods out right away, so make sure the date next to their name matches the build you're running! They usually are around the thread and are open to doing custom mods if you ask Be sure to thank them and check out the credits section for more info!
Baldwinguy77 (Updated for 8/9/14 build)
Back to Stock ZIP - Returns you to the stock version of the ROM by removing SystemUI and framework-res mods.
Stock kernel flashable ZIP - Overwrites any custom kernel you have installed with the stock kernel normally packaged with the ROM.
Inmanster (Updated for 3/9/14 build)
36 DPI Nav. Bar - Replaces the stock navigation bar with a smaller (height-wise), 36 DPI version.
Black Dash-style Softkeys - Replaces the stock navigation bar buttons with black, dash-style ones.
Blue Stock Softkeys - Replaces the stock navigation bar buttons with blue-colored ones.
Carrier Text Replacement - Replaces the carrier text on the lockscreen and pulldown notification shade with "Galaxy Nexus".
Extended Battery Framework Mods - Improve accuracy of battery level reporting for those using extended batteries.
2100 mAh (with Carrier Text Replacement mod)
3050 mAh
3800 mAh
5900 mAh (with No CRT-off Animation mod)
Grey Battery Percentage - Enables display of the current battery percentage in the status bar with grey-colored font.
InmanMod - A combination of the 2100 mAh battery, no CRT-off animation, carrier text, 36 DPI nav. bar, and white zenyth softkeys mods.
No CRT-off Animation - Removes the stock, default CRT-like screen off animation.
White Zenyth-style Softkeys - Replaces the stock navigation bar buttons with white, zenyth-style ones.
Universal Mods & Downloads
These mods have been compiled by myself, sometimes in conjunction with the modders above, to always work with any version of the ROM (but not necessarily any device). Therefore, you don't have to worry so much about these being up-to-date because they should always work. If that is ever not the case, simply PM me and we'll get it fixed This section also includes some other Verizon Galaxy Nexus related downloads such as the latest radios and bootloader. You can use these according to the installation instructions in the OP.
Universal Mods
AOSP Web Browser (for Android 4.4) - Installs the AOSP web browser with Chrome bookmark syncing for Android 4.4.
DSP Manager(for Android 4.4) -Installs the DSP Manager app along with the audio libs and configs important to running the service, allowing you to customize the audio equalizer of your device. At the moment, certain apps on Android 4.4 do not work with the modular DSP service.
ClockworkMod Images
Touch 6.0.4.3
Non-touch 6.0.4.3
ClockworkMod Recovery Flashable ZIPs
Touch 6.0.4.3
Non-touch 6.0.4.3
Chainfire's SuperSU Root Control App and ROOT Flashable ZIP (Works with 4.3 & 4.4)
Download (Latest version, v2.02)
Toro Radios[/size]
FK01 & FK02 Radios Flashable ZIP (Latest)
FF02 & FG02 Radios Flashable ZIP
Tuna Bootloaders[/size]
PRIMEMD04 Bootloader Flashable ZIP (Latest)
PRIMELC03 Bootloader Flashable ZIP
Thanks for your roms, they have been the daily driver on my wifes GN since you started posted them way back when.
I've been using this ROM for the last couple of builds (including latest 2/9) and since flashing the ROM I'm sometimes unable to receive phone calls when the phone is plugged into a wall charger.
The first flash I wiped everything, though latest was only cache. I'm using the 4.2.2 (JDQ39) LTE FK01/CDMA FK02 Radios.
Any ideas?
kielby said:
I've been using this ROM for the last couple of builds (including latest 2/9) and since flashing the ROM I'm sometimes unable to receive phone calls when the phone is plugged into a wall charger.
The first flash I wiped everything, though latest was only cache. I'm using the 4.2.2 (JDQ39) LTE FK01/CDMA FK02 Radios.
Any ideas?
Click to expand...
Click to collapse
Are you sure it's only when plugged into a wall charger? If that's true, it sounds like a hardware issue, but I think you probably just happened to notice it at that time. You may want to try out the 1/4 build as that one seems to work well for people with mobile data-related problems in the newer builds.
kielby said:
I've been using this ROM for the last couple of builds (including latest 2/9) and since flashing the ROM I'm sometimes unable to receive phone calls when the phone is plugged into a wall charger.
The first flash I wiped everything, though latest was only cache. I'm using the 4.2.2 (JDQ39) LTE FK01/CDMA FK02 Radios.
Any ideas?
Click to expand...
Click to collapse
How did you flash the radios? Also are you using any mods/3rd party kernels? First step in fixing radio issues for me is to restore back to stock - this makes sure good radio files get installed then after allowing to settle for 24 hours I flash back to a custom Rom then checking without installing any mods for a day.
If unsure that radios flashed cleanly or having strange signal issues that make no real sense it is a good idea to try stock install.
hotrodwinston said:
How did you flash the radios? Also are you using any mods/3rd party kernels? First step in fixing radio issues for me is to restore back to stock - this makes sure good radio files get installed then after allowing to settle for 24 hours I flash back to a custom Rom then checking without installing any mods for a day.
If unsure that radios flashed cleanly or having strange signal issues that make no real sense it is a good idea to try stock install.
Click to expand...
Click to collapse
I flashed the zip files from this thread using CWM before flashing the ROM the first time. I'll try going back to stock for a couple of days to see if it fixes the issue.
To the previous poster, I'm pretty sure it's related to charger somehow. My wife started complaining that should couldn't reach me on my cell during the work day (hmm is this a *feature* or a bug?!). I was sitting at my desk during those times with my phone plugged in. I tried calling the Nexus from my desk phone and it wouldn't ring until I unplugged it. It only started after I flashed the new radios and ROM.
Thanks guys.
kielby said:
I flashed the zip files from this thread using CWM before flashing the ROM the first time. I'll try going back to stock for a couple of days to see if it fixes the issue.
To the previous poster, I'm pretty sure it's related to charger somehow. My wife started complaining that should couldn't reach me on my cell during the work day (hmm is this a *feature* or a bug?!). I was sitting at my desk during those times with my phone plugged in. I tried calling the Nexus from my desk phone and it wouldn't ring until I unplugged it. It only started after I flashed the new radios and ROM.
Thanks guys.
Click to expand...
Click to collapse
By the way I reflashed the 4.1.1 (JRO03O) radios from radio thread without changing anything else and the problem seems to have gone away.
What kernel should I use with this ROM to get the best performance/battery life combo. Link please!
Sent from my 2013 Kindle Fire HD
Is an upgrade to KVT in the works?
UPDATE -- I'm running the latest version with the latest franco and Xposed Framework and - wow. Rock stable, fast and melted chocolate smooth (boom - trademarked.) I don't know why I haven't done this sooner. This is all I need for awhile. Truly happy with my GNex at this moment haha.
RoxRedEye said:
Is an upgrade to KVT in the works?
UPDATE -- I'm running the latest version with the latest franco and Xposed Framework and - wow. Rock stable, fast and melted chocolate smooth (boom - trademarked.) I don't know why I haven't done this sooner. This is all I need for awhile. Truly happy with my GNex at this moment haha.
Click to expand...
Click to collapse
Hey there! I'm sorry, somehow I missed your post earlier! Anyways, glad to hear you're liking the ROM so much There is an updated build available as of today so check the download post. More info is coming in a few seconds
3/9/14 Build Information
Hey there everyone! It seems like it's been awhile since the last time I got make one of these new build posts, and I have to say it feels good to be able to do it again! I first have to apologize for my absence both in terms of development and communication in the thread. I'm getting close to the end of my sophomore year in college, and let's just say it has been keeping me extremely busy. I don't mind it, but I just wish it still left more time for me to do Android-related things! Luckily, I had a whole week off to catch up on a lot of things, including Shiny ROM development. So with that, we have a new build ready to go that includes a very minor update to the AOSP base of the ROM as well as some not so minor updates to the telephony stack. What this means is that mobile data and voice performance/reliability may have some big improvements in this build. We didn't get a chance to do a wide-scale test with these changes, and they're only in the master branch of AOSP, but after reviewing the code I'm hopeful that they'll bring improvements for us. That being said, be sure to leave your feedback here on the thread so we know how it's working! If you experience any problems, try to grab a logcat and let us know about them so we can try to get everything straightened out! So after reviewing the other information and installation instructions below, head over to the download post to grab the new build!
I also want to take this opportunity to point out that Shiny ROM has a new website! For now, the URL/domain is still http://shinyrom.goofball.org/ to stay consistent. The website has a lot of information about Shiny ROM as well as some future plans. It also lists details for the newest build of Shiny ROM along with download links, etc. I'm hoping that this website serves as a good platform for Shiny ROM to grow as we can now deliver a lot of information without having to worry about it getting buried in the forum and whatnot. So check that site frequently for Shiny ROM news and updates as well as information about new builds! There is also a contact form there for everyone to leave their suggestions, report bugs, etc. I hope you all like it!
(You can still access all of the Shiny ROM files here.)
Thanks to everyone for your continued support of myself and Shiny ROM!
Installation Instructions
Download desired ZIP files (ROM, SuperSU*, mods, etc.) and place on internal storage.
Reboot to the latest version of your preferred custom recovery (CWM or TWRP).
Wipe cache.
Wipe dalvik cache.
**OPTIONAL** Wipe data/factory reset (will erase user data like apps and saved games, etc., but may fix strange bugs).
Flash ROM.
**OPTIONAL** Flash other desired ZIPs (SuperSU, mods, etc.).
Reboot.
Enjoy!
*As of 3/9/14, the latest version of SuperSU is v1.93.
baldwinguy77 said:
Hey there! I'm sorry, somehow I missed your post earlier! Anyways, glad to hear you're liking the ROM so much There is an updated build available as of today so check the download post. More info is coming in a few seconds
Click to expand...
Click to collapse
No worries. Thanks for the reply and thank you for your hard work bringing us a stable stock KitKat. Glad I have extra batteries with me - gonna download and flash asap.
Hey @baldwinguy77, can't access rootz right now, but was systemui.apk updated for today's build? I have a home cooked mod from last version that I'd like to use. Thx
ART isn't sticking when I change from dalvik. I flashed on top of the last build. Did not do a full wipe yet.
Sent from my Galaxy Nexus using Tapatalk
asilentcivilian said:
ART isn't sticking when I change from dalvik. I flashed on top of the last build. Did not do a full wipe yet.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
full wipe did the trick. thanks for keeping this ROM alive!
Sent from my Galaxy Nexus using Tapatalk
klobkelosh said:
Hey @baldwinguy77, can't access rootz right now, but was systemui.apk updated for today's build? I have a home cooked mod from last version that I'd like to use. Thx
Click to expand...
Click to collapse
Hmmmm I would just give it a try, I think it will probably work fine especially if it only modifies SystemUI
asilentcivilian said:
full wipe did the trick. thanks for keeping this ROM alive!
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Glad to hear it! Thanks for your support!
baldwinguy77 said:
Hmmmm I would just give it a try, I think it will probably work fine especially if it only modifies SystemUI
Click to expand...
Click to collapse
Yes it worked fine, thanks for the response. Unfortunately, this build is not very nice to my battery
klobkelosh said:
Yes it worked fine, thanks for the response. Unfortunately, this build is not very nice to my battery
Click to expand...
Click to collapse
Glad to hear it! I would give it some time before making any conclusions; charge it up tonight, grab it in the morning and see how it is with normal use
If you want, you can put the APN refresh delay back to its value from the previous build. To do this, you need to be rooted so that you can edit the build.prop. You simply have to remove this line:
Code:
persist.radio.apn_delay=5000
I don't think it should be making a big difference, but that's the only change that could (in theory) have some effect on battery life. Of course, removing that line may come at the price of having longer/trickier data handoffs. Unfortunately, Verizon's network certainly isn't making it easy for us to give everyone good battery life and good data handoffs
baldwinguy77 said:
Glad to hear it! I would give it some time before making any conclusions; charge it up tonight, grab it in the morning and see how it is with normal use
If you want, you can put the APN refresh delay back to its value from the previous build. To do this, you need to be rooted so that you can edit the build.prop. You simply have to remove this line:
Code:
persist.radio.apn_delay=5000
I don't think it should be making a big difference, but that's the only change that could (in theory) have some effect on battery life. Of course, removing that line may come at the price of having longer/trickier data handoffs. Unfortunately, Verizon's network certainly isn't making it easy for us to give everyone good battery life and good data handoffs
Click to expand...
Click to collapse
I'll take that under consideration, but man it was really killing me. Following new rom flash, for everything set up, charged up to 100 percent. Good. Drive to dinner, 30 mins, in and out of 4g and 3g, battery at 80 percent. After 2 hour dinner on 3g, 60 percent. Back home 40 percent, lots of hand offs. She's nearly dead now and I haven't even used her tonight. I love this ROM, but she's not right...
Q&A for [ROM][UNOFFICIAL] CyanogenMod 11 Nightlies / Releases [M11]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
my desire hd cant boot when i swich to ART mode
Mustaavalkosta said:
General:
These are UNOFFICIAL CM11.0 Kitkat Nightlies / Releases brought to you by AceEnablementProject and TeamCodefire as a continuum to CM10 and 10.1 nightlies. Builds are generated automatically each night. Process starts around 00:30 PDT. If it fails, then there will be no build until the reason for failure is taken care of which can take time. Latest 12 nightlies will be kept on the server. If you want a longer history of them, you are free to archive them yourself.
Thanks and credits:
Andromadus
CodeAuroraForum
CyanogenMod
BananaGranola
Epic Beard Men
eXistZ
Flemmard
Flinny
goo.im
Juansheng
paulb_nl
randomblame
synergye
TeamCodefire (for build server and hosting, priceless)
All the rest that have helped to construct these builds and develop software for ace directly or indirectly in the past.
Githubs:
CyanogenMod
AceEnablementProject
Changelogs:
CM Gerrit
CM Google+
Github (see above)
Installation instructions:
Download Nightlies / Releases [BasketBuild mirror]
Download gapps from here. Pico/Nano/Micro recommended, Mini/Full/Stock doesn't fit in our system partition after the ROM has been installed.
Put the files on SD card.
Reboot to recovery.
Do factory reset (ie. format /data, /cache, /sd-ext and /sdcard/.android_secure)
Flash cm-11-YYYYMMDD-UNOFFICIAL-ace.zip
Flash gapps zip
Remember to reflash boot.img via fastboot if you are HTCDev unlocked.
Reboot and enjoy.
Update instructions:
Download Nightlies / Releases [BasketBuild mirror]
Put the file on SD card.
Reboot to recovery.
Flash cm-11-YYYYMMDD-UNOFFICIAL-ace.zip
Remember to reflash boot.img via fastboot if you are HTCDev unlocked.
No need to flash gapps as CM backuptool script should take care of them. (Results may vary depending on which gapps package you are using.)
Reboot and enjoy.
InspireMod
http://downloads.codefi.re/mustaavalkosta/inspiremod
Kernel
Source: github
Compiler: stock AOSP gcc-4.7
Branch: cm-11.0
Kernel Version: 3.0.101
defconfig: spade_defconfig
Contact:
My Google+
My twitter
#codefireX @ freenode
Donations:
For hosting: codefi.re (use the donation button at the bottom of the page)
I don't really need your money right now but if you insist on donating to me I suggest you donate that money to EFF instead here: https://supporters.eff.org/donate
Q&A:
Q: I tried to flash the ROM and got this:
Code:
Installing update...
set_metadata_recursive: some changes failed
E:Error in /sdcard/..path od ROM.zip
(Status 7)
Installation aborted.
A: Update your recovery to one that is compatible with new recovery functions. See the list below.
4EXT Recovery Touch v1.0.0.6 RC 3 or newer
CWM 6.0.4.8 Advanced Edition / PhilZ Touch 6.29.8 or newer
TWRP 2.7.1.0 ACE or newer
Q: I've used HTC Dev unlock and flashed the rom but it won't boot. What should I do?
A: You need to extract boot.img from the zip and flash it via fastboot. If you don't have fastboot executable anymore from flashing recovery, install Android SDK platform tools (Linux users should find it from distro's package management) and then reboot to bootloader, open command prompt and navigate to the location you extracted your boot.img and type:
Code:
fastboot flash boot boot.img
You need to repeat this everytime you flash new version of this rom to ensure everything will work fluently as long as you have just basic HTC Dev unlock.
Q: Where are my developer and performance options?
A: http://goo.gl/jpS8r
Q: Feature X doesn't work, let's make 1000 posts about it to annoy everyone.
A: Please, dont. Use search and then use search again and only then report your problem with necessary logs. [Logcat guide, thanks to MusikMonk for the link]
Q: I hate you for not fixing this issue X!!!
A: I love you too.
Q: How I can build CM11.0 myself?
A: Setup a basic Android build environment.
Code:
mkdir cm11
cd cm11/
repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
mkdir -p .repo/local_manifests
wget https://github.com/AceEnablementProject/android/raw/cm-11.0/local_manifest.xml -O .repo/local_manifests/cm_ace.xml
repo sync
cd vendor/cm/
./get-prebuilts
cd ../../
. build/envsetup.sh
lunch cm_ace-userdebug
mka bacon
Once the build finishes you'll find your goods from out/target/product/ace/ directory.
Q: Something about something something something.
A: Ask the guy/gal next to you.
XDA:DevDB Information
[UNOFFICIAL] CyanogenMod 11 Nightlies / Releases [M11], ROM for the HTC Desire HD
Contributors
Mustaavalkosta, paulb_nl
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Beta
Current Beta Version: M11
Beta Release Date: 2014-10-08
Created 2014-04-11
Last Updated 2014-10-09
Click to expand...
Click to collapse
some saids it`s because the partition of cache is too small
CM11 latest release freezes after first reboot
GD to all. I am trying to install CM11 latest release, first time starts ok, but after reboot it doesn't start, freezes with black screen before bootanimation. Tried to flash boot.img via ADB & also tried to install CM 10.1 SR3, nothing helped, same situation. Waiting for your replies. Thx in advance.
Hey!
Would it be possible to you to add gpu overclock to that kernel?
Thx
Question about bugfixes
Hi,
at the moment i have M10 installed but i want to ask if there is a fix in M11 included which fixes sudden restarts.
My DHD restarts over night or when i want to something (it doesnt depends on what i am doing).
And another Problem sometimes the screen wont turn on when pressing the power button only the menu keys lighten up.
And i think it is more like off topic but how i can unlock the phone that i do not need to flash boot.img it is at the moment only HTC-Unlocked.
And very much thanks for this ROM it is great!
Thanks in advance for your answers
ag1707
Cannot dirty flash Nightlies
Hi
Since sometime around M11 release, I can not dirty flash nightlies on nightlies. The phone stuck at booting with the message "Android is upgrading / Finishing boot".
I'm using TWRP 2.7.1.0 for recovery.
1. Install Rom
2. Wipe Cache/Dalvik (I've tried without wipe too)
3. Reboot System
Am I missing something here?
I'm using non-English locale. Could it be the reason?
Best Regards,
Solved
Nanashi_anon said:
Hi
Since sometime around M11 release, I can not dirty flash nightlies on nightlies. The phone stuck at booting with the message "Android is upgrading / Finishing boot".
I'm using TWRP 2.7.1.0 for recovery.
1. Install Rom
2. Wipe Cache/Dalvik (I've tried without wipe too)
3. Reboot System
Am I missing something here?
I'm using non-English locale. Could it be the reason?
Best Regards,
Click to expand...
Click to collapse
Just figured it out that PA_GAPPS requires flash every update for recent ROMs.
Hi and thx for your rom!
I flashed the cm-11-20141008-UNOFFICIAL-M11-ace from releases, using twrp 2.7.1.0 for the recovery on a HTC Desire HD.
I am experiencing some lag when opening the screen or starting apps / widgets. It can take be almost instant up to 3-5 sec for the app to launch and be accessible (camera, gallery, weather, settings, mail anything really).
Also once in a while parts of the text in the screen get deformed (example here), any action by me (moving my finger around) or by the OS (some notification) fixes it.
As far as I can tell I followed your instructions properly. Is there anything I could try?
XZelin said:
some saids it`s because the partition of cache is too small
Click to expand...
Click to collapse
Possibly. There are some posts about this from paulb_nl on the main thread but I didn't find them right now. They are there though.
sky141 said:
GD to all. I am trying to install CM11 latest release, first time starts ok, but after reboot it doesn't start, freezes with black screen before bootanimation. Tried to flash boot.img via ADB & also tried to install CM 10.1 SR3, nothing helped, same situation. Waiting for your replies. Thx in advance.
Click to expand...
Click to collapse
Are you using the latest recoveries mentioned in the first post's Q&A section in the development thread? If your issue is what I think it is, full wipe with the previously mentioned recoveries should fix it.
_Bon_Bon said:
Hey!
Would it be possible to you to add gpu overclock to that kernel?
Thx
Click to expand...
Click to collapse
Is there working GPU OC for ace? I thought it was hardware locked thus can't be overclocked via software.
ag1707 said:
Hi,
at the moment i have M10 installed but i want to ask if there is a fix in M11 included which fixes sudden restarts.
My DHD restarts over night or when i want to something (it doesnt depends on what i am doing).
And another Problem sometimes the screen wont turn on when pressing the power button only the menu keys lighten up.
Click to expand...
Click to collapse
I haven't heard any complaints about frequent reboots. I know that there are those but it's been said to happen like once a week or so. M11 may change something if your issues come from corrupted devlog partition but if it's something else, then M11 won't do anything for your reboot issue.
Nihim said:
Hi and thx for your rom!
I flashed the cm-11-20141008-UNOFFICIAL-M11-ace from releases, using twrp 2.7.1.0 for the recovery on a HTC Desire HD.
I am experiencing some lag when opening the screen or starting apps / widgets. It can take be almost instant up to 3-5 sec for the app to launch and be accessible (camera, gallery, weather, settings, mail anything really).
Also once in a while parts of the text in the screen get deformed (example here), any action by me (moving my finger around) or by the OS (some notification) fixes it.
As far as I can tell I followed your instructions properly. Is there anything I could try?
Click to expand...
Click to collapse
It's a bit slow but I suppose that's understandable considering we are talking about 4 year old device. People have reported it gets slower the more apps you install. I'm not sure why.
I'm seeing that kind corruption on the screen graphics for the first time. Any chance of figuring out how to reproduce it and write step-by-step what to do so I could maybe replicate the issue on my end?
Mustaavalkosta said:
It's a bit slow but I suppose that's understandable considering we are talking about 4 year old device. People have reported it gets slower the more apps you install. I'm not sure why.
I'm seeing that kind corruption on the screen graphics for the first time. Any chance of figuring out how to reproduce it and write step-by-step what to do so I could maybe replicate the issue on my end?
Click to expand...
Click to collapse
Yea that is very much true, this might sound bad but would is there some other version you would recommend (even if it's a previous android release) which would be snappier? (your ROM so far is absolutely fine outside of that lag which as you stated is probably because DHDs hardware can't handle it).
As for that graphics glitch can't think of something, any apps were installed from play store (not restored by titanium for example) it happens on different ones but a lot more often on k-9 email client (from which the screenshot is).
If there is something that you would like me to try, feel free to tell me, though any action on the screen restores it to its normal way.
Nihim said:
Yea that is very much true, this might sound bad but would is there some other version you would recommend (even if it's a previous android release) which would be snappier? (your ROM so far is absolutely fine outside of that lag which as you stated is probably because DHDs hardware can't handle it).
As for that graphics glitch can't think of something, any apps were installed from play store (not restored by titanium for example) it happens on different ones but a lot more often on k-9 email client (from which the screenshot is).
If there is something that you would like me to try, feel free to tell me, though any action on the screen restores it to its normal way.
Click to expand...
Click to collapse
I don't mind people looking for better solution for their needs. You may want to try my CM10.1 builds which were noticeably faster if I recall correctly. I haven't been using other ROMs that much during the time I've kept my own stuff going here so I can't really recommend anything else. A fellow user may be a bit less biased to recommend other options.
I'll see if I can catch that graphical glitch with K-9 myself. Thanks for reporting it!
Mustaavalkosta said:
I'm seeing that kind corruption on the screen graphics for the first time. Any chance of figuring out how to reproduce it and write step-by-step what to do so I could maybe replicate the issue on my end?
Click to expand...
Click to collapse
I get that black boxes glitch with the standard Email app all the time. They usually go away in less than a second. I also checked for those when I was testing the 4.4 adreno drivers and it was still not fixed.
paulb_nl said:
I get that black boxes glitch with the standard Email app all the time. They usually go away in less than a second. I also checked for those when I was testing the 4.4 adreno drivers and it was still not fixed.
Click to expand...
Click to collapse
Oh ok. If it has been mentioned in the development thread, I've just probably forgotten about it.
Mustaavalkosta said:
I don't mind people looking for better solution for their needs. You may want to try my CM10.1 builds which were noticeably faster if I recall correctly.
Click to expand...
Click to collapse
Thanks! What would be the proper way to backup the whole "phone" so I can switch back and forth between roms? Atm I 'm only backing up apps & data with titanium.
Nihim said:
Thanks! What would be the proper way to backup the whole "phone" so I can switch back and forth between roms? Atm I 'm only backing up apps & data with titanium.
Click to expand...
Click to collapse
Doing a backup in recovery should be sufficient to backup everything except sdcard.
Mustaavalkosta said:
Are you using the latest recoveries mentioned in the first post's Q&A section in the development thread? If your issue is what I think it is, full wipe with the previously mentioned recoveries should fix it.
Click to expand...
Click to collapse
Thx 4 yours above. I'm using latest 4ext recovery touch + full wipe, of course. Will try to do something with partition.
Update from M11 to Nightly
It is possible to flash the newest nightly over the M11 release?
Or I need a full wipe.
Christian1987 said:
It is possible to flash the newest nightly over the M11 release?
Or I need a full wipe.
Click to expand...
Click to collapse
Well, generally it's recommended to wipe if you switch from one to another but it may work in this case without wiping. Make a nandroid backup and try it.
My battery dies really fast. Do you guys have a recommendation in terms of which battery to get? Link it here. Thanks.
prufessor_oak said:
My battery dies really fast. Do you guys have a recommendation in terms of which battery to get? Link it here. Thanks.
Click to expand...
Click to collapse
You can get original Desire HD battery on ebay cheaply, no point looking at other batteries which cost almost the same. Just look for one in your region.
Install Wakelock Detector from the Play store and find out what is causing your battery drain. Depending on phone use it should be able to last all day, 2 days if just left on standby all the time. Screen on all the time will be around 3-4 hours.
Q&A for [ROM][L900] Cyanogenmod 12.0 [12/14/14]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][L900] Cyanogenmod 12.0 [12/14/14]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
keyboard ?
works Good to what i see but there's no keyboard . Any fix for that ?
Working great no issues with phone, gps or camera. Great job and I look forward to the updates. Seems great so far.
Thanks
I just installed the new build I am only wondering how do I turn off my mobile data. This ROM is amazing and everything works except for data turning off and front camera
Battery Life
When i flashed this rom onto my device, i noticed a significant drop in battery life. Has anyone else noticed this and is there a fix for this?
thnx
Thank you sooooooooooo much man ,,, its sooooooo cooool ROM
working Perfectly on my sprint Note 2 SPH-L900
camera works fine ,,, everything is cool ,,, downloading now gapps
So I'm relatively new to the forums, I mostly just read, learn and try to stay out of way. Just flashed latest nightly last night. So far very smooth and stable. I did some poking a prodding this morning to answer some questions I had coming from CM11 which I was also new to.
Nice to see Sprint carrier billing back in this version. I know I saw it posted that NFC was not working but everything but Tap & Pay seems to work fine for me. Beam and Tags all function okay.
On top of Netflix not working yet, Play Movies 3.6.16 FCs on launch and after reverting to 3.4.23 it waits until you press play to FC.
I did have the keyboard issue that has been mentioned but was prepared with SwiftKey apk on my sdcard just in case. After finishing setup ALL keyboards seem to function just fine.
BT and GPS both working great.
All in all very usable and I'm going to give it a go as a daily for as long as possible though I may have to revert back to CM11 just for the Netflix/Play Movies since we only stream in my household. We'll see.
Not sure if this thread was the best place to share (I can't seem to comment on the main thread) but if there's a more appropriate place to provide feedback that someone wants to point me at, happy to do it.
Nice work everyone who's contributing. Thanks for your efforts keeping my Note 2 relevant.?
GPS
How did you get the GPS working? I tried flashing the GPS fix linked in the thread and a clean install with the latest nightly. I drive around and never obtain a GPS lock.
k3v0 said:
How did you get the GPS working? I tried flashing the GPS fix linked in the thread and a clean install with the latest nightly. I drive around and never obtain a GPS lock.
Click to expand...
Click to collapse
I followed the sequence in this comment on the main thread and it just worked.
http://forum.xda-developers.com/showthread.php?p=58403610
Credit: @kylemccracken
"Edit: Make sure all important data and backups are stored to your external SD card before formatting. I used Philz 6.48.4 and CWM 6.0.5.0 when following this procedure.
[IMPORTANT]
After wiping clean to install a new rom, factory resetting, and wiping cache and dalvik cache, in philz recovery, go to your storage and mounts settings and format every option you can EXCEPT sdcard1. Reboot your recovery then proceed with the steps below.
Make sure you have your ROM, Gapps, SuperSU, and GPS fix zips on your external sdcard1. Flash in the order below.
1. Flash your ROM zip.
2. Perform a factory reset then wipe both cache options. This step is very important when facing problems after flashing.
3. Flash your Gapps zip. Wipe both cache.
4. Flash your SuperSU zip. Wipe both cache.
5. Flash GPSfix zip. Wipe both cache.
6. Reboot.
This process will give you the cleanest possible install with the highest chance of success. When I start having problems with flashing, I format everything (except sdcard1) then follow those steps. It's the same procedure I took when flashing the CM12 nightly and all is running well."
So I've been following the change log for this Rom, and I can't understand much.
I'm still on the 1/5/15 non nightly version and it's pretty much functional as a daily driver. What I'm wondering is are there any major differences for the newer nightlies?
Perhaps in addition to being a Q&A on these nightlies, everyone can post which version they're on, how it is (what's broken/what's been fixed), and what's new if anything.....
Newb question: This is the first time I've started on a ROM at such an early stage of its development. Typically how fast does CM development progress once a new version is started? Idle curiosity mostly.
The Commish said:
Newb question: This is the first time I've started on a ROM at such an early stage of its development. Typically how fast does CM development progress once a new version is started? Idle curiosity mostly.
Click to expand...
Click to collapse
That would be nightly.
Sent from my SM-N910P using XDA Free mobile app
t4d73 said:
That would be nightly.
Sent from my SM-N910P using XDA Free mobile app
Click to expand...
Click to collapse
Haha, thanks. ? I understand the nightly releases. What I meant was I guess is how long after a new version is started does it normally take to get to the first milestone or even snapshot release for instance? Like I said, I'm just curious about the process.
The Commish said:
Haha, thanks. ? I understand the nightly releases. What I meant was I guess is how long after a new version is started does it normally take to get to the first milestone or even snapshot release for instance? Like I said, I'm just curious about the process.
Click to expand...
Click to collapse
Lol. Yeah I wouldn't get your hopes up too high for that. It might happen but I guess we'll see. I don't think any device has gotten a milestone just yet anyway.
Sent from my SM-N910P using XDA Free mobile app
Keeps restarting on cm12 boot screen
Hey guys,
I have a situation I've never come across and wanted to see if someone might be able to point me in the right direction. I have two Samsung Note 2(l900) and running on cm12 as of this morning. I installed the new nightly on both devices the same exact way by opening clockwork recovery and installing zip. One device was successful and is working just fine, the other seemed to flash fine until it had finished loading the apps and going into boot. The device would restart on the note 2 logo screen and then proceed to the cm12 boot screen and then restart after a few seconds. I went back into recovery which took longer than usual, and proceeded to clear partition, wipe dalvik cache, and install older nightlies. I had the same result no matter what nightly I went with.
I decided to set the device back to stock rom and root again. I it worked just fine, so I went through the process about 4 times installing different nightlies but had the same restarting results. It was then I noticed that getting in clockwork recovery manually lagged about 30 seconds. I took the advice of someone on the Google plus forum and switched the recovery from clockwork to twrp. Tried again with the same restarting results and with the manual recovery lagging about 30 seconds to get into.
It seems to work just fine if I flash to stock touchwiz but recovery seems to have issues.
Anyone getting Netflix or Play Movies to work yet on the latest versions? It's the only thing that made me have to revert back to CM11. I tried looking over the change log but honestly I don't know what half that stuff means.?
The Commish said:
I followed the sequence in this comment on the main thread and it just worked.
http://forum.xda-developers.com/showthread.php?p=58403610
Credit: @kylemccracken
"Edit: Make sure all important data and backups are stored to your external SD card before formatting. I used Philz 6.48.4 and CWM 6.0.5.0 when following this procedure.
[IMPORTANT]
After wiping clean to install a new rom, factory resetting, and wiping cache and dalvik cache, in philz recovery, go to your storage and mounts settings and format every option you can EXCEPT sdcard1. Reboot your recovery then proceed with the steps below.
Make sure you have your ROM, Gapps, SuperSU, and GPS fix zips on your external sdcard1. Flash in the order below.
1. Flash your ROM zip.
2. Perform a factory reset then wipe both cache options. This step is very important when facing problems after flashing.
3. Flash your Gapps zip. Wipe both cache.
4. Flash your SuperSU zip. Wipe both cache.
5. Flash GPSfix zip. Wipe both cache.
6. Reboot.
This process will give you the cleanest possible install with the highest chance of success. When I start having problems with flashing, I format everything (except sdcard1) then follow those steps. It's the same procedure I took when flashing the CM12 nightly and all is running well."
Click to expand...
Click to collapse
I've tried several methods and combinations of wiping at every possible opportunity before pressing reboot and i'm still having
issue. All the the apps are listed in the app drawer displaying the file name instead of the app name. Also all of the apps display the same icon (default android) and the not installed toast appears when attempting to launch any of them. Is anyone else having this issue
attempted flashing
cm-12-20150203-NIGHTLY-l900.zip with md5: ba795d6a4261654648b0eb5cec019021 downloaded from http://download.cyanogenmod.org/?device=l900&type=stable
cm-10.1.3-l900.zip with md5: ba795d6a4261654648b0eb5cec019021 downloaded from http://wiki.cyanogenmod.org/w/Gapps
has anyone had success with either of these
currently running Android 5.0 Lollipop ROM for Galaxy Note 2! [CM12] downloaded from http://galaxynote2root.com
attempted with both gapps-lp-20141109-signed.zip and LollipopMicroGapps-121914-HighOnAndroid.zip both downloaded from http://galaxynote2root.com
I would prefer to use the aforementioned build because the build I'm running is not compatible with the nightlies
thanks for any responses in advanced.
KAZETARO said:
I've tried several methods and combinations of wiping at every possible opportunity before pressing reboot and i'm still having
issue. All the the apps are listed in the app drawer displaying the file name instead of the app name. Also all of the apps display the same icon (default android) and the not installed toast appears when attempting to launch any of them. Is anyone else having this issue
attempted flashing
cm-12-20150203-NIGHTLY-l900.zip with md5: ba795d6a4261654648b0eb5cec019021 downloaded from http://download.cyanogenmod.org/?device=l900&type=stable
cm-10.1.3-l900.zip with md5: ba795d6a4261654648b0eb5cec019021 downloaded from http://wiki.cyanogenmod.org/w/Gapps
has anyone had success with either of these
currently running Android 5.0 Lollipop ROM for Galaxy Note 2! [CM12] downloaded from http://galaxynote2root.com
attempted with both gapps-lp-20141109-signed.zip and LollipopMicroGapps-121914-HighOnAndroid.zip both downloaded from http://galaxynote2root.com
I would prefer to use the aforementioned build because the build I'm running is not compatible with the nightlies
thanks for any responses in advanced.
Click to expand...
Click to collapse
Sorry, I'm probably not the most knowledgeable. If it wasn't for these forums I wouldn't know how to do any of it. I haven't had any issues flashing, but I followed the steps I quoted from the get go and do that every time. Currently I'm back on the last KitKat nightly because Netflix/Play Movies is still not working on CM12. Have you tried any of the CM11 builds? Im currently using:
http://download.cyanogenmod.org/get/jenkins/98444/cm-11-20150118-NIGHTLY-l900.zip
and I use the 20140606 GApps package found here:
http://wiki.cyanogenmod.org/w/Google_Apps#Downloads
The Commish said:
Anyone getting Netflix or Play Movies to work yet on the latest versions? It's the only thing that made me have to revert back to CM11. I tried looking over the change log but honestly I don't know what half that stuff means.?
Click to expand...
Click to collapse
Odd that Netflix and Play Movies don't work. Plex, Amazon Instant Video, MX Movie Player, and Chromecast all work.
Sent from my SPH-L900 using Tapatalk
Deleted
Hi folks,
Just decided to retire my old S3 and when looking for a new phone my main requirement was to get a good DAC built in without breaking the bank or renewing my contract, ended up with the Sprint Note 2. Naturally I was excited but quickly put off by the stock ROM so I decided to root/flash, etc. This is what happened so far;
-Rooted with newest TWRP and root verified on stock rom (followed NK2 instructions)
-Made the big mistake of flashing now without backup, after trying a couple of roms I kept having the same problem (phone gets stuck in load animation indefinitely regardless of rom flashed)
-Gave up on custom roms so I flashed a rooted stock NE2 rom and phone turned on wooohooooooo
-But wait, no network connection, no voice or data, tried to flash modem zip file from http://forum.xda-developers.com/showthread.php?t=2139889 but it keeps saying zip is corrupt, redownloaded & recopied to SD with the same result.
Now I have a working phone but not so working since I can't place calls. What went wrong? any help is very very appreciated.
Phone works after flashing Alliance ROM but somehow now TWRP recovery is gone and phone is UnRooted which is less than ideal but it works nevertheless...
Now before I go off wasting a whole day flashing & waiting for battery to recharge can anyone please point me in the right direction?
I need to figure out the following:
-Root method that works, I'm on Alliance NE2 now
-Which recovery is best recommended for current ROMs?
-Need a kernel that enables audio features like Direct DAC & upsampling
-ROM that actually works with said Kernel and functions at least 90% with wifi tethering etc.?
Surprised it's this difficult with this phone coming from the S3 which took me no more than an hour first time rooting/flashing.
hhmmm 63 views and nobody able to help?
Currently stuck on this ROM, which is horrible because maps doesn't work well, pandora crashes, UI fc's left & right and to top it off the phone is sluggish in every way possible.
Unified Toolkit not working, drivers installed properly, ADB visible in device manager, debugging enabled yet phone can not be seen by Toolkit.
I really don't want to switch back to my cracked S3 but I'm not left with many options considering my note 2 is barely usable now.
Is anyone out there... there.... ere... ere... ere.....
lol seriously feeling like I'm the only person left in these forums.
Use odin to flash recovery but make sure you uncheck reboot option. Once flashed remove battery and while doing the recovery hotkeys insert battery. Now wipe everything and flash another rom.
Sent from my GT-N7105 using XDA Premium 4 mobile app
here's what I've done now;
-Flashed newest TWRP via Odin
-Wiped & flashed Rwilco12's NE2
-Rebooted and phone booted yipeeee
-No cellular connection, crap phone i hate you
-Rebooted to recovery & flashed NE2 Modem
-Rebooted again and recovery is now gone
So either I get root but can't use the phone as a PHONE
or I loose Root and get basically the same POS I started with.
I've given up on eye candy, custom rom, custom settings and my expectations have dwindled down to just ANY ROM + Root + Tether yet that can't even be accomplished. I know I'm doing something wrong but at this point I'm over 10 hours into trying to figure this out and have no idea what to do next. Anything?
Finally:
CWM Recovery - OmniROM - Micro Gapps - Devil Kernel - Rooted
In case someone is in my shoes and hating life, I'll save you a lot of headache by telling you that TWRP recovery does not work for 90% of the ROMs that are still available for this phone so use Phil'z CWM
oceanisbleu said:
Finally:
CWM Recovery - OmniROM - Micro Gapps - Devil Kernel - Rooted
In case someone is in my shoes and hating life, I'll save you a lot of headache by telling you that TWRP recovery does not work for 90% of the ROMs that are still available for this phone so use Phil'z CWM
Click to expand...
Click to collapse
Twrp 2.8.6.x works for almost every rom but you will find most users recommend philz. I as a wantabe dev will suggest philz 6.0.7.9 expect in a few rare cases with aroma installer needing twrp. Personally I have philz 6.9.7.9, twrp 2.8.6.0, shift dual recovery and devil dual recovery zip on my external sdcard. This way I always have what I need depending on what I am doing.
All this info along with solutions to every problem is here on xda already. It may take some time to find everything but really the users should do his homework before doing anything to the phone anyways.
Also if you read the rom thread (Alliance) you would know why you lost root. Simply put you updated supersu app and binary. It is a known issue on every ne2 based custom rom for this device.
Sent from my GT-N7105 using XDA Premium 4 mobile app
Hey thanks for the feedback.
Almost everything I tried on twrp failed, when flashing anything I follow all instructions in the OP's first page. In Alliance's case the resolution to the issue does not come up till page 23, I'll just be honest & say I haven't and probably will never read every page of comments before flashing a ROM, 10 pages okay but beyond that it's more trouble than it's worth.
Can that same issue happen with all other ROMs? on Omni I just ran Root Checker & it said not properly installed!
oceanisbleu said:
Hey thanks for the feedback.
Almost everything I tried on twrp failed, when flashing anything I follow all instructions in the OP's first page. In Alliance's case the resolution to the issue does not come up till page 23, I'll just be honest & say I haven't and probably will never read every page of comments before flashing a ROM, 10 pages okay but beyond that it's more trouble than it's worth.
Can that same issue happen with all other ROMs? on Omni I just ran Root Checker & it said not properly installed!
Click to expand...
Click to collapse
I will read every page myself even if it takes a week. You say reading it is more trouble than it is worth which is why you had that issue with Alliance. Same goes for your omni issue.
If you don't want to read that is up to you. A google search will normally help with common issues. I dont mind helping but you have to help yourself first. Not to be rude but I wont answer your omni question because you have not looked. Ypir issue is the number 1 issue omni users have.
Sent from my GT-N7105 using XDA Premium 4 mobile app
won't argue with your opinion as I have my own
oceanisbleu said:
won't argue with your opinion as I have my own
Click to expand...
Click to collapse
I see you edited that a bunch. I dont mind helping. I have been helping so far. Now about the omni gps. I only know on possible fix bit it is a pain.
1. Flash stock/stock based rom
2. Get gps lock
3. While locked and in app reboot to recovery
4. Wipe and install aosp rom & gapps or restore aosp backup
Then you might get gps lock.
Sent from my GT-N7105 using XDA Premium 4 mobile app
reading back I realized some clarity on my part would have been helpful rather than make a general statement.
So the issue with reading 25, 50 or a 100 pages isn't by choice (may have sounded arrogant the way I said it at first) but I work 50 hrs a week, I do work on my home myself, I rent out rooms to students, I have other projects going, etc. so a very very busy lifestyle. Not to mention the daily crap that tends to come up all the time the moment I get home from work so in short, I really can't afford the time to read in that much detail whether I want to or not.
Regardless, by no means am I lazy when it comes to research, notice my post count? yet I've been here since 2009, and since 09 I've had at least 8 different phones (windows phones too) I really try to figure out everything I need on my own so in this case I spent 3 days working on my initial issues, after that I posted this thread which was 8 days ago and had it figured out and finished yesterday (a few bugs aside), that's easily 10 days I spent at least an hour or two a day working on one thing. Surely you understand how frustrating that must begin to feel.
Regarding my last reply, haha I had to delete most of it because I realized I was beginning to take my frustration out on you when in fact you're the only person who actually offered help (still very very thankful) and to top it off I screwed up the rest of the reply when I mentioned GPS, got that mixed up with the topic we were actually discussing (losing root) this happened because I was reading through the GPS issues before I got to your reply and yah mixed it all up, so again apologies for the lack of clarity and thanks for your last reply, it's more straight forward than all the comments I found on that issue.
You won't have to explain anything else I promise haha and I did all this just now but want to verify I did it correctly so I don't come back to it again. After flashing ROM/Gaps/Kernel & supersu, never update supersu after running rom correct?. Root verified as of 30 minutes ago.
GPS, this one is a big big deal because I use it for work but I had already found the answer pretty quickly as I had read something about it before I even flashed Omni.
I do know how frustrating it can be. I have been in worse spots and had to create my own fixes which I have shared here. As far as time goes I understand that being a parent of 7 children.
I am still active here and always willing to help others long as they help themselves also. We seem to have gotten off badly. While some of your post seemed you had done nothing to help yourself. So lets forget earlier stuff and move on.
Yes you seem to have all the steps correct.
FYI android 5.0-5.0.2 all have gps issues but there is a flashable fix. Most new 5.1.1 builds have gps fixed.
If you run into any issues feel free to ask but include steps you have taken to fix the issue. The more you tell the better help you can get. Plus others wont think you are wanting to be spoon fed.
Sent from my GT-N7105 using XDA Premium 4 mobile app
haha thanks for understanding, very much appreciated.
7 kids??? where do you find the time? my situation does not fare in comparison :laugh:
Now that I've resolved the "failed" issue when flashing ROMs I may be brave enough to test some 5.x.x out, I had stuck to 4.x.x because I was under the impression that they were more stable...
Would you be willing to recommend any specific ROMs based on our discussion?
By the way, I tend to ramble on and on most forums that's a bit faux pas so I've sorta been conditioned to keep it sweet & short, clearly that is a bad approach on here, we live & learn
oceanisbleu said:
haha thanks for understanding, very much appreciated.
7 kids??? where do you find the time? my situation does not fare in comparison :laugh:
Now that I've resolved the "failed" issue when flashing ROMs I may be brave enough to test some 5.x.x out, I had stuck to 4.x.x because I was under the impression that they were more stable...
Would you be willing to recommend any specific ROMs based on our discussion?
By the way, I tend to ramble on and on most forums that's a bit faux pas so I've sorta been conditioned to keep it sweet & short, clearly that is a bad approach on here, we live & learn
Click to expand...
Click to collapse
Well I personally have a Frankenstein device. It started out as a sprint l900 but I removed the sdcard/sim board and put a n7100 board so I can use a cricket sim. This causes issues with calls on aosp so I run modified t0lte (n7105 international) roms.
As far as 5.1.1 roms I personally build 2. First is CyanideL (highly modified cm base) and broken (a highly modified slimroms base). Those two are really the only two worth flashing. There is also cm and I think a liquid rom but they don't have the features of the two I compile.
If you want a stock based rom I did the Community Rom (s5/n3 based) which is stable with only two issues. Spen clipping does not work and updating suoersu causes loss of root.
Sent from my GT-N7105 using XDA Premium 4 mobile app
jlmancuso said:
As far as 5.1.1 roms I personally build 2. First is CyanideL (highly modified cm base) and broken (a highly modified slimroms base). Those two are really the only two worth flashing. There is also cm and I think a liquid rom but they don't have the features of the two I compile, I believe Phill'z CWM download link is down as well.
If you want a stock based rom I did the Community Rom (s5/n3 based) which is stable with only two issues. Spen clipping does not work and updating suoersu causes loss of root.
Click to expand...
Click to collapse
wow CyanideL is you, how did I miss that?? looking at too many ROMs is how I suppose...
Going to CyanideL asap. Seriously thank you for keeping the CyanideL thread up to date, it drove me crazy to read & read & read in ROM threads for a while until I decided "okey let's give this one a try" only to find out that the download links are broken or the files are no longer there, had that issue with Omni till I found comparable files on another website (gapps I think it was) and Phill'z CWM thread has a dead end download link as well.
I was really really wanting CyanideL to work for me last week (when I was having the flashing issue) and was so bummed out every time I failed to flash it. I plan to make a donation as soon as I get it working, I feel like I owe you simply for the time you've spent on my thread alone and of course I love supporting people who support families :highfive:
oceanisbleu said:
wow CyanideL is you, how did I miss that?? looking at too many ROMs is how I suppose...
Going to CyanideL asap. Seriously thank you for keeping the CyanideL thread up to date, it drove me crazy to read & read & read in ROM threads for a while until I decided "okey let's give this one a try" only to find out that the download links are broken or the files are no longer there, had that issue with Omni till I found comparable files on another website (gapps I think it was) and Phill'z CWM thread has a dead end download link as well.
I was really really wanting CyanideL to work for me last week (when I was having the flashing issue) and was so bummed out every time I failed to flash it. I plan to make a donation as soon as I get it working, I feel like I owe you simply for the time you've spent on my thread alone and of course I love supporting people who support families :highfive:
Click to expand...
Click to collapse
Well the donation would be nice but understand when you hit my donation button/link it will take ypu to the Red Cross donation site. That is not a mistake. I personally dont take donations and feel of someone wants to donate something it should go where it can be used by those who need it.
Sent from my GT-N7105 using XDA Premium 4 mobile app