[TESTING] - NAND OMGB (1.2.3)

[viber]

Just now flash my phone nand omgb with new ril inside zip. (with task29 before).
-GSM don't work anyway
-when display shut of status led must be green. But not in my case is stay orange.
here is some logs

[teemo]

Maybe its just me being confused and not paying attention, but...
Has anyone on RHOD100 had any luck with RIL and data connection?

I have the idea that the new RIL is only to get 400/500 on GSM.

Am I way off ?

[vzihome]

Originally Posted by [ACL]

hmm well i dont need the numbers of your ts-calib file but of the calib file generated on first boot. You can always grab a fresh one by doing this on adb shell

cat /sys/android_tp_cal/tp_cal

It should match your tri color numbers but in a different order.

I did a fresh install and didnt get any info, thats why i posted the other rhodiums numbers ill try that when i get home

Sent from my Touch Pro 2 using Tapatalk

[[ACL]]

Originally Posted by teemo

Maybe its just me being confused and not paying attention, but...
Has anyone on RHOD100 had any luck with RIL and data connection?

I have the idea that the new RIL is only to get 400/500 on GSM.

Am I way off ?

No one has reported success. Follow my thread on Xda since there are more gsm users there. I'm really hoping you guys can team up and come up with a good list of bugs to kill. To be honest im surprised it even booted, but now its time to get down and dirty.

[[ACL]]

Originally Posted by viber

cat android_tp_cal/tp_cal show me
815,854,214,872,513,525,816,203,213,205
in ts-calibration of sdcard builds little bit different but with this parameters touch screen works better:
820,881,183,879,497,529,822,179,181,178
Can i edit android_tp_cal and put there digits from ts-calibration file?

no those are in nand from wince. its done by the kernel and cant be modified. (well at least not yet. In the future we might venture into it)

your orig tri color : 507,524 799,845 788,201 221,210 221,847

Something is not right since the data is not matching your tri color. For now just use your old ts calib file and put it on the /data/ since thats where android reads it from.

When we first boot cleanly, the script below executes to generate the /data/ts-calibration

	cat /sys/android_tp_cal/tp_cal > /data/ts-calibration
        cat /data/ts-calibration > $touchscreendir/calibration_points

So as long as you have a valid /data/ts-calibration, the ts will use those.

Also forget about the old build, the 12-5 build will most likely be the new stable. So this ts calib system is here to stay. We just really need to find a ts calib app incases where you want to recalib such as you do now.

[mbellot]

OK, I need to completely rescind my statements about OMGB and power management.

I downloaded an app called "Battery Calibration" which deletes the existing battery cal data file and forces the system to recreate it.

Below is a picture of my phone ~ 10 minutes before it finally shut down.

Approximately 38.5 hours run time on a single charge.

ACL - You are DA' MAN!

[[ACL]]

Originally Posted by mbellot

OK, I need to completely rescind my statements about OMGB and power management.

I downloaded an app called "Battery Calibration" which deletes the existing battery cal data file and forces the system to recreate it.

Below is a picture of my phone ~ 10 minutes before it finally shut down.

Approximately 38.5 hours run time on a single charge.

ACL - You are DA' MAN!

no you da man. Cuz i had no idea about this app. haha. Actually i think clockwork mod has the ability to wipe. Hopefully soon it will be our primary recovery and we can do away with the old legacy recovery. I forget that thing is from the good ol froyo days.

are you using this as a daily phone ? Also how is your ts calibration doing since vzihome is having issues and im wondering who else

[trevoroni]

I had issues using the calibration from winmo. I specifically flashed to the rom I used before I switched to this (Blackout rom-winmo 6.1) and calibrated before flashing the new build.
I replaced the ts-calibration file with the sd card one and it is much better.

I have also had 36+ hours of battery life with minimal use, a few short calls, a dozen or so texts and a little web browsing. I average 14-16 hours during a normal day. This is with a new OEM battery, before I got the new one I was lucky to get 6 hours with normal use. =D>

I've been using this as my daily phone for the past 3 weeks and it's been great, now that I updated to the Verizon radio and haven't had any more slow wakes I can honestly say that my phone is just as good as my GF's Hero, which is similar in hardware specs except native Android.

[[ACL]]

Originally Posted by trevoroni

I had issues using the calibration from winmo. I specifically flashed to the rom I used before I switched to this (Blackout rom-winmo 6.1) and calibrated before flashing the new build.
I replaced the ts-calibration file with the sd card one and it is much better.

I have also had 36+ hours of battery life with minimal use, a few short calls, a dozen or so texts and a little web browsing. I average 14-16 hours during a normal day. This is with a new OEM battery, before I got the new one I was lucky to get 6 hours with normal use. =D>

this is good to hear. cdma will go full stable soon after one final update to include gps. Lot of little buggs getting killed.

I had to consult with cotulla on the calib points. we have the right numbers but we may not have the orientation correct. They may be inverted. So i'll play with it tonight and see what can be done about this.

[viber]

I'm really hoping you guys can team up and come up with a good list of bugs to kill.

If we need team up us, then on XDA need start thread (for rhod100 testers)and add on top of page instructions (standard) how people must report about his found issues and how they can collect logs and of course they must put logs with his issues. Other post will be ignored and deleted. Also in top of thread can be added basical exercise. Like check mobile settings save radio logs, on-off autobrightness, try to sleep and awake device, seve dmesg logs. Of course with explaining how to get them.