yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] ksper6986:
realize

ok after extraction i see that it has been edited on 1\2\11 that is why it shows that it has the same commit sorry testing now will feed back
[Touch Pro2, Tilt 2 Android Development] MassStash:
What are you testing still on that kernel exactly?

N can see the keyboard in the dark!
[Touch Pro2, Tilt 2 Android Development] hceuterpe:
Ah man you actually tagged the modules tarball as 'dirty'? For your next kernel testing package, you should flag it as 'filthy':D:D
[Touch Pro2, Tilt 2 Android Development] neohemp:
Since updating from 1/1 kernel to 1/2 none of my apps will open and even the shell or whatever crashes eventually. Tilt 2
[Touch Pro2, Tilt 2 Android Development] neohemp:
Yep when i put that in my startup.txt it gets rid of the sd card mount problems; and yep FRX03
[Touch Pro2, Tilt 2 Android Development] kdub94:
I am using a sprint touchpro2 and this kernel is amazing. The battery life is better then i ever thought possible. It has been about 16 hours sense i unplugged the phone and it is still at 50% Battery!
[Touch Pro2, Tilt 2 Android Development] manekineko:
I'm no dev, but you could try dropping by the IRC channel where all the devs hang out and asking them about it there. More likely to get a good response than buried way in this unrelated thread. Don't mind if nobody responds right away though, most of them are pretty busy I think.
[Touch Pro2, Tilt 2 Android Development] snalbansed:
Mine will always go into error mode if when it is activated the system is using 100% resources. Either reboot or use one of the tricks to get it back in order, then try to activate wifi.

WRT the time issue, it isn't a dumb reason: Windows sets system time to local time, unix sets system time to UST or what ever it is called (GMT). If you are unfortunate to not live in the UK in the winter (or Potugal etc), then you should use TimeSyncTZ or something like that in Windows and ClockSync in Android.
[Touch Pro2, Tilt 2 Android Development] snalbansed:
Again this is associated with the system process taking all the resources. Sort that out (reboot or use the tricks), and the keyboard becomes a joy again!
[Touch Pro2, Tilt 2 Android Development] Jandyman:
Yeah modules are definatly abit off . . . Iv run these kernals on both FRX04 and neopeek builds and on neopeek builds the kernal only works properly without modules. But that's not a major problem.

Anyway is highlandsun and wistilt2 now working together on ril? And are ril problems with this kernal still to be posted here or on the other thread?

Cause iv a small problem to report :)

I booted android with this kernal toay in a shoddy coverage area, and I got the error:selected service provider (----) not available. And later in good coverage areas it still hadn't connected. Searching for network didn't work, said none available but I kno there should be at least4. Airplane on/off froze up and didn't work.

A reboot fixed this problem. So I don't know if this was a once off but its still best to report I tink :)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Please report RIL related issues in the RIL testing thread, assuming you're using that test RIL.

Please report issues with this kernel, in this thread - but please only if they pertain to changes in this kernel - IE the panel wake, the button lights, etc.
[Touch Pro2, Tilt 2 Android Development] tomdeaap:
Back after a few weeks, went straight from the 26/2 to the 30/3 kernel (tried the one from beginning of March but that gave a whole lot of freezes). Been using it for 10h, and so far so good! Sleep is very good, wake is now very consistent! Used to be really quick sometimes (faster than with this one), but very slow or had to touch at other times.

One thing I noticed is when I hang up a call (not on speakermode) the infamous buzz (described in the GSM buzz thread) suddenly pops up for a second or 2! No biggie, but strange nonetheless. Also some calls both parties can't hear anything. Haven't tried switching to speaker and back yet.
[Touch Pro2, Tilt 2 Android Development] The_Font:
I am new to the test kernels, the 3/30/11 kernel is the second one I run. I am running this kernel for a few hours now. So far no SOD and the phone goes to deep sleep in only a few seconds most of the time. Phone wakes up almost immediately from deep sleep. Open WIFI works fast, I did not have the chance to test wpa jet. I will let you know the results.

Running RHOD100,AUO with the FRX05 as posted in the threath now called FRX06 :)
[Touch Pro2, Tilt 2 Android Development] electricalve:
all the test kernel versions before this one is working smooth on my phone, from the autobuild site the bug begins with the 1276, or the first with camera support, if you really need to know the number let me know and i willtest all the kernels 1 by 1 untill i find the first with the bug

