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.
Related
My GPS worked out of the box when I got this phone last week but now it hasn't locked on all day. I am running the latest evil fascination ROM. Any advice?
Did you try wiping data, cache, and dalvik after install?
Sent from my SCH-I500 using XDA Premium App
I am having the exact same issue. I NEVER get a lock anymore - even leaving it on for 30 minutes....
I have been running various ComRoms with various kernels and radios and still the same unusable GPS. I have also played with GPS Aids, GPS Status, and some other ones. I have read all the various forum posts about this issue to. Still nothing.
Would really love to know if anyone has any new advice... I too am getting really sick of it not locking on at all.... it used to just be slow, now it's useless all together.
Similar issue on a i9000 galaxy S here. Question: do you all recall if prior to the issue appearing you upgraded the version of google maps installed? Or some other app?
goldohulk said:
Similar issue on a i9000 galaxy S here. Question: do you all recall if prior to the issue appearing you upgraded the version of google maps installed? Or some other app?
Click to expand...
Click to collapse
It was that damned Google Maps update after all! I stumbled into this: http://www.google.ru/support/forum/p...053f4eeb&hl=en
Uninstalled (the updates over the stock) Google Maps and presto: locked just fine!
try rebooting phone leaving gps on. you might want to look into a gps aid like gps booster. Since I have been running the powerwash rom, gps works better than ever.
I'll preface with this:
1. I am not a dev.
2. I don't intend to take credit away from any of the CM7 devs.
3. I don't intend to take credit for any of the solutions posted here.
I like to keep up with the main thread, but it has become a little unruly, with the same questions being asked and answered repeatedly. I was thinking we could keep this thread as something of a troubleshooting thread, with known problems and solutions in the OP, in an attempt to keep the main CM7 thread (here) a bit more organized for dev related stuff.
Mods, if this thread is in the wrong forum or inappropriate, feel free to deal with it accordingly.
OK:
----------
CM7 for Thunderbolt
Current Version: RC1.4 (MR2/2.5 Radio Only)
Merged to Mainline: No
Wipe Required: No if upgrading from RC1.2 or RC1.3 (although if you are having ANY problems, first troubleshooting step is to reinstall following a complete wipe). Yes if you are coming from ANY OTHER PREVIOUS VERSION OR ROM
Problems With Known Fixes
Problem:
I just installed CM7, where is the Market?!
Solution:
Not a problem, you just have to install gapps.
- Easiest way is to download and install through ROM Manager: Rom Manager -> Download ROM -> Google Apps.
- Alternatively, you can download and install manually. Link. Flash using Recovery.
Problem:
GPS is not getting a fix
Solution:
1. Be sure that you are on RC1.2, and that you did a full wipe prior to installing.
2. Backup CM7 in Clockwork Recovery.
3. Do a full wipe.
4. Flash a Sense based ROM, such as BAMF.
5. Boot into the Sense based ROM that you flashed in Step 4, and obtain a GPS fix.
6. While your GPS is locked, reboot to recovery. (Hold Power -> Reboot to Recovery)
7. Do a full wipe.
8. Restore the CM7 backup you made in step 1.
9. Boot into CM7. Your GPS should now be working.
Problem:
Inaccurate signal bars/I only have two bars on LTE
Solution:
FIXED ON RC1.3
Problem:
Non-GPS geolocation is (very) inaccurate
Solution:
wraithdu said:
The inaccurate non-GPS location can be fixed by turning on WiFi (does not need to be connected, just ON). Obviously a temporary fix, but works for me - I can get location now in Beautiful Widgets, SiMi Clock, The Weather Channel, and the browser. I increased my WiFi scan interval to 3 minutes to try and help battery. But it beats getting the weather for Guam.
Click to expand...
Click to collapse
Problem:
Choppy Netflix playback
Solution:
Netflix now has official Thunderbolt support. Install the updated Netflix App from the Market.
Problem:
Unlock lag and/or no backlit softkeys
Solution:
Turn off auto brightness, should take care of both of these issues. (thanks to Mustang302LX)
Problems With Fixes of Questionable Effectiveness
Problem:
Problems with in-browser flash
Solution:
chmod 000 /data/data/com.android.browser/app_plugins/com.adobe.flashplayer/.macromedia/Flash_Player/config.data
Varying reports of this working/not working
Problem:
Low volume
Solution:
Since perception of volume is subjective, it's difficult to say whether or not this is a true problem, and whether or not it's been fixed. Slayher has stated that it's been fixed since one of the earlier releases. Another possible solution is here (credit to utkanos), which has been used with varying results - again, volume perception is subjective.
Problem:
Included wireless tethering not working
Solution:
From what I've seen, you will be able to connect to the wireless network, but you will not be able to obtain an IP address. I have found that forcing an IP release/renew upon connecting generally takes care of this problem. On Windows, this can be done with the following:
1. Start -> Run -> "cmd"
2. ipconfig /release
3. ipconfig /renew
Problems Without Known Fixes
Problem:
Streaming audio over bluetooth is choppy
----------
OK, post problems (and fixes, if there are any) and I'll do my best to keep the OP updated in an attempt to keep the main dev thread more organized. When posting an issue, please include:
CM7 version
Kernel
Radio
Wipe
all aosp roms including gingerbread roms reads data strength instead of cellar radio strength. that's why it appears to have less bars. if you search there are mods i believe to give you the appearance of higher signal strength on the forums here.
cm7 and Netflix issues
I believe this is a CM7 issue, as it only happens with is rom and previous versions but I'm not sure if its FPS or just choppiness but Id like to get this fixed other fixes like chmod 000 have not worked.
On a different note I would like to thank everyone involved with CM7 its by far the best ROM.
Thank You Devs.
arkshel said:
I believe this is a CM7 issue, as it only happens with is rom and previous versions but I'm not sure if its FPS or just choppiness but Id like to get this fixed other fixes like chmod 000 have not worked.
On a different note I would like to thank everyone involved with CM7 its by far the best ROM.
Thank You Devs.
Click to expand...
Click to collapse
This is also true for embedded flash videos. If I use the chmod 000 it skips if I go above 360 but it works. Older versions don't let me go above 360 because the video menu, it just closes whenever I open it.
The one issue that bugs me the most about this ROM is that it does not find my location correctly. Not talking about GPS because that works perfectly, but how I'm found through the network does not work. Google Maps works perfectly at finding my location but apps like fancy widget and even google.com locate me in different places.
I live in Buffalo, NY but my phone insists I move frequently around the world. First I'm in Fort Wayne, IN, then Houston, TX, then Nairobi, Kenya, and sometimes in Lawndale, CA.
Something's wrong and no one seems to have a fix that'll work for me. I'm assuming that's cause no one cares about it because its so miniscule.
Tried different radios and GPS status but nothing has worked.
Fix? Slayher?
I am absolutely loving this rom, I flashed it on my girls Droid x and instantly had to have it on my tbolt. GPS works great, more than great, and no other issues except two things.
First, when streaming Pandora or slacker through bt the skip like crazy, but when played through the phones speaker they're fine. No big deal.
Secondly I must be doing something wrong because my battery life is terrible. I have an extended battery that the phone ate through in 8 hours moderate use. And my stock battery is dropping about 30% an hour...
I'm not a noob with screen time out to 10 mins and brightness all the way up, so its got to have something to do with my CPU settings. I'm using set CPU to over clock to 1450. Tried different goveners. I assume there's different kernels out there I'm gonna have to try out, what kernel is included? Running mr2 ota
Sent from my ThunderBolt using XDA App
Cm7. 2
Stock kernel
OTA radio
Full wipe
Volume is too low. Volfix. Zip hasnt worked for me. Otherwise Cm7 is flawless.
Yes i cleaned my ears.
Suggestions?
Thanks for this thread and to the devs for their work
Sent from my ThunderBolt using XDA Premium App
i flashed it and im running the mr2 radio. it didnt install the market and im not able to download another and it work properly. when i go into recovery and try to flash the market zip it aborts. anyone know how to fix this?
dearbeloved said:
i flashed it and im running the mr2 radio. it didnt install the market and im not able to download another and it work properly. when i go into recovery and try to flash the market zip it aborts. anyone know how to fix this?
Click to expand...
Click to collapse
What rom were you running before, and did you wipe?
In any case, easiest solution would be to install GAPPS from ROM Manager.
Can't seem to connect to my home wifi network. Anyone else experience this issue?
From looking through the main thread, saw one suggestion, which didn't work for me: post 7360
OTA MR2; full wipe; RC1.1; gapps; set up accounts; cache wipe; RC1.2
bliang said:
Can't seem to connect to my home wifi network. Anyone else experience this issue?
From looking through the main thread, saw one suggestion, which didn't work for me: post 7360
OTA MR2; full wipe; RC1.1; gapps; set up accounts; cache wipe; RC1.2
Click to expand...
Click to collapse
Try a full wipe before installing 1.2. I believe that was recommended by slayher.
Is it only your home wifi, or are you having trouble with all wifi connectivity?
problem: voice to text works intermittently and not at all with any background noise
corrective solutions taken that haven't corrected problem: installed talkback, kickback and google voice search.
CM 1.2
OTA radio
stock kernel
full partition wipe, also formatted SD prior to install
Let's merge our threads, yeah?
http://forum.xda-developers.com/showthread.php?t=1125466&highlight=CM7
joshnichols189 said:
Let's merge our threads, yeah?
http://forum.xda-developers.com/showthread.php?t=1125466&highlight=CM7
Click to expand...
Click to collapse
Yes! Sorry, thought I did a thorough search. Apparently not. Mods please merge.
Sent from my ThunderBolt using XDA Premium App
minazaki said:
Try a full wipe before installing 1.2. I believe that was recommended by slayher.
Is it only your home wifi, or are you having trouble with all wifi connectivity?
Click to expand...
Click to collapse
Didn't think it would matter. Did a full wipe and reinstalled -- everything working okay now. Thanks
Installed CM7 and purchased ROM Manager Premium. I enabled advanced mode in settings. But I still can't download Cyanogenmod ROMs via ROM Manager? It doesn't appear in the list. Anyone have a similar problem, and preferably a solution? What's going on? Thanks.
darknesis said:
Installed CM7 and purchased ROM Manager Premium. I enabled advanced mode in settings. But I still can't download Cyanogenmod ROMs via ROM Manager? It doesn't appear in the list. Anyone have a similar problem, and preferably a solution? What's going on? Thanks.
Click to expand...
Click to collapse
it's not officially supported by cyanogenmod yet, therefore you can't obtain it via ROM manger.
you can find CM 1.2 here: http://forum.xda-developers.com/showthread.php?t=1049542
make sure you download the ROM and the Gapps
Oh ok, thanks!
Sent from my ThunderBolt using XDA Premium App
darknesis said:
Oh ok, thanks!
Sent from my ThunderBolt using XDA Premium App
Click to expand...
Click to collapse
feel free to push the "thanks" button under my post
stayin100 said:
I am absolutely loving this rom, I flashed it on my girls Droid x and instantly had to have it on my tbolt. GPS works great, more than great, and no other issues except two things.
First, when streaming Pandora or slacker through bt the skip like crazy, but when played through the phones speaker they're fine. No big deal.
Secondly I must be doing something wrong because my battery life is terrible. I have an extended battery that the phone ate through in 8 hours moderate use. And my stock battery is dropping about 30% an hour...
I'm not a noob with screen time out to 10 mins and brightness all the way up, so its got to have something to do with my CPU settings. I'm using set CPU to over clock to 1450. Tried different goveners. I assume there's different kernels out there I'm gonna have to try out, what kernel is included? Running mr2 ota
Sent from my ThunderBolt using XDA App
Click to expand...
Click to collapse
I'm interested to know the answer to this battery issue. Which kernel is best for battery life/stability? I'm running stock right now, but I really haven't ran it long enough to get good usage stats.
An update to Google Maps was released in the last couple of days. After updating, when I open the app it crashes after a few seconds and reboots my tablet. Is anyone else seeing this behavior?
I'm on the cm9-p4wifi-20120511.zip ROM. Prior to this issue, the ROM had been completely stable for me. I wasn't planning on changing ROMs until an IC or JB ROM had a working camera, but now I'm thinking I might experiment just to get Maps working again.
Before I do that however, does anyone have any suggestions on getting Maps stable so I don't have to flash just yet?
Thank you.
Same here, Maps 6.10.0 crash few seconds after been loaded w/CM9 aug 15
You should do a wipe cache, erase data from settings >> app >> maps or probably you should change you kernel flashing a new one
I have also the same problem. Wiping cache changes nothing. I use cm9-p4-20120814.zip ROM.
Sent from my GT-P7500 using xda app-developers app
Same issue here on Ganbarou CM9.
isthisagoose said:
I'm on the cm9-p4wifi-20120511.zip ROM. Prior to this issue, the ROM had been completely stable for me. I wasn't planning on changing ROMs until an IC or JB ROM had a working camera, but now I'm thinking I might experiment just to get Maps working again.
Click to expand...
Click to collapse
I updated to the latest CM9 nightly last night, cm-9-20120819-NIGHTLY-p4wifi, and Maps is still crashing.
6.10 is buggy. I only updated it on my Sensation and it causes reboots when I use it, and causes reboots for Rezound users as well. Guess we all have to roll back or wait for an update.
Can anyone post the previous .apk? I haven't been good about keeping Titanium Backups, I admit.
Here's version 6.9.2 - http://goo.gl/4p2O9
thank you, 6.9.2 is OK, no crash.
new google maps 6.11 = same crashes.
back to 6.9.2.
p4wifi, update Maps to 6.11.1. Same problem. The crash occurs each time I enter an area that is cached for offline use, or when I try to modify the offline settings.... or after just a few seconds. Not only the app crashes (that would report the issue to Google, which could be useful), but it directly crashes the tablet (possibly a kernel panic, I have no console so no clue).
I'm having this issue with maps crashing my Samsung tab 10.1 AOKP milestone 6 and my Sensation running cyanogen 9 and when I flashed revolutionary rom with sense. I noticed on the sensation in location settings the GPS source was not checked off (cyanogen). After I chose internal source the problem stopped. There is not this option on the tablet AOKP so it still crashes. Not sure if anyone else is seeing this issue.
oopewan said:
I'm having this issue with maps crashing my Samsung tab 10.1 AOKP milestone 6 and my Sensation running cyanogen 9 and when I flashed revolutionary rom with sense. I noticed on the sensation in location settings the GPS source was not checked off (cyanogen). After I chose internal source the problem stopped. There is not this option on the tablet AOKP so it still crashes. Not sure if anyone else is seeing this issue.
Click to expand...
Click to collapse
Same problem here, with Galaxy Tab 10.1 P7500 on latest Ganbarou ROM. Current GMaps reboots the tablet after few seconds. I looked for GPS Source setting and it's present on Ganbarou ROM. However, it is correctly checked and problem still persists. Looks more like a kernel/driver bug invoked by GMaps, putting tablet into kernel panic.
galaxy tab cm9 maps crashes
I have this issue as well. Its a version conflict. You need to install v6? Or something like that. Anyone have the link? Its somewhere on droid basement i just havent found it
isthisagoose said:
An update to Google Maps was released in the last couple of days. After updating, when I open the app it crashes after a few seconds and reboots my tablet. Is anyone else seeing this behavior?
I'm on the cm9-p4wifi-20120511.zip ROM. Prior to this issue, the ROM had been completely stable for me. I wasn't planning on changing ROMs until an IC or JB ROM had a working camera, but now I'm thinking I might experiment just to get Maps working again.
Before I do that however, does anyone have any suggestions on getting Maps stable so I don't have to flash just yet?
Thank you.
Click to expand...
Click to collapse
Sorry if this thread already exists.
You have no idea how happy I am this ROM exists!! But I cannot get SMS working. I get FC's on every SMS app I try including Hangouts. Anybody else getting this and/or have a remedy? Thanks
I was about to post the same error here, I have an Amaze with Videotron, S-Off, Super CID, HBOOT-1.93.2222 (JuopunutBear), TWRP as a recovery.
I tried everything, I tried different Gapps, I also tried without installing Gapps, I tried sms apps from the Play Store and Hangouts too. The only thing I haven't tried is formatting my internal SD card. (it was a clean install, all formatted and cache cleared). I also tried switching to ART but I had the same problems.
Everytime I try to just open the sms apps, the app crashes. I managed to see the error once and it was something about SQL but it might be a misinterpretation from my part.
Calls, 4G and WiFi were all working perfectly too.
After some research on Google, I tried installing busybox, xposed framework and uninstalling Voice+, but nothing works. The basic messaging app just closes without any kind of message and other apps show that it stopped working.
(I tried the Evervolv rom 4.4 and SMS were working on that one, maybe it's a setting with my network type as I am on Videotron in Canada and it is using AWS, maybe a setting under *#*#4636*#*# ??)
I want to contribute and sen some log of that error, how can I do that? I am familiar with roms, kernels, etc but not that much with logs... I tried many roms before and never got that specific problem...
Thanks to anyone who can help with this issue!
It's not just you SMS simply doesn't work on this rom and I was surprised to see that no one else pointed this out in the original thread. The default Messaging app closes immediately when you try and open it. Other SMS apps also crash either immediately upon opening them, or when you try to send a message (hangouts & SMS Pro for example). This is the only thing keeping me from using this amazing rom as my DD.
I have the same exact problem with SMS- will try the evervolv 4.4 though was really looking forward to CM11
Edit: also didnt have any other problems with the rom except for the black boxes and the camera
Let's hope there is a way to fix it!
I would post the question in the official thread but I do not have enough posts to do so unfortunately
Heck I couldn't even try SMS due to the black box issue, that's why I didn't mention it in the original thread.
For those with the black box issue--are you using the correct gapps?
In olden days there were some issues with some google things not working, and people uninstalling the ones that came in gapps and downloading them fresh from the play store.
Have you gone into recovery and fixed permissions?
Again, in days of yore, this might straighten some things out.
Is it possible that black-boxing has something to do with CPU frequency, and is it possible to tweak up the speed through developer options and lose the boxes?
I haven't tried this rom yet, as I'm currently sticking with the stable(r) cm10.
Good luck.
anybody get the SMS working on this ROM so far?
pbergonzi said:
For those with the black box issue--are you using the correct gapps?
In olden days there were some issues with some google things not working, and people uninstalling the ones that came in gapps and downloading them fresh from the play store.
Have you gone into recovery and fixed permissions?
Again, in days of yore, this might straighten some things out.
Is it possible that black-boxing has something to do with CPU frequency, and is it possible to tweak up the speed through developer options and lose the boxes?
I haven't tried this rom yet, as I'm currently sticking with the stable(r) cm10.
Good luck.
Click to expand...
Click to collapse
The black box issue has nothing to do with GPU or CPU speeds. There are discussions on the dev threads. The issue affects other legacy devices on various KK based source builds, not just Amaze and CM. The consensus is this seems to be related to the default browser which has changed in KK. This would also explain why it effects other gapps too.
MS92 said:
anybody get the SMS working on this ROM so far?
Click to expand...
Click to collapse
Not that I'm aware of.
Media Issues
The ROM is pretty good for the most part.
I just have this problem where Play Music gives this error, "Cannot play the music track you requested"
I clear my media storage and try to rescan my SD card but none of the apps work. They all crash.
Is there anyway to fix this?
ranwal said:
The ROM is pretty good for the most part.
I just have this problem where Play Music gives this error, "Cannot play the music track you requested"
I clear my media storage and try to rescan my SD card but none of the apps work. They all crash.
Is there anyway to fix this?
Click to expand...
Click to collapse
Maybe app settings for the app and Erase App Data?
can i get a link for the updated adreno drivers? thanks!
865DETH said:
can i get a link for the updated adreno drivers? thanks!
Click to expand...
Click to collapse
Yes you can its on last three pages of orignal thread you also have to sign up for that
Sent from my HTC_Amaze_4G using Tapatalk
as the OP says and i quote that only non working things are
1. camera exposure
2. tethering
but as the thread goes ahead we read more prolems/bugs
May i ask what is the current status for bugs/not working and other issues and what has been fixed and any other stuff we should flash over the ROM like driver, may it be upoaded to the OP for ease as its reall hard to search for those things on mobile app. thank you and good luck.
Anyone else have issue disabling their microphone while in a call? I tried with both the speaker phone and regular handset mode, the "no mic" icon enables but my caller can still hear me. The Hold button seems to work fine though.
FYI, it took a while for the battery to figure itself out. I wiped the battery stats before flashing everything and the first few days I got a lot of jumping battery levels. I let it charge all the way down as much as I could then rebooted and did a full charge and rebooted again and then full charge again. That seemed to reset the battery level to the correct state.
I also , enabled Device/GPS only for the location detection other wise the google services at 50% or more battery.
I'm running the 2014-02-16 build, with the updated video drivers.
Camera is not working
I have also installed this pacman rom 4.4.2. all is well instead of camera.
Any updates for the camera isssue??
Shahxz said:
I have also installed this pacman rom 4.4.2. all is well instead of camera.
Click to expand...
Click to collapse
Since PAC uses the CM device tree for its source any issues with CM will also be evident in PAC. Until the CM devs are able to resolve the camera exposure issue it will exist in both ROMs.
Librastar said:
Any updates for the camera isssue??
Click to expand...
Click to collapse
Think about your question for a minute. Have you seen any recent posts in the CM dev thread indicating an update which solves this issue? If you had just taken a moment to look at the dev thread instead of posting this you would have answered your own question. It's not like the CM-11 thread is incredibly long, it's only 28 pages total. This post is just laziness on your part and an unnecessary waste of bandwidth.
is there any alternate app in the market, i tried couple of apps but nothing useful
@Odysseus1962
If I were to compile AOSP, which variant would you suggest for me to build?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
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