Android OS Forum banner
121 - 140 of 306 Posts
To assist further, more info is required:
What computer OS are you using (Win7, XP, Linux, Snow Leopord)?
What ROM are you using on your HP Touchpad 64GB, CM7, CM9 or something else?
Does it react correctly from webOS (eject from HPTouchpad parent folder) USB connection or do you get the "Ouch" response?
Does the CM7 eject not work or not see the volume?
CM9 under MTP connect doesn't have an eject or dismount, which kinda bugs me.

Help us, the community, help you.
window 7 64 bit, Windows OS doesn't having anything to do with the touchpad. I'm using CM9 nightly build, dated August 23 - 22 2012 version. although it's been happening through all builds. earlier cm7 version this didn't happen that I recall, it will mount for several mins when booted enough to get a nightly starting downloaded, then after that's done it will UN-mount no further communications. frustrating works fantastic in WebOs zero problems there. thanks been needing to mention this quite awhile ago. I made a video about it and live recording of it happening. build 14th I won't touch completely breaks my Touchpad CM9. apps no longer run etc, couldn't even get into android settings etc. thanks guys at a loss as what to do. this is the white touchpad 64GB WebOs/Android CM9

Sent from my Motorola DROID RAZR MAXX XT912 ICS 4.04 v.211 using Tapatalk 2
 
window 7 64 bit, Windows OS doesn't having anything to do with the touchpad. I'm using CM9 nightly build, dated August 23 - 22 2012 version. although it's been happening through all builds. earlier cm7 version this didn't happen that I recall, it will mount for several mins when booted enough to get a nightly starting downloaded, then after that's done it will UN-mount no further communications. frustrating works fantastic in WebOs zero problems there. thanks been needing to mention this quite awhile ago. I made a video about it and live recording of it happening. build 14th I won't touch completely breaks my Touchpad CM9. apps no longer run etc, couldn't even get into android settings etc. thanks guys at a loss as what to do. this is the white touchpad 64GB WebOs/Android CM9

Sent from my Motorola DROID RAZR MAXX XT912 ICS 4.04 v.211 using Tapatalk 2
Sorry, you're kinda on your own because you have a 64GB TouchPad. There are very few of those floating around and I doubt many here know if there are specific issues unique to that TouchPad. If you can get some kind of response from J.C. Sullins, he is the developer on the HP TouchPad.
 
window 7 64 bit, Windows OS doesn't having anything to do with the touchpad. I'm using CM9 nightly build, dated August 23 - 22 2012 version.
you posted on August 20th that you have "August 23 - 22 2012 version" ? Now I'm confused.
 
I've been having the same problem. The first time it happened, I changed the partition size and all was good, but it was the largest size I could select. So now the problem has arise again but I'm unable to be sized the petition at least to the menu.

I'm still confused how SD and USB storage differ from one another, after all they are the same device. I do understand how their mounted as different as partitions, but where is the main android OS located, SD card storage or USB storage?

Any recommendations, tips or tricks to resize the best the partition and or resolve the issue with SD card on mounting.

thanks
Chris
 
I've been having the same problem. The first time it happened, I changed the partition size and all was good, but it was the largest size I could select. So now the problem has arise again but I'm unable to be sized the petition at least to the menu.

I'm still confused how SD and USB storage differ from one another, after all they are the same device. I do understand how their mounted as different as partitions, but where is the main android OS located, SD card storage or USB storage?

Any recommendations, tips or tricks to resize the best the partition and or resolve the issue with SD card on mounting.

thanks
Chris
Let me see if I have this straight, you used JC Sullins memory size fix to increase your internal memory to 3.45 GB. And now you have downloaded so many apps that you have run out of internal memory?

The total memory on a TouchPad is allocated to different purposes. Some for internal memory, some to operating system and the rest to storage which in WebOS speak is called the usb drive and in Android speak is called the SD card. It's all the same space, just called by a different name.

I'm guessing that the first time you used JC's memory fix , you ran it and it worked. Now when you try to run it it says "Failed". The only way around this is to backup your install and then run ACMEUninstaller. This will reset all the Android memory partitions and completely remove anything Android except what is on the SD card.
Now reinstall Moboot, CWM and the nightly you are currently using, don't waste your time with Gapps.. Boot to Android to insure the install worked OK. Now got to CWM and run the 2048 memory fix. Immediately boot Android to initialize the new memory. If you check settings/storage you will see you have 3.45GB of internal memory. Now if you really think you have to have more internal memory, go back to CWM and run the memory fix again and reboot. This will increase internal memory to 5.5GB. Now restore your backup and you'll have more internal memory for all that stuff you keep downloading. Just remember, whatever you allocate to internal memory, is lost to the SD card. Why don't you seriously look at the number of programs you have downloaded that you don't need or never use.
 
Can anyone tell me if the "stashing" workaround and its CM7 files will also work with CM9?

I've seen a lot of talk about the other workaround working, but I'm more interested in moving my files back to internal storage and taking it from there.

I wasn't sure if I should have started a new topic for this or not, but I chose to write it here because it is topical.
 
good advise. i will advise the outcome after the holiday weekend.
Just realized that I didn't update as promised. Followed your advise NT and my co-workers Touchpad is working flawlessly now.. thanks
 
  • Like
