yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Odd, I got an error on wifi too.

Don't use it much, so I didn't even notice. I'll see what I can do, probably a missing module or smth silly.

Just checked logcat,

E/WifiService( 1434): Failed to load Wi-Fi driver.

I'm going to a car show right now, I'll see if I can fix it when I get back :p. If not, perhaps someone can look at the modules and see if it is indeed missing that module?
[Touch Pro2, Tilt 2 Android Development] toadlife:
Another spontaneous reboot..though I think this one might have been related to overclocking, as I don't see a kernel panic in the kmsg logs. I'm going to run at the stock speed for awhile and continue to take logs.

http://dl.dropbox.com/u/25754012/debuglogs-2011-04-17_spontaneousreboot.tar.gz
[Touch Pro2, Tilt 2 Android Development] toadlife:
Must only affect certain models (I see you and arrrghhh are both on Sprint), as WIFI works for me with this kernel.
[Touch Pro2, Tilt 2 Android Development] BigOnes69:
Interesting.
[Touch Pro2, Tilt 2 Android Development] Starfox:
Tethering works on 4/15 on Sprint RHOD400. It loads bcm4329.ko.dated 4/15.

-- Starfox
[Touch Pro2, Tilt 2 Android Development] BigOnes69:
What are you using for tethering. I am using xdandroid wifi tethering for root
[Touch Pro2, Tilt 2 Android Development] Starfox:
The built-in one. As mentioned in one of the threads, it works as long as you "set" the settings after turning it on.

-- Starfox
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Hrm, perhaps I messed something up... Not sure what. I don't really use wifi. I'll try to triage my issue, but if it's working for others...

I was running a weird build at the time (modded FRX06), I'll try a clean one.

BigOnes69 - which build are you running?
[Touch Pro2, Tilt 2 Android Development] toadlife:
scbs causing reboots

I'm thinking my spontaneous reboots might have been caused by the scbs thingy. I turned off overclocking and later generated a scbs.conf file using the 'ba tree app'. After rebooting with the scbs.conf file, the phone kept rebooting right after booting up. Once I removed the scbs.conf file from my sdcard, the phone stopped rebooting.

Here is the bad conf file....

http://dl.dropbox.com/u/25754012/scbs.conf.xxx

EDIT: jonpry informed me that my conf file was bad. I'm generating a new one.
[Touch Pro2, Tilt 2 Android Development] BigOnes69:
FRX06 with Wistilts 4/1 Kernel 1276. I noticed that Jonrils kernel is labelled 1276 also so I am thinking he used the same one.
[Touch Pro2, Tilt 2 Android Development] dsramesh:
Using the latest rootfs.img and kernels and the require apk file, the battery on Rhod 500 (Verizon TP2) shows wrong. It said I needed to charge the battery and that it had 10% left. I boot up into Windows mobile and it showed 50%.

..Ramesh
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Did you actually calibrate? Did you do the analysis of the logs...?
[Touch Pro2, Tilt 2 Android Development] husam666:
Dude something really weird is happening.

I pulled out my battery while running android forgetting that its connected to the charger and android is working :eek:

Is it safe??

It's like laptops working from power source without battery

Proof

cant think of an xda app signature
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I didn't think it would work, but I don't see why it would be bad/unsafe. Just won't charge your battery, as you've pulled it out.. Why do you ask? What does it have to do with this thread?
[Touch Pro2, Tilt 2 Android Development] husam666:
Just thought that maybe you had info ;).

It doesn't happen with winmo and I didn't know where to post it :p

cant think of an xda app signature
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Heh, it works for me too. Never needed to do it, so I've never tried it before. It's a feature ;).
[Touch Pro2, Tilt 2 Android Development] husam666:
Glad you like it :p

No more overheating batteries ;)

cant think of an xda app signature
[Touch Pro2, Tilt 2 Android Development] toadlife:
NO sleep

Noticed that in the last few hours, my phone will not sleep at all. I've tried killing all user processes, and even killed scbs. Nothing is running and phone still won't sleep. It blinks green, but wont go full green

I took some logs....

http://dl.dropbox.com/u/25754012/nosleep.zip
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
I do this all the time and have been doing it for a while. I have 3 batteries, so when one is dying I connect it to the charger just so I can pull the battery out and put another charged one in. I then unhook the charger. It takes a few minutes for Android to figure out the battery is new and charged, but eventually it shows 100% after a few minutes.

