Database Info

[Q][Solved] Problems on Nexus S i9023

As the title suggests, I have a Nexus S i9023 (no root, perfectly clean) and the major problem is that i've upgrade the phone to ICS manually and now there are some things that don't work (recovery, light sensor, etc.). I know that there are a lot of threads like this, i know that the problem of the recovery is a problem of brightness, but i wanna know which ROM i've to flash. I'm using the build IML74K.
Another problem is that sometimes the keyboard freezes. Is it caused by the wrong build?

Which rom did you flash?
Try lastest version of ics

I'm using ICS 4.0.3, build IML74K, flashed manually.
Sent from my Nexus S using XDA App

alfax21 said:
I'm using ICS 4.0.3, build IML74K, flashed manually.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I am using the same on my i9023 with no issues, only difference is I am rooted and have clockwork recovery. I suggest a re flash.

I'll try to re-flash the same ROM. If it won't work i'll root the phone and i'll flash CM9.
Anyway, how can i solve the problem of the keyboard? I don't think it's a problem of the build.

I've flashed the ROM for Nexus S i9023 two times but the problems still remain. Any suggestion?

alfax21 said:
I've flashed the ROM for Nexus S i9023 two times but the problems still remain. Any suggestion?
Click to expand...
Click to collapse
Only thing I can suggest is installing clockwork recovery, rooting etc and flashing another rom to see if the problem persists, if so then it probably a hardware issue.
Also where did you get the rom your flashing? There is a thread in the general section with the full rom package I used. Its on the first page at the mo.

Ok maybe there's no solution (i'm new in this forum so i can't post link as the one below):
code.google.com/p/android/issues/detail?id=23065&can=1&q=ics%20nexus%20s%20i9023%20recovery&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars
So I think it will be fixed in the next release. I ask confirmation if someone knows something.

CONTACTMC said:
Also where did you get the rom your flashing? There is a thread in the general section with the full rom package I used. Its on the first page at the mo.
Click to expand...
Click to collapse
Yeah, i've seen it. This one, right?
forum.xda-developers.com/showthread.php?t=1445635

alfax21 said:
Yeah, i've seen it. This one, right?
forum.xda-developers.com/showthread.php?t=1445635
Click to expand...
Click to collapse
Yeah that's the one, flash the full rom package. You may just have a corrupt .zip.

Alredy done two times, but the problem remains. Mmmh i don't think it's a corruption problem, i mean, i've tried to put the update in the phone from two PC.
Sent from my Nexus S using XDA App

Recovery: Known problem. Backlight stays off. Nothing you can do without unlocking your bootloader or rooting. Angle + lamp will show you what is on the screen.
Light Sensor: It's still buggy. With the phone locked, cover your hand over the light sensor (left of the ear piece while facing the phone). Hand still covering, unlock the phone. After a few seconds, remove your hand and face it under a light source. What i've noticed is it'll get brighter initially but refuse to darken again. Of course, you need to have Automatic brightness adjustment (just in case it isn't set to auto).
Unsure about your keyboard problem though, but it does like to stay open for longer than i'd like after going back to the home screen.

Harbb said:
Unsure about your keyboard problem though, but it does like to stay open for longer than i'd like after going back to the home screen.
Click to expand...
Click to collapse
Yeah, it remains open also after going back to the home screen, and it doesn't work. The only way is to crash it by going to the setting of the keyboard in the notifications.

alfax21 said:
Yeah, it remains open also after going back to the home screen, and it doesn't work. The only way is to crash it by going to the setting of the keyboard in the notifications.
Click to expand...
Click to collapse
Mine doesn't remain open though,. It just stays for say half a second, then animates away. Would be much more perfected if it went away while animating the previous window away, not a second later. I've not experienced the keyboard causing those kind of problems.
Might be wise to try SwiftKey or some other kind of keyboard alternative? That is easily enough to sway me away from stock.

Harbb said:
That is easily enough to sway me away from stock.
Click to expand...
Click to collapse
I agree. I'll wait for an Experimental Mod of CM9, then i'll root the phone.

