yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] Tippfehler:
I have no bluetooth with kernel htc-msm-linux-20110510_210546-package

from http://glemsom.users.anapnea.net/android2/htc-msm-linux/

Is this the kernel with bluetooth?
[Touch Pro2, Tilt 2 Android Development] highlandsun:
The userland patches for bluetooth are still not out.
[Touch Pro2, Tilt 2 Android Development] JustusIV:
So when you say bluetooth, in what form is it taking? A2DP?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
A2DP is supported from what I've gleaned. It's not been tested by anyone but Jerome tho AFAIK.

When we mean bluetooth, it means complete functional bluetooth, matching what WinMo provides.
[Touch Pro2, Tilt 2 Android Development] JustusIV:
My mouth waters in anticipation :)

Do i watch http://glemsom.users.anapnea.net/android2/htc-msm-linux/# for the changes?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
For kernel updates, of course.

I think I've answered some of your questions on PPCG - watch that BT thread, I post updates any time there are any.
[Touch Pro2, Tilt 2 Android Development] Raul^:
Should I post logcat from adb here too?

I posted some on ril topic, but I think some of the problems (like no signal after wake up) could be kernel related (I don't see anything happening there, I hope it's not to late).

I can make dmesg if you want.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
The no signal after wakeup is a well-known issue with CDMA phones running in GSM mode. It's a clocks issue, there was a huge clocks commit on 1258 that broke this.

No body as of yet has been able to trace the root cause of the issue. If you're using a CDMA device as GSM, stick with 1253 until the issue is resolved.
[Touch Pro2, Tilt 2 Android Development] Raul^:
The wistilt kernel 1276 (?) worked fine previosly. His newest kernel doesn't work.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yea, when he pulled that clocks commit from jb? Why don't you believe what I say...
[Touch Pro2, Tilt 2 Android Development] Raul^:
I do belive you but I used older ril (one of the first from higlandsun) and the wistlilt 1276 kernel with modules (dirty). And I haven't had such a problem. As soon as the phone woke up the signal was on. And the wake-ups were 99% of times very fast.

I used FRX05 and then FRX06 (but I only changed system.ext2, the data was the same).

Maybe there are two or three problems not just one?

I really do appreciate your work and commitment with the project, I just say that i'm not lying , as there would be no sense (I would make it harder to repair the problem).

I can get some dmesg/logcat if it would be helpful.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
No, as I've said before, we know exactly where the problem was introduced - but the issue is no one can determine what's wrong with the code. It all 'looks' fine from several people tracing it.
[Touch Pro2, Tilt 2 Android Development] Raul^:
Ok, one last thing. Just a minute ago phone went to sleep, I woke it up and there was bo signal. Then i tried Info trick and the phone app force close, and few seconds later I had 3G singal .

I've changed kernel to wistilt 1276, phone doesnt go to deep sleep but the phone signal works after wake up.

PS.

After 10 hours of usage with 1276 i can see it works well, even after deep sleep!

What i've done:

I've added gsm strings to build.prop wih proper values of my mobile provider.Higlandsun wrote that users of CDMA should put theirs info there, but also he wrote that gsm is no more using fake provider info. I think that means you should put it there for gsm too.

I'm not sure if that helped much.

Then after a deep sleep (with 1276 kernel) it was no signal again. Then i made info trick but this time I checked WCDMA preffered.

And voila, no lose of signal for about 10 hours.And 4 restarts, by me. I wanted to check if it will work after.

arrrghhh, i can make a video and put somewhere if you dont belive me.
[Touch Pro2, Tilt 2 Android Development] championc:
Sorry for posting seemingly stupid questions but .......

With all these updated Kernels and Modules, which rootfs.img file should I be using ? Also, does the phone know to use the correct modules-xxxxx file if it's not got the same name each time ?

Also, on a Rhod100, should the USB for file copying work ?

C
[Touch Pro2, Tilt 2 Android Development] Christiaan91:
Read the first post of this thread.

For USB download droidexplorer and PDAnet
[Touch Pro2, Tilt 2 Android Development] diegolvobanania:
Or you can use MyPHoneExplorer if you have WiFi
[Touch Pro2, Tilt 2 Android Development] Raul^:
Does anyone remember where is the last kernel log before restart? My phone is restarting twice a day and i would like to know what is a reason for this.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
/data/system/dropbox
[Touch Pro2, Tilt 2 Android Development] Raul^:
Thanks again
[Touch Pro2, Tilt 2 Android Development] DHSoccer4:
6/15 kernel out

