Database Info

Android Browser build that AutoRotates

Here's a recompiled version of the Browser that supports auto rotate.
Here's the download location for the Browser.apk:
http://www.koushikdutta.com/2008/12/auto-rotate-for-android-browser.html
Run the following from the command prompt to install the new Browser:
Installation Instructions:
adb remount
adb shell rm /system/app/Browser.odex
adb push Browser.apk /system/app/Browser.apk
Now start up the Browser.
You may not have a Browser.odex depending on your phone model.
The change, as I mentioned before, is really trivial. In the BrowserActivity.onCreate, I did the following:
// the next line is the original code
// setRequestedOrientation(mSettings.getOrientation());
// make it use the sensor for orientation instead.
setRequestedOrientation(ActivityInfo.SCREEN_ORIENTATION_SENSOR);
To restore the original Browser, flash RC30 again.

Koush, thanks so much! I have been waiting for this!

i can't get it to install and now the browser don't work and i can't install the back up

I'm getting no space available when pushing the browser.apk
JF rc30 v1.2

kron2 said:
i can't get it to install and now the browser don't work and i can't install the back up
Click to expand...
Click to collapse
You can't get it to install? Could you be more specific?

saul972 said:
I'm getting no space available when pushing the browser.apk
JF rc30 v1.2
Click to expand...
Click to collapse
Your /system partition ran out of room. Is there something you can delete from there? I've seen this before as well on some of my company's phones; I usually end up deleting some ringtones or other junk files.

took a couple of tries but installed now...thanks!
fyi i rebooted phone to initially install the new Browser. I first got errors w/o rebooting so that may fix the problem

I had the same problems with the new browser crashing and then being told that the file couldnt be copied due to lack of space,
Easiest fix is to just reinstall rc30 or rc8 and install the patched browser again.
Worked fine after that

Koush said:
Your /system partition ran out of room. Is there something you can delete from there? I've seen this before as well on some of my company's phones; I usually end up deleting some ringtones or other junk files.
Click to expand...
Click to collapse
Not sure.
Here's the message
failed to copy 'Browser.apk' to 'system/app/Browser.apk' : no space left on device

SGTDavePwnage said:
I had the same problems with the new browser crashing and then being told that the file couldnt be copied due to lack of space,
Easiest fix is to just reinstall rc30 or rc8 and install the patched browser again.
Worked fine after that
Click to expand...
Click to collapse
Will I need to start the process again?

saul972 said:
Will I need to start the process again?
Click to expand...
Click to collapse
Its basically telling you that it cant copy the file because of lack of space withing the system partition.
As koush advises, if you know how to clear space that will fix the problem.
If you dont know how to remove things and are a bit unsure of what to do, reinstalling the modified rc30 / rc8 will reset the system partition back to its defaults.
Once your back and set to default you can try to install again if you want

I'm assuming this is for those who have root access only?
If so, it would be nice to state that when posting these mods.

Henchman said:
I'm assuming this is for those who have root access only?
If so, it would be nice to state that when posting these mods.
Click to expand...
Click to collapse
Yes this requires root access,
I can see what you are saying about perhaps specifying in the post when something requires root access, but when you look at the instructions in this case its quite obvious that this one does require root.
PS.... Cheers for the upload Koush

SGTDavePwnage said:
Yes this requires root access,
I can see what you are saying about perhaps specifying in the post when something requires root access, but when you look at the instructions in this case its quite obvious that this one does require root.
PS.... Cheers for the upload Koush
Click to expand...
Click to collapse
Obviouse to em...
But probably not to everyone.
And you know the old saying. When you Assume...

where do i put Browser.apk to install it on the sd card and if so how do i use adb to see it or do i push it from like c:\browser.apk \system\app\browser.apk

SGTDavePwnage said:
Its basically telling you that it cant copy the file because of lack of space withing the system partition.
As koush advises, if you know how to clear space that will fix the problem.
If you dont know how to remove things and are a bit unsure of what to do, reinstalling the modified rc30 / rc8 will reset the system partition back to its defaults.
Once your back and set to default you can try to install again if you want
Click to expand...
Click to collapse
Finally got it!!! Thanks for your help

