Hi,
Just plugged my XBox 360 joypad into keyboard dock to play some GTA. The light shows up on the controller indicating it's drawing power but the pad itself is not being detected by the tablet. No button presses or analogue stick movements are being registered. This worked fine previously on Honeycomb.
Is there an option I'm missing or is this not supported in ICS?
I am surprised you even got it to work with honeycomb, i yried everything on my tf 101 b80 with 8.6.5.21 and to no avail was unsucessful, if you could give details on how you got yours to work i would GREATLY APPRECIATE IT, as for your problem on ics, i wil keep scouring the forums for an answer and keep you posted if i find anything, i decided to wait a little bit before upgrading to ics---reason being i feel there are too many little bugs in the first release- how would you compare ics to hc? tia for your reply and answers
In honeycomb, I just plugged in my USB XBox 360 joypad and it worked, simple plug and play. Had used an unofficial one previously (replaced it due to an unrelated failure in the pad) which had everything working except the bottom two triggers and then bought an official Microsoft black USB 360 pad where every button worked. Was using it for GTA, Shadowgun, Riptide, Cordy and a bunch of emulators flawlessly.
Kinda gutted that it's not working on ICS now. Especially as my USB hard drive still detects fine (thankfully as I have a LOT of movies on there, lol).
As for ICS, loving it, much faster than previous, web browser works much better, being able to use Chrome is another big plus (works great, just a shame that it'll never support flash ). Glad to finally have inbuilt folder functionality as I prefer to keep all my apps sorted by category.
Love the Asus task manager widget and being able to swipe away running apps and notifications.
App drawer is much better organised and smoother, putting widgets in there was a great idea. Being able to force 2D GPU rendering is awesome as older apps now run smoother also due to now using hardware acceleration.
Videos still work fine using various video players such as Dice & MX. Oddly enough I noticed that the stock video player now plays standard def avi files (such as xvid and divx), pretty sure it didn't play those before.
Would have been nice to have face unlock but luckily I have Visiodon AppLocker installed. As a default lock screen it's useless as pressing home skips it, but it is much more convenient (and unskippable) than Asus App Locker for protecting apps, now protected apps can only be opened via a face unlock.
Anyway, back on topic now, has anyone had any success with a USB pad after ICS update?
I too have been unable to get my controller working post update to ICS
I will keep an eye on this forum so if anyone finds an answer please post or if I do I will post as well.
I did try a PS3 controller plugged in via USB and it worked fine but like the OP said the light comes on but nothing happens.
Download this follow instructions, map the dock keys on the app so it can recognize them on the controller (xbox and sixasis compatible)
Works on HC and ICS
surtrafl said:
Download this follow instructions, map the dock keys on the app so it can recognize them on the controller (xbox and sixasis compatible)
Works on HC and ICS
Click to expand...
Click to collapse
sucks to pay 4 bucks for something that was plug and play in HC
Problem is I also used the 360 joypad for Onlive and I'm pretty sure it won't work with that app.
In the meantime, I found a spare PS3 pad and using that now via bluetooth (see: http://forum.xda-developers.com/showthread.php?t=1514777), works very well. Just doesn't register button presses in Onlive, works flawlessly with everything else though (GTA, Shadowgun, etc).
i tried it for me, pluggin in the xbox 360 into the key dock. but the xbox button only blinks.
/dev/input list
EDIT 2: Fixed below.
To preface this: I'm not an Android developer, just a CS grad. I noticed on my ICS upgrade, the /dev/input directory only has event0 to event3, but I saw talk on other ROMs about a js0 device. If anyone still has HC or installs an HC-based ROM, could you do an 'ls -al /dev/input' and post the results here?
I can't imagine that Asus would intentionally break something that was present in previous firmwares.
EDIT: Can an HC user also post an 'ls -al /system/lib/modules' listing? Mine on ICS is:
android:/system/lib/modules $ ls
battery_rvsd.ko
bcm4329.ko
bcmdhd.ko
scsi_wait_scan.ko
Fixed.
I've fixed this issue on my TF101.
DISCLAIMER: This is absolutely a hack. I have no clue if it will survive future updates to the firmware, and I have no clue if it will work on TF201s. I have a TF101, followed these steps, and gamepads work in SNESoid now. Proceed at your own risk. Thanks go to the original authors of the components listed below.
You will need:
Ingredients
1. ViperMOD PrimeTime v4.5, found here: http://forum.xda-developers.com/showthread.php?t=1427125
2. ff-memless and xpad kernel modules, found here: http://forum.xda-developers.com/showthread.php?t=1517949
Steps
1. Follow the instructions in the ViperMOD PrimeTime thread to give yourself root access to the tablet. If successful, you will also have access to the adb shell.
I have a TF101, but the 3rd option, recommended for TF101s, did not work for me. Option #1 did, however. Confirmed by whoami in adb shell.
2. unzip the xpad-v2.zip to your SD card, for example, I unzipped mine to /sdcard/Download/xpad-v2
3. Run 'adb shell' in Windows, and run
Code:
su
to give the shell superuser privleges. Once you are working as root, your terminal prompt should switch from a $ to a #, but if you want to make absolutely sure, run 'whoami', and it should say 'whoami: unknown uid 0'. If this is the case, you are root and may proceed.
4. Remount the /system filesystem as read-write by running the following:
Code:
mount -o remount,rw /system
5. Copy the ff-memless and xpad modules to /system/lib/modules by doing the following:
Code:
cp /sdcard/Download/xpad-v2/ff-memless.ko /system/lib/modules/
cp /sdcard/Download/xpad-v2/xpad.ko /system/lib/modules/
6. !! OPTIONAL !!
you can test gamepad support by running the following commands:
Code:
insmod /system/lib/modules/ff-memless.ko
insmod /system/lib/modules/xpad.ko
at this point, js0 should appear in /dev/input, the two modules should be listed in lsmod, and gamepad support should work. I tested an Xbox 360 controller in GBCoid and SNESoid and it worked like it did in Honeycomb, with no problems at all.
But we're not done yet.
7. To make these modules autoload, you have to make a script that runs at boot. Run the following commands:
Code:
echo "#!/system/bin/sh" >> /system/etc/install-recovery.sh
echo "insmod /system/lib/modules/ff-memless.ko" >> /system/etc/install-recovery.sh
echo "insmod /system/lib/modules/xpad.ko" >> /system/etc/install-recovery.sh
chmod 777 /system/etc/install-recovery.sh
8. Reboot and your gamepads should work. I tested mine in SNESoid and it works perfectly.
Good luck!
Didn't work with my USB Controller, still doing nothing.
RobertZFord said:
I've fixed this issue on my TF101.
DISCLAIMER: This is absolutely a hack. I have no clue if it will survive future updates to the firmware, and I have no clue if it will work on TF201s. I have a TF101, followed these steps, and gamepads work in SNESoid now. Proceed at your own risk. Thanks go to the original authors of the components listed below.
You will need:
Ingredients
1. ViperMOD PrimeTime v4.5, found here: http://forum.xda-developers.com/showthread.php?t=1427125
2. ff-memless and xpad kernel modules, found here: http://forum.xda-developers.com/showthread.php?t=1517949
Steps
1. Follow the instructions in the ViperMOD PrimeTime thread to give yourself root access to the tablet. If successful, you will also have access to the adb shell.
I have a TF101, but the 3rd option, recommended for TF101s, did not work for me. Option #1 did, however. Confirmed by whoami in adb shell.
2. unzip the xpad-v2.zip to your SD card, for example, I unzipped mine to /sdcard/Download/xpad-v2
3. Run 'adb shell' in Windows, and run
Code:
su
to give the shell superuser privleges. Once you are working as root, your terminal prompt should switch from a $ to a #, but if you want to make absolutely sure, run 'whoami', and it should say 'whoami: unknown uid 0'. If this is the case, you are root and may proceed.
4. Remount the /system filesystem as read-write by running the following:
Code:
mount -o remount,rw /system
5. Copy the ff-memless and xpad modules to /system/lib/modules by doing the following:
Code:
cp /sdcard/Download/xpad-v2/ff-memless.ko /system/lib/modules/
cp /sdcard/Download/xpad-v2/xpad.ko /system/lib/modules/
6. !! OPTIONAL !!
you can test gamepad support by running the following commands:
Code:
insmod /system/lib/modules/ff-memless.ko
insmod /system/lib/modules/xpad.ko
at this point, js0 should appear in /dev/input, the two modules should be listed in lsmod, and gamepad support should work. I tested an Xbox 360 controller in GBCoid and SNESoid and it worked like it did in Honeycomb, with no problems at all.
But we're not done yet.
7. To make these modules autoload, you have to make a script that runs at boot. Run the following commands:
Code:
echo "#!/system/bin/sh" >> /system/etc/install-recovery.sh
echo "insmod /system/lib/modules/ff-memless.ko" >> /system/etc/install-recovery.sh
echo "insmod /system/lib/modules/xpad.ko" >> /system/etc/install-recovery.sh
chmod 777 /system/etc/install-recovery.sh
8. Reboot and your gamepads should work. I tested mine in SNESoid and it works perfectly.
Good luck!
Click to expand...
Click to collapse
Worked like a charm except for the script at the end. Dont know if I am doing something wrong but does not seem to run at boot. I just created a install-recovery.sh file with the script and copied to /system/etc is that not right?
Also any idea as to why these would have been removed since they were working in HC just prior to the update?
Perfect Solution tyvm
RobertZFord said:
I've fixed this issue on my TF101.
DISCLAIMER: This is absolutely a hack. I have no clue if it will survive future updates to the firmware, and I have no clue if it will work on TF201s. I have a TF101, followed these steps, and gamepads work in SNESoid now. Proceed at your own risk. Thanks go to the original authors of the components listed below.
You will need:
Ingredients
1. ViperMOD PrimeTime v4.5, found here: http://forum.xda-developers.com/showthread.php?t=1427125
2. ff-memless and xpad kernel modules, found here: http://forum.xda-developers.com/showthread.php?t=1517949
Steps
1. Follow the instructions in the ViperMOD PrimeTime thread to give yourself root access to the tablet. If successful, you will also have access to the adb shell.
I have a TF101, but the 3rd option, recommended for TF101s, did not work for me. Option #1 did, however. Confirmed by whoami in adb shell.
2. unzip the xpad-v2.zip to your SD card, for example, I unzipped mine to /sdcard/Download/xpad-v2
3. Run 'adb shell' in Windows, and run
Code:
su
to give the shell superuser privleges. Once you are working as root, your terminal prompt should switch from a $ to a #, but if you want to make absolutely sure, run 'whoami', and it should say 'whoami: unknown uid 0'. If this is the case, you are root and may proceed.
4. Remount the /system filesystem as read-write by running the following:
Code:
mount -o remount,rw /system
5. Copy the ff-memless and xpad modules to /system/lib/modules by doing the following:
Code:
cp /sdcard/Download/xpad-v2/ff-memless.ko /system/lib/modules/
cp /sdcard/Download/xpad-v2/xpad.ko /system/lib/modules/
6. !! OPTIONAL !!
you can test gamepad support by running the following commands:
Code:
insmod /system/lib/modules/ff-memless.ko
insmod /system/lib/modules/xpad.ko
at this point, js0 should appear in /dev/input, the two modules should be listed in lsmod, and gamepad support should work. I tested an Xbox 360 controller in GBCoid and SNESoid and it worked like it did in Honeycomb, with no problems at all.
But we're not done yet.
7. To make these modules autoload, you have to make a script that runs at boot. Run the following commands:
Code:
echo "#!/system/bin/sh" >> /system/etc/install-recovery.sh
echo "insmod /system/lib/modules/ff-memless.ko" >> /system/etc/install-recovery.sh
echo "insmod /system/lib/modules/xpad.ko" >> /system/etc/install-recovery.sh
chmod 777 /system/etc/install-recovery.sh
8. Reboot and your gamepads should work. I tested mine in SNESoid and it works perfectly.
Good luck!
Click to expand...
Click to collapse
This is also worked for me, I thank you very much.
I was happily using a wired 360 controller with OnLive on my TF101 when it was running HC.
Then ICS broke it
This is not the perfect solution for OnLive mind. There is a mismapping of buttons compared to the HC implementation it seems.
I sense that the Back button on the controller is acting as a back button as opposed to how it used to act within OnLive and the ever blinking 360 button just takes me back 'Home to my launcher instead of bringing up the OnLive dashboard.
Other than that this is perfect until ASUS fix it fix it fix it.
More than likely one of the incredibly talented XDA devs will arrive at a solution prior to ASUS though.
Cheers
djasmithxda said:
This is also worked for me, I thank you very much.
I was happily using a wired 360 controller with OnLive on my TF101 when it was running HC.
Then ICS broke it
This is not the perfect solution for OnLive mind. There is a mismapping of buttons compared to the HC implementation it seems.
I sense that the Back button on the controller is acting as a back button as opposed to how it used to act within OnLive and the ever blinking 360 button just takes me back 'Home to my launcher instead of bringing up the OnLive dashboard.
Other than that this is perfect until ASUS fix it fix it fix it.
More than likely one of the incredibly talented XDA devs will arrive at a solution prior to ASUS though.
Cheers
Click to expand...
Click to collapse
You may want to try this for the onlive controller I ran across it trying to fix shadowgun
http://forum.xda-developers.com/showthread.php?p=23151895#post23151895
My question concerns the script it is working however I wanted to add to it so that a file would be pushed on each boot as well.
echo "#!/system/bin/sh" >> /system/etc/install-recovery.sh
echo "insmod /system/lib/modules/ff-memless.ko" >> /system/etc/install-recovery.sh
echo "insmod /system/lib/modules/xpad.ko" >> /system/etc/install-recovery.sh
echo "cp /data/flash/libflashplayer.so /data/data/com.adobe.flashplayer/lib/" >> /system/etc/install-recovery.sh
chmod 777 /system/etc/install-recovery.sh
Does this look correct for pushing libflashplayer.so at each boot?
I'm unsure about the pushing of files at startup using install-recovery.sh
Beyond my scope of knowledge that one.
In theory I would say that it should work? Much like a batch script at the startup of windows?
I had reverted back to Revolver 3.1 but given your post had a crack with Revolver 4 again.
I insmod'd the xpad files and then copied the keyboard layout as per your post.
I still found the controller within OnLive to act as if the Back and XBox buttons were mismatched to how they acted previously under HC.
So I have reverted back to HC and Revolver 3.1
Other than a few bugs and a smoother launcher with folders I see no reason yet to upgrade to ICS? All works well for me on HC.
Cheers
The script is working like a charm for me.
Stock ICS rooted rom with xbox 360 gamepad
RobertZFord said:
I've fixed this issue on my TF101.
DISCLAIMER: This is absolutely a hack. I have no clue if it will survive future updates to the firmware, and I have no clue if it will work on TF201s. I have a TF101, followed these steps, and gamepads work in SNESoid now. Proceed at your own risk. Thanks go to the original authors of the components listed below.
You will need:
Ingredients
1. ViperMOD PrimeTime v4.5, found here: http://forum.xda-developers.com/showthread.php?t=1427125
2. ff-memless and xpad kernel modules, found here: http://forum.xda-developers.com/showthread.php?t=1517949
Steps
1. Follow the instructions in the ViperMOD PrimeTime thread to give yourself root access to the tablet. If successful, you will also have access to the adb shell.
I have a TF101, but the 3rd option, recommended for TF101s, did not work for me. Option #1 did, however. Confirmed by whoami in adb shell.
2. unzip the xpad-v2.zip to your SD card, for example, I unzipped mine to /sdcard/Download/xpad-v2
3. Run 'adb shell' in Windows, and run
Code:
su
to give the shell superuser privleges. Once you are working as root, your terminal prompt should switch from a $ to a #, but if you want to make absolutely sure, run 'whoami', and it should say 'whoami: unknown uid 0'. If this is the case, you are root and may proceed.
4. Remount the /system filesystem as read-write by running the following:
Code:
mount -o remount,rw /system
5. Copy the ff-memless and xpad modules to /system/lib/modules by doing the following:
Code:
cp /sdcard/Download/xpad-v2/ff-memless.ko /system/lib/modules/
cp /sdcard/Download/xpad-v2/xpad.ko /system/lib/modules/
6. !! OPTIONAL !!
you can test gamepad support by running the following commands:
Code:
insmod /system/lib/modules/ff-memless.ko
insmod /system/lib/modules/xpad.ko
at this point, js0 should appear in /dev/input, the two modules should be listed in lsmod, and gamepad support should work. I tested an Xbox 360 controller in GBCoid and SNESoid and it worked like it did in Honeycomb, with no problems at all.
But we're not done yet.
7. To make these modules autoload, you have to make a script that runs at boot. Run the following commands:
Code:
echo "#!/system/bin/sh" >> /system/etc/install-recovery.sh
echo "insmod /system/lib/modules/ff-memless.ko" >> /system/etc/install-recovery.sh
echo "insmod /system/lib/modules/xpad.ko" >> /system/etc/install-recovery.sh
chmod 777 /system/etc/install-recovery.sh
8. Reboot and your gamepads should work. I tested mine in SNESoid and it works perfectly.
Good luck!
Click to expand...
Click to collapse
Any chance this could also work on the Team EOS nightlies? I tried this and it doesn't seem to fix my wired Xbox360 pad
EDIT: Well, I flashed over to Revolver 4.0.0 to test this using a stock-based ROM and it seems to be working fine now. I do I could get it working with one of the AOSP ROMs too though. In any event, thank you RobertZFord!
robert your script worked for me thanks. one glitch i found is when you hit any triggers while playing GTA3 you get stuck in look around mode and have to unplug and reconnect for it to work again
ics ARHD
ok so i am not good at adding script
can the script be made in to a zip and flashed i am clueless on even getting to this to work or just some serious help is needed i just flash android reveloution ics 3.01.1 and love it no probs but i just want my xbox controller to work
I really, really hate to bump this thread, but the script that guy posted isn't working for me. I tried it 2 times but it just won't work. Is it because I'm not on stock ICS but a custom ROM?
Related
Posting this here because I think it will be of more interest to the tinkerers/devs than general users, if not, feel free to move it. I cobbled all of this together from various places on the web, but I think the credit for the binaries goes to Paul @ MoDaCo.
Nandroid before going any further!
Files you'll need:
For WiFi and CDMA SSH access - QuickSSHD (Download this from the Market. $1.50). I'm just going to assume if you're still reading, you know what this is for and how to use it. It's braindead simple. I think dropbear can be installed and configured manually, but for the $1.50...meh.
adb for tethered access.
The rest are zipped up here: terminfo, nano, bash, profile**
Unzip bashnano.zip onto your SDCard.
adb remount
From adb shell:
Install Terminfo:
cp -r /sdcard/terminfo /system/etc
Setup Bash:
cp /sdcard/bash /system/bin/bash_new
mv /system/bin/sh /system/bin/sh.old
ln -s /system/bin/bash_new /system/bin/sh
mv /sdcard/profile /sdcard/bash_profile (Thanks to jjvcuyler for finding adb bash profile location.)
Setup Nano:
cp /sdcard/nano /system/bin
I'm not sure if this setup will have any impact on sh scripts being used in the various ROMs, so use this at your own risk. I think it would kick ass to see this type of bash functionality baked into the custom ROMs.
If anybody would like to make this a flashable.zip, please do. I don't know how to do that yet.
Anyway, hope y'all find it useful.
**profile reflects a few personal choices for aliases and colors, but you can edit to your personal taste.
So I just did this. Is there any way to get this functionality into a local terminal?
Also I was able to do everything from a local terminal without adb. Just do the following first:
su
remount rw
Click to expand...
Click to collapse
adb shell fires off bash, but it doesn't read profile from /etc. It's going to be a simple matter of figuring out where bash is looking for it. I just haven't found that out yet.
How do you like having full bash capabilities on EVO? Arrows/tab completion/color prompts, etc...
J
jmxp69 said:
adb shell fires off bash, but it doesn't read profile from /etc. It's going to be a simple matter of figuring out where bash is looking for it. I just haven't found that out yet.
How do you like having full bash capabilities on EVO? Arrows/tab completion/color prompts, etc...
J
Click to expand...
Click to collapse
Copy profile to /sdcard/bash_profile
jjvcuyler said:
Copy profile to /sdcard/bash_profile
Click to expand...
Click to collapse
WooT! There it is. I'll update the OP. Thanks jjvcuyler.
Edit: /sdcard/bash_profile works for ssh and adb. OP updated to reflect the change.
jmxp69 said:
Posting this here because I think it will be of more interest to the tinkerers/devs than general users, if not, feel free to move it. I cobbled all of this together from various places on the web, but I think the credit for the binaries goes to Paul @ MoDaCo.
Nandroid before going any further!
Files you'll need:
For WiFi and CDMA SSH access - QuickSSHD (Download this from the Market. $1.50). I'm just going to assume if you're still reading, you know what this is for and how to use it. It's braindead simple. I think dropbear can be installed and configured manually, but for the $1.50...meh.
adb for tethered access.
The rest are zipped up here[/URL]: terminfo.zip, nano, bash, profile**
Unzip bashnano.zip onto your SDCard.
Unzip terminfo.zip (from inside bashnano.zip) onto your SDCard.
adb remount
From adb shell:
Install Terminfo:
cp -r /sdcard/terminfo /system/etc
Setup Bash:
cp /sdcard/bash /system/bin/bash_new
mv /system/bin/sh /system/bin/sh.old
ln -s /system/bin/bash_new /system/bin/sh
mv /sdcard/profile /sdcard/bash_profile (Thanks to jjvcuyler for finding adb bash profile location.)
Setup Nano:
cp /sdcard/nano /system/bin
I'm not sure if this setup will have any impact on sh scripts being used in the various ROMs, so use this at your own risk. I think it would kick ass to see this type of bash functionality baked into the custom ROMs.
If anybody would like to make this a flashable.zip, please do. I don't know how to do that yet.
Anyway, hope y'all find it useful.
**profile reflects a few personal choices for aliases and colors, but you can edit to your personal taste.
Click to expand...
Click to collapse
there is no terminfo.zip and there is nothing in terminfo directory from within the original zip... help?
Sorry, I missed the recurse flag zipping the terminfo directory. It's fixed now. Go ahead and re-download.
Here's a link for just terminfo.zip
J
I modified the bash_profile to get rid of the colors since the window's cmd.exe doesnt support ansi colors. probably a better way to do this but it works for me.
also found this useful for setting PS1 to my liking http://www.cyberciti.biz/tips/howto-linux-unix-bash-shell-setup-prompt.html
jmxp69 said:
adb shell fires off bash, but it doesn't read profile from /etc. It's going to be a simple matter of figuring out where bash is looking for it. I just haven't found that out yet.
How do you like having full bash capabilities on EVO? Arrows/tab completion/color prompts, etc...
J
Click to expand...
Click to collapse
is there a way to get tab completion through adb shell?
Yes. This works with adb shell. Just follow the directions in the OP.
jmxp69 said:
Yes. This works with adb shell. Just follow the directions in the OP.
Click to expand...
Click to collapse
i have and i do have everything done as stated in the OP, when i try tab completion via adb shell (phone tethered with usb) from my pc, it just puts in a tab, it doesn't complete.
Hmm....could be a dos thing with cmd.exe. I haven't tried on a PC, I'm on a Mac. adb shell via OSX works fine with tab completion. Try ssh'ing in instead with something like putty? Once you get ssh going, you don't need a cable.
Edit: Confirmed...tab completion doesn't work over Win cmd.exe and adb shell.
jmxp69 said:
Hmm....could be a dos thing with cmd.exe. I haven't tried on a PC, I'm on a Mac. adb shell via OSX works fine with tab completion. Try ssh'ing in instead with something like putty? Once you get ssh going, you don't need a cable.
Edit: Confirmed...tab completion doesn't work over Win cmd.exe and adb shell.
Click to expand...
Click to collapse
Thanks for looking into it... I'll try getting it to work via linux instead. I guess ssh would be a solution, but i never turn wifi on.
Is anyone able to do a NAND backup/restore after doing this? With Amon Ra's recovery I was unable to NAND backup.
EDIT:
I think this is a big negatory. I was just able to do a NAND backup, so maybe the error I got was a coincidence after applying these changes.
Anyone else noticing that the time is always displayed as GMT in the prompt? The date command gives the correct time for my timezone but the bash prompt always shows GMT
Vinny75 said:
Anyone else noticing that the time is always displayed as GMT in the prompt? The date command gives the correct time for my timezone but the bash prompt always shows GMT
Click to expand...
Click to collapse
Change PS1 line: \A to `date +%H:%M`
jmxp69 said:
Posting this here because I think it will be of more interest to the tinkerers/devs than general users, if not, feel free to move it. I cobbled all of this together from various places on the web, but I think the credit for the binaries goes to Paul @ MoDaCo.
Nandroid before going any further!
Files you'll need:
For WiFi and CDMA SSH access - QuickSSHD (Download this from the Market. $1.50). I'm just going to assume if you're still reading, you know what this is for and how to use it. It's braindead simple. I think dropbear can be installed and configured manually, but for the $1.50...meh.
adb for tethered access.
The rest are zipped up here: terminfo, nano, bash, profile**
Unzip bashnano.zip onto your SDCard.
adb remount
From adb shell:
Install Terminfo:
cp -r /sdcard/terminfo /system/etc
Setup Bash:
cp /sdcard/bash /system/bin/bash_new
mv /system/bin/sh /system/bin/sh.old
ln -s /system/bin/bash_new /system/bin/sh
mv /sdcard/profile /sdcard/bash_profile (Thanks to jjvcuyler for finding adb bash profile location.)
Setup Nano:
cp /sdcard/nano /system/bin
I'm not sure if this setup will have any impact on sh scripts being used in the various ROMs, so use this at your own risk. I think it would kick ass to see this type of bash functionality baked into the custom ROMs.
If anybody would like to make this a flashable.zip, please do. I don't know how to do that yet.
Anyway, hope y'all find it useful.
**profile reflects a few personal choices for aliases and colors, but you can edit to your personal taste.
Click to expand...
Click to collapse
I followed the steps exactly, but end up with "- exec '/system/bin/sh' failed: Permission denied (13) -" while typing "adb shell" in a windows or linux terminal. I cannot recover the original sh because the root is lost, and I cant root my phone anymore probably because something wrong with the new sh. Any idea how to fix this?
EDIT: Acutally nevermind. adb shell works in recovery mode. but still, not sure why the modified sh doest work for me
The Downloadlink is dead!
So the thread is useless.
francwalter said:
The Downloadlink is dead!
So the thread is useless.
Click to expand...
Click to collapse
Yeah.....no.
A simple google search would have shown you that the files are here: http://66.197.42.222/bashnano.zip
or here http://androidforums.com/attachment...ide-installing-bash-nano-android-bashnano.zip.
EDIT: I've also attached it in case the links above ever die, there will still be one which does not.
ya this is great and all but any decent busybox installer will setup bash for you.
Here is a script i've made (had nothing to do, so...).
Phone must be rooted and have busybox installed.
What first menu looks like:
1 - enable/disable hardware acceleration
2 - enable/disable jit
3 - enable/disable stagefright player
4 - change heapsize
s - show status
r - revert to original configuration
q - quit (don't forget to reboot your phone!)
==================
enter your option:
Click to expand...
Click to collapse
Download:
http://www.4shared.com/file/gApTB6EG/tweaks.html
md5 b0865d9de67a82215913512cb644211d
Just copy the file to your sdcard. Then in a terminal emulator run:
su
cat /sdcard/tweaks > /data/tweaks
rm /sdcard/tweaks
cd /data/
./tweaks
If it doesn't run, type first:
chmod 755 /data/tweaks
Additional notes:
Script does not work if run from sdcard, must be in /data/ or /system/ (this one goes to allsalvati for testing)
---
If anything is wrong i will fix it, but only if you give me feedback
If you know any good tweaks, say it and i'll add them.
---
Changelog:
version 1.02:
backup/restore added
version 1.01d:
working again. sorry for the mess...
version 1.01c:
nothing new. just rearranging code
version 1.01b:
messages were not staying in output. fixed
version 1.01a:
small fix. v1.01 was not working
version 1.01:
added status menu
ruigui said:
Here is a script i've made (had nothing to do, so...). Phone must have busybox.
Download:
http://www.4shared.com/file/gApTB6EG/tweaks.html
md5 ea568c399c67ecd87db0dd790cdf0e93
Just copy the file to your sdcard. Then in a terminal emulator run:
cd /sdcard/
./tweaks
If it doesn't run, type first:
chmod 777 /sdcard/tweaks
Please give me some feedback. I don't own the phone so i can't test.
Click to expand...
Click to collapse
what the script does?
So script should be able to do:
enable/disable hw acceleration
enable/disable jit
enable/disable stagefright player
change heapsize
Yes. For now it's what it does.
The ideia is to be able to enable/disable a certain tweak, without reflashing zips, and rewriting files in phone.
But i need some feedback to know if it is working. I can't test it.
It will only change values in /data/local.prop, nothing else.
It seems that it is well written, so I will try that and let you know what's happened.
Thanks for testing. I'm still waiting to have some money so i can buy this phone...
Meanwhile, i'm "playing" with ROMs and files. I'm not good at scripting, but i'm trying to learn while doing something useful.
How much did you increase the heap size?
domenic_s said:
How much did you increase the heap size?
Click to expand...
Click to collapse
I didn't increase it. Script shows this message:
"default=24, recommended=32"
"enter new heapsize value (1-64): "
You can enter any value between 1 and 64.
If you enter any other value, or a string, character, symbol... script will show this message:
"wrong value"
"please input a value between 1 and 64"
For those who don't feel like editing this themselves this is great. Thanks for releasing it for people to try out more tweaks on stock ROMs.
i'm trying to run this script and gives me the following message: ./tweaks: permission denied
Before anything i typed su, then chmod 777 and it gave me error.
It should work be working...
Anyone else confirms this issue? Is this script running or not?
If it is working and there are more tweaks, i can easilly add them to the script.
If this is an isolated case, i really can't help. I don't own an android phone (yet), so i can't test....
allsalvati do you have busybox installed?
No, i don't.
Sent from my LG-P500h using XDA App
That may be your issue.
You must mount /system/ as read-write, then copy busybox binary to /system/xbin/, then run these commands in terminal emulator:
su
cd /system/xbin
/system/bin/chmod 755 busybox
./busybox --install -s /system/xbin
After that you can mount /system/ as read only again, and reboot your phone.
I don't know if there is another way to install it that is easier.
I downladed busybox installer from market and the app says that was installed. The. /tweaks gives me the same message.
How do i test if busybox was installed right?
Sent from my LG-P500h using XDA App
I found this:
That is a problem, you cannot chmod a script to executable on the SD card. (well some things can, but 99% no) the system is designed to prevent u executing scripts from an SD card
cp it to /system/xbin or /system/bin.
Or if u hate to see it in system', use /data/
THEN chmod it. should be fine to run
Click to expand...
Click to collapse
Try to copy the file to /data/ (so you don't mess with /system/), and then try to run it with:
cd /data/
chmod 777 tweaks
./tweaks
It should not need to be run as root
Moved to /data and worked.
I changed heap size to 32 and disabled hardware accelaration just to test.
With hw acc - 981 on Quadrant
Without - 820
So i think this is working.
Perhaps you should print the values so the user can see what is enabled or not before apply.
Thanks for your help
Sent from my LG-P500h using XDA App
Can you test something for me?
Make sure you have hardware acceleration disabled, and reboot you phone.
Then open terminal and run:
getprop | grep hw (see what it outputs)
then run the script, enable hardware acceleration on it, but DON'T reboot your phone yet.
Then exit script, and run again:
getprop | grep hw
Has the value changed, or is it the same?
I need to know if the system assumes immediately any changes (although they may not be functional until reboot).
This is needed to work on your request.
allsalvati said:
Perhaps you should print the values so the user can see what is enabled or not before apply.
Click to expand...
Click to collapse
I'll work on that and post an update after someone tries what i asked above.
Thanks for testing
EDIT: to test benchmarks, enable/disable jit. It gives greater differences in values
I tried what you say and both outputs are the same:
$getprop | grep hw
[debug.sf.hw]: [0]
[hw.keyboards.65537.devname]: [7k_handset]
[hw.keyboards.65540.devname]: [thunder_keypad]
[hw.keyboards.65541.devname]: [touch_mcs6000]
[hw.keyboards.65542.devname]: [atcmd_virtual_kbd]
Edit: Tested disabling JIT and it worked. Linpack Before 7.35 - After 4.3
So i can't rely on getprop to check current values...
If anything is changed, getprop won't give the right output till reboot.
Damn... Script was almost updated. Now i must find a new way and redo this section.
Thanks for testing again
EDIT:
New version for download at first post. status menu added.
I think it's all ok.
It seems work fine on my phone. But I can't see the status. When I choose to see current status or status after reboot, the screen of my emulator returns too fast to the selection menu (show curent status or after reboot) and I can't see anything !
Credit for koush for Droid2 Bootstrap
Credit for edgardcastro for sharing lots of information about 2nd-boot on Milestone1
Credit for Skrilax_CZ for 2nd-init and sh hijack
If you just want to install 2nd-init on your phone you can skip the whole guide and flash update-2nd-init.zip into your phone. As usual I will not hold responsibility to any damages it may cause.
WARNING: Use this ONLY if you know exactly what you are doing. This guide will make major changes in the /system partition and may turn the phone inoperative. I won’t hold responsibility if you brick your phone or to any damages it may cause.
Pre-requisites: A computer with Android SDK and ADB drivers installed and working. It’s recommended to have RSD Lite 4.9 and the appropriate SBF image just in case anything goes wrong.
This guide was made using a Brazilian Motorola Milestone2 based on Brazil Retail SBF and a computer running Windows Vista 32-bits. I started it from the scratch by flashing my phone with RSD Lite 4.9 and performing a full data/cache wipe, just to make sure any changes were discarded.
Note: Commands that should be entered in command prompt will be listed as: “C:\> <command>”. Commands issued to ADB Shell will be listed as: “# <command>”.
1. Enable USB Debugging on your phone;
2. Get permanent root. I used the app z4root which can be found here on XDA;
3. Install Droid2 Bootstrap. It may be downloaded from Market to support the developer. More info here http://www.koushikdutta.com/2010/08/droid-x-recovery.html;
4. Open Droid2 Bootstrap and click “Bootstrap Recovery”;
5. Use bootstrap to reboot into Clockwork Recovery and backup your phone;
6. Reboot;
7. C:\> adb remount
8. # stop
9. # mkdir /system/etc/rootfs
10. # cp /*.rc /system/etc/rootfs
11. # mkdir /system/etc/init.d
12. # cp /system/bin/sh /system/bin/_sh
13. # cp /init_prep_keypad.sh /system/bin
14. C:\> adb push sh_hijack.sh /system/bin/
15. C:\> adb push 2nd-init /system/bin/
16. C:\> adb push sysinit /system/bin/
WARNING: at this point you should keep a terminal window (adb shell) opened before replacing the 'sh' binary. This is so because you wont be able to open a new abd shell window to run the chmod command.
17. C:\> adb push sh /system/bin/
18. # chmod 755 /system/bin/sh
19. # chmod 755 /system/bin/sh_hijack.sh
20. # chmod 755 /system/bin/2nd-init
21. # chmod 755 /system/bin/sysinit
22. # ln -s /system/bin/busybox /system/xbin/mount
23. # ln -s /system/bin/busybox /system/xbin/rmdir
24. # ln -s /system/bin/busybox /system/xbin/cp
25. # ln -s /system/bin/busybox /system/xbin/umount
26. # ln -s /system/bin/busybox /system/xbin/run-parts
27. # reboot
28. At this point you should be getting into Clockwork Recovery every time, no matter how many times you have rebooted or if you’ve taken the battery of or not. THIS IS NORMAL. It means that the 2nd-boot + sh hijack is working as it should. The boots into clock recovery are caused by a conflict between sh hijack and logwrapper hijack (used by Droid2 Bootstrap). Continue the guide to fix this issue.
29. In clock recovery menu go to: mounts and storage>mount /system;
30. Open ADB Shell again (it will be available in clockwork recovery as well);
31. # cp /system/bin/logwrapper.bin /system/bin/mylogwrapper
32. C:\> adb pull /system/etc/rootfs/
33. Open init.rc and init.mapphone_umts.rc into a text editor that preserves unix end-line format (e.g.: notepad++). Find all entries of “/system/bin/logwrapper” replacing for “/system/bin/mylogwrapper”.
34. In init.mapphone_umts.rc find entry for “exec /init_prep_keypad.sh” replacing for “exec /system/bin/init_prep_keypad.sh”. Add the following text to the end of this file to be able to run all scripts in /system/etc/init.d at boot time:
Code:
service bootscripts /system/bin/sysinit
class post-zygote_services
disabled
oneshot
35. Save and close.
36. C:\> adb push init.rc /system/etc/rootfs/
37. C:\> adb push init.mapphone_umts.rc /system/etc/rootfs/
38. # chmod 755 /system/etc/rootfs/init.rc
39. # chmod 755 /system/etc/rootfs/init.mapphone_umts.rc
40. Choose “Reboot system now” in clock recovery menu;
You’re all set! Now it is just a matter of changing the rc files in /system/etc/rootfs to customize your system boot.
If you want to log the system boot you may also copy the provided log-init.sh script into /system/etc/rootfs and uncomment the line “exec /log_init.sh” from my init.rc file. Doing so will create the /data/logcat.log file that may get huge in sometime.
2nd-init files and my modified *.rc files attached.
Have fun!
UPDATED to version 2.0.0 (froyo) this version exploits /system/bin/mount_ext3.sh instead of sh binary. It's a new method I developed in order of starting 2nd-init earlier but also keeping compatibility with Droid2bootstrapper (recovery takes place first). This might help me booting Leaked GB from 2nd-init, which wasn't possible on the previous version. Take note it's not ready yet to apply on GB.
I just missed the exec /system/bin/init_prep_keypad thanks!
What is this for?
Sent from my A953 using XDA App
inheme said:
What is this for?
Sent from my A953 using XDA App
Click to expand...
Click to collapse
A method to customize initialization scripts of android system. It's a major hack used be some Milestone1 custom ROM's. I've succeeded into porting this to MS2, and I think some modders here of XDA may be interested into adding this to custom ROM's. It may be added to the stock ROM (as I did) but it is not something that everyone is willing to try.
Word of advise: If you don't know what it is you don't need it
Ok thanks for the explanation
So it means that custom roms will be easier to create?
Sent from my A953 using XDA App
That's some major news for our little community.
Tell me if I'm wrong, but since init starts after the kernel is loaded, it's not useful at all for loading a custom kernel, true?
But having a custom init script is a step to CyanogenMod 6 port on Milestone 2, still true?
Anyways, great job, and great howto.
momus87 said:
That's some major news for our little community.
Tell me if I'm wrong, but since init starts after the kernel is loaded, it's not useful at all for loading a custom kernel, true?
Click to expand...
Click to collapse
To load a custom kernel we'll need that kexec hack that team freemymoto is working on.
But having a custom init script is a step to CyanogenMod 6 port on Milestone 2, still true?
Click to expand...
Click to collapse
Well, it's possible, but I believe the big issue here is the impossibility of running custom kernels. Even so, a skilled Modder may be able to overcome that and port CM6 to MS2 using Motorola's stock kernel. It has been done for the MS1.
Anyways, great job, and great howto.
Click to expand...
Click to collapse
You're welcome.
Thanks, r2beta0... this is going to help us out a lot!
r2beta0 said:
Well, it's possible, but I believe the big issue here is the impossibility of running custom kernels. Even so, a skilled Modder may be able to overcome that and port CM6 to MS2 using Motorola's stock kernel. It has been done for the MS1.
You're welcome.
Click to expand...
Click to collapse
Guess that would be me
nah just kidding. I've just happened to have some luck porting Froyo and Gingerbread to the bootloader-locked x10 mini pro. I've just ordered my milestone 2 and I will work on CM6. AWESOME JOB on the 2nd init man! Really, thanks!!
edit: just can't stop thanking you! You saved me a lot of work and porting CM will be easy as sh*t for me now! THANKS
Mikevhl said:
Guess that would be me
nah just kidding. I've just happened to have some luck porting Froyo and Gingerbread to the bootloader-locked x10 mini pro. I've just ordered my milestone 2 and I will work on CM6. AWESOME JOB on the 2nd init man! Really, thanks!!
edit: just can't stop thanking you! You saved me a lot of work and porting CM will be easy as sh*t for me now! THANKS
Click to expand...
Click to collapse
You're welcome! You can count on me to provide as much help as I can to free our MS2's from Motorola's hand. I would be very grateful if you could share your knowledge of porting CM to locked devices. I was trying to port MIUI and Shadow mod BR to MS2 but I got stuck when dealing with proprietary files.
Sent from my A953 using XDA App
@r2beta0
Could this port work on Motorola defy?
Sent from my MOTO Defy
demolition23 said:
@r2beta0
Could this port work on Motorola defy?
Sent from my MOTO Defy
Click to expand...
Click to collapse
It's very likely, since the 2 devices are very similar. Most of the files I attached are from Milestone1 and works perfectly on MS2. Though I recommend you to NOT replace your *.rc files with the attached ones since they could be not compatible. It would be better if you edit your own files. Also try it ONLY if you have a working version of ClockworkMod Recovery (or other custom recovery). You may adapt this guide for your device and post it here on XDA, just remember to mention my name on credits
Already posted and hoping someone to port this..
http://forum.xda-developers.com/showthread.php?t=1003449
demolition23 said:
Already posted and hoping someone to port this..
http://forum.xda-developers.com/showthread.php?t=1003449
Click to expand...
Click to collapse
BTW, why do you want to use 2nd-init? You know, this guide is more inclined for devs/mods who want (need) to include this feature on their ROM's. With this you can change the way things are loaded on linux system before android starts up. But to take advantage of that you should know a lot about how linux works and so on. Regular users should look for a ROM based on the features he needs. Most ROM's already have 2nd-init implemented, but it's not something users are aware of.
Possible issue I've come across:
When replacing sh, i can no longer re-open the shell for obvious reasons... potentially I need to already have a second terminal open with shell running in it already?
SBFing and trying again :3
smacky_wolf said:
Possible issue I've come across:
When replacing sh, i can no longer re-open the shell for obvious reasons... potentially I need to already have a second terminal open with shell running in it already?
SBFing and trying again :3
Click to expand...
Click to collapse
I had no such issue here. When executing the steps of this guide I kept two windows opened all the time. One command prompt to run adb push/pull and another window running adb shell.
Thanks to point that out! I will post a warning in the main post. You should have a adb shell window already running to be able to run chmod just after replacing sh.
But don't worry, you don't need to SBF. Just reboot into clockwork recovery, mount /system via menu, and open your adb shell. It uses a different shell so you can fix the problem in /system/bin.
Looks like Motorola Defy now has CyanogenMod 7 using 2nd-init script! Wish same were the case for MS2.
syl0n said:
Looks like Motorola Defy now has CyanogenMod 7 using 2nd-init script! Wish same were the case for MS2.
Click to expand...
Click to collapse
I'm on it, but development is slow
No necessary to use 2nd init.
Just install "droid 2 bootstrap" and Rom Manager will work perfectly.
keylight65 said:
No necessary to use 2nd init.
Just install "droid 2 bootstrap" and Rom Manager will work perfectly.
Click to expand...
Click to collapse
What are you talking about? This guide isn't related to ROM Manager.
Hi everybody, I would like to share my experiences with the Infinity and ask you guys to share your opinions, thoughts and ideas on tweaking it. Hopefully we can sort something out together.
Please remember that you can brick your tablet with any of these methods and lose your warranty too and be the one solely responsible for it. I have not bricked mine, so I am writting all of this with best intentions . Proceed with caution and only if you are sure that your Infinity not booting will not lead you to jumping off a high building! Seriously.
Ok, here it goes.
Hit [THANKS] if it helps.
Seems this thread somehow got to the News, so special thanks go to Joe and those of you who have reported it newsworthy. I'm glad I could've helped you with this!
Remember 1) you'll have to do most of these each time you update firmware / change ROM and 2) go back to stock /system files every time before you apply an OTA update, as it does various checks on /system integrity now.
1. ROOT
Don't use ASUS Device Tracker! (see point 6. below)
Install SuperSU and follow these steps before updating to the Jelly Bean to preserve root (thanks to nooktablet for posting this). Others said that Superuser app combined with RootKeeper sufficed, so do as you wish.
DroidEris1981 has reported that in his case on the .30 firmware he was only able to root his Infinity using an older version of Debugfs and only when pausing it at each reboot, waiting for the device to fully boot up before the next step.
So far the only rooting method that works is the Debugfs method by sparkym3. By rooting you can boost your Infinity's performance a bit, including its poor I/O results, and much, much more (see threads on reasons for rooting and apps).
Once again: ROOT BEFORE UPDATING TO THE JB!
If you've failed to do this, however, there is still a way to work things out - see the first few posts in this thread if you're under unrooted JB now.
In case you experience problems using this method, you may try one of the solutions described in this thread, but as there is a new 2.2 version now, you should be good just using it.
Some need to RUN the Superuser app first before it starts working. And remember about BusyBox, it comes handy in many situations, especially if you are going to use the shell. And you can use SuperSU instead of the "default" Superuser app.
RootKeeper might come in handy when updating firmware on a rooted Infinity.
1.1. We have the unlocking tool now, and a few custom ROMs in the development section.
2. I/O scheduler [only after rooting your device] OBSOLETE
Since the .26 update and under the JB as well cfq is the default scheduler and better than non-stock sio, so no reason to change the scheduler at this point already on >= 9.4.5.26 firmware!
After a day of using JB I can say that (stock) noop is slightly faster than cfq for most uses.
[REMOVED]
3. build.prop tweaks ("/system/build.prop" file)
These are for the ICS. We'll all have to see how these perform under the JB. So far changing the DPI via build.prop has been confirmed to be obsolete.
EDIT 22.12.2013 Deleted several obsolete entries, see LaraCroft304's post for reference.
I have used various suggestions as a reference, incl. demandarin's tweaks for the Prime (just search "build.prop tweaks" on xda and read about what these tweaks do). I am still unsure of some of them, e.g. the proper heap size instead of the default 256m (or maybe we should leave it be?). The tweaks I'm using are the following.
Edit: I'm leaving the default heap size, I think it's better for the games.
Lines to EDIT:
#an old proposal, which seems to be of no use
#dalvik.vm.dexopt-flags=m=v,o=y
dalvik.vm.dexopt-flags=v=n,o=a,u=y
#In case you experience problems with some apps after this, try (unhash) this instead:
#dalvik.vm.dexopt-flags=v=a,o=v,u=y,m=y
#(you can also see, for example, this thread for instructions)
# optional: CHANGE SCREEN RESOLUTION / PIXEL DENSITY (so that your screen can become more capacious)
# ro.sf.lcd_density = 160
Lines to ADD:
# BATTERY SAVING
pm.sleep_mode=1
wifi.supplicant_scan_interval=180
# UI & GENERAL PERFORMANCE
ro.kernel.android.checkjni=0
persist.sys.strictmode.visual=0
persist.sys.strictmode.disable=1
dalvik.vm.execution-mode=int:jit
com.ti.omap_enhancement=true
# MEDIA QUALITY & PERFORMANCE
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=false
media.stagefright.enable-http=true
ro.media.enc.jpeg.quality=90
ro.media.enc.hprof.vid.bps=8000000
persist.sys.use_dithering=1
# NETWORK PERFORMANCE
# there are different types of advice here, you can try what work's best for you out of the latter two (just delete all the spaces which xda keeps adding!):
net.tcp.buffersize.default=4096,87380,256960,4096,16384,256960
#net.tcp.buffersize.wifi=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.wifi=262144,524288,1048576,262144,524288,1048576
# SWITCHING SOME NOTIFICATIONS OFF
# disable sending usage data
# disable adb notifications
persist.adb.notify=0
# FAST REBOOT
persist.sys.purgeable_assets=1
# you can also unhash this and disable boot animation for faster boot:
# debug.sf.nobootanimation=1
# This is for current, Wi-Fi only version of Infinity of course:
ro.carrier=wifi-only
# Just for those who need it - unhash the following line to make your device run all ADB shell and terminal emulator commands as ROOT by default (use with caution)
# ro.secure=0
3.1. You can edit the build.prop file manually, you can use one of a few apps out there to manage it, but I have found manually mounting the system r/w (and r/o again after changing the file) and editing it through a PC (you can use Dropbox) or the Infinity with the dock most helpful - you can just cp the new file to (remember to make a backup copy of the old file just in case!).
If you like using the term, you can just 'su' and write these commands:
a) R/W before edit:
mount -o rw,remount /system
b) R/O after edit (remember to run 'chmod 644 /system/build.prop' as root before remounting /system R/O):
mount -o ro,remount /system
3.2. Remember to reboot your device after changing the file. Clearing dalvik-cache won't hurt either.
Edit: Actually I highly recommend wiping dalvik cache to avoid bootloops (as root: rm /data/dalvik-cache/*) <- and then.reboot
4. Minfree tweaks:
You can either change the values in /sys/module/lowmemorykiller/parameters/minfree (remember these are pages, so 1024 means 4MB!) or use any of the apps from the Playstore meant for that. I'm using System Tuner for things like that (look for Tweaks / Auto-Kill in the app). You might set anything you like, possibly 8,16,200,220,240,275 MB proposed by the author of the (messy) SuperCharge script for the 1GB RAM devices (based on a minfree calculator by another XDA member). I have it currently set on 8,16,32,128,192,192 MB, which seems aggressive enough.
You can read more about it and what these values mean here.
You can also have a look at my thread on battery life.
5. Disable "smart dimmer", which is the reason you can see some screen flickering when changing between light and dark backgrounds that many find annoying (described by some as "dynamic contrast", which it resembles):
Can be done through SYSTEM SETTINGS under the JB, so no need to do this manually anymore.
To disable:
echo 0 > /sys/devices/tegradc.0/smartdimmer/enable
To re-enable echo 1 to the this file or simply reboot.
Be sure to include this in a script so that rebooting won't change it (just make an .sh script with the above line in it, you can use either SManager or system .sh scripts (you can use my simple solution posted here if you don't like editing files yourself). See also jtrosky's hints on changing the brightness settings.
Please note that it may negatively affect your battery life, although with brightness set low it shouldn't be much worse.
All credit goes to those who have found out about it - see this post for details.
6. Disable remote management that allows ASUS (or anybody in charge of their servers) to track, lock or wipe your device over-the-air or steal your data, which has been confirmed ASUS is doing: read the whole story about warranty voided because of rooting here.
7. Install Volume+ or a similar app to boost your device's sound level (you can register here to get the full version for free, but if it helps, support the developer). And remember to change the audio device in the system audio settings to Volume+!
8. Other tweaks, init.d, scripts etc.
See the development section for custom ROMs which include various tweaks and for custom recoveries.
9. Some keyboard solutions:
Re-map the browser keyhttp://forum.xda-developers.com/showthread.php?t=1497624 in the dock in order to be able to use your favourite browser or do some custom re-mappings.
In case of problems with diacritics when docked, be sure to use KLSwitcher for setting your locale.
Finally, not really a tweak, but something that a lot of users find helpful: KEYBOARD SHORTCUTS.
10. Remove bloatware (see the first few posts with further links here).
11. Set background processes to max. 4 in the dev. settings for better stability (that's true for the ICS at least).
<----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------->
And remember, at the end of the day, when you're done tweaking, you should disable USB debugging if you don't want to get hacked.
Hit [THANKS] if it helps.
Thank you for this! I'll have to try some of these out when I pick up my tablet.
i remember reading about some 300 users using, browser2ram (i think that's what its called) for a better internet browsing experience.
denniegst said:
i remember reading about some 300 users using, browser2ram (i think that's what its called) for a better internet browsing experience.
Click to expand...
Click to collapse
Can you give us a link? Google is not helpful with this name you mentioned (browser2ram).
http://forum.xda-developers.com/showpost.php?p=25286407&postcount=61
i think it only works on stock browser, but i could be wrong. and since everything is sent to the ram, once the tablet resets everything will be lost: browser history settings etc
denniegst said:
http://forum.xda-developers.com/showpost.php?p=25286407&postcount=61
i think it only works on stock browser, but i could be wrong. and since everything is sent to the ram, once the tablet resets everything will be lost: browser history settings etc
Click to expand...
Click to collapse
Thanks, that sounds interesting, but I am not sure there is a need for it on the Infinity. Dolphin HD performs exceptionally well (thanks for the info, ray3andrei: http://forum.xda-developers.com/showthread.php?t=1752809&page=2).
Edit: Can't recommend Dolphin anymore due to serious privacy issues.
Hi
Correct me if i'm wrong:
1. install the drivers if they are not installed allready
2. tick usb debugging
3. tick unknown sources
4. unzip DebugfsRoot_v1.8
5. connect tab to pc
6. run RootDebugfs.bat
7. select option 1 -Root
8. since haven't go further this step, i don't know what's next till rebooting
that's it? device rooted?
i have a little experience in rooting cause i have rooted my galaxy s a few times, but that phone is almost unbrickable
i just want to be sure i'm doing it right
thanks
dobranszky said:
Hi
Correct me if i'm wrong:
1. install the drivers if they are not installed allready
2. tick usb debugging
3. tick unknown sources
4. unzip DebugfsRoot_v1.8
5. connect tab to pc
6. run RootDebugfs.bat
7. select option 1 -Root
8. since haven't go further this step, i don't know what's next till rebooting
that's it? device rooted?
i have a little experience in rooting cause i have rooted my galaxy s a few times, but that phone is almost unbrickable
i just want to be sure i'm doing it right
thanks
Click to expand...
Click to collapse
Yep, that's basically it
Then it reboots a few times while pushing some files through adb, you get the Superuser program installed etc. After a few minutes you should have a rooted Infinity.
However, it will be much more fun after installing BusyBox from the Market/Play. It gives you a bunch of commandline tools to play with.
Just remember to charge your device and not to connect any other Android device while rooting.
I don't understand why you are using the 1.8 version when the 1.9 is there. I used 1.9 to root without any problems.
Alkzn said:
I don't understand why you are using the 1.8 version when the 1.9 is there. I used 1.9 to root without any problems.
Click to expand...
Click to collapse
There are links to both in the thread I was referring too. Actually I don't see any harm in using 1.8, as 1.9 is just updated Superuser app, which will update itself from Google Play anyway (they had some problems uploading the file to xda btw)
Hi fellow Infinity-Users!
I tried both versions (1.8/1.9), and both equally worked/failed with my (european) TF700.
The issue that actually broke the batch-script was adb wait-for-device, which just seemed to catch a timeout after waiting for the tablet to reboot.
As there is little magic in that script, you can safely execute all it does by hand (basically all the lines involving adb). That's the way I just rooted my TF700 and it worked like a charm.
Alternatively, if you don't feel comfortable with executing the adb actions by hand, you might want to just replace all occurrences of
Code:
adb wait-for-device
with
Code:
pause
(or something like that.)
Then you will have to hit enter (or some other key) each time once the tablet has rebooted.
What is actually needed for rooting:
Wait for your tablet to be fully booted up.
In a terminal execute the following commands in the folder you unpacked the rooting stuff to:
Code:
adb kill-server
REM as we are not rebooting and we don't hit a timeout, the first wait works
adb wait-for-device
adb push debugfs /data/local/
adb push su /data/local/
adb push debugfsinput /data/local/
adb shell mv /data/local/tmp /data/local/tmp.bak
adb shell ln -s /dev/block/mmcblk0p1 /data/local/tmp
adb reboot
REM Wait for the tablet to reboot
pause
adb shell chmod 777 /data/local/debugfs
adb shell "/data/local/debugfs -w /dev/block/mmcblk0p1 < /data/local/debugfsinput"
adb shell rm /data/local/tmp
adb shell mv /data/local/tmp.bak /data/local/tmp
adb shell rm /data/local/su
adb shell rm /data/local/debugfs
adb shell rm /data/local/debugfsinput
adb reboot
pause
REM Wait for the tablet to reboot
Now check the if you've got a rootshell - thus the given uid and gid of the are indeed root (0). make sure to remove the REM from the first or second part, if needed
You do this eg. by executing:
Code:
adb shell "/system/xbin/su -c id"
If you are root, install the Superuser Management Toolpack:
Code:
adb install Superuser.apk
adb reboot
Else cleanup:
Code:
adb shell /data/local/nachoroot.bin --undo > nul
adb reboot
Hope this cleared things up a little!
(all commands are taken from the script. If someone feels this is undesirable to post here, please let me know, I'll remove that immediately. Thanks to sparkym3, miloj and viperboy for giving me root-power !)
Thanks, that's interesting, I have the "European" version, as you called it, or rather WW firmware, and the script worked perfectly for me.
d14b0ll0s said:
Thanks, that's interesting, I have the "European" version, as you called it, or rather WW firmware, and the script worked perfectly for me.
Click to expand...
Click to collapse
True, I'm running WW_epad-9.4.5.21-20120601. From what I've seen so far, the issue seems not to be related to the tablet, but seems to be some issue with the OS adb is run on. In my case this is win7x64. What OS are you running? Would be interesting to track this down for others who may run into this issue in the future .
burningcf said:
True, I'm running WW_epad-9.4.5.21-20120601. From what I've seen so far, the issue seems not to be related to the tablet, but seems to be some issue with the OS adb is run on. In my case this is win7x64. What OS are you running? Would be interesting to track this down for others who may run into this issue in the future .
Click to expand...
Click to collapse
Good point. Unfortunately, the OS version trace seems to lead to nowhere, as I'm on Win 7 x64 too... perhaps something else then?
Run on balanced no matter what, everything runs better, and the tablet seems to not get stuck anymore or lag while downloading... so for the love of your infinity run on balanced instead of performance
Sent from my Jelly Beaned GNexus
ray3andrei said:
Run on balanced no matter what, everything runs better, and the tablet seems to not get stuck anymore or lag while downloading... so for the love of your infinity run on balanced instead of performance
Click to expand...
Click to collapse
I had good experience with "balanced" too, but if you compare it to benchmarks you can see that actually some operations are faster in "performance": mostly GPU, but not only that - RL Benchmark (SQLite Performance) is 110 in balanced instead of <90, reading & writing speeds are often faster in "performance" etc. But I agree it is the best mode to be running in everyday use, mostly because of power/battery *balance* and governing the CPU.
d14b0ll0s said:
I had good experience with "balanced" too, but if you compare it to benchmarks you can see that actually some operations are faster in "performance": mostly GPU, but not only that - RL Benchmark (SQLite Performance) is 110 in balanced instead of <90, reading & writing speeds are often faster in "performance" etc. But I agree it is the best mode to be running in everyday use, mostly because of power/battery *balance* and governing the CPU.
Click to expand...
Click to collapse
i really cant seem to get better gpu performance,,, quite the contrary i get better o balanced
Sent from my Asus Transformer Pad Infinity
I used sparky root on my prime and my tf300. Question. Can I use sparky root on my tf700 or will I need to do the debugfs method? If I have to use the debugfs method is there a step by step link?
leroybrute said:
I used sparky root on my prime and my tf300. Question. Can I use sparky root on my tf700 or will I need to do the debugfs method? If I have to use the debugfs method is there a step by step link?
Click to expand...
Click to collapse
So far only Debugfs has been confirmed to be working.
You might find either of these useful:
http://forum.xda-developers.com/showthread.php?t=1706588
http://forum.xda-developers.com/showpost.php?p=28490040&postcount=8
Thank you
Hi all!
Was about to purchase a Nexus 7 when I saw a huge discount on the Asus TF101 and decided to take it. How I have a it in front of me proudly informing it has the firmware revision IML74K.WW_epad-9.2.1.27-20120615. BTW, the s/n starts with B50 if it matters.
And now what? Wait for the official JB or root it right now? I usually root all my devices at least to have nandroid + TiBu, even if I don't plan to install any alternative FW.
The problem is it's an ICS 4.0.3 with the problem to enter into recovery mode and I have only a Mac computer, no Windows and no Linux machines around. I read the threads and see every time the Windows tools, nothing for Mac. No root from SD card neither.
Any advice how to root using the Transformer itself or my Mac? And any advice regarding best JB ROM or at least best kernel for stock 4.0.3 ROM with exFAT support? I don't use NTFS because my Macs can't write on and old FAT16 has the famous 4 Gb limit, not good for the movies.
Many thanks in advance.
You could try and install Windows on your Mac to essentially have a dual boot of both OS's. Or you could use something like VMWare (I think that's what it is but I'm like 5% sure) which allows you to run windows without necessarily installing it. Anyway, I suggest, if you can, to go ahead and root your device and install a JB ROM like EOS or CM10 or something.
If it's not possible to do Android modifications on a Macintosh it looks like your only option would be to setup a dual boot with Linux to do your Android Rooting and ROM flashing since I would imagine you would want to avoid having to use Windows for this It would be better to avoid virtual machines to do device modifications and just stick to the dual boot option since support for USB devices is iffy in virtual machines.
Hi all,
Shmi117 said:
You could try and install Windows on your Mac to essentially have a dual boot of both OS's.
Click to expand...
Click to collapse
No chance! I don't like to spend hours installing Windows and all this stuff again !!! :crying:
WCL1990 said:
If it's not possible to do Android modifications on a Macintosh it looks like your only option would be to setup a dual boot with Linux to do your Android Rooting and ROM flashing since I would imagine you would want to avoid having to use Windows for this It would be better to avoid virtual machines to do device modifications and just stick to the dual boot option since support for USB devices is iffy in virtual machines.
Click to expand...
Click to collapse
Basically what Linux can to Mac OS X can do. At least regarding adb and the command line use. The problem is I have found tons of good information about how to do it using Windows, but nothing for Linux nor Mac.
OK, here is the answer. One can root the Asus Eee Pad Transformer TF101 using Mac OS X only!
Developing in next message...
OK, here is the solution. :fingers-crossed:
First of all, I presume the Android SDK for Mac OS X is installed and upgraded.
Next, on the Transformer please go to Settings -> Developer options and activate the USB debugging. Finally, please check this forum thread and download the latest version of PERI. Yes, PERI for Windows 0.4 as of today. Please unzip the downloaded file.
No sorcery or black magic here, I've just learned from the bat file and tried to reproduce the whole procedure manually using adb.
Most Linux users will smile, but I will show the commands the way most Mac OS X user will need to input them. Basically, you don't really know that the shell path is and what "finally add adb to your path" means, right?
1. OK, please open the Finder and go to the directory where the adb executable lives. Something like ~/Downloads/android_sdk/android-sdk-macosx/platform-tools/.
2. Now please open the Terminal.app inside Application/Utilities folder and go to the same directory.
3. Please connect the Transformer to the Mac using the USB cable.
4. First of all, let's see if adb sees the Transformer. Please input
Code:
./adb devices
If everything is OK, you'll see something like this:
Code:
List of devices attached
024640c082db4561 device
5.
Code:
./adb push /Users/YOURUSERNAME/Downloads/OneclickrecoveryV0.4/recoveryblob /sdcard/
Basically you input ./adb push, drag the a.m. file and next input /sdcard/
6.
Code:
./adb shell mv /data/local/tmp /data/local/tmp.bak
7.
Code:
./adb shell exit
8.
Code:
./adb shell ln -s /dev/block/mmcblk0p4 /data/local/tmp
9.
Code:
./adb reboot
Wait while the Transformer reboots.
10.
Code:
./adb shell dd if=/sdcard/recoveryblob of=/dev/block/mmcblk0p4
11.
Code:
./adb shell exit
12.
Code:
./adb reboot
Wait while the Transformer reboots.
13.
Code:
./adb push /Users/YOURUSERNAME/Downloads/OneclickrecoveryV0.4/Superuser-3.0.7-efghi-signed.zip /sdcard/
See #5.
14.
Code:
./adb reboot
Wait while the Transformer reboots.
15. Now please shut down the Transformer manually and boot into recovery. Please hold Power + Volume Down buttons and next confirm with Volume Up button when asked. Rogue XM recovery will boot.
16. Wipe cache, wipe Dalvik cache, next choose Install zip file from internal storage and choose the Superuser-3.0.7-efghi-signed.zip.
17. When it's done, reboot.
18. PROFIT. :good: Your device is rooted with Rogue XM recovery installed.
From there I suggest to install SuperSU and eventually SuperSU Pro as it seems to work better than Superuser and Superuser Elite respectively. You can eventually get rid of Superuser if you wish so, instructions available in this forum thread. As I own both SuperSU Pro and Superuser Elite, I've installed SuperSU and upgraded Superuser, just in case of. You should not mix them, though, thus I've revoked the root permission of Superuser.
Next I've installed Busybox. I don't know if it's the best version for TF101, works well on my GNote.
Finally, let's play with the recovery options courtesy of some awesome developers. :good: We can choose among Rogue XM Touch, CWM classic, CWM 6.x and official or modified TWRP. I've chosen the official TWRP with GooManager.
Next stop, Titanium Backup.
Should you have other recommendations, please do not hesitate.
Thanks a lot friend. I used the same procedure to root my TF101 using Ubuntu Are you using any Customised ROM ? I am using CM10 based ROM built by RaymanFX and it is simply awesome
iLearner said:
OK, here is the solution. :fingers-crossed:
First of all, I presume the Android SDK for Mac OS X is installed and upgraded.
Next, on the Transformer please go to Settings -> Developer options and activate the USB debugging. Finally, please check this forum thread and download the latest version of PERI. Yes, PERI for Windows 0.4 as of today. Please unzip the downloaded file.
No sorcery or black magic here, I've just learned from the bat file and tried to reproduce the whole procedure manually using adb.
Most Linux users will smile, but I will show the commands the way most Mac OS X user will need to input them. Basically, you don't really know that the shell path is and what "finally add adb to your path" means, right?
1. OK, please open the Finder and go to the directory where the adb executable lives. Something like ~/Downloads/android_sdk/android-sdk-macosx/platform-tools/.
2. Now please open the Terminal.app inside Application/Utilities folder and go to the same directory.
3. Please connect the Transformer to the Mac using the USB cable.
4. First of all, let's see if adb sees the Transformer. Please input
Code:
./adb devices
If everything is OK, you'll see something like this:
Code:
List of devices attached
024640c082db4561 device
5.
Code:
./adb push /Users/YOURUSERNAME/Downloads/OneclickrecoveryV0.4/recoveryblob /sdcard/
Basically you input ./adb push, drag the a.m. file and next input /sdcard/
6.
Code:
./adb shell mv /data/local/tmp /data/local/tmp.bak
7.
Code:
./adb shell exit
8.
Code:
./adb shell ln -s /dev/block/mmcblk0p4 /data/local/tmp
9.
Code:
./adb reboot
Wait while the Transformer reboots.
10.
Code:
./adb shell dd if=/sdcard/recoveryblob of=/dev/block/mmcblk0p4
11.
Code:
./adb shell exit
12.
Code:
./adb reboot
Wait while the Transformer reboots.
13.
Code:
./adb push /Users/YOURUSERNAME/Downloads/OneclickrecoveryV0.4/Superuser-3.0.7-efghi-signed.zip /sdcard/
See #5.
14.
Code:
./adb reboot
Wait while the Transformer reboots.
15. Now please shut down the Transformer manually and boot into recovery. Please hold Power + Volume Down buttons and next confirm with Volume Up button when asked. Rogue XM recovery will boot.
16. Wipe cache, wipe Dalvik cache, next choose Install zip file from internal storage and choose the Superuser-3.0.7-efghi-signed.zip.
17. When it's done, reboot.
18. PROFIT. :good: Your device is rooted with Rogue XM recovery installed.
From there I suggest to install SuperSU and eventually SuperSU Pro as it seems to work better than Superuser and Superuser Elite respectively. You can eventually get rid of Superuser if you wish so, instructions available in this forum thread. As I own both SuperSU Pro and Superuser Elite, I've installed SuperSU and upgraded Superuser, just in case of. You should not mix them, though, thus I've revoked the root permission of Superuser.
Next I've installed Busybox. I don't know if it's the best version for TF101, works well on my GNote.
Finally, let's play with the recovery options courtesy of some awesome developers. :good: We can choose among Rogue XM Touch, CWM classic, CWM 6.x and official or modified TWRP. I've chosen the official TWRP with GooManager.
Next stop, Titanium Backup.
Should you have other recommendations, please do not hesitate.
Click to expand...
Click to collapse
Thanks, that worked nicely for me!
One thing I can't figure out yet, though, is how to do a backup - the microsd card doesn't mount at /sdcard/ and backing up to internal storage is not recommended...
Wheelie
Hi!
A linux only solution for B70(+) devices can be found here:
http://androidroot.mobi/2012/05/27/introducing-wheelie-nvflash-for-asus-transformer-tf101-b70/
It is what I used twice so far. Works as it should.
I do not claim credit for anything! I just stumbled upon the solution.
Problem rooting
Hi,
this is my first post on XDA.
After a lot of readings here, I think I have tried everything I could, but my knowledge in rooting is too limited to understand these bugs:
At first, when I tried running these lines on the terminal, I couldn't push the files to /data/local: permission denied.
Then, I tried pushing to /sdcard/ and it worked.
But the next error I get is when linking:
"link failed Function not implemented"
Can you help me please?
My computer is a Mac, so I have tried you method first. I also tried on my Parallel Desktop with Windows 8 and on the PC with Windows 8.1 of my girlfriend, with RootDebugFs.
Here is the description of my Infinity pad:
model: ASUS Transformer Pad TF700T
Android: 4.2.1
Kernel: 3.1.10-g9827b9a, [email protected] #1
Build: JOP40D.WW_epad-10.6.1.14.8
I had the build 14.10 but I found that I should downgrade to 14.8, so I did, but nothing changed.
I also unlocked my tablet by mistake, thinking it would help rooting.
Thanks for your help.
Best,
Yohan.
Just did this!!! Still works!!! Followed your steps. Now the recovery is TWRP 2.5!!! As the peri version changed I checked if the .bat was still doing the same things, and it is!!
Thanks for your tuto! Saved me some time installing W**** ...