[Unofficial] Paranoid Android G2 4.6b3+ NoHeatMod - G2 General

Creating a new thread as posting modding info in the official thread might be considered rude/inappropriate/hijacking.
Read the official thread first, starting october 6 2014.
These modding descriptions are for the works of the AOSPA and AOSPA-legacy team, about 101% of the credits go to @ayysir and @houstonn and all oft PA team. Awesome stuff.
Feel free to donate to them in the way of their liking.
And of course @777jon, owner of the cited unofficial VS980 thread, who gave the essential hint about the display-caf package
This thread is intended to provide a knowledge base for modding the official builds as long as they seem flawed for some of us. Feel free to reference helpful stuff from other threads in accordance to forum rules.
D802 @ AOSPA 4.6b3

Here's what made the issue go away for me on D802. This might be dangerous, so don't do it if you can't live with the risk of bricking your phone, you are entirely on your own if something goes wrong.
Prerequesites:
- Install official 4.6b3 AOSPA-legacy zip-image to phone
- [optional] Install Renders Kernel
- Install updated root
- Download and extract unofficial 4.6b3 VS980 zip-image from @777jon 's thread (yeah, it's the wrong phone, but we need only one file; find thread in Forum yourself, got yelled at for crosslinking stuff before )
Procedure:
-MAKE NANDROID BACKUP!
-Copy file from extracted VS980-image [zip]/system/lib/hw/hwcomposer.msm8974.so to phone's sdcard folder via USB (eg. ./Download)
-Start terminal on phone or adb shell
-Create backup dir:
Code:
mkdir /sdcard/noheatbackup
-get root access by typing
Code:
su
-make /system writeable by typing
Code:
mount -o remount,rw /system
-backup existing file by typing
Code:
cp /system/lib/hw/hwcomposer.msm8974.so /sdcard/noheatbackup/
-overwrite existing file by typing
Code:
cp /sdcard/Download/hwcomposer.msm8974.so /system/lib/hw/
-reboot by typing
Code:
reboot
-Note that you will need to be on a root shell to remove the backup again with
Code:
rm -r /sdcard/noheatbackup
:
Screenshot after replacing /system/lib/hw/hwcomposer.msm8974.so : Heat issue gone, see temp in status bar. After deep sleep, temps are about 3-5 K over room temperature.
{
"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"
}
D802 @ AOSPA 4.6b3

Thanks for creating a new thread man, but i don't think this qualifies for the Original Development section though
@Judge Joseph Dredd please move to correct section

mjwhirly said:
Thanks for creating a new thread man, but i don't think this qualifies for the Original Development section though
@Judge Joseph Dredd please move to correct section
Click to expand...
Click to collapse
Just move it whereever this kind of stuff belongs to. I still have to learn forumish [emoji17]
D802 @ AOSPA 4.4

Oh yes. See me:
Can i do it?
Download the vs980 From Post on original g2 development thread. Extract the zip and copy the file. (the 06/29 version)
Download the official beta 3 on aospal and extract it. Now i'll copy the file before and paste on beta 3 extracted zip, then i replace it. Now i'll zip the files and flash them via twrp. This method works too?

bielphc said:
Oh yes. See me:
Can i do it?
Download the vs980 From Post on original g2 development thread. Extract the zip and copy the file. (the 06/29 version)
Download the official beta 3 on aospal and extract it. Now i'll copy the file before and paste on beta 3 extracted zip, then i replace it. Now i'll zip the files and flash them via twrp. This method works too?
Click to expand...
Click to collapse
No, i meant the 4.6v3 version from october. Might work the way including it to the zip, but I'm really new to this and haven't tried.

Benztown said:
No, i meant the 4.6v3 version from october. Might work the way including it to the zip, but I'm really new to this and haven't tried.
Click to expand...
Click to collapse
Ok. you saved my life. Thx. i love this rom but i dont want to cook a pizza on him.
thx

