yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] Erbid:
Tried under GBX0A. Radio 4.49.25.95 No overclocking (528MHz)

(would try 4.49.25.57, but see no link to my issues, also curious about RIL, but that may be in this kernel and modules)

a) Left modules name as it was, with "dirty" in the filename.

b) Deleted data.img.

c) booted 3 times (see below)

1st boot, recreated data.img and seemed to lockup once the screen went black. I was not watching, as I was going to give it 5 minutes. I did see the gui come up and it "seemed happy" until later when I noticed it seemed frozen.

In haret's startup.txt, I have the cdma arguments =0 and pm.sleepmode=2.

I patiently fiddled trying to wake it up. Pressed each putton and scribbled gently on the screen. IIRC, the "sleep mode" light was yellow, and the screen never flickered. RESET.

2nd boot I wated a few minutes and attempted to enable data. Typically, I just add the password to ATT under the APN settings. No data after a minute or two, so a graceful shutdown. It felt responsive and fluid. Normal shutdown.

3rd boot, data was working, browser pulled down "google". I attempted to enter a userid and password under sync settings, but the gui locked up as it started to scroll the network settings options.

Ready put old kernel back, but wonder what I can retrieve to help? I have had "droid explorer" working (but have not tried this kernel, not running long enough yet).

Let me know what to grab if anything is useful. I don't see an update that WisTilt2 has found wht he needs to move forward. Watching 1st post.

Erbid
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I disable and re-enable data all the time. Works flawlessly, issue is not with this kernel. I just tried again, no problem.

What RIL are you using? Do you have the ril2 that uses the rootfs enhancements as well? IIRC it worked before I did that as well, but I could be wrong.

Please test on FRX06. Gingerbread is not so stable yet ;).
[Touch Pro2, Tilt 2 Android Development] highlandsun:
I disagree. Any time you get a kernel panic like that, with a message like

you have a legitimate kernel issue. No matter what is going on in userland you should never be able to cause a kernel NULL pointer dereference. WisTilt2 needs to be made aware of this.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I'm not saying the issue he's listing is RIL related, I'm just saying I can't recreate it... I don't think there is an issue with the kernel, I think there's some issue with his setup - what it is, I have no clue. I just know on my RHOD400 I can disable and re-enable data no problems.
[Touch Pro2, Tilt 2 Android Development] JBaxendale:
Arrrghhh: I can switch data on and off (enable, re-enable) without a problem, but I do have the following problem which seems as though it might be related.

When I enable portable wi-fi hotspot in settings, all is well. I can connect another computer without problem. That said, if I want to dis-enable the wi-fi hotspot I am unable to -- and most often a reboot into android will occur. So, what I do is use the data enable/re-enable capability (which is acceptable); except of course that I can't receive email on my phone with data dis-enabled.

I believe others have reported this (sporadically) but I am not aware of any conclusive fix. Is this generally known, are others able to enable/dis-enable wi-fi hotspot without problem to your knowledge, and is it reasonable to expect a fix for this in the future mists of time? I tried dis-enabling data first, and then dis-enabling the wi-fi hotspot function, to see if that sequencing would work, but it did not.

I can live with this, but thought I'd ask you about it as the enable/dis-enable/re-enable data issue was being discussed just now in this thread (apologize if I should have posted this elsewhere). I have had this problem with all the other kernels (and with FRX03 through 06) so I suppose it isn't specifically related to this kernel; but then again I suppose it isn't RIL or Rootfs related either.

I am on a Rhod 300 (Tilt2) using FRX06, WisTilt2's 4/4 kernel, highlsndsun's latest RIL, and F22's latest Rootfs.

BTW, with this set-up everything seems very stable just now, excellent battery life, able to go into solid green state in but 2 or three seconds. I'm happy -- but would like to be able to turn wi-fi hotspot on and off without having to go through the whole reboot process. Thanks for all your dedication and hard work.

James
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Interesting, I didn't realize that if you disable data that portable hotspot works correctly. That's an interesting tip... I'll pass it on, thanks!

Oh, and in case you were wondering the built-in wifi-tethering app does this. It's buggy, we're working on a fix. With this information we might be able to get closer to fixing it.

