{
"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"
}
What is this?
This is the AOKP-android open kang project compiled for the TF201. I have tested this and this flashes with no problem. This rom has waaaaaaaay more features then CM9. Like seriously... it has a option in Settings called Rom Control. You can read about it here: http://forum.aokp.co/
Disclaimer
I or PG are not responsible for what happens to your beautiful prime. So, please act with caution. I am 100% sure this works as I have tested it, however.... if if you dont know how to use adb, i suggest you stop reading right now and learn that first.
BEFORE YOU FLASH PLEASE READ
This rom has been shared for educational and entertainment purposes. Please dont flame, dont complain and please dont wine if you find something that doesn't work, this is why this is Work in Progress. Hopefully, it'll work 100% 1 day, and we of course have no ETA. So please do not ask. Maybe another dev can take a crack at it?
Who made this build? Compiled it?
This build was compiled by PlayfulGod. Please donate to him here: http://bit.ly/yeOD3T. Original work by AOKP. This is just a port for the tf201 and nothing more. Credit to AOKP. I have been given permission by PG to release it to the public. This rom comes with no support. However, you can stop by #asus-transformer on freenode and If i am around... I will gladly help. As the TF201 has been unlocked, i figured it would be beneficial to all android enthusiast to have more than 1 option for roms. That is why we are making this build available. Test it out and tell me what you think. Please expect bugs as this is a WIP. I will post screenshots soon.
What is not working?
Screen Rotation is only in portrait mode (Looking into Orientation Switch on market)
Not all options in the Rom Control work
LED Options
Reboots when pressing the Power Button to sleep the TFP
Screen won't turn off while closing the dock/tablet
MicroSD (Looks like there is a solution for CM9, will look into it)
I have noticed on a few occasions as some of these options are not working with the TF201, it will do a fastboot. So, please do not complain.
Instructions
Install like any other rom, however MAKE SURE you unmount SYSTEM and unmount STAGING.
1. Make sure you're on the latest CWM
2. MAKE A NANDROID
3. unmount system & staging
3. wipe data/factory reset in recovery
4. flash ROM
5. flash Gapps (if you want)
6. reboot
Remember, to make a backup of your current rom. Also make a backup of your boot.img, so if you do decide to go back to your rom you can flash the boot.img and you'll be back to normal.
How to backup your Boot.img? You can use ADB or Terminal Emulator
1. su (to make sure you have #)(if your in adb.... adb shell)
2. dd if=/dev/block/mmcblk0 of=/sdcard/boot.img bs=4096 skip=3968 count=2048
Wanna restore to what you had?? Heres how to do it right....
So you saw it, you like it, you can't wait till it completely works, but you wanna go back to what you had for now....
1. Make sure you have your boot.img backed up from the rom your going to restore.
2. Go to CWM and do the Restore
3. Once thats done, go to ADB and flash Boot img
4. adb shell & su (make sure you have #)
5. dd if=/sdcard/boot.img of=/dev/block/mmcblk0 seek=3968 bs=4096 count=2048
6. Exit & Reboot
Now you should be back exactly where you are now be4 you flash AOKP.
Download
AOKP for TF201 - Build 26 - http://goo.gl/2LOiO
Gapps - http://goo-inside.me/gapps/gapps-ics-20120224-signed.zip
Awesome, thanks! Been waiting for this!
One thing: where's the Gapps download?
EDIT: Seems to reboot when you press the power button.
redbullcat said:
Awesome, thanks! Been waiting for this!
One thing: where's the Gapps download?
EDIT: Seems to reboot when you press the power button.
Click to expand...
Click to collapse
gapps-ics-20120224-signed.zip
MasterZen88 said:
gapps-ics-20120224-signed.zip
Click to expand...
Click to collapse
Yeah, I found them literally after I said that. Thanks
Yeah baby more roms! Thank you for this, you beat jermain to the punch with aokp but the more the merrier
-EVO-
Woooo! Can't wait to install this thank you!
Yea, i had noticed that also. I completely forgot to mention it. It was 3 am when i posted this last night.
Updated post.
too many choices, need some help
Is there some high-level comparison of AOKP vs. CM9 vs. Asus stock?
What is Kang and what is its relationship with Cyanogenmod? I've seen CM kernels that have kang in the name, but then also AOKP as a separate rom.
What specific features make Kang compelling for tablets? I've explored the Kang website a bit, but there's nothing that gives an overview of the purpose/goals of the project.
ragesoss said:
Is there some high-level comparison of AOKP vs. CM9 vs. Asus stock?
What is Kang and what is its relationship with Cyanogenmod? I've seen CM kernels that have kang in the name, but then also AOKP as a separate rom.
What specific features make Kang compelling for tablets? I've explored the Kang website a bit, but there's nothing that gives an overview of the purpose/goals of the project.
Click to expand...
Click to collapse
Kang is not the name of the rom, kang means built from someone elses code Eg, if someone takes the cm kernel source builds a kernel from it and releases it you could call that a kang.
The name of this rom is more of a joke I believe as it is "kanged" from source
sent from my Transformer Prime
No NTFS support ?
Hi, Firstly thanks for sharing the ROM. Installed over the Virtuous ROM (.15 v2) to play with and all installed ok, apps restored via TB, etc. but have found that my 32gb microsd card shows up as a Blank SD Card when inserted (I had to create the Removable subfolders first, as per http://forum.xda-developers.com/showpost.php?p=23006383&postcount=2), this read fine before on the stock roms and also on Virtuous. So guessing that the kernel used on this rom doesn't support NTFS ?
Any plans to get NTFS support included as 90% + of the HD films I have are way over 4gb
A feature list for the OP would be nice.
I believe it has the same features as listed on this lsit: https://sites.google.com/site/androidopenkangproject/feature-lsit?
YES!!! AKOP on my prime!! This rocks thank you!
cant wait to flash it!!! thx buddy!
For those that are unaware, AOKP is AWESOME!
I don't think I will flash this until some of those bugs are cleared up, but as soon as those are fixed I am in.
I have not used CM9 yet, but AOKP on my Galaxy Nexus is more stable than any CM7 ROM I ever tried. Its packed with features and the devs are always adding new stuff.
marko! said:
Kang is not the name of the rom, kang means built without permission or stolen work. Eg, if someone takes the cm kernel source builds a kernel from it and releases it you could call that a kang.
The name of this rom is more of a joke I believe
sent from my Transformer Prime
Click to expand...
Click to collapse
I must correct you, Kang is an official denomination of self compiled CM from sources. The Kang ROMs are not stolen !!
CM are built by a buildbot automatically every day or nearly, everyone can build a Kang from sources (remember it's open source) and when you do that the build script automatically add 'Kang' to the name of the ROM as it appear is Settings> About Device menu.
Thus you can easily make the difference between ROM compiled by Cyanogen buildbot and ROM compiled by dev. Usually Kangs are a way to pick only interesting commits for the specific device (called cherry picks) or even removing some commits that are eventually causing bugs.
For example on my optimus 2X phone, CM9 is not officially released, but the CyanogenMod dev in charge of maintaining CM tree for our phone made a Kang to enable us to test it (he named it SelfKang with humour ...)
Don't write such things it could lead to misinterpretations...
Hell yeah. Thought I was in the inc2 forums for a second. This is the best ics rom I've ever used (at least for mobile). Can't wait to give it a run on the tfp
Sent from my Incredible 2 using XDA App
"Orientation Switch" from the Market helps with the orientation issue.
Other issue: the screen won't turn off while closing the dock/tablet.
Nice AOKP on my Desire HD and now my prime. This is great news. For everyone who doesnt know, there are a lot of customizations with rom control. Once the few bugs are worked out, its golden.
Sent from my HTC Desire HD using Tapatalk
Thank you sooooo much! The C9 ROM was KILLING ME! Bug city. After flashing it, I couldn't get wi/fi on any of the other ROM's i was using. So far this looks great. I'm hoping the landscape fix is coming soon.
hobbypunk said:
"Orientation Switch" from the Market helps with the orientation issue.
Other issue: the screen won't turn off while closing the dock/tablet.
Click to expand...
Click to collapse
From what I've learned the kernel is usually the issue with orientation. I have a Skyrocket and of I use a kernel from the Hercules (TMobile version) the orientation is opposite. Sometimes in settings you can torn off specific degrees of orientations.
Thanks for the tip about the app BTW.
Sent from my SAMSUNG-SGH-I727 using xda premium
Related
eyeballer and I are pleased to announce that
{
"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"
}
ParanoidAndroid 3.60for the Nook Color is now available!
ParanoidAndroid 3.15 is a AOSP based rom that allows users to enjoy tablet or phone UI, or hybrid.
Most apps have several different UI's for various layouts, choose which interface you prefer.
Paranoid Android sources are out and building a ROM has never been easier. See the third post for instructions!
AOSPA Features include
Control the UI of individual apps as well as your entire tablet
Small. mid and large tabletUI layout.
Customization of toolbars, lockscreen and more/
Netflix. Update: Now working with latest apk from Play Store, but you need this hack.
Color-splash for nav-bar and apps
Expanded Desktop w/ PIE controls
I especially would like you to take a second and appreciate the Cyanogen team, especially our home team of fat-tire, nemith, keyodi, eyeballer, krylon360 and steven676.
I would recommend you never pass up an opportunity to thank those guys for their efforts
.
From one of the PA creators, molesarecoming...
To be honest, this is not tablet mode at all, it has nothing to do with silly build.prop hacks.
This is the first and only Android rom to feature true Hybrid mode.
This rom lets you scale and project every app, every widget, even systemcomponents individually.
Remember, android is modular, everything is an app: Lockscreen, navigationbar, dialogs, popups, keyboards, widgets, and your regular apps of course.
Apps have the capability to switch into various designs or layouts according to the device they run on.
This can result in a complete new experience as many apps will transform to the better.
Now for every element that you like chose a mode (PhoneUI, Phablet/Nexus-7UI, TabletUI) and/or a size.
You are 100% independent of the system DPI which runs nicely in whatever value it has been assigned to.
You do not need to boot your phone into a certain DPI. Neither will most of the changes you apply require a reboot.
You will not suffer from the myriads of troubles which normally haunt you under build.prop tablet mode.
Your market, phone, etc. will all work, apps won't shrink on you unless you shrink them yourself.
This project will entirely transform your device, but retain the aesthetics and the feel of your phone.
Click to expand...
Click to collapse
Here are some screenshots of the ROM for the Nook Color
In the settings, you will see a new pane for Hybrid Settings.
Here you can adjust the default GUI and DPI for all system or user apps, or even each app individually. There is a picture walk-through at the top of the third post.
Download
Updates will also be available through Goo Manager via browse compatible roms -> mateor -> paranoidAndroid
No special GAPPS necessary; just use the latest you can find!
If you are going to run this from an sdcard, see Leapinlar's sdcard-install guide
New! Download Page
PA is using NookieDev's 3.x kernel and device tree, among other projects.
3.15 Issue List
When in extended desktop or 0% navbar, touch events where the nav bar was are touchy, at best. This will continue to be worked on. (Here was one attempt)
You can only reboot into recovery through Cyanoboot!
Boot animation is in landscape
You will have to reflash GAPPS each update (known upstream issue)
Governor/Scheduler selection in Settings does not stick (Works in 3rd party apps like TricksterMod)
Some ALSA -related noise in logcat I plan on investigating.
You tell me!
Contributions to any aspect of the project are welcome, see the involved projects here.
Thanks are due to:
molesarecoming, aaronpoweruser, D4rKn3sSys and the ParanoidAndroid Team
The CM Team, including our own fattire, keyodi, dalingrin, eyeballer, Krylon360, sluo (yeah, that's right, we thanked ourselves. What about it?)
steven676 deserves a special mention for maintaining our device and kernel. This update in particular owes him a large debt.
kevank, snipa, and the rest of TeamWin for hosting and general good will (yeah, twice) (Wanna make something of it?)
tonyp for general PA expertise
inportb for GP.
RedneckReg for the replacement device and Leapinlar for all he does for the Nook community.
Click to expand...
Click to collapse
Great work by mateorod on this!
Building from source is a ton better than the older builds where we had to patch frameworks from other devices.
Please post any feedback and/or preferred settings that you find or use for certain apps so we can improve the default experience.
Here is a walk-through of how to interact with Paranoid Settings (found in the device settings menu)
Click to expand...
Click to collapse
You will notice some of the above user-interfaces are not yet available on this rom. Every device is configured differently.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Easiest build instructions on XDA!
These instructions are for 64 bit Linux environments, try VirtualBox if you don't use Linux normally.
Take 15 minutes and follow the beginning of this guide. if you don't have ADB set-up, it will take longer, but that is just for downloading the SDK.
If you need help installing the JDK (the hardest part, honest) do this (this is the absolute easiest way)
Code:
cd ~/
wget https://github.com/flexiondotorg/oab-java6/raw/0.2.7/oab-java.sh -O oab-java.sh
chmod +x oab-java.sh
sudo ./oab-java.sh
sudo apt-get install sun-java6-jdk
When it gets to the step to intialize the repo (repo init -u ETC.) STOP, and come back here, You are done with that guide, forever. Those steps only need to be done once.
Enter:
Code:
[FONT="Courier New"]repo init -u git://github.com/mateor/android.git -b pa-4.2[/FONT]
[FONT="Courier New"]repo sync[/FONT]
If you experience fetch errors during the repo sync, change the command to repo sync -j4 -f. If they still occur, then repo sync -j1 -f.
This will take a long time, do it before bed, or family time, or go eat.
When the sync is done
Code:
. build/envsetup.sh
lunch pa_encore-userdebug
make bacon
You're done! I used to have a build script here, but that is not currently working, ParanoidAndroid preferences FCs with the build script.
When it is done compiling, your ROM will be waiting for you at ~/android/system/pa/out/target/product/encore.
Fat-tire says this makes you an Android ninja, so you know it must be true. That means that if you don't try, you are admitting you don't want to be a ninja. Which reveals you to be the geek you already are but with loser rubbed all over you. Why else are you on XDA if not to learn?
I have used Paranoid on my GNex. It is a great ROM! I was hoping someone might port it to the Nook Color.
If you need any testing or help I would be willing.
:good:
I am going to for sure try this later today after I am done taking the kids to their stuff!
Just picked an extra sdcard to try this on. Cant wait.
what doesnt work on this rom? ie netflix youtube hd etc.
darrylking06 said:
what doesnt work on this rom? ie netflix youtube hd etc.
Click to expand...
Click to collapse
Probably everything that doesn't work in the regular CM9 rom.
darrylking06 said:
what doesnt work on this rom? ie netflix youtube hd etc.
Click to expand...
Click to collapse
Nburnes said:
Probably everything that doesn't work in the regular CM9 rom.
Click to expand...
Click to collapse
Yeah, that seems to be about the size of it. I used non-opengl, which I suppose I will add to the OP. But it will have whatever limitations CM9 has, in the best case.
Maybe I should give it a try lol.
Eyeballer let me try an early version of this rom on a verygreen SD install. It works great on the SD. There are a couple of precautions I would point out.
If you set your systemui to phone mode, it will not by default show the soft navigation keys. There is a setting in settings that let you turn those on. It is off by default.
Second, the settings for the paranoid setup is stored in a file called pad.prop in /system. With the SD install, that file gets overwritten on installing an updated rom. I recommend that SD install users back up that file before updating the paranoidandroid rom. For SD installs just rename to .bak and after flashing, delete the new one and remove the .bak on the original. Eyeballer said he would try to fix that issue for emmc installs in the next version, but that will not help SD install users.
With this rom you can set YouTube to display in phone GUI and all HD videos will play in HQ. You can also set it for standard tablet dpi and the videos look great. In the tablet GUI of YouTube, HD videos try to play in HD and fail. And the only other choice is standard, which look horrible.
YES! This just made my day. Trying it now...
Sent from my NookColor using xda premium
Oh, I like this ROM! In particular I like the ability to set each app to it's own settings. Some apps work good in tablet ui even if systemui is in phone ui. And vice-versa. This is a winner.
leapinlar said:
Oh, I like this ROM! In particular I like the ability to set each app to it's own settings. Some apps work good in tablet ui even if systemui is in phone ui. And vice-versa. This is a winner.
Click to expand...
Click to collapse
I was specifically thinking of you when I was working on it, and all the hoops you had to jump through to be able to choose your own GUI.
Let me know what you think after you've played with it a while.
And thanks, computerist, for your in-depth feedback. We will definitely see what we can do.
thanks for this.. will be flashing it soon once i get some time off from work!
This for me is the best of both worlds. One of the reasons that I wanted to change dpi way back was because of the tiny fonts on the tablet GUI at 160 dpi. And changing that put you in phone GUI. Now you can set your dpi to whatever you want and choose the GUI you want. Not only that but you can change an individual app to behave like you want with a custom dpi that makes the fonts for that app just the size you want them. You can customize your entire system.
I'm never going back to ordinary cm9 again. So I encourage you guys to keep up the good work. I think everyone will love it once they understand what it can do.
Sent from my NookColor using ParanoidAndroid and Tapatalk
I tried a version of this ROM on my phone a while ago and although i don't use it on my phone anymore i remember thinking it would be perfect for the nook. I will definitely try this out when I get a chance. Thanks to the developers for their hard work and time on this ROM.
Sent from my GT-I9000 using xda app-developers app
Just some clarifications
Hi guys. First of all I want to say kudos on a job well done to the team that came up with this.
I am very new to the rooting and Android scene in general. But I have rooted/nooted my Nook Color with Cyanogen Mod 7. What I'd like to know is what do I need to do to go from CM7 to having ParanoidAndroid on my Nook and what will I not be able to do that I can do on CM7? (Which is Gingerbread?). I apologize if answers to thse questions are already available. Thanks again!
Adriel623 said:
Hi guys. First of all I want to say kudos on a job well done to the team that came up with this.
I am very new to the rooting and Android scene in general. But I have rooted/nooted my Nook Color with Cyanogen Mod 7. What I'd like to know is what do I need to do to go from CM7 to having ParanoidAndroid on my Nook and what will I not be able to do that I can do on CM7? (Which is Gingerbread?). I apologize if answers to thse questions are already available. Thanks again!
Click to expand...
Click to collapse
The normal steps for flashing any ROM. Assuming you have it all installed on emmc:
-Download ROM and appropriate Gapps and place on SD card
-Boot into Clockwork Recovery
-Create a backup of current setup
-Wipe current setup
-Flash new ROM/install from SD
-Flash Gapps
If you run on SD I couldn't tell you as I haven't done that in ages, but I don't think the setup process for SD varies much from ROM to ROM.
It is working well
Thanks to the devs for all the hard work. I installed this yesterday and I couldn't be more pleased. It allowed me to fix a few things that bothered me with CM9. Now it works like I want.
Thanks.
{
"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"
}
Project Open Cannibal presents...
Cannibal Open Touch v2.1 for Asus Nexus 7
About Cannibal Open Touch:
Cannibal Open Touch is the next generation of custom recoveries. Jam-packed with cool and useful features, it can handle just about anything you can throw at it.
Main Features:
1. Theme support
2. Touch screen button controls!
3. GooManager support!
4. Advanced Backup
5. Delete old backups!
6. Persistent settings
7. User-defined backup locations!
8. ADB Sideload
9. Touchscreen calibration
Why the name Cannibal Open Touch?
Because we can. The name also embodies everything that Cannibal Open Touch is. It is no longer just a variant of ClockworkMod Recovery, it is it's own recovery by itself. Combining features from ClockworkMod 5, Team UtterChaos' Sony Xperia recovery, AmonRa 3.0.6, Xionia CWMA and a heaping helping of our own special enhancements it is truly revolutionary.
What to do when an error occurs:
DO NOT simply say "xxxx doesn't work" as that is highly unhelpful and will probably be ignored. Instead, post the recovery log! To grab a log when an error occurs, simply open a terminal (or command prompt if on Windows), "cd" to an easily accessible directory and execute:
Code:
adb pull /tmp/recovery.log
Paste the log as an attachment (don't paste the text inside, as it can be quite lengthy), or paste it on pastebin.com.
WARNING!
If you are upgrading from a previous version of Cannibal Open Touch you must delete the settings.ini file located in the cotrecovery folder on your sdcard!
The Cannibal Open Touch App for Android (separate from this recovery image, which is fully functional on all devices) is *NOT* functional on Nexus 7 devices running Android 4.2 or later. A fix is being investigated.
Flashing instructions:
1. Download the Cannibal Open Touch recovery image.
2. Reboot your device to bootloader mode (adb reboot bootloader)
3. Flash the image with fastboot (fastboot flash recovery /path/to/recovery.img)
4. Reboot to recovery mode
5. PROFIT!
Main Recovery Screenshots
Main Gallery (external link)
Available Themes:
Themes Gallery (external link)
Download Cannibal Open Touch v2.1:
Note: The below link is an external link to the Project Open Cannibal forums. We do not require registration to download any public release, but we'd sure appreciate it if you stopped by to say hello
WARNING!
This has only been tested on the non-3g models (grouper/nakasi); while it is hightly probable this will work on the nakasig we cannot confirm this at this time (at best I would expect assert errors with rom zips).
Cannibal Open Touch Download
XDA:DevDB Information
Cannibal Open Touch, a Tool/Utility for the Nexus 7
Contributors
Sblood86, drewwalton19216801, thenameisnigel
Version Information
Status: Stable
Current Stable Version: 2.1
Stable Release Date: 2012-12-01
Created 2013-09-05
Last Updated 2013-09-05
Thanks this looks awesome, I will definantly use it when it supports 4.2. I may give it a shot on 4.1.2 though to see what it is all about
mlaws90 said:
Thanks this looks awesome, I will definantly use it when it supports 4.2. I may give it a shot on 4.1.2 though to see what it is all about
Click to expand...
Click to collapse
Yeah Drew (the other dev on the project) wrote in that warning there; it's referring to the Android control application that he did. Allows you to easily change the persistent settings from within android instead of recovery (including but not limited to the user defined backup paths). The recovery does work in 4.2, the app does not.
To set user defined backups you could use the app in 4.1 or older than upgrade the settings will remain in place; or manually create a file in sdcard/cotrecovery/ with the title .userdefinedbackups and the sdcard folder you would like backups saved to: for example if you wanted to add rom manager compatibility you would want your backups to be in '/sdcard/clockworkmod/' so in the .file you would simply write 'clockworkmod' without the quotes.
Sblood86 said:
Yeah Drew (the other dev on the project) wrote in that warning there; it's referring to the Android control application that he did. Allows you to easily change the persistent settings from within android instead of recovery (including but not limited to the user defined backup paths). The recovery does work in 4.2, the app does not.
To set user defined backups you could use the app in 4.1 or older than upgrade the settings will remain in place; or manually create a file in sdcard/cotrecovery/ with the title .userdefinedbackups and the sdcard folder you would like backups saved to: for example if you wanted to add rom manager compatibility you would want your backups to be in '/sdcard/clockworkmod/' so in the .file you would simply write 'clockworkmod' without the quotes.
Click to expand...
Click to collapse
Oh see, that is not a big deal at all. I would be willing to give that a shot, didn't even know there was an app Thanks for the detailed reply, I'm sure it will help others as well.
The recovery looks nice ^_^
Don't know why I prefer unique recoveries and not popular ones
I like the look of this recovery, I have nothing as of yet to flash, but I'll definitely be keeping it
Thanks
Sent from my SGH-I747 using xda premium
OK just to clarify, this does work 100% with 4.2.1 ROMs? And where can i find some themes for it.....looks verrrrrrry promising
Edit...and I'm not concerned about backups as i never use them.... FULL wipe every time for me
Sent from my Nexus 7 using xda premium
lightninbug said:
OK just to clarify, this does work 100% with 4.2.1 ROMs? And where can i find some themes for it.....looks verrrrrrry promising
Edit...and I'm not concerned about backups as i never use them.... FULL wipe every time for me
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Yes the recovery works w/ 4.2 roms the only issue is the app that Drew did not being able to communicate with the sdcard properly in 4.2 (this is not related to the recovery itself).
Themes we could use more of; there is an outline of them on our forums and on github (nexus 7 is of course the jb-800x1200 branch)
Looks nice gonna give it a run through
Are there any sources? I kind of want to build this for my spectrum or do you not have plans for open source
Sent from my Nexus 7 using Tapatalk HD
azoller1 said:
Are there any sources? I kind of want to build this for my spectrum or do you not have plans for open source
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I apologize; I ripped the thread layout off from Drew and didn't realize the source was not linked. I'll get it linked in the OP at a later time but for now suffice it to say yes we have open sourced everything; we have full intention of open sourcing all future related code as well (hence the 'Open' part of the name ):
Either sync a CM10 tree or use the jellybean branch in Drew's hacked up manifest (this will only build recovery).
Whichever way you sync your repo you will need to replace the recovery folder (Drew's manifest is pulling the old repo)
you will need the jellybean branch from the recovery itself:
android_bootable_recovery
if you used Drew's manifest you should already have the following if not you will want to pull these as well:
the jellybean branch from here
android_bootable_recovery_gui
and the master from here
android_bootable_recovery_res
Lastly; a slightly modified grouper device repo (pretty sure this one is also for recovery only lol)
I'll definitely give this a run when I can later today!
Pretty Awesome. Installed just fine on my Nexus7 WiFi. Gonna run this for a while and see how she goes, tnx!
Quick question, is there a way to flash this without a computer? As u currently don't have one and could I use my twrp backup if anything are to happen or would I need to make a new one with this recovery?
Sent from my Nexus 7 using Tapatalk HD
xfrancis14 said:
Quick question, is there a way to flash this without a computer? As u currently don't have one and could I use my twrp backup if anything are to happen or would I need to make a new one with this recovery?
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
You need to use fastboot, which requires use of a computer (for now). TWRP backups are not compatible so yes you would need to make a new backup.
Okay well I don't currently have a computer so I guess ill stick with twrp for now and okay
Sent from my Nexus 7 using Tapatalk HD
Is it possible for you to make an app which would flash the recovery? If so that would he amazing as I really want to try this recovery
Sent from my Nexus 7 using Tapatalk HD
xfrancis14 said:
Is it possible for you to make an app which would flash the recovery? If so that would he amazing as I really want to try this recovery
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Well... If the nexus 7 supports flash_image or dd (which I have no idea if it does, you'll have to find out or ask Drew) than yes it's possible; than again you could simply do it from a terminal emulator in that case. Fastboot is the safest way in particularly without having the device myself to play with.
finally got a chance to test her out, so far so good!
not the absolute best advance since sliced bread but i do love seeing an alternative!
as of now i give it a 7 out of ten being no problems i can find, everything seems to work but dont feel as if im gaining much over my other recovery options... that said i felt the same way at first with 4ext recovery and now i absolutely love it, so ill let you know if this moves to 10 out of 10 an time soon
thanks again for giving me options!
{
"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"
}
Welcome to Eos 4.0! The Eos project originated with the AOSP release of ICS, and was originally founded by Solarnz and co founded by Bigrushdog. Since then, Eos has evolved into a multinational collaborative effort backed by top Android developers. Our objective is to provide a world class AOSP build with unique features and enhancements. Eos is an ongoing development project in which builds are released on a regular basis. Every release should be considered stable and highly functional.
Solarnz - Project founder and backend systems admin
Bigrushdog - Project lead, Chief Developer
Kevdliu - Feature Engineer, Toro maintainer
Timduru - Frameworks Developer, TF101 maintainer
Roach - Frameworks Developer - N4 maintainer
RaymanFX - Remote branch and Experia maintainer
Runandhide05 - Xoom maintainer
UBER - Chief Graphics Designer
Sykomaniac - Maguro maintainer
Code:
NX Gesture Navigation Bar
Custom Quick Toggles Tiles with Brightness & Volume Seekbars
Softkeys Long-Press Actions
Custom Navigation Bar Ring Quick Launch Targets
EOS Status Bar Toggles
Navigation Bar Color w/ Project Glass (Auto-Transparency, not the Google Project Glass :P)
Status Bar Color
Battery Indicator Mods
Clock Mods
T-Mobile Theme Engine
Hide System Bars
Performance Settings
Volume keys switch depending on rotation. So the volume up key is always either on the top or to the right of volume down. (Toggle-able)
Default Volume Control Stream (Ring or Media)
Advanced power menu with reboot options.
Eos Control Center
MORE...
We give love and much respect to Cyanogenmod. The AOSP scene would not exist as it does today without them. We implement some of their branches to support legacy devices and features that users have demanded. The resources we use include, but are not limited to:
Features:
Code:
Phone: for T9 dialer support
MMS
T-Mobile Theme Engine
Branches:
Code:
libhardware, libhardware_legacy, system/core, system/netd, /system/vold, frameworks/native, frameworks/av, isolated frameworks/base cherry-picks,
and various qualcomm support related branches. We also use some qualcomm related branches from CodeAurora Forum.
Team EOS Grouper Nightly builds
Download
G-Apps Package
Because this is an AOSP based rom Google Apps are not included. To install Google Apps please flash the following package after installing the rom:
Gapps package
Nexus 7 comes with the stock aosp kernel.
These builds are designed to be installed from your favorite recovery. MAKE SURE YOU HAVE THE LATEST 4.2.2 COMPATIBLE RECOVERY.
Changlog
Contribute
Gerrit Review
Gitweb for GPL compliance
Ohai! Guess I'll jump in here.
Yup... Spoiled by the participating...
Caution - SDcard directory changes with 4.2 installation
For those of you that are new to 4.2 releases, be aware that installing and running this rom creates a directory "/sdcard/0" and moves all content in the sdcard directory to the "0" directory. (Perhaps I missed a posting somewhere on this.)
I reinstalled this rom a few times due to Gapps crashes and later could not find any of my files files in the sdcard directory including my backup files. I first thought I had accidentally formatted the sdcard, but later found that each time I had tried to flash and start this rom another new "0" subdirectory was created and all files were moved to yet another subdirectory. By time I was done all my files were safely stored in /sdcard/0/0/0/.
Also be aware that the Clockworkmod directory is one of those moved and Clockworkmod Recovery may not be able to find your nandroid backup in the new directory if you decide to restore. I haven't tried the latest version of CWM, but it was a problem on the six week old version I had installed.
It took me a few minutes to figure out what was going on and am hoping to save someone else the trouble.
Edit: Installed the latest version (as of 12/17) of CWM and it.too was unable to find my nandroid backup once it was moved to the /sdcard/0 directory by the 4.2 installation process. To restore my old rom I had to do a clean install, then install ES file Explorer, move the clockworkmod directory to /sdcard/ and THEN restore.
freecity said:
For those of you that are new to 4.2 releases, be aware that installing this rom creates a directory "/sdcard/0" and moves all content in the sdcard directory to the "0" directory. (Perhaps I missed a posting somewhere on this.)
I reinstalled this rom a few times due to Gapps crashes and later could not find any of my files files in the sdcard directory including my backup files. I first thought I had accidentally formatted the sdcard, but later found that each time I had tried to flash this rom another new "0" subdirectory was created and all files were moved to yet another subdirectory. By time I was done all my files were safely stored in /sdcard/0/0/0/.
Also be aware that the Clockworkmod directory is one of those moved and Clockworkmod Recovery may not be able to find your nandroid backup in the new directory if you decide to restore. I haven't tried the latest version of CWM, but it was a problem on the six week old version I had installed.
It took me a few minutes to figure out what was going on and am hoping to save someone else the trouble.
Click to expand...
Click to collapse
You need to upgrade your recovery to the latest cwm or twrp. The issue has been fixed since 11/16
freecity said:
For those of you that are new to 4.2 releases, be aware that installing this rom creates a directory "/sdcard/0" and moves all content in the sdcard directory to the "0" directory. (Perhaps I missed a posting somewhere on this.)
I reinstalled this rom a few times due to Gapps crashes and later could not find any of my files files in the sdcard directory including my backup files. I first thought I had accidentally formatted the sdcard, but later found that each time I had tried to flash this rom another new "0" subdirectory was created and all files were moved to yet another subdirectory. By time I was done all my files were safely stored in /sdcard/0/0/0/.
Also be aware that the Clockworkmod directory is one of those moved and Clockworkmod Recovery may not be able to find your nandroid backup in the new directory if you decide to restore. (I haven't tried the latest version of CWM.)
It took me a few minutes to figure out what was going on and am hoping to save someone else the trouble.
Click to expand...
Click to collapse
Its not "this ROM" its all 4.2 ROMs that do it. And the way to prevent the /0/0/0/0 is by updating your recovery to the latest CWM or TWRP.
the new multi user in 4.2.x moves all your internal data to /data/media/0 for the main device owner. And if you create another user you will see /1 for the second user and so on for however many users you add.
So on 4.2.x ROMs you will have one /0 and it needs to be like that, if you move all your data to /data/media you will have issues. The /0 is a must and is the way of the future.
Having said that I will say it again. If you haven't already you really need to update your recovery.
Also on the note of gapps you must use the gapps specifically for 4.2 not 4.1.1 if you don't use 4.2 gapps you will have gapps fc like crazy
The slider in the Quicksettings menu for brightness is very laggy. Volume seems fine though. Also, my battery meter in Quicksettings sometimes says 0%, even though I'm at 97%.
runandhide05 said:
Its not "this ROM" its all 4.2 ROMs that do it. And the way to prevent the /0/0/0/0 is by updating your recovery to the latest CWM or TWRP.
the new multi user in 4.2.x moves all your internal data to /data/media/0 for the main device owner. And if you create another user you will see /1 for the second user and so on for however many users you add.
So on 4.2.x ROMs you will have one /0 and it needs to be like that, if you move all your data to /data/media you will have issues. The /0 is a must and is the way of the future.
Having said that I will say it again. If you haven't already you really need to update your recovery.
Also on the note of gapps you must use the gapps specifically for 4.2 not 4.1.1 if you don't use 4.2 gapps you will have gapps fc like crazy
Click to expand...
Click to collapse
The version of gapps I installed was 4.2 downloaded from the OP. I also tried a 4.2 gapps downloaded from another link so I was probably just missing a step somewhere or had a bad rom download, I'll try again tomorrow.
I do not believe I suggested that there was anything wrong with this or any other 4.2 rom (and certainly did not mean to suggest anything of the sort), only that there are important changes to be aware of when moving from 4.1 to 4.2 and back.
Thanks, will give it a try.
freecity said:
The version of gapps I installed was 4.2 downloaded from the OP. I also tried a 4.2 gapps downloaded from another link so I was probably just missing a step somewhere or had a bad rom download, I'll try again tomorrow.
I do not believe I suggested that there was anything wrong with this or any other 4.2 rom (and certainly did not mean to suggest anything of the sort), only that there are important changes to be aware of when moving from 4.1 to 4.2 and back.
Click to expand...
Click to collapse
Also note a full wipe is a MUST coming from any other ROM or even eos3
And I didn't read it as implying anything.
Just be sure to update recovery
All good Buddy
Does this have tablet ui? Can't use my nexus 7 without it. Lol
Sent from my Nexus 7 using xda premium
TheUndertaker21 said:
Does this have tablet ui? Can't use my nexus 7 without it. Lol
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
In a way.. It has the option to put the soft keys in the left side like tab ui but keeps the top status bar
Sent from my Nexus 7 using Tapatalk 2
Haha that'd do. Thanks for reply.
Sent from my Nexus 7 using xda premium
That's pretty sweet.
New build out. Eos is on a roll
Can we just dirty flash 45 over 44? Will gapps need to be reflashed again also?
44 was running pretty well. Already downloaded 45. Waiting on answer before I flash new build.
demandarin said:
Can we just dirty flash 45 over 44? Will gapps need to be reflashed again also?
44 was running pretty well. Already downloaded 45. Waiting on answer before I flash new build.
Click to expand...
Click to collapse
Dirty flash is fine.. I've had no issues going from 44 to 45
Sent from my Nexus 7 using Tapatalk 2
DJLamontagneIII said:
Dirty flash is fine.. I've had no issues going from 44 to 45
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Yep..dirty flashed rom an reflashed gapps. All running well so far.
Unless instructed otherwise from eos4 nightly to nightly a dirty flash is fine.
Also the latest update fixes ALOT of the third party apps FC'ing.
So put firefox, kindle, and many more on the problem squashed list.
Anybody having issues using the latest nightlys with custom kernels? I tried using Franco's kernel and I am unable to install paid apps with it. I get the USB storage error.
// Droid Bionic
// Android 4.2.2
// Current Version [ 4.2.14 ]
// All Languages
{
"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"
}
MIUI ROM 4.2.14 Full Changelog
[Home screen]
New - New Edit Home screen interface (2-12)
New - View the notificiation shade by swiping down anywhere on the Home screen (2-12)
Optimization - Previewing Home screens uses less system memory (2-12)
Fix - When user created a shortcut without a name, FC would occur (2-12)
[Phone]
Fix - Sometimes the switch for auto IP identification would display incorrectly (2-11)
[Gallery]
New - Album thumbnails of screen shots will be detected automatically (2-10)
Fix - User could not delete albums that they had shared with themselves (2-10)
Fix - When Wi-Fi was disabled, photo downloads would be canceled (2-10)
Fix - User could not copy photos to shared albums (2-10)
Fix - When user rotated phone photo would not maintain its scale or position (2-10)
Click to expand...
Click to collapse
MIUIv5 4.2.14 Download
2-19-2014: MIUI v5 4.2.14 XT912
Working:
- Everything, hopefully
MIUI General FAQ
Q: How do I root this?
A: Enable root in the perm manager, which can be found in the security folder.
Q: Why is G-Apps not listed for Download?
A: Too Bloaty, add a Google account and install the play store as an APK, I suggest using Aptoide to find it.
Q: 4G LTE isn't working
A: Load the Phone, dial *#*#4636#*#*, goto Phone information, Set preferred network type to LTE/CDMA auto (PRL).
Q: Help! Phone/SystemUI/Keyboard Isn't working/Is Force Closing!
A: Make sure to do a completely clean wipe, also I'm not sure how well this will work if flashed in CWM.
Q: The Browser looks terrible.
A: Settings -> Advanced -> User agent string -> MiOne (It Renders much better & more naturally!)
Q: My Filesystems won't mount/My PC can't see my device/My phone won't act as a MTP/USB Mounting isn't working!
A: Settings -> Developer Options -> Enable Development / USB Debugging (switch both to on)
Link as soon as rom uploads!
Sent from my XT910 using Tapatalk
kascro said:
Link as soon as rom uploads!
Sent from my XT910 using Tapatalk
Click to expand...
Click to collapse
I'm source building for the entire Moto device tree, each source build takes about 3-4 hours, so I have roughly 40ish hours of source building for 12 devices to do before this is completed.
Honestly though since this thread got a reply first I'll play favorites and finish this before everything else
Thank you very much !
Sent from my XT910 using Tapatalk
@Tquetski Thank you very much for your efforts. You mentioned in the header of your post "All languages", does this mean the Chinese & English like default or did you manage to include further translations? If so, which?
the thread says "Droid Razr", does this mean there will be only XT912 version? Do you plan releasing a version for umts_spyder (XT910)?
Thanks!
woonaval said:
the thread says "Droid Razr", does this mean there will be only XT912 version? Do you plan releasing a version for umts_spyder (XT910)?
Thanks!
Click to expand...
Click to collapse
You can directly download for UMTS_SPYDER version here :
http://en.miui.com/download-21.html
All Languages Miui v5 (XT910) ; http://forum.xda-developers.com/showthread.php?t=2597488
majamee said:
@Tquetski Thank you very much for your efforts. You mentioned in the header of your post "All languages", does this mean the Chinese & English like default or did you manage to include further translations? If so, which?
Click to expand...
Click to collapse
My MIUI releases are international and include every avail language, in 2-3 hours I should be done with MIUI for this device.
I just finished my 'code test' for XT926, and have begun building for this device.**edit: As soon as building for already supported phones are done this is next
To be clear I don't care who is releasing MIUI for this phone, I'm doing this for 'completion' purposes and not to be in competition, It's my goal to fork MIUI to every device I can in bulk atm; I'm fine with people using the CM base I'm building for their own MIUI projects on this device as well, It's not about money or territory just fun
Um, this may be a little off topic but since the other MIUI thread is closed, I dunno where else to ask. I am trying to install the official santajin port of 4.2.7. So I am on clean 4.1.2 en.eu OTA. I factory reset erasing my internal storage. On the 2nd boot, after the android guy, I go into SS. I made a 1G/4G/1G slot 1 in SS, the maximum size. I installed MIUI 4.2.7. I clean cache/davlik. I reboot into system without installing gapps yet. That seems to be as clean as an install as I can think of. After going through the setup phase, I have about 70M/1G free and it goes down fast without doing anything. It's so slow it's basically unusable. I reboot again, same thing. Is this normal? This seems like I shouldn't even think of opening the default MIUI apps, forget installing my own stuff... I tried miuiandroid's version of 4.2.7 and it was the same. Oh BTW my device was asiaretail. What am I doing wrong here? This can't be what everyone is using...
Is this ROM cm based smali ported? Or offical 4.1 based?
Sent from my XT875 using XDA Premium 4 mobile app
adtrisno said:
Um, this may be a little off topic but since the other MIUI thread is closed, I dunno where else to ask. I am trying to install the official santajin port of 4.2.7. So I am on clean 4.1.2 en.eu OTA. I factory reset erasing my internal storage. On the 2nd boot, after the android guy, I go into SS. I made a 1G/4G/1G slot 1 in SS, the maximum size. I installed MIUI 4.2.7. I clean cache/davlik. I reboot into system without installing gapps yet. That seems to be as clean as an install as I can think of. After going through the setup phase, I have about 70M/1G free and it goes down fast without doing anything. It's so slow it's basically unusable. I reboot again, same thing. Is this normal? This seems like I shouldn't even think of opening the default MIUI apps, forget installing my own stuff... I tried miuiandroid's version of 4.2.7 and it was the same. Oh BTW my device was asiaretail. What am I doing wrong here? This can't be what everyone is using...
Click to expand...
Click to collapse
Memory leak; I have no idea,
Give me some time to finish souce builds and I'llhave this up soonish
waiting with fingers crossed mate!!
Tquetski said:
Memory leak; I have no idea,
Give me some time to finish souce builds and I'llhave this up soonish
Click to expand...
Click to collapse
Ok, take your time... I was wondering, what steps are people doing clean installing miui v5 and what am I doing differently?
adtrisno said:
Ok, take your time... I was wondering, what steps are people doing clean installing miui v5 and what am I doing differently?
Click to expand...
Click to collapse
Full wipes and format system
Also any volunteers to test this before I wantonly throw it up
!
this thread should be deleted !!!! you make thread open with some rom theme but you don't have any rom.that what you do i for nobody interestingly. first make your rom finish and after that make new thread with link for download !!!!!:silly: before that do not make time waste here !
mirot said:
this thread should be deleted !!!! you make thread open with some rom theme but you don't have any rom.that what you do i for nobody interestingly. first make your rom finish and after that make new thread with link for download !!!!!:silly: before that do not make time waste here !
Click to expand...
Click to collapse
Take it easy..... He is source building MIUI for lots of motorola devices so this could be considered...
Sent from my XT875 using XDA Premium 4 mobile app
mirot said:
this thread should be deleted !!!! you make thread open with some rom theme but you don't have any rom.that what you do i for nobody interestingly. first make your rom finish and after that make new thread with link for download !!!!!:silly: before that do not make time waste here !
Click to expand...
Click to collapse
I've already build CM10.1 for this device with source edits to accommodate MIUI's gfx and using that source base patched MIUI to it.
I can update this as MiCode updates their builds internally; as of right now the only thing standing in my way is your phones kernel, which is a little different than what I have experience with.
Even if I don't finish MIUI for this phone which may happen depending on how things play out with the kernel, I'll have still finished a suitable CM10.1 base for it that anyone can consider using for MIUI, Lewa, Color OS which would normally have severe GFX issues otherwise.
The XT925, XT926, XT907, XT897, XT897c, MB886, AtrixHD didn't have functional MIUI for a while even though the thread existed on XDA, It's a development site and since I've started this project I'm starting a thread for it, now I can push weekly updates to those devices on a solid CM base.
Truth be told I didn't like some of the posters who frequented one of my device forums and so I ignored the phone completely for uh.. a really long time.
I'm really not above being a dickhead too. Especially when you consider I'm just some guy not someone making a living off of this.
There you go dummy, I included a 'best of' because I know your attention span is real short
Edit: Project update for everyone else, everything beside the kernel is done. If I have to use your stock kernel I'll have to employ other options.
My friend kernel has always been a problem for us. For example we have only kexec kernel option and that didn't allow us to use our full hd camera till 4.4.2. With that I mean it would be maybe easier for u to build the miui with 4.4.2 which has a good functioning kernel with full hd video. But I dunno if it's possible. Just saying
Sent from my XT910 using XDA Premium 4 mobile app
Where link?
[ROM][3/26/15] Pure AOSP ROM -★| 5.1.0_R3 | LMY47I | Build #6 | Proof of concept! |★-
Pure AOSP for the Nexus 6
Preface:
This is meant to be a Pure AOSP build with just minor edits to stop the stock recovery from replacing custom recovery, add some Google edits to the ROM for GPS, and modify the ramdisk so as not to preclude it from being rooted! Its not meant to be a fancy ROM, its just meant to be a baseline AOSP ROM. This ROM was produced by following the steps in the build guide I wrote. See post #2 for build guide links!
Install Instructions
Must have custom Recovery on unlocked device
Copy ROM to device (Gapps and root too!)
Reboot to recovery
Choose Factory reset (TWRP, not sure what CWM is)
Choose Install ROM
Now you can install the Gapps, and Root if you desire!
Specs and Download Link!
Android Build Version: 5.1.0_R3 / LRX22G
Current Build Date: 3/26/2015
Download: HERE!
Recommended Add-Ons
SuperSU by Chainfire here: SuperSU Stable Version
PA Gapps here: [GAPPS][5.0.x][BETA] OFFICIAL Up-to-Date PA-GOOGLE APPS (All ROM's)
Change Log
1/19/15 - Build 6 - Complete rebuild as proof of concept for 5.1.0_r3. This is PURE AOSP with no edits and no fixes.
1/19/15 - Build 5 - Fixed Youtube, Net flix DRM play back issue. Thanks to @sykopompos for pointing me to @ayysir git hub for the fix by @BeansTown106
1/17/15 - Build 4 - Fixed Browser force close in settings.
12/19/14 - Build 3 - Updated to Android 5.0.2_r1
12/15/14 - Build 2 - Switched back up to block based build for installation speed! Thanks to @hlxanthus for the 411!
12/14/14 - Build 1 - Initial build
{
"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"
}
Click to expand...
Click to collapse
Build Guide Link
Want to build this exact ROM yourself?
Here is a great build guide I wrote: [Guide][1/19/2015] Building AOSP for the Nexus 6!
Change Log
Add-Ons
Sprint Data connectivity linked by @orlzzt is HERE!
Reserved!
Hmm... I'll take this for a spin later. Thanks!
Is it safe to say with this being pure aosp shamu that it is still set to force encryption?
Also, the drawback of not doing the block style flashable is it takes several times longer to actually install via recovery.
hlxanthus said:
Is it safe to say with this being pure aosp shamu that it is still set to force encryption?
Also, the drawback of not doing the block style flashable is it takes several times longer to actually install via recovery.
Click to expand...
Click to collapse
Yes. Its pure AOSP.
Can you give me a calculation of time to install block based and file based ROM? Several times longer is a strong statement. If you could produce factual data I would appreciate.
However I am still not going block based installs because the user can take this ROM, add or remove things before it is even installed.
But I look forward to the numbers you show me! If you dont have the data that is fine. I can change the false to try in the script ota_from_tools and test it myself. Should only take a few minutes to recompile as block based.
But thanks for the input!
Took like 3-5 minutes to install your ROM and maybe 20 seconds to at most a minute to install either rastapop or cm12alpha. Honestly I thought it stalled or failed so I rebooted recovery and installed just your ROM (instead of gapps together via twrps) and it simply takes a LONG time to flash.
Great to finally see you here scrosler!!! Always great to welcome another knowledgeable developer to the forums
hlxanthus said:
Took like 3-5 minutes to install your ROM and maybe 20 seconds to at most a minute to install either rastapop or cm12alpha. Honestly I thought it stalled or failed so I rebooted recovery and installed just your ROM (instead of gapps together via twrps) and it simply takes a LONG time to flash.
Click to expand...
Click to collapse
The exact numbers your reported time can vary buy almost 66%! Thats a huge variance.
Also, you are testing differnt ROMS. For a control I need to build this exactly as it is but block based.
I will test it on my device with a high end chronograph and report my results.
Also, what recovery are you using?
Ok, I timed the file based intall, it was 2:16.08 (which was closer to your 3 minute estimate but a far cry from the 5 minute estimate)
I will build a block based ROM tonight and test to see the difference. However its still very unlikely I would change the current set up. Although I could just post both! :highfive: Win Win for everyone :good:
But once again! Thanks for your input!
scrosler said:
The exact numbers your reported time can vary buy almost 66%! Thats a huge variance.
Also, you are testing differnt ROMS. For a control I need to build this exactly as it is but block based.
I will test it on my device with a high end chronograph and report my results.
Also, what recovery are you using?
Click to expand...
Click to collapse
I can time it if that helps, or you can test yourself if you would rather. As for recovery, the only one I know of is twrp, downloaded directly via their website (only one version there) and manually fastbooted in place.
hlxanthus said:
I can time it if that helps, or you can test yourself if you would rather. As for recovery, the only one I know of is twrp, downloaded directly via their website (only one version there) and manually fastbooted in place.
Click to expand...
Click to collapse
We are cross posting. I timed it myself and it was just a hare over 2.25 Minutes. Which is not that far off from your assert of 3.0 minutes.
Im going to build the block based tonight and post it so people can have both options.
You brought a valid point. Once again, thanks for your input!
Edit: Also, wasnt trying to beat you up, I just like solid number comparisons.
Haha no worries, us old optimus s veterans need to stick together ?
Edit: if you wanted to remove the force encryption, it is a very simple fstab.shamu edit. Under the /userdata line, change "forceencrypt" to "encryptable". Looking at a few rom sources, that is how they all do it. That way if you are encrypted you will stay encrypted. If not, then it wont force encrypt you. Would save people from having to flash an alternate kernel . .
hlxanthus said:
Haha no worries, us old optimus s veterans need to stick together ��
Edit: if you wanted to remove the force encryption, it is a very simple fstab.shamu edit. Under the /userdata line, change "forceencrypt" to "encryptable". Looking at a few rom sources, that is how they all do it. That way if you are encrypted you will stay encrypted. If not, then it wont force encrypt you. Would save people from having to flash an alternate kernel . .
Click to expand...
Click to collapse
OMG!!! Optimus S? Are you serious? That was my first Android Phone / ROM!
Yeah, I know how to shut it off. But i wanted to leave this as close to pure AOSP as I could. I think I will shut it off on the next build though. I heard the encryption can slow things down a hair too.
Ok, I just got lost reading comments. Is this encrypted? If it is, does anyone mind letting me know what to do BEFORE I flash to decrypt.
Ty.
gcng said:
Ok, I just got lost reading comments. Is this encrypted? If it is, does anyone mind letting me know what to do BEFORE I flash to decrypt.
Ty.
Click to expand...
Click to collapse
You just flash a no force encrypted kernel which I basically any of them. And as @scrosler just said he may just build it into the next build.
---------- Post added at 02:55 PM ---------- Previous post was at 02:53 PM ----------
And yes, same user name over at android central, I had DanteRom that I released. ?
EDIT:
DAMN! There is no comparison from Block Build and File based build
Block build was roughly 2 minutes and 30'ish seconds
Block based build was 10'ish seconds!
Hey Scott glad you are building for the nexus 6 are you planing on a Clean Rom also? Or just keeping it aosp
scrosler said:
OMG!!! Optimus S? Are you serious? That was my first Android Phone / ROM!
Yeah, I know how to shut it off. But i wanted to leave this as close to pure AOSP as I could. I think I will shut it off on the next build though. I heard the encryption can slow things down a hair too.
Click to expand...
Click to collapse
I'd say leave it encrypted for now until faux finally makes it to the threads...from his g+ posts it seems his found a way to keep the device encrypted yet have around the speed as though it was unencrypted. And he's a very open source guy so I'm sure he'll share the magic