Re: [TESTING] - NAND OMGB (1.2.3)
 

Had a weird lock-up today. I couldn't wait for it to sleep/recover (needed to make a call), but attached is the last_kmsg I pulled after things came back online.

Hope it helps.

Re: [TESTING] - NAND OMGB (1.2.3)
 

damn this one is hideous.. first time im seeing this. Looks like something happened to sound while using microp.

[48242.385284] Can't set tpa's reg
[48242.385345] tpa2016d2: tpa_set_register: reg 4, value 0x0
[48244.347717] msm_i2c msm_i2c.0: Error waiting for notbusy
[48244.347808] msm_i2c msm_i2c.0: Still the bus master, status 9b01, intf 200
[48244.347869] msm_i2c msm_i2c.0: i2c_scl: -524, i2c_sda: -524

need to hunt this thing down and figure out what happened.

What is the clock speed on deep sleep? Reason I ask is because if you enable wireless tether and disconnect it from power, the AP is visible but no packet passes (including the dhcp reply) while the Rhod is in deep sleep.

Right now I can wakelock it via Terminal Emulator, but ideally tether could do on it's own whenever a client connect.

-- Starfox

Re: [TESTING] - NAND OMGB (1.2.3)
 

Another lock-up this morning. Fortunately I could wait for it to sleep/recover.

Pulled last_kmsg and ran GetLogs, both attached.

Interesting tidbit in last_kmsg, second to last line says "ARM9 crashed"

Phone did eventually go back to sleep and recovered. When I woke it back up it had a FC dialog waiting, but that dismissed without issue.

Phone is still running without rebooting since the lockup/recovery.

Re: [TESTING] - NAND OMGB (1.2.3)
 

Were you using GPS? Just curious, I've heard of that happening a lot when the GPS is in use.

Re: [TESTING] - NAND OMGB (1.2.3)
 

Yup. Was just starting up Navigation, which has been flawless since detule's updated lib and the injector.

Re: [TESTING] - NAND OMGB (1.2.3)
 

Wrong thread, we should take this to the xtra thread, but looking at your crash it looks to me like it's unrelated to the xtra injections. In particular

This sequence seems incorrect and something that should be fixable.

Re: [TESTING] - NAND OMGB (1.2.3)
 

The screen went "half bright", so it's possible I accidentally bumped the END button. I have END set to go to the home screen, which would have sent the gps_stop signal...

Still odd it would have created a lock-up, but definitely a possible answer as to the cause.

Re: [TESTING] - NAND OMGB (1.2.3)
 

Partial Update (2-21-2012)

Unfortunately I left too many things open to publish the latest OMGB so for now i'm just going to release latest LK and Recovery.

It's no longer a secret, we now will use cwm as our main recovery. Note this is not the same as the one originally posted, so if you downloaded that one. Just get rid of it and use this below.
http://rhodium-nand.googlecode.com/f...m_recovery.img

This recovery also includes a piece of code that will help me identify some of the sub variants. So if you have a tellus or one of the rhod100's who has the broken keyboard, you need to do the following

adb shell
#cat /sys/class/htc_hw/cid
CWS_001

Note the output above is from the test rhod300 i have. You should have a different value. Goal here is for the rhod500 tellus users to see what their CID is and if its not the default verizon, then use a diff keyboard. Same logic applies to rhod100 folk


Also the latest LK is here. This is hopefully the last time you will need to wipe your phone to update LK using the NBH. We can now update LK from fastboot directly making the NBH a one time install.

Here is a list of fixes on LK
1) Serial number is now the OEM serial. I finally found it on nand so we dont need to generate one.
2) I now double check the variant from mem and nand. Just to be safe.
3) Lk can update itself now. Big improvement since you dont need to wipe anymore to update.

Re: [TESTING] - NAND OMGB (1.2.3)
 

Does this NBH safe? Just use RIFFBOX to repaired my phone from RHOD100 to RHOD400.