yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] cameraddict:
I've been testing 3.3.6 for several weeks now. I have a thorough report, and will make a log file. Since 3.4 is currently being worked on, do the powers that be still have an interest in what I've found? If so, I'll post it all by tomorrow.

Thanks. I haven't had a whole lot of time as of late to help, but still hope to contribute.

Peace
[Touch Pro2, Tilt 2 Android Development] xXHawkeyeXx:
3.3.x Kernels and Vsync.

Hello.

The latest Kernels do seem very nice, except they appear to have Vsync enabled. Any chance of disabling it? They don't perform as well with scrolling and such like the other 2.x Kernels do. :)

Thank you! :D
[Touch Pro2, Tilt 2 Android Development] detule:
Thanks for the kind words, but .... what the hell are you talking about?
[Touch Pro2, Tilt 2 Android Development] xXHawkeyeXx:
AHA!... You know, Vsync? or Vertical Synchronization. Its to prevent "screen tearing". I do notice the screen does not "Tear" with scrolling or any other animations while using the 3.3.x Kernels... but I guess you could say having Vsync enabled doesn't work well if your hardware isn't that great...

Well, it is enabled, or disabled through the Kernel... How exactly I really don't know, I don't have any experience with editing Kernels, what so ever.
[Touch Pro2, Tilt 2 Android Development] detule:
I am going to be nice since you admitted you don't know what you are talking about. Take this to be the answer to your question: no performance improvements can be made on our device by disabling anything called vsync.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I'm kinda wondering why he thought it would... lol.
[Touch Pro2, Tilt 2 Android Development] xXHawkeyeXx:
Ok, Listen. I took the liberty of giving Walters build with the 3.3.6 Kernel a try, since it works with it, just in case the performance issue I'm experiencing is somehow specific to GBX0. It isn't, Indeed like before, it seems the 3.3.x Kernels are the cause. Scrolling and other animations are just not as smooth, and really, it is a noticeable difference. Now the good news, Although I didn't notice it at first, there is still screen tearing, meaning Vsync is not enabled, So it was pointless bringing that up, however, it is a real thing...

I won't waste anymore of your time on the subject, I'm sure its just one of those mystery problems. :p but it is there, and it especially shows while playing emulators, big difference in performance between 2.x and 3.3.x

Thank you kindly for your time, Detule. I wish I could be of some help, but all I can do is say "its there", sorry. :o

Because It would. Vsync is indeed an option for some Android phones (In the Kernel, that is) From some research, I'm under the impression it may not be for Rhodium... especially not being a native android device, but don't dismiss it as irrelevant when it comes to performance, my good sir.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Link for reference please.

You keep saying it would, but don't provide anything to back it up - so why are you so convinced? I'd imagine you read something, somewhere on the subject.

Either way, it sounds like snake oil as usual.
[Touch Pro2, Tilt 2 Android Development] xXHawkeyeXx:
http://xdaforums.com/showthread.php?t=1312067

There you are, proof that is an option for the Optimus One. Like I've said though, from what I've found, I think it may only be for a select few.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I'd read the last post.

Vsync seems to be snake oil for benchmarks. There's a TON of snake oil for benchmarks out there...
[Touch Pro2, Tilt 2 Android Development] :
http://irclog.netripper.com/htc-linux/2011/11/23/

Wistilt2 mentions it also.. I'm inclined to say it isn't beneficial though...
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
They're talking about that 30fps limit which was broken on the OG EVO. They were thinking we had a similar artificial limit...
[Touch Pro2, Tilt 2 Android Development] thegof:
1. Thank You, Thank You, Thank You to all those continuing to develop these for the Touch Pro 2!!!

2. any idea when 3.4 will be included in the autobuilds?

3. Is there a link to what's new in 3.4 for us less informed techno geeks? :D
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
1. You're welcome.

2. Nope. Probably when it's ready.

3. If you read the git commits, you should be able to get the jist. I don't think there's a whole lot of "new stuff" as far as RHOD-specific code... Just new kernel code that they're trying to get working on the RHOD.
[Touch Pro2, Tilt 2 Android Development] detule:
htc-msm-3.4

I emailed WisTilt2 this morning, and hopefully 3.4 will get added to the autobuild soon.

It's in pretty good shape now, but initially we had a few serious issues with this kernel.

