yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] mrbears:
Wireless Tethering

The latest kernel is wonderful. Thank you all for your hard work.

I wanted to ask if wireless tethering is working for any of you with latest version. It used to work with older version, but I am having difficulty in getting it to work. Thank you.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Need an updated firmware, again. I need to update my GBX0B rootfs so .35+ kernels use the newest new firmware ;).
[Touch Pro2, Tilt 2 Android Development] mrbears:
So tethering should be able to work once the firmware is updated? That's great news! :)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
It's worked fine for a long time, the issue was when you try to disable it. This new firmware works so well that it doesn't implode when the connection is torn down.

Again, this only applies to .35+ kernels.
[Touch Pro2, Tilt 2 Android Development] frostyguy:
Trying to load the latest kernal and keep getting "ms after vsync request" am I missing something?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
First, "kernel".

Second, what build?

Third, what kernel? kernel-pack-htc-msm-3.2.11-gafefbbc-20120403_185735.zip?

Have you ever run a new kernel? You're using a RHOD at least I hope?
[Touch Pro2, Tilt 2 Android Development] frostyguy:
My Bad for the confusion.

GBX0B

kernel-pack-htc-msm-3.2.11-gafefbbc-20120403_185735.zip

Using RHOD400

I finally got it to work with

htc-msm-linux-20120227_213021-package.tar.bz2

instead.

Whats the difference anyway? And how can I get kernel-pack-htc-msm-3.2.11-gafefbbc-20120403_185735.zip to work? Just replace the .tar and zImage?
[Touch Pro2, Tilt 2 Android Development] walter79:
Can some one write a small how to compile kernel from source? Is it possible to compile a 3.xx kernel with nand config from acl 2.6.27 kernel source?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
ACL made a couple of changes to the .27 to boot on NAND. There were some panel changes, among many other things I'm sure. So there's a fair bit of porting that needs to take place in order for anything but .27 to run on NAND.

As for compiling these kernels, the source is available and fairly similar to compiling anything else.

http://www.linuxplanet.com/linuxplanet/tutorials/202/1
[Touch Pro2, Tilt 2 Android Development] CodaHighland:
Where do you get the toolchain? I understand from detule and jonpry that you can't use a generic arm-elf gcc, but you have to use CodeSourcery. Unfortunately, a Google search hasn't helped me much.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
http://arago-project.org/wiki/index.php/Getting_CodeSourcery_Toolchain

That's what I used...
[Touch Pro2, Tilt 2 Android Development] mpannen:
I tried banging out a 3.3 kernel but my modules tar.gz was 8MB! I noticed that some modules were many times larger than those from 3.2, and as a result bootup is failing with an "out of space" message. I am pretty good with configuring kernels and such (not a coder though). Anyone have a quick answer?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Try w/o modules - the only major thing you'll miss is wifi.

I'm guessing the modules didn't get stripped in 3.3?

Edit - wait, there's no 3.3 in the autobuild. So you're compiling it yourself? Strip the modules :p.
[Touch Pro2, Tilt 2 Android Development] mrbears:
Hi, arrrghhh

So in order for tethering to work, GBX0B rootfs has to be updated? Can you share the updated rootfs when available, please?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Well I will certainly share when it's available. Kinda waiting on access to the MMS repo so a final commit can make it in... then I'd like to do another release, hopefully ze final one.

Tethering works, it just implodes the phone when you tear it down - causes the phone to lock up hard. The new firmware doesn't explode when it's unloaded.
[Touch Pro2, Tilt 2 Android Development] mpannen:
Do you know what can be stripped. I see there are a ton of options for 'strip'. Perhaps just debugging symbols, or others as well? Thanks!

Edit:

NICE! Lol I had a problem at first, you have to use the version of strip that comes with your cross-compiler :) Went from 13 Megs to 900kb.
[Touch Pro2, Tilt 2 Android Development] ObviousMan:
Keeping my fingers crossed for updated rootfs

OM
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
You can update the firmware manually in the rootfs, it's quite simple... If that's all you're waiting on.

I'm not going to publish a new build until all the commits hit the tree - we're waiting on getting access to a final MMS commit, then I think it's good-to-go.
[Touch Pro2, Tilt 2 Android Development] mpannen:
Here are some lines to do it in Ubuntu. You need to have the new firmwares named exactly as this, CAPS and all:

BCM4325_apsta.bin bcm4325-rtecdc.bin

