yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] highlandsun:
We're pretty used to reading the getlogs files. Don't worry about whether or not they're ugly.

I'm beginning to think we need to see some Winmo logs too - Winmo used the prox sensor too didn't it?

It seems that I'm going to actually spend some time debugging this after all. I'm in Europe for the next month, and my Droid4 is useless here (except on Wifi) so I'm relying on my TP2 again, and these problems are getting worse. Looking thru one of my own recent radio logs, I see that these "WCDMA" or "GSM" responses can occur randomly for other commands too. In this case, it prevented my phone from listing the available networks, because "WCDMA" was returned before the network list, and that confused the Phone.apk enough that it couldn't register onto any network. (Took me several tries in and out of Airplane mode to finally get a clean list and successful registration.)

I'm also getting into hang/SOD situations again. This time it's a little more obvious what is going on - logcat -b radio shows that the modem has stopped responding. The rest of the phone continues to function, but if you let the screen turn off, it will not turn on again while the modem is hung.

Unfortunately, I have no idea why the modem got hung, or how to bring it back to life without doing a hard reset. But I think these WCDMA/GSM messages are part of the larger problem.
[Touch Pro2, Tilt 2 Android Development] detule:
Have you tried disabling the prox sensor? If we can verify that this is exacerbating the issue we can maybe add a delay in the kernel driver to prevent conflicting values reported within an absurdly short time-span of eachother.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
I switched back to the bundled .27 kernel and the problem isn't there. How would I disable the prox sensor in 3.2.2?
[Touch Pro2, Tilt 2 Android Development] detule:
The bundled .27 also has prox right?

Here's a 3.2 with prox disabled,
[Touch Pro2, Tilt 2 Android Development] jonners59:
These new contributions to the thread are the same as I had from the start and slowly progressed in to the issues I now have with the phone. See early replies.

One thing that I have found seems to help with restoring voice and data connection has been to ensure that data and data roaming are switched off and ideally also use flight mode before shutting down, or if it boots up with the phone problems than to select these before doing a reboot.
[Touch Pro2, Tilt 2 Android Development] agibby5:
Just wanted to give some quick feedback. FYI, I've only been using this for a few hours so far.

I setup my Google account, but Gmail was missing. I went into Marketplace and it froze for a long time during which it converted to Google Play. Once that was over, I downloaded Gmail and it started syncing my mail automatically. I'm assuming this is something that will be bundled when the 'stable' version is released.

I've noticed that the device has been a bit quicker on this build than FRX. I'm running the .35 kernel because the first post talks about .27 which is bundled missing sound. The call quality is night and day better than FRX.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
lol, the bundled kernel works, obviously... But I didn't want people going to different autobuild .27 kernels, because they wouldn't work. However, the newest .27 autobuild ironically has the new acoustic code in it - but that's a pretty recent occurrence.

Also, I don't remember that issue with GMail... So when it asked to add an account, "Exchange" was the only option? (Might be named "Corporate email, but you get the point :p)

A lot has changed acoustically in this build. Audio should be better all around.
[Touch Pro2, Tilt 2 Android Development] agibby5:
Thanks for updating the first post... the wording of it was what pushed me to use the .35 kernel.

Google was an option when setting up a sync account, but Gmail wasn't within the sync settings. Adding the Gmail app via Google Play fixed this.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Oh, I see. I remember that as well now. I guess the gapps package doesn't include GMail... I don't know if it will be included then. Not sure...

Edit - Sorry about being unclear in the first post earlier. I really felt the need to update it since the autobuild is now updated. I just wanted to be clear that the autobuild was not OK before... I didn't realize that people would think the bundled kernel wouldn't work either, haha.
[Touch Pro2, Tilt 2 Android Development] hao0907047407:
I don't understand. ????
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Because we've made HUGE strides forward in acoustic routing with this new build. Literally every single response has been that audio is all-around better in this build. Read the few above yours - no one else thinks the acoustic code should be reverted, except you. So either you're joking, or insane.

