Re: [TESTING] - OMGB - 1.2.2{2.3.5} - 400/500 Only
 

I've been getting failed wakes quite regularity all day. Seems to happen more often when it's charging. Here's a quick log from where it took multiple times of pressing the power button (the keys light up) and the touchsreen responds by vibrating if you touch where the 'slide to unlock' should appear but the screen isn't on. Once the key lights turn off and I try to wake again sometimes it works, other times it takes three or four tries before it comes on.
Edit: Occasionally the screen flickers on for like 1/10th of a second before it turns off again, maybe it's registering my single button press as multiple?
I don't use any overclocking app and the only tweak i've applied is the supercharger script on aggresive and hard to kill launcher.
Other then that, everything has worked good, GPS works good and sleep happens right away with it left on. It took about 10 minutes to get a lock the first time but that's expected I guess, now it's usually within a minute.
Hopefully this works, it's my first time posting a log...

Re: [TESTING] - OMGB - 1.2.2{2.3.5} - 400/500 Only
 

To get gapps to load, go to mounts and storage and mount system, then you can install gapps.

As far as your not getting anything to flash, try leaving your battery out for a minute or two? I saw that you tried LK NBH from sd card, did you try WM ROM from sd too?

Re: [TESTING] - OMGB - 1.2.2{2.3.5} - 400/500 Only
 

yeah but too much work .. lol.

Re: [TESTING] - OMGB - 1.2.2{2.3.5} - 400/500 Only
 

something is pegging your cpu. thats all i cas see.

Re: [TESTING] - OMGB - 1.2.2{2.3.5} - 400/500 Only
 

Finally found people have same problem with me. something is pegging my cpu, all apps installed on OMGB is same with installed on FRX7, FRX7 works well without this problem.
In last posts, not only trevoroni has fail wake issue.

ACL, this build is modified by which OMGB version? INCREDIBLE? INCREDIBLE 2? HERO?
OMGB | T3hH4xx0r

Re: [TESTING] - OMGB - 1.2.2{2.3.5} - 400/500 Only
 

+1 for the same behavior here (no high cpu usage). Only happening on most recent build, not the build previous to it. Perhaps light sensor problem? The screen will come on and then immediately fade to dark, perhaps 2 or 3 times. Sometimes it doesn't happen, sometimes it does.

Michael

Re: [TESTING] - OMGB - 1.2.2{2.3.5} - 400/500 Only
 

This build is 100% from source. Not some binary hack.. who the hell do you think i am ? lol

I'm not going to solve any pegging issues for you guys. There is a high percentage that have no issues with the same devices. So unless i can replicate it or have some useful logs, I cant do much :(.

When the pegging is happening, do a top and see what process is consuming the most. Maybe its a bad app, or possibly the gps. GPS isnt not perfect.

Re: [TESTING] - OMGB - 1.2.2{2.3.5} - 400/500 Only
 

In reality if it was a light sensor problem, disabling the auto back light would make your issue go away. Since polling the light sensor is done at a fixed rate, i doubt its this.

Try this. Remove /system/lib/hw/gps.rhodium.so and reboot. This is the gps lib and without it you pretty much have the old build. Test and see whats going on. The logs posted by trevoroni show almost nothing. Only thing we know the cpu is crunching away at something. once the cpu is pegged, all hell breaks loose and people start blaming anything.

Re: [TESTING] - OMGB - 1.2.2{2.3.5} - 400/500 Only
 

That's really the whole issue people. The logs posted show NOTHING useful, other than the processor is pegged by "something".

GetLogs is a great app (see the Logs topic on the wiki), and I recommend everyone use it if they want to pull logs. It shows processes in top, and has corresponding logs from the kernel - so in theory lines can be matched up, because again in this case just a logcat with no timestamps is useless.

Re: [TESTING] - OMGB - 1.2.2{2.3.5} - 400/500 Only
 

Here's what Getlogs spit out after having a few failed wakes this morning. In the logs it failed to wake on about every second attempt at the end.
Wifi, GPS and network location are all off, phone is plugged into AC charger.
It doesn't say anything about the CPU being pegged this time.

Regarding a separate issue, is there a way to change the physical keyboard layout? My Telus phone is a Rhod500 but it has a keyboard like the Sprint Rhod400. Pretty much all custom Rom's for windows mobile put it as a Rhod500 keymap and a registry hack was needed to get it to the correct one, on XDAndroid I could just edit startup.txt, so it's not just this build that has this issue. Is there a file to change on this build or is it set on boot?