Ok i'll make the thread as solved. I want to thanks Harbb for his help, i quote his post for those who will read this thread.
Harbb said:
Recovery: Known problem. Backlight stays off. Nothing you can do without unlocking your bootloader or rooting. Angle + lamp will show you what is on the screen.
Light Sensor: It's still buggy. With the phone locked, cover your hand over the light sensor (left of the ear piece while facing the phone). Hand still covering, unlock the phone. After a few seconds, remove your hand and face it under a light source. What i've noticed is it'll get brighter initially but refuse to darken again. Of course, you need to have Automatic brightness adjustment (just in case it isn't set to auto).
Click to expand...
Click to collapse
If you have problems (like the recovery one and the light sensor) with ICS 4.0.3, build IML74K, on your Nexus S i9023 there's nothing you can do, probably Google will fix it on his next update 4.0.5.

I'll just add that many custom ROMs allow light sensor manipulation. I hear there are great, working settings, its just the stock calibration that sucks. I've not tried this myself, but should be available in cm9, cna, etc.

..

Election Day said:
This is how I have my i9023 set up. These settings work very well, so feel free to use them.
Click to expand...
Click to collapse
Are these settings of the stock ROM?

..

Screen won't rotate, would root/flash help?

Hi all,
just bought an Inspire off CL, and unfortunately didn't reallize that the screen won't rotate. I trired recalibrating, but it kept being aborted even though I put the phone flat on the table on its back. A search turned up tons of complaints from about a year ago with few resolutions, and none worked for me (reboot, recalibrate, kill all apps with adv task killer, switch sim card, etc.)
So the big question is, would rooting the phone and flash custom rom solve the problem? Has anyone solved the problem with the g-sensor?
Sent from my NookColor using Tapatalk

Is the phone rooted? Some roms have customizations to lock the screen and keep it from rotating. Do any screens rotate? Or is the home screen just not rotating?
Try going to home> settings> display and check auto rotate screen.
Sent from Soundwave aboard Nemesis.

Auto-rotate is checked. Apps the should rotate (e.g. Google search, email) don't rotate, and most frustrating is that games that use the g-sensor just won't work. The phone is running stock Gb 2.3.3.
Sent from my NookColor using Tapatalk

fishline said:
Auto-rotate is checked. Apps the should rotate (e.g. Google search, email) don't rotate, and most frustrating is that games that use the g-sensor just won't work. The phone is running stock Gb 2.3.3.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
If not rooted I would root and try a custom rom would hurt nothing. But make sure you use Ace Hack Kit and no out of XDA method. Also read, read, then read the Effen manual and make sure your knowledged on the steps for rooting. If you get stuck anywhere there is an IRC chat connection in the Ace Hack Kit page.
The thing about buying used phones from someone else is like buying a used car. Your basically buying some elses headache.
The other option would be to return to seller for money back, your option.
PS: If you decide to try out a ICS ROM remember that the kernels are not fully released as of yet so some games will not fully work and do have a few bugs depending on how it reacts with your phone. For gingerbread I would try a few out and see which one you like.
(Absolution 3.7 , Coredroid 9.4) lol my preference but thats a can a worms you dont want to open here on XDA by asking which is best ROM so dont.
Welcome and Enjoy the learning.

Ok, so all the reading made the rooting process seem somewhat intimidating. However, when I actually screwed up the courage to do it, it was like, that's it? It's donde in under 5 minutes, and I hardly did anything!
So the good news is that the phone is now rooted and flashed with coredroid (looks nice!). The bad news is that there's no change in the problem with the g-sensor! I'm starting to suspect that it's more likely hardware. In any case, I wonder if there are any Roms that might have a better shot at fixing the problem? Somehow I have the probably wrong impression that a custom rom that's modded from stock aren't likely to fix my problem... Any suggestions?
Sent from my SAMSUNG-SGH-I777 using Tapatalk

