yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] detule:
The only difference I see between your dmesg output and what I see here is that I am successfully connecting to an AP on channel 6 <- don't think this would make a difference.
[Touch Pro2, Tilt 2 Android Development] nickleby:
I've switched to the 3.2 kernel from .27. Till now, works OK (camera, 3.5mm, etc). I haven't tried 3G data, but I guess it should work ok. This kernel boots more quick than .27 :)

USB works ok, but I agree with highlandsun about Wi-Fi... It works, but it definitely fails a lot when it tries to connect to the AP, but it could be the FW instead of the kernel. Sorry, but no logs this time. :p I think I'll stay on 3.2 for a while
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Fyi, the "new" firmware in the GBX0B bundle is 4.217.74.0. I've found a newer 4.217.95.0 which works for me. (The "old" firmware is 4.216.77.0)

https://github.com/tom3q/android_de...df116678b4c9/prebuilt/acclaim/wifi/rtecdc.bin

There's also an AP mode firmware here, which works if you mess with it. I'm not going to document the steps here, it's still too ugly.

https://github.com/tom3q/android_de...78b4c9/prebuilt/acclaim/wifi/rtecdc_apsta.bin

Just pointing it out so it's not lost.
[Touch Pro2, Tilt 2 Android Development] MadBeef:
Works for me too, on RHOD100. Seems quicker at joining the network. Thanks :)
[Touch Pro2, Tilt 2 Android Development] highlandsun:
OK. There is a trivial bug in the bcm4329.ko wifi driver that prevents wifi tethering from starting correctly. I've patched it and attached a binary here for the current 3.2 kernel.

The patch is here http://lists.xdandroid.com/pipermail/xdandroid-dev/2012-February/000447.html

You also need the 4.217.95.0 AP firmware that I linked above. With both installed, wifi tethering works flawlessly for me. In AP mode, not ad hoc!
[Touch Pro2, Tilt 2 Android Development] detule:
Thanks. I've pushed the patch to the 3.0/3.1/3.2 trees and consequently this functionality should already be in the auto-build kernels (no need to swap out the kernel module).

To users interested in using the wifi tethering functionality -> you will need the *_apsta firmware from hyc's earlier post. In particular, the *_apsta file should overwrite:

/etc/firmware/BCM4325_apsta.bin

It is probably a good idea to also update the non-apsta firmware (new version also found in hyc's earlier post). It seems it offers better connectivity when using WPA-Enterprise security. The non-apsta firmware should overwrite:

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

Note, to be able to do this you need to remount /system as rw. In addition, resetting the device will revert to the older firmwares. To make these changes permanent, replace init.etc/firmware/BCM4325_apsta.bin and init.etc/wifi/bcm432x/bcm4325-rtecdc.bin.new with the corresponding binaries as well.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I should be able to crank out a new rootfs that doesn't blow this up. Still need to get all my commits accepted!
[Touch Pro2, Tilt 2 Android Development] fortunz:
Would you mind using the xdaledregime app to turn on led debug and make sure your device does in fact sleep when you turn it off? Much obliged.
[Touch Pro2, Tilt 2 Android Development] CodaHighland:
Updated my RHOD210 from .27 to the latest 3.2.2 autobuild, and loaded on the new firmware. Everything seems happy. (I'm a fan of the clearer bootscroll text!)

It's hard to tell at this point what the current points needing testing/refinement are. I'm up for experimentation now that I've got myself a nice stable configuration I can back up, so what's known to be new and/or broken in 3.2? I'm not having a lot of luck finding information on it.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Just report issues, I think 3.2 is pretty close to .27 at this point in the game.
[Touch Pro2, Tilt 2 Android Development] CodaHighland:
Awesome, thanks.

And on that note, it seems BT is still a little bit flaky. My laptop can discover my phone, but can't pair. In three trials, no passcode came up on one attempt, the passcode came up on both sides but pairing failed on the next attempt, and on the third attempt the laptop generated a passcode but the phone never prompted to pair.

Attempting to pair the other direction (discovering my laptop FROM my phone) showed a passcode on my laptop but never on my phone; confirming it just sat there until the pairing timed out. My laptop reports connected but not paired, and a file transfer likewise spins until it times out.

I didn't see anything useful in logcat, but http://pastebin.com/yRm9ZZLj has GetLogs output. I'd try to dig some more but my experience with Bluetooth development is limited.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
BT isn't so great at this stage.

I don't think file transfer has worked for anyone, ever. In addition, some report great things with their headset/cars, while others report complete failure with a different headset/car.

So to say BT is inconsistent is an understatement.... Which again, is on par with .27 ;).
[Touch Pro2, Tilt 2 Android Development] CodaHighland:
Ha, I suppose that's true. If I had some more experience with BT code I might consider hacking on it myself, but given the apparent low level of this failure I think I'd be out of my league. I'm mostly an application developer with a hefty chunk of sysadmin experience; I've written a couple drivers for custom hardware in my day -- debugging those with an oscilloscope was fun -- but I wouldn't know where to start tracking this down.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Patches are always welcome mate ;). Join us in #XDAndroid (on Freenode) if you wish.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
You mean, file transfer has never worked for GBX and these kernels? Because it worked fine for me on FRX06+ with .27...

What about camcorder? OMGB says camera is fully working, does that include camcorder? It definitely is not working here, and after you attempt to use it there are endless dmesg spams from msm_camera from that point until you reboot.
[Touch Pro2, Tilt 2 Android Development] detule:
Right, about the last thing that's not working - it's been waiting for a champion looking for a project :). ACL did away with using some jpeg encoding functionality of the qualcomm blob to fix the camera on omgb, don't think that would affect the camcorder. You should give it a go. Need to bisect if it's an issue with Alex's clocks since I remember having to make some changes in the camera files when i ported them over - does the same error happen with .27 (still on JB's clocks)?

