Hi!
I am having a difficult time in disabling the proximity sensor in Galaxy S II. A few days ago I discovered that it was damaged, but it is probably gonna take a while till I am able to send it to Samsung for repair.
so When I receive a call or someone calls me the screen never comes back and I have to reset it or remove the battery which is pretty annoying.
So I have tried several methods using the Internet.
First there is this option in the caller application which basically disables the proximity sensor when calling. But this is not available in Jelly Bean 4.1. It has been removed...I am not sure why....
Second I tried adding manually in the biuld.prop file the entry
Code:
gsm.proximity.enable=false
After rebooting the phone that did not work either...
Finally I downloaded hardware disabled from the market, ticked the proximity sensor driver, rebooted and that worked fine. However when I do that the CPU remains in very high levels causing the phone to warm up a lot and the battery drain is amazing! So this is not really an option and I disabled that...
So I am wondering if any of u Jelly Bean users have any other ideas to offer cause I am kinda stuck here...
Thank you!
Paladin13 said:
Hi!
I am having a difficult time in disabling the proximity sensor in Galaxy S II. A few days ago I discovered that it was damaged, but it is probably gonna take a while till I am able to send it to Samsung for repair.
so When I receive a call or someone calls me the screen never comes back and I have to reset it or remove the battery which is pretty annoying.
So I have tried several methods using the Internet.
First there is this option in the caller application which basically disables the proximity sensor when calling. But this is not available in Jelly Bean 4.1. It has been removed...I am not sure why....
Second I tried adding manually in the biuld.prop file the entry
Code:
gsm.proximity.enable=false
After rebooting the phone that did not work either...
Finally I downloaded hardware disabled from the market, ticked the proximity sensor driver, rebooted and that worked fine. However when I do that the CPU remains in very high levels causing the phone to warm up a lot and the battery drain is amazing! So this is not really an option and I disabled that...
So I am wondering if any of u Jelly Bean users have any other ideas to offer cause I am kinda stuck here...
Click to expand...
Click to collapse
Wow, thank you, I didn't know this option exists. I am running NeatRom v4 Lite and that option you mentioned is still there. (it is also JellyBean)
Lol got same problem as OP and tried similar things including chmod 0000 to cm3663 folder but no success.
Any ideas?
Hi I upgraded to a new CM10 nightly several weeks ago and then did not use my prime for several weeks I turned it on today and the above message keeps popping up I searched and it seemed to be a cm10 issue so I changed to a different rom (baked black bean 6) but no change and to top it off I can't even access the play store to try a different keyboard app so I really need help to solve the stupid message problem.
Keyboard has stopped working
fastfibre said:
Hi I upgraded to a new CM10 nightly several weeks ago and then did not use my prime for several weeks I turned it on today and the above message keeps popping up I searched and it seemed to be a cm10 issue so I changed to a different rom (baked black bean 6) but no change and to top it off I can't even access the play store to try a different keyboard app so I really need help to solve the stupid message problem.
Click to expand...
Click to collapse
I am having the same problem. I downloaded the latest PACMAN rom and noticed the battery would not charge past 40%. I figured it was a rom bug, so I reset to factory, installed the stable version of cm 10 and gapps, and now I cant use anything because the keyboard has stopped working message keeps popping up and wont let me text or download anything from the play store. Can anyone help us with this??
I just got a refurbished phone from Verizon. I never messed around with it or anything and I immediately rooted it and installed the Jelly Bean leak.
I had issues with contact photos showing up in the Favorite Contacts widget and I had problems with my phone not switching between landscape and portrait mode.
So I did a factory reset and reloaded everything, now the issue is happening again.
Could it possibly be a software problem? I've downloaded a few different apps to test it and I'm almost certain it isnt a hardware problem. Any help would be appreciated!
Thanks
bbro said:
I just got a refurbished phone from Verizon. I never messed around with it or anything and I immediately rooted it and installed the Jelly Bean leak.
I had issues with contact photos showing up in the Favorite Contacts widget and I had problems with my phone not switching between landscape and portrait mode.
So I did a factory reset and reloaded everything, now the issue is happening again.
Could it possibly be a software problem? I've downloaded a few different apps to test it and I'm almost certain it isnt a hardware problem. Any help would be appreciated!
Thanks
Click to expand...
Click to collapse
settings/Display/auto-rotate screen see if it is enabled. also you can install a custom rom to see if it's persisting
if those doesn't work, go to warranty
Hi Folks,
This was the closet forum I could find for my phone. I actually have the GS2 HD LTE (i757) from Bell Mobility in Canada. Monday I finally received my Jelly Bean Update (4.1.2) I wish I could say I an excited however it has caused me so much stress, Ever since I installed it my phone has been terrible laggy. ICS gave me no troubles but after seeing the huge performance boost in my Wife's i9100m last month when it was available to hers I did not hesitate to update mine. Below I will list my symptoms, as well as the steps I have done to resolve this. I have search everywhere for an answer and have come up with nothing. Also to note, my Friend in the office has a Galaxy Note with a different provider (Telus) who received the update the same day, we can put our phones side by side and we both experience the exact same issue.
Setup:
i757 (S2 HD LTE)
Not Rooted
Symptoms:
Swiping to unlock is choppy
Opening Messaging to text takes three part (Loads the body, loads previous message and then keyboard loads in the middle of the screen and works its way down.
30-45 second pause to open the dialer
when clicking the power button to get to the lock screen it shows the desktop for a second, then god to my lock screen wallpaper then my lock screen icons appear. After this I can swipe.
loading apps
at startup RAM is 558MB/737MB. I hit clear memory right away it goes to 394MB/737MB. But open any app I am back up to to 550MB-600MB
Things I have tried:
Install install was Down with Kies as a regular update with all my Apps still installed.
I Wiped Cache and down a Factory Reset
Reloaded the Stock ROM with Odin3 v1.85
In developer options I disabled animation for Window, Transition and Animator
I disabled ripple effect for lock screen
I disabled Google Now
Tried to Wipe Cache then resume use without reloading OS
Tried Disabling GPS, Bluetooth, WiFi and sync.
Installed Android assistant to clean up startup
Did another Factory Reset/Cache Wipe then install OS from MSD
None of these options have made a difference. The phone worked flawlessly on ICS, I don't know what else I can do. Has anyone experienced this issue? and if so have they fixed it?
At this point I will try anything before I take out the hammer and fix it for good. Any assistance would be greatly appreciated.
- Boots!
Also my Current status is Factory Reset/Wipe Cache OS Installed from SD Card nothing install.
* * * COULD MOD PLEASE MOVE TO APPROPRIATE FORUM I MUST HAVE OVER LOOKED THE i757 FORUM * * *
Moved
Hi,
I have the exact same symptoms on my SGH-i757m.
The phone is brand new! I got it for the job, in replacement of my s2-i9100. As soon as I got it, I had the official ICS, then JB done to it...and it is an absolute disaster up to now.
Sometimes I can't even take an incoming call because the ''incoming call screen'' (with the green and red phones logo) freezes, giving me the ''com.android.phone has stopped'' error.
I'll be looking out for solutions, but I might just take it back to ICS soon...
windex23 said:
Hi,
I have the exact same symptoms on my SGH-i757m.
The phone is brand new! I got it for the job, in replacement of my s2-i9100. As soon as I got it, I had the official ICS, then JB done to it...and it is an absolute disaster up to now.
Sometimes I can't even take an incoming call because the ''incoming call screen'' (with the green and red phones logo) freezes, giving me the ''com.android.phone has stopped'' error.
I'll be looking out for solutions, but I might just take it back to ICS soon...
Click to expand...
Click to collapse
windex.
Please keep this thread in mind, Anything I can find I will post it here. If you could do that same that would be great. My S2-i9100 was amazing with the Official JB release also. I am surprised more people are not complain online about this as I know my friend with the Note on Telus is having same issue (Update was released the same time for him) I also called Bell and their Tech support said they were receiving alot of the same issues since the May JB update..
Damn Lag has got my phone!
AH! damn update lag has got my phone and my girlfriends too! We both have the samsung galaxy HD LTE I757M phone and have exactly the issues all of you guys have. From extremely slow response to flickering and its just a pain in the ass. My girlfriend tried a factory reset which worked for about a week with no lag or anything but then just started the same lag issues we all have. A lot of people apparently are reporting that a factory reset does the charm but its only a matter of time before the issues creep back to your phone. Right now I am going to try a custom rom for our phones and hope that it works. If it does Ill post the results for you guys to hopefully benefit from.
sean
I was having the same problem with my I757M. This phone is fine on ICS 4.0.4.
I don't know the real solution but, the phone is fine (for now)
Used Forever Gone app
Did a factory reset before upgrading to JB 4.2.1 (Maybe?)
Removed Ripple effect on Screen lock
Set the transitions to 0.5x
Power savings enabled (Screen only)
Disabled these system apps
100% HD Games
AllShare Play
Asphalt 6
Google Play Magazine
Google Play Movies
Google Play Music
Google+
GPS navigator
Let's Golf 3
Self-Service
Update software
Google Play Books (or Play Books)
Social Network
Ringtones and Applications
Sympatico.ca
Talk
Talkback
TV mobile (bell)
Y! Finance
Yahoo! Finance Daemon
Yahoo! News
I installed JB 4.1.2 today, saw some improvements, hope it is fixed for good !
The ram usage on boot (369MB / 737MB)
Sorry to post again !!
Okay, it started to lag as described by others. So I went back to 4.0.4... The battery life is better on Jelly Bean because it can reduce the screen's power (not just brightness)
I did this today, my last attempt with JB...
In Dial :: *2767*3855# (it formats everything, even sdcard, so backup your things before doing this !!!)
I configured ICS from the welcome screen (no gmail configuration, etc.)
Installed JB 4.1.2 from Kies.
I disabled the programs mentionned at my previous post...
There was still a lag when unlocking the phone. Tried Holo Locker and didn't do anything... still lags.
Then, I searched on the net :
http://forum.xda-developers.com/showthread.php?t=2224906
It seems TouchWiz has problems rendering Widgets on homescreen, so, I installed Nova Launcher to replace it.
For now, when receiving a SMS, after unlocking, the wallpaper can become black, but there is no lag like before. :good:
Same situation
My wife‘s i757m has the same situation. I wiped to factory and uninstall like "let's golf", google play music. Then it turned much better for about 1week and then be back lag lag lag again.
I have no idea why it is so ridiculous , cause my friend's I727(GS2HD rogers) is very good after he updated his in March.
Please help me SGH-1757M
I have the same Issues.
After upgrading the Phone to 4.1.2 bellow issues identified.
1) When Incoming call comes the Phone Frezes and Green and Red button on the screen does not work
2) Some times it works but when I get any call the Phone rings with black screen and after some time it comes with number and then caller id and then answer button
3) Every time when I went to Messaging it loads the messages with number and next updates the Caller ID and then body of the messages and text editor
4) Morning when alarm rings phone Freezes and does not allow me to stop the alaram and force restart the Phone.
I am having so amny problems like this .
Please suggest what we can do here to resolve these issues.
Hey guys!
I've already posted my problem in the Nexus 4 Q/A-Forum.. till now without help. Well i thought that maybe here is a good place to get help, too!
So whats my problem.. Yesterday i flashed a new update of Xylon-Rom (clean flash) on my Nexus 4. Installed and restored all Apps. Usually I use Swiftkey 4 as keyboard, so I set up everything like all the times before. The last times everything works fine, but this time not. I set up SK as my standard keyboard and began to write. After a while I wanted to write again, but suddenly there was the AOSP keyboard. Changed back to SK. But after some moments it happend again. So everytime when there is a text input AOSP appears.. I change back to SK then, but after turning screen on some minutes later AOSP again.
As it would be not enough, the same thing is happening since yesterday on my gf phone (HTC One S, also rooted with Carbon Rom). Like on my phone, it never happenend before.
What I've done till now? Erased App-Data of both keyboards, disabled AOSP keyboard. Everything without success.
Dont know why it happens now... I often flash other Roms, Updates etc and I use Swiftkey for a long time. Restoring with Titanium works everytime. And this time i haven't done any other thing on Restoring.
I hope u understand my problem (my english isn't the best ) and anyone could help me!?
Thanks so far.
Cls
Tried to freeze the AOSP in Titanium -> no effect
Set Swiftkey as System-App -> no effect
:X
I was encountering this with swipe keyboard previously, and my solution was to use swiftkey.
Sent from my Nexus 7 using Tapatalk 4 Beta
same thing
im suffering from this problem too.. no solution yet :3