[UPDATE FOR JB.15][Custom Build Prop] Increase Performance & Battery Life of PRIME - Asus Eee Pad Transformer Prime

[UPDATE FOR JB.15][Custom Build Prop] Increase Performance & Battery Life of PRIME
MAJOR UPDATE: U.S. & WW. MODDED BUILD.PROP FOR NEW. 15 JELLYBEAN RELEASE ADDED. here are edited build.prop files for both the US & WW 10.4.2.15 Jelly Bean. Tweaks are listed as to what they are within the build.prop and to install just copy over using Root Explorer or similar app and then ensure permissions are set correctly. MUCH LOVE AND THANKX GO TO MR.WOOKIE FOR THIS and his constant contributions to making the prime a better device to own. I know I haven't been around as much as I don't own a prime anymore. But I can continue to update this thread as needed. Its very important that if issues arise, PLEASE TRY TO HELP ONE ANOTHER OUT. I can try to help out when I can. As always, make sure to set permissions correctly. JB build.prop Modding should be no different than previous versions. so most of the instructions in this OP/thread still apply. please post up how this mods are working for you on new JB firmware. if you notice any particular mod or line is causing problems with JB, please let us know. so it can be modified again. HAVE FUN...PRIME WILL ALWAYS BE HOME FOR ME
With the permission of the Original Developer, Seanzscreams, we bring a modified version of his mod for the 300 that now works on the Prime also. This is a custom modified build prop, that Brings Overall Performance & Battery life Improvements to the Transformer Prime. This will make your device feel more snappy and responsive overall. It should improve battery life. Other performance tweaks also will improve everyday use of Prime.Your device has to be on the latest U.S. .21 or U.S..28 firmware and rooted. If you on a ww version or other, you may need to tweak the build.prop to reflect your region version. Take a look inside the modded build.prop & see before you try it out. If you know how to edit it, give it a shot. just make sure to back up your original build.prop. If unsure, hit the link & ask the developer. It is possible to not be rooted and push this through ADB but being rooted makes it ALOT easier.
UPDATE: U.S. & WW .28 MODDED BUILD.PROP ADDED. EVERYTHING EXCEPT power collapse & wifi scanning added. some users reported issues that could be linked. same instructions on implementing this. MAKE SURE TO MAKE BACKUP OF YOUR ORIGINAL FILE. MIGHT BE BEST TO SEND IT TO SOMEPLACE OUTSIDE INTERNAL MEMORY OF PRIME. JUST TO BE ON THE SAFE SIDE.
*Users on region versions other than the US .21 or U.S. .28, read the tips at the end of this post before you attempt this. Putting this US version of build.prop in your device can cause issues if not properly edited to reflect your region.
*If you running Androwoki rom, no need to apply this tweak. the developer already added these tweaks to his ROM/build.prop.
-UPDATE: fellow member Mekrel made a .21 WW version of this for those who wish to try out. or you go the other route like mentioned in this post. the WW version is attached to this thread also.
Thanks to Hairdex for making a making a version for people running Team EOS Cornerstone build #9. only those on build #9 can use it.
-added De .21 version also
PLEASE READ IMPORTANT INFO & TIPS AT THE BOTTOM OF THIS POST IN CASE ANY POSSIBLE ISSUES ARISE.
Method described below is for rooted users as I don't really know how to do it the stock(not rooted) method through ADB. You can go to original thread and ask developer on how to push it through ADB method
Quote from developer, Seanzscreams:
" This is a modified build.prop to include all the latest ics tweaks
(from a build.prop standpoint)
forced 60fps
faster wifi connect and suplicant scan set at 100 (battery saver as well)
added deep sleep mode
added screen dithering
removed checkin back to base
kernel tweaked
dalvik mins and max set higher than stock
increased over-all fling velocity min and max now set
min at 8000 and max at 12000
a few nvidia specific graphics tweaks as well
. power collapse disable enabled
-and just a few i dont feel like explaining google is your friend"
Link to his original thread: http://forum.xda-developers.com/showthread.php?t=1641219
DISCLAIMER: I nor the original developer take responsibility if you don't follow instructions or researched first. USE AT YOUR OWN RISK. It should be a fast n simple mod. Works great on my prime. If you run into issues, we will help you the best we can. Please read the important info & tips at the bottom of this post. It could eliminate possible issues from arising.
USE ROOT EXPLORER:
this modded build.prop, which is attached to this thread, goes in /system. Make sure to back up your original build prop or add .bak to the end of it(.bak). I sent a copy of my original file to my drop box. just an extra safety precaution... You will need to change root explorer to mount as RW. after you back up the original file, paste the new modded build prop into /system. then long click on it and press permissions. the permissions need to be exactly like the original file. which is rw-r--r-- after you properly set the permissions, change root explorer back to Read only. then power down and reboot, then profit. You can reboot twice to make sure everything sticks, if you want. If you don't notice anything initially, let it cache(kind of like letting a car warm up before you drive off) just like with roms. just start using tab so it can cache.
CLARIFICATION ON SETTING PERMISSIONS IF UNSURE. your permissions for this mod build.prop should look like this: rw-r--r--
...........Read. Write
Owner. X .......... X
Group. X
Others. X
I would suggest before even applying this, open the mod build prop up in root explorer. then just take a look at it all. Then cross reference the new tweak lines added with the links I will provide now. These links show all the build prop tweaks and what they do. This is to get a better understanding of what will be improved on your device Performance & Battery Savings wise. It won't hurt for you to become more familiar with what the different lines do and it might eliminate some questions concerning what each does.
http://forum.xda-developers.com/showthread.php?t=1639104
http://forum.xda-developers.com/showthread.php?t=1510652
EXAMPLES OF SOME OF THE TWEAKS SEEN IN THIS MODDED BUILD.PROP & WHAT THEY DO OR AFFECT: Thankx to TheFrankenstain & H M Judge threads for Reference
- Allows the tablet to sleep better: This setting puts your tablet into a deeper sleep when on standby
ro.ril.disable.power.collapse=1
- Allows your wifi to scan less frequently, saving more battery
wifi.supplicant_scan_interval=100
- Increase overall touch responsiveness
debug.performance.tuning=1
video.accelerate.hw=1
-Increases Scrolling responsiveness
windowsmgr.max_events_per_sec=300
- Faster Scrolling
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
-Increases quality of photo/Increases the memory cap when decoding JPEGs
ro.media.dec.jpeg.memcap=8000000
-Raises quality of JPEG images: makes JPEG Higher Quality
ro.media.enc.jpeg.quality=100
-Enable Surface dithering:Improves image quality
persist.sys.use_dithering=1
-System tweaks:
Change the Dalvik VM heap size
-dalvik.vm.heapsize=256m
-dalvik.vm.startheapsize = 8м
-makes apps load faster and frees more ram.
dalvik.vm.dexopt-flags=m=y
-Use Jit (Dalvik just-in-time compiler): faster better caching system
dalvik.vm.execution-mode=int:jit
-Disable error checking (Should speed things up a bit)
ro.kernel.android.checkjni=0
ro.kernel.checkjni=0
this has been running great for me so far. battery life seems improved and the responsiveness of the touch screen is unbelievable. it scrolls so fast n fluid it crazy. this is with the regular UI & within browsers. It also increases quality of your JPEG pictures. Im really impressed with it so far.
Do note though, once OTA update comes, it will knock all this out and a new custom build prop will have to be made. this is even if you accept the new OTA.
I will keep this thread updated to stay current with the developers original thread. As new updates come out, he will be modifying the newer build props within the update. So I will add those here as they come.
Make sure to click on the developer, Seanzscreams, original thread(http://forum.xda-developers.com/showthread.php?t=1641219) and give him thanks. You can leave feedback in this thread and original thread, if you wish. Feedback is encouraged as it will lead to better future results on this mod.
THANKS TO: Seanzscreams for Modding my Prime build prop. Now we have this MOD available to all prime owners on latest .21 firmware and rooted.
Attached to this post is a zip file with the custom build prop inside of it. The U.S. and WW version
*IMPORTANT:
If you come across a difficulty, you can ask in this thread or even better would be to ask in the developer original thread. He would know more on possible issues that may arise.
If you run into issues or caught in a bootloop or something here is how to use adb and push back your original build.prop file: Thanks to Mekrel
in regards to being for locked/unlocked users, I posted two sets of commands. Technically three scenarios exist:
Being locked
If you're locked, you're not going to have any third party kernel installed and therefore WILL have a secure kernel and therefore not able to push files to /system. That's why you need the command that involves pushing to the /sdcard and then using su via shell to copy from the /sdcard and then to /system.
Unlocked but with a kernel installed that's still secure
As above
Unlocked but with a kernel installed that's insecure
You can push directly to /system, so you don't have to push to the /sdcard first
If you're unlocked you're going to be running a secure kernel which means you're not going to be able to run adb as root, so even with root and the /system partition mount as r/w; you're not going to be able to push to system:
Code:
adb shell
su
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
exit
exit
adb push build.prop /sdcard/
adb shell
su
cp /sdcard/build.prop /system
chmod 644 /system/build.prop
rm /sdcard/build.prop
exit
exit
Unlocked and with an insecure kernel:
Code:
adb shell
su
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
exit
exit
adb push build.prop /system
adb shell
su
chmod 644 /system/build.prop
exit
exit
In regards to remounting to read only once finished, you don't have to as you can simply reboot and the commands executed in ramdisk will remount every partition with the relevant flags. Or you could:
Code:
adb shell
su
mount -o remount,ro -t ext4 /dev/block/mmcblk0p1 /system
exit
exit
you should be good to go after this.
*TIPS for users that are not on US .21 but instead on a WW or other version: thnkx to Buxtahuda & Gage_Hero
- instead of editing this build.prop with your information, edit your build.prop with any missing lines from this one. That's going to cut down on error a lot, and even if you get the right characters and spacing, the build.prop can be finnicky as all hell.
- IF you edit the build.prop use the right tool which would be notepad++ (download) not the standard windows note pad. if you use the standard windows notepad you could end up with format and character issues
*CAUTION:
We had a user who was unlocked, boot to a black screen. He got his prime back running by doing a restore from recovery. For unlocked users who want to try this, make sure to do a full backup, including the original build.prop file. Unlock users could even edit their own build.prop & add the lines one by one until it breaks. You can download notepad + yes it is +(plus). then you can edit the build prop (properly with out screwing up the format) on the pc and move it to the tablet. I'm not sure if being unlocked conflicts with this mod. just make sure you on latest .21 or .28 firmware and rooted. Then follow instructions carefully. you can even click on the original developer link for assurance on how to install if unsure how to install or if you have any possible conflicting issues. It would be best to ask developer if this is safe for unlocked users also. Unlocked users should proceed with caution and make sure you will be OK using this.
update:Developer said being unlocked shouldn't matter. I'm still waiting to hear back on what if people are on a different version like WW or something.
You can feel free to Hit my Thanks also, if you want. For putting this guide together on my Prime solely. The Prime is my PC Make sure to give feedback here & to OG developer, Seanzscreamz and his OG thread http://forum.xda-developers.com/showthread.php?t=1641219 . He made this all work for our Primes when he didn't have to. Much thanks to him & other members who contributed critical info, tips, & feedback.
Thanks to Texstar & Andromorphone for editing U.S. .28 buildprop.

That is the one I am looking for so long. Thanks for sharing.
Sent from my HTC Desire HD using xda premium

Could you please explain how to do this without root?

okay okay.. I will try it and report back

1SiK1500 said:
Could you please explain how to do this without root?
Click to expand...
Click to collapse
you actually dont need root
but this is way easier if you do
you could adb push /system/build.prop
or you could just paste it into root explorer replacing your existing
(back up existing or rename it to build.prop.bak just for safe keeping )
then reboot
or
when it reboots and adb comes alive you may be able to push it to /system with: adb push build.prop /system
not really much more was explained. you can click on his original thread link to get more details or ask him about it. most seem to be doing this the rooted method. I haven't seen anyone confirm doing this adb way yet.

I get an error..
"There was not enough free disk space to complete the paste operation" when I tried to paste this into /system with the original .bak there
I had to remove the original file to make room
Also, I think you better expand on what -RW, -R, -R means for people - like exactly what boxes to check and uncheck

I forgot to add:
If you don't notice anything initially, let it cache(kind of like letting a car warm up before you drive off) just like with roms. just start using tab so it can cache. it'll take to the changes.

Lock-N-Load said:
I get an error..
"There was not enough free disk space to complete the paste operation" when I tried to paste this into /system with the original .bak there
I had to remove the original file to make room
Click to expand...
Click to collapse
that's strange. I still have my original file in there renamed. I never got that error. Do you still have all those modded wifi files in there also?
edit: I saw the other part you added, I gotcha

demandarin said:
that's strange. I still have my original file in there renamed. I never got that error. Do you still have all those modded wifi files in there also?
edit: I saw the other part you added, I gotcha
Click to expand...
Click to collapse
Yes I do in /bin which is in /system - suppose i should delete those.
But this implies /system looks for and checks the size of that directory and pukes if it is beyond xx size - which is kind of interesting
Also, technically speaking, aren't permissions rw-r--r-- not -RW, -R, -R

Well, I did this and it just goes to a black screen and does nothing else.
How can I get back into the system and restore the old file?

Lock-N-Load said:
Yes I do in /bin which is in /system - suppose i should delete those.
But this implies /system looks for and checks the size of that directory and pukes if it is beyond xx size - which is kind of interesting
Also, technically speaking, aren't permissions rw-r--r-- not -RW, -R, -R
Click to expand...
Click to collapse
I edited OP to reflect that.
acdcking12345 said:
Well, I did this and it just goes to a black screen and does nothing else.
How can I get back into the system and restore the old file?
Click to expand...
Click to collapse
were you rooted and on .21 firmware?
did you put the modded file into /system & set its permissions to rw-r--r--? & rename the old file? so it won't be confused with 2 files try to be activated.

demandarin said:
I edited OP to reflect that.
were you rooted and on .21 firmware?
did you put the modded file into /system & set its permissions to rw-r--r--? & rename the old file? so it won't be confused with 2 files try to be activated.
Click to expand...
Click to collapse
I did exactly that..It was also unlocked...
Not sure how to go back to the old file..

Works great! Wow I can see a big speed difference! I can't wait to see how much longer the battery lasts.. Thanks man!
Sent from my Transformer Prime TF201 using XDA Premium App

jjdevega said:
Works great! Wow I can see a big speed difference! I can't wait to see how much longer the battery lasts.. Thanks man!
Sent from my Transformer Prime TF201 using XDA Premium App
Click to expand...
Click to collapse
you see changes that quick?? guess I will test mine more tonight.
my install went fine and reboot went fine.
I believe in this mod type as I did similar mods to my OG Droid

Lock-N-Load said:
you see changes that quick?? guess I will test mine more tonight.
my install went fine and reboot went fine.
I believe in this mod type as I did similar mods to my OG Droid
Click to expand...
Click to collapse
Surprisingly did. I didn't think I would see much of a difference that quick. As soon as it rebooted and right after the lock screen swiping was fast and opening closing apps are much quicker load times
Edit: overall loading speeds are improved quite a bit
Sent from my Transformer Prime TF201 using XDA Premium App

At work and don't have my Prime with me at the moment.
I will try tonight and report to you guys.
Good to hear positive feedback.

acdcking12345 said:
I did exactly that..It was also unlocked...
Not sure how to go back to the old file..
Click to expand...
Click to collapse
I'm wondering if being unlocked messes with things. Did you make a backup of your original file? if so. you can try to adb push it in there. you should go to original developer thread and post this up. As I'm not exactly sure on the adb method on getting the prime to use the original file.
ill make sure to add to the OP that being unlocked may conflict with this. As this is the only difference between yours n mines.
so you rebooting and it just went to a black screen? any Asus logo or anything? can you get into recovery and reflash your rom or restore a backup?
Anyone with insight into how he get back using the old file from state he is in now?

I don't see a wifi scan interval on either the original or this build prop. That was one I changed from 30 seconds to 100 on my phone to cut down on the power used by wifi to go out and ping and search for signals.
On my phone is it wifi.supplicant_scan_interval = 30
A bit surprised this does not exist as it can be a good battery saver
I also see some telephony stuff in this prop that seems of no value as we dont have phones

demandarin said:
I'm wondering if being unlocked messes with things. Did you make a backup of your original file? if so. you can try to adb push it in there. you should go to original developer thread and post this up. As I'm not exactly sure on the adb method on getting the prime to use the original file.
ill make sure to add to the OP that being unlocked may conflict with this. As this is the only difference between yours n mines.
so you rebooting and it just went to a black screen? any Asus logo or anything? can you get into recovery and reflash your rom or restore a backup?
Anyone with insight into how he get back using the old file from state he is in now?
Click to expand...
Click to collapse
I just went into recovery and restoring from a 3 old backup..

Lock-N-Load said:
I don't see a wifi scan interval on either the original or this build prop. That was one I changed from 30 seconds to 100 on my phone to cut down on the power used by wifi to go out and ping and search for signals.
On my phone is it wifi.supplicant_scan_interval = 30
A bit surprised this does not exist as it can be a good battery saver
I also see some telephony stuff in this prop that seems of no value as we dont have phones
Click to expand...
Click to collapse
it there is one actual in there. you have to look closely. its set to 100. I just looked in saw it. its like the 4th line above the additional build properties. I believe this scan is lower than in stock configuration.
I noticed the phone stuff also. he said once he updates, he has more tweaks he will add. ill update this thread with the changes also.

Related

[WIP] Just in time compiler for Nook Color

There seems to be a lot of mystery surrounding the release timeline for the official Froyo (2.2) update for the Nook Color. One of the biggest advantages that I've found using Froyo is the serious speed boost, compliments of the Just-in-time compiler (JIT). Many other Froyo features are directed primarily at mobile phones and aren't particularly relevant to our device. That said, I know that JIT was slated for release on 2.1 but wasn't ultimately implemented until 2.2. The good news is that JIT does run on 2.1 and isn't that difficult to implement (It does NOT require a special kernel or anything). I've done some research and am going to start working on getting the JIT to run on Nook 2.1 tomorrow morning once I sober up. I started this thread in order to see:
1. Is this feasible?
2. Is there an interest in this?
3. If people would be willing to test this
4. If anyone has some input on how to get started
5. If others will help me develop an easy method to get this running for others
While I certainly respect and encourage the developers working on the community version of Froyo, we all know that it's not ready for prime time. This should give us many of the advantages of Froyo without having to sacrifice daily usability.
Next up: REAL, system-wide copy and paste (incl. http links, etc.)
http://www.xda-developers.com/android/jit-enabled-for-htc-hero/
that would be cool, i don't see how that would not be possible but then again i am not a dev,... I know threre is more to it that just flash 10.1 but HTC had there own version of it while motorola didn't on there 2.1 OS
easy9 said:
that would be cool, i don't see how that would not be possible but then again i am not a dev,... I know threre is more to it that just flash 10.1 but HTC had there own version of it while motorola didn't on there 2.1 OS
Click to expand...
Click to collapse
It's possible, follow that link. Cyanogenmod had it on my Nexus One when it was 2.1. I am like 90% sure it can be done I need to work on it and I will tomorrow night just wanted to get people aware of this and looking into it.
Would be awsome. JIT and Flash are all I am really missing.
Sent from my ADR6300 using Tapatalk
I don't know how helpful it is but some of the old evo 2.1 roms had jit compiling. Maybe you could look at those. Damage control 3.5 i remember specifically having it.
Sent from my nook COLOR.
Ordieth said:
Would be awsome. JIT and Flash are all I am really missing.
Sent from my ADR6300 using Tapatalk
Click to expand...
Click to collapse
you can use Skyfire as a browser for the flash part
Honestly it probably wont work very well. When the Droid 1 first came out many devs worked on enabling JIT on 2.1 for it. It worked but with major stability issues. And it wasn't only the D1 having stability issues. 2.1 just wasn't written with JIT in mind originally, which is why 2.2 was so huge.
Sent from my ADR6300 using XDA App
SWM is right. I installed it on my Droid in March of last year and it was fast, but ultimately proved to be unstable. The following is post I made about JIT. It was in March of last year (the links are surely not functional now as I think those websites are gone now). Also, ignore the optimism in the post because the stability did not last:
I’ve been running Bugless Beast roms since the end of January.
Everything that follows is all based on work done by t3hSteve. Here’s his description of the process: He rebuilt the file dalvikvm with JIT defined “and then copied libnativehelper, libdvm, and dalvikvm to my phone. Added dalvik.vm.execution-mode=int:jit to build.prop and rebooted”. After reading that short post, I started reading and googling until I learned how to do the same using his modified dalvikvm file. After reading (http://alldroid.org/viewtopic.php?f=210&t=1673 ) and learning that some folks that are running JIT are still having problems with browsers closing and with some force closes. I, on the other hand, knew that JIT had run well on my Droid with BB7.7. After all the reading, I was more convinced than ever that having Animations turned off was a key to successful operation with JIT. I have no technical reasons to support this position other than it seems that a lot, not all, but a lot of people that are having problems with JIT enabled are also mentioning how much they like Live Wallpapers. So taking those two tenuous data points (1. My Droid ran fine with 7.7 and JIT enabled and 2. I have animations turned off and most folks obviously do not due to the fascination with Live Wallpapers.) I decided to go for it. I then enabled JIT on my droid.
The results are pretty good so far. Before enabling JIT I would mostly get 159 - 179ms benchmarks. With JIT enabled I’m getting at lot of reading in the 130 - 150 range. I downloaded Linpack and promptly started getting readings in the 11’s. My best so far is 11.924 Mflops/s. So far so good. I’ve had absolutely no issues at this point. I’ve been running with JIT enabled for about 4 hours so far. It’s hard to operate the Droid and type with my fingers crossed. 
To accomplish this I added a line to the end of the build.prop file and replaced libdvm.so and libnativehelper.so with copies I got from t3hSteve. Here’s the procedure I followed:
1. Make a full Nandroid backup and save a copy of it on the computer.
2. Download the file “vmlibs.zip” here http://alldroid.org/download/file.php?id=1374
3. Create a new folder on your sdcard named: JIT
4. Extract vmlibs.zip to the new JIT folder on the sdcard.
5. Open the JIT folder and create a new folder in it named Backup. This is where you are going to keep your current files that are going to be replaced: dalvikvm, libdvm.so and libnativehelper.so
6. Disconnect phone from Computer. The following steps are going to be done with Root Explorer.
7. Go to /system/bin and copy dalvikvm.
8. Go to /sdcard/JIT/Backup and paste dalvikvm there.
9. Go to /sdcard/JIT/bin and copy dalvikvm.
10. Go to /system/bin and select the mount RW button
11. Paste dalvikvm there – answer yes to the overwrite question.
12. Long press the new dalvikvm file and choose Permissions and check every box.
13. Press the Mount RO button.
14. Go to /system/lib and copy libdvm.so and paste it in sdcard/JIT/Backup.
15. Go to /system/lib and copy libnativehelper.so and paste it in sdcard/JIT/Backup.
16. Go to /sdcard/JIT and copy libdvm.so.
17. Go to /system/lib and press the “Mount RW” button.
18. Paste the libdvm.so file there. Answer yes to the overwrite question.
19. Go to /sdcard/JIT and copy libnativehelper.so .
20. Go to /system/lib and paste the libnativehelper.so file there. Answer yes to the overwrite question.
21. Press the “Mount RO” button.
22. Go to /system and long press the build.prop file.
23. Select “Open in Text Editor” in the window that opens.
24. Open your physical keyboard and scroll to the bottom of the file and enter the following:
25. Dalvik.vm.execution-mode=int:jit
26. Press the phone’s Menu button and select “Save & Exit”
27. Reboot
------------------------------------------------------------------------------
Here's the adb vesion (don't know the source, it wasn't me):
abd pull /system/build.prop build.prop
Open in WordPad and add
Add as the last line:
dalvik.vm.execution-mode=int:jit
SAVE
adb shell mount -o remount,rw /dev/mtd/mtdblock4 /system
adb push dalvikvm /system/bin/
adb push libdvm.so /system/lib/
adb push libnativehelper.so /system/lib/
adb shell chmod 755 /system/bin/dalvikvm
adb push build.prop /system/
adb shell reboot
-------------------------------------------------------------------------------------
I am not a dev and have no idea if any of this old stuff will help with the NC, but there it is!!
Good luck.
To Geezer Squid: Great find, I've put it into my blog, thanks. I have a collection of NC quirks there -- with probable ways to improvements. Yours should work like a charm.
To brashmadcap: Excellent move! Hope your next "Next up" after system-wide copy-paste would be hardware assisted 2D/3D drivers and video overlay and/or VOME engine out of AOSP 2.3:
Now all it may take is searching for OMAP36xx's JIT (dalvikvm and libdvm.so and libnativehelper) for A2.2.1 (or maybe 2.3 if already available and different from A2.2.1's). Next step (or preliminary step?) would be getting rid of all UI "animations" and "Live Wallpapers" crap that were designed before a good JIT compiler appearance.
While digging in TI OMAP36xx (or maybe even in TI OMAP4430) and Droid X/2 repositories for better JIT, I would ask to pull and try better (later) 2D/3D drivers, the newer NEON framework and better (read: working) hardware assisted overlay (HQ YouTube is obviously using it today, why other/stock video players don't know it even exists? where's the usual "stagefright" fallback options of build.prop?).
Then flash_for_2.1.apk (Flash 10.1) will simply work, I hope.
fineoils.blogspot.com

[REF][Patch] Malware Exploit for all pre-Gingerbread phones

I'm posting this here for visibility for Fascinate users and ROM developers. In the following thread you can find all the information, as well as how to download and apply the patch files:
http://forum.xda-developers.com/showthread.php?t=977154
I'm sure it will be incorporated into the major ROM's soon. However, if you install apps from unverified sources, or regularly try out new apps from the market, you shouldn't wait.
Patching via CWM:
imnuts said:
Here are two zips if people want them and don't feel like going to another thread/page/topic/whatever.
DroidDreamMalwarePatch_pre-edify.zip
DroidDreamMalwarePatch_edify.zip
Click to expand...
Click to collapse
Patching via ADB or terminal emulator:
Alternatively, probably the quickest way (and if you copy and paste, the most fool-proof) if you are rooted and know how to use ADB, is to open up a command prompt or a terminal emulator on the phone to access the adb shell. If on a PC, type:
Code:
adb shell su
Then type the following lines, omitting the $ and # (if you are on a terminal emulator, start here):
Code:
$ su
# mount -o rw,remount /dev/block/stl9 /system
# touch /system/bin/profile
# chmod 444 /system/bin/profile
You are now protected from the current iteration of DroidDream Malware. Consider installing a security program like LookOut to protect against future vulnerabilities.​
Original Post:
Rodderik said:
[Patch][Rom]Malware Exploit for all pre-Gingerbread phones
Who is affected? All phones pre-gingerbread
Who should act? Users and developers using pre-gingerbread roms
How do I fix? Flash attached .zip at the bottom of this post or use one of the alternate methods down there
What if I think I was infected? Completely wipe your device, format sdard, go back to stock and re-apply rom, then flash the attached .zip (before installing any apps)
Why should I care? read below...
http://www.androidpolice.com/2011/0...your-phone-steal-your-data-and-open-backdoor/
Link to publishers apps here. I just randomly stumbled into one of the apps, recognized it and noticed that the publisher wasn’t who it was supposed to be.
Super Guitar Solo for example is originally Guitar Solo Lite. I downloaded two of the apps and extracted the APK’s, they both contain what seems to be the "rageagainstthecage" root exploit – binary contains string "CVE-2010-EASY Android local root exploit (C) 2010 by 743C". Don’t know what the apps actually do, but can’t be good.
I appreciate being able to publish an update to an app and the update going live instantly, but this is a bit scary. Some sort of moderation, or at least quicker reaction to malware complaints would be nice.
EDIT: After some dexing and jaxing, the apps seem to be at least posting the IMEI and IMSI codes to http://184.105.245.17:8080/GMServer/GMServlet, which seems to be located in Fremont, CA.
I asked our resident hacker to take a look at the code himself, and he’s verified it does indeed root the user’s device via rageagainstthecage or exploid. But that’s just the tip of the iceberg: it does more than just yank IMEI and IMSI. There’s another APK hidden inside the code, and it steals nearly everything it can: product ID, model, partner (provider?), language, country, and userID. But that’s all child’s play; the true pièce de résistance is that it has the ability to download more code. In other words, there’s no way to know what the app does after it’s installed, and the possibilities are nearly endless.
Click to expand...
Click to collapse
The offending apps from publisher Myournet:
* Falling Down
* Super Guitar Solo
* Super History Eraser
* Photo Editor
* Super Ringtone Maker
* Super Sex Positions
* Hot Sexy Videos
* Chess
* ????_Falldown
* Hilton Sex Sound
* Screaming Sexy Japanese Girls
* Falling Ball Dodge
* Scientific Calculator
* Dice Roller
* ????
* Advanced Currency Converter
* App Uninstaller
* ????_PewPew
* Funny Paint
* Spider Man
* ???
Click to expand...
Click to collapse
http://www.androidpolice.com/2011/0...-android-nightmare-and-weve-got-more-details/
Now, on to some more details of the virus. We should point out that this vulnerability was patched with Gingerbread, meaning any device running Android 2.3+ should be fine. In other words, if you’re looking to play the blame game (which I’m not, but having read all the comments on the original post, many people are), then there’s plenty to go around. The hole was fixed by Google, but it’s relatively useless since many phones aren’t yet running a version of Android that is protected. It’s noteworthy that some manufacturers released updates that patched the exploit for devices without updating to Gingerbread; unfortunately, it appears that minority is quite a small one.
Perhaps most important is the question of what infected users can do about their situation; unfortunately, the answer is not much of anything. Because the virus opens up a backdoor and can bring in new code at any time, the only way to really rid an infected device of any damage is to completely wipe the device – not exactly the optimal solution, but it looks like the only one available, at least for now.
Finally, Justin notes that ROM developers working with pre-Gingerbread versions of Android can prevent the virus from backdooring in code by putting a dummy file at /system/bin/profile.
Click to expand...
Click to collapse
As you can see androidpolice.com reports on this backdoor and roots and steals personal information. The apps are removed from the market but that doesn't mean they got them all. Attached is a flashable fix as suggested by androidpolice.com
So users can flash this .zip or simply create a blank file called profile and place it in /system/bin/ (developers are encouraged to include this file in future releases. A blank file is not going to affect performance at all)
Alternate methods:
Using 'adb shell' or terminal emulator (should work on any ROOTED phone) as suggest by xaueious here
Code:
$ su
su
# remount rw
Remounting /system (/dev/stl9) in read/write mode
# touch /system/bin/profile
# chmod 644 /system/bin/profile
#
Alternate 2:
Download blank profile file from here (or create one and name it profile)
Use a program like Root Explorer to copy it to /system/bin/
Then longpress on it and check the permissions should be read/write for user, read for group, and read for others.
Alternate 3:
cyansmoker has put together an apk for the patch here https://market.android.com/details?id=com.voilaweb.mobile.droiddreamkiller
Thanks for pointing this out photoframd and androidpolice.com for investigating and reporting!
UPDATE: I renamed the .zip file and reuploaded it (350 hits wow). Also in the edify scripted version I added 644 permissions to the file (but if you already flashed it then it should have defaulted to that). I also added a pre-edify version of the patch thanks to xaueious for people using a recovery that does not yet understand edify.
Click to expand...
Click to collapse
Thanks
Sent from my Rocking dj05, themed superdark w/o swype mod, voodoo 5, with custom boot and shutdown.. With premium xda app.
I would also recommend installing the free Lookout Mobile Security app. I find it to be very non-intrusive on my phone, no negligible battery drain or performance issues. Just scans any app you install, looking for bad stuff. Also does weekly full system scans, contact backup, and provides phone lock/alarm/location tracking features in case you lose it. Premium version has even more bells and whistles.
Posted from my EB01 SuperClean Fascinate with Voodoo
This has been stuck for the time being as it seems to be affected a BOATLOAD of users. Thanks for the linkage!
Here are two zips if people want them and don't feel like going to another thread/page/topic/whatever.
adb shell busybox touch /system/bin/profile
is all you need. Most fascinate kernels (of recent) have a bug, and /system is mounted as r/w.
So everyone should flash this no matter what rom you are using? Should we flash the new cwr also?
sorry delete
jcase said:
adb shell busybox touch /system/bin/profile
is all you need. Most fascinate kernels (of recent) have a bug, and /system is mounted as r/w.
Click to expand...
Click to collapse
adb shell chmod 644 /system/bin/profile
also?
NOsquid said:
adb shell chmod 644 /system/bin/profile
also?
Click to expand...
Click to collapse
This would probably be a good thing. Basically locks the file from being written to, right? Should I add it to the first post?
lasportsfan said:
So everyone should flash this no matter what rom you are using? Should we flash the new cwr also?
Click to expand...
Click to collapse
Yes.
All this is is a quick fix that will create a blank file. The current iteration of the malware checks to see if it already exists. This file fools it into thinking it already exists, so it moves on.
As you might guess, the author needs to only update his code to bypass this, in order for this to be an issue again.
And now that this is out, someone else will probably try it. Someone who is a little more thorough.
Moral of the story?
Be careful.
Consider running something like LookOut.
Backup your important data regularly.
As far as CWM goes, is there some kind of connection to the malware thing? Or just in general?
(If just in general, it's better to ask elsewhere as to not derail the thread).
Otherwise, I don't believe the newest (orange) clockwork recovery from ROM manager is fully compatible yet. Last I heard, it still had some bad binaries and 1 bad mounting point. Stick with the Red from JT's thread (which is the same bundled into SuperClean). Other than a couple superficial bugs that don't hurt anything, it works wonderfully and has more features than the orange CWM currently has.
GizmoDroid said:
This would probably be a good thing. Basically locks the file from being written to, right? Should I add it to the first post?
Click to expand...
Click to collapse
I dunno, it was in Rodderik's post but jcase didn't mention it. He's smarter than me, that's why I asked...
444 or 000 would be safer as that would prevent the file from being overwritten at all. 444 for read-only, 000 for no access.
If I never downloaded any of the apps in the list and have lookout on my phone is this neccesary to download or should i not be worried?
italysfinest327 said:
If I never downloaded any of the apps in the list and have lookout on my phone is this neccesary to download or should i not be worried?
Click to expand...
Click to collapse
Who should act? Users and developers using pre-gingerbread roms
Click to expand...
Click to collapse
I'd say that means you should be worried. Those apps listed are just the ones that were found on the market with them from one publisher. Just how virus's can get put into any application on a PC, the same can be done on phones.
Remember folks, our phones are just as exploitable as any other computer, so be careful!
good thing the patch came out!
imnuts said:
444 or 000 would be safer as that would prevent the file from being overwritten at all. 444 for read-only, 000 for no access.
Click to expand...
Click to collapse
Not sure whether Android interprets permissions differently from desktop Linux, but even if a file is 000 the owner can delete it on Debian. And root definitely can. If the file needs to be there for the root exploit to work, then this prevents it, but if they can run the root exploit and get root while this file is there then changing permissions on it will do nothing.
iofthestorm said:
Not sure whether Android interprets permissions differently from desktop Linux, but even if a file is 000 the owner can delete it on Debian. And root definitely can. If the file needs to be there for the root exploit to work, then this prevents it, but if they can run the root exploit and get root while this file is there then changing permissions on it will do nothing.
Click to expand...
Click to collapse
This is just another reason why I see this as a quick fix for what will need to have a much better one in the future.
If anyone hears of a more robust solution (besides using LookOut), let us know!
I navigated through Root Explorer to system/bin/profile and found a file there that reports
"01 Aug 08 06:00:00 rwxr-xr-x 0 bytes".
The 2008 date has me worried, although the 0 bytes means it is empty. Does anybody know if this is put there by FrankenClean 2.8 as a fix for this issue, or am I the only one on SuperClean seeing this (which would be bad!)
SupraLance said:
I navigated through Root Explorer to system/bin/profile and found a file there that reports
"01 Aug 08 06:00:00 rwxr-xr-x 0 bytes".
The 2008 date has me worried, although the 0 bytes means it is empty. Does anybody know if this is put there by FrankenClean 2.8 as a fix for this issue, or am I the only one on SuperClean seeing this (which would be bad!)
Click to expand...
Click to collapse
It is included in SC2.8. The 0 bytes is the best indicator that you are clean, since this patch is merely an empty file.
If you were infected, that file would actually have code in it.
For CWM 2.5.x.x DJ05, which one do you flash? or both?
DroidDreamMalwarePatch_pre-edify.zip
DroidDreamMalwarePatch_edify.zip
Thanks and sorry for the trouble, just wanted to be sure.

BHT Installer (Basic Hacking Tools)

Hey guys, I came up with a basic set of tools which I find useful. You may redistribute , include in any custom ROMs and/or distributions.
This includes:
Rewrite /default.prop for ADB
Install and deploy busybox in /system/xbin
install bash, ipctool, strace, tcpdump, and viewmem binaries.
To install, you must be rooted.
Unzip the attached file
place it on your nook.
cd to the folder you installed
Run the following
Code:
sh /sdcard/BHT/run.sh
Please note, I use Android Market app QuickSSH to get into my nook terminal, your results may very.. I hope someone else grabs these files and makes it all more user friendly. I've got too many other things going on.
I encourage other developers to include these valuable debugging tools in their packages.
You, sir, are a monster! You get my vote.
Sent from my Nexus S using xda premium
AdamOutler said:
Hey guys, I came up with a basic set of tools which I find useful. You may redistribute , include in any custom ROMs and/or distributions.
This includes:
Rewrite /default.prop for ADB
Install and deploy busybox in /system/xbin
install bash, ipctool, strace, tcpdump, and viewmem binaries.
To install, you must be rooted.
Unzip the attached file
place it on your nook.
cd to the folder you installed
Run the following
Code:
sh /sdcard/BHT/run.sh
Please note, I use Android Market app QuickSSH to get into my nook terminal, your results may very.. I hope someone else grabs these files and makes it all more user friendly. I've got too many other things going on.
I encourage other developers to include these valuable debugging tools in their packages.
Click to expand...
Click to collapse
I can turn this into an apk, if you don't mind. By turn on adb with this method, adb will be rooted and the device will still be allowed to sleep?
brianf21 said:
I can turn this into an apk, if you don't mind. By turn on adb with this method, adb will be rooted and the device will still be allowed to sleep?
Click to expand...
Click to collapse
By all means. Please do.
My vote too. I just hope after you win that you keep up the great work on the Nook Tablet. The last two weeks or so have looked very promising towards getting custom roms on here and a lot of that has to do with Adam's hard work along with a few others
Nearly all of these are already in snowball-mod, but I'll include ipctool, and viewmem for the next release.
cfoesch said:
Nearly all of these are already in snowball-mod, but I'll include ipctool, and viewmem for the next release.
Click to expand...
Click to collapse
How did you get default.prop reread into memory? The only think I can see is the 2nd init hijack? Am I missing something a lot easier?
brianf21 said:
How did you get default.prop reread into memory? The only think I can see is the 2nd init hijack? Am I missing something a lot easier?
Click to expand...
Click to collapse
Note, I said "nearly all". I don't really see though how changing /default.prop would keep over reboots... rootfs is stored in memory and recreated every time, isn't it?
I've added the binaries to NT Hidden Settings. I have not implemented /default.prop swap yet. I have to play with hijacking init before I do. Thanks again.
brianf21 said:
I've add the binaries to NT Hidden Settings. I have not implemented /default.prop swap yet. I have to play with hijacking init before I do. Thanks again.
Click to expand...
Click to collapse
cool. where are you hosting that binary? I currently have a mirror set up at nook1.adamoutler.com for easy access... When someone gets a new device, they need to download 3 things onto their device to make it a real tablet.. nook1=hidden settings, nook2=homecatcher, nook3=market.. I may change 3 to launcherpro, but hidden settings is the number1 tool required for the nook Tablet.
AdamOutler said:
cool. where are you hosting that binary? I currently have a mirror set up at nook1.adamoutler.com for easy access... When someone gets a new device, they need to download 3 things onto their device to make it a real tablet.. nook1=hidden settings, nook2=homecatcher, nook3=market.. I may change 3 to launcherpro, but hidden settings is the number1 tool required for the nook Tablet.
Click to expand...
Click to collapse
Homecatcher? I mean, I understand if you want to keep using the B&N store and stuff, but if you don't care about the B&N stuff, then the hacked SystemUI.apk is a way better option than Homecatcher.
But then, you're advancing "launcher pro", while I would more generally say "any non-B&N launcher"...
I added another option to nt hidden settings to run adb as root. It doesn't require a reboot and it automatically turns off auto mount. I am using nemith's adbd.
remount / as rw
stop adbd
replace /sbin/adbd
remount / as ro
setprop to turn off auto mount
start adbd as root
It's not persistent after reboot, but it works and doesn't kill the battery. I am not going to bother with hkvc's hijacking init method, because it looks like you, hkvc, bauwks, and nemith will be able to replace the os soon. Thanks.

[MOD][ICS] Modified boot.img with adb root & init.d support

I am not sure if someone else has posted this already. But I couldn't find one, so here you go. (Please let me know if I'm mistaken)
I made two small edits to the boot.img of the stock (leaked) ICS rom in order to satisfy my needs:
1. ability to run init.d scripts,
2. start adb in root.
They are very simple and anyone with a little knowledge can do it himself, but it still is convenient to have someone else do it, isn't it? I, for one, searched the forum in vein.
Here's a short explanation of what it is, and how to utilize the features.
1. init.d :
You can place your own shell scripts in /etc/init.d (you have to create the directory yourself, of course) and run them at boot time. If you prefer the CM style userinit.d, you could create a script like:
Code:
#!/system/bin/sh
# call userinit.sh and/or userinit.d/* scripts if present in /data/local
if [ -e /data/local/userinit.sh ];
then
log -p i -t
userinit "Executing /data/local/userinit.sh";
logwrapper
/system/bin/sh /data/local/userinit.sh;
setprop
fi;
if [ -d /data/local/userinit.d ];
then
logwrapper busybox
run-parts /data/local/userinit.d;
fi;
and place it in init.d (credit: CM team). After that, you can place additional scripts without remounting system partition. Just don't forget to chmod appropriately.
A word of caution: Don't go wild and install all those tweaks found in other forums without checking to see their contents. I found that most of them to be either irrelevant or even harmful to the Amaze. Remeber, we've got one of the best phones on the market and wouldn't want to ruin it by running tweaks designed for our 'lessor' siblings!
2. adb root :
I was getting tired of the inability to adb push files to user restricted directories. Also, I use Droid Explorer a lot, but was tired of its inability to obtain root even though my phone is rooted. So I basically changed the default.prop and everything is fine now.
Added benefit is that 'adb remount' works now.
Well, that's it. Too simple, but until someone comes up with a nice kernel with these mods built in, we got to live with what's available.
DISCLAIMER : Should I even include a disclaimer? Why not? This is just a stock boot.img with minor modifications to its ramdisk portion, and it shouldn't harm your phone. If it doesn't work, simply reflash the stock boot.img found in the stock/leaked ICS roms. However, I don't want anyone to brick his phone, so don't flash this unless you know what you are doing. Also, I've seen some people bricking their phones merely by trying to flash innocent files like this one. Hard to believe, but anything can happen, so I will not be responsible if you brick your phone.
INSTRUCTIONS :
0. be sure you got the ICS build 4.0.3 with the stock kernel. rooted and have installed busybox (for init.d support only).
1. download the attached boot.img.
2. place the file where adb/fastboot can find it.
3. flash it using 'fastboot flash boot boot_new.img.
4. reboot.
5. try 'adb shell' and see if you get # prompt.
6. add some scripts in /etc/init.d and reboot and see if it runs.
It runs on my Amaze running the newer leaked ICS rom (unlocked bootloader, rooted, and busybox from the market). If you have any other settings, it probably won't do any good.
That's it, guys. Hope you have some fun with it (like I did).
Just flashed your modified boot.img so far everything works as described. Going to attempt my backlight script now. Just reflashed the stock RUU as certain Roms were giving me WiFi issues. Thanks
Is this why adb remount never worked?? I asked a few people and they acted like I was crazy.. I KNEW there had to be a reason it wasn't working.. I guess my only question is why was it no one thought to do this since the ICS release except you? LOL.
Edit: And I am out of thanks, this is my mental note to come back and hit thanks when I get some to give again!
Edit2: As advertised it works flawlessly, as advertised. It will be awesome to be able to push files to my phone and all the other things I couldn't do before! A simple tweak, as you said, still appreciated!
seems like were getting some more people around here that actually contribute to the amaze forums. thanks guys...carry on
Thank you very much
Now to find some scripts to run, lol.
Thank you all for the kind words! As I said in the OP, I was curious at first about the usefulness of my post. I truly believe that, if HTC had given us more power to mod this phone, this forum would have been 10 time more active with all sorts of useful stuff. Come on HTC, you give us the best phone (even better than the One series!), and why do you want to cripple us?
Double0EK said:
Just flashed your modified boot.img so far everything works as described. Going to attempt my backlight script now. Just reflashed the stock RUU as certain Roms were giving me WiFi issues. Thanks
Click to expand...
Click to collapse
As I didn't test the boot.img with any roms around, I don't know what went wrong with your wifi. That's why I only promised it would work with the NEWER stock ICS rom. Is it possible that you flashed the boot.img to a custom rom that is based on the OLDER leak?
Additionally, if the rom dev has made his/her own mods to the boot.img, it would not be compatible with the stock boot.img like mine. I didn't add, remove or move any files.
Silentbtdeadly said:
Is this why adb remount never worked?? I asked a few people and they acted like I was crazy.. I KNEW there had to be a reason it wasn't working.. I guess my only question is why was it no one thought to do this since the ICS release except you? LOL.
Edit: And I am out of thanks, this is my mental note to come back and hit thanks when I get some to give again!
Edit2: As advertised it works flawlessly, as advertised. It will be awesome to be able to push files to my phone and all the other things I couldn't do before! A simple tweak, as you said, still appreciated!
Click to expand...
Click to collapse
Hehe, yeah it is because of some security settings that phone manufacturers chose to enable in order to minimize customer support costs, I guess. Instead, they should give us all the power (and funding, too) so that we can support each other at XDA!
mrmako777 said:
seems like were getting some more people around here that actually contribute to the amaze forums. thanks guys...carry on
Click to expand...
Click to collapse
bilek06 said:
Thank you very much
Click to expand...
Click to collapse
I've used more than two dozen smart phones in the past, including ancient pda's and even iPhones (ouch!), and I think the Amaze has the best (mix of) hardware. I, too, wish there were more devs here, and wonder why some great devs around didn't see the potential in it. Well, HTC isn't doing something right...
Dark Nightmare said:
Now to find some scripts to run, lol.
Click to expand...
Click to collapse
Hard to find anything useful for the (already mighty) Amaze, isn't it?
Things I would add for myself are like:
- house keeping: delete cache, move/copy important files from internal to external sdcard, etc.
- renice phone and input method a bit. How about acore? Probably not...
- zipalign, maybe, if you're fanatic about it.
- save logs and erase oldest ones. Gosh, what am I saying? We've got so much storage space. Oh, well. If we save the logs in external sdcard, we can view them even when the phone doesn't turn on...
Hehe, I think I should search.
I never flashed your boot.img on custom roms only on the stock. I have better WiFi with stock.
--------------------------------
It's Better To Fail At Originality
Than To Succeed In Imitation.
--------------------------------
ringochan said:
Hard to find anything useful for the (already mighty) Amaze, isn't it?
Things I would add for myself are like:
- house keeping: delete cache, move/copy important files from internal to external sdcard, etc.
- renice phone and input method a bit. How about acore? Probably not...
- zipalign, maybe, if you're fanatic about it.
- save logs and erase oldest ones. Gosh, what am I saying? We've got so much storage space. Oh, well. If we save the logs in external sdcard, we can view them even when the phone doesn't turn on...
Hehe, I think I should search.
Click to expand...
Click to collapse
Lol searching, was thinking about the v6 supercharger script, still reading into it though.
I use Cache Cleaner NG to clean. Set it on Auto with new method 2 times a day.
--------------------------------
It's Better To Fail At Originality
Than To Succeed In Imitation.
--------------------------------
Double0EK said:
I never flashed your boot.img on custom roms only on the stock. I have better WiFi with stock.
--------------------------------
It's Better To Fail At Originality
Than To Succeed In Imitation.
--------------------------------
Click to expand...
Click to collapse
I must have misread your original post. My bad. But then, I have no idea about your wifi problem with the modified boot.img. I didn't touch anything other than 2 things that I mentioned. And my wifi is working just fine. It's spooky.
Dark Nightmare said:
Lol searching, was thinking about the v6 supercharger script, still reading into it though.
Click to expand...
Click to collapse
LOLOLOL! That guy is something! I mean the guy who created the v6 script. Yes, I think his concept is right on. I may borrow some of his tweaks like app grouping and oom/minfree. I've done similar adjustments when I was still using my G1/Dream, but with Amaze with de-bloated ICS, I am already getting (almost, if not) everything he is promising we can achieve with his script.
The only lag I have is when some background services are busy. But I don't really want to make them low priority (yet).
What do you think you like to achieve using v6? I may be able to help because I myself want to experiment some.
Double0EK said:
I use Cache Cleaner NG to clean. Set it on Auto with new method 2 times a day.
--------------------------------
It's Better To Fail At Originality
Than To Succeed In Imitation.
--------------------------------
Click to expand...
Click to collapse
Hehe, you know that some script junkies won't approve of ANY apps to take over what he can do with scripts, right? I've seem many. No, I've worked with many! They refused to use GUI text editors, LOL!
ringochan said:
LOLOLOL! That guy is something! I mean the guy who created the v6 script. Yes, I think his concept is right on. I may borrow some of his tweaks like app grouping and oom/minfree. I've done similar adjustments when I was still using my G1/Dream, but with Amaze with de-bloated ICS, I am already getting (almost, if not) everything he is promising we can achieve with his script.
The only lag I have is when some background services are busy. But I don't really want to make them low priority (yet).
What do you think you like to achieve using v6? I may be able to help because I myself want to experiment some.
Click to expand...
Click to collapse
Hey, if you want to try out something cool, check this out.. http://android.mimic.ca/ it patches the services.jar file to change the OOM priority, evidently in a way more effective than the supercharger script can do it. I was going to try to include it in the latest update for my rom till I decided I wanted to work on other things.. the guy who made supercharger script helped design the patch for the file though Just thought you may be interested.
Silentbtdeadly said:
Hey, if you want to try out something cool, check this out.. http://android.mimic.ca/ it patches the services.jar file to change the OOM priority, evidently in a way more effective than the supercharger script can do it. I was going to try to include it in the latest update for my rom till I decided I wanted to work on other things.. the guy who made supercharger script helped design the patch for the file though Just thought you may be interested.
Click to expand...
Click to collapse
erm... it CAN'T be more effective than supercharging... because it IS SuperCharging
Well, 50% of it. The other 50% comes from the script when on ICS.
Why do you think that website is integrated into the latest V6 Scripts?
That needs to be done in addition to the V6 script when using ICS roms to get 100%.
Of course, non ICS roms get 100% supercharged with the script itself since there's no need to patch services.jar
zeppelinrox said:
erm... it CAN'T be more effective than supercharging... because it IS SuperCharging
Well, 50% of it. The other 50% comes from the script when on ICS.
Why do you think that website is integrated into the latest V6 Scripts?
That needs to be done in addition to the V6 script when using ICS roms to get 100%.
Of course, non ICS roms get 100% supercharged with the script itself since there's no need to patch services.jar
Click to expand...
Click to collapse
LOL. Did you search yourself? HAHA. Yes, we are talking about how awesome your scripts are..
I would be using them myself but I can't figure out a setting that really makes it awesome like it did with my old vibrant!
Edit: And thanks for the explanation, that makes more sense than whatever post that lead me to your patch.
what is a modified boot image?
what is the different between the modifed boot image and the android we can download from the developer google site/?

difficulty pulling build.prop using twrp - trying to get miracast to work.

Hi there, i've been trying to make some changes to my build.prop (mainly enable miracast...can't believe they would disable it!) and i've had a rather challenging time.
I am now stuck on how to pull the actual build.prop...when i enter the command i get a long list of ADB definitions but no file - at least not that i could find. I tried a few times, including directing the file to be saved on an empty drive in case i could not see it.
I have unlocked my boatloader and installed TWRP. Mounted the system then gone back and entered the commands in ADB....and i don't seem to be having any success. Any help would be appreciated.
thanks
m
Why not just edit it within the built in editors in most file explorers? I use Solid Explorer and it allows me to edit at will within the app itself, no pushing or pulling. Of course I back up my current one before doing anything to it
Tower1972 said:
Why not just edit it within the built in editors in most file explorers? I use Solid Explorer and it allows me to edit at will within the app itself, no pushing or pulling. Of course I back up my current one before doing anything to it
Click to expand...
Click to collapse
i'm not rooted...and i've read that you don't get OTA updates...and it's happened to me more than once that i have an issue with the phone, and i can't get service because it's rooted...
and i guess i thought it was too much trouble to get rooted, make the changes, and then unroot...but i could be wrong at this point?!
You won't get OTA with twrp either. You need stock recovery.
so i bit the bullet and rooted my phone...i was able to get the build.prop editor to work (at first i did not have busybox which it seems helps apps to realize you have root). So now when i go to unable Casting, i can turn it on from the top right of the cast screen, and my tv appears. I can select it and it starts to sync up...then the mircosoft display adapter shows that it's also trying to sync...and then it times out it seems. I've checked it with my tablet and my wife's phone...both work.
any suggestions?
I understand Miracast no longer works in Nougat. I'm still on MM with my 6P and it works, but if you're on 7, you may have lost that feature.
What about WUGS toolkit? Do you need to re rooted for that...ifnot thats what I always use to edit the prop. So much easier as it has most edits you'll make and you just choose.
you never needed to root i edit build.prop like this all the time
1. boot to twrp recovery
2. go to mounts and select system
3. adb pull /system/build.prop
4. make edits
5. adb push build.prop /system/
idk if your edit will work but thats how to do it without root and for some of the other things said in this topic you can ota in twrp but it will fail if modify anything like you just did

Categories

Resources