http://glemsom.users.anapnea.net/android2/htc-msm-linux/
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Meh, TOPA only stuff.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
New kernel just rolled out, fixes the GSM sleep bug on rhod400/500...
[Touch Pro2, Tilt 2 Android Development] championc:
My TP2 clock is continuously losing time. I'm using the 6/15 code but it was happening before this. Could it be something in my setup.txt or an incorrect rootfs.img ?

Any ideas greatly received. When the phone ran WinMo, I never had any issues.

C
[Touch Pro2, Tilt 2 Android Development] Starfox:
Wow first kernel that didn't have an issue with the kernel thinking something during boot (unbalanced irq and stuff). The fix for minclock may have fixed the unresponsiveness during an incoming call, but I can't test it.

There is still some error in dmesg after boot, should I dump dmesg?

-- Starfox
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Yeah I was pretty sick of those so I squashed 'em. (Those fixes came from my 1331 kernel...)

Sure.
[Touch Pro2, Tilt 2 Android Development] Starfox:
I just nuked my data.img, so this is a "first boot" dmesg.

http://db.tt/Ti2KuPL

-- Starfox
[Touch Pro2, Tilt 2 Android Development] JBS2:
Battery of my rhod100 drains in about 10 hours with 20110618_144657 kernel. With an older kernel I was able to run Android for about 1 1/2 - 2 days..
[Touch Pro2, Tilt 2 Android Development] championc:
Seems fixed now with 20110618_144657
[Touch Pro2, Tilt 2 Android Development] khabibul35:
Just updated to FRX06 on a Sprint TP2. Used the Rhod_400 startup.txt included in the build, default Kernel, and the default ts_calibration included in the FRX06 post on this (TP2 dev) thread.

ANyway, I get random reset a few times a day... and generally weak performance. It's pretty much the same as what I was dealing from a previous FRX version I got in March, although I figured there would improvements.

Does anyone know of a better Kernel for me to try that would prevent the random restarts? If it hurts graphics performance or kills camera, no big deal, just want a stable android version on the phone.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Try the newest kernel, and work your way backwards. Usually what I recommend to people - the newest kernel will have the newest code, but regressions do happen.

Resets can also be related to a misbehaving SD card. Try a different card if you can.
[Touch Pro2, Tilt 2 Android Development] khabibul35:
Latest kernel from where? Sorry if that's noob, but I don't see a kernel database on xda.
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
http://xdandroid.com/wiki/Incremental_Updates
[Touch Pro2, Tilt 2 Android Development] khabibul35:
Thanks fishingmedic, but I've tried about 4 kernels with pretty poor results. Are there any that would work specifically with a Rhod_400 (Sprint). I figured you might know since you seem to be on sprint.

Secondly, after the new kernels, I'm getting hit with failed wakeups a lot. Could this sort of thing be related to a bad sd card? Or is that the sort of thing that's related to the kernel mostly.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
The latest autobuild .27 kernel should be great on rhod400.
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
I would def try reformatting the sd card using sd formatter or the hp tool that you can get in the FAQ's and also try another sd card to see if it's any better. Those kernels from autobuild have had a lot of changes lately most of which should be good. If you've done that and it it's still causing problems, do what Arrrghhh recommended and keep going backwards.
[Touch Pro2, Tilt 2 Android Development] Erwinrom:
Hmm is it just me or does somebody else encountered the same problem? I've downloaded the 20110622_180615 version for my rhod100 but after a while I got disconnected of my provider... what I do is set airplanemode on and off so I need to type my PIN again. but then I get a Wrong PIN error...
[Touch Pro2, Tilt 2 Android Development] helicopter88:
Please don't use pin,disable it in windows mobile..
[Touch Pro2, Tilt 2 Android Development] Erwinrom:
Oh no, not that PIN.. not the PIN you setup in Windows mobile... hmm how must I describe it.. the SIM pin? :D
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yes, disable it. You should not use a SIM PIN.
[Touch Pro2, Tilt 2 Android Development] Raul^:
My comments after weeks of using on Gsm - connection to internet still has problems, it disconnects from time to time. Airplane mode work half of the time, somethimes it stucks at disconnectin and i cant connect again.