We were happy enough with bzo and WisTilt2 to get the camera going - but perhaps I broke something with that commit. Again that looks to be isolated to the camera functionality but I could be wrong.

Edit: Perhaps this and subsequent patches?

I am going by this logcat output

02-24 08:03:51.529 F/CameraSource( 1392): frameworks/base/media/libstagefright/CameraSource.cpp:152 colorFormatStr != NULL
02-24 08:03:51.669 I/DEBUG ( 1389): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
02-24 08:03:51.669 I/DEBUG ( 1389): Build fingerprint: 'Android/full_msm/msm:2.3.7/GINGERBREAD/eng.Oliver.20120115.214511:userdebug/test-keys'
02-24 08:03:51.669 I/DEBUG ( 1389): pid: 1392, tid: 1421 >>> /system/bin/mediaserver <<<
02-24 08:03:51.669 I/DEBUG ( 1389): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr deadbaad
02-24 08:03:51.669 I/DEBUG ( 1389): r0 deadbaad r1 0000000c r2 00000027 r3 00000000
02-24 08:03:51.669 I/DEBUG ( 1389): r4 00000080 r5 afd46668 r6 a30608bc r7 406d6c4c
02-24 08:03:51.669 I/DEBUG ( 1389): r8 a811cbdd r9 00022b58 10 00100000 fp 00000001
02-24 08:03:51.669 I/DEBUG ( 1389): ip ffffffff sp 406d67e8 lr afd193ad pc afd15f34 cpsr 00000030
02-24 08:04:02.450 I/InputDispatcher( 1422): Application is not responding: Window{40894800 com.android.camera/com.android.camera.VideoCamera paused=false}. 5015.4ms since event, 500

