I updated to the FRF83 build, but I still have issues with the widgets. After reboots and mounting to the usb, widgets do not load. They are either missing or says "can't load widget". Does anyone know how to fix this?
Don't have that application installed to the sdcard.
It's not only widgets that are on the SD card. Even the calendar widget has issue.
Related
I formatted my sd card after installing Dwangs ROM, however I originally formatted it wrong so I got the black screen. Before I formated the SD card I had downloaded a bunch of apps.
Now that I've formatted the sd card all of my apps are gone. When I go into the Market to re-download them the market thinks I still have them installed.
I went to Manage Applications and cleared the cache of the Market App.
I then sorted for 3rd party apps and sure enough they still all show up under that filter but they are all 0.00Kb and when I click on them the phone just says App no found.
Anything else I should try beyond a whipe and re-install the Rom?
Yeah I had that happen too. I just went ahead a re-installed the rom, but I'm pretty sure if you pushed the .apks to /system/sd your phone would read them properly. They would have to be named exactly as they were before though - "com.handcent.nextsms.apk" for example, and not just "Handcent.apk."
this is happening with my lock screen widget, i try to add it it's not there i look in applications under settings and it's not listed, i go to market and in my downloads its there but i can't open or uninstall i've flashed 3 times already do i need a wipe? i have my apps on sd but i'm not trying to install them from market again
You can manually edit out the problem apps entries in /data/system/packages.xml
Nevermind i fixed it...just did a nandroid restore and then flashed cm4.2.4 then my theme and it's there and working now, strange
"Application is not installed on your phone" after moving apps to SD on Froyo
hey guys,
first of all i searched the forum but didn't find anything like my problem
(i run Froyo on non-rooted Nexus One)
so, i moved several apps to SD using that ADB command to change default install location from internal memory to SD. everything worked and apps were running smoothly. then my battery went dead during the night and when i switched the phone on in the morning i see icons with green robot for all those apps moved to SD. and if i try running them i get "application is not installed on your phone" error message. thou apps are still on the SD. it seems that my phone erased the part of the data of those apps stored in the internal memory.. which sucks.
anyone faced such a problem so far? i wonder if it's possible to solve without reinstalling all the apps..
many thx in advance.
Cheers.
It happened on my phone too, just removed battery for few minutes.
Looks like a bug.
dpds said:
hey guys,
first of all i searched the forum but didn't find anything like my problem
(i run Froyo on non-rooted Nexus One)
so, i moved several apps to SD using that ADB command to change default install location from internal memory to SD. everything worked and apps were running smoothly. then my battery went dead during the night and when i switched the phone on in the morning i see icons with green robot for all those apps moved to SD. and if i try running them i get "application is not installed on your phone" error message. thou apps are still on the SD. it seems that my phone erased the part of the data of those apps stored in the internal memory.. which sucks.
anyone faced such a problem so far? i wonder if it's possible to solve without reinstalling all the apps..
many thx in advance.
Cheers.
Click to expand...
Click to collapse
Forcing the apps to install to SD will break them. In order for applications to be successfully moved to the SD card in Froyo, they must have an appropriate flag set on them from the developer. If the application isn't updated with this flag, it will not work by default from the SD card.
The ADB command should work fine (I think) once all apps are updated, but until then it will just cause problems like what you're seeing.
codesplice said:
Forcing the apps to install to SD will break them. In order for applications to be successfully moved to the SD card in Froyo, they must have an appropriate flag set on them from the developer. If the application isn't updated with this flag, it will not work by default from the SD card.
The ADB command should work fine (I think) once all apps are updated, but until then it will just cause problems like what you're seeing.
Click to expand...
Click to collapse
What app in the market currently supports apps 2 sd?
ram130 said:
What app in the market currently supports apps 2 sd?
Click to expand...
Click to collapse
Not sure, as I'm currently unable to access the market (being deployed will do that). There is a thread on the subject though, which is here: http://forum.xda-developers.com/showthread.php?t=687659
codesplice said:
Not sure, as I'm currently unable to access the market (being deployed will do that). There is a thread on the subject though, which is here: http://forum.xda-developers.com/showthread.php?t=687659
Click to expand...
Click to collapse
THanks man!!
I set the installation location to SD via ADB and restored my apps via Titanium Backup. Here's what I found.
Apps will occasionly seem to have dissapeared (from App page + download page from the market) seems intermittent and seems to correct itself.
If you mount the SD card via USB then obviously your phone can't access the apps, after unmounting it takes a little time for the system to correct itself (my recommendation is to turn the screen off and on again).
Keep any widget app you are going to use on the phone's storage (i.e. install app, then move it back to phone via the 'applications' menu).
Shortcuts to apps will revert to a generic green/white robot icon, but they will still work (not when the SD card is mounted via usb though obviously).
Basically any application/live wallpapers or anything else that you expect to run live (constantly) should be moved to the phones memory.
bumskins said:
I set the installation location to SD via ADB and restored my apps via Titanium Backup. Here's what I found.
Apps will occasionly seem to have dissapeared (from App page + download page from the market) seems intermittent and seems to correct itself.
If you mount the SD card via USB then obviously your phone can't access the apps, after unmounting it takes a little time for the system to correct itself (my recommendation is to turn the screen off and on again).
Keep any widget app you are going to use on the phone's storage (i.e. install app, then move it back to phone via the 'applications' menu).
Shortcuts to apps will revert to a generic green/white robot icon, but they will still work (not when the SD card is mounted via usb though obviously).
Basically any application/live wallpapers or anything else that you expect to run live (constantly) should be moved to the phones memory.
Click to expand...
Click to collapse
This is how I've been using it, also when you reboot the phone, I give it a minute to calculate the applications on the SD card and load them into the phone memory. (Notice if you go to App settings while you can't access the application, they are all there and being "calculated."
After installing CM6 RC3 I have lost all my apps on the SD card, they did come back for a short time after a reboot but then disappeared again after another reboot. I cannot even uninstall them or reload them from the market as they just hang when I try to uninstall or re-install from the market.
When I look at application info, the apps on the SD just show "Computing" and nothing ever shows up.
Also, I am unable to mount the SD over USB.
I have gone back to stock ROM but I still have the issue.
I was using apps2SD but I made sure not to move any widgets or running apps.
I've tried booting into recovery to wipe data and cache but of course my recovery is broken.
If I missed this in the forums please give me a search that will give me results that are not too numerous to parse.
Thanks for any help.
There is no apps2SD support in CM6 or the stock rom, that's why you can't see them.
CM6 only support the FroYo apps on SD method right now, and they are working on a newer better apps2sd for future versions.
If you flash back to CM5, you might be able to see them, but I am not familiar with the old apps2SD method.
Then why did my apps show up in CM6? They were there and functioning fine, I think I must have messed with a setting somewhere.
FYI, I was able to restore my apps by deleting .android_secure from the SD card and then re-install Ti Backup and restore my apps.
Can someone explain how the app location setting in CM6 affects apps? I am thinking when I enabled this it screwed things up.
The .android_secure directory on the SD card is the 2.2 official apps to SD. So you probably were using that all along and something screwed up. That's why you could use them for a bit.
So I am having a problem. On almost every reboot, I get an error over every widget saying "Problem Loading Widget". I have all my widgets installed on the internal memory. Does anyone else have any similar problems or ideas how to fix it? This happens with ADW, ADW EX, and VTL Launchers and is very frustrating!
I was having this issue on both Zeam and ADW. I had to wipe/clear System and Cache and reinstall the stable 7.0 version, reinstall GAPPS. I also reflashed Dalingrin's OC kernel (the 4/11 version), but the problem was fixed before I did that.
I have/had the same issue. After every reboot the problem loading widget error occurs. One thing I noticed is that my external SD card was not mounted. Once it mounted all the widgets started to populate. On every reoboot I open up astro and nav to the \sdcard, it won't be there immediately, but astro some how finds it and mounts it. Hope this helps.
I believe i read somewhere that using themes other than the standard "system" theme would cause the sd card to not mount right away. I know that i've had the same issue since applying the cyanbreadx theme.
Can anyone confirm or deny this, please?
Expatriotex said:
I believe i read somewhere that using themes other than the standard "system" theme would cause the sd card to not mount right away. I know that i've had the same issue since applying the cyanbreadx theme.
Click to expand...
Click to collapse
Having same issue on CM7 #256, if it's as simple a fix as using the stock themes it would be disappointing but no longer frustrating.
Best regards,
m0nk3d0
[Q] Getting "Couldn't install on USB Storage or SD Card" error with multiple apps.
My TF-701 is dead stock, no root, no ROM and lately I've been getting an increasing list of apps failing to update with the error "Couldn't install to USB Storage or SD Card".
It started with Aldiko Premium, then RealVNC and now Pocket Admin.
I tried uninstalling the first two and now I can't even (re)install them as I get the same error.
Has anyone else been having this issue?
Does anyone know the cause?
Is there a fix or workaround?
Asus Transformer TF-701 (K00C) running stock Android 4.4.2
Kernel - 3.4.66-g96e53b8
Build number - KOT49H.US_epad-11.4.1.17-20140711
UPDATE: Unmounting and removing the microSD Card does provide a workaround. It seems to me like this is a programming error in the app, probably some incorrect path checking when there is a microSD Card installed. I almost wonder if there is some change in Android L that some developers are adapting for but are breaking backwards compatibility by doing it incorrectly?
Screencap of the error attached
I sometimes had the same error message. For me the installations went fine when I removed all SD cards (SD-Card and MicroSD card) before installing/updating the apps.
Yeah, I get this too. Popping out the MicroSD, and then hitting install seems to temporarily fix the issue. I'm guessing that there is some code on the install/update of some apps that check something on external storage, and the 4.4.x stuff blocks that, and therefore fails as saying it couldn't put something on the SD card. This only happens with certain apps. However, if I uninstall the app, format the SD card, reboot, then reinstall the app... It still does it. Therefore it has to be something to do with the apps and possibly their install routines or their declared permissions.
At least this is my guess. I haven't bothered to trace this stuff, nor anything further.