yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] drynaps:
I have had issues with all the kernels after the 11/03/2011 which is by far the most stable for me. I believe it is based on the autobuild 1276 kernel.

The phone gets extremely hot on the newer kernels and I get random reboots both with the new RIL and the regular one.

I do have my RHOD400 on CDMA and it is overclocked, but as I mentioned I don't get these reboots with the 11/03/2011 kernel.

Also I have just tested the phone without overclocking and it does not get as hot, but it still reboots randomly.

I have removed my data.img and the same thing still happens. It is really laggy with the new kernels.

I should mention that the same thing happens with the autobuild kernels past 1276.

Any ideas?

Thanks!
[Touch Pro2, Tilt 2 Android Development] dsramesh:
Thanks. It is working fine so far.

One problem I see is that the Volume button does not work.

It woke up from sleep without problem. I had it running all night and switched over to windows as I had to drive and be on a call (Bluetooth). Once Bluetooth is enabled then this is my full time OS!

..Ramesh
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
auto-rotate screen issues...

Previous to the 4/2 build that had the stylus/landscape issue and previous to this 4/4 build I really never had that much of an issue with the screen auto-rotating when I flipped the phone from a portrait to landscape position or vice-versa. I am guessing something that Wistilt2 messed with when breaking and/or fixing the issue in the 4/2 and 4/4 screen has changed something to where my Rhod400 gets stuck in one orientation or the other when auto-rotate is pressed.

I know auto-rotate was always a little bit buggy, but in reality I never really had that much problem with it at all, and it work 98% of the time correctly for me until now.

Obviously if I slide the keyboard out it does go to landscape if I want it to go that way. Any thoughts or possible fixes to get it back to where it was in the kernels previous to 4/2 and 4/4?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I have the same device, using the same network - haven't had a single reboot on these new kernels. Even with an OC to 710.

Also, I have noticed some lags - but I think I'm just getting too widget-happy :p.

Could be your SD card I guess. I don't know why older kernels would be better for you...

Missed this one, sorry.

My screen doesn't get stuck in any particular orientation at all - not more than any other kernel... I'll ask him, but so far you're the only one who seems to have this issue :p.
[Touch Pro2, Tilt 2 Android Development] dsramesh:
I had no problem on the orientation on rhod500 (Verizon Touch Pro2).. though felt it was a tad over sensitive to a point a that a slight tilt would change the orientation.

In fact I have problem in Windows mobile 6.5.. where every now and then it gets stuck in portrait orientation and then only works when keyboard is flipped open.

..Ramesh
[Touch Pro2, Tilt 2 Android Development] aberry:
reboot

Sprint, Rhodium400, FRX06, Wistilt 4/4 kernel, Test Ril -

Having said all of that, I've rebooted one time in a low service area only when I was scanning wifi signals trying to find one to connect to. It was really struggling to find a wifi signal and it finally gave up and rebooted. I was in Oologah, OK. Very low service area and the data and radio did wonderfully while I was there. This might have been better posted in the RIL thread, but I wanted to confirm your findings Arrrghhh even in low service areas.
[Touch Pro2, Tilt 2 Android Development] reckert:
Using the 4/4 Kernel, FRX06 and Test RIL:

This kernel is working really well, though for me battery seems to last about 6 hours - I need to figure out what extra stuff I have running.

however I do seem to have a repeating problem - when I turn off the device, on the next boot the fsck's report errors - at one time it changed data.img to DATA.IMG which seems to have prevented booting to android.

I havent seen this in the previous kernel so I was wondering if a 'sync' was missing somewhere?

Otherwise everything is running great.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
All my builds have a line in the user.conf file that removes these files, because they will always get created - can't really avoid it, we don't properly unmount everything when rebooting to WinMo after all - even using the Shutdown menu does not properly dismount everything. This will be a moot point with NAND.
[Touch Pro2, Tilt 2 Android Development] Starfox:
Actually, Haret seems to be the one responsible. I think it tries to create a copy of startup.txt right before boot, then the cluster goes unallocated.