After few calls and when someone calls me if i chose not to answer i cant call to anyone. It just ends the call as soon i push call button.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Are you on the new(est) RIL or the old one...?
[Touch Pro2, Tilt 2 Android Development] Raul^:
Im on the newest ril and with rootfs that has been changed for the new ril.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
*shrug* dunno.

I randomly have service drop too, but that happens to me in WinMo as well. IMHO that's the nature of cell phones, but perhaps your issue is different. Not sure.
[Touch Pro2, Tilt 2 Android Development] Raul^:
The funny thing is it has HSDPA signal, I boot into Android. It shows 3G with full bars and then it is 3g no bars. And then it's full bars again.

I can say new ril for me isnt better, even if it should :)

I can get some logs, i hope that this getlogs program would be enough because it would be really hard to test such things at home.

One thing I know now, I love Android.

And I love Touch Pro 2. If it only wasn't so dated it would be perfect (i mean like Desire Z hardware wise but with TP keyboard).
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Agreed on the hardware part, probably the only reason so many of us still have the devices...

At any rate, logs would be good. I dunno if it's a failure of the RIL or of the kernel, but perhaps highlandsun will be gracious enough to look over your logs and help pinpoint the problem.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
I've been having the same problem. So far the radio logcats are not very enlightening, they just show that the radio reports "unknown error" whenever you try to dial, after not answering a call. Have to admit I haven't spent much time looking into it though.

Might have to grab a radio log from winmo in the same situation to see what they do differently...
[Touch Pro2, Tilt 2 Android Development] majkeljj:
any new about RAPH100 panel collapse? I know that some time ago WisTilt2 with stinebd were working on it.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Never got it to work right. WisTilt2 seemed to figure out how to collapse the panel, but they never figured out how to reliably wake it back up. RHOD has the same issue, still kinda does at times depending on what's going on underneath...

Problem was on RAPH, the panel would never wake back up correctly. I haven't seen any traction on it lately, sorry.
[Touch Pro2, Tilt 2 Android Development] majkeljj:
ok. thank you for information.
[Touch Pro2, Tilt 2 Android Development] detule:
New LED-enabled kernels

There is a new .27 kernel as of this afternoon, one that enables android to take over the front LED on RHOD and TOPA in order to convey notifications. Other devices should remain unaffected.

Please read this post completely.

The kernel now offers three regimes for the front LED, controlled by the following parameter:

/sys/module/microp_klt/parameters/led_regime

The modes are:

"2" -> This was the long standing pattern AMBER when awake, GREEN when sleeping;

"1" -> This is a modification on the above: AMBER when awake, OFF when sleeping;

"0" -> This is the default mode the phone boots in. In this mode the LED no longer signifies whether your device is sleeping or not, rather, it conveys notifications from Android, much like a LED equipped Android device would.

In the event that you want to debug your device's sleeping behavior, you can control the led_regime parameter in the following ways:

1. Via the app XdaLedRegime.apk. The app is self explanatory. The changes to led_regime enacted in this fashion will not survive a reboot. Download at: http://bit.ly/mTSoaI

2. Directly via a terminal on the phone or an adb shell using the following command:

echo "1" > /sys/module/microp_klt/parameters/led_regime

where you may substitute the number one with the number two or zero. This change will not survive a reboot.

3. Via the custom commands section of your .conf file. In particular copying the above command in your .conf file will enact a change to led_regime (starting with the next time you boot your phone) that will survive reboots to the device.

***UPDATE: The library discussed below has been incorporated in FRX07.1. Instructions below are only relevant if you are using an earlier system build.***

The kernel is one half to completely enabling this functionality. The other half is the lights.msm7k.so library, which enables the LED to blink. Without it, in led_regime=0 the LED will only turn either SOLID amber or green. Download the library from http://bit.ly/riJGit and place it anywhere on your sdcard. Add the following command in the custom commands section of your .conf file:

mount --bind "path-to-library"/lights.msm7k.so /system/lib/hw/lights.msm7k.so

In my case the library is at the root of my sdcard so my command is

mount --bind /sdcard/lights.msm7k.so /system/lib/hw/lights.msm7k.so