I never mentioned it, because I thought nothing of it! :)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
It appears wifi puked over, and over, and over, and over again.

[63009.365112] BUG: scheduling while atomic: events/0/5/0x00000002
[63009.365112] Modules linked in: iptable_nat iptable_filter ip_tables xt_multiport xt_state ipt_MASQUERADE nf_nat nf_conntrack_ipv4 nf_conntrack x_tables [last unloaded: bcm4329]
[Touch Pro2, Tilt 2 Android Development] toadlife:
OK, tonight the phone went haywire. Luckily I was taking logs the whole time.

Phone working fine for several hours...

* played music with pandora connected to external speaker for about an hour

* closed pandora and unhooked usb dongle

* system went to sleep

Trouble starts....

* failed wake (with solid green) for several minutes

* phone FINALLY woke up after mashing/holding buttons for several minutes

* system *extremely* sluggish

* osmonitor/top shows system server and system taking up ~25% CPU time\

* After killing several process, finally decided to kill -9 system_server process

* system reloaded but no radio connection and system still extremely sluggish

* gave up and reset the phone

http://dl.dropbox.com/u/25754012/system_sluggish.zip
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I've heard that using the USB dongle can sometimes cause this condition to occur. I can't seem to find mine, so I can't recreate the issue. ACL needs to look at it, but he's knee-deep (maybe neck deep? :p) in NAND.
[Touch Pro2, Tilt 2 Android Development] pdawg17:
Yup...it's not just this kernel...it's been doing that for me ever since I got mine a few months ago...I know a few logs have been posted somewhere but obviously not as important as the other stuff going on...
[Touch Pro2, Tilt 2 Android Development] Gilliland:
Yeah, I've had that experience pretty consistently. It's really the only thing at this point that makes Android unstable for me. It's great to have the USB headset working, but it seems to work just once per boot. If you unplug it and reconnect it a time or two, you find either that your audio is hosed, or that the entire system becomes extremely sluggish, or that it simply locks up completely.
[Touch Pro2, Tilt 2 Android Development] manekineko:
Since you use the headset a fair bit, if you've got time, maybe you should try some of the older kernels from a few months back and see if this problem still exists.

