Hi. After my SGS died I got myself the Wildfire S (until the next Nexus comes out and I'm quite happy with it.
The only problem is that I can't get Google Music beta running on the device.
I already checked a few apks from the forums and Music 3.0.1 is running fine - but it doesn't connect to my Music beta Account. Has anybody a solution for this is at least the same problem.
Further information: I live outside the US and i can't simply download the Music apk from the Market, but it was never a problem to get it to run on my other Android devices and several different ROMs on every device.
Thanks for helping!
Sent from my HTC Wildfire S A510e using Tapatalk
After a few suggestions from the App-Thread itself didn't work (like cache cleaning, de- und reinstall, disable app information syncing, ...) a factory reset did the trick for me.
When setting up the phone again I just installed the music app first (!!!) and - tataaa.... - the "settings"-option appeared.
So - my advise to all those with similar problems. Setup your music app first (!) when you set up your phone because in case of problems you may need to factory reset your whole phone.
Hope that helped someone...
Related
Hi,
From this morning when I try to open the Market it will say loading for about a minute then come back with a "network error has occurred" like it cannot connect and then it will close the Market when I select 'cancel'
Tried the following to try fix it / determine where the problem is...
- reboot
- Have 3G / WIFI connectivity to browse etc so it is not connectivity.
- Factory / data / ext wipe
- Tried diff rom's Leedroid / Open Desire
- I am based in South Africa so thought it might be a Market enabler issue - tried that
- Then thought it might be my Google account so setup another one, logged in but got the same error!
- Formated the SD card
None of this has helped
Any more idea's...any suggestions will be hugely welcomed.
Russ
Dont worry its a worldwide event. Its like all planets alligned or something to take Android market down for almost everyone.
iFoggy said:
Hi,
From this morning when I try to open the Market it will say loading for about a minute then come back with a "network error has occurred" like it cannot connect and then it will close the Market when I select 'cancel'
Tried the following to try fix it / determine where the problem is...
- reboot
- Have 3G / WIFI connectivity to browse etc so it is not connectivity.
- Factory / data / ext wipe
- Tried diff rom's Leedroid / Open Desire
- I am based in South Africa so thought it might be a Market enabler issue - tried that
- Then thought it might be my Google account so setup another one, logged in but got the same error!
- Formated the SD card
None of this has helped
Any more idea's...any suggestions will be hugely welcomed.
Russ
Click to expand...
Click to collapse
PHEW!!!!
Thanks man, should of asked the ? before going through all that pain and stress
Yup, my market is down too.. Sucks
Sent from my T-Mobile myTouch 3G Slide rooted cm6 using XDA App
Same here market down in asia
Down too, in Spain
Apparently twitter is going crazy about it http://www.google.com/search?q=andr...1&sa=X&ei=b2NvTP-OE8HhnAfd763mBw&ved=0CAwQpwU
cant get apps market on my phone but can get it on my computer in double twist. weird. i am in the us.
It's back up!
Mine was down for a few hours (vodafone uk), now its up again but not working fully, the 1st page just says something like no matches found in market... when i click on apps or games its very limeted, even if i go to my downloads and click on something popular like facebook for android, it opens then click more apps by developer and its not there, no apps at all, even searching for popular qpps like facebook doesnt give the official release, still seems like ite not working 100%
Sent from my HTC Desire using XDA App
Still cannot see some installed apps in the Downloads. Recently updated ones.
Got an issue with the market it starts but when I go to my apps or downloads it gives a server error and cancels.
I am using the latest market update which has been working OK but the last 2 days when I go to "My Apps" to check for updates I get the following:
"A Server error has occurred. Retry or cancel and return to previous screen"
Anybody else seen this, tried rebooting several times makes no difference, holding off doing a hard reset too many apps installed would have to reinstall them all again.
Not being able to backup like winmobile a real pain in the ass. I know I can use Mybackup Pro but it never seems to get the restore correct there always some none functional apps after the restore
I'm having the same problem here from Trinidad...
Sent from my HTC Desire using XDA App
I'm having the same problems too, maybe due to the imminent market upgrade?!?!? I have no idea?!?!
It's up for me (12 hrs)
Sent from my HTC Desire using XDA App
it stopped working after i switched roms from juggernaut to beast mod! But then when i switched back to jugernaut it still wont work. Before i went back to jugernaut the second time i went back to stock completely i thought if i did that it might help as i rerooted etc....it was just working less then a day ago.
Heres my problem i install app and then i enable my google account to go with it and then i press play and then it buffers for like 10 sec and then it just stops. Doesnt FC it just stops while my Google music screen just sits there, its not frozen.
I checked volume, not the problem
Audio Galaxy streams just fine, thats not the problem
Google music will play a file off my ext card just not my streaming library
I tried clearing data, nope, uninstalling it, using diff versions none of this works!!!
As this is one of my most used apps! any help would be greatly appreciated!!!!!!!
Heres the fix to this solution! When ever u install a new rom or do a fresh wipe of windows 7 it authorizes a new user to ur music beta account but u can only have 8 accounts open to ur account!! So i went into music beta settings on my pc and look at my account and thats what it was i had 8 open already! just deauthorize a few and now its working like brand new!!
Just a tip for u guys!! enjoy
Hi there, i got desire HD with Android Revolution HD 7.0(2.3.5 (Gingerbread) + Sense UI 3.5 )
and i got some questions.
1. I have installed CurrentWidget in order to check on my battery and i set the log correctly but the application is not making any log ? Do i need to keep it running or its running by it self?
2.I got Samsung ue55d8000 TV and i connected it to my wireless AP(phone also connected to it) and Samsung Remote cant seem to find it?
ps. Connection works on TV and on phone.
ok i fixed the samsung problem, it was firmware upgrading to new got it working.
anyone for this current wig. ?
If you have any task killers exclude Cur. Widg. from it, and be sure to actually place the widget on the home screen.
Goto Curr.Wid from Settings-> apps. Clear the data and force close. then restart the application. probably this might work.
canabi 1859
ok i kinda fixed it dont know how
one some more questions coming
3. ok after cleaning my antenna contacts i get better gps reception i can fix on 7-9 sats. in like less then 30seconds, but when i keep start walking(was in park trees only 500m around me clear no buildnings) i start losing sats one by one.
i installed igo my way 8.4.3.179971 put maps on it and everything else i started it and i got fix on my location but when i started walking (same in park) it says gps lost and gps off.
So my question is this rom related problem or hardware or even application?
4. How can i force phone to install applications on Sd card?
try GPS fix given from android revolution thread....
Sent from my Desire HD using XDA App
i tryed was working good but then i found
this thread
http://forum.xda-developers.com/showthread.php?p=17081413
done that and now seems to be working much better
Hi guys
Need some help troubleshooting an issue.
LG G3 running Android 4.4.2 stock from LG/provider.
Since I got the phone 2 months ago I have been unable to stream media from my home media servers (PS3 media server/Plex). (yes other devices can stream from them)
Using the Android gallery they just show as empty. Using media house I can see everything but when I want to play something it just stays at the connecting screen.
Even if I kill the app my phone gets extremely hot and I experience extreme battery drain until I restart the phone.
Using my phones media server I am able to stream to other apps.
Questions:
1. I have done a lot of googling and only found one other person with this problem with no replies, has anyone experienced this before?
2. What sort of troubleshooting/logging can I enable/view on my device, or how can I diagnose this problem.
Thanks in advance and sorry if I left out any necessary info.
Regards,
I think this question suits better for the developer of said app. You can email the developer, email information is on the Gplay page.
I will try the app developer but I don't know how much they will need able to help as the problem is not limited to their app
Hi!.
I've been having this annoying problem with Galaxy Wearable app for the last three days where the app crashes on launch every time. I've been trying to fix it all this time and i have tried different remedies that didn't help at all. I haven't the slightest clue what's wrong and i don't know where to ask for help so i figured i ask for it here first. I'll post a logcat if anyone is willing to help.
Here's what i've tried so far:
1. Cleared cache - Didn't fix the issue
2. Cleared storage - Didn't fix the issue
3. Complete reinstall of the Wearable app and services - Didn't fix the issue
4. Removed the Samsung account - Didn't fix the issue
5. Resetting the watch and setting it back up again - Didn't fix the issue
6. Tried 3 and 5 together - Didn't fix the issue
7. Did a clean install of ROM (Havoc 2.8) - Fixed the issue but it came back in about an hour
9. Rolled back to the previous build of Havoc (2.7) - Same as above, problem came back after some time
10. Dirty flashed 2.8 - Same
11. Restored to 2.8 and uninstalled a bunch of apps that i thought might be clashing with the Wearable app - Didn't fix the issue
ANY help would be much appreciated. I'm starting to think something is wrong with the watch itself.
EDIT: Never mind, i found what's going on. It's Samsung Pay that's making the app crash. I uninstalled it on a whim and now it works!!! Mods, kindly delete this thread.
How much memory your phone got? Try to close all other apps and then try. I have the same behave with other apps on my Moto phone.
Helhound0 said:
Hi!.
I've been having this annoying problem with Galaxy Wearable app for the last three days where the app crashes on launch every time. I've been trying to fix it all this time and i have tried different remedies that didn't help at all. I haven't the slightest clue what's wrong and i don't know where to ask for help so i figured i ask for it here first. I'll post a logcat if anyone is willing to help.
Here's what i've tried so far:
1. Cleared cache - Didn't fix the issue
2. Cleared storage - Didn't fix the issue
3. Complete reinstall of the Wearable app and services - Didn't fix the issue
4. Removed the Samsung account - Didn't fix the issue
5. Resetting the watch and setting it back up again - Didn't fix the issue
6. Tried 3 and 5 together - Didn't fix the issue
7. Did a clean install of ROM (Havoc 2.8) - Fixed the issue but it came back in about an hour
9. Rolled back to the previous build of Havoc (2.7) - Same as above, problem came back after some time
10. Dirty flashed 2.8 - Same
11. Restored to 2.8 and uninstalled a bunch of apps that i thought might be clashing with the Wearable app - Didn't fix the issue
ANY help would be much appreciated. I'm starting to think something is wrong with the watch itself.
EDIT: Never mind, i found what's going on. It's Samsung Pay that's making the app crash. I uninstalled it on a whim and now it works!!! Mods, kindly delete this thread.
Click to expand...
Click to collapse
Yep had the same exact problem the other day after upgrading to Android 10. There's another thread in here where I found the same issue (it's throwing a java ClassNotFound exception on mine). It's especially nefarious because they sideload the pay plugin so you won't see it if you're uninstalling via the play store, and it's not sorted alphabetically with the other Samsung apps so you might not even see it if you're searching manually.
I say nefarious because depending on how bad the crash is (background task vs UI), they may not be able to even push an automatic fix since they're not using the play store. Seems like a pretty terrible approach to me.
Sent from my Pixel 2 using Tapatalk
oxygenes said:
How much memory your phone got? Try to close all other apps and then try. I have the same behave with other apps on my Moto phone.
Click to expand...
Click to collapse
I got 3 gigs and not even half of it being used at idle. And i don't really do memory intensive stuff on my phone anyway. The issue was definitely Samsung Pay. if anyone has this issue where you're running Pie and are rooted with any version of magisk, uninstall Pay. It's been a few days and i haven't had this issue repeat even once.
shmaque said:
Yep had the same exact problem the other day after upgrading to Android 10. There's another thread in here where I found the same issue (it's throwing a java ClassNotFound exception on mine). It's especially nefarious because they sideload the pay plugin so you won't see it if you're uninstalling via the play store, and it's not sorted alphabetically with the other Samsung apps so you might not even see it if you're searching manually.
I say nefarious because depending on how bad the crash is (background task vs UI), they may not be able to even push an automatic fix since they're not using the play store. Seems like a pretty terrible approach to me.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
I just uninstalled Pay from the app list in settings and rebooted. If there is a sneaky sideloaded plugin somewhere, it doesn't seem to be interfering with the Wearables app anymore.
And I guess you're right about this being a terrible approach. But Pay isn't even supported where i currently live so my question is WHY even sideload it on a device being used in an unsupported region... Such a waste of resources.