**Standard Disclaimer applies here: If you screw up your device trying the following steps in this thread, I cant be responsible. But thats old news**
If your phone stays black after a call you can fix it by a couple of ways.
First:
Code:
[B]Q[/B]:Where is the proximity sensor?
[B]A[/B]:Top left of the screen in opposite place to led, if you tily screen under the light you should see the sensor reflect back at you.
Install this app and test your proximity sensor to be sure, that it is not broken: Proximity Sensor Finder
Options you need to try first.
The screen protector, yes it might be transparent but the sensor detects it. Using a sensor testing app from the market it suggested the sensor was covered almost all the time.
So the solution was replace the protector with new one but cut an arc at the top just big enough around the sensor at the top left, easy fix now in call screen is more responsive.
With a vacuum cleaner vacuum over the top area of the phone. This must suck all the dust out of there.
<-------------------------------------->
1 of the other option would be an app called Anyunlock which seems to have solved the problem for me. It seems to be able to wake up when the screen turns off after a call. The app allows you to unlock with the volume key and replaces the lock screen with its own screen.
This option works on my Desire S
<-------------------------------------->
If it's broken, you'll see 0.0 cm all the time.
Solution to disable proximity sensor incall is to put this line into build.prop and reboot:
you can edit the build.prop by pulling it first from the device by doing:
Code:
adb pull /system/build.prop c:\where\you\want\to\put\it\
open with wordpad and add the following line
Code:
gsm.proximity.enable=false
Then
Code:
adb remount
adb push c:\where\you\want\to\put\it\build.prop /system/
reboot so that the settings take effect
This option works on my Desire S
Credits
For disabling the proximity sensor in call go to Matri}{
Rest of the credits go to all the people that figured the other stuff out. (to many post on the net so I don't know who made them but thanks)
Thanks to myself for making this tutorial. (It's my first on xda)
If you have any other idea's just pm me or drop a post.
Thanks
Reserved
Thanks for the guide, it seems that there are quite some people affected by this and I find it much useful. Just a suggestion - IMO more proper place for it will be the General section, so you can request moving it there from the moderators and also adding it to the Index thread (PM ben_pyett)
Sent from my Desire S
Hey,
I just tried your fix but it didn't work for me. Screen still goes black when receiving a call and only reacts when I plug it in through USB. Could it be because my ROM is ICS?
Also tried removing the screen cover & sucking out the dust on the top.
The Anyunlock app works, but that's not ideal of course.
Yes it could be that it's Rom related. I use Endymion. And matri}{ extracted it from the Rom.
Wich Rom do you use. I can take a look for you tonight when I get home.
The anylock works most off as between solution.
Sent from my HTC Desire S using Tapatalk 2
Hey,
I tried it on MIUI ICS, Endymion which both failed. Now I'm using the Reaper ROM but it still doesn't work.
It should work on Endymion. I used it and I even checked if it's the same proximity line in de file of update 3.5.
Did you changed it on the phone or with a text editor on the computer?
I tested it on Endymion just 5 min ago and it worked.
Does your screen still stays black after hanging up? If so can you only unlock with USB cable or power cable?
Sent from my HTC Desire S using Tapatalk 2
Hm, you're right, it does work on Endymion (sorry). I'm having some stability problems with that ROM though...
Do you know how to enable it on MIUI or Reaper (CM based)?
I'm going to check for you tomorrow ok. I'll get back to you.
I just discovered that there is a setting in the MIUI dialer to disable the proximity sensor! This also works, sorry for taking up your time.
But maybe a new suggestion for people who don't want to edit the build file ? Try MIUI!
Solution to disable proximity sensor incall is to put this line into build.prop and reboot:
you can edit the build.prop by pulling it first from the device by doing:
Code:
adb pull /system/build.prop c:\where\you\want\to\put\it\
open with wordpad and add the following line
Code:
gsm.proximity.enable=false
Then
Code:
adb remount
adb push c:\where\you\want\to\put\it\build.prop /system/
reboot so that the settings take effect
This option works on my Desire S
Click to expand...
Click to collapse
if anyone could explain this in noob terms it would be much apprecited
New kid on the block
papaganz said:
I just discovered that there is a setting in the MIUI dialer to disable the proximity sensor! This also works, sorry for taking up your time.
But maybe a new suggestion for people who don't want to edit the build file ? Try MIUI!
Click to expand...
Click to collapse
Hey, I'm a TOTAL rookie at this stuff guys...........can you talk me through this process step by step. The sensor is banjaxed (tested it) and I need to turn the thing off.
Thanks in advance!
Larpogue said:
Hey, I'm a TOTAL rookie at this stuff guys...........can you talk me through this process step by step. The sensor is banjaxed (tested it) and I need to turn the thing off.
Thanks in advance!
Click to expand...
Click to collapse
Well, if you install a MIUI-based ROM (check the android development forum here), you can just go to your dialer settings and select the option.
rolfharris said:
if anyone could explain this in noob terms it would be much apprecited
Click to expand...
Click to collapse
it works good.
the easiest way is to install rom toolbox app on a rooted phone, go to buildprop editor and add the line, click save and reboot
---------- Post added at 10:15 PM ---------- Previous post was at 10:12 PM ----------
papaganz said:
Well, if you install a MIUI-based ROM (check the android development forum here), you can just go to your dialer settings and select the option.
Click to expand...
Click to collapse
---------- Post added at 10:16 PM ---------- Previous post was at 10:15 PM ----------
papaganz said:
Well, if you install a MIUI-based ROM (check the android development forum here), you can just go to your dialer settings and select the option.
Click to expand...
Click to collapse
the easiest way is to install rom toolbox app on a rooted phone, go to buildprop editor and add the line gsm.proximity.enable=false
click save and reboot
Aprentice_ said:
it works good.
the easiest way is to install rom toolbox app on a rooted phone, go to buildprop editor and add the line, click save and reboot
---------- Post added at 10:15 PM ---------- Previous post was at 10:12 PM ----------
---------- Post added at 10:16 PM ---------- Previous post was at 10:15 PM ----------
the easiest way is to install rom toolbox app on a rooted phone, go to buildprop editor and add the line gsm.proximity.enable=false
click save and reboot
Click to expand...
Click to collapse
Thanks man for your advise but how do u root a phone (he asks cringeing!) Soory dude but I did say I was a rookie
papaganz said:
Well, if you install a MIUI-based ROM (check the android development forum here), you can just go to your dialer settings and select the option.
Click to expand...
Click to collapse
Larpogue said:
Thanks man for your advise but how do u root a phone (he asks cringeing!) Soory dude but I did say I was a rookie
Click to expand...
Click to collapse
Since you're flashing a custom ROM than it's already rooted
Aprentice_ said:
Since you're flashing a custom ROM than it's already rooted
Click to expand...
Click to collapse
Nope don't think so, "Root Check Failed" hits me when i open the app.
Oh..umm...download this zip file, unzip anywhere on your computer, connect the USB cable to your phone and run the bat file.
http://forum.xda-developers.com/attachment.php?attachmentid=841876&d=1325678726
Aprentice_ said:
Oh..umm...download this zip file, unzip anywhere on your computer, connect the USB cable to your phone and run the bat file.
http://forum.xda-developers.com/attachment.php?attachmentid=841876&d=1325678726
Click to expand...
Click to collapse
Ok bud will do, I'll let you know how I get on
Aprentice_ said:
the easiest way is to install rom toolbox app on a rooted phone, go to buildprop editor and add the line gsm.proximity.enable=false
click save and reboot
Click to expand...
Click to collapse
That's not true. In my experience this line only works in Sense ROMs...
Related
I created a well-received and ever-growing solution to GPS issues for the Inspire 4G and the DesireHD. POSSIBLY, it will be available for the Sensation in the near future. One user has used it and has had great success.
I'm wanting to determine if it works well with this device.
I believe it will and should work well with almost any Android devices. But, I don't have them to test from.
If anyone is willing to test, you can download the patch and read notes and details on http://forum.xda-developers.com/showthread.php?t=1250226 thread.
It would require backing up your existing configuration and flashing a ZIP using Clockwork Recovery. The only thing the patch does is REPLACE your GPS.CONF with a properly built one.
This can be a useful patch for anyone using custom ROMs.
Respond here to tests and successes!!!
THANK YOU!
crypted said:
I created a well-received and ever-growing solution to GPS issues for the Inspire 4G and the DesireHD.
I'm wanting to determine if it works well with this device.
I believe it will and should work well with almost any Android devices. But, I don't have them to test from.
If anyone is willing to test, you can download the patch and read notes and details on http://forum.xda-developers.com/showthread.php?t=1250226 thread.
It would require backing up your existing configuration and flashing a ZIP using Clockwork Recovery. The only thing the patch does is REPLACE your GPS.CONF with a properly built one.
This can be a useful patch for anyone using custom ROMs.
Respond here to tests and successes!!!
THANK YOU!
Click to expand...
Click to collapse
I'll take a stab at it. I have a custom one running as well from another thread where I get 8 sats locking on eventually.
Sounds good. Got the two devices I can easily support/test doing quite well. I'd just like to share this with as many as I can, but without a device it's hard to know who would benefit.
Initial flash made my phone bork lol. It wouldn't boot up. Did a adb reboot and a system error window showed up.
Tried the 2nd time and booted up fine. Weird. I guess next time I'll just push the gps.conf. .
Ok I'll report back on the locks tomorrow. I'll test out the gps locks tonight before bed.
kpjimmy said:
Initial flash made my phone bork lol. It wouldn't boot up. Did a adb reboot and a system error window showed up.
Tried the 2nd time and booted up fine. Weird. I guess next time I'll just push the gps.conf. .
Ok I'll report back on the locks tomorrow. I'll test out the gps locks tonight before bed.
Click to expand...
Click to collapse
That is extremely weird. How did you flash it?
crypted said:
That is extremely weird. How did you flash it?
Click to expand...
Click to collapse
Via recovery using the latest CWM of course . Using Coredroid 2.4 rom using the Faux123 kernel: 1.4 1.58nohtz.
And to update, I rebooted once more to see if I could replicate that error upon reboot. And did unfortunately.
Now I am going to try to just revert to my old nandroid and just push the gps.conf file and report back.
I go into recovery,
I always wipe cache partition and dalvik partition
mount system
flash nagps1.2.zip
reboot
And twice so far I have gotten a boot error message. Looks like a sense issue. Because it offers to force close or wait. I press force close and the screen goes blank but the screen is still "on". Just a blank black screen with the backlight on. Even pressing the power button only turns off the screen and then on again if I hit the power button the second time.
The only annoyance with this is that I have to redo my bootani now lol....
EDIT: Pushing the gps.conf file worked instead of flashing. GPS locked instantly. I was getting about 8-9 sats locking in from the bedroom window. Not too shabby!
I have attached the gps.conf file. Just unzip the rar, and adb push the gps.conf file to /system/etc, reboot and enjoy.
crypted said:
I created a well-received and ever-growing solution to GPS issues for the Inspire 4G and the DesireHD.
I'm wanting to determine if it works well with this device.
I believe it will and should work well with almost any Android devices. But, I don't have them to test from.
If anyone is willing to test, you can download the patch and read notes and details on http://forum.xda-developers.com/showthread.php?t=1250226 thread.
It would require backing up your existing configuration and flashing a ZIP using Clockwork Recovery. The only thing the patch does is REPLACE your GPS.CONF with a properly built one.
This can be a useful patch for anyone using custom ROMs.
Respond here to tests and successes!!!
THANK YOU!
Click to expand...
Click to collapse
Some questions:
If use your worldwide file on my rooted sensation, can I just copy the gps.conf to rewrite the original one at the system folder? Or I should do a Recovery flash but does the file update-binary and updater-script compatible with sensation (andriod 2.3.4. sense 3.0)?
kpjimmy said:
Via recovery using the latest CWM of course . Using Coredroid 2.4 rom using the Faux123 kernel: 1.4 1.58nohtz.
And to update, I rebooted once more to see if I could replicate that error upon reboot. And did unfortunately.
Now I am going to try to just revert to my old nandroid and just push the gps.conf file and report back.
I go into recovery,
I always wipe cache partition and dalvik partition
mount system
flash nagps1.2.zip
reboot
And twice so far I have gotten a boot error message. Looks like a sense issue. Because it offers to force close or wait. I press force close and the screen goes blank but the screen is still "on". Just a blank black screen with the backlight on. Even pressing the power button only turns off the screen and then on again if I hit the power button the second time.
The only annoyance with this is that I have to redo my bootani now lol....
EDIT: Pushing the gps.conf file worked instead of flashing. GPS locked instantly. I was getting about 8-9 sats locking in from the bedroom window. Not too shabby!
I have attached the gps.conf file. Just unzip the rar, and adb push the gps.conf file to /system/etc, reboot and enjoy.
Click to expand...
Click to collapse
The boot issue is from the nohz kernel. I've had it happen quite a few times and so have others.
Sdobron said:
The boot issue is from the nohz kernel. I've had it happen quite a few times and so have others.
Click to expand...
Click to collapse
soma900 said:
Some questions:
If use your worldwide file on my rooted sensation, can I just copy the gps.conf to rewrite the original one at the system folder? Or I should do a Recovery flash but does the file update-binary and updater-script compatible with sensation (andriod 2.3.4. sense 3.0)?
Click to expand...
Click to collapse
So you flashed it fine with CRW? Or, are you just copying it over? You can just copy it over. My ZIP's updater script only copies the gps.conf over; it does nothing else. It's easiest for people to have a flashable ZIP.
Do you know how to get around the problem with the NOHZ kernel? That way people could flash it?
I'd like to find a suitable way to supply this to users and start doing a Sensation release.
---------- Post added at 08:09 AM ---------- Previous post was at 08:03 AM ----------
kpjimmy said:
Via recovery using the latest CWM of course . Using Coredroid 2.4 rom using the Faux123 kernel: 1.4 1.58nohtz.
And to update, I rebooted once more to see if I could replicate that error upon reboot. And did unfortunately.
Now I am going to try to just revert to my old nandroid and just push the gps.conf file and report back.
I go into recovery,
I always wipe cache partition and dalvik partition
mount system
flash nagps1.2.zip
reboot
And twice so far I have gotten a boot error message. Looks like a sense issue. Because it offers to force close or wait. I press force close and the screen goes blank but the screen is still "on". Just a blank black screen with the backlight on. Even pressing the power button only turns off the screen and then on again if I hit the power button the second time.
The only annoyance with this is that I have to redo my bootani now lol....
EDIT: Pushing the gps.conf file worked instead of flashing. GPS locked instantly. I was getting about 8-9 sats locking in from the bedroom window. Not too shabby!
I have attached the gps.conf file. Just unzip the rar, and adb push the gps.conf file to /system/etc, reboot and enjoy.
Click to expand...
Click to collapse
If you have a chance, try a different kernel possibly and see if soma's point is correct?
How was your GPS working prior to flashing this?
If we can get a reliable method for installation, I think I can start supporting an aGPS option for Sensation.
crypted said:
So you flashed it fine with CRW? Or, are you just copying it over? You can just copy it over. My ZIP's updater script only copies the gps.conf over; it does nothing else. It's easiest for people to have a flashable ZIP.
Do you know how to get around the problem with the NOHZ kernel? That way people could flash it?
I'd like to find a suitable way to supply this to users and start doing a Sensation release.
---------- Post added at 08:09 AM ---------- Previous post was at 08:03 AM ----------
If you have a chance, try a different kernel possibly and see if soma's point is correct?
How was your GPS working prior to flashing this?
If we can get a reliable method for installation, I think I can start supporting an aGPS option for Sensation.
Click to expand...
Click to collapse
I want to say soma is correct with regards to the kernel. Prior to pushing your file over, my gps was fast, but wasn't as fast as yours. Meaning its a matter of seconds really. Whereas I run gps fix and now I got a fix before the map loads up, which never happened in the past.
As for trying it with a different kernel, I'll do that later maybe after work if my 3 yr old stops "helping" me on my netbook lol.
As for a faster and more reliable way of installing your gps.conf, IMO is to just simply push the file to the /system/etc folder. But I know a lot of people are wary of adb commands and much rather flash and forget it, but I think trying out adb commands are worth the practice and with this it's easy peasy to push it over via adb. As for a simple flash, well I guess if they are on a stock kernel they can try to flash it once you mount your system under recovery. Or when flashing a new rom or update, they can revert and flash a stock kernel first, flash your zip file and reboot, but seems like a bit more work than just pushing the gps.conf file.
With either extracting your gps.conf or mine stripped down with your info, here's a basic adb/shell command thread to help people on their way if they choose to.
http://forum.xda-developers.com/showthread.php?t=517874
Back to topic: as stated before, locking onto my gps now is a breeze. Thanks!
---------- Post added at 08:59 AM ---------- Previous post was at 08:52 AM ----------
soma900 said:
Some questions:
If use your worldwide file on my rooted sensation, can I just copy the gps.conf to rewrite the original one at the system folder? Or I should do a Recovery flash but does the file update-binary and updater-script compatible with sensation (andriod 2.3.4. sense 3.0)?
Click to expand...
Click to collapse
Make a backup of your current gps.conf from your phone under /system/etc so you can revert back to that file if this one doesn't work for you.
As for installation, just push that file over or even use root explorer.
EDIT 2. From work (office window with view of sky), I tried to get a lock but it did not lock even though gps test saw the sats. Ever since flashing roms, I think wifi has a conflicting issue when trying to get a gps lock. I then turned off wifi, let the phone sit for a minute to let it get the 4g up and going and then tried the gps test again. I then got 8 sats and then opened up gps fix to see how fast I could get a fix and like before, the gps locked my location before it fully loaded up. Pretty cool IMO. LOL
And after the lock, I can go ahead and turn wifi on again and it no longer conflicts with the gps lock issue. Weird work around, but that's how I have been able to get gps locking to work.
kpjimmy said:
I want to say soma is correct with regards to the kernel. Prior to pushing your file over, my gps was fast, but wasn't as fast as yours. Meaning its a matter of seconds really. Whereas I run gps fix and now I got a fix before the map loads up, which never happened in the past.
As for trying it with a different kernel, I'll do that later maybe after work if my 3 yr old stops "helping" me on my netbook lol.
As for a faster and more reliable way of installing your gps.conf, IMO is to just simply push the file to the /system/etc folder. But I know a lot of people are wary of adb commands and much rather flash and forget it, but I think trying out adb commands are worth the practice and with this it's easy peasy to push it over via adb. As for a simple flash, well I guess if they are on a stock kernel they can try to flash it once you mount your system under recovery. Or when flashing a new rom or update, they can revert and flash a stock kernel first, flash your zip file and reboot, but seems like a bit more work than just pushing the gps.conf file.
With either extracting your gps.conf or mine stripped down with your info, here's a basic adb/shell command thread to help people on their way if they choose to.
http://forum.xda-developers.com/showthread.php?t=517874
Back to topic: as stated before, locking onto my gps now is a breeze. Thanks!
---------- Post added at 08:59 AM ---------- Previous post was at 08:52 AM ----------
Make a backup of your current gps.conf from your phone under /system/etc so you can revert back to that file if this one doesn't work for you.
As for installation, just push that file over or even use root explorer.
EDIT 2. From work (office window with view of sky), I tried to get a lock but it did not lock even though gps test saw the sats. Ever since flashing roms, I think wifi has a conflicting issue when trying to get a gps lock. I then turned off wifi, let the phone sit for a minute to let it get the 4g up and going and then tried the gps test again. I then got 8 sats and then opened up gps fix to see how fast I could get a fix and like before, the gps locked my location before it fully loaded up. Pretty cool IMO. LOL
And after the lock, I can go ahead and turn wifi on again and it no longer conflicts with the gps lock issue. Weird work around, but that's how I have been able to get gps locking to work.
Click to expand...
Click to collapse
I think I know how to resolve that wifi issue. I can give you the test version of 1.3.
If v1.3 works fine AND if you can help me draft instructions on specifically installing on your device, I can post the full-support thread.
Are you up for this? If so, please draft and message me instructions. And, I'll send you the test version of 1.3 for your flashing pleasure.
Well ..didn't seem to do any good for me ... stock rom .. rooted.
There has to be a way to allow it to position based on less satellites .... damn it.
steve841 said:
Well ..didn't seem to do any good for me ... stock rom .. rooted.
There has to be a way to allow it to position based on less satellites .... damn it.
Click to expand...
Click to collapse
All: try these two patches individually instead: http://derekgordon.com/gps-files/worldwide1.2-t.zip and http://derekgordon.com/gps-files/worldwide1.2-tn.zip
If one doesn't work well, try the other. This solved a problem with some Tunisia users. It has to do with GPS and Wifi conflicts when the phone has an older GPS unit built in.
crypted said:
I think I know how to resolve that wifi issue. I can give you the test version of 1.3.
If v1.3 works fine AND if you can help me draft instructions on specifically installing on your device, I can post the full-support thread.
Are you up for this? If so, please draft and message me instructions. And, I'll send you the test version of 1.3 for your flashing pleasure.
Click to expand...
Click to collapse
What do you want me to draft up? I'd help if I can of course. OH nvm I think I got it lol....sending you a pm.
kpjimmy said:
What do you want me to draft up? I'd help if I can of course. OH nvm I think I got it lol....sending you a pm.
Click to expand...
Click to collapse
Thanks.
All: let me know how those test builds (posted above) and the one in private message (kpjimmy) work out on your Sensations. I feel confident that we can make this release happen next week when v1.3 comes out.
crypted said:
So you flashed it fine with CRW? Or, are you just copying it over? You can just copy it over. My ZIP's updater script only copies the gps.conf over; it does nothing else. It's easiest for people to have a flashable ZIP.
Do you know how to get around the problem with the NOHZ kernel? That way people could flash it?
I'd like to find a suitable way to supply this to users and start doing a Sensation release.
---------- Post added at 08:09 AM ---------- Previous post was at 08:03 AM ----------
If you have a chance, try a different kernel possibly and see if soma's point is correct?
How was your GPS working prior to flashing this?
If we can get a reliable method for installation, I think I can start supporting an aGPS option for Sensation.
Click to expand...
Click to collapse
Dear crypted,
Your configure script works on HTC sensation. Thanks! Great work! Got a lock in 10 seconds. before it is really difficult and take ages to get a lock.
Did not flash it just change the file property "readonly" with RE. Copy and overwrite.
I am sorry I do not understand what is an NOHZ kernel. I am a noob.
By the way I am using a modded ROM of LeeDroid 3.1.0. S-OFF, Revolution recovery 5.0.2.0. Thus ROOTED. Now every program use GPS-sat get a quick lock within 10 seconds. You shall promote your script to every ROM-devs. I highly recommand your script!
Yeah ... if you could just post the gps.conf file ... I find that much easier to add using file explorer rather than flashing the .zip.
Thanks.
soma900 said:
Dear crypted,
Your configure script works on HTC sensation. Thanks! Great work! Got a lock in 10 seconds. before it is really difficult and take ages to get a lock.
Did not flash it just change the file property "readonly" with RE. Copy and overwrite.
I am sorry I do not understand what is an NOHZ kernel. I am a noob.
By the way I am using a modded ROM of LeeDroid 3.1.0. S-OFF, Revolution recovery 5.0.2.0. Thus ROOTED. Now every program use GPS-sat get a quick lock within 10 seconds. You shall promote your script to every ROM-devs. I highly recommand your script!
Click to expand...
Click to collapse
steve841 said:
Yeah ... if you could just post the gps.conf file ... I find that much easier to add using file explorer rather than flashing the .zip.
Thanks.
Click to expand...
Click to collapse
Okay. If y'all could private message instructions on how to copy the GPS configuration over to the /system/etc folder, I would appreciate it.
I have one set of instructions sent to me thus far. I'd just want to make sure we have all of the various methods ready to post when I release the Sensation version.
Faux kernel no go for me so I am trying another. The bricked 0.5ver. Flashing now and will report back.
EDIT:Back in the office. Flashed the bricked 0.5 v kernel and then flashed the test 1.3 gps script.
Got about 5 sats in use and in view using GPS test and locked it with 10 seconds. Not as fast as 1.2 but still quick. Maybe because it's looking at the worldwide servers before seeing where I am? I was using 1.2 US gps script.
---------- Post added at 01:55 PM ---------- Previous post was at 01:38 PM ----------
steve841 said:
Yeah ... if you could just post the gps.conf file ... I find that much easier to add using file explorer rather than flashing the .zip.
Thanks.
Click to expand...
Click to collapse
Just download whichever file you want to use and extract the zip under system/etc and then push the gps.conf over via adb or root explorer.
I'm surprised at there being a decrease in v1.3. Possibly a placebo effect. Hmmm.
Sent from my Inspire 4G using XDA App
I had just received a fresh new Galaxy SIII from Asurion and eagerly rooted and flashed my favorite AOSP ROM and found out my camera wasn't working. I search through these forums like a mad man trying to find a solution and I tried EVERYTHING but then I read someone's reply to troubleshooting and I admit I may have been overlooking the wording in some of these guides as to the path of my camera files but I fixed it and I want to share my findings so someone who is having a similar issue can get it fixed too. I'm also going to add the methods that didn't work but may work in other cases.
This fix ultimately replaces bad or missing firmware files. If you haven't tried Odin back to stock, re-rooting, or wiping data and getting a fresh start, I would recommend that first. This is more or less if sh** hits the fan.
THIS IS ONLY FOR THE GALAXY SIII
***MY FIX***
BACKUP ANYTHING IMPORTANT JUST IN CASE
Download this zip https://dl.dropboxusercontent.com/u/91693945/CameraFiles-signed.zip
Flash using Recovery
Wipe Cache & Dalvik (optional)
Fix Permissions
Reboot into Android
Start the camera app and cross your fingers
***MY FIX (Old Way)***
Download any TouchWiz based ROM to your phone or computer.
Unzip the ROM
Goto /system/cameradata and copy all the SlimISP files to your phone.
Goto /data and there should be another SlimISP bin file, copy that but don't mix it up.
Move these to the files to the corresponding areas of your phone.
Check permissions, I granted full access to Root, and User
Start the camera app and cross your fingers
Reboot if it didn't work immediately
I recommend keeping a copy of these on your ExtSD if you have one because you will have to do this if you flash a new ROM.
***Other Guides***
Same sort of directions also contains files you can download.
http://forum.xda-developers.com/showthread.php?p=40409206#post40409206
This is an explanation to what I put above and the guide that ultimately fixed my problems (Single-Post rest of thread is helpful too).
http://forum.xda-developers.com/showpost.php?p=37257851&postcount=11
For all you TouchWiz lovers, this might not be as relevant anymore but I'm putting it here anyway.
http://forum.xda-developers.com/showthread.php?t=2006128
SlimSnoopOS posted this below and I'll add it here.
http://rootzwiki.com/topic/100194-cant-connect-to-the-camera-again/page-2
If people have questions post them here or PM me I want to help anyone having this issue. Being as attached to my phone as I am I was really put out by all the trial and error.
Appreciate the guide, hope it helps someone down the road. I'm in the camp that has no issues going back and forth between AOSP 4.3 or TW. I'll add this Rootz link as well which provides some additional information and might be making its way into roms via Github. Seems like as good an opportunity to spread the wealth.
Zophone i5 v8?
dwibbles33 said:
I had just received a fresh new Galaxy SIII from Asurion and eagerly rooted and flashed my favorite AOSP ROM and found out my camera wasn't working. I search through these forums like a mad man trying to find a solution and I tried EVERYTHING but then I read someone's reply to troubleshooting and I admit I may have been overlooking the wording in some of these guides as to the path of my camera files but I fixed it and I want to share my findings so someone who is having a similar issue can get it fixed too. I'm also going to add the methods that didn't work but may work in other cases.
This fix ultimately replaces bad or missing firmware files. If you haven't tried Odin back to stock, re-rooting, or wiping data and getting a fresh start, I would recommend that first. This is more or less if sh** hits the fan.
***MY FIX***
Download any TouchWiz based ROM to your phone or computer.
Unzip the ROM
Goto /system/cameradata and copy all the SlimISP files to your phone.
Goto /data and there should be another SlimISP bin file, copy that but don't mix it up.
Move these to the files to the corresponding areas of your phone.
Check permissions, I granted full access to Root, and User
Start the camera app and cross your fingers
Reboot if it didn't work immediately
I recommend keeping a copy of these on your ExtSD if you have one because you will have to do this if you flash a new ROM.
***Other Guides***
Same sort of directions also contains files you can download.
http://forum.xda-developers.com/showthread.php?p=40409206#post40409206
This is an explanation to what I put above and the guide that ultimately fixed my problems (Single-Post rest of thread is helpful too).
http://forum.xda-developers.com/showpost.php?p=37257851&postcount=11
For all you TouchWiz lovers, this might not be as relevant anymore but I'm putting it here anyway.
http://forum.xda-developers.com/showthread.php?t=2006128
SlimSnoopOS posted this below and I'll add it here.
http://rootzwiki.com/topic/100194-cant-connect-to-the-camera-again/page-2
If people have questions post them here or PM me I want to help anyone having this issue. Being as attached to my phone as I am I was really put out by all the trial and error.
Click to expand...
Click to collapse
I am facing the same problem on my iphone clone - zophone i5 v8. These models do not have a "cameradata" folder in /system. Do you have a fix for these MTK phones?
shailendrachimade said:
I am facing the same problem on my iphone clone - zophone i5 v8. These models do not have a "cameradata" folder in /system. Do you have a fix for these MTK phones?
Click to expand...
Click to collapse
Me too had problem with camera, but it seems like i got fixed it finally... I have a Cubot One MTK6589 with Miui rom. The steps are:
1. http://d-h.st/BKA download this file and flash it. It will install jb camera for your mobile.
2. check it
3. if it works delete the old camera app with titanium backup because if u run the old bad camera app the problem will come back and u have to flash again.
4. install some good camera app like camera awesome because for me the jb camera doesn't detected my front camera.
I hope this will help you!
Will Try
papp-david said:
Me too had problem with camera, but it seems like i got fixed it finally... I have a Cubot One MTK6589 with Miui rom. The steps are:
1. http://d-h.st/BKA download this file and flash it. It will install jb camera for your mobile.
2. check it
3. if it works delete the old camera app with titanium backup because if u run the old bad camera app the problem will come back and u have to flash again.
4. install some good camera app like camera awesome because for me the jb camera doesn't detected my front camera.
I hope this will help you!
Click to expand...
Click to collapse
Let me try..thanks!
---------- Post added at 05:33 PM ---------- Previous post was at 04:58 PM ----------
shailendrachimade said:
Let me try..thanks!
Click to expand...
Click to collapse
I flashed successfully...but I do not see any camera app installed? I can see the Galary app. Even tried deleting original camera app by Titanium, still same issue.
Thank you. I also had this problem with any aosp ROM but the fix stopped working for me with the kk ROMs did you have the same problem?
Uou need to patch the shared objects using your stock tom files
Sent from my SM-N9006 using xda app-developers app
remzej said:
Uou need to patch the shared objects using your stock tom files
Sent from my SM-N9006 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply.. Bit could you explain a little more?
evertking said:
Thanks for the reply.. Bit could you explain a little more?
Click to expand...
Click to collapse
shailendrachimade said:
Let me try..thanks!
---------- Post added at 05:33 PM ---------- Previous post was at 04:58 PM ----------
I flashed successfully...but I do not see any camera app installed? I can see the Galary app. Even tried deleting original camera app by Titanium, still same issue.
Click to expand...
Click to collapse
dwibbles33 said:
I had just received a fresh new Galaxy SIII from Asurion and eagerly rooted and flashed my favorite AOSP ROM and found out my camera wasn't working. I search through these forums like a mad man trying to find a solution and I tried EVERYTHING but then I read someone's reply to troubleshooting and I admit I may have been overlooking the wording in some of these guides as to the path of my camera files but I fixed it and I want to share my findings so someone who is having a similar issue can get it fixed too. I'm also going to add the methods that didn't work but may work in other cases.
This fix ultimately replaces bad or missing firmware files. If you haven't tried Odin back to stock, re-rooting, or wiping data and getting a fresh start, I would recommend that first. This is more or less if sh** hits the fan.
THIS IS ONLY FOR THE GALAXY SIII
***MY FIX***
BACKUP ANYTHING IMPORTANT JUST IN CASE
Download this zip https://www.dropbox.com/s/bt1ucpgb9xfmjbi/CameraFiles-signed.zip
Flash using Recovery
Wipe Cache & Dalvik (optional)
Fix Permissions
Reboot into Android
Start the camera app and cross your fingers
***MY FIX (Old Way)***
Download any TouchWiz based ROM to your phone or computer.
Unzip the ROM
Goto /system/cameradata and copy all the SlimISP files to your phone.
Goto /data and there should be another SlimISP bin file, copy that but don't mix it up.
Move these to the files to the corresponding areas of your phone.
Check permissions, I granted full access to Root, and User
Start the camera app and cross your fingers
Reboot if it didn't work immediately
I recommend keeping a copy of these on your ExtSD if you have one because you will have to do this if you flash a new ROM.
***Other Guides***
Same sort of directions also contains files you can download.
http://forum.xda-developers.com/showthread.php?p=40409206#post40409206
This is an explanation to what I put above and the guide that ultimately fixed my problems (Single-Post rest of thread is helpful too).
http://forum.xda-developers.com/showpost.php?p=37257851&postcount=11
For all you TouchWiz lovers, this might not be as relevant anymore but I'm putting it here anyway.
http://forum.xda-developers.com/showthread.php?t=2006128
SlimSnoopOS posted this below and I'll add it here.
http://rootzwiki.com/topic/100194-cant-connect-to-the-camera-again/page-2
If people have questions post them here or PM me I want to help anyone having this issue. Being as attached to my phone as I am I was really put out by all the trial and error.
Click to expand...
Click to collapse
The file is not available on dropbox for download , i am using AOKP on SG3 and the camera stops working if i open through whatsapp or any other app and when i go back to the camera it gives that error
Try the One+ One or AOSP modded cameras in the Apps and Themes section. One+ One camera is awesome!
Ahmadqatei said:
The file is not available on dropbox for download , i am using AOKP on SG3 and the camera stops working if i open through whatsapp or any other app and when i go back to the camera it gives that error
Click to expand...
Click to collapse
Link fixed, sorry I don't really keep up with this anymore, my bad
fix front camera
work for my mtk device
edit builtprop, open the editor and change or add
hw.cameras=1
ro.camera.dcim=1
explanation
# hw cameras
hw.cameras = 2 (1 only for the Front, 2 for the Front & Back)
# camera DCIM dir. 0: sd only; 1: nand only; 2, sd first
ro.camera.dcim = 1
This is likely to occur due to the use of internal memory is converted into ROM
while the external sdcard memory is converted into internal
hopefully work
:cyclops:
Just sharing:
flashing didn't work, used servicely and added camera service to hitlist.
can i use it on galaxy core
Hi everybody! I've switched over to CM 10.2 M1 as my daily driver, but I missed being able to change the volume on my tv with my phone. So, I've managed to get the QuickRemote app from the stock ROM working on Cyanogenmod (and hopefully other AOSP roms). There is nothing carrier-specific in this, so it should work on all variants.
Luckily there is no kernel module involved in driving the IR hardware. Instead the IR chip is a black box that is controlled via an internal serial port interface. The QuicksetSDK.apk package includes the code to control the IR chip. It creates a Service that the LGQRemote.apk app binds to to send commands to the IR hardware.
Installation
This will only work on rooted devices.
To get this working you'll need to install two APKs:
QuicksetSDK.apk
LGQRemote.apk
You'll also need to add a script that runs on device boot.
You can download mine here: 10QuickRemote
Or just make one yourself, containing this code:
Code:
#!/system/bin/sh
chmod 666 /dev/ttyHSL1
setprop persist.sys.lge.eula_agreement true
This makes the serial port accessible to non-system processes. On the LG stock rom the QuicksetSDK package runs as the system user, but here we're running it as a normal unprivileged user, so we need to make the serial port world-readable and writable. We also use the 'setprop' command to tell the QuickRemote app that we've agreed to LG's EULA, otherwise it will attempt to launch a non-existent EULA activity and crash.
I'm not 100% sure how the init.d system works on other AOSP roms, but on Cyanogenmod, you can place this script in the /data/local/userinit.d directory (creating the userinit.d directory if necessary). The script should not have an extension, and should be executable.
A quick method that works on CM, assuming you've downloaded my 10QuickRemote script to your current directory:
Code:
adb root
adb shell "mkdir -p /data/local/userinit.d"
adb push 10QuickRemote /data/local/userinit.d
adb shell "chmod 755 /data/local/userinit.d/10QuickRemote
For the above to work, you'll need to enable root for adb in Settings > Developer Options > Root Access
After a reboot, you should be able to use the QuickRemote app just like on the stock ROM!
If the app crashes right away, or if it launches but won't send any IR commands or learn new ones, your start-up script probably isn't being executed properly. Try running it manually and see if things work:
Code:
adb shell
--- inside adb, as root:
# sh /data/local/userinit.d/10QuickRemote
# ls -l /dev/ttyHSL1
-- result should be:
crw-rw-rw- system system 245, 1 2013-11-06 08:20 ttyHSL1
# getprop persist.sys.lge.eula_agreement
-- result should be:
true
If running it manually works, make sure the script is executable or it won't be called automatically on boot:
Code:
-- inside a root shell
# chmod 755 /data/local/userinit.d/10QuickRemote
If it is executable and still doesn't work after a reboot, and you're running a non-Cyanogen ROM, they probably do init scripts differently. Hopefully you can google up how to make it work
If everything looks correct and it still won't work, send me a logcat and I'll try to figure it out.
Enjoy!
sefnap said:
Hi everybody! I've switched over to CM 10.2 M1 as my daily driver, but I missed being able to change the volume on my tv with my phone. So, I've managed to get the QuickRemote app from the stock ROM working on Cyanogenmod (and hopefully other AOSP roms). There is nothing carrier-specific in this, so it should work on all variants.
Luckily there is no kernel module involved in driving the IR hardware. Instead the IR chip is a black box that is controlled via an internal serial port interface. The QuicksetSDK.apk package includes the code to control the IR chip. It creates a Service that the LGQRemote.apk app binds to to send commands to the IR hardware.
Enjoy!
Click to expand...
Click to collapse
thanks so much!!
would it be possible to make this into a flashable zip?
just a quick question am i suppose to see the list of make and models? if so i dont see it... the remote is installed though
nvm... some how the list came out.. not sure what i did. thx for the mod
blkghost22 said:
just a quick question am i suppose to see the list of make and models? if so i dont see it... the remote is installed though
nvm... some how the list came out.. not sure what i did. thx for the mod
Click to expand...
Click to collapse
I have the same issue. You just keep playing around with it?
Sent from my LG-VS980 using Tapatalk
steveo17 said:
I have the same issue. You just keep playing around with it?
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
yes.. but honestly i really dont know what i did... the last thing i did was try to make a universal remote and just cancelled out of it... and installed the sql...apk
---------- Post added at 11:11 AM ---------- Previous post was at 11:09 AM ----------
just figured it out.. the •QuicksetSDK.apk is not running at first.. so i just reinstalled it again... and the list comes up... for some reason i guess it doesnt start.
blkghost22 said:
yes.. but honestly i really dont know what i did... the last thing i did was try to make a universal remote and just cancelled out of it... and installed the sql...apk
---------- Post added at 11:11 AM ---------- Previous post was at 11:09 AM ----------
just figured it out.. the •QuicksetSDK.apk is not running at first.. so i just reinstalled it again... and the list comes up... for some reason i guess it doesnt start.
Click to expand...
Click to collapse
Right i installed it by clicking the apk and installed it like normal. And now it works
Sent from my LG-VS980 using Tapatalk
steveo17 said:
Right i installed it by clicking the apk and installed it like normal. And now it works
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
for some reason tho... once i reboot my phone. i need to install that again.
awesome job!
I've been leery of flashing a custom rom for the lack of IR and other features. Plus I'm really digging the stock rom.
But with AOKP coming soon, I am might be tempted. Good to know that the application works with directly with the IR blaster.
I thought AOSP 4.4 was suppose to have support for IR blasters, but it seems noone has them working on CM yet.
blkghost22 said:
for some reason tho... once i reboot my phone. i need to install that again.
Click to expand...
Click to collapse
Same here
Sent from my LG-VS980 using Tapatalk
blkghost22 said:
yes.. but honestly i really dont know what i did... the last thing i did was try to make a universal remote and just cancelled out of it... and installed the sql...apk
---------- Post added at 11:11 AM ---------- Previous post was at 11:09 AM ----------
just figured it out.. the •QuicksetSDK.apk is not running at first.. so i just reinstalled it again... and the list comes up... for some reason i guess it doesnt start.
Click to expand...
Click to collapse
The list is actually downloaded by the QuicksetSDK app at runtime. I guess they did it that way so they could add models after shipping the phone.
I hope make flash.zip it is easy
Set this up on my D801, works great! It's a little difficult to navigate sometimes because some of the coloring of menus is designed for the stock rom. It seems to be missing the Comcast cable box settings though, it could be possible the app is different on different phones. Either way I just made it "learn" buttons over my TV remote which works way better than the short while I had it on the stock rom. This is the only feature I miss at all from stock, now my phone has every feature I want!
It's really not difficult to use a little terminal/command prompt, people are scared of putting in commands for some silly reason. If you've used ioroot, you already have adb to use too.
nice job!
i made a quick flashable zip package:
http://www43.zippyshare.com/v/86147127/file.html (new slim mod)
-> http://forum.xda-developers.com/showpost.php?p=47500016&postcount=94
(installs in data partition so it should survive a rom update)
RieGo said:
nice job!
i made a quick flashable zip package:
http://www60.zippyshare.com/v/62581043/file.html
(installs in data partition so it should survive a rom update)
Click to expand...
Click to collapse
I get this
Sent from my LG-G2 using XDA Premium 4 mobile app
RieGo said:
nice job!
i made a quick flashable zip package:
http://www60.zippyshare.com/v/62581043/file.html
(installs in data partition so it should survive a rom update)
Click to expand...
Click to collapse
I tried flashing this zip and working fine on mine thank you!
Sent from my LG-D802 using xda app-developers app
RieGo said:
nice job!
i made a quick flashable zip package:
http://www60.zippyshare.com/v/62581043/file.html
(installs in data partition so it should survive a rom update)
Click to expand...
Click to collapse
Flashable works gr8 here as well.... have not rebooted to make sure everything sticks though... tnx guys!
zplit said:
I get this
Sent from my LG-G2 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
which recovery?
which rom?
did you do a manual installation before flashing the zip?
thank you SO MUCH sefnap! and thank you RieGo for the flashable zip. just flashed on PA 4.3 for D801 and everything is working beautifully.
and as mentioned above- if there's any way you could get the lg camera to work, too, you would be the king. it looks like some sort of progress has been made over in this thread. the AOSP camera works well, but i'd love to have the manual focus option, and so on.
thanks again for adding this great functionality back for us! :good:
Thanks. Flashable zip works perfectly with slimbean on D801. This was the only thing I was missing with AOSP. Thanks again
LG D801 on Slimbean
A camera port with official firmware LG can not? If you can, do it please.
And that zip up to 160 MB? Driver? Replacing the files?
MODIFIED TO NOW WORK WITH VERIZON.
Confirmed working on Verizon Retail Edition and Dev Edition (no flashing involved, just what is listed here)
Here's a zip you can flash on firmware NCG. Thanks to @BigBot96
NCG auto enabler
OKAY guys I got it working. See screenshots. AND FOLLOW THESE STEPS
Requirements:
Use this services.jar NOT the one from the zip. https://www.dropbox.com/s/3vjq70yfdxrmmj9/services.jar
Root
ES File Explorer (make sure Root Mode is enabled)
v2.1 odex file from this thread http://forum.xda-developers.com/showthread.php?t=2719582
YMMV, so I recommend copying these two files from your system folder to somewhere safe (external sd or PC) just in case something goes wrong.
GOOD LUCK!
1. Download/unzip the services.odex file from the zip. Download modified services.jar from here (https://www.dropbox.com/s/3vjq70yfdxrmmj9/services.jar )
2. Copy Both files to the /system root folder
3. Fix all permissions to rw-r-r (3 checks in first column, first check in second, rest blank) DOUBLE CHECK THIS (See Attached)
4. Copy services.JAR from the system root folder to the /system/framework folder, overwrite.
5. Copy services.ODEX from the system root folder to the /system/framework folder, overwrite again.
6. Reboot
Mine took a few minutes to boot up, and reodexed everything "Android is updating apps".
?????
Profit.
CLICK THANKS.
btw HUGE thanks to RevelationOmega for doing the hard part!!
Also thanks to joshw0000 and Joderme for testing/helping me come up with this!
TURNING ON DOWNLOAD BOOSTER
CREATE A SHORTCUT TO ENABLE
1. Download AnyCut from the play store (icon is a mushroom)
2. Open the app, and choose New Shortcut > Activity
3. Find Download Booster
4. This should add a shortcut icon to your Home Screen
5. Use shortcut to turn it on.
TO GET THE QUICKSETTINGS TILE
1. Download SQlite editor (the one in the screenie works best)
2. In apps, find settings storage > settings.db > system
3. Search for notification
4. Find the three labeled Notification_Panel_Active_App_List, notification_panel_default_active_app_list and Notification_Panel_Active_App_List_for_Reset, add it to all of these.
5. Add NetworkBooster; as seen in screenshot attached.
6. Go to Settings > Notification Panel > and press Reset
7. Reboot
TESTING DOWNLOAD BOOSTER
0. Make sure you are connected to WIFI and LTE (Does not work on regular 4G or lower)
1. Open the Play Store
2. Find the app called DCIkonZ (or any app over 30 mb)
3. Install app as normal. You should get a popup as seen in attached and see a toast saying Download Booster enabled...
If you'd like to donate just PM me for PayPal. Hope you enjoy.
This bricked my Verizon S5 don't do it...
Jace300 said:
This bricked my Verizon S5 don't do it...
Click to expand...
Click to collapse
Thanks that this came up, was in process of getting everything ready now. Will wait til a Verizon person is able to successfully do this with proof of screenshots.
Dennisg34 said:
Thanks that this came up, was in process of getting everything ready now. Will wait til a Verizon person is able to successfully do this with proof of screenshots.
Click to expand...
Click to collapse
Got my hopes up...
Yeah don't do this... now my phone is stuck on the Verizon logo.. I don't know how to fix it! :|
Jace300 said:
Yeah don't do this... now my phone is stuck on the Verizon logo.. I don't know how to fix it! :|
Click to expand...
Click to collapse
Try this, can't hurt
http://forum.xda-developers.com/showthread.php?t=2784880
If your phone won't boot, take it to your local Best Buy. The Samsung people have a reflash tool that can fix your phone. Not sure if you guys have a odin image or not just wanted to let you know.
I'm sorry guys. I hoped it would work.
Guess I took one for the team... Thank you for the help!
Jace300 said:
Guess I took one for the team... Thank you for the help!
Click to expand...
Click to collapse
Did you try flashing back to stock in Odin? Can't hurt...then just re root
Dennisg34 said:
Did you try flashing back to stock in Odin? Can't hurt...then just re root
Click to expand...
Click to collapse
Its flashing as we type.
---------- Post added at 05:40 AM ---------- Previous post was at 05:35 AM ----------
chronicaust said:
If your phone won't boot, take it to your local Best Buy. The Samsung people have a reflash tool that can fix your phone. Not sure if you guys have a odin image or not just wanted to let you know.
I'm sorry guys. I hoped it would work.
Click to expand...
Click to collapse
Please edit the OP and say it will soft brick on VZW variants... So don't try it
Jace300 said:
Its flashing as we type.
---------- Post added at 05:40 AM ---------- Previous post was at 05:35 AM ----------
Please edit the OP and say it will soft brick on VZW variants... So don't try it
Click to expand...
Click to collapse
Let me know how it goes! Yeah he already changed it !
Dennisg34 said:
Let me know how it goes! Yeah he already changed it !
Click to expand...
Click to collapse
Looks like flashing did the trick, thanks alot!!!
Jace300 said:
Looks like flashing did the trick, thanks alot!!!
Click to expand...
Click to collapse
No problem! Figured it can only be a soft brick easily fixed by flashing stock again. Better to re-set everything up and do a 15 second root than it is going about having to get a whole new phone
Dennisg34 said:
No problem! Figured it can only be a soft brick easily fixed by flashing stock again. Better to re-set everything up and do a 15 second root than it is going about having to get a whole new phone
Click to expand...
Click to collapse
yea.. if his phone can get to boot screen good chance to save it usin odin.. this thread should b closed lol dunno y someone posted in our forum when we have a dif variant.. glad no hard bricks came of it
Sent from my SM-G900V using XDA Premium HD app
Yup just barely finished restoring back to stock. Now I have to set up my settings again.
Droid_Evo_8 said:
Yup just barely finished restoring back to stock. Now I have to set up my settings again.
Click to expand...
Click to collapse
in the same boat as you. didnt see the change on it not working for vzw... restoring now
bruderhood15 said:
in the same boat as you. didnt see the change on it not working for vzw... restoring now
Click to expand...
Click to collapse
Same here, bud. Just debloating everything again. (At least the root works)
Droid_Evo_8 said:
Same here, bud. Just debloating everything again. (At least the root works)
Click to expand...
Click to collapse
Might be a bit late.. but chances are ADB was still active. When I was trying out to remove the hotspot restriction manuaĺly, by uploading a recompiled framework-res.apk, it also got stuck at the verizon logo in the boot process but i was still able to use adb to replace the file with the original and when it finished copying the phone completely booted.
Anyone willing to send me their services.jar file and test for me? I'll see if I can get this working for you guys.
chronicaust said:
Anyone willing to send me their services.jar file and test for me? I'll see if I can get this working for you guys.
Click to expand...
Click to collapse
sent. i'll also send a link to the rest of the framework directory if you should need any other files.
This is a tested and working Exchange Security Bypass that I am using on my AT&T LG G3. This mod should work on any variant of LG G3 that is running stock or AOSP ROM's.
All credit goes to the below developer, I was simply looking for a solution to bypass the exchange security policy that required me to have a password or pin on my lockscreen. After several tests using Xposed Framework and other APK's I came across this and it works flawlessly. You can see the developers thread here.
http://forum.xda-developers.com/showthread.php?t=1965468
DISCLAIMER: I'm not responsible if:
• You get caught by your employer and are punished in any way
• This bricks, breaks, scratches, dents, misplaces or cracks your phone
• This security bypass leads to any negative outcome.
USE THIS AT YOUR OWN RISK.
I have rooted my phone and used Root Browser to perform the following steps (You can use ADB as well, please follow the guide in the link above).
Instructions:
1. MAKE A BACKUP OF YOUR STOCK EMAIL (LGEmail.apk & LGEmail.odex) - Copy and place it in another folder incase anything happens and you want to revert.
*Stock LG Email is located in system/priv-app2. After your make a backup, delete the stock LGEmail.apk and LGEmail.odex files
3. Download the files attached to this post and put them in the system/app folder
4. Change the permissions of the two new APK's (Exchange2.apk & Email.apk) to rw-r-r (DON'T FORGET TO DO THIS)
4. Once the 2 files (Exchange2.apk & Email.apk) are placed in your system/app folder, click on them and install
5. That's it...close out of your root explorer, open your new email app and set up your exchange account. :good:
I hope this helps users who are looking for a solution to their exchange security issues like I was. Enjoy
btw u can only do this if u are rooted..for those who arent dont even try it
crazyagg said:
1. MAKE A BACKUP OF YOUR STOCK EMAIL (LGEmail.apk & LGEmail.odex) - Copy and place it in another folder incase anything happens and you want to revert.
*Stock LG Email is located in system/priv-app2. After your make a backup, delete the stock LGEmail.apk and LGEmail.odex files
Click to expand...
Click to collapse
It should not be necessary to delete the LGE apps, the two can work side by side. And if you are set on disabling the LGE app it is probably better to freeze it with TBU than delete, in case you change your mind later.
Those contemplating the use of this mod should keep in mind that the LGE stock email app is FAR, FAR, FAR more intelligent than the stock KK email app when it comes to autoconfiguring your Exchange connection. In fact I recommend running the LGE stock app first, then going into settings and taking a screenshot to document how the account was configured. You will almost certainly have to enter this information manually into the KK app because it will be unable to figure it out on its own.
Why not just edit data\system locksettings.db ?
canecbr600 said:
Why not just edit data\system locksettings.db ?
Click to expand...
Click to collapse
Because I'm nit sure what to edit, I've always just used a hacked APK. Please feel free to shed some light though and provide a little more detail.
You've peaked my interest.
Sent from my LG-D850 using XDA Premium 4 mobile app
crazyagg said:
Because I'm nit sure what to edit, I've always just used a hacked APK. Please feel free to shed some light though and provide a little more detail.
You've peaked my interest.
Sent from my LG-D850 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Go to data/system and there is a file locksettings.db. Open it in SQL editor. Next tap on locksettings, and u should have a item listed as lockscreen.password_type . Change the value for this to 0. That will change lockscreen to swipe to unlock.....
canecbr600 said:
Go to data/system and there is a file locksettings.db. Open it in SQL editor. Next tap on locksettings, and u should have a item listed as lockscreen.password_type . Change the value for this to 0. That will change lockscreen to swipe to unlock.....
Click to expand...
Click to collapse
I'm assuming I'd need to set up exchange first and once it enforces the password lock I'd need to modify the file? I would assume when adding an exchange account it would change change that value.
Sent from my LG-D850 using XDA Premium 4 mobile app
crazyagg said:
I'm assuming I'd need to set up exchange first and once it enforces the password lock I'd need to modify the file? I would assume when adding an exchange account it would change change that value.
Sent from my LG-D850 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes sir, you got it. I always use this method, with stock exchange email.
LG Email has no widget, which is a killer for me. I'm following all the directions above but unable to install the Exchange, though the Email was easily installed. Any thoughts on why?
---------- Post added at 10:02 AM ---------- Previous post was at 10:00 AM ----------
Has anyone tried this method?
http://forum.xda-developers.com/showthread.php?t=1749921
canecbr600 said:
Go to data/system and there is a file locksettings.db. Open it in SQL editor. Next tap on locksettings, and u should have a item listed as lockscreen.password_type . Change the value for this to 0. That will change lockscreen to swipe to unlock.....
Click to expand...
Click to collapse
Does that work for all exchange policies?? If so f'ing awesome
---------- Post added at 07:13 PM ---------- Previous post was at 06:59 PM ----------
bjc112 said:
Does that work for all exchange policies?? If so f'ing awesome
Click to expand...
Click to collapse
Worked great. Thanks so much. Now I can dump stock kit kat exchange hacked email app.
JPD19 said:
LG Email has no widget, which is a killer for me. I'm following all the directions above but unable to install the Exchange, though the Email was easily installed. Any thoughts on why?
---------- Post added at 10:02 AM ---------- Previous post was at 10:00 AM ----------
Has anyone tried this method?
http://forum.xda-developers.com/showthread.php?t=1749921
Click to expand...
Click to collapse
That's the one I always use, but now we got the inside track on the sql editor... Stock app is definitely better than the exchange bypass, but ill take what I can get..
canecbr600 said:
Go to data/system and there is a file locksettings.db. Open it in SQL editor. Next tap on locksettings, and u should have a item listed as lockscreen.password_type . Change the value for this to 0. That will change lockscreen to swipe to unlock.....
Click to expand...
Click to collapse
This caused a bootloop at the Verizon logo. How do I fix this??
JPD19 said:
This caused a bootloop at the Verizon logo. How do I fix this??
Click to expand...
Click to collapse
I realized I edited the database incorrectly...I had to reset my phone by going into recovery mode, but this method does work if you edit the database just as described.
Would anyone know what the "value" should be if you want knock code instead of swipe to access phone?
GroovyGeek said:
It should not be necessary to delete the LGE apps, the two can work side by side. And if you are set on disabling the LGE app it is probably better to freeze it with TBU than delete, in case you change your mind later.
Those contemplating the use of this mod should keep in mind that the LGE stock email app is FAR, FAR, FAR more intelligent than the stock KK email app when it comes to autoconfiguring your Exchange connection. In fact I recommend running the LGE stock app first, then going into settings and taking a screenshot to document how the account was configured. You will almost certainly have to enter this information manually into the KK app because it will be unable to figure it out on its own.
Click to expand...
Click to collapse
Can you please explain how to do this?
kobbz said:
Can you please explain how to do this?
Click to expand...
Click to collapse
Run TBU, touck checkmark icon in upper right of screen, wait for "Calculating scenarios" message to complete, scroll down to Freeze/Defrost, touch appropriate option (could the color scheme of TBU be any more awful than it is? sheesh, the developer must be color blind ) then select apps to freeze/defrost.
GroovyGeek said:
Run TBU, touck checkmark icon in upper right of screen, wait for "Calculating scenarios" message to complete, scroll down to Freeze/Defrost, touch appropriate option (could the color scheme of TBU be any more awful than it is? sheesh, the developer must be color blind ) then select apps to freeze/defrost.
Click to expand...
Click to collapse
LOL .. what's TBU? (I must be clearly missing something. Sorry if this has been explained before)
kobbz said:
LOL .. what's TBU? (I must be clearly missing something. Sorry if this has been explained before)
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=com.keramidas.TitaniumBackup
https://play.google.com/store/apps/details?id=com.keramidas.TitaniumBackupPro
TBU - Titanium Backup, must have if you're rooted.
ddavtian said:
TBU - Titanium Backup, must have if you're rooted.
Click to expand...
Click to collapse
I see... I'm familiar with the app. I guess I'd never heard of it referred to as TBU before. Thanks guys.
---------- Post added at 05:13 PM ---------- Previous post was at 05:10 PM ----------
kobbz said:
I see... I'm familiar with the app. I guess I'd never heard of it referred to as TBU before. Thanks guys.
Click to expand...
Click to collapse
One odd thing is happening. I have root explorer installed and from that application, I browse to the location where the locksettings.db file lives. However, when I click on the file and the "Complete Action Using" pop up window comes up, I don't see SQL Editor as one of the choices there. Alternatively, I thought I'd just open SQL Editor directly and try to edit the file in there; this does not work since SQL Editor has not been granted root access.
Anyone know if there's a way to grant a specific application root access?
kobbz said:
I see... I'm familiar with the app. I guess I'd never heard of it referred to as TBU before. Thanks guys.
---------- Post added at 05:13 PM ---------- Previous post was at 05:10 PM ----------
One odd thing is happening. I have root explorer installed and from that application, I browse to the location where the locksettings.db file lives. However, when I click on the file and the "Complete Action Using" pop up window comes up, I don't see SQL Editor as one of the choices there. Alternatively, I thought I'd just open SQL Editor directly and try to edit the file in there; this does not work since SQL Editor has not been granted root access.
Anyone know if there's a way to grant a specific application root access?
Click to expand...
Click to collapse
You should be able to add it through super user or reopen a few times to get the root prompt.