** DoPa6 (AOSP - Marshmallow) ** is now available - see this post for details and downloads
Click to expand...
Click to collapse
DoPa5 v1.3 is a Lollipop ROM for Sero 7 Pro owners worldwide. It focuses on core functionality that must be built-in and relies on 3rd-party apps to provide features that can be added-on. This release also offers a version of TWRP Recovery that is compatible with all models of the S7P.
Key Features
International Support - a single ROM for all Sero 7 Pros sold worldwide (US, UK, Australia, Germany, and elsewhere)
Speed Control - speed when you need it and stock performance when you don't
OTG Charging - charge the tablet while an external device is attached to the USB port
Flexible Formatting - full support for both F2FS and EXT4 on your internal storage, and exFAT/FAT32/NTFS/F2FS/EXT4 support for external storage
Installation
First-time Users
If you're upgrading from a stock ROM (any variety), please click the "show content" button and read the instructions very carefully - they're long but your tablet's continued good health may depend on it!
STEP 1: Install TWRP or Philz Touch Recovery
Users outside the US must use the DoPa versions of these recoveries to install the ROM - neither the stock recovery nor other versions of CWM or Philz will work. Users in the US should use them just to avoid problems.
Stock Recovery
If you still have the stock recovery program you'll have to use the 'fastboot' program to install TWRP or Philz. On Windows, this requires installation of the 'ADB' USB drivers while in fastboot mode (see below). A package containing the drivers, fastboot, adb and other files can be found in the 2nd posting on the DoPa Stock ROM thread. Note: there are several batch files (*.bat) in the package - do NOT run them.
put fastboot.exe in a convenient directory, then unzip the recovery zip and put the .img file (twrp.img or philz.img) in the same directory (you won't need the other files)
unplug any USB cable, then press and hold Power+VolumeUp; the word "fastboot" should appear on the screen (nothing further will appear)
plug the USB cable from your PC into the tablet, then install the driver (open Device Manager, right click on "Other Devices->Fastboot", then select "Update Driver Software")
after installing the driver, open a command prompt ("DOS window") and change to the directory containing the files
enter, as appropriate, fastboot flash recovery twrp.img or fastboot flash recovery philz.img
when done, force the tablet off, remove the USB cable, then reboot into recovery: Power+VolumeDown - you should see the word "recovery", then either the TWRP or Philz menu
CWM
If you have CWM installed, copy your choice of recovery zip to an SD card, insert it in the tablet, then:
remove any USB cable, then boot into recovery: Power+VolumeDown
select "Install Zip", then "Choose zip from /storage/sdcard1"
select the file, then OK the selection
when done, back out to the main menu, select "Advanced options", then "Reboot recovery"
after the initial "recovery" screen, you should see the TWRP or Philz menu
Regardless of how you install your chosen recovery, the result should be the same. If it boots OK, compatibility is assured
STEP 2: Backup
I can't emphasize this enough: you must make a backup of your existing ROM. If something goes wrong, there's no way to get your device working again other than to restore it using the backup you've made. There's also another reason to do a backup: before installing the new ROM, you will have to reformat your /data partition. This will wipe out your apps, your settings, and most importantly, all the music/photos/etc stored on your "internal SDcard". These last items can be restored if you follow the instructions below:
You must do your backup onto a real SD card that you can remove because your "internal SDcard" will be erased in the next step. In fact, it wouldn't be a bad idea to do two backups (preferably to different cards) just in case one is faulty.
using Philz, select "Backup and Restore", then "Backup to /storage/sdcard1" -if there's enough space on the card, the backup will start without any further prompt;
using TWRP, select "Backup", then tap "Storage" (halfway down the screen) and ensure that "sdcard" is selected; on the previous screen, swipe the slider to start the backup;
it could take anywhere from 3 to 15+ minutes depending on the amount of data and the speed of your card
if needed, you can enable compression to create a smaller backup: for TWRP, you can check "Enable compression" on its main backup screen; for Philz, select "Misc Nandroid Settings -> Default Backup Format -> tar + gzip", then on the previous menu, tap on "Compression" to set the appropriate level
STEP 3: Install the DoPa5 ROM
Before you begin, you may want to download a Google Apps ("Gapps") package that you can install after the ROM. See the TK Gapps thread for details. I recommend the "Nano Modular" package which gives you the basics - you can always upgrade later. Put your Gapps package along with the ROM zip on an SD card and insert it into the tablet - you can use the same card you're using for your backups.
using TWRP, select "Wipe", then "Format data"; on the next screen type "yes" to confirm you want to proceed;
using Philz, select "Wipe and Format Options", then "Custom Format Options"; next select "format /data and /data/media (/sdcard)" (the 8th item), then OK your choice;
return to the main menu
using TWRP, select "Install"; at the top it should show "Storage: sdcard" - if not, tap there and change the setting
using Philz, select "Install Zip -> Choose zip from /storage/sdcard1"
select sero7pro-aosp511-dopa5-v1.3.zip, then OK your choice - the install process should take about 40-60 seconds
next, install your Gapps package
return to the main menu, select "Reboot" then "System" if using TWRP, or "Reboot System Now" for Philz, then hold your breath for the next 3-4 minutes
the Hisense screen should be up for 30 seconds, followed by the DoPa boot animation for another 3 minutes
If the boot animation is still running after 5+ minutes, force the tablet off, then reboot. If that doesn't fix it, try formatting /data again. If it still doesn't work, restore your tablet from your backup ("Backup and Restore -> Restore from /storage/sdcard1"), then post a message here. If everything works out as hoped for, re-read the first posting in this thread for details on some of the features (and problems) of this ROM.
Upgrades
UK, AU, and DE users must use the DoPa versions of TWRP or Philz Touch to install the ROM because they are the only ones compatible with your tablet. US users can use any SELinux-enabled version of CWM, Philz, or TWRP.
from DoPa5 AOSP Lollipop ROMs - no need to wipe or format anything!
from DoPa AOSP Kitkat ROMs (v1.0-v2.7) - a clean install is recommended but not required
from pre-Kitkat (v4.4.x) or any CM-based ROMs - wipe your /data partition before installing to avoid unnecessary problems.
install sero7pro-aosp511-dopa5-v1.3.zip
- the installer will wipe (but NOT format) /cache and dalvik-cache for you
install your preferred Gapps package
- upgraders: this is required to prevent your downloaded Google apps from crashing
optionally, install the Nexus7 spoof (sero7pro-nexus7spoof-dopa5-v1.3.zip)
reboot (ignore any "fix root" prompt - it's incorrect)
f2fs / ext4 Migration
This DoPa ROM gives you the flexibility to format any of your built-in partitions using either the f2fs or ext4 file systems.
As part of your install - or at any time - you can switch formats without losing any data. Click "show content" for instructions.
If you haven't already installed TWRP or Philz Touch Recovery, please do so first.
TWRP
make a backup to your external SD card
select Wipe then Advanced Wipe
select the partition to reformat, then tap Repair or Change File System
on the next screen, tap Change File System, then F2FS (or EXT4 to restore the default file system)
swipe the slider below to start formatting
when done, use the Restore option on the main screen to restore the contents of the partitions you reformatted
Philz
make a nandroid backup to your external SD card
select Wipe and Format Options, then Custom Format Options
select toggle f2fs <-> ext4 migration
- be sure there's a confirmation message at the bottom of the screen
select each partition you want to convert or wipe, then select the format and OK your choice
Important: to convert your /data partition, you must select format /data and /data/media (/sdcard)!!!
use Custom Restore from /storage/sdcard1 to restore the contents of the partitions you reformatted
Changes since DoPa5 v1.2
Xposed and GravityBox - these staples of the DoPa KitKat ROMs are back and preinstalled to provide all the tweaks you want - and none of the ones you don't
ArchiDroid Optimizations - this version of Android was built using gcc 4.9 and is highly optimized thanks to settings provided by JustArchi. To help ensure stability, the kernel uses standard optimization levels but is better tuned to our Cortex A9 processor due to the use of linaro 4.9 (a version of gcc optimized for ARM processors).
No Odex-ing - odex-ing has been abandoned because Xposed recompiles all apps, making the .odex files redundant. There should now be enough space on the /system partition to install the TK-Gapps Micro package.
Adaptive Brightness - a longstanding bug that could cause the screen to go black has been fixed. Overall brightness levels have been adjusted to provide greater dynamic range in low lighting conditions.
Notes
Xposed - having the Xposed framework installed shouldn't cause any issues, but if you wish to remove it you can do so using the xposed-uninstaller available in the Xposed XDA thread. The Xposed Installer and GravityBox apps will remain but will be inactive - you can use a root-enabled filemanager to remove them if you wish.
Encryption - if you wish to encrypt your /data partition, you must first use Philz Recovery to format it. Using TWRP to format may cause the partition to become un-decrytable, resulting in the complete loss of all your data. This is NOT an issue if you don't plan to use encryption.
WiFi Display - end a WiFi Display session from your television, not the tablet; doing so from the tablet may cause it to lock up. Chromecast is reportedly not subject to this issue.
USB Audio - booting up with a USB audio device attached may result in a bootloop.
Gapps - due to limited space on the /system partition, the TK Gapps's "Mini Modular" and larger packages will not install. I suggest using the "Nano" package, then downloading those apps you really want from PlayStore.
Credits
ziddey
randomblame
davepmer
the CM team
Downloads
sero7pro-aosp511-dopa5-v1.3.zip the full ROM
sero7pro-nexus7spoof-dopa-v1.3.zip identify tablet as a Nexus7 to (possibly) show more apps in PlayStore
sero7pro-twrp287-dopa5-v1.3.zip a customized version of TWRP Recovery v2.8.7 usable on all versions of the Sero 7 Pro
sero7pro-philz6.58.0-dopa-v2.7.zip the final version of Philz Touch CWM-based Recovery v6.58.0 compatible with all models of the Sero 7 Pro
TK Gapps an XDA thread with links to various Gapps packages
sero7pro-format-thirdparty.zip - only needed if you are downgrading from DoPa6 (Marshmallow) to a previous version (i.e. this one)
GPL Notice: the source code for this kernel is available at https://github.com/dolorespark/android_kernel_hisense_m470bsa on the 'master' branch.
XDA:DevDB Information
Sero 7 Pro (US/UK/AU/DE) - DoPa5 AOSP, ROM for the Android General
Contributors
dolorespark
Source Code: https://github.com/dolorespark
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.1.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: v1.3
Stable Release Date: 2015-09-26
Created 2015-01-28
Last Updated 2016-01-02
Reserved
Thx for all your hard work
on these tablet
Thx
ok, so I have a question or several as I remember them...
I noticed in Beta 4 that we were (or at least I was) suffering from the well documented play movies bug that was afflicting a number of 2013 Nexus 7 models.
Has this been fixed yet?
If not, is there a workaround?
If so, what is it?
I also noticed some performance and stability issues when using the performance tab along with apps like 3c Toolbox and System Tuner. Unfortunately, I did not see a way to use performance tab to overclock the gpu and leave the cpu clock stock so that I could tweak the system through the aforementioned apps.
Also, can the cpu be overclocked beyond 1.5 Ghz?
If so, is this already enabled, or is there some magic involved?
I really liked the beta 4 (beta r3) Rom and the way it looked, felt, and ran.
I found it to be better at managing free memory than kitkat in that I had at least 50% more free ram than Kitkat. I believe this contributed to some of the performance increase. But I had a hard time with the Google Play Movies bug. And some people were saying it was a general problem within the os's video subsystem.
Legend, keep up the great work
Excellent work! Looking forward to this!
Sent from my Nexus 7 using XDA Free mobile app
alpurl said:
I noticed in Beta 4 that we were (or at least I was) suffering from the well documented play movies bug that was afflicting a number of 2013 Nexus 7 models. Has this been fixed yet?
Click to expand...
Click to collapse
I'm sorry I didn't know about this until you mentioned it. I'm too poor/cheap to buy stuff from Google Play Movies, so I'd never have learned about this on my own. Fortunately this was my day off, so I was able to spend the afternoon chasing down this bug. Here's the fix - install it from Recovery:
sero7pro-video-drm-fix-dopa5-v1.0.zip
I'll repackage the main ROM in the near future to include this fix, but first I want to investigate a few possible problems I noticed while getting this fixed.
I also noticed some performance and stability issues when using the performance tab along with apps like 3c Toolbox and System Tuner. Unfortunately, I did not see a way to use performance tab to overclock the gpu and leave the cpu clock stock so that I could tweak the system through the aforementioned apps.
Click to expand...
Click to collapse
Every time you display the Performance page, it will restore all parameters to the values you set previously. If 'Speed Control' is enabled, it will reset the CPU & GPU speeds, overriding values set by some other app. Your best bet is to turn it off. If neither of the apps you mention knows how to set the GPU speed, you can do so temporarily from a terminal or permanently from an init.d script like so:
Code:
echo -n 1250 > /sys/kernel/tegra_cap/core_cap_level # "1200" is 448mhz - "1250" is 520mhz
echo -n 1 > /sys/kernel/tegra_cap/core_cap_state
Also, can the cpu be overclocked beyond 1.5 Ghz?
Click to expand...
Click to collapse
Nope, not without extending the kernel's DVFS table further, then recompiling. Someone had it running at 1700mhz, but I'd consider that ..umm.. ill-advised for a chip that's intended to run at 1200-1300mhz.
Loving the first build. Very silky smooth speed and pretty stable as well as far as Lollipop is concerned at this point. As far as themes are concerned I haven't had too many issues using them on the current CM12 nightly for the Sero 7 Pro despite the DPI difference. Can't wait to see where this goes from here. Thanks for all the hard work! :highfive:
dolorespark said:
Nope, not without extending the kernel's DVFS table further, then recompiling. Someone had it running at 1700mhz, but I'd consider that ..umm.. ill-advised for a chip that's intended to run at 1200-1300mhz.
Click to expand...
Click to collapse
Well, on nVidia's page it recommend a maximum of 1.6 GHz, so 1.7 is not too much of an overboard if Hisense had built these units well enough. However, even with 1.5 GHz the chips is already running uncomfortably hot so it would be wise to back off from any higher clock. I do however think that the GPU of this tablet is a lacking a bit of oomph (ironically), is it possible to raise the clocks of the GPU beyond 520MHz? (granted that there would be a possibility of artifacts )
dolorespark said:
I'm sorry I didn't know about this until you mentioned it. I'm too poor/cheap to buy stuff from Google Play Movies, so I'd never have learned about this on my own. Fortunately this was my day off, so I was able to spend the afternoon chasing down this bug.
Click to expand...
Click to collapse
Being under that magic number of 10 posts, I couldn't post this in that main thread, and when I tried to post in the q&a thread where "reply" sent me, the forums bot catcher tripped me up.
Thanks, that worked like a charm.
Every time you display the Performance page, it will restore all parameters to the values you set previously. If 'Speed Control' is enabled, it will reset the CPU & GPU speeds, overriding values set by some other app. Your best bet is to turn it off.
Click to expand...
Click to collapse
I did, and had stability. Just didn't know about just gpu o/c.
If neither of the apps you mention knows how to set the GPU speed, you can do so temporarily from a terminal or permanently from an init.d script like so:
Code:
echo -n 1250 > /sys/kernel/tegra_cap/core_cap_level # "1200" is 448mhz - "1250" is 520mhz
echo -n 1 > /sys/kernel/tegra_cap/core_cap_state
Click to expand...
Click to collapse
To my knowledge, they don't, or at least I haven't figured that part out yet. Haven't figured it out in trickster mod either. I'll try the code. I only remember seeing one init.d file, does it matter where in that file I add the code?
Yeungers said:
on nVidia's page it recommend a maximum of 1.6 GHz
Click to expand...
Click to collapse
The Tegra3 is a family of SoCs with models designed for mobile, automotive, and embedded use. Ours is the low-power mobile version. Some variants do have higher maximum clock speeds but they use more power at every frequency step than ours.
I do however think that the GPU of this tablet is a lacking a bit of oomph (ironically), is it possible to raise the clocks of the GPU beyond 520MHz?
Click to expand...
Click to collapse
Possibly. The original overclock patch just upped the GPU speed to 520mhz without increasing the voltage any - and that seemed to work. When I rewrote the o/c code, I increased the voltage when running at 520mhz for what I considered solid reasons, Since it now has more power, I suspect I could up the speed somewhat without causing problems. However, even at a higher speed, it's still going to be an also-ran in today's market.
alpurl said:
dolorespark said:
If 'Speed Control' is enabled, it will reset the CPU & GPU speeds, overriding values set by some other app. Your best bet is to turn it off.
Click to expand...
Click to collapse
I did, and had stability. Just didn't know about just gpu o/c.
Click to expand...
Click to collapse
Having some other app set the CPU or GPU speeds isn't going to make it any more or less stable than having the built-in facility do it.
Be aware that if you're trying to use one of these apps to set the Interactive Governor's parameters, you're wasting your time. Not only does our Interactive Governor NOT work like you'd think - and not work like other implementations - it's totally ineffective. Every time the kernel brings another core online, it kicks all cores to the maximum allowed speed, totally sabotaging the governor's efforts. If you use Trickster to track the time at each speed, you'll see that the bulk of the time is spent either at very low speed or max speed, with all the intermediate speeds hardly used at all.
I only remember seeing one init.d file, does it matter where in that file I add the code?
Click to expand...
Click to collapse
Create a new file named, f'rinstance. "02gpuspeed". Put "#!/system/bin/sh" on the first line, then the code I provided on the following lines. The files will be executed in alpha-numeric order: 00banner, 02gpuspeed, 99SuperSUDaemon. Be sure to set its permissions to '755' so it is executable.
I pretty well figured that would be the case, but...
Based on my somewhat limited understanding ,If you have a utility in the Rom trying to manage the cpu speeds, and an app trying to do the same with me "choosing" to use the performance governor, conflicts are bound tio arise. Based on my pc understanding, conflict equals poor performance and instability.
And it was honestly one where I was using performance settings for the gpu, and then one of the other apps for the cpu.
So, I found that if I simply turned off the performance settings and lived with the lower gpu clock, my system ran stable. So I was asking about how to get the higher gpu clock without using the cpu overclock portion of the performance tab.
You pretty well answered that, and I thank you.
Now, do I need to include the bit in the code at the end of the first line where it says 1200 is 448, and 1250 is 520?
Also, I don't understand setting permissions to 755. I understand setting read, write, own, etc, but not 755, if that's the case, then what app do I use for that? I created the file as a blank text document on my tablet directly and input the code there, then rebooted. Or did I screw the pooch on that one?
Sadly, I know nothing about the individual governor settings within each governor configuration. Therefore, I figure that the wisest and safest course of action is to leave it alone. It's easier and safer to work with the stuff I DO know until I can get feedback and advice from someone who DOES know.
I realize that some of this may seem stupid to you, but it's the only way I know to learn.
I will make another post later when I have more time to comment on some other things I keep seeing and would like to know what to do there.
alpurl said:
If you have a utility in the Rom trying to manage the cpu speeds, and an app trying to do the same with me "choosing" to use the performance governor, conflicts are bound tio arise.
Click to expand...
Click to collapse
The CPU/GPU settings on the Performance page are set-and-forget values. They simply set the maximum speeds once bootup is done, and again when you display that page. They don't monitor anything - the CPU governor does that, and it is constrained by these settings. The corresponding settings in the other apps you've tried operate the same way.
You should be aware that the "performance" governor is really no governor at all. It simply sets the processor to the maximum permitted speed and never changes it. On the whole, this governor generates more heat than performance.
I found that if I simply turned off the performance settings and lived with the lower gpu clock, my system ran stable.
Click to expand...
Click to collapse
This strongly suggests that your device really can't handle the higher speed - at least when the CPU is running full-bore at all times. You may want to search for the postings in some of the early S7P threads where people described attaching copper foil to the SoC to dissipate excess heat.
do I need to include the bit in the code at the end of the first line where it says 1200 is 448, and 1250 is 520? Also, I don't understand setting permissions to 755.
Click to expand...
Click to collapse
Anything after a '#' in a shell script is a comment. As to '755', that's "read/write/execute" for the owner, and "read/execute" for the group and other users. Do a search for the 'chmod' command for more details on setting and interpreting Unix permissions.
Ok, that's fair enough.
Occasionally, I'll boot and get an error that the process called system is not responding and then it wants to know if I want to wait, or close it. It will do this every subsequent boot until I wipe cache and Dalvik (because I end up doing both out of habit) from recovery and then all is well again for several boot cycles where we start up again.
What am I missing here?
Are we free to discuss RRO theming for the S7P in this thread for now? I have been following BitSyko Development for a week or so and opted into the Layers beta and so on. I will be spending some time this week to figure this all out.
Sent from my XT1034
kenundrem said:
Are we free to discuss RRO theming for the S7P in this thread for now? I have been following BitSyko Development for a week or so and opted into the Layers beta and so on. I will be spending some time this week to figure this all out.
Click to expand...
Click to collapse
Since I'm not familiar with RRO theming how is this different from the themes released for say CM12 and the like?
kenundrem said:
Are we free to discuss RRO theming for the S7P in this thread for now? I have been following BitSyko Development for a week or so and opted into the Layers beta and so on.
Click to expand...
Click to collapse
AngryManMLS said:
Since I'm not familiar with RRO theming how is this different from the themes released for say CM12 and the like?
Click to expand...
Click to collapse
Of course you're welcome to discuss RRO - especially since it gives me an opening to throw in my 2 cents
Runtime Resource Overlays provides a way to override and/or replace the "resources" (icons, layouts, colors, strings, and fixed values) that are built into an .apk file. Since the resources used by Android itself are packaged into an .apk, you can modify the OS as well as individual applications.
RRO has been around for a long time but no one other than Sony ever used it. BitSyko's greatest contribution has been to make people aware that it's a superior way to do theming which is already built into the OS and is fairly easy to use. Unlike CM's theme engine, no custom code is required.
Beyond that, their contribution is somewhat less revolutionary than their many admirers seem to think. Their efforts are directed primarily at ease of use. The Layers app is essentially a file manager that makes copying themes into place a bit easier. What the app does you can do yourself using ESFileExplorer or ADB (though without some niceties they've added).
Their tweaks to the OS are designed to make life a bit easier for themers by changing hard-coded color values into "symbolic references". In other words, rather than specifying the color for each checkbox, you say each one should be the "checkbox_color", then define what that means somewhere else. That way, rather than having to modify the color of many different checkboxes, you change the definition of "checkbox_color" once and they all become that color.
Now, as to what all this means to the Sero 7 Pro and the DoPa5 v1.0 ROM... I delayed the ROM's release for several days until I could get their patches in place and tested, so this facility is in there and ready for use. The problem is that none of the themes I've seen really support the S7P. Any color changes a theme makes will show up just fine (I'm using someone's orange theme currently). However, all the icons are targeted at higher resolution screens than ours, so the OS ignores them and uses the same ones it has always used. If you can find themes for the Nexus 7, or some of the older Asus or HP tablets that also have a 1280*800 screen (213dpi), they should work just fine.
FYI... if you want to install a theme without using Layers, create an 'overlay' directory in '/system/vendor' (i.e. '/system/vendor/overlay'). Next, get some theme packages from this thread and unzip them. Select the .apk files you want, copy them into the 'overlay' directory, then reboot. If you don't like the result, delete them and reboot again.
Perfect explanation @dolorespark on RRO. I'm hoping eventually some kind of dark holo blue theme is made for RRO as all I really need is the color scheme.
AngryManMLS said:
Perfect explanation @dolorespark on RRO. I'm hoping eventually some kind of dark holo blue theme is made for RRO as all I really need is the color scheme.
Click to expand...
Click to collapse
So you want black on holo blue aka 33b5e5? I'm going to make a white/pink themed for my daughter as its her tablet but I will see what I can do for you while I'm at it.
Sent from my XT1034 using XDA Free mobile app
kenundrem said:
So you want black on holo blue aka 33b5e5? I'm going to make a white/pink themed for my daughter as its her tablet but I will see what I can do for you while I'm at it.
Click to expand...
Click to collapse
That would be amazing if you could. Here is an example of what I mean as well.
http://forum.xda-developers.com/android/themes/theme-dark-holo-theme-v1-0-01-25-15-t3012227
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
Pure Vanilla 2.1 AOSP - well as much as reasonable .
zach.xtr and I are pleased to offer Vanilla2.X! (BIG credits to zach.xtr for tweaking and help with getting all bugs worked out. zach.xtr truly made this blazing quick... and freed up TONS of internal phone storage!)
checkout the change log for a full feature list and details.
{
"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"
}
Remember to donate to the developers that make this possible!
Credits:
bertoch for hosting and Linux help
dsixda for his time saving kitchen - http://forum.xda-developers.com/showthread.php?t=633246
Conap and Decadenc3 for their CFS kernel with OC and for MMS fix - http://forum.xda-developers.com/showthread.php?t=774211
Conap for his support and general help and a few libs from CELB - http://http://forum.xda-developers.com/showthread.php?t=679194
punk.kaos for his Trackball notification/softkey fixes - http://forum.xda-developers.com/showthread.php?t=685594
Gnarlyc for his Android Builder for quick access to 2.1 AOSP source - http://forum.xda-developers.com/showthread.php?t=707414
Framework43 for his pioneering work with AOSP 2.1 builds and a few "Senseless" parts - http://forum.xda-developers.com/showthread.php?t=686870
nfinitefx45 from the Hero CDMA forum on his work for cache2cache - http://forum.xda-developers.com/showthread.php?t=790889
other xda members for tips, tricks and beta testing (you ROCK)
SERIOUSLY... DONATE TO ONE OF THE DEVS ABOVE. IF IT WASN'T FOR THEM, YOUR ERIS WOULD BE THE PHONE THAT "COULDN'T"
-----------------------------------------------------------
Base Vanilla2.X Features:
All the goodness of Android AOSP 2.1 with root access superuser permissions
Built from AOSP 2.1 source including all your favorite AOSP 2.1 apps!
Custom sysint process to optimize ROM system settings
Smart design for a tailored user experience (only turn on the features what you want!)
Overclock support - default setting overclock to 710400
Apps2sd and Cache2cache support (see instructions below)
designed to be a stable everyday ROM
Check out the change log below to see details
-----------------------------------------------------------
Download Vanilla2.0.4: http://zach.xtr.i6ix.com/Vanilla2.0.4.zip
MD5 checksum: ae9eb1cf3c67dd08ea31c8cd5ec11dfb
-----------------------------------------------------------
Vanilla2.X Options:
GScript
For Vanilla2.X we have compiled and incorporated the opensource GScript app (see http://code.google.com/p/gscript-android/) 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. You must reboot the phone for the change to take effect.
-----------------------------------------------------------
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 (Quick Boot makes this easy!).
** If you run into issues using the default Term Emulator (in Dev Tools), please download "Android Terminal Emulator" from the Market.
-----------------------------------------------------------
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.
Performance Improvements:
I HIGHLY recommend setting your Animations (Spareparts) to either OFF or FAST for a much smoother, faster experience.
Free Internal Memory and Dalvik-cache heapsize - We 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”
Default dalvik vm heapsize: 24m (38m 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
Overclock Settings - the included kernel supports overclocking and as part of the custom sysinit process we have added scripts that you can run to overclock the CPU 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 enable/disable overclock 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 (Quick Boot makes this easy!).
Cache2cache & Cache2sd:
By default, the dalvik-cache for Vanilla2.0 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 151mb on internal /data/ for apps and over 97mb in internal /cache/ for dalvik-cache. This means that you can probably install close to 100 apps WITHOUT moving 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 location of dalvik-cache you can just run the appropriate GScript and reboot your phone (Quick Boot makes this easy!).
Apps2sd:
Apps2sd for Vanilla2.0 is incorporated in the custom sysinit process. 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 we 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 just run the appropriate GScript and reboot your phone (Quick Boot makes this easy!).
Apps2sd Basics
When you run the apps2sd , upon reboot, it will move ALL your existing apps to the sd card ext partition and ALL future apps will be installed and stored on the sd card ext partition.
Running the apps2internal script, upon reboot, it will move ALL your existing apps to the /data/ block of internal storage and ALL futures apps will be stored in internal storage.
For NON CyanogenMod based ROMs it is all or nothing and you cannot move individual apps.
Apps2sd 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
Vanilla2.X has bootloop protection 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 /sd-ext/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
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. You can also go to menu>Settings>Sd card and phone storage - when on space available under Available storage will be over 150mb will go down at a VERY slow rate when new apps are installed.
To Install
YOU MUST HAVE A ROOTED PHONE WITH THE AMON_RA RECOVERY PARTITION
download the base Vanilla 2.X.zip file
complete NANDROID backup
copy the .zip file to the root of your sd card
From amon_ra recovery Wipe data/factory reset, Wipe Dalvik-cache, and Wipe SD:ext partition
flash the Vanilla2.X.zip file from sd card
reboot - first boot will take a while (i.e. over 10 mins - deodexed ROMs take longer on first boot)
complete short setup and let your accounts sync
Setup GScripts
you can now one-click toggle settings at any time
-----------------------------------------------------------
Tips:
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
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")
Turn off notifications for Superuser 2.3.5 from the Settings tab of the app
Pure AOSP 2.1 does NOT play wma/wmv files. I have attempted to fix, but still a work in progress. Please download "yxplayer Pro" from the market if you need wma/wmv capabilities.
-----------------------------------------------------------
KNOWN ISSUES:
autobrightness not working
camera zoom not working
trackball notify only once with message... ** (see below)
NFL Mobile from Verizon app does not work with JIT
xda dev app may have intermittent issues logging in for first time with JIT
MMS video recived issue (true for ALL known AOSP ROMs)
-----------------------------------------------------------
** If you prefer that Notifications are mapped to the LED light instead (it will continually flash to notify you, as opposed to the default trackball light, which will only flash once), you can download the following and flash in recovery:
http://zach.xtr.i6ix.com/LED-Notifications.zip
-----------------------------------------------------------
Change Log and Such
Change Log
Vanilla 2.0.4 Change log
More minor updates...
Download: http://zach.xtr.i6ix.com/Vanilla2.0.4.zip
MD5 checksum: ae9eb1cf3c67dd08ea31c8cd5ec11dfb
fixed Contacts category bug and updated contacts
fixed NAND ext backup issue by changing the mount point for sd ext to /system/sd instead of /sd-ext/ (ALL apps2sd/cache2sd related scripts and the init.rc file)
updated a number of gscripts
New userservice framework and battery tweak service now built into the custom sysinit process
added Multi-Touch browser
updated kernel (modified CFS kernel)
updated superuser (chainsdd)
updated maps
updated street
updated voice
updated market
Vanilla 2.0.3 Change log
Minor updates...
Download: http://zach.xtr.i6ix.com/Vanilla2.0.3.zip
MD5 checksum: 8a15ca3c277ceb2b6b0e4cfeff808a96
updated to newest BFS kernel
updated build.prop to enable wma (recognized, still not playing)
install Live wallpager support via GScript (Although fun ... MOST LWP DO NOT WORK WELL ON ERIS HARDWARE )
fixed set min memory GScripts
removed default overclock (run the set cpu overclok gscript to turn on)
added Gscript support to set min CPU freq value of 19200 (for you battery save folks) and max value of 748800
updated to older version of street.apk (the street view on nav) as the current sometimes displayed a half transpartent white/black overlay
updated the icon of the settings to match the new stock 2.1 icon set...
Vanilla2.0-beta
Initial release of pure Vanilla AOSP 2.1 sweetness... A BIG thanks to tenzomonk for getting this nice little ROM going!
Download Vanilla2.0: http://zach.xtr.i6ix.com/Vanilla2.0-beta.zip
MD5 checksum: d122323a996c1d0a067578c64f0b23dd
new 2.6.29.6 BFS Kernel
"Purest" 2.1 ASOP Eris ROM to date (A LOT of work went into getting everything STOCK and running smooth and reliably for the ERIS)
Rooted with current Superuser 2.3.5
Full overclock support with built in default settings of 710400
Full Apps2sd support (easy toggle with Gscripts)
Full Cache2cache and Cache2sd support - default to /cache/ which opens up close to 250mb of INTERNAL phone storage! (easy toggle with Gscripts)
Just In Time (JIT) Compiler support (easy toggle with Gscripts)
Custom sysinit process to allow user control and optimize ROM performance settings
Current stock 2.1 Vanilla apps:
Clock (with working weather)
Browser
News and Weather
Music
Gallery 3d (smooth and fast!)
Contacts (with market facebook sync)
Email
Messaging (with working MMS)
Camera
Calendar
Calculator
Added
Wireless Tether
Wired Tether
Corporate Calendar
Dev Tools
Spare Parts
Current 1.3.2 Facebook (can be uninstalled)
Quick Boot
Custom build of GScripts
Much more that we have forgotten
This build looks very nice. I am not a big fan of the dialer though. I used that dialer in the Froyo builds and don't like how it does not have smart dialing. I rely on smart dialing very extensively. May I ask what AOSP means? How does that compare to the kernel that is used in the xtrSense rom?
Thanks for all of the hard work you devs do to give us these great roms to increase the life of the Eris. I think, and have always thought the Eris is the best phone I have ever owned.
Jeff
thanks jeff! for the dialer... we didn't change anything in regards to the "Vanilla" feel. we were both just looking to get a "real" 2.1 AOSP release out
AOSP = Android Open Source Project
as for the kernel, check this post here for full details:
http://forum.xda-developers.com/showthread.php?t=772053
Downloading right now... SO excited! ......... giggity
This ROM needs live wallpapers Other than that..... I can tell this is going to be my daily ROM already, just from playing with it for like 3 minutes. Can't wait for updates!
Thanks for the rom. Everything good so far. Just one thing could you guys keep the original eris camera format. I like the old camera that takes up the entire screen when taking pictures.
sowhat808 said:
Thanks for the rom. Everything good so far. Just one thing could you guys keep the original eris camera format. I like the old camera that takes up the entire screen when taking pictures.
Click to expand...
Click to collapse
i believe you are referring to the HTC Camera. (Un)fortunately, this ROM has no HTC framework built-in...
------------------------------------------------------------------------------
as for LWP's... that's certainly a possibility moving forward
mmm Gotta Try this !! thanks !!!
Its about time Tenzo and Zac!
Question,
I've been running the 1.9 beta. Should I do a full wipe and flash?
GPS has been working perfectly for me on that version by the way.
Glad to see two great devs on one project! Thanks for all the hard work!
So we have found one bug in the set minmemory gscripts where the vales do not set after reboot... a missplaced quotation mark : (
[EDIT] fixed and will be in next relase...
Sent from my Eris using XDA App
Seanydizzley said:
Its about time Tenzo and Zac!
Question,
I've been running the 1.9 beta. Should I do a full wipe and flash?
GPS has been working perfectly for me on that version by the way.
Glad to see two great devs on one project! Thanks for all the hard work!
Click to expand...
Click to collapse
yes... you will have to wipe. we have incorporated a lot of changes, new kernel, etc. thanks for the testing! it's much appreciated! you should have no GPS issues with this release either
Awesome! Flashing now! Great work guys! Glad to see it go public.
The best of luck to you both!
Zach and Tenzo, got a question before I flash this. Since you have freed up so much internal app space, A2Sd does not seem to be really needed. Can the ROM be booted without a partitioned card (and then of course never run the script to turn A2SD on)?
Thanks
caleris said:
Zach and Tenzo, got a question before I flash this. Since you have freed up so much internal app space, A2Sd does not seem to be really needed. Can the ROM be booted without a partitioned card (and then of course never run the script to turn A2SD on)?
Thanks
Click to expand...
Click to collapse
yup... that's how i'm running it now
tenzomonk said:
yup... that's how i'm running it now
Click to expand...
Click to collapse
Super, that is how I will try it as well.
Thanks
Great job! Thanks. I just flashed it, and so far so good. I've never had to make so few pre-flash changes before.
It seems as if the contacts are being sorted incorrectly on my phone, headings are not being displayed based on first letter. The only headings displayed are "S" and "e". Not sure if this is a setting on my end or an issue with the dialer/contacts.
Great job on the ROM, I'm always looking for good AOSP ROM.
wshuman3 said:
It seems as if the contacts are being sorted incorrectly on my phone, headings are not being displayed based on first letter. The only headings displayed are "S" and "e". Not sure if this is a setting on my end or an issue with the dialer/contacts.
Great job on the ROM, I'm always looking for good AOSP ROM.
Click to expand...
Click to collapse
ahhh, you are right! good find!
they actually do sort correctly for me... but the S and E are the only "headings" shown.
will get that fixed up
you credit nfinitefx45 for his work on cache2cache but I can't seem to pull up anything with forum search within CDMA forum.
SUPREME Mods v1.5
For CM9/ICS!
FEATURES:
Code:
-wifi speed increases
-changed bluetooth name to "Touchpad"
-increased quality of photos and videos
-added initial dalvik heapsize for better start up
-changed the wifi scan interval to 180 (save battery when not connected to wifi)
-kernel tweaks for less debugging/more RAM
-higher events per second for the window manager (smoother scrolling)
-overall performance boost and responsiveness increase with higher cache values
-disable sending usage data (not sure if functional but it was a property listed in the documentation)
-deeper sleep during the night hours for better battery life
-disables error checking
-faster media streaming
-changed device info to that of a SGH-T989 from Samsung so most Gameloft games are compatible to download the SD files
-270 degree rotation
-uses image dithering for faster performance
-keeps launcher in memory for faster launcher performance
-better battery management in terms of percentage and associated kernel actions
-better sqlite management for apps
-better sqlite management for apps
-faster app switching between google apps
-defragmentation of database files
-cleaner of temporary files at bootup that are no longer in use
If you want support, either post here or ask me on twitter: http://twitter.com/rohanXm
COMPATABILITY: Tested on Cyanogenmod Alpha 2 and the CM9 nightlies, may/may not work on other ROMs!
If you install this with ROMs other than CM9, then you will see many side effects in the Settings app, such as it displaying you are running CM9 when really you are running some other ROM. The build.prop is built off of the latest official nightly, 20120404.
DOWNLOAD:
Choose the DPI you want and download the respective one!
160 DPI: supreme-rohan-v1.5-160dpi.zip
120 DPI: supreme-rohan-v1.5-120dpi.zip
If you don't know what DPI is, download the 160 DPI version.
DOWNLOAD IS HERE: http://goo-inside.me/devs/rohan/tenderloin/SUPREME Mods
Current version is v1.5
Click to expand...
Click to collapse
INSTRUCTIONS
WARNING: Make a nandroid backup before downloading this!
If something goes wrong (even though it has been tested numerous times) its always good to have a backup! I am not responsible for anything that happens to your device as a result of this!
1. Download the .zip from goo-inside.me linked below
2. Reboot into ClockworkMod
3. Install zip from SD Card -> Browse for zip you just downloaded
4. Wipe Dalvik cache (in advanced menu)
4. Reboot
5. Heres the decision point: you can either end here, or you can continue on to install the V6 ICS Supercharger script. The process is a little bit involved, so if you don't want to continue, you don't have to. I reccomend you do continue though, as the Supercharger script makes a very big difference in terms of speed! For those of you who choose not to continue, thanks for installing the SUPREME Modpack! Enjoy your Touchpad! For those that want the ICS Supercharger too, continue below!
=======================================================
6. Download the latest Supercharger script from this post: http://forum.xda-developers.com/showthread.php?t=991276 to your /Download folder (the file is called "V6_SuperCharger_for_Android-update8.sh.txt") (Note: the name might change if a new release of the script comes out)
7. Continuing to install the supercharger script... open up a file manager and rename the file to get rid of the .txt extension (so that it becomes a .sh extension)
8. Open up the app called Terminal Emulator on your Touchpad. If its not already installed (it should have come with CM9) then just install it from the market.
7. In the Terminal, type the following.
Code:
su
Then accept the Superuser request that opens up.
8. Then type:
Code:
sh /Download/V6_SuperCharger_for_Android-update8.sh
(Note: the name might change if a new release of the script comes out)
9. The screen will display some text as the script loads up. Be patient and wait.
10. After loading, it will come to a thing where it detects what launcher you are running. Press the enter key to confirm your launcher.
11. The script will do some more stuff and then ask for what type of scrolling you want. Type in "1" without quotes to confirm you want fast scrolling to make the install process quicker and then press enter.
12. It will do some more stuff and then ask about integration. Type "y" without quotes confirming you want integration and then press enter.
13. It will do some more stuff and then ask about animations. Type "y" without quotes confirming you want to disable the animation and then press enter.
14. It will do some more stuff and then ask about what type of Supercharger you want. Type "9" without quotes confirming you want the highest and most aggressive tweaks (they work the best for the Touchpad) and then press enter.
15. The script will finish up and then ask if you want to super clean your system. Type "y" without quotes and then press enter. Your system will reboot.
16. Go to this link: http://android.mimic.ca/
17. Upload your services.jar file from the /system/framework/ directory
18. Patch the file using the online patcher
19. Download the CWM file it gives you (the .zip). Don't worry about what it says about being for Nexus S.
20. Reboot to recovery and flash the CWM file it just gave you.
Congrats, you have the SUPREME Modpack and the ICS Supercharger scripts installed! Reboot normally and enjoy!
To update, just follow the same instructions as the install directions! You will also need to install every time you install a new ROM.
Click to expand...
Click to collapse
Changelog:
4/05: -Removed the ICS Supercharger script as its creator respectfully asked for it to be removed from the package. You may still install it separately though using the instructions I posted though.
-Cleaned up the init.d file thanks to tweaks made by archrival
4/1: -Includes the ICS Supercharger Script from zepplinrox! Original thread is here: http://forum.xda-dev...44#post16635544
-Cleaned up the init.d tweak file and removed conflicting code
-Updated the build.prop to the latest official nightly
-Added database defragmentation
-Added removal of temporary system files at bootup
3/10: -MANY new tweaks!
-Fixed some wifi issues due to some unruly init.d tweaks
-better sqlite management for apps
-faster app switching between google apps
3/3: -Added an init.d tweak file!
-270 degree rotation
-uses image dithering for faster performance
-keeps launcher in memory for faster launcher performance
-attempts to always keep the home button on
-better battery management in terms of percentage and associated kernel actions
-kernel tweaks for less debugging/more RAM
2/27: -Added comments to build.prop file so that you guys can customize it easier if you want to
-increased quality of photos and videos
-added initial dalvik heapsize for better start up
2/26: -Initial release
this sounds amazing but i am just wondering if i could edit this so it doesnt touch the dpi at all? i use 132 right now and dont want to mess with it, other then that this sounds amazing
First time posting in the touchpad forums...
I applied this mod and attempted to install 9mm but still got a "not compatible with this device" error. Unless I'm in error of some sorts I believe this game still has issues running on our devices. I at least had to give this a shot to maybe see if it would help with me getting this game installed.
Nonetheless excellent work and thank you for your contribution!
slyr114 said:
this sounds amazing but i am just wondering if i could edit this so it doesnt touch the dpi at all? i use 132 right now and dont want to mess with it, other then that this sounds amazing
Click to expand...
Click to collapse
I added the build.prop text in the OP near the bottom, in a pastebin link. Copy the text from there, paste it into your build.prop, and then find the line for the density and edit that back to 132 before saving.
freaktractor said:
First time posting in the touchpad forums...
I applied this mod and attempted to install 9mm but still got a "not compatible with this device" error. Unless I'm in error of some sorts I believe this game still has issues running on our devices. I at least had to give this a shot to maybe see if it would help with me getting this game installed.
Nonetheless excellent work and thank you for your contribution!
Click to expand...
Click to collapse
I don't own the game so I was not able to test it, sorry! I know this change has worked for Modern Combat 3, Asphalt, and a couple other games. I will look into making 9mm work, since this might be a problem across multiple games!
Testing now, will let you know how it goes over the next few days
apply dalingrin's 120dpi
Click to expand...
Click to collapse
Sorry for the n00b question, but how do you apply this ? By just installing the Alpha 2 or is there a standalone zip ?
JohnKoffee said:
Sorry for the n00b question, but how do you apply this ? By just installing the Alpha 2 or is there a standalone zip ?
Click to expand...
Click to collapse
Install the zip file from the link in the first post in clockwork recovery mode after you have installed Alpha 2.
I'm on Classicnerd Butta 0.1.1-v3.2 and will definitely flash this at work to test it out.
Sent from my SAMSUNG-SGH-I727 using XDA App
Im really looking forward to a smoother scrolling experience. I love my tp immensely but I've always found the very subtle studder of scrolling to be a little displeasing when it comes to scrolling in between home screens. Does this "smooth scrolling" enhancement effect web browsing scrolling?
I am definitely going to give this a shot bud, brb with thoughts and opinions. Thanks again for your work in this community.
---------- Post added at 03:05 AM ---------- Previous post was at 02:39 AM ----------
Anyone have a link to dilinger's 120dpi fix?
Please help me to fix usb storage fix
Please help me to fix usb storage fix.Because when i connecting my touchpad to computer, nothing is happening.Touchpad memory is not opening.
i tried turning off developer mod.then also same.How to fix this
please help me
thanks
bentech4u said:
Please help me to fix usb storage fix.Because when i connecting my touchpad to computer, nothing is happening.Touchpad memory is not opening.
i tried turning off developer mod.then also same.How to fix this
please help me
thanks
Click to expand...
Click to collapse
Lmao.
Plug in your device. Then Go to: settings, then click on storage on the left. then on the top right you will see 3 vertical dots, click it for more options. "USB computer connections" will be available. Select it. Then check mark the "media device (MDP)" field.
If you're using windows, ignore the driver installer error prompt. Your TP should still be visible when you go to my computer.
Push Thanks if I helped. i hope I did. >.> lol
thanks it's working now.
freaktractor said:
First time posting in the touchpad forums...
I applied this mod and attempted to install 9mm but still got a "not compatible with this device" error. Unless I'm in error of some sorts I believe this game still has issues running on our devices. I at least had to give this a shot to maybe see if it would help with me getting this game installed.
Nonetheless excellent work and thank you for your contribution!
Click to expand...
Click to collapse
its the dpi change to 160 9mm works just fine i beat the game on my TP i use PG86100 on the build prop evo 3d
What changes did you make to make better media streaming?
I don't want to make all the changes.
Sent from my cm_tenderloin using Tapatalk
Can someone point me to dalingrin's dpi fix? Can't find it anywhere. thanks!
grukko said:
Can someone point me to dalingrin's dpi fix? Can't find it anywhere. thanks!
Click to expand...
Click to collapse
Taken from Alpha 0.6 thread on rootzwiki.
LCD Density Updates:
120: http://goo.gl/2vd7h
Revert to 160: http://goo.gl/mndEs
Click to expand...
Click to collapse
This really works! I was stuck using 160dpi on Alpha2 because 120 or 132dpi both were not smooth, they had a small skip or judder when transitioning screens. Bugged the heck out of me so I set it to 160dpi where it is smooooth.
I flash this build.prop this morning and 132 is now just as smooth! Not sure what else it fixed but it didn't break anything which is always a good thing. Me happy
Thanks Rohan!
Nice one
Changed the build.prop in notepad to 160dpi then saved over the top and just flashed, now I'm playing BackStab HD! Thank you very much!
Thanks for doing this but I have a question. In your OP, you listed:
disables error checking (may have side effects)
Does this affect the SD card error checking (fsck_msdos) that the TP does on boot, which shows up as Preparing SD card on notifications?
Btw, just a suggestion that it might be a good idea to put a line in your OP and recommend doing a nandroid backup or at least backing up of the original build prop file before flashing this. Thanks again.
Mike T
Hi guys, sorry, just got back from school. I've answered some of your questions below.
Also, just wanted to say that tonight I will be adding a whole boatload of improvements via the init.d file. I worked on it at school today for a little bit at lunch and it should bring a whole host of speed improvements and smoother aspects to CM.
@Mr.Quipster Yes, this also affects the web pages. It increases the screen's refresh rate when scrolling, thus allowing a "smoother" experience.
@ruthienu I've changed it so that StageFright, the media streaming tool in Android 2.2+ scans meta tags, as well as HTTP filesystems for media. It doesn't hurt to have these lines in there if you aren't using media streaming. It also doesn't interfere with anything else. If you want to delete it, flash the zip and delete lines 101-104 [the ones starting with media.stagefright(...)]
@webdroidmt Nope, this disables something called CheckJNI. It basically scans the system every now and then for things such as invalid variables and arrays, bad buffers, and some UTF-8 errrors. None of the errors it catches are system-threatening and disabling it frees up a substantial amount of RAM. If you do not want this to be enabled as a feature then simply flash the zip, then edit your build.prop and delete the line "ro.kernel.android.checkjni=0". And thanks for the suggestion, added a warning
Rom (Ice Cream Sandwich):
A Near stock image, modified for a clean root, busybox install
ezAcer_AV041_A500_1.31.00_WW_GEN1_RootBusybox_S.zip
(MD5: 7e9fe5642b6e082fb4382288337d8dfa)
The long overdue update to my previous Honeycomb rom
==~== Requirements ==~==
This rom requires the unlocked ICS bootloader, I also recommend my A500 Public Recovery, however all recoverys patched for the new bootloader ought to allow installation of the rom.
Bootloader install instructions are: here thanks to civato. Note for step 4 simply ensure my update zip above is either in on the device instead of the ones listed. Note instructions below before actually flashing the rom.
Additional information can be found at Skrilax_CZ's bootloader development thread here
And my A500 Public Recovery development thread here
==~== Installing ==~==
Once you have the new bootloader and ICS recovery installed (again preferably the A500 Public Recovery but any ought to work)
Cleaning your tablet:
If you are attempting to upgrade the tablet without wiping (and there is no need to wipe if you are currently running my acer7.014.14 rooted image
Select "cleanup tab" in the main menu of the A500 Public Recovery
(If you are using another recovery, select the options for a. Wipe Cache, b. Wipe Dalvik Cache, and c. Fix Permissions)
Install the rom:
Select "install zip from sdcard" and navigate to ezAcer_AV041_A500_1.31.00_WW_GEN1_RootBusybox_S.zip
Thats it
==~== Root ==~==
Applications are granted Superuser access from ChainsDD's Superuser.apk as usual (a request asking you will appear when an application requests root, and permissions granted before the upgrade may still be active post upgrade)
adb shell: ADB by default will not have root access here you have the following options:
> if you run 'adb root' all adb operations will have root until reboot (aka 'adb shell' and 'adb remount')
> If you have a non-root 'adb shell' you can switch to root with the 'su' command
> If you wish to restore the permanent adb root on boot add the following line to the build.prop 'service.adb.root=1' this will force the old behavior of root always via adb without using the 'adb root' command.
This change has been made as its a little more secure, (However obviously still lets anyone with access to the USB port access to all the tablets data)
==~== Features ==~==
This rom is intended for users that wish a nearly stock system configuration, however either need root and busybox, or enjoy conducting more advanced tasks at the command line and wish a smooth root experience.
In addition some other small mini-fixes have been applied to the image in hope of a smooth experience.
Here is a list of the features and changes in the rom
Modified ADB to allow adb root to operate without changing the production build properties
Kernel patched to allow system remount
Busybox built from CM9 source tree and integrated into the rom
runparts (ie /system/etc/init.d functionality)
GPS lto fix thanks to waydownsouth
FDUpdater (ie system update) removed to not be prompt for an update you can't install.. if you want it the original app is in the system folder of the update.zip, (FDUpdater.apk) its not odexed so install normally)
Kernel modules md4.ko sha512_generic.ko and cifs.ko added to the rom (md4/sha512 is loaded on boot via an init.d script, users of cifs need to check the "Load cifs module" option in CifsManager.
Added Superuser
DHCP Infinite Lease bugfix (why has google not fixed this) applied as a patch to the framework.odex
Rom is still odexed (and I re-odexed the one changed odex for the DHCP patch)
Developers wanting more details or the source to anything I changed can see this detailed modification guide: http://pastebin.com/ApUjMDJ7
Note to anyone wishing to make a modification to the rom they are flashing, everything in the system folder of the update.zip is unchanged from the original rom. (when flashed the system is patched and augmented via various files and tools in the custom directory, also the boot image is pre-patched)
==~== Extras and Addons ==~==
** Overclocked test kernel: See my ezT20 kernel here (previously OCTestV3 here
(kernel last updated June 18th 2012)
** Disk IO enhancement: significantly increase diskio scores, and make the table slightly more responsive when reading/writing to flash: On this post
(diskIO last updated June 5th 2012)
==~== Tips and Tricks ==~==
This section is where I try to explain how to get the most of your tablet, and solutions to common complaints due to changes between versions.
-----) Rom "Bloat" (------
First half of what people call rom bloat is not quite true, (there is such a thing, and problems related to it)
Our tablets have 590MB system partition, a 97MB vendor partition, a 1GB cache partition, and the rest of your tablets space in a data partition (mine is 27GB, but if you have a smaller tablet model it will be less) All roms will have currently the same split between the partitions.
Its only that last partition that contains your data, the system/vendor partitions are by default read only, and the cache partition is temporary data.
System apps are on the two read only partitions, thus removing them for the most part will not cause more data to be available to your apps. Also this is storage space so having more "free" will not speed up your device (well as long as we are not too close to full.. and this rom is not)
Most of these apps play nice, they don't run unless you select them thus you can ignore they are on your tablet and all will be just as fast as if they were never installed
There is however one *Problem* Applications pre-installed that run constantly in the background that you the user are not interested in.
Solution: Freezing apps
* Goto Settings-> Apps-> All
* For any of the following that you do not use:
> Photo Browser 3D
> SocialJogger
> Acer Media
Select the app,
Choose Disable
Clear Data
If you use the app, obviously keep it enabled, also you can return to this screen and re-enable the app.
-----) Screen flickering/brightness oddities (------
I have had some brightness issues initially, simple fix was to go into settings->display->brightness uncheck auto bightness, lower the meter, and re-check auto brightness
-----) Sluggish system (------
Make sure on first boot you give the system some time (2h/3h after upgrading or re-installing where there is a large collection of media on the tablet) before measuring speed, as the system may be still sorting/indexing tablet data and will speed up when done.
Also while apps are installing the system may behave slower (if you have many market updates happening in the background)
Otherwise check running processes in settings to see if anything may be slowing down your tablet in the background (Settings -> Apps -> Running)
==~== Credits ==~==
civato - for his guide to installing the new bootloader and some testing of some of the tools I use to patch the rom up
waydownsouth - for the GPS patches (and work on CM9 for our tablets as it helped create some of the utilities in use here)
CyanogenMod and Team - For the idea of the root change, modifications to the bustybox build, and Koush's ClockworkMod recovery
vache - various insight all over XDA on how our device works (and leaks but this build is from the official OTA I recived)
Skrilax_CZ - for the unlocked bootlaoder, without which we couldn't run these roms
And the many others that provide development insight, source code, and examples here on XDA
2nd Post
reserved for future
Nice and congratulations with your release.
I will ad a link to this rom in the unlocked bootloader guide.
Overclocked kernel [May 23rd 2012]
(wow I think we can hear crickets in here..)
Anyway using the now released source code from acer, and richardtrip's OC patches from HC I now have an overclocked kernel.
As of V3 I also have the voltage controls patched up from richardtrip's kernel.
[size=+2]AcerOCTestV3_S.zip[/size]
MD5: 6907e7585fedf534261cc8ebe23d824a
Instructions are simple: flash from recovery
Links to the github source and other information on the AcerOCTest kernels is in this related notecard
While I've only tested it on this rom, the installer is using koush's anykernel logic (or one of my own flavors of that logic anyway) and thus this ought to cleanly install on any rom based on the stock ICS kernel regardless of the tweaks the rom creator may have added.)
Also I've not had much time to test so let me know if there are issues
----
List of all versions:
V3 - AcerOCTestV3_S.zip (md5: 6907e7585fedf534261cc8ebe23d824a) May 23rd 2012
V2 - AcerOCTestV2_S.zip (md5: da01a90dda3916ec55ebb62bbb1164f1) May 22rd 2012
V1 - no public binary (caused reboots on tablet sleep)
Just tried the OC kernel on Civato's latest rom and it does work. Can't go over 1.2ghz without a reboot, but that extra bit of speed is nice.
Jigga0o7 said:
Just tried the OC kernel on Civato's latest rom and it does work. Can't go over 1.2ghz without a reboot, but that extra bit of speed is nice.
Click to expand...
Click to collapse
what dosn't work? >1.2ghz or flashing it on Civato's rom
the rom ought to work, it extracts the current boot.img, swaps the zImage (leaves the ramdisk) and swaps the modules in /system/lib/modules.
as for the speed.. your device is intended for 1.0ghz any thing extra is a bonus.. the kernel thus boots at 1.0
edit: although I'll look into it some may be a new verification in the updated kernel. the tegra2 OC logic is much more complicated than the msm logic I'm used to on the HTC dream.. I'm more worried about reboot-on-wake bugs I had in earlier revisions
ezterry said:
what dosn't work? >1.2ghz or flashing it on Civato's rom
the rom ought to work, it extracts the current boot.img, swaps the zImage (leaves the ramdisk) and swaps the modules in /system/lib/modules.
as for the speed.. your device is intended for 1.0ghz any thing extra is a bonus.. the kernel thus boots at 1.0
Click to expand...
Click to collapse
Oh I said that it does work and that the only thing is can't go over 1.2ghz. We've got a nice speed bump here, thanks for your hard work.
Jigga0o7 said:
Oh I said that it does work and that the only thing is can't go over 1.2ghz. We've got a nice speed bump here, thanks for your hard work.
Click to expand...
Click to collapse
looking closer its a but..
So now I have two OC tests I've made.. the first one I didn't publish because while it could go > 1.2 it crashed when you put the tab to sleep. (at least when USB wasn't connected)
This one crashes when you go over 1.2.
maybe if a combine them I can get something that works...
Perhaps a slight voltage bump is needed to get beyond 1.2? In either case, 1.2ghz feels leaps and bounds faster than 1ghz using this rom. I'm starting to feel like we don't even need cyanogenmod 9 for the a500.
Jigga0o7 said:
Perhaps a slight voltage bump is needed to get beyond 1.2? In either case, 1.2ghz feels leaps and bounds faster than 1ghz using this rom. I'm starting to feel like we don't even need cyanogenmod 9 for the a500.
Click to expand...
Click to collapse
No.. well maybe but you not getting that far.. its a kernel BUG condition, meaning some code found some invalid input and refused to process it, instead triggered a reboot.. looking at the diff of mycode and the code in the CM thread.. no logic is different so i'll need to poke min/max rail voltages. (still sorting out all the voltages and CPU speeds.. the dream had it all in one large table .. here it seems spread out in various places between two files..)
(I'll also try to include the voltage manipulation patches just making sure things are stable first thus 1.2ghz is a better testing speed for me than trying to Max my device)
As for CM..it seems to have many interesting features.. but at some point I'm not sure its direction matches my interests.. (maybe its just become too much of a kitchen sink i don't know, that or too much now in aosp) I'm sure to look at it but probably start an aosp build with cherrypicked features I like.. until then this tweaked ics rom will need to do.
Fyi I haven't had a single issue on your kernel.
Been waiting on this! Thanks ezterry.
Jigga0o7 said:
Fyi I haven't had a single issue on your kernel.
Click to expand...
Click to collapse
Well next version will have voltage controls and working higher overclock speeds
(just ironing out some minor issues with the voltage control)
Some side info and feedback I get from some users that are on ICS bootloader and still getting SoD
I made a boot.img with in the "boot.img-ramdisk" / postboot.sh = I deleted the following line
"echo 7> /sys/module/wakelock/parameters/debug_mask" and it solves the SoD problem some still have when they are on ICS bootloader.
Just had a other pm today confirming it worked.
And I'm testing your modules and OC zImage with this modded in the boot.img-ramdisk (and my other tweaks) and I don't get any SoD , screen off , back on no problem.
Also confirming 1200 is max , over that it will reboot.
Ezterry,
Thanks!
very nice kernel, I flashed the 'civato' version to avoid SOD ...
Works nicely in 1.2 Ghz...
Btw, the old "No-Frills CPU control" apk doesn't apply the upper 1.2 Ghz frequency at Boot as asked.
Do you know another tool working to apply OC at boot?
(I'm using Civato's last version of flexreaper ROM)
=================================================================
>>>>> I have found a solution: I now use System Tuner PRO with its OC setting and it works <<<<<
=================================================================
civato said:
Some side info and feedback I get from some users that are on ICS bootloader and still getting SoD
I made a boot.img with in the "boot.img-ramdisk" / postboot.sh = I deleted the following line
"echo 7> /sys/module/wakelock/parameters/debug_mask" and it solves the SoD problem some still have when they are on ICS bootloader.
Click to expand...
Click to collapse
.. I think this solution has nothing to do with the debug variable and everything to do with *forcing* the user to install a ICS kernel and stop messing around with the HC kernel they had earlier. (since you are installing a new boot.img)
So says the code anyway. If you want to prove it wrong after the crash + quick reboot get your users to dump the last_kmsg and output of dmesg so we can actually debug what is going on.. well unless its just the wrong kernel
But if the "obecalp" works to get some your users to install the right thing and so they fix there own problem.. so be it.
--
I have to inform users of my rom its no longer my rom if they install one of your (or anyone else's) full boot images and not to complain of any resulting bugs here.. If anyone with this rom has a SoD (none reported yet.. but I block installation on the old HC bootloader) let us know if you have such an issue. (just want to add if the full boot image was modified from the one in this rom, and intended for users of this rom that isn't an issue.. the issue is when its for another rom)
Its a bit different when you flash my update on another rom, since I only swap the kernel and leave the ramdisk as is, (by unpacking and repacking the boot.img) the rom designers changes stay intact.. well unless they had a kernel module that I've not included.. but even then we will need to re-build that module)
and you can test this after boot enter terminal and run echo '3> /sys/module/wakelock/parameters/debug_mask' that is the default.
(If it is disabled it just won't print the list of wakelocks to the kernel log on suspend..)
UPDATE @@
http://forum.xda-developers.com/showpost.php?p=26432810&postcount=4
ezterry said:
[size=+2]AcerOCTestV3_S.zip[/size]
MD5: 6907e7585fedf534261cc8ebe23d824a
Click to expand...
Click to collapse
Hopefully fixed the max speed bug, and added in the voltage controls.
Not much else yet has changed. but seems stable.
Its the same anykernel package as last time so it should cleanly swap the kernel (leaving the previous ram disk) for any ICS stock kernel based rom.
(Is there one app out there that actually knows how to successfully set *both* cores frequency and set voltage on boot, without giving the world access to the /sys files [so a malicious app cant overclock+fry the device or under clock it so it feels painfully slow]... soon I'll just write an init.d script for myself to echo the values directly into the kernel settings /rant)
I use setcpu.
civato said:
I use setcpu.
Click to expand...
Click to collapse
I don't like that he (and has always) granted global write permissions to the /sys/ files controlling the CPU/Voltage settings .. and it was acting flaky on voltage settings on boot.
Voltage Control looked good until a verification in /sys indicated if left the second CPU core at 1GHz
Now poking system tuner/system tuner pro.. many interesting features. Not sure they quite understand use root to write the value.. or set the file to your own ownership..
*ANYWAY*
you can check these yourself manually at the command line/adb shell:
CPU0: /sys/devices/system/cpu/cpu0/cpufreq
CPU1: /sys/devices/system/cpu/cpu1/cpufreq
current status of the voltages is in the readonly: frequency_voltage_table
list readonly of available frequencies is: scaling_available_frequencies
list readonly of available governors: scaling_available_governors
the current min frequency: scaling_min_freq
the current max frequenct: scaling_max_freq
the current cpu governor: scaling_governor
the current undervolt levels (negative values are over volting): UV_mV_table
UV_mV_table is in the same order as frequency_voltage_table, and if written to with the same number of values will update the voltage levels.
I got a question , why :
sha512_generic.ko = what does this do ?
modules.order = why does it need to know the order ?
** DoPa6 (AOSP - Marshmallow) ** is now available - see this post for details and downloads
Click to expand...
Click to collapse
** DoPa5 (AOSP - Kitkat) ** is now available - see this post for details and downloads
Click to expand...
Click to collapse
DoPa v2.7 is a ROM for Sero 7 Pro owners everywhere. Whether bought in the US, Britain, Australia, Germany, or elsewhere, your tablet is supported.
The ROM starts with well-tested AOSP code and adds core functions where needed but skips the frills that are easy to add on - and remove when they cause problems. It's aimed at people who want to choose their own features and not have them imposed by the developer.
New / Improved
International Support - a single ROM for all Sero 7 Pros sold worldwide
New in v2.7 - support for the German model of the Sero 7 Pro (m470bsg)
Speed Control - a unified kernel provides speed when you need it and stock performance when you don't.
Use the new Performance page in the Settings app to control it
exFAT - support has been moved into the kernel for improved performance
Boot Animation - a handsome new DoPa animation thanks to @mikembley, our first-ever UK user
To get you started customizing your ROM, v2.7 offers these add-ons:
built-in: SuperSU, Xposed Installer GravityBox, Phab7
optional: have your tablet claim it's a Nexus7 to get more apps in PlayStore
The package does not include any Google apps (e.g. Playstore). See this thread for links to the latest GApps packages.
Installation
UK / AU / DE / First-time Users
If you're upgrading from a stock ROM (any variety), please click the "show content" button and read the instructions very carefully - they're long but your tablet's continued good health may depend on it!
STEP 1: Install Philz Touch Recovery
Users outside the US must use this version of Philz to install the ROM - neither the stock recovery nor other versions of CWM or Philz will work. Users in the US should use it just to avoid problems.
Stock Recovery
If you still have the stock recovery program you'll have to use the 'fastboot' program to install Philz. On Windows, this requires installation of the 'ADB' USB drivers while in fastboot mode (see below). A package containing the drivers, fastboot, adb and other files can be found in the 2nd posting on the DoPa Stock ROM thread. Note: there are several batch files (*.bat) in the package - do NOT run them.
put fastboot.exe in a convenient directory, then unzip sero7pro-philz6.58.0-dopa-v2.7.zip and put the file philz.img in the same directory (you won't need the other files)
unplug any USB cable, then press and hold Power+VolumeUp; the word "fastboot" should appear on the screen (nothing further will appear)
plug the USB cable from your PC into the tablet, then install the driver (open Device Manager, right click on "Other Devices->Fastboot", then select "Update Driver Software")
after installing the driver, open a command prompt ("DOS window") and change to the directory containing the files
enter fastboot flash recovery philz.img
when done, force the tablet off, remove the USB cable, then reboot into recovery: Power+VolumeDown - you should see the word "recovery", then the Philz menu
CWM
If you have CWM installed, copy sero7pro-philz6.58.0-dopa-v2.7.zip to an SD card, insert it in the tablet, then:
remove any USB cable, then boot into recovery: Power+VolumeDown
select "Install Zip", then "Choose zip from /storage/sdcard1"
select the file, then OK the selection
when done, back out to the main menu, select "Advanced options", then "Reboot recovery"
after the initial "recovery" screen, you should see the Philz menu
Regardless of how you install Philz, the result should be the same. If it boots OK, compatibility is assured
STEP 2: Backup
I can't emphasize this enough: you must make a backup of your existing ROM. If something goes wrong, there's no way to get your device working again other than to restore it using the backup you've made. There's also another reason to do a backup: before installing the new ROM, you will have to reformat your /data partition. This will wipe out your apps, your settings, and most importantly, all the music/photos/etc stored on your "internal SDcard". These last items can be restored if you follow the instructions below:
ROM
You must do your backup onto a real SD card that you can remove because your "internal SDcard" will be erased in the next step. In fact, it wouldn't be a bad idea to do two backups (preferably to different cards) just in case one is faulty.
on Philz main menu, select "Backup and Restore"
next, select "Backup to /storage/sdcard1" (the 6th item on that menu)
if there's enough space on the card, the backup will start without any further prompt; it could take anywhere from 3 to 15+ minutes depending on the amount of data and the speed of your card
if needed, you can enable compression to create a smaller backup: select "Misc Nandroid Settings -> Default Backup Format -> tar + gzip", then on the previous menu, tap on "Compression" to set the appropriate level
Internal SD card
This is optional but worthwhile if you have files you value stored on the tablet:
on Philz main menu, select "Backup and Restore"
next, select "Custom Backup to /storage/sdcard1" (the 9th item on that menu)
on the next screen, deselect everything, then select "Backup /data/media" (the next-to-last item)
finally, select "Start Custom Backup Job"
STEP 3: Install the DoPa ROM
Before you begin, you may want to download a Google Apps ("Gapps") package that you can install after the ROM. See this thread for a selection of packages. To avoid complications, I'd suggest choosing the "Nano Modular Package" to get just the basics - you can always upgrade later. Put your Gapps package along with the ROM zip on an SD card and insert it into the tablet - you can use the same card you're using for your backups.
on Philz main menu, select "Wipe and Format Options", then "Custom Format Options"
select "format /data and /data/media (/sdcard)" (the 8th item), then OK your choice
back on the main menu, select "Install Zip -> Choose zip from /storage/sdcard1"
select sero7pro-aosp444-dopa-v2.7.zip, then OK your choice - the install process should take about 40 seconds
next, install your Gapps package
return to the main menu, select "Reboot System Now", then hold your breath for the next 3-4 minutes
the Hisense screen should be up for less than a minute, followed by the DoPa boot animation for another 2-3 minutes
when the Google setup screen appears, you'll probably get a warning that "Bluetooth Sharing" has stopped - after you clear it, you'll never see it again
If the boot animation is still running after 5+ minutes, force the tablet off, then reboot. If that doesn't fix it, try formatting /data again. If it still doesn't work, restore your tablet from your backup ("Backup and Restore -> Restore from /storage/sdcard1"), then post a message here. If everything works out as hoped for, re-read the first posting in this thread for details on some of the features (and problems) of this ROM.
Upgrades
While any SELinux-enabled version of CWM or TWRP can be used to install the ROM, the companion Philz Touch CWM-based recovery is highly recommended if you use exFAT-formatted SD cards.
from DoPa AOSP Kitkat ROMs (v1.0-v2.6) - no need to wipe or format anything!
from pre-Kitkat (v4.4.x) or any CM-based ROMs - wipe your /data partition before installing to avoid unnecessary problems.
install sero7pro-aosp444-dopa-v2.7.zip
- the installer will wipe (but NOT format) /cache and dalvik-cache for you
install your preferred Gapps package
- upgraders: this is required to prevent your downloaded Google apps from crashing
optionally, install the Nexus7 spoof (sero7pro-nexus7spoof-dopa-v2.7.zip)
reboot (ignore any "fix root" prompt - it's incorrect)
f2fs / ext4 Migration
This DoPa ROM gives you the flexibility to format any of your built-in partitions using either the f2fs or ext4 file systems.
As part of your install - or at any time - you can switch formats without losing any data. Click "show content" for instructions.
If you haven't already installed Philz Touch Recovery, please do so first. Philz has gotten complicated, so read this carefully!
make a nandroid backup to your external SD card
select Wipe and Format Options, then Custom Format Options
select toggle f2fs <-> ext4 migration
- be sure there's a confirmation message at the bottom of the screen
select each partition you want to convert or wipe, then select the format and OK your choice
Important: to convert your /data partition, you must select format /data and /data/media (/sdcard)!!!
use Custom Restore from /storage/sdcard1 to restore the contents of the partitions you reformatted
Notes
Speed Control - this version uses a redesigned kernel that caps processor speeds at stock levels during start-up, then adjusts them once the tablet is up and running. Go to Settings->Performance to enable this feature, and to set the top speeds for the CPU (1.0-1.5ghz) and GPU (448-520mhz). When disabled,the processor will remain at stock speeds (1.2ghz/448mhz) unless changed by a 3rd-party app.
Encryption - the first time you formatted your /data partition, you lost the ability to encrypt your tablet's data. Using the companion Philz Touch Recovery to reformat /data (using either filesystem) will restore that ability. To preserve your existing data, do a backup first, then restore just /data when done. Note: you must select "format /data and /data/media (/sdcard)" when reformatting.
OTG Charging Support - this kernel supports charging the tablet while an external device (flash drive, keyboard, etc.) is attached to the USB port. This feature requires either an OTG 'Y' cable or an OTG USB hub, and the AC adapter that came with the tablet. For this to work, power must be connected to the cable or hub before plugging it into your tablet. The OTG device(s) can be attached/detached at any time.
WiFi Display (a.k.a. Miracast) - video works but its performance may depend upon your TV; audio does not work.
Bluetooth Sharing - on the initial boot, this service will FC due to a timing issue. The system will restart it and you should never see this error again.
Added/Changed in v2.6
International Support - added support to the kernel for the British and Australian models of the Sero 7 Pro
Overclocking - replaced separate standard and overclocked kernels with a unified kernel that uses less power when overclocked; added a new Performance page to the Settings app to control it
exFAT Support - moved exFAT support to the kernel for improved performance
Boot Animation - added a custom boot animation created by @mikembley
Added/Changed in v2.51
Flexible Formatting - added F2FS support for the /thirdparty and /mnt/modem partitions
Bug Fix - enabled Philz Touch Recovery to format the /thirdparty and /mnt/modem partitions using EXT4
Added/Changed in v2.5
Flexible Formatting - enabled use of either F2FS or EXT4 for any of the built-in partitions
External Storage - added support for F2FS, and for devices formatted without a partition table (i.e. Windows-style "super-floppies")
Android version - upgraded from AOSP 4.4.4_r2 to AOSP 4.4.4_r2.0.1
Recovery - added a DoPa version of Philz Touch Recovery
Added/Changed in v2.1
SD Cards - added support for SD cards formatted with the NTFS or exFAT filesystems
Android version - upgraded from AOSP 4.4.4_r1 to AOSP 4.4.4_r2
Added/Changed in v2.0
Google Now - voice activation (i.e "OK Google") now works in the Google Now launcher
kernel - added OTG charging support.
Credits
ziddey
randomblame
davepmer
the CM team
Downloads
sero7pro-aosp444-dopa-v2.7.zip the full ROM
sero7pro-nexus7spoof-dopa-v2.7.zip identify tablet as a Nexus7 to (possibly) show more apps in PlayStore
sero7pro-philz6.58.0-dopa-v2.7.zip a customized version of Philz Touch CWM-based Recovery v6.58.0
sero7pro-format-thirdparty.zip - only needed if you are downgrading from DoPa6 (Marshmallow) to previous versions (i.e. this one)
GPL Notice: the source code for this kernel is available at https://github.com/dolorespark/android_kernel_hisense_m470bsa on the 'master' branch.
Thanks man been running it since day one no problems and very stable.
Can We call these the Semi OFFICIAL ROM ?
I installed v1 after it booted up play store wasn't installed. Did any one else experience this? I did a dirty flash and a full wipe.
Sent from my Sero 7 Pro using xda app-developers app
How much free space should there be on a system after a fresh install?
datboy143 said:
I installed v1 after it booted up play store wasn't installed. Did any one else experience this? I did a dirty flash and a full wipe.
Sent from my Sero 7 Pro using xda app-developers app
Click to expand...
Click to collapse
I followed the instructions and noticed the same thing and gmail kept crashing. Flashing the latest gapps will fix all of that. I still have some testing to do and will report back later.
Gazoo119 said:
I followed the instructions and noticed the same thing and gmail kept crashing. Flashing the latest gapps will fix all of that. I still have some testing to do and will report back later.
Click to expand...
Click to collapse
Ok will do thanks
Sent from my SGH-I777 using xda app-developers app
GPS and Google music
I noticed on version 0 that GPS could take awhile to lock on, and if you turned it off and back on that sometimes it wouldn't lock on at all. I also noticed an issue when running Google music where it would freeze and cause the tablet to reboot. Anyone having these issues on the new build? Otherwise, this is one of the cleanest KitKat builds I've used
gotshores said:
I noticed on version 0 that GPS could take awhile to lock on, and if you turned it off and back on that sometimes it wouldn't lock on at all. I also noticed an issue when running Google music where it would freeze and cause the tablet to reboot. Anyone having these issues on the new build? Otherwise, this is one of the cleanest KitKat builds I've used
Click to expand...
Click to collapse
Don't use Google music but I do use scanner radio and whenever I switched streams the tablet would freeze and I would have to hold the power button to turn the tablet off.
Now its working like it should. So this latest build might fix Google music.
Another issue I was having is when I opened the calendar it would not close hitting the back button. Its closes fine now.
The GPS doesn't seem to load any slower for me than it did with the stock ROM but I don't use it much.
Anyway I would recommend trying this latest build. Just make sure you wipe cache and dalvik cache and flash the latest gapps. Everything should still be the same as before when you boot with the new ROM and hopefully you will notice some improvements.
---------- Post added at 07:31 PM ---------- Previous post was at 07:22 PM ----------
dolorespark said:
This is a plain-vanilla build of KitKat for those who prefer their enhancements added on rather than built in.
Click to expand...
Click to collapse
Just want to thank you for fixing the sound bug. V4A is working perfectly and as far as I can tell so is everything else. I will keep testing and if I run across anything strange I will post here. Your work on this is very much appreciated
dolorespark said:
This is a plain-vanilla build of KitKat for those who prefer their enhancements added on rather than built in. The only changes to the AOSP and kernel code are those needed to ensure compatibility or to enable standard features Hisense omitted (e.g. USB-OTG support). Because it relies on well-tested AOSP code, it is likely the most stable KitKat ROM available for this tablet. For the same reasons, it is almost certainly not the fastest KitKat ROM either.
To make it more functional, the package includes a handful of apps most people find useful: SuperSU, ES File Explorer, Xposed Installer, GravityBox, and my Phab7 UI switcher. To avoid the wrath of Google, it does not include any GApps; see this thread for links to the latest packages.
Installation
Having an SELinux-enabled version of CWM or TWRP installed is a prerequisite. You can find versions built by randomblame here or by davepmer here.
If you're upgrading from v0 of this ROM, clearing cache and dalvik-cache should suffice. Otherwise, do a full wipe of both your data and cache partitions. As always, a backup of your existing setup is recommended.
Notes
All features should be present and work as expected with these exceptions:
WiFi Display (a.k.a. Miracast) - video is enabled but very slow; audio is disabled because it doesn't work and generates 45 error messages per second when enabled
SELinux - the kernel runs in permissive mode due to missing entries in its configuration.
As these issues are resolved, the ROM will be updated accordingly.
Credits
randomblame
davepmer
the CM team
Download
sero7pro-aosp442-dopa-v1.zip
GPL Notice: the source code for this kernel is available at https://github.com/dolorespark/android_kernel_hisense_m470bsa on the 'master' branch.
DoPa
Click to expand...
Click to collapse
Thanks for the rom. After flashing the rom I rebooted, powered down and installed gapps. On reboot I got a message about root access possibly being lost and offering to fix it, I said yes. First time I get that, is it ok? (It seems to be working ok)
chopin_k said:
Thanks for the rom. After flashing the rom I rebooted, powered down and installed gapps. On reboot I got a message about root access possibly being lost and offering to fix it, I said yes. First time I get that, is it ok? (It seems to be working ok)
Click to expand...
Click to collapse
This is normal..
Sent from my Sero 7 Pro using XDA Premium 4 mobile app
enfermo said:
Can We call these the Semi OFFICIAL ROM ?
Click to expand...
Click to collapse
Generic, yes - (semi-)Official, no.
datboy143 said:
I installed v1 after it booted up play store wasn't installed.
Click to expand...
Click to collapse
Gazoo119 said:
I followed the instructions and noticed the same thing and gmail kept crashing. Flashing the latest gapps will fix all of that.
Click to expand...
Click to collapse
As noted in the OP, none of the GApps (e.g. Playstore) were included in this ROM. I have updated its verbiage to be even more explicit. As to GMail crashing, I'm a little puzzled how that could happen if it wasn't included - did you mean the generic Email app?
gotshores said:
I noticed on version 0 [...] an issue when running Google music where it would freeze and cause the tablet to reboot. Anyone having these issues on the new build?
Click to expand...
Click to collapse
I hope not: v1 wouldn't have been released if that bug were still present. The problems you encountered were caused by enabling sound effects, either built-in or 3rd-party - the notes for v0 said as much. Perhaps Google Music enabled them automatically.
chopin_k said:
Thanks for the rom. After flashing the rom I rebooted, powered down and installed gapps. On reboot I got a message about root access possibly being lost and offering to fix it, I said yes. First time I get that, is it ok? (It seems to be working ok)
Click to expand...
Click to collapse
I ran into that too - and something even odder. SuperSU's su and daemonsu program files should have a flag that marks them as authorized to give root access. That flag is now missing but I can still get root whenever needed. I don't know if this is to be expected with SELinux in place or just something specific to SuperSU. I'll investigate...
tinybeetle said:
How much free space should there be on a system after a fresh install?
Click to expand...
Click to collapse
After installing the ROM, the "Gapps Standard" package, and Antutu, Settings->Storage says I have 5.48gb available. This is the free space on your /data partition and includes the space used by your emulated SD Card (which is actually just a subdirectory of /data).
"Smart ass alert"
Not only was playstore not installed, it doesn't give me the winning lottery numbers for next week! What gives?
Ok, being serious, Thank you for your time and effort. This weekend I am going to finally give this a try.
Dolorespark,
I haven't messed with any sound effect settings, so it must be Google Music messing with things. Have you noticed any issues with GPS? I can run any of the other rom's, including CM11, and it locks on immediately, but it seems random with AOSP. Sometimes I'll wait a coupled of minutes and it'll get a lock, and other times it won't lock on at all. Anyway, thanks for all you do. I'll keep testing, and keep my trusty backup of DOPA v2.
Working brilliantly so far. V0 to V1 smooth after adding gapps back to the mix. Sounds like time to reinstall V4A and sync some commute podcasts!
Thanks Dolorespark!
envygreen said:
Working brilliantly so far. V0 to V1 smooth after adding gapps back to the mix. Sounds like time to reinstall V4A and sync some commute podcasts!
Thanks Dolorespark!
Click to expand...
Click to collapse
intermittently get google services has stopped.... only that but everything looks good so far.... anything to fix google services stopping? also had a root fix need after rebooting, did yes and everything is ok... thanks DOPA....
dolorespark said:
I hope not: v1 wouldn't have been released if that bug were still present. The problems you encountered were caused by enabling sound effects, either built-in or 3rd-party - the notes for v0 said as much. Perhaps Google Music enabled them automatically.
Click to expand...
Click to collapse
I had this issue on v0 as well and it seems that it's not gone yet. I only wiped dalvik & cache coming from v0 so I'm not sure if that's part of the problem, but I'm still experiencing the Google Play Music crash. It only seems to crash when playing content that hasn't already been cached locally. Attached is a logcat.
dolorespark said:
As noted in the OP, none of the GApps (e.g. Playstore) were included in this ROM. I have updated its verbiage to be even more explicit. As to GMail crashing, I'm a little puzzled how that could happen if it wasn't included - did you mean the generic Email app?
Click to expand...
Click to collapse
No it was gmail. It would close followed by the message "unfortunately this application has closed" or something like that. It wasn't really crashing but rather would not stay open. Anyway flashing the latest gapps fixed that and all is good for me so far.
I played with the tablet extensively last night and did not experience any problems. Even movies, streaming or local using XBMC play using a bluetooth headset. There is no stuttering as there was in all of the previous Jelly Bean roms, stock....DoPa1 and DoPa2. I don't know if that was a KitKat fix or what but I am very happy with the stability of this rom and the fact the XBMC bluetooth bug was fixed is icing on the cake. Of course V4A makes it even better.
I will continue to run the rom and will post if I find any bugs. Thanks again.:good:
Been running since v1 was posted. Have to say the music bug is no more! Listening to lucky mixes all day today and email, g+, and everything my wife and kids have done on it. No problems! Thanks You have really taken your time to make this rom perfect!!!!
Gazoo119 said:
[gmail] would close followed by the message "unfortunately this application has closed" or something like that. It wasn't really crashing but rather would not stay open. Anyway flashing the latest gapps fixed that and all is good for me so far.
Click to expand...
Click to collapse
nccruz said:
intermittently get google services has stopped.... only that but everything looks good so far.... anything to fix google services stopping?
Click to expand...
Click to collapse
Did you use the latest GApps package? As Gazoo119 noted, that fixed a problem with another app that uses Google Play Services. If the problem persists, you may want to go to Apps->Google Play Services, then tap the "Manage space" button. On the next screen it lets you clear all data.
gotshores said:
Have you noticed any issues with GPS? I can run any of the other rom's, including CM11, and it locks on immediately, but it seems random with AOSP. Sometimes I'll wait a coupled of minutes and it'll get a lock, and other times it won't lock on at all.
Click to expand...
Click to collapse
I hadn't tried GPS at all until you mentioned it. I installed Google Maps but couldn't get a lock at all. It's raining here, so I couldn't get fully in the clear. Instead I sat in my car and it still did nothing. Finally, I forced-stopped the app, cleared data and cache, then retried. This time it only took a few seconds to find me. I then turned off GPS, rebooted, and moved to my semi-covered patio. After getting everything going again, it took 10-15 seconds to get a rough fix (off about 70 feet) and it continued to hold it even after I went inside. You may want to try clearing Maps' data (if that's what you're using) to see if that helps.
unomar said:
I had this issue on v0 as well and it seems that it's not gone yet. I only wiped dalvik & cache coming from v0 so I'm not sure if that's part of the problem, but I'm still experiencing the Google Play Music crash. It only seems to crash when playing content that hasn't already been cached locally. Attached is a logcat.
Click to expand...
Click to collapse
Whatever crash you're seeing isn't the one that I fixed. That one was produced a full-blown hardware crash with a register dump. Your logcat doesn't show a register dump or even a Java runtime exception dump. There were two errors that caught my eye but I don't know if either would cause an "Unfortunately..." popup.
Code:
04-08 09:40:24.213 E/DownloadTaskImpl( 3156): Download failed because of IO Error: Socket closed
04-08 09:40:24.213 W/DownloadTaskImpl( 3156): Experienced error when trying to download: [mId=[7871, DEFAULT] mTrackTitle="Le onde" mRemoteId=9ea5817b-9753-348e-af52-ea7c0947c6cb mSourceAccount=1954430662 mPriority=3 mOwner=MUSIC_PLAYBACK mSeekMs=0 mRetryAllowed=true mFileLocation=[mFullPath=/data/data/com.google.android.music/files/music/mplayback_7871.tmp mStorageType=INTERNAL mCacheType=2] mExplicit=false]
Here, the (software) communication link being used to download "Le onde" was broken. Later on, you got this error:
Code:
04-08 09:40:57.133 I/wpa_supplicant( 618): wlan0: CTRL-EVENT-DISCONNECTED bssid=00:1a:30:e4:64:00 reason=0
[...]
04-08 09:40:59.803 E/DownloadTaskImpl( 3156): Download failed because of IO Error: recvfrom failed: ETIMEDOUT (Connection timed out)
04-08 09:40:59.803 W/DownloadTaskImpl( 3156): Experienced error when trying to download: [mId=[363, DEFAULT] mTrackTitle="Black Hole Sun" mRemoteId=8076a782-8454-3fd8-899d-213bb23836ac mSourceAccount=1954430662 mPriority=0 mOwner=MUSIC_PLAYBACK mSeekMs=0 mRetryAllowed=true mFileLocation=[mFullPath=/data/data/com.google.android.music/files/music/mplayback_363.tmp mStorageType=INTERNAL mCacheType=2] mExplicit=true]
This download failure is a lot easier to understand: your WiFi connection had dropped. I don't know that either of these is something I can fix. As above, you may want to try the obvious fixes if you haven't done so already: use the most recent GApps package, clear the app's cache and data, and play with the app's caching options.