yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
Arrrghhh, don't know what happened, but I f'd my phone up good lol... Getting a new one soon hopefully... (I can assure anyone wondering... it's not the builds fault the phone is tweaked...)

Now onto my other issue... running GBX on my kids phone, ear piece speaker won't work worth a damn. Speaker itself works and you can hear everything, but nothing I've tried has gotten to earpiece to allow you to hear anything. Tried making a call to my house today, still didn't work, turned speakerphone on, worked fine, turned back off and still nothing through earpiece. Still on stock .27 kernel. Grabbed logs for you to see if anything jumps out. And I grabbed all the csv's that you attached too, so it should be basically just 100% stock build, no OC, nothing.

Thanks!

http://pastebin.com/xFu1eECU

Here's another set of logs after testing on an incoming call. call received around 11:20 AM EST, answered call, earpiece doesn't work, toggled speaker on, worked fine, then tried earpiece again still without good results.

http://pastebin.com/tSvJdZck

Thanks again
[Touch Pro2, Tilt 2 Android Development] XDAcelt:
Thanks arrrghhh and abdelgni.

I didn't know that Total Commander would obscure some files. My desktop probably *does* have some files hidden so I'll uncheck that box and see what I find. If nothing is there, I'll use the files that abdelgni was nice enough to attach here.

For what it's worth, arrrghhh, I'm currently using EnergyROM.

Thanks for the reponses.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
lol, not even going to try and address this one eh? PM me if you want.

Before I even look at logs, does it work in WinMo? Have you had issues with it in FRX? Thanks.
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
I honestly don't know what happened, battery died and phone will no charge, will not boot, will not do anything. Tried hard resetting, tried different good working battery, tried everything I could think of. Flashed stock rom, etc. Nada, zilch, nothing... phone is is a boot loop in winmo and won't even get to the winmo screen. It's been acting funky lately, when I closed the kb at times it would reboot. but something happened last night when the batt died that completely screwed it. Tech at the store couldn't figure it out so they ordered a new one. That's why I stated it had nothing to do with the build to anyone reading the post.

As far as the speaker issue, works fine in winmo and FRX7.1, no problems whatsoever, at least not speaker related. But I can constantly re-create the problem in gbx, but it seems like for his phone only, because when mine was working right, I never had that issue. I've tried every little thing I can think of and nothing is working on it. So I grabbed the logs to see if the genious' can figure anything out. As I noted before, I'm using the .csv's that you posted which are the same that I'm using. And if I boot with FRX the speaker works fine, so I've gotta believe it's something I've done or something just acting funky on his phone.
[Touch Pro2, Tilt 2 Android Development] XDAcelt:
Following up to the missing CSV files: They *were* hidden. Thanks for the help.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Ouch! Good luck man...

Interesting... I'll see if anything jumps out in the logs, that's strange for sure.

Edit -

02-02 11:20:42.862 INFO : htc-acoustic_wince: update_hw_audio_path: mic=1, dual_mic=0, speaker=0, headset = 0

It's routing the audio... nowhere?

Then, about 10 seconds later:

02-02 11:20:52.009 INFO : htc-acoustic_wince: update_hw_audio_path: mic=1, dual_mic=1, speaker=1, headset = 0

It's routing correctly out the speaker. Why, is the question I cannot answer. I'll see what I can dig up.

np, glad you figured it out.
[Touch Pro2, Tilt 2 Android Development] pipokitas25:
And call is normally?
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
Arrrghhh, got my new phone, trying it out for a few days before I unlock and update to latest VZW radio. On another note regarding my sons phone, seems like it IS a hardware related issue, sounds to me like a loose connection to the earpiece which just recently started as it's hit or miss and a lot more noticable in android as he's using it as a daily driver and it didn't happen previously in winmo. It happened to have really started almost continuously failing after I switched a kernel but can be replicated in winmo as well, but like I said it was hit or miss and didn't happen the 2x I initially tested in winmo, but after constantly pissing the wife off by calling the phone to see if I could hear her answer (she freaking snapped on me after about the 15th call, although she kept answering lmfao) I realized it was indeed a hardware issue, so he's got a new one coming as well. Sorry about the wild goose chase, but I swear I did attempt to narrow the issue down first!!
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
lol, no worries mate. Hardware issues are some of the most troublesome to track down - especially since no one ever wants it to be a hardware issue.
[Touch Pro2, Tilt 2 Android Development] jonners59:
Hi guys

OK, found a little time over the weekend to try and get things sorted.

Copied the contents of my SD card to the desktop of my PC and then re-formatted the card. I copied all back on except the GB data.img

Put a new data.img on to the card and rebooted.

Tried my fully working Frayo 7.1, but that would not boot - oh, hell - not for this thread, but it got me straight on to the GB build.

Rather than use Titanium to re-install all my apps, I just used it for a few critical one - 3 or 4. I used my app brain to download all the apps and install so they matched the machine - so far looks good.

For now, though I have installed the Go Launcher and it's accompanying tools, I am not going to use it. just to check out if my gut feeling that the problems I have had were related to not enough umph in the machine to run it.

A couple of things I have noticed, that may well be normal. Just need clarification.

Always get a message that "process system" is not responding after boot.

The "Superuser" app will not upgrade. Says it needs to but fails.

Other than that, so far, seems Grrrreatttt!
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
All those words and these are your questions... Oy.

Sometimes you'll get wait/force close messages. That's usually an indicator that a lot is going on in the background, and you should probably wait. Since you said after boot, that probably means the phone is still booting, right? Right.

Superuser won't upgrade on its own. If you look at the 'related apps' to SU (scroll to the bottom of the SU upgrade...) and you'll see a SuperUser Fix app. Install that, and SU can be upgraded. I tried to roll this in, but it wasn't feasible. I guess I could roll in the fix app, but then I'll just get questions on wtf is this app doing etc...
[Touch Pro2, Tilt 2 Android Development] jonners59:
CHeers arrrghh

I thought as much. I also get the same for Launcher, which is why I think that Go caused all my probs. I think it is a great launcher, but too hungry to work on the build.

Bar an issue I had after a missed call (the phone was making a lot of noise and was not responsive, requiring about 3 reboots to get working), bar that she has been working a treat.:D That also got me to notice it does not like a reboot with WiFi on. It would not activate the radio. Lesson lernt.
[Touch Pro2, Tilt 2 Android Development] jonners59:
Great. Worked a treat......:D

I'd rather give the picture of how I got to where I am, it may be a clue to what went wrong and an aid to others.

Do you know an app called SD Boost... If so, does it actually work/do anything???? Says it boosts SD speed by x40.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
It's in my speed improvements thread (you've read that right?) So yes... I encourage you to read the first post from that thread.
[Touch Pro2, Tilt 2 Android Development] antonyo17:
Display Brightness

