Clean AOSP 4.1.1
build 5 (JRO03R)
for the Verizon LTE Galaxy Nexus (toro)
Twitter: http://twitter.com/javroch_dev
Based off of the AOSP "android-4.1.1_rX" branch. it's a mostly bare ROM, basically just rooted. I'll slowly add the previous features back in subsequent builds. I redid everything clean, from the ground up, for 4.1.1.
NOTE: I don't know if this 4.1.1 release will bring a new kernel with it, when Verizon releases it. As well, I don't know if there will be a new radio/etc, but this ROM does not include those if so. radio.img's aren't released via AOSP as far as I know. Feel free to correct me, if I'm wrong.
Modifications:
The only modifications that I have made are listed below, mostly they include enabling features that are already included in AOSP's source code, but weren't enabled by default:
Here's what's made it so far for 4.1.1:
Root/Superuser (ChainsDD)
Wi-Fi Tethering Subscription Check Removal
Enabled Backup/Restore
Google Movies access fix (peteralfonso)
Root Settings/Selective Root (cyanogenmod)
Custom "Clean extras" settings panel
Settings shortcut to Clean extras for easy access
SIP+VoIP
Battery Percentage in Status bar (Icon, Text, or Both)
Fixed Facebook Contact Sync (romanbb)
Reboot/Safe mode Options in Power menu
Here's what's to come in the near future:
Screenshot Options in Power menu (DvTonder)
Airplane/Silent Mode toggles via Custom extras
Number of home screens Option in Clean Extras
Aside from the explicit credit given above, I also spent tons of time looking through the git repo's of cvcps, peteralfonso, cyanogen, and many others. As well, I often used howto.ccroms.net and source.android.com/source as references. I'm sure there are others I'm not giving credit to that should be getting it.
Let me know what you think or if anything is broken! This is still a learning experience for me. Nobody's perfect.
Current Version: http://bit.ly/R71Yu8
MD5: 023271a54f428bb2197e667b9033ffe4
GApps: http://goo-inside.me/gapps/gapps-jb-20120726-signed.zip
Previous Versions:
4.1.1 for us with gapps: http://goo-inside.me/gapps/gapps-jb-20120726-signed.zip
build 4: http://bit.ly/QeH61x, md5: 3cc96cc0d703300a52ca885e49f73139
build 3: http://bit.ly/Tq0g88, md5: f3dea30b0922e2d67926510a6afd2a31
build 2: http://bit.ly/R69UYK, md5: cbbcadf2ed7a4ca7a516389abe6338af
build 1: http://bit.ly/PRByu2, md5: 69d101d025037c554ea2d0b25b55ad25
build 0: http://bit.ly/NqmH9M, md5: 3ad6f6134656b7adf65c6b48c8f5805f
4.0.4 for use with gapps: http://goo-inside.me/gapps/gapps-ics-20120317-signed.zip
build 5: http://bit.ly/HPGMq8, md5: eb0daa742d56189b770ff0662a984b12
build 4: http://bit.ly/IP7omo, md5: 1ec18075db77936b4972a7593a5878ec
build 3: http://bit.ly/HlA1ah, md5: fbcde7d07617ead21a369756df306304
build 2: http://bit.ly/HHYVQF, md5: e989c25388feaabee5da92c6c0965b7c
build 1: http://bit.ly/H3oM5P, md5: 590c36c905cd50a072027bbf9da8b1d1
4.0.3
build 4: http://bit.ly/GGEK7W, md5: fc1b733d37c8d61c21a3f248b8b6a2b7
build 3: http://bit.ly/FPBsSK, md5: 53dc910d5e1c23c32c7e4a696d679790
build 2: http://bit.ly/xbzUKR, md5: 56ccfc3856e0f6ea8e7aaecbbdc7b799
build 1: http://bit.ly/xNzKZQ, md5: a373793a69fb193ca162f24a719636b3
I just flashed to AOKP, so I will run that for a while. But, I will try this next.
Thanks!!
Updated / cleaned up the description to provide more information
Added the md5 - a373793a69fb193ca162f24a719636b3
Just a heads up, I'm in the process of migrating everything over to github. As well, I'll be adding facebook sync and possibly one or two more tweaks hopefully tonight. Also, starting with the next release, I'll be naming them "Clean AOSP x.y.z build #". So, the update hopefully coming tonight will be "Clean AOSP 4.0.3 build 2". Any further tweaks / modifications will probably be added to a separate ROM, possibly Clean AOSP+, because I really want to keep Clean AOSP tweak free.
Build 2 posted, includes fixed Facebook Contact Sync. That's about it for now. Next thing I want to do is validate whether or not Google Wallet is working. I've been able to use NFC to beam, etc and everything else seems to be working fairly well so far. Let me know if anybody has any feedback for me
I tried to see if I could get Twitter's Contact Sync working in a similar fashion, but it seems it's an issue on their end: http://support.twitter.com/groups/3...cles/213727-known-issues-with-the-android-app
so to clarify...the apps like rom manager and terminal emulator will be removed?
I hate having to delete all the apps from CM9
thinking about making a rom that is as close to stock as possible (all google apps and stuff but its still going to be based on CM)
if your rom removes all this stuff....niiiceeeeeee.
ezcats said:
so to clarify...the apps like rom manager and terminal emulator will be removed?
I hate having to delete all the apps from CM9
thinking about making a rom that is as close to stock as possible (all google apps and stuff but its still going to be based on CM)
if your rom removes all this stuff....niiiceeeeeee.
Click to expand...
Click to collapse
My ROM isn't based on CM at all in any way whatsoever. It's based on AOSP source directly. So no, there won't be any ROM Manager or Terminal Emulator included by default. My goal for this ROM was actually exactly what you said, "[to make] a rom that is as close to stock as possible".
I'm not gonna add this as a "Modification" or anything... because I didn't really do anything to fix anything, but I just wanted to confirm that I was successfully able to use Google Wallet on Clean AOSP last night. Apparently, I just needed to "Reset Google Wallet" from when I flashed from stock
today, i will begin working on implementing the new root settings menu from cyanogenmod into clean aosp. i feel that this is really an essential feature for any ROM and so i think this is a necessary modification for clean aosp
I'm currently uploading build 3. should be up tonight / tomorrow. it includes the root settings menu under developer options. the menu provides four options "Disabled", "Apps Only", "ADB Only", and "Apps and ADB". currently the default in build 3 is "Apps Only", however i will probably be putting out a build 4 which defaults it to "Disabled". my code is mainly based off of cyanogenmod's commits mentioned in the blog post here, and functions much in the same way. cm doesn't build Superuser from source, but i do, so I also added some of my own code related to this in Superuser. basically in CM it would say that superuser had granted apps permissions if they were on the whitelist, even when root was disabled via the settings and they didn't actually have root. i plan on launching the developer's settings intent as well, if you get denied superuser permissions because the setting is disabled. this way you can easily re-enable it. but that isn't in build 3.
i should note that this way doesn't seem to give you access to google play movies. i like to think of it as a selective root, rather than completely removing root altogether. but, the main purpose of this is security, not to enable google play movies. i've been leaving mine on "Disabled", and i really don't find that i have to re-enable root very often.
posted build 3..
This sounds really awesome! Does the voip work and could you include an option to allow led with screen on?
I haven't used it as I don't have a VoIP account, but the options are there and should be enabled/working fine. I'm not sure what you mean by "allow led with screen on" to be honest.
Normally the led will only blink if the screen is off.
foxdog66 said:
Normally the led will only blink if the screen is off.
Click to expand...
Click to collapse
Got it, to be honest I'm sort of reluctant at this point to implement too many tweaks into Clean AOSP. I kind of want it to be as barebones as possible. But, as I am considering a few others, I might look into this one as well, either as part of Clean AOSP or as part of some Clean AOSP+ version with extra modifications that I might put out separately.
Either way, if you do give it a shot, let me know your findings related to VoIP. I have no reason to think it shouldn't work, but I haven't tried it yet.
Thanks for this!
What kernel are you using for this build? I assume the stock google one.
Including status bar toggles and soft key options would be the only mods I would look from the clean build.
BarberAE said:
Thanks for this!
What kernel are you using for this build? I assume the stock google one.
Including status bar toggles and soft key options would be the only mods I would look from the clean build.
Click to expand...
Click to collapse
I'm just using the stock Google one. Haven't changed anything there. Haven't really played around with kernel development.
Those are likely mods I'd include in some sort of Clean AOSP+ version as well. Along with reboot options, though those I might actually shoehorn into regular Clean AOSP as well. Either way, I will be looking to getting in some of these mods in either Clean AOSP or some other AOSP+ version when time permits.
I wanted to wait and get more features in, but I might be busy for the next week or so. So, here's build 4. The only change is that root is "Disabled" by default
I just saw that the AOSP 4.0.4 Source Code is being pushed out today. I'm gonna see if I can't get a build out in the next couple of days, probably just with the features I've implemented for 4.0.3
Related
My new rom Glazed ICS is out so go and grab it and ENJOY. This rom will no longer be recieving features in fact i will be taking away useless stuf to make this a bareboned rom.
GLAZED ROM
Updated 6-7-2012 Scroll Down For Changelog. Scroll down for installing not included gapps (Like talk).
Hello Forum i would like to introduce a new rom called Simple CM9. As you can tell by the name this rom is special since it does not have all the useless items that most roms have. This rom is Sweet and To The Point. This is my first rom ever so give me a break if its bad. (Hope its not). I made this rom because i really enjoyed Takenover83 original cm7 bareboned rom, so i decided to make a ICS one, also because some people were requesting it in the original thread. Anyways enjoy your SPEEDY KINDLE.
Disclaimer - I am not responsible for any damage that is caused by flashing this rom or by modding this rom and flashing etc. I take no responsibility if your kindle breaks, bricks, sets on fire.
|Some of the features this rom offer are|
Super Fast Bootup (Should be working properly since last update)
Preloaded Gapps
Volume Slider in Notification
Extremely Good Battery Life
Great smooth performance
Modified build prop for more Play Store apps.
Custom Boot Animation
ABOUT 85MB <<<<<WOW
|Things that were removed.....| (Gonna upload a package later with all the items)
Some useless apps such as Voice apps
Removed a google search (Dont worry one is still there)
Removed all Live Wallpapers
Removed CM Wallpapers
Removed Androidian Theme
Removed alot of ringtones
Removed Alarm Tones
Removed Spare Parts
Removed lots of languages
Removed Facelock
Removed Default Android Videos
Removed Video Editor
Removed Google Talk
Removed Voice Search
Removed Nagging Setup Wizard (You can login to google account by going into the play store)
Removed News and Weather
Removed Bug Reporting and Feedback
Removed File Manager (Download a new one VIA Play Store)
Removed Download manager (Dont tap a file while downloading will crash browser)
Removed Developer Tools
Removed Terminal
Removed Superuser
Removed Trebuchet
Removed Google Search
Removed Gmail
Removed Email
|Bugs| (Of course every rom has to have bugs )
All of 3.0 Kernel Bugs
Any other bugs please report to me
To Flash this rom do the same as all other TWRP roms.
Wipe cache, dalvik cache, Factory reset, System
Then just flash this rom.
Well thats it for this rom.
WHAT..??? You say you want screenshots?
Video And Screenshots of updated rom will be posted in a day or two.
Thanks to all the people |Takenover83| For his original CM7 Bareboned Rom, Also to |Trojan38| For his vanilla rom as a source. A Big thanks to |Hashcode| without him this wouldnt exist. Whooh finally its over, now to the good stuff
|Downloads|
June 28th 2012 - Download
June 10th 2012 - Download
June 7th 2012 - Download
June 4th 2012 - Download
June 3rd 2012 - Download
|Changes|
June 28th
Removed A bunch More Stuff Look Up
Replaced Trebuchet with Apex, Much Lighter
Created a Custom Boot Animation For It
Lightened up the system now even faster
June 10th 2012
Updated to latest Kernel
Updated to latest CM9 Updates
Removed many of the options that were applied in the June 7th release.
Removed beats audio
Removed CRT tv lock
June 7th 2012
Updated To Latest 3.0 Kernel Thanks Hash
Added MANY options on customizing the system from settings
Updated Trebuchet
Added The SGT7 notifications options, etc.
Fixed the black boot up option (Should Boot Extremely Fast )
Updated CM9 since the last June 7th update.
Removed File manager, Downloads, Developer tools, TweakZV6 (Mainly because TweakZV6 Was just a Placebo)
Added old tv Lock Animation
Added Edge Swipe Navigation
June 4th 2012
Optimized the Speed Quite a Bit
Fixed Build.prop for gameloft games.
Fixed the Usb Storage Problem (Now Properly Mounts)
Added Beats Audio (Its a plus for anybody)
Added TweakZV6 For Optimal Performance
Removed The Remaining Live wallpapers
Removed a couple of Useless Apks such as Google Feedback, ETC
Took off the default adb settings due to inproper mounting
Renamed The Zip File
Sacrificed boot speed for System Speed <<< Sorry
June 3rd 2012
Initial Release
Gapps
If for some reason you need more of the gapps not included such as google talk and others download them from HERE. Note, Flashing these apps will slow down your system quite a bit.
Reserved For Future Use
Thank you for the new ROM, I hope you will keep up to date, many abandoned.
Repositories СM9 updated every day, but no one wants to collect the ROM (
do gameloft's games install in this rom? like gt racing, asphalt...
Cool
excited to try, nice way to start off Sunday morning. Will post any issues i find, or praises
Can you post screen shots of boot animation, the rom, etc
Sent from my Kindle Fire using xda premium
Put the following line in your build.prop
persist.sys.usb.config=mass_storage,adb
And the USB will work without having to go to Settings
nice work will try.Thanks for sharing.
joshuabg said:
Can you post screen shots of boot animation, the rom, etc
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
Will do as soon as i get home later.
Tony84 said:
do gameloft's games install in this rom? like gt racing, asphalt...
Click to expand...
Click to collapse
Whats weird is the graphics intense games like modern combat and ashpalt 6 work but other free gameloft games don't work. Ill see what i can do.
gedemis said:
Put the following line in your build.prop
persist.sys.usb.config=mass_storage,adb
And the USB will work without having to go to Settings
Click to expand...
Click to collapse
Thanks will update the rom later on.
gedemis said:
Put the following line in your build.prop
persist.sys.usb.config=mass_storage,adb
And the USB will work without having to go to Settings
Click to expand...
Click to collapse
It should be noted that this was recently added to the default prop in the kfire android (Hashcode's)
https://github.com/KFire-Android/device-amazon-otter/commit/3c69448cf98749305051be89fd3ea3562e19d95b
Should be the default behavior for most soon.
OP; always nice to see a stripped version, grats on the first release.
joshuabg said:
Can you post screen shots of boot animation, the rom, etc
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
the boot ani looks to be the one from the GNex smartphone
hey Hyperrunner,
Since nobody has reported any issues I assume it's a non-issue (at least with TWRP).
However, naming your ROM zip "Simple CM9.zip" with a space in the filename seems a little dangerous to me. You never know if all recoveries can handle spaces in filenames.
Huge fan of barebone type ROMs (esp. of the CM variety), so I loaded this one.
My System partition went from 244MB to 171MB. Bootup time for my KF went from 58 secs down to 35 secs.
Everything appears to be running smoothly ... not even a single hiccup to this point. Not much of a gamer, so I cannot comment on that aspect.
Was running the Vanilla CM9 ROM before this, so time and size comparisons are between that and this ROM. I also found the Vanilla CM9 to be very smooth in operation.
So far, it seems like the dev did an excellent job on this. Thanks, Hyperrunner.
twa_priv said:
hey Hyperrunner,
Since nobody has reported any issues I assume it's a non-issue (at least with TWRP).
However, naming your ROM zip "Simple CM9.zip" with a space in the filename seems a little dangerous to me. You never know if all recoveries can handle spaces in filenames.
Click to expand...
Click to collapse
Thanks for the notice will update that later on.
Also there are no problems for CWM since I tested it.
Sblood86 said:
It should be noted that this was recently added to the default prop in the kfire android (Hashcode's)
https://github.com/KFire-Android/device-amazon-otter/commit/3c69448cf98749305051be89fd3ea3562e19d95b
Should be the default behavior for most soon.
OP; always nice to see a stripped version, grats on the first release.
Click to expand...
Click to collapse
Sblood86,
Does this even work?
I might be missing something but I remember trying this with persist.adb.notify and putting it in default.prop and didn't work. I needed to have this property in build.prop to get it to work (so i ultimately put it in system.prop).
So to test I just did a full wipe and installed the latest vanilla rom.
However, in order to see the kindle as an usb drive I needed to go to Settings -> Storage and enable mass storage.
It seems it needs to be in build.prop...
twa_priv said:
Sblood86,
Does this even work?
I might be missing something but I remember trying this with persist.adb.notify and putting it in default.prop and didn't work. I needed to have this property in build.prop to get it to work (so i ultimately put it in system.prop).
So to test I just did a full wipe and installed the latest vanilla rom.
However, in order to see the kindle as an usb drive I needed to go to Settings -> Storage and enable mass storage.
It seems it needs to be in build.prop...
Click to expand...
Click to collapse
Yes. It works tested it but still need to fix a few things before a new upload. Probably tommorow.
Hyperrunner said:
Yes. It works tested it but still need to fix a few things before a new upload. Probably tommorow.
Click to expand...
Click to collapse
It works if persist.sys.usb.config is set in build.prop. But it does not work if it is just set in default.prop when building from source.
twa_priv said:
It works if persist.sys.usb.config is set in build.prop. But it does not work if it is just set in default.prop when building from source.
Click to expand...
Click to collapse
Seems like the code that gemedis posted earlier had adb enabled and kept the device from properly mounting. Got it all resolved though "persist.sys.usb.config=mass_storage" goes into the build prop.
Just wanted to say thanks to the dev....great, stable ROM, no issues so far, been browsing, played a game or two, nothing but smoooooooth riding. =D. make a RoM for the Motorola photon!!!!
sent via Tapatalk - buy it, tis amazing
processorsaurus said:
Just wanted to say thanks to the dev....great, stable ROM, no issues so far, been browsing, played a game or two, nothing but smoooooooth riding. =D. make a RoM for the Motorola photon!!!!
sent via Tapatalk - buy it, tis amazing
Click to expand...
Click to collapse
Thanks. I would make one if i had a one.
I've started a project building an AOSP ROM for wingray for my own amusement, and I thought I'd share, just in case someone wanted a nearly pure AOSP ROM with some carefully chosen tweaks.
As far as I am aware this is a fully functional ROM, but I am unable to test exhaustively so treat it as a pre-release beta, use at your own risk, blah, blah, blah.
I don't make any promises to continue development or fix bugs.
Features:
Built from pure AOSP 4.1.1 R4 (JRO03L) source with the following tweaks:
Fixed Guava compilation errors (thanks to CM10)
Added Busybox binary (thanks to ChainsDD)
Added Superuser package (thanks to ChainsDD)
Removed cellular and tethering references from wingray build (thanks to Peter Alfonso)
Disabled inclusion of AOSP recovery in the build (thanks to Peter Alfonso)
Fixed init.d support (thanks to CM10)
Working Camera
Bigger thumbnail size in recent apps menu
To do:
Horizontal recent apps menu
Reboot menu
T-Mobile Theme Chooser
More ...
Known Issues:
May encounter an issue with Superuser forgetting app permissions. Workaround: install SuperSU.
To install this ROM, I recommend wiping System, and Dalvik Cache, and performing a Factory Reset, but feel free to try it your way.
Make a Nandroid backup first!
Use standard Jellybean gapps.
http://goo.im/devs/zigackly/roms/wingray/AOSP_JRO03L
All feedback/bug reports welcome!
Well this is pretty neat, Thanks!
Glad you like it. I'm finding it quite snappy to use, even though it's not overclocked. I'll try to build in some more features as I get the time, if I can do it without losing the butteriness.
Hey thanx for your work.:good:
I wonder how this would run with a Tiamat/Eos Kernel ? Anyone tried?
Only one way to find out
Development is going a bit slowly in the last two days as I have been having trouble with corruption in my git repository.
i was just wondering if someone might ever do an aosp build for my xoom. thank you so much for your efforts, and for sharing the fruits with us!
cool deal man, i'll give this a spin and report back. so good to see others dev'ing for the Xoom! thank you thank you thank you
when looking in TB there is a system app listed with Chinese characters followed by 4.1.1-eng.zigackly.20120914.083408. What is this and can it be removed?
just like to add that first impressions go a long way and i dont normally look at the boot animation, but i did this time and it was way smoother than any other ive seen on my tablet, dont know what the diff is, but i like it
so far so good
Getting build.prop error 7 on install. Looking for Wingray in the build.prop line.
Might be a bad download? I am trying to update from CM10 and the stock update Stachre provides.
dodgefan67 said:
when looking in TB there is a system app listed with Chinese characters followed by 4.1.1-eng.zigackly.20120914.083408. What is this and can it be removed?
Click to expand...
Click to collapse
That will be the AOSP Chinese keyboard. There's a Japanese one too. Look in Settings->Language and input and you will see them as options. I believe you can safely remove them.
tincbtrar said:
Getting build.prop error 7 on install. Looking for Wingray in the build.prop line.
Might be a bad download? I am trying to update from CM10 and the stock update Stachre provides.
Click to expand...
Click to collapse
Could you try the download again? Build.prop should be replaced in system when you install, so it doesn't sound like a problem with where you are coming from.
MD5 checksum is 8cfdb670d42b5486f07f816f0e9a4791. You can check with MD5 checker from the play store.
If it's not a download problem, try a factory reset and wipe system before installing. Make sure you back up first.
In other news, I have fixed my git repositories although I had to redo all my work, but I am now working on a new build with improvements to the recents menu to take advantage of the Xoom's screen size. Hoping to implement bigger app thumbnails tonight and possibly a horizontal menu tomorrow.
The addition of a reboot menu is challenging. I made some changes based on the way Peter Alfonso does it and that didn't work, so I looked at the way CM10 do it and that didn't work either! I don't give up easily though. I'll take another stab at it this week. I'm learning this as I go along. Best way to learn, I think.
I'm also hoping to look at adding Theme Chooser this week.
Thank you for the md5, it matches, but still doesnt install.
z1gackly said:
That will be the AOSP Chinese keyboard. There's a Japanese one too. Look in Settings->Language and input and you will see them as options. I believe you can safely remove them.
Click to expand...
Click to collapse
thanks and looking forward to the updates!
may i suggest one or two? i like the options for things like setting quiet hours or profiles, being able to change toggles, etc. not sure how easy those would be to add in. i'm more than willing to help out and test things.
tincbtrar said:
Thank you for the md5, it matches, but still doesnt install.
Click to expand...
Click to collapse
what recovery are you using and are you sure you have done a complete wipe? (factory reset/wipe data, format cache, format system, wipe dalvik)?
Im using Rogue Recovery...did full wipe, dalvik, cache and system.
Perhaps its the recovery - but that doesnt make sense as every other rom ive installed worked well.
I modified the build.prop with some more operators to see if it will accept the model name or similar instead and I get a error 6 instead.
Maybe its just my Xoom? Nonetheless, ill wait for now, and stick with CM10 - its been pretty stable for me with no reboots.
tincbtrar said:
Im using Rogue Recovery...did full wipe, dalvik, cache and system.
Perhaps its the recovery - but that doesnt make sense as every other rom ive installed worked well.
I modified the build.prop with some more operators to see if it will accept the model name or similar instead and I get a error 6 instead.
Maybe its just my Xoom? Nonetheless, ill wait for now, and stick with CM10 - its been pretty stable for me with no reboots.
Click to expand...
Click to collapse
understandable. maybe try TWRP recovery just to make sure? if you have the time or are up to it?
I guess I could try TWRP, but I dont like how I always have issues with mounting sd with it...its why I stick to Rogue.
Ill give it a shot later on with TWRP to try and pinpoint the cause.
Edit: Tried TWRP and it flashed. Interesting! Thanks a bunch!
Build 7 added with larger app thumbnails in the recent apps menu. Available for download in post 2.
I'll look at what it might take to add those features, dodgefan67. I'm looking to implement the ones in my wish list in the OP first though.
I also need to get my head around merging in some improvements from the AOSP code base from after 4.1.1 r4.
The build.prop error is caused by an assert in the updater-script which checks you're installing the ROM on the correct device.
You could extract the updater-script and remove the assert, then replace the updater-script in the ROM.
It's in /META-INF/com/google/android in the zip.
I'm trying to get hold of a build.prop from a wingray which exhibits this problem, so I can correct for it in the script, but I expect yours will be fine now.
Worst case I can just remove the assert, then if someone flashes it on the wrong device it's their lookout, but I'd rather add the variant which is causing the problem to the assert.
I'm going to have to halt development on this for a time whilst I work on some stuff for my Nexus 7. I've updated build 7 so it will work with Rogue recovery. Back in a little while.
thanks for the update!
ORIGINAL CREDIT TO BALDWINGUY77 OVER ON ROOTZWIKI. CHECK OUT THE ORIGINALi: http://rootzwiki.com/topic/36706-ro...a-like-stock-android-442-kot49h/#entry1031982
I'm only port to maguro.
Is a port from original rom no have base maguro only changes for use GSM networks
This ROM is Android Kitkat 4.4.2, build KOT49H. 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.2, build KOT49H
Source (AOSP) built kernel (boot.img)
(De)Odexed
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)
Believe it or not, December is still a month!
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
Installation Instructions (VERY IMPORTANT - Note: I use recovery-clockwork-touch-6.0.4.3-maguro)
ROM
pbls said:
By the way TWRP works with this rom.
Click to expand...
Click to collapse
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 Superuser 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. Flash the ROM
OPTIONALS:
11. Root: 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.
12. Mod's: If you like any mod you can install zip now
13. Change kernel: U can change aosp stock kernel. Tiny Kernel, Fancy Kernel, Dirty V, Franco Kernel, Mpokang kernel.
14. Reboot your phone, and enjoy!
Toro XDA Thread: http://forum.xda-developers.com/showthread.php?t=2508073
CHANGELOG:
1/12/2014
First Release port on base aospa beta3
1/20/2014
Port 1:1 toro build
Fix panorama preview
2/04/2014
Fix root troubles
DOWNLOADS:
LAST VERSIÓN:
ROM 02/04/14
Mega
Link 1 Google Drive
Link 2 Google Drive
OLD VERSIONS :
ROM 1/20/14
Mega
ROM 1/12/14
Google Drive
Mega
MODS:
Universal Mod's:
AOSP BROWSER: Change Chrome for STOCK browser.
AOSP Mms.apk: Install on system aosp mesaje apk
DPS Manager: Add Cyanongen DPS Manager.
MOD's to 012014:
Return to Stock:
BACK TO STOCK Returns you to the stock version of the ROM by removing SystemUI and framework-res mods.
Return to ShinyROM Kernel: Returns to Original Shiny Kernel
Tweaks & Look:
36 DPI Nav Bar: Reduces Nav Bar to 36 dpi
Battery Percent Grey
More mod in this url: http://shinyrom.goofball.org/?dir=012014/toro/Mods/inmanster
No GApps "Add-on" Zip
Some people don't like the way ShinyROM includes its own GApps. Flash this zip directly after the ROM and it will strip out most of the included GApps so that you may use the preferred GApps of your choosing. This will leave the core GApps (Store, Services, etc.) as well any others required for basic functionality (Keyboard, Camera, Launcher, Dialer, etc.) since there are none of the AOSP counterparts included.
[ Attachment removed - new version up in Official thread ! ]
This is something what I wanted. Love stock(ish) ROMs.
Sent from my Galaxy Nexus using Tapatalk
Drive disabled here, please upload to Dropbox (direct link support) or any other mirror Thanks.
Could someone upload to XDA or Mega?
That's what we have been waiting for! Although Google left us, I wanted our device to be up to date with "stock" ROM. Thanks!
Sent from my Galaxy Nexus using Tapatalk
can someone re-upload somewhere? too many users downloaded from google drive and we're out
If you like, I will upload to my server. Gimme a short feedback.
Best regards, PlusOne.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
can i install the rom by twrp or cwm is obligatory?
I can't download becouse there are too many users trying to get it... please upload on other server
Sorry, you can not view or download this file at this time.
There are too many users who visualized or downloaded this file recently. Try again later access. If the file you are trying to access is particularly large or is being shared by many people, you may tarry up to 24 hours to view or download. If after 24 hours you still can not access the file, please contact your domain administrator.
So did anyone actually manage to download and flash this yet? I'm without Wi-Fi for a couple of days.
osm0sis said:
So did anyone actually manage to download and flash this yet? I'm without Wi-Fi for a couple of days.
Click to expand...
Click to collapse
Not so far... Tried a few minutes ago. Still nothing.
I guess those who ended download tickes flew away :laugh:
It would be great if someone could upload it to Mega.. Thanks!!
(Tried to add it to my Drive too but it keeps giving me problems...)
New link to mega in second post :good:
I liked the ROM, simple and quick. Thank you.
Fantastic job....
Inviato dal mio Nexus 5
Shiny rom,blazzing fast,going to test battery for a few days and post feedback.Thank you sir.By the way TWRP works with this rom.
Finally ROM based on stock without modifications. Will try this
Anyone tried this ROM with mpokang kernel?
@Sesme
osm0sis said:
Amazing! Been hoping someone would do this for awhile! Really looking forward to trying it out!
It mentions SystemUI and framework-res mods over stock; what are they, like completing the white KitKat look? (I hope so!)
Click to expand...
Click to collapse
SlimRoms is a custom android operating system. The main goal is to offer users a slimmed down but still feature rich alternative to other android operating systems.
The entire SlimTeam work together to bring you this tailor-made beauty straight from Android Open Source Project (AOSP) source code.
All of the sources can be publicly viewed through GitHub and you can stop by the public Gerrit to submit patches of any type.
SlimKat is the project name for SlimRoms based on Android 4.4 and offers the following original features:
The Real Dark Slim
Full system-wide dark interfaces. - If you like it smooth and classy.
Custom Shortcuts. Everywhere.
Hardware keys, Navigation Ring, Navigation Bar, Lockscreen, Tiles, Notifications etc. - We've got you covered.
System-Wide Keyboard Controls
Rotation, cursor control, optional emoticions, etc. - You'll be tapping away to your heart's content.
SlimCenter
Downloads, contact information, system app removal. - More fun than you can shake a stick at.
Camera Features
Trueview, Smart Capture. - Capture life moments with ease.
Important links:
slimroms.net - The official webpage where you will find everything you need to know about SlimRoms.
Slim Downloads - Download the ROM, GApps and other Addons.
Installation instructions - Follow these steps to the letter if you're about to install SlimRoms on your device.
Latest Changelog - Read here if you want information on changes in latest build.
FAQ - The most frequently asked questions with answers.
Kernel Source - The source of your device's kernel.
See Post #2 for Known Issues and Installation Notes.
Get in touch! - Contact SlimRoms at these places if you have questions, requests or feedback.
Google+
Twitter
Facebook
Forum
Special thanks to (in no particular order):
The Slim Team
CyanogenMod
prbassplayer
wantowan2
kintwofan
Disclaimer: SlimRoms are not responsible for any damages to your device.
I do not own the SGH-T989, but I do have 3 SGH-i727 Skyrockets, and the Hercules is almost identical. My time is limited, but due to several requests for this, I wanted to share. Please help each other out, and keep the thread friendly and informative.
Installation:
Install a 4.4 compatible recovery, and reboot to recovery afterwards.
Format /system, /data and /dalvik cache.
Flash a compatible radio (see below).
Flash the ROM.
Flash GApps.
Reboot and enjoy!
Known Issues:
Power-off charging animation not working.
You tell me...
Reporting Issues:
Do NOT report issues here if you're running a non-stock kernel, Xposed and/or modules, or any other non-stock mods.
For bug reporting (stock Slim ROM/kernel/GApps only), please use the Slim Bugreport tool, accessible through Settings > SlimCenter > Bugreport to produce a zip file in the phone's storage which you then can upload to the SlimROMs Hercules Subforum for review. Please see Reporting Bugs on the Slim web site for more information.
Any issues please explain with specific details, how to reproduce the problem, and provide a Slim Bug Report (preferred, in the ROM), or a logcat. Good feedback is ESSENTIAL.
Installation Notes:
Radios: Make sure you are running a JellyBean radio or newer (T989: UVMC6 | T989D: TLMC4), and follow the installation instructions linked to in post #1. A thread for flashable radios is here.
Recovery: Recommended recovery: CWM or TWRP.
Superuser: The Slim Team has made it so the Superuser App is not enabled by default, requiring users to intentionally turn on Root access. To enable it, navigate to Settings > Developer Options > Root Access and choose Apps and ADB (even though it may appear selected). For this to work, you need to first go to Settings > About Phone and tap on Build Number several times to gain access to the Developer Options.
Also see here: http://slimroms.net/faq/slimbean/441-how-do-i-enable-root
Kernel: The kernel is based on the Moretz CM-11.0 kernel, but overclocking has been disabled to enhance stability. For sweep2wake, fast charge, and CPU freq/governor control features, I'd recommend [ROOT] Kernel Tweaker from the Play store.
Wi-Fi: Wi-Fi connection dropping issues? Check your region code in Settings > Wi-Fi > (menu key) > Advanced > Wi-Fi region code. It may be set to Europe by default, which uses a different set of Wi-Fi channels than the United States or Canada.
DPI: For information on changing the screen DPI, see here: How to change the screen density (DPI). Beware that some apps may not play nice with custom values, although normally the Slim GApps are modified to tell the Play Store and a couple of other apps that the phone's DPI is always 240.
Enjoy!
(reserved)
Initial test build: http://www.androidfilehost.com/?fid=23578570567714111
Welcome to the Hercules forum and thanks for bringing this ROM back to us. I will be testing this later this evening after work. Also I will get the word out on G+.
big fan of slim cant wait to see what this brings
Initial Impressions
OK after a few hours of testing, here is what I found:
First of all, the instruction to not change the governor on the stock kernel apparently applies to Wild! V6 as well. After installation, boot was just fine. Thinking I could change the governor because this was a custom kernel, I changed the governor to Intellidemand. No problem then either, but after a reboot the phone boot looped. Re-installing the kernel fixed that, but then it happened again. Also the wi-fi setting was not saving my password either. So after getting the phone to boot up (had to install the kernel once more), I set the governor to Interactive. No more boot loops after three reboots. So that was taken care of.
The other issues I encountered were extremely slow charging (only 1% charge in about a 45 minute time frame) and Google Now FCd every time I tried to open it (even after I wiped data & cache). Upon those problems I had to restore my nandroid for now. I do also want to mention some positives. The ROM really does fly, and with Slim mini gapps over 200mb of free ROM space is available so the ROM lives up to its name of "less is more". Video recording was perfect and without any delay. I have been out of the loop for a bit on changelogs, but for those who don't know the new theme engine is still not included in this ROM as of yet. The real dark Slim does work though.
Bottom line this is not yet ready for a DD IMHO, but with tweaking, could be the fastest ROM we have available. I really was almost willing to deal with the bugs because I was so impressed with the speed. The screen wake lag that plagues all the other ROMs did not happen for me here. Thanks again @NoSpamDan, I'll be happy to try future builds as well.
ArtfulDodger said:
OK after a few hours of testing, here is what I found:
First of all, the instruction to not change the governor on the stock kernel apparently applies to Wild! V6 as well. After installation, boot was just fine. Thinking I could change the governor because this was a custom kernel, I changed the governor to Intellidemand. No problem then either, but after a reboot the phone boot looped. Re-installing the kernel fixed that, but then it happened again. Also the wi-fi setting was not saving my password either. So after getting the phone to boot up (had to install the kernel once more), I set the governor to Interactive. No more boot loops after three reboots. So that was taken care of.
The other issues I encountered were extremely slow charging (only 1% charge in about a 45 minute time frame) and Google Now FCd every time I tried to open it (even after I wiped data & cache). Upon those problems I had to restore my nandroid for now. I do also want to mention some positives. The ROM really does fly, and with Slim mini gapps over 200mb of free ROM space is available so the ROM lives up to its name of "less is more". Video recording was perfect and without any delay. I have been out of the loop for a bit on changelogs, but for those who don't know the new theme engine is still not included in this ROM as of yet. The real dark Slim does work though.
Bottom line this is not yet ready for a DD IMHO, but with tweaking, could be the fastest ROM we have available. I really was almost willing to deal with the bugs because I was so impressed with the speed. The screen wake lag that plagues all the other ROMs did not happen for me here. Thanks again @NoSpamDan, I'll be happy to try future builds as well.
Click to expand...
Click to collapse
Thanks, I appreciate the testing and feedback!
Let me first say that details are everything, especially when I don't have a test phone available...
I am looking for bugs that exist in the as-built ROM, and therefore I am unable to provide any support for 3rd party kernels... This could have caused most of the issues you experienced.
Was there a problem with the stock CM-11.0 kernel bundled into the ROM, aside from the known governor switching issue? If so, the built-in Slim Bug Report tool (Settings > SlimCenter > Bugreport) will produce a zip file you can upload here for the time being for review. Please see Reporting Bugs on the Slim web site for more information.
For random reboots (RR's), you can also try using Bootlog Uptime to automatically dump /proc/last_kmsg for you to review/upload.
The Google Now issue shouldn't have anything to do with the ROM itself, that is in GApps. And if you were using the mini-gapps package, did you install Google Search separately? According to the TRDS GApps thread, it's not included in the mini package, and you could have been missing some key library files from the GApps package.
What version of KK4.4 GApps did you install? You said mini, but was it v155, v157, v160?
For now, I would recommend using the beta GApps with Unofficial builds until an Official ROM version is released. Please bear in mind that @dankoman has been producing new beta TRDS GApps versions quite often. His discussion thread is here.
What I really need are bug reports and logs using only the stock Slim ROM/kernel/GApps... Unfortunately, without these, I won't be able to provide effective support to try and make this ROM better, much less try to get the Hercules officially supported on the Slim site.
Thanks again!
NoSpamDan said:
Thanks, I appreciate the testing and feedback!
Let me first say that details are everything, especially when I don't have a test phone available...
I am looking for bugs that exist in the as-built ROM, and therefore I am unable to provide any support for 3rd party kernels... This could have caused most of the issues you experienced.
Was there a problem with the stock CM-11.0 kernel bundled into the ROM, aside from the known governor switching issue? If so, the built-in Slim Bug Report tool (Settings > SlimCenter > Bugreport) will produce a zip file you can upload here for the time being for review. Please see Reporting Bugs on the Slim web site for more information.
For random reboots (RR's), you can also try using Bootlog Uptime to automatically dump /proc/last_kmsg for you to review/upload.
The Google Now issue shouldn't have anything to do with the ROM itself, that is in GApps. And if you were using the mini-gapps package, did you install Google Search separately? According to the TRDS GApps thread, it's not included in the mini package, and you could have been missing some key library files from the GApps package.
What version of KK4.4 GApps did you install? You said mini, but was it v155, v157, v160?
For now, I would recommend using the beta GApps with Unofficial builds until an Official ROM version is released. Please bear in mind that @dankoman has been producing new beta TRDS GApps versions quite often. His discussion thread is here.
What I really need are bug reports and logs using only the stock Slim ROM/kernel/GApps... Unfortunately, without these, I won't be able to provide effective support to try and make this ROM better, much less try to get the Hercules officially supported on the Slim site.
Thanks again!
Click to expand...
Click to collapse
Yeah I was afraid you might bring the logs up, and rightfully so. Reason that I did not use the built in kernel is that I have NEVER had good experiences with stock kernels from CM. Plus with the limited governor availability, I was hoping Wild! would eliminate that problem. I was also unaware of Bootlog Uptime or I would have used it to help with this situation.
On Gapps, I used these from the Slim ROMs web site: http://slimroms.net/index.php/downloads/dlsearch/viewdownload/1150-addons4-4/12060-slim-mini-gapps-4-4-4-build-6-112
Google Now wasn't included so I restored it via Titanium Backup. After the FCs, I wiped the data. Still no luck. I tried to uninstall it but when I checked settings/apps, it was still showing as installed. I should have just fresh installed it from Play or better yet, used the Banks Gapps I already had. At any rate, I know I could have fixed that problem if I had tried other things.
Any idea what might have caused the slow charging? I've had that happen on official CM as well.
ArtfulDodger said:
On Gapps, I used these from the Slim ROMs web site: http://slimroms.net/index.php/downloads/dlsearch/viewdownload/1150-addons4-4/12060-slim-mini-gapps-4-4-4-build-6-112
Google Now wasn't included so I restored it via Titanium Backup.
Click to expand...
Click to collapse
Yeah, those GApps are pretty outdated, but should still work. TiBu on the other hand, can be pure evil sometimes...
After the FCs, I wiped the data. Still no luck. I tried to uninstall it but when I checked settings/apps, it was still showing as installed. I should have just fresh installed it from Play or better yet, used the Banks Gapps I already had. At any rate, I know I could have fixed that problem if I had tried other things.
Click to expand...
Click to collapse
OK. Now (Quicksearchbox.apk) is a System App, so yeah, I can see trouble with it if restored.
Any idea what might have caused the slow charging? I've had that happen on official CM as well.
Click to expand...
Click to collapse
Not off-hand. I take it you've tried different chargers/cables...? There's an app on XDA here called Skyrocket Charger Test that, while it's labeled 'Skyrocket', based on what it queries for information, might work on the Herc to check the charging rate and type. I believe it also works on the Note 1 SGH-i717... Worth a shot to test chargers and cables for issues. It's saved me many times.
NoSpamDan said:
Yeah, those GApps are pretty outdated, but should still work. TiBu on the other hand, can be pure evil sometimes...
OK. Now (Quicksearchbox.apk) is a System App, so yeah, I can see trouble with it if restored.
Not off-hand. I take it you've tried different chargers/cables...? There's an app on XDA here called Skyrocket Charger Test that, while it's labeled 'Skyrocket', based on what it queries for information, might work on the Herc to check the charging rate and type. I believe it also works on the Note 1 SGH-i717... Worth a shot to test chargers and cables for issues. It's saved me many times.
Click to expand...
Click to collapse
Well thing is, on other ROMs like PA or Beanstalk 4.4 builds I get about 40% an hour charge. I use two different chargers at home & work, both Samsung with no issues. The slow charging issue is one I've only encountered with official CM (especially 4.4 nightlies), an old Beanstalk 4.3 ROM and unofficial Carbon 4.2 build back from last fall.
On TB it really is both a blessing and a curse sometimes!
Only issue is found is SD card usage. I don't have external SD card btw
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
smokenbiskits said:
Only issue is found is SD card usage. I don't have external SD card btw
View attachment 2858649
Click to expand...
Click to collapse
Thanks for the report.
I take it you did wipe /data or perform a factory reset upon installation? This will not wipe your internal SD card (music/photos/etc)...
Sometimes just a dalvik and cache wipe from recovery fixes this. A log/bugreport might help. Did you try clicking on that SDCard entry to see what app or process it says is running? Do you have Outlook installed or Exchange mail configured?
And I couldn't help but notice, are you running Juice Defender? FYI many have reported worse battery life on KitKat with that... I purchased the full version myself back when I switched from GB to ICS, but ended up ditching it when JB came along, and never looked back.
Everyone's usage/situation is different...
NoSpamDan said:
Thanks for the report.
I take it you did wipe /data or perform a factory reset upon installation? This will not wipe your internal SD card (music/photos/etc)...
Sometimes just a dalvik and cache wipe from recovery fixes this. A log/bugreport might help. Did you try clicking on that SDCard entry to see what app or process it says is running? Do you have Outlook installed or Exchange mail configured?
And I couldn't help but notice, are you running Juice Defender? FYI many have reported worse battery life on KitKat with that... I purchased the full version myself back when I switched from GB to ICS, but ended up ditching it when JB came along, and never looked back.
Everyone's usage/situation is different...
Click to expand...
Click to collapse
Yes to wipe everything except internal SD.
I will try a dalvik/cache wipe/battery stats and see if it helps.
Don't have either of those email clients installed.
Clicking on SD card entry in battery just shows cpu uptime for SD Card, not specific process.
I'll remove juice defender after the wipes above work/don't work, don't want too many variables changing while trying to troubleshoot. :angel:
LOL, yes, one step at a time is good. else you can end up with no clue at all
Oh, I just saw "battery stats"... and wiping those has no effect in Android 4.4. Google debunked that some time ago. See here. Recharging the device will reset the battery usage stats in Settings > Battery.
I used to wipe the battery stats myself, and I honestly didn't know there were still recoveries that still had that built in (TWRP maybe) since I've been on PhilZ Touch CWM recovery myself for a long time. No Fix Permissions either, wouldn't you know (not a bad thing, actually)...
I sure did like my placebo effect, though. I still miss it, lol.
The Dalvik/cache wipe fixed SD card issue... Thanks
First, thanks for helping us all out and working on bringing us this ROM. Tried it out today and was impressed by how fast it booted and its responsiveness. Flashed through TWRP 2.7.1.0 along with newest beta slim mini gapps. Full wipe/clean install. A few things I noticed:
1) Native superuser doesn't function. Tried going into settings>advanced options>superuser and auto-allowing apps permissions...no go. Unable to create logcat/bugreport for this issue as they both require root. Fixed by flashing Chainfires SuperSU zip through TWRP
2) Battery charge speed seemed normal here
3) I live in US and wifi region code was set to Europe after install.
4) In your OP you mention radios not related to our model. The newest radio for T989 is T989UVMC6
5) Something not specific to your ROM, but with all recent ROMs (CM related?) stock messaging app no longer turns data on to send/receive MMS messages. Again, nothing on your end, just felt the need to bring attention to it.
Thanks again for your work
ive been on this all day today without any problems! slims as good it was before
HipHopAnonymous3 said:
First, thanks for helping us all out and working on bringing us this ROM. Tried it out today and was impressed by how fast it booted and its responsiveness. Flashed through TWRP 2.7.1.0 along with newest beta slim mini gapps. Full wipe/clean install. A few things I noticed:
1) Native superuser doesn't function. Tried going into settings>advanced options>superuser and auto-allowing apps permissions...no go. Unable to create logcat/bugreport for this issue as they both require root. Fixed by flashing Chainfires SuperSU zip through TWRP
2) Battery charge speed seemed normal here
3) I live in US and wifi region code was set to Europe after install.
4) In your OP you mention radios not related to our model. The newest radio for T989 is T989UVMC6
5) Something not specific to your ROM, but with all recent ROMs (CM related?) stock messaging app no longer turns data on to send/receive MMS messages. Again, nothing on your end, just felt the need to bring attention to it.
Thanks again for your work
Click to expand...
Click to collapse
Thank you much for the feedback.
1) You have to enable Superuser through Developer options. See installation notes in post #2, with a link to Slim's FAQ on it.
2) Good!
3) I've seen this before, and will look into it, although as you said, if you drill into the Wifi > Advanced > Region code settings, you can change it to whatever. So, low priority.
4) I'll look at the assert script for the radio version. Can you link the radio thread please?
5) I haven't heard of this. I don't believe it affects the Skyrocket...? Does this happen on the recommended radios?
I have a new build compiling with a "stock-ish" version of the Moretz kernel (no over clock/undervolting).
It has sweep2wake, fast charge, more governors, and reportedly better Bluetooth support (with SR users).
I'll post it for testing when it's ready for those interested...
I don't have any volunteers for testing (yet). . If you want to volunteer, you should be able and willing to clean flash at times 3-4 builds in a day, be able to capture logs and send them. Normal testing would be occasional builds, unless there was a major issue.
Looking for 3 or so testers to help possibly get this into the Slim weekly cycle.
Cheers!
The Unlegacy Android ProjectIntroduction
Unlegacy-Android started out as the OMAP4-AOSP Project. It was created in late 2015 in order to maintain a clean and organized place for pure AOSP support for various OMAP4 devices, such as the Galaxy Nexus and the Samsung Galaxy Tab 2 series. Over time this evolved to support more than just these devices, but still maintains its roots of supporting "legacy" devices that no longer receive "official" updates: hence Unlegacy Android was born. In our opinion, these ROMs are how the official updates would look.
On top of AOSP, we only include changes which are necessary to support the hardware, be secure, and get acceptable performance. Current features for hammerhead include:
BFQ IO scheduler (official kernel 3.4 release), set up so GUI processes have the highest priority
Volume button wakeup (setprop persist.wm.volume_wake_screen 1)
Last upstream (kernel/msm) hammerhead kernel tag merged
Charging LED control (setprop persist.sys.led_on_charger 0)
Enhanced backlight map for lower min brightness
Night display blue light filter (GLES-based)
KCAL & PCC color temperature interfaces
Other security patches & minor bug fixes
F2FS support from K4.4 backports
SELinux in Enforcing mode
Installation
It's important that /system needs to be unmounted before installing the ROM - some recoveries tend to leave it mounted after performing operations on it.
If you're planning to install GApps, be sure to read the second post.
Aside from these, installation and upgrading is no different than on other ROMs.
Problems
No known issues on Nougat builds
See post #3 for Oreo/Pie notes
If you notice anything, be sure to report it in this thread. Stability is our main concern. While it may takes some time, I usually read the thread and acknowledge the bug reports, even if I don't reply directly to them.
Downloads
See: http://builds.unlegacy-android.org. Our automated builds ensure that we always have the latest Android security patches merged in, without having to manually start and upload builds
Also, we'll have a built-in OTA updater (just like stock) soon (it's a work in progress).
Features?
There isn't much to say here - this is AOSP, if you install GApps, you pretty much get the same thing that's running on the Nexus devices (see second post). The aim of this project is to create a fast and stable ROM, as close to AOSP as possible without diminishing usability. Occasionally, small non-AOSP features may be implemented, provided there is a clear need and they make sense on hammerhead.
XDA:DevDB Information
Unlegacy Android Project, ROM for the Google Nexus 5
Contributors
amaces, Ziyan
Source Code: https://github.com/Unlegacy-Android
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 7.1.2
Stable Release Date: 2017-04-18
Current Beta Version: 9.0.0
Beta Release Date: 2017-10-02
Created 2017-04-21
Last Updated 2018-10-30
GApps
If you want to install GApps, we recommend micro packages on N builds (e.g., Open GApps), and pico otherwise.
An important note: as this is a pure AOSP ROM, installing GApps tends to be problematic: in order to try to avoid installation issues, be sure to install GApps immediately after installing the ROM, before booting the system for the first time. If you experience any issues with the Google applications, be sure to go into Settings -> Apps, and grant every permission to every Google application - most importantly, Google Play services.
In the case of an upgrade, be sure to re-install the GApps package, as upgrading wipes /system. You shouldn't need to re-set the permissions afterwards.
Stock-like setup
Disable the following built-in (AOSP) apps:
- Android keyboard (once you installed Gboard)
- Browser
- Calculator
- Camera
- Clock
- Email
- Gallery
Install the following apps from the Play store:
- Google Photos (https://play.google.com/store/apps/details?id=com.google.android.apps.photos)
- Calculator (https://play.google.com/store/apps/details?id=com.google.android.calculator)
- Chrome (https://play.google.com/store/apps/details?id=com.android.chrome)
- Clock (https://play.google.com/store/apps/details?id=com.google.android.deskclock)
- Gboard (https://play.google.com/store/apps/details?id=com.google.android.inputmethod.latin)
- Gmail (https://play.google.com/store/apps/details?id=com.google.android.gm)
- Google Calendar (https://play.google.com/store/apps/details?id=com.google.android.calendar)
- Google Camera (https://play.google.com/store/apps/details?id=com.google.android.GoogleCamera)
- Google Now Launcher (https://play.google.com/store/apps/details?id=com.google.android.launcher)
Rooting
You can flash the latest SuperUser (phh's open source fork), Chainfire's SuperSU, or Magisk to get rooted.
Oreo/Pie Status & CAF Notes
Oreo 8.1 builds are almost bug-free at this point, but still tagged as experimental. While last issues are sorted out, I will trigger manual builds, also published at https://builds.unlegacy-android.org/aosp-8.1/hammerhead.
To my knowledge, these are the remaining issues:
Bluetooth HFP speaker (mono/SCO) output is garbled. This seems related to a more general issue with audio effect/ACDB blobs.
Once all visible issues are fixed, and stability is comparable to Nougat builds, I'll switch on official builds on our Jenkins server.
Pie 9.0 builds are also becoming fully usable. Current builds have the same one remaining HFP bug described above.
Beyond "official" experimental builds, I post personal builds (including CAF experiments) in the hammerhead folder here.
Regarding sources for the WIP CAF kernel-based builds, see https://github.com/airend/android_kernel_lge_hammerhead/commits/tmp/caf+113+common. Corresponding device tree is still in rough shape and not uploaded yet, but assuming everything goes well, it'll replace current device tree when it's ready.
I've used the 05/04 build for 2 days a few weeks ago and it was a great rom.
The only issue I came across back then was that it has the green flickering when recording videos.
It's nice that the project has a XDA thread now and I gonna test this rom asap.
Thanks for keeping our good old Nexus 5 up to date.
Nexive said:
The only issue I came across back then was that it has the green flickering when recording videos.
Click to expand...
Click to collapse
Should be fixed on current builds (both green bar, and Google Camera flickering).
have a volume wake option?
Does it have issues with network location (Battery saver location)?
Some AOSP-based ROMs have this issue, so many apps (Chronus, Google Fit, f.lux, Instagram) can't get location.
alessio89g said:
Does it have issues with network location (Battery saver location)?
Some AOSP-based ROMs have this issue, so many apps (Chronus, Google Fit, f.lux, Instagram) can't get location.
Click to expand...
Click to collapse
No, all UA ROMs have this issue fixed
Ziyan said:
No, all UA ROMs have this issue fixed
Click to expand...
Click to collapse
Great, I think I'll try this ROM tomorrow!
--- --- ---
EDIT:
Is there any kind of changelog?
--- --- ---
RE-EDIT:
Okay, I found this:
https://gerrit.unlegacy-android.org
Hi....
Any screen shot?
keretapanau said:
Any screen shot?
Click to expand...
Click to collapse
Umm… it's barebones AOSP?
Buttery smooth,everything seems to be working fine here..Awesome jobs dev..keep it up.Finally this is the rom i been waiting for.:good:
CreateYourDream said:
have a volume wake option?
Click to expand...
Click to collapse
It is not an AOSP feature. It is something custom roms introduced.
Android-Andi said:
It is not an AOSP feature. It is something custom roms introduced.
Click to expand...
Click to collapse
thanks for answer, but i have broken power button :crying:
Cant Install Gapps
I've flashed it for about half a day, and it's very promising, it seems a great ROM!
I've noticed only three defects:
- The blue light filter (Night mode) is missing;
- With stock kernel, SuperSU will be in system mode;
- The Clock app crashes if you try to add another Time zone in the main screen.
Everything else works fine.
CreateYourDream said:
thanks for answer, but i have broken power button :crying:
Click to expand...
Click to collapse
Did you try this
Check out "Custom Navigation Bar"
https://play.google.com/store/apps/details?id=xyz.paphonb.systemuituner
Thanks for the ROM guys!
When I flash Open Gapps this message appears:
"This Gapps pkg is for Android 7.1.x ONLY
Please download the correct version for you ROM: 5.1.1 (SDK 22)"
I've flashed build ua_hammerhead-7.1.2-20170423031839 before gapps
Is there any alternative app for kcal..?KCAL app seems to be force closing once installed.
substratum support please