[TESTING] - NAND OMGB (1.2.3)

[arrrghhh]

Originally Posted by trevoroni

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.

Please attempt to recreate without any apps interfering. I can't recreate it, and neither can ACL...

[trevoroni]

Originally Posted by arrrghhh

Please attempt to recreate without any apps interfering. I can't recreate it, and neither can ACL...

I'll try to find some time tonight to wipe everything and see if it still happens.

[[ACL]]

Originally Posted by trevoroni

I'll try to find some time tonight to wipe everything and see if it still happens.

all is not lost. i did find a bug but not related to your issues.

<4>[ 3154.086334] Division by zero in kernel.
<4>[ 3154.086395] [<c02804b4>] (dump_stack+0x0/0x14) from [<c002df78>] (__div0+0x18/0x20)
<4>[ 3154.086486] [<c002df60>] (__div0+0x0/0x20) from [<c0142f4c>] (Ldiv0+0x8/0x10)
<4>[ 3154.086547] [<c0056f40>] (htc_get_batt_info+0x0/0x890) from [<c0058264>] (htc_battery_thread+0x54/0xa0)
<4>[ 3154.086639] [<c0058210>] (htc_battery_thread+0x0/0xa0) from [<c0061360>] (do_exit+0x0/0x7a
<4>[ 3154.086700] r7:00000000 r6:00000000 r5:00000000 r4:00000000

This code wasnt changed since the good ol days, so this buy may have been around for a while. Ill have this fixed for next kernel

Edit: for those of you having isssue.. please try and report the following. 1) test after removing gps.rhodium.so 2) did you use the new LK? 3) does this happen afer a fresh install with no additional apps. thnx

[trevoroni]

Awesome, glad it helped out one way or another.
One other thing I've noticed is that the 'zoom bar' on the bottom of the screen is active, just not to control zoom. You can use it to scroll left-right, flip through pages, etc. it's kind of handy right above the buttons and not having to swipe on the visible part of the screen.

[arrrghhh]

Originally Posted by trevoroni

One other thing I've noticed is that the 'zoom bar' on the bottom of the screen is active, just not to control zoom. You can use it to scroll left-right, flip through pages, etc. it's kind of handy right above the buttons and not having to swipe on the visible part of the screen.

What!??! The zoombar is certainly not active. You must be touching a part of the screen without realizing it, lol.

What app to you think it works in? I can't get it to work at all, and the only kernel where it was actually put into use was a .39 kernel way back when. It was used as a fake for multitouch, and actually worked quite well as a zoombar. Hopefully in time that can make its way to NAND, but .39 has to settle down first.

[trevoroni]

Originally Posted by arrrghhh

What!??! The zoombar is certainly not active. You must be touching a part of the screen without realizing it, lol.

What app to you think it works in? I can't get it to work at all, and the only kernel where it was actually put into use was a .39 kernel way back when. It was used as a fake for multitouch, and actually worked quite well as a zoombar. Hopefully in time that can make its way to NAND, but .39 has to settle down first.

It doesn't function as a zoombar, just an extension of the screen.
And my fingers aren't that fat!
I can use it with the stylus too, it registers to the bottom of the little lines. I use it on Google Reader to swipe from one article to the next. It also works for Launcher Pro to swipe between docks.

[arrrghhh]

Originally Posted by trevoroni

It doesn't function as a zoombar, just an extension of the screen.
And my fingers aren't that fat!
I can use it with the stylus too, it registers to the bottom of the little lines. I use it on Google Reader to swipe from one article to the next. It also works for Launcher Pro to swipe between docks.

I wonder if it's your screen calibration. I can't get the zoombar to do anything, at all - which is how it should be. It certainly should not be swiping between screens.

[[ACL]]

Originally Posted by [ACL]

all is not lost. i did find a bug but not related to your issues.

<4>[ 3154.086334] Division by zero in kernel.
<4>[ 3154.086395] [<c02804b4>] (dump_stack+0x0/0x14) from [<c002df78>] (__div0+0x18/0x20)
<4>[ 3154.086486] [<c002df60>] (__div0+0x0/0x20) from [<c0142f4c>] (Ldiv0+0x8/0x10)
<4>[ 3154.086547] [<c0056f40>] (htc_get_batt_info+0x0/0x890) from [<c0058264>] (htc_battery_thread+0x54/0xa0)
<4>[ 3154.086639] [<c0058210>] (htc_battery_thread+0x0/0xa0) from [<c0061360>] (do_exit+0x0/0x7a
<4>[ 3154.086700] r7:00000000 r6:00000000 r5:00000000 r4:00000000

This code wasnt changed since the good ol days, so this buy may have been around for a while. Ill have this fixed for next kernel

Edit: for those of you having isssue.. please try and report the following. 1) test after removing gps.rhodium.so 2) did you use the new LK? 3) does this happen afer a fresh install with no additional apps. thnx

cant seem to find a division in this function.. odd

also im removing gps from the next. We will see if things return to normal then.

[icevapor]

Originally Posted by [ACL]

This code wasnt changed since the good ol days, so this buy may have been around for a while. Ill have this fixed for next kernel

Edit: for those of you having isssue.. please try and report the following. 1) test after removing gps.rhodium.so 2) did you use the new LK? 3) does this happen afer a fresh install with no additional apps. thnx

Hey, been running android as my daily off SD for a while, but thought I would test yours out. I have an Epic4g also so I'm pretty familiar w/ flashing/adb/etc..

I just flashed 1.2.3 using the LK that is in the OP (is that new "new" one?) and have had "wake" issues from the first or second time it went to sleep.

Any logs I can get you to help squash this issue?