Re: [TESTING] - NAND OMGB (Latest version 1.2.3) - 400/500 Only
 

This is a known issue and ive been looking for it for a while. I cant seem to locate it. Everything on the log points to "htc_get_batt_info" but i dont see any division over there.

Also i notice this only happens while charging. Wonder if charginign is killing the panel ..

anyways your issue is not like anish. Your kernel logs look clean and there is no msm_fb time outs. Maybe the next kernel will help you too .. :disgust:

Re: [TESTING] - NAND OMGB (Latest version 1.2.3) - 400/500 Only
 

hey ACL,
Im glad we found something.
in regards to wifi, i leave it on while im at home, but when ever its off i have no problems putting the phone to sleep, even when with the old Lk where gps worked.

the apps the you mentioned, i can only recognize two which is Clocksync, which seemed to sync with this install, but i will soon uninstall because i dont have a problem with the clock. and i think the com.bwx.bequick maybe for quickpic or quick settings? the other two i have no idea.

i have attached the grep panel log too.

Re: [TESTING] - NAND OMGB (Latest version 1.2.3) - 400/500 Only
 

[ 1.488952] htcrhod_init_panel: Initializing panel id=20

Nice job.

Re: [TESTING] - NAND OMGB (Latest version 1.2.3) - 400/500 Only
 

so i did get the right log, correct?

Re: [TESTING] - NAND OMGB (Latest version 1.2.3) - 400/500 Only
 

I'd say so, I'm pretty sure that's what ACL wanted to know - if you had a different panel type than the rest of us. It appears you have the same panel type, so the mystery continues.

Do you have an SD card mounted? Some have said that caused wacky issues, especially if the card is dying. I'd be curious, pull the card and see if the panel wake problems ensue.

Re: [TESTING] - NAND OMGB (Latest version 1.2.3) - 400/500 Only
 

Yeah arrgg is right. 20 is what most of us have so this is still a little strange. Before i left home this morning i left the build cooking, so hopefully sat or sun there will be a new release out. This is the first time ive see the msms fb time out in ages.

Re: [TESTING] - NAND OMGB (Latest version 1.2.3) - 400/500 Only
 

hmm. ok ill pull the sd and see if it continues. I just bougt the SD card two months ago. hopefully it's not that


update: SD card removed. still getting failed screen wake

Re: [TESTING] - NAND OMGB (Latest version 1.2.3) - 400/500 Only
 

Decided to take the plunge today and try OMGB. :headbang:

I figured I would relate my experiences in case anyone else has similar stumbling and fumbling.

Installing the rhodimg.nbh took a couple tries, something about the first 1GB SD card I chose was not liked by the boot loader. The second 1GB (also Sandisk, identical from all appearances) worked first time out. Go figure.

Once I got that rolling I couldn't attach to the phone via adb/fastboot. Windows was popping up a "new device" dialog, so I figured it had to be driver related, even though adb (and droid explorer) work with FRX7.1 without issue.

I ended up editing the Google/Android USB driver to add the VID/PID (18D1/0001) that was shown in the device manager and then allowed Windows to "re-install" the driver. Now I finally have access to the phone via fastboot.

Using fastboot to install the recovery image was a breeze, as was getting OMGB 1.2.3 installed from within recovery.

Booting OMGB went surprisingly fast, I waited for the system to settle out before rebooting back into recovery to install Gapps.

Installed the full (20mb) gapps.zip and rebooted. When I got into OMGB they were nowhere to be found. Rebooted into recovery and tried again, but still no sign of gapps when I went back into OMGB. :scratch:

Back into recovery, wiped the cache and data partitions, booted back into OMGB and again waited for things to settle out. This time into recovery I tried Vzi's minimal gapps and it worked.

Are there any known issues with the full version of Gapps and 1.2.3?

My next stumbling block (yet to be fixed/understood) is that Market from vzi's minimal gapps is FC after a short time. It loads, sometimes search works, sometimes FC. I managed to install one application (Zeam), but that seems to be about it - too many FC to get anything done.

Should I try 1.2.2 since it's "more stable", or is there something I can do to fix Market in 1.2.3?

Next question is in regards to APNs... it seems like they are not fully working - I set it up and click "save" but the APN doesn't appear. I need to use an APN to get MMS working with Boost, so if there is anything I can do to help debug why it's not working let me know. I'm guessing this is an artifact of needed GSM support...

Also, I can't seem to reboot into recovery from within OMGB (via the power down menu choices). The phone just appears to freeze, I end up pulling the battery to get it to reset.

All in all I have to say I'm quite impressed. If I can get Market working (so I can install a couple of apps I really use a lot) this will be awesome.

Re: [TESTING] - NAND OMGB (Latest version 1.2.3) - 400/500 Only
 

Sigh... I guess we need a better list of broken things and how to fix them.

Only time I had an issue with this is when one of my cards was oddly formatted to FAT instead of FAT32... Not sure what else causes SD cards to not work flashing NBH's... definitely need to fix the issue where you can't flash over USB.

I thought I said this here as well, but I use the gapps package from Cyanogen. There's only one package for CM7/GB, and it's always worked great for me. ACL - perhaps you should just link to it, and pull down the one you put up.


This one's been covered quite a few times - set your language to something meaningful under Settings, Language & Keyboard.

CDMA doesn't actually use APN's. At all. That was a hack hyc used in order to easily pass information from the end-user to the system...

Also, APN's will disappear/be ignored if you don't put in the correct MCC/MNC... which again is probably related to the fact that CDMA devices don't actually use APN's.

I've had some good luck and some bad with rebooting. Sometimes it hangs, other times it works great. I'm not sure why it works some times and not others tho... I also might be mixing up bugs, there's a couple different recoveries - are you using AOSP or CWM?

[QUOTE=arrrghhh;2158339]
Also, APN's will disappear/be ignored if you don't put in the correct MCC/MNC...[/QUOTE

Does your apn stick with sprint, I haven't had luck with it even with correct mcc et al



Sent from my Touch Pro 2 using Tapatalk