Hi

i am testing XDAndroid GBX0B 2.3.7 Build on my TP2 Rhod100 and i would like to know if there is a way to increase the display brightness because even if i set it on 100% the brightness is still too low.

Is there a way to make the HOME key to turn on the terminal when it is on standby (i am asking this because my key power does not work properly)?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I don't know what you mean about brightness, my screen is very bright... but perhaps there's a bug with AUO panels. Is this a new bug or old? Please don't rehash old bugs.

I don't know what you mean about the other statement, there is no HOME key. We remapped END CALL to HOME. Turn on the terminal? Oh, perhaps you mean you want to be able to wake the device with the 4 buttons at the bottom? Ah jeez. I can't win here... Originally all the front buttons would wake the phone, and people complained that it was killing battery life with the phone sitting in their pocket, it would constantly get turned on. So we changed it, and now you can only power on the phone with the power button.

No one is going to be happy about this. If you want it different, hack the rootfs. It's in the keymaps.
[Touch Pro2, Tilt 2 Android Development] antonyo17:
Thanks for your answer arrrghhh, reguarding the brightness my screen is not bright even if i set it on 100%.

For the Home key you understood excatly what i meant and i need to make at least one of the 4 buttons works in order to wake the phone, because the power button on my phone does not work properly.

Is there a software that would make one of these buttons work in order to wake my phone, without changing the roofts?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Not to my knowledge.
[Touch Pro2, Tilt 2 Android Development] jonners59:
Try Brightness Widget - Backlight! Do the settings bit first to add the steps (brightness levels) and then every time you click it, it goes up, then down one step....