"-overwrite existing file by typing cp /sdcard/Download/hwcomposer.msm8974.so /system/lib/hw/"
My phone rebooted of it self after doing the step above!?
But the copying seem to have worked! Thanks a lot for this guide!

For me doesn't work.

slade9220 said:
For me doesn't work.
Click to expand...
Click to collapse
Did you take the VS980 zip from @777jon s thread? I guess the official one has the same issues as the d802 official one.
Also I did it in an ADB shell, dunno if it works on phone's terminal.
D802 @ AOSPA 4.4

Benztown said:
Did you take the VS980 zip from @777jon s thread? I guess the official one has the same issues as the d802 official one.
Also I did it in an ADB shell, dunno if it works on phone's terminal.
D802 @ AOSPA 4.4
Click to expand...
Click to collapse
Thanks.. I'll try! ✌
Edit: IT WORKS! THANKS!

Do Anyone try the new 4.6Beta4?!

I wonder if you can just take the hwcomposer.msm8974.so file from any rom based on dr87's source?
Its the same thing right?
______________
Edit
I just extract the lib from 3 different rom cm unofficial by fabioio (no number), pa vs980 (1), and mahdi 920 (2). Fabioio's cm is smallest and both pa and mahdi are of the same size.

punyategar said:
I wonder if you can just take the hwcomposer.msm8974.so file from any rom based on dr87's source?
Its the same thing right?
______________
Edit
I just extract the lib from 3 different rom cm unofficial by fabioio (no number), pa vs980 (1), and mahdi 920 (2). Fabioio's cm is smallest and both pa and mahdi are of the same size.
Click to expand...
Click to collapse
I didn't compare the sources and also didn't check for device dependencies. If its design is done properly there shouldn't be any though. So yeah you should be able to take it from any dr87 based image as long as the structure doesn't change between different commits.
For the size that might just be different compiler options or even just symbol paths. Difficult to compare.
Also with this whole pa closedsource vs. pa opensource one cannot be sure what's really behind the official builds. Can someone actually bring me up to speed what's behind this open/closed source nonsense? Just IP protection?
D802 @ AOSPA 4.4

slade9220 said:
Do Anyone try the new 4.6Beta4?!
Click to expand...
Click to collapse
After what I've read... I'll stay miles away from that build [emoji16]
D802 @ AOSPA 4.4

Benztown said:
I didn't compare the sources and also didn't check for device dependencies. If its design is done properly there shouldn't be any though. So yeah you should be able to take it from any dr87 based image as long as the structure doesn't change between different commits.
For the size that might just be different compiler options or even just symbol paths. Difficult to compare.
Also with this whole pa closedsource vs. pa opensource one cannot be sure what's really behind the official builds. Can someone actually bring me up to speed what's behind this open/closed source nonsense? Just IP protection?
D802 @ AOSPA 4.4
Click to expand...
Click to collapse
The closed source thing is supposedly because that particular stuff(?) Is still buggy. Seeing how stuff go at desktop linux, this reason is really weird.
Yeah i just did the copy paste thing, i got stuck at lg logo. Right as i paste it the cellphone rebooted. I havent changed permission. I havent tried it for the second time though. Not sure if itll be the same.

punyategar said:
The closed source thing is supposedly because that particular stuff(?) Is still buggy. Seeing how stuff go at desktop linux, this reason is really weird.
Yeah i just did the copy paste thing, i got stuck at lg logo. Right as i paste it the cellphone rebooted. I havent changed permission. I havent tried it for the second time though. Not sure if itll be the same.
Click to expand...
Click to collapse
That does indeed seem weird. It seems to me that custom roming is more about magical coding wizardry and fame than about progress in a classical open source sense. Maybe it's just an issue about age. I'm obviously too old...
Strange, my phone didn't reboot. I did it with adb shell and su.
D802 @ AOSPA 4.4

Related

[ROM] [AOSP] WD40M0D: Froyo with a little extra ;) (ALPHA 2)