If you really, truly do have an issue then stick with FRX07.1, I doubt acoustic will make its way back to that build.
[Touch Pro2, Tilt 2 Android Development] CodaHighland:
The only thing I can think of that you might consider "better" is that there's a possibility that some of the audio parameters in the csv files might have been tuned in a way that (in your subjective opinion) was more pleasing. The actual audio QUALITY as well as stability is (objectively) superior in GBX.

On that note, I could use some advice in that regard: My speakerphone is WAY TOO LOUD even on the lowest setting. Where can I tune that?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Short of mucking with the CSV files, there's an app called Volume+. I think it usually helps tweaking the volume in the other direction, but it might help tweak it down as well... I've never used it myself.
[Touch Pro2, Tilt 2 Android Development] eik:
I thought it was about time for me to try out this version. It seems to run smoother than Froyo. But I ran into an issue: both with the .27 as well as a .39 kernel I lost connection while commuting. I seem to pass through areas with very low phone coverage. When I arrive it appears to be impossible to reestablish a connection without a reboot. Even airplane mode will not work (it just won't go into that mode).

The symptoms are very similar to what I had before in Froyo until a new ril was created there.

Unfortunately no logs yet; next action for me is to figure out how to get getlogs to work.

I am a Rhodium100 GSM user.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yea, there's either some regressions with GB related to the RIL, or there's some new stuff in GB that didn't cause us issues in Froyo. Devs are workin on it, thanks for the info.

If this is crippling for you, stick to Froyo. Thanks.
[Touch Pro2, Tilt 2 Android Development] CodaHighland:
Tried to get AGPS working on my phone and... well, discovered that location services apparently aren't working at all -- not just GPS, but also network-based. Not sure what to make of it. I even switched back to the original gps.xdandroid.so and that's not working either. It just sits there and blinks the location icon in the status bar and never gets a lock no matter how long I wait. I even got GPS Essentials and it never even reports that it's tracking any satellites.

I rebooted into WinMo and location works there (both network and GPS) so it's not a hardware issue. Haven't tried Froyo yet.

Edit: Spoke too soon, apparently... I turned off location services, went to clean house a little, and came back with intent to get some logs, only to discover it picked up a lock as soon as I opened Maps. This is with the stock GPS lib, not the new one. Still confusing.
[Touch Pro2, Tilt 2 Android Development] JDog2pt0:
Seem to be getting a lot more "Your device isn't compatible with this app" or w/e it is in the Market. Script Manager, ES File Explorer, etc. I had to start fresh, most of those were from a backup so I'm not sure if the issue was always there or a recent development. Those are the only two examples I have at the moment. Thankfully they are available for download on their respective homepages. I saw a CM7 post/fix for the issue, but I'm not sure it's relevant.

http://myraroldan.com/wp/2011/09/yo...th-this-item-annoying-android-market-message/

I suppose I should look more into it later. Minecraft is a helluva drug.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
lol, nice post. As usual, he's thinking LCD Density settings...

Either way I love the end of the post:

Hahaha. So I guess the new Market/"Google Play" is not playing nicely with a lot of phones... I've seen a few people complaining about this recently, and it wasn't until the Market updated to Play that I really saw an uptick in them... But as that post points out, no matter what - there's always sideloading ;).
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
Is there a setting for RHOD400 that changes the speed of mms viewing? When I get an MMS if it's multiple pics they flash by so quickly you can't see them. It was fine using GoSMS or any of the other apps of that sort, but I like the stock messaging app which seems to just fly by the pics. Any thoughts?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Hrm... hyc hacked MMS because Sprint really mangles it thru the phone. I can't remember if he made it so it froze in place, or paused for 8 sec - but that was on FroYo. I thought that patch made it into this build tho...

Do you/did you have that same problem with FRX?
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
No, FRX was fine, once hyc put his tweak in. I'm assuming it didn't make it in here or if it did I screwed it up somehow. And IIRc correctly it paused it for 8 sec or something of that sort, because it was like a slideshow as opposed to freezing them.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I'll doublecheck that the MMS patch made it in... I thought it did!
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
That would be great, I could get rid of GoSMS again then lol.
[Touch Pro2, Tilt 2 Android Development] detule:
Different MMS patch - this is likely what is needed. Looks like stine is the only one with commit access there.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Ah, I thought they all made it in. That definitely looks like the bugger we need... Hum, I think stine's going to have to expand commit access...
[Touch Pro2, Tilt 2 Android Development] detule:
camcorder fix

Here's the series of userland patches that get the camcorder going on my rhod400.

You can download the compiled binary here. Needs to be mounted over (or it should replace) /system/lib/libstagefright.so .
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
I have a slight problem with the patch. The camcorder runs and records, but on playback I only got sound for the first 4-5 seconds or so of my video. I took another video and there was no sound at all. So something quits routing sound recording during the first video being recorded and the only way to fix it is to reboot, and then it only records the first 4-5 seconds again. I have moved the video to my computer and it doesn't play sound after the first 4-5 seconds either meaning it isn't even recording sound after that first 4-5 seconds. Any thoughts. I can dump logs if you need me to.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yea, logs please! logcat especially, but as always GetLogs is preferred ;).
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
http://pastebin.com/5YxC4gzd

