yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] detule:
This kernel is in its infancy, (it's only a couple of weeks old as Linux kernel, let alone as a kernel adapted for rhodium). Having said that, in very limited testing there are no immediate problems with it and this is why it made it to the auto-build.

Feel free to use it but if you wish to report a bug do the following:

0. Include GetLogs output of the problem (or it didn't happen).

1. Include Rhodium model (100, 210, etc).

2. Try to reproduce the problem on 3.1 and .39 (no need to try 3.0).

Sure. If you do so, as always, include GetLogs output, as well as make/model of Bluetooth device used. Also, as mentioned in the first post, it would be very helpful, if you could say how your experience compares to .27 with regards to BT under same circumstances (same BT device etc). Or rather, just include the .27 GetLogs output as well.
[Touch Pro2, Tilt 2 Android Development] ryannathans:
Does anyone else's wifi work in 3.0?

I have been on 3.0 for a while now and I've never been able to connect to my wifi, it turns on but just won't connect. (wpa2)

Just updated to latest 3.0

If I haven't overlooked something I'll post logs tomorrow if i remember. Wifi can still be used for location though. (finds networks)

Roar and goodnight :p
[Touch Pro2, Tilt 2 Android Development] detule:
md5sum /etc/wifi/bcm432x/bcm4325*

Should be bca2*

If not, follow the directions here.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Or just make sure you're using a rootfs from my GBX0B build ;).
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
Grabbed the 3.2 kernel today and tried it out. Seemed nice and snappy but when I shut my kb the phone rebooted (this is a phone issue, NOT kernel issue) and when it booted back to GBX everything was FC'ing, so I tossed the data.img and restarted from scratch but the flying text kept getting stuck saying there was something missing, although I didn't write down what it was. So I tossed .27 back in and rebuilt with that.

Is this is known issue and if not, do you want me to copy my .27 data.img and try to reboot again with the 3.2 to let you know what the line said?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
So you're saying that 3.2 doesn't create a new data.img or...? I don't quite follow.

I have seen boots fail, and a new data.img was the only option. This seems to be a new thing with acoustic - lots of services dying, etc.
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
It did create a new data.img, I found this out after I rebooted back to Winmo. The phone got borked for some reason or another, so when I tried to create a new data.img using the 3.2 it failed to boot fully. When the text was still scrolling it stopped on a certain line, and my like a moron didn't write down what it said, other than something was missing. So I basically tossed the data.img that was I assume partially created, and started over with the .27 kernel. I'm still working right now but if I get a chance later tonight or over the weekend I'll move the data.img I just created with .27, put the 3.2 back in and try to create another one. If that fails I promise to take my dunce cap off and note exactly where it gets stuck. Completely OT but sad to see you give up your RHOD, although for our sake I hope you keep doing what your doing!!
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yea, I'm not going anywhere anytime soon. I kinda had to do it too - I couldn't turn my back on getting paid just for having the phone....

Good luck with the testing!
[Touch Pro2, Tilt 2 Android Development] ryannathans:
48a36f22412ec284088bc4ea1552e795 bcm4325-rtecdc.bin

Woot, the new driver works nicely!

Wifi, here I come!
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
wtf, are you not on my rootfs? You're on GBX0B right?

My rootfs handles this firmware flip automatically, as I already said :rolleyes:.
[Touch Pro2, Tilt 2 Android Development] ryannathans:
I intended to use yours all the time, turns out I have a rootfs partition and your rootfs.img file just wasn't being loaded ;D

I moved your rootfs to the correct partition and its working smoothly.
[Touch Pro2, Tilt 2 Android Development] detule:
usb tethering

Anyone care to test usb tethering on 3.0/3.1/3.2 (make sure you download fresh from the autobuild).

I have it working for me in Linux (fedora), but another confirmation would be helpful. Also it probably needs testing in Windows. If it fails for you make sure you provide GetLogs output.

Thanks
[Touch Pro2, Tilt 2 Android Development] boggsie:
I have kernel-pack-htc-msm-3.0.18-gef3018d-20120128_163214 loaded up and everything (bluetooth w/ Jawbone) works wonderfully - except connecting via USB (not tethering).

I have a Win7 x64 desktop.

I connect to USB.

In Android on phone.

The status bar updates to indicate that USB debugging is connected.

The status bar updates to indicate that USB mass storage is available.

Open the notification list and select the USB mass storage option.

I click the button to Turn on USB storage.

On the Win7 x64 desktop.

Device manager updates to indicate that ADB Interface is connected. (HTC Dream Composite ADB Interface)

My Computer updates to indicate that Removable Disk (Drive I:) is available.

If I click to open or browse the I drive, I am prompted to please insert a removable disk.

At this point, with this status, on the Android device, the USB connected window is open with the circle (working meter) spinning.

I have waited as long as ten minutes and the connection is never completed to the point where I can browse the Android drive from the Win7 x64 desktop.

At that point, I pull the usb cable and pull logs.

Best regards,

-boggsie
[Touch Pro2, Tilt 2 Android Development] boggsie:
Hey, thank you again for contributing your time as a volunteer (developing, packaging updates and testing) so that I can continue to use my >2 year old phone in ways that GOOG, HTC and MSFT never dreamed imaginable.

I wanted to check to see if the newly added 3.2 included bluetooth support? This seems to indicate that it wouldn't, but as 3.2 was added to the mix AFTER the op was originally written, I thought I would ask.

Best regards,

-boggsie
[Touch Pro2, Tilt 2 Android Development] detule:
Excellent, I've been waiting for feedback re: bluetooth - since it seems to be working fine, I'll see into adding it to 3.1 and 3.2 soon.

It seems you are trying to make use of the mass storage functionality? Why? adb push/pull works magically well. I recall arrrghhh saying at some point that droid explorer(?) has the ability to mount /sdcard somehow via the adb protocol? Don't know, windows is pretty mysterious to me.

You are probably aware of this, but mass storage does not work on haret unless you are using a partitioned build.

Having said that, I use gbx on ext4 partitions, and mass storage works. There seems to be an issue when turning mass storage OFF, some message about a blank SD card in the taskbar - but I am not quite sure what are the adverse effects of this (if any). Probably one needs to manually remount the relevant partition to /sdcard.

Also, in general, usb functionality seems to vary depending on the OS of your host machine - as I don't have a windows machine I have no way of figuring out what's happening (hence, asking about usb tethering feedback on windows machines).
[Touch Pro2, Tilt 2 Android Development] detule:
No problem, I am similarly motivated by very selfish reasons and wanting to extend the lifetime of my rhodium. Having said that, there are others (jonpry, WisTilt2) who deserve most of the credit with regards to +.39 kernels, as they are the ones who did (and still do) the heavy lifting to get these kernels off the ground.

Right, still no BT in 3.2. I'll add it first chance i get to cherry-pick the commits from 3.0 since it seems to be working well over there.
[Touch Pro2, Tilt 2 Android Development] boggsie:
Ignorance and maybe a little bit lazy. :o

Off to fix the ignorance portion of above with a search for droid explorer!

ty, tyvm :cool:

I felt especially lazy after my post asking about BT in 3.2, so I loaded up the kernel and confirmed that BT wouldn't fire up, just didn't make it back in time to update my question.

I'm looking forward to it. Thank you, again.

Best regards,

-boggsie
[Touch Pro2, Tilt 2 Android Development] ryannathans:
You seem to have tethering (the act of using your phone as an Internet modem) mixed up with using your phone as a mass storage device ;)

My RHOD is out of action since NAND killed it, won't even charge properly. I don't know how I'm supposed to flash a winmo rom when it won't even charge to get enough battery to do so
[Touch Pro2, Tilt 2 Android Development] boggsie:
Just a follow-up here; Droid Explorer FTW. :D

Download x64 install package.

Run the installer.

Point it to the SDK folder.

Browse your Android device.

Thanks for the pointer, detule.

Best regards,

-boggsie
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
OT to this thread, but you should be able to charge with the device off. Otherwise you have to a) find another device to charge the battery with or b) use an external battery charger.
[Touch Pro2, Tilt 2 Android Development] hashtowent:
just give that a try:

put in battery

connect usb (assume activesync is installed)

press volume down

phone will power on in bootloader (tricolor)

pull battery

should stay powered by usb!

please report if thats working ;)
[Touch Pro2, Tilt 2 Android Development] detule:
If only I had the power to ban people.
[Touch Pro2, Tilt 2 Android Development] boggsie:
Lots of calls on BT over the past couple of days. I had several calls on each day > 45 minutes and did not experience any lockups, crashes, or reboots.

I even took some time to test out voice activation. Tap BT headset, hear tone, call out request "Call Home" ... it works.

Good stuff, for sure; At least with my Jawbone!! :D

Best regards,

-boggsie
[Touch Pro2, Tilt 2 Android Development] bryanwieg:
I can confirm that on the partitioned build, after getting done with mass storage, and disabling it, the taskbar says the sdcard is missing. I can only fix it by restarting the device.
[Touch Pro2, Tilt 2 Android Development] boggsie:
I have kernel-pack-htc-msm-3.0.18-gef3018d-20120128_163214 loaded up and everything (bluetooth w/ Jawbone) works wonderfully.

Today I had a lockup.

I was in Market in the midst of an application update. I had WiFi and BT on, but was not talking at the time. Immediately prior to the update, I was on a 45 minute call via BT, without any issues.