After booting back into android, you should verify you have mounted the library properly by either noticing your LED blinks on a notification, or issuing the following command in a adb shell

# ls -l /system/lib/hw/

The library should be listed with an August date. If the date is July, your mount was unsuccessful.

Enjoy.
[Touch Pro2, Tilt 2 Android Development] nickleby:
I've done every single step and I'm still getting solid green on notifications...It doesn't blink...

# ls -l /system/lib/hw/ =The library is dated August 16

echo "0" > /sys/module/microp_klt/parameters/led_regime =This's the line in my froyo.user.conf

I'm using the latest kernel and rootfs.
[Touch Pro2, Tilt 2 Android Development] detule:
No need for the conf line as it defaults to led_regime=0.

Post complete logs (it's best if you use GetLogs) covering the period before and after receiving a notification (text message would be best).
[Touch Pro2, Tilt 2 Android Development] großa:
Are you using this kernel :Starfox Kernel 8/20 (or the one from autobuild?)

Wasn't working for me either, but after using the new kernel it is working fine now.

No need for the conf line as detule stated before.
[Touch Pro2, Tilt 2 Android Development] nickleby:
Don't worry, I restarted the phone like 2 times and then it worked properly! I know there's no need to use that line, I used it because I thought the phone was not reading the led conf correctly :p

Is a shame that the blink led notificaction only works when the screen is off. Thanks anyway for your help and your work :)
[Touch Pro2, Tilt 2 Android Development] trancerobot:
You folks should try the October 1st kernel. It's much more stable than before. The battery meter seems slightly more accurate, it has a better signal, GPS is working, and it boots faster.

Off topic, but still important - I recommend the game Space Physics, if you haven't installed it already. It runs perfectly in XDAndroid, and I find it more fun to play with the Touch Pro 2 stylus than on my stylus-lacking rooted Nook Color.

/// lol, I just realized this wasn't the right section to bring this up. Ignore it.
[Touch Pro2, Tilt 2 Android Development] championc:
I have to say the the latest kernel htc-msm-linux @ 20111017_080427 is looking pretty good on my RHOD100. Quick responses 90% of the time - especially if I ever rotate it 90 deg to landscape view
[Touch Pro2, Tilt 2 Android Development] hashtowent:
can agree with landscape switch it works good w/o its okay. =) regarding wake up
[Touch Pro2, Tilt 2 Android Development] großa:
New kernel htc-msm-linux @ 20111017_080427 is working fine so far.

But i'm going back to Starfox test kernel. It's faster and ext4 is working with his kernel.
[Touch Pro2, Tilt 2 Android Development] milda25:
Kernel issue?

I have one problem with any glemsom kernel/modules (even I'm always using latest glemsom's kernel). Having GSM Rhod100 in Czech Republic, operator O2). If I'm in area with 3G network, too often is some issue with incoming call - phone ringing, get up call, call is conected, but nobody hear me and I don't hear anybody on other phone side, ending call. Other side has been call me again, get up the call and now is all OK. But on 2G network I haven't this issue. I'm setting up "Using only 2G network" in Menu-Settings-Network Settings-Mobile Network and all is OK even if I am on 3G signal (but using 2G). Have this problem anyone yet?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Why do you think this is a kernel issue? Is there another kernel that doesn't exhibit this behavior..?
[Touch Pro2, Tilt 2 Android Development] milda25:
I don't know if there is another kernel without this behavior, I always using only glemsom kernel :) And every version of this kernel has same behaviour. But I must say, that I don't know if that is a kernel issue. I don't occurred me another cause. So that's the reason why I'm asking here, if anyone have this problem too.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Well, it could be any number of things.

You say it's just an audio routing issue? So you can hear the far-end in the phone call, but the far end can't hear you? Have you tried the speakerphone on/off trick...?

If you turn the speakerphone on, then back off, quite often it remedies one-way audio issues.
[Touch Pro2, Tilt 2 Android Development] milda25:
No, I can't hear far-end in the phone call and far-end can't hear me (no audio on both side of phone call). My english isn't perfect, but I make efforts write this in my first post :-)

And no, I haven't tried speakerphone on/off trick. Should I try this in this case? (in case of mutual no audio?)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Sure, it certainly can't hurt.

