yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
It actually happens on Zeam and only happens on the latest 3.3.3 from yesterday. I'll keep flip flopping back and forth and honestly I did assume it was a launcher or other issue and not the kernel, but it seems like the only time I can replicate is with the latest kernel. I'll keep playing with it and will let you know if I find anything else. Is there a place to see what the kernel changes are, i.e. to see if it's for the RHOD, other than the link provided in the first post? BTW thanks for all you're doing for us on these phones!!
[Touch Pro2, Tilt 2 Android Development] detule:
Hey no problem - working on this for selfish reasons here, though my device is on its last legs. Besides, I came in at a point in time when jonpry and WisTilt2 had already done all the heavy lifting, I just try not to break things. The link in the first post is indeed the best source of info. Clicking on the "htc-msm-3.3" branch will bring up a list of commits. The last few read:

jonpry committed 6f904f4
Added wait to whitestone panel unblank

jonpry committed 743c05a
fixed panel gpio for whitestone

detule committed a106414
whitestone-led: Fix array indexing

detule committed a7232e0
whitestone: add gpio_keys per CptAjs findings

detule committed e7a2831
whitestone: i2c version: CptAj reports:

detule committed 552270f
whitestone: Add lcd backlight support

detule committed 50dead9
Revert "Remove fake vsync code. Runs off real vsync interrupts now."

The commit log (message) usually has some information about what that code snippet is relevant to.

There was a LMK commit that went in on APR21, but it seems pretty benign and it's an update straight from kernel.org (not something jonpry and I cooked up) so chances are it's probably not causing your issues. Besides, today I decided to update to the official gbx0c rather than my own patchwork build, and in the process must have put the build under serious strain - it handled it like a champ.

You can post getlogs output perhaps we can at least see what it is that's FC-ing.
[Touch Pro2, Tilt 2 Android Development] eik:
Pretty weird. It seems the issue is not as simple as I thought. i rebooted again into 3.3.3 and played around with brightness a bit. It seems it stays working for now. I suspect it may have something to do whether it starts up with auto backlight on (or not). I'll experiment a bit more :)

As soon as it stops working (if it does...) I will try your suggestion.

I hardly ever used the camera, but I just tried it out; took a picture or 10 and a few movies. All seems to work great.
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
Here's the logs. IDK if it's my getlogs app or what, as I think I've got the latest one out there but it wouldn't give me a pastebin url, so I hit just a file, copied and pasted that to pastebin and here's the link. If it doesn't have the relevant boot info let me know and I'll redo another log off of a fresh boot. Thanks! http://pastebin.com/zUXG7PxV
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
Yeah I saw a crapload of amazon garbage in there as well, so I tried the pm disable on that as well as some others. I forgot about the GoSMS in there so I'll junk that as well, although the pics show up a lot larger in Go SMS than the native app, but not a deal breaker. Not sure about Slacker although I wonder if I've just got the apk stuffed in there. I'll try cleaning it all up and give it another shot, and maybe I'll grab another sd card to play with, but like I noted earlier this is only happening on the latest 3.3.3 from 04/25 and not the one from last week. It's also the only one I lose the taskbar on, and it seems to have a bit of a slower wake time, but that might just be all the crap bogging it down. Thanks again for looking!
[Touch Pro2, Tilt 2 Android Development] highlandsun:
Hey, has anyone else tested bluetooth file transfer recently? On my 3.2.11 install it pairs with other phones OK but xfers always fail at 0% transferred.
[Touch Pro2, Tilt 2 Android Development] nickleby:
Same here! It's a pain to transfer a file to another bluetooth device...With kernel 3.3.3 is even more painful :(
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Pretty sure BT isn't enabled on 3.3.3 yet.

As for BT file transfer, I don't think that ever worked - at least I never got it to successfully work. It would pair, but never xfer... I only tried with a handful of devices, and never really looked into it very deeply.
[Touch Pro2, Tilt 2 Android Development] walter79:
Current Kernel Pack: kernel-pack-htc-msm-3.3.4-g8a97c2a-20120501_041820.zip

Built: Tue May 1 04:18:20 PDT 2012

GBX0C running:

- light sensor, backlight setting did not work

- speed is good
[Touch Pro2, Tilt 2 Android Development] detule:
Feel like I am repeating myself. Both work fine here.

