yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] Tippfehler:
Wistilt2-kernel:

The display and standby seems to be o.k., but this version from your #1 is very slow.

---Edit---

With an new SDCard and clean install it is faster now.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
What's slow...? Kernel really has little to do with overall speed.

However, if you do want to discuss something in particular with that kernel, that discussion would best take place in that thread - not this thread ;). I was merely suggesting things to try to see if it was any better!
[Touch Pro2, Tilt 2 Android Development] Tippfehler:
If I touch the display, everything is very slow, 10 times slower compared with other kernels and b4home is not working. I will boot into android an test a second time.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Please, if you're on a WisTilt2 testing kernel and you feel the issues are related to that kernel, post in that thread. This talk will quickly derail this thread!
[Touch Pro2, Tilt 2 Android Development] majkeljj:
on my RAPH100 everything starts from kernel 1232! I test every kernels to 1276.
[Touch Pro2, Tilt 2 Android Development] Raul^:
Try as fast as possible set you mobile operator in APN settings, it will then freeze, but on the next reboot everything should be fine.
[Touch Pro2, Tilt 2 Android Development] majkeljj:
another method found, i enter phone to airplane mode asap and after next rebot also everything is ok.
[Touch Pro2, Tilt 2 Android Development] billerbong:
Wifi reboots

Hey I do not know if anyone else has this issue I did not find anything in the forums beside a couple of older posts so here it goes. When I enable WIFI on my Rhod500 the system seems to come up with an error just after boot. If I wait about 20 or 30 minutes the wifi will enable and work good. But when I do enable the wifi the system will crash and reboot back into windows about 2 to 4 hours after I enabled the wifi.

Once again I have a Rhod500 running the latest Glemsom kernel build and modules on FRX05. I did modify my system so that my camera works as well but I do not think this has any issues with the MIFI. Let me know if there are any files you want or logs. Also if I leave the system just using the 3G network the system remains running for days. Let me know if I can be of any help.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Hrm, 20 to 30 minutes seems like a long time to wait after boot for wifi to come up. If you said 5 minutes, I might be able to write that off, but not 20-30 mins...

What do you mean "modify my system so that my camera works" - if you're running FRX05 with the latest kernel, there should be nothing you need to add/change for cam...

Has wifi worked fine before? Is this a new issue for you? I don't use wifi much, so the 2 to 4 hour thing is something I haven't tested TBH. Flipping wifi on when it first boots I don't think I've tried either.

Either way, logs are going to be needed. I'd like to see a dmesg and logcat from trying to flip wifi on from boot, and some logs from /data/system/dropbox after a reboot to WinMo - autobuild kernels should still have klog enabled no problem, just look for the SYSTEM_LAST_KLOG files. The most recent one is your 'last boot' basically. So recreate the wifi issue, should reboot to WinMo - then boot back to Android, and pull the logs from dropbox and post the last_kmsg.
[Touch Pro2, Tilt 2 Android Development] codedesignr:
Bluetooth Working?

There's a new kernel today from the autobuild service. Not exactly sure what's new, but there are comments about bluetooth and backlight for the front keys.
[Touch Pro2, Tilt 2 Android Development] jordanthompson:
Please note I am quoting here... ;)

is pdawg17 mistaken?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
No, you're misreading what he's saying. He is saying you have to do the call vm trick in WinMo while booting Android to get the speakerphone mic working during a phone call...
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Maybe a stupid question, but why is this linux-msm fork still using 2.6.27 as a base? The kernels for the HTC G1 are using 2.6.35 already, 2.6.27 is pretty ancient by now. Is there any possibility that some new drivers are present in 2.6.35 that would address the bluetooth and camera issues?

The G1 uses the Qualcomm MSM7201A, TouchPro2 uses MSM7200A, and from what I've read these parts are pretty much the same.

And just to repeat a question I posted in the other thread that wasn't answered:

Has anybody talked to this David Thornton guy about getting the bluetooth working?

http://www.spinics.net/lists/linux-bluetooth/msg01645.html
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
There's a guy who is running the entire 35 kernel on his kovsky (AFAIK). I'm sure the devs would love to get up to .35, but that'll mean a lot of work. Basically rewriting a lot of what had to be done on .27...