With that said, have you tried any of the other wifi tethering apps? XDAndroid wifi tether works pretty well, and AFAIK it doesn't blow up when you disable it ;).
[Touch Pro2, Tilt 2 Android Development] JBaxendale:
Thanks Arrrghhh:

I may have worded this in-artfully when I said "I tried dis-enabling data first, and then dis-enabling the wi-fi hotspot function, to see if that sequencing would work, but it did not". I think you may have misunderstood me -- disabling data first, then disabling the wi-fi hotspot function DOES NOT work as a solution.

But, I do thank you for the tip on XDAndroid wifi tether as a fix. I'll try that. Keep up the great work.

James
[Touch Pro2, Tilt 2 Android Development] Starfox:
Right now there is no PM code for "turning off" the Broadcom WiFi short of a restart. I also use the tethering capability (devs note - there is a bug turning on hotspot - see below) and resort to restart - Gen.Y to "turn off" tethering.

Once you turn on WiFi, you need to go into the HotSpot setting (AP name and key) and click OK in order for the radio to start broadcasting. It does not matter if the settings are the same or different, just checking the Wireless Tether box isn't enough.

-- Starfox
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Ah, I did misunderstand you. I'll play around with it, I don't think I've even looked at what the logs spit out under this condition. Would be nice to use the built-in tether app - not only is it built-in, but it's the only one to my knowledge that throws up an actual AP instead of an ad-hoc network.
[Touch Pro2, Tilt 2 Android Development] muziling:
I use highlandsun's newest ril(not ril2, I also try it, problem still), when I enabled data ,about 30 seconds later, disable , then phone reboot.

This problem I have ,since the first time I use android on my rhod400, Both stock ril and test ril had this problem.

follow is I post at highlandsun's thread.

http://xdaforums.com/showpost.php?p=12807248&postcount=247

Found an patch which relate to ldisc.c, but kernel version not same with our kernel.

http://www.kernel.org/pub/linux/ker...ldisc-user-count-into-a-proper-refcount.patch

http://kerneltrap.org/mailarchive/git-commits-head/2009/8/5/670/thread
[Touch Pro2, Tilt 2 Android Development] JBaxendale:
Arrrghhh, again thanks for suggesting XDAndroid wifi tether.

I just tried it, and realize that I had used this previously. There are limitations in this, for me, though. Notably, the inability to use even the WEP wifi encryption, or for that matter, the "access-control" function. So, this leaves one very vulnerable in my opinion. Also, while my computer can "see", and connect to, the ad-hoc network that XDAndroid wifi tether creates, other devices that require an actual Access Point can't.

The nice thing about the built-in tether application not only is the superior encryption available (versus really no encryption at all) but also having the visible AP, as you correctly point out.

I think this is why I "put-up" with having to reboot my phone and reload FRX06 every time I want to turn off the built in tethering application, as opposed to using XDAndroid wifi tether which I can turn off and on but which makes me feel more vulnerable.

With all of that said it would be great if a) you could look into whether a fix for the enable/disable problem with the native application is viable, and or b) someone could point me toward a non-native wifi tether application that readily provides decent encryption (equivalent to the native built in wifi tethering capability) and which "throws up" (to use your technical terminology!) an actual AP. I suspect a solution to "a)" above, might be difficult to come by; and that there may be no readily available application that addresses what I'd like to have in a wireless tethering capability, as expressed in "b)" above, other than the problematic (for us) native application of Froyo 2.2.

Finally, I hope I haven't diverted attention (though I fear I have) from the real purpose of this thread which is to test the various WisTilt2 Kernels. If I have done so, I apologize.

James
[Touch Pro2, Tilt 2 Android Development] Starfox:
The AP Mode for tether uses a different firmware for the WiFi chip called SoftAP. I'd guess that you'd run into the same sort of issues with a software that uses IBSS.

-- Starfox
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
New kernel guys. SCBS is now integrated ;).
[Touch Pro2, Tilt 2 Android Development] Tippfehler:
SCBS?

Can you explain, for what scbs is needed?
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
Battery meter system from Jonpry http://forum.ppcgeeks.com/android-t...sting-scbs-improved-battery-meter-system.html
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
fish answered, but did you even bother reading?!? Edit - I guess I need to mention with all the updates to re-read the first post for details...