What kind of a message is "F/" supposed to prefix? Fatal?
[Touch Pro2, Tilt 2 Android Development] CodaHighland:
I can confirm that the camcorder causes the camera to break on my RHOD210; my experience matches highlandsun's in that the camera is completely unusable after you try to start recording. kexec kicks it back into behaving; I don't have to let Windows reinit the hardware. The still camera works (as long as you don't try to record video).

Unrelated: Is it possible to shut up the startup console spam from the acoustic code? I'm looking at the scroll and trying to figure out everything I can squelch without losing anything important, in hopes that maybe I can fix the ts calibrator. (Its main problem so far seems to be that console output overwrites the crosshairs.) I get the feeling I'll be more helpful here than on the BT side.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
O? I thought it never worked, my bad. From the reports, (IIRC) file transfer never really worked, and only some headsets would work - but it t'was a crapshoot. Sorry for the misinformation! BT is so inconsistent...

I can test camcorder on OMGB, I think it works for everyone but the RHOD100 folks. I don't think ACL has implemented that camera patch yet - but I know he was looking at it.

WisTilt2 did this on his kernels, and did fix it. I don't see the big deal tho - we have a userland app that can do calib now, thanks to HTC and ACL....
[Touch Pro2, Tilt 2 Android Development] CodaHighland:
I hadn't heard of or seen that userland app. I can't even find it with a search. Got any pointers?

How would you get to it without a working touchscreen, though? >.>
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
There's values in the bootloader. How do you think the OMGB ROM works...?

For HaRET, you just use an existing ts-calib and then refine it once in Android. I don't think anyone's taken ACL's port of HTC's calibration app and used it on HaRET yet tho.

Edit - forgot, this guy ported the app to work on VGA, but I don't think he did anything to get it to work on HaRET, but I don't think it would be that difficult. I say that without knowing what it would entail of course :p.
[Touch Pro2, Tilt 2 Android Development] CodaHighland:
My point is that the problem is that we AREN'T shipping an existing ts-calib. If you aren't upgrading from FRX07 (which had a working boot-time calibrator) you're essentially screwed. Maybe this isn't a problem now because GBX0B is still technically in development, but if this is going to be our official answer we're going to need to come up with a solution that doesn't require that -- or at least offer a basic calibration file, or perhaps a file for each model if they vary enough. I'd be happy to contribute my own for the 210.

I suppose the other option would be to run the userland calibrator on first boot, but then we need to get that set up. (And as I asked: where can I find the userland calibrator? I'm not finding it in a search and AFAICT it's not in the GBX0B images.) (Edit: Never mind, you linked it.)

But one way or another (fix console calibrator, auto-launch graphical calibrator, or ship good-enough defaults) this is something that needs fixed, and I'm happy to provide whatever effort I can into making it happen.
[Touch Pro2, Tilt 2 Android Development] detule:
Please take these concerns to the gbx0b thread.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Agreed. CodaHighland, you have a PM.
[Touch Pro2, Tilt 2 Android Development] CodaHighland:
Ah, my apologies for going off-topic. Forgot that I was in the kernel thread, and while asking the acoustic stuff here is relevant the rest totally isn't. ^^()
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
I know I must be missing something really simple, but when using root explorer to replace the files in the init.etc/wifi and the init.etc/firmware it doesn't write and just reverts back to the old files, even if I delete the old .bin files they just come back. It is mounted in r/w, but the funny thing is in Root Explorer it is stuck in r/w, I can't unmount it.

Is there something I am doing wrong?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
My evil rootfs is doing it (the one bundled with GBX0B). If you replace the .bin.new file, the rootfs doesn't know the difference and will use that as the new firmware.

Just replace 'em in the roofs outside of Android, should be fine. Just loop mount the rootfs and replace the .bin.new file.
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
Thank you, never edited a rootfs before. Figured it out using Gizmo Manager and Ext2 IFS in Windows. I don't have ubuntu/linux and really don't know how to mess with it much more than what I do with my phone occasionally, so being able to do it in windows was great. Wi-Fi tethering works well now.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
That's what VM's are for ;).

Glad you got it workin.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
I had a SOD event when using kernel-pack-htc-msm-3.1.10-g99327f5-20120222_054320 and GBX0B 2.3.7 Build.

Logs here:

http://pastebin.com/qqKRqkhF

Is there anything else I can get for you?
[Touch Pro2, Tilt 2 Android Development] detule:
No idea, nothing jumps out, other than perhaps wifi having a hard time connecting to your network.

As a side note, kernel.org has stopped updating the 3.1 tree so it's a good idea to migrate to 3.0 or 3.2. 3.0 is designated Long Term Support, and will continue to receive updates from korg for the following year or two, and of course, 3.2 is the current-active kernel branch.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
I just went back to the last kernel release. I didn't have any issues with that one. Maybe the next release will be more friendly to my phone.
[Touch Pro2, Tilt 2 Android Development] JDog2pt0:
What are the pm.sleep_mode settings?

What I know:

0 - Leaves the phone awake with the screen off

1- Makes the phone sleep, may cause screen wakeup issues

Are those correct?

Odd thing is I haven't had wakeup issues, but my battery life doesn't seem as good as it was on FRX. I've read that there were a few others modes, most notably "2" which is supposed to be the most power saving. Not sure if it's still relevant though as it was for an older build of xdandroid.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
2 is not the most power saving, at all. Quite a long time ago, 2 was required for overclocking.

