Related
I am running the stock official GB Rom for my Atrix model. It is rooted and the bootloader is unlocked.
Quite after every reboot it happens that all the widgets fail to load and the message "Problem loading widget" is displayed.
This happens both with ADW Launcher EX and Go Launcher EX.
I tried to repair the permissions from the Recovery. It did not fix the problem.
Any suggestions, please?
Are you using a ROM?
Sent from my PC36100 using XDA App
I gave up running Faux kernels because of this problem. I could not find a way around it (fix permissions and certain re-unlock steps work for some people). What kernel are you running?
I wish there was a way around it for me. Between widget problems and webtop status bar issues I have not found a kernel that would work other than the stock one.
I forgot that I am using faux kernel,too! Can this really be the problem?
Inviato dal mio MB860 usando Tapatalk
dgraziotin said:
I forgot that I am using faux kernel,too! Can this really be the problem?
Inviato dal mio MB860 usando Tapatalk
Click to expand...
Click to collapse
Yes, sir...if you flash the stock kernel the widget problems should go away. Some people have the widget problem and some don't. It goes away for some and it doesn't for others. I tried everything. Rom manager fix permissions, etc. Every time I used a Faux kernel my widget problems came back. Sometimes immediately, sometimes a few days later. I have never seen the "problem loading widget" error message on the stock kernel. Not ever....
Use ROM Manager to fix permissions (fixes issue in most cases). This is a very old problem. Simple search would have answered your question.
CaelanT said:
Use ROM Manager to fix permissions (fixes issue in most cases). This is a very old problem. Simple search would have answered your question.
Click to expand...
Click to collapse
Besides repairing the permissions from the recovery, I also tried to fix them with Rom Manager, too.
Unfortunately, it did not fix the problem.
Update: it seems so much strange that a kernel could cause such problems. I read somewhere that the "problem loading widget" message usually appears when the widget is not able to load some resources. It smells like a permissions problem, of course.
Update 2: I also am no more able to fix permissions through rom manager, it gives me a generic error
Sorry for the bump but after reading some replies, I understand that I have not made myself clear.
Problem:
After a Reboot, the widgets display a "Error loading widget" message
Contexts:
Stock ROM, rooted and unlocked, Faux Kernel, ADW Launcher EX, Go Launcher EX
NottachTrix 1.2.2, stock kernel + ram fix, ADW Launcher EX, Go Launcher EX
Tried Solutions:
Fix permissions from Recovery
Fix permissions from Rom Manager
dgraziotin said:
Sorry for the bump but after reading some replies, I understand that I have not made myself clear.
Problem:
After a Reboot, the widgets display a "Error loading widget" message
Contexts:
Stock ROM, rooted and unlocked, Faux Kernel, ADW Launcher EX, Go Launcher EX
NottachTrix 1.2.2, stock kernel + ram fix, ADW Launcher EX, Go Launcher EX
Tried Solutions:
Fix permissions from Recovery
Fix permissions from Rom Manager
Click to expand...
Click to collapse
I used to get this exact same thing happening. Fix Permissions in CWM for some reason isn't as good as doing it from ROM Manager, then rebooting. This always worked for me, and it was the only semi-perma solution which ever surfaced as far as I know, other than going back to a stock kernel. I too use ADW-EX.
CaelanT said:
I used to get this exact same thing happening. Fix Permissions in CWM for some reason isn't as good as doing it from ROM Manager, then rebooting. This always worked for me, and it was the only semi-perma solution which ever surfaced as far as I know, other than going back to a stock kernel. I too use ADW-EX.
Click to expand...
Click to collapse
I (sort of) solved it: it was probably caused by Titanium Backup.
Even if the applications were not on the SD-card, there was something wrong with them (permissions, I guess) and the permissions utilities were not able to fix them.
Therefore, I re-installed the ROM and tried to install the applications from the Market instead of restoring them from TBA. Everything works now.
Thank you all for the suggestions, in any case!
Make sure whichever launcher you are using is not on the SD card. I had the same problem with go launcher as soon as I moved it to my SD. I moved it back to phone and haven't had the problem since.
I've tried a couple customs ROMS on my p4wifi, and in every case, I've had an issue with trebuchet, the CM launcher, failing. sometimes immediately, sometimes after a while. my most recent attempt was with the cm-10.1-20130117-0012-p4wifi-sgt7-gcc47.zip ROM, where I was able to operate for a little more than an hour before trebuchet failed.
in that most recent attempt, I was able to see that trebuchet forgot the grid size settings (originally 9x7, I think), and would show no numbers in the grid size height & width spinners, showing a 0 underneath. I could not spin them to a valid number, however, and shortly thereafter, trebuchet went into the repeated failed pop-up message.
luckily, I had backed-up my system and could restore back to my TouchWiz ICS image (though the back-up file being pushed into a 0/ folder is a pain, had to first re-image with CM 10.1 again, and use the file manager app to move the back-up files to a folder that nandroid would see.)
is anyone else having these problems with trebuchet when using CM 10 or 10.1 ROMs? I see posts from people saying their SGTs are running great with a number of these ROMs, so clearly it's working for them. where could I post bug reports for trebuchet? (here, but on the development forum?)
if I loaded an alternate launcher, would trebuchet failing not be an issue?
thanks.
mikejacobs99 said:
I've tried a couple customs ROMS on my p4wifi, and in every case, I've had an issue with trebuchet, the CM launcher, failing. sometimes immediately, sometimes after a while. my most recent attempt was with the cm-10.1-20130117-0012-p4wifi-sgt7-gcc47.zip ROM, where I was able to operate for a little more than an hour before trebuchet failed.
in that most recent attempt, I was able to see that trebuchet forgot the grid size settings (originally 9x7, I think), and would show no numbers in the grid size height & width spinners, showing a 0 underneath. I could not spin them to a valid number, however, and shortly thereafter, trebuchet went into the repeated failed pop-up message.
luckily, I had backed-up my system and could restore back to my TouchWiz ICS image (though the back-up file being pushed into a 0/ folder is a pain, had to first re-image with CM 10.1 again, and use the file manager app to move the back-up files to a folder that nandroid would see.)
is anyone else having these problems with trebuchet when using CM 10 or 10.1 ROMs? I see posts from people saying their SGTs are running great with a number of these ROMs, so clearly it's working for them. where could I post bug reports for trebuchet? (here, but on the development forum?)
if I loaded an alternate launcher, would trebuchet failing not be an issue?
thanks.
Click to expand...
Click to collapse
The onoy a'swer is see iz to try it out before panicing, try another launcher and let me know if it worked
mikejacobs99 said:
if I loaded an alternate launcher, would trebuchet failing not be an issue?
Click to expand...
Click to collapse
I've loaded pershoot's latest 10.1 (JB) ROM, and loaded Nova Launcher, and it's running just fine!
I have flashed the Candy5 rom a few times, but I am not able to get the facebook app to install. I have tried serveral Gapps. Is this a common thing or is there something I can do to fix this?
I posted in the Candy5 rom thread a few times, but I am unable to post there again because I have less than 10 posts?
I understand the work around to this problem could be, do without the facebook app and just login using a web browser. I just want to know if this is a common problem among flashing new/custom roms?
Seems like I was finally able to get the facebook app to install. It hung up on install but I just waited and waited and it finally successfully installed this time. We shall see if it fails to update/install in the future.
Well It won't let me move it to the sd card, and now I am stuck trying to re-install it again. Anyone else have this problem?
Anyone?.....
Bueller?..... Bueller?
blahforme said:
Anyone?.....
Bueller?..... Bueller?
Click to expand...
Click to collapse
Have you tried converting it to a user app using titanium backup? Not sure if this would help. These new roms are just beginning to become stable though so expect some bugs in the lollipops until the devs have a chance to perfect them. Is there a particular reason you need to have it on sd card?
Sent from my SAMSUNG-SGH-I717
developweb said:
Have you tried converting it to a user app using titanium backup? Not sure if this would help. These new roms are just beginning to become stable though so expect some bugs in the lollipops until the devs have a chance to perfect them. Is there a particular reason you need to have it on sd card?
Sent from my SAMSUNG-SGH-I717
Click to expand...
Click to collapse
I am not sure about converting to a user app with titanium backup. I would like to move it to the sd card to save some space, but when apps get moved there, they seem to disappear sometimes and they don't like to update. The facebook app is the worst. It doesn't want to install and if you get it installed it doesn't want to update. Thanks for your reply.
I have not had any issues installing Facebook so in bit sure what to say. Is your device telling you that's it's out of space?
Sent from my HTC0P3P7 using Tapatalk
gimmeitorilltell said:
I have not had any issues installing Facebook so in bit sure what to say. Is your device telling you that's it's out of space?
Sent from my HTC0P3P7 using Tapatalk
Click to expand...
Click to collapse
No, it just takes a long time downloading and then it says it is installing, but it doesn't install. I think a couple of times it might have said error 904, but I am not certain.
I do have it installed after many attempts, but it says it needs updated, and it goes back to the downloading & installing, but failing. Some of my other apps seem to disappear from my home screen and I have to drag them back out again and some apps disappeared and I had to reinstall them.
I did a fresh flash, wiped dalvik cache/cache/system/ before I flashed the v3.6 with the 09/09/15 gapps. Should I restore it to an earlier backup and update/flash through the Candy OTA instead?
I could try uninstalling the facebook app and try to reinstall it, but I am worried that might not work because this has happened to me on earlier roms too. Also crashes when I open a website link or youtube video in the facebook app.
I uninstalled the Facebook app then reinstalled it, but it appeared to hang up on install again. I shut down my device and waited for a minute or two and then turned it back on. While booting, it said Candy5 is optimizing Facebook app. Now the google play store shows the app is up to date.
I then tried opening a YouTube link from Facebook and it crashed to the home screen. Sometimes it shows the Samsung loading screen briefly, only with the Facebook app. Any suggestions?
blahforme said:
No, it just takes a long time downloading and then it says it is installing, but it doesn't install. I think a couple of times it might have said error 904, but I am not certain.
I do have it installed after many attempts, but it says it needs updated, and it goes back to the downloading & installing, but failing. Some of my other apps seem to disappear from my home screen and I have to drag them back out again and some apps disappeared and I had to reinstall them.
I did a fresh flash, wiped dalvik cache/cache/system/ before I flashed the v3.6 with the 09/09/15 gapps. Should I restore it to an earlier backup and update/flash through the Candy OTA instead?
I could try uninstalling the facebook app and try to reinstall it, but I am worried that might not work because this has happened to me on earlier roms too. Also crashes when I open a website link or youtube video in the facebook app.
Click to expand...
Click to collapse
I'm not sure which gapps you're using but maybe try another version. Make sure they are small or Pico gapps 5.1 version. Not the old 5.0
I am using the mini gapps from the op link.
Should I wipe internal & external SD cards also and flash again? When I wipe in twrp, I go to advanced wipe, dalvik cache/cache/system/data. I usually repeat that a few times before flashing the ROM.
I think my problem was due to file conflicts. I also had my original jellybean installed in twrp recovery backups and maybe the two different versions caused a conflict? I wiped everything and am now able to install facebook and move it to my sd card.
This is what I was worried about. It happened again during an update. Do I need to keep flashing gapps updates?
I just updated gapps to the 09/17/15 version and got this error now. I know I have plenty of space.
I was able to get the Facebook app installed again. I had to uninstall some apps and music to make space, which doesn't make sense because my 29 GB SD card was not even close to being full.
I am on Candy 9-08 build. I can install Facebook but can't update or move it to SD card. So if there is a new version, I have to uninstall and reinstall from the playstore. This usually takes a while and requires a reboot.
It probably something to do with the Facebook app. It used to work fine but stopped working a few months ago for me. I was on the 3-16 build of Candy for a while.
Sent from my LGL41C using Tapatalk
What I have to do to get installed is going to play store, initiate the download and install. When it's sat there for a little bit, reboot the phone.
Sent from my SAMSUNG-SGH-I717 using Tapatalk
Hi. I'm using CM12.1 with my quark (xt1254). Using a clean install method if I flash cm with a current gapps build (tried 1/29/16 & 1/30/16) the play store will not download apps over approx 25 MB. Play store downloads the app to 99%, restarts the download, then fails with error 963. Small apps are unaffected. Using the exact same method, but with an open gapps from 12/08/15
https://www.dropbox.com/s/e7a48os7ucj014p/open_gapps-arm-5.1-stock-20151208.zip?dl=0
, works perfectly fine. Just thought I'd see if anyone had any thoughts as to what's up. Ideas, contents, suggestions appreciated.
sd card
I had the same problem . I disconnected the SD card and now it all seems to be working again . It is not a permanent solution but a temporary solution , I hope
Hopefully it works .
kikkie said:
I had the same problem . I disconnected the SD card and now it all seems to be working again . It is not a permanent solution but a temporary solution , I hope
Hopefully it works .
Click to expand...
Click to collapse
I think the issue is related to the way CM12 chooses the default install location for you. The newer gapps builds may have triggered something, but I believe the root of it to be the default installation location. Please see this post for a possible permanent solution.
http://forum.xda-developers.com/showpost.php?p=65139180&postcount=6
Negative results. Bummer.
https://www.dropbox.com/s/kr21nbkkvnl6i24/open_gapps_debug_logs.tar.gz?dl=0
elderlypunk said:
Negative results. Bummer.
https://www.dropbox.com/s/kr21nbkkvnl6i24/open_gapps_debug_logs.tar.gz?dl=0
Click to expand...
Click to collapse
No joy after changing the default location? Which way did you use to change the location? Did it give you any messages? it shouldn't have, if it worked, it should just have returned a prompt.
Just to be on the safe side, I would load the gapps file that you mentioned was working in the past, and change the default location before trying any of the apps. If you already have it all loaded up, then yes, I'd also recommend you clear the cache and data from the playstore and playservices apps.
Don't know if you're using opengapps, but I took a look at their most recent builds and noticed that the file size changed slightly after 01/20/2016, so your reasoning has merit.
If you happen to be using TWRP, you could also try changing the location from recovery. Advanced -> Terminal Command -> Select and then enter the command. I really hope this helps.
I used the su terminal method. The location was definitely changed from 0 (auto) to 1 (internal). Behavior did not change at all. I am using open gapps and the working/not working is across builds (aroma thru nano/pico). Date of build appears to be the only determining factor. I originally thought size of the app mattered, but in talking with other users that seems to be less of an issue than previously thought. Also, apps that do not download from the play store cannot be side loaded either.
elderlypunk said:
I used the su terminal method. The location was definitely changed from 0 (auto) to 1 (internal). Behavior did not change at all. I am using open gapps and the working/not working is across builds (aroma thru nano/pico). Date of build appears to be the only determining factor. I originally thought size of the app mattered, but in talking with other users that seems to be less of an issue than previously thought. Also, apps that do not download from the play store cannot be side loaded either.
Click to expand...
Click to collapse
Ugh. I was able to recreate the behavior you're experiencing on a 2012 Nexus 7 - the only device I have access to with no SD card slot. I used the last two nightlies of CM12 and opengapps from two days ago, and also the one I mentioned from 1/20. Always had the behavior when downloading large apps, and as you say, apps not from the playstore. And yes, same behavior whether I used nano, pico, et. al.
The behavior disappears once I flash the latest nightly with the gapps from 1/20 AND change the default location. I wish I had more to give you, but since we're using different devices, there is a chance something else is different in the builds.
Gster09 said:
I wish I had more to give you, but since we're using different devices, there is a chance something else is different in the builds.
Click to expand...
Click to collapse
No worries! Since I found a working older gapps I'm inclined to let this go for now.
Which older version did you install? I'm running into this issue.
See link in op.
Hello,
I have same 963 error issue on my both cm 12.1 devices : Galaxy Nexus and Nexus 7 (2012).
I tried on my Galaxy to "pm set-install-location 1" but it don't solved the issue.
(delete the play store app cache and data don't work)
Can you provide me the link to this Gapps, it is not working anymore
ancelin said:
Hello,
Can you provide me the link to this Gapps, it is not working anymore
Click to expand...
Click to collapse
Try this. Turns out the problem is a Google play issue. One of the devs (baybutcher) posted this and I can confirm it fixed my issue. It downgrades Google play to a working version. If you are a doing a clean install just flash after gapps. If trying to fix an existing install make sure to uninstall all Google play updates then try flashing.
https://www.dropbox.com/s/0pzzlkiip6b97c8/play-6.0.5-flash-via-twrp.zip?dl=0
elderlypunk said:
Try this. Turns out the problem is a Google play issue. One of the devs (baybutcher) posted this and I can confirm it fixed my issue.
Click to expand...
Click to collapse
Did s/he mention when it will be fixed?
If you're looking for a version of Open GApps that doesn't have the double download fail with error 963. Then you should install Open GApps 2016.01.05. Don't install the 2015.12.08 version if you're using CyanogenMod! You'll end up breaking WebView on your rom if you do. You can find an Older Version option on the Open GApps Web Site and get the version I mention from there.
As others may have mentioned you can temporarily dismount your SD Card as a work around to this issue, but I preferred to downgrade rather than having to do that every time I used the Google Play Store.
As I understand the issue it's not a bug with Open GApps itself but a bug with the Google Play Store, apparently but I haven't confirmed any version of Google Play above 6.0.5 can have this issue.
elderlypunk said:
Try this. Turns out the problem is a Google play issue. One of the devs (baybutcher) posted this and I can confirm it fixed my issue. It downgrades Google play to a working version. If you are a doing a clean install just flash after gapps. If trying to fix an existing install make sure to uninstall all Google play updates then try flashing.
https://www.dropbox.com/s/0pzzlkiip6b97c8/play-6.0.5-flash-via-twrp.zip?dl=0
Click to expand...
Click to collapse
This fixed the issue for me, and I was able to install the 2 problematic apps. Strangely, I had no trouble installing some other apps, namely made by my operator (MEO music and MEO drive), which leads me to think it might be related to locale.
However, now I can't search the play store, as it force closes when tapping the search box :/
Best thread ever.
Finally it works.
Thanks everyone
I don't know if others are facing the similar problem but it has turned my life into hell after the new update. I will list down the issues on ALL ROMS after the new OOS 3 update with bootloader in my device.
I had issue in accessing storage, which means gallery, file explorer or literally any app crashes when I try to access from the storage, be it internal or external sd card.
Couldn't use the latest snapchat at all, can't post in story, can't save any snap, can't upload from camera roll. It was just a dead end. However I could only post into story with a older Snapchat version, still due to storage access issue, I couldn't save or upload from Camera Roll
Facebook picture upload would ocassionally crash the app.
Couldn't take more than 1 picture in latest youcam app, storage issue would crash the app.
Gallery apps fail to generate thumbnail previews.
All these above problems caused permanent storage access unavailability until I rebooted device.
Need to charge my device twice as Battery runs faster than Usain Bolt.
So finally after a lot of tingling, I finally downgraded my device to OOS 2.1.3 with TWRP 2.8.7. Trust me it's very stable, bug free and battery friendly. Though I miss the new security patches features and snappy feel from Android 6 & 7.
The above problems are not happening in 2.1.3. I can use latest snapchat, youcam & facebook without any issue at all. Is there any way to prevent these issues on new Android OS in my device ? I believe it's not a device issue as 2.1.3 is running very stable and bug less.
Never had any of those issues on OOS 3 update. Think you might of gone wrong somewhere maybe.
Exodusche said:
Never had any of those issues on OOS 3 update. Think you might of gone wrong somewhere maybe.
Click to expand...
Click to collapse
I am really eager to find that out. I have almost tried every ROM on the new bootloader. Except MOOS 2.0 or something, each and every ROM had this bug, even official OOS 3.1.4. Any idea what might went wrong ? The bugs are not reproducing in OOS 2.1.3 though. Which makes me believe that my device is ok.
arafat_mw said:
I am really eager to find that out. I have almost tried every ROM on the new bootloader. Except MOOS 2.0 or something, each and every ROM had this bug, even official OOS 3.1.4. Any idea what might went wrong ? The bugs are not reproducing in OOS 2.1.3 though. Which makes me believe that my device is ok.
Click to expand...
Click to collapse
Think I figured it out for you. You are on really old OOS2 build you need to flash 2.2.3 before you update to OOS3. It was made for the update to MM.
Are you sure you gave the good permission. On MM, when you first launch an app, it should ask you for it. Maybe a bug appear at one point.
You should go to menu settings / app / 3 dots menu at the top right an reset app prefs.
Then re open app one by one.
You can try first without your SD inside to see if it happens again.