currently im running on 3/11 test version and i got 10 hour of battery(daily use), a few fail to wake, camera and everything else is working fine
[Touch Pro2, Tilt 2 Android Development] snalbansed:
Just tried this new kernel - didn't try the 30th one.

Hardware lights come on as described, except if you press the end call button. Lights seem to ignore this one.

This may or may not be related to the fact that I am running an F22 rootfs with end key mapped to home.

AUO Panel rhod100.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Expected behavior currently - evidently all the keys except end call are microp - end call is gpio. So WisTilt2 is in the process of hashing that out.

Anything else? If that's all you got, I'd say we're in great shape :p.
[Touch Pro2, Tilt 2 Android Development] Starfox:
One additional thing I noticed was that the 3/30 kernel does not seem to include a TTY. This resulted in a minor panic as the kernel dumped me to a root shell. This happened at the same time that dosfsck decided my copies of FAT was not in sync, so I thought my SD card decided to crap out on me. Only after replacing kernel+modules+rootfs+system and still seeing the tty error message, right as I was about to do a battery pull, did it continue the boot process.

Usually when any Linux system dumps you into a root prompt during boot means something horrible has gone wrong. Maybe not including was intentional (to prevent dmesg output?) but either the flying android logo screen has to come earlier or a graceful way of not showing a root prompt has to be in place.

Also, I still encountered the stuck key in 3/30. I'll try the 3/31 to see if I can repro it, one xda forum has been fsck'ed.

-- Starfox
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Oh, you mean after A N D R O I D (before the bootani) you see a prompt?

I noticed that too, but so long as the bootani always comes up, you're fine. If it just sits at the prompt, you've got a problem :p.

If you're talking about something else that I'm not grasping, let me know.

As for the stuck key issue, I noted it as well - but it seems "better" - in that it doesn't seem to happen as frequently.

Thanks for your feedback! Keep it up guys!
[Touch Pro2, Tilt 2 Android Development] PlacidFury:
Ok... Rhod210, here's my experience with latest zimages:

3/30: Used night of 3/30, had one instance of device not waking on first power button push, tried again, it worked. Otherwise was good.

3/31: Been using for a couple hours. Had one instance like already mentioned, and one totally failed wake where I had to soft-reset. :-( The green light was blinking, but device would not wake up no matter what I did.

Am using FRX06 3/25, if that helps.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Do you happen to know what it was doing when it froze on you? Or what you were last doing on it rather...

There is still the RIL issue, which is being sorted out in another thread ;).
[Touch Pro2, Tilt 2 Android Development] Entropy512:
Stuck in the blinkengreen would indicate to me a failed sleep, not a failed wake.

Note that it appears that many of our stability problems are not actually in the kernel, but in the RIL. They're fully independent, but it can sometimes be difficult to separate things symptomatically.

We probably need some new terminology, since Sleep of Death is a bit comprehensive considering it can describe multiple hanging problems.

Stuck in solid green - I would call this a proper Sleep of Death. I haven't ever seen this.

Stuck in blinkengreen - I would call this "Failed sleep" or "hung in sleep" - Every time I've seen it, it has been unrelated to kernel PM. For example, the following chain of events:

1) Hit power button to sleep when connected to wifi

2) Android likes to shut down wifi and transfer to cell data when asleep, so Android shuts down the wifi and starts a data call

3) Data call fails for whatever reason (much more likely in weak signal), Android gets a call ended notification before it gets a call established notification. Android gets confused and goes splodey splodey. Kernel is fat dumb and happy, but you can't tell because userland is hosed. highlandsun is working this issue right now in his test RIL.

Stuck in orange, orange was due to phone waking up or never being put to sleep - suspected userland hang problem IMO, no real way to tell unless the screen was on when it hung.

Screen fails to turn on after pressing power to transition from deep sleep (solid green) to on (orange) - I believe this is nearly all kernelspace and is what I consider a "failed wake"
[Touch Pro2, Tilt 2 Android Development] PlacidFury:
I walked out to my car after work, and since I hadn't tested GPS yet on FRX06, I fired up Google Maps to try it out. It worked, I went in and force-closed Maps so my battery wouldn't die while commuting, then pushed the power button on my phone, put it in the console in my car, and drove home. Once I got back into town about 30 mins later, I picked it up to use it and it was unresponsive.