---------- Post added at 09:34 PM ---------- Previous post was at 09:33 PM ----------

Of course ;)
[Touch Pro2, Tilt 2 Android Development] fortunz:
http://lmgtfy.com/?q=wake+android+without+power+button
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Thanks, didn't take the time lol.

Seems "No Lock" is the ticket.
[Touch Pro2, Tilt 2 Android Development] fortunz:
My phone hasn't gone to sleep since I loaded the most recent build, timestamped 1/30/12. I noticed my battery was draining awfully fast despite not using my device at all, so I enabled the old amber/green sleep indicator using xdaledregime, and sure enough, it never turned green no matter how long the device was off.

Just to be sure it wasn't an issue with stuff I had loaded, I let the build create a new clean data.img and checked again. The logs below are from that clean img which also never slept. I set up wifi so getlogs would have a place to upload to, and then turned my TP2 off, waited a bit, turned back on, rinsed and repeated, then uploaded the logs.

I have a Rhod500, the kernel is the 1/13 .27 that came in the bundle. If any more info is needed or you need me to do something particular, I'm happy to oblige.

http://pastebin.com/dVTnxnqP
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Just to be clear, you had NO apps installed and it still never slept once? Never saw the green LED?

Did you have ANY radios on? GPS, cell, BT, etc? Just curious, gotta paint the picture...
[Touch Pro2, Tilt 2 Android Development] moovius:
Great job on this latest test release, arrrghhh!

I've been using it for the last week and it's much more fluid and responsive than FRX07.1 (except for a slightly longer delay when clicking the phone button and waiting for the dial pad to load up).

The keyboard is more responsive and I'm not experiencing lockups or random resets like I did with FRX07.1. (I have nearly the same startup file too, same cpu clock at 650something).

The only major issue I'm noticing is that it uses up the battery a bit quicker than FRX07.1.

