yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] F22:
My production 210 as expected says:

My engineering sample 210 that is marked as having an AUO panel unexpectedly says:

Perhaps, just like with the EID panels which may be either 14 or 15, there may also be two different AUO panels too, 7 or 13. Or I suppose it just might be that this particular handset is a real oddball given that it is an engineering sample.
[Touch Pro2, Tilt 2 Android Development] husam666:
sry to go off-topic but i found a glitch with sound during a call,

if you have the phone keypad sound enabled and press a number, the sound will be redirected to the rear speaker.

tried it on every rom here and so i guess it's a kernel issue (correct me if I'm wrong)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Based on what you're saying that's expected behavior - if you press numbers on the dialpad, it plays thru the rear speaker and not the front earpiece.... That way you can hear it.
[Touch Pro2, Tilt 2 Android Development] husam666:
But shouldn't the sound be directed back to the earpiece?

TP2, xda app, what more would you like to know?

Stop tapping my phone for god's sake :mad:, I didn't do anything!!
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
I had another reboot to WinMo, this time when I tried calling someone. It froze on the screen whrer you cabn select whcih number of a contact to call (home, mobile etc). Due to the Gen.Y it started to boot android, couple of minutes later I pushed power to show the screen and it was frozen (with orange light). Both logs are below.

I haven't had time to look for another SD, but if this is againthat issue,could you tell me what to look for in the log, so I can post only the ones without it.
[Touch Pro2, Tilt 2 Android Development] rcgators:
Noticed the same behavior. If you press a key the speaker is now active but softer than normal. If you toggle the speaker phone on it gets louder and when you toggle off the speaker phone, the rear speaker is still active, just softer. Could not find a way to return the call to the normal earpiece.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I'll take a look at these and let you know what I find.

Edit - just looked at the logs... they're all garbled to me. Can you see if they look OK to you and if so pastebin them...? Thanks. Still not sure what causes the logs to get messed up like this, it's very annoying!

Again, isn't this expected behavior...? Am I just missing something here? I don't see a problem, or how it applies to this testing kernel...
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
Hmmz, was a little hasty and renamed the .gz to txt instead of extracting the txt. :rolleyes: Here they are again.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Odd. The reboot.txt still has quite a bit of jibberish in it, but it's much more readable than before ;).

The freeze.txt looks fine tho, looks like the phone reset at the end of it...

[42918.368133] htcraphael_reset: Soft reset done.
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
in case you need it, its on pastebin as well:

http://pastebin.com/mDkhXcir

Is that also shown when resetting with the reset button you access behind the cover?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I don't think so...

Besides, there was a kernel panic right before it - those usually cause resets to WinMo.
[Touch Pro2, Tilt 2 Android Development] husam666:
This happened to me on every kernel out there :o

TP2, xda app, what more would you like to know?

Stop tapping my phone for god's sake :mad:, I didn't do anything!!
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Hence the reason I keep saying it's expected behavior. Unless I'm missing something, the behavior you have described is expected and is not going to be changed.
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
For some reason when I call someone, the phone window hangs on the first screen. It doesn't dial, I can switch to it, but not kill it.... I think I'm switxhing back to the reference build, or are there any specific issues your going for in this thread? I'm getting the feeling this thread is quieting down? I can imagine with the gingerbread being launched, Wistilt has got enough to do?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
WisTilt2 has absolutely nothing to do with gingerbread, as he's a kernel dev.

In addition, this kernel is "build agnostic" in that you can use it in Gingerbread.

Aren't you doing this testing on FRX04...? What's the last kernel that works for you correctly, do you use the newest (1253)?
[Touch Pro2, Tilt 2 Android Development] husam666:
Lol, I just liked to let you know :)

Btw I'm running on 30/1 kernel, I think, and I don't have SODs whatsoever, I'm downloading this version now,

Thx

TP2, xda app, what more would you like to know?

Stop tapping my phone for god's sake :mad:, I didn't do anything!!
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
Ah right I saw his name in connection to gingerbread somewhere I thought

Anyway, I'm currently using the zimage and modules from the 1st post, the auto-panel-select. But I was thinking a bout going back to the stock frx04, haven't really looked for anything other than that (except for this one).