At the point of the lockup, I was in Market and I couldn't get the phone to respond.

I plugged the phone into USB, but ADB never recognized a connection so I was forced to reset the phone via switch..

I opened SYSTEM_LAST_KMSG@1328205677078.txt and it is not a readable file ... lots of gibberish or machine language.

Best regards,

-boggsie
[Touch Pro2, Tilt 2 Android Development] pipokitas25:
hello,

I have the HTC touch pro 2 and have tried the various kernels available here in the forum and what happens to me is that bluethoot works or not or when I want to make two calls at the touch off my phone and continue playing where I called.

Does anyone can help me?
[Touch Pro2, Tilt 2 Android Development] pfc_m_drake:
I think he accidentally his verb. :)
[Touch Pro2, Tilt 2 Android Development] pipokitas25:
I'll try to explain what is going on with the HTC TOUCH PRO 2:

When making calls to another mobile phone from my mobile phone the call sign two times and disconnects the call automatically.

Although off the call continues to call on another phone for which I made the call.

Then the kernel in question sometimes puts bluethoot working sometimes not.

Have they ever happened to anyone?

Someone could help me these questions?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
What is the kernel in question?

Do you have these problems on .27?

I think I finally understand the issue - you can't make outgoing calls, it just makes the 'call disconnected' 2 beep on the phone, but the call continues to go thru to the far-end... haven't heard of that before.
[Touch Pro2, Tilt 2 Android Development] eurohunter:
I am trying the kernels, but they seem pretty much the same (expect for that BT from what I've read). so, if these kernels are maintained by the same group of people, and they differ very little, why not focus on just one? am i supposed to test a certain kernel depending on the type of rhodium that i have? I am confused. :)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Any kernel works for any RHOD... .27, .35, .39, 3.0, 3.1, 3.2... perhaps 3.3 soon :p.

The kernels are newer, but there's a lot of code specific to our devices that is the same. Some of the code is different, but a lot of that is on the back end and a normal 'user' shouldn't notice the difference.

Perhaps enjoy the fact that you can go to 'about phone' and see you're running a kernel 3.2. I'm not aware of too many native devices that can say that ;).
[Touch Pro2, Tilt 2 Android Development] wizardknight:
I seem to be having issues over clocking using the startup.txt file. I made the change noted on the first page, but my apps still show the 528 max speed. It also feels like I am running at that speed. I am using kernel-pack-htc-msm-3.0.18-gef3018d-20120128_163214 on GBX0B_Full_Bundle_2011.12.30. I attached my startup.txt file here. Could someone double check it, and make sure I am not missing something obvious.:p

Thanks
[Touch Pro2, Tilt 2 Android Development] Chatty:
Those test kernels don't support DIAM100 whereas 2.6.27.46, which comes with GBX0B, works fine.

Haret loads the kernel, then the screen turns black and a few seconds later the device boots instead of showing the boot up messages.

Can DIAM100 be supported again? How may I help?

BTW: "works fine" means I can connect to my WPA2 network, but gsensor is upside down (but I have to touch what can be seen). So when I headstand I can use it... ;-) For GSM/3G to work I had to enable & disable flight mode. I can see visible BT devices - didn't try any pairing yet. I cannot be heard in a call, but ear speaker and loud speaker work as expected.
[Touch Pro2, Tilt 2 Android Development] detule:
Have you done much kernel work? It wouldn't be hard (no "new" code needed, just need to port some device drivers from .27 and write a board file or two) if you know what you are doing, otherwise it would be a very large undertaking. In either case it requires time and DIAM device, and I don't have either.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
The overclocking statement for .27 and .35+ are different.