I think it is fairly short because I did it the first time and then rebooted to see if a reboot would fix and then shot another video. So there should only be one video being recorded in this log. Video recording starts around Line 477.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Aw, are you not on my rootfs? The dmesg log doesn't have timestamps. Sad panda. I suck at reading logs, and that makes it A LOT easier on my n00b eyes.
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
Yeah I am with the exception that I put the firmware in your rootfs and re-saved it. So I am using your rootfs just with the Wi-fi tethering firmware on it. I see timestamps in that pastebin a the begining of each line.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Look at the kernel log, there's no timestamps.

That's strange, I don't know why swapping firmware would cause any issues with that. I guess I need to put out a new rootfs with that firmware.

I was hoping to get a new build out with all the patches detule's been making/finding. I sent an email to Sir Stine, hopefully we can sort out the commit access debacle.
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
Well theoretically there is only one rootfs (yours) that should work on GBX0B correct? I feel pretty confident when I pulled the rootfs and worked on it I pulled it out of the GBX0B folder on my computer. I mean it was back in late Feb, so it is hard to remember everything I did, but I don't think I would have screwed that up. I didn't think any other rootfs would work that is already available for download on xdandroid?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
The autobuild rootfs will work on GBX0B. I just added some nice things into mine that are some enhancements that I plan on committing to the autobuild at some point. One of them is the dmesg binary from hyc that provides timestamps. The other is the firmware flip for .27 and .35+. Can't remember what else I've done to it, I think that's it ;).
[Touch Pro2, Tilt 2 Android Development] agibby5:
I'm having some issues with MMS. I had this problem in FRX as well, but it went away with later updates. First, the messages don't auto download. I have to press a Download button when I open the received MMS. Then, it sits there saying "Downloading" for quite some time. Then the battery dies very soon after if I end up forgetting about it. To fix this I just reboot and go back in, ignoring the fact that I received an MMS message. Ideas on this?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I'm pretty sure it's in this thread, read back a few posts. We just had a conversation about MMS.

Basically Sprint mangles MMS pretty badly. a) be happy it works at all and b) there's a patch for MMS that did not make it into this build.
[Touch Pro2, Tilt 2 Android Development] detule:
Pretty sure that the dualmic is not working on +.39 kernels so this is probably why one might get low-volume or no mic recording during video. No idea about .27