No clue about your BT question. Don't think .35 will help us with the camera whatsoever tho...
[Touch Pro2, Tilt 2 Android Development] F22:
The parts are very similar, but the devil is in the details that are different. The proprietary amss firmware that varies from handset to handset is one such example. There is much that needs to be reverse-engineered the hard way through pain-staking effort due to the lack of available documentation on those subtle but key differences. For the G1 that really wasn't necessary since all the information needed for the device was already available in the source code.
[Touch Pro2, Tilt 2 Android Development] jordanthompson:
Not to beat a dead horse:o, but since I was totally confused I had to try it for myself... Regardless of whether you do the vm trick or not, on my phone, running the release that started this thread:

1) the speaker mic does

not

work during a phone call

2) the speaker mic

does

work for voice commands.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Thanks, I hadn't considered the firmware differences. So even though Broadcom has provided a BCM4329/4325 driver in the Android source tree, there's still no guarantees that it would work with the BCM4325 in these phones? Kinda makes all their talk about unified drivers seem a bit empty...
[Touch Pro2, Tilt 2 Android Development] F22:
Dec. 17th Kernel (1233)

New Kernel. See 1st post for commit message & download info. This kernel is known to break Diamond/Raphael. A patch to fix them is being written.
[Touch Pro2, Tilt 2 Android Development] F22:
New Kernel (1235) - Dec. 17, 2010

Another new kernel today. Commit 1234, which is included, fixes the problems caused for Diam/Raph by commit 1233. See 1st post for commit messages and download links.
[Touch Pro2, Tilt 2 Android Development] ice.bogdan:
The new kernel feels fast and stable. The only issue seems to be the wifi, it doesnt start on my topaz, it used to work on the glemsom builds. Great work guys anyway. :cool:
[Touch Pro2, Tilt 2 Android Development] vnes1984:
Would love to see a change log....RHOD400 running FRX03 with 12/17 kernal. smooth sail'n. Very responsive with no OC.
[Touch Pro2, Tilt 2 Android Development] pdawg17:
On my Rhod400 on Sprint 12/17 is running very smoothly...when running Homerun Battle 3d there is some flickering on the bottom third of the screen...this did not occur with the Dec 4 kernel (did not try Dec 11)...
[Touch Pro2, Tilt 2 Android Development] thomas d:
hey can someone post the zimage an a zip file because when i try to change the name to just zimage it says that i am actually changing the whole file or is there another way to do this?
[Touch Pro2, Tilt 2 Android Development] F22:
New Kernel (1237) - Dec. 17, 2010

Third new kernel today. See 1st post for commit messages and download info.
[Touch Pro2, Tilt 2 Android Development] binht611:
i update my rhod500 with 1233, 1235 kernel and after 1-2 outgoing call, it can't recieve incomming call!!! Can you help me to fix it, i user rhod500, frx03, 11-08 roof!!
[Touch Pro2, Tilt 2 Android Development] binht611:
really fast :D:D:D, i will try 1237, thanks for your update:):):) !!!
[Touch Pro2, Tilt 2 Android Development] muziling:
I use version gb7033df, when turn off data enabled(network->data enabled), the phone auto reboot.