Is there anything in this kernel you're still looking for? Sysserv is absolutely gone, not sure if panel collapse for auo is fixed, so the question is really if you still need auo panels in this thread.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Well... seems WisTilt2's code has been committed... New autobuild kernel, 1258! Woot!

I was going to ask you to triage, but in light of his code being committed... Yea. Let's just hope we can iron out any remaining wrinkles.
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
Wicked, gonna try this! Should I report any issues here, or somewhere else? In anycase, I'll keep an eye on this thread, thx!
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Unless you're running a test kernel, I'd prefer you keep the discussion in the New Kernel thread.

There will probably be more testing kernels, but for now nothing new ;).
[Touch Pro2, Tilt 2 Android Development] rcgators:
Maybe this will help.

I go to voice mail, listen to a message using earpiece, delete the message by pressing 7, I hear the key tone from the back speaker, now the next message is being broadcast out the

back

speaker. :eek: Hope this makes sense. Not sure if this is part of the kernel... just trying to clarify what the orignial user was reporting...
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Oo that makes more sense (at least the explanation does). I'll test it myself, not sure I've ran into this before... I never check voicemail on my phone anymore, so I'm not in this situation often :p.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Forgot to test what I said I was going to test with voicemail... Sorry 'bout that!

At any rate, I've posted a new kernel - this is for everyone (with a RHOD), especially RHOD100/AUO users who had issues with the last kernels, or with the newest GIT kernel 1258. My phone has been waking basically instantaneously, which is incredible. Let me know how it goes guys!
[Touch Pro2, Tilt 2 Android Development] Eodun:
Everyone - everyone?

Edit: I imagine only Rhod's ;)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yes, RHOD only. Sorry... I guess I'll adjust that post. This is in the RHOD section to be fair, and I was pretty clear in the first post :p.

I guess there's nothing to stop you from trying it, honestly you shouldn't notice any improvement or degradation. But if you do notice anything degraded, I guess I would ask is it degraded on the 1258 GIT kernel? If so, then we need to address that. Thanks!
[Touch Pro2, Tilt 2 Android Development] Eodun:
Yeah, sorry for the interference, I follow TP, TP2& blac android forums and sometimes I don't know where I am...
[Touch Pro2, Tilt 2 Android Development] Jandyman:
I had problems with the last test kernal, but when I switched to1258 today oddly enuf its running lovely so far :D any improvements for non rhod100 user in the latest test? Or should I stick to 1258 for now?
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
A quick report: I've been pressing the powerbutton a lot the past 15 minutes, at first wakeup would be normal when sleeping, but I had to touch and slide when not sleeping to wakeup. Then a SoD, and now I always need touch and slide to wakeup :(

EDIT: taking it all back, haven't seen it this responsive before, without having to slide or whatever!
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
On my RHOD400 I had intermittent issues with the panel waking completely - it was rare, but would happen. Also, sometimes it seemed like it would take extra time to wake. With this newest test kernel, it's been instant every time.

Uhm... I guess I'm confused. Your first report sounded horrible, and now it's flawless? lol, I guess I'll go with flawless for now unless I hear something else.

So who else? Everyone with a RHOD is welcome to test, the more feedback the better! Just please, let's focus on panel wake with this test kernel...
[Touch Pro2, Tilt 2 Android Development] djcrosstunez:
It is just the same as the official kernel, the screen just comes up after 5 sec
[Touch Pro2, Tilt 2 Android Development] electriczbif:
Rhod100_uk, WisTilt2 test kernel 02/16:

Certainly an improvement, but I still have 10-15% wakeups that take more than 15 seconds. Usually when waking-up the screen immediately after shut-down, i.e. after 2-3 seconds, before the power led turns green or immediately after. In every case, touching the screen in the place of unlock button wakes up the screen instantly. Waking up on incoming call works ok, but the screen brightness isn't restored to the preset value but to a much lower one (with autobl disabled).
[Touch Pro2, Tilt 2 Android Development] Jandyman:
Switched to latest test kernal 2/16

Here's my Report:

*Seems better than 1528 untill now anyway in the time between screen off and deepsleep. In 1528 (and previous tests) it could take up to and over 30seconds to go from redLED to greenLED, with this test kernal its 2-5 90%of the time. EDIT:ironically this super quick sleep transition suddenly stopped . . . . . .XD