I'm pretty happy with it. Thanks again.
[Touch Pro2, Tilt 2 Android Development] fortunz:
On the clean data image, yes, I installed nothing and yes, I repeatedly turned it off and the led never turned green. I put it in airplane mode immediately, but I also turned on wifi pretty much right away. Assuming airplane mode turns off GPS and bluetooth (which I don't use normally), wifi was all that was on.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Hum. Wake locks prevent the device from sleeping, and I see this A LOT!

active wake lock PowerManagerService

I also see a lot of this, which I'm not sure what it means... but it seems bad:

02-08 00:09:22.850 ERROR: msm_i2c msm_i2c.0: error, status 83c8
02-08 00:09:22.850 ERROR: msm_i2c msm_i2c.0: Error during data xfer (-5)
02-08 00:09:22.868 WARN : micropklt, i2c write retry

Can you try with a different kernel? 3.2 or something newish.

Edit - Also, try to put the phone to sleep in 'true' Airplane Mode - no radios, including WLAN. I see a wakelock at the end of your dmesg that indicates WLAN is keeping the phone awake. That's not present in the first few collapses tho...
[Touch Pro2, Tilt 2 Android Development] fortunz:
I'll try with a different kernel and all radios silent later and holler back with more logs.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
np. I'll see if some of the more knowledgeable folk see anything that sticks out... I certainly haven't heard of this before, I'd like to get to the bottom of it!
[Touch Pro2, Tilt 2 Android Development] jonners59:
Data lost

Help, please.

I seem to have lost data connection. I have the phone connected OK and recieve calls and TXT messages, but no data.

It started this AM. I used WiFi to download and install a couple of app updates. I also tried to set up a sync to a Blue Tooth device, which failed. I turned off the Bluetooth and also the WiFi, but since then I have had no data.

I have tried turning on and off the Flight mode, reboots with and without Flightmode on and turned to 2G only and off again... Won't come back.

I had an app called Data On Demand which controls when the data is enabled to save battery and usage, so I have also uninstalled that too in a hope it would fix it.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Hum.

Well you've tried the normal things I would suggest. You said you turn 2g only on/off, data enabled is checked right? I know, dumb question... How about data when roaming?

Lastly, do you 'see' 3g and arrows, they just don't go white? Or do you never see the 3g/arrows at all, just the signal bars?

As a test, just to rule out any apps... rename your data.img to data.bak and boot. You won't have any apps, but reversion is easy - delete the newly created data.img, rename data.bak to data.img and you're back.

If all else fails, I'd like to see some logs (preferably from the fresh data.img...). Thanks.
[Touch Pro2, Tilt 2 Android Development] jonners59:
Cheers arrrghh

I managed to get it to restart, but I was scared! And re Q above, yes roaming was on.

I managed to get it going, after all the above by turning on GPS and CoPilot... Don't ask me how it worked but all I could think of was to turn on and off every combination of radio type I could think of. Whether that was what did the trick or it just happend to co-inside with it deciding to turn on again I do not know, but data was lost since c11AM and it is now 9PM! So something had upset it.

Chers for getting back so soon. Fingers crossed it does not happen again. If it does I'll swot up on running logs and get back to you.
[Touch Pro2, Tilt 2 Android Development] fortunz:
Okay. Did two boots, both on the clean data image, both were in true airplane mode the whole time. I guess in gingerbread, you can't toggle gps the same way you could in froyo, but there was no GPS thing in the status bar, so I'm pretty sure that was off too.

I getlogged to a file for both boots so wifi would never be on. Both are attached. The one with 27 in the name has the .27 kernel, and the one with 3pt2 in the name has the... wait for it... 3.2 kernel, newest from the autobuild. The zipped file has the same text logs in it, thought I remembered someone liking zipped logs.

The 3.2 logs show a new wake lock that didn't show in the other one, "ev dev". I obviously don't know what any of this stuff means, but new info is always good, right?

Thanks for looking at this stuff arrrgh, as well as any devs who take a gander. You guys are the bomb. This may be a beta, but it seems a lot smoother than frx ever was, so I hope no one mistakes these posts as complaints. I'm just trying to contribute a little.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Man, this is nuts. I kinda suck at reading logs, but your 3.2 logs I can't even make heads or tails. I guess quite a bit changed as far as what is displayed in the console...

At any rate, nothing is screaming at me in your logs. So we've tried a new data.img, and airplane mode... Here's a couple of other ideas (yes, I'm grabbing at straws):

Boot Android with WinMo in airplane mode

Reboot, and wait for WinMo to finish booting completely. If you use Gen.Y, disable it. Once WinMo has 'settled' (give it 5 mins or so) try booting Android

Blow away the card with the HP Tool.

Try a new SD card

I guess I didn't really ask - did anything change on your side, that you can think of...? There's not a lot that should cause this considering all we've tried already. If signal was an issue, airplane mode should've solved that. If it was a new app, new data.img should've solved that... Ugh. Not really sure man, this one is a mystery.
[Touch Pro2, Tilt 2 Android Development] fortunz:
I already boot android with winmo in airplane mode, every time, without fail. Old habit from long ago. I also always let winmo settle before booting, usually because I'm NOT eyeing it waiting for it to get ready so I just let it sit and come back to it in the 15-30 minute range when I get around to it, and I don't use gen.y. There's nothing new I can think of, other than the 1/30 gbx build.

My current card is the best booter I have (high 4k write benches), and I used hp tool to format it right from the start. I may not post here often, but I'm an avid reader of your posts.

If there really is nothing wrong with the build, then perhaps I copied something wrong when I was putting it all together. I'll test that theory and a new card at the same time later on, just to be sure. I'll also roll back the build on my current card. If it starts sleeping again once I have the jan 2nd build, then that would isolate the issue a little.

You needn't worry much about fixing this on my behalf. I don't have an issue going back to the last build. I was just trying to help. I recall sleeping issues used to be a big deal, but this is my very first one.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Well, I guess I'm not positive if it's a widespread issue - without the sleep indicator, no way to know other than reports of severely poor battery life reports. I've had a few, and I think battery life might be a little worse - perhaps something with acoustic, perhaps something with GB... who knows. But I haven't had too many reports (if any?) of severely poor battery life like yours.

Maybe I should turn it back on by default to see what kind of reports we get? I dunno. I thought this was a random occurrence, you're saying it started with the newest build? Interesting....
[Touch Pro2, Tilt 2 Android Development] fortunz:
Yup. This build only. But I will get around to checking that the build before this one still sleeps. The battery life before and after the new build was night and day though, so I feel pretty confident about the outcome.

I don't really have an opinion about whether the LED should be on by default. As long as it can still be toggled to notifications. Has there been much adoption of the 1/30 build? I actually wouldn't have noticed its release if a buddy hadn't pointed it out to me.
[Touch Pro2, Tilt 2 Android Development] detule:
Not sure why this would make a difference, but try turning Auto Rotate OFF in 3.2 and see if that makes a difference. In 3.2 at least, your wake_locks are being held by evdev -> and one culprit can be the bma driver (though it works fine for me over here).
[Touch Pro2, Tilt 2 Android Development] fortunz:
Tried it, and evdev is still showing up on the wake lock lines.

Is there any reason evdev might show up for 3.2 but not for .27 when both have the same issue?
[Touch Pro2, Tilt 2 Android Development] fortunz:
For the record I finished a last couple of tests. I loaded the 1/30/12 build on a fresh blank sd card with nothing on it, tossed in my startup, tscal and .csvs, turned on the led debugging, turned it off and it wouldn't sleep. I then loaded the 1/02/12 build on the same card, even used the same data image built by the 1/30/12 build (didn't actually mean to, just forgot to delete it), and it slept just fine.

I'm willing to do additional tests, but I feel pretty certain this is a build issue. I'm also willing to shut up about it if indeed I'm the only one affected for some reason. Sometimes these things work themselves out as development proceeds.
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
I haven't pulled any logs to show wake locks, etc, but I can say that even with a fairly new OEM battery the battery life really blows for me. And I've done the PM disable trick and don't have a ton of apps loaded but still blows. Can't get even a half day out of it and used to be able to make it an entire day. And I've also lately been having just random reboots. Phone sitting on my desk then I hear the double vibrate, check phone and it's booting android again... that however just may be the card. It's not too old but who knows, I've had a ton of builds on it, etc, so I'm gonna grab a new c4 sd and see if that helps with the rebooting.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Hrm... perhaps something really did get FUBAR on the last build.

Trying to think of what I changed... other than building the image myself, I don't think a whole lot changed on the system image side... Crap.

Someone want to try running the new kernel on the old image?
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
I can check the new kernel on the old image, which one are you referring to 01/02/12 or FRX? And believe me, I'm sure you'd have a lot more complaints about rebooting if it was more than just me, so don't put too much weight into my complaints, at least until I get a brand new sd card and try it on that. Any thoughts on how to attack the market issues I mentioned the other day?
[Touch Pro2, Tilt 2 Android Development] fortunz:
I haven't pulled the log off it yet, but I just tried the 1/2/12 build's kernel (dated 12/31/11) and ran it with the 1/30/12 build, and led debug did turn green indicating sleep repeatedly. I guess I'll go back to that kernel in my normal setup. Pretty easy solution actually. Silly that I didn't think to try it myself.

Are there changes in the new .27 that would have been made to the 3.2 I tested the other day as well?
[Touch Pro2, Tilt 2 Android Development] detule:
Here's the changelog:

http://gitorious.org/linux-on-qualcomm-s-msm/linux-msm/commits/htc-msm-2.6.27-acoustic

The _only_ difference is acoustic related (important!, without it you will have frequent total audio failure) which has absolutely no bearing on sleep.

I use 3.2 and I almost always have green LED on, so it's not a kernel issue that you are experiencing.

I am also on the latest gbx0b, albeit one that I compiled myself. However, you say 1/30 works fine for you with an older kernel, so it's not a build issue.

Out of ideas here, not a kernel issue, not a build issue -> must be something particular to your setup.