[TESTING] - NAND OMGB (1.2.3)

[arrrghhh]

Originally Posted by vzihome

Try switching into airplane then reboot(when switching to airplane mode it doesn't actually switch until you restart) then after you restart switch back to airplane off reboot (same as above) it worked for me when I was having issues don't know if its related I'm on sprint rhod400

Sent from my Touch Pro 2 using Tapatalk

What do you mean "airplane mode doesn't actually switch until you restart"? Airplane mode goes in effect immediately here.

[vzihome]

Originally Posted by arrrghhh

What do you mean "airplane mode doesn't actually switch until you restart"? Airplane mode goes in effect immediately here.

Guess its only on my phone only but icons still show service but can't actually use it and airplane mode option greyed out need to reboot

Sent from my Touch Pro 2 using Tapatalk

[[ACL]]

Originally Posted by vzihome

Try switching into airplane then reboot(when switching to airplane mode it doesn't actually switch until you restart) then after you restart switch back to airplane off reboot (same as above) it worked for me when I was having issues don't know if its related I'm on sprint rhod400

Sent from my Touch Pro 2 using Tapatalk

Thats not correct behavior. On normal usage when going to airplane mode if you look at the radio logs you should see it go immediately to airplane mode. If yours is only doing that on reboot, means there is something stuck on the radio and wont happen until the radio restarts.

I know you have some mods on your own build prop, so try to trace back and see what setting may have caused this. On the 400, im able to switch to airplane with no issues.

If you need a hint of what may be causing it, keep your eye on the radio log as you are switching it. It may show you there whats going on.

[teemo]

What about the radio. I dont think we had an update for more than a year. 400/500 has brand new radios afaik.
What radios are you using?

[[ACL]]

Originally Posted by teemo

What about the radio. I dont think we had an update for more than a year. 400/500 has brand new radios afaik.
What radios are you using?

I think at least everyone should be running 2.32. I know thats what i run on one of my rhods. but i found 2.37 vz radio to be more stable with gps. So that is definitely the recommended setup. Most of the users here are on 2.37 as well.

[vzihome]

Originally Posted by [ACL]

Thats not correct behavior. On normal usage when going to airplane mode if you look at the radio logs you should see it go immediately to airplane mode. If yours is only doing that on reboot, means there is something stuck on the radio and wont happen until the radio restarts.

I know you have some mods on your own build prop, so try to trace back and see what setting may have caused this. On the 400, im able to switch to airplane with no issues.

If you need a hint of what may be causing it, keep your eye on the radio log as you are switching it. It may show you there whats going on.

Ill try it on my test rhod and backtrack that way, thanks

Sent from my Touch Pro 2 using Tapatalk

[starling100]

Originally Posted by [ACL]

hey did you try the light sensor and prox ? this dmesg is really short and doesnt show much activity when it comes to LS and prox

There is something wrong with your setup.

12-15 01:01:47.530 E/lights ( 122): write_int failed to open /dbgfs/micropklt_dbg/auto_backlight

This does not exist on my code. Did you modify the sensors ?

EDIT: I see, you are using haret libs. I'm going to let you know this only once. I don't support hacked setups. It makes it impossible to troubleshoot and delays progress. So if you want to help, you have to use what we put out. Plain and simple. Or else your bugs will be mistaken for something else and we end up loosing time.

So please, fix your setup or wait until a final release.

OK, I see.
I do all of them again and use all the newest dev from your Google code pages.

PS:
I used the new ibhtcgeneric-ril.so, kernel and changed the ro.telephony.default_network = 1

1. GSM is working.
2. The light sensor and prox are working.
3. Panel working after sleep.
4. Calling: MIC issue. Can use the headset to let he/she to hear your voice.

3 version Logs are attached, hope it's helpful.

[arrrghhh]

Originally Posted by starling100

OK, I see.
I do all of them again and use all the newest dev from your Google code pages.

PS:
I used the new ibhtcgeneric-ril.so, kernel and changed the ro.telephony.default_network = 1

1. GSM is working.
2. The light sensor and prox are working.
3. Panel working after sleep.
4. Calling: Can use the headset to let he/she to hear your voice.

Awesome. So for GSM to work, you have to make that build.prop change? Have you tried this without the build.prop change? Sorry for making you jump thru hoops, we just really need to sort out what is needed and what isn't.

Also, for #4 calling - obviously the mic doesn't work - for headset, are you using the extUSB headset? Which is wired, plugs into your phone? Also, have you tried the speakerphone on/off trick? Wonder if that works. Thanks.

[starling100]

Originally Posted by arrrghhh

Awesome. So for GSM to work, you have to make that build.prop change? Have you tried this without the build.prop change? Sorry for making you jump thru hoops, we just really need to sort out what is needed and what isn't.

Also, for #4 calling - obviously the mic doesn't work - for headset, are you using the extUSB headset? Which is wired, plugs into your phone? Also, have you tried the speakerphone on/off trick? Wonder if that works. Thanks.

Yes, the orignal extUSB headset as below.

Speakerphone on/off trick many times, not working.

BTW I upload the logs above, hope it's helpful for troubleshooting.

[arrrghhh]

Originally Posted by starling100

Yes, the orignal extUSB headset as below.

Speakerphone on/off trick many times, not working.

BTW I upload the logs above, hope it's helpful for troubleshooting.

Cool, thanks.

What about the build.prop hack? Are you positive that was required? I know it's annoying, but if you wouldn't mind trying with new RIL, new kernel and fresh install...? I think if that build.prop change is required, it will cause problems for others (not positive tho) so I'd like to see if you can still get service with it set to 0. Thanks!!