When I was first testing the USB headset, I could have sworn this problem didn't exist, and being able to know which commit caused it really helps a lot in fixing these sort of things.
[Touch Pro2, Tilt 2 Android Development] Gilliland:
:) It's a reasonable suggestion, and I'll try to find time to do some testing like that. But I've been quietly testing this feature with every kernel since it was announced, and I've never had any consistent luck with it. (I say quietly because I've posted here only very rarely.) It always works at first, but never continuously. In fact, that's what's driven me to try to keep up with the newest kernels, including test kernels. I don't have the tech skills to dig deeply into this, but testing it with a couple of older kernels is certainly within my grasp. So I'll see what I can do.
[Touch Pro2, Tilt 2 Android Development] toadlife:
I've never had this problem with the usb headphones...only the usb *dongle*. I've been using usb headphones ever since they first added support for them in the kernel with no problem.

EDIT: Now I'm going to try out my usb headphones now to see if the issue happens with them too.
[Touch Pro2, Tilt 2 Android Development] BigOnes69:
I have been using a dongle and have not had consistent problems with it. I connect and disconnect all the time. It is more than likely a brand problem.
[Touch Pro2, Tilt 2 Android Development] toadlife:
What do you mean a "brand problem". My dongle is the original HTC one that came with my phone, as are my usb headphones.
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
It's happened to me using the HTC usb dongle, but I can't say it's consistent IMO. I made mention of it in one of these threads or over at PPCG some time ago, but in really paying attention to it, I can't say that it was a consistent issue each and every time I've used the dongle, which leads me to believe it's something other than the coding, i.e. apps may be running that are really causing a lag.
[Touch Pro2, Tilt 2 Android Development] BigOnes69:
I have an off brand dongle and it works most all the time connecting and disconnecting. I have had connection problems but that is over weeks not daily. I have a 16GB card that has about 12GB of music and use it daily.
[Touch Pro2, Tilt 2 Android Development] toadlife:
When it happened to me I killed all user apps, connected to abd a looked at all of the processes via top and nothing weas taking up cpu time, so this has to be a system/kernel issue.

Both time it has happened I pulled out the dongle while the app (Pandora) was still open and playing. I'll experiment a bit - try closing out the program first before disconnecting and try it with the build in media player too.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
dmesg logs, although I think some have already been taken... Perhaps some printk's around the usb dongle code is in order...
[Touch Pro2, Tilt 2 Android Development] toadlife:
Ah ha!

Tonight I tried pulling the headphones out of the 3.5mm jack before taking the dongle out, and the bug did not appear. Every time the problem has happened I've pulled the dongle out while the headphones where plugged into it.
[Touch Pro2, Tilt 2 Android Development] toadlife:
I spoke too soon. The sluggishnes started a minute or two after removing the dongle. :(
[Touch Pro2, Tilt 2 Android Development] Starfox:
Can you post a kernel module with compcache stuff enabled (lzo/xvmalloc) so I can test whether there is a difference? Thanks.

-- Starfox
[Touch Pro2, Tilt 2 Android Development] manny05:
Okay so i installed this kernel from the first post and apparently i cant get my 3G to work..the icon wont come up on my status bar.. is this a bug you guys have ? if not how do i fix it?

also my phone wont connect to wifi (it has a wep password..i heard it has this issue connecting to routers with a wep password. i forgot what app to download from the market if there is any to fix this issue.) if anyone can help me out on this, i will really appreciate it
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
I have no issues with my RHOD400's icon, but don't know what phone you're on or service you're using. As far as wep, it's noted in the FAQ that arrrghhh has done in his first post and by searching you'd see it's a common occurrence. Change the security to WPA or wifi-ace may work.
[Touch Pro2, Tilt 2 Android Development] manny05:
i have the tilt 2 on AT&T.

my data was working fine until i added this kernel. so i dont know what exactly is blocking me from getting data.. i tried turning it on and off, turning airplane on and off..even restarted my phone a couple of times..but nothing.
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
Search through the thread for recent posts about issues w/ data but I don't recall seeing any. Might be something else you've added to the build that's causing the issue. There's enough people using that phone that someone will if they're having issues or a fix.
[Touch Pro2, Tilt 2 Android Development] manny05:
Also ive discovered that if i leave my phone sleeping for say 5-10mins or more my carrier signal would turn off. I would turn on the screen and it would say

no service...only way to get the signal back is if i turn on airplane mode and turn it off..otherwise i would have to restart my phone...

any fix to this?!

EDIT: managed to fix the data issue..just read the 1st post and had to change a couple of more files...

i am now looking to see if the carrier connection issue still occurs. so i will update on this
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
You can copy it in and insmod or modprobe it in I would think...

I didn't realize these kernels didn't include it - doesn't really matter, as all the testing in the past related to it failed. Made no difference whatsoever, slowed the device down IIRC.

Are you using a RHOD400/500 as a GSM device? The radio will shut off in sleep if so. Known bug, working on a fix.
[Touch Pro2, Tilt 2 Android Development] manny05:
actually i think i managed to get rid of it. i re-read the 1st post and i forgot to go to the other thread and retrieve the other files. after i did that, wifi and data work flawlessly and i never lose my signal.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Ah yes. It's always a good idea to follow the steps :p.
[Touch Pro2, Tilt 2 Android Development] SteelLife:
Wifi-Ace, I changed rootfs and can't get a connection now but wifi-ace does work, didn't think rootfs would affect wifi but I'm a noob!
[Touch Pro2, Tilt 2 Android Development] Starfox:
Logs of a miniboot attached. This was actually the 2nd miniboot of that boot. You'll notice that main logcat buffer is already full by the time the restart is complete. First mini was during update of an app. This one was a nonresponse to opening Terminal.

dmesg > crash.txt

logcat -d -v time > crashlg.txt

logcat -d -t radio -v time > crashrd.txt

http://db.tt/V9zjPql

-- Starfox
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I'm going to assume by miniboot you mean you're doing something, system freezes, and all the sudden you see the flying Androids boot animation again?

This is a known issue, with no known fix. I seriously doubt it's a kernel problem, I'm almost positive it's userland - killall zygote seems to happen when the system becomes unresponsive. Hopefully the logs are useful, but like I said I seriously doubt it's an issue related to this kernel or any other kernel for that matter.

Reboots to WinMo... are a different story. Those are kernel, whether the kernel didn't handle something correctly, or just decided to panic itself into oblivion.
[Touch Pro2, Tilt 2 Android Development] reckert:
I've been seeing the random reboots to WinMo - how do I collect the logs when that happens, after I restart it looks like the logs are reset
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
They are.

There's ramconsole, which is broken on this kernel... or you can setup logs to constantly run thru init or gscript (haven't done this myself, been meaning to) so you can catch them hopefully right up to the point of failure.
[Touch Pro2, Tilt 2 Android Development] Christiaan91:
Most of the time, when somebody is calling me, i can't hear the other side. When i call there is no problem. I know this is a know problem, but can i help with providing some logs? If so, witch logs?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
This is fixed, at least I haven't experienced it in months.

Does flipping the speakerphone on/off fix the issue? If so, there's evidently still some audio routing logic that isn't working on your device.

Also, you know to not have the phone in a muted/vibe-only state. AFAIK that bug was fixed as well, but I can't remember.
[Touch Pro2, Tilt 2 Android Development] Christiaan91:
I'm almost always in vibe-state and then 8 of the 10 are working as normal. When the volume is at its highest, then the trouble starts.

I forgot the speaker trick. I'll try it.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
So you're saying when it's set to vibe-only it does work?

Previously this was an issue - if the phone was set to silent/vibe-only, in-call audio had issues. I'm pretty sure WisTilt2 patched this tho.
[Touch Pro2, Tilt 2 Android Development] Christiaan91:
Depends who's calling, depends on phone and/or carrier. Cuz the problem is always with the same persons. 1 home phone and 1 winmo. The home phone is always calling when i'm in normal mode. the 1 winmo is vibe mode.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Hrm... Either I'm not following, or this doesn't make any sense :p.

I don't see how the far-end would have any effect if it's a bug in XDAndroid... Unless I'm just flat out missing something.
[Touch Pro2, Tilt 2 Android Development] Christiaan91:
I'm not so familiar with the working of Android (i believe it's linux. Learning to make scripts, so that's almost working perfect:D) So it most be just a coincidence.

But can i help or find the problem through logs?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Perhaps, but I wouldn't be able to help decipher. dmesg will be kernel logs. Not sure where the issue is to be honest, I don't have the issue - but I haven't tested every aspect of the bug. My ringer is on 100% of the time too, so that might have something to do with it - experiment, and do a fresh boot each time.

-See how it acts on a fresh boot with vibe-only on. Inbound/outbound, see if the issue recurs.

-Again, on a fresh boot, set audio to full and see if you can recreate.

Another interesting thing to note is perhaps flipping between vibe-only and audio on is the issue. Gotta triage and locate the actual action that is causing the issue. Then the logs will be more useful. Just a jumble of logs doesn't do me any good. I'm also not very good at picking apart logfiles :p.
[Touch Pro2, Tilt 2 Android Development] Christiaan91:
I'll try it when i have the change. :P
[Touch Pro2, Tilt 2 Android Development] DVA4890:
For me I would like to see it the other way around. Solid green for going into deep sleep and a slow green blink to show it is in deep sleep. Just me
[Touch Pro2, Tilt 2 Android Development] highlandsun:
I would have preferred it that way too...
[Touch Pro2, Tilt 2 Android Development] toadlife:
Button lights on while asleep

Small problem...

To solve the problem of butt-dialing, I configured my keymaps so that the the non-keyboard buttons do not wake the phone up (removed WAKE_DROPPED). When the phone is in deep sleep and I hit the back and end-call buttons at the same time, the buttons light up and never go off - presumably because the phone is in deep sleep.

Would it be possible to fix this behavior?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Well the button lights shouldn't be in the kernel in the first place. Need hooks to userland, so userland can tell the kernel what the light status should be. Same goes for caps/FN. Having them turn on/off in the kernel is really just a hack anyways.

I've seen other times when the button lights stay on. Power the phone on/off, fixed.
[Touch Pro2, Tilt 2 Android Development] DVA4890:
arrrghhh do you know if there is a way me and highlandsun or anyone else could change that is there something we could do on our end to change it.

Thanks
[Touch Pro2, Tilt 2 Android Development] manekineko:
You could implement the hooks in the Android system to the kernel so they work properly.
[Touch Pro2, Tilt 2 Android Development] DVA4890:
Might ask how I could do that. Or where to look.

Thanks
[Touch Pro2, Tilt 2 Android Development] manekineko:
If you're a programmer, you could jump on irc and discuss this. I think stinebd would be the guy to talk to, he is chiefly responsible for the Android system side, and maintains the repository. It could also help to discuss with WisTilt2, who originally implemented the LEDs, so you understand where to hook into.

If you're not a programmer, you can't.
[Touch Pro2, Tilt 2 Android Development] manny05:
Have a small problems that may or may not have been addressed... dont know if this has to do with the kernel or what. I have a tilt 2 running froyo with this kerne and the highlanders ril.

everything runs great however when i plug in my headphones (via the adapter that i had to purchase...) whenever i unplug it i lose all sound...when i plug it in it doesnt fix the issue so i am forced to either restart my phone.

any fix to this?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Does this happen on autobuild kernels?
[Touch Pro2, Tilt 2 Android Development] manny05:
autobuild kernel?!? im not sure if i have that (im new at this)

im using the kernel from the 1st post in this thread.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Surely you've used the autobuild service? There's a link to this site in the first post of my FRX06 and GBX threads.
[Touch Pro2, Tilt 2 Android Development] manny05:
EDIT: as a matter of fact, i tried one and it solved the issue.

now i just gotta get my data working again -_-' wifi is working fine.. just lost data when i formatted my sd card. (re-did everything since my tilt just randomly kept freezing or rebooting..)

im thinking it probably has to do with the rootfs file since i tried a couple of the kernels on the site and never got data back.

ill see what i can find.

as of now i am using this kernel from the link you gave me:

htc-msm-linux-20110228_202832-package.tar.bz2
[Touch Pro2, Tilt 2 Android Development] Sank112:
Camere freezes

Hi,

When i tried to use the camera on my TP2 Rhod100 it freezes and afterwards it says that he wasn't able to connect to the camera.

Further so far so good. Amazingly fast and stable at the moment. Using it just a couple of hours, but i'm impressed!

Just one more thing. During the boot a message came along, wich said the was a module he couldnt install. It happend so fast almost at the end, before i got the splash screen.

:confused:
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Kernel isn't meant to test cam.

Also, unless you're having an issue with a module missing, don't worry about it.
[Touch Pro2, Tilt 2 Android Development] Entropy512:
However, unless the autobuild kernels now display paneltype, these kernels are the only way to find out if you have a AUO panel.

Cam is broken on RHOD100s with an AUO panel. Known issue - AUO panels are rare and no AUO panel owners stepped up for testing when the camera integration was performed.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
True, I forget to mention that. I preferred to just mention this test kernel isn't meant to test cam :p.

At any rate, this is OT to the thread, but a few AUO panel folk have stepped up and jb has taken some time to peruse their logs. With more investigation, it seems in very low light their cameras do work, but as the light levels increase the stability decreases - hopefully jb has a fix for them soon.

Alrighty, for more discussion of this AUO panel cam topic, please put it in the appropriate thread - cam testing thread. Thanks!
[Touch Pro2, Tilt 2 Android Development] Sank112:
Thmx for the reply..

Another question. Today my phone hung for 3 times in landscape modus. And nothing on the phone reacted anymore, no buttons, nothing. Any possible sollution. Auto landscape is off.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Dunno. Pretty sure it's unrelated to the kernel, just sounds like the system hung. Get some logs if you can consistently reproduce it.
[Touch Pro2, Tilt 2 Android Development] Christiaan91:
Best thing to do for you is running logs.

The logs can help the devs to find the problem.

Logs for a kernel problem are, i believe, kmsg and dmesg.

Probably for this problem you need a kmsg log.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
kmsg and dmesg are basically the same thing, kernel debugs ;).
[Touch Pro2, Tilt 2 Android Development] Christiaan91:
:o lol, didn't know.

but you can run a kmsg realtime, dmesg from 1 moment.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
True. Kinda pick-your-poison there - do you need to run once, or do you want to keep it running? ;)