If you have video recording at_all than the camcorder patches are working as they should. Dualmic needs a champion, patches are welcome.
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
But if it was not working at all why would I get 4-5 seconds of sound recording then it just stop. Obviously some mic is on for that 4-5 seconds. I am running the latest 3.2... I will look into it. It was a ***** getting the sound to work in FRX07.1, but someone patched it to work. Guessing that isn't able to be worked into GBX0B?
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
detule, not sure if you want to look or not, but here's logs from the camcorder. I had the issue issues as slickdaddy, records video fine but the audio drops off after a few seconds. RHOD400, bind mounted the lib, haven't done any audio tweaks. Personally I don't use the camcorder, just figured I'd do a little testing to see if I was having the same issues. http://pastebin.com/yGermMsi
[Touch Pro2, Tilt 2 Android Development] detule:
Thanks i see something that could be fixed. I may need you to test the product since apparently my device is the exception in that my dualmic is not functioning at all.

Edit: See if this libhtc_acoustic fixes this for you. As usual, goes in /system/lib
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
That did it for me. Let me know if you need more logs but I bind mounted it and it worked fine. The first time I started a recording it kinda froze, so I stopped it. Restarted it and recorded for about 15-20 seconds and video and audio were both great and recorded as long as I wanted them to (well...as great as they can be on this device). Thanks for looking at this and getting it fixed so quickly!!
[Touch Pro2, Tilt 2 Android Development] detule:
No problem. The patched lib you have is not ideal, and it will probably go through another iteration - so make sure you update whenever the new build is out.

On a side note, I looked into the MMS slideshow - it seems in the gingerbread branch google already has code equivalent to what's in the hyc's patch, they've just done a poor job enforcing the codepath. At any rate, after a one-liner, the mms slideshow is working as it should.
[Touch Pro2, Tilt 2 Android Development] agibby5:
I actually read the MMS convo that just happened. The problem was not the same as the one I reported, that's why I posted separately about what I was running into.
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
Ignore this post...
[Touch Pro2, Tilt 2 Android Development] JDog2pt0:
So update, changing the res did fix it. I changed the res to 240, removed play and reinstalled then set the res back to 210. I can download all my things again.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Thanks for confirming that. Kudos!
[Touch Pro2, Tilt 2 Android Development] CodaHighland:
Call failed to hang up.

http://pastebin.com/6kac7b6V

Still on 3.2.2, using detule's .so.4 library.

I can't tell if it's a radio issue or something else. I called my wife's phone (trying to find it around the house) and then hung her phone up without answering the call. My phone therefore got sent to voicemail. The screen was still backlit but black. I tapped the screen and it lit up, then I hit the End Call button and put the phone down and stopped paying attention until I heard the VM system giving me message options a minute later. Attempting to hang up the call at that point worked.

I do see the onUnsolicited handler firing in there.
[Touch Pro2, Tilt 2 Android Development] armedmetallica:
just wanted to report on the outgoing call issue that i think 1 or 2 others reported back....

i'm on the newest autobuild (linked from the 2nd post)... I first extracted the stuff from OP, deleted out the zimage and modules, and copied over the new ones. and booted, let it create a data.img file; then i copied that data.img over to my computer, and used the resizer util to increase it to 1.9GB. It complained about file errors, and "fixed them"; then I copied it back to the device. (copying happens under WinMo/usb).

SO... when i attempt a dial, it tries for two seconds and immediately shows me call ended.... however, the call is ongoing other end rings... AND if the other end picks up, guess what? This end SENDS them the audio... so it's almost like a ghost call session .. and scary enough, can hear everything. I wonder if my real-estate agent heard me bad mouthing him yesterday!

This didn't happen in the Froyo build.... Oh one other peculiarity, the Reboot/Kegex options seem to just hang about 80% of the time... I end up taking the battery out. Using stock dialer or Dialer one, same scenario

I liked the newer kernel because it is the only one that lets you run the Kindle app.

I'll try again on stock kernel.

Should I attempt to read-up on Adb/getlogs or is this so rare an occurrence that you folks wouldn't spend time on it? and finally, should i cross post this in the kernel build thread?

Help me help you help me :D
[Touch Pro2, Tilt 2 Android Development] CodaHighland:
Nope, it's an annoyingly common issue to RHOD210 users. We (mostly detule and highlandsun) are working on a fix.