Edit - although it looks like you're using the right one for .35+. When I was overclocking I had both statements in there. No harm.
[Touch Pro2, Tilt 2 Android Development] Chatty:
@detule: You seem to not read your PMs. I know how to code and how to use git/svn/etc. So please gimme a hand on what to do...
[Touch Pro2, Tilt 2 Android Development] detule:
Yeah i've been keeping busy with some non-kernel work.

First thing's first. Clone the git repo in the first post and make sure you can compile the kernel (we use msm_defconfig for config). After that, you can look at the commit history in the .39 tree to try and trace some relevant commits (i can point you in the right direction with this). At one point jonpry made .39 topaz friendly so those commits should be helpful. You can find me mostly on #xdandroid.

Before you get going with this, you should also be aware that there is a good chance that making the 3.x kernels diamond friendly will take up more time than it's realistically worth it, and there is a good chance it will never happen -> only do it if you are in it to learn something, not because you have expectations of actually making it happen. It seems to be the reality of where things are headed as more and more developers abandon the project.
[Touch Pro2, Tilt 2 Android Development] wizardknight:
I am not sure what went wrong, but I did a clean rebuild and it is working now. :D
[Touch Pro2, Tilt 2 Android Development] JDog2pt0:
Not sure what's going on. For a while there I was focusing a lot of time on my phone, then I switched back to messing with Ubuntu on my laptop, and now that I've got everything set for the time being, I'm going back to my phone.

Anyways, having an inconvenient issue. Almost every evening, (~12 hours of on time) my phone either dies or sod's. As far I can tell, I'm having both issues. Generally if it's in my pocket it will die. Sitting out all day and it seems to sod.

So, the pocket issue never occured with foryo. In my pocket most of the time it dies, but I have had it sod on occasion. And sitting out it sod's and dies on occasion. This has persisted across 3.1 and 3.2.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Is this only 3.x? Have you tried (and been able to recreate the issue on) 3.0, .39 or the dreaded .27?

Just curious. You probably weren't running 3.1/3.2 on FroYo ;). Are you in poor service areas? Some people still have issues with poor service areas, and usually disabling only data at least prevents the SoD's. Something to keep in mind.
[Touch Pro2, Tilt 2 Android Development] JDog2pt0:
Yeah, I'm a poor service area alright. *scratches head* It'd sure be nice if there was a program to disable data when certain condition were met, e.g. poor data. Ah well, I'll see about putting a shortcut on my home. Thanks for the info, I'll test all the other kernels over the coming days *without* disabling data. Maybe I'll get one of those wifi phone boosters, if Verizon offers them.
[Touch Pro2, Tilt 2 Android Development] eurohunter:
is it just me, or the ringtones don't play when receiving calls using the new kernels? with .27 everything is great. when i switch to 3.0, 3.1 or 3.2, ringtones do not play. i got the kernels from the website shown in the first page, and i just copy/pasted the two files (zImage overwritten).
[Touch Pro2, Tilt 2 Android Development] detule:
It's just you.
[Touch Pro2, Tilt 2 Android Development] numero9:
At the risk of sounding really stupid -- I tried all three of these kernels and none of them would load.

Everything was working fine from the GXB2.3.7 thread that I was using. I replaced the two files on my SDcard from the zip files from the kernel. I tried the kexec method but it boots up again to WinMo. So I just connected my phone when in WinMo and deleted the old zImage, etc. and replaced them with the new ones.

This method seemed to work fine when I was updating the kernels in the Froyo builds a while ago, but now all three just get stuck on the black/white boot screen.

I've got a Sprint Touch Pro 2 -- am I missing something completely obvious or is there any reason that any of these kernels just wouldn't work like this?
[Touch Pro2, Tilt 2 Android Development] detule:
3.2 has Bluetooth. It's the same patch-set as what was reported as working in 3.0.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
So .39, 3.0, 3.1 and 3.2 all do not boot?

If you've replaced a kernel before, the process is the same. Remove zImage, replace. Repeat for modules. Make sure zImage is named... zImage.

Make sure you're using EVERYTHING from the GBX0B build. The HaRET.exe is different and so are the startup.txt's. If you don't have the startup.txt entry and the proper HaRET, you won't be able to boot.

