[TESTING] - NAND OMGB (1.2.3)

[vzihome]

Originally Posted by PedroDaGr8

Whoo hoo! I finally am able to join the land of nand! Replacement TP2 after the previous one decided to perpetually flash up the Video Out screen in WM. First time I tried (before x-mas) LK kept thinking the end key was pressed. So I gave up. Tried again today from scratch, following the wiki (which by the way to which I added a comment about a minor correction); deleted EVERYTHING, made sure to erase all of the partitions multiple times, flashed recovery 4x times before rebooting. Boom. IT WORKS!

I have to say you guys are awesome. This runs lightyears more smoothly than FRX. Swype was always a bit laggy in FRX. Now it runs smooth as butter.

Now I just need to find the post where you put the calibration apk. because mine is off pretty wicked (it appears to be missing the top ~10-20 pixels and the bottom 10-20 pixels plus about 10 on the right side).

Just install the apk and run the app

Edit: re-read post my bad

Sent from my Touch Pro 2 using Tapatalk

[muziling]

Originally Posted by [ACL]

Do you know exactly what line ? I mean this could only happen if buffer->batt_tempRAW is 0. Can you printK to see if thats the case ?

Our battery chip is ds2746, same as HD2?

Division by zero must be buffer->batt_tempRAW equal 2600

<7>[ 49.493133] hw3d: was enabled
<6>[ 53.186035] [BATT-INFO];id=361, vol=4010, temp=500, current=120, level=88, charging_source=0, charging_enabled=0, full_bat=0, batt_tempRAW=2614
<6>[BATT-INFO];id=365, vol=4011, temp=500, current=120, level=87, charging_source=0, charging_enabled=0, full_bat=0, batt_tempRAW=2610
<6>[BATT-INFO];id=364, vol=4011, temp=500, current=120, level=87, charging_source=0, charging_enabled=0, full_bat=0, batt_tempRAW=2605
<6>[BATT-INFO];id=366, vol=4015, temp=500, current=120, level=87, charging_source=0, charging_enabled=0, full_bat=0, batt_tempRAW=2604
<6>[BATT-INFO];id=365, vol=4015, temp=500, current=120, level=88, charging_source=0, charging_enabled=0, full_bat=0, batt_tempRAW=2601
<6>msm72k_udc: OFFLINE -> ONLINE
<6>[ 95.141113] hsusb: reset controller

Here has some chips driver: https://gitorious.org/~dorimanx/linu.../drivers/power

[[ACL]]

Originally Posted by PedroDaGr8

Whoo hoo! I finally am able to join the land of nand! Replacement TP2 after the previous one decided to perpetually flash up the Video Out screen in WM. First time I tried (before x-mas) LK kept thinking the end key was pressed. So I gave up. Tried again today from scratch, following the wiki (which by the way to which I added a comment about a minor correction); deleted EVERYTHING, made sure to erase all of the partitions multiple times, flashed recovery 4x times before rebooting. Boom. IT WORKS!

I have to say you guys are awesome. This runs lightyears more smoothly than FRX. Swype was always a bit laggy in FRX. Now it runs smooth as butter.

Now I just need to find the post where you put the calibration apk. because mine is off pretty wicked (it appears to be missing the top ~10-20 pixels and the bottom 10-20 pixels plus about 10 on the right side).

Calib is on the project page. Just go to the dl page and download it. Put it on your sdcard and enjoy.

[[ACL]]

Originally Posted by muziling

Our battery chip is ds2746, same as HD2?

Division by zero must be buffer->batt_tempRAW equal 2600

No idea what our chip is. Its all handled by smem so i dont think we have a individual controller like the HD2. Trust me i tried to write the code. We even disassembled a battery thinking it might be inside, nothing found ..lol.

I just realised this is written on the code

/* TODO: temp algo is not ok..if someone have the timte -> must look into the driver */

I guess I'll have to look into winmo see how the temp is handled. For now i guess we can just have a little check to see if it hits 2600 and we can just manually set av_index to 0.

[PedroDaGr8]

Originally Posted by [ACL]

Calib is on the project page. Just go to the dl page and download it. Put it on your sdcard and enjoy.

