My current configuration:
STOCK JB 4.1.2
AT&T
Screen Rotation selected
Things I have tried:
Gyroscope calibration (result: ball stuck in the middle)
Leveling Applications from Play Store (result: looks like it calibrated but did nothing ultimately)
Used *#0*# - Sensors (result: All sensors passed except image test)
I view my phone horizontal and the screen rotates to landscape as expected. I rotate my phone to normal position and the screen is still displaying landscape. It should be portrait. HELP!!!!!!!
Redownload and reinstall the firmware to insure it was not a corrupted download or bad write.
I forgot to mention that prior to updating to official JB, I installed CM10 JB 4.2.2 and screen rotation didn't work at all. So I restored to stock and it still was broken. It was working prior to installing CM10 JB 4.2.2. I came to the conclusion that it had to be CM10's version that messed up my settings with screen rotation. I restored to stock 2.3.6 and tried everything possible. I restored CWM backup image of working image prior to install of CM10. Still having the same issue. Last night, I updated to official JB 4.1.2 via Kies and thought that they may fix it. I was wrong....
studacris said:
Redownload and reinstall the firmware to insure it was not a corrupted download or bad write.
Click to expand...
Click to collapse
You've flashed several kernels at this point
Pretty much ruling out software issues (unless you've restored an app that's getting funky or something weird)
Kinda sounds like a hardware malfunction to me
jtrinh said:
I forgot to mention that prior to updating to official JB, I installed CM10 JB 4.2.2 and screen rotation didn't work at all. So I restored to stock and it still was broken. It was working prior to installing CM10 JB 4.2.2. I came to the conclusion that it had to be CM10's version that messed up my settings with screen rotation. I restored to stock 2.3.6 and tried everything possible. I restored CWM backup image of working image prior to install of CM10. Still having the same issue. Last night, I updated to official JB 4.1.2 via Kies and thought that they may fix it. I was wrong....
Click to expand...
Click to collapse
You are NOT alone. CM 10.1 broke auto-rotate on a LOT of phones. I'm currently flashing CM 10.1 from 4/22/13, since that version worked correctly, to see if that will help.
I read about another phone having the same problem a while back, and they had some weird, contorted way of fixing the problem that, of course, could not be done to the Note.
P.S. I have also tried installing CM 10.1 from 5/02/13. No joy.
I hope installing the new Stock 4.1.2 between CM versions didn't yak the phone forever.
I give up. Hopefully, someone will come up with a flashable .ZIP file that can fix this mess.
Related
Hello everybody,
I installed the latest aopk (from 19.11.) for Medipad.
Everything works good but now, the Display sometimes flicker when the Pad is in Landscapemode.
I tried some other Settings of the DPI but it doesnt work.
Can someone help? Thx.
Had that too, didn't find a solution, ended up going back to stock firmware.
Thx.
I have Recover my Backup and work with 4.0.4.
I also have Problems with Adobe Flash on 4.1.2, so i will wait for a later Rom-Version.
Hello, I've got issues with my S3, I was going to reinstall it with the fresh CM 10.1 and i also wanted to flash a new recovery. I downloaded Mobile ODIN and tried but the file didn't show up so i used my pc's ODIN to do it. It didn't go that great and the screen started to flicker and the phone didn't start up further than the Samsung text when so i downloaded clockwork mod recovery with touch and installed. It worked good but the touch didn't work in the recovery, didn't really see that as a big issue and installed CM 10.1 thru the recovery without any errors. But when the phone booted again i realized i couldn't touch anything. The two touch buttons worked fine but not anywhere on the screen itself. Now I've downloaded and flashed a stock Samsung firmware and reset everything but the touch is still the same.
Anyone that know how i can fix it and what might happened?
Still got the same issues even after a full reset but i think theres maybe some file that left in there making the touch disabled?
ppoolliiss said:
Hello, I've got issues with my S3, I was going to reinstall it with the fresh CM 10.1 and i also wanted to flash a new recovery. I downloaded Mobile ODIN and tried but the file didn't show up so i used my pc's ODIN to do it. It didn't go that great and the screen started to flicker and the phone didn't start up further than the Samsung text when so i downloaded clockwork mod recovery with touch and installed. It worked good but the touch didn't work in the recovery, didn't really see that as a big issue and installed CM 10.1 thru the recovery without any errors. But when the phone booted again i realized i couldn't touch anything. The two touch buttons worked fine but not anywhere on the screen itself. Now I've downloaded and flashed a stock Samsung firmware and reset everything but the touch is still the same.
Anyone that know how i can fix it and what might happened?
Still got the same issues even after a full reset but i think theres maybe some file that left in there making the touch disabled?
Click to expand...
Click to collapse
I think you flashed someone wrong and bricked/fried the touch controller like Erica from XDA-TV. She has a video about what happened and how she fixed it Go check it out
I doubt software can disable the touchscreen so yeah.
xSpeced said:
I think you flashed someone wrong and bricked/fried the touch controller like Erica from XDA-TV. She has a video about what happened and how she fixed it Go check it out
I doubt software can disable the touchscreen so yeah.
Click to expand...
Click to collapse
Think you could link to the video? I've looked all over.
Found it! http://www.youtube.com/watch?v=oMG-_26NgXM
Hi,
We have 2 Vibrant phones. 1 is on Paranoid Android 2.54 (via stock eclair, ICS Passion, Slim Bean 2.9 & 3.0) and works perfectly.
The second one was on ICS Passion for a long time and I have finally got around to (trying LOL) to update it.
Here is where the weirdness begins - Flashed PA 2.54 no problems, flashed and booted up, but no wi-fi, well no wi-fi icon, and it can find a couple of wi-fi networks belonging to my neighbours, but won't find my network, 2 rooms away. The network is obviously all good, I am sending this from my laptop through said network.
Obviously I need an internet connection to get through the phone setup, so I power down, throw the SIM back in and boot up only to find no cell data either.
Skip the google account setup and get to the home screen to check things further and I find:
Calls in/out work, and most things are running, but wi-fi won't co-operate, and nothing in the APN list? Baseband and IMEI all look normal, too.
Try to flash Slim Bean 2.9 as I put the zip on the phone at the same time as a fallback and I get EXACTLY the same thing...
Anyone able to shed any light on what would cause this? Anything else worth trying? I'd like to avoid Odin as it honestly scares me reading all the problems people on here have with it...
At this point I've tried flashing both ROMs a few times with exactly the same results, I also can't go back to the ICS nandroid as the partition setup has changed and the restore doesn't work...
Thanks in advance for any help anyone can give.
Cheers...
I ended up flashing a 4.2 ROM (slim 4.2 beta 1) and it made the problem go away, I'm guessing something in the 4.1 base was broken and not getting overwritten on new installs?
ROM seems pretty sorted for a beta, few minor things not working, but hopefully it gives us a clean upgrade path...
Thanks.
I had the same issue with Slim 4.2 Beta 2. If anyone has a solution other than flashing the modem, please post.
Weird. The phone I was having this problem with now has that ROM on it and is working 100%.
I have a suspicion that flashing a ROM that uses a different kernel is what fixed it for us. I guess it just overwrites/replaces more stuff?
Maybe try hellybean 4.2 and see if it makes a difference, and if it does flash back to slim 4.2 and see if the problem comes back?
I have installed slim and other ROMs but not had this issue. Currently on jellybam
Sent from my GT-I9300 using xda premium
wendleburger said:
Weird. The phone I was having this problem with now has that ROM on it and is working 100%.
I have a suspicion that flashing a ROM that uses a different kernel is what fixed it for us. I guess it just overwrites/replaces more stuff?
Maybe try hellybean 4.2 and see if it makes a difference, and if it does flash back to slim 4.2 and see if the problem comes back?
Click to expand...
Click to collapse
The weird part is that every other Slim Bean has worked great. I'll keep my fingers crossed for beta 3.
I *had* an un-rooted e970 with the standard 4.0.4 installed. I saw an update and updated to 4.1.2. I don't know if this is coincidence or if 4.1.2 just sucks with the Optimus G, but ever since I updated the phone:
(1) Data signal works half the time and decides randomly when it wants to work. (Toggling Airplane-mode and restarting does nothing). I've also factory reset this thing twice and it still has issues.
(2) Now the phone can't auto-rotate even though the option is clearly clicked to ON in the display settings.
Since then, I rooted my phone hoping something might trigger it, but no luck. Ultimately I want my issues fixed, but I think downgrading to 4.0.4 might fix the issues but I have no idea how to do that. Can anyone help?
Have you tried or considered flashing 4.1.2 stock meaning a complete flash of the latest available stock ROM using the LGNPST tool? I don't mean flashing 4.0.4 and then doing the OTA to 4.1.2, I mean completely flashing the LGE970AT-01-V20j-310-410-MAR-08-2013 build direct to the device in download mode using LGNPST... that might help alleviate some of the issues you noted, it might not, but it probably can't hurt to take that step. If it doesn't, you can then flash back to 4.0.4 which is out there as LGE970AT-00-V10o-ATT-US-SEP-29-2012-0. I think there's a V11c build as well posted someplace by SnowLeopardJB too.
As for the auto-rotate thing, I know one of the radios has been noted to have an effect on that, perhaps somehow that could be related. Flashing the stock 4.1.2 fully should help since it'll flash the stock JB AT&T radio, or at least it should, that might help with the auto-rotate too.
I purchased an AT&T SGH-i717 and was told everything worked. When I checked it out, everything seemed fine too. After using it for a couple hours I realized it just seemed to reboot at random. I rebooted into recovery and did a factory reset and wiped the cache. After rebooting it...it would get stuck at the AT&T screen. I then installed the latest stock rom 4.4.2 using Odin and it booted up fine but I got the no sim card error. I put in an AT&T sim card and rebooted but got a sim not provisioned error. I then tried a T-Mobile card and I didn't get the error and it showed signal bars but when I tried to dial it said emergency calls only. I tried a Verizon sim card just to see what kind of error I would get but it was just the same as the T-Mobile sim. I thought it might a corrupted rom so I tried installing the latest nightly CyanogenMod using CWM but got error status 7. I then tried various custom and stock roms including AOKP, BeanStalk, and several different versions of CyanogenMod but always got the same error status 7 msg. I then came across a forum posts stating that CWM no longer works for the SGH-i717. I downloaded the latest TWRP touch recovery and was able install the latest stable CyanogenMod but it would not boot past the animated CyanogenMod logo even after sitting for over an hour. At that point I gave up and decided to just go back to the stock rom. I rebooted into TWRP and the slide to unlock would not work anymore. I had to install CWM using Odin which allowed me to flash back to the stock 4.4.2 rom. After doing another factory reset and wiping the cache then rebooting...the touch screen stopped working. I then flashed it back to the stock 4.0.4 rom but the touch screen still does not work. While trying to figure out what happened I realized the pen still works and touch screen buttons on the bottom but thats it. Also the pen only works on the screen and not on the touch screen buttons. I've been messing with this for 3 days and will probably just sell it for parts but wanted to post this problem so if anyone else had this problem they would know what I've already tried. I did also take apart the phone and clean the connections but that didn't help either.
If anyone has a suggestion for something I haven't tried...please let me know. My last attempt will be install the Padawan JB rom from this post:
http://forum.xda-developers.com/showthread.php?t=1907203
Thanks
Right out of tge gate, there is no stock 4.4.2 for this device. Not official anyway. 4.1.2 is official OS.
Status 7 means your recovery needs updating.
CWM does work and the newest CWM touch is just dandy.
I would try going all the way back. You need to be totally clean.
Factory
Cache
Davlik
Format
Go to Kies and go with emergency firmware recovery.
Get back to stock and see what is working.
Clean clean clean, the best way for anyone to help you. You would be at the best starting point.
Maybe do a little reading as many of your issues have been documented and solved. None of them are major.
Start from scratch and folks can get you running again.
Sent from my SAMSUNG-SGH-I527 using xda app-developers app
captemo said:
Right out of tge gate, there is no stock 4.4.2 for this device. Not official anyway. 4.1.2 is official OS.
Status 7 means your recovery needs updating.
CWM does work and the newest CWM touch is just dandy.
I would try going all the way back. You need to be totally clean.
Factory
Cache
Davlik
Format
Go to Kies and go with emergency firmware recovery.
Get back to stock and see what is working.
Clean clean clean, the best way for anyone to help you. You would be at the best starting point.
Maybe do a little reading as many of your issues have been documented and solved. None of them are major.
Start from scratch and folks can get you running again.
Sent from my SAMSUNG-SGH-I527 using xda app-developers app
Click to expand...
Click to collapse
Thanks for replying...I hadn't used Kies in awhile becuase it never seemed to work right. I downloaded the latest version and it looks like they made a lot of improvements. I did the factory restore and wiped the cache then installed the latest firmware thru Kies. Everything seemed to work fine but after rebooting the touch screen doesn't work at all, not even with the pen. The touch screen buttons seem to still work but its stuck at the AT&T Ready2go screen because I can't hit cancel or get started buttons.
Thanks
cycloneus said:
Thanks for replying...I hadn't used Kies in awhile becuase it never seemed to work right. I downloaded the latest version and it looks like they made a lot of improvements. I did the factory restore and wiped the cache then installed the latest firmware thru Kies. Everything seemed to work fine but after rebooting the touch screen doesn't work at all, not even with the pen. The touch screen buttons seem to still work but its stuck at the AT&T Ready2go screen because I can't hit cancel or get started buttons.
Thanks
Click to expand...
Click to collapse
well my friend, you had the phone apart once already, I am no expert, but my guess is this is no software issue. maybe some connections came loose. in my time here, I have not come across this issue. I do not have the brain pan nor the courage to take my phone apart.
good luck to you.
maybe someone else will mosey on by.
cycloneus said:
Thanks for replying...I hadn't used Kies in awhile becuase it never seemed to work right. I downloaded the latest version and it looks like they made a lot of improvements. I did the factory restore and wiped the cache then installed the latest firmware thru Kies. Everything seemed to work fine but after rebooting the touch screen doesn't work at all, not even with the pen. The touch screen buttons seem to still work but its stuck at the AT&T Ready2go screen because I can't hit cancel or get started buttons.
Thanks
Click to expand...
Click to collapse
My guess is the digitizer has gone bad if odin &/or kies can't fix the issue at hand.