My sometimes-workaround is to place another call (maybe to voicemail); the first call will show up as on hold at that point and you can switch to it. Doesn't always work though.
[Touch Pro2, Tilt 2 Android Development] armedmetallica:
ah - i forgot to mention i'm on RHOD300 (Tilt2)...

torn between having to futz with this or giving up kindle. oooh decisions decisions.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Basically the same thing, it's a GSM problem.
[Touch Pro2, Tilt 2 Android Development] detule:
Thanks for your report. It's being worked on. I think jonpry and hyc are onto something and we might have something in the works, though not sure.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
So far it's looking really good here.
[Touch Pro2, Tilt 2 Android Development] armedmetallica:
excellent! let me know if you need a guinea pig ?
[Touch Pro2, Tilt 2 Android Development] detule:
You (and other GSM users that are having radio/ril issues) should try the latest 3.2 kernel from the autobuild - jonpry pushed a patch out that should hopefully normalize things. If you run into any issues, make sure to include complete GetLogs output.
[Touch Pro2, Tilt 2 Android Development] CodaHighland:
That said, so far it's working for me!

Edit: Er. Scratch that. Apparently the kernel I'm running ISN'T this one. XD I can't attest one way or the other yet.

Edit #2: The kernel I have has the same fix, but the autobuild is more efficient at handling some stuff. So yeah, take this as a +1 from me on this patch helping with the call problems.
[Touch Pro2, Tilt 2 Android Development] detule:
arrrghhh i have a favor to ask of you and your raph...you know what it is...

make sure that thing is amss5225 (should be readable from the prop gsm.version.baseband )
[Touch Pro2, Tilt 2 Android Development] armedmetallica:
just tried 3.2.11 and still have same issue. I deleted zimage and modules#### ... should i delete my data.img as well?

also a bit OT, how do you people separate froyo and gb (other than by directory). all the folders that android is creating on the root of my sd card could cause conflicts, no?

my installs are in \Andy\Froyo; \Andy\GB\ etc ... should we move this discussion to the autobuild thread?
[Touch Pro2, Tilt 2 Android Development] jonners59:
Driving to Italy via France, Belgium, Netherlands, Germany and Austria, in one hit - again, so I shall be able to report back on how well the build switches between networks if you are interested still. Based on the progress since F6 when I went last year I have great expectations. Let me know if you want to know, otherwise I shall just focus on the wine ahead.:)
[Touch Pro2, Tilt 2 Android Development] detule:
No need to delete data.img.
[Touch Pro2, Tilt 2 Android Development] armedmetallica:
will get that up.. sorry... but did try w. new data.img, and that seemed to work; only tested once. trying old data.img again. takes a while to boot/reboot .

thanks again!
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Separate cards is best. Otherwise, I haven't had a problem with the directories at the root of the SD being shared. So long as you separate out the build folders, which you have, then you're fine.
[Touch Pro2, Tilt 2 Android Development] armedmetallica:
is there any benefit of expanding the data.img from the default size? does it allow more multi-tasking, room for more contacts, or just app install space?

sorry this part of the world is new to me.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
All it allows is more app install space, nothing more. It's like adding (or expanding, if it was possible) the hard drive on your computer. Doesn't speed things up (assuming the HDD's are identical, obviously), just gives you more space for junk.
[Touch Pro2, Tilt 2 Android Development] armedmetallica:
thanks! i may go big later ....

OK - i started over - and guess what, at least for me, on 3.2.11 - it was DialerOne that killed it. using the built-in dialer after installing DialerOne is still no good

will try uninstalling DialerOne and post back...

also - can anyone recco a good dialer then ? :rolleyes:

edit: uninstalling DialerOne did not help; stock dialer does same thing now. re-deleting data.img and starting over, again. i'll try getting logs if you want to pursue, or i'll just find an alternate dialer.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
What do you mean 'alternate dialer'? I dial numbers, the phone rings, it works. Perhaps I'm missing something? lol.