Related
Version 5.x of xtrROM builds on the heritage and continues the evolution of this fast reliable feature rich ROM that you as the user can customize to enhance your Droid Eris Android experience! This ROM has a very Vanilla feel but is based on the core HTC framework to offer the best relibility possible in a custom ROM. I am reliant on my phone at work so stability and consistent quality of user experience are the top priorities for xtrROM. If you like the HTC Sense experience then be sure to check out xtrSENSE and if you would like a "pure" Vanilla 2.1 AOSP experience then be sure to try VanillaASOP.
{
"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"
}
Base xtrROM Features:
All the goodness of Android 2.1 with Root access and Superuser permissions
A very Android ASOP Vanilla feel from removing HTC "bloat"; while embracing reliable HTC sync and app coordination
Fully odex to save as much "usable" internal space as possible and provide faster boot times
Over clock support - default to 710400
Many reliable "hacked" tweaks such as: Collin_ph battery tweak, some Flash support, OpenGLES 1.1, new Android Market, wired tether, etc...
Included opensource GScript app allows you to easily turn on/off core ROM settings (CPU OC, Apps2sd, Cache2sd, JIT, etc...) with one-click
Live wallpapers as a separate module you can enable
Full Cache2cache support (see details below) - better use of the /data/ and /cache/ file blocks which opens up unused internal storage allowing you to install close to 100 apps without using Apps2sd!
Apps2sd support (see instructions below)
Customized theme including wallpapers, phone dialer, keyboard, bootanimation, and other small touches...
Lean and very crisp running ROM - it almost "feels" lighter in your hand!
Designed to be a stable everyday ROM
Check out the change log to see the full evolution and details
Credits and General Public License (GPL):
HTC kernel source: http://member.america.htc.com/download/RomCode/Source_and_Binaries/desirec_2.6.29_8a03cb9a.tar.bz2
Zanfur OC kernel support – source: http://forum.xda-developers.com/showthread.php?t=679102
GScripts source: http://code.google.com/p/gscript-android/source/checkout
Wired tether source: http://code.google.com/p/android-wired-tether/source/checkout
Built from the July Verizon 2.37.605.4 Eris code base
bertoch for hosting and helping me understand Linux
dsixda for his time saving kitchen – source: http://forum.xda-developers.com/showthread.php?t=633246
gr0gmint on how to make jit (mostly) work with HTC ROMs – source: http://forum.xda-developers.com/showthread.php?t=684535
ChainsDD for Superuser – source: http://forum.xda-developers.com/showthread.php?t=682828
vash8806 for Flash 10 source: http://forum.xda-developers.com/showpost.php?p=7316925&postcount=46
synaptyc for custom boot animation - source:http://forum.xda-developers.com/showthread.php?t=768513
rogro82 for starting GScript - source: http://forum.xda-developers.com/showthread.php?t=486486
nfinitefx45 from the Hero CDMA forum on his companion work with cache2cache
thenestor on help with the DroidXIME keyboard
firestrife23 for helping me understand permission issues with the init.d process
Damageless and TrevE for a model on how to do apps2sd (originally based on tkirton's Darktremor A2SD work) and other boot settings
t2noob on the July patch
Collin_ph for the battery tweak code – source: http://forum.xda-developers.com/showthread.php?t=737352
dearmasfamily for OpenGLES1.1 - source: http://forum.xda-developers.com/showthread.php?t=915058
xda member beta testers (you ROCK)
other xda members for tips and tricks
Download xtrROM5.0.1: http://zach.xtr.i6ix.com/xtrROM5.0.1.zip
MD5 checksum:1e5482eb3fc8486182151c5fad01a253
Default ROM Configuration:
You do not need to run any scripts unless you would like to change the following default configuration:
Live Wallpapers: Not supported (you must run GSript to enable)
dalvik.vm.heapsize: 24m
min free memory values: "balanced" (1536,2048,4096,10240,12800,38400)
CPU Overclocked: Min-245760 Max-710400
CPU Governor: Ondemand
Just In Time Compiler (JIT): Off
Cache Location: Cache2cache On
Apps2sd: Off
User service and battery tweak: Off
Thanks to Canop you can flash other Kernel options from the links below:
BFS - http://forum.xda-developers.com/showthread.php?t=772053
CFS - http://forum.xda-developers.com/showthread.php?t=774211
Get older versions of xtrROM in the change log
OPTIONS AND CONTROLS:
Stock Battery Icon
If you prefer the stock battery icon over the circle battery then flash the below zip.
Make sure to wipe dalvik-cache AFTER flashing this zip
Stock battary Icon: http://zach.xtr.i6ix.com/xtrStockBattery.zip
Live Wallpapers
Live Wallpapers is a feature you can enable for this ROM. I have included my favorite for you to try and you can get others from the Market. Many of the live wallpapers from the market DO NOT function well on our Eris or do not "stick" after reboot, our hardware is underpowered for most and I also find them to be a battery drain. That said I still run a few at times because they are just COOL !
To enable live wallpaper functionality just run the appropriate GScript.
Android ASOP Keyboard and Themed Dialer
This ROM uses a custom themed Android ASOP keyboard as the default keyboard and I have themed the phone dialer to match. If you prefer the standard HTC style keyboard check out jonasl HTC_IME mod keyboard – source: http://forum.xda-developers.com/showthread.php?t=624416. Or if you would like the stock setup download and flash the below .zip file.
Stock keyboard and dialer: http://zach.xtr.i6ix.com/xtrStockKeys.zip
LOOKS LIKE THIS DOES NOT WORK FOR XTRROM5.0 ONLY OLDER VERSIONS - I'LL UPDATE SOON FOR XTRROM5.0...
Clear HTC Lockscreen
It is my personal favorite and since I make the ROM I get to pick . To update the lockscreen go to the Photos app - select the photo you want - select the Set as option - and then select lockscreen.
To get back to the clear lockscreen just run the set_lockscreen_clear.sh GScript and reboot your phone.
GScript
I have compiled and incorporated the opensource GScript app to load and one-click run user settings.
To setup your GScripts complete the following steps:
1. After opening GScript press the menu button and select "Add script"
2. A new window will open.
3. Press the Load file button
4. Select a script from the list (each is obviously named as to its function)
5. Ensure Needs SU? is checked
6. Now select "Save" and you have added your script
7. To run just select it from the list in the main GScript screen
8. Some scripts may prompt you to reboot the phone for the change to take effect.
There are a lot of scripts but remember your phone has been setup great by default with this ROM and if you do not understand the function or purpose of a GScript then best to not save and run it . One can always search this forum and ask others about all the fun things you can now do with your phone! I will look to add a list of each GScript and its function as time allows...
Wired Tether
For wired tether to work you must make sure that your computer has the appropriate RNDIS drivers. Learn how to do this at the android-wired-tether Wiki.
Per roirraW "edor" ehT:
The wiki incorrectly states, or implies, that Windows 7 includes the RNDIS support. Or at least, they imply that Windows 7 includes the RNDIS driver necessary. I can confirm that neither Windows 7 x86 or x64 works with tethering out of the box. The instructions for XP users are correct and also work for Windows 7. Just download HTCSync for your device (Eris) and install it, and it'll install the correct driver.
Flash Support
A hacked version of Flash 10.1.123 is baked into this ROM however it has proven to be hit and miss and preforms more like a flash "lite"... Full flash sites such as Halo do not work however many others do; they may just take a while as the Eris is not a powerful phone
Performance Improvements:
Free Internal Memory and Dalvik-cache heapsize - I have update default user settings to allow a larger dalvik heapsize of 24mb (think more space for apps to play) AND optimized how memory is freed up using Androids internal task killer.
Default min memory free: “balanced” (1536, 2048, 4096, 10240, 12800, 38400)
Default dalvik vm heapsize: 24m (48m with JIT on)
To change dalvik vm heapsize or min memory free settings you can just run the appropriate GScript.
If you would like to further modify the default min memory free settings then download Autokiller or MinFreeManager, these apps will allow you to set and monitor the min memory free values. For more information on Androids “internal task killer” and min memory free values go here.
default Overclock Settings - the ROMs kernel supports overclocking and as part of the custom sysinit process I have added scripts that automatically set the below CPU clock settings when the phone boots:
Min: 245760
Max: 710400
I have included a few GScripts to change between stock cpu settings and default overclock settings without using a market app . You can also run the report_cpu_freq script from GScript to get a printout of which frequencies and time in each you phone has been operating.
To change CPU overclock settings just run the appropriate GScript.
If you would like to further modify OC settings then download SetCPU or Overclock Widget, these apps will allow you to set and monitor the CPU speed. Remember YOU CAN DAMAGE YOUR CPU IF RUN TO HOT FOR TO LONG with higher settings. MAKE SURE TO RUN THE set_cpu_stock GSCRIPT IF YOU INSTALL A MARKET APP. The internal overclock support may overwrite the market app settings...
JIT - JIT (Just In Time compiler) is a built in option for the ROM but is off by default. For a detailed overview of JIT go here. PLEASE NOTE for Android 2.1 JIT is not stable with all applications and can cause odd things on your phone.
To enable/disable JIT just run the appropriate GScript and reboot your phone.
User Services Power Management (Collin_ph Battery Tweak) - I have built in a user services that runs at a polled interval and can set the performance settings of your phone in realtime. The first script that is available is a 2.1 HTC framework version of the Collin_ph Batter Tweak. For a detailed overview of you can view the original thread at here.
The power management battery tweak is disabled by default but there is a gscript to enable plus you can run "battconf" from terminal on the phone or adb shell to configure... The battery tweak runs a script every 60 (or less if you are on power) to poll the capacity of the battery, and as the battery goes down the cpu max freq is progressively lowered. It also changes the CPU write characteristics (all of which I do not yet fully understand). You can see all the details in the /system/bin/batter_tweak file.
I take no real credit on this and just ported the concept to the HTC framework and HTC kernel (with the zanfur OC patch). This took a lot of work and I fixed a few bugs but the concept is not mine and all Collin_ph.
When you first run terminal remember to type "su" (or equivilent for your app) to run as root and select "1" then enter when first prompted after starting "battconf".
So how do I know it is working? just run the report_log.sh GScript and you will see when it logs a change to the system settings. Also you can run the report_system_settings.sh GScript and for a display of current settings. This process will be faster if you plug into a power source and wait about 60 seconds
To enable/disable the battery tweak just run the appropriate GScript (user_service_batterytweak_enable.sh or user_service_batterytweak_disable.sh) and reboot your phone.
Cache Location (Cache2cache):
By default, the dalvik-cache has been relocated from the internal /data/dalvik-cache/ directory to the internal /cache/dalvik-cache directory. The Eris comes with an internal /cache/ file block of 130mb that is not used! After reviewing a number of xda member file system usage reports (thanks xtrROM and xtrSENSE users!) the MOST reported use of this space was 5%... So by moving the dalvik-cache to this free area you now have over 150mb on internal /data/ for apps and over 75mb in internal /cache/ for dalvik-cache. This means that you can probably install close to 100 apps WITHOUT having to partition and move anything to the SD Card ext!
You can also move the dalvik-cache to your sd card ext or back to the stock internal /data/ file block.
To change the dalvik-cache location just run the appropriate GScript and reboot your phone.
So why does my Settings>SD card & phone storage>Internal phone storage only show 150mb or less? This is because this number ONLY reflects the /data/ file block on your phone and does not "see" the /cache/ block that is now being used for dalvik-cache storage. You can run the GScript report_system_settings script to see amount available in /cache/.
Apps2sd and Cache2sd:
I have revamped my implementation of apps2sd to use simpler and better organized scripts. For apps2sd to work you must first complete the listed prerequisites and it is a good idea to read through the "things you may want to know about apps2sd" section. Although it can provide gobs of space for apps, Apps2sd is not for everyone as it ties the stability of your phone to your SD card... If you do not need the space I would recommend that you keep the default of DISABLED; if you want to try you can always disable it again however there is always the chance of issues.
To enable/disable apps2sd and cache2sd just run the appropriate GScript and reboot your phone.
Prerequisites
If you have not setup your SD card (for those new to Apps2sd) as per tkirton:
BACKUP YOUR SD CARD TO YOUR COMPUTER. Can't stress this enough, as partitioning will wipe the entire card.
Reboot into recovery
In Android System Recovery, select Partition sdcard
In the Partition sdcard menu, select Partition SD
Follow the instructions on the phone to partition your SD card. Most folks seem to recommend using the default values however you can go larger or smaller use values 256, 512,768,1024. You will also be asked to set a swap size; I stayed at 32mb (anticipate future ROM options to allow moving swap to sd)
Once the partition is initially created you must then convert to ext3 - In the Partition sdcard menu, select SD:ext2 to ext3. Follow the instructions on the screen.
Press the back button on the phone to go back to the main menu.
Your SD card is now ready to work with an Apps2sd supported ROM.
Things you may want to know about apps2sd
Bootloop protection is built in if your SD card is corrupted or is removed from the phone with Apps2sd enabled. Your apps will go away but your phone will boot .
There are 3 subsets of data associated to an app when it is installed and run on your phone.
1) /data/app/ (and /data/app-private) - actual .apk files we think of as the applications that are not system apps (i.e. installed on /system/app)
2) /data/data/ - the files produced by ALL apps (system apps and market apps) during installation that are used by the Android system to run the app
3)/data/dalvik-cache/ - app cache file and work space for ALL apps (system apps and market apps).
From root explorer (or similar) you can browse to the /data/app OR the /system/sd/app folders and you will see the same thing, both will tell you how much space you have used and have left. The way apps2sd works is by "linking" the /system/sd/app to the /data/app folder so that the Android system thinks it is accessing the /data/app it is really at /system/sd/app.
I have seen using Apps2sd cause issues with some.zip flash updates as they try to write directly to the /data/app folder which no longer "physically" exists
If you get into a bootloop issue using apps2sd boot into amon_ra recovery and try one of the follow:
1) from the Other menu option select the Fix apk uid mismatches
2) from the Wipe menu option complete a)Wipe data/factory reset b)Wipe Dalvik-cache c)Wipe SD:ext partition
Apps2sd and Cache2sd Basics
When you run the apps2sd or cache2sd script, upon reboot, it will move ALL your existing apps or cache to the sd card ext partition and ALL future apps and cache will be installed and stored on the sd card ext partition.
Running the apps2internal or cache2internal script, upon reboot, it will move ALL your existing apps or cache to the /data block of internal storage and ALL futures apps and cache will be stored in internal storage.
With HTC based ROMs it is all or nothing and you cannot move individual apps like in the CyanogenMod ROMs.
So how do I know Apps2sd is on? - You can run the GScript report_system_stats which will give you a printout of what fileblocks are used as well as a “true/false” value for Apps2sd On. You can also go to menu>Settings>Sd card and phone storage - when on space available under Available storage will go down at a VERY slow rate when new apps are installed.
TO INSTALL:
YOU MUST HAVE A ROOTED PHONE
download the xtrROM .zip file
complete NANDROID backup
copy the .zip file to the root of your sd card
From Wipe data/factory reset, Wipe Dalvik-cache, and Wipe SD:ext partition (folks coming from previous versions may try no wipe updates but a full wipe is always "cleanest")
flash the xtrROM file from sd card
reboot (first boot may take around 10 minutes)
complete short setup and let your accounts sync
you can save and run GScripts to personalize settings at any time
Available Market Apps You May Want to Add:
Widgetsoid - provides the CyanogenMod style customizable power widget that can be put in the notificaton bar
Root Explorer
Launcher Pro
Tips
For an even faster feel turn off window animations under Settings>Sound & Display>Animaiton.
To update the lockscreen goto the Photos app select the photo you want and select the Set as option and then select lockscreen.
Random FC - Lower your overclock settings or turn off JIT. Our little Eris's can only do so much and not all hardware is equal... Also remember this ROM is quite fast in stock form and higher Linpack scores DO NOT make for a better user experience
Google contact sync issus? check out the following fix http://forum.xda-developers.com/showpost.php?p=6796805&postcount=102. I think this is not uncommon coming from 2.2 Froyo ROMs as they seem to sync with Google a little differently and I do not think the folks at HTC or Google built their systems with the thought that users would be jumping back and forth between versions as much as we all do...
Slow facebook sync? per erishasnobattery: log into your facebook account on your computer - Click Account>Application Settings>under Authorized - remove listing for HTC Sense.
To turn on vibration with keypress for the keyboard long hold the ?123 button in the bottom left and select Android keyboard settings>Vibrate on keypress
If you have 50% time without signal under Settings>About Phone>Battery>Cell Standby complete the "airplane trick" by turning Airplane mode on wait just a few seconds and then Airplane mode off (search the forum for "time without a signal")
If you are syncing facebook then you may want to remember to check the "View contacts" for facebook from the People app Menu>View setting
Turn off notifications for Superuser from the Settings tab of the app
Known Issues
Messaging sometimes FC when send and IMMEDIATE rotate from portrait to landscape. The message still sends and the app stays open there is just an annoying FC on the screen...
Flash does not work for some sites, Halo for example.
The keyboard does not have an updateable user dictionary
Verizon NFL does not work with JIT on
CHANGE LOG:
Click here to view the full change log
Sweet! Thanks! Going to flash when I get home. Is OTA disabled?
USE AT YOUR OWN RISK - settings above 710400 have been reported unstable on some Eris's and YOU CAN DAMAGE YOUR CPU IF RUN TO HOT FOR TO LONG with higher settings.
Weird....I've been running mine on 768000 for the longest time now with no problems what so ever.
kenshincbb said:
USE AT YOUR OWN RISK - settings above 710400 have been reported unstable on some Eris's and YOU CAN DAMAGE YOUR CPU IF RUN TO HOT FOR TO LONG with higher settings.
Weird....I've been running mine on 768000 for the longest time now with no problems what so ever.
Click to expand...
Click to collapse
And I run at 806 but he is saying this for the majority of ppl. So if they DO damage their phone, they dont blame him.
always good to have more options ...i will check it out
rvpartsguy said:
always good to have more options ...i will check it out
Click to expand...
Click to collapse
You really try everything dude. It's a very nice thing to do.
Anyone try it with JIT yet?
Wondering if wired tethering would be included in a later release? Seems to work somewhat faster than wireless for me.
Spencer_Moore said:
You really try everything dude. It's a very nice thing to do.
Click to expand...
Click to collapse
I've been lurking for quite a while, just recently started posting on xda. Pretty sure I've tried all of the ROMs too.
Just got this one downloaded, about to flash it and see how it goes. Won't have to worry about A2SD with over 140mb of internal memory. Outstanding!
Nice Job
Just got XTR setup and it is very responsive. If battery life is decent then I will definitely use this everyday! Excellent effort and I commend you on your opening page. Very clear and consise!
Re: [ROM][6/3/2010] xtrROM2.0 [stable,lwp, oc]
Wondering if wired tethering would be included in a later release?
Click to expand...
Click to collapse
Thanks for the feedback. I will add wired tethering to the StockApps.zip flash and re post tonight or tomorrow.
-------------------------------------
Sent via the XDA Tapatalk App
Jit Failure for me.
My first try with jit on this rom locked up. Maybe too much sense left. But you know what, this rom is plenty fast without it.
Re: [ROM][6/3/2010] xtrROM2.0 [stable,lwp, oc]
Sweet! Thanks! Going to flash when I get home. Is OTA disabled?
Click to expand...
Click to collapse
OTA is disabled.
-------------------------------------
Sent via the XDA Tapatalk App
Re: [ROM][6/3/2010] xtrROM2.0 [stable,lwp, oc]
My first try with jit on this rom locked up. Maybe too much sense left. But you know what, this rom is plenty fast without it.
Click to expand...
Click to collapse
Thanks for trying it out and the feedback! This ROM still runs on the core HTC framework and during my testing with jit could not get it stable enough for a daily ROM.
-------------------------------------
Sent via the XDA Tapatalk App
The widgets are broken apparently. I installed Advance Task Killer and everytime I click on it, it'll vibrate and that's it. OC widget isn't working either. Any ideas?
[EDIT] Oh, reboot was needed. Disregard.
Advanced task killer is not needed. The autokiller app does a much better job. Get rid of atk.
-------------------------------------
Sent via the XDA Tapatalk App
Great running ROM. No troubles yet. Thanks.
I'm running Launcher Pro Beta instead of Sense UI. JIT works GREAT. Getting 5.3mflops @ 806mhz. 5.1mflops @ 768mhz. This thing is FAST!!
I noticed you said this has LWP, so I'm assuming nav wont work then since that seems to be a common them. ie Alyosius
Re: [ROM][6/3/2010] xtrROM2.0 [stable,lwp, oc]
I noticed you said this has LWP, so I'm assuming nav wont work then since that seems to be a common them. ie Alyosius
Click to expand...
Click to collapse
Nav works very well with lwp on this ROM & I use almost daily. the Nav I have included is Googles NOT the HTC version which is where I believe (though I have fully tested) the issues are caused.
-------------------------------------
Sent via the XDA Tapatalk App
soo my phone when clicking on "updates" says
"DM initialisation is not ready
Check network or SIM card"
why? it didnt used to say that
mine does the same thing when it firsts boots up or looses signal its normal when you dont have a good data connection with tmobile or its searching for signal
I know that this is an old thread but I thought it might be helpful if I post the solution to the “DM initialisation is not ready. Check network or sim card" when trying to check for an OTA update. It seems to be linked to task managers. If the process “Device Management” is not running in the background when you check for an update then you will receive the DM error message. What I do is add an exclusion to the Device Management process in my task manager.
I have checked my Captivate, I saw that "Device management" is running in my task manager (advance task cleaner), and I receive the same message. However I am rooted.
Running the Android Compatibility Test Suite on TF101
Background: what CTS is
The Android Compatibility Test Suite is an automated test harness which tests one or more devices to ensure that they offer a fully-compliant running environment for 3rd-party applications.
Passing these tests is required to use the Android brand name for retail devices and it's also the basic prerequisite for acquiring a Google Play license for OEMs.
Background/2: what CTS isn't
As of the current CDD (Compatibility Definition Document) the CTS still doesn't enforce stability or performance requirements for devices, even though some of its tests are taxing enough for the device to expose subtle problems. Some performance tests are nevertheless included, but they're not run by the main CTS plan, nor are they part of the current CDD.
Background/3: why it's important for TF101 users
Given the way the CTS stresses the system, it is useful as a standardised testing procedure for some of the problems some users are currently experiencing with ICS on TF101. It also can help ensuring that the device works as intended with (most) 3rd-party applications straight out-of-the-box.
Requirements: host
The host should be a Linux-based workstation with the Java 6 JDK installed (either Oracle's or OpenJDK - IBM JDK or GNU gcj are not supported, while Oracle/OpenJDK JDK 7 are untested), a fully working installation of the Android SDK and about 3 or 4 GB of disk space available for downloaded media files.
Test results are best viewed with a recent version of Firefox, otherwise you can post-process them into an HTML file using an XSLT 2.0 engine (tested with Saxon).
Requirements: target device
The target device should be a completely stock and unrooted TF101 running 9.2.1.24. It is possible to run the CTS on custom roms, but the tests assume that the device is running a user build (not eng, not even userdebug) in secure mode. YMMV, expect unpredicted failures.
Required files
You're going to need the following files from the CTS downloads page:
Android 4.0.3 R2 Compatibility Test Suite (CTS)
CTS Media 1.0
The following files are optional:
Compatibility Test Suite (CTS) User Manual (if you want more information about the test harness)
Android 4.0.3 R1 CTS Verifier (used to perform user-assisted tests - I didn't run this yet, if you feel brave go ahead and post the procedure you used)
You may also need a log collecting application, even though the CTS should be capable of collecting device logs on its own (it didn't work for me). LogDog (if you have it) is strongly recommended.
Host-side setup
Download the required files and unzip them into a folder of your choice, then change the first line of media/copy_media.sh from:
Code:
#!/bin/sh
to:
Code:
#!/bin/bash
so that the script runs successfully on Debian-based systems (the script is full of bashisms which make dash complain and exit with multiple errors).
Ensure the user you'll be running CTS under has the proper privileges to run adb.
Device setup
First and foremost: perform a full Factory Data Reset (either through the Settings menu or using the VolDown+Power chord at boot time and selecting "Wipe Data").
As soon as the system boots after the wipe, perform the first run wizard selecting English (US) as the system language, connect the device to a wireless network, do not add any Google account (yet), and then reboot the device again to regain access to the system bar widgets (known 9.2.1.24 bug).
Once the system is back up, open Settings and perform the following actions:
disable Quick Settings (ASUS customized setting → ensure Use ASUS Quick Setting is unchecked)
disable System bar lock (ASUS customized setting → System bar lock → ensure Enable system bar lock is unchecked)
disable ASUS Sync (Accounts & sync → ensure Launch ASUS Sync is unchecked)
disable the internal GPS to save battery (Location services → ensure GPS satellites is unchecked)
deactivate all screen locks (Security → Screen lock → None)
temporarily enable Unknown sources (Security → ensure Unknown sources is checked)
under Language & input, ensure that the default input method is Android Keyboard
enable USB debugging (Developer options (dismiss the nag dialog) → ensure USB debugging is checked)
enable Allow mock locations (Developer options (dismiss the nag dialog) → ensure Allow mock locations is checked)
Now go back to Accounts & sync, turn off synchronization and add the Google Account you normally use for Google Play, but don't restore anything, nor accept to synchronize anything - you're going to need this just to install WakeLock.
Close the settings, open Google Play Store, go to its settings and deactivate automatic updates and the infamous auto-add for widgets, then install WakeLock.
Now go back again to Settings → Accounts & sync and nuke the account you just set up.
At this point, you're ready to upload CTS test files, so connect the device via USB to your host, disconnect any other Android device (emulators included!), ensure adb is on your PATH and then run the following commands from the directory where you unpacked the CTS archives:
Code:
cd media
./copy_media.sh all
This will upload the CTS media files (Big Buck Bunny) on the device, it will take a bit of time.
When it's done, you have to install the instrumentation apks:
Code:
cd ..
adb install android-cts/repository/testcases/CtsDelegatingAccessibilityService.apk
adb install android-cts/repository/testcases/CtsDeviceAdmin.apk
Now back on the device, open Settings again and perform the following actions:
enable Accessibility → Delegating Accessibility Service
go to Security → Device administrators → check all android.deviceadmin.cts.* administrators
This is a good time to install LogDog and reboot the system if you wish.
After that, go back to Security and ensure that Unknown sources is unchecked.
Unplug the device from USB and charge it fully.
After the device is charged, plug it back to the host, go to Settings → Developer options (again, dismiss the nag dialog) → ensure Stay awake is checked even though it won't work.
Launch WakeLock, select FULL_WAKE_LOCK as lock type, deselect "Show notification?", select "Start on boot?" and then "Acquire lock".
>>> Press the Home button to go back to the home screen.
Congratulations, you're ready to start the test harness.
Running CTS
On the host, run android-cts/tools/cts-tradefed. It will detect the device and print its android device id, then wait for a command.
To start the full CTS suite, issue run cts --plan CTS. It will take several hours and the battery will barely last for the entire duration. DO NOT INTERACT WITH THE DEVICE IN ANY WAY WHILE THE TESTS ARE RUNNING!.
After the test is finished, just type exit to terminate the test harness utility. Test results will be in android-cts/repository/results/<start time>/testResult.xml, open it with Firefox to see them or process them with saxon-xslt to produce an html file.
If you were running LogDog during the tests, archive the logs now and transfer the log archive to the host.
Post-run caveats
Wipe the device to ensure that any leftover is cleared. If you wish to run the tests again, restart from the "Device setup" step.
reserved for future notes
Thanks for the in-depth guide, very interesting!
Hi all,
imagine I run CTS and 15 tests fail. Can I run only those 15 tests and not the hole CTS?
Thanks!
GnobarEl said:
imagine I run CTS and 15 tests fail. Can I run only those 15 tests and not the hole CTS?
Click to expand...
Click to collapse
IIRC there is a way to tell tradefed to run a specific test, but I don't have the CTS documentation and tradefed itself ready at hand.
Try issuing 'help' at tradefed's prompt, it should provide with the necessary syntax to run a single test instead of a full-blown test plan.
Hi,
you can do something like "add --derivedplan -result fail" and run only failed tests. The problem is that creats another report, and not update the first report.
I wanted to have only one report in the end.
thanks for your reply.
After having a great deal of stress regarding the notification issues, I have come up with a solution.
Please note:
1. I have no idea why my solution works on only this one version of the firmware, but I can only reproduce it on build number NXT-AL10C00B129SP02 (The second-to-newest Chinese firmware). I cannot reproduce the solution on other versions and have not yet gotten notifications working on them, so please make sure you have the same version of everything as I do to make it go smoothly. I have only tried and failed on the latest Chinese and the latest international firmware, so perhaps an older version of that will have good results.
2. I can't guarantee this will work for everyone. Everyone has a different combination of software and settings, etc. What works for me very well may not work for you, and vice versa.
That being said, here is what I did, and how you can test and make sure it's working right for you.
Step One: Set up the OS.
Get NXT-AL10C00B129SP02 (available from the development section of this forum). You can unpack it and flash it with flashboot. The unpacking tool is as follows:
http://fs1.d-h.st/download/00173/wwfQ/HuaweiUpdateExtractor_0.9.9.3.zip
This tutorial won't cover flashboot usage. Please figure it out with google and feel free to ask if you need additional help.
You will then need to get TWRP installed. Please refer to root thread.
Getting into TWRP, please first format your /data partition, then flash the following in order. (maybe different versions will work, but these are what I used, and they worked for me, so maybe better safe than sorry.)
---
decrypt boot B129SP02.zip (can be found in this forum)
BETA-SuperSU-v2.66-2016013015024.zip
open_gapps-arm64-6.0-micro-20160108.zip
---
Then, clear cache and dalvik cache, boot the device up, and set it up.
Get into developer options and turn on ADB debugging. We will use adb to check that everything is working properly. Also, configure an email account with gmail. We'll use gmail to test as well.
Step Two: Doze Settings
Download and install Doze Settings Editor, available from the following:
http://forum.xda-developers.com/android/apps-games/root-doze-settings-editor-android-t3235130
Open SuperSU, then open Doze Settings Editor. SuperSU will ask for root permission, please grant it.
Go into Doze Setting Editor. To keep it easier, go to preferences and change display from milliseconds to seconds.
Set the following, from the top down.
30, 0, 0, 20.0, 0, 0, 12, 12, 2.0, 60, 600, 2.0, 3600, 300, 60, 20
(Easier way to do this is to load tuhinxp04's profile and just change idle timeout and max idle timeout to 60 sec and 600 sec respectively)
Step Three: Test
Now, we will test! Make sure you have adb on your computer, plug your phone into your computer, and run the following commands:
adb shell
dumpsys battery unplug
(turn off the screen of your phone)
dumpsys deviceidle step
(repeat this command until the state is IDLE.)
Now, check the status with this command:
dumpsys deviceidle
Things to look at from the output of this command are:
mState
mNextAlarmTime
Basically, mNextAlarmTime will count down to zero. When it reaches zero, mState will go from IDLE to IDLE_PENDING (and that's when you'll get your notifications). The settings we put in Doze Settings Editor make it so that the countdown starts at one minute, then increases twofold each time until it hits ten minutes. So the longest you'll wait to receive an email notification would be 9 min, 59 seconds.
If everything went well, the device will go from IDLE to IDLE_PENDING after the countdown. Send a test email and watch it arrive.
That's it! If this works, you'll get your notifications. You can adjust the numbers in Doze Settings Editor to match your personal preference.
Now here's the odd thing. With the latest Chinese firmware and international firmware, it does not go into IDLE_PENDING after the countdown. Instead, the countdown goes from +1sec to 0sec to -1sec and counts up, when debugging with ADB. I have no idea how to fix this, but if anyone with other firmware wants to try this solution and see what happens, hopefully we can fix notifications for all software versions. For now I'll stick with NXT-AL10C00B129SP02
UPDATE: I have somehow gotten AL10C00B129SP02 to behave the same as the newer version. I will look further into this as best I can and figure this out. So please hang on a little longer
Is the push notification issue affecting every firmware and model or only few? I'm still deciding to buy the phone or not, so wondering.. Thanks!
Vikram1988 said:
Is the push notification issue affecting every firmware and model or only few? I'm still deciding to buy the phone or not, so wondering.. Thanks!
Click to expand...
Click to collapse
I tried this on my L29 running B162. It seems to have made no difference at all. Notifications are still significantly delayed, especially for email.
---------- Post added at 04:58 PM ---------- Previous post was at 04:56 PM ----------
Vikram1988 said:
Is the push notification issue affecting every firmware and model or only few? I'm still deciding to buy the phone or not, so wondering.. Thanks!
Click to expand...
Click to collapse
I think this is a Huawei EMUI thing. If you look back at older phones on older versions of Android (P8, Mate 7, etc) they all had this issue (and still do). People try to blame doze, but this issue existed long before Marshmallow was around.
I have the European L29 model and I see this issue. Don't let anyone try to tell you that model doesn't suffer from it. It's real.
Guys check my post on 100% working solution for Notifications http://forum.xda-developers.com/mat...ues-huawei-t3345380/post66044102#post66044102
Hello XDA community,
Im a noobie when it comes to rooting, thats why i need help...
I deleted some files that i want to recover on my Samsung S7 Edge 2-3 years ago, this device has Android 7.0. (Never updated)
There is a lot of apps such as Disk Digger that offer you to recover every single file but the device must be rooted to access 100% on the internal memory.
Right now my Samsung S7 Edge is not rooted but i need to root to recover this files, so my question is, there is anyway of rooting without factory reset, or there is anyway of doing a fully backup of the internal memory of my device without touching the partitions so then i can try recovering my files later with this apps?
I hope someone can help me...
Regards
It's pretty disappointing that nobody ever responded to this considering how big is a community it is and how popular the S7 Edge was. I know this is pretty old and hopefully you were able to resolve this before this message but I'm going to respond to this just so you don't feel like your question wasn't acknowledged at all. I have an S7 Edge through Verizon which uses the Snapdragon processor. And I will find a link to post for you that although the method says it's discontinued I rooted my phone through this method and it works fine. The only reason that you would have to wipe your phone is if you're changing firmware as far as I know. I've rooted my phones and did not have to wipe them. I kept all the data and everything.
Before I lift this you are also asking about an application that you could use to back up your phone and that would be Samsung smart switch. It has a companion app for the desktop and it sinks to the phone and it'll make a backup of your data.
Now on to the root method all props and praise goes to the people that worked to give this to the people I'm not good at doing all this **** and I'm not meaning to step on any toes I'm just trying to help you since nobody did for two ****ing years.
To root
1. Download PrinceComsys Odin
Odin.Prince.Comsy.zip
drive.google.com
2. Download the engboot.
Engboot Download
Nougat_S7_Edge_EngBoot.tar.md5
drive.google.com
3 make sure you have adb and fastboot installed on your computer (goggle them)
4. Root file
Download the file below.
Nougat_S7_Root_2_82_All_Carriers_V2.zip | by jrkruse for Galaxy S7 Edge
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
BELOW IS THE ROOT AND MOD FOR THE PHONE!!!!!
Follow this method to root:
1. Shut off the phone and boot into download mode (volume down, home, and power). Use Odin And Flash Nougat_S7_Edge_EngBoot.tar.md5 In AP Slot
2. When the phone reboots, unlock developer options by going into the phone settings scroll down to 'about phone' find the build number and tap on it repeatedly after several times it will unlock Developer Options then back out once and in your settings you should have a new option on the very bottom called developer options go into that and enable USB debugging and Disable Verify Apps Over USB.
Plug the phone into the computer and make sure you have adb and fastboot installed to this location
C:\Users\YOUR PROFILE\AppData\Local\Android\Sdk\platform-tools
go to that folder and inside it hold shift and right click then click on 'open command window here'
then in command prompt type
adb devices
then hit enter.
The computer should automaticly detect and run adb
3. Unzip the Nougat_S7_Root_2_82_All_Carriers_V2.zip and hold shift and right click then click on 'open command window here'
In the command window type root.bat then press enter from your PC.
4. This will install root when done phone will reboot
5. The process wipes dalvik cache so it will take a few minutes to reboot
6. If having problems getting Grant SuperSU dialog to come up you can delete the SuperSU app and root will be granted instantly to all root request
Give phone a few min to settle open developer options set animation scales .05 and others to .05
Give phone a few min to settle open developer options set animation scales .05 and others to .05
ODIN FAILED TO WRITE ERROR
Did you get this Failed To Write Message in Odin?
----------------------------
Odin Error Message:
<ID:0/003> FAIL! Model dismatch fail
<OSM> All threads completed. (succeed 0 / failed 1)
SOLUTIONS
Did you:
? Open Odin as Administrator?
? Try the Prince Comsy version?
? Enable Developer Settings?
-Open Settings > About Phone > Tap Build Number 7 Times
? Enable OEM Unlock?
-Go Back to Settings > Tap Developer Options > Tap OEM Unlock
? Enable USB Debugging?
-Tap Developer Options > Tap USB Debugging
NOTHING WORKS
Did you try every single thing but nothing works?
Well, did you right click "Odin" each time you go to open it and then click "open as administrator"?
Sometimes you have to try several different versions of Odin.
But I have found that Odin3 v3.12.7 was the one that would work when the others had not.
I always would forget to also open Odin as Administrator.
It's a pain in the neck to have to remember to open as admin every time.
But you usually have to do it.
Did you check that ADB had started? Maybe that might be the reason it won't work?
But I doubt it! But you just never know and I am just trying to help you get it flashed.
It's a very quick flash and you can see that the PDA load was very quick as well.
But as far as the errors, you just have to keep trying...
Which I mean, you sometimes have to open, close, reopen Odin when it doesn't work.
Sometimes that helps, sometimes it doesn't.
It's all about the right Odin version at the time
making sure the cord is good
Opening Odin as Admin
And keep trying again after restarting your phone by holding the download mode button sequence again.
============
Congratulations! You are ROOTED but you're not done
Follow these instructions next
On your phone, open the SuperSU app (installed during the root process) and tap on Settings. Half-way down under Security, tap on "Enable su during boot".
This option will ensure that startup scripts that are installed during this process get to do their job correctly.
Download the fix or fix+debloat script flashable ZIP package appropriate for your model of phone and copy this file to your device:
S7_VOLTE_ICON_FIX_ALL_VARIANTS or S7_or_S7Edge_Fixes_V15.zip (MD5 hash F15CD9BDC35382A8F48FFBEDBB1BCDF0) (any Samsung Galaxy S7 or S7 Edge)
turn off auto update of time and date in your phone settings, then set your year to 2013,
Launch FlashFire app on the phone and click the (+) button in the lower right to add a step. Select a 'Flash ZIP or OTA' flash step.
Locate the flashable ZIP package and select it. For options, check on 'Mount /system read/write' and leave the rest of the options unchecked.
Tweaks to Root
Debloat and fix several issues with the phone (CPU lag issues, poor battery performance, phone becoming too hot, Wi-Fi not saving passwords, hotspot/tethering not working,
VoLTE icon appearing, searching for service issues, MMS not working, unauthorized security nag notification, etc.):
Full notes on what this flashable update does:
Adds a rotate button to the native gallery app
.
Adds a shortcut call button in the call log next to each logged call.
Adjusts several CPU tunables, which fixes phone lag and battery life issues.
Disables "No SIM" popup when no SIM card is present.
Disables roaming data by default.
Disables secure storage support, which fixes Wi-Fi passwords not saving issue.
Disables Verizon provisioning for Wi-Fi tethering/hotspot (will still use your data plan, of course).
Enables ADB to run as root by default.
Enables CPU idling/sleeping, which fixes phone heat issues.
Enables mock GPS locations.
Enables native call recording feature in the dialer.
Enables native Wi-Fi calling feature in the dialer.
Enables RIL power saving features.
Enables scheduled messages in the native messaging app.
Enables the camera during calls.
Enables unlimited contact merging.
Enables using the new 3GPP2 Profile ID (Verizon exclusive).
Fixes various 'searching for service' and other cellular network connectivity issues (SMS/MMS not working, calls not working, etc.)
Knox apps, drivers, and data are removed (fix+debloat version).
Prefers LTE network.
Raises the contact name length limit to 1,280 characters.
Raises the maximum SMS recipient limit from 10 to 90.
Remove nagging 'unauthorized actions' security notification (fix+debloat version).
Removes VoLTE icon.
after you flash your stuff change the date back. and you're good.
I know this all seems like a lot and it seems very confusing but it's pretty easy if you just follow the directions this will not wipe your data. Please do research, read through the forms and just tried to get as much knowledge as you can before you go about doing this it's an easy process but it's better to go in with more knowledge, I hope this helps. If you have to reinstall the firmware make sure that you install CSC home so you don't lose your data