Guest t0mm13b Posted July 20, 2011 Report Posted July 20, 2011 (edited) Came across this app which could be useful for those having proximity issue... linky PPPPFFFFFFTTTTT Crap app - don't use! Does not work with our CM7 kernel... Edited July 20, 2011 by t0mm13b
Guest ColdEmbrace Posted July 20, 2011 Report Posted July 20, 2011 Came across this app which could be useful for those having proximity issue... linky PPPPFFFFFFTTTTT Crap app - don't use! Does not work with our CM7 kernel... you think its a crap app my computer gave me a safety warning about the site being unsecure and likely to contain damaging content
Guest danieljtmcleod1989 Posted July 20, 2011 Report Posted July 20, 2011 Tom G posted a temp fix on the tracker to be flashed with cwm, I used when I was on rc1 before I started using the nightlies. If I can find it I will post the link. It worked wonders for me.
Guest k0zmic Posted July 20, 2011 Report Posted July 20, 2011 Tom G posted a temp fix on the tracker to be flashed with cwm, I used when I was on rc1 before I started using the nightlies. If I can find it I will post the link. It worked wonders for me. http://code.google.com/p/cyanogenmod/issues/detail?id=3955#c38
Guest t0mm13b Posted July 20, 2011 Report Posted July 20, 2011 http://code.google.com/p/cyanogenmod/issues/detail?id=3955#c38 Here's another linky to confirm indeed if the proximity works or not - Just watch out for NEAR and FAR when covering the sensor with your thumb by the left of the earpiece.
Guest t0mm13b Posted July 20, 2011 Report Posted July 20, 2011 you think its a crap app my computer gave me a safety warning about the site being unsecure and likely to contain damaging content Huh?! I downloaded it via barcode scanner on android and that's how I said it's a crap app! :P
Guest danieljtmcleod1989 Posted July 22, 2011 Report Posted July 22, 2011 Recalibration? *983*0# ;) Doesn't that only work with the zte dialers engineering mode?
Guest k0zmic Posted July 22, 2011 Report Posted July 22, 2011 Doesn't that only work with the zte dialers engineering mode? Correct.
Guest Monfro Posted July 22, 2011 Report Posted July 22, 2011 PM_CZ found the solution. He wrote this in GSF thread. I think this is useful to all Blade users that doesn't use ZTE Dialler. Hi all, I have seen in the last pages of this thread, that people request SMS delivery notification fix, the old SIP audio routing problem fix and Engineering mode access mainly due to the sensor calibration. The requests are made for GSF 14 or older at the time of writing this message. Wipe should not be necessary with my solution. The MMS has already been solved (by installing Mms.apk from CM7.03), but it has to be done by hand. I have built the update zip. Before that, I have also tried to use current Nightly Mms.apk, but it crashes on settings Page; original ZTE Mms.apk without their dialer crashes during startup due to different contact database format. mms.zip Second thing is the ZTE Engineering mode app. It requires the ZTE dialer to access the menus, so one has to break the installation by its addition. However, there is a solution, although not a simple one. One can install the Emode itself, but to access it, some application which shows hidden Activities must be used. I personally use Widgetsoid, which will be used in this solution (the hidden activity we need is com.zte.emode.TestDialer). First, one must install the zte-emode.zip in recovery. zte-emode.zip After the installation, unpack the widgetsoid settings zip to sdcard, it contains the setting for Widgetsoid. Create a Widgetsoid 1x1 switcher on your desktop, go to Profiles tab and you should have ZTE_emode_kb profile there. Load it, Apply, and click on the icon. You should get a simple dialer keyboard, where you can enter the engineering codes (e.g. *983*0#). emode-widgetsoid_setting-unpack_to_SD.zip Alternatively, you can use Shortcut -> Application -> All Activities and select com.zte.emode.TestDialer. Concerning the audio routing problem, replacing the broken library with the one from CM (where the problem is reported to be fixed according to this forum) I had no success, the framework crashed due to address inconsistency.
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now