-- Starfox
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Hrm... I'm not positive in fact, this is just what I heard from some devs (assuming IIRC :p).

Either way - whether it's the lack of umount or haret, both are moot points on NAND ;).
[Touch Pro2, Tilt 2 Android Development] steel4w:
hi, arrrghhh

where can i get old wistilt kernels? for example i want wistilt 3/1/11 (Mar 1) kernel, but can't find anywhere.

Thanks
[Touch Pro2, Tilt 2 Android Development] Jandyman:
As arrrghhh said before, this kernal is for testing not just for general use, when its ready for general use the changes will be commited. There is no point giving out old kernals because that way we'll make no progress, the only way to move forward is the use the latest . . . .have problems? Report them, grab a logcat if you can and I'm sure they will be solved. That way you are helping everyone.

Sry I know its harsh if that was the best working kernal for you but that's what was said ;)

Tell us what buld your using and your problems? :)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Jandyman hit the nail on the head - I don't repost old kernels (and I would appreciate it if no one else does ;)), what would the point of that be? Don't look back friend, we must look forward.

As these kernels are for testing, if you have issues, it's best to revert to an autobuild kernel - all the stuff we test here is destined for autobuild in one way or another, WisTilt2 just wants to test this code with a wide group of people before he pushes commits.
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
I've been trying the latest test, and the results on my rhod100/auo aren't that good :(

- A lot of hangs (5+/hour)

- Wake-up needs touch to wake (8/10) or is slow

- It won't go to sleep, when pressing power the following happens:

* bl and screen turn off, LED remains orange

* after 5-10 sec. light goes to blinking green (is it correct that the blinking freq. is much slower, like 1 in 10 sec?)

* won't go to solid green

I tried this on new data.img, with test RIL. For me the best working test kernel is still the 26/2/11 one (haven't been able to test all of the ones after that).

What I noticed is that I get a whole lot of text on bootup, of which I have no clue as to what it means :)

Posted dmesg on http://pastebin.com/Ft8f1YwR. It consists of bootup and a few power-button presses.

Considering that I have an AUO panel, and everybody else is so happy with this kernel, would that be the likely culprit?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Hrm, you did try on a new data.img and the issues still persist? Even without any apps installed!??!

Have you tried a different SD card?
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
Yep, although I installed a terminal emulator to export the dmesg (don't have adb at work)

Not sure if a different SD card would have any influence, this one is 1 month old and really works fine with all previous testing kernels. I just switched back to my regular kernel, and it works fine.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
So you're the first AUO user to try the 4/4 kernel? Or the 4/2 kernel?

I thought other AUO folk tried it, but perhaps not... Ugh. You guys are so difficult :p.
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
Not sure if I'm the first, I know Shatred is also AUO, but not sure if he's tried these already.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I'll see what I can pull from your log... I don't know what to tell you to be honest tho, not much should've changed for AUO... at all... Your phones are so difficult!
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
Yeah I know, I hate us :D.

just PM'ed Shatred to see if he has tested this one... One thing I noticed on bootup was that it was whining about something with irqs that were already taken (in the log). Since you said Wistilt found something strange with the irqs and changed it, perhaps its related? Anyway, I'll let the rest of the debugging in your capable hands ;)
[Touch Pro2, Tilt 2 Android Development] Tippfehler:
- Kernel 4/4

- Rhod100_de

- newest ril

- I have a green light in standby.

I hope, I can help with my dmesg.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Do you have any problems? Solid green is good, that means it's in deep sleep...
[Touch Pro2, Tilt 2 Android Development] Tippfehler:
Sometimes I have problems to wake it up. But it is not dead, it only takes a long time. Ten seconds maybe?

With Wlan I have no access to my router. But I think it´s a problem of Opera Mini (with activated Opera Link). It is difficult to switch between 3G/GSM and Wlan. It´s all on, but i don´t know how it connects to the internet. Sometimes I don´t have internet access, wait a few seconds and it is running. Maybe there is a better Connection Manager in the market.

I try android only one or two hours a day and look forward to the day when I can use android like winmo. (need BT and longer battery lifetime)
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
The battery life in these builds far surpasses running in WM. Moderate usage I am getting 12-18 hours usually. I could never get that on WM. I hear BT is getting close to being fixed.
[Touch Pro2, Tilt 2 Android Development] Jandyman:
The battery life in these builds far surpasses running in WM. Moderate usage I am getting 12-18 hours usually. I could never get that on WM. I hear BT is getting close to being fixed.

[/QUOTE]

Well that's unusual, most peoples android battery life is nower near as good as winmo . . . . But less than 18 hours in winmo seems like nothing? What rom your using?

Also on the bluetooth status last time I heard the modules side was fixed but there was some userland stuff still to be added. But maybe problems where found since I don't kno.
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
My quote thing didn't work right on the XDA App... Yeah I get good battery life on Android, but not more than 10-12 hours usually with moderate usage on WM. I am running the the most recent Mighty Rom even though it has been a couple of months since I have actually ran in WM. I just boot straight into Android.
[Touch Pro2, Tilt 2 Android Development] Tippfehler:
That sounds good. When I play with my phone it says after two hours that the battery is nearly empty. Maybe it is better with the newest kernel. I will try it in the evening. I need 10 hours lifetime, one hour usage and 9 hours standby, then I can charge it. How many power consumes the green led? I think it is better to switch the led off in standby in the final version of the kernel.

Sorry for this off topic, I hope we find back to the testkernel.
[Touch Pro2, Tilt 2 Android Development] nasapunk88:
my battery life has gone down since past builds. I used to reach around 12hours and now I'm back to getting around 8hrs. =(

If your WM is not getting over 24hours your doing something wrong (and thats not just standby time).

If you are in solid green your battery should last id say at least a day. In solid green I've done 5hours using only 10% roughly. So for your case you should never have a problem. I use mine in school for around 6 hours straight of class's, thats how I avg 8 hours only lol. (who actually pays attention in class when u can be on ur phone reading these fourms >.>)
[Touch Pro2, Tilt 2 Android Development] eik:
I am running this kernel on Rhod100 AUO. It is running ok so far. Still some stability problems though (freezes), alsso with the new ril.

Yesterday it burned out of my pocket for the first time since wistilt2 did his fixes. Battery had drained in 3 hours or so. But normally it goes to solid sleep. And if not just waking it up and asking it to go asleep again will work (these phones are just like small kids sometimes)
[Touch Pro2, Tilt 2 Android Development] Entropy512:
Once the PM issues are resolved and things are stable, the LEDs can be switched over to providing notifications.

I don't like the idea of using solid green for deep sleep, but I think if the 3G radio is on, the power used by a single LED is negligible.
[Touch Pro2, Tilt 2 Android Development] The_Font:
I have been running the 4/4 kernel now for a few days on my RHOD100/AUO without any problems. It goes nice into deep sleep and wakes up fast.

I discoverd that incomming calls do not always have sound but I am not sure if I had that issue with other kernels. I must find me an empty card so I can see what it does with a clean install.
[Touch Pro2, Tilt 2 Android Development] SLver:
Rhod 400

using 4/4 kernel

more stable (for me) and more free memory

but... the miniusb plug dont work anymore for play music, a rare noise come frome speakers when i plug the miniusb

return to previous kernel in GingerBread Bundle original thread

srry bad english D:
[Touch Pro2, Tilt 2 Android Development] Entropy512:
Do you have the phone in vibrate when incoming calls don't have sound?

I had that problem in the 4/2 kernel - all sound (incoming or outgoing) was disabled when the phone was in vibrate mode. I haven't figured out a good way to test this - I don't have a landline to dial my phone from. Outgoing calls when phone is in vibrate work fine.

It may or may not matter, but that was with a highlandsun test RIL.
[Touch Pro2, Tilt 2 Android Development] rcgators:
Happens with all kernels and is independant of RIL. I found it to be intermittent at times. This has been reported a few times.

It's one of a few sound issues within calls. The other big one to watch for is keytones or voicemail notification puts the active call on the external speaker.:eek:
[Touch Pro2, Tilt 2 Android Development] Tippfehler:
I have played with android 3 hours, nearly no problem.

With wlan I have had one time no internet data after wakeup, but this was only for 5 seconds.

(newest ril bcbbc4f)

I have not rebootet to winmo and will test this kernel during the rest of the weekend further.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Yeah, I've had all of these issues too since before I touched any of the ril code.

(bcbbc4f is no longer the newest. It locked up on me when I drove thru an area with no signal. The newest one no longer locks up.)
[Touch Pro2, Tilt 2 Android Development] gamefanatic:
Using a RHOD300 (Tilt2) 4/4/11:

I am not sure if it's the kernel causing this, but at times I find the system runs slow to a point that it actually restarts it's self to the (XDAndroid) boot screen.

Also I have been flying around this past week and found that I was having troubles pulling the phone out of Airplane mode. One time I couldn't and ended up having to restart in order fix the problem. Getting it into Airplane mode typically takes between 5-15 seconds.

Screen seems to be more responsive when returning from the off state. Still have had a few times that it wouldn't completely power on. If I swiped the screen then it would in some cases.

Noticed the desktop is in landscape mode on startup again. Hitting the Windows Key / Settings button returns it to portait as before.

Screen rotation in general is definately better than before!

Battery life is definately good. Still getting > 10 hours in basic use / standby. Playing some games for 3 hours and still having more than 60% (with 3G enabled or without).

Had one issue with the Phone not hanging up (even after 5 minutes). Though I don't think that is caused by the Kernel if I am correct?

I used the Speaker to play music (mp3's) for about an hour. This put the battery down to about 60%. If I remember correctly this is pretty close to the WinMo usage though. ;)

Definately more stable so far!
[Touch Pro2, Tilt 2 Android Development] DVA4890:
No matter what build or anything i use i seem to ALWAYS have a solid orange LED that never goes away or turns to green not just with this one but others that are older
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Solid orange? With this kernel? Even with GPS you should at the very least get a blinking green LED (indicating a wakelock...)

You have a RHOD I assume?
[Touch Pro2, Tilt 2 Android Development] The_Font:
I think my phone was on vibrate yes. I will do some tests with the sound on and see what happens. I am testing with just the 4/4 kernel without the test RIL.
[Touch Pro2, Tilt 2 Android Development] DVA4890:
I always seem to have a solid orange LED let me try this build again with a reformat of my SD card ill report back
[Touch Pro2, Tilt 2 Android Development] DVA4890:
Ok an update it is orange when i have it on blinks green fast when it is off. Is there a way to change it or disable it all together?

Is there a move to move all my contacts over also?

Thanks

Now it is going solid green orange between the two in sleep mode
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Ok, you need to stop posting in this thread and read the FAQ. Then re-read the first post in this thread. Perhaps then you'll be ready to run this test kernel.

Please, don't run this test kernel unless you know what it does and what the difference is - it doesn't do anybody any good to have you fill this thread with questions like how to move your contacts...
[Touch Pro2, Tilt 2 Android Development] muziling:
use highlandsun's ril, when disable data connection, phone crash and auto reboot.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
What does this have to do with my thread, or this test kernel...?
[Touch Pro2, Tilt 2 Android Development] muziling:
I had discuss with highlandsun today, and we think this maybe kernel problem. I use this test kernel, so I upload kernel logs and search for help.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Well those logs are empty... not sure what you want me to do with that.

Besides, if you're testing multiple things like that you'll have to triage and locate the issue. Does it happen on autobuild kernels? Do you have a problem without the RIL and on this kernel?
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Apparently there's no crash using an older kernel. These folks are really bad at providing complete information.
[Touch Pro2, Tilt 2 Android Development] Entropy512:
A spontaneous reboot clearly has kernel involvement - if indeed the issue does not happen with autobuilds, then it is relevant to this kernel.

I've had periodic (but fairly rare) spontaneous reboots with this kernel, just never reported them since I didn't have logs and couldn't find a reproducible cause, and because while some hangs and spontaneous reboots hose my contacts DB (making the phone unusable without intervention from a PC), I haven't had that problem in a while.
[Touch Pro2, Tilt 2 Android Development] Jandyman:
I used to have spontaneous reboots, they seemed to only happen though when I wasn't using highlandsuns ril. With the latest kernals here, and always happend in bad coverage area.

So for me anyway they seemed to be very much so ril related, (happend in the same conditions where SOD's used occur)
[Touch Pro2, Tilt 2 Android Development] muziling:
Logs is store in /data/system/dropbox, these are kernel's debug message. I delete yesterday before logs.

I did wrong?

I will try autobuild kernel, disable data connection cause phone reboot happended long long ago, the first time I flashed android in my rhod400, the problem did, about four or fifth months ago.

I found the xdandroid ril will kill pppd process when disable data connection, this is the reason which cause phone reboot, I don't know why kill pppd process could cause phone reboot.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Uhm, did you look at the logs you posted? They're completely empty, other than the headers. Dropbox doesn't work on these kernels, I believe WisTilt2 moved the location of ramconsole.
[Touch Pro2, Tilt 2 Android Development] muziling:
Where can I find these debug logs?

ramconsole = adb logcat?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
ramconsole != adb logcat.

Logcat is for userland logs, dmesg/klog is for kernel logs. ramconsole is useful if you have a reboot to WinMo, you can pull historical logs from it.

I have no clue where the dropbox logs come from - they're similar to ramconsole, but I don't think they're one in the same. You can think of them similarly, as dropbox logs will have historical data from past boots, and should have errors from reboots to WinMo. However, in these test kernels, dropbox logs have been borked for a while. ramconsole has as well, AFAIK, so they might be tied together somehow - I just haven't had anyone explain to me how ;).
[Touch Pro2, Tilt 2 Android Development] muziling:
Sorry for this ,where can I find ramconsole's log?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I said several times now, it's broken in this kernel. Only works in autobuild kernels...

IIRC you have to use haretconsole.
[Touch Pro2, Tilt 2 Android Development] muziling:
Here is the only guide to use haretconsole I searched.

http://forum.ppcgeeks.com/2025332-post755.html

Guide to ramconsole not found.

Auto build kernel thread not too.
[Touch Pro2, Tilt 2 Android Development] Starfox:
Seems a few changes were pushed to autobuild - are the changes from this test or should we wait for a new test build?

-- Starfox
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
What are you talking about? The autobuild service is not a thread, it's where the mainline kernels are hosted for XDAndroid...

haretconsole is needed for ramconsole, but they're not the same thing... Please, quit posting stuff in this thread that has nothing to do with this kernel. Ramconsole is borked in this kernel for the time being, you won't get anything from it!!!!!

The changes are pushed in GIT, but there's no new kernels compiled... Also, this kernel != autobuild. Usually WisTilt2 puts his kernels up to date with the autobuild, but the newest commits were born from this kernel testing (some, at least were). There's also a fix in there for BT that will allow others to use BT, and our phones to sleep again. Needs testing, I think that's why there's no new kernels yet (I need to ask about that tho).
[Touch Pro2, Tilt 2 Android Development] muziling:
Disable data connection cause phone reboot.

I use command "cat /proc/kmsg" to catch kernel logs, hope log file is useful.

And hope catch log method is right now.