Froyo with a little WD40 in the gears!
Presenting WD40M0D! This is my first rom, so I still need feedback. (feel free to let me know in this thread)
What's inside?
*Built from AOSP (last sync 7/27/10)
*Stock Froyo kernel
*Rooted boot partition with "adb remount" permission
*Superuser 2.2.2 from ChainsDD
*Added busybox and bash
*Custom yellow bootanimation by JHPadu
*Update script modified by KingKlick
What I'm planning:
*LeoParts
*Tweaks from CM source
*Faster kernel (won't be oc'd)
Changelog:
7/29/10
*Initial release (alpha 1)
*updated gapps link
8/04/10
*Fixed updater-script (thanks leonnib4)
*Integrated gapps
Download: (IMPORTANT!!! READ THIS POST TO FIX SUPERUSER.APK!)
http://www.mediafire.com/file/3prssbdkm752988/WD40M0D_ALPHA2-signed.zip
Radio: (You MUST have a Froyo radio!)
4.06: http://www.mediafire.com/?kgk8rirjmgy (fastboot flash radio radio.img)
5.08: http://www.mediafire.com/?og2folywjny
(*NOTE*: Either radio will work, I have used both. If you have issues with network switching or wifi on 5.08, try 4.06)
Installation:
1. NANDROID BACKUP
2. Install radio, either via recovery or fastboot
3. Wipe data/cache, and Dalvik cache
4. Flash the WD40M0D-signed.zip via recovery
5. Enjoy!
Screenies:
{
"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"
}
Thanks to (no order): Google, dsixda, ChainsDD, JHPadu, stampere, KingKlick, Rsotbiemrptson, leonnib4
(if I left you out, please let me know)
Good to see others jump in on developing roms. Nice job on building from AOSP, appreciate the effort.
By the way, which gapps version did you post? Is that the new one as of yesterday with the new gmail?
moved
10char
jlevy73 said:
Good to see others jump in on developing roms. Nice job on building from AOSP, appreciate the effort.
Click to expand...
Click to collapse
Thanks! Let me know what you think
jlevy73 said:
By the way, which gapps version did you post? Is that the new one as of yesterday with the new gmail?
Click to expand...
Click to collapse
Nope, it's FRF91 hdpi. I'll get on that, didn't know there was a new one
Here you go, posted by Rori:
http://www.tap3w0rm.com/hosted/android/nexus-1/gapps-hdpi-FRF91-UP-signed.zip
jlevy73 said:
Here you go, posted by Rori:
http://www.tap3w0rm.com/hosted/android/nexus-1/gapps-hdpi-FRF91-UP-signed.zip
Click to expand...
Click to collapse
Thank you! I guess they're both FRF91 hdpi lol.
wdfowty said:
Thank you! I guess they're both FRF91 hdpi lol.
Click to expand...
Click to collapse
I think the only difference is the new gmail app.
Oh ok I'll look around, see what feels "new".
Has anyone flashed this yet? I'd love to hear what you guys think. Is anyone having wifi issues?
(updates with 720p and LeoParts should be live tomorrow or monday, as well as trackball wake)
FRF91 based on?
I love stock rom with root only and base mods, so your is good (except bootanimation.zip, i love default one).
It's a fresh build based on the latest AOSP source, so it should have all the FRF91 goodies.
Thanks for trying it out!
If you want a stock bootimage: adb remount, push this to /system/media, then reboot.
http://www.mediafire.com/file/sjxpzpi2hc9809x/bootanimation.zip
I just happen to love the color yellow
Update script fixed. Uploading now. Huge thanks to leonnib4 for gtalking with me at 5am Paris time!
ATTENTION! To fix SuperUser.apk, follow these instructions:
Download this: http://www.mediafire.com/file/9n9s33c81qgzabj/sh
Code:
adb remount
Code:
adb push /path/to/sh /system/bin
Code:
adb reboot
To test if it worked, type in terminal:
Code:
adb shell
I'll add this to my update.zip and upload after the weekend. Gone camping
is this as close to stock froyo rom?
also, do you think you can do one with nothing on it? just stock with all the necessaries and tweaks? and normal boot animation ?
It's pretty damn close
I think Geo411m's froyo is a better bet foor you, but it isn't aosp. It's basically the same tweaks as mine, but in a modified stock FRF91 package. Stock feel, good tweaks under the hood.
flashed yours, but i get problem connecting to wifi, keep saying obtaining IP.
Also, it won't save my APN
wdfowty said:
It's a fresh build based on the latest AOSP source, so it should have all the FRF91 goodies.
Thanks for trying it out!
If you want a stock bootimage: adb remount, push this to /system/media, then reboot.
I just happen to love the color yellow
Click to expand...
Click to collapse
could you please reupload this ?
I´m getting " Invalid or Deleted File
The key you provided for file download was invalid. This is usually caused because the file is no longer stored on Mediafire. This occurs when the file is removed by the originating user or Mediafire. " from MF
rockuman_ex said:
flashed yours, but i get problem connecting to wifi, keep saying obtaining IP.
Also, it won't save my APN
Click to expand...
Click to collapse
That's odd...I'm in the process of tweaking my source and straightening it out...I should have a beta 1 out this weekend. Little busy today though . In the mean time, try out leonnib4's LeoFroyo AOSP build. He's one of my favorite rom chefs, and it's one of my favorite roms.
s0ulstdb said:
could you please reupload this ?
I´m getting " Invalid or Deleted File
The key you provided for file download was invalid. This is usually caused because the file is no longer stored on Mediafire. This occurs when the file is removed by the originating user or Mediafire. " from MF
Click to expand...
Click to collapse
That's odd, the link works for me... Here's a link to the folder on mediafire: http://www.mediafire.com/?8yxbkhv225fd5
Thanks, I will keep an eye on your rom updates!