Works fine for me. I am not a fan of Winrar, have you heard of 7zip? Worlds ahead of Winrar IMHO and it's free (in every sense of the word).
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
I don't know, personally when I see a post stating new kernel I head to the first page to check it what the changes are ;)

And I unzipped it with 7zip no issues, running great now.
[Touch Pro2, Tilt 2 Android Development] Tippfehler:
Thanks, I have tried to find informations about scbs in the first posting and google.

I think, the new rootfs will break my homekey.

Unpacking the file was no problem with 7zip.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
What do you mean rootfs will break your homekey?

If you're using a rootfs from F22, then yes you will lose the special features that his rootfs provides. Hopefully we'll get it all committed soon - lots of stuff in testing, and assuming it goes well there will be a big push to get it all to mainline so everyone can enjoy ;).
[Touch Pro2, Tilt 2 Android Development] coder12:
I already enjoy it! arrrghhh! every time I read your name I feel like an... arrrghhh pirate matey! haha
[Touch Pro2, Tilt 2 Android Development] Jandyman:
Do we need to change pm sleep mode to 1 as stated in the ppc scbs thread on ppcgeeks?

Or on this kernal do we continue using pm sleep mode=2 as requested before by wistilt2?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Uhm... you should always be in sleep_mode=1. WisTilt2 asked us all to set it to 1 on his previous test kernels, I never said to set it to 2.
[Touch Pro2, Tilt 2 Android Development] Raul^:
Yes , it is FRX03. I wouldn't write that If i wasn't sure what i'm using.
[Touch Pro2, Tilt 2 Android Development] haniel73:
Problem Vibracall

Hello, i have been testing the new kernel 1/2/11 on HTC Touch Pro2 rhod100 and it seems that everything is going ok. The only problem that i am having is that the vibracall does not work.

But in the other version 01245, the vibracall was working, and also the speakerphone has a laud sound.

In the version 01245 the only problem that i found was that the keyboard backlight did not work.

It seems strange to see that as we go on with the new versions not everything is working, infact if one thing was working with the oldest version if i use a new version it does not work anymore, for example the vibracall.

One last thing, i have noticed that at each reboot in the root of the SD card are created these files FSCK0000, FSCK0001, FSCK0002...

Is this normal?
[Touch Pro2, Tilt 2 Android Development] JBS2:
I'm experiencing some problems to wake my phone up. To get the screen on I have to press the home or power buttons a few times or slide the keyboard out. No SOD, because the screen gets on after a few tries.

An known issue with 01/02/2001 kernel?
[Touch Pro2, Tilt 2 Android Development] snalbansed:
Did you read the first post on this thread? If not, please do, and where you see the word 'panel', substitute the word 'screen'. Then, if that doesn't describe your problem, let the thread know.
[Touch Pro2, Tilt 2 Android Development] JBS2:
I did a few days ago but didn't remember that part. I'm sorry :rolleyes:

Touching the screen solves the problem :)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Ok, I have no clue why you can't boot. You're using the rootfs from 11/15? Do you have any other modifications? You're literally the only one with this problem, and you have the same piece of hardware as I do...

Vibrate sometimes breaks, not sure why. Doesn't seem directly related to the kernel, I think it's a system image (aka 'Userland') bug.

Reboot usually fixes it. The FSCK files are in every build as well. Have you never used Android before? Let's just stick to reporting things that are different with this kernel people! I know WEP doesn't work, that's status quo. I know FSCK files get created at the root of the SD, that's status quo!!!!

You can get rid of the fsck files by putting