*(about)1/4 wakeups the panel doesn't wake correctly ie)haptic feedback/no backlight (not sod!), but usually after a couple presses of the power button the led reverts back to green and the nxt wake is usually succesfull.
[Touch Pro2, Tilt 2 Android Development] husam666:
Sleeps faster to me, but wakeups are just like the person above me.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
...anything that's not committed to GIT (ie has any changes from the main tree, local changes that are not committed...) create so-called "dirty" modules.

Plus, I already said wifi is fixed. It is indeed fixed folks, first post has been updated!!!
[Touch Pro2, Tilt 2 Android Development] F22:
wifi drivers

These are all for non-rhodium wi-fi. Rhodium uses the Broadcom 4329 driver which is backwards compatible with its bcm4325 chip. It's the other handsets supported by xdandroid (top, raph, diam, black, kov) that have the Texas Instruments chip instead and use these.
[Touch Pro2, Tilt 2 Android Development] F22:
I can report that kbd backlights now work fine on the 210 (as long as they're on at boot as per the testing instructions). :)
[Touch Pro2, Tilt 2 Android Development] dcmedic:
I keep locking up in boot.

Unable to mount sd card......
[Touch Pro2, Tilt 2 Android Development] MassStash:
what phone??????????????????????????????????
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Sounds like you need to format your card.

What phone/build would be good info...
[Touch Pro2, Tilt 2 Android Development] F22:
kbd backlight initialization

Test Kernels keep getting better and better tonight...Kbd backlight no longer requires being turned on before starting haret to work with the latest zImage! Great progress!
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I know it. Fast fixes for sure, first post updated with new goodness!
[Touch Pro2, Tilt 2 Android Development] pdawg17:
The work being done tonight is amazing!

With the Jan1 test kernel I have had 2 random reboots to WM...this last one was while it was sleeping plugged into the charger...I have it o/c'd to 710 with sleep=1...I may need to try a new SD card though as I've had some weird stuff when using Android lately...

Also: Keyboard backlight works great, wifi working again
[Touch Pro2, Tilt 2 Android Development] MassStash:
710000-528000=182000 => pushing a system past the standard yada yada. Has this been proven to have absolutely nothing to do with system instability, mainly reboots??? is 182mhz over the reg not a biggie?
[Touch Pro2, Tilt 2 Android Development] pdawg17:
I should have mentioned the first reboot was at 528...
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Good to hear on wifi. Might want to try disabling the OC. Certain apps can cause resets too, there's a ton of factors.
[Touch Pro2, Tilt 2 Android Development] neohemp:
I'm having the same unable to mount SD problem with the newer kernels, but the original kernel worked/works fine. I've formatted the SD card with no luck. Have a Tilt 2

Any ideas?
[Touch Pro2, Tilt 2 Android Development] MassStash:
which order are your partitions? list in order of creation?
[Touch Pro2, Tilt 2 Android Development] neohemp:
If I knew how to answer this I would be more than happy to :) At this point you can either hold my noob hand and tell me how, or just ignore this and we can both move on.

:D
[Touch Pro2, Tilt 2 Android Development] MassStash:
did you just partition your sdcard all one thing fat32?
[Touch Pro2, Tilt 2 Android Development] neohemp:
Yep I sure did; I found these commands in another thread which made it work;

msmsdcc_1bit msmsdcc_fmax=14000000

Any idea what this does? And more importantly why the first kernel works fine without them but the new (1238+) I get the mount error?
[Touch Pro2, Tilt 2 Android Development] Naadi900:
Rhod100 test

So I thought I give it a try with my Rhod100_uk.

I booted with Keyboardbacklight on, just to be sure. Keyboard backlight dimmed a bit, the turned off. It actually booted fine just now, 3g works as well. Wifi was broken for me in the 1245 kernel and a few before. But with this kernel it works again =D Not sure what the problem for the Rhod100s would be, but i dont experience them yet. Autobacklight works, after switching on and off for a few times.

When the phone wakes from sleep the panel kicks in reasonably quick.

Overall no problems i would say.

If i can help with any files posted or adb, let me know :)
[Touch Pro2, Tilt 2 Android Development] jeffgarret:
Great thanks for the quick work on WiFi I love the keyboard light. You guys keep up the awesome work!
[Touch Pro2, Tilt 2 Android Development] Bieka:
Hey there,

