CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.3 (Jelly Bean), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
What are Nightly builds? Auto compiled builds of the latest CyanogenMod source from github. This version change each night and aren't officialy supported. If you find bugs/issues you can/must discuss here (do not submit nightlies bug on CyanogenMod issue tracker).
Downloads
Latest build: http://download.cyanogenmod.org/?device=captivatemtd
Google Apps: http://goo.im/gapps
Please use http://goo.im/devs/Hashcode/gapps/gapps-jb-20130729.zip or http://d-h.st/4vB for versions prior to 20130816
Installation
- First time flashing CM10.2 to your Captivate (or coming from another ROM)?
Root your device and install ClockworkMod Recovery.
Reboot into Recovery using 3-button-combo
Do a Nandroid backup!
WIPE (wipe data/factory reset + wipe cache partition)
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon
- Upgrading from CM7/CM9?
Do a Nandroid Backup!
WIPE (wipe data/factory reset + wipe cache partition)
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon
- Upgrading from another CM10/CM10.1/CM10.2 prior to 20130816 Build?
Do a Nandroid Backup!
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally restore /data from Nandroid Backup (the update will wipe your /data)
Optionally install the Google Addon
- Upgrading from another CM10.2 Build?
Do a Nandroid Backup!
Install the ROM from internal sdcard using ClockworkMod Recovery
Note: The partition layout of CM10.2 (beginning from 20130816 nightly) differs of that of CM10/CM10.1. The first install will wipe your /data to switch to the new layout, but after that you may use CWM to restore/backup data of CM10/10.1/10.2. More about repartitioning
Known Issues
SELinux context of some files not always being set properly
No access to DeviceParts (HSDPA settings, TV out)
Reporting Bugs
You are allowed to report bugs only in this thread. Before reporting a bug, please make sure you are running as stock as possible. This means no custom kernel, no custom framework modification, etc. If you are using any of the above modifications, please flash the rom again to get rid of the modifications before reporting.
REPORT BUGS IN THIS THREAD ONLY
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. The following is a useful format to follow. Note: If you can provide the latest night/build that the bug didn't exist, it would greatly help in tracking down what caused it.
Code:
What is your--
Phone model:
Radio (baseband):
CM version:
CM Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
CMSettings/Performance settings (other than stock):
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
FAQ
Can I request a feature?
If it is a feature in general CyanogenMod, please post the request at the CyanogenMod bug tracker.
http://jira.cyanogenmod.org
IRC
Join us on #teamhacksung-support (user channel) or #teamhacksung (developer channel)
Changelog
A rough changelog is available here:
http://changelog.bbqdroid.org/#/cm10.2/captivatemtd or http://10.2.cmxlog.com/?device=captivatemtd
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
First!!!
Sent from my SGH-I897 using xda premium
Second!!!!
Sent from my SGH-I897 using xda premium
third,thanks for dev to port 4.3 to captivate...
Sent from my SGH-I897 using xda premium
4 is an even number
Sent from my SGH-I897 using Tapatalk 4
Issue feedback:
About lock screen, can't set the lock icon to blank after you have set it..Thanks..
aliver.dun said:
Issue feedback:
About lock screen, can't set the lock icon to blank after you have set it..Thanks..
Click to expand...
Click to collapse
Works for me, set it to "Empty".
android.process.media
I am not sure if it is the gapps file or something on my device. Haven't played with 4.3 yet.
Already wiped cache, dalvik, data
Will fixing the permissions fix it all?
@PaWipt. I have the encryption unsuccessful bug on phone and my internal sdcard is unusable. In 4.2.2 I switched the vold.Fstab to boot from external sdcard. Is it possible to switch sdcards in 4.3. There is no vold anymore supposedly its only in kernel now, is it at all possible to use 4.3 on my phone.
Sent from my SGH-I897 using Tapatalk 2
Thunder22 said:
@PaWipt. I have the encryption unsuccessful bug on phone and my internal sdcard is unusable. In 4.2.2 I switched the vold.Fstab to boot from external sdcard. Is it possible to switch sdcards in 4.3. There is no vold anymore supposedly its only in kernel now, is it at all possible to use 4.3 on my phone.
Sent from my SGH-I897 using Tapatalk 2
Click to expand...
Click to collapse
Unfortunately, you'll have to compile your own kernel with the edited fstab.
nav bar
cm10.2 have option for enabling/disabling nav bar..?I don't want to edit build.prop...
The smaller alternative gapps package causes Google keep and Google music to force close. Don't know what other Google services might be affected.
Sent from my SGH-I897 using Tapatalk 4
Important information about repartitioning
The next nightly will repartition /system to be 600 MB (from the previous 400 MB) to fit the ever enlarging Android system. The repartition process is automatic, but you will lose your /data. When flashing, the first installation will fail with a warning that your /data will be wiped, simply select the .zip again and the install will proceed. If you've backed up your phone before installation (which you should), you may restore /data from backup (using "Advanced Restore" option in CWM) with no ill effect.
So does the nightly for 8/16 fix the Focal crash issues? I saw the changelog had a lot of code cleanup so not sure...I might check it out later today but in the meantime if anyone knows
DarthVesh said:
So does the nightly for 8/16 fix the Focal crash issues? I saw the changelog had a lot of code cleanup so not sure...I might check it out later today but in the meantime if anyone knows
Click to expand...
Click to collapse
Give it a try and let us know
Alrighty!
Did a clean flash and it still does the same thing...focal closes when trying to switch to any other mode (i.e. panorama, video camera, picsphere). I can take on or two regular pics without it closing. Browsing and changing settings is no issue.
Otherwise, system run super smooth, apps install and run with no issue. No fc or random reboots (yet )
Sent from my Amazon Kindle Fire using xda app-developers app
Do anyone have complied kernel with edited fstab? Please help, I dont have knowledge about linux, and dont have any linux machine. Or can anyone tell me how to do on windows. Many thanks
Gửi từ SGH-I897 của tôi bằng cách sử dụng Tapatalk 2
doubt on partition
pawitp said:
Important information about repartitioning
The next nightly will repartition /system to be 600 MB (from the previous 400 MB) to fit the ever enlarging Android system. The repartition process is automatic, but you will lose your /data. When flashing, the first installation will fail with a warning that your /data will be wiped, simply select the .zip again and the install will proceed. If you've backed up your phone before installation (which you should), you may restore /data from backup (using "Advanced Restore" option in CWM) with no ill effect.
Click to expand...
Click to collapse
sorry for noob question.. is it partitioning internal SD..?
ajeesh vijayan said:
sorry for noob question.. is it partitioning internal SD..?
Click to expand...
Click to collapse
It moves some space from /data to /system.
I'm new to custom android on phones I have Transformer Infinity with TWRP CM 10.2 but what does I need to know of baseband and modems? Do I need to update them from stock. I'm planing on putting CyanogenMod on my friends Samsung Captivate SGH–I897.
Related
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
CHANGELOG for 2.6.1.0:
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks
CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
-Can encrypt a backup to prevent theft of private data from your backup files
-Updated graphics / icon courtesy of shift
-Updated exFAT to latest commits
-Fixed a problem with Samsung TouchWiz decryption
-Update SuperSU binary
-Fixed saving of backup partitions list
-Fixed saving of last used zip install folder
-Fixed backup of datadata on devices that use a separate partition for datadata
-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
-Fixed some problems with partitioning a SD card
-Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
installed last night. already liking it a lot! no problems so far.
I also am enjoying this. No issues to report. I am waiting for some loving for my xoom. Great job guys!
Amazing work as always, love it guys!
Finally decided to give twrp a go after reading so many praises about it. Very nice... Very fast!
Hmmm. Cant believe I'm the only one where Capacitive keys don't light up. Any Ideas? Love the hell out of this Recovery.
this recovery is full of win!
Flashed yesterday, no problems throughout the day.. Now my phone is shutting down and rebooting into recovery immediately after turning it on.. Any fix?
stevey5036 said:
Flashed yesterday, no problems throughout the day.. Now my phone is shutting down and rebooting into recovery immediately after turning it on.. Any fix?
Click to expand...
Click to collapse
Has nothing to do with the recovery, been running it since the first day and zero problems
False alarm.. The OTA was pushed to my phone (again) and would reboot the phone to try to install via stock recovery but it obviously wasn't there. Sorry.
I flashed this recovery yesterday and everything works fine. I love the touch screen working so great. Only one issue. I'm unable to mount usb storage through recovery nor my ROM. I'm currently running gingeritis 3D and also tried with ICS MIUI, I couldn't mount on either one. I'm wondering if there is anything I can do to get my computer to recognize my phone. Thank you in advance.
Sent from my rabbit hole using my carrotbolt.
Me likey. Thanks for this!!!!
droid future said:
I flashed this recovery yesterday and everything works fine. I love the touch screen working so great. Only one issue. I'm unable to mount usb storage through recovery nor my ROM. I'm currently running gingeritis 3D and also tried with ICS MIUI, I couldn't mount on either one. I'm wondering if there is anything I can do to get my computer to recognize my phone. Thank you in advance.
Sent from my rabbit hole using my carrotbolt.
Click to expand...
Click to collapse
Just shooting in the dark here, but have you tried a different kernel?
USB Mass Storage works for me with TWRP2 & LiquidSmooth 3.2.
What if I want to go back to CWR, do I just use rom manager and reflash the recovery again. Can I restore a nandroid from CWR with twrp 2.0. This looks awesome. Like to try it only if I can back to CWR.
Sent from my ADR6400L using Tapatalk
PeteLopez197 said:
What if I want to go back to CWR, do I just use rom manager and reflash the recovery again. Can I restore a nandroid from CWR with twrp 2.0. This looks awesome. Like to try it only if I can back to CWR.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
I used ROM Manager to reflash CWM.
The way TWRP backs up the rom seems to be different than CWM (hooray compression!), so you can't restore a CWM Nandroid directly. At least, not that I've noticed.
So i may have bricked my phone...
Flashed TWRP without a rom installed. So it rebooted to the white HTC screen and obviously just hung there. Pulled the battery, removed the IMG file from my SD card using my computer card reader, put the card back in, put the battery back in and now it won't turn back on, dead. So uhhh was that a cardinal sin or is my phone salvageable?
twrp works great for me. its very fast. made a backup of lgb 3.2 in about 2 minutes!
I just flashed this. It worked for me. Did u make sure you renamed the zip and put it root of sdcard. This recovery has potential. I do like using the touch screen instead of my hardware, especially if volume keys are not responsive.
Sent from my ADR6400L using Tapatalk
GatoEnFuego said:
So i may have bricked my phone...
Flashed TWRP without a rom installed. So it rebooted to the white HTC screen and obviously just hung there. Pulled the battery, removed the IMG file from my SD card using my computer card reader, put the card back in, put the battery back in and now it won't turn back on, dead. So uhhh was that a cardinal sin or is my phone salvageable?
Click to expand...
Click to collapse
So the twrp IRC chat was extremely helpful in getting my phone working again. Great group of guys! Lesson learned, if you're going to flash a new recovery make sure you have a working ROM installed or else you can get caught in a bind if you pull the battery during the white HTC screen.
And if you do, make sure you lick your terminals...
I really like the concept of this recovery (touchscreen instead of hardware keys), but I feel it still needs some work to become "idiot proof", and needs to be more thorough.
For example, I decided to try restoring a backup of Skyraider Zeus, coming from Gingeritis1.1. After it completed and I rebooted into the system, there were all sorts of "leftovers" from the Gingeritis ROM packed in with Skyraider Zeus.
In other words, the recovery doesn't format the partitions prior to restoring the backup. This could lead to some serious issues for people when restoring backups of one ROM from another without manually formatting everything first.
Sent from my ADR6400L using XDA App
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
CHANGELOG for 2.6.1.0:
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks
CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
-Can encrypt a backup to prevent theft of private data from your backup files
-Updated graphics / icon courtesy of shift
-Updated exFAT to latest commits
-Fixed a problem with Samsung TouchWiz decryption
-Update SuperSU binary
-Fixed saving of backup partitions list
-Fixed saving of last used zip install folder
-Fixed backup of datadata on devices that use a separate partition for datadata
-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
-Fixed some problems with partitioning a SD card
-Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
This looks interesting
I hope that many of you find this recovery very useful. I spent many days bugging the hell out of dees_troy on getting this up and running(sorry about that dees). But I my opinion the features that this recovery offers is much more than any other than what the A500 currently has. Please check it out and if you like it and would consider donating, please visit team win website. These guys spent a lot of time into this recovery and have good plans for future stuff. Enjoy!
Sent from my Sensation using Tapatalk 2
Can someone please post the flashable zip file for this? I can't install from GooManager, it always abort installation.
Does this recovery support flash from USB?
Sent from my A500 using Tapatalk 2
this recovery don't support flexreaper r11 rom (Picasso).
"Status aborded 7"
Sent from my A500 using Tapatalk 2
Does this recovery support the extendedcommand file?
micky387 said:
this recovery don't support flexreaper r11 rom (Picasso).
"Status aborded 7"
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
I was wondering why it didn't install for me. Hope the team will fix this issue.
because build prop is false with flexreaper (i suppose)
who can change recovery (.zip) for flexreaper ??
thanks
Sent from my A500 using Tapatalk 2
micky387 said:
this recovery don't support flexreaper r11 rom (Picasso).
"Status aborded 7"
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
Guys Status 7 Aborted errors are usually bad downloads. Please keep trying and it should go through.
i'm downloaded 5 times but same errors
Sent from my A500 using Tapatalk 2
10507 said:
Can someone please post the flashable zip file for this? I can't install from GooManager, it always abort installation.
Does this recovery support flash from USB?
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
This flashable zip has been tested on cwm-based recovery's 1.3.something and 1.7 by the man who's name may not be named.
I see no reason why it won't work on any ROM as recovery is independant of it.
Edit: Ofc only tested on my iconia a500. Just saying.
That's work with your .zip but like micky387, before I tried 5 times with GooManager and the installation didn't work.
elborak said:
Does this recovery support the extendedcommand file?
Click to expand...
Click to collapse
We have ported OpenRecoveryScript over to ClockworkMod Recovery and have submitted the code to CyanogenMod for inclusion so that any app will be able to take advantage of the same scripting support in ClockworkMod Recovery too.
Some may now be wondering why we didn't just use the "extended commands" feature that already exists in ClockworkMod Recovery. Unfortunately, recent builds of ClockworkMod Recovery have been locked down to only work with ROM Manager, so other apps like GooManager are unable to make use of this feature.
Click to expand...
Click to collapse
Some instructions on the OpenRecoveryScript would be much appreciated. Does someone have a link?
Taptalked u see
Reno_kun said:
That's work with your .zip but like micky387, before I tried 5 times with GooManager and the installation didn't work.
Click to expand...
Click to collapse
So it worked, and now you have twrp 2.1.0? On which rom? To be honest, i couldn't get the gooapp to do the work for me, that's why i made this zip (based on thor's zip as template, who's ics rom i am running also)
Taptalked u see
Yes I have twrp 2.1.0 now instead of RA-Iconia 3.16. I use Flexreaper 11.
You made a good job with this zip because it's very easy to install it and thanks to the team win for this recovery !
May have missed it, but in the wipe area, there is no wipe flexrom, some times that needs to be wiped when there are problems.
Also I forgot to look around, but can /data/media be toggled so when you wipe data that data/media can be wiped also?
Sent from my A500 using Tapatalk 2
thanks zatta.
Work fine now with your .zip.
Thank you very much
Best regards
Sent from my A500 using Tapatalk 2
Looks real nice. Just take care of the couple little things mentioned in previous posts and it will be great. (Ability to toggle full data backup and restore/wipe data/media, and ability to format flexrom)
Sent from my A500 using xda premium
BakaNeko59 said:
Looks real nice. Just take care of the couple little things mentioned in previous posts and it will be great. (Ability to toggle full data backup and restore/wipe data/media, and ability to format flexrom)
Sent from my A500 using xda premium
Click to expand...
Click to collapse
Have you tried toggling data/media yourself?
Can someone with twrp already installed try this out for us?
Thanks all
Sent from my NexusHD2 using Tapatalk
BakaNeko59 said:
Looks real nice. Just take care of the couple little things mentioned in previous posts and it will be great. (Ability to toggle full data backup and restore/wipe data/media, and ability to format flexrom)
Sent from my A500 using xda premium
Click to expand...
Click to collapse
Flexrom format we decided that was not really needed. I have been using twrp for almost 2 months now and have not had an issue. If a rom does anything with flexrom which are only stock based roms, they format flexrom during the install process. These are features that can be added with a theme as well. Will talk with team win tomorrow.
Sent from my Sensation using Tapatalk 2
FFU5y said:
What is OpenPDroid?
OpenPDroid is a set of modifications to the Android framework and libraries which allows fine-tuning of the data which applications are able to retrieve about your device, your account, your messages, and more. Specifically, it is a Privacy service provider (using the PDroid 1.51 interface) forked from CollegeDev's PDroid 2.0, which is itself an extension of Syvat's PDroid.
Click to expand...
Click to collapse
Again, this is not my work. I'm using the CM10.1 work that XpLoDWiLD/Entropy512 started, and the patches that OpenPDroid provides.
If you want to give thanks/beer-money, the people below deserve it more. Go to their threads and give a thanks! or donation
Sources:
CM10.1 port from XpLoDWiLD/Entropy512, ...
OpenPDroid by FFU5y, Mateor and wbedard, ...
PDroid by CollegeDev
Why:
Pdroid/openpdroid won't be included in "official" CyanogenMod, but since our default Oppo firmware has a similar feature, I've decided to kang it
How To Use:
Basically, treat this ROM like any other CM10.1 nightlies ROM. Whichever method you use to handle CM10.1 ROMs works for this ROM as well.
Download ROM to device, Download gapps.
Reboot to recovery, backup current ROM
Wipe dalvik-cache/system/data
Flash new ROM, then flash gapps. Then wipe dalvik-cache/system/data
Boot into android. Download PDroid or PDroid Manager to edit the settings.
How to reset to old ROM
Reboot to recovery, wipe, restore from your backup
If you want to update this MOD on your own
All of the changes to the underlying CM10.1 sources: Simply apply the patches and build from scratch. Isn't that easy? You can do it too. Here's a guide on how to setup a build environment on ubuntu and how to build CM from scratch.
You could also patch an existing pre-built ROM, but I haven't tried that.
Download:
Release on 04/28/2013
OpenPdroid v1.0.1, CM10.1 pull from 4/28/2013
Click to expand...
Click to collapse
Next Steps:
Flashable Zip instead of a full build (so that people can install latest CM10.1 nightlies, then flash OpenPDroid zip.
If anyone wants to get started, here's a source: Auto-patcher by mateorod http://forum.xda-developers.com/showthread.php?t=1719408
Most of the work is already done for you, just make that flashable zip!
No Access:
Modified with my own data:
If I understand correct this is a better alternative then lbe save guard?
A flash able zip would be awesome
Verstuurd van mijn Find 5 met Tapatalk
CoopZor said:
If I understand correct this is a better alternative then lbe save guard?
A flash able zip would be awesome
Verstuurd van mijn Find 5 met Tapatalk
Click to expand...
Click to collapse
lbe vs pdriod (you'll probably want to use pdriod with a firewall like DroidWall)
http://forum.xda-developers.com/showpost.php?p=24733115&postcount=4
could make a flashable zip when I get home... (or you could make the flashable zip yourself, no programming required: http://forum.xda-developers.com/showthread.php?t=1719408 )
overall, I've tested it, it seems to block apps properly.... some apps do crash because they don't handle the "random" info generator properly (if you manually set it to some random number, they won't crash) --> this is why Cyanogenmod won't ever integrate something like this -- it'll create too much confusion
if you disable "Network Info", some apps will actually say "no internet connection" and stop connecting (Facebook, TuneIn Radio, Amazon App store)...wonder if it'll save battery (since those apps won't connect to internet in the background to run), or waste battery (app will keep polling the "blocked" connection, wasting battery)
[ROM] Evervolv | 6.0.0p1 [AOSP Marshmallow 6.0.1] [3.4 kernel] [nightlies] WIFI & 4G
For those that don't know what evervolv is, Evervolv is an AOSP (Android Open Source Project) rom. We're fully open sourced and encourage it with no restrictions. The work put into this rom is community driven and and Evervolv Project is made up of numerous members and contributors.
Right now the current source we are working on is Marshmallow(Android 6.0.1).
Current version: 6.0.0p1
Current Items not working/Buggy
Updated 07-13-2016
WIFI MODEL
Camera
4G list
Camera
hotspot -- requires reboot if you turn hotspot on it kills network interface.
You tell me what you find.
Click to expand...
Click to collapse
Evervolv Github: https://github.com/Evervolv
Evervolv Gerrit: http://review.evervolv.com/
Evervolv website: http://www.evervolv.com/
Twitter: https://www.twitter.com/wbellavance
IRC: #evervolv
Click to expand...
Click to collapse
[GPL Compliance]
Kernel Source
Click to expand...
Click to collapse
[Download]
[Unoffical TWRP Builds]
2.8.7.0 TWRP recovery with MTP support and F2FS. http://evervolv.com/get/FLINTMAN-TWRP-touch-data_media-SELINUX-f2fs-2.8.7.0-12-17-15.zip Fixed up reboot to recovery in recovery
3.0.0.0 TWRP recovery with MTP support and F2FS. http://evervolv.com/get/FLINTMAN-TWRP-touch-data_media-SELINUX-f2fs-3.0.0.0-2-07-15.zip Updated to 3.0.0.0
3.0.2.0 TWRP recovery with MTP support and F2FS. http://evervolv.com/get/FLINTMAN-TWRP-touch-data_media-SELINUX-f2fs-3.0.2.0-4-27-16.zip Updated to 3.0.2.0
**REQUIRES 800MB System Partition MIN.
WIFI MODEL TEST BUILDS
WIFI MODEL NIGHTLIES
http://evervolv.com/devices/tenderloin NIGHTLIES
4G MODEL TEST BUILDS
4G MODEL NIGHTLIES
http://evervolv.com/devices/tenderloin4g NIGHTLIES
These are the gapps im using. http://opengapps.org/?api=6.0&variant=nano gapps that seem to work the best with marshmallow UPDATED 11-28-15
Click to expand...
Click to collapse
****************************************PLEASE READ**************************************************************
F2FS installs. If you want to try out F2FS you will have to wipe your data parition which includes your internal sd card. Some steps if you want to backup your data. PLEASE NOTE DON'T DO THIS IF YOU DON'T KNOW WHAT YOU ARE DOING CAN CAUSE ISSUES OR LOST DATA. IF YOU DON'T DO THIS IT WILL STILL WORK WITH THE CURRENT FORMAT EXT4.
-- Flash the F2FS compatible TWRP Recovery
-- Boot into Recovery
-- Backup > Data
-- Save your internal SD card by transfering to your PC or if you have room your external_sd
-- Wipe > Advanced Wipe > Data > Repair or Change File System > Change File System > F2FS
-- Wipe > Advanced Wipe > Cache > Repair or Change File System > Change File System > F2FS
-- Copy the saved SD card content back to your device
-- Restore > Choose backup > Data (the warning about ext4 backup doesn’t matter)
-- Advanced > Fix Permissions
-- Wipe > Advanced Wipe > Cache & Dalvik Cache
-- Flash the 2-12-15 test build and gapps to ensure you got them
-- Reboot to system
Click to expand...
Click to collapse
[UPGRADE(Dirty Flash)]
I have noticed if you dirty flash on first boot you may experience a little lag or possible reboot. After it settles down no issues. Not sure if its art related on upgrades or what. Its hard to pin point as it only happens once and smooth after that. Recommend after an upgrade let it settle in before playing hard.
Thanks
Click to expand...
Click to collapse
FIrst boot is a little slow but that is due to art. I always recommend a clean install when upgrading but if you feel luck. Backup and try a dirty flash. If you have issues run a clean install and if you still have issues please post with a logcat. You can upload via bugreport in the toolbox under settings. If going from a differnt rom other then evervolv lollipop always clean install. ALWAYS REMEMBER TO BACKUP its important if you don't want to loose anything
Click to expand...
Click to collapse
NOTE: NEED a clean install if moving from a previous version and or another ROM.
Flashing from cm or any other ROM will require a clean install, dirty flashes can cause random reboots and random errors
[Disclaimer]
I am not responsible for bricked devices, lost data, etc, etc. You all know the drill. BACKUP BACKUP BACKUP
Click to expand...
Click to collapse
[Special Thanks]
i would like to thank Flemmard, Jcsullins, Dorregaray, Invisiblek, Milaq, and anyone else that helped to make this happen. More great work to come.
Mitchbaria --for a 4g model to start in on this
EricBlade --for my second 4g model to start in on this for Marshmallow
Colchiro-- For a spare Touchpad WIFI to be able to test on one and develop at the same time
Click to expand...
Click to collapse
Gapps are touchy in marshmallow. Ill post a link soon. You can try different ones if yiu want. Still working a bunch of issues but it is usable
Sent from my Nexus 6 using XDA Free mobile app
Is it compatible with jcsullins toolbox?
yasingedik said:
Is it compatible with jcsullins toolbox?
Click to expand...
Click to collapse
Unsure. It should be i updated the files for it. If you had lollipop just factory reset and install via recovery.
Sent from my Nexus 6 using XDA Free mobile app
Nice work ?
Sent from my Touchpad using XDA Free mobile app
flintman said:
Forced those that don't know what evervolv is, Evervolv is an AOSP (Android Open Source Project) rom. We're fully open sourced and encourage it with no restrictions. The work put into this rom is community driven and and Evervolv Project is made up of numerous members and contributors.
Right now the current source we are working on is Marshmallow(Android 6.0.0).
Current version: 6.0.0p1
Current Items not working/Buggy
****************************************PLEASE READ**************************************************************
NOTE: NEED a clean install if moving from a previous version and or another ROM.
Flashing from cm or any other ROM will require a clean install, dirty flashes can cause random reboots and random errors
Click to expand...
Click to collapse
Anyone notice the Evervolv update? And let me know what you think. It needed a change and Elginsk8r took that on and came up with something new. 8)
Sent from my Nexus 6 using XDA Free mobile app
Quick feedback: I flashed your twrp, than rom and than this gapps and keyboard won't work. going to try with the gapps you linked.
update: clean installed your rom and gapps and keyboard works, thanks
yasingedik said:
Quick feedback: I flashed your twrp, than rom and than this gapps and keyboard won't work. going to try with the gapps you linked.
update: clean installed your rom and gapps and keyboard works, thanks
Click to expand...
Click to collapse
Ya some gapps keyboard doesnt work.
Sent from my Nexus 6 using XDA Free mobile app
Thanks Flintmann! You rocked it again!
This release is off to a great start! I can do w/o the BT and camera for now. I just love it's got a booting and operational M on here.
Thanks finding little bugs as i play around with it. Ill be updating issues as i go. If anyone notices any as they play around and don't see it in the list please let me know. Marshmallow has been a challenge but which version hasn't been 8)
Cool feature in marshmallow is multi window. Need to enable it under development options. Once enabled click on the recent apps and you can set where you want thag screen. When u click recebt apps you will see [ ]. Click it and set the position of that app.
Sent from my Nexus 6 using XDA Free mobile app
flintman said:
Cool feature in marshmallow is multi window. Need to enable it under development options. Once enabled click on the recent apps and you can set where you want thag screen. When u click recebt apps you will see [ ]. Click it and set the position of that app.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
the multiwindow is AWESOME!
---------- Post added at 12:30 AM ---------- Previous post was at 12:25 AM ----------
I caught a small issue w/ my Wi-Fi after turning on multi window. I followed w/ a hot reboot because the recent apps was not allowing me to choose a layout at first and I didn't want to go through a cold reboot. I'll get logs asap. Then I'll do a hard reboot to see how that works out.
UPDATE: I uploaded my logs via the bug report. I'll do a hard reboot and let you know if I see anything similar again Flintman
I just added my personal email account to the built in mail app and as it was downloading my mail, it repeatedly FCed on me. I will do a reboot and see if the FCs stop. Just thought I'd mention that before I go hit the sack for a few hours. FYI, the type of account was an IMAP account.
flintman said:
Ya some gapps keyboard doesnt work.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
maybe the gapps from rgib CM13 (note 8) could be a lead. (because they work like a charm on my tablet with cm13)
Amazing first MM. The HPTP runs great on Marshmellow. Great job Flintman!!
Sent from my Touchpad using XDA Premium HD app
I've been playing with the multi window more and I find that it's still a bit temperamental. Some times it won't let me tap on any layout options when I hit the recent apps icon. I'll keep the logs coming as I play with this, but I am very pleased with how this has started so far! Thanks Flintman and EV team for such hard work to teach our "old" TPs new and amazing tricks with M!
MM Screen rotation
Got a couple of Keyboard double clicks when entering details for the 1st time (Wifi selection page) and also screen rotation doesnt appear to be functioning..
If i reboot with the TP held in portrait, it come up in portrait but wont rotate to landscape when at the home screen.. likewise, Boot up on landscap, no rotation to portrait.. Setting in "Display" is set to rotate contents.. There doesnt appear to be the older 90,180,270 degree etc
Excellent work @flintman... Thank you
The native e-mail client continues to force close when it connects to the IMAP mail server for my account to pull down new mail. This is despite multiple reboots.
Thanks flintman for a great test build of MM for TP. Most of the apps run with no problems. But the Titanium Backup and facebook messenger are not working. The logcat is attached for your review. Thanks!
For those that don't know what evervolv is, Evervolv is an AOSP (Android Open Source Project) rom. We're fully open sourced and encourage it with no restrictions. The work put into this rom is community driven and and Evervolv Project is made up of numerous members and contributors.
Right now the current source we are working on is Nougat(Android 7.0.0).
Current version: 7.0.0p1
Current Items not working/Buggy
Updated 10-27-2016
WIFI MODEL
Camera
Wifi cuts out for some.
4g MODEL
Camera
Wifi cuts out for some.
You tell me what you find.
Click to expand...
Click to collapse
Evervolv Github: https://github.com/Evervolv
Evervolv Gerrit: http://review.evervolv.com/
Evervolv website: http://www.evervolv.com/
Twitter: https://www.twitter.com/wbellavance
IRC: #evervolv
Click to expand...
Click to collapse
[GPL Compliance]
Kernel Source
Click to expand...
Click to collapse
[Download]
[Unoffical TWRP Builds]
3.0.2.0 TWRP recovery with MTP support and F2FS. http://evervolv.com/get/FLINTMAN-TWRP-touch-data_media-SELINUX-f2fs-3.0.2.0-09-06-16.zip Updated to 3.0.2.0
3.0.2.0 TWRP recovery with MTP support and F2FS. http://evervolv.com/get/FLINTMAN-TWRP-touch-data_media-SELINUX-f2fs-3.0.2.0-09-11-16.zip Made a little smaller then previous 9.2mb
**REQUIRES 1312MB System Partition.
This is very easy to do via JCSullins Toolbox
WIFI MODEL TEST BUILDS
http://evervolv.com/get/ev_tenderloin-7.0-testing-2016.10.05.zip Ok this isn't block style install which allows changing the size of system to what you want and use all of it. Its a slower install time but not much slower then before. Also some BT changes that allow me to use my headset. Test out BT and let me know. I'm still testing myself. Another change is root is disabled by default. You will have to go into Evervolv toolbox to enable root.
http://evervolv.com/get/ev_tenderloin-7.0-testing-2016.10.27.zip Behind the scene updates along with fixing BT speakers HOPEFULLY 8)
4g MODEL TEST BUILDS
http://evervolv.com/get/ev_tenderloin4g-7.0-testing-2016.09.07.zip
http://evervolv.com/get/ev_tenderloin4g-7.0-testing-2016.09.17.zip Includes all above
http://evervolv.com/get/ev_tenderloin4g-7.0-testing-2016.10.27.zip Behind the scene updates along with fixing BT speakers HOPEFULLY 8)
These are the gapps im using. http://opengapps.org/?download=true&arch=arm&api=7.0&variant=pico gapps that seem to work the best with Nougat UPDATED 09-06-16
Click to expand...
Click to collapse
****************************************PLEASE READ**************************************************************
F2FS installs. If you want to try out F2FS you will have to wipe your data parition which includes your internal sd card. Some steps if you want to backup your data. PLEASE NOTE DON'T DO THIS IF YOU DON'T KNOW WHAT YOU ARE DOING CAN CAUSE ISSUES OR LOST DATA. IF YOU DON'T DO THIS IT WILL STILL WORK WITH THE CURRENT FORMAT EXT4.
-- Flash the F2FS compatible TWRP Recovery
-- Boot into Recovery
-- Backup > Data
-- Save your internal SD card by transfering to your PC or if you have room your external_sd
-- Wipe > Advanced Wipe > Data > Repair or Change File System > Change File System > F2FS
-- Wipe > Advanced Wipe > Cache > Repair or Change File System > Change File System > F2FS
-- Copy the saved SD card content back to your device
-- Restore > Choose backup > Data (the warning about ext4 backup doesn’t matter)
-- Advanced > Fix Permissions
-- Wipe > Advanced Wipe > Cache & Dalvik Cache
-- Flash the 2-12-15 test build and gapps to ensure you got them
-- Reboot to system
Click to expand...
Click to collapse
[UPGRADE(Dirty Flash)]
I have noticed if you dirty flash on first boot you may experience a little lag or possible reboot. After it settles down no issues. Not sure if its art related on upgrades or what. Its hard to pin point as it only happens once and smooth after that. Recommend after an upgrade let it settle in before playing hard.
Thanks
Click to expand...
Click to collapse
FIrst boot is a little slow but that is due to art. I always recommend a clean install when upgrading but if you feel luck. Backup and try a dirty flash. If you have issues run a clean install and if you still have issues please post with a logcat. You can upload via bugreport in the toolbox under settings. If going from a differnt rom other then evervolv lollipop always clean install. ALWAYS REMEMBER TO BACKUP its important if you don't want to loose anything
Click to expand...
Click to collapse
NOTE: NEED a clean install if moving from a previous version and or another ROM.
Flashing from cm or any other ROM will require a clean install, dirty flashes can cause random reboots and random errors
[Disclaimer]
I am not responsible for bricked devices, lost data, etc, etc. You all know the drill. BACKUP BACKUP BACKUP
Click to expand...
Click to collapse
[Special Thanks]
i would like to thank Flemmard, Jcsullins, Dorregaray, Invisiblek, Milaq, and anyone else that helped to make this happen. More great work to come.
Mitchbaria --for a 4g model to start in on this
EricBlade --for my second 4g model to start in on this for Marshmallow
Colchiro-- For a spare Touchpad WIFI to be able to test on one and develop at the same time
Click to expand...
Click to collapse
Biggest thing is need to update system size and use new recovery.
Alot of features have been turned on yet this is ALPHA its not a daily. I released for all to play with and we will grow on this. 8)
TP Toolbox v0.42 Complete Data Reset Guide with Updated Links
NOTICE: THIS THREAD WAS ABANDONED BY THE OP, BUT I WILL KEEP THE LINKS IN THIS POST UPDATED
This guide is for a complete data reset to start from scratch. You should only need to use TP Toolbox to either adjust partition sizes, or start from scratch if any partitions got corrupted or you get errors while adjusting partitions or installing new ROMs.
If you end up having to start from scratch in TP Toolbox v0.42, follow these steps:
- Download a TP Toolbox Compatible ROM
- Download a TP Toolbox Compatible GApps
- Download a TP Toolbox Compatible TWRP
I recommend keeping those files on your PC hard drive so you can always re-use them in the future if needed.
1. In the TP Toolbox v0.42 main menu, do a 'Complete Data Reset' to start from scratch
2. Select the 'Install Android' option from the main menu
3. Copy the 3 above files from your PC to the "tpinstall" folder after the TP is mounted
4. When given the option to adjust partition sizes, increase the System partition to at least 1312mb
5. Finish install, and reboot to TWRP
6. While in TWRP, flash the newer 3/24/17 TWRP 3.1.0.0
7. Reboot into the new TWRP that you just flashed
8. In TWRP advanced wipe menu, wipe the System partition
9. While still in TWRP, flash the Wifi model ROM or the 4G model ROM along with some OpenGapps
AlwaysLucky said:
Great work @flintman! Will test out now! Many thanks on your continued attention on the tenderloin!
PS: Your OP says you are working on "Marshmallow(Android 7.0.1)"
Click to expand...
Click to collapse
Missed that one. Remember to upsize your system partition.
Wow.
Thank you flintman for giving our touchpad a treat of fresh nougat.
I increased the system size to 1.5 gb several days ago and waited for your nougat. Now downloading it...
Edit: are we required to use the new twrp recovery in the OP? I have twrp 3.0.2 with an older time stamp.
BIG THANKS @flintman
googlephone said:
Wow.
Thank you flintman for giving our touchpad a treat of fresh nougat.
I increased the system size to 1.5 gb several days ago and waited for your nougat. Now downloading it...
Edit: are we required to use the new twrp recovery in the OP? I have twrp 3.0.2 with an older time stamp.
Click to expand...
Click to collapse
Yes use the one in the op you will get an error (not fatal) on older recoveries.
Sent from my Nexus 6 using XDA-Developers mobile app
flintman said:
Remember to upsize your system partition.
Click to expand...
Click to collapse
I actually enlarged the System partition to 1500mb just to be safe, and am testing the Nano OpenGApps. So far everything works great! I've installed several different apps, and all seem to work just fine with no FCs. I also get to test out the apps I'm developing on the Nougat OS, so that's really nice. I do miss CM theme support and the Evervolv toolbox, but I promise to be very patient; as I know those are out of your hands. :angel: I also flashed AdAway to the system and that is also functioning fine.
EDIT: For those who would like a flashable zip of AdAway to flash it to the System, I attached it to this post.
I dirty flashed over evervolve 6.0.1 and it boots up in about 6 minutes.
It feels much faster than 6.0.1 and the multi window is amazing.
There is no evervolve toolbox tab in setting, so there is no option to change the cpu frequency.
In the OP, it mentioned evervolve toolbox for bug report. Is the toolbox supposed to be absent?
Edit: second question: where do we control root permissions?
googlephone said:
I dirty flashed over evervolve 6.0.1 and it boots up in about 6 minutes.
It feels much faster than 6.0.1 and the multi window is amazing.
There is no evervolve toolbox tab in setting, so there is no option to change the cpu frequency.
In the OP, it mentioned evervolve toolbox for bug report. Is the toolbox supposed to be absent?
Edit: second question: where do we control root permissions?
Click to expand...
Click to collapse
Im surprised a dirty flash worked. As stated above not alot of features have been added but the toolbox access at the moment is only though the launcher you should see toolbox just like any other app. Root permission is controlled though the toolbox as well.
How can we promote this thread to the xda news portal? Flintman deserves a spot there.
Edit: there is no thanks button any more on XDA? I can not find that button.
Edit: now the thanks button shows up. Weird.
AlwaysLucky said:
I actually enlarged the System partition to 1500mb just to be safe, and am testing the Nano OpenGApps. So far everything works great! I've installed several different apps, and all seem to work just fine with no FCs. I also get to test out the apps I'm developing on the Nougat OS, so that's really nice. I do miss CM theme support and the Evervolv toolbox, but I promise to be very patient; as I know those are out of your hands. :angel: I also flashed AdAway to the system and that is also functioning fine.
Click to expand...
Click to collapse
Toolbox is located in the launcher for now. All features will be added back little by little. 8) trying to get a good base and then we move on.
flintman said:
Toolbox is located in the launcher for now.
Click to expand...
Click to collapse
OMG, I'm so blind. Sorry about that. :silly:
@ flintman
how is your general partitionsetup, not just system.
schwatter said:
@ flintman
how is your general partitionsetup, not just system.
Click to expand...
Click to collapse
1312 for system, 1 gig for external and rest in data. I
Sent from my Nexus 6 using XDA-Developers mobile app
flintman said:
1312 for system, 1 gig for external and rest in data. I
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Ok, it looks like my setup. I find in touchpad toolbox the partition "media". So "media is like "external" right?
And about "cm-cache", i think i set it up in the past from 200 to 1000. Is that better? So normally yes because
of more. But i don't know how android handle it. That's why i ask.
Hey gang, using tptb I placed jcs rom and the gapps and used jc twrp recovert. it failed. ant pointers? thanks..
deafasheck said:
Hey gang, using tptb I placed jcs rom and the gapps and used jc twrp recovert. it failed. ant pointers? thanks..
Click to expand...
Click to collapse
If you've switched to f2fs, then that's the reason. TPTB is unfortunately incompatible with it.
Hi didn't switch to f2fs. I downloaded the files and used pc tptb for the installation.. Currently I am trying to get wifi working better. I installed the job new rom and cm 12 going to the WiFi forum. I have just bought a new one that's 16 gig, it has WiFi access but falters..
But on this issue I will try to get it going on the other TouchPad see if it works..
Amazing stuff
Great job as always. Flintman, you have always been the first ou with the new release of Android since i have had a toucpad for the last few years. Congratulations again and thanks for all your work.
And Multi screen works too!