[ROM][WIP][AOKP] Android Open Kang Project Beta 26 for TF201[2/29/2012]

{
"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

Cannibal Open Touch v2.1 (latest update: 12/1/2012)

{
"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!

Android 5.0 Lollipop ported on LG Optimus G (GEE & GEEB)

Hello guys,
Now we can try Android 5.0 on our LG Optimus G (I'm using it on E970).
Thanks a loooooot to @Kevinjoa for his port.
Thanks to @KevTheGuy for his detailed info about this port.
***CAMERA is working fine, including 'lens blur' feature***
***Don't flash any GAPPS
***Flash the kernel (linked below)
***TWRP is the preferred recovery method
Caution:
NFC not working.
SD Card can not be mounted.
Link to the original posts:
From XDA
From another blog
*Download the latest release from HERE
*Flash this KERNEL
*Flash SuperSU to get root access.
Instructions:
1. Backup your current ROM
2. Wipe 'System', 'Data', 'Dalvik Cache' & 'Cache'
3. Flash the ROM -> Kernel -> SuperSU. One by one.
4. Wipe 'Dalvik Cache' & 'Cache'
5. Reboot & give it atleast 5 minutes for 1st boot.
Google Now Launcher (Andorid 5.0) link:
http://www.dropbox.com/sh/1u17g3me7y308mo/AADNYxVzkfVbsKPnXYjIb5_Ea?dl=0
Other Google Apps (Android 5.0) link: (Just install 'Gmail, Calendar for material design experience. Other apps already installed in the ROM)
https://www.dropbox.com/sh/m8rw7h4rytjbo7d/AAD4TOXeQuCtpoMR9z1jlA27a?dl=0
Thanks
Screenshot:
{
"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"
}
Thank you going to try it.. Need to found some fix to sd its very important
danielad200 said:
Thank you going to try it.. Need to found some fix to sd its very important
Click to expand...
Click to collapse
You are welcome . Yeah, I'm looking for that too.
is the camera working correctly on geeb?
The builds provided in the link you posted are from @Kevinjoa , and he has a thread on the Sprint LG Optimus G forums (http://forum.xda-developers.com/optimus-g-sprint/development/port-android-l-preview-gee-t2818325). There are more posts and active members there, so anyone that wants to know what's up should head there.
Also, Data doesn't work with kernelgeeb.zip on release 17 (just tested it)
You can get Data and camera to work on release 17 (or any Kevinjoa's builds i think) with this kernel (https://mega.co.nz/#!VNcRCCiK!I0cV-A1MgcEsTWsx07zVmxEDGgQIjt7DjP_dEqY_WwU) but then wifi doesnt work. Right now I'm experimenting replacing some wifi files in the rom to see if wifi works with the jollaman's kernel provided above.
I'll report back as soon as I can.
And btw thanks for creating this thread here on e970 forums, I don't think everyone knows about the Spring OG thread
EDIT2: Well turns out making a flashable zip isn't as simple as I thought xD
EDIT1: Ok so I got Wifi, Data, and camera working on release 17 with jollaman's geeb kernel for L, though autorotation gets bugged most of the times i think.
For those interested:
I took all wifi-related files in this rom (https://mega.co.nz/#!xB9xGSpK!kGCJo_GiLqRhPneqbv95xckbSmL2UMQbs7kdn0kZyAU)
from these folders:
\system\etc\wifi
\system\vendor\firmware\wlan\prima
\system\etc\firmware\prima
and copied them to the respective folders in release 17 rom.
Then I flashed the modified rom file and the jollaman kernel.
I can try to make a flashable zip of the wifi files, though i have never done it before.
And also, I read that jollaman999 is working on v12 of his kernel which would be compatible with Lollipop, so in the meantime if you want jollaman's kernel features then this is the way to go
uumeshh said:
is the camera working correctly on geeb?
Click to expand...
Click to collapse
Camera is working, including 'Lens Blur' feature.
KevTheGuy said:
The builds provided in the link you posted are from @Kevinjoa , and he has a thread on the Sprint LG Optimus G forums (http://forum.xda-developers.com/optimus-g-sprint/development/port-android-l-preview-gee-t2818325). There are more posts and active members there, so anyone that wants to know what's up should head there.
Also, Data doesn't work with kernelgeeb.zip on release 17 (just tested it)
You can get Data and camera to work on release 17 (or any Kevinjoa's builds i think) with this kernel (https://mega.co.nz/#!VNcRCCiK!I0cV-A1MgcEsTWsx07zVmxEDGgQIjt7DjP_dEqY_WwU) but then wifi doesnt work. Right now I'm experimenting replacing some wifi files in the rom to see if wifi works with the jollaman's kernel provided above.
I'll report back as soon as I can.
And btw thanks for creating this thread here on e970 forums, I don't think everyone knows about the Spring OG thread
EDIT2: Well turns out making a flashable zip isn't as simple as I thought xD
EDIT1: Ok so I got Wifi, Data, and camera working on release 17 with jollaman's geeb kernel for L, though autorotation gets bugged most of the times i think.
For those interested:
I took all wifi-related files in this rom (https://mega.co.nz/#!xB9xGSpK!kGCJo_GiLqRhPneqbv95xckbSmL2UMQbs7kdn0kZyAU)
from these folders:
\system\etc\wifi
\system\vendor\firmware\wlan\prima
\system\etc\firmware\prima
and copied them to the respective folders in release 17 rom.
Then I flashed the modified rom file and the jollaman kernel.
I can try to make a flashable zip of the wifi files, though i have never done it before.
And also, I read that jollaman999 is working on v12 of his kernel which would be compatible with Lollipop, so in the meantime if you want jollaman's kernel features then this is the way to go
Click to expand...
Click to collapse
I'm on E970 & camera, wifi worked perfectly. But thanks a lot for your detailed post. Is there any patch for SD card & NFC? Except these 2 things, this ROM is not bad!
mtatohin said:
I'm on E970 & camera, wifi worked perfectly. But thanks a lot for your detailed post. Is there any patch for SD card & NFC? Except these 2 things, this ROM is not bad!
Click to expand...
Click to collapse
Not yet. That's what's keeping me from using this rom as a daily driver :c .
I guess Jollaman's kernel v12 will fix those issues, but as far as I know, there is no word on when he's releasing it
KevTheGuy said:
Not yet. That's what's keeping me from using this rom as a daily driver :c .
I guess Jollaman's kernel v12 will fix those issues, but as far as I know, there is no word on when he's releasing it.
Click to expand...
Click to collapse
are you sure? v12 is here for geeb
http://buf.jollaman999.com/jolla-kernel_AIO-gee/
samuel3mn2 said:
are you sure? v12 is here for geeb
http://buf.jollaman999.com/jolla-kernel_AIO-gee/
Click to expand...
Click to collapse
EDIT: Well the v12 does have the option for android L kernel, but then wifi and data dont work, and still no SD card mounting : |
Wou that's new. sorry, I'll edit my post, and try it on android L release 17 to see how it goes.
according to jollaman999 camera is working and he added sd card init lines for geeb (http://forum.xda-developers.com/opt...el-jolla-kernel-cm-based-roms-t2851612/page46).
Sd card still not working with the new kernel
I am was install the kernel camera works perfectly but 3g data is dissaper
How stable is this to use as an everyday?
@mtatohin,
Nice work on the post
I tried the Android L Porting with Kernel "jolla-kernel_AIO_V12_Rev2-geeb,e970" and finding trouble in.....
---------------
1. No reboot option.
2. Camera can't connect error.
3. NFC Not working.
4. Data connection not working. Tried the steps to manually add the APN's but still problem exists.
5. SD not Mounted.
---------------
I did a clean install.
Please help for the above with any fixes.
Thank you.
P.S You are doing a Good Job.:good::good:
Is there no way to enable sad card?
Mikeandrd2292 said:
Is there no way to enable sad card?
Click to expand...
Click to collapse
As been mentioned many times in this thread, no. It might require a framework modification.
Amazing work!
Rockwig said:
As been mentioned many times in this thread, no. It might require a framework modification.
Click to expand...
Click to collapse
Is there no way to enable the happy card?
Sent from my AT&T LG Optimus G
plaster said:
Is there no way to enable the happy card?
Sent from my AT&T LG Optimus G
Click to expand...
Click to collapse
You could try decompiling the framework-res.apk and then modifying the file "storage_list.xml" in "res/xml/" and add the proper values, something like:
"<storage
android:mountPoint="/storage/sdcard1"
android:storageDescription="@string/storage_sd_card"
android:removable="true"
android:maxFileSize="4096" />"
(from https://source.android.com/devices/tech/storage/config-example.html)
after the existing entry in there.
Then you would need to recompile the .apk and add that to the device.
After that, it might show up (with the right Kernel).
Rockwig said:
You could try decompiling the framework-res.apk and then modifying the file "storage_list.xml" in "res/xml/" and add the proper values, something like:
"<storage
android:mountPoint="/storage/sdcard1"
android:storageDescription="@string/storage_sd_card"
android:removable="true"
android:maxFileSize="4096" />"
(from https://source.android.com/devices/tech/storage/config-example.html)
after the existing entry in there.
Then you would need to recompile the .apk and add that to the device.
After that, it might show up (with the right Kernel).
Click to expand...
Click to collapse
thanks for this..
will try soon..
i read that for proper ad card support we neen to mod kernel, framework-res.apk and platform.xml..
will you tell us what we need to do with kernel and platform.xml ?

[ROM][3/26/15] Pure AOSP ROM -★| 5.1.0_R3 | LMY47I | Build #6 | Proof of concept! |★-

[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

Categories

Resources