Database Users

[Q] Widgets Issue...

Alright this has been driving me mad for a while now and there doesn't seem to be an active thread with a solution to this.
Every once in a while when i boot up my phone will have problem loading widget. So i moved them back to phone for the ones that mattered and tried to select the widget again from the menu. Well they're not there any more. and even after a reinstall and reboot boot the programs don't show in the widgets section.
Has anyone had this issue and/or have a fix for it?
Thanks,
Urzu

What ROM? When you set the install location to automatic, widgets should install the the phone by default (which is where all widgets need to be installed, or you get errors when loading the widget). To be safe, I would set the install location to phone, then reinstall the widgets and see where that gets you... This is of course assuming you are running a ROM that allows for this.

TybaltX1 said:
Alright this has been driving me mad for a while now and there doesn't seem to be an active thread with a solution to this.
Every once in a while when i boot up my phone will have problem loading widget. So i moved them back to phone for the ones that mattered and tried to select the widget again from the menu. Well they're not there any more. and even after a reinstall and reboot boot the programs don't show in the widgets section.
Has anyone had this issue and/or have a fix for it?
Thanks,
Urzu
Click to expand...
Click to collapse
After following winsettr instructions boot into recovery go to advanced a wipe dalvic cache
Sent from my Liberty using XDA App

Sorry should have stated I'm using cm 6.1.0.
Andok I'll do these steps and post my results.
Thank you!
Sent from my Liberty using XDA App

Worked like a charm thank you!
Sent from my Liberty using XDA App

Completely stuck, definitely need help at this point

Ok, so I've looked through various threads today and cant seem to get a fix.
First, heres the symptoms- N4 (4.2.1) has massive battery loss/ something running in the background killing it (battery page says Android OS). I killed all the background apps and everything else it would let me kill and it still will not charge (tried different plugs, cables, outlets, etc). I've had it plugged in for the past 6 hours and I'm finally up to 9%.
The phone has been rooted, and I'm trying to flash it and return it to stock, but thats when I ran into problem 2. It won't recognize that it is plugged into a computer (running on a Mac, but tried XP machine, Win7 machine, and again different cords).
From here, I don't know where to go. I'm new to this Android ball game so I don't have a ton of background here, so hopefully I missed something simple.
PS by massive battery loss- I fully charged the phone last night, then went to class today with wifi/blue/gps off and always have 5 bars of AT&T here and after 1 Hr, I had 35% battery left with Android OS consuming almost all of it.

definitely pickup gsam battery monitor and better battery stats to monitor the battery usage. gsam might be able to tell you what app is causing the battery drain. bbs is more technical but might tell you more about what is going on. Make sure your maps app is not reporting your location.

rmkbow said:
definitely pickup gsam battery monitor and better battery stats to monitor the battery usage. gsam might be able to tell you what app is causing the battery drain. bbs is more technical but might tell you more about what is going on. Make sure your maps app is not reporting your location.
Click to expand...
Click to collapse
Thanks for the response. Downloaded it and the usage is 1%, so now I think its something more than that. Either hardware or some weird glitch??

It won't charge and isn't recognized by any computer?
I'd call it a hardware fault to be honest.
Try to get a stock rom on the device, re flash it and RMA it.

Nuu~ said:
It won't charge and isn't recognized by any computer?
I'd call it a hardware fault to be honest.
Try to get a stock rom on the device, re flash it and RMA it.
Click to expand...
Click to collapse
Yeah, thats what I was thinking.... still stuck on how to get a rom on it without it recognizing being plugged in though?

GunninZombiesdown said:
Yeah, thats what I was thinking.... still stuck on how to get a rom on it without it recognizing being plugged in though?
Click to expand...
Click to collapse
Just let it die and RMA it anyways. They arent gonna bother to Charge it, then "look to see if you Rom'd it".

I'm gonna help ya out here...
1. download this app from the playstore and relock bootloader : https://play.google.com/store/apps/details?id=net.segv11.bootunlocker
2. download the stock ROM & recovery from this thread straight to your phone : http://forum.xda-developers.com/showthread.php?t=2006088
3. boot into recovery, full wipe, flash the ROM then the recovery. all done, back to stock:beer:
Sent from my Nexus 4 using xda app-developers app

