A2SD view apps loaded in partition - Hero CDMA Q&A, Help & Troubleshooting

First post, hope I haven't picked the wrong place. I did search the forum before asking this.
Is there a way to see the A2SD partition, or to see the apps installed on it? I set mine rather low, at 512MB (that's what it asked for at default) and I figured that should be more than enough since I only have ~100MB or so on stock ROM.
So yeah, none of the market apps I have seen can show me the space being used or how much room is left free on the partition.
Any idears?

Quick System Info in the Market, will show you the total amount of mb being used and what is left for a2sd.

Connect to your phone via USB cable and enter the following in a command prompt (this of course assumes you have installed the android sdk):
adb remount
adb shell
ls /system/sd/app/
I got this from this post: "forum.xda-developers.com/showthread.php?t=603052"
just put the http tag in front of the above and cut and paste it into the browser address bar.

Thanks, to both of you. The Quick System Info App does the trick!

Related

How much free memory should I have after running taskiller?

I have task killer set to ignore two applications: Battery Widget and Weather Widget (donation version).
I've rooted my phone and am running Cyanogen 4.0.1 with Ted's hero theme. And I've formatted my SD to have FAT32, EXT3, and Linux Swap partitions and have my apps installed to my SD.
However, when I use taskiller to close all my applications I'm usually left with only 28 to 30 M free. Sometimes I'll only have 26 M or all the way up to 33 M left. Is this normal?
How much memory do you guys have left after you kill your tasks? Are my numbers low enough to make you think I've not partitioned my SD correctly or something else?
I feel like my phone should be much much faster than it was before I rooted it, but I don't see the huge improvements many people seem to.
Any help is appreciated.
yeah, I have questioned this too. I use Advanced Task Manager with 2 apps excluded. I usually am at 41 MB when all are ended. Prior to rooting this was in the 50's. I assume it is because the ROM has used some of this memory?
I also seem to have a lot less internal memory than others. I have 54MB when I go review my memory under settings. Not sure how others are in the 70-80 MB range. I clear cache frequently.
Also have 3 partitions 7.5GB/500MB/32MB
to the OP - have you deleted the cache of programs like browser, google maps?
I'm not sure how. I'd love to delete both of those and a few others (voice dialing I will never use you!!). I've gone into the apps manager but it won't let me uninstall them.
Yes, I'm a complete noob at this .
One thing I may have done wrong. I didn't reflash my cyanogen rom after formatting my SD. Could that be a problem?
Nagh, the rom would do it on the next reboot... go to menu... settings... sd card and phone storage. It should show all memory there (including second partition).
To delete cache, go to menu... settings... applications... app manager.
Click on browser, scroll down and delete cache. How much was there?
There wasn't much. It was like 1 to 1.5 megs, but it's gone now. I also set my gmail sync down to 1 day and cleared out it's data. Still though, my phone just feels like it's not getting the big speed upgrades others talk about.
I am hoping someone else will chime in on the low memory reported by task killer/manager in our cases.
How much internal memory were you showing under settings and removing cache?
You can sort the app manager by size too (of course the apps are on your sd card) but the cache is not.
I take it you confirmed your partitions were working?
They seem to be working. I've got 486 MB for my ext3 partition and only 413 available. I'm assuming 73 MB are being used by my programs.
I have 64 MB of internal phone storage available. I don't know what it was before.
I also have 5 desktops with a lot of icons on each one, plus I have a background that is about twice as wide as normal (1067x480 vs 640x480). Still the background is only 70k.
If you want to delete stock apps
Code:
adb remount
adb shell
cd system/app
ls
This will let you see the actual names of apps. From there you can just rm -r them as usual
example
Code:
rm -r VoiceDialer.apk
rm -r com.amazon.mp3.apk
rm -r VoiceSearch.apk
rm -r LatinIME.apk
Don't forget to clear your dalvik-cache after you done nuking stuff!!!
Code:
rm -r system/sd/dalvik-cache
mkdir system/sd/dalvik-cache
You can do all of this from terminal as well but adb make is much easier.
@ OP. I too have only 28-33MB of free ram after closing most of my widgets but I think it's pretty normal as too much free memory means too much wasted memory. And you will not see HUGE improvements in speed neither... there's only so much developers can do. What Cyan is trying to do is to introduce new features (global search, vpn, exchange) without bogging down the system (and doing a great job at it IMHO).
Good luck
^ that is an awesome post. Thank you for that.
Thanks a ton for that. Very helpful post. If I won't see any speed improvements by uninstalling apps I'll just pass on doing that.
Are there any ways I could see speed improvements beyond what Cyanogen already provides?
Limit the amount of desktops, and limit the use of widgets. Power wideget from donut seemed to use a lot of ram and slow things down a little.
why are you people confusing internal storage with system ram?
The information available under settings/sdcard-phone storage/available space reffers to the space available in the /data partition of your phone. Wether you have 1 or 100 (well, 89) mb free in this partition is irrelevant to your phone's performance. All that gets written to this partition is installed apps (not part of the system), dalvik-cache (for ADP or AOSP based roms that don't have their classes pre-compiled), and user data and settings.
People who have 70-89 mb free in that partition are using a2sd, data2sd, and cache to sd, which, imho, is a flippin waste because the internal nand is a lot faster than the bottlenecked bus for the sd card and it's just going to waste if you're not using it. Nothing, i repeat NOTHING is gained by having a free data partition (much like having free space in system which is never going to be used).
Your system has 192 mb of RAM, which is the actual working memory of the device, of those 192, only 90 are available to the dalvik VM, which is the Android part of your phone. This ram can be checked using "free" (if your build has busybox) at the terminal, and this will tell you how much ram is being used by the system, along with how much swap space (if you're using it) is being used. The used ram space fills up fast, and that's a good thing, because unused RAM is wasted RAM. Linux manages things and drops processes as required (to a swap file if available) to free up ram for processes that require it.
To keep your phone running smootly, I'd recomend a reboot every night (when you put your phone to charge). Android is full of memory leaks that have to be fixed, and until they're worked out, the 90 mb ram you have available is all you have to go with (unless you use swap, but one should never really consider that space memory anyway)
The biggest performance difference I've seen has been to shut down my battery widget. After I did that phone's responsiveness has been great.

Revert from Apps2SD with Apps intact?

Sorry if this has already been asked before, but searching through multiple pages of results using multiple search terms I was unable to find the answer that I was looking for.
Is there a way to revert from automatic Apps2SD with Cyanogen without losing my applications.
Would:
adb pull /system/sd/app app
adb pull /system/sd/app-private app-private
Before a full reformat of my SD card to a single partition work?
I'm looking to keep all of my data and settings if possible. If not, I'll probably just end up staying with Apps2SD.
cityeyes said:
Sorry if this has already been asked before, but searching through multiple pages of results using multiple search terms I was unable to find the answer that I was looking for.
Is there a way to revert from automatic Apps2SD with Cyanogen without losing my applications.
Would:
adb pull /system/sd/app app
adb pull /system/sd/app-private app-private
Before a full reformat of my SD card to a single partition work?
I'm looking to keep all of my data and settings if possible. If not, I'll probably just end up staying with Apps2SD.
Click to expand...
Click to collapse
make sure you also pull /data/data since thats what holds all the data and settings
in app and app-private are the actual apks
an adb pull of the app, app-private, and data/data folders should be all you need after you finish reformatting your card
you can just use a program like appmanager pro to back them up and then use backup for root users to copy the app data, then transfer them to your computer, wipe your sdcard to a single partion than reflash your rom so it drops apps2sd then transfer apps back to fresh format sdcard, install apps then use backup for root users
Your pull commands will be successful in backing up your apps to your computer, however, you will have to reinstall them one by one using Linda File Manager, or similar program to have access to the package installer feature. I would say use something Backup for root users or Atrackdog which allows you to bulk reinstall. If you have a lot of apps, reverting back to using the phone's internal memory is obviously gonna force you to pick and choose which apps you want to keep.
Ahh. Thanks for the clarification. I might just stick with Apps2SD instead of going through all of that. I thought that maybe there was a way to push the applications to the internal memory of the card in order to completely skip the whole "reinstallation phase". If I do end up doing it, I might go with the batch reinstall process.
I'm not having many problems with apps2sd, I just figured the small benefits that I'm getting don't outweigh the fact that my SD card is getting taxed in the process.
Thanks for all of the helpful responses!
sd cards are cheap, by the time you burn that card out, bigger and better ones will be cheap too
I'm shocked with all the helpfull info grid is putting out.
gridlock32404 said:
sd cards are cheap, by the time you burn that card out, bigger and better ones will be cheap too
Click to expand...
Click to collapse
Yeah that's true. I just had no scale as to how fast the cards burn out. Some people are saying they last years, some say they last only a few months.
I guess with the majority they last at least a year, which is absolutely fine by me. Thanks for all of the help!
i have had the same sdcard for over 2 years with no signs of damage or corupting
and once again preme, screw you

[HOWTO] Getting Hero To Run Fast

A lot of people have a tough time with Hero/Sense ROMs. I thought I'd make a guide on what I do to help others out. This is not definitive but it's my personal way of doing things. Comments, tips and suggestions are welcome here. I will update this with some more info as I go along.
I have a MT3G but this is the same for G1.
**Firerat has really comprehensive guides for A2SD and other tweaks. Please check his thread for more info. Also, his post about setcpu profiles is a must read.
First, get a ROM. I'm currently playing with KingKlick's Legend Port and Vegaman's kernel update.zip. This guide applies to any Hero ROM though.
Table of Contents / Overview
First things first
Get your task killers in order (TasKiller, AutoKiller, etc.)
MyBackup Pro or similar if you use them
Autostarts-- one of my favorites. Would love to hear about a free alternative
Droidwall-- free, blocks Internet to apps you choose
Reboot, wipe Dalvik-cache, reboot
Additional steps, Misc, Errata
FIRST:
Partition your SD card. I set a 256MB swap partition and have copious memory left over even under heavy load. EXT2 is better than 3/4.
Flash the ROM, flash the kernel update after. Boot the ROM, go through set up. I always skip signing in at this point as the setup is heavy on the CPU and wait for things to settle before the memory intensive sign in process begins.
SECOND:
Okay, now I see the home screen. Install TasKiller (free/paid) with ADB, MyBackup Pro and kill all the processes except Sense. I highly recommend Autostarts (paid). It handles not only autostart processes but also event listeners and will significantly speed up the ROM. Here are the services I disable:
"After Startup"
Download Manager
My Uploads
Network Location
PC Synchronization
HTC Message Uploader
Peep
HTC Media Uploader
Flickr/FaceBook/MySpace/etc
com.htc.socialnetwork.provider
HTC Widget Download Manager
MyBackup Pro (Uploads your location to their servers at every boot!!)
"Connectivity Changed"
My Uploads
Network Location Service
HTC Message Uploader
HTC Media Uploader
com.htc.socialnetwork.provider
"Application Installed"
PC Synchronization
Pico TTS (why would text-to-speech need to run...)
If you use Slacker.. disable it completely from all "Application Changed/Installed/Removed" categories. No need in them knowing your usage..
"Screen Off"
TasKiller
Notice how (and you can watch with logcat) when an application is modified or installed, it starts up Pico TTS (text-to-speech), synchronization, etc. This is not necessary and a memory hog. You might also be thinking "but I needz muh Facebook" but you don't need it to autostart. These services will load on demand as you use them. Without them, things go a lot quicker.
THIRD: (If you use MyBackup Pro)
Now, I sign into my account with Market, accept the terms and conditions. Once things have settled and I'm able to use the Market I exit the app immediately. I use MyBackup Pro to restore my apps. Version 3 now links apps to Market so they can be updated. Pretty slick despite the fact it logs your location to their servers without your permission. Luckily Autostarts stopped that. Now there's a small catch-- MyBackup messes up the Market database. Easy fix with ADB:
Code:
# cd /data/data/com.android.vending/databases
# ls -l
[I]I summarized the output here for formatting's sake..[/I]
----rwxr-x assets.db
-rw-rw---- billing.db
-rw-rw---- webview.db
-rw-rw---- webviewCache.db
See how assets.db is owned by root and the wrong permissions? This will FC Market 10/10 times. So:
Code:
# cp assets.db BACKUPassets.db
# cp -p billing.db assets.db
# cat BACKUPassets.db | tee assets.db
# rm BACKUPassets.db
Now it will work. The theory is that we can't chown the DB due to an "unknown user" but the other files there have the correct permissions. We use cat and tee to overwrite the clone with the correct contents. It's a hack that works perfectly.
FOURTH:
I then reboot and go to the Market. Install Droidwall (free) and set it to blacklist any app that doesn't need Internet Access. I also install AdFree (free). One site that it doesn't block is flurry.com. This site is used by a lot of applications such as MoreLocale. It uploads personally identifying information about you including your location, phone number, account info, etc. without your permission. I append it to my hosts file afterward. Note that each update with AdFree will erase that entry but I use Autostarts to disable it at boot and never update.
Code:
# mount -o remount,rw /dev/block/mtdblock3 /system
# echo "127.0.0.1 flurry.com" | tee -a /system/etc/hosts
# mount -o remount,ro /dev/block/mtdblock3 /system
FIFTH:
With all the apps now installed that I want to start out with, I go back to Autostarts and disable those I don't want (pretty much all of them). I reboot into recovery mode and wipe Dalvik cache. Reboot, wait for it to cache again and all is well.
Additional Steps
You can easily lock home into memory. *thanks speedysilwady and firerat. Here's how to set this permanently:
Code:
adb pull /init.rc
[I]replace "setprop ro.HOME_APP_MEM ..." with:
[B]setprop ro.HOME_APP_MEM 1536[/B]
[/I]adb push init.rc /sdcard/init.rc
adb shell
# mount -o remount,ro rootfs /
# cat /sdcard/init.rc | tee /init.rc
# mount -o remount,rw rootfs /
# rm /sdcard/init.rc
I will update this as I go. Any comments and tricks like reducing call delays are welcome. Again, this is just how I do things. Hope it helps.
Reserved for the updates....
Reserved for more updates. Just in case.
Don't bother getting kings version just get Vegaman's 0.3 version.
It works a treat and fast as well...
EDIT= and on Vegaman's use EXT2 not EXT4 like you have to do in kings roms. EXT2 is faster then EXT4
Awesome thread! you could also use AutoKiller and Cachemate to keep things smooth as well! =]
Updated OP. I'm looking for the prioritizer script that supposedly gets incoming calls within 1-2 rings... will update when I get it figured out. I have between 40-55MB free memory according to TasKiller when no apps are running.
deuse said:
Don't bother getting kings version just get Vegaman's 0.3 version.
It works a treat and fast as well...
EDIT= and on Vegaman's use EXT2 not EXT4 like you have to do in kings roms. EXT2 is faster then EXT4
Click to expand...
Click to collapse
I agree...and great job thread creater!!!
Interesting! I will try this, how much will the speed increase be?
With what I do, I barely get any slow downs unless I run a lot of apps but I have TasKiller's mini taskbar on one of my home screens and always clear things out before I do something like web browsing, Maps, or games to keep RAM clean.
I'd love an alternative to Autostarts that's free but it is truly great. Blocking listeners causes a huge boost in speed. You will see in logcat when you install an app that all these services start running in the background like Voice Dialer, TTS, etc. That's the reason installing apps seems to peg the phone for a few minutes. Not so when you block those background services.
enatefox said:
Updated OP. I'm looking for the prioritizer script that supposedly gets incoming calls within 1-2 rings... will update when I get it figured out. I have between 40-55MB free memory according to TasKiller when no apps are running.
Click to expand...
Click to collapse
Code:
su
setprop ro.HOME_APP_MEM 1536
this will keep home in memory. I learned that one from Firerat , should make calls come in faster
from what i understand a large swap like that might offer some positive temporary results, but after time clogs up
adelco93 said:
from what i understand a large swap like that might offer some positive temporary results, but after time clogs up
Click to expand...
Click to collapse
It's bad to have a large swap and high swappiness.
I haven't had any issues. The swap partition hasn't clogged up or even gone under 100MB left for me yet. Your mileage may vary but it's what I set it to. What size/swappiness would you recommend then? 96MB is not enough, 128MB seemed like too close to the edge of what I need.
I need to make the OP not look like crap...
It is better for the life of your sdcard to have a large swap....because if you allocate say only 64mb to swap...those blocks on your sdcard are constantly being written/read and the rest isn't....better to have a swap of say 256mb so that you are evening out the stress on the blocks more.
I think Wes G or Chris S said this....but that's my paraphrase of it.
Also no difference in speed between a 32mb swap and a 256mb swap. Just depends on your sdcard's class.
enatefox said:
I haven't had any issues. The swap partition hasn't clogged up or even gone under 100MB left for me yet. Your mileage may vary but it's what I set it to. What size/swappiness would you recommend then? 96MB is not enough, 128MB seemed like too close to the edge of what I need.
I need to make the OP not look like crap...
Click to expand...
Click to collapse
60 at most 80 or 100 is to much
G1ForFun said:
Also no difference in speed between a 32mb swap and a 256mb swap. Just depends on your sdcard's class.
Click to expand...
Click to collapse
If we were talking about computers then swap would be same size as ram, it's better to have no swap at all then to have one
Read some of this:
https://help.ubuntu.com/community/SwapFaq
G1ForFun said:
It is better for the life of your sdcard to have a large swap....because if you allocate say only 64mb to swap...those blocks on your sdcard are constantly being written/read and the rest isn't....better to have a swap of say 256mb so that you are evening out the stress on the blocks more.
I think Wes G or Chris S said this....but that's my paraphrase of it.
Also no difference in speed between a 32mb swap and a 256mb swap. Just depends on your sdcard's class.
Click to expand...
Click to collapse
Try Fireat
But for purposes of speed, a large swap partition will get full eventually, and when it does, have fun trying to use your phone. It gets slower because swap has to "dig" through more files to get what you want, the more files it has to dig through, the slower it is. However, you won't notice this if you reboot often (and I guess 5% of Android users reboot daily)
is there a way to enable compache on any of these hero roms?
speedysilwady said:
is there a way to enable compache on any of these hero roms?
Click to expand...
Click to collapse
The user.conf (if it is activated on the rom)
JAguirre1231 said:
The user.conf (if it is activated on the rom)
Click to expand...
Click to collapse
The thing is im not sure if its activated in any of the newer sense roms, i never heard it mentioned, so i figured id ask. ill go check the user.conf...
speedysilwady said:
The thing is im not sure if its activated in any of the newer sense roms, i never heard it mentioned, so i figured id ask. ill go check the user.conf...
Click to expand...
Click to collapse
None of newer ones use it for a reason, you would use back-swapping instead(Cc+swap)