GPS maybe? I don't know. But that's really all I did from the time I booted it up while leaving my desk at work and getting into town.

What is the RIL anyway? I'm getting the zImage, modules, data.img, rootfs, etc. down, but haven't heard anyone talk about the RIL until recently and I have no clue what it is/does. Still learning...
[Touch Pro2, Tilt 2 Android Development] PlacidFury:
Agreed and makes sense. Is there somewhere that I can find out more about the RIL? Haven't really seen any description of it anywhere before to know what it is, how to switch it, etc.
[Touch Pro2, Tilt 2 Android Development] rpierce99:
RIL stands for Radio Interface Library, it's basically the middle-man between android and the hardware radio, it sends AT commands to the radio hardware, and listens for responses.

On FRX06 it is located at /lib/froyo/libhtcgeneric-ril.so

On GBX0A it is located at /system/lib/libhtcgeneric-ril.so

To use a different RIL, save the file to your sd card somewhere and add a line to your froyo.user.conf in the custom commands section (you'll see some #echo lines by default) as follows:

mount --bind /sdcard/path/to/libhtcgeneric-ril.so /path/to/libs/libhtcgeneric-ril.so
[Touch Pro2, Tilt 2 Android Development] rpierce99:
The current RIL being tested (in more ways than one) can be found here: http://xdaforums.com/showthread.php?t=1009112
[Touch Pro2, Tilt 2 Android Development] slobba:
My Rhod110 still seems to be booting up into landscape mode with 03/31/11 update. I've tried rebooting a couple of times but still the same. I am usign FRX06 25/03 update.

Not necessary to have new data.img?
[Touch Pro2, Tilt 2 Android Development] PlacidFury:
Mine worked fine (in regards to the landscape/portrait issue) without a new one.
[Touch Pro2, Tilt 2 Android Development] PlacidFury:
Ah, ok... I gotcha. Thanks!
[Touch Pro2, Tilt 2 Android Development] dsramesh:
Just tried twice on Rhod 500 (Verizon Touch Pro2), it started haret and just stopped and froze up!

- Had to pull the cover off and reset.

Is there a different version I need to use for rootfs?

- using Feb. 24 image.

- using FRX05.

..Ramesh
[Touch Pro2, Tilt 2 Android Development] djcrosstunez:
Kernel 31-3 works good for now! Love the new lights!

No sods or failed wakes.

Thanks!

rhod100
[Touch Pro2, Tilt 2 Android Development] sportfisio:
delete this post, sorry
[Touch Pro2, Tilt 2 Android Development] sportfisio:
Sorry for this noob questions...How do I exactly install them? Just copy to root? Do I have to change anything in startup or somewhere?

So many thanks!
[Touch Pro2, Tilt 2 Android Development] Christiaan91:
Download the zip file in post #1. Unzip it and will get a zIamge (without extension) and a file called module(with here some number).tar.gz. Don't rename the files.

Delete you old zImage and module file on your sd card and copy the new ones.

The module file doesn't have the same name as your old module file, so make sure you delete it or else it probably wont boot
[Touch Pro2, Tilt 2 Android Development] sportfisio:
Thanks!! Already done, and Portrait on boot perfect, and love the button lights again!

Great worK!

So many thanks!
[Touch Pro2, Tilt 2 Android Development] sportfisio:
Ok, is NOT a bug, just want to share behaviour of Led light:

-when power off scren, the led goes inmediately off, and then goes green. Sometimes it blinks green-orange during this, as it was closing some process. But stays green great, and turns orange the same moment I push power button.

I think is closer to perfection! So amazing!

Thanks!
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Reboot. I've had a few failed boots, happens on the autobuild kernels.

I've noticed an uptick of the comments on failed boots with this kernel... odd. I have those failed boots, and they are very random - and very rare for me. Rebooting and trying again usually works... I've only have it happen 2 or 3 times in a row maybe once or twice in all my testing...
[Touch Pro2, Tilt 2 Android Development] wmg316:
Blinking green...not going to solid green

I hope this is relevant to this post!

I was selecting the power button to go into sleep mode. The solid green indicating deep sleep was not coming on...it was a continuous blinking green.

What I had done before this was use the google navigation app. This was the only thing I did after booting the device. First I turned on GPS using the GPS switch on the power control widget. I then started the google navigation app. When finished, I closed the google navigation app and turned off GPS using the GPS switch on the power control widget.

I then tried to put in sleep mode. This is when I only got the blinking green; I let it sit for 2 minutes and it never went solid green. I went back to Settings, Location and Security: Use GPS satellites was NOT checked. I checked the box...got out of Settings...went back into Locaton and Security settings and unchecked the box...exited settings...selected the power button to go into sleep mode and I got solid green immediately.

So I guess my question is: does the GPS switch on the Power Control widget somehow hang something up to prevent the device from going to sleep? Or was all this just coincidence?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Perhaps the power control widget doesn't work correctly...

It's interesting that the box was unchecked tho. Have you always used the power control widget? Perhaps that widget is borked, I'm not sure - I always go thru settings, loc&sec....
[Touch Pro2, Tilt 2 Android Development] dsramesh:
tried with F22 Rootfs and it finally booted but gave lot of errors about long file name and kept going really fast and I had to reset to stop after 10 minutes and windows boot partition was messed up as the windows complained it could not boot and press up volume to reset.. So had to hard reset after 3 failed reset.

..Ramesh
[Touch Pro2, Tilt 2 Android Development] Ltilt2:
Feedback on 3/31/11 Kernel

Well all works ok, I mean hard buttons light work, potrait works, but

stuck repeat letter bug is still there, orange LED death is still there. fail wake still there.

I have to run my device wit the DATA CONNECTION DISABLE or else SOD as soon as I loose data connection.

My device is a HTC TILT 2
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
What gave you lots of errors? Kernel? Some pop up in Android?

Window boot partition!?!? On your computer? Hard reset seems a little drastic. No one has had the issues you outlined, and A TON of people have downloaded the kernel and used it without issue.

Stuck letter bug is still present, but should be better at least - in the sense that it doesn't seem to happen as frequently (for me at least this is the case).

Orange LED death? That's RIL, nothing to do with kernel (at least that's the theory...) Since you say you're fine with data disabled, I'd say that is your issue. Nothing in the kernel will fix it then, try out hyc's RIL test. I hear it's pretty much done for GSM, as you guys already had all the code needed already :p.