ardedpr Bartles
lowrider262 said:
I'm gonna help ya out here...
1. download this app from the playstore and relock bootloader : https://play.google.com/store/apps/details?id=net.segv11.bootunlocker
2. download the stock ROM & recovery from this thread straight to your phone : http://forum.xda-developers.com/showthread.php?t=2006088
3. boot into recovery, full wipe, flash the ROM then the recovery. all done, back to stock:beer:
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Thanks man, really appreciate it! Man I hope this works, because I came from a i 4s and was about to slit my throat and buy an iPhone 5.

GunninZombiesdown said:
Thanks man, really appreciate it! Man I hope this works, because I came from a i 4s and was about to slit my throat and buy an iPhone 5.
Click to expand...
Click to collapse
just remember when you go to flash the downloaded files theyll be located in the /download folder (just in case you didn't know) and also by "full wipe" I mean factory reset + wipe cache
Sent from my Nexus 4 using xda app-developers app

Well now it seems I've hit another brick wall. After entering into, or trying to enter into Recovery mode, it comes up with an error message saying No Command. I swear, I'm not usually this bad with these things. Any ideas?

For future reference MTP doesn't work with Win XP, and you need a separate app for it to work on a Mac. Should be recognized on the Win 7 PC though.

GunninZombiesdown said:
Well now it seems I've hit another brick wall. After entering into, or trying to enter into Recovery mode, it comes up with an error message saying No Command. I swear, I'm not usually this bad with these things. Any ideas?
Click to expand...
Click to collapse
That means you currently have the stock recovery installed. First unlock the bootloader again with the Bootlock app. Then download Rom Manger from the play store https://play.google.com/store/apps/details?id=com.koushikdutta.rommanager . open it up and select flash clockworkmod recovery. When its done re-lock your boot loader again with bootlock. Then boot back into recovery manually (or even easier,open rom manager again and push reboot into recovery) and proceed to flash the stock rom & recovery files. (Don't forget to wipe first)
Sent from my A200 using Tapatalk HD

Possible Fix For 4.1.2 Battery Drain

Hi guys
I came across this thread by "galchristian" in the Verizon SIII subsection, and thought I would share it here in the hope it might help someone. I myself haven't tried it yet as I'm at work, but I will be later on or tomorrow. According to the OP though, this seems to sort out battery drain issues for Jelly Bean.
Here is the original thread: http://forum.xda-developers.com/showthread.php?t=1976666
"For all of you who have a JellyBean ROM already installed and have the battery drain skip to Step.8
1. Download your JellyBean ROM of choice
2. Place on SD card
3. MAKE A NANDROID BACKUP of your current ROM
4. Wipe data, cache and dalvik cache
5. Select ROM of choice from the SD card (Most ROM's these days come with an Aroma-Installer so remember what you picked to be installed and what not.)
6. Boot device
7. Set up the phone and let it restore all apps. Set everything you will use (facebook, e-mail, flipboard etc) -then ReBoot
8. I used TitaniumBackup and removed "Media Storage" and I also removed "Downloads 4.1.1"
9. ReBoot into Recovery & wipe cache and dalvik cache
10.Dirty-Flash your ROM of choice which you chose @ Step.5 and chose the same features if possible.
11.Install your prefered Kernel optional (I personally chose Ktoosez 3.0.49 just because it gave me good battery life)
12.Wipe cache and dalvik the last time and also fix permissions.
13.ReBoot the last time and enjoy!"
Please share your thoughts and feedback as I'm sure a lot of us are very peed off with losing 20% battery overnight.
Cheers

My first question will be, how can I convert a .tar ROM to a suitable format to be flashed via my SD rather than through Odin? Unless, of course, flashing a ROM via odin without wiping first is exactly the same as flashing a "dirty" ROM via recovery?

Thanks to OP. But this guide is something like how to drive your Ferrari on 6th gear without mentioning how to start it! What is 'dirty flash'? How will you flash the ROM, Mobile Odin or PC Odin or what? Also not everyone knows what Aroma installer is.
Besides, I don't think even after doing this battery life could improve. Imo, if 4.1.2 had good backup then it'll be just present there normally, like 4.1.1.
'Swyped' from my GT-N7100

jujuburi said:
Thanks to OP. But this guide is something like how to drive your Ferrari on 6th gear without mentioning how to start it! What is 'dirty flash'? How will you flash the ROM, Mobile Odin or PC Odin or what? Also not everyone knows what Aroma installer is.
Besides, I don't think even after doing this battery life could improve. Imo, if 4.1.2 had good backup then it'll be just present there normally, like 4.1.1.
'Swyped' from my GT-N7100
Click to expand...
Click to collapse
Dirty flash is flashing the rom over your current one without wiping first.
From what I deduced I assumed the OP is saying to flash via your SD card and not via odin. Also that aroma is not necessary, but if you use it then to keep all settings the same.
If any newbies have any question we'll try and help them, but I don't think it terribly overcomplicated for most people on this site.
I am not sure whether this works as I haven't yet tried it, but the OP certainly seems to think it does.

fade2black101 said:
Dirty flash is flashing the rom over your current one without wiping first.
From what I deduced I assumed the OP is saying to flash via your SD card and not via odin. Also that aroma is not necessary, but if you use it then to keep all settings the same.
If any newbies have any question we'll try and help them, but I don't think it terribly overcomplicated for most people on this site.
I am not sure whether this works as I haven't yet tried it, but the OP certainly seems to think it does.
Click to expand...
Click to collapse
The op says "POSSIBLE" fix
Sent from my GT-N7100 using xda premium

I'm use to wipe /system before a new flash. Have i right to do that?
Sent from my GT-N7100 using xda app-developers app

KyleDevlin12 said:
The op says "POSSIBLE" fix
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
I said possible fix, the original op said it worked for him 4 times.

igol24 said:
I'm use to wipe /system before a new flash. Have i right to do that?
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Well for an upgrade there is basically no meaning doing a wipe, but if you want to make sure and wanna do a wipe anyway, then you should do it after flashing the ROM, not before.

fade2black101 said:
I said possible fix, the original op said it worked for him 4 times.
Click to expand...
Click to collapse
Sent from my GT-N7100 using xda premium

So what consequences will removing media storage and downloads have?

Guys first thing first about battery draining is your mobile network not configure properly.. just realize it after I install configuration message from provider.. I drain 1% all over night.. and get 2day standby battery with medium usage.. 10 hours screen.. and leaving the phone with charging all night is weaken your battery.. first time I forget to unplug and everything change.. battery drain 5% after sleep 6hours..and only last for 1 day with medium usage.. 6hours on screen now I dont know how to make it back like it was.. using note for 3weeks anyone knows how to increase batt life without changing rom or kernel ?? Im still runing stock 4.1.1
Sent from my GT-N7100 using Tapatalk 2

[Q] Black Screen in the morning...

Howdy all!!
I'm currently running Franco Kernel r111 and the latest CM10.1 Nightly (20130327), and twice now I've woken up and my screen is black and won't turn on. The LED at the bottom is flashing a notification, but I can't wake the device. I have to hold the power button and then turn the device back on. The issue is, that I use this as my alarm clock, so it's made me late a few times now...
Is this the "SOD" that everyone is talking about? I think it's related to this most current nightly, as I've used r111 of Franco's Kernel along with the 23rd and 24th CM10.1 nightly and I didn't see the problem.
I guess my question is, is there something I can do to tell what is causing the crash? It's plugged into the charger, so could I run some app that will take a log that I can check the next morning if it should freeze?

Maybe you have undervolted too much, how much did you UV?. Try raising the voltage and see if that helps.

gee2012 said:
Maybe you have undervolted too much, how much did you UV?. Try raising the voltage and see if that helps.
Click to expand...
Click to collapse
I don't undervolt anymore on top of what Franco does by default.

jsylvia007 said:
I don't undervolt anymore on top of what Franco does by default.
Click to expand...
Click to collapse
Frano default is stock voltages, it is noy UV`d. Then maybe there is an installed app or widget that is going crazy and causes fc`s.

gee2012 said:
Frano default is stock voltages, it is noy UV`d. Then maybe there is an installed app or widget that is going crazy and causes fc`s.
Click to expand...
Click to collapse
That's why I was hoping someone knew of an app that might log things, so I can check after the reboot.

jsylvia007 said:
That's why I was hoping someone knew of an app that might log things, so I can check after the reboot.
Click to expand...
Click to collapse
Try BetterBatteryStatts, it shows activity`s of apps.

gee2012 said:
Try BetterBatteryStatts, it shows activity`s of apps.
Click to expand...
Click to collapse
I'm running that now actually, but I didn't think it's data persisted through a reboot.

Get a logcat via adb.
Sent from my Nexus 4 using xda premium

gravitysandwich said:
Get a logcat via adb.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
So, I assume I would do these steps:
1. When I wake up and notice that the device is "frozen", hold the power button to turn it off.
2. Boot the device into fastboot mode
3. Use ADB to pull the logcat
4. Reboot the phone normally
Forgive me, but I haven't used ADB to get a logcat, and I believe that if I do it after a reboot into the full OS, won't the new boot overwrite the logcat from the frozen state?

jsylvia007 said:
Howdy all!!
Is this the "SOD" that everyone is talking about?
Click to expand...
Click to collapse
Sounds like the "SOD" issue many of us have. It's cause is currently unknown although turning WiFi off may prevent this from happening.

xda6969 said:
Sounds like the "SOD" issue many of us have. It's cause is currently unknown.
Click to expand...
Click to collapse
Ok, this is good to know... I've only JUST started to experience it in the most current CM10.1 nightlies... It happened to me once a while back with a CM10.1 nightly, but the update the next day fixed it, and never showed up again until recently.

same here!
Hey all! havin same issues here! ;( Dont know why is it happenin, and most important, why it only happens sometimes.... :silly:
I attached a logcat to molesarecomming and he told me it is some kind of driver mess up I've done a full wipe and going totally stock with no luck, IDK what to do....
PD: I hav a thread here so if you can just take a look!
jsylvia007 said:
So, I assume I would do these steps:
1. When I wake up and notice that the device is "frozen", hold the power button to turn it off.
2. Boot the device into fastboot mode
3. Use ADB to pull the logcat
4. Reboot the phone normally
Forgive me, but I haven't used ADB to get a logcat, and I believe that if I do it after a reboot into the full OS, won't the new boot overwrite the logcat from the frozen state?
Click to expand...
Click to collapse
what I did: when i noticed my phone its frozen I just connect it to pc and use adb to pull logcat, without reboot.

malavi said:
Hey all! havin same issues here! ;( Dont know why is it happenin, and most important, why it only happens sometimes.... :silly:
I attached a logcat to molesarecomming and he told me it is some kind of driver mess up I've done a full wipe and going totally stock with no luck, IDK what to do....
PD: I hav a thread here so if you can just take a look!
what I did: when i noticed my phone its frozen I just connect it to pc and use adb to pull logcat, without reboot.
Click to expand...
Click to collapse
Why don't you open a ticket with Google support and send them the logcat?

No when its frozen plug it in the computer and type adb logcat in the cmd window. A cmd window should pop up with your logcat.
Sent from my Nexus 4 using xda premium

gee2012 said:
Frano default is stock voltages, it is noy UV`d.
Click to expand...
Click to collapse
The 1026MHz slot is UV'd by default on Franco kernel. Though that won't have anything to do with the OP's problem.
Sent from my Nexus 4

Black screen in morning, flashers take warning

VoiD_Dweller said:
Black screen in morning, flashers take warning
Click to expand...
Click to collapse
This made me LOL so hard...
In other news its definitely some combination of CM nightlies & Franco kernel. I'm now on the newest nightly and r116, and it didn't happen this morning.
When it happens again I will try the adb logcat and see what I can figure out.

Ok... So! I am running Franco Kernel r117 & CM10.1 Nightly 20130403... I had the black screen again for the first time in a few days...
I plugged the phone into my computer, started the Nexus Toolkit, and followed the options to pull a logcat over to my computer. The problem is, the screen stayed at "Waiting for Phone" for almost 15 minutes, and then I had to leave for work...
Any help here?

Can't upgrade from 2.2

[Resolved]
Help, I downgraded from 2.3 to 2.2 for various reasons,but now when I try to upgrade again I just get the pink screen ,if I try using the option from settings/storage,it says key data couldn't be backed up , the installation will stop. Also if I boot into the system it runs fine for about a minute then locks up completely so I can't even continue to use it in 2.2 can anyone advise ?
Sent from my Nexus 7 using XDA Free mobile app

Try to put the 2.3 dload folder to a sd card, then remove the battery, plug in a USB cable to the computer and the phone, volume up+down+power (if I remember right lol). See if it will update that way.

no, that's the usual way I've been flashing it, I can get to the image folder ,but it won't boot into recovery either
Sent from my Nexus 7 using XDA Free mobile app

totsy1972 said:
no, that's the usual way I've been flashing it, I can get to the image folder ,but it won't boot into recovery either
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
Odd. Maybe try to flash the ICS pink screen unlocker? I had weird issues at some point too, then I flashed that and the problems went away. Afterwards flash ICS.

Just tried that,still no luck,it doesn't even get to the unpacking screen,it just stays pink. beginning to think its beyond repair
Sent from my Nexus 7 using XDA Free mobile app

totsy1972 said:
Just tried that,still no luck,it doesn't even get to the unpacking screen,it just stays pink. beginning to think its beyond repair
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
I think it's still possible to fix it. I was loosing hopes too, but I messed around with it anyway and got it working. Just try different dload's, different methods and maybe you'll get it running. Maybe other users will have some ideas too.

CrysisLTU said:
I think it's still possible to fix it. I was loosing hopes too, but I messed around with it anyway and got it working. Just try different dload's, different methods and maybe you'll get it running. Maybe other users will have some ideas too.
Click to expand...
Click to collapse
I've been trying all different ways, this is what I get when trying it from storage menu
Sent from my ST15i using XDA Free mobile app

@Moihack maybe you have any ideas? You've written this to me before:
Moihack said:
As long as your phone still gets power and pink/blue screen shows there is nothing to be afraid of yet,since this isn't a hardbrick.
Contact me on hangouts telling me what you have done resulting in the above issue.
I have bricked my u8800pro in every possible way both soft and hard brick (thank god warranty was still active back then).
Click to expand...
Click to collapse

Hi there!
I think when you upgrade from software menu there is an option for data back-up.
Uncheck this option and the error should go away.
Also what do you mean with this: "Also if I boot into the system it runs fine for about a minute then locks up" ?
What do you mean it locks up? Touchscreen is not responsive for example?
My suggestions:
1) Do a factory reset and then check if you can upgrade
2) Try re-installing your recovery(use cwm 5.0.27 by geno for best compatibility) or even replace the whole image folder with the froyo one from here: http://forum.xda-developers.com/showthread.php?t=2146856
Your phone is not beyond repair that's for sure. Since it boots fine.

Moihack said:
Hi there!
I think when you upgrade from software menu there is an option for data back-up.
Uncheck this option and the error should go away.
Also what do you mean with this: "Also if I boot into the system it runs fine for about a minute then locks up" ?
What do you mean it locks up? Touchscreen is not responsive for example?
Click to expand...
Click to collapse
I haven't noticed an option for data backup,will check again later on. And yes when it locks up touch screen becomes unresponsive and none of the buttons respond either. Also when I try to enter recovery ,both custom and stock, it displays the kernel logo then vibrates with a black screen for a second then back to kernel logo and continues to boot.
Sent from my Nexus 7 using XDA Free mobile app

Ok guys,I copied over the stock image folder and now it works ok, however I still can't upgrade from froyo. At least I can use it again though so thanks for your help, its much appreciated. Incidentally, there wasn't an option to back up data when upgrading, but that error has now gone, except it now just reboots instead, so I will just keep trying.
Sent from my U8800Pro using XDA Free mobile app
[Edit] Finally I've managed to upgrade to GB , had to put both step 1 and step 2 in the same dload folder and it worked. So cheers for the tips

You've put all steps in one folder?

DarkSkyGhost said:
You've put all steps in one folder?
Click to expand...
Click to collapse
Steps 1&2 in dload folder ,step 2 renamed to UPDATE_G.APP.
Didn't use step 3 as I was updating to ICS after that
Sent from my Nexus 7 using xda app-developers app