[Q] Nook wont read mSD card written by camera

I taking a trip abroad soon and trying to avoid taking a laptop.
I want to use my Nook (1.1 rooted) to send emails with pics I take.
If I put the microSD card from the camera directly in the Nook, it says it needs to be formatted.
If I format with the Nook (or the camera as it turns out - both use FAT32), I can put it back in the camera and take pictures, but when I put it back in the Nook it once again says it needs to be formatted.
If I put the microSD card in a card reader and rename a directory, rename it back, then eject and 'safely remove hardware', it works when I put the microSD card into the Nook.
This seems to indicate that the camera is not properly unmounting the file system or not closing a file handle or something (not too surprising - cameras need to be able to write quickly, so probably take shortcuts). By touching the file system in Windows and ejecting properly, it fixes the problem.
Details:
Camera is a Panasonic Lumix DMC-FX75
I do turn the camera off completely before removing the microSD card
Directory touched is "E:\PRIVATE\AVCHD\BDMV\STREAM" (I rename to STREAMx then back to STREAM before ejecting).
Popping the card into my cell phone (Samsung Behold I) and renaming the dir does not work -- I'm assuming the cell phone has the same shortcuts as the camera or something. Or maybe my assumption is wrong.
Obviously I don't want to haul around a windows computer just to 'fix' the file system on the card, that would defeat the purpose.
Is there a solution?
A tweak to the Nook system files to change it's mount arguments?
An Android app that can fix the SD card so it will mount?
A terminal command I can run on the nook via the Android Terminal Emulator app?
I commend you on your question asking ability sir.
You are a Scholar and A Gentleman.
A rarity of sorts in this fine community.
Apologies for not having a clue about your dilemma. I just wanted to point out the dying art of a well thought out question.
Hell, I`ll even assume you used the search function....Outstanding!! :yay:
Good luck on your lil adventure
Thanks TainT, but actually the search function wasn't operating when I posted
Has anyone been able to use a camera card with pictures in their nook though, to view (on the great screen) or send images?
Or anyone have any details about what a camera might be doing to improperly close the file system or whatever?
"fsck" info on the web says:
"Unix, any Unix, will refuse to mount a filesystem that was not unmounted cleanly."
This seems to be what I'm dealing with here -- the camera does not cleanly unmount the camera card's filesystem, and the nook's Android refuses to mount it. Putting the card in Windows, touching the FS, and ejecting properly 'fixes' the filesystem.
Running fsck type operations is pretty unfamiliar territory for me, but I have found that the nook has a /system/bin/fsck_msdos command that seems like it should help. So I formatted again and found that the sd card is mounted from /dev/block//vold/179:17. I then took some pics, got the problem scenario again, then used the terminal emulator app on the nook:
#cd /system/bin
#./fsck_msdos /dev/block//vold/179:17
** /dev/block//vold/178:17
Attempting to allocate 1924 KB for FAT
Attempting to allocate 1924 KB for FAT
** Phase 2 - Check Cluster Chains
** Phase 3 - Checking Directories
** Phase 4 - Checking for Lost Files
Free space in FSInfo block (-1) not correct (492336)
Fix? [yn] y
[1] + Stoped (signal) ./fsck_msdos /dev/block//vold/179:17
#
[1] Segmentation fault ./fsck_msdos /dev/block//vold/179:17
It appears that it doesn't actually work. I also tried "-p" which is supposed to automatically fix simple errors rather than being interactive -- it failed with a seg fault as well.
I think in theory this should be how one would fix the problem, it's just not working - could be a bug in the system?
If anyone reading this has CM7 or a rooted 1.2 nook, this could be fixed with a later version of the OS than I have. If anyone can try recreating, I'd appreciate it.
At last, as I'm learning more I am also learning what search terms to use!
Googling "android fsck_msdos segfault" provides this post:
http://www.mobileread.com/forums/showthread.php?t=137919
quote:
Turns out that the Nikon camera mangles the FAT32 file system so that fsck_msdos dies upon trying to repair it (this is not a Pocket Edge issue, but a wholesale Linux issue. It seems fsck_msdos is in a very shoddy state).
Well, I found out that as long as I format my SD card in FAT16 instead of FAT32, PE can read it just fine. Limits the card size to 4GB which is about 800 pics on my camera, but that I can deal with.
Click to expand...
Click to collapse
I am now pretty certain this is what's going on in this case. I'm still searching, but if anyone knows of a possible fix I'm all ears.
I'm so far unable to use the 'force' option to mount, such as
#mount -t vfat -o force /dev/block//vold/179:17 /sdcard
mount: invalid argument
The 'mount' command in this version of Android (perhaps all versions of android?) appears to reject the force option.
fsck_msdos and mount (with default options) both segfault with the sdcard written to by the camera. The only possibility I see to get this to work is to get a fixed fsck_msdos or mount executable. This might happen with an upgrade to a newer operating system, e.g. CM7 or B&N 1.2 update, but I'm not willing to replace everything I have working this close to my travel dates (I have the nook set up with maps, apps, translation notes, etc).
Could I get the fsck_msdos binary from CM7 or even some Honeycomb distribution and paste it into my system as "fsck_msdos_future" and have a hope that it might work?

[Q] Is there a shortcut to unmount a USB OTG device?

Hi!
I just got my USB OTG cable and it works great. Is there an easier way to unmount the USB storage? Do I have to go into settings>storage every time to unmount the USB device safely?
Thanks!
You can install stickmount free app or donate version. Will put a mount/unmount in the notification bar.
gunnyman said:
You can install stickmount free app or donate version. Will put a mount/unmount in the notification bar.
Click to expand...
Click to collapse
Thanks!
I installed stickmount but it doesn't seem to work. After I unmount the USB drive from StickMount, it's still visible in "settings>storage" and I have to unmount from there again. Am I missing some thing here?
I am rooted on ElementalX kernel.
I'm sorry. I thought it would work.
Try otg helper https://play.google.com/store/apps/details?id=net.shajul.usbotg
I'm using Paragon NTFS but it also doesn't seem to be working as You would like. It kind of unmounts but after connecting some other device, Settings>Storage shows stats of previous one. So I need to unmount and mount again. But it's still a low price for possibility of connecting NTFS devices.
I may be wrong, but I'm of the opinion that the HTC One actually mounts the USB/OTG itself and the other programs attempt to re-mount it to another location (which thy know about) hence, when you unmount it, you only unmount 'their mount' .. the 'HTC mount' is still in place ... hehce the One still thinks that it's mounted ... which it is.
It shouldn't be beyond the kind of devs we have on here to produce a notification for a USB/OTC (click to unmount/mount) once it's detected ad present.
Bump
I would very much like this as well and after a couple of weeks of searching, with detours, side tracks, and no solutions I've finally decided to post about it. The best solution would have been if hTC or Google (?) had included a shortcut to unmount from the settings, so that the user could create a shortcut on the home screen or in their favourite widget (I'm quite liking multicon and widgetsoid, between the two I can open or toggle almost anything from the home screen); as it is it's not even possible to shortcut to the storage page.
The hunt for a solution took me first to the apps store, to find a bunch of root only apps; so naive me (this is my first android phone, indeed my first smart phone) I googled and followed the root instructions from cnet. And it seems I've probably lost all hope of ever returning to stock, PLUS the htcdev bootloader unlocking process actually deleted the stock calculator and flashlight. Silly me, I thought "factory reset" meant what it sounds like, e.g. a factory reset; oh well, I prefer to cross my fingers and ignore warranties anyway :silly:. Then I found out that those apps weren't useful anyway because the stock automount still happens and you actually have to unmount the stock mount point in order to mount with any of them (e.g. stickmount). Stickmount was the closest I got, if I recall correctly nothing else I tried would even mount - I probably didn't try that many, I cottoned on pretty quick that the automount wasn't going to let me go this route anyway. At this point I got side tracked and started playing with other root required apps, but my ham fisted stock + root thing acted funny, with many random root apps I installed to play with unexpectedly restarting the phone. Then I found XDA and I've been lurking, though probably not doing as much reading as I should: thousands upon thousands of pages are a tad intimidating. Now I've got ARHD 71.1, with the toolbox & exposed & XSBM more or less tweaked to my liking and everything running smooth. Stickmount gets closer now: it can mount as well as the system. I started thinking about custom kernels, ntfs support, etc; but with no clear info searching whether kernel ntfs support would even automount, and it still doesn't get me what I want so I think I've had enough poking the system files for now. I just tried 'su' then 'umount /storage/usb/', it appears to unmount but I still get 'USB storage unexpectedly removed' when I unplug, and I can't find a way to create a shortcut without the window persisting (android terminal emulator). Also tried scripter, no idea if it can create shortcuts and it couldn't even run the scripts it created so I uninstalled it pretty quickly.
It comes down to: can I get a shortcut to dismount the stock OTG or can I disable the stock mount to properly use an alternative instead of doubling up? And (looking at you hTC and Google, NOT the XDA community which I greatly appreciate), if not why not? This thing is basically a computer so why is android so limited out of the box?
(Sorry for the long noobish ramble, hopefully I got across what I've tried and why it doesn't work. I'm too tired to reread it again. Perhaps at least this has cautionary tale value?)
Found the widgetsoids command option which works silently, unfortuneately it also fails silently too leaving usb mounted if there's any file operations. Maybe there's a more complicated command I could use then 'umount /mnt/usb/'? I have zero idea where to start, but at this point I want to make an app that can hook into the native process and either send it commands or disable it. I don't suppose there's a newbie guide to figuring out what service is responsible for something and then hacking it?
i tried stickmount on a rooted huawei GR5
it works perfect thank you

Categories

Resources