I've had the M for about a month, and everything seems to work fine, except for the Spectrum Puzzles app. It force closes before even loading the puzzle. I've uninstalled and reinstalled, and can't think of anything else to try. I've contacted the developer and he's stumped. He says he hasn't encountered anyone else with this problem. The same app worked fine on an Incredible, a Note II and a S3. Now I'm worried it's my phone. Ideas? (Unrooted, running Apex launcher.)
Related
Hey, so I've just encountered a pretty strange problem with my browser when running on wifi. When using either Dolphin HD or the stock browser, it just hangs and never really loads anything, but all other apps that require internet (facebook, tweetdeck, etc.) still work just fine. When using 3G both browsers also work just fine. This problem only started occurring today, don't know what I could have done to have cause something like this to happen but I'm pretty stumped on how to fix it. Any ideas?
(Running on Azure 1.0.1)
kill all tasks and try again
Nah I power cycled the phone a few times and no dice. The issue is resolved now actually, although I have no idea how or why it came up, nor do I know how it got fixed. Some strange fluke I guess.
Ok hell, I have no idea what's going on but I'm having more problems with this again, and now it's happening to the browser while using either wifi or 3g. Browser stops working, yet other internet requiring apps still work. I feel like this might have something to do with chrome-to-phone/foxtophone cause it tends to happen after I've used it. Anyone else experiencing this?
Same happens to me, its really random. I'm running Azure 1.0 any help would be much appreciated.
Greetings. I have a Motorola Xoom and when I run Netflix, the first time it looks fine. After that, When I run it again, the Netflix menu looks huge and I cannot really navigate around it. The only way to fix the problem is to either clear the Netflix cache and data every time before I use it (requiring me to log back in each time), or installing version 1.3 (which then annoyingly prompts me to upgrade every time I launch it).
Does anyone else have this problem? Is there a fix?
Nobody else has this problem? Really?
I run Netflix on Xoom quite often but I don't have the problems you describe. My issues are usually with the app locking up and needing to force close it and restart. It was definitely running much better in the older versions.
I have the exact same problem, but I can't solve it even if I clear the cache. It's somehow showing the "stretched" phone UI instead the tablet UI. It's just unusable now.
Same problem here.....it went away for awhile, but it is back. Even tried facotry reset, didn't work.
I was able to install an HD version on Xoom running ics ROM
http://forum.xda-developers.com/showthread.php?t=1394637
May fix your problem but I doubt it. This should just change the buffering.
I had netflix issues too with honeycomb. It wouldn't even load to even log in.
Flashing the EOS nightly ICS rom fixed it.
What I did is uninstall find version 1.3 install that and visit the market it sees the old version and updates it.
Working fine now.
I have 1.3 if you need it I think but its the one found in xda forums
Sent from my MZ604 using xda premium
Hello everyone. I've done a few searches on here but haven't found this exact problem. Relevant details without extra background info are in bold.
My wife and I each got an S4 with Sprint's recent BOGO promotion. My phone has had no issues. It came with MDL in the box, which I updated to MF9 via OTA, flashed TWRP via Heimdall in Linux, rooted, and installed the hotspot mod.
Her phone - completely stock MF9 and new from the store - has had problems, one of which I've so far been unable to fix. (How I wish it were mine. I develop for Android, but this is much more of a pain for her.) Hers already had MF9 at the store. It had the Google Services Framework/Core Apps runaway process issue with heat/battery drain from the start - which I fixed. However, it also has unresponsive sensors for ~3 seconds when receiving a call. It's almost as if there's some lag in activating the sensors. The phone is otherwise snappy with no other lag noted.
- Hard reset has been tried.
- The touchscreen is unresponsive during this time, though the display functions.
- The gesture for answering (when enabled) also does not work.
- We haven't tried enabling the home key to answer, but this will be next.
I've seen this before with Android a good while back. It was an inherent problem with Gingerbread on many phones. Haven't seen it pop up in Jellybean at all. In trying to diagnose, I've ensured that all bells and whistles are turned off. No air gestures are on.
We'd really like to get it working as it should. Has anyone else experienced this? Any advice?
Many thanks!
I believe this is more of a stock software issue. I have had the issue since day one.
When I turned off svoice and some of the other added features most of the lag disappeared. Svoice is pretty good at creating lag as far as ive seen.
Voice response seems to create th lag as it is awaiting a voice command from you.
This is what I have noticed anyway.
Sent from my SPH-L720 using xda app-developers app
So I had the WatchESPN & NBCSports Live Extra apps working just fine on my AT&T S4.
Ever since I updated to 4.3 they won't launch at all. Both apps crash immediately on launch.
I've tried clearing the cache etc and uninstalling/re-installing but no joy.
Has anyone else experienced issues with these apps?
Does anyone know how to get any kind of clue as to what might be causing this?
The phone is not unlocked or rooted.
How do I debug what's going on? I'm pretty new to Android. I can't root the phone since it's a work-owned device.
Amazon Alexa app crashes in all custom ROMs I have tried. I have tried clearing cache, uninstalling, etc, etc. but the same bad behavior remains. Runs fine if I revert to stock. Anyone else run into this?
Same here. I am on newest lineageOS.
Yep, that is my experience as well.
I use the alexa app on my stock tablet and have removed it from custom roms on my phone.
Haven't found a workaround yes but would appreciate one.
Works fine here on Dirty Unicorns on 3 devices and SAOSP on another.
Try turning off cellular data when trying to use the app. Any problems I have had with the Alexa app have been solved with this, doesn't seem to work well with it.
chibichuba said:
Try turning off cellular data when trying to use the app. Any problems I have had with the Alexa app have been solved with this, doesn't seem to work well with it.
Click to expand...
Click to collapse
Will try that tonight. Thanks for the idea.
I will post my results.
At least I am not alone in this.
The regular pre conversations app works for me on all devices, however it does not when I add a phone number. Basically I have a problem with the new conversations. It starts to load I get all icons then a faint conversations label and then it crashes. I have tried almost all ROMs available for my moto x pure, no exaggeration. I am using DU at the moment and it does not work. Amazon thought it may be that I did not have an activated SIM card and had no data. So, I purchased and activated SIM card after having phone for almost 2 years and data does not help. Turning data off changes nothing for me as well. My sons phone is a samsung stock and his SIM card has never been activated but it works fine.
I also have been having troubles with TP-Link Kasa the most recent update is causing it to act the similar. It simply ignores my sign in. I have come to conclude their is a security validation check being used by amazon and tplink.
This kind sucks...I don't know why certain apps does this. Android was built on open source however I notice slowly they are closing Windows/doors.
Alexa app crashing solved for me!
Whenever I would hit the listen button the app would crash, if this is one of your symptoms try turning off notifications, it worked for me, found the answer in a post for Miui phones.
Ime using MaxiCM(CyanogenMod-Mod) on 5.1.1 and for me it crashed as soon as i logged in and it got Internet, using the App offline works fine but yea, no use for it.