Perhaps you should read kernel boot line parameters. Look for the pm.sleep_mode. I never really understood the difference between 1 and 0 to be honest. 1 is the safest AFAIK, perhaps 0 brings more power savings with some heightened risk of SOD?
[Touch Pro2, Tilt 2 Android Development] JDog2pt0:
I'm setting it on 0 for the time being. So far my device seems like it's waking up too quickly. Though, maybe the kernel is just that good :shrug:

Actually, what should I look for in the logs to be sure my device is actually sleeping properly?
[Touch Pro2, Tilt 2 Android Development] nickleby:
Can't use Wi-Fi after update the kernel 3.2.9 Mar 08 :( I just see this in the logcat after enable the Wi-Fi:

E/WifiService( 1313): Failed to load Wi-Fi driver.

I tried to delete the modules (rm -rf /lib/modules) but it doesn't work.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I'm confused, deleting the modules didn't work or after deleting them it didn't work...?

This error is pretty straightforward. You're missing the WLAN driver, wlan.ko. Does that file exist? Can you insmod it?
[Touch Pro2, Tilt 2 Android Development] nickleby:
After delete the modules it didn't work. I tried to insmod it, but it says there's not such file or directory. I've checked /system/lib/modules and it didn't have the wlan.ko file
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Edit... nevermind.
[Touch Pro2, Tilt 2 Android Development] detule:
In .39+ we are using bcm4329 rather than wlan. What's the output of "modprobe bcm4329"?
[Touch Pro2, Tilt 2 Android Development] nickleby:
#modprobe bcm4329
modprobe: chdir3.2.9-g59895b7: No such file or directory

EDIT: I think after update the kernel the system messed up, I've tried a clean install of GBX0B and it's working (using the original files that came in the bundle, not just deleting data.img)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Derp, my bad. Sorry for the misinformation.
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
What was changed in the new 3/8 3.2 kernel?

I noticed the updated 3.2 kernel. What was added or changed in the kernel? Seeing that someone might have had a problem with it in the last few posts I just wanted to know before I started using it.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
https://gitorious.org/linux-msm-rhod/linux-msm-rhod

However, detule will probably have some pretty things to say about it that are beyond my comprehension :p.
[Touch Pro2, Tilt 2 Android Development] muziling:
Kernel 3.2 merge some nand file, does nand kernel update to 3.2 in progress.
[Touch Pro2, Tilt 2 Android Development] detule:
You have to be clearer - is this a question or a statement?

Some time ago I added the nand driver (to fix the creation of wifi-nvram on boot) but there was never any serious effort to nand-ify these kernels.

