Related
Today I had several reboots on my Desire. After the third I decided to do a hard reset.
Since rebooting the Android Market has been REALLY slow.
It will find apps and let me install them, however the screen doesn't change after the install - it keeps saying installing. The only way to remove the "installing" message is to reboot
I have tried several reboots, reflashed the stock T-Mobile UK ROM and I have formatted the SD card, but none of these have fixed it.
I get the same using WiFi or mobile internet (vodafone UK)
Anyone having the same issue, or got any ideas how to resolve it??
Cheers
Zippyioa
Delete please..
See below...
Try THIS!
If not then just wait as the Market on googles servers needs time to catch up with the diffrent build numbers changed, since a flash i belive
Mine took personally after everyflash at least a hour to start even working a bit.
EDIT: Maybe if it carries on being very slow, maybe something happened in the flash whilst in recovery, and has written some data to some bad sectors, causing this issue << only spectulation tho!
zippyioa said:
Since rebooting the Android Market has been REALLY slow.
It will find apps and let me install them, however the screen doesn't change after the install - it keeps saying installing. The only way to remove the "installing" message is to reboot
Click to expand...
Click to collapse
Thanks for the link, but I tried that already (after searching for this issue!)
It didn't resolve either issue for me (the slow market, or the installing issue) nor did other threads, hence me starting this one.
Any further help would be appreciated
Zippyioa
potter1984 said:
Delete please..
See below...
Click to expand...
Click to collapse
Please don't!
See above.....
zippyioa said:
Please don't!
See above.....
Click to expand...
Click to collapse
Lol, i ment delete my post
Then referred to my second post.
Soz for the confusion
Still having this issue.
I have tried the close market place and clear cache/data idea, but no joy
I have now re-formatted (after a factory reset and clearing storage in bootloader) but it still sticks on installing in market even though the app installs fine.
Please help!
Slow for me today as well, stock Desire.
Maybe give it a day?
Okay, its been a few days now and I am still having the never ending install and slow market issue.
Surely I cant be alone??
Hey everyone. between my brothers and I, we have five Evo's. two of us are running full roots and nand unlocks, the other three are using unrevoked. those that unrevoked can use the wifi router without issue, but for my brother and myself, using the wifi router results in the app crashing and having to force close.
has anyone seen anything similar? can anyone offer me some solution?
and btw, this is my third rom. they all have the same results(full wipe, data and davik cache clear each time)
Delete wi fi tether from the phone and re-download it. This has worked for me everytime i change roms =)
Hope it helps.
Do you mean the wireless tether app? I am running my own rom but it seems that it worked for me when I was using fresh. But that is the only other rom I have tried. Have you tried re-installing the tether app?
I'm not sure i can remove the base wifi tether app. it's always cooked into the rom. and i have tried reinstalling the app. i've gone from the original version, to the newer version and finally the beta version with no luck
I was having this issue for awhile. I'm not sure exactly what fixed it, but my work around was:
1. Re-install from the market place (Do not launch)
2. Reboot
3. Install this version http://code.google.com/p/android-wifi-tether/downloads/detail?name=wireless_tether_2_0_5-pre2.apk&can=2&q=NexusOne
(Don't lanch)
4. Reboot
5. Should work now
Hmmmmmm. I am sure someone else can offer better advice, but does the super user app come up to ask for permission or it fc's before that?
topdawgn8 said:
I was having this issue for awhile. I'm not sure exactly what fixed it, but my work around was:
1. Re-install from the market place (Do not launch)
2. Reboot
3. Install this version http://code.google.com/p/android-wifi-tether/downloads/detail?name=wireless_tether_2_0_5-pre2.apk&can=2&q=NexusOne
(Don't lanch)
4. Reboot
5. Should work now
Click to expand...
Click to collapse
okay, i did exactly as you said. now the app will start, but as soon as i click on the wifi symbol, it thinks for a second and says "Unable to start tethering. Please try again!"
Edit: and on first run, it asked me for super user permissions. i click grant and checked the box to allow future requests
I am not sure if your signature is correct but have you tried flashing the newest radio? I am not sure if that would fix it or not. And the same thing happens to the other phone? Puzzling indeed. I'm sure someone will drop in and tell you how to fix it soon. Worst case, start over. Even though I know you said you tried various roms, maybe you are accidentally skipping a step, I do that sometimes
SilverStone641 said:
okay, i did exactly as you said. now the app will start, but as soon as i click on the wifi symbol, it thinks for a second and says "Unable to start tethering. Please try again!"
Edit: and on first run, it asked me for super user permissions. i click grant and checked the box to allow future requests
Click to expand...
Click to collapse
Ok, go back through the same process and try this one instead of what was in step 3.
http://code.google.com/p/android-wi...me=wireless_tether_2_0_2.apk&can=2&q=NexusOne
If that doesn't work, I've got nothing else. The first one was the beta you probably tried earlier. This is the stable one; however, I never tried it with this one. I always got it working using the 2_0_5 version.
Also, for ****s and giggles, have you tried updating you profile and prl?
- you didn't flash the wireless n patch over a 1.47 base Rom correct? Can you connect to a WiFi router or is it just the tether app?
elegantai said:
Also, for ****s and giggles, have you tried updating you profile and prl?
Click to expand...
Click to collapse
uh....what?? you got me there! i thought i knew what those were, but it escapes me now.
the only thing i can think of is that the rooting process screwed up somehow. but for it to screw up in the same way for two separate phones is odd, but it's the only thing that has remained constant since the very beginning.
Menu - settings - system updates. The profile and prl won't mess with root or anything but its something I have heard to do in this case. Don't know if it will help.
Also did you see the note about the wifi n patch on the other page? I added it after I posted... like this
elegantai said:
Menu - settings - system updates. The profile and prl won't mess with root or anything but its something I have heard to do in this case. Don't know if it will help.
Also did you see the note about the wifi n patch on the other page? I added it after I posted... like this
Click to expand...
Click to collapse
done. same results. "Unable to start tethering. Please try again!"
Well crapola. I think I'm outta ideas man. if you didn't patch the wireless n over a 1.47 Rom then I have no clue what it could be. maybe Sprint is spying on you and has your phones on lock down! but if you can't find the answer just try starting fresh. it might be a pain but who knows what little quirk could have gotten messed up.
elegantai said:
Well crapola. I think I'm outta ideas man. if you didn't patch the wireless n over a 1.47 Rom then I have no clue what it could be. maybe Sprint is spying on you and has your phones on lock down! but if you can't find the answer just try starting fresh. it might be a pain but who knows what little quirk could have gotten messed up.
Click to expand...
Click to collapse
i do have the wireless N enabled, but i do not have the new 1.47 yet. i'm waiting on OMJ to release an update
Ok, so I've searched on this and haven't been able to find anyone with the same problem. This is so annoying!
Phone specs:
HTC Evo, rooted
Cyanogen 7.0.3.1
PRL 01115
not sure what else you might need to diagnose this.
Around the time that Sprint released their stock gingerbread rom for the Evo, my GPS went on the fritz. All of a sudden, google maps would only get a fix maybe once every few minutes. Useless for navigation! Sometimes the GPS icon wouldn't even flash, like it wasn't even trying to get a fix, meanwhile, Maps is "waiting for location."
I tried the usual "fix" that you hear about, by flashing back to a sense rom and typing ##gpsclrx##, and then the MSL number when prompted. No success.
I finally figured out that if I go into recovery and clear the dalvik cache, and then run GPS Status after it reboots, the gps works again, but a few days later, I have to do that all over again.
Any idea what's causing this or how to fix it?
I get similar problems. I just started using Cyanogen when Sprint came out with their first Gingerbread update and broke everything. I love Cyanogen, and I have managed to get everything working except for the GPS.
A lot of times it takes a long time to turn on when I start up google maps, and then it will get a fix, and then after a minute it will loose the fix and won't be able to get gps lock again. I tried flashing back to a stock rom and doing the ##gpsclrx# thing, but it just clears the call screen and never even asks for a MSL number, so I don't know if that works or not. I love Cyanogen, but don't know if I can live without the GPS working.
Has anybody else figured anything out? Does anyone know if this is a know problem that is being worked on or not?
I get no fix on gps and no voice
a question for the OP since you dont make any mention of it.
Have you tried flashing the Galandy fix for GPS? Using the Vision GPS driver makes a world of difference.
the first one, at the top of the list.
found here in this thread - http://forum.xda-developers.com/showthread.php?t=1132412&highlight=gps+fix
use the flashable zip that corresponds to your recovery type. i've used the Fix_2 on several devices with CWM recovery.
I was able to solve it using the drivers here:
http://forum.xda-developers.com/showpost.php?p=14534313&postcount=2478
Not sure if this is the same thing as what drdrewdown posted... sounds like it is.
secretspy711 said:
I was able to solve it using the drivers here:
http://forum.xda-developers.com/showpost.php?p=14534313&postcount=2478
Not sure if this is the same thing as what drdrewdown posted... sounds like it is.
Click to expand...
Click to collapse
galandy made that post you are referring to lol... so yea its the same
Bumping this thread with a question: Will the Vision GPS driver (Galandy) work on a near-stock Sense ROM (GB)?
I'm running Jiminy, which is mostly a debloated stock ROM with a few changes made for ease of use on the Cricket network.
Currently my GPS is doing what the OP of this thread is describing- my current workaround is to do the following every single time I want to use nav:
1) Open GPS Status. Clear AGPS data. Download new AGPS data.
2) Open GPSFix. Hit "Start Fix", then hit the Map button.
3) Do my Navigation. It works fairly well after that.
This is an annoying procedure!!! I want to load the Vision driver but don't know if it will screw something up- it seems like most of the people running it are on CM7 or some other AOSP custom ROM.
Will it work with my setup?
mpsantiago said:
Bumping this thread with a question: Will the Vision GPS driver (Galandy) work on a near-stock Sense ROM (GB)?
Click to expand...
Click to collapse
In theory, they should work fine on Sense roms as well. However if your stock Sense GPS drivers are not working then the Vision drivers might not work either, but it doesn't hurt to try. Just backup your gps.supersonic.so file in /system/lib/hw/ folder before flashing the driver.
I posted new drivers HERE today btw
galandy said:
In theory, they should work fine on Sense roms as well. However if your stock Sense GPS drivers are not working then the Vision drivers might not work either, but it doesn't hurt to try. Just backup your gps.supersonic.so file in /system/lib/hw/ folder before flashing the driver.
I posted new drivers HERE today btw
Click to expand...
Click to collapse
Oddly enough, my phone does not have that file. And installing it seems to do nothing
The closest thing I have is /system/lib/libgps.so
Being the daring sort, I renamed that file and replaced it with the a renamed copy of the Vision gps.supersonic.so; my phone did not like that at all- no boot, had to reflash
drdrewdown said:
a question for the OP since you dont make any mention of it.
Have you tried flashing the Galandy fix for GPS? Using the Vision GPS driver makes a world of difference.
the first one, at the top of the list.
found here in this thread - http://forum.xda-developers.com/showthread.php?t=1132412&highlight=gps+fix
use the flashable zip that corresponds to your recovery type. i've used the Fix_2 on several devices with CWM recovery.
Click to expand...
Click to collapse
I flashed the vision driver and then the new one posted last night, and neither worked. my GPS is useless right now, for the first time ever...
Gonna try the GPSFix app now...
Another thing I notice is that I don't even get the GPS Icon when I'm trying to use GPS Status or navigator
HipKat said:
I flashed the vision driver and then the new one posted last night, and neither worked. my GPS is useless right now, for the first time ever...
Gonna try the GPSFix app now...
Another thing I notice is that I don't even get the GPS Icon when I'm trying to use GPS Status or navigator
Click to expand...
Click to collapse
you'd have to tell us a little more about your config if you want us to help diagnose it, as well as a little back history
galandy said:
In theory, they should work fine on Sense roms as well. However if your stock Sense GPS drivers are not working then the Vision drivers might not work either, but it doesn't hurt to try. Just backup your gps.supersonic.so file in /system/lib/hw/ folder before flashing the driver.
I posted new drivers HERE today btw
Click to expand...
Click to collapse
You are the frickin man!!!!
Before that driver I'd see 3 satellites and could rarely get a lock. Now I see 10 and it locks quick!!!
Thanks.
BTW, in case it helps anybody else, I used that latest Vision driver from galandy along with the PRI/Radio/NV combo found here: http://forum.xda-developers.com/showthread.php?t=1128135 and could not be happier with the results.
well, it worked great for a while, but now it's back to only working when it wants to (which is never when I need it)
Has anybody ever heard of undervolting breaking GPS? I ask because that's the only thing I've done aside from rooting/installing the ROM.
I had a problem with GPS. So I got off 28 nightly and went to the 100s lol works great.
World peace with no regard for human life.
mpsantiago said:
well, it worked great for a while, but now it's back to only working when it wants to (which is never when I need it)
Has anybody ever heard of undervolting breaking GPS? I ask because that's the only thing I've done aside from rooting/installing the ROM.
Click to expand...
Click to collapse
nope, i undervolt quite a bit & gps works great.
mpsantiago said:
Bumping this thread with a question: Will the Vision GPS driver (Galandy) work on a near-stock Sense ROM (GB)?
I'm running Jiminy, which is mostly a debloated stock ROM with a few changes made for ease of use on the Cricket network.
Currently my GPS is doing what the OP of this thread is describing- my current workaround is to do the following every single time I want to use nav:
1) Open GPS Status. Clear AGPS data. Download new AGPS data.
2) Open GPSFix. Hit "Start Fix", then hit the Map button.
3) Do my Navigation. It works fairly well after that.
This is an annoying procedure!!! I want to load the Vision driver but don't know if it will screw something up- it seems like most of the people running it are on CM7 or some other AOSP custom ROM.
Will it work with my setup?
Click to expand...
Click to collapse
Thank you a lot
It works for me @ Cyanogen 9 on my Nexus S !
First of all, I would like to thank everyone involved in making our Defy's so awesome.
Thanks to you all, as after getting all the info and help, I was successfully able to
upgraded to CM7 1.0-RC1.5-jordan-signed, and after few initial hiccups everything is working fine. Except the battery drainage issue. And I have been loving the new look and feel of my Defy ever since.
Today Morning. I've started getting a new problem. Whenever I want to call someone and I go to contacts, it force closes itself with following error:-
"The Process android.process.acore has stopped unexpectedly. Please try again."
I have restarted the phone and no respite from the problem.
Help please....
Did you change something or install a new app immediately before this started to happen ? Did you restart your phone while it was still connected to the PC or so? Some other people solved this problem by doing a factory reset. But you need to find the specific reason or cause in your case and correct that.
tdlr said:
Did you change something or install a new app immediately before this started to happen ? Did you restart your phone while it was still connected to the PC or so? Some other people solved this problem by doing a factory reset. But you need to find the specific reason or cause in your case and correct that.
Click to expand...
Click to collapse
Well, the last thing I did last night was that I installed two ADW themes. and also downloaded few wallpapers.
Do you think, the themes could have created this problem?
mandhir.s.bajwa said:
Do you think, the themes could have created this problem?
Click to expand...
Click to collapse
As there is, according to my information, no standard cause for this problem, everything could be the reason. Other people reported this error on different devices too and the reasons were diverse.
Some have had the problem after installing a new app, others due to rebooting the phone while it was still connected to the pc. Others made a factory reset and then it worked again and the true reason was never found.
It won't kill you to try and disable/uninstall the new themes or wallpapers (if they are live wallpapers).
Maybe there is another specific well known reason for that out there. In this case I simply don't know one.
If you're lucky, others had the same problem and have identified a more precise cause. Then they will answer hopefully.
I would try to undo the last things you changed before and find out the true cause.
tdlr said:
As there is, according to my information, no standard cause for this problem, everything could be the reason. Other people reported this error on different devices too and the reasons were diverse.
Some have had the problem after installing a new app, others due to rebooting the phone while it was still connected to the pc. Others made a factory reset and then it worked again and the true reason was never found.
It won't kill you to try and disable/uninstall the new themes or wallpapers (if they are live wallpapers).
Maybe there is another specific well known reason for that out there. In this case I simply don't know one.
If you're lucky, others had the same problem and have identified a more precise cause. Then they will answer hopefully.
I would try to undo the last things you changed before and find out the true cause.
Click to expand...
Click to collapse
Thanks for the suggestions.
Will uninstall the new themes.
And as you said, Factory reset. If I do that, what exactly will happen.
Asking this because as mentioned before, I'm no longer on the version which came with phone and I am on CM7. so Factory reset will take me to which phase?
mandhir.s.bajwa said:
And as you said, Factory reset. If I do that, what exactly will happen.
Click to expand...
Click to collapse
Have a look here: https://motorola-global-en-uk.custh...00/~/defy---master-reset-/-factory-data-reset
You may also try fixing permissions before with Rom manager.
tdlr said:
Have a look here: https://motorola-global-en-uk.custh...00/~/defy---master-reset-/-factory-data-reset
You may also try fixing permissions before with Rom manager.
Click to expand...
Click to collapse
well the link tells me what will happen on a stock rom. My question is. If I factory reset on CM7, will it take me to the original state or the default settings of CM7.
Flash cm7 again! maybe it helps.
guys,do i need cyanogen 7.1 installed on my device to install cyanogen 7.5?
Make a backup and try wiping via CWM. Both data and cache partition.
Sent from my ME525+ using Tapatalk
yashank said:
guys,do i need cyanogen 7.1 installed on my device to install cyanogen 7.5?
Click to expand...
Click to collapse
You can flash any CM7 directly via recovery menu if yer on Froyo.
Sent from my ME525+ using Tapatalk
Recenty started getting few more issues.
1.> Phonebook crashing because of FC's. I'm hardly able to use my phonebook now
2.> Last night, messages stopped working. Again FC's.
3.> Today morning the native camera application stopped working.
And I have done following to overcome all the issues with no luck:-
wipes all cache including devik.
Did factory reset
reflashed with CM7 jordon 1.5
All failed to give me any respite from the errors.
Now I have downloaded cm7-110923-0710-Nightly.
Do let me know if this is an OK one. I've faced way too many errors and afraid of showing it off to anyone now as It might crash anytime.
Much to my disappointment, even flashing to newer nightly, I'm still getting the same errors.
Can someone provide me the 3.4.3-36-1.7 SBF? the one in the link provided earlier is not working.
Or any other solution.
The errors are way too much to ignore, and if this continues then I have to go back to Froyo. But I seriously love the new feel of the phone. All thanks to CM7.
need assistance ---defy just rebooting and rebooting after 2ndinit install
need assistance ---defy just rebooting and rebooting
i installed the rom amanger premium
after that i installed the 2ndInit from market for android and installed the latest version .....and after that i uncheck the usb debugging and restarted the defy
since then its auto rebooting from logo to black screen and back to logo ....
please help me i am new to this and really pissed off .......
First of all I apologize if I posted this on the wrong forum. I am an XDA fan, this is where all get all the goodies for my phone but never actually post.
I flashed SlimBean4.3OfficialBuild1 along with the gapps they provided on their site (SlimMinimalGapps4.3Build1). As always I keep my apps backed up with TitaniumBackup but I downloaded the apps and it said my device wasn't rooted. I checked USB Debugging and enabled it and still no luck, then i downloaded SU from playstore and it gave me same message, no root. I do not know what it is and I am frustrated its late and I need to get up early. I will leave the phone as it is till I find a solution. Another big BIG issue is the screen flickering I have been getting and looked all over the web and i could not find a solution. I only been getting the screen issues with android 4.3 on all the roms I tried so far. I did get those screen flicker a long time ago but I thought it was because of the ROM i was on then I switched to another one and it was all good. I you would please help me find a solution to this. I feel like throwing my phone to the wall. I have a Samsung Galaxy S3 i747. THANKS IN ADVANCED.
I had to change the superuser app that I'm using before TB will register. I'm using SuperSU but I have to manually update it sometimes, or just download superuser from Store. Download Root Checker
(https://play.google.com/store/apps/details?id=org.freeandroidtools.root_checker) and it'll tell you if you're rooted or not. The flickering is way beyond me. I'm way too weak in the Force to go into 4.3 ROMS yet.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
IrvGotte said:
First of all I apologize if I posted this on the wrong forum. I am an XDA fan, this is where all get all the goodies for my phone but never actually post.
I flashed SlimBean4.3OfficialBuild1 along with the gapps they provided on their site (SlimMinimalGapps4.3Build1). As always I keep my apps backed up with TitaniumBackup but I downloaded the apps and it said my device wasn't rooted. I checked USB Debugging and enabled it and still no luck, then i downloaded SU from playstore and it gave me same message, no root. I do not know what it is and I am frustrated its late and I need to get up early. I will leave the phone as it is till I find a solution. Another big BIG issue is the screen flickering I have been getting and looked all over the web and i could not find a solution. I only been getting the screen issues with android 4.3 on all the roms I tried so far. I did get those screen flicker a long time ago but I thought it was because of the ROM i was on then I switched to another one and it was all good. I you would please help me find a solution to this. I feel like throwing my phone to the wall. I have a Samsung Galaxy S3 i747. THANKS IN ADVANCED.
Click to expand...
Click to collapse
You have to activate root on 4.3 ROMs. Its settings>development>root set it to apps and/or adb.
Sent from my SGH-I747 using Tapatalk 4
Re-flash SuperSU
IrvGotte said:
First of all I apologize if I posted this on the wrong forum. I am an XDA fan, this is where all get all the goodies for my phone but never actually post.
I flashed SlimBean4.3OfficialBuild1 along with the gapps they provided on their site (SlimMinimalGapps4.3Build1). As always I keep my apps backed up with TitaniumBackup but I downloaded the apps and it said my device wasn't rooted. I checked USB Debugging and enabled it and still no luck, then i downloaded SU from playstore and it gave me same message, no root. I do not know what it is and I am frustrated its late and I need to get up early. I will leave the phone as it is till I find a solution. Another big BIG issue is the screen flickering I have been getting and looked all over the web and i could not find a solution. I only been getting the screen issues with android 4.3 on all the roms I tried so far. I did get those screen flicker a long time ago but I thought it was because of the ROM i was on then I switched to another one and it was all good. I you would please help me find a solution to this. I feel like throwing my phone to the wall. I have a Samsung Galaxy S3 i747. THANKS IN ADVANCED.
Click to expand...
Click to collapse
Well, I had to re-flash a SuperSU update and that seemed to fix the prob. Even just flashing the latest nightly unrooted my phone. I'll try and find the link for you. Also, try a system, cache, and dalvic wipe.