Reactions: nevertells
Can anyone tell me if the "stashing" workaround and its CM7 files will also work with CM9?

I've seen a lot of talk about the other workaround working, but I'm more interested in moving my files back to internal storage and taking it from there.

I wasn't sure if I should have started a new topic for this or not, but I chose to write it here because it is topical.
Explain in more detail. Don't have a clue what you are talking about, "Can anyone tell me if the "stashing" workaround and its CM7 files will also work with CM9?"
 
Explain in more detail. Don't have a clue what you are talking about, "Can anyone tell me if the "stashing" workaround and its CM7 files will also work with CM9?"
JCSullins, in his original post, wrote the following:

The next fix/workaround allows you to 'stash' some of the apps
on the 'sdcard' so that the 50+ issue does not come into play.
This will allow you to move apps back from the 'sdcard' without
encountering the "Removed SD card" error while attempting to do so.
Each time you apply this 'fix', it will 'stash' all but 40 of
the apps on the 'sdcard'.

So, apply this fix once. Then move apps back from the 'sdcard' to
the 'phone' (or 'Internal storage'). Note that apps that have been
'stashed' might show with a greyed-out icon with an 'SD Card' symbol
and the letters 'SD' -- do not attempt to move these. After you
have moved the apps from the 'sdcard' back to 'phone' (those that
haven't been 'stashed'), you apply the fix again. Applying the
fix the second time will 'unstash' the remaining apps (remember
that it will not allow more than 40 apps to be 'unstashed') thus
allowing you to move them off the 'sdcard' too.
This is what I'm referring to.
 
JCSullins, in his original post, wrote the following:

This is what I'm referring to.
OK, having never had that issue, I went back and reread JC's OP and got more familiar with "Stashing". The person that can answer your question is going to be JC as he is the developer of that fix. Bad news is I have not seen any posts or work done by him since early August I'm betting that it does work on CM9. So if you can't get a reply from JC, then your next best bet would be to try it out. You've already backed yourself into a corner with all the apps you have moved to the SD card and you may just have to blow everything off the SD card, uninstall Android, reinstall, and then run the zip to increase your internal memory before reinstalling all your apps.

Another thought would be to remove a bunch of apps you don't use much or not at all from the internal memory and then move everything off the SD card, make a nandroid backup, uninstall and reinstall CM9, install the memory zip, reboot and then restore your backup.

Also, in the future, I would suggest you be a little more selective in your downloading.
 
UPDATE: The CM7 "stashing" workaround DOES work on CM9, for anyone who wants to try it.

First, you're going to want to do a nandroid backup, just in case. Look here for a guide. Second, just install the fix. Reboot into ClockworkMod Recovery, choose "install zip from SD card", and navigate to jcsullins' stash fix and run it (probably in the /Downloads folder). Reboot into CM9, go into Settings > Apps > On SD Card and move several of the checked apps back to the internal memory by selecting the app and then selecting "move to tablet". You will see several apps that are "grayed out", but this is part of the workaround. They'll return to normal after you reboot into ClockworkMod again and run the fix a second time. And you're done. Everything should be buttery smooth again.
Image


Believe it or not, not everything requires a CM reinstall.

Unsolicited advice: install App2SD. Not only will it let you know which apps can be moved to the SD card, grouped by size, but it'll let you keep track of how many apps you have already moved, so you can optimize the 50 apps (hopefully less) to only include the only largest ones that don't need to be hogging your TouchPad's internal memory.
 
UPDATE: The CM7 "stashing" workaround DOES work on CM9, for anyone who wants to try it.

First, you're going to want to do a nandroid backup, just in case. Look here for a guide. Second, just install the fix. Reboot into ClockworkMod Recovery, choose "install zip from SD card", and navigate to jcsullins' stash fix and run it (probably in the /Downloads folder). Reboot into CM9, go into Settings > Apps > On SD Card and move several of the checked apps back to the internal memory by selecting the app and then selecting "move to tablet". You will see several apps that are "grayed out", but this is part of the workaround. They'll return to normal after you reboot into ClockworkMod again and run the fix a second time. And you're done. Everything should be buttery smooth again.
Image


Believe it or not, not everything requires a CM reinstall.

Unsolicited advice: install App2SD. Not only will it let you know which apps can be moved to the SD card, grouped by size, but it'll let you keep track of how many apps you have already moved, so you can optimize the 50 apps (hopefully less) to only include the only largest ones that don't need to be hogging your TouchPad's internal memory.
So after "stashing" your apps, did you successfully apply the memory upgrade? You won't need the App2SD if you have enough internal memory.
 
I have sd card problem. Says there is no sd card mounted. Tried to download fixes. Could not download says needs sd card to download. Cannot go into usb mode under cm9. Can get into usb mode in webos. I am in a mess. cm9 apps gone or don't work. Any suggestions?e
Have you been moving a lot of apps to your SD card? Did you read this entire thread? Until you properly educate yourself on how to deal with this issue, downloading any of these apps is not going to help you.
 
Another thought would be to remove a bunch of apps you don't use much or not at all from the internal memory and then move everything off the SD card, make a nandroid backup, uninstall and reinstall CM9, install the memory zip, reboot and then restore your backup.
that's exactly what I've done. Now I don't care about in-tablet-storage anymore :D
 
121 - 140 of 306 Posts