fishline said:
Ok, so all the reading made the rooting process seem somewhat intimidating. However, when I actually screwed up the courage to do it, it was like, that's it? It's donde in under 5 minutes, and I hardly did anything!
So the good news is that the phone is now rooted and flashed with coredroid (looks nice!). The bad news is that there's no change in the problem with the g-sensor! I'm starting to suspect that it's more likely hardware. In any case, I wonder if there are any Roms that might have a better shot at fixing the problem? Somehow I have the probably wrong impression that a custom rom that's modded from stock aren't likely to fix my problem... Any suggestions?
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Click to expand...
Click to collapse
Yeah, if you had a sensor problem before the root and it persists after, it is more then likely a hardware issue and no amount of rooting/flashing a new ROM is gonna fix it. If you're under warranty, unroot and send it back for a replacement.

fishline said:
Ok, so all the reading made the rooting process seem somewhat intimidating. However, when I actually screwed up the courage to do it, it was like, that's it? It's donde in under 5 minutes, and I hardly did anything!
So the good news is that the phone is now rooted and flashed with coredroid (looks nice!). The bad news is that there's no change in the problem with the g-sensor! I'm starting to suspect that it's more likely hardware. In any case, I wonder if there are any Roms that might have a better shot at fixing the problem? Somehow I have the probably wrong impression that a custom rom that's modded from stock aren't likely to fix my problem... Any suggestions?
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Click to expand...
Click to collapse
Did you look in setting for rotation display settings. Some launchers like adw launcher lets you also check and uncheck rotation angles. All roms are great in their own way, try a few on for size but I would give them each at least a week or two of testing. A day or two is not really enough to get the feel of them. You can try Absolution 3.7 , Redemption Alpha 6 (ICS) , or even go over to the Desire HD Dev section and try out - Ice Cold Sandwich 7.2 (ICS) (also dont forget to flash inspirmod as well with this one). Also these three will get rid of the stock look.
Good Luck