And you didn't provide any logs nor did you list what device you are using.

Please follow the directions in the first post in detail when trying to submit bug reports.
[Touch Pro2, Tilt 2 Android Development] walter79:
Rhodium 100 de ? I will try with a fresh, clean install.
[Touch Pro2, Tilt 2 Android Development] detule:
Look one page back another 100 user had a similar experience as yours.
[Touch Pro2, Tilt 2 Android Development] walter79:
Ok. Backlight works now.

But there is no light sensor. Checked with GPS status tool.
[Touch Pro2, Tilt 2 Android Development] detule:
There is but the values are not reported to userland - nor does userland need them.

In this kernel and build, when we check the Auto-Backlight box, the screen automatically adjust the backlight based on readings from the lightsensor. These values are never reported to the user (nor is there a driver in the kernel to poll them), all adjustment is done on the hardware level.
[Touch Pro2, Tilt 2 Android Development] walter79:
Ok, on 2.6.27 kernel (nand) i can use light sensor in apps like gps status.
[Touch Pro2, Tilt 2 Android Development] x12CHRIS18x:
I just installed the kernel 3.3.4. I cant see my SD card, it doesnt let me overclock it stays on 528 MHz besides that its all good.
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
What do you mean see your SDCard? If you booted up Android then you can see your SDCard from within Android using a file explorer program, if you are talking about seeing the SDCard on a computer by USB sharing, then no you will never see that. Our build doesn't support it because we are running off the SDCard and not Nand.

You can push and pull files and install things from your computer with ADB though. You have to put the overclock settings in the startup.txt folder with a certain command. You can't use an app to do it. Please search the forum to see how to do it and the commands.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Sometimes the SD card will show "Unknown" in Settings. In this case, for whatever reason, I tell people to backup everything on the card, format HP Tool. Full format, FAT32. Then restore all your data - don't have to restart over with anything in that respect. Not sure why that fixes it, but that 'trick' usually does for whatever reason.

As for overclocking, .39+ has a different OC statement. When I used to OC, I had both statements in my startup.txt - have you checked that?
[Touch Pro2, Tilt 2 Android Development] x12CHRIS18x:
I haven't checked it but when I try formatting my SD card and if it works, ill check it.
[Touch Pro2, Tilt 2 Android Development] ObviousMan:
On my Sprint CDMA Rhod 3.3.4 would not even go through initial boot. I gets to the calibration part, but then it is stuck on "x same direction, y same direction" The previous version had worked for a while, but after 2 days everything would FS. And I mean Market, Gmail, etc. Not sure what is so different now.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Did you lose your ts-calibration file...?
[Touch Pro2, Tilt 2 Android Development] ObviousMan:
That was my 1st thought too. No it is safely there, same I used in FRX and 3.3.2 before. After I went back to 3.3.2 it had no problems. Makes little sense.

OM
[Touch Pro2, Tilt 2 Android Development] x12CHRIS18x:
Ok I just formatted my SD card and I still cant see it. I also still cant OC. Here is a copy of my startup.txt, I would upload logs to but I cant because the apk is in my SD card
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
You really looked hard for those OC statements, didn't you?

I said there's two different OC statements. One for .27, one for .39+. You have the OC statement for .27, so of course if you're on a .39+ kernel that statement WON'T WORK! Oy ve, hopefully that makes sense. You should bother reading the second post of this thread, it will help you sort out this issue (I hope :rolleyes:)

As for the SD card, dunno - I'd say it's a dying card, or you didn't format with the HP tool? Or you didn't do a full format? Not sure. This issue has always been an esoteric one, without a definitive solution - all I know is formatting fixes the vast majority of the problems people have with the "No SD Card" issue.
[Touch Pro2, Tilt 2 Android Development] x12CHRIS18x:
Sorry I forgot about that but I found. Do you think I should return back to default kernel or start over with the 3.3.4 kernel?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
In what respect? You can overclock at any time, assuming you use the correct OC statement.
[Touch Pro2, Tilt 2 Android Development] x12CHRIS18x:
I just started all over with the 3.3.4 kernel. The OC works now but I still cant access my SD card while in android
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Try my previous suggestions re: SD card not being found.
[Touch Pro2, Tilt 2 Android Development] x12CHRIS18x:
You mean formatting it? I already did that 2 times and it still doesnt work
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Specifically a full format, FAT32 using the HP Tool.