i just wanted to add that i gave this kernel a try on my rhod100_de. I started with keyboard bl on and suprise it works great!!! The Kernel also works as smooth as never before. In 3 of 4 starts i had 100%cpu usage and now it runs very cool on 20% ;). I will try this kernel the next days and report back.

Only Thing is, when i type something the Light dims for the time pressing the Key. But only sometimes!
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Thanks for the reports guys.

I noticed much faster sleeps at first as well... then they started taking longer. Odd indeed.

I also have noticed that while at first the panel seemed to wake much faster, it's almost back to the same behavior of taking a few seconds to wake... Hrm. I don't know why that would be, but I'll pass on all this info to WisTilt2.

Keep the feedback comin, thanks a bunch for testing guys!
[Touch Pro2, Tilt 2 Android Development] großa:
Phone is booting fine. Seems to be faster.

Couldn't wake up the phone. Led switched from green to orange and back. Tried every key. Same problem.

Called my phone, panel black, went back to sleep. After pressing the power button, the panel was a little bit brighter. Touched it and the panel woke up.

Put the phone back to sleep, same procedure starting again.

Don't have a problem with the 1253 kernel. No SOD or wake up problems.

Sent from my MSM using the XDA mobile application powered by Tapatalk
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Odd. You're on FRX04 and this new test kernel yes? You can verify by going to Settings -> About Phone. What does "Kernel version" and "Build number" say? Thanks.

tomdeaap has a RHOD100/AUO panel as well, and he reported that this kernel is much better...

What is your sleep_mode?
[Touch Pro2, Tilt 2 Android Development] großa:
No I'm on GBX0A.

The LED is switching from green to orange for about ~6 seconds after pressing the power button. If I'm playing around with the vol up/dwn buttons or if I'm touching the panel, the LED stays orange.

I can even use DroidExplorer and copy files from and to the phone...

After a call, if i use the vol up/dwn buttons, I'm able to lower or raise the volume (notification sound / vibrating). It seems that the phone is awake but the panel is still black, no matter what I do...

But this is only working a few times. Than I've to call my phone again.

sleep_mode=1 (using the startup.txt from your first post, added only rel_path)

Kernel Version:

2.6.27.46-01258-gf9e4956-dirty root@wireless251 #5

Build:

full_msm-userdebug 2.3.1 GINGERBREAD eng. bryan.20110204.211942 test-keys

Added the latest 3 kmsg.

EDIT:

Just tried to call my other phone. Panel is black after ending a call?!

Turned my phone off with the end button. Yes the phone is definitly awake.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Ah... Well, to rule out any potential issue with that build can you try back on FRX04 and see if it still persists on it? I love the Gingerbread build stine made available, but there's a lot of oddities with it, and I prefer to not test kernels on it... Thanks for understanding!
[Touch Pro2, Tilt 2 Android Development] großa:
No problem :D
[Touch Pro2, Tilt 2 Android Development] rcgators:
Had an SOD today and also seeing the wakup issue where I have to tap the screen. FRX04 with testing kernel 01258-gf9e4956-dirty and recent rootfs.

Captured the last kmesg... attached. Otherwise working well. Had to set pm.sleep_mode=1 to allow incoming calls, otherwise dialer would hang if call came in while in deep sleep.

(XDA Admins really need to add .gz and .tgz to the valid attachment types... we are using linux on these phones.;))
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Never really understood the strict limits, but I'm sure it helps with their bandwidth!

I'll ping WisTilt2 with this info... you have the same phone as he does, so that's interesting.

