[TESTING] - NAND OMGB (1.2.3)

[boggsie]

Originally Posted by arrrghhh

You shouldn't need to task29 again. While it's not a bad idea, it only works via USB/Windoze. I always just throw a RHODIMG.nbh from a WinMo ROM at the root of the SD and flash back to WinMo. Never had a problem reverting.

As I was hoping to relate, I don't feel this has anything to do with Android or OMGB ... something is up with my eMMC because I can't get anything (RHODIMG.nbh) to flash - period - via any method I have tried or am aware of. It really is quite bizarre.

Best regards,
-boggsie

[arrrghhh]

Originally Posted by boggsie

As I was hoping to relate, I don't feel this has anything to do with Android or OMGB ... something is up with my eMMC because I can't get anything (RHODIMG.nbh) to flash - period - via any method I have tried or am aware of. It really is quite bizarre.

That's not good. I would definitely investigate that, lest you end up with a brick.

[trevoroni]

Originally Posted by arrrghhh

I always post to pastebin. I'll try on the SD now.

Edit - works great to the SD as well. Said "File saved to: /mnt/sdcard/Android/data/com.GetLogs/files/data.txt"

Perhaps I have a newer version? Try the one attached.

That one works. Thanks!
Looks like you have a newer version then the one posted on XDA.
I'll try and get a log today if it happens again.

Edit: Here's a log where the screen doesn't wake on the first try, but does on the second.

[arrrghhh]

Originally Posted by trevoroni

That one works. Thanks!
Looks like you have a newer version then the one posted on XDA.
I'll try and get a log today if it happens again.

Edit: Here's a log where the screen doesn't wake on the first try, but does on the second.

Looks like you might have some apps causing this issue (pure speculation FYI):

<4>[ 4375.224456] select 1327 (weather.android), adj 15, size 3556, to kill
<4>[ 4375.224487] send sigkill to 1327 (weather.android), adj 15, size 3556
<4>[ 4376.011291] select 1394 (facebook.katana), adj 14, size 8354, to kill
<4>[ 4376.011352] send sigkill to 1394 (facebook.katana), adj 14, size 8354
<6>[ 4376.601348] request_suspend_state: wakeup (3->0) at 4364840000000 (2011-11

Accuweather & Facebook. Do you have this problem on a fresh install, no apps? I'm just wondering if it's some app that is causing an issue. I don't use either of these apps.

[trevoroni]

Originally Posted by arrrghhh

Looks like you might have some apps causing this issue (pure speculation FYI):

Accuweather & Facebook. Do you have this problem on a fresh install, no apps? I'm just wondering if it's some app that is causing an issue. I don't use either of these apps.

I'm not sure if it happened on a fresh install, it was shortly after I installed that I loaded up the apps I use frequently.
I could try uninstalling those two for starters and see if that helps.

Would an app make a difference if it happens more regularly when the phone is charging? It fails to wake on the first try ~50% when it is plugged in as opposed to rarely ever when it is not plugged in.

[arrrghhh]

Originally Posted by trevoroni

I'm not sure if it happened on a fresh install, it was shortly after I installed that I loaded up the apps I use frequently.
I could try uninstalling those two for starters and see if that helps.

Would an app make a difference if it happens more regularly when the phone is charging? It fails to wake on the first try ~50% when it is plugged in as opposed to rarely ever when it is not plugged in.

I doubt it, but I've never had a failed wake problem on NAND. Used to happen on the time on HaRET, now it "just works".

Edit - besides, the phone isn't actually sleeping when it's on the charger, so I don't know what the hell to call that. It's not a failed wake, as the phone isn't even asleep.

Edit 2 - is this consistently reproducible? Put it on the charger, phone fails to wake? I certainly can't reproduce that. Please try on a freshly installed build, no apps - see if you still have the failed wake issue when charging. If so, I'd like to see those logs. Thanks.

[kylanschilling]

Originally Posted by arrrghhh

Format the card FAT32. That's all you need to be able to flash, assuming you put RHODIMG.nbh at the root of the SD. Never had a problem, with any SD assuming it was formatted correctly.

Use the HP Tool to format. Full format, FAT32.

thanks. i just tried that and still no go. iv tried everything else anyone else has mentioned aswell like formatting the card to 2 gb or smaller since its a 8gb sd card. i dont have anyhting smaller or transportation to go buy a smaller one

[arrrghhh]

Originally Posted by kylanschilling

thanks. i just tried that and still no go. iv tried everything else anyone else has mentioned aswell like formatting the card to 2 gb or smaller since its a 8gb sd card. i dont have anyhting smaller or transportation to go buy a smaller one

You only have one SD card?

*shrug*. I've always flashed via SD card, even back in the WinMo days. I hated the thought of booting Windows just to flash the stupid phone.

[[ACL]]

Originally Posted by vzihome

Why is enabling buttons interfere with gsm?

Sent from my Touch Pro 2 using Tapatalk

the gpio buttons for gsm are currently not creating interrupts like they do for cdma. I'm im tired of people not being able to press the end call key so i disabled on cdma which helps gsm boot.

You are welcomed to add it Here is my LK code

https://gitorious.org/~acl/lk-msm720...mits/google_lk

Also this hboot menu you speak of was never part of the google or CA lk, so it's really not something out of the box.

[trevoroni]

Originally Posted by arrrghhh

Edit - besides, the phone isn't actually sleeping when it's on the charger, so I don't know what the hell to call that. It's not a failed wake, as the phone isn't even asleep.

I guess so. It's more of a failed panel initialization since the phone still responds to the touchscreen, via vibration of where the 'slide to unlock' should be displayed.