yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
What line does it hang on...? Same one every time? This is definitely an odd issue, as we have several models of RHOD that work just fine on this kernel, including yours (assuming you're on a RHOD210, which is what F22 has).
[Touch Pro2, Tilt 2 Android Development] F22:
I do recall that his isn't a production 210. It's an engineering sample with an AUO panel, just like many of the 100's. There may be other subtle hardware differences that are causing problems.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Yes, always the same. The very last line is always the last line of the calibration report. Like you see here http://xdaforums.com/showpost.php?p=10646251&postcount=447
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Right. I've ordered yet another TP2 off eBay. Hopefully it will be more vanilla. If I get that working more easily, I will happily send this engineering sample to any developer who feels like tinkering with it.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Ah, I didn't realize that was the case. Let us know what happens with the ebay'd TP2. I'm sure there's plenty of devs that could use a RHOD :D.

I'm kinda hoping to get dzo involved, we could really use his expertise. If he's up for it, and we can get him a RHOD, he would be an incredible asset, even if he is only working in a diminished capacity.
[Touch Pro2, Tilt 2 Android Development] F22:
Please try the following then:

adb shell dmesg > dmesg.txt

adb logcat > logcat.txt

ctrl-c (terminates the logcat)

It's possible that you may get an error stating that the device isn't found because either it boot up is hanging before adb is started up on the handset, or the device is left in such a state that it can't be accessed remotely. If on the other hand you do get results, post the two files here.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
No luck, adb is apparently not started yet. Is there something we can tweak in init.rc to get it started sooner?
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Copying more of the screen (by hand):

Modules already unpacked for this kernel version -- skipping installation of /sdcard/andboot/modules-2.6.27.46-1253-gd53ddf6.tar.gz
insmod: can't read '/lib/modules/lzo_compress.ko': No such file or directory
insmod: can't read '/lib/modules/lzo_decompress.ko': No such file or directory
[ 28.432312] ramzswap: disk size set to 102400 kB
insmod /lib/modules/ramzswap.ko disksize_kb=102400
swapon: /dev/block/ramzswap0: No such device or address
/bin/userinit.sh: line 496: fail: not found
[ 28.639068] Something used micropklt_lcd_ctrl. This function should no longer be used.
[ 28.657073] Something used micropklt_lcd_ctrl. This function should no longer be used.
USING EXPERIMENTAL RHOD210 LAYOUT
Using Saved Touchscreen Calibration
[ 29.032562] touch_calibration: Point 1 824, 893.
[ 29.050109] touch_calibration: Point 2 176, 897.
[ 29.057464] touch_calibration: Point 3 480, 543.
[ 29.074768] touch_calibration: Point 4 827, 172.
[ 29.082092] touch_calibration: Point 5 200, 174.
[ 29.095611] touch_calibration: do calibration ok.
[ 29.108886] touch_calibration: x max 130, x min 876.
[ 29.116394] touch_calibration: y max 121, y min 950.
[ 29.123382] touch_calibration: x same direction, y same direction.

It always ends there.
[Touch Pro2, Tilt 2 Android Development] F22:
It looks like it's dying in init, not in init.rc. That's not surprising as touch screen calibration is handled near the bottom of init, before control gets passed to init.rc. Since it appears to be the touch screen calibration that is hanging your handset you can comment that out. If that's the only issue, then it should come up with adb working once that's disabled.

Since you're running linux on your desktop, you can mount the rootfs.img in the android boot directory of your sd card via loopback, pull the init script into your favorite editor and comment out the following:

If you need more detailed instructions just let me know.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
I did some other tweaks before I saw your reply. First I just tried adding "/sbin/adbd &" before it did the calibration, but my laptop never saw the adb device wake up. Not sure what's going on there.

Then I stuck in a "dmesg > /data/dmesg.1" before the calibration and another "dmesg > /data/dmesg.2" after the calibration. Both of these succeeded. I've attached the latter one here.

So, it's something after that, I'll sprinkle in some echo statements and try and narrow it down further.

I added echo statements in front of all the following statements, the last thing was "exec'ing init.android". So there's actually no problem anywhere inside this init script, it's something later. ugh.
[Touch Pro2, Tilt 2 Android Development] afrizal_chen:
I have been using FRX03 since BLAZN wasn't get updated.

I notice that I will get BSOD (Dark Frozen Screen that I have to push the magic reset button) everytime I lost both 3G and GPRS reception. This mostly happen when i get into an elevator or subway train with no reception. But, It is FINE if it lost 3G and it found GPRS.

Anybody notice the same issue?

My RHOD100 is currently using Kernell-1253.
[Touch Pro2, Tilt 2 Android Development] F22:
So it probably is something in init.rc that gets done before adb is started. That contains instructions for init.android.

There should be a "exec'ing init.android" echo statement at the end of the init script. It would have made it obvious that the cause wasn't in init and saved us some time.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Nice job, getting that dmesg! Sometimes you have to get a little creative ;)

I found some odd references to what seems to be issues accessing the SD - have you tried a different card? Kinda a long shot, and your phone is seemingly very unique...

Also, do any kernels after 1232 work, or is 1232 the last functional kernel for you? Thanks.

Here's the errors I'm talking about, if you're curious:

[ 19.232604] mmc1: Data timeout
[ 19.240905] mmc1: DMA channel flushed (0x80000004)
[ 19.249023] Flush data: 0000c003 25280000 00000000 00400040 00670065 00008003
[ 19.265106] mmcblk0: error -110 transferring data
[ 19.482788] mmc1: Data timeout
[ 19.491149] end_request: I/O error, dev mmcblk0, sector 5966096
[ 19.507263] end_request: I/O error, dev mmcblk0, sector 5966104
[Touch Pro2, Tilt 2 Android Development] highlandsun:
I've noticed those errors on some boots. Not on every boot, and they also occur on some 1232 boots too. 1232 still boots up completely regardless. I don't have another card handy at the moment but will give it a shot later.

I've tried every kernel in the first post of this thread, 1232 is the only one that works.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
I found a 1GB card I had lying around unused and did a fresh install. Those mmc errors are no longer present in the dmesg.

It appears that init.android is simply refusing to run. I've added "write /dev/console initX" messages throughout the init.froy.rc file and get nothing. With the 1232 kernel I get an "A N D R O I D" banner and all of my initX messages.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
I downloaded the XDandroid source tree and recompiled the init program with some more debug. Found that it was hanging here:

@@ -883,8 +886,10 @@ int main(int argc, char **argv)

have_console = 1;

close(fd);

- if( load_565rle_image(INIT_IMAGE_FILE) ) {

- fd = open("/dev/tty0", O_WRONLY);

+ INFO("init image file\n");

+ if( 1 /* load_565rle_image(INIT_IMAGE_FILE) */ ) {

+ /* fd = open("/dev/tty0", O_WRONLY); */

+ fd = open(console_name, O_WRONLY);

if (fd >= 0) {

const char *msg;

msg = "\n"

So I bypassed load_565rle_image(). It seems that it still hung trying to open /dev/tty0; I would only expect this to happen on an RS232 port that was waiting for DCD or DTR to go high. Not sure what's up with that, using the console instead got it past that. Then init seems to run to completion, but a few seconds later there's a kernel panic and I haven't managed to catch everything in dmesg from there yet.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Here's briefly what I see from the kernel panic:

Backtrace:

micropklt_speaker_led+0x0/0x70

msm_setup_audio+0x0/0x198

snd_set_device+0x0/0x114

snd_ioctl+0x0/0x56c

vfs_ioctl

do_vfs_ioctl

sys_ioctl

after I commented out "panic_on_oops" in init.froyo.rc I was able to use adb shell to get the dmesg for this...
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Odd.

Can you get a logcat too? It almost looks like something I saw when JIT is enabled... Not sure why that would choke your phone like this, just curious. Thanks!
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Here's the logcat...

Oh, and another dmesg - there's apparently more going wrong after the msm_audio oops. Both of these are from the same boot attempt.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Almost looks like issues with the .35 framebuffer...

Which was committed in 1233. So that seems to be the issue. Now what I don't know is the 'why' or the 'how to fix' :p.

I'll see if ACL has any ideas, as the .35 fb was his baby.

Logcat wasn't really useful, which does make sense... that's really for debugging userland issues. So we'll see what I can churn up.
[Touch Pro2, Tilt 2 Android Development] [ACL]:
Hey fellas. F22 notified me of this issue and i'll look into it when i get a chance.

The errors seem to crap out when making microp related calls. Bot autobl and speaker led setup use microp so this is hat they have in common.

[ 29.444763] PC is at micropklt_speaker_led+0x2c/0x70

and

[ 44.520935] [<c01b06f0>] (micropklt_panel_resume+0x0/0x150) from [<c004b9e0>] (htcrhod_mddi_panel_unblank+0x1c/0x24)

I'll post a test kernel when i get a chance.

Edit: Also i need to know who compiled this kernel.? if this was F22 or someone else.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Sweet! Saves me a step of trying to get a hold of you :p

Oh, and I'll let F22 confirm for sure, but he did compile all the kernels in the first post. I guess we should also get confirmation from highlandsun that he is using the kernels compiled by F22...? I'd assume so... but we all know what happens when we assume!
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Yes, I'm just using the kernels that were posted in the first post of this thread. I now have a XDA build environment all compiled, but the only thing I've used from it is my hacked up init.
[Touch Pro2, Tilt 2 Android Development] F22:
Kernel Source

Kernels downloaded from the links attached to the first post of this thread were compiled by yours truly. On the other hand Kernels downloaded from Pixelwattstudio, a site that has been mentioned in this thread and others on numerous occasions, were compiled by ice.bogdan. If anyone isn't certain regarding the source of their kernel, going into Settings and clicking About Phone and then scrolling down to Kernel version will tell you. If the second line says upcm@anaxagoras then the kernel you're using is one of mine.
[Touch Pro2, Tilt 2 Android Development] AkumaX:
hi5 everyone!
[Touch Pro2, Tilt 2 Android Development] neo_zycho:
do you have any fix on the wifi, when reactivating it, it returns error. the voicemail call is not working. hope someboday had a work around on this one.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
So it works initially, but when you go to reactivate wifi, it fails...?

Voicemail call is only for the system_server bug - when your phone is unbearably slow basically.
[Touch Pro2, Tilt 2 Android Development] DmK75:
Its there any differences with 1253 kernels compiled at 13.01 and 21.01 ?

Thanks.
[Touch Pro2, Tilt 2 Android Development] imranjamadar:
please fix the wifi error once for all

Yes the wifi error happens when we de activate the wifi and then reactivate plus after you wake the phone from a deep sleep.:mad::eek::confused:

Using Android system information from the logs i read that the system is unable to

find the wifi driver twlan0 after we deactivate and activate wifi.

i will try to get that log, and my device is topaz diamond2.

F22 or ACL or anyone else if interested i am ready to provide the logs.

Thanks.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Go right ahead and post them. I guess I don't really mess with wifi much, and neither does F22... not surprised we haven't caught this.

What I'd like to know tho - is this a new bug or has it existed in XDAndroid for a while...?
[Touch Pro2, Tilt 2 Android Development] imranjamadar:
Will post the log soon

I have the logs and will post them as soon as i return from a nephews birthday party , he wont cut the cake till i am there :p

cheers
[Touch Pro2, Tilt 2 Android Development] F22:
There's also the issue that ACL & I both have rhodiums which use the bcm driver instead. So even if we wanted to test it out, we can't. Logs are thus always helpful of course. Emwe told me that it's a known issue, but that it hasn't made it to the top of his priority list. There's been a note regarding issues with non-rhodium wifi in the first post of this thread for awhile now.

The ti wlan driver, unlike the bcm driver, is not a part of the linux-msm 2.6.27 kernel tree. It's built from a separate package and integrated into the modules file. I'm using that particular driver package simply because it's the same one that Glemsom was using. Initially I thought the problems were all due to something I was doing, but I've since learned that there were plenty of complaints regarding the ti wlan driver back when he was building the kernels too.

I did find a live git for the ti driver awhile back that might possibly be better than the package we've been using. It may be worth looking into for the future.
[Touch Pro2, Tilt 2 Android Development] [ACL]:
If you have your own kernel build env then i would go ahead and build a kernel yourself. I would comment out the micropklt_speaker_led and see if that helps.
[Touch Pro2, Tilt 2 Android Development] geminix2:
I had already downloaded the 13.01 compile so I downloaded the 21.01 version and did a WinHex compare. Assuming I didn't make a mistake, WinHex said the zImages were identical but not the modules package.

Whether the difference is significant or just an artifact of recompiling I don't know.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
OK, will try that soon, thanks for the suggestion.
[Touch Pro2, Tilt 2 Android Development] imranjamadar:
Here are the log files as asked

Here are the log files as requested ---

Dmesg ---> http://pastebin.com/Rvtqs1EM

Logcat ---> http://pastebin.com/b4PdxFqr

I have also attached Logcat dump and bug report dump for yourself .*

let the hunt begin.
[Touch Pro2, Tilt 2 Android Development] imranjamadar:
ti wlan git reprositrories

Are these the reps

http://gitorious.org/rowboat/system-wlan-ti/commits/rowboat-froyo

http://gitorious.org/search?q=++ti+wlan+

or

this http://gitorious.org/0xdroid/system_wlan_ti
[Touch Pro2, Tilt 2 Android Development] Raul^:
Kernel 1253, from this topic.

Sprint Rhod400. When I call someone and then cancel the call phone "hangs" for about a minute. Sometimes when I call it from other phone it don't react, and I hear my voicemail. I didn't call that many times from the phone and haven't checked if after a call I puch End button it will reboot but I will try.

I haven't seen that problem with other kernels.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
My 2nd TP2 arrived today, it doesn't have any problem booting up 1253. If any devs want my engineering sample, PM me and I'll send it to you.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Since it is such a difficult phone to use, stinebd might be the best candidate.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Cool, will get it sent out Monday.

On the topic of calibration - when I boot up into the SPL (power + volume down) I see the Touchpad calibration values from the factory. Should I be able to plug these values into a ts-calibration file and just use them?

On the new phone I see:

RHOD210 32M SS-BC
SPL-0.87.0000
MicroP(LED) 0x0A
MicroP(KEY) 0x04
TURBO HW/TURBO SW
TP MFG DATA
500,524 781,866
799,187 220,200
212,869 Calibrated

On the engineering sample I see

Security Unlocked

RHOD210 32M SS-BC
SPL-0.87.0000
MicroP(LED) 0x06
MicroP(KEY) 0x04
TURBO HW/TURBO SW
TP MFG DATA
513,527 807,858
807,193 219,188
226,855 Calibrated

(Yes. I plugged in the values in what appears to be the correct order, works fine. Notice that the order listed in the SPL doesn't match the order in the ts-calibration file.)
[Touch Pro2, Tilt 2 Android Development] F22:
TI WLAN driver repo

No, but the first looks like a clone of the original, and the third appears to be a derivative of it. Here's the link to the repo I found:

http://android.git.kernel.org/?p=platform/system/wlan/ti.git;a=summary

I've compiled it successfully in the past, although I did revert one of the commits which I heard causes problems. I never did get around to testing it out though. I've stayed with the same sta_dk_4_0_4_32 package that Glemsom used instead. I can look into recompiling it against the latest kernel and rolling it into a new modules file for testing later this weekend. I have two other tasks in my dev queue before I can get to it however. If you prefer, you can try it out yourself and let me know how it goes. If you do, you may want to consider reverting commit 849c6d4186a7fcd4d25bcff6cc2e6bc25f8c4696 however.
[Touch Pro2, Tilt 2 Android Development] F22:
1253: different builds

Where did you find these two different versions of 1253? Is the 13.01 compilation mine?
[Touch Pro2, Tilt 2 Android Development] F22:
That's an interesting observation. What ordering did you use that works? Btw, the MicroP(LED) value of 0x0A on your new handset matches mine. It's interesting that your engineering sample is different.
[Touch Pro2, Tilt 2 Android Development] imranjamadar:
The last commit was on 2010-03-23 by Dmitry Shmidt. So is this project dead?

Did you compare it against the clonned rep?
[Touch Pro2, Tilt 2 Android Development] F22:
It doesn't look like any additional work has been done on the clone since it was made. Its last commit was also 2010-03-23 by Dmitry Shmidt. The other tree appears slightly more active, but it doesn't look like they've done anything of substance within the recent past either.
[Touch Pro2, Tilt 2 Android Development] geminix2:
Well, I thought I got them both from here http://pixelwattstudio.com/android/kernel/ but maybe I got the 13.01 version from the mediafire link in your post. I'm going by memory but I 'think' I went to the archive, or maybe I just checked it.

There is no distinguishing identification (meaning same file name) other than date and noticing there is a WinHex difference. According to Windows properties they both have the same number of files and total length but the newer one has 4 bytes less packed length (825298 vs 825302).

I have both because on my PC I have dated "as of" subfolders containing what I installed on the date, so I can revert to a known configuration if problems, as in "As of 01-13-11" and "As of 01-21-11."

Btw, can the new FR04 OTA update be applied to Rhodium?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yes, FRX04 OTA can be applied to any device running a clean FRX03 image.
[Touch Pro2, Tilt 2 Android Development] vnes1984:
FRX04 running very well for me so far. Does sleep mode 0 work or should I stick with 1?
[Touch Pro2, Tilt 2 Android Development] imranjamadar:
System still shows FX03

System still shows FX03, do i have to delete data.xxx file to reflect the change?
[Touch Pro2, Tilt 2 Android Development] rpierce99:
In "About phone" my Build number says FRX04 and I did not delete data.img, sounds like something in your update didn't take.
[Touch Pro2, Tilt 2 Android Development] imranjamadar:
SO what now??

So F22 what should we do now? :confused:​

dimitrysh@google.com

his email ID, i will get in touch with him and ask him. and may be point him to us and lets see if we can get him overboard>> is that ok?
[Touch Pro2, Tilt 2 Android Development] imranjamadar:
Have a look at this link

F22 have a look at this git link,

https://www.codeaurora.org/git/proj...sitory/revisions/master/show/android/hardware

Plus this link also ---> titled Kernel will not load wifi driver

http://groups.google.com/group/andr...5351ed4e522/8dd040b24352fea2#8dd040b24352fea2
[Touch Pro2, Tilt 2 Android Development] imranjamadar:
hmmm..

anyways i deleted, data.img and now it shows fx04, i read somewhere about it that you should when a new system image is released.

can some one confirm on this one :)
[Touch Pro2, Tilt 2 Android Development] highlandsun:
For example, my ts-calibration file now has:

781,866,212,869,500,524,799,187,220,200

Relative to the pairs in the SPL display, that would be

#2, #5, #1, #3, #4

(Counting left to right, top to bottom)
[Touch Pro2, Tilt 2 Android Development] geminix2:
Thanks.

I'm new at this so I don't know what to expect but I copied the update in and installed the latest rootfs as per instructions. I saw the 'applying update', so far so good, but then, during the next boot, Android restarted itself 3 or 4 times, along with what now seems to be the obligatory 'process system not responding' messages (I 'wait').

However, I hung in there and it seems to be working.

I'm just wondering if that behavior is expected or indicative of a problem.

To bad you guys can't hop over to Skype and fix their useless app. They never could make it work right on WM (sound) and they've continued the tradition on Android (can't log in).
[Touch Pro2, Tilt 2 Android Development] F22:
Sounds like Bogdan did a recompile of his modules file. You could open up the tar archives and see which modules have changed. You could also just ask him.

Yep, in fact it contains ACL's improved graphics libraries for wvga devices like the rhodium.
[Touch Pro2, Tilt 2 Android Development] F22:
calibration values

Hmm....my ts-calibration is:

838,881,192,881 512,520 845,166 182,163

if I were to use the values from the spl, it would be:

819,849,204,851,512,519,822,189,210,187

Not exactly the same, but it looks like they would work. I'm not certain which set of values is more accurate at this point, nevertheless it presents the intriguing possibility of automating the entire calibration process by just grabbing the factory-set values from the spl.
[Touch Pro2, Tilt 2 Android Development] geminix2:
I'm not that curious but if someone 'needs to know' I'll do it.

It seems much better behaved on my tilt2 and, so far, I've not had to 'dial out' to settle system down but I didn't have a lot of experience to go by as I just got back in the game a week ago.

I find it odd (same as before) that orientation doesn't seem to work till sliding the keyboard in and out. Not a biggie, just a notation.

Angry birds works now but Skype is still broke.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Yes, my thoughts exactly. The difference between the values you quoted seems small enough that it would be close enough either way. On my phone, I actually noticed a couple areas of the on-screen keyboard that were easier to hit after I put in the SPL values. (A couple of the keys at the left edge of the screen.)
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
I was able to update to FRX04 without deleting my data.img file. Thank God, cause I really didn't want to have to download all the apps and set up all my preferences again. FRX04 seems to run smoother than FRX03 in my opinon.
[Touch Pro2, Tilt 2 Android Development] [ACL]:
Let me know how it worked out.
[Touch Pro2, Tilt 2 Android Development] jordanthompson:
I have found that pressing the red button on the bottom right does the same as sliding the keyboard.
[Touch Pro2, Tilt 2 Android Development] bonald:
screen split

My screen is like splitting with these new builds. (TouchDiamond500)

Hard to describe. Part of the left screen is now on the right ...

I does not always do that, most of the time it does that when scrolling and there's now way to get it back centered.

Any idea what's going on ?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Known bug, I believe it starts after 1242.