Workarounds/known issues 7/22: Updated for FRX07

[highlandsun]

I believe all ril-related SoDs are now fixed in my ril.

Haven't tested Call Waiting, but that may turn out to be a ril-related bug too. I can probably investigate it later.

Data Connection - should be 100% reliable now.

MMS - reception on CDMA has improved with the new ril in real CDMA mode. You get the message and a download link, but thus far no one has gotten the download link to work. Seems to be a framework/config issue; the ril-related pieces are all now in place. Probably needs a profile to be updated using ##3282# or similar.

GPS - the bug where it always starts with your position in the middle of the ocean has been fixed. Aside from that, it's still a slow startup. http://forum.xda-developers.com/showthread.php?t=969761

Clock - if your network supports Network Informed Time Zone updates, you can get the clock set automatically whenever your phone registers to the network. So far it looks to me like GSM networks only send these updates once, at initial registration. However toggling Airplane Mode on and off causes another update. On CDMA networks you can get NITZ info much more frequently, but right now the RIL is only set up to process the update from the initial registration. I think parsing every single received NITZ on CDMA would be overkill. (It's sent with every tower status update message, along with the tower lat/long coordinates.)

Tethering over USB - I have a hacked adb binary that sets up a ppp session over an adb session. (The regular adb binary will set up a ppp session using a tty device on the phone, e.g. to talk to the phone's radio.) I use my hacked adb to tether between my phone and my laptop. http://forum.xda-developers.com/showpost.php?p=4537323

[highlandsun]

Call waiting for CDMA is now working in my latest ril. (It was always working for regular GSM. I think it is probably still broken for fake GSM.)

Sent from my MSM using Tapatalk

[highlandsun]

I see manekineko already updated the first post, but I wanted to bump this thread anyway.

Battery charging should be totally reliable in the latest autobuild kernel. Along with USB status changes, which enabled the native USB tethering.

I seem to recall that WisTilt2 got the stylus sensor working, but then backed out the change because userland wasn't coping with it. Frankly, I don't know what userland's response to that sensor ought to be...

We've come a long way and the list of working features is really impressive. I've been running this as my primary phone for the past 2 months. Having owned a G1 since their first release, I'm a longtime Android user and there's really nothing missing here, to me.

Sent from my FRX06+ TP2 using Tapatalk

[manekineko]

Originally Posted by highlandsun

I see manekineko already updated the first post, but I wanted to bump this thread anyway.

Battery charging should be totally reliable in the latest autobuild kernel. Along with USB status changes, which enabled the native USB tethering.

I seem to recall that WisTilt2 got the stylus sensor working, but then backed out the change because userland wasn't coping with it. Frankly, I don't know what userland's response to that sensor ought to be...

We've come a long way and the list of working features is really impressive. I've been running this as my primary phone for the past 2 months. Having owned a G1 since their first release, I'm a longtime Android user and there's really nothing missing here, to me.

Sent from my FRX06+ TP2 using Tapatalk

Okay, I'll remove the battery discharging while charging bug for now on the assumption it's fixed, and will re-add if I see it again (or someone else credibility claims they got hit by it again).

Stylus sensor is kinda not obvious what it should do. Best option to me sounds like exposing it to userland so it can be set via settings to do something by the user, such as launching a note taking program, but that would probably be a long way off, if ever.

Agreed on the great state of the working feature list. I've been using it as my primary phone for months now, and am quite happy with it, much happier than I was with WinMo. Though I'd trade it all, for a little bit more...

[chroniX0]

you say you can make sound come to headphones by putting all sound through the headphones, but how?

[manekineko]

Originally Posted by chroniX0

you say you can make sound come to headphones by putting all sound through the headphones, but how?

I'm not 100% sure since I haven't heard from anyone wanting to do this in a while. Can you try this for me? Add to your cmds section of your startup.txt:
snd.force_headset=2

Let me know if that'll work, so I can update the first post with that info.

[chroniX0]

Originally Posted by manekineko

I'm not 100% sure since I haven't heard from anyone wanting to do this in a while. Can you try this for me? Add to your cmds section of your startup.txt:
snd.force_headset=2

Let me know if that'll work, so I can update the first post with that info.

Yeah, I've tried this, and it doesn't seem to work, I've also tried it with the voice mail dialer trick and it pauses during boot, tried the voicemail trick without snd.force and it still pauses at the boot up screen.

EDIT: I've tried this with a clean install of GB and it still doesn't work, I could try it with Froyo to see if it would make a difference, but i doubt it would.

[manekineko]

Originally Posted by chroniX0

Yeah, I've tried this, and it doesn't seem to work, I've also tried it with the voice mail dialer trick and it pauses during boot, tried the voicemail trick without snd.force and it still pauses at the boot up screen.

EDIT: I've tried this with a clean install of GB and it still doesn't work, I could try it with Froyo to see if it would make a difference, but i doubt it would.

Okay, I've updated the original post to remove that workaround then. Assumedly, some commit broke that workaround, and since I don't think many people were using it, no one ever noticed.

[manekineko]

FYI, added a link to the workaround at the bottom for Youtube HQ and other high-res video playback problems.

[highlandsun]

All Sprint MMS issues now resolved... http://forum.xda-developers.com/show...9&postcount=17

Sent from my FRX06+ TP2 using Tapatalk