[TESTING] - NAND OMGB (1.2.3)

[[ACL]]

Originally Posted by sykosoft

+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

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.

[arrrghhh]

Originally Posted by [ACL]

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.

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.

[trevoroni]

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?

[[ACL]]

Originally Posted by trevoroni

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?

something wrong with your setup. You have way too many application errors with no real info behind them. Also did you use cwm as your recovery ?

Also you have some widget issues. I cant support specific app setups so you need to do a full wipe again. Sorry. If we have an App causing issues, then we can drill on that but we cant change code just because of one app.

[trevoroni]

Originally Posted by [ACL]

something wrong with your setup. You have way too many application errors with no real info behind them. Also did you use cwm as your recovery ?

Also you have some widget issues. I cant support specific app setups so you need to do a full wipe again. Sorry. If we have an App causing issues, then we can drill on that but we cant change code just because of one app.

Ok sounds good.
No, I used the recovery from the first post.

Sorry, I couldn't provide any useful information. Hopefully a fresh install will fix the problem... I'll probably wait until the next update however since it doesn't bother me too much since it only really occurs when it's charging, and when it's charging a rarely use my phone.

[[ACL]]

Originally Posted by trevoroni

Ok sounds good.
No, I used the recovery from the first post.

Sorry, I couldn't provide any useful information. Hopefully a fresh install will fix the problem... I'll probably wait until the next update however since it doesn't bother me too much since it only really occurs when it's charging, and when it's charging a rarely use my phone.

also there is a script inside /system/bin/rhodium-seq.sh i belive. that handles the keyboard setup. You can run it manually if you feel your kb was not properly detected.

next release will be a big one. moving to 2.3.7

[boggsie]

Originally Posted by [ACL]

also there is a script inside /system/bin/rhodium-seq.sh i belive. that handles the keyboard setup. You can run it manually if you feel your kb was not properly detected.

next release will be a big one. moving to 2.3.7

Since it appears that my phone is completely stuck with LK as my rom, bring on the updates !!

<F5><F5><F5><F5><F5><F5><F5><F5><F5>

Best regards,
-boggsie

[trevoroni]

Originally Posted by [ACL]

also there is a script inside /system/bin/rhodium-seq.sh i belive. that handles the keyboard setup. You can run it manually if you feel your kb was not properly detected.

next release will be a big one. moving to 2.3.7

Looking forward to it! Keep up the great work.

I ran rhodium-nand-seq.sh and here's what it came up with:

Command:
'/system/bin/rhodium-nand-seq.sh' 
-------------
Out:
exec sh '/system/bin/rhodium-nand-seq.sh' 
# exec sh '/system/bin/rhodium-nand-seq.sh' 
/system/bin/rhodium-nand-seq.sh: /bin/grep: not found
[: RHOD300: unknown operand
[: RHOD210: unknown operand
[: RHOD400: unknown operand
[: RHOD500: unknown operand
CAN'T DETERMINE RHODIUM VARIANT TYPE
RHOD500
cp: can't create '/system/usr/keychars/qwerty.kcm.bin': File exists

I think the issue is that Telus phone's are Rhod500's but have a keyboard like Rhod400's... why couldn't they make life easier and only produce one version of our phones?

[arrrghhh]

Originally Posted by trevoroni

Here's what Getlogs spit out after having a few failed wakes this morning.

There's no way you used the GetLogs app. The logcat has no timestamps, there's no kernel logs and the PS section at the end is missing. Plus the top part doesn't have any of the other stuff GetLogs provides. Please use the app for future log posts.

Originally Posted by boggsie

Since it appears that my phone is completely stuck with LK as my rom, bring on the updates !!

Wait, what? Did I miss something? LK is not a ROM. If he updates anything, it'll be the system image - I don't think there'll be any more updates for LK unless there's some GSM-specific stuff that needs to be baked in.

If you can't get LK or any other NBH to flash, you might be SOL. You never really updated us on that problem.

Originally Posted by trevoroni

I think the issue is that Telus phone's are Rhod500's but have a keyboard like Rhod400's... why couldn't they make life easier and only produce one version of our phones?

Just do it manually. The keyboard script doesn't run properly anyways, ACL mentioned this a few posts back.

[boggsie]

Originally Posted by arrrghhh

Wait, what? Did I miss something? LK is not a ROM. If he updates anything, it'll be the system image - I don't think there'll be any more updates for LK unless there's some GSM-specific stuff that needs to be baked in.

Apologies - my terminology is still catching up ... coming over from WM, I grew accustomed to referencing the NBH as the ROM.

So, as of late yesterday, I got the updated (RHODIMG_TESTING.NBH) flashed. I was able to install the non-CWM recovery.img file. I have been able to install the OMGB_rhodium-1.2.2.zip and GAPPS.zip.

Android on TP2 / eMMC is working quite well. I have market up and running (thank you for location and language tip) and have installed and am using various applications, without incident. For the purposes of this thread, I am all set and looking forward to updates.

What did occur in the process, is at some point, something unexpected happened and the results are that I can no longer flash (either via SD or USB) my phone with any RHODIMG.NBH file.

I cam to find this out, because, being a creature of habit, I wanted to ensure that I could reproduce the success. First step: wipe everything with Task29. Surprisingly, it would not flash ... I can't say that this has anything to do with Android or OMGB, so I started another thread to solicit tips on overcoming that particular issue.

Best regards,
-boggsie