my phone is rhod400 (touch pro2 sprint version)
[Touch Pro2, Tilt 2 Android Development] alexdoux25:
Doesn't work Wi-Fi on Topa 100 constantly using all last kernels.
[Touch Pro2, Tilt 2 Android Development] thorfr:
same for me with topaz no wifi :(
[Touch Pro2, Tilt 2 Android Development] rpierce99:
The commits that have gone in recently are for the led backlight on the front keys of Rhod, as well as the kernel side of the bluetooth fix, bluetooth will not work yet as the userland side is still not ready. I don't know enough about the lights fix to know if it works without userland support or not.
[Touch Pro2, Tilt 2 Android Development] Ltilt2:
New Kernel 184049 from the Autobuild

I'm using the above kernel from the AutoBuild site. I get green/orange light blinking. Does anyone know if the phone is actually asleep or is it trying to go to sleep.

Anyone else experiencing this?
[Touch Pro2, Tilt 2 Android Development] jordanthompson:
Works for me

This combination works extremely well for me. Light works as advertised and the phone does not get hot, even with my overclocked settings. I am getting longer life out of the battery as well. I have not had a crash in the few days I've used it and it seems more responsive.

On the down-side, although the camera "works" it won't take pictures and I cannot edit the settings (crashes whenever I touch a button or the screen.)
[Touch Pro2, Tilt 2 Android Development] DmK75:
I wish to compile kernel from sources for himself.

But without annoying leds debugging, please say me where i can disable this?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
You'll have to actually modify the kernel and compile it yourself - if you're up to that task, I think you can start taking a peek thru the commits no?

The LED will not change until we hammer out the issues with sleep - perhaps someone can look at making the LED effects app work on RHOD like it does for RAPH/DIAM.
[Touch Pro2, Tilt 2 Android Development] Entropy512:
It might be beneficial it is an option for those of us who aren't experiencing SoDs, or whose devices are experiencing non-PM related hangs? (I'm inclined to believe that all of my stability issues are in the RIL at this point, since I've had screen-on-while-charging hangs in the same situations that usually caused me to hang with the screen off.)

I really don't see the benefit of the LEDs for debugging at this point on my device, or at least what the point of having a deep sleep indicator other than "LED OFF" is. With the last two test kernels I have never had a green-light hang - always orange-light or blinkengreen. So the ability to differentiate between deep sleep and fully powered off isn't really useful any more.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
I agree with Entropy512...
[Touch Pro2, Tilt 2 Android Development] majkeljj:
in raph100 is only one white light, sleep or deep sleep doesn't matter, light blink the same.
[Touch Pro2, Tilt 2 Android Development] manekineko:
Yeah, for what it's worth, I agree as well. At the least, it'd be nice to change deep sleep to LED off. I like the blinkengreen for trying to sleep, as that provides useful information, but the solid green might as well be solid off (or better yet, notifications!).
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yes, this is status quo for the RAPH. LED Effects works great for that device, if you wish to change it.

I still think we need some sort of indicator for sleep, until sleep is completely fixed.

To be honest the best option would be to fix LED Effects for RHOD. That way the user can decide and customize how the LED is handled.
[Touch Pro2, Tilt 2 Android Development] toadlife:
Yeah, I got the same behavior. The phone never actually goes to sleep. On that kerfnel my battery went from 100% to 3% in 7 hours overnight. I switch back to the 3/11 wistilt2 kernel.
[Touch Pro2, Tilt 2 Android Development] eu0741924381:
Kernels

Ok, i have a rhod100 UK .... my idea is to merge 2 kernels but i don't know how to do that... i use GBX0A and the kernel that comes with it gives me great battery life about 14h but gives me a lot of failed awakes also...

Latest WisTilt2's 2 kernel resolves the failed awakes but has poor battery life...

So my request... Can someone merge those 2?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Hell no.

WisTilt2's test kernels are meant for testing - they're not meant for anything else!

His code will get committed to mainline once it's been tested and cleaned up, which he is constantly doing. So be patient, that's the only way the kernels get merged.... You can't just take two kernels and mix them and expect it to work, the code needs to be carefully integrated...
[Touch Pro2, Tilt 2 Android Development] eu0741924381:
I know that and i didn't mean merge them now! just saying what works for me in both of them and what combination i would like to see:)

update: latest system.ext2 for xdandroid's gingerbread seems to solve a lot of the failed awakes ( not all of them )
[Touch Pro2, Tilt 2 Android Development] QuentinX5:
Wait a minute... So does that explain why using his kernels sometimes causes my phone to start having some of the apps (Messaging, Phone, Installed Apps, etc.) to crash and do a restart on the data.img?

Or am I just reading you wrong?

Also, how stable are WisTilt2's kernels as compared to the ones provided in the FRX06 and Gingerbread builds?
[Touch Pro2, Tilt 2 Android Development] Entropy512:
wistilt2's kernels should give you great battery life, unless something in userland is preventing sleep.

If you have constant blinkengreen, do a dmesg and post it here to identify what's wakelocking you.

Common known culprits, no known fix right now:

1) Having GPS enabled. Disable it to permit sleep.

2) Facebook app tends to wakelock me a lot. Kill it with a task killer.
[Touch Pro2, Tilt 2 Android Development] R^7Z:
I think you may be missing the point. WisTilt2's kernels are NOT meant to be stable just as a means for testing, if I'm not mistaken. Which I could very well be but you could wait for the thread OP or the poster you replied to answer... :D
[Touch Pro2, Tilt 2 Android Development] QuentinX5:
I know they are not meant to be stable and are for testing. I was asking if the kernels that come with FRX06 and Gingerbread we're WisTilt2's kernels or if they were made by someone else.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
If you actually read the OP in my Froyo and GB threads, you'll see which kernel I use.