Shut down your phone and remove your memory card. Insert into your card reader. The lines below are an example of the commands needed to update the firmware inside your rootfs.img file on your memory card.

sudo mount /media/5AAA-2F46/GBX0B/rootfs.img ~/rootfs/ -o loop
sudo cp ~/Downloads/BCM4325_apsta.bin ~/rootfs/init.etc/firmware/
sudo cp ~/Downloads/bcm4325-rtecdc.bin ~/rootfs/init.etc/wifi/bcm432x/bcm4325-rtecdc.bin.new
sudo umount ~/rootfs/

This example assumes an empty folder in your home directory on your computer called rootfs to attach the rootfs.img to. The mount command will vary slightly depending on the volume name and location of any subfolder your android files are stored on your memory card. The paths to the firmwares will depend on where you have them stored on your computer.

Throw your memory card back into your phone and reboot into Windows Mobile/Android. The new files will be automatically copied to your system on startup.

If you don't know squat about linux this probably doesn't help much, lol.
[Touch Pro2, Tilt 2 Android Development] mpannen:
Well I'd like to comment that so far with 3.3 I haven't had an SOD, whereas with 3.2 I had one nearly once a day. Both kernels are not overclocked. Knock on wood! Thanks!

Sent from my MSM using the XDA mobile application powered by Tapatalk
[Touch Pro2, Tilt 2 Android Development] fortunz:
Indeed, I just started using it really. I actually wasn't expecting 3.5mm jack to work, but it does.

Only things I've noticed missing are backlight adjustment and LEDs hack (which turns off the front button leds and the charge/notification led) won't work. Edit: actually I think OC'ing is out too, but I don't care much about that.

Props to the dedicated and long suffering devs still laboring away on rhodium. :)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
hahaha!

Yea, OC should work - but there's a different statement than .27. I had both statements in my startup when I was overclocking, it's harmless.

acpuclock-arm11.oc_freq_khz=614400

Thanks to fishingmedic for reminding me ;).
[Touch Pro2, Tilt 2 Android Development] nickleby:
Last kernel 3.2.11-ge75583a is not working. The phone gets stuck at the bootani...Same with 3.3.1!
[Touch Pro2, Tilt 2 Android Development] detule:
Thanks -> we are experimenting with some new toolchains and may have broken something. It's pretty late over here but we'll fix it tomorrow.
[Touch Pro2, Tilt 2 Android Development] detule:
Just reverted some of our recent commits (some toolchain quirkiness broke wifi and perhaps other thing) -> hopefully it's business as usual with 3.2 and 3.3.

Let me know if you are still having issues.
[Touch Pro2, Tilt 2 Android Development] nickleby:
Thanks detule, 3.2 and 3.3 works now :)
[Touch Pro2, Tilt 2 Android Development] fortunz:
I doubt anyone else cares, but keyboard backlight controller (and its cousin adjbrightness) has a button led off option that does work with kernel 3.2. Yay for me! :D https://play.google.com/store/apps/details?id=com.deskangel.kblight I read at night in book mode, and every time I turn a page the button led turns on, hurting my eyes and generally annoying me, so utils like this make me happy.

Brightness adjustment of the backlight still doesn't work, but overall, I'm liking 3.2. With the GBX0b .27 kernel things tended to get a little unstable after a day or so, which was especially problematic because my device wouldn't sleep until a day or so had passed, so shortly after it started to sleep I had to reboot because apps would crash and refuse to launch again and then it wouldn't sleep for a while... I've been running 3.2 for maybe a week without instability.
[Touch Pro2, Tilt 2 Android Development] detule:
Not sure what you mean by this but both the manual screen back-light adjustment as well as the automatic (both in Settings -> Display) work just fine for me.
[Touch Pro2, Tilt 2 Android Development] fortunz:
I didn't realize it was a malfunction. I just assumed it was a feature that hadn't been added. When I try to adjust the backlight, nothing happens. The max brightness looks the exact same as the minimum brightness. My reading applications that adjusted it themselves, Moon+ and Kindle, also can't dim the screen like they could under .27.

I'll test this on some clean boots and probably even my clean testing image. If it acts the same way there, I'll log it and post back.
[Touch Pro2, Tilt 2 Android Development] fortunz:
I was using a 3.2 kernel dated 4/13. It failed to adjust brightness on my normal image and a clean test image. I've switched to 4/20 and it works flawlessly.