Haha, dunno how I missed that. I was on pg 50 decided to see if anyone had replied. LOL

ANyways, I side-loaded it using DroidExplorer and it worked PERFECTLY! I now have a fully working touch screen.

I am super stoked!

\\Thanks again. You guys rock.

[muziling]

Originally Posted by [ACL]

I guess I'll have to look into winmo see how the temp is handled. For now i guess we can just have a little check to see if it hits 2600 and we can just manually set av_index to 0.

Confirm

<6>[ 1909.437347] [BATT-INFO];id=364, vol=3892, temp=500, current=120, level=73, charging_source=0, charging_enabled=0, full_bat=0, batt_tempRAW=2600
Division by zero in kernel.
<4>[ 1909.437469] [<c0281da8>] (dump_stack+0x0/0x14) from [<c002df94>] (__div0+0x18/0x20)
<4>[ 1909.437652] [<c002df7c>] (__div0+0x0/0x20) from [<c0142eac>] (Ldiv0+0x8/0x10)
<4>[ 1909.437744] [<c00568ec>] (htc_get_batt_info+0x0/0x8f0) from [<c0057c7c>] (htc_battery_thread+0x54/0xa0)
<4>[ 1909.437896] [<c0057c28>] (htc_battery_thread+0x0/0xa0) from [<c0060ed8>] (do_exit+0x0/0x7a8)
<4>[ 1909.438018] r7:00000000 r6:00000000 r5:00000000 r4:00000000

[[ACL]]

Originally Posted by muziling

Confirm

thanks muz. can you post this on the project page as an issue. I dont want to loose track of all your work. I'll patch it up for next release.

[muziling]

Originally Posted by [ACL]

thanks muz. can you post this on the project page as an issue. I dont want to loose track of all your work. I'll patch it up for next release.

Issue 16
I notice buffer->charging_source equal 0 or 2, never 1 whether plug USB with PC or AC.

struct battery_info_reply {
    u32 batt_id;        /* Battery ID from ADC */
    u32 batt_vol;        /* Battery voltage from ADC */
    u32 batt_temp;        /* Battery Temperature (C)corrected value from formula and ADC */
    s32 batt_current;    /* Battery current from ADC */
    u32 level;        /* formula */
    u32 charging_source;    /* 0: no cable, 1:usb, 2:AC */
    u32 charging_enabled;    /* 0: Disable, 1: Enable */
    u32 full_bat;        /* Full capacity of battery (mAh) */
    u32 batt_tempRAW;    /* Battery Temperature (C) from formula and ADC */
};

[mbellot]

ACL - Things have been running so smoothly I just had to mess with it.

One of the few features I really would like is GPS, so I downloaded GBX0B and yanked the gps.xdandroid.file. Pushed it into /system/lib/hw as gps.rhodium.so and rebooted.

Maps and other GPS programs seemed to work well, so I decided to push it. I left Maps running yesterday on my way home and today on my way in, attached are the last/kmsg files from the reboot that happened in each case (yesterday made it almost 30 minutes, this morning was more like 15).

If I'm reading it right it looks like a surfaceflinger stack overflow, but reading logs isn't my strong suit.

Anyway, if I'm going outside the testing you're after just tell me to stop. I just figured since it hadn't broke in several days I needed to fix it.

[arrrghhh]

Originally Posted by mbellot

ACL - Things have been running so smoothly I just had to mess with it.

One of the few features I really would like is GPS, so I downloaded GBX0B and yanked the gps.xdandroid.file. Pushed it into /system/lib/hw as gps.rhodium.so and rebooted.

Maps and other GPS programs seemed to work well, so I decided to push it. I left Maps running yesterday on my way home and today on my way in, attached are the last/kmsg files from the reboot that happened in each case (yesterday made it almost 30 minutes, this morning was more like 15).

If I'm reading it right it looks like a surfaceflinger stack overflow, but reading logs isn't my strong suit.

Anyway, if I'm going outside the testing you're after just tell me to stop. I just figured since it hadn't broke in several days I needed to fix it.

Hah, nice. Curious, what version of Google Maps? v6.x seems to have problems, but not these kind...

I would like GPS tho . ACL, you have done great work. Considering the few things that remain, it really is impressive!