ACL is an authority and what needs to be done to make these kernels nand-worthy. Off the top of my head, the panel code needs to be updated to match what's in acl's kernels, and perhaps some of the rhodium board config (not sure what kind of a command line is used on nand or how it's passed).

But I think ACL has said he plans on updating only to .35 when he does so I am not sure if a 3.2 nand kernel will ever come about.
[Touch Pro2, Tilt 2 Android Development] CodaHighland:
Did something change with overclocking between .27 and 3.2? I put "acpuclock.oc_freq_khz=614400" in my kernel cmdline but once it's booted up I'm still only getting 528MHz out of it. Or am I missing something that should have been obvious?
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
IIRC you need to use acpuclock-arm11.oc_freq_khz=614400 for all other than .27. I personally keep both lines in there so regardless of which kernel I'm using it's going to be OC'd.
[Touch Pro2, Tilt 2 Android Development] CodaHighland:
Thanks! That's helpful. :) I'll make that change once I'm done debugging a RIL issue I'm having.
[Touch Pro2, Tilt 2 Android Development] detule:
Just pushed a batch of patches to the 3.2 tree. All users of this kernel should update to the current autobuild.

Some highlights include:

- Optimization of the lowmemorykiller android driver. Should no longer hold a full tasklist lock while traversing the proc list, among other improvements.

- A patch from WisTilt optimizing some code related to the refresh rate -> should buy you ~0.5 fps in Neocore. I seem to score +23fps pretty consistently without any kind of over-clocking.

- Some optimizations to the android hooks inside the input layer.

- Some optimizations to the suspend cycle, including an upgrade to a new (and much more minimal) android alarm driver taken from google's 3.3 tree.

- An attempt to fix the sporadic hang-ups when plugging in usb.

- Of course many kernel patches from kernel.org which likely have very little to do with us.

Just a reminder, the kernel repository is listed in the first post -> if you have any questions about how kernel x differs from kernel y make sure you checkout the repo first.
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
I was using the script in the Speed Improvement thread to fix some of the low memory stuff. It runs at startup. Do your fixes do things similar to that script so I don't have to run that script anymore or does it do different things?
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
According to Arrrghhh and Detule it does some of the same things, although I'm not sure exactly what. Since they noted that I haven't run that script and the phone's been running beautifully. Can't wait to see how the new kernel performs.
[Touch Pro2, Tilt 2 Android Development] detule:
The changes in the recent kernel are to the lowmemorykiller driver (this is the stock android task killer) itself - optimizations that affect the manner in which it goes about killing processes. They do NOT change the aggressiveness profile -> this is something that is done via userland (either via /init.cfg/init.gingerbread.rc or for more extensive changes via a script like V6). If you have found that V6 improves the performance on your device, you should continue using it. Unlike other task killers, from what's advertised in the V6 thread it works _with_ lowmemorykiller rather than on top of it, and I count this to be a big plus.

I think I documented this in another thread, but on my device I don't use V6 and have changed the corresponding lines in init.gingerbread.rc to

echo "1536,3072,5120,6400,8192" > /sys/module/lowmem*/para*/minfree
echo "0,2,4,7,12" > /sys/module/lowmem*/para*/adj

The last number (number of pages) on the first line is the first threshold (measured in (available memory to the system) = (number of pages)*4KB ) when lowmemorykiller engages.

With the stock gbx settings we are asking lowmemorykiller to engage when available memory drops below 48MB. The above lines change that to 32MB. This might still be too aggressive (what's the point of having all this RAM if we are constantly running with ~30MB free), so using V6 is not a bad idea for users that want a more custom experience.

The lowmemorykiller profile is a balancing act between performance and battery life and there is no one right setting that works for all.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Couldn't have said it better myself detule.

As he said, his changes are to the kernel driver. The changes V6 is making is to the userland settings that interact with the kernel... so in reality the SuperCharger script should now work better ;).
[Touch Pro2, Tilt 2 Android Development] detule:
rhod 1xx camera

Just pushed an adaptation (of part) of brinka123's rhod100 patch to the 3.2 tree. Unfortunately I don't have the latest version of his patch (he never posted an update to the *-dev mailing list) - at any rate if there are any rhod1xx users running this kernel they should give it a go.

All other rhod versions are unaffected.

On a side note I have the camcorder working with gbx -> not a kernel issue. I submitted the patch-set to the mailing list for review. Not sure if anyone with commit access to the userland tree is still active, but if I don't hear back from anyone, I'll just post the compiled binaries in the gbx thread.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Thanks. I'll prod a couple of peoples about it, and if worse comes to worse I think stine can take care of it at some point still.

I also want to prod brinka123 - I thought there was some low-light performance improvements for all RHOD's that he contributed/unearthed. I have no clue what he posted or what he didn't post, so that certainly might've gone under the "didn't post" category.
[Touch Pro2, Tilt 2 Android Development] JDog2pt0:
Alright, I'm getting a "switch root: cannot execute /init no such file directory-Kernel Panic-Rebooting"

The first time this happend, I had wiped my dalvik cache using one of zeppelin's scripts. I then wiped my card and started over. Last night I was using a Busybox installer to install Busybox. It sat there for an hour or two on "creating symlinks" I was going to bed so I said screw it and pulled the battery. Booting the phone up today I'm greeted with the same kernel panic. Is there anyway to fix it or do I need to do another wipe?
[Touch Pro2, Tilt 2 Android Development] CodaHighland:
I had the same problem with changing Busybox. My advice? Don't update Busybox. ;) I haven't found a compelling reason to do so; the bundled version works with V6 Supercharger.
[Touch Pro2, Tilt 2 Android Development] JDog2pt0:
So really what you're telling me I'm telling myself is to backup my data.img before doing anything Busybox related. I didn't know Busybox shipped with the build.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Busybox has to ship, otherwise we couldn't provide root OOB ;).

But yea, I wouldn't update busybox. I think because of how we implement it, the "normal" way of updating it doesn't work.