Since you didn't specify, I'm going to assume you're using the wrong utility - the built-in Windows and WinMo format utilities do not work!

The other suggestion I gave was try another SD card. At least I think I suggested that. If not, try another SD card :D.
[Touch Pro2, Tilt 2 Android Development] x12CHRIS18x:
I got it now
[Touch Pro2, Tilt 2 Android Development] ObviousMan:
@detule,

Does the latest 3.3.4 kernel (5/5 build) has BT baked in as you were saying few days ago or not?

I am giving it a try. So far replaced kernel/zimage leaving data.img from 3.3.2

Booted fine (for now). Have not tried wifi for previously reported issues, or BT yet.

Thanks for the update in either case.

OM
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
Have you read any of the threads at all? Wi-Fi is not broken. You need to boot with the original +.27 kernel one time so that it can generate the wifi-nvram.txt file in the proper location. Then you can switch out the kernel to whatever you want and wi-fi works great. +.27 kernel pulls your MAC address from your wifi and puts it in that text file the newer kernels do not automatically, but as long as you boot in .27 kernel (that was included with GBX0C build) and then replace the kernel after first boot up you are fine.
[Touch Pro2, Tilt 2 Android Development] detule:
No need to berate him -> it seems he has read the threads, since I believe I mentioned elsewhere that this fix should no longer be needed.
[Touch Pro2, Tilt 2 Android Development] detule:
Sorry, no BT yet, been sidetracked with other projects.

I did find a missing piece of google code that's relevant to how vold interacts with the partitions on the sdcard, so that's what the last commit is all about. So if you were having problems with your card not showing up in android - give it a go.
[Touch Pro2, Tilt 2 Android Development] detule:
BT in 3.3.x

Decided to push the BT patches anyways (*g69ce2c7) since I am not sure when I am going to have time to test them.

Hopefully you will find the functionality to be the same as in 3.2.x. If not, let me know and I'll see what we can do.
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
I wasn't trying to berate him, but wifi has never really been broken recently, and some people do not read. You just either had to do the .27 trick or now that you have fixed the other kernel (3.3.4 I guess since the others have not been updated in a while) having to do nothing special for it to work. I now understand the frustration that arrrghhh got sometimes with people (even me) for not reading the threads and keeping up to speed.
[Touch Pro2, Tilt 2 Android Development] ObviousMan:
The point is the WiFi does not work for me. The wifi-nvram.txt is in the proper location, and it has the correct MAC in it. Still, when enable wifi, nothing happens besides the checkmark appearing in the box. Even the icon in the notification area does not appear. I am going to try booting into .27 again, just to check, then maybe 3.2 then back to 3.3.4. Will report.