rm -f /sdcard/*.rec

in the "CustomCommands" section of your froyo.user.conf.

Seriously folks, let's focus on what this kernel fixes - speakerphone mic (in-call) and keyboard backlight! Keep it simple and focused, that way I can actually give useful feedback to WisTilt2. Otherwise I won't be able to give him anything useful, which means there's no real point in releasing these kernels... So c'mon guys, help me out here!
[Touch Pro2, Tilt 2 Android Development] kwoodyusa:
SPK works good. BL works great! I noticed some people reporting GPS having issues. First, second, and third try no issues. Next day GPS would not connect in the Navigation program. I used GPS Test and got lock in 1 minute. Went back to Navigation got lock right away. Still working on battery life. Speed does seem faster but not sure if its just a placebo affect.

Not sure if this is addressed in this build but when dialing DTMF while on a call it will open the speaker. Example checking VM and pressing 7 to delete will turn on speaker. To shut if off you have to turn on speaker phone and then turn it off again. Call will then return to normal. I tested on other kernels and found the same problem.
[Touch Pro2, Tilt 2 Android Development] jchutch2:
Everything for me seems to be working OK. Except for the hands free speaker being fuzzy during a call, but I believe that is outside the scope of this kernel testing. Like was previous commented, it would be nice to be able to have a little control over the bl duration period, but that's far from being anything I really care about. More like an, "it would be awesome if..." type thing.

Even my wife notices a difference. You have no idea how hard it's been to get my wife on board with Android. But I did find a good free cribbage game that she likes better than anything for WinMo, so...small victories... :)

Awesome work guys. I don't say thank you often enough, but I certainly am very excited and grateful for the effort everyone puts into this project...
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Interesting, never noticed this. I'll ask WisTilt2, while he's mucking around with speakerphone stuff he might be able to look at this and squash it sooner rather than later. Thanks!
[Touch Pro2, Tilt 2 Android Development] Raul^:
Yes, rootfs is from 15/11, and it boots and works for one minute ... and then sudely stops responding at all.

I have kernel and modules from old FRX03 package and it mostly works perfect (not sure about phone, I had some problems , I will write about it if I manage to repeat that).

You are probably using CDMA and not GSM.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
It is a CDMA phone, but that shouldn't make any difference whatsoever. You don't seem willing to troubleshoot, and you're the only one experiencing the issue... so I'm not too concerned to be honest.
[Touch Pro2, Tilt 2 Android Development] Raul^:
Why do you think i'm not willing? I do appreciate what you are doing, just thought that you want feedback. I tried to install adb, but have some problems. When i conect phone to usb it seems that drivers dont install (dont recognize my phone).

Kind regards,

Raul
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Assuming you're using Windows, Droid Explorer makes ADB a breeze (usually).

I also assumed you were willing from the scant posts you made - typically people who are willing to troubleshoot do a ton on their own, and when they've exhausted all avenues they ask for help. From your post, I can't tell if you've done anything to troubleshoot other than reverting the kernel.
[Touch Pro2, Tilt 2 Android Development] randomblame:
argh - have you committed these changes to git yet? I was about to compile a new kernel for myself and wanted to include your commits.

doesn't look like you did, can I get a .diff?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Unfortunately this code is not available yet... WisTilt2 will commit it when he cleans it up and it passes the legendary phh-test.
[Touch Pro2, Tilt 2 Android Development] randomblame:
boo ;D
[Touch Pro2, Tilt 2 Android Development] JBS2:
Still using the 1/2/2011 kernel and it is working very well. One freeze a couple of hours ago after making a call. Receiving a call didn't freeze my rhod100 yet :)
[Touch Pro2, Tilt 2 Android Development] snalbansed:
Feedback on testing kernel rhod100_uk

Hi

I have installed the kernel I downloaded today from the first post in this thread.

I have a rhod100_uk that was previously having problems with the newer kernels with the sleep of death, and so I had held back for a while!

So far:

# Sleep wake works well

# System seems responsive

# Keyboard back light is a God send! Works as described

# Speaker phone has the buzz that others have mentioned, but otherwise works for incoming voice - I have only tried it with voicemail so far so can't comment further on the microphone yet.

# I tried using key tones whilst in call (selecting an option in voicemail), and it worked as it should, so I can't replicate the issue with switching to speakerphone.

# Too early for battery consumption information

Arrrghhh/F22/Any other expert - can you tell me if using this kernel, when the led indicates sleep mode by turning green, the panel is switched off to the extent that we would expect problem rhod100 panels to not get turned on again? And if so, has this been fixed as mine does turn back on (so far)?

Thanks guys (and WisTilt2 if he doesn't read these threads) for all your hard work. Much appreciated.
[Touch Pro2, Tilt 2 Android Development] gnnash:
Not sure if I should post this here or in jonners59's topic, but I am experiencing the same no service issue that he is, using the 11-2 test kernel. This has happened to me three times now, although mine comes back with a restart.

My phone says no service, and I can't make calls. Two of the three times, I was in a call when it ended and the phone said no service until I restarted. The other time was last night, sometime when I was sleeping.

Not sure if it is related to this kernel or not, but thought you should know in case
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I tried this and could not replicate it as well.

Thanks for the report! Glad it's actually working for you. The LED should be back to "normal" (as in, green = sleep, orange = wake). WisTilt2 thought he'd have to do a bunch of work to get the RHOD100 guys working, but it appears to be working for you as well - which is great news!

Unfortunately this happens on all kernels. It's erratic, do you feel it's occurring more frequently in this kernel...? I've booted before, and just had the radio completely disable itself. It's rare for me, but it does happen.
[Touch Pro2, Tilt 2 Android Development] Jandyman:
Just checked my startup and I havnt put in the cdmline so its at whatever the default it (1)

Lol oh rit, well I always had it at what was said here . . . . . I was sure that at the start of the project there was a stage when sleep_mode=1 caused instability? Hah well sry for the mixup :P
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Several months ago (4 maybe?) if you overclocked, sleep_mode=1 was bad. I don't think it was ever bad if you weren't OC'd.
[Touch Pro2, Tilt 2 Android Development] Tippfehler:
Yes, that´s, what I mean.

Excuse my bad english, I am still learning.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Bah, your English is fine. I just wanted to make sure I was clear - you just need to be more thorough in your descriptions ;).
[Touch Pro2, Tilt 2 Android Development] ryannathans:
is it clear if I can combine changes to this rootfs with F22's rootfs?

Really need the keys...

thanks ;)
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
You may want to ask jonpry in his thread where he posted the rootfs. Theres a link a few posts back.
[Touch Pro2, Tilt 2 Android Development] adamsmiley:
You said nothing else change since the 4/4 Kernel what about updates to the 4/15 on (01259)? Do you know if it has the SCBS added?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Uhm... what? Do you mean autobuild kernels? If you do, then no - SCBS is not mainline yet.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
You're more than welcome to try. Just don't repost any horrible hybrids, thanks ;).
[Touch Pro2, Tilt 2 Android Development] toadlife:
Kernel Panic/Reboot tonight. It happened as I ended a call. IIRC I've gotten spontaneous reboots while ending calls before recently.

I've been keeping kmsg logs, so here they are....

http://dl.dropbox.com/u/25754012/debuglogs_kernel_panic.tar.gz
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Hrm. I'll see what WisTilt2 has to say. Seems like this famous bug happened tho:

END CALL triggered without being in a call!

Like it tried to end the call after the call was already ended? lol, not sure. Interesting one for sure.

Question for you, how do you get logs like this? Do you just boot Android and kick off the logs right away thru terminal emulator? Cuz I haven't been able to capture logs like this in a looong time!
[Touch Pro2, Tilt 2 Android Development] toadlife:
I use Gscript lite and launch this script soon as I can after I boot up:

kill -9 $(pgrep logcat)
kill -9 $(pgrep cat)
if [ -f /sdcard/debuglogs_logcat_time_radio.txt ]; then
tar -cz -f /sdcard/lastdebuglogs.tar.gz /sdcard/debuglogs_*.txt
fi
cat /proc/kmsg>/sdcard/debuglogs_kmsg.txt &
logcat -v time >/sdcard/debuglogs_logcat_time.txt &
logcat -v time -b radio>/sdcard/debuglogs_logcat_time_radio.txt &
echo Finished!

After closing gscript it tends to hang in the background taking up 80% of the CPU for no reason so I have to kill it using the terminal.
[Touch Pro2, Tilt 2 Android Development] toadlife:
My wife probably hung up before I hit end call. She's got a fast trigger finger.
[Touch Pro2, Tilt 2 Android Development] BigOnes69:
4-15 Kernel had to go back to Wistilts previous kernel updated to this new one and could not get WIFI to work. FRX06 rhodium 400. It seemed to be a little better on the battery. Tried every trick I know to get Wifi tethering to work but could not. Once I reverted back to the 4/1 Kernel 1276 and the old rootfs file it came back fine. Thought I would post here for informational purpose. I dont have time to go through another thread from another website searching for answers.