I heart 3.2 and detule and whatever other crew remains that's is tinkering away with these. :)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
They're up to 3.3.1 :eek:!!

At any rate, I'm actually posting for 2 reasons. First, detule - the OP states only 3.0 has BT, but I thought that changed a while back... no?

Second, does anyone know what WisTilt2's been up to? The autobuild web page seems down :(.
[Touch Pro2, Tilt 2 Android Development] numero9:
Switched to the latest kernel from .27 and now when I try to use the camera it says along the lines of "Insert SD card to save photos", so I can't take any photos. In the original bundled kernel, it worked fine but after upgrading now this has happened. Anyway to fix? Everything else is running much smoother and faster, except for that problem which unfortunately is a big one for me. :(
[Touch Pro2, Tilt 2 Android Development] detule:
See if android sees your SD card at all: Settings->Storage. If not, this is likely an issue with your SD card. I hear formatting with HPTool and starting over from scratch has worked in the past for people.
[Touch Pro2, Tilt 2 Android Development] CodaHighland:
Hey detule, could you toss the latest kernel build up here as an attachment or something since autobuild is down? Or is there nothing important added since 60a2?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
The really weird thing is you don't even have to start over...

numero9, backup everything on the SD card. Format it using the HP Tool. Full format, FAT32. Then copy everything back to the card. Try try again.
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
Auto-build is back up and running now
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
& updated to 3.3.3 :eek:

That is just awesome.
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
Nice, I didn't see the 3.3.3, that was after I checked!!! Thanks for the info, now I really have the latest and greatest, and waiting patiently for the official release ;)
[Touch Pro2, Tilt 2 Android Development] walter79:
Low memory killer setting

init.rc

original:

write /sys/module/lowmemorykiller/parameters/minfree 2048,3072,4096,6144,7168,8192

new:

write /sys/module/lowmemorykiller/parameters/minfree 1536,2048,2304,2560,2816,3072

On NAND build the new settings works better. I have only 19Mb ram after boot. With old settings Android start to free up ram at 24-28 Mb ram. With new settings it starts at 12Mb.

For me overall performance is better.

Can someone test this settings for SDcard build?
[Touch Pro2, Tilt 2 Android Development] detule:
I appreciate you are being well-meaning, but this post has nothing to do with any one kernel in particular and it doesn't belong here. If you feel inclined you should post your settings in the gbx thread -> this in addition to the now three other threads you have posted this same post in.

These kernels are currently used with GBX where the system boots up with a lot more than 20MB available memory (at least it does for me). Advertising settings that work for you, in OMGB, with .27 is entirely irrelevant.

In addition I am not sure if it's a good idea to repackage ACL's kernels -> you are introducing multiple variants floating around and confusing efforts, for something that can easily be done from an adb shell.

Not to mention that there are entire threads dedicated to scripts like V6 that make extensive changes in addition to changing those few values. The LMK topic has been beaten to death I think, and resurrecting it with new values that someone discovered to work for them on ONE build with a particular kernel can't be productive.
[Touch Pro2, Tilt 2 Android Development] CodaHighland:
I thought GBX was already running 1536 anyway.
[Touch Pro2, Tilt 2 Android Development] walter79:
Sorry for posting my settings in this thread and thanks for your good work.

A few questions.

Why work all developers on different kernels? Why not take one LTS kernel and fix all problems? HTC Rhodium Hardware is old and did not need lates kernel (IMO). New kernel = new problems. I think NAND Android is the right way for our phone. Nobody like WindowsMobile for booting into Android.

Only a few developers works on kernel. Can someone like you write a HOW to compile the kernel for HTC Rhodium?

There is no documentation about this.

With a good how to i think more people can test and try new things.

I tried to compile kernel for Rhodium but no success.

Toolchain problem maybe.

Why not wrote something like this from Xperia X1 thread plus how to config my Linux for compile all this.

# Get and build kernel (if you want to use mine)
git clone git://gitorious.org/~poussevin/linux-on-qualcomm-s-msm/tp-alex-linux-xperia.gi
t -b android-2.6.35

cd tp-alex-linux-xperia
cp arch/arm/configs/htc_msm_android_defconfig .config
make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- TARGET_BOARD_PLATFORM=msm7k
make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- TARGET_BOARD_PLATFORM=msm7k modules
rm -rf modules_path
mkdir modules_path
make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- TARGET_BOARD_PLATFORM=msm7k INSTALL_MOD_PATH=modules_path modules_install
cd ..

