Wrong pin bug after restart and login possible without Pin:
Sporadically (once a week) after a reboot the following situation occurs:
1. The Pin screen pop up > You can type the correct pin but it is always recognized as wrong
2. After the second attempt > You reboot the device again
3. The Galaxy W starts with Flight Modus > You can disable Flight Modus > Now your SIM works without Pin
(Tested and occured on the following ROMS: CM10 Alpha 6, CM9 RC2, CM9 RC6)
Issue was seen on two different Galaxy W devices, therefor I assume that this should be a know bug.
Krenk said:
Wrong pin bug after restart and login possible without Pin:
Sporadically (once a week) after a reboot the following situation occurs:
1. The Pin screen pop up > You can type the correct pin but it is always recognized as wrong
2. After the second attempt > You reboot the device again
3. The Galaxy W starts with Flight Modus > You can disable Flight Modus > Now your SIM works without Pin
(Tested and occured on the following ROMS: CM10 Alpha 6, CM9 RC2, CM9 RC6)
Issue was seen on two different Galaxy W devices, therefor I assume that this should be a know bug.
Click to expand...
Click to collapse
didnt happen to mine till now..
Is there a setting to keep the backlight ON on the hardware buttons when the screen is on? (The same as the default behavior in GB.)
my question exactly
rh09 said:
Is there a setting to keep the backlight ON on the hardware buttons when the screen is on? (The same as the default behavior in GB.)
Click to expand...
Click to collapse
same issue over here -- I flashed the buttons backlight fix for a previoys CM and don't see it working in 10.1
any ideas?
https://www.dropbox.com/s/hjv64rsi06b1lyp/Lights_Library_Config.zipthis right here is what is needed. after flashing through recovery go into terminal emulator type this out. each line means hit enter after command
su
liblights.sh
0 for yes or 1 for no(hit 0)
reboot
profit
I've noticed that my device has suddenly turned off on several occasions; I only notice because it does not respond to the power button and to use it I must take out and reinsert the battery.
I am running the latest installer build. Is this an issue with CM, the phone or something else? I need it fixed quickly because I am missing important text messages and phone calls. Should I flash M9 over the installer build, or is it something serious enough to merit a deeper change?
RaymieHumbert said:
I've noticed that my device has suddenly turned off on several occasions; I only notice because it does not respond to the power button and to use it I must take out and reinsert the battery.
I am running the latest installer build. Is this an issue with CM, the phone or something else? I need it fixed quickly because I am missing important text messages and phone calls. Should I flash M9 over the installer build, or is it something serious enough to merit a deeper change?
Click to expand...
Click to collapse
It sounds like you're having issues with your phone not waking up. A couple things you can try immediately(these are terminal commands to enter in terminal emulator or adb):
### lower wakeup thresholds
Code:
su
sysctl -w kernel.random.read_wakeup_threshold = 64
sysctl -w kernel.random.write_wakeup_threshold = 128
### increase max frequency
Code:
su
echo 1200000 > /sys/devices/system/cpu/cpu0/cpufreq/screen_off_max_freq
When your phone screen doesn't turn on when you press the power button, try plugging it into the charger to see if turns on then.
Also this can sometimes be a kernel related issue. Try flashing some afterstock kernels like Fancy or Dirty V.
I have written this shell script for those of you who are having problems with your GS4's screen not responding as expected during calls, such as the screen not turning off when you put your device to your ear, and not turning on when you take your device away from your ear etc.
Before running this script, the first thing to try would be to clean the proximity sensor itself. Dismantling the device and cleaning it is by far the best method. See this video.
However, an easier method is to blow compressed air down into the sensor (which is located under the silver earpiece at the top of the phone) and also clean it with a vacuum cleaner.
If you are still experiencing erratic behaviour even after doing this, then this adb shell utility may be of some help to you.
NOTE: You need a rooted device for this utility to work!!
Downoad Here
Download Here
Installation Instructions
1. Download ProxCal.sh from the above link
2. If downloaded via PC, copy ProxCal.sh onto your device.
Job done!
Script Execution
1. Open up an ADB Shell on your PC, or any sort of Terminal Emulator console session on your handset
2. If you are not at the root (#) prompt, enter su
3. Change directory to where you downloaded/copied ProxCal.sh eg. cd /sdcard/scripts
4. sh ProxCal.sh
You will then be presented with a straight forward menu of options:
ProxCal v1.00
-------------
Re-calibrate your handset's proximity sensor
Use this utility if you are having problems with your handset's
screen reacting normally during calls, even after cleaning
the sensor with compressed air etc.
Handset: GS4 (GT-I9505G)
Sensor: MAX88920
1. Show current values
2. Test run
3. Recalibrate proximity sensor
X. Exit
Enter choice:
1. Show current values
Shows the current values of proximity sensor related files on your device. The state value is the important one here. With nothing in front of the sensor, this should be as close to 0 as possible. A high value signifies a problem with the sensor, and that it requires cleaning and/or re-calibrating. Try performing this function as many times as you wish, placing your hand at varying distances from the sensor each time. See how the sensor reacts by examining the state value.
Current Proximity Sensor Values:
prox_cal : 0,60,45
state : 4
efs_prox_cal: *
2. Test run
Performs a test run. No files are altered during this process. The function only displays what it would have done on an actual recalibration run.
Re-calibrating GS4 proximity sensor.
(Test Mode)
Please wait.......
Recalculating efs offset...
Current offset: 0
Current state: 3
New offset: 3
Test Run Log
------------
echo 0 > /sys/devices/virtual/sensors/proximity_sensor/prox_cal
echo 1 > /sys/devices/virtual/sensors/proximity_sensor/prox_cal
mkdir -p /sdcard/tmp/ProxCal/BKP
cp /efs/prox_cal /sdcard/tmp/ProxCal/BKP/efs_prox_cal.2014-09-04--07-55
echo $\x3 > /efs/prox_cal
chown system:system /efs/prox_cal
chmod 644 /efs/prox_cal
Re-calibration test complete.
3. Recalibrate proximity sensor
This option actually recalibrates the sensor by updating the necessary files.
The proximity sensor will now be recalibrated.
Please ensure there is nothing in front of the sensor.
Proceed? (Y/N) y
y
Re-calibrating GS4 proximity sensor.
Please wait.......
Recalculating efs offset...
Current offset: 0
Current state: 3
/efs/prox_cal backup created:
/sdcard/tmp/ProxCal/BKP/efs_prox_cal.2014-09-04--08-01
New offset: 3
Re-calibration complete.
Backups
A backup of /efs/prox_cal is performed during an actual run (menu option 3)
Backups of this file are made into /sdcard/tmp/ProxCal/BKP
A backup is made on a date/time basis. Eg. efs_prox_cal.2014-09-04--07-55
Should you need to restore a backed up file, then type the following at and adb shell # prompt:
cd /sdcard/tmp/ProxCal/BKP
cp efs_prox_cal.[date-stamp] /efs/prox_cal
X. Exit
Exits the shell script and returns you back to a # prompt.
If the sensor was calibrated you will get the following message:
Your proximity sensor has been re-calibrated.
Please reboot your GS4 then re-run
this utility to check the new values.
Pay particular attention to the 'state' value.
When nothing is close to the sensor, this should
be a very low value (the closer to 0 the better)
** Please reboot your GS4 ***
proxcal.sh completed successfully.
Automatic Script Execution
The script can be called to automatically calibrate the sensor without any further user interaction.
This is done by including the auto parameter.
ie:
sh ProxCal.sh auto
This is useful if you want to automatically recalibrate the sensor on each boot using init.d scripts.
Credits
This script merely automates the tasks that I found on the internet which recalibrates the sensor. Examples:
XDA thread: Proximity Sensor Bug Fixed, .Screen turns off during call.ISSUE FIXED by @Ammar Saood
Android Legend post
CM thread on Reddit
CM Forum thread
Recalibration app on the Play Store, suggested in above thread
Full credit goes to these guys.
*** Reserved 1 ***
*** Reserved 2 ***
Excellent job, made it so easy its unbelievable!!
Many thanks
Works great
Send from my phone
Why do people love crappy file hosts? There are two download buttons, one is a phishing attack, the other is malicious download. Why not use pastebin?
sbcontt said:
Why do people love crappy file hosts? There are two download buttons, one is a phishing attack, the other is malicious download. Why not use pastebin?
Click to expand...
Click to collapse
good questions. can be very annoying while the problem for me only exists on mobile devices. i recommend to download stuff on your computer and use USB OTG to tranfer. of course there is ADB and other means of transfer but noting is faster and more reliable for me than an USB stick with sufficient memory and dual ports one micro USB and USB A on the opposite end. those things have gotten very cheap lately.
Worked fine for Resurrection Remix v5.8.0 , thank you.
sbcontt said:
Why do people love crappy file hosts? There are two download buttons, one is a phishing attack, the other is malicious download. Why not use pastebin?
Click to expand...
Click to collapse
+1
I want Fix a problem Sensors calls for 5.1.1 roms
proximity sensor calibration
Hi,
i need to recalibrate the proximity sensor so that detect an objects at a distance of 20 cm.
anyone knows if it is possible?
tanks
marco
indian28 said:
Hi,
i need to recalibrate the proximity sensor so that detect an objects at a distance of 20 cm.
anyone knows if it is possible?
tanks
marco
Click to expand...
Click to collapse
Nope. This sensor is just used for calls and sleep/wake features. If it detects objects above its intended to be (exactly 8cm) it may cause unexpected problems.
BTW a sensor can detect above 20cm?
In a Arduino module can only detect up to 15 cm and it's very bulky already, so a small sensor can detect 20 cm, impossible.
BTW new here
@hawkerpaul i get 500 Internal Server Error on devhost
So I recently switched carriers and couldn't get a signal out of the box with my OP5T. After digging around on some blogs I found users who were able to get it working by enabling VoLTE by changing some settings and flashing two files using EfsTools.
The process was basically to install OnePlugLogKit. Dialing #*800# to access the settings, enabling VoLTE there.
And then Dialing #*801# to get into that menu, enabling full port switch and connecting the device to a PC.
Using EfsTools, I flashed two files mcfg_autoselect_by_uim and mcfg_sw.mbn using these commands:
EfsTools.exe writeFile -i mcfg_autoselect_by_uim -o /nv/item_files/mcfg/mcfg_autoselect_by_uim
and
EfsTools.exe uploadDirectory -i mcfg_sw.mbn -o / -v
Restart the phone and BOOM, the VoLTE icon appears and it connects to the network.
The first time I did this, it worked perfectly and I assumed that the fix was permanent. It was also supposed to transcend any software updates/wipes because I'm flashing something to the modem if I understood correctly.. ?
But then I visited another country and used a different SIM card, when I returned back my signal was gone again. I thought, okay maybe the new SIM card disabled it something, so I reflashed and it worked again.
This time however, it reverted back much more quickly and without any major changes that I could tell. I reflashed again just to see what would happen and the signal came back. Unfortunately the flash does not last long at all anymore. The most recent flash had it working for about 1 day and has now reverted back.
Is there any way I can check some log files to see what is causing it to revert back? I don't know what to do because yesterday I went out for a bit with the signal connected and working, and then just completely random it reverted back and I was left with no signal.
Appreciate any help.