OM
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Try wifi in .27 for sure. Then come back to the newest, 3.3.4 as of this post. Make sure wifi works again. If it does not, install GetLogs and please pull some logs.
[Touch Pro2, Tilt 2 Android Development] ObviousMan:
I had exact same idea. First I went back to 3.2, no dice. Then back to .27, still no wifi. Blew away data.img, started with .27 Worked fine. 3.2 Worked fine. Latest 3.3.4 (today's commit) WiFi it is. Not sure what was the deal before.

Also tested the sleep w/ wifi issue - no problem, it goes to sleep, wifi goes inactive until awake. I have not tried BT yet which needs testing. Something to do tomorrow I guess.

Thanks for everyone's help.

OM
[Touch Pro2, Tilt 2 Android Development] motisu:
I tried the new kernel with the BT patches. As soon as I try to turn on the BT, phone freezes completely. Only way to recover is to pull the battery. Wifi and 3G work OK.
[Touch Pro2, Tilt 2 Android Development] ObviousMan:
My results using May 6th 3.3.4 kernel on Sprint CDMA Rhodium were identical. Freezes until the battery pull.

OM
[Touch Pro2, Tilt 2 Android Development] nickleby:
BT works "good" for me with 3.3.4, I'll say it works slightly better than 3.2.11... At least I could send/receive a file without troubles...Pair devices is still a pain tho.
[Touch Pro2, Tilt 2 Android Development] fortunz:
I pulled this out of the 3.3.x nand thread as it triggered a thought for me, though I'm using gbx. I started having non responsive backlight adjustment shortly after my last post where I thought it was fixed. I didn't bring it up because I didn't feel like messing with it much, I just tried different .39+ kernels from my archive going back to january, none worked. .27 used to work, but won't sleep, and I'd rather have backlight issues. But when I read the above quote, I finally thought to mess with the backlight in winmo before booting android -- it was set to auto-adjust, I flicked that off and lowered the level. I wasn't even really hoping to get back adjustment, I just thought maybe it would come on lower in android. But sure enough, it adjusts again, at least so far. Knock on wood.

I'm mostly just posting in case this helps someone else. I'm happy as a gopher in soft dirt again. If this has already been documented somewhere I should have read but didn't, opps in advance. :o
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I don't know if it's really "documented" anywhere per se... this was an old issue that was resolved with .27. Perhaps that patch never made it into the newer kernels? I know for a long time we told people to disable autobl in WinMo, but that was at least 6 months ago. That "bug" has been fixed for a while, again in .27 at least.
[Touch Pro2, Tilt 2 Android Development] Stijnjits:
Hmm, upgrading from 1 may tot 6th may 3.3.4 kernel seems like a huge battery improvement here!
[Touch Pro2, Tilt 2 Android Development] numero9:
For what it's worth, the latest Kernel fixed my SD card recognition issues. First one to do that since .27 or whatever the original bundled one was. Battery life has improved quite a bit too but the other night it lost data/phone randomly overnight which kind of sucked waking up to...but so far, so good though.
[Touch Pro2, Tilt 2 Android Development] ObviousMan:
Tethering worked fine on the latest 3.3.4. No issues when shutting it down too.

I also tested the camera today with the kernel from 5/6 3.3.4 on Sprint CDMA Rhod. The camera app shows up, you can zoom, etc. until the picture is taken. Then the phone requires a battery pull. No picture is written to the card, waited for about 5 minutes. Not sure if anyone else experienced this.

OM
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I assume GBX0C? Hard lock, screen freezes on? No adb?
[Touch Pro2, Tilt 2 Android Development] ObviousMan:
You got it, hard lock, screen frozen on the last image camera was pointed on, no ADB. I thought this was fixed in previous builds, may be it had not made into 3.3.4

Having 30 spare minutes on this fine Mother's Day (Shout out to all Moms that may be hanging out here) testing 3.3.6 that got autobuilt today. I've just updated from 3.3.4 on the existing data.img

So far tested that was not working in 3.3.4 of 5/6

BT - placed 3-4 calls, although after the reboot it did not find the paired headset which was next to the phone. After the next reboot, it took 3-4 minutes after the homescreen showed up for the device to connect to headset. Overall seems the same behavior as the initial version of 3.3.4 (before detule baked in BT code he could not test) - If you get BT up the 1st time (enable when inactive at boot, or booted active) you can make/receive calls with it. Then if the connection goes inactive due to sleep, airplane mode, device being outside the range for a brief time, etc., once you try to get it reconnected (disabling airplane mode, etc.), or it tries itself (like after it wakes up after deep sleep) - you get the hard freeze, screen locked , no ADB. So I presume BT is a no go at this time and disable it until someone tells me different.

Camera appears to work. I've taken 3 pictures fine, written to card, etc.

Sleep appears to work, BT and wifi go inactive.

Boot seems to be slightly faster than in 3.3.4

Have not tried to do anything with tethering. As I posted separately, you can even "kind of" play Angry Birds when OC'd to 710 with background disabled, if it loads before screen goes off.

OM
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
Does the new 3.3.6 kernel have all the battery goodness from ACL's NAND kernel rolled into it? I see the commit entry that things were rolled in from ACL's kernel, but I was unsure if that included the more accurate battery code, and if that code would actually work with haret builds?
[Touch Pro2, Tilt 2 Android Development] detule:
Just pushed a nice patch from ACL:

We are no longer over-clocking via a command line parameter. Rather, you can use userland apps like SetCpu, AnTuTu CPU Master etc.

Let me know if I broke something.
[Touch Pro2, Tilt 2 Android Development] Eric Z:
Dear Detule:

Arrrghhh said that I might post this problem here instead in the GBX0C thread, so here is the problem:

I have clean GBX0C(that is, everthing from Arrrghhh's GBX0C package) on SD, with no change/add to startup.txt, and I have Rhod 100. It boots and runs fine expect a wired wifi problem which I already posted it on GBX0C thread. The thing is, that 3.x Kernels can not boot on my phone. They all stop at the "nonexistent dictionary" line, where the process normally shall just pass on. But, if I have a data.img file created by booting with .27 kernel completely, and then switch to 3.x Kernels WITHOUT deleting the data.img file, then they all run fine. 3.x Kernels don't pass the "nonexistent dictionary" line, if the data.img is created when booting with 3.x Kernels.

Is my description clear? Do you need Logs? if logs, how shall I do it because the phone doesn't even finish the boot process?
[Touch Pro2, Tilt 2 Android Development] Eric Z:
Detule, Please just ignore my previous post about the boot issues.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Now I'm curious, what was the issue?
[Touch Pro2, Tilt 2 Android Development] Eric Z:
I was just given up with Android on SD, but now you ask, so her is the issue:

Boot with .27 kernel no problem. But can not boot with 3.x kernels.

If I have a data.img, which is created when the phone boot with .27, then 3.x kernels boot with no problem.

If I delete the data.img, and boot with 3.x kernels, then under the process a data.img will be created, but process will later stop at a "nonexistent dictionary" line and can not proceed.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Oh, so you didn't solve anything... Bummer :(

I remember this issue, I thought you were saying it was fixed... Oh well. Good luck.
[Touch Pro2, Tilt 2 Android Development] Eric Z:
No never fixed:o

None of the two issues(the one with Wifi and this one) I have luck to get it fixed. But this one is actually not a big issue. The Wifi problem is killing me:(

I ask Dutel to not pay attention to this any more only because I decide to move on to NAND.:p
[Touch Pro2, Tilt 2 Android Development] cameraddict:
Help with kernal install

Hi all.

I had been using FRX07.1 since November'11. I decided to move up to GBX0C. It works fine. Except for battery drain issues. So I went looking for a solution. Seems that the newer kernals do a lot of good, including fixing battery drain problems.

Problem is, I have scoured this thread and the GBX0C thread, and although I can find the kernal repository just fine and download a file, I have no idea what to do with it! And yes, I've tried searching.

From this address I downloaded the following file:

https://gitorious.org/linux-msm-rhod/linux-msm-rhod

linux-msm-rhod-linux-msm-rhod-htc-msm-3.3.tar.gz

using 7-zip, I extracted the archive... but now what?

Any help would be greatly appreciated!
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
Look at the first page of this thread and find the link to the AutoBuild Service for the Kernels. Once you click on that link it will take you to the download links to the kernel files. I would use 3.3.6 (the last one on that page). Once downloaded, unzip and replace your zimage with the one in the zip file and delete your other modules file in your build and replace it with the one in the zip file. Then boot as normal.
[Touch Pro2, Tilt 2 Android Development] cameraddict:
Thanks for the fast reply.

I followed the wrong link the first time 'round. Let's try this again... thanks!

---------- Post added at 11:58 AM ---------- Previous post was at 11:46 AM ----------

Phone is booted with 3.3.6 now! Testing testing testing. Will report any issues that come up.

Thanks again!
[Touch Pro2, Tilt 2 Android Development] ObviousMan:
Don't hesitate to flame if it is really a stupid question:

I see the 3.4 branch created, and a couple of bug fixes pushed to it already, but nothing is showing up in autobuild. Is it for a reason, or something hung up in autobuild?

Thanks.

OM
[Touch Pro2, Tilt 2 Android Development] wizardknight:
Well it was only created ~ a week ago. I am sure we will see some 3.4 action as soon as they make enough changes to make worth releasing.
[Touch Pro2, Tilt 2 Android Development] CodaHighland:
To answer the question itself, the autobuilds have to be configured on the server specifically for each branch that wants to be tracked. New branch means no autobuild.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
You can always compile the kernel yourself!
[Touch Pro2, Tilt 2 Android Development] ObviousMan:
I thought of that, but no compiler currently...

I was looking for CodaHighland answer, as I suspected something like that.

Thanks everyone for education.

OM
[Touch Pro2, Tilt 2 Android Development] Caldair:
For anyone interested, here is an informative (and entertaining) blog from a recognized kernel developer outlining some of the trials and tribulations faced when compiling kernels for existing devices like ours. Basically if everyone worked together this could be a much simpler process!

http://allsoftwaresucks.blogspot.ca/