# Recreate bootdir
rm -rf newboot
mkdir newboot
cd newboot/

# Unpack original boot.img
export PATH=../BootTools/:$PATH
cp ../boot.img .
../BootTools/unpack-bootimg.sh boot.img
rm -rf boot.img-ramdisk/lib

# Replace image
cp ../tp-alex-linux-xperia/arch/arm/boot/zImage boot.img-kernel

# Change minimum cpu freq
sed -i 's/min_freq 122880/min_freq 19200/g' boot.img-ramdisk/init.kovsky.rc

# Add modules
cp -rf ../tp-alex-linux-xperia/modules_path/* boot.img-ramdisk
[Touch Pro2, Tilt 2 Android Development] numero9:
It's not seeing it as available. Total space: Unavailable

I formatted and backed up everything as suggested above, too.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Hrm, sounds like something is wrong with your card, or your phone does not like the card. Strange it works in WinMo, but I guess we're not running the OS off of WinMo.

The last resort effort is to backup the card, format it as before, and truly start over. Do a fresh boot, new data.img, new bundle, all of it. Make sure nothing else is on the card. Immediately check the Settings section to see if the SD card is showing available or not. If it is, then there's something odd on the SD screwing it up. If it isn't, then I'd say the SD card itself is the culprit.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
There is, it's just outdated and I guess not as easy/drop-in as the X1 folks have setup...?

Also, re: your comments about devs. They'll work on what they want to work on man... Seems some still don't like NAND. Notice that ACL's pretty much the lone ranger out there...

It would be nice if there was no difference between NAND and HaRET kernels, but from what ACL has stated there's a lot of panel and other things that would need to change for the kernels to boot on both platforms.
[Touch Pro2, Tilt 2 Android Development] numero9:
Well, this has happened before upgrading to like 3.1 and then I rolled back to .27 with it working fine. This was on a different SD card too. So I formatted this card and put everything back on it and it still doing it under the latest one. I can navigate the SD card on Astro or whatever but in the storage info it still says unavailable.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
That's really strange. However - if you're not willing to break it down, then I really don't have a whole lot else to offer you.
[Touch Pro2, Tilt 2 Android Development] walter79:
Thanks with this help, I found the way to compile kernel. I will write my own small how to
[Touch Pro2, Tilt 2 Android Development] mpannen:
So this is my hack and slash for making kernel/modules. The paths for the variables will be different since home directory and structure will vary. I have stolen bits and pieces from other scripts, I am in no way a shell code writer lol.

#!/bin/sh
#-------------------------------------------------------------------------
# Build Script for linux-msm-rhod (Android on HTC) kernel, modules
#-------------------------------------------------------------------------
#
# Set the following variables
# ANDROID -- Root director for Android files
ANDROID=/home/mpannen/android
# KERNEL_PATH -- directory containing the linux-msm kernel source
KERNEL_PATH=$ANDROID/linux-msm-rhod
# TOOLCHAIN_PATH -- directory containing the arm toolchain
TOOLCHAIN_PATH=/home/mpannen/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-linux-gnueabi
# MODULES_PATH -- directory for modules
MODULES_PATH=$ANDROID/modules
#-------------------------------------------------------------------------

# build kernel and modules
#export ARCH=arm
cd $KERNEL_PATH
make clean
make ARCH=arm msm_defconfig
make ARCH=arm CROSS_COMPILE=$TOOLCHAIN_PATH- INSTALL_MOD_PATH=$MODULES_PATH zImage modules modules_install
[ $? -eq 0 ] || fail "Kernel compilation failure"

# copy all drivers to single level directory for compression
cd $MODULES_PATH
KERNMODS=$(find -name "*.ko")
for i in $KERNMODS ; do
cp $i $MODULES_PATH
done

# compress modules to a tar.gz and move to output
KER_VER="$(cat $KERNEL_PATH/include/config/kernel.release)"
$TOOLCHAIN_PATH-strip --strip-debug $MODULES_PATH/*.ko
echo "Outputting modules"
cd $MODULES_PATH
tar -cvzf modules-$KER_VER.tar.gz *.ko
mv $MODULES_PATH/modules-$KER_VER.tar.gz $ANDROID

# move new kernel
mv $KERNEL_PATH/arch/arm/boot/zImage $ANDROID/zImage-$KER_VER
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Hey, I added them for you - but always but any code snippets in

braces. Helps readability out a ton! Thanks.
[Touch Pro2, Tilt 2 Android Development] numero9:
All right, I did everything you listed and it is still giving me the SD card unavailable thing. I tried my original TP2 SD and it did the same thing. This is on all the newest kernel and GBX0c
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
If you weren't able to get it to recognize the SD card after a completely fresh rebuild, there's not a whole lot you can do. Unless you're not doing a full format, or you're not using the HP Tool, I can't really think of what else could cause that.

Does this happen on .27? I guess you have to stick to .27.
[Touch Pro2, Tilt 2 Android Development] numero9:
Yeah I'm doing a full format, the HP tool didn't recognize my SD cards for some reason (just direct from the phone not into my own computer's SD reader). So I used Windows's built-in thing and chose full format. Took a little under an hour, then I Titanium Backup-ped after downloading all the latest stuff from the forums. I guess that's the only other option I've got. For what it's worth, I've got a different data.img file in there since I wanted to use some of my 8GB card. I followed the instructions in the thread on here, and on .27 (and subsequently on the latest 3.3 or whatever's on the autobuild) it works fine -- recognizes the appropriate internal space.

Any idea on why the card isn't reading? All my apps work fine, it's just downloading stuff from the browser and the camera which are big things for me as a user unfortunately. I'm consistently pleased with the kernel progress and going back to .27 sucks -- but it's been acting this way on any upgrade from .27 for some reason, both on 2 different memory cards.
[Touch Pro2, Tilt 2 Android Development] CodaHighland:
Yeah, that doesn't work reliably. There's a reason we recommend the HP tool. I don't know what Windows does wrong but after formatting with Windows, some SD cards just become unreadable to a lot of non-Windows devices. Formatting it using a product that does it "right" (like the HP tool, but I believe mkfs.vfat on UNIX systems does it right too) yields much more reliable results.

If the HP tool can't read your card, there may be a bigger issue at play.
[Touch Pro2, Tilt 2 Android Development] numero9:
Thanks, I figured as much. I couldn't get either of them listed. I guess I'll try it again tonight.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
If you're on Win7, make sure you run the HP Tool as an administrator.

Otherwise, if the HP Tool can't see your card, that might explain why Android can't either lol.
[Touch Pro2, Tilt 2 Android Development] eik:
I am coming from the GBX0C thread... I tried 3.3 and 3.2.11 kernels. In both cases the brightness controls do not work for me. When switching back to .27 they do work. It may have to do with the beloved AUO/Rhod100 I have.

Logs at http://pastebin.com/4G4XKcnV.
[Touch Pro2, Tilt 2 Android Development] detule:
Alas, neither I or jonpry has 100, and I have no way of guessing if this is a panel issue or something else. Let me get a confirmation from another 1xx user that backlight adjustment does not work for them either and then I can try and take a look at the .27 panel code.

On another note does camera work for you?

Edit: One thing you can try re: backlight is:

1. Make sure Auto-Backlight is UNchecked in Settings->Display. Power the screen off and then on.

2. While the screen is on, in an adb shell:

# echo "x" > sys/class/leds/lcd-backlight/brightness

where x is a value between 0-255. See if the backlight on your panel changes.

(This is doing manually what android should be doing when you are using the slider in display settings).
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
Just loaded up the latest 3.3.3 from 04/29 and maybe it's just me and my set up but I seem to lose the taskbar using the latest, and I also consistently get a system force close/wait option. Just hit wait and it's fine from then on, except for the taskbar missing. Detule, is this something you want logs for? If so I'll switch back and reboot and grab them, for now I've just reloaded the 04/20 3.3.3 and it's fine.
[Touch Pro2, Tilt 2 Android Development] detule:
Hey so, this is unlikely a kernel problem. The taskbar missing, that sounds like some issues I've had with ADW in the past but it's likely contained to whatever launcher are you using. Can you try replicating it with zeam? FCs usually means your system is under heavy load, perhaps v6 time?

At any rate, the last few batches of commits that have gone into the kernel are all related to htc whitestone and don't touch any rhodium code. I will update the rhod code at some point this week, with the nand driver (fix for the wifi-nvram creation issue) and perhaps add bluetooth to 3.3 - this will happen when we update the tree to 3.3.4. Just need to test it on my device first for a day or two.