Also, failed wake is still present - but again, for me it seems significantly better - no?
[Touch Pro2, Tilt 2 Android Development] Entropy512:
My experience is that the power control widget is a steaming turd on multiple devices.

I gave up on using it quite rapidly on my Huawei S7, didn't even bother to try it on my xdandroid.

Edit: As to hyc's RIL - there are still some potential hang issues, but many of the causes are identified and hyc is working on the solutions. I get the impression from the chatter on the dev list it may require some architectural changes to how pppd is managed for data calls.
[Touch Pro2, Tilt 2 Android Development] Raul^:
Failed wake in 31/3 for me is worser than 11/3, I had like 2-3 today and none or one for a few days on 3/11.

31/3 kernel seems to be a bit better than 30/3 but still wake-up no signal issue is present. It take some time to get proper signal and data after waking-up.

One thing that seems to be better is clock - it's working without losing time , I had perfect time from morning till late evening.
[Touch Pro2, Tilt 2 Android Development] wmg316:
LOL....I guess I won't use that "steaming turd" then! ;)
[Touch Pro2, Tilt 2 Android Development] slobba:
Yeh, it' strange. When I try GBX0A I have normal portrait mode on boot and yet I believe that release uses the standard 1276 auto-build kernel. Don't know why this one doesn't work for me.

Anyway, it's not a big issue. Quick press on the back key sets it right.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Yes, I want to eliminate /bin/pppd and get back to using /system/bin/pppd, and a couple of the other devs want pppd to be controlled from init.rc instead of being spawned directly by ril.
[Touch Pro2, Tilt 2 Android Development] dsramesh:
After haret ran, the linux started up and gave lot of errors at kernal, not pop up and kept going and going .. Long file name something.. and not corrected.

So after 10 minutes did a soft reset and then on booting up windows mobile.. it kept crashing and once I successfully booted up but application were not launching and some of them complained and some took real long time, resetting again, the windows mobile complained of unable to boot up due to corrupt files.. so finally had to do hard reset.

Now, wondering if I should try again and if so, which Rootfs?

- 2/24 rootfs or F22's rootfs?