Autobuild, is the short answer. I do not roll any testing kernels into builds, and there should never be a testing kernel rolled into a build. tiad8 was doing it with jb's kernels, without his permission.
[Touch Pro2, Tilt 2 Android Development] QuentinX5:
*Scratches head*

I did read it, I just assumed the autobuild was the same as WisTilt2's kernels. Thanks for clearing that up :P
[Touch Pro2, Tilt 2 Android Development] R^7Z:
The autobuild site is maintained by Glemsom tmk and wiztilt2 just so happens to be a kernel dev (if i'm not mistaken, again) that is kind enough to allow us to test with his kernels.

It's always good to seek clarification/clarity... :D ;)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
^^ that's pretty much it...

Sorry if that wasn't previously clear, I thought I was pretty clear in my build threads which kernels I use and where they come from (I provide links to the autobuild, etc).

Probably need to do more work on the wiki. Damn that thing :p.
[Touch Pro2, Tilt 2 Android Development] muziling:
Which command can I dump kernel's debug messages.

If my post is stuff, sorry for this and please ignore me.
[Touch Pro2, Tilt 2 Android Development] R^7Z:
This is defined & answered in the FAQs ( as ADB, I believe :o ), as far as XDAndroid builds are concerned. Don't know about any others such as neopeek and/or variant's... :)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
dmesg, didn't I mention that in the other thread?
[Touch Pro2, Tilt 2 Android Development] muziling:
dmesg only got logs after boots.

Last boot's log you said can obtain it from ramconsole.

ramconsole logs need to use an tool named haretconsole.

My question is which haretconsole command can get last boot kernel logs?

If not, maybe only method is "dmesg > /sdcard/dmesg.txt &", when system crash, read dmsesg.txt and find reason.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Correct. I don't know exactly where the last boot's logs come from (the ones in /data/system/dropbox). They seem like they would be the same from ramconsole, but I'm told that's not possible. I haven't had anyone describe where they come from.

/proc/kmsg = dmesg

I don't know if the method you mention will work - it might, it can't hurt I guess. I would think you would want two >> so it appends instead of overwrites.

As for ramconsole, I think you put this in haretconsole:

pwf dm 0x8e0000 0x20000

Assuming you're running kernels from the autobuild service, ramconsole should work just fine.
[Touch Pro2, Tilt 2 Android Development] muziling:
Disable data connection cause phone reboot, same at autobuild kernel.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I fear there's something wrong with your phone, or with your particular setup. I can't recreate this at all, and I've spoken to several others - they can't recreate it either, GSM CDMA, all works...
[Touch Pro2, Tilt 2 Android Development] muziling:
I do an fresh install again.

1. Full fomat my SD Card with HPUSBFW

2. Extract **Complete Froyo Bundle!!** FRX06 - "Stable" - Minor Fixes to my SD Card.

3. copy ts-calibration,STARTUP.TXT and new kernel to SD Card(delete old kernel)

4. add two line to froyo.user.conf

mount --bind /sdcard/conf/libhtcgeneric-ril.so /lib/froyo/libhtcgeneric-ril.so

mount --bind /sdcard/conf/build.prop /system/build.prop

5. copy highlandsun ril to /sdcard/conf

6. copy build.prop to /sdcard/conf and add

ro.telephony.default_network = 4 (modify 0->4)

ro.cdma.home.operator.numeric=46003

ro.cdma.home.operator.alpha=ctc

Then problem still, seems log have some more SMD info, SMD is used in ril.

Now I can do is to modify ril code, remove killall pppd code, no reboot again, but disable data connection not really disconnected.
[Touch Pro2, Tilt 2 Android Development] R^7Z:
If it is ril related, wouldn't it be better discussed in that thread? Just thinking out loud here. If I am wrong, by all means, ignore me :) ;) :p
[Touch Pro2, Tilt 2 Android Development] AkumaX:
what's up w/ the latest official kernel from 4/15? re-enabled BT in rhodium??
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Well, trace thru the commits.

First BT was enabled - but if you ran the kernel, you'd know it killed sleep. So BT was disabled, but just for RHOD. Very soon thereafter, jb posted a patch that fixed the sleep issue with BT for RHOD, so it was subsequently re-enabled.