Also make sure you're on the newest kernel/rootfs.
[Touch Pro2, Tilt 2 Android Development] milda25:
OK, I will try speakerphone on/off trick and give the feedback (but tomorrow, in my home location is only 2G, only in bigger town, where I'm working is 3G).

And yes, I have newest kernel (20111017_080427) and newest rootfs (20111019-8404718).

Thank you, arrrghhh, for this time.
[Touch Pro2, Tilt 2 Android Development] milda25:
Hi arrrghhh, I tried recommended trick with speakerphone on/off and yes - it's help me!

But can you explain me how is possible, that this problem is solved by switch using 2G network only too, if main problem is in audio routing?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
No clue, other than our audio routing is far from perfect. There's some new code that *should* fix all of it, but there's still some bugs we're trying to iron out before it's released publicly.
[Touch Pro2, Tilt 2 Android Development] milda25:
OK, thank you, arrrghhh. I'm enjoy for new results of your and other devs hard work.
[Touch Pro2, Tilt 2 Android Development] aichemist:
latest kernel last longer on battery and more responsive. Very nice =). Don't have to charge in the middle of the day right now.

Good !!
[Touch Pro2, Tilt 2 Android Development] galexandr:
Which kernel number is it? im trying to figure the battery length,

Thanks
[Touch Pro2, Tilt 2 Android Development] coolwater22:
what kernel is it,? my battery usually lasts like 5-6 hours, which is not alot.. i only send/receive a few texts and listen to music for like an hour.. it dies off preety quick..

thnx
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I would assume the newest kernel.
[Touch Pro2, Tilt 2 Android Development] crownvn:
I spent 4 days for testing of latest kernels.I feel that about working time of battery 's very good & better than original however I wonder why the screen always turn 90 degree when I access any option ( setting, ....) although I tried reboot from WM then run Haret.exe it 's straight at the first time only.(I don't changed any in the startup file)

more infor : in case I like come back to original kernels(attached build), I copied & pasted original zImage & modules file come back then run Haret.exe but can't . I don't know why? have anybody ever happen?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
You should focus on one question at a time, because these nonsensical ramblings are confusing.

If the screen is set to auto-rotate, it'll auto-rotate. Disable this if you don't like the feature. If you mean on boot, that issue was resolved in the later kernels.

What do you mean you "can't" copy and paste the original zImage/modules? Remove the existing, replace. Just as with any other kernel.
[Touch Pro2, Tilt 2 Android Development] crownvn:
yes, I knew it. I 'm set to auto-rotate but the problem 's the screen should rotate right direction. actually now when I take the phone on upright direction the screen should keep as upright direction but it rotate 90 degree (opposite key board) although I tried re-calibrate G-sensor & re-check in WM ,it rotated right direction. of cause I don't forget reboot android :)

the reason I would like come back original zImage/modules for re-test & make sure that if original zImage/modules happen as same as latest .

I deleted new zImage/modules(latest kernel) then copy & paste original kernel for replacement to be successful . at the end run Haret.exe the screen display cycle run( reading data on WM) and held on here. can't access Linux screen :)
[Touch Pro2, Tilt 2 Android Development] crownvn:
spent some days for looking for error at the end found my SD card was failed ( can't copy & paste although the notice that copy or paste successfully) Now it can't format on windows, dos or mini tool . I don't know why ? anybody know about format tool for SD card ? ( my SD card has partitions 3 ext and still running android normally )
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
HP Tool.
[Touch Pro2, Tilt 2 Android Development] muziling:
enable data connection, use browser to aceess some webs, press power button to turn off screen, after serveral minutes, phone auto reboot.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Is this consistently reproducible? What build? Is this some new issue with this kernel, is there some older kernel where it doesn't occur?

C'mon, you've been around long enough to know that logs are great, but if you're going to report a bug like this being thorough is also necessary.
[Touch Pro2, Tilt 2 Android Development] muziling:
Happend many times, with build Neofroyo, Disable data connection, all kernel with FRX07K,FRX06,Neofroyo may cause phone reboot, ACL nand version will cause phone freeze

I had looked this kmsg log, phone reboot is because of kernel/system auto close smd connection, my radio version is SPCS 2.32.00WF, which download from

http://forum.ppcgeeks.com/cdma-tp2-...10-rhodium_w-radio-roms-mirrors-included.html
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Try the 2.37 VZ firmware. I don't have this problem.