I did the whole manual update to Lollipop, unfortunately, my phone keeps searching for GPS when I use apps that need it.
The problem is I like to use a boating app, and I go far enough offshore that I do not get data. Btw, I get this issue with any app that needs GPS, including Pokemon Go!
After searching online, it appears to be a bug in Lollipop itself.
Either downgrade, of go to Marshmallow if I can find a decent daily driver.
Anyone else have similar issue?
leroadrunner said:
I did the whole manual update to Lollipop, unfortunately, my phone keeps searching for GPS when I use apps that need it.
The problem is I like to use a boating app, and I go far enough offshore that I do not get data. Btw, I get this issue with any app that needs GPS, including Pokemon Go!
After searching online, it appears to be a bug in Lollipop itself.
Either downgrade, of go to Marshmallow if I can find a decent daily driver.
Anyone else have similar issue?
Click to expand...
Click to collapse
My Mate2 did the same thing...mostly after google updated a bunch of stuff. Just started doing it about a month or so ago.
Haven't touched it (all stock) in about a week. Got my new Mate8 about 4 days ago
"Searching for GPS" bug, might need to downgrade to KitKat
Try this:
http://forum.xda-developers.com/showthread.php?p=68572626
See post 35!
More details of my experience in that thread. Wife just pre-ordered an iPhone 7, probably out of pity, for me. One day I showed her my Google Maps and set it to drive home. No sound, no directions, but it quickly discerned origin and route home, when we got home it said "you have arrived," but the map, even though the pointer updated position throughout the drive, still showed the route line from the origin!
Sent from my iPad using Tapatalk
I've never had this issue on any ROM
Found a workaround
I was experiencing exactly the same issue! Not only that but it seems like this issue has popped up on reddit and latest amazon reviews too. Seems to have started occurring after July of this year for many people. I haven't determined the root cause, but it seems like it's affecting too many people to be a hardware issue. Some things I tried that DIDN'T work:
* Flashed latest Cyanogen snapshot, although I like it a lot more than stock
* Tweaked the /system/etc/gps.conf file for my region
Finally I found that my phone time significantly drifted off atomic time, noticed it could be a whole second off. After reading online about GPS technology, it seems having an accurate client atomic time should improve GPS performance. I used an app called ClockSync (with root is easier) to make sure my time was accurate and turned off syncing time with cell tower. It worked!! Using a GPS testing app (GPS Status & Toolbox) I can lock on to my position reliably in < 10 seconds. This is still running on Cyanogen.
I'm in love with this phone, so happy I don't have to buy a new one.
fenwaysnow said:
I was experiencing exactly the same issue! Not only that but it seems like this issue has popped up on reddit and latest amazon reviews too. Seems to have started occurring after July of this year for many people. I haven't determined the root cause, but it seems like it's affecting too many people to be a hardware issue. Some things I tried that DIDN'T work:
* Flashed latest Cyanogen snapshot, although I like it a lot more than stock
* Tweaked the /system/etc/gps.conf file for my region
Finally I found that my phone time significantly drifted off atomic time, noticed it could be a whole second off. After reading online about GPS technology, it seems having an accurate client atomic time should improve GPS performance. I used an app called ClockSync (with root is easier) to make sure my time was accurate and turned off syncing time with cell tower. It worked!! Using a GPS testing app (GPS Status & Toolbox) I can lock on to my position reliably in < 10 seconds. This is still running on Cyanogen.
I'm in love with this phone, so happy I don't have to buy a new one.
Click to expand...
Click to collapse
I tried to install CM13. I failed miserably. Then I started by playing the Pokémon Go game and observing the erratic character movement. Then played with the GPS settings. Turning off High Accuracy and leaving on Device Only still is working, except inside structures that block GPS signal. Tried High Accuracy while visiting San Francisco this last weekend and started having issues there, so back to Device Only for me.
Thank you for sharing what has worked for you!!!!
Sent from my MT2L03 using Tapatalk
I found the latest Cyanogen snapshot I tried (cm-13.0-20160823-SNAPSHOT-ZNH5YAO0M5-mt2) too unstable. I started to experience random reboots every day, even while using Google maps turn-by-turn navigation. Restored back to official lollipop build (MT2-L03C00B322) from my backup (that was factory restored before backing up). Now it's suddenly working without any workarounds! I have no idea why it's working now. If you are considering dumping your phone for a new one, you could try a factory reset first to make sure it's not a hardware issue. :/
---------- Post added at 05:26 AM ---------- Previous post was at 05:19 AM ----------
jzchen said:
I tried to install CM13. I failed miserably.
Click to expand...
Click to collapse
It was definitely not straightforward, I ran into several issues. First, TWRP recovery was complaining about invalid file system format so I switched to Cyanogen recovery to flash system. Second, I was getting constant Google services has crashed messages. Found out I needed to install it right after, before rebooting first. Third, I was stuck in boot-loop during Cyanogen startup. A hard reset finally fixed it.
fenwaysnow said:
I found the latest Cyanogen snapshot I tried (cm-13.0-20160823-SNAPSHOT-ZNH5YAO0M5-mt2) too unstable. I started to experience random reboots every day, even while using Google maps turn-by-turn navigation. Restored back to official lollipop build (MT2-L03C00B322) from my backup (that was factory restored before backing up). Now it's suddenly working without any workarounds! I have no idea why it's working now. If you are considering dumping your phone for a new one, you could try a factory reset first to make sure it's not a hardware issue. :/
---------- Post added at 05:26 AM ---------- Previous post was at 05:19 AM ----------
It was definitely not straightforward, I ran into several issues. First, TWRP recovery was complaining about invalid file system format so I switched to Cyanogen recovery to flash system. Second, I was getting constant Google services has crashed messages. Found out I needed to install it right after, before rebooting first. Third, I was stuck in boot-loop during Cyanogen startup. A hard reset finally fixed it.
Click to expand...
Click to collapse
That's a lot to deal with!!!
As of yesterday I am back to High Accuracy, and just as you note everything seems fine, particularly with regards to GPS.
I guess if I want to have Android 7, I'll save up for a phone that comes with it, unless I learn how to manually do it myself. (I was once a CECS major, about 16 years ago...)
Thank you again for sharing your experience! I hope we can all go back to enjoying our exceptionally large screens....
Sent from my MT2L03 using Tapatalk
Related
I have only tested this on the CM9 nightlies, so if you decide to try it on anything else, make a backup beforehand and report if it works for you.
Do you want Google Now on your HP Touchpad? Of course you do. I have been following this thread for a while waiting to get Google Now on my ICS phone.
http://forum.xda-developers.com/showthread.php?t=1747224
XDA member cajunflavoredbob has been keeping a post updated with the latest flashable zips. So keep checking back for the latest one here:
http://forum.xda-developers.com/showpost.php?p=29756226&postcount=2856
I have used these files on my phone and got Google Now working for me. I decided to try the same thing on my TouchPad and it is still a bit buggy but worked pretty well. Voice search and talk back all worked (still buggy though). Just flash in CWR. I dont know if there is any easy way of removing it. So make a backup of your ROM just in case you want to revert back.
I started from a fresh flash of CM9's most recent nightly and then flashed Google Now v6.zip. I was able to get Now working a few times for searches but since have received the "double take" bug that does not automatically set a time reminder etc. After a couple attempts, pressing the MIC button shows an "initializing" screen and does not function.
I've read through his post several times over looking for a fix via permissions, disabling voice actions, etc, but have not been able to get it working 100%. What is your status with it on your TP?
suasponte 375 said:
I started from a fresh flash of CM9's most recent nightly and then flashed Google Now v6.zip. I was able to get Now working a few times for searches but since have received the "double take" bug that does not automatically set a time reminder etc. After a couple attempts, pressing the MIC button shows an "initializing" screen and does not function.
I've read through his post several times over looking for a fix via permissions, disabling voice actions, etc, but have not been able to get it working 100%. What is your status with it on your TP?
Click to expand...
Click to collapse
I think we're on the same page. When it works, it works well. But it still has small bugs. Pressing on the mic in the search bar seems to work better. But at least every feature is there now. A step closer.
Yeah, I'll keep my eye on that thread. I switched around a couple of the updated velvet.apks since there were a few floating around, stated as working, to no avail but I will continue to test fixes. Any bets on whether his Google Now fix or a stable CM10 for the TP is released first?
OP updated with link to latest files.
I'm using reeko's zip, it fails on first try about half the time but when i retry it works pretty much always, if not i retry again lol
I did install the google voice search from app store after flashing the zip. I set the mic to go to this voice search, and pressing the word google brings up google now. So I have one that always works, and one that kind of almost always works.
I'm using the online only version of the zip, I don't know if the offline would need to initialize to google server or if it would work without failing
I havent even tried the offline version. But it sounds like they have similar issues. When you say you retry, do you hit the mic icon or the actual word "Retry"?
either one, or both
i just tested it, it works with doing either, it really is hit or miss it seems. around 15-20% success rate sometimes. I mean I hit retry/mic (depending on how bored i am) and I can do this around 10 times before getting it to work once. Then other times I can get it to work 3-4 times in a row before failing again
edit: from what I can tell (or what it looks like to me) hitting retry, retries in the app. hitting mic relaunches app? i say this since i see it kind of jump, like the entire app relaunched quickly. So my take is if this launch didnt work, i hit mic to relaunch it and hope this time is a bit better
eyeb said:
either one, or both
i just tested it, it works with doing either, it really is hit or miss it seems. around 15-20% success rate sometimes. I mean I hit retry/mic (depending on how bored i am) and I can do this around 10 times before getting it to work once. Then other times I can get it to work 3-4 times in a row before failing again
Click to expand...
Click to collapse
I kinda have a feeling one of the older files worked better.
If you get bored, try this file out. This was the first one I came across but havent gotten around to flashing it back to see if it was better.
https://www.box.com/s/78f4efb985d94487d5d5
I am also hitting about 10%. Whether or not I hit mic or reset. I play with the settings, changing language and what not and it seems to reset it. But still hit and miss...
Same. Im running CM9 nightly 8/07, tested flashing every G Voice rom and the same error occurred with each one. I came across a post saying G Now only worked with a specific ICS rom, but I cannot find that particular post anymore nor a post on the main thread with a CM9 TP confirming G Now is working.
I'm also having problems getting G Now to work properly on the HP Touchpad with the latest nightly build.
Only thing that is buggy which today for me stopped working altogether is the voice search.
Anyone figure out how to fix this yet?
I'm not a developer but shouldn't it be possible to get G Now working for CM9? Since it is running ICS.
It would be awesome to get Voice working.
Hi - My post count is not high enough to ask this question in the CM10.1 thread.
I've installed cm-10.1-20130304-EXPERIMENTAL-fireball-M2.zip and gapps-jb-20130301-signed.zip successfully and most everything seems to be working well except for Google Navigation.
After selecting a destination, it correctly shows my location, determines the route, draws the map and shows route. However, as soon as I begin to drive it freezes and the app stops responding requiring force close.
I don't think it's the GPS since GPS Status, Zillow, c:Geo and even Google Maps all work OK tracking me while I drive.
All I've tried so far is to uninstall/reinstall Google Maps and cold boot.
Any suggestions?
Thanks
I just noticed you said your running the experimental M build. I'm running the nightly from that sane date and nav works just fine.
Sent from my Incredible 4G LTE using Tapatalk 2
MJL99 said:
I just noticed you said your running the experimental M build. I'm running the nightly from that sane date and nav works just fine.
Sent from my Incredible 4G LTE using Tapatalk 2
Click to expand...
Click to collapse
i'm running the m snapshot and GPS works fine.also there is a new gapps package available, which you have I see
I can definitely attest to experiencing this problem on multiple occasions. I haven't put a whole lot of thought or effort into troubleshooting it yet, as I was more inclined to restart my phone and restart navigation so that I don't miss my turn as opposed to sitting there and trying to test various scenarios to see what causes the issue. Without any serious level of troubleshooting, i think the only helpful information that I can bring to the table is that I have only noticed it while the phone is charging in the car. It doesn't happen every time (maybe 20% of the time), but when it does happen, the screen freezes immediately upon the screen flying into the proper position on the map.
smtrekkers said:
Hi - My post count is not high enough to ask this question in the CM10.1 thread.
I've installed cm-10.1-20130304-EXPERIMENTAL-fireball-M2.zip and gapps-jb-20130301-signed.zip successfully and most everything seems to be working well except for Google Navigation.
After selecting a destination, it correctly shows my location, determines the route, draws the map and shows route. However, as soon as I begin to drive it freezes and the app stops responding requiring force close.
I don't think it's the GPS since GPS Status, Zillow, c:Geo and even Google Maps all work OK tracking me while I drive.
All I've tried so far is to uninstall/reinstall Google Maps and cold boot.
Any suggestions?
Thanks
Click to expand...
Click to collapse
read the OP IN development cm 10,1 workarounds, gps fix is there
Shot in the dark. Did you try force closing the maps app and clearing the data and cache of the app then restarting it. I've had this fix problems for apps in the past. Worth a shot.
Sent from my Nexus 7 using xda app-developers app
Thanks for all the suggestions. I'll try a nightly build to see if that fixes it. I'll also try running it while not charging - so far it's also been on the car charger. As I mentioned, the GPS works fine, so the GPS workaround didn't seem to be needed. I did try the force close and clear data/cache.
I did find a working workaround by googling the issue. Apparently it's not uncommon across various phones and Adnroid versions. I couldn't find a fix though.
The work around that works is to set Nav to use 'North Up'. You do that by hitting the little compass symbol on the top left while in nav. It was tricky to hit it quick enough before freezing, but I got it. Thankfully that setting sticks for future nav requests. I get no crashes/freezes when I use it North up. As soon as I switch it back, it freezes. Odd. At least I can use it, but would still be good to find the cause and fix.
somerandomname1 said:
Shot in the dark. Did you try force closing the maps app and clearing the data and cache of the app then restarting it. I've had this fix problems for apps in the past. Worth a shot.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yeah I'd recommend just using a different nightly. I could not replicate this problem with and without a charger on Thursday.
Sent from my Incredible 4G LTE using Tapatalk 2
Same problem. I have wiped, reflashed a dozen different nightlies, and still have the same problem. It works fine in every other rom I try, either Viper or stock. Every cm10.1 causes this problem. I am using the workaround posted above(north up), but it is annoying.
Waze works well, also.
My wife has the same phone, same setup, and hers works fine.
I have yet to experience this issue with CM10.1 and I regularly flash the "sudo" nightly builds posted by mdmower on goo.im.
That said, for those experiencing this issue:
- Did you a full wipe/facotory reset before flashing to the new rom?
- Did you make sure that all your location services were turned on before flashing to the new rom?
-- If you didn't enable all location services before flashing the new rom, I strongly encourage you to flash to a sense rom and follow the instructions provided by mdmower on the CM10.1 thread in the development section.
Good luck!
retrostudd said:
I have yet to experience this issue with CM10.1 and I regularly flash the "sudo" nightly builds posted by mdmower on goo.im.
That said, for those experiencing this issue:
- Did you a full wipe/facotory reset before flashing to the new rom?
- Did you make sure that all your location services were turned on before flashing to the new rom?
-- If you didn't enable all location services before flashing the new rom, I strongly encourage you to flash to a sense rom and follow the instructions provided by mdmower on the CM10.1 thread in the development section.
Good luck!
Click to expand...
Click to collapse
Yes, full wipe and factory reset.
Yes, all 3 location services are on.
GPS locks fine. It works with north up in Maps, and with Waze, and with any other rom. Just not cm10.1
smtrekkers said:
Hi - My post count is not high enough to ask this question in the CM10.1 thread.
I've installed cm-10.1-20130304-EXPERIMENTAL-fireball-M2.zip and gapps-jb-20130301-signed.zip successfully and most everything seems to be working well except for Google Navigation.
After selecting a destination, it correctly shows my location, determines the route, draws the map and shows route. However, as soon as I begin to drive it freezes and the app stops responding requiring force close.
I don't think it's the GPS since GPS Status, Zillow, c:Geo and even Google Maps all work OK tracking me while I drive.
All I've tried so far is to uninstall/reinstall Google Maps and cold boot.
Any suggestions?
Thanks
Click to expand...
Click to collapse
Why are you using such an old nightly? Step up from M2 to the RC. The only issue I've had with the RC is a minor audio problem that has a workaround in place.
Sum Dumb Guy said:
Why are you using such an old nightly? Step up from M2 to the RC. The only issue I've had with the RC is a minor audio problem that has a workaround in place.
Click to expand...
Click to collapse
It's with every nightly, including M2 and RC1.
scottyb96 said:
It's with every nightly, including M2 and RC1.
Click to expand...
Click to collapse
I've been using mdmower's unoficial CM10 releases for a couple weeks and haven't had any google issues. Where have you downloaded your zips?
http://goo.im/devs/mdmower/fireball-cyanogenmod-oc
Sum Dumb Guy said:
Why are you using such an old nightly? Step up from M2 to the RC. The only issue I've had with the RC is a minor audio problem that has a workaround in place.
Click to expand...
Click to collapse
That post was from March when that nightly was current. The later versions didn't fix it either. The issue still exists for me, and I've just been living with the North Up workaround. I suspect it's not something CM10.1 specifically, but that was a contributing factor as it worked before the ROM switch. I think there have even been Google Maps app updates since the issue started that didn't fix it.
With the new kernel version of cm10.1 becoming available, I did a full wipe and fresh install with the 7/1 nightly, and I still have the maps issue. Living with the North Up fix for now.
scottyb96 said:
With the new kernel version of cm10.1 becoming available, I did a full wipe and fresh install with the 7/1 nightly, and I still have the maps issue. Living with the North Up fix for now.
Click to expand...
Click to collapse
cm10.2 from mdmower fixed this problem for me. Navigation works flawlessly now. Reverting back to 10.1 reproduces the issue.
I've finally hit a breaking point with Maps 7.x. Has anyone else still been having problems with it, or better yet, not had problems with it?
This is a video showing some of the problems I've been seeing. Most noticeable is the jittering glitches. If I'm driving around, the screen is unreadable for directions or street names. At the end is a screenshot I took of a completely glitched out warning prompt to tell me "please enable wifi and mobile network to improve accuracy" though you'd never be able to guess that.
http://www.youtube.com/watch?v=yMAVZnMx3m8
I'm running Infection 2.9.1, and I've tried several kernels (ROM default, Hiro, and Funkybean) and switched up the governors and schedules, and nothing has seemed to work. I've tried disabling/enabling hardware overlays. I'm just at a loss, and hoping someone out there knows more than I do. I just finally had it because it's cool enough outside to run now without getting heat stroke, and Endomondo (my running app) freaks out and loses signal 5 steps into a run. Downgrading to Maps 6.x makes everything happy. Is sticking with the old Maps still the best solutions for this?
Is there any more information that I can provide to eventually get this resolved?
nu Maps stinks on Rezound
I unwisely installed the new Maps from Google Play Store.
It forgot my Favorite places and cached location. Experienced
poor location finding and not-fun routing to locations.
After hating it for a week, I searched for Maps 6.14.4.apk
and installed it with Root Explorer. I am very glad to have
a good working version of Maps running again now.
dbighead77 said:
I've finally hit a breaking point with Maps 7.x. Has anyone else still been having problems with it, or better yet, not had problems with it?
This is a video showing some of the problems I've been seeing. Most noticeable is the jittering glitches. If I'm driving around, the screen is unreadable for directions or street names. At the end is a screenshot I took of a completely glitched out warning prompt to tell me "please enable wifi and mobile network to improve accuracy" though you'd never be able to guess that.
http://www.youtube.com/watch?v=yMAVZnMx3m8
I'm running Infection 2.9.1, and I've tried several kernels (ROM default, Hiro, and Funkybean) and switched up the governors and schedules, and nothing has seemed to work. I've tried disabling/enabling hardware overlays. I'm just at a loss, and hoping someone out there knows more than I do. I just finally had it because it's cool enough outside to run now without getting heat stroke, and Endomondo (my running app) freaks out and loses signal 5 steps into a run. Downgrading to Maps 6.x makes everything happy. Is sticking with the old Maps still the best solutions for this?
Is there any more information that I can provide to eventually get this resolved?
Click to expand...
Click to collapse
To be honest google has been messing up alot of things for the Rez lately and maps being one of them....no matter what kernel you are on or what rom you are on its not gonna fix this maps issue...personally i prefer waze as it is not only free on google play but just works alot better and are even more up to date than google maps....plus it has many cool features like it lets you know if theres a cop or accident up ahead...also to note theres a gps test app out there that gives you a much better lock on your gps so it wont loose its signal as much
I have the same flickering issue until I close the app and reopen it. Seems to work fine after that.
Hello,
Been using that rom for some time now, but still no luck with my Pebble. I realy use it, and get used to it. Now it almost 75% of the time is disconected. I tried everything. Previously on 4.4.2 I had no issues. But I wanted the new 5.0
I tried to write there in the gooh topic, but nonone seemed to care about it. and with the speed of 20 posts per hour, my question was fast lost in the conversation. Maybe someone else from the comunity had simmilar issue? Any advice will be greatly apriciated.
Bart
qasq said:
Hello,
Been using that rom for some time now, but still no luck with my Pebble. I realy use it, and get used to it. Now it almost 75% of the time is disconected. I tried everything. Previously on 4.4.2 I had no issues. But I wanted the new 5.0
I tried to write there in the gooh topic, but nonone seemed to care about it. and with the speed of 20 posts per hour, my question was fast lost in the conversation. Maybe someone else from the comunity had simmilar issue? Any advice will be greatly apriciated.
Bart
Click to expand...
Click to collapse
I have been having pebble connectivity issues, and I believe it's just rom compatibility because it's been an issue with all lollipop roms for me. This is what I did to fix the issues.
1. Uninstall the pebble app
2. Unpair the watch on both the phone and the watch
3. Install the app
4. Login and follow the instructions, pairing the watch using the app.
5. Make sure that notifications are turned on for it and that it is not greenfield.
6. Go in to settings, device, accessibility, make sure it's on
7. Go in to settings, sounds and notifications, notification access, enable it.
8. If a watch face is not updating (weather), switch to another face and then switch back.
I have found that restoring the app via Titanium Backup/Rom Toolbox, creates some issues too. Installing the app fresh from the market seems to be the most reliable.
MyNarwhalBacon said:
I have been having pebble connectivity issues, and I believe it's just rom compatibility because it's been an issue with all lollipop roms for me. This is what I did to fix the issues.
6. Go in to settings, device, accessibility, make sure it's on
restoring the app via Titanium Backup/Rom Toolbox, creates some issues too. Installing the app fresh from the market seems to be the most reliable.
Click to expand...
Click to collapse
Acctually I had it installed from TitBack!, also I'm not sure about Accessibility option (if it was or not) for now it works, but I'll see for how long.
Another issue is (was before too) that any notification are coming always doubled. That's sick
qasq said:
Acctually I had it installed from TitBack!, also I'm not sure about Accessibility option (if it was or not) for now it works, but I'll see for how long.
Another issue is (was before too) that any notification are coming always doubled. That's sick
Click to expand...
Click to collapse
I am glad it works for you, for now!
This not a ROM, but a kernel issue. Had a similar problem with my Xiaomi Mi Fitness Band. It would only connect reliably after I flashed Civato 3.5 kernel.
Sent from my SM-N910F using Tapatalk
Hi forum!
I have a good ol' galaxy tab 10.1. And it's horrible. Super slow, Chrome won't run, constant "unfortunately ___ has stopped", for some reason Hangouts keeps attempting to run and stops. It's pretty close to unusable. Is it possible to save it?
I'm a newb (I've rooted and installed custom roms in the past, but nothing in the last 3 years or so, so I'm pretty much back to start).
Details:
Android version 4.2.2.
kernel 3.1.10-cyanogenmod
AOKP p4wifi_unofficial_Mar-16-13
The reason I haven't bought a new one is because I use it so infrequently. I've got the S7 and it does just about everything I need, but every once in awhile it would be nicer to have a bigger screen. So I don't really want to go out and spend hundreds of dollars on a new tablet if I can salvage this one for the rare occasion I use it. The reason I dragged it out this time was to edit a video, so it would be nice if I could do that (powerdirector doesn't support this version). Beyond that it would probably just be a movie player for road trips with the kid... Or if anyone has any other suggestions what to do with it, I'm open!
Any help is greatly appreciated! I'd hate to see it go!
No, never let go I've got 7.1.1 Nougat running well with the latest update. A bit laggy but not too much, and stable so far.
The trick is it will autoupdate to an incompatible version of Google Play services (and some other gapps) - unless you take the right steps as shown in this thread (check the first 2 posts and the last few pages of posts).
https://forum.xda-developers.com/galaxy-tab-10-1/development/rom-android-7-0-nougat-t3471350
NB The gapps recommended in the orig post wouldn't flash for me. I used open_gapps-arm-7.1-pico-20170119.zip
from
https://github.com/opengapps/arm/releases/tag/20170119
Once you stop autoupdates in Play Store and roll back to the last compatible versions of some major google apps, it runs great for most ordinary purposes. My Sygic app is working properly again too.
Sure it's a bit of work and it was a bit confusing for me working out how to get the right version of Google Play services installed, but I found it very rewarding and worthwhile. There's a couple more of its nine lives yet imo. Was a great choice of tablet.
(I can't speak for hangouts though; I don't use it.)
rubbercorners said:
No, never let go I've got 7.1.1 Nougat running well with the latest update. A bit laggy but not too much, and stable so far.
The trick is it will autoupdate to an incompatible version of Google Play services (and some other gapps) - unless you take the right steps as shown in this thread (check the first 2 posts and the last few pages of posts).
https://forum.xda-developers.com/galaxy-tab-10-1/development/rom-android-7-0-nougat-t3471350
NB The gapps recommended in the orig post wouldn't flash for me. I used open_gapps-arm-7.1-pico-20170119.zip
from
https://github.com/opengapps/arm/releases/tag/20170119
Once you stop autoupdates in Play Store and roll back to the last compatible versions of some major google apps, it runs great for most ordinary purposes. My Sygic app is working properly again too.
Sure it's a bit of work and it was a bit confusing for me working out how to get the right version of Google Play services installed, but I found it very rewarding and worthwhile. There's a couple more of its nine lives yet imo. Was a great choice of tablet.
(I can't speak for hangouts though; I don't use it.)
Click to expand...
Click to collapse
Well that's annoying - I subscribed to the thread but it never told me that someone was kind enough to reply!!
Well here's an update in case you're curious: I've bricked it. I tried to flash it back to stock and now it's stuck in a bootloop *sigh*
So, if I can ever get it out of that state I'll give your suggestions a try. Thanks so much for posting!
Holy crap I saved it! But it's runnig Android 3.2 LOL
So I'm going to see about getting JellyBam on there, it looks to be pretty stable.
I've just been trying to decide what to do with mine,
I have ASOP 5.1.1 but always get 'Google Play Services has stopped' so want to find a version that I can just put on and leave it on without having to do anythign too technical
Did you try the link that rubbercorners posted?
I'll take a look
LincolnElectra said:
Holy crap I saved it! But it's runnig Android 3.2 LOL
So I'm going to see about getting JellyBam on there, it looks to be pretty stable.
Click to expand...
Click to collapse
Did you end up giving up on it? I updated to a newer version of Nougat (same link I linked above) and it seems to have solved the Google Play Services crashing error. But you still need to use older versions of some apps, and Google Maps doesn't seem to work properly any more (I use Sygic navigation).
It also has some kind of 'Neon emulation' which slows down some apps.
Realistically, with this tablet, you have to be prepared to use workarounds for a bunch of things and for most people it's too much of a hassle, and very laggy with things like Google Now/Assistant or whatever it's called. I doubt you could use it for video editing, and youtube works at 480p max I think.
Having said that, I have it running well for what I use it for - Sygic navigation, occasional browsing, gmail etc. And I think it would run 720p movies okay if already downloaded (I haven't tried Netflix etc.)
I doubt running older ROMs like JellyBam would have any advantage over the latest Nougat (I could be wrong?). Surprisingly, Marshmallow and Nougat run less laggy than the older ROMs ever did for me (including the official ones).
I went with Jellybam but get an error with the keyboard AOSP so can't type anything at all
Now Google Play Services started crashing again. I will try to solve it again, but I might be getting to the point of just using this tablet for Sygic offline navigation.
*slaps myself for losing faith in my tablet*
The developer fixed Nougat again and it's working pretty pretty nicely for me (no Google Play Services crash). Remains to be seen whether anyone will try to get Oreo running on it (or if it's even possible), but I can see myself getting another year out of this ROM:
https://forum.xda-developers.com/galaxy-tab-10-1/development/rom-android-7-0-nougat-t3471350
If anyone tries it, note:
- read the first few posts of the thread carefully
- install using TWRP 2.8.7.0 if it fails using TWRP 3
- turn off autoupdates (see thread).
- if you have problems with Google Play Services crashing (it updated itself to 11.5.17 and is running fine for me), try to find a way to install one of the earlier versions recommended there - maybe install the earlier gapps (P7500-open_gapps-arm-7.1-pico-20170119.zip) and roll back/uninstall Google Play Services to the stock one if it autoupdates.
- there's an unfixable hardware bug where sometimes the battery drains with the power off. The workaround is to always shut down the tablet by rebooting into TWRP recovery and power off there. (This bug has apparently always been in this tablet, but it shows up more in later Android versions.)
- if tablet doesn't power up, hold the power button down for about 10 seconds
- I rooted using the phh SuperUser option (2 steps to this). Some people seem to be having trouble with the Magisk option.
seriously? ive had absolutely no issues with mine! I use it as a puzzle/game/ebook/reddit browser/ video player... nothing intensive and its a t-580 running 6.0.1 (Ultra Lean MM V6). Everything works (everything ive ever tried including magisk and xposed)...
Chiz511 said:
its a t-580...
Click to expand...
Click to collapse
That's the much newer Galaxy Tab 10.1 A - different tablet This thread is about the 6-year old original iPad challenger that it has become a point of pride to keep going.