Although your issues don't sound related to that... perhaps try on a fresh data.img? I'm not sure without seeing what is actually going wrong.
[Touch Pro2, Tilt 2 Android Development] Chatty:
@numero9: What device are you using?

2.6.27 supports a whole lot more devices than these new kernels (Diamond is no longer supported, for instance).
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Should work great for TP2's.

Chatty, this is the TP2 section. Just sayin'. Not like we're posting this stuff in the DIAM section lol.
[Touch Pro2, Tilt 2 Android Development] boggsie:
Shenanigans (just sayin') - they all three boot fine for me on the SD build of gingerbread. I need bluetooth support, so 3.2 is my daily driver.

Best regards,

-boggsie
[Touch Pro2, Tilt 2 Android Development] numero9:
I don't doubt they work, I'm just trying to find what I'm doing wrong.

I wiped my card clean after getting rid of Froyo, then followed all the instructions on the GBX thread. Everything went fine and as expected.

I'll try again later tonight to replace haret. Is there anyway to back up everything so I don't have to re-install every application I downloaded? Doing that after deciding to format after Froyo was a long mistake I don't want to repeat downloading all the apps.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
There's many ways to backup apps, but that's really on you. Titanium Backup seems to be the most popular.

You can also copy your data.img, but this isn't so reliable.
[Touch Pro2, Tilt 2 Android Development] numero9:
Thanks, it seems these kernels are stalling out and giving a panic saying "not syncing: VFS: Unable to mount root fs on unknown-block(0,0)" then listing a few more lines then just stopping.

I tried replacing the rootfs file with the one in the original GBX thread and still no dice. I'm just gonna backup and wipe clean.

Edit: Okay, got it working after wiping the SD clean.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
The phone still locks up on me when I plug the USB cable in. Using latest 3.2 kernel now. I see the "USB Debugging connected" line in the status bar, and then it's dead.

Hm, and Caps and Alt lights aren't working. Is this still kernel side, or should it be userland now?
[Touch Pro2, Tilt 2 Android Development] highlandsun:
And wifi isn't working for me either. It sees networks, but times out when associating. I see a couple warnings in dmesg, not sure how significant they are.

(See attached dmesg)
[Touch Pro2, Tilt 2 Android Development] detule:
I have had this happen to me as well. These kernels have an updated usb stack, and to me it seems more finicky. I will say that, using the OEM usb cable that came with the phone seems to notably reduce the incidence - so much so that I have thrown out all other cables. (This though could be a function of the fact that my usb port has been on its way out for some time). Also, turning the screen on before plugging the cable in seems to help, which in turn could point to some of the PM/IDLE collapse code. Don't know. I will say that to me it doesn't happen more than perhaps once a week (if that), and I use the usb port perhaps more than the average user.

It's userland. They work, as long as whatever app you are in is using the correct meta-key-listener class. For example, they'll work if you are typing in the search bar, but not in ConnectBot. Oh yeah, and you need up-to-date rootfs with the correct permissions in place.

Sounds like you aren't using the bundled rootfs. The new kernels depend on updated tegra wifi firmware. Arrrghhh put some fancy logic in the bundled rootfs to detect which kernel you are on, and copy over the appropriate firmware. But yeah, make sure the md5 matches the md5 of the firmware here.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I found in .39+, you basically HAVE to turn on the screen before plugging it in. .27 I didn't have this problem, but it didn't wake correctly either (except on NAND :rolleyes:)

So hyc, make sure the screen is ON before plugging in that cable...

To both these points, there's some stuff I've asked to be committed to the autotbuild rootfs that hasn't been. I think at this point I've submitted all my changes to the rootfs.

The LED stuff should be in the autobuild rootfs, but the "fancy" firmware switch is only in mine (for now) ;).
[Touch Pro2, Tilt 2 Android Development] highlandsun:
OK. I was mistaken about the Caps/Alt lights - yes they work, just not in Connectbot, as you said.

I am definitely using the bundled rootfs. This is a different SDcard from my FRX image, and there's nothing else on it.

Screen is on when I plug in the USB cable. Like I said, I can see the "USB connected" message in the status bar just before it dies. (Sometimes. Sometimes it just dies with no message.) And yes, I'm using the HTC cable, and yes, my USB port is pretty worn out, for the same reasons as yours no doubt.

Will check the firmware hash and come back later...