The phone was bought off craigslist, so no hope of return or warranty. Rotate sreen in settings has been checked, as well as g-sensor calibration (which invariably ends in abort, even after rooting and flashing coredroid. I might try absolution in a few days.
The phone is for my son, and he cares a lot more whether the accelerometer works (for games) than how nice the rom looks.
One problem I found after flashing coredroid is that even at boot up tbe email app keep crashing (without me opening the app). Anyone knows whats up with this?
Sent from my SAMSUNG-SGH-I777 using Tapatalk

fishline said:
The phone was bought off craigslist, so no hope of return or warranty. Rotate sreen in settings has been checked, as well as g-sensor calibration (which invariably ends in abort, even after rooting and flashing coredroid. I might try absolution in a few days.
The phone is for my son, and he cares a lot more whether the accelerometer works (for games) than how nice the rom looks.
One problem I found after flashing coredroid is that even at boot up tbe email app keep crashing (without me opening the app). Anyone knows whats up with this?
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Click to expand...
Click to collapse
Did you do a full wipe (factory, cache partition, dalvik) before flashing rom. Coredroid has a zip called full wipe 1.5 as well.

I flashed absolution, and it didn't help with the g-sensor problem at all. I put coredroid back, this time wiping data and cache, and the email problem went away. I guess my son will have to live with the g-sensor as is. Thanks to everyone who replied for the suggestions.
Sent from my SAMSUNG-SGH-I777 using Tapatalk

is there a sensor fix yet?

sorry to make another thread on this but anyway, lets get to the point
my sensation (and others, as well) has problems with the proximity and light sensors.
sometimes the proximity sensor works, but after a while it stops reading it. this is most likely not a hardware issue. with the ambient light sensor i have no idea whether it works or not but im assuming this is also a software related.
any fixes yet or is this a problem with all sense4.0/ICS ROMs? its really irritating when i have to change brightness all the time or when my face hangs up or mutes a call haha
i heard some people tried fixes, tried reverting to sense 3.6 or even GB ROMs but the problem persisted.. i hope its not completely and permanently damaged, i just bought this phone

DonDizzurp said:
sorry to make another thread on this but anyway, lets get to the point
my sensation (and others, as well) has problems with the proximity and light sensors.
sometimes the proximity sensor works, but after a while it stops reading it. this is most likely not a hardware issue. with the ambient light sensor i have no idea whether it works or not but im assuming this is also a software related.
any fixes yet or is this a problem with all sense4.0/ICS ROMs? its really irritating when i have to change brightness all the time or when my face hangs up or mutes a call haha
i heard some people tried fixes, tried reverting to sense 3.6 or even GB ROMs but the problem persisted.. i hope its not completely and permanently damaged, i just bought this phone
Click to expand...
Click to collapse
Turn off fastboot. This was the fix I used when I experienced this in ARHD.

kgs1992 said:
Turn off fastboot. This was the fix I used when I experienced this in ARHD.
Click to expand...
Click to collapse
i turned off fastboot, shut down my phone, then turned it on face-down in a dark room and both proxi and light are working again..
the thing is, others have tried this and it ends up failing eventually. i really hope this is just a software/kernel issue and will be resolved with updates.. if its a hardware issue, i think im gonna have to step away from HTC after all these years..

DonDizzurp said:
i turned off fastboot, shut down my phone, then turned it on face-down in a dark room and both proxi and light are working again..
the thing is, others have tried this and it ends up failing eventually. i really hope this is just a software/kernel issue and will be resolved with updates.. if its a hardware issue, i think im gonna have to step away from HTC after all these years..
Click to expand...
Click to collapse
Software issue for sure. don't worry!

i did a "superwipe" using the file from the ARHD thread
then i installed the base from the same thread
Then i installed ARHD and both sensors are working
then i did a superwipe again and installed the PKMN ROM and both sensors are still working after several reboots... hmmmmm...
im gonna try ordroid again, hopefully they dont mess up
im really really really really glad this is not a hardware issue

DonDizzurp said:
i did a "superwipe" using the file from the ARHD thread
then i installed the base from the same thread
Then i installed ARHD and both sensors are working
then i did a superwipe again and installed the PKMN ROM and both sensors are still working after several reboots... hmmmmm...
im gonna try ordroid again, hopefully they dont mess up
im really really really really glad this is not a hardware issue
Click to expand...
Click to collapse
Does your sensors still working? did you figured out what was the problem?

tamirsh said:
Does your sensors still working? did you figured out what was the problem?
Click to expand...
Click to collapse
yea it didnt work.. it stopped working by the end of the day. i think the t-mobile firmware is from a different country
so this time i did the same thing but i used the latest T-mobile US firmware that came out a week or two ago (since my phone is t-mobile from US)
process:
- superwipe
- install firmware
- install ordroid
things have been good for the past few days. im getting worse service with the radio but im gonna change it and see if it affects it
i guess these phones are very small hardware variations that different firmware addresses differently. its been working for days now so i think its fixed for good

DonDizzurp said:
yea it didnt work.. it stopped working by the end of the day. i think the t-mobile firmware is from a different country
so this time i did the same thing but i used the latest T-mobile US firmware that came out a week or two ago (since my phone is t-mobile from US)
process:
- superwipe
- install firmware
- install ordroid
things have been good for the past few days. im getting worse service with the radio but im gonna change it and see if it affects it
i guess these phones are very small hardware variations that different firmware addresses differently. its been working for days now so i think its fixed for good
Click to expand...
Click to collapse
To be honest, SuperWipe is not the best way to clean up the phone.
I'd recommend the "Format all partitions except SD Card" option in 4ext.
Also, this is unnecessary if you are switching between ROMs having the same Android version & Sense version. In that case, just back up as you usually would before switching a ROM (NANDROID+ Apps + Messages + Contacts), wipe cache & dalvik, then proceed to install the ROM.
Should you face any problems, format all partitions except SD Card & re-install.
Hope this helps.

kgs1992 said:
To be honest, SuperWipe is not the best way to clean up the phone.
I'd recommend the "Format all partitions except SD Card" option in 4ext.
Also, this is unnecessary if you are switching between ROMs having the same Android version & Sense version. In that case, just back up as you usually would before switching a ROM (NANDROID+ Apps + Messages + Contacts), wipe cache & dalvik, then proceed to install the ROM.
Should you face any problems, format all partitions except SD Card & re-install.
Hope this helps.
Click to expand...
Click to collapse
i usually just do a full wipe.. the superwipe thing does the same thing expect it also wipes system

Are you guys finding its not just the prox and light sensor but the gyroscope, accelerometer as well?

dtyson said:
Are you guys finding its not just the prox and light sensor but the gyroscope, accelerometer as well?
Click to expand...
Click to collapse
oh man i hope not
the proxi and light sensors are pissing me off, they dont last. sometimes as long as you dont turn your phone off or restart, theyll last forever but its so annoying
i think my gyro and acc are working.. not sure how accurate they are but they are taking measurements so i guess thats good enough

My phone was stuffed, no sensors (acc,gyro,g-senor,prox,light,magnetic etc etc), then the next thing was the earpiece got all tinny sounding (on both stock and custom roms). HTC Australia did a straight handset swap, 4 business day turn around. hopefully I wont get the same prob again

Fastboost on or off????
After experiencing the same problem most of you have: light sensor and proximity are not working, I checked some posts. Espescially when in direct sunlight my Auto Brightness wasn't working and when hanging up a phone call my screen stayed black.
All posts had to do with Super Wipe, change kernels, flash ROM's etc etc
Then I saw that somone said: turn Fastboost off.
But my Fastboost was already off. So...I turned it on....reboot and......it works again!!!!
Hope it stays this way. Everybody....good luck!!
BTW: Sensation is Super CID, 4.0.3 Sense 3.6, software version 3.33.401.6

So...
Got the same problem here...
All of my sensors "died" and the backlight on the buttons as well...
I've tried everything said over here...
I realy do hope its a software issue and getting fixed fast

accelerometer, gyroscope not working
First of all, sorry to pull back a really old thread but I thought this thread had the most relevant discussion.
My Sensation's accelerometer and gyroscope sensors are not working. They stopped working the first time I tried unlocking the bootloader of my phone and installing a custom ROM. That was almost a year back and I have been trying to live with the phone like that. Since then, I have also installed multiple different ROMs. Currently, I am on Cyanogenmod 10 nightly. Its a good ROM and everything works except the Gyroscope and accelerometer sensors but I need to get these sensors working again. I have tried different kenels, firmwares, ROMs, etc etc.
Any suggestions?

aslambhai said:
First of all, sorry to pull back a really old thread but I thought this thread had the most relevant discussion.
My Sensation's accelerometer and gyroscope sensors are not working. They stopped working the first time I tried unlocking the bootloader of my phone and installing a custom ROM. That was almost a year back and I have been trying to live with the phone like that. Since then, I have also installed multiple different ROMs. Currently, I am on Cyanogenmod 10 nightly. Its a good ROM and everything works except the Gyroscope and accelerometer sensors but I need to get these sensors working again. I have tried different kenels, firmwares, ROMs, etc etc.
Any suggestions?
Click to expand...
Click to collapse
Try to go to stock again by flashing a ruu and check again
Sent from my Nexus 7 using xda premium

ganeshp said:
Try to go to stock again by flashing a ruu and check again
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks Ganesh. I will try doing this.
Can you share some reliable site for the RUUs? I found some, but am not sure about the authenticity of the ROMs given that the MD5 cheksum is missing at the download locations.

Proximity Sensor Troubles? I think I have your fix... [AOSP or Sense]

I've seen several posts in different ROM threads talking about proximity sensor issues, and I think I have your fix.
Awhile ago, back when I was on CM10, I noticed that my proximity sensor was no longer functioning as expected. The screen would remain on when I was on phone calls, and would stay black for long periods of time after hanging up.
I initially chalked it up to a CM10 issue, but when I flashed back to a Sense ROM, the issue remained. Eventually, I discovered this app...
https://play.google.com/store/apps/details?id=com.incredicontrol.ProxSensorCalibrator&hl=en
...and it worked perfectly.
The best thing to do is start up the app and see if it says "NEAR" or "FAR" at the bottom, then move your hand close and further from your phone to see when it changes. To be completely honest, I don't entirely understand what the settings in the app correspond to - I just played with the settings until the "NEAR" and "FAR" labels appeared at what I believed was the correct time. The attached screenshot shows the settings that ended up working for me.
Sure enough, I have no proximity issues now - except when I recently flashed LiquidSmooth, and forgot to re-run this app. As soon as I re-calibrated, it worked great again. So, this fix isn't permanent - you have to keep this app installed, and it has to be set to run on boot. You also have to have root for it to work its magic.
Hope this helps some of you out there!

Thanks for the info. I'm definitely going to give this a shot. I've had issues like you had on all 4.2 ROMs with s2w. My issue does go away when I go to something different though. Still gonna give it a whirl though and see if it helps.
Oh well, it doesn't look like my calibration is off. Thanks for the suggestion though.
Sent from my One X using Tapatalk 2

pside15 said:
Thanks for the info. I'm definitely going to give this a shot. I've had issues like you had on all 4.2 ROMs with s2w. My issue does go away when I go to something different though. Still gonna give it a whirl though and see if it helps.
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Yeah, I think the s2w bug may be something different entirely, but it can't hurt to check.

Silellak said:
I've seen several posts in different ROM threads talking about proximity sensor issues, and I think I have your fix.
Awhile ago, back when I was on CM10, I noticed that my proximity sensor was no longer functioning as expected. The screen would remain on when I was on phone calls, and would stay black for long periods of time after hanging up.
I initially chalked it up to a CM10 issue, but when I flashed back to a Sense ROM, the issue remained. Eventually, I discovered this app...
https://play.google.com/store/apps/details?id=com.incredicontrol.ProxSensorCalibrator&hl=en
...and it worked perfectly.
The best thing to do is start up the app and see if it says "NEAR" or "FAR" at the bottom, then move your hand close and further from your phone to see when it changes. To be completely honest, I don't entirely understand what the settings in the app correspond to - I just played with the settings until the "NEAR" and "FAR" labels appeared at what I believed was the correct time. The attached screenshot shows the settings that ended up working for me.
Sure enough, I have no proximity issues now - except when I recently flashed LiquidSmooth, and forgot to re-run this app. As soon as I re-calibrated, it worked great again. So, this fix isn't permanent - you have to keep this app installed, and it has to be set to run on boot. You also have to have root for it to work its magic.
Hope this helps some of you out there!
Click to expand...
Click to collapse
Thank you. I hated hitting the wrong button with automatic machines. Will try this out. I am also on liquid smooth so I may try the same settings. Thanks!
Sent from my One X using xda app-developers app

solving with
Proximity Sensor Fix

Worked for me! Thank you

Hitting the thanks button is probably enough, rather than digging up an old thread by commenting on it.
Sent from my Evita

My Device: HTC One X
There are problems with the proximity sensor.
The application worked fine. Thank you very much.

[Q] New Google Maps flickers on CM10.1

Some of you may have noticed that the new maps app flickers on MT4GS running CM10.1. I reflashed gapps with the old maps, turned off auto-updates and it still updated itself. It is just useless.
Does anyone have a solution? I doubt google cares.

emi.bu said:
Some of you may have noticed that the new maps app flickers on MT4GS running CM10.1. I reflashed gapps with the old maps, turned off auto-updates and it still updated itself. It is just useless.
Does anyone have a solution? I doubt google cares.
Click to expand...
Click to collapse
Saw you mention this in one of the dev threads as well. I'm running SilverL's Unofficial CM 10.1 and haven't personally noticed this issue, while I saw someone else back you up with similar problems.
Maybe you pulled a map update I haven't seen yet? I'm showing version 6.14.4(#6140400) Web
Are you higher? Do you have a lot of layers on maybe?

PsychoPhreak said:
Saw you mention this in one of the dev threads as well. I'm running SilverL's Unofficial CM 10.1 and haven't personally noticed this issue, while I saw someone else back you up with similar problems.
Maybe you pulled a map update I haven't seen yet? I'm showing version 6.14.4(#6140400) Web
Are you higher? Do you have a lot of layers on maybe?
Click to expand...
Click to collapse
Yes, version 7 is out. auto-updated earlier week on my phone. dev threads? i don't recall, posting anything, I don't think I have permission to post there.
Anyway, I figured it out. I reflashed gapps, but it doesn't contain the maps app, and that's why it was ineffective. I uninstalled version 7, and pulled the version 6 apk from a friend's phone and installed it.
I also turned off auto-update in play.

emi.bu said:
Yes, version 7 is out. auto-updated earlier week on my phone. dev threads? i don't recall, posting anything, I don't think I have permission to post there.
Anyway, I figured it out. I reflashed gapps, but it doesn't contain the maps app, and that's why it was ineffective. I uninstalled version 7, and pulled the version 6 apk from a friend's phone and installed it.
I also turned off auto-update in play.
Click to expand...
Click to collapse
Sorry, saw someone mention it, thought it was you! Glad to hear it was sorted, I'll be sure to avoid a map update if I see one pop, but I haven't yet. Maybe it was causing issues outside of custom roms and google stopped pushing it until they got it sorted.

interesting, i was also having this issue.i was on the jellykang rom 1.8 and changed to silverL's 10.1 unofficial cm and im seeing a version 7.0.1 and it look like its working fine. ill report back if i see anything messing up again. but looking at android polices coverage of this update release reported that there were several versions getting pushed all over the place so maybe some work better than others..

Tampoon said:
interesting, i was also having this issue.i was on the jellykang rom 1.8 and changed to silverL's 10.1 unofficial cm and im seeing a version 7.0.1 and it look like its working fine. ill report back if i see anything messing up again. but looking at android polices coverage of this update release reported that there were several versions getting pushed all over the place so maybe some work better than others..
Click to expand...
Click to collapse
Interesting. I finally popped for the map update yesterday, and after reading this I figured I'll give it a shot. I like everyone else definitely had issues with the map, the jitteryness, the menu icon on bottom left slightly off screen. I uninstalled and reverted to 6.14.4 from my backup and it's just fine again. Hope this does get fixed, the new map looks nice if it was working. Wondering if you really are issue free or just didn't notice anything real quick.
It did seem like as I was playing with location options (use network for location, gps radio on or off, let google always allow access, having a gps lock or not) sometimes it seemed like it would smooth out for a second or two, then get all glitchy again. Wonder if any official JB handsets are getting the issue, I think I know what I'll google next.

PsychoPhreak said:
Interesting. I finally popped for the map update yesterday, and after reading this I figured I'll give it a shot. I like everyone else definitely had issues with the map, the jitteryness, the menu icon on bottom left slightly off screen. I uninstalled and reverted to 6.14.4 from my backup and it's just fine again. Hope this does get fixed, the new map looks nice if it was working. Wondering if you really are issue free or just didn't notice anything real quick.
It did seem like as I was playing with location options (use network for location, gps radio on or off, let google always allow access, having a gps lock or not) sometimes it seemed like it would smooth out for a second or two, then get all glitchy again. Wonder if any official JB handsets are getting the issue, I think I know what I'll google next.
Click to expand...
Click to collapse
yea you were right, i just did a glance look at it and didint really dive into it that far. i checked it out again and it is still all messed up so nevermind ..
are there any custom roms that dont have the issue i wonder. maybe this can help narrow down the root cause. unless its just an inherent problem with the app as it stands today. it almost reminds me of this issues i was having with ingress when i was on stock.

Tampoon said:
yea you were right, i just did a glance look at it and didint really dive into it that far. i checked it out again and it is still all messed up so nevermind ..
are there any custom roms that dont have the issue i wonder. maybe this can help narrow down the root cause. unless its just an inherent problem with the app as it stands today. it almost reminds me of this issues i was having with ingress when i was on stock.
Click to expand...
Click to collapse
Unfortunately it seems to me to be an issue with all of the 10.1's at least, and from my googling before, it seems likely specific to our device, just not sure why
Anywho, I'm pretty OK with maps 6, it works, and still has separate navi app, and is what anyone with earlier than android 4.0 is stuck with anyway.
UPDATE: So I tried the 7/22 update that I got hit with, and it's weird. Initially it seemed OK, aside from the menu button still being half off screen. After fooling around for a bit with menus and settings, it got all flickery again. It seems like it heavily had to do with overlays/prompt dialogues showing up. The box would kind of disappear aside from the outline, but still respond. After fooling around quite a bit and disabling boxes from asking again, eventually everything seems to have evened out. Now I haven't actually done any kind of navigation or heavy use, but I've been using v 7.0.2 now on and off for a few days, and the stutter hasn't come back. Wish I had a more definitive way of what I did to get rid of it, or if it eventually just smoothes out on it's own, but for now it seems like I'm good with the new maps on a CM10.1 rom.

Bump for update, anyone else experiences with new maps?

PsychoPhreak said:
Bump for update, anyone else experiences with new maps?
Click to expand...
Click to collapse
Yes, I'm having the exact same issues as you. Screen flickers and overlay menus keep blanking out so you can't read them. I have an HTC Inspire 4G running CM 10.1. Came across this thread searching for "Maps 7 screen flicker". I had to revert back to Maps 6 as 7 was unusable!

greiland said:
Yes, I'm having the exact same issues as you. Screen flickers and overlay menus keep blanking out so you can't read them. I have an HTC Inspire 4G running CM 10.1. Came across this thread searching for "Maps 7 screen flicker". I had to revert back to Maps 6 as 7 was unusable!
Click to expand...
Click to collapse
I am having same issue with HTC Evo 4g 3d buil 7-17 of CM Flicker maddness . . . it seems to be the CM build or something within CM Rom. Other phones or devices do not have the issue . . <---- my story

j1232 said:
I am having same issue with HTC Evo 4g 3d buil 7-17 of CM Flicker maddness . . . it seems to be the CM build or something within CM Rom. Other phones or devices do not have the issue . . <---- my story
Click to expand...
Click to collapse
Im running PACman ROM v22.4.0, same issue as you guys with the new maps, and navigation is a stutterfest.

I'm on jellykang 1.8 and that's definitely happening to me. especially in the navigation app

Since others are now finding this thread outside of just us DS users, I figure I'll share this idea from a dev thread:
Originally Posted by pyro9219
"Have you tried Settings > Developer Options > Disable HW Overlays?
I had to do that for several games that were causing screen tearing / artifacts."
I hadn't, but that's a wonderful suggestion, wonder if anyone else has?
Edit: So after learning how to re-enable dev options, I just tried this, and it definitely seems to WAY help. Is there any downside to leaving this checked all the time?
So something for others to try/chime in on?

Guys, can you try disabling android debugging AND USB debugging in developer options?
I saw it on a sensation ROM forum and it seems to be working for me.

anitgandhi said:
Guys, can you try disabling android debugging AND USB debugging in developer options?
I saw it on a sensation ROM forum and it seems to be working for me.
Click to expand...
Click to collapse
Hrm, I'll try it. Just loaded maps now, it was sketchy, disabled and seemed fine. Turned back on, and it was still fine, this one seems to be crazy inconsistent.

It wotk fine on my device
Gesendet von meinem GT-I9505 mit Tapatalk 2

possible workaround?
I found another workaround that seems to work for me:
Turn on the "Extended Desktop" (or "Expanded"? I'm on German here). And it's gone. Strangely the flickers don't return when I turn it off again.
Extended Desktop Option has to be activated in the settings, if it's not available in the power switch menu.

Counter perspective
I've just been working with the newest CM builds for the MT4GS, and I don't encounter any flickering. This is with a complete wipe prior to installing however.

same issue with HTC G2 on CM10.1
Hello,
I experienced the same issue on my HTC G2 with CM10.1. I had to revert to Maps v6...the v7 would sometime work fine, but most of the time I had some part of the screen flickering and the navigation feature was not usable at all (the animation would not work). I first thought it might be because of the overclocking. but I tried with stock frequency and the issue persisted.
My wife's Sony Ericsson Mk16a also has the same issue but on a custom stock rom..