Related
I've compiled 2.1 from source and I ran in to a problem. The device will boot and the touchscreen,keyboard, apps, and the phone all work but i'm having a problem trying to install apps from the marketplace. when i download an app it will download ok but always says installation unsuccessful and says insufficient storage. I checked the phone storage and it's over 100mb so i'm clueless as to why i'm getting this error.
I'm also having problems getting the sound working. I can select ringtones but nothing ever plays. I've copied the proprietary files from a ROM i was using on the device prior to flashing this and added them into this ROM. any help is greatly appreciated.
1) Try this from a command prompt (terminal app or adb shell):
chown system.system /data/app
chmod 0771 /data/app
If this works, you should add this to your update-script before flashing again:
set_perm 1000 1000 0771 DATA:app
2) Not sure about the sound issues, although I have an AOSP 2.2 ROM that acts the exact same way.
you actually inspired me to try to make my own ROM. I used your android builder and dsixda's kitchen. let me know if you figure something out with the sounds. It took me long enough to figure out how to get it to recognize the SD card.
That worked. I'm also havings issues with the camera and softkey lights. i copied the lights file into the proper folder but they still don't work. camera doesn't do anything either.
setcpu also for some reason can't get root either, it says root access not detected but i have su in /system/bin. too many problems!
update. apparently my permissions are somehow screwed up. i can use ADB and have root access but from the device itself using a terminal emulator i've figured out i don't have full root. any suggestions?
fixed the su issues. i had to adb remount and adb shell and chmod 06755 /system/bin/su if anyone was wondering
I'm still having issues with sound, camera, etc. i have moved all the proprietary files from a stock HTC 2.1 ROM over and i'm still having problems. I'm now using the new CFS kernel from conap and decad3nce and got overclocking to work. The main problems are sound and the softkey lights, once i get those working i can use this ROM everyday and work on the wifi, bluetooth and camera. If anyone has any tips or knows any other libs that might work it would be great.
Do not use the lagfix anymore voodoo will be incorporated into our new kernels very soon. Thanks
Kept the attachments so you can remove if needed!
I keep getting permission errors when I try this. I found another way to update busybox but the script doesn't work
With the current limited root I have, I could not write to /system/bin. I just woke up and I didn't feel like figuring that out, so I copied stuff to the sdcard, then I used cat to write the file to /system/bin as shown above (steps below). I would suggest before starting, download Quadrant Standard from the Market, run the full benchmark and see where your device is on the list. Mine was below the Galaxy S before starting.
This is what I did (on Mac) to get busybox in place:
Code:
./adb shell
su
mkdir /sdcard/lag_fix/
exit
exit
./adb push ~/Downloads/busybox /sdcard/lag_fix/
./adb shell
su
cat /sdcard/lag_fix/busybox > /system/bin/busybox
cd /system/bin/
chmod 755 busybox
ls -l (check the permissions)
exit
exit
Now busybox is in it's right place with the right permissions.
Now, I have to manually execute the steps in the lagfixme.bat file, because I'm not on a PC and I don't feel like re-writing the script, because I just woke up.
Before pushing the files, I edited lines 35 and 36 in the createlagfix.txt file to fit my sdcard folder path. I like to keep my SD card organized, so I put all the files from the zip into the /sdcard/lag_fix folder I created above. Here is what my line 35 and 36 look like before I push createlagfix.txt to the SD card:
busybox cp /sdcard/lag_fix/playlogos1 /system/bin/playlogos1
busybox cp /sdcard/lag_fix/userinit.sh /system/bin/userinit.sh
Now, I know the folder paths below looks ugly, but that's because I just pushed the files directly from my Downloads folder. Hopefully you guys can see what I did here. If not, let me know and I'll edit the post to read better. These are basically the lines in the batch file written out manually for Mac users:
Code:
./adb kill-server
./adb push ~/Downloads/RyanZAEXT2LagFix\ ALPHA\ 1/createlagfix.txt /sdcard/lag_fix/createlagfix.sh
./adb push ~/Downloads/RyanZAEXT2LagFix\ ALPHA\ 1/playlogos1 /sdcard/playlogos1
./adb push ~/Downloads/RyanZAEXT2LagFix\ ALPHA\ 1/userinit.sh /sdcard/userinit.sh
./adb shell su -c "/system/bin/sh /sdcard/lag_fix/createlagfix.sh"
Once the process is complete, run Quadrant Standard again and you'll see your device as the fastest one in the list.
Many thanks to Dirrk!!
Worked just fine for me.
Thanks for this and your root instructions!
Guys, is the phone actually laggy, or are you just assuming it's laggy because of complaints with the other models? I mean, you've only had them a day or two, right? Took me longer to notice lag than that on my i9000.
I'm tempted to grab a Fascinate, but all the issues I've had with the i9000 and it's a tough call.
I've seen it lag sometimes under high load, but I thought that was normal.
I've tested it with GroceryIQ, to compare against the last 30 seconds or so of this video ( http://www.youtube.com/watch?v=10ox35vMS78 ) and the Fascinate is nowhere near as bad at lagging. That video was 8/21/2010, so they may have updated their application by now, not sure.
Edit - Anyway, it works just fine. Nice work Dirrk! 2,191 !
Yep, worked like a charm! My Quadrant score jumped to 2125 after the fix. Phone is much snappier too. Thanks Dirrk!
i've been trying this but i keep getting permission denied.
can someone take me step by step on how to do this?
So, after running this, I am now getting a notification that internal storage is nearly full. Any ideas?
spotmark said:
So, after running this, I am now getting a notification that internal storage is nearly full. Any ideas?
Click to expand...
Click to collapse
If you have root, you can now remove many of the bloatware apps that you do not use (this fix uses 1gb of your internal storage - performance is expensive)
m2cool2go said:
If you have root, you can now remove many of the bloatware apps that you do not use (this fix uses 1gb of your internal storage - performance is expensive)
Click to expand...
Click to collapse
Whoa, careful there. That's a quick way to brick your phone. Try removing Verizon Backup Assistant and you're bricked.
C:\sdk\tools>adb shell
$ su
su
# cat /sdcard/busybox > /system/xbin/busybox
cat /sdcard/busybox > /system/xbin/busybox
cannot create /system/xbin/busybox: read-only file system
Any ideas why I'm getting this error? It looks like I'm screwing up something very simple...
namebrandon said:
Whoa, careful there. That's a quick way to brick your phone. Try removing Verizon Backup Assistant and you're bricked.
Click to expand...
Click to collapse
Really? I removed Backup Assistant and I'm not bricked. Am I missing something?
Removing VZW backup assistant will absolutely not brick your phone. Its one of the first things to go on all my android phones since the eris.
undo lagfix
Hello. I want to undo this for now, due to running out of space for apps. I assumed running unlagfixme would do the trick, but it hasn't given me back the 1 gb it used. Am I doing it wrong, or is it stuck like this now? Thanks for your help!
is there a list of apps someone can recommend to remove that's just bloat? thanks....and ive ran this quadrant score, im averaging 871 three times testing now with minimal apps (used task killer...) - and ive got 177mb left on my phone hehe...
Nevermind, figured it out
xirnibor said:
is there a list of apps someone can recommend to remove that's just bloat? thanks....and ive ran this quadrant score, im averaging 871 three times testing now with minimal apps (used task killer...) - and ive got 177mb left on my phone hehe...
Click to expand...
Click to collapse
You screwed up if your only getting 871 thats stock. Open up a shell on your phone and type mount and place the results in here
Whitepaint said:
Removing VZW backup assistant will absolutely not brick your phone. Its one of the first things to go on all my android phones since the eris.
Click to expand...
Click to collapse
Thanks for the info, and my bad on the post!
I heard that removing this on the Droid X was bricking phones.
If people want to share what they've been successful in removing/renaming, that would be helpful.
namebrandon said:
Thanks for the info, and my bad on the post!
I heard that removing this on the Droid X was bricking phones.
If people want to share what they've been successful in removing/renaming, that would be helpful.
Click to expand...
Click to collapse
I am waiting on rom manager so I can make a back up before I continue removing stuff
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.
Is there a way to get around it? I installed the Comcast Xfinity app (this one). When I run it, it gave an error about not enough memory. I'm sure it is related to this.
- Xfinity TV app currently supports devices that allow more than a 16MB memory limit on applications and will automatically detect the required memory. This includes most devices. However, the AT&T HTC Aria is a notable exception and is not compatible.
Click to expand...
Click to collapse
Is there any way around it on our phones?
Hmm, might try increasing your heapsize in build.prop and seeing if that fixes it.
That blurb seems to indicate they don't care to support old devices. Might not work at all, on any older device.
manekineko said:
Hmm, might try increasing your heapsize in build.prop and seeing if that fixes it.
Click to expand...
Click to collapse
This solved my issues with Google Maps constantly killing traffic due to insufficient memory.
Our device has enough RAM to support larger heapsizes than the default, so in terms of "older" - we're actually better than quite a few devices because setting vm.heapsize to 32m does not seem to cause any issues for us. (At least not for me.)
Problem is that the default AOSP build.prop does not set vm.heapsize at all, and the default is something stupidly low like 12m.
manekineko said:
Hmm, might try increasing your heapsize in build.prop and seeing if that fixes it.
Click to expand...
Click to collapse
Where is that file located? I don't recall seeing it among my android files.
Avatar28 said:
Where is that file located? I don't recall seeing it among my android files.
Click to expand...
Click to collapse
It's in /system (from within Android). Basically in the system.ext2 file.
arrrghhh said:
It's in /system (from within Android). Basically in the system.ext2 file.
Click to expand...
Click to collapse
Guess that would explain why I couldn't find it on the card.
Yeah, /system/build.prop
I forget the exact trick for editing it on-device as my SD card is a partitioned build and I have a Linux machine - easier to just shut off the phone and edit the file from my computer.
I think the basic idea is:
adb pull /system/build.prop edited_build.prop
edit build.prop
Remount system read/write (adb shell followed by 'mount /system -o remount,rw' in the shell IIRC)
adb push edited_build.prop /system/build.prop
Reboot
Note: The default build.prop has no VM heap size entry. I'll try to pull up the exact syntax tonight.
dalvik.vm.heapsize = xxm
I edit my build.prop from the one existing on /system to /sdcard, then umount/bindmount, and seemed to take it without issue according to the heap tool. Default is 16, changed it to 32 and noticing alot less GC (from geniewidget) according to logcat.
-- Starfox
[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.