..Ramesh
[Touch Pro2, Tilt 2 Android Development] PlacidFury:
Testing with the new RIL tonight...

And didn't work. I did the same thing as yesterday (boot Android, start Maps, close Maps, then shut off GPS, push power button), but with the new RIL. I had the same result, a "failed sleep," with blinking green light and completely unresponsive hardware.

Any ideas, anyone? I don't know where to start trying to figure it out.

Again, Rhod210, FRX06, latest RIL from the other thread, and 3/31/11 kernel from this thread... I'm stumped.
[Touch Pro2, Tilt 2 Android Development] Entropy512:
Unless you happened to be using the SD card for both Android and storage for some Windows apps, I can't figure out how this could have happened. When running from SD, Android doesn't (and can't) touch the NAND flash that Winmo resides on.

So there are two possibilities:

1) Your phone's hardware is failing

2) You have some app in Winmo that wants to use the SD card, and this app got borked by Android somehow.

Edit: Prior to attempting a hard reset, did you ever try just pulling the battery out for a few seconds and then putting it back in? I have had one or two situations where the phone acted wonky on multiple resets via the little reset hole, but was fine after a short battery pull.
[Touch Pro2, Tilt 2 Android Development] nickleby:
Yes, the repeat letter bug is still present...And when I pull out the Stylus, the phone switch to landscape mode! :(
[Touch Pro2, Tilt 2 Android Development] dsramesh:
You are right I do have some apps installed on the storage card and that could have caused it. Yes, I did try taking out the battery before hard reset.

Now after re-installing haret and other files I get this:

- Rootfs from 2/24.

I keep getting "Error reading file. Expected 4096 got 0"

Any idea how to fix it?

I have redone startup.txt many times and keep getting the same error.

..Ramesh
[Touch Pro2, Tilt 2 Android Development] wmg316:
100% of the time...if I get the 20-40 second blinking green before going to solid green sleep...if I reboot...blinking green is gone. I posted earlier that the blinking green for 20-30 seconds before sleep state occurred for me after switching to GPS using the Power Control widget...but later in the day...my blinking green for 20-30 seconds came back after texting and using tweetcaster...so I can't really tell what caused it??? But it always DID go to sleep after 20-40 seconds. (RHOD300)
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
The blinking green is just saying its in the process of shutting down, some something in the background is still running. IMO I wouldn't worry about it as long as it's still going solid green, that happens to me often, but as long as it goes solid green I'm not concerned and haven't seen negative effects. That's just one of the changes that wistilt has in the test kernel, and you can differentiate between true deep sleep, awake or going to sleep.
[Touch Pro2, Tilt 2 Android Development] ryannathans:
31st Kernel, No audio.

Have not tried headset.

On phone speaker I have no ringtone and music does not play.
[Touch Pro2, Tilt 2 Android Development] rcgators:
it's a test kernel for specific items... sleep, wake, panel. When the changes are committed it will merge with other fixes and enhancements.
[Touch Pro2, Tilt 2 Android Development] jellenl:
This kernel (3/31/11) works good for me. Button light works properly.

The only thing is that I still have landscape mode on boot.

I'm a RHOD100 user and it doesn't break my phone and I've no SoD's with this kernel.

Thanks for all the hard work! ;-)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Wow... I didn't realize that pulling out the stylus would cause that in this kernel, that's an interesting note! Thanks!

Also, new kernel guys. WisTilt2 said he found an irq set wrong with tssc - touchscreen - and basically was causing the failed wakes! Hopefully they're fixed...

It seems processes in the background can still cause havoc with screen wake, but I'm not sure what needs to be done about that...
[Touch Pro2, Tilt 2 Android Development] Jandyman:
Yeah I can confirm that too. On removing stylus it switches to landscape mode, on inserting the stylus it switched back to portrait.

On the kernal from earlier today I got what seemed lik a SOD with a blinking green light o.o no harware/kb lights, and totally unresponsive to any type of touch or button press. I was in a bad coverage zone so that might have been the problem (I am using the test RIL)

Also downloded new kernal, will restart, test and report :)
[Touch Pro2, Tilt 2 Android Development] AkumaX:
Thread title intriguing - trying out asap
[Touch Pro2, Tilt 2 Android Development] rodrilobo02:
Same for me, have a RHOD300 using new 4/2 kernel.