[2.1 OC ROM] Simply Stunning V1.0.0 (2/12/10)

[ChevyNo1]

Auto brightness should still be there .. I think it was a 1.1 OC from 1.0.0. Check it in SetCPU ... this is what is weird. I can experience the same issues as you, clock down to say 900 and it runs fine. Clock back up, has issues. Reboot recovery and wipe data, and it's fine again.

[airwake]

In SetCPU do you have "Set on Boot" selected?

[airwake]

Thanks for the help Chevy, it looks like using the 1.0 boot rom fixed my issues. I've had a couple reboots and everything still works fine. Glad to have this think working again!

[ChevyNo1]

Was that question intended for me? Yes, I have it set on boot ... I am doing more testing today, I flashed the kernel back from the virgin 2.0.1 ROM, which of course only runs at 550, and I haven't had a single FC or reboot yet, in all my typical trouble areas. This definitely seems related to the kernel - anyone having issues, have you tried to flash a Taz kernel on top of my ROM?

[gregsjh13]

IM FUSTRATED!...I LOVE YOUR ROM CHEVY BUT I JUST GOT 2 REBOOTS in 5 minutes.

[ChevyNo1]

IM FUSTRATED!...I LOVE YOUR ROM CHEVY BUT I JUST GOT 2 REBOOTS in 5 minutes.

Dude, I hear you - I have a repeatable situation on my hands where I can guarantee a crash - been working hours on isolating the issue!!!

[ChevyNo1]

Well everyone - after HOURS AND HOURS of testing every little thing that could be causing these reboots, and I mean rebuilding the kernel and all - I've come to this conclusion:

The 2.1 launcher SUCKS!!!

Every situation where I am able to guarantee myself a crash, does NOT crash on the 2.0.1 launcher. I have tried AdamZ's launcher; on 2.1 it simply has the same issues.

That being said - I am not actively working on patching Launcher2. I would rather continue to improve on the ROM, using the 2.0.1 launcher. I will continue to include the 2.1, but before you post up a bug regarding FC's / reboots, try to duplicate on the 2.0.1 launcher. If it still fails, then let me know and I will take a look. I of course will continue to search for answers for this, but I'm not in a position to get into the coding of the apk itself (at least right now).

Using the 2.0.1 launcher I have great results, even at 1.2Ghz.

Thanks for your continued support!

ps - here is the badness that shows up in logcat, ONLY on 2.1 launcher, and then it reboots:

V/RenderScript_jni( 1508): surfaceCreated
V/RenderScript_jni( 1508): surfaceChanged
V/RenderScript( 1508): setSurface 480 816 0xba3a90
E/IMGSRV ( 1045): sgxif.c:108: WaitForRender: Timeout
W/IMGSRV ( 1045): mapper.c:42: MapperDumpSyncObjects: Dumping all active sync o
bjects..
W/IMGSRV ( 1045): mapper.c:50: MapperDumpSyncObjects: Sync object ID=73, 0xFHWR
=0x0130, WOC DevVAddr=0xd80052c, ROC DevVAddr=0xd800534
W/IMGSRV ( 1045): mapper.c:50: MapperDumpSyncObjects: Sync object ID=72, 0xFHWR
=0x0300, WOC DevVAddr=0xd800d54, ROC DevVAddr=0xd800d5c
W/IMGSRV ( 1045): mapper.c:50: MapperDumpSyncObjects: Sync object ID=71, 0xFHWR
=0x0130, WOC DevVAddr=0xd8002d4, ROC DevVAddr=0xd8002dc
W/IMGSRV ( 1045): mapper.c:50: MapperDumpSyncObjects: Sync object ID=53, 0xFHWR
=0x0300, WOC DevVAddr=0xd80031c, ROC DevVAddr=0xd800324
W/IMGSRV ( 1045): mapper.c:50: MapperDumpSyncObjects: Sync object ID=52, 0xFHWR
=0x0300, WOC DevVAddr=0xd8002a4, ROC DevVAddr=0xd8002ac
W/IMGSRV ( 1045): mapper.c:50: MapperDumpSyncObjects: Sync object ID=50, 0xFHWR
=0x0130, WOC DevVAddr=0xd80022c, ROC DevVAddr=0xd800234
W/IMGSRV ( 1045): mapper.c:50: MapperDumpSyncObjects: Sync object ID=49, 0xFHWR
=0x0130, WOC DevVAddr=0xd800574, ROC DevVAddr=0xd80057c
W/IMGSRV ( 1045): mapper.c:50: MapperDumpSyncObjects: Sync object ID=3, 0xFHWR=
0x1000, WOC DevVAddr=0xd800064, ROC DevVAddr=0xd80006c
W/IMGSRV ( 1045): mapper.c:50: MapperDumpSyncObjects: Sync object ID=2, 0xFHWR=
0x1000, WOC DevVAddr=0xd80004c, ROC DevVAddr=0xd800054

[pokemaughan]

Keep it up!