This afternoon, I received a notification that I had an update for Adobe AIR. When I attempted the update, it stuck on "Downloading," with the progress bar flashing but not downloading. I ran the usual steps through the grinder (cleared Google Play cache, did likewise to Google Services Framework, deleted and readded my Google account information, and rebooted the Fire), but no luck. I even did a full sdcard wipe, reinstalled the newest gedeROM with 4/29 Google Apps, and still nothing. I was convinced it was my Fire having a compatibility issue, but now my Samsung Galaxy Tab 2 7.0 and Asus Transformer TF300T are doing the exact same thing!
Is there a current Google Play Store outage/update in progress that's not being reported? I know Gmail and YouTube were having issues awhile ago.
I googled for this issue and came across your post and another one here: http://forum.xda-developers.com/showthread.php?p=27165478
Anyway, I'm having the same or similar issue on my Galaxy SII. I'm not seeing many other complaints online so it doesn't seem to be a widespread issue. And I think it's just over wifi for me. I can't test it too well because I exceeded my 5GB of data this month so I'm throttled to terrible edge speed.
---------- Post added at 07:04 PM ---------- Previous post was at 06:57 PM ----------
A minute after posting my reply it randomly started working again. YouTube and Google Play, both working ok over wifi.
Related
I get textsall throughout the day, then, my sms app must think it is like 6 hours ahead, and starts marking the messages according like. Like:
Me: --- 2:01
them:-- 2:02. but shows 5:02 as recieved.
I downloaded the timestamp fix app but it lags my phone. How can I correct this issue? I am on Synergy No GM atm.
Does that same issue happen when using different ROMs or only this current one?
I had this issue on CM7 and have it on a Mikrom also. Tryin 2.55 mik to see if that changes.
---------- Post added at 07:47 AM ---------- Previous post was at 07:46 AM ----------
will also try r3charged to see if that happens. Annoying problem.
Well, it jsut started happening randomly on synergy. I had it for about a week, and then incorrect timestamps. I haven't flashed any other ROM as of yet. Any suggestions on what to try? I am thinking MIUI but should I test it on another sense rom?
I have been having intermittent issues with my GPS but its getting worse. I am currently running Bonestock v2.0.2 but this has happened on other ROMs as well. Didn't use GPS enough while it was stock to know if it was an issue or not. Here is what is happening:
Some apps that use GPS including Google Maps, Car Dashboard Pro, etc will say that GPS is disabled. Google Maps will actually pop up and say its disabled and gives me the option to cancel or go to settings. If I go to settings, everything is checked implying GPS is indeed enabled. Yet Maps still says its disabled. Occasionally Maps will work for a minute and then just randomly lose the GPS signal. This was a huge PITA as I was on a 7 hour drive for a Job interview and kept losing my GPS signal. After about two hours and 4-5 reboots on the road, it finally stayed on for the rest of my trip.
Today, due to the snow storm in MI, I had to pick up a coworker on my way to work. Used Google Maps on my phone because I didn't know where he lived. It worked just fine. Dropped him off after work and tried to use Google Maps again to get out of his convoluted neighborhood, and it gave me the GPS disabled message and 2 hours later after a few reboots, and I still cannot get it to work.
Software info:
Android 4.3
Sense 5.0
Bonestock 2.0.2
Baseband 1.12.42.1104
Let me know if you need any other info off the phone to help diagnose. Any help is appreciated. For the record, I did full wipes while flashing new ROMs. This has been an issue on at least three different ROMs.
I have no experience with Bonestock but on my stock ROM the Google location settings are in a different Google Settings app and not directly controlled by GPS enable/disable. I had so many problems with Google Maps I switched to a couple of other alternatives. Have you tested to see if you have the same problems when using another app such as Osmand or Locus?
lalec said:
I have no experience with Bonestock but on my stock ROM the Google location settings are in a different Google Settings app and not directly controlled by GPS enable/disable. I had so many problems with Google Maps I switched to a couple of other alternatives. Have you tested to see if you have the same problems when using another app such as Osmand or Locus?
Click to expand...
Click to collapse
I have not tried other navigation apps, but I have several apps that use the GPS signal and they dont work either. Car Dashboard Pro provides street information and speed, but can never find satellites. I just checked the google settings app that I had tucked away in folder, but that says everything is enabled as well.
kaverorzi said:
Are you running the newest firmware on the phone?
Click to expand...
Click to collapse
How can I find out?
You said your baseband is 1.12.42.1104, but the newest one is 1.12.41.1112_2.
Update your radio and your phone should work flawlessly.
---------- Post added at 01:13 AM ---------- Previous post was at 01:10 AM ----------
Use this page to update your radio to the latest version.
http://forum.xda-developers.com/showthread.php?t=2485319
The download link to the file is http://www.androidfilehost.com/?fid=23269279319196812
im_high_tech said:
You said your baseband is 1.12.42.1104, but the newest one is 1.12.41.1112_2.
Update your radio and your phone should work flawlessly.
---------- Post added at 01:13 AM ---------- Previous post was at 01:10 AM ----------
Use this page to update your radio to the latest version.
http://forum.xda-developers.com/showthread.php?t=2485319
The download link to the file is http://www.androidfilehost.com/?fid=23269279319196812
Click to expand...
Click to collapse
I had heard bad things about the newest OTA radio which is why I went with 1.12.42.1104. But the problem was occurring even before I flashed 1.12.42.1104, so I really don't think its the problem.
I just flashed 1.12.41.1112_2. So, we will see what happens.
ezflip said:
I had heard bad things about the newest OTA radio which is why I went with 1.12.42.1104. But the problem was occurring even before I flashed 1.12.42.1104, so I really don't think its the problem.
I just flashed 1.12.41.1112_2. So, we will see what happens.
Click to expand...
Click to collapse
SO did you fix the issues?
Honestly, I don't remember. This was 2 years ago. I've been through 4-5 phones since then. I will say, the M7 was probably the worst phone I've owned in recent years. I only used it for a few months before dumping it.
My G3`s compass not work can help?
My compass also seems not to be working. I noticed in Google Maps, the arrow that's supposed to point in the direction of travel was wrong. In GPS Test Plus, the headings are either zero or seemingly random. Oddly, I downloaded a compass app, and that appears to work OK. Strange.
I tried clearing the data in Maps, but no change.
Is this a hardware problem? Anyone else experiencing this?
---------- Post added at 04:24 PM ---------- Previous post was at 03:33 PM ----------
A bit more info... I don't think this is really a compass problem - - at least not for me. The incorrect heading in GPS Test Plus comes from GPS, not the compass. So the issue is with GPS.
Looking for some help, with WiFi Calling.
Tried three different locations
-Home Uverse - 18 Mbps
-Friends House - 24Mbps
-Work - Verizon 6Mbps
The call connects perfectly, and I can hear the caller but the caller can't hear me.
Any ideas?
What do you have installed on your phone
AWESOME G3
BACARDILIMON said:
What do you have installed on your phone
AWESOME G3
Click to expand...
Click to collapse
Stock Software
Rooted
G3 Tweaksbox - (Visual changes only)
Looks like T-Mobile is having issues with their WiFi Calling servers yet again. I had this same problem for months on the Note 3 until I complained and they opened a master trouble ticket and fixed it on their end.
I guess their servers are glitching up again.
xtentual said:
Stock Software
Rooted
G3 Tweaksbox - (Visual changes only)
Click to expand...
Click to collapse
Just made a few calls on WiFi calling and it all works. Sorry bro best I can do is say uninstall xposed and reboot and check.
AWESOME G3
Wifi range sucks on this phone probably phone thinks u far away and looses signal even though it shows strong bet if u close to router it will work but if u walk away it will lose signal and show connected.I dont know if a new modem or build will fix this.
Mine works fine
Not sure what the issue was, but ended up reverting back to stock.
I then re-rooted, and tested Wi-Fi Calling prior to, and after all major changes. End result....phone that is setup exactly the same, with the same apps etc...and Wifi Calling is still working.
They had a new update today thats supposed to fix some bugs with wifi calling
I've had the same issue. Most calls go through fine but probably 10% connect and there is no audio. I have to turn off WiFi and or reboot the phone to make calls correctly.
mobilelingual said:
I've had the same issue. Most calls go through fine but probably 10% connect and there is no audio. I have to turn off WiFi and or reboot the phone to make calls correctly.
Click to expand...
Click to collapse
Had that happening on my Note 3. Reported it on their forums and they opened a master trouble ticket, had someone contact me to take down my info (router make, model, firmware version, phone firmware version, settings, etc.), and two days later it started working properly - apparently it was an issue on their end.
I suggest you post on their support forum with a detailed description of your problem and the steps you tried to remedy it so far.
Mine has this issue about 30% of the time. ..no rhyme or reason Must just be another "you get what you pay for" related issue. I'm actually going back to Verizon on the M8 sometime tomorrow
---------- Post added at 10:09 PM ---------- Previous post was at 10:06 PM ----------
I've had Verizon for about 10 years up until about a week ago. It's been way too frustrating since switching. Sure, I'll save about $30/month with T-Mobile, but I'll have to put that $30 towards Ativan and Clonadine prescriptions if I stick with them.
My experience with T-mobile's unpredictable service quality has been a nightmare. Can't do it anymore.
---------- Post added at 10:11 PM ---------- Previous post was at 10:09 PM ----------
Plus the M8 looks BAD ASS!!!
Would like to ask if anybody experienced the issue "fingerprint hardware not available"?
There's a thread in z5 forum:
http://forum.xda-developers.com/xperia-z5/help/fingerprint-hardware-available-t3354800/page11
but seems liker a common problem for whole z5 series...
There are several possible solutions there but nothing works for me. And there is no clear symptom, when is occurs...
Perhaps can anybody share experience?
I have this problem too, im on latest romaur and with the aur kernel and i loose the fingerprint Thing after about 30mins after a reboot. I also get an video error from Youtube so i vant watch videos
Goto google player service and disable body sensor from permission, if the problem persists then downgrade google play service to stock.
kiritoxda said:
Goto google player service and disable body sensor from permission, if the problem persists then downgrade google play service to stock.
Click to expand...
Click to collapse
Didn't help and Google Play services gets updated automatically again...
I have recently been having the same issue while running v4.1 of ROMAUR, I never upgraded to v4.2.1 and it got considerably worse in the last two weeks. Initially it would happen once or twice a month but then, like you, I started experiencing it every 30 minutes and nothing would solve that issue.
For over a week now I have not had that issue, that is because I have gone back to a stock ROM of 253 and used a stock kernel that simply has recovery and drm fixes. I am rooted and running xposed, problem is with Auras work, whatever he is doing to his ROM is breaking the functionality of the sensor.
Sent from my E6853 using Tapatalk
Mobfigurz said:
I have recently been having the same issue while running v4.1 of ROMAUR, I never upgraded to v4.2.1 and it got considerably worse in the last two weeks. Initially it would happen once or twice a month but then, like you, I started experiencing it every 30 minutes and nothing would solve that issue.
For over a week now I have not had that issue, that is because I have gone back to a stock ROM of 253 and used a stock kernel that simply has recovery and drm fixes. I am rooted and running xposed, problem is with Auras work, whatever he is doing to his ROM is breaking the functionality of the sensor.
Sent from my E6853 using Tapatalk
Click to expand...
Click to collapse
I doubt that, because I had been using Romaur 4.2.1 since a while and the sensor worked fine for a really long time until about 2 weeks ago.
Can you share your Google Play Services version?
CrisperNeO said:
I doubt that, because I had been using Romaur 4.2.1 since a while and the sensor worked fine for a really long time until about 2 weeks ago.
Can you share your Google Play Services version?
Click to expand...
Click to collapse
I do not doubt it, I have seen first hand that it was an issue when I was running ROMAUR and now I am not having a single issue. I updated all my apps, including Google apps via apkmirror, so the same Play Services was running on both ROMAUR and my stock 253, yet not a single issue on stock, so explain that one.
Sent from my E6853 using Tapatalk
---------- Post added at 12:26 PM ---------- Previous post was at 12:23 PM ----------
Oh yeah, when I rebooted my phone on stock, it actually boots back up first time, does not act up and loop either like it did on ROMAUR and I have all the same apps running, including Xposed and Viper.
Sent from my E6853 using Tapatalk
Just to report back:
In another thread in Z5 forum (http://forum.xda-developers.com/showpost.php?p=68299976&postcount=165) there was a solution proposed, and it works for me so far:
Try renaming these files on /system/etc/firmware/
tzwidevine.b00 -> tzwidevine.b00.bak
tzwidevine.b01 -> tzwidevine.b01.bak
tzwidevine.b02 -> tzwidevine.b02.bak
tzwidevine.b03 -> tzwidevine.b03.bak
tzwidevine.mdt -> tzwidevine.mdt.bak
Then reboot.
Click to expand...
Click to collapse
This seems really to be fix. Havent got the fingerprint problem ever since (should have already had several times, based on the experience in the last weeks). It also solves the youtube video issue.
In addition I found a thread on this on Z2 forum: http://forum.xda-developers.com/xper...t3290793/page2
Seems to be a bug regarding unlocked bootloader or similar. Don't know what the files really do. But based on knowledge that people solved this with newer .253 ROM and kernel (rootkernel), perhaps SONY has already done something there. Perhaps anybody can check his .253 ROM?
Anyway, thanks to @depotjam.