Related
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...
I'm having a frustrating problem with my note 8
Here is a pic showing the problem
imgur.com/zBHKJrn
Whenever I stream a video or a gif it shows those frustrating stripes
This problem started when I upgraded to CM13
Any idea how to solve it?
I have seen issues like that after messing with various kernel and ROM loads.
Seems like some loads will not play well until the device is clean.
My method now goes over and beyond what peeps here request when loading a cutom build or kernel.
1st I remove the battery connector for a few minutes. Once the device is cleared, I reconnect the battery and boot straight to download mode and flash a factory ROM to make sure every option available functions.
Once I am done testing, I then boot into download mode after I power down the device.
Once in down load mode, I flash the recommended recovery for the custom ROM. Not all recoveries will perfectly load a particular ROM or patch, so be careful on what recovery you choose.
Once the recovery is loaded, you can then wipe the device and clear both caches. I even go into aroma and wipe out the internal SD files and folders if the recovery used does not do so. Stock recovery does when doing a factory reset. Philz does not completely wipe the internal SD when clearing out for a new ROM.
If you choose to run Boeffla CM13 kernel, load it before rebooting when you have completed the CM13 load. It does make a difference, at least for ROM builds that do not have Boeffla kernel as listed to use.
Also I have found various boot loaders effect various custom ROMs. Seems like a lot of older builds work well for peeps with older boot loaders. Right now I am a wee leary for using the latest version on my WIFI version. Seems like I am forced making a cutom ROM from the latest Samsung build to be very much like a build that is flakey on the new boot loader. All because I wanted a good stagefright fix, perfect miracast, and a few 4.4.2 operational fixes, and multi DPI.
Well thst sums it all up... careful cleaning and careful installation procedures, should keep difficulties at bay.
Okay I'll summerize what I understood since I'm not an expert
1) Remove the battery connector
2) Flash factory rom
3) Flash the custom recovery -TWRP is fine I guess-
4) Wipe the device through recovery
5) Kernel and rom installation
In case these steps are perfectly right
- I'd like to ask more about the battery connector step since I don't actually know how to remove the battery in N5100 I thought it's sealed.
- Also the kernel step, I don'y totally get it to be honest so if you can explain more or provide links for other threads about kernel to help me understand that would be appreciated greatly.
I was wondering:
-Will flashing the kernel only solve this?
-Maybe a full wipe will? Since I upgraded from CM12.1 to CM13 directly without wiping the device
Thanks alot for your reply
You have it in a nutshell, just be sure the stock firmware loads from odin and functions as it should, miracast, power buttons, wifi, sounds and all work propper... once satisified, you can flash your recovery, be sure to flash the recommended recovery by the ROM you select.
As for links? I assume kernel??? Check in the Development section... it is one of the top 5 topics. Boeffla Kernel for CM13. You can try it though read up as it is fairly new. Compare the differences in other CM13 kernels before jumping in. Some kernels provide options that you may find more important.
Battery can be accesed by removing the spen from the case, and removing SIM if available and SDRAM card if available from the side of the device. You can pop open the back over by care fully using a plastic knife and wedging it between the backcover and the silver frame at the opposite side of the buttons. Be sure to have the device off and buttons clear from being pressed accidentally.
Once you press enough you will notice the cover seperating under the plastic knife. Try to wedge a credit card and run down along the seam. This will sound like a zipper as each tab will give a light pop. Be careful to do the the full length of the buttonless side first and work from corner to corner once the side has been disengaged. When you have only the button side to free, place the tablet face down and rock the cover up and down while pulling away.
When the cover is removed, there will be a connector coming from the battery. It will have two red, two blue and two black wires. To remove I use a very small hobby knife and with the blade facing away from the connector ... I slide it under the wires against the connector. Being careful to lift lightly til the side that lifts snaps, and then life the oposite side while lowering the handle of the hobby knife a wee bit.
Do not lift the wires straight up... as the wires are brittle at the battery. You will not see the battery connections for the wires because of the mylar covering to protect the battery.
To reconnect just line up the connector carefully and press down. It should snap in place.
As for flashing the kernel... simply flashing a kernel will not correct a settings issue. The device has android settings, and internal settings. Kernel is set by design, so flashing the kernel soon after flashing a new ROM will keep unknown android settings from effecting how a new kernel functions. Plus when a new Android ROM loads, the kernel has routines that may allow the ROM to load system info differently than previous kernel, so swapping kernels back and forth may not be as good as starting off fresh with your kernel and android load.
Note: This should go without saying since this is a very early beta build, but I'm not responsible for any direct, or indirect damage done to any phone or accessories from flashing/ using this rom.
Also please read the entire op before installing/posting.
Welcome to:
THE ARKO PROJECT
About the Rom:
I started this whole project when I had a G5, and development was still slow. I met someone who was kind enough to get me started, and give me the basic info I needed to start my journey in development. I had always wondered if I could, but never really knew where to start.
Seeing the lack of development for such a great device. I decided to take matters into my own hands (however inexperienced they may be). So far I've created basic tweaked stock roms for the G5 & G Stylo. I never released them however because I didn't make it too far. Because the devices ended up being damged (which is unusual for me).
Anyway that brings us to here & now. This rom is also very basic (for now). I plan however to add as many features as possible & plausible. While keeping it fast, smooth, and reliable. Rest assured I test every build for at least a couple of days before posting them here. Anyway onto the good stuff.
Source: Pulled from stock MM 6.0 30d
Boot img: Pulled from stock MM 6.0 30d (changed to insecured).
Android ver: MM 6.0 30D
Features:
Rooted (Sytem install)
Wifi, data, bluetooth etc. all working
Dpi set to 560
Debloated (More apps removed in future updates)
Busybox
All app multiwindow support enabled by default
Quick power on
Auto rotate in homescreen (tested with Nova Launcher)
Faster video streaming
Increased wifi scan interval
No ring delay
Enabled Adoptable storage
Jpeg quality 100% plus other media enhancements
Disabled error reporting
And some more I can't think of....
Planned features (feel free to suggest some):
4 way reboot
Volume button orientation mod
Possibly aroma installer
That's all I can think of off the top of my head but there is more.
I also plan to make a few color ui themes as well.
For example
Red & Black
Blue & Black
Green & black
Etc. Etc.
Feel free to request different colors as well (doesn't mean it will neccesarily happen, but you can ask
Install instructions:
*Make sure the version of TWRP you are using supports updater-scripts! This is very important! If it doesn't the rom will not flash! I'm using the latest version of multirom TWRP, and can confirm the rom flashes just fine.
1. Make a TWRP backup (optional, but heavily suggested)
2. Download and place zip on sd card
3. Do a full wipe
4. Install zip
5.Enjoy
Note: updates are disabled two minutes after booting the rom. No user action is required. The old method I had tried didn't actually work. Got the ota again a week later. However it is 100% fixed now.
New DL link: https://drive.google.com/file/d/0B1bdSH2f5u2UMzdBUlkzcTFBMU0/view?usp=drivesdk
I don't know if this would work since I have not really put much research in to it, but could you make the folder where the update is downloaded to read-only?
BoredKender said:
I don't know if this would work since I have not really put much research in to it, but could you make the folder where the update is downloaded to read-only?
Click to expand...
Click to collapse
Probably not a good idea. Folder also has a few log files too. If all else fails then I'll give it a shot. I also had a thought that perhaps it isn't named anything like lgdmsclient.
After some sleep I've got a couple days off work so I'm gonna try to get multi rom working. (Haven't used it since kk early android L. That way I can just go down the list remove lg services apk's one by one and hope that either multirom or twrp could save me from a brick if anything goes wrong. Right now I have been using the delete update.zip/reboot. To keep the zip off my phone. Only problem is it takes a while for the system to realize an update is available after that. So It would be easier to remove an apk, build, flash, repeat until I find the culprit. MR will really help though as it'll save a lot of time between flashes. I really do appreciate the help/input though.
Also I've randomly found myself booted into twrp and the update try to install itself. Just luckily had zip verification on so it didn't flash.
Removed build.
Deleted
The Rom now has it's own thread in Tmo Android development located here:https://forum.xda-developers.com/tm...t/rom-arko-project-g3-edition-6-0-mm-t3555919
Moderater if you will please, close this thread. Thanks.
Thread Closed.
Ok so I have a HTC ONE M8, it says it has Android 6 and Sense 7 and I am in UK.
I have unlocked the bootloader, installed TWRP 3.2.3-0 (and backed up) and Rooted with SuperSU 2.82
So all I need is a rom...
I have been looking for hours trying to decide which rom to try but I am at a loss.
My needs are simple...
1. The newest version of android I can get (just to annoy my dad)
2. I must be able to blacklist calls and texts (without needing an app)
3. No bloatware, I don't want my phone doing anything unless I want it to.
4. Things like blinkfeed are totally not wanted.
5. I am not even sure what sense is, I am pretty sure I don't use it
That will do it, thank you for looking. Suggestions?
alphalvr said:
Ok so I have a HTC ONE M8, it says it has Android 6 and Sense 7 and I am in UK.
I have unlocked the bootloader, installed TWRP 3.2.3-0 (and backed up) and Rooted with SuperSU 2.82
So all I need is a rom...
I have been looking for hours trying to decide which rom to try but I am at a loss.
My needs are simple...
1. The newest version of android I can get (just to annoy my dad)
2. I must be able to blacklist calls and texts (without needing an app)
3. No bloatware, I don't want my phone doing anything unless I want it to.
4. Things like blinkfeed are totally not wanted.
5. I am not even sure what sense is, I am pretty sure I don't use it
That will do it, thank you for looking. Suggestions?
Click to expand...
Click to collapse
First, you need to know there is no "golden rom" that will make everyone happy. You have to try them out yourself and see which one you like the most.
Anyway, to answer your questions:
1. Lineageos 16 currently is the only rom with android pie. However it's very early release, so minor and major bugs are to be expected. I'd recommend you lineageos 15.1 instead - oreo isn't that old and the rom is very stable.
2. It's possible on lineageos 15.1 and roms based on it, should also be possible on 16. Not sure about sense roms.
3. Almost all of the custom roms don't have bloatware. Also you can get root and delete apps you don't need.
4. Blinkfeed is only in stock roms. You can disable or uninstall it.
5. You're using it 100% of the time. Sense is the name of android skin on htc devices. It includes changes in look, feel and some functionality compared to stock android. You should know there are sense based roms - they are based on the stock rom, retaining sense functionality and look and custom, pure android roms - those have only minor changes in them and feel and look like stock android.
Great answers in the previous reply. Just wanted to add:
What qualifies as "bloatware" is completely subjective. The goal of the makers of these built-in apps (whether it be a manufacturer, carrier, or even Google themselves) is to provide useful apps. But that doesn't always work out, and certainly not always for everyone. However, what qualifies as "bloat" to one user, is a useful or even necessary app for another. So you say "no bloat" doesn't mean too much; without you being specific about what you want/need and what you don't. Therefore, there are various approaches/answers:
- If you refer to HTC specific apps, these won't be present in any of the more current ROMs. By definition, HTC stopped supporting this device with OS updates at Marshmallow. Anything after that, will be non-HTC and therefore AOSP or "pure Android" based.
- The AOSP based custom ROMs will often allow (even require) you to flash Google apps (gapps) separately from the ROM. This also allows you to choose which gapps package to install, and therefore tailor to your own needs. From minimal installation to get Android to work; to full suite of Google apps (many of which, a lot of users will consider bloat).
- Any pre-installed apps can be disabled or removed with root. Although you should take caution, as removing some bloat apps may break other phone functions. Unless you research and know the specific app is safe to remove, better to disable or "freeze" it with a root app like Titanium Backup. Then test the phone for a while, to see if there are any resulting bugs or issues.
Thanks, I have never really got into the whole Android and Iphone thing. My best ever phone was a Nokia N-gage and I only stopped using it recently due to my eyes not being what they once were.
My last phone was a LG nexus4 and I have only switched it up to the M8 as i saw it in a friends house with a broken screen.
I can already see it is a tad more responsive and to be honest the stock rom is probably fine for what I do (nothing + odd game) but where is the fun in that
Going to download lineage 15.1, sounds like a good start.
one last thing my M8 is 16GB of which 6GB was used, then I backed it up and that sucked up another 4GB so what happens exaclt when i install a rom does the original 6GB become free again? i have installe roms before back in the early days but my memory like my eyes aint what it once was
OK so i just jumped in and followed the 15.1 instructions (i think) Installed the rom, the suggested superuser thing and that went ok, but when installing the gapps (nano) it failed with lack of space. Doing something wrong??
The rom is starting with pink balls so I am almost there......and it is working. I went back and tried to flash gapps nano again and it actually says there is insufficient space on the system partition.
Resized it, then it seems to have worked. thanks guys i love it so far.
alphalvr said:
one last thing my M8 is 16GB of which 6GB was used, then I backed it up and that sucked up another 4GB so what happens exaclt when i install a rom does the original 6GB become free again?
Click to expand...
Click to collapse
No storage is going to free itself up, from flashing a custom ROM. You will have to free it up yourself. You can delete the LOS ROM zip, once it has been installed. Although, I like to keep copies of custom ROMs on my computer for a while, just in case I need it again in the future.
If you have an SD card installed to the device, you can have your TWRP backup on the SD card, which will free up a lot of space. As you've seen, the TWRP backups take up a ton of storage! Having a backup on the device (either SD or internal storage) is "best practice" in my opinion; so it is handy in case you need to restore that backup.
You'll never get all 16 GB of storage. A significant amount is taken by the system (OS) and other uses. I think something like 12 GB of user-accessible storage is all you will ever see on a 16-GB device. And this starts to be eaten up the moment you start installing apps and using the device.
You guys have been a great help, I ordered a 2nd m8 off ebay and a genuine HTC dot matrix case although I now realise the dot thing is part of sense which I no longer have. whoops
I didn't realise at the time because everything seems to work but when i was installing I kept seeing a red line of text. iirc it was something about unable to access dalvik partition? I only realised it shouldn't have been saying that when I watched a youtube video of installing a rom that wasn't plagued by this line.
I need to do it again to try and figure what was going on.
Wanted to keep a thread for each one opinion on custom roms and why do you choose the rom you are using?
i have tried al custom roms and i always love to flash different ones,
What do you notice regarding stability? performance? battery ? bugs? etc in the rom you are using.
Love to hear all your opinions on this matter.
last time i flashed a custom ROM 10years ago. No need to flash anything since. All factory stock.
All i did for every phone is bloatware removal via ADB
I've only ever used the stock rom since I've had this phone. Using A11, A12 and now A13.
Only 1 annoyances during my time with this phone and stock ROM. ( Camera related blue light bleeding in a very bright artificially lit scenario )
Always stock rom with Root these days
Holy smokes. It's ok to not answer a question if it doesn't apply. Pardon my double negative.
I've been contemplating moving on from to stock to custom, when I came across this thread and thought, well this will be great; several viewpoints about several custom roms, but instead came across a few responses that didn't answer the question that was asked.
It's hard to sift though the roms' threads because, in most cases, you'll see "this is a great rom, everything works perfectly", almost immediately followed by "stuck in a boot loop", "looks like msm again", or "xyz is borked, please fix".
So, to reiterate og's question, what are the thoughts on the custom roms (not stock) for the 1+9pro (not a device from your past)?
Nameless seems to be the most stable out of the custom roms, but lacks more in depth customization. CrDroid and Watchdog are better for customization, but more features usually means more bugs.
I've tried tons of the roms on here and will probably continue to do so as stock OOS just doesn't do it for me. Battery isn't ideal, and aesthetically it's hard to configure to what I like. It definitely works for a lot of people as it has many features and is mostly stable.
kodayoda713 said:
Nameless seems to be the most stable out of the custom roms, but lacks more in depth customization. CrDroid and Watchdog are better for customization, but more features usually means more bugs.
I've tried tons of the roms on here and will probably continue to do so as stock OOS just doesn't do it for me. Battery isn't ideal, and aesthetically it's hard to configure to what I like. It definitely works for a lot of people as it has many features and is mostly stable.
Click to expand...
Click to collapse
You favor nameless I'm guessing?
It depends on the day honestly. I have a disease, haha. As of right now that's what I'm using. But I'm sure I will flash something else here in the next week.
kodayoda713 said:
It depends on the day honestly. I have a disease, haha. As of right now that's what I'm using. But I'm sure I will flash something else here in the next week.
Click to expand...
Click to collapse
I'm currently on stag os 13, beta from october with a pair of important bugs... however probably I will flash another one tomorrow. I have to decide first which one xD
However I would ask you what are the steps now for flashing another android 13 rom, considering I'm on android 13 and I prefer not do a clean install (dont want to do any wipes as I have my phone tweaked and fully oriented for privacy)
Los20 Google free
Without gapps, store and ps apps
been on nameless for about 6 months, no complaints
Running my own fork of LineageOS 19 with features cherry-picked from other ROMs (nothing against them but I don't need the extra 30 fazillion features they offer when a handful of features I want does the job just fine). Once LineageOS 20 builds resume with fixes for some of the major issues in place (see the LOS 20 thread for OP9Pro), I'll be upgrading to the New Hotness (I've already made the necessary changes and tested them on my OP7Pro test phone, I'm just waiting for the all-clear for the OP9Pro).
spamerobaldomero said:
I'm currently on stag os 13, beta from october with a pair of important bugs... however probably I will flash another one tomorrow. I have to decide first which one xD
However I would ask you what are the steps now for flashing another android 13 rom, considering I'm on android 13 and I prefer not do a clean install (dont want to do any wipes as I have my phone tweaked and fully oriented for privacy)
Click to expand...
Click to collapse
Oof, that's a tough one. You could *attempt* to do a dirty flash of the rom you're wanting to flash. Although, I wouldn't recommend. I've read that people do it with little side effects, but I've also seen people with lots of bugs.
What I typically do is use swiftbackup for SMS and apps, then just restore those on the new rom. But, depending on what tweaks you've applied, that might make things more difficult. As far as I know, there's not a way to restore everything, especially if the tweaks are specific to the rom. Maybe someone else might know a way?
I kept mine as stock w/root since I got it. Just reflashed and I was blown away with how much nicer it feels. Even with the amount of work I'd done to kill bloatware, background processes, etc on the stock rom.
kodayoda713 said:
Oof, that's a tough one. You could *attempt* to do a dirty flash of the rom you're wanting to flash. Although, I wouldn't recommend. I've read that people do it with little side effects, but I've also seen people with lots of bugs.
What I typically do is use swiftbackup for SMS and apps, then just restore those on the new rom. But, depending on what tweaks you've applied, that might make things more difficult. As far as I know, there's not a way to restore everything, especially if the tweaks are specific to the rom. Maybe someone else might know a way?
Click to expand...
Click to collapse
thanks for your answer mate
I didn't touch anything specific to the rom nor kernel. Only much app config and some processes freezing.
So I will save apps+data with my old friend titanium backup pro, don't know another method to do :/
By the way, I will lose root if I do clean flash or can I save that any way?
I guess a clean flash instructions should be something like this?
Extract recovery package zip
Reboot to bootloader & connect your phone to PC
Double click on flash.bat
Reboot to recovery home page & tap Factory reset > Format data/factory reset
Back to recovery home page & tap > Apply update > Apply from ADB
Now sideload rom using command adb sideload <rom_filename>.zip
Now reboot to system.
spamerobaldomero said:
thanks for your answer mate
I didn't touch anything specific to the rom nor kernel. Only much app config and some processes freezing.
So I will save apps+data with my old friend titanium backup pro, don't know another method to do :/
By the way, I will lose root if I do clean flash or can I save that any way?
I guess a clean flash instructions should be something like this?
Extract recovery package zip
Reboot to bootloader & connect your phone to PC
Double click on flash.bat
Reboot to recovery home page & tap Factory reset > Format data/factory reset
Back to recovery home page & tap > Apply update > Apply from ADB
Now sideload rom using command adb sideload <rom_filename>.zip
Now reboot to system.
Click to expand...
Click to collapse
Of course, glad I could contribute. Swiftbackup will do data for apps as well, but titanium backup should work too if that's what you prefer.
Yep, there's a couple ways to do it, and that will work. As far as root, you will definitely lose it, but you can either sideload magisk:
- download magisk APK and rename to .zip file
- after sideloading rom finishes, reboot to recovery
- sideload magisk.zip
Or
- follow root guide on this forum
Tried about every rom posted that I can find. A lot of nice roms, depends on what you want for customization. The one I prefer is Xtended. Been back and forth since A11 each one a little nicer. The latest -- v5 is best for me. I always go back to it. Currently on stock OOS13. Not all that bad with little tweaking. My disappointment is the lack of kernel development for the phone after A11. I guess the sources released by OnePlus a mess. Waiting for Ancient to be released. Could be nice.
kodayoda713 said:
Of course, glad I could contribute. Swiftbackup will do data for apps as well, but titanium backup should work too if that's what you prefer.
Yep, there's a couple ways to do it, and that will work. As far as root, you will definitely lose it, but you can either sideload magisk:
- download magisk APK and rename to .zip file
- after sideloading rom finishes, reboot to recovery
- sideload magisk.zip
Or
- follow root guide on this forum
Click to expand...
Click to collapse
really appreciate your help man, I had forgotten the steps to do root in only 3 months hahaha, my memory is awesome
I followed the method u mention and worked fine
For my words seems I am a newbie but only old hahahah, don't blame on me. I'm on this world of customization/tweaking phones since the old htc one and the first iPhone, so every day it costs me more as I increase my laziness year every passing year xD
spamerobaldomero said:
really appreciate your help man, I had forgotten the steps to do root in only 3 months hahaha, my memory is awesome
I followed the method u mention and worked fine
For my words seems I am a newbie but only old hahahah, don't blame on me. I'm on this world of customization/tweaking phones since the old htc one and the first iPhone, so every day it costs me more as I increase my laziness year every passing year xD
Click to expand...
Click to collapse
Haha, glad I could help! Memory is my biggest downfall as well, so you're not alone lol
Other backup options I like - tarb and Neo Backup. Swift I don't like because it only stores the latest backup, and the google play tied licensing is annoying when bouncing between various devices.
Used to love titanium backup but it never works successfully for me anymore