kron2 said:
where do i put Browser.apk to install it on the sd card and if so how do i use adb to see it or do i push it from like c:\browser.apk \system\app\browser.apk
Click to expand...
Click to collapse
Place it in the tools folder of the SDK folder on your PC

thx joshoowa i installed it finally i did have it in the tool folder but would not install but after several tries it did i was starting to think i was installing it wrong

I've deleted most of my .ogg audio related tones in the /media/audio folder but i still get no space left. what else can i delete?
btw i'm using adb shell rm /xxx/xxx/xxx/xx.ogg to delete. is that right?

Hey Hey!!!...
Had to free up some room, but it works great..
Thanks..

Apps to SD card app

Hey all,
I know I just put up my tutorial on how to do this but hopefully this will make things easier for everyone. I'd still suggest doing a nandroid backup first just to make sure but I tested this on my phone so it should work. Just run the app and if this is the first time moving your apps to your sd card(and you want to keep the ones you have) leave the checkbox checked. Otherwise uncheck it. Then just press the buttons that correspond to what you want to do. Enjoy
In order to use this you MUST:
1: Have an apps-to-sd ROM
2: Have your sd card partitioned correctly with FAT32 first and ext2 second.
3: Have busybox already installed to /system/xbin
NOTE: I'll try to help as much as I can but I can't take responsibility for anything this does to your phone. I'm pretty sure nothing bad will happen and nothing irreparable can happen but gotta say these things just to be sure anytime I'm messing with root permissions.
ANOTHER NOTE: I'll put this up in the market for $1. It'll remain free here but people can donate to me that way.
YET ANOTHER NOTE: I've managed to get a new method working that's a lot more stable and flexible. I will keep this thread here but won't be maintaining it.
EDIT: Moving data is too unstable, I've removed the option. It doesn't force close anymore when you don't have the setup right, it just gives an error and wont let you do anything, so that's better.

Tried it this morning and worked great. You might add a pop up at the end of moving apps to restart the device. When less experienced people use it, they won't know to do that I'm afraid.

the app sends me into abootloop at the htc screen
ps
i tried from fresh wipe and sd

Nismo300zx said:
the app sends me into abootloop at the htc screen
ps
i tried from fresh wipe and sd
Click to expand...
Click to collapse
OH SHOOT!!! I fixed this problem on the market one but forgot to put it back up on here. Umm... for now no1 should use the one posted here, until I can get home and post the updated one. OR if you still want to fix this and don't much just a bit of fiddling in the recovery terminal, after moving apps to sd, restart in recovery mode and do this:
Code:
mount data
ln -s /system/sd/app /data/app
For anyone who cares about such things, the problem is that it deletes the /data/app folder and then makes a symlink, which sounds ok, except that every super user command has to be run through the whitelist app... which no longer exists. So it's not able to set up the link and all hell breaks loose.

i did use the 1 from here
it says ln: /data/app: file exists

if i already had apps2sd, tried to upgrade my phone from 5.0 to 5.01G, so I wiped...then data.img wouldn't flash over...if i do this, will my apps show up again?

Nismo300zx said:
i did use the 1 from here
Click to expand...
Click to collapse
ya it's the one from here that's broken, sorry. If you haven't already flashed back and everything(still have the boot loop) then you can use the code I posted and it should fix it. I'll post the updated version tonight when I get back home.

AbsoluteDesignz said:
if i already had apps2sd, tried to upgrade my phone from 5.0 to 5.01G, so I wiped...then data.img wouldn't flash over...if i do this, will my apps show up again?
Click to expand...
Click to collapse
Yes, just uncheck the checkbox. But you might want to read the note that I just posted, there's a known problem with it that has a fix but requires going into the recovery terminal. I'll post the updated version of this app that doesn't have that bug tonight.

jus tried and nothing ..now im stuck at tmobile g1 screen..im startin to think it just dnt like me

Nismo300zx said:
jus tried and nothing ..now im stuck at tmobile g1 screen..im startin to think it just dnt like me
Click to expand...
Click to collapse
Try reading a few of the posts above yours.