This is only kernel level support, we still have no userland support for BT (AFAIK). At least it doesn't turn on for me :p.
[Touch Pro2, Tilt 2 Android Development] randomblame:
is 2.6.35 working at all yet? There have been so many commits...
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I don't think any of the commits are for RHOD specifically, and I don't know of any kernel dev that's working on RHOD. TOPA and KOVS are the only two devices that I know of that have booted .35.
[Touch Pro2, Tilt 2 Android Development] manny05:
wrong thread..sorry guys
[Touch Pro2, Tilt 2 Android Development] Wiliuxaz:
Is it just me or 20110415_205352 kernel screws up on RHOD_100_UK with Data Connection? i can't connect and if i leave it with tick on - GSM network disconnects after some time and in this case usualy a restart is needed.
[Touch Pro2, Tilt 2 Android Development] randomblame:
lol wistilt2's not interested in a nice shiny new code base to fix? I guess I'll have to git the source and take a look since I'm bored with my inspire...
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yea, I guess WisTilt2 is looking to fix up .27 rather than move to the new base. I haven't really talked to him about it much, I'm sure he has a good reason :p.
[Touch Pro2, Tilt 2 Android Development] randomblame:
because it'll be a pita
[Touch Pro2, Tilt 2 Android Development] highlandsun:
2.6.27 is antiquated. And it's missing features that Froyo was written for. There's no way anyone is going to get Gingerbread running stable on such an outdated kernel.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
It'll certainly be nice to start over with a new base... Just not a lot of kernel developer interest from what I've gathered. Only a few are working on it, and none are working on it for the RHOD to my knowledge.

JB might be testing a bit for .35, I don't know how to follow his progress short of stalking his git repo's...
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Partitioned builds

That commit doesn't apply cleanly to 2.6.27 but I wrote an equivalent patch and recompiled the kernel. Now USB mount/unmount works perfectly for me. (In addition to the initrd change.)
[Touch Pro2, Tilt 2 Android Development] jordanthompson:
Screen auto-rotate is off by 90 degrees

I poked around but could not find this. I have had this problem with every version of XDAndriod I have ever tried. Is this a setting I am missing? If I turn off auto-rotate, it works fine in portrait-only mode, but I want Auto :D
[Touch Pro2, Tilt 2 Android Development] Christiaan91:
Change gsensor_axis=*,*,* (in your startup file) into this gsensor_axis=2,1,3
[Touch Pro2, Tilt 2 Android Development] jordanthompson:
That was it! thanks very much
[Touch Pro2, Tilt 2 Android Development] toadlife:
Usb discharing battery

Starting with the 5/4 autobuild kernel, the battery does not charge via USB and seems to actually discharge. Same with the latest 5/6 kernel that just came out.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Indeed... also in the 5/6 kernel that was just released, I thought the phone was supposed to immediately wake - or at least recognize - a USB charger? I plugged the phone in via USB, and it's still sleeping... AC seems to wake/charge the phone immediately.
[Touch Pro2, Tilt 2 Android Development] engfantom:
hay all there is another build issued in 6-5 (01313) its great for me and its normally charge my phone and good sleep and no sod till now
[Touch Pro2, Tilt 2 Android Development] slycker:
Failure to deep sleep with new kernel [01313]

A problem with the new kernel:

I now regularly have a failure to enter deep sleep with new kernel [01313] (LED flickers green, every 1-3 seconds, but otherwise orange). I returned to 01295 and normal sleep/wake functionality returned. I left the data file untouched - potentially it may have made a difference, I suppose, if I had deleted/renamed it and had it re-built - I will try this sometime in the next day or so.

There were no new software installations changing the environment, and I ensured no processes were running that could interfere with sleeping.

Telus RHOD 400

FRX 06 + minor fixes

Hyc's RIL2

F22's rootfs
[Touch Pro2, Tilt 2 Android Development] Entropy512:
give us a dmesg... Can't help you otherwise.
[Touch Pro2, Tilt 2 Android Development] slycker:
I do plan to do this - I'm planning to get to this in the next day or so after work settles down a bit - sorry for not getting it out there right from the beginning.
[Touch Pro2, Tilt 2 Android Development] ryannathans:
WisTilt2's testing kernel has perfect wakes and no SODs EVER.

My first day with 9/5 kernel I had a failed wake almost every time and a few SODs.

Going back to testing kernel.... :D
[Touch Pro2, Tilt 2 Android Development] highlandsun:
That's a real shame, because the power management patch from Wistilt2 that fixes this stuff is the one patch that doesn't apply cleanly to the current source tree. And the autobuild kernel has a lot of other fixes in it now (mostly USB stuff I guess) like the new bluetooth and audio fixes.