Sorry forgot to ask - did you get this SoD while charging or shortly after taking it off of the charger? Thanks.
[Touch Pro2, Tilt 2 Android Development] rcgators:
Got the condition driving home, not on charger. I did drive through a weak coverage area. In the past, I've noticed more SOD problems where network coverage is weaker. Rarely have an SOD at the office where I have full bars, more often at home where coverage is weak. May not be related...
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
So after a day of testing: waking problems are almost over, after a weird first 15 minutes (I'll wait a bit longer to post next time :D) where it was almost worse than before, it wakes quite well, I'd say 8 out of 10 correctly. Some other issues have arised

- when it boots, I wait until it goes to sleep (quickly) and wake it, it will always say that the system process is unresponsive and asks if I want to close or wait. If I press wait, and wait a few seconds, there is nothing wrong that I can see.

- I had 3 or 4 sods since having installed this newest kernel (all when NOT charging :S) , while with the previous test kernel and the 1258 it was avg 1/day. Added to logs.

Btw, is this related to my perhaps faulty SD?:

[ 325.757324] sm_i2c msm_i2c.0: Error during data xfer (-5)
[ 325.775848] micropklt, i2c write retry

UPDATE: decided to reboot just to see if the good behaviour would continue after a reboot, and it doesn't: I often need to touch where the unlock slider would be, or even slide it. Also sometimes the phone wakes up after sliding, but still a black screen. The 3rd situation is that when I press the power button, the light switches to orange, but the screen stays black. When I press power again, the screen lights up just a quarter of a second, goes to black and back to sleep.

Had another freeze, log included (#3)
[Touch Pro2, Tilt 2 Android Development] shatred:
im not sure what this newest kernel of you should fix but i installed it on my rhod-100 and its working just fine, don't see much difference with the 14-2 1258 kernel tough. locking goes fast, unlocking takes 4-5 secs and sometimes i have to press the button on phone 2 or 3 times to bring the unlock screen up.
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
Arrgghhh, could you confirm that logs like these are due to failing SD?

lost page write due to I/O error on mmcblk0p1
[ 275.196472] Buffer I/O error on device mmcblk0p1, logical block 7416195
[ 275.196533] lost page write due to I/O error on mmcblk0p1
[ 278.794555] EXT2-fs error (device loop0): read_inode_bitmap: Cannot read inode bitmap - block_group = 19, inode_bitmap = 155650

If so, I won't bother you anymore with my logs, and wait for my new SD (will opefully arrive tomorrow)
[Touch Pro2, Tilt 2 Android Development] Eodun:
Have you tried formatting it with HP usb format tool?
[Touch Pro2, Tilt 2 Android Development] Christiaan91:
Don't forget to format in FAT32.
[Touch Pro2, Tilt 2 Android Development] snalbansed:
AUO rhod100 20110216 test kernel

I've been running this kernel for a few hours now on my AUO panel rhod100 with FRX04 and F22's rootfs.

I have had the device freeze on me three times now:

1st freeze: On charge, orange light, panel off

2nd freeze: After rebooting, a few seconds (15s?) after unlocking the screen, orange light, panel on (application draw open on screen).

3rd freeze: After rebooting, working for longer this time, orange light, panel on (trying to add log files to a zip!)

All three SYSTEM_LAST_KMSG files attached.

I also have the issue with needing to press the screen to get the panel to wake up properly, but this is small fry compared to the main issues for my device!

Back to 1226 for me :-(
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Frustrating.

So 1226, that's the last kernel that works for you? 1230 starts freezing and acting bad, and anything after it is the same? Thanks. If that's the case, we can start focusing on kernel 1230 and start narrowing down commits that could negatively effect the RHOD100...
[Touch Pro2, Tilt 2 Android Development] shatred:
uuhm, 1253 works just perfect for my rhod-100.... no freezes etc. also not realy laggy or unstable and no random reboots. 1258 sometimes gives me an SOB or freezes for 2-3 mins and sometimes random reboots.
[Touch Pro2, Tilt 2 Android Development] husam666:
I don't know if this is causing it but, when I put my phone to sleep (about an hour or more I guess), when I wake it up I do a test call and the call ends directly, without any reason.

And I can't get the calling to work except after turning flight mode on and off.

Also battery life is about 12 hours on my rhod210, on very light use. (Not sure if that what we should get or not)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
What panel type do you have? Look in dmesg, you'll see a Panel type near the beginning.

If you have an EID panel, that's expected. If you have an AUO panel, then I'm really confused :p.

Oh, Panel type 14 is EID, 13 is AUO.
[Touch Pro2, Tilt 2 Android Development] shatred:
i rly have no idea where to look

here: View attachment 520290
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Are you running a kernel from the first post? Build date/time says Thu Jan 13 15:12:48 EST 2011... Definitely not running a kernel from here.
[Touch Pro2, Tilt 2 Android Development] snalbansed:
1226 is the last kernel that I know works for me. To be sure, I'd need to go back and start to load them up again, which I can't do at the moment :-(

Any one else with a rhod100 AUO able to confirm?