ThaBadBoy said:
Try reading a few of the posts above yours.
Click to expand...
Click to collapse
i been at this for 2days ive tried evrythin ..hmm time to give up soon

Nismo300zx said:
i been at this for 2days ive tried evrythin ..hmm time to give up soon
Click to expand...
Click to collapse
Not really,,
According to the like 6th post or something its states this app wont work if you download it from here, but if you were to get it through the market....
Bob should now be your uncle
if you give him some time as clearly posted again, he will fix the app from the first post and replace it later on

Dantehman said:
Not really,,
According to the like 6th post or something its states this app wont work if you download it from here, but if you were to get it through the market....
Bob should now be your uncle
if you give him some time as clearly posted again, he will fix the app from the first post and replace it later on
Click to expand...
Click to collapse
ok if i typed the commands in manually and it wnt work ..and the app wnt work ..im tired of wipin the fone and formattin the sd card...=[ i give up

Nismo300zx said:
ok if i typed the commands in manually and it wnt work ..and the app wnt work ..im tired of wipin the fone and formattin the sd card...=[ i give up
Click to expand...
Click to collapse
you had the "stale NFS handle" right? I'm not really sure what's going on but something in your phone's file system sounds like it went screwy. Maybe someone like JF or LucidREM could help? Your problem goes way over my head and I'm guessing the same is true of a lot of people on here unfortunately.

its cool imma jus stay with apps n caches to sd...n kep dalvik on the fone..i got passed the nfs error and get stuck at tmo g1 screen maybe ill try again l8ter

jf rom
Ok question I know it says apps to sd rom is needed does this mean only haykuro roms? I have a jfrc33 1.42 and I could do apps to sd using this rom (planning on doing it tonight my 8gig class 6 card arrived) so my question is can I just use this app or do I need to do all the steps manually

jjjackson56 said:
Ok question I know it says apps to sd rom is needed does this mean only haykuro roms? I have a jfrc33 1.42 and I could do apps to sd using this rom (planning on doing it tonight my 8gig class 6 card arrived) so my question is can I just use this app or do I need to do all the steps manually
Click to expand...
Click to collapse
It should work on any apps to sd ROM. This includes LucidREM's modified JF ROMs. If you're gonna be manually changing it into an apps to sd, then I would think it would work but can't promise it. I wasn't able to figure that out when I tried so I'm not 100% sure that they work the same but I would imagine they would. Again, though, the one posted here has that known bug which will be fixed after I get home from work.
Short answer(s):
Haykuro's ROM: definitely works
LucidREM ROM: Don't have it to test it but almost assuredly works
Self-modified: probably works?

Sounds good I wasn't doing it till later tonight anyways (stuck at work also) also is it still a good idea to keep ext2 parititon less then 2gb like lucid reported on his tutorial

jjjackson56 said:
Sounds good I wasn't doing it till later tonight anyways (stuck at work also) also is it still a good idea to keep ext2 parititon less then 2gb like lucid reported on his tutorial
Click to expand...
Click to collapse
Probably, I haven't tried anything bigger... and seriously, you'd need a crazy amount of apps to fill up even 1GB...

[email protected] said:
Probably, I haven't tried anything bigger... and seriously, you'd need a crazy amount of apps to fill up even 1GB...
Click to expand...
Click to collapse
True. that sure would be a lot I dont even think all the apps in the market would fill 2gigs lol. Thanks for your work look forward to trying it later

[WIP-Tutorial] Installing AOSP apps in your favorite ROM

Myself and apparently many others like the AOSP apps better than the sense apps. I find the interface for the AOSP messaging, calendar, browser, calculator, and dialer/contacts applications to be more attractive and in some cases more usable. I really liked Bugless Beast 0.4 since it featured these applications, but I have had a hard time with the bug that keeps disk drive from working, and there are various reports of some syncing and battery issues. The EVO-NonSense series has been great too, but I use HDMI out sometimes and like having some of the sense stuff installed. Big thanks to both BuglessPete and tjohnsonjr for their AOSP work.
(7/18/2010) I have attached some of the files I have been using, see descriptions at the bottom of the post.
So since it took a little digging for me to figure out how to do this (even though to advanced users this is easy) I thought it might come in handy for other new users. Additionally I'm hoping by posting this someone can help me figure out how to get the dialer/contacts stuff working, I have the others working fine.
I've done the below on DamageControl, and I think another (baked snack maybe, can't remember). I'll probably throw together an update.zip that can patch these in place later, but I'd rather get the dialer/contacts part figure out first.
Setup:
1. You will need a fully rooted (toast root part 2, NAND unlocked) phone, and adb up and running. There are several explanations for both parts, but the ones listed in the "useful threads" sticky are joeykrim's for adb and toast's part 1 and part 2 for root.
2. I have been using the apk's from BuglessPete's bugless beast 0.4 ROM. The thread for it is available here.
Once you unzip the file, you will find the needed apks in the /system/app folder.
Note: Please donate to pete, he doesn't even have an EVO yet and is doing some great work. Hopefully if he has a phone to work on he can get some of these small bugs squashed and keep the development for BB going.
3. Backup your phone. If you don't know how to reboot into recovery and restore from a nandroid backup, you do not want to do this yet, especially if you want to try help me figure out how to get the dialer running. The idea with the dialer is to try different things until something works. In all likelihood you will hit a point where things are FCing so much you can't do anything. You will almost certainly need to restore from a Nandroid backup at some point.
Important: More than likely anything I list here can't break a phone in a way that a nandroid restore won't fix, but I can not and will not be accountable for any problems with your phone.
Which files:
One nice thing about adding files this way is you can pick and choose what to use. If you like the stock messaging but want the AOSP calendar, you can do just that.
Calculator: Calculator.apk
Calendar: CalendarProvider.apk and Calendar.apk
Default "Navigator" application: CarDock.apk <- you can keep both
Internet: Browser.apk and HTMLViewer.apk <- doesn't show previews of each tab, but allows up to 8 instead of 4. There may be other functionality gained or lost, I dunno.
Clock: DeskClock.apk (can exist beside HTC clock, and can be installed without this procedure)
Messaging (SMS, Text): Mms.apk <- Many people have trouble with this one.
####### Not Working! See post #2 ########
# Phone: Phone.apk, ContactsProvider.apk, Contacts.apk
###################################
To install:
I think you can use adb to do this install with the files still on the computer, but I go ahead and throw all the needed apks onto my sdcard, typically in a folder. Also, if you need to be in the Android SDK's /tools directory to use adb (this depends on your configuration) do that. Connect your phone, and make sure it is in "Charge Only" so the sdcard stays mounted. To make sure adb sees the phone properly issue:
Code:
adb devices
and you should get a return listing the device ID. If so we will mount the /system partition as read-write:
Code:
adb remount
Log into the phones local shell:
Code:
adb shell
you are now on the phones command line and file system, not on your local machine. Now we can start installing files. I'll use Calculator in this example, and I have the apk in a folder on the sdcard called AOSP_apks:
Code:
install /sdcard/AOSP_apks/Calculator.apk /system/app
You can do a couple at a time, and you must do more than one at a time when installing a provider like CalendarProvider.apk and Calendar.apk.
Once you are done, exit the phone's shell, and reboot the phone:
Code:
exit
adb reboot
The change may show up immediately, but the phone and applications aren't designed to change these core functions on the fly, so make sure to reboot the phone. Once it reboots you will probably notice the AOSP icon has replaced the former, and you have the AOSP skin and/or functionality.
Post #2 will deal with progress so far on the dialer/contacts.
(added 7/17) Notes on different apks: The BB Launcher2.apk has his skin on the google search widget, or grab the apk from something else like DC for stock. Launcher.apk from BB is the one with the wide drawer and (I think) 9 screens.
Music.apk from DC is the modded music app from Cyanogen. It has some very nice UI tweaks.
Attached:
- Music.apk used in Cyanogenmod from DC
- Calendar, CalendarProvider, Browser and HTMLViewer from BB 0.4
- CarDock, Calculator, and MMS from AOSP EVO-NonSense

Contacts/Dialer Progress: I'm sure some of the more advanced developers know the answer to this, so ideally someone can fill me in. In the meantime I'll report my findings here, and if others can add feedback to the thread on what they have done, I'll update this post. Hopefully in the long run there will be a straightforward explanation for this I can add to the above post.
I have installed the three files listed above (ContactsProvider.apk, Contacts.apk, and Phone.apk) which seems to install the right bits, but I get FCs.
Later on I added Telephony.apk and FutureDialService.apk, which didn't improve anything. Finally I noticed that Bugless Beast didn't have HTCDialer.apk, so I removed that as well. I think this was the point things went from the dialer and contacts applications FCing to non-stop FCs that kept me from doing anything on the phone.
Attached are the three apps I'm sure are involved for the Contacts/Dialer, pulled from tjohnsonjr's AOSP EVO. More files may be needed, but I'm still trying to figure out which.

The Dialer/Contacts apk used to work, I believe on ROMs that are not based off the newest OTA. Since it worked for me, but stopped once I started using ROMs based of the newest OTA. Anyways great post.

I installed the files and I cant see them. They're in the folders but its like they're hidden from the OS.

I tried to do this before since I love BB but the wake bug in v4 was killing me. I always got install errors. Did you delete the Mms.apk first.. THEN install Mms.apk and reboot? Or did you just install over it? I got errors either way. Also it totally disabled texting on my phone even after reinstalling the HTC Mms.apk.
I had to clean cache/reset then reflash my Nand backup and even then my texting was still broken until I sent one to my wife and then magically I got the 10-15 test "texts" I had sent.

RikusHaven said:
The Dialer/Contacts apk used to work, I believe on ROMs that are not based off the newest OTA. Since it worked for me, but stopped once I started using ROMs based of the newest OTA. Anyways great post.
Click to expand...
Click to collapse
Thanks and thanks. This is interesting. Of course BB is based on the older ROM, so maybe that is why BB works but this doesn't. I'll have to grab an older ROM and try that. It may be an issue of grabbing a newer build of the dialer or something.
warmachine69 said:
I installed the files and I cant see them. They're in the folders but its like they're hidden from the OS.
Click to expand...
Click to collapse
Did it overwrite the existing files? Or do you totally not have whatever you installed, AOSP or sense? Which ROM and version?
MikeBrWade said:
I tried to do this before since I love BB but the wake bug in v4 was killing me. I always got install errors. Did you delete the Mms.apk first.. THEN install Mms.apk and reboot? Or did you just install over it? I got errors either way. Also it totally disabled texting on my phone even after reinstalling the HTC Mms.apk.
I had to clean cache/reset then reflash my Nand backup and even then my texting was still broken until I sent one to my wife and then magically I got the 10-15 test "texts" I had sent.
Click to expand...
Click to collapse
Were you able to successfully do the adb remount first? The way I did it just overwrote the existing Mms.apk.
Also what ROM and version are you running?

laydros said:
Thanks and thanks. This is interesting. Of course BB is based on the older ROM, so maybe that is why BB works but this doesn't. I'll have to grab an older ROM and try that. It may be an issue of grabbing a newer build of the dialer or something.
Did it overwrite the existing files? Or do you totally not have whatever you installed, AOSP or sense? Which ROM and version?
Were you able to successfully do the adb remount first? The way I did it just overwrote the existing Mms.apk.
Also what ROM and version are you running?
Click to expand...
Click to collapse
BBv3 and yes the remount worked.. I am currently in my 84th hour of a long battery duration test so I can't plug it in and try it right now since it will wipe my stats. However it would give some "parse" error and then fail to install. If I forced it by just cp'ing the apk and chmod'ing the exec permissions it would fail horribly.

84th hour of a battery duration test? details please?

MikeBrWade said:
BBv3 and yes the remount worked.. I am currently in my 84th hour of a long battery duration test so I can't plug it in and try it right now since it will wipe my stats. However it would give some "parse" error and then fail to install. If I forced it by just cp'ing the apk and chmod'ing the exec permissions it would fail horribly.
Click to expand...
Click to collapse
Was it something like
Code:
Failure [INSTALL_PARSE_FAILED_UNEXPECTED_EXCEPTION]
If so, I had the same error when I didn't have the /system partition fully mounted as read-write. Did you get any errors from the "adb remount" command?

davebu said:
84th hour of a battery duration test? details please?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=7154719&postcount=993
This is my post talking about it.. I am on hour ~91 of the test.. still running with 8% battery left... BBv3 rocks!

laydros said:
Was it something like
Code:
Failure [INSTALL_PARSE_FAILED_UNEXPECTED_EXCEPTION]
If so, I had the same error when I didn't have the /system partition fully mounted as read-write. Did you get any errors from the "adb remount" command?
Click to expand...
Click to collapse
Hmmm maybe I did and didn't notice it.. I am down to 8% right now so by mid day my battery will probably die. I am hoping to make the 100Hr on one charge mark, after that I will try again and note any errors.

MikeBrWade said:
Hmmm maybe I did and didn't notice it.. I am down to 8% right now so by mid day my battery will probably die. I am hoping to make the 100Hr on one charge mark, after that I will try again and note any errors.
Click to expand...
Click to collapse
ok so I just redid your steps and I didn't get the error code this time (maybe my remount didn't work the last time I tried it). But now I get FC everytime I try and launch the text app. I installed over the Htc mms.apk =(
Anyone got an HTC Mms.apk handy they can post so I don't have to restore nand?

If you have the AOSP apps available, could you please post them all in .zip folder in the OP?

MikeBrWade said:
ok so I just redid your steps and I didn't get the error code this time (maybe my remount didn't work the last time I tried it). But now I get FC everytime I try and launch the text app. I installed over the Htc mms.apk =(
Anyone got an HTC Mms.apk handy they can post so I don't have to restore nand?
Click to expand...
Click to collapse
NVM I extracted it from an old nand backup. So, for me at least the Mms.apk from AOSP causes FCs and won't run at all . Put the HTC Mms.apk back and it works fine. =( Urgh any hints?
edited to add the HTC Mms.apk incase someone does what I did and kills it, so they dont' have to go through the process of trying to extract it.

MikeBrWade said:
NVM I extracted it from an old nand backup. So, for me at least the Mms.apk from AOSP causes FCs and won't. Put the HTC Mms.apk back and it works fine. =( Urgh any hints?
edited to add the HTC Mms.apk incase someone does what I did and kills it, so they dont' have to go through the process of trying to extract it.
Click to expand...
Click to collapse
The only issues I've had with the AOSP Mms.apk was the lack of actual mms functionality.
thanks for the apk so I could go back

I[E said:
The only issues I've had with the AOSP Mms.apk was the lack of actual mms functionality.
thanks for the apk so I could go back
Click to expand...
Click to collapse
Interesting that you say that, since I had some MMS texts in my cache. Wondering if when the AOSP version couldn't deal with them so it just FC'ed instead.
So I tried that, deleting ALL my texts so it wouldn't have some MMS collision or something. But that didn't work either, HTC Mms.apk works fine.. the AOSP.apk FC's. Could the OP or something with a working AOSP Mms.apk post it maybe it's my copy. Mine has an MD5 of : 441e3b8863bc3ab88ce6ad9bc1671f22

I have mms messages in my cache too. The AOSP apk shows them fine, just can't send new mms messages. Maybe your file is corrupt?
Sent from my PC36100 using XDA App

I going to upload all the AOSP apks that I include in my ROMs when I get home tonight.

Can you tell us how you got contacts.apk to work? I'm trying with FreshRom and I pulled the Contacts.apk from your Rom and it won't recognize the file when I push it using adbshell. The file is in the app folder but android ignores it.

I[E said:
I have mms messages in my cache too. The AOSP apk shows them fine, just can't send new mms messages. Maybe your file is corrupt?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Does does your md5 match mine?

[Q] Removing CDFS partition without rooting?

Is it possible to remove the CDFS partition (Verizon Mobile) without rooting the phone?
It is the company's phone, so no rooting for me but I would love to be able to use the TB as a USB stick on my JVC KD-AVX77 in the car. Right now it doesn't see any music and I suspect that's because of that CDFS partition.
Any help would be appreciated.
Thanks.

I'd like to know this as well...

Bumping this up. Even if it requires root, would still like to know how to do it period, as I can't seem to find any info anywhere.

you have to delete a file and you need to be rooted to do so because it is a system file.
/system/etc/cdrom.iso is the file that needs to be deleted

magneticzero said:
you have to delete a file and you need to be rooted to do so because it is a system file.
/system/etc/cdrom.iso is the file that needs to be deleted
Click to expand...
Click to collapse
Awesome, thanks!

magneticzero said:
you have to delete a file and you need to be rooted to do so because it is a system file.
/system/etc/cdrom.iso is the file that needs to be deleted
Click to expand...
Click to collapse
How big is the file "cdrom.iso"?

bignew67 said:
How big is the file "cdrom.iso"?
Click to expand...
Click to collapse
I dont recall offhand...it isnt that big....more annoying than how big it is

The ISO is only about 6mb. However, after removing it, the CD drive still shows up when connected, just with no data. Any thoughts, or is this something a kernel dev/CM7(lol down with Sense!) is going to have to take care of?

In the programming menu the option was removed. Take the Incredible for instance, you could disable it, but not so on the TB for now. Unless someone figures out a way to change it Im out of ideas, but removing it worked for me.

magneticzero said:
In the programming menu the option was removed. Take the Incredible for instance, you could disable it, but not so on the TB for now. Unless someone figures out a way to change it Im out of ideas, but removing it worked for me.
Click to expand...
Click to collapse
Well at least removing it gets rid of the autorun prompt. Good enough for now, and I'm sure the CM team will figure it out.

Root here. Didn't work for me. I can't mount my sd card through my phone after deleting that file.
I did flash adrenalyn's 1.9 kernal some days before which may be the cause of my having a different result from others in this thread however I think it's a good idea to DO A NANDROID BACKUP BEFORE ATTEMPTING!
or at least rename the file with a .old or .bak extension, whatever ya like... luckily I have the backup from before the kernal flash
would logcat be able to track down what's being accessed while the phone is mounting volumes while enabling disk mode?

Rather than removing it, I replaced it with an ISO of my own that has the Tether for Android setup exe and dmg, and a few other misc files I might need

[Q] "Lost root" after busybox upgrade - Cannot r/w to / !

[Hopefully I didn't miss this being covered somewhere else, as I am much the same as many of you and get beyond irritated with endless repeat questions. I searched using the best keywords I could think of for the issue, but to no avail. Apologies in advance if this has been covered!]
Alrighty. I've got a TF101, rooted it myself (thank you XDA), running 8.6.5.1.9 i believe, stock rom just with root. Used nvflash and Razorclaw. Worked like a charm.
It's been fine for the last 6 months, no issues. However, I decided to update busybox using its internal updater as I have before with no problems. I noticed I accidentally told it to install to /system/bin instead of /system/xbin, and the only reason I even knew about that was due to having to configure an app to find busybox in /xbin instead of /bin.
Now there's a problem. I can still access the internal virtual sd card, but that's about it. The device can't seem to read or write to the main directory (although it can deal with going DIRECTLY to /mnt/sdcard). Ghost commander can't view the main directory, but ESFile explorer _can_, although root browsing in ESFile Explorer is UNchecked. It shouldn't be able to do what it's doing, and it's only doing it in one of two apps.
As a result, I've got no access to any root apps obviousy, but the wifi is having issues as well, it tries connecting but it can't complete the connection.
I'm toying with just wiping and flashing a new rom entirely, but figured I'd ask before I jump in the deep end of things. I keep backups of stuff, but it's still such a pain in the ass reinstalling things.
Any suggestions? I have a feeling it's something "simple", a link file or ... something which linux gurus would know about and I would not, not being a guru or disciple myself.
Thanks in advance!

If only you have working CWM installed. You could just flash this Superuser3.0.7.

Ah, but the plot thickens. I had superuser on there. I even uninstalled and reinstalled it. No dice.
Update: I said fuggit and did a factory reset. However, my wifi is still not fully connecting to my network although it has no problem finding it. I don't have a recovery image on the external SD and unless i get the network working, will have to wait until tomorrow to get a working microsd->usb adapter to put it on there.
I CAN still get into CWM, thank god.
Current rom is stock 8.6.6.19
Razorclaw gives an error when trying to root.
Also, when trying to moust USB from the recovery menu. it fails, saying "E:unable to upen ums lunfile (no such file or directory).
I am hoping this will magically get fixed after re-installing stock from the SD card ... and that my device isn't somehow crippled.
Sorry for the massive details, but more data = better.

It will magically get fixed
I recommend you flash any Totally stock ota. Then upgrade to the latest OTA, then use my tool PERI (or another) to install recovery and root. Then you should be all fixed up.

Well, it looks like I did get things back on track, but oddly enough, neither of the standard OR modified for root stock ROMs would work. One just wouldn't install, another failed halfway through. MD5s checked out and everything. I had put Revolver 4 beta on there sort of as a "just in case", and that one installed fine (and I was pleased when it displayed "installing Busybox symlinks").
Phew. CLose close call. Now to deal with the bull**** of setting stuff back up again.
However, the question remains: I'm assuming this whole thing happened because of the busybox update and me accidentally installing it to /bin instead of /xbin, and I think it "cleaned up" its own symlinks or something.
I'm not saying don't update your busybox, although I'm sticking with what works and **** upgrading anymore, just be careful...
Thanks for the help!

Recently I used the busybox installer to update my busybox version and it went through great... but after reboot it reverted back to the old version.. And I never touch it since.. don't want to take the hassle further..

There are certain 'plague' versions of busybox that simply don't work. I'd find that list of working BBs and STICK with one that's good. I'm still on 1.63 or someat like that.

Mangraa said:
[Hopefully I didn't miss this being covered somewhere else, as I am much the same as many of you and get beyond irritated with endless repeat questions. I searched using the best keywords I could think of for the issue, but to no avail. Apologies in advance if this has been covered!]
Alrighty. I've got a TF101, rooted it myself (thank you XDA), running 8.6.5.1.9 i believe, stock rom just with root. Used nvflash and Razorclaw. Worked like a charm.
It's been fine for the last 6 months, no issues. However, I decided to update busybox using its internal updater as I have before with no problems. I noticed I accidentally told it to install to /system/bin instead of /system/xbin, and the only reason I even knew about that was due to having to configure an app to find busybox in /xbin instead of /bin.
Now there's a problem. I can still access the internal virtual sd card, but that's about it. The device can't seem to read or write to the main directory (although it can deal with going DIRECTLY to /mnt/sdcard). Ghost commander can't view the main directory, but ESFile explorer _can_, although root browsing in ESFile Explorer is UNchecked. It shouldn't be able to do what it's doing, and it's only doing it in one of two apps.
As a result, I've got no access to any root apps obviousy, but the wifi is having issues as well, it tries connecting but it can't complete the connection.
I'm toying with just wiping and flashing a new rom entirely, but figured I'd ask before I jump in the deep end of things. I keep backups of stuff, but it's still such a pain in the ass reinstalling things.
Any suggestions? I have a feeling it's something "simple", a link file or ... something which linux gurus would know about and I would not, not being a guru or disciple myself.
Thanks in advance!
Click to expand...
Click to collapse
You may have been hit with a bug I introduced.
There was a bug with version 8.0 of my application.
There is not an issue with Busybox V1.20.1.
I apologize for this bug, the application symlinked all applets to Busybox and on some devices there are applets which are unique to the device and should not be replaced by those offered by Busybox.
A simple way to fix this is to simply reflash your rom. You do not need to wipe or clear any data. This will fix the issue and you can update Busybox normally with my application as long as it is version 8.1 or higher.
I apologize for the frustration I have caused, please let me know if I can do anything to help you further. I am trying to find people who were affected to see if I can help rectify the situation.

yeah me too
I guess I should have done a more recent backup. I tell you, there is a reason i have 38 updates waiting, everytime I start going through them, boom blows up in my face