- When it came out, there was a serious problem with the memory manager in the upstream 3.4 kernel that flat out broke the chroot system call (not just for us, but other users as well). If you have ever taken a peak at our initramfs, we use chroot (or rather switch_root) to maneuver onto our rootfs. We were stuck spinning our wheels until around 3.4.2 made an appearance on kernel.org and this problem was patched.

- We had another problem with the patches that instruct the vanilla linux kernel to use the android wake_locks infrastructure. Not sure who's to blame here, but I am inclined to think it's kernel.org again. At any rate, for the first time ever I saw frequent SODs on the 3.x kernels. I think we fixed this also.

- Finally, USB: I think we are victims of our own success here. To get adb, usb tethering etc, to work with android, we use android-specific patches on the vanilla linux kernel. As we progress to newer and newer kernels, so do these android patches. The problem is that ever since 3.0, google has stopped supporting gingerbread-like usb configurations in their kernel patches. So we've been dragging the usb layer from .39 all the way up to 3.3 -> this way we were successful in using the new kernels with gingerbread. This however is a HUGE hack and not good in any way shape or form. Finally something in the new 3.4 kernel prevents us to use the drivers from .39 and we were forced upgrade our usb layer, and together with it bring in ICS geared USB patches.

The result: with some work, we can get adb to work. However gingerbread is looking for active USB connections in the wrong place and even if you get ADB going, GB is unaware of an active usb connection so you can't enable other perks like USB tethering.

Not sure what the solution is to this last problem -> probably need to hack at frameworks in GBX but the motivation for this is somewhat low, since at that point we would need to be distributing a separate build to use specifically with 3.4.

Therefore finally, the current bug-list for 3.4:

1. Kexec is broken

2. USB: We can get ADB (instructions on this to follow), however USB notification doesn't work, and consequently can't enable USB tethering. <--- see here how to take advantage of usb functionality on htc-msm-3.4

3. Bluetooth -> haven't looked at the BT patches yet, but hey BT never really works OK anyways.

On the bright side -> you will be using a kernel that's the bleeding edge in the linux world. Also, this might be placebo, but I think the new usb drivers manage the serial clocks better and perhaps power-management seems slightly better (interested in hearing how other folks think it compares).
[Touch Pro2, Tilt 2 Android Development] nickleby:
Autobuild seems to be offline :confused:
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yea, jonpry said something similar earlier on IRC...
[Touch Pro2, Tilt 2 Android Development] detule:
htc-msm-3.4 update: We managed to fix USB Tethering, and sounds like WisTilt2 will do his best to get the kernel on the autobuild shortly.

Please follow these instructions to take advantage of the usb functions on this kernel.

As always, when submitting reports please include complete GetLogs output.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Autobuild is back baby :D
[Touch Pro2, Tilt 2 Android Development] eurohunter:
Are the kernels newer than 3.3.6 optimized for Nand GBX0*?
[Touch Pro2, Tilt 2 Android Development] cameraddict:
I assume that since nobody replied to my post, and that 3.4 is getting closer to stable, that no one is interested in the log file I offered for 3.3.6??

Thanks
[Touch Pro2, Tilt 2 Android Development] CodaHighland:
You should have posted the log anyway.
[Touch Pro2, Tilt 2 Android Development] detule:
I didn't see anything in your post that needed responding to.

You seem to be having some backlight issues, that were half way resolved by turning off auto-backlight in WinMo. Jonpry has 210 as do other users (Codahighland?) and I haven't heard from them about any issues re: auto-backlight.
[Touch Pro2, Tilt 2 Android Development] CodaHighland:
I've got a 210 but I don't use autobacklight (I prefer having it set fixed to the second-lowest setting) so I couldn't say.
[Touch Pro2, Tilt 2 Android Development] ObviousMan:
Running 3.4.3 now. USB enable app works as advertized. Basis functionality is all there. Have not done much testing after that yet.

I there anything should be tested earlier rather than later?

Thanks.

OM
[Touch Pro2, Tilt 2 Android Development] cameraddict:
Apologies for my delay in responding. I've been crazy busy. Which is also why I didn't get a log file right away. By the time I posted my results, 3.4 was here. I want to help, but I run my own business, and administer two others- so time is at a premium for me, and I need to spend it wisely.

Detule, the biggest issue I had was the high energy use using wifi. This is the first time I have had this problem.

CodaHighland: From now on, I'll grab a log as I test from the moment I install a new kernal. Live and learn.

Thanks for both of your responses.
[Touch Pro2, Tilt 2 Android Development] Stijnjits:
I just suddenly got a weird thing with my Rhod100...

I have the LED mode set to orange when awake, off when sleeping. At 22h the orange led suddenly started blinking at about 0.5 to 2Hz (frequency shifts a bit).

If someone thinks it's worth investigating, the logs are here

At a few minutes after 22h, you'll see I enabled the wifi to upload the log file.

After uploading I disabled the wifi again, and the orange led started blinking again.
[Touch Pro2, Tilt 2 Android Development] detule:
Without looking at the log, I'll just mention that I've had this happen a few times -> always in situations when the battery was critically low (regardless of what the battery indicator was saying). Not sure what it is, but there's some sort of an interrupt storm right before the device shuts down completely due to low battery, that wakes up the device at the frequency you describe.
[Touch Pro2, Tilt 2 Android Development] ObviousMan:
I am still running 3.4.3 It has been quite stable, but I just needed to use wi-fi tethering, and it would not enable. Has anyone else had this problem?

If I roll back to 3.3.8, there is no problem with tethering...

OM
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Can you describe the behavior?

Any logs?
[Touch Pro2, Tilt 2 Android Development] Caldair:
I think if it works in 3.3.8 then for 3.4 you need to use detules XdaRndisToggler from the second post of this thread, here:

http://xdaforums.com/showpost.php?p=20953829&postcount=2
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
AFAIK that toggler only applies to USB tethering and ADB. Nothing to do with wifi tethering...
[Touch Pro2, Tilt 2 Android Development] Caldair:
oops! Sorry, totally missed that.
[Touch Pro2, Tilt 2 Android Development] ObviousMan:
When I tried to enable wifi tethering, it would display "enabling ..." or some thing of the kind, and the come back and just display "Error"

I needed the tethering, so I switched to 3.3.8 before capturing any logs.

Here are the logs in pastebin from 3.4.3: http://pastebin.com/q55CdLyM

Thanks.

OM
[Touch Pro2, Tilt 2 Android Development] wizardknight:
The simplest thing to do is just use the get logs app. http://xdaforums.com/showthread.php?t=1123129&highlight=getlogs+apk
[Touch Pro2, Tilt 2 Android Development] ObviousMan:
Got the app. Thanks.

Tried again. Same thing. Gives message "Turning on..."

Then just "Error" WiFi turns off after that.

Here is the pastebin location for the logs: http://pastebin.com/q55CdLyM

OM
[Touch Pro2, Tilt 2 Android Development] codyt:
Wifi Tethering "Error"

I'm having the exact same problem with my rhod400 running the 3.4.3 kernel.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Not sure we're going to get a fix for 3.4.x... especially since that kernel targets a lot of ICS stuff.

3.3.x might be the end of the line. Which, to be honest, is still really freakin new in the kernel world. My girlfriend's Optimus S is still on 2.6.35...
[Touch Pro2, Tilt 2 Android Development] ObviousMan:
Fair enough. 3.3.8 is pretty good too.

arrrghhh, in you own opinion, is any of the NAND set-ups currently ready for everyday use, or not?

THanks.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I sent ya a PM, as it's really not on-topic for this thread...
[Touch Pro2, Tilt 2 Android Development] ObviousMan:
Indeed, sorry. THanks.
[Touch Pro2, Tilt 2 Android Development] :
I tried to boot your kernel on a nand rom but it resulted in kernel panic.

the kmsg i grabbed from /proc/last_kmg: http://pastebin.com/gNLpuhQW

BTW, its Autokernel build kernel-pack-htc-msm-3.3.8-ge0d700d-20120607_073427.zip

I compiled your kernel from source (with the config from walter79's ICS boot.img), but it also resulted in the same error.
[Touch Pro2, Tilt 2 Android Development] pfc_m_drake:
Thexe kernels are only for GBX0C (sd card build) and detule's GBX0*+3.3.x kernel nand build. If you were using another nand build, then that is likely your problem (e.g. kernel incompatibility).
[Touch Pro2, Tilt 2 Android Development] detule:
Go back and read the first post - it clearly states which build these kernels are optimized to run on.

Beat me to it - though very similar, there are still couple of differences between these, and the kernel that's in the gbx0c nand build (in case anyone cares: different smd driver, and the panel commits never got merged). So yeah, the kernels from the autobuild should really only be used with xdandroid gbx0c.
[Touch Pro2, Tilt 2 Android Development] Karim Kahale:
Can I use these kernels for nand?
[Touch Pro2, Tilt 2 Android Development] wizardknight:
No.These are for SD GBX0C builds only unless someone merged the kernel trees, and I missed it somehow.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
There's already a few kernels for NAND, just not here. Detule posted some for his GBX NAND ROM, as did Walter for his CM7 ROM.
[Touch Pro2, Tilt 2 Android Development] detule:
That was in response to something about /proc/kmsg, GetLogs already includes this output, as well as the output of "logcat".

What's the output of the insmod command?

Also, can you provide the output of

md5sum /system/etc/wifi/bcm432x/bcm4325-rtecdc.bin

Also can you attach /data/wifi-nvram.txt
[Touch Pro2, Tilt 2 Android Development] JDog2pt0:
My bad, missed that one.

insmod: can't read '/lib/modules/bcm4329.ko': No such file or directory

I have no modules folder.

bca2cb274070423a7ea332c1e8cee115 /system/etc/wifi/bcm432x/bcm4325-rtecdc.bin

Nothing in my /data folder
[Touch Pro2, Tilt 2 Android Development] detule:
Type out the following in adb shell

mount -o rw,remount /
ln -s /system/lib/modules /lib/modules

Then reboot. See if your /lib/modules folder is populated, and if so, try the insmod command again.

I take it this means, you can't find that particular file in /data, rather than /data is empty. Follow these instructions

http://xdaforums.com/showpost.php?p=9187263&postcount=80
[Touch Pro2, Tilt 2 Android Development] JDog2pt0:
No, I mean /data has nothing in it, completely empty.

I honestly have no clue what's going on. 3.1 has no modules folder, empty data folder and crashes when I try to use wifi. 3.0 was working, then I started getting error with wifi. Decided to jump boat to .35 and still have no modules folder and empty /data along with non-funtioning wifi. On .35 after populating modules with the command you posted, insmod gives me this

insmod: can't insert '/lib/modules/bcm4329.ko': invalid parameter

:mad:

Thankfully I have my entire Froyo setup saved.
[Touch Pro2, Tilt 2 Android Development] detule:
Your problem is not with any of these kernels, you are having issues with setting up the build correctly. You should go back to the GBX0B thread and start from scratch.
[Touch Pro2, Tilt 2 Android Development] JDog2pt0:
I guess it's a no no to switch kernels before booting for the first time, because that seemed to be my issue. Using 3.1, everything is good now except for incoming call ringtone, but that's being addressed in the GBX0B thread.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Hrm, I can't honestly think of a reason why you wouldn't be able to switch kernels on the first boot... Odd.
[Touch Pro2, Tilt 2 Android Development] bryanwieg:
First I have to say THANK YOU (THANKYOU THANKYOU) for this work. I have to have a WinMo 6.5 device for some applications I need, and with this Andriod port I get the best of both worlds with this device. I absolutely love what you all have done here. Thanks you!

Now, here is a bug report:

On my RHOD500 with 3.1 and GBX0B I also have an issue with WiFi. When I enable wifi the phone will work for a few seconds and then begin an endless cycle of rebooting Andriod, not WinMo.

I can break the cycle by removing the battery. When I resume Andriod it works fine.

Pastebin before: http://pastebin.com/RmQXpjaJ

Pastebin After (on reboot) : http://pastebin.com/5zh6yiQf

Also I was playing with the acpuclock.force_turbo parameter, evidently it doesn't do anything in this build, as others claim it does in thiers. As a side note, the WiFi error occurred before I was messing with parameters as well.
[Touch Pro2, Tilt 2 Android Development] detule:
Can you attach your /data/wifi-nvram.txt file?
[Touch Pro2, Tilt 2 Android Development] detule:
As you suspect, force_turbo doesn't do anything on rhodium devices.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
+1, it's not just this build, it's the device. That's not a valid startup.txt option for Rhodium's...
[Touch Pro2, Tilt 2 Android Development] bryanwieg:
Thank you! I will post that as soon as possible.

Just quickly Id like to report that it does not ring incomming calls reliably, as reported earlier. As well, I tried the acpu.clock paramter mentioned in the other froyo buid in this forum- it also has no effect, although he claims it works on his rodium.

I will post that info as soon as I can. Thanks again.

*posted from my tp2 running gb 3.1
[Touch Pro2, Tilt 2 Android Development] detule:
This is a userland issue, to be patched in the next testing release. It shouldn't matter which kernel you are on.

The parameter has been renamed in .39/3.0/3.1 to acpuclock-arm11.oc_freq_khz

Not quite true ;)
[Touch Pro2, Tilt 2 Android Development] JDog2pt0:
I suppose I can remove that from my startup...

So I guess Froyo reporting in the kernel messages that it is supported was just a false positive?

Thanks for this
[Touch Pro2, Tilt 2 Android Development] bryanwieg:
A search of all files on the SD card with Andriod revleals no existence of this file "wifi-nvram.txt".

---------- Post added at 11:27 PM ---------- Previous post was at 11:23 PM ----------

The log says the parameter was accepted and enabled for me asl well, although I can not say for ceratin I received any performance gain.

Also, am I mistaken about the versioning when you say it was "not quite true I posted with my tp2 in gb 3.1"? Sorry for that! I was posting with my TP2 in Andriod though! I meant that as my way to say, "This is working, and it awesome!"
[Touch Pro2, Tilt 2 Android Development] detule:
This should fix your wifi.
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
So is this what we should be using to OC the device when using a .39/3.0/3.1 kernel?
[Touch Pro2, Tilt 2 Android Development] detule:
Yes. Apparently "Yes" is too short of a message for xda so I have to add this sentence.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Uhm no. Turbo mode is always on for Rhodium's, regardless of the startup.txt setting. Just like hw3d, there's no need to force it on anymore. Heck, I even think it has always, always been on for RHOD's. I think it's a hardware level thing that is one of the few things they improved over the RAPH.

I actually put both lines in. Doesn't hurt anything, and that way whether you boot .27 or .35+, you'll get the same OC.
[Touch Pro2, Tilt 2 Android Development] detule:
First post updated : As of today, all kernels should have extUSB audio support, as well as 3.5mm audio support for CDMA rhodiums (Thanks to ACL and emwe).

Running out of things to do.
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
New 3.1 kernel has LED on orange all the time. Was that on purpose, or is some debugging tool (sleep/non-sleep) thing?
[Touch Pro2, Tilt 2 Android Development] detule:
Nothing in the recent commits has anything to do with the color LED. Any unexpected LED behavior is stemming from problems/apps is on your end.
[Touch Pro2, Tilt 2 Android Development] bryanwieg:
I got as far as the Terminal Emulator, but when I try to run it I get the error over and over:

"The Application Terminal Emulator (process com.andriod.term) has stropped responding unexpectedly. Please try again."

http://pastebin.com/E3t0cnG2

Am I missing something?

Thanks,

Bryan

EDIT: Others app are doing it to, a few, not all, that were working fine yesterday. It must be something I did to it... I'll work at it.
[Touch Pro2, Tilt 2 Android Development] detule:
You can type out those commands in an adb shell, or alternatively you can use ConnectBot (like Terminal Emulator) from the market.
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
Latest 3.1 working fine here, nothing funky at all with led's.
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
I figured it out. For some reason using Dual_Boot in windows mobile even though I specified GBX0B as my path to haret it used the old haret from my andboot (FRX7.1 folder) but still booted GBX0B, and the orange LED came on. I am still trying to figure out why it using that haret instead of the one in the GBX0B folder, but that is off-topic for this thread, so I will not discuss it here.
[Touch Pro2, Tilt 2 Android Development] bryanwieg:
Placing this here as requested:

I and one other expeience this when trying to restart. I am running 3.1. The only way to reboot without freezing is 'shutdown'. Which still, does not shutdown, but restarts the phone.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Dude. No offense, but seriously there's no point in posting a log from 3.1 BT failing, I thought you would've gotten that from the other thread...

3.1 doesn't have BT. If you want to test BT, do it on .27 or 3.0... what's not clear about that?
[Touch Pro2, Tilt 2 Android Development] bryanwieg:
Hey,

I noticed a new kernel is on the auto-build:

http://autobuild.wirelesstcp.net/

kernel-pack-htc-msm-3.2.1-g29e19e5-20120116_100113.zip

I would be glad to try it out. Any particular issues I should look for? What can I do to help test it thoroughly? I could not find any notes anywhere, like http://xdandroid.com.

Regarding bluetooth, is more input still sought? I have seen some poeple post results of their attempts already. If so more information is needed, please let me know, so I can also try build 3.0 and bluetooth connectivity. I can test tethering, pairing to PC (obviously), and post logs.

Bryan
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I was just going to post that 3.2 is now up on the autobuild :p.

AFAIK it's about the same place as 3.1 at this point - test it out and let us know! All the same caveats apply as with any .35+ kernel.