Auto-Rotate not working in CM's last couple - G1 Q&A, Help & Troubleshooting

Hi,
I just received my phone back after warranty repairs (bad SPL flash).
Installed Recovery 1.4, then 4.2.8, and no auto-rotate.
4.2.8.1 - no auto-rotate.
4.2.9.1 - still no auto-rotate.
I have tried toggling the various settings (Orientation in Sound & Display, and Launcher Rotate in Spare Parts). Nothing seems to be working.
I have tried fix permissions, a couple of guides, the fix_rotate.sh guide seemed like it would work, but, alas, didn't.
I know the phone realises what it should be doing, because if I open the screen, then close it, it stays landscape. The only way to get it back to portrait is to turn the screen off (not the whole phone), and then hit menu to get back into the phone.
Also, it is not the accelerometer, because PapiJump (Good ol' accelerometer tester) still plays perfectly, if not slightly more touchy then before the repair.
First install to 4.2.8, and install to 4.2.8.1 were without wipe.
Every (re-)install I have done of 4.2.9.1 has been with a wipe, both typing wipe into the console, and using Alt + W.
I have A2SD running (course I do, it's CM =). I can't remember the exact sizing of my partitions, but I can check on them if anyone thinks they would make a difference.
Other than that, everything is stock. Haven't changed radio, or SPL.
(When I say stock, I mean from CM 4.2.9.1)
It would be greatly appreciated if anyone could help me out.
=)
swanniebroo

I have the same problem:
http://forum.xda-developers.com/showthread.php?t=609128

try to wipe and reflash from the beginning with the HTC recovery

Hi Tazz9690
I just reflash my HTC Dream with these two files :
* Signed-dream_devphone_userdebug-ota-14721.zip
* Update-cm-4.2.11.1-signed.zip
I went through the recovery cyanogen 1.4 and I did a "wipe data" and then "apply any zip from sd"
Unfortunately, I still have the same problem, unable to use the Accelerometer or Orientation

have you tried flashing a different from from another dev and seeing if you have the same problem?

try flashing the latest amon ra recovery. under the wipe menu there's an option for wiping the rotate settings. perhaps that may help?

hey,
Got Amon_RA's recovery. Love it.
Didn't solve anything, though.
Still stuck.
Market hangs too, but this isn't a CM issue.

See if it's enabled in spare parts, if not - enable it, if it is - toggle off and on.
Good luck.

Related

Not Booting! - stuck at splash. Please Help

Hi,
My roger's dream decided to stop working today (i've only had it for like a week). It's rooted, but I haven't done anything major to it. It was running stably for a couple of days after rooting it so I'm fairly confident that it's unrelated.
I wasn't doing much at the time, messing with Klaxon i believe, but it randomly shut off and now whenever it tries to boot, it gets stuck at the splash screen (just playing it over and over).
I've tried booting in safe mode (w/ Home button) and it won't come up. That's about all i know how to do. can anyone help me out with this?
Thanks so much, i'm in a state of crisis right now.
Yea just wipe the phone, reapply the update.zip and it should be good. If that fails. You may need to backup your sd card, wipe that, redo it and put just the apps and apps-private folder back in and link it. (Unless your rom automates that for you)
You can also try in the recovery console from cy the alt-x to terminal, then type fix_permissions and do a fix ext filesystems. That may restore you as well.
Does pressing Power + camera key get you into the fastboot screen?

Help, I Searched but NoOne Has this problems (Video Link)

http://tinypic.com/r/9u7q15/4
This is what's going on with my phone.
Downgrade to rc-29,
Use JF's guide to activate over wifi,
Root, flash the hard spl,
Then the radio (2.22.19.26I),
Then flashed cm-4.0.4,
Then partitioned your sdcard to 1.5gb fat32, 500mb ext3,
Then tried to do a nandroid restore of 4.1.11.1 that had been past the sign in screen,
Then removed the ext3 partition from sdcard, and now you are where you are now.
As you can see in the Video
Everytime i try to call, got to contacts, use the market, text i get a error message saying something suchas
The process (process.android.acore) has stopped unexpectedly, or The process (com.android.phone) or other errors similar to these.
When some one calls me it doesnt even acknowledge that, it just send them to voicemail and i'll never know it
I also cant touch the screen ... it isn't responding to touch, and the rotate isn't working anymore either, The Airplane mode comes on by its self
**Note, it was working perfectly fine the touch and everything until i partition the sdcard then a couple hours after i did that the phone seems as it if caught a virus so i don't know what to do i just basically want to use the market, call, & text.. because everything else works btw the touch screen sensor. so if you can help please do, if not i may just unroot it and send it to HTC, if i can't fix it ;/
This has nothing to do with development. Try posting in the correct section.
Reported
needs to be in Q&A
also need more information, is it rooted or not, if rooted what build is bein used
Best thing to do is wipe it and re-install the ROM.
Turn off your G1.
Turn it on while holding the home button. Wait for the recovery screen to appear.
Press ALT-W (This will wipe your phone's data!)
When it's done wiping, restart the phone, check if it works.
If not, then install the Cyanogen ROM again.
PSP_Hacker said:
Best thing to do is wipe it and re-install the ROM.
Turn off your G1.
Turn it on while holding the home button. Wait for the recovery screen to appear.
Press ALT-W (This will wipe your phone's data!)
When it's done wiping, restart the phone, check if it works.
If not, then install the Cyanogen ROM again.
Click to expand...
Click to collapse
anyone else notice her screen is mirrored? i think it was the video, but it threw me off for a sec... in any case, try wiping and reinstalling rom. if that doesnt work, unroot, go back to factory settings and see if the screen works then. if it does, retry the whole process (rooting) make sure you are using the correct radio and the correct spl. if you still cant figure it out, get an iphone
Don't make movies with a mirror..
could be a hardware problem? doubt it though

Random Kinda/Sorta Brick?? Ideas??

Hello!
First real problem EVER with this phone. Am running Cyanogen's latest 4.1.999 build which has been running fine for the last 2 weeks. Nothing moved or changed recently besides un-installing the iMusic App earlier today. At any rate I had it plugged into my PC via USB, pulled cord out (never had an issue doing this before)... knew I had a couple txts waiting so tried to wake screen... lights came on but black screen (has delayed like this before... wasn't worried yet). Waited, tried pressing menu again then opening keyboard and pressing menu... nuthin. Suddenly a quick buzz and it reboots and I see the T-Mobile G1 screen (STILL not worried at this point since I know Cyanogen 4.1.999 is experimental and to not begrudge a random reboot here and there... HOWEVER... after sitting at G1 screen for a bit it simply fades out and SITS.... doing NOTHING. Black screen... no android logo... but button lights are on. Hit power button I get G1 screen again. What I've tried so far:
1. Removed/replaced battery and reboot - No change.
2. Removed/replaced SIM Card and reboot - No change.
3. Removed SD card and reboot - No change.
4. Wasnt able to at first, but now after leaving battery out for a bit I can boot into Recovery, did a wipe, tried rebooting... it just shuts off and doesnt reboot. Recovery again, tried restoring latest nandroid backup... it said it did, reboot, same thing. Finally tried recovery, then flashing latest HTC recovery build needed for Cyanogen's latest... it started, then screen went dark during the process. Almost like a bum power supply! RANDOM!!
Don't have ADB installed unfortunately... was going to but then I realized since I can't even boot into the OS to enable USB debugging what's the point?
Reasonably saavy here but by no means a coder... ideas?? Help?? Sympathy?? LOL
since you have tried a lot of things already, you may need to flash the rc29 image in bootloader and re-root your phone, if it still will not work after the rc29 flash, then it is hardware related altogether.
RC29?? Couldn'ty I just flash to 1.5 if it came to that?
themoebius said:
RC29?? Couldn'ty I just flash to 1.5 if it came to that?
Click to expand...
Click to collapse
to unroot you flash the DREAIMG.nbh file because it will overwrite everything.
themoebius said:
Hello!
First real problem EVER with this phone. Am running Cyanogen's latest 4.1.999 build which has been running fine for the last 2 weeks. Nothing moved or changed recently besides un-installing the iMusic App earlier today. At any rate I had it plugged into my PC via USB, pulled cord out (never had an issue doing this before)... knew I had a couple txts waiting so tried to wake screen... lights came on but black screen (has delayed like this before... wasn't worried yet). Waited, tried pressing menu again then opening keyboard and pressing menu... nuthin. Suddenly a quick buzz and it reboots and I see the T-Mobile G1 screen (STILL not worried at this point since I know Cyanogen 4.1.999 is experimental and to not begrudge a random reboot here and there... HOWEVER... after sitting at G1 screen for a bit it simply fades out and SITS.... doing NOTHING. Black screen... no android logo... but button lights are on. Hit power button I get G1 screen again. What I've tried so far:
1. Removed/replaced battery and reboot - No change.
2. Removed/replaced SIM Card and reboot - No change.
3. Removed SD card and reboot - No change.
4. Wasnt able to at first, but now after leaving battery out for a bit I can boot into Recovery, did a wipe, tried rebooting... it just shuts off and doesnt reboot. Recovery again, tried restoring latest nandroid backup... it said it did, reboot, same thing. Finally tried recovery, then flashing latest HTC recovery build needed for Cyanogen's latest... it started, then screen went dark during the process. Almost like a bum power supply! RANDOM!!
Don't have ADB installed unfortunately... was going to but then I realized since I can't even boot into the OS to enable USB debugging what's the point?
Reasonably saavy here but by no means a coder... ideas?? Help?? Sympathy?? LOL
Click to expand...
Click to collapse
Try adb, USB debugging is usually on with these modded ROMs. See if you can get a logcat to someone who is much more knowledgeable.
Hold on...not to call you out, but im pretty sure cm 4.1.999 HAS NOT been out for 2 weeks...please clarify...did you flash the newest update THEN had problems?
themoebius said:
Hello!
First real problem EVER with this phone. Am running Cyanogen's latest 4.1.999 build which has been running fine for the last 2 weeks. Nothing moved or changed recently besides un-installing the iMusic App earlier today. At any rate I had it plugged into my PC via USB, pulled cord out (never had an issue doing this before)... knew I had a couple txts waiting so tried to wake screen... lights came on but black screen (has delayed like this before... wasn't worried yet). Waited, tried pressing menu again then opening keyboard and pressing menu... nuthin. Suddenly a quick buzz and it reboots and I see the T-Mobile G1 screen (STILL not worried at this point since I know Cyanogen 4.1.999 is experimental and to not begrudge a random reboot here and there... HOWEVER... after sitting at G1 screen for a bit it simply fades out and SITS.... doing NOTHING. Black screen... no android logo... but button lights are on. Hit power button I get G1 screen again. What I've tried so far:
1. Removed/replaced battery and reboot - No change.
2. Removed/replaced SIM Card and reboot - No change.
3. Removed SD card and reboot - No change.
4. Wasnt able to at first, but now after leaving battery out for a bit I can boot into Recovery, did a wipe, tried rebooting... it just shuts off and doesnt reboot. Recovery again, tried restoring latest nandroid backup... it said it did, reboot, same thing. Finally tried recovery, then flashing latest HTC recovery build needed for Cyanogen's latest... it started, then screen went dark during the process. Almost like a bum power supply! RANDOM!!
Don't have ADB installed unfortunately... was going to but then I realized since I can't even boot into the OS to enable USB debugging what's the point?
Reasonably saavy here but by no means a coder... ideas?? Help?? Sympathy?? LOL
Click to expand...
Click to collapse
I am having the EXACT same problem with CM4.2.4. I certainly hope its not hardware, but it sure "feels" like it. Especially when my G1 is even shutting down from the Recovery Menu. I'll try to unroot and see if that resuscitates it.
Another one....
Have a look at my current issue on this thread: http://forum.xda-developers.com/showthread.php?t=582576. Check to see in bootloader mode what your board type is (it states it at the top for those who don't know).
Mine is currently showing an EVT board, which doesn't exist. I've pulled the battery out and am leaving it for a while. It could be a hardware issue, but I'm not sure. I was having the "fading screen" issue and eventually got back to RC7 (when I could get into recovery).
Which recovery are you using?

[Q] Please help! flashed without disabling lagfix-3button recovery+downld mode gone

Please help.
I have the Bell i9000m. I had JH2 rooted with RyanZa lagfix 2+ (and USB debugging was on) and the phone rebooted on it's own and couldn't load the firmware. It kept booting until getting the Touchwiz lockscreen with black background but the touchscreen wouldn't work and the phone would just shut off.
I know it's better not to flash a rom without disabling lagfix but at that point didn't have a choice anymore. At that point 3 button recovery (2e) and download mode were working. So I tried to reflash JH2 with Odin but this time the phone wouldn't even get to the Touchwiz lockscreen and just shut off on it's own. Went into recovery and did factory reset and wiped the cache, tried rebooting, didn't work. Tried to reflash JH2 and same thing again. So I tried flashing JP3 with Odin and I got into recovery mode allowing to reformat internal sd. Tried all the other recovery options (wipe cache, etc) and then tried internal sd formating. Don't remember the exact details but said something about not being able to find E: and sd card not mounted.
Now when i reboot i get the i9000 screen the "S" screen and then it goes into a weird screen that has red text on the upper left side with a little android behind the text and some yellow text on the upper right side saying: "Kernel panic, upload mode" and it won't go in either download mode or recovery.
At this point i have no idea what my problem is, i read about sd card failing on the i9000m, is this what happened? if not can i do anything to fix this?
Really running out of solutions right now, any help would be greatly appreciated.
Gab
P.S.
(don't know if this is relevant but had stock JG8, tried to flash kaplik JP6 which was really buggy and kept force closing (sort of, i would press power on to turn on screen and it would be a black background and have to load everything once again, GSM connection, wallpaper, widgets, etc.) so I flashed stock JH2 with Odin, which still did this sometimes but was far more stable than JP6)

First time CM7...fail...try again..

mkay o i'm kind of new to android and tonight i wet my pants cause i thoughy i bricked the optimus. I wanted to install CM7 but something went horribly wrong.
After I rooted and installed ROM manager I copied CM7 to my SD and installed. After it was done the CM7 boot screen kept looping. No way the phone was doing anything more than that.
The only other thing it would do was to sho a 'waiting for update' screen. After a lot of searching I mangaged to get stock ROM back by using smartflash, praise be...
Now that I know I can rescue the phone I'd like to know what whent wrong..any clues? Did I use the wrong build of CM7? I just used the latest of the 4th of july.
I want to try again but maybe some insight would be helpful, thanks...
Did you remember to tick the wipe data box in ROM Manager?
Well it would not install from rom
Manager (installation canceled by itself and ennded up with fresh install of LG rom...) so after that i did it from recovery. cant remember if i got the option to wjpe in there...
So when i installed from ROM manager i did xheck the wipe boxes. Then started installing from SD. The installation stopped, i have seen some sort of warning exclamation but i could not read what was wrong the message disappeared too fast. I think the 'wipe' was sucssesful though because all my apps and settings for stock LG firmaware were back to factory.
Ah ha.
ROM Manager and the stock ROM don't get on too well. Boot to recovery, wipe and install from there.
Assume you are using CWM recovery? It has the option to wipe on there if you look carefully so you can wipe it manually before flashing.
I tried again and it seems GB is now running cause I can see the battery icon on a different angle but it keeps givin me LG installation error messages after boot which i may ' forrxe close' but basicly nothing happens. Did i forget to wipe somerhing or forget to do smth else?
What recovery are you using? If it's 4.0.0.5, you might want to update to the newest 4.0.0.5, as the original one I built had some problems formatting.
The error messagel all seem to refer to LG apps or services. Device wont go beyond these messages.
I know, if it's what I'm thinking, they will have been left behind during the CM install, which shouldn't happen.
Ok so what do you think i should do? thanks for the snappy replies rusty.
Fyi, behind the error messages i can see a black background. The top bar with battery indicator is present, it charging. Signal indicator is there but has no signal.
Change recovery and flash again, either to 3.2.0.0 or the newest 4.0.0.5
this is what it looks like now. When i switch off and do volume down+ power its says waiting for S/W upgrade.
First i need to re-install syock again i guess? Wont do much else..
If you're getting software upgrade, you're letting go of power to early, keep em both held.
Edit: Or use 'adb reboot recovery'
hmkay im in recovery now thanks for that. It says 3.0.2.8
Signarure check enabled
Signature check disabled
Script asserts eneabled
Im not quite sure what you want me to do now. Thanks for your patience
Oh, 3.0.2.8 shouldn't have had any problems then, annoying.
Still, pik the wipe data/cache option, then install CM7
Im there thanks so much Rusty.

Categories

Resources