Related
There is a command radiooptions we can run to enable QXDM, which should be the radio diagnose port. But don't know what's enabled, and where to read the diagnose messages. Please help...
It's interesting when run radiooptions with parameter 3, from /dev/smd0, we can read this line: [WCDMA] SDLOG Fail (no.-2)
And here is the radiooptions command help:
Usage: radiooptions [option] [extra_socket_args]
0 - RADIO_RESET,
1 - RADIO_OFF,
2 - UNSOL_NETWORK_STATE_CHANGE,
3 - QXDM_ENABLE,
4 - QXDM_DISABLE,
5 - RADIO_ON,
6 apn- SETUP_PDP apn,
7 - DEACTIVE_PDP,
8 number - DIAL_CALL number,
9 - ANSWER_CALL,
10 - END_CALL
blues said:
There is a command radiooptions we can run to enable QXDM, which should be the radio diagnose port. But don't know what's enabled, and where to read the diagnose messages. Please help...
It's interesting when run radiooptions with parameter 3, from /dev/smd0, we can read this line: [WCDMA] SDLOG Fail (no.-2)
And here is the radiooptions command help:
Usage: radiooptions [option] [extra_socket_args]
0 - RADIO_RESET,
1 - RADIO_OFF,
2 - UNSOL_NETWORK_STATE_CHANGE,
3 - QXDM_ENABLE,
4 - QXDM_DISABLE,
5 - RADIO_ON,
6 apn- SETUP_PDP apn,
7 - DEACTIVE_PDP,
8 number - DIAL_CALL number,
9 - ANSWER_CALL,
10 - END_CALL
Click to expand...
Click to collapse
Do you have an SD card in the phone?
Yes, I do have the 1G SD card come with the phone
Does it work for you?
Update:
Update: I noticed the sdcard is readonly when it is connected to my XP PC.
I have disconnected the usb storage. Now I can see sdcard is writable.
But still the QXDM is not working for me.
In Normal HTC CDMA Device Such Programmed are called automatically by just Pressing the Codes in Dialer of Phone
in CDMA
##3424# goes to PST ( Diagnostic Port ) but this command dont work in G1
When i dial this it says USSD Code Running but Flashes error " Connection problem or invalid MMI Code"
when i run
##778# ( ##pst# ) and dial it show " UNKNOWN APPLICATION "
Some of the G1 Source Pointing ## as Starting Code for Diagnostic Method
Code:
/* Example of how to route a call to another Application. */
58 if (POUND_POUND_SEARCH && number.startsWith("##")) {
59 Intent newIntent = new Intent(Intent.ACTION_SEARCH);
60 newIntent.putExtra(SearchManager.QUERY, number.substring(2));
61 newIntent.addFlags(Intent.FLAG_ACTIVITY_NEW_TASK);
62 context.startActivity(newIntent);
63 setResultData(null);
64 }
The Radio Option is defined in Following File of Android
http://git.source.android.com/?p=pl...2;hb=dbbb392e15b5ace6f19e76c49c80ea14292e8a4d
Which is
[platform/hardware/ril.git]/rild/radiooptions.c
are there any news on the diagnose port?
I'd love to be able to access some of the information using an app on the phone
I have looked at this app before. You can initiate calls, terminate calls and turn the radio on/off but the QXDM functions don't do anything. I have noticed that the Dalvik Debug Manager has an option to "dump radio state" when a device is connected, but it gives an error about a logfile that is missing. Perhaps this logfile is where QXDM messages are sent to.
You can type "logcat -b radio" to see the error msg too.
The app calls ril lib to send the AT commonds to the SMD0 port (shared memory channel between the application processor and radio processor). And the radio processor receives this AT commond, and if the software (AMSS?) runs on the radio chip (ARM9?) is configurated correctly, then it should produce the log.
Any one has the experince to reverse the firmware on the radio chip? I guess it is a simple switch we can turn it on if we knows the AMSS thing.
Any updates??
Check this out!
You may want to take a look at my post. This will virtually work with any device who's kernel source is released . http://forum.xda-developers.com/showthread.php?t=948360
Sorry to revive such an old post, but do your link doesn't work anymore. I need this info, thanks!
hey guys n gals, iv been reg'd a few days now n thought id make my first post a worth while one
Alot of the credit though must go to Christian Buchner for his initial guide of getting a ZTE usb modem working with vodafone over in Germany.
NOTE: BASED ON ZT-180 SLATE 0929 FIRMWARE (rooted)
To get your ZTE modem working you must be able to use adb confidently!
ok first things first, as Christian pointed out in his guide, if the Flash drive side of the modem is enabled, your slate wont recognise it, so our first job is to disable it.
*Nix Users - Im assuming you have a good knowledge of AT commands already and how to use them so just run
Code:
AT+ZCDRUN=8
Windows Users See Here hxxp://3g-modem.wetpaint.com/page/executing+AT-commands+under+Windows
and execute the above AT command
Right, so now our slate recognises our Modem, now lets get this rocking and get connected.
You will need to Pull the following files from your slate
note: some files may not exist so you will have to create them
/system/etc/ppp/peers/cdma
/system/etc/ppp/peers/cdma_h
/system/etc/ppp/peers/cdma~
/system/etc/ppp/options-3g
/system/etc/ppp/chat-3g-connect
/system/etc/ppp/chat-3g-disconnect
/system/etc/ppp/pap-secrets
/system/etc/ppp/chap-secrets
Now heres what goes in them...
/system/etc/ppp/peers/cdma
Code:
file /system/etc/ppp/options-3g
connect '/system/xbin/chat -v -f /system/etc/ppp/chat-3g-connect'
disconnect '/system/xbin/chat -v -f /system/etc/ppp/chat-3g-disconnect'
user three
/system/etc/ppp/peers/cdma_h
Code:
file /system/etc/ppp/options-3g
connect '/system/xbin/chat -v -f /system/etc/ppp/chat-3g-connect'
disconnect '/system/xbin/chat -v -f /system/etc/ppp/chat-3g-disconnect'
user three
/system/etc/ppp/peers/cdma~
Code:
file /system/etc/ppp/options-3g
connect '/system/xbin/chat -v -f /system/etc/ppp/chat-3g-connect'
disconnect '/system/xbin/chat -v -f /system/etc/ppp/chat-3g-disconnect'
user three
/system/etc/ppp/options-3g
Code:
/dev/ttyUSB3
921600
nolock
crtscts
modem
passive
novj
defaultroute
noipdefault
usepeerdns
noauth
hide-password
debug
nodetach
ipcp-accept-local
ipcp-accept-remote
/system/etc/ppp/chat-3g-connect
Code:
ABORT "BUSY"
ABORT "NO CARRIER"
ABORT "VOICE"
ABORT "NO DIALTONE"
ABORT "NO DIAL TONE"
ABORT "NO ANSWER"
ABORT "DELAYED"
ABORT "ERROR"
REPORT CONNECT
TIMEOUT 10
"" AT
OK AT+CGDCONT=1,"IP","3internet"
OK ATDT*99#
TIMEOUT 20
CONNECT ""
/system/etc/ppp/chat-3g-disconnect
Code:
ABORT "BUSY"
ABORT "ERROR"
ABORT "NO DIALTONE"
SAY "\nSending break to the modem\n"
"" "\K"
"" "\K"
"" "\K"
"" "\d\d+++\d\dATH"
SAY "\nPDP context detached\n"
/system/etc/ppp/pap-secrets
Code:
# client server secret IP addresses
three * three
/system/etc/ppp/chap-secrets
Code:
# client server secret IP addresses
three * three
Now Push all the files back into your slate and reboot.
Once you plug your modem in you will notice it show signal strength, however sometimes it requires you to set an APN up manually, but try a hard reset first if that fails, this is how to do it...
Settings > Wireless & Networks > Mobile Networks > Access Point Names
Name : Anything
APN : 3internet
Username : three
Password : three
Authentication Type : PAP or CHAP
and thats really all there is to it!
nitr0genics said:
hey guys n gals, iv been reg'd a few days now n thought id make my first post a worth while one
Hello !!! I received 180 ZT 1030 and have upgraded the firmware. Now I want to use ZTE 3G modem mf100 follow your instructions but still not on the internet. I live in Russia and the Beeline network using WCDMA. Looking forward to your help. Excuse my English . Thanks !!!
Click to expand...
Click to collapse
Hi nitr0genics,
I tried this with Frojo and it works perfect . Thank you for this also to all other experts.
(google translate, hope you understand )
Hi people
I read the surfstick from german provider 1und1 (ZTE MF110) to run in the ZT-180. Do any of you can experience the driver has to extract? i will use the stick in my gome flytouch2
thx
working on android
hello, does anyone know if this means that we can use the MF110 on any android device with froyo??
thanks
”You will need to Pull the following files from your slate
note: some files may not exist so you will have to create them
/system/etc/ppp/peers/cdma
/system/etc/ppp/peers/cdma_h
/system/etc/ppp/peers/cdma~
/system/etc/ppp/options-3g
/system/etc/ppp/chat-3g-connect
/system/etc/ppp/chat-3g-disconnect
/system/etc/ppp/pap-secrets
/system/etc/ppp/chap-secrets”
How can i make these files, because if iuse notepad those are no more executabiles ?
Hey there.
I'd love to enable the diagnostic mode in my Nexus 5 so that I can trace the radio interface with software such as QXDM, X-CAL, etc... but I've had no luck so far.
basically I'm trying to change the variable sys.usb.config to [diag,adb] as shown in this post for the Nexus 4. I'm doing:
> su -c 'setprop sys.usb.config diag,adb'
(if you run getprop you see that the correct order is sys.usb, not usb.sys as shown in that post)
However, when I enter this command the phone automatically reboots... and the value is reverted back to [mtp,adb].
Any ideas? Do you know of any 'friendlier' way to enable diag mode on the Nexus 5? For example, in the Galaxy S4 you can just dial *#0808# to get into the USB config menu, which easily allows you choose the DM mode... but I can't find a similar menu on the Nexus 5.
Seems a bit absurd to me that a developer-oriented phone is the hardest one to put in diag mode... :/
Note: I'm rooted.
my phone is the same situation
prometheusZ said:
my phone is the same situation
Click to expand...
Click to collapse
I'm seeing the same thing.
Code:
[email protected]:/ $ su -c 'setprop sys.usb.config diag,adb'
[email protected]:/ $ getprop sys.usb.config
mtp,adb
Was this a change in AOSP? Might have to dig through the sources to see what changed.
---------- Post added at 04:56 PM ---------- Previous post was at 04:52 PM ----------
For what it's worth I can get that to change in recovery, but it doesn't enable anything else.
Code:
setprop sys.usb.config diag,adb
~ # getprop sys.usb.config
diag,adb
satadru said:
I'm seeing the same thing.
Code:
[email protected]:/ $ su -c 'setprop sys.usb.config diag,adb'
[email protected]:/ $ getprop sys.usb.config
mtp,adb
Was this a change in AOSP? Might have to dig through the sources to see what changed.
---------- Post added at 04:56 PM ---------- Previous post was at 04:52 PM ----------
For what it's worth I can get that to change in recovery, but it doesn't enable anything else.
Code:
setprop sys.usb.config diag,adb
~ # getprop sys.usb.config
diag,adb
Click to expand...
Click to collapse
i have done this with cm11, but the result was the same
prometheusZ said:
i have done this with cm11, but the result was the same
Click to expand...
Click to collapse
I'm definitely seeing that this works on d2 devices with cm11. I wonder if it works on the LG G2, since that is similar inside.
The problem is that this needs to be run as root, with SELinux disabled.
You can set SELinux to permissive with this tool: https://play.google.com/store/apps/details?id=com.mrbimc.selinux
As per here:http://forum.xda-developers.com/showpost.php?p=39686712&postcount=3 the usb init script for hammerhead should tell us the steps for diag mode.
That hammerhead init script is here: https://android.googlesource.com/device/lge/hammerhead/+/kitkat-release/init.hammerhead.usb.rc
Here's the essence, if you want to run it from your own script:
Code:
stop adbd
echo 0 > /sys/class/android_usb/android0/enable
echo 1004 > /sys/class/android_usb/android0/idVendor
echo 61F1 > /sys/class/android_usb/android0/idProduct
echo 239 > /sys/class/android_usb/android0/bDeviceClass
echo 2 > /sys/class/android_usb/android0/bDeviceSubClass
echo 1 > /sys/class/android_usb/android0/bDeviceProtocol
echo smd > /sys/class/android_usb/android0/f_acm/acm_transports
echo diag > /sys/class/android_usb/android0/f_diag/clients
echo acm,diag,mtp,adb > /sys/class/android_usb/android0/functions
echo 1 > /sys/class/android_usb/android0/enable
start adbd
setprop sys.usb.state diag,adb
Here's what you need to do from a shell, either via adb shell or a shell from a console app:
Code:
su
setprop sys.usb.config diag,adb
The device immediately disconnects you.
When I do a
Code:
getprop sys.usb.config
from a console on the device it does show diag,adb mode but I'm not seeing a device showing up when I connect the adb cable.
dmesg on the device (needs to be run as su) shows this error:
Code:
adb release
dwc3 f920000.dw3: request ed50b780 was not queued to ep0out
mtp_release
adb_open
android_usb_gadget: unable to get diag usb channel
diag: Cannot open channel 'diag'
android_bind_enabled_functions: diag failed
andoird_enable:usb_add_config failed: err: -19
adb_open
mtp_release
satadru said:
The problem is that this needs to be run as root, with SELinux disabled.
You can set SELinux to permissive with this tool: https://play.google.com/store/apps/details?id=com.mrbimc.selinux
As per here:http://forum.xda-developers.com/showpost.php?p=39686712&postcount=3 the usb init script for hammerhead should tell us the steps for diag mode.
That hammerhead init script is here: https://android.googlesource.com/device/lge/hammerhead/+/kitkat-release/init.hammerhead.usb.rc
Here's the essence, if you want to run it from your own script:
Code:
stop adbd
echo 0 > /sys/class/android_usb/android0/enable
echo 1004 > /sys/class/android_usb/android0/idVendor
echo 61F1 > /sys/class/android_usb/android0/idProduct
echo 239 > /sys/class/android_usb/android0/bDeviceClass
echo 2 > /sys/class/android_usb/android0/bDeviceSubClass
echo 1 > /sys/class/android_usb/android0/bDeviceProtocol
echo smd > /sys/class/android_usb/android0/f_acm/acm_transports
echo diag > /sys/class/android_usb/android0/f_diag/clients
echo acm,diag,mtp,adb > /sys/class/android_usb/android0/functions
echo 1 > /sys/class/android_usb/android0/enable
start adbd
setprop sys.usb.state diag,adb
Here's what you need to do from a shell, either via adb shell or a shell from a console app:
Code:
su
setprop sys.usb.config diag,adb
The device immediately disconnects you.
When I do a
Code:
getprop sys.usb.config
from a console on the device it does show diag,adb mode but I'm not seeing a device showing up when I connect the adb cable.
dmesg on the device (needs to be run as su) shows this error:
Code:
adb release
dwc3 f920000.dw3: request ed50b780 was not queued to ep0out
mtp_release
adb_open
android_usb_gadget: unable to get diag usb channel
diag: Cannot open channel 'diag'
android_bind_enabled_functions: diag failed
andoird_enable:usb_add_config failed: err: -19
adb_open
mtp_release
Click to expand...
Click to collapse
yes i got these messages too. does they mean google disable the diag channel on hardware level?
I suspect a software and not a hardware issue. Maybe compare kernel sources with that on the LG G2 and also that for the Nexus 4...
Sent from my SCH-I535 using XDA Premium 4 mobile app
---------- Post added at 10:23 AM ---------- Previous post was at 10:23 AM ----------
Or maybe a kernel module in the source just isn't getting built.
Sent from my SCH-I535 using XDA Premium 4 mobile app
satadru said:
I suspect a software and not a hardware issue. Maybe compare kernel sources with that on the LG G2 and also that for the Nexus 4...
Sent from my SCH-I535 using XDA Premium 4 mobile app
---------- Post added at 10:23 AM ---------- Previous post was at 10:23 AM ----------
Or maybe a kernel module in the source just isn't getting built.
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
"unable to get diag usb channel" maybe is the key of this problem, i guess
I think so. But it seems silly to disable a diag channel in hardware in case there's a problem...
Sent from my SCH-I535 using XDA Premium 4 mobile app
---------- Post added at 10:38 AM ---------- Previous post was at 10:35 AM ----------
We might also be able to check the diag functionality by looking at other devices that also have a Qualcomm MDM9x25 chipset, which is only in newer devices...
Sent from my SCH-I535 using XDA Premium 4 mobile app
could you locate the source code witch throws this err?
Sent from my Nexus 5 using xda app-developers app
satadru said:
I think so. But it seems silly to disable a diag channel in hardware in case there's a problem...
Sent from my SCH-I535 using XDA Premium 4 mobile app
---------- Post added at 10:38 AM ---------- Previous post was at 10:35 AM ----------
We might also be able to check the diag functionality by looking at other devices that also have a Qualcomm MDM9x25 chipset, which is only in newer devices...
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
found this err in /kernel/msm / android-msm-flo-3.4-kitkat-mr0 / drivers / usb / gadget / f_diag.c
int diag_function_add(struct usb_configuration *c, const char *name,
int (*update_pid)(uint32_t, const char *))
{
struct diag_context *dev;
struct usb_diag_ch *_ch;
int found = 0, ret;
DBG(c->cdev, "diag_function_add\n");
list_for_each_entry(_ch, &usb_diag_ch_list, list) {
if (!strcmp(name, _ch->name)) {
found = 1;
break;
}
}
if (!found) {
ERROR(c->cdev, "unable to get diag usb channel\n");
return -ENODEV;
}
......
......
}
prometheusZ said:
found this err in /kernel/msm / android-msm-flo-3.4-kitkat-mr0 / drivers / usb / gadget / f_diag.c
Click to expand...
Click to collapse
Does the Galaxy S4 also use the same chipset? The kitkat kernel sources for that (at least the google edition model) just got released too.
We might be able to do a diff on the usb trees inside the kernel source and see if there's a difference. Probably also makes sense to compare the the source out there for the LG G2 model too, since that's going to be very close to our model.
Also have you seen the work they're trying to do with the LG G2 with qpst here: http://forum.xda-developers.com/showthread.php?t=2493659?
We might want to combine our efforts.
satadru said:
Does the Galaxy S4 also use the same chipset? The kitkat kernel sources for that (at least the google edition model) just got released too.
We might be able to do a diff on the usb trees inside the kernel source and see if there's a difference. Probably also makes sense to compare the the source out there for the LG G2 model too, since that's going to be very close to our model.
Also have you seen the work they're trying to do with the LG G2 with qpst here: http://forum.xda-developers.com/showthread.php?t=2493659?
We might want to combine our efforts.
Click to expand...
Click to collapse
my friends and i recompile the kernel with choosing "usb qualcomn diagnostic bridge driver" option, and made a boot.img. after flash the boot.img, the diag mode still can not open and the error messages are the same
prometheusZ said:
my friends and i recompile the kernel with choosing "usb qualcomn diagnostic bridge driver" option, and made a boot.img. after flash the boot.img, the diag mode still can not open and the error messages are the same
Click to expand...
Click to collapse
Is the qualcomm bridge driver loaded in the LG G2 kernel?
If it isn't enabled in the N5 kernel, it's possible that they didn't bother updating the code for it. Will the LG G2 kernel load on our device? They're definitely able to get diag mode on their device.
satadru said:
Is the qualcomm bridge driver loaded in the LG G2 kernel?
If it isn't enabled in the N5 kernel, it's possible that they didn't bother updating the code for it. Will the LG G2 kernel load on our device? They're definitely able to get diag mode on their device.
Click to expand...
Click to collapse
wo tried and succeed. finally the diag mode is opened. you can try recompile the kernel by choosing these options
Awesome. Can somebody upload the modified kernel image with the diag kernel?
Sent from my SCH-I535 using XDA Premium 4 mobile app
Yippeee!!!
satadru said:
Awesome. Can somebody upload the modified kernel image with the diag kernel?
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yup...eagerly waiting for the modified kernel and exact command to get it working.
:good:
enable diag mode : Boot_with_diag.img
- bbs.gfan.com/android-6953114-1-1.html
- pan.baidu.com/s/1sxMe1
satadru said:
Awesome. Can somebody upload the modified kernel image with the diag kernel?
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
use fastboot command to flash this image
Here is my experience with proximity sensor, and finally got it working back with manual recalibration. So sharing here with you if any one having same issue.
Symptoms : Weired behavior of proximity sensor, I had issue like screen was not turning On after call ends. Air call accept not working
Test : Dial *#0*#
Now this will open up menu, select sensor from there and putting hand near proximity sensor screen should turn green and vibrate. I have had that, but when moving hand away from proximity sensor it was not turning back to normal stat. So once proximity sensor gets activated, it was remaining On always.
Suggestion from net : There wa plenty of cases I have seen having same issue on note3. there was different suggestion like turning auto brightness off / removing Ext SD card was worked for other but not worked on my case. Also someone asked to blow compressed air in earpiece to clean sensor, that helped but just for few minutes only.
Solution that was worked for me.
First thing this setting files remains in EFS folder, so if you have EFS backup, you can try restoring it. In my case I had old EFS backup (MJ1) and have ROM MK2, and later I realized, there is some file difference in both version. (samsung have again screwed EFS, Thanks )
So finally I need to manually recalibrate proximity sensor and that worked fine and since couple of hrs using it without issue.
Requirements :
-Adb access and rooted device.
You should have rooted device, also make sure USB debugging is ON
Connect device to PC and run adb shell
Type following command
Code:
cd /sys/devices/virtual/sensors/proximity_sensor/
then
Code:
cat state #blank value
You will get some value(blank value), note that value. In my case it was 85.
Now enter this command to get actual configuration value
Code:
cat prox_cal
you will get some value, note that value too. In my case it was 46,166,126
Now make total of blank value and actual value(first part) , e.g. in my case it was 85+46 (red above) = 131
Now you need to find HEX value for 131. Get from here OR Here
So in my case it was (HEX value for 131) 83
Now you need to write this value in prox_cal file in EFS folder. For this you need,
Type this with adb
Code:
su
Grant supersu permission from device if ask.
then
Code:
echo -en $'\x83' > /efs/prox_cal
here 83 is my value, you have to replace with your.
then
Code:
sync
Now last step you needs to change permission. here is three steps for that.
Code:
chown system:system /efs/prox_cal
chmod 644 /efs/prox_cal
sync
Reboot device and check proximity sensor is working fine.
GoodLuck !
Referred too many threads on XDa and google, main credit goes to @greaty for clear instruction.
Sorry intended to post on Note3 general forum.
Mod please move this thread.
Hi dr.Ketan,
Good morning!
Sometime back I wrote to you about the proximity sensor not working and also about the weird results I was getting with adb. You told me to wait for some time as you were busy with the kitkat rom for note 2. If you are relatively free now, would you please guide me in this regard. I'm pasting the results I get on adb:
"Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\Admin>adb devices
List of devices attached
4df723a360****** device
C:\Users\Admin>adb shell
[email protected]:/ $ cd /sys/devices/virtual/sensors/proximity_sensor/
cd /sys/devices/virtual/sensors/proximity_sensor/
[email protected]:/sys/devices/virtual/sensors/proximity_sensor $ cat state #blank valu
e
#blank value <
1
[email protected]:/sys/devices/virtual/sensors/proximity_sensor $ cat prox_cal
cat prox_cal
11,9
[email protected]:/sys/devices/virtual/sensors/proximity_sensor $"
You would have noticed that:
1. Once I punch in a command in adb, it puts the cursor at the end of the line rather that at a new line;
2. 'cat prox_cal' is giving me only two values;
3. If I add the blank value, i.e., 1 and the first digit of the cat prox_cal, i.e., 11, I would get 12 and a hex value for the same as 'C'.
Is it normal? If you are busy , would appreciate if you can indicate some resources regarding adb and android
regards,
dcpathak
yeah ut can be any so better first use that value and see if that works or not. If doesn't work then let me know.
you have to use this
echo -en $'\xC' > /efs/prox_cal
Click to expand...
Click to collapse
as per instruction and don't forget to do it with Supreuser (root access)
Did that and it seems to have solved the problem.
Interesting observation: this time the blank value increased to 14 so corresponding hex was E. used that and problem solved.
Any idea why commands were starting from the same line as the previous command?
Thanks and regards,
dcpathak
Thanks man, finally a solution for the promity sensor i really appresiate that you are sharing this with us i finally will get my prox sensor working
i wonder if this value is a normal value
[email protected]:/sys/devices/virtual/sensors/proximity_sensor $ cat prox_cal
cat prox_cal
2013274108,2013274228,2013274188
Hi,
you my friend are a legend, this works finally for me again after over month putting up with it.
Thanks
what should i do it's said not found?
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>adb devices
List of devices attached
4df79c57088840c5 device
C:\Windows\system32>adb shell
[email protected]:/ $ cd/sys/devices/virtual/sensors/proximity_sensor/
cd/sys/devices/virtual/sensors/proximity_sensor/
/system/bin/sh: cd/sys/devices/virtual/sensors/proximity_sensor/: not found
127|[email protected]:/ $
SOLVED
my one has returned back to the same issue again just randomly.
Thanks
Sent from my SM-N9005 using Tapatalk
Thanks @dr.ketan for share this method...and now my proximity sensor is back... i'm on leaked lollipop ????????????????????????????????? i'm very happy?
I had this issue too. After Samsung refused to repair my n9005 because of the triggered Knox counter, I just opened my phone and cleaned the dust that gathers between the prox. sensor and the front glass with isopropanol and a microfiber cloth. Now it's working again. The method described by OP and other methods didn't work for me.
i had the same problem and solved it typing in a terminal emulator
HTML:
$ su
$ echo 0 > /sys/devices/virtual/sensors/proximity_sensor/prox_cal
$ echo 1 > /sys/devices/virtual/sensors/proximity_sensor/prox_cal
$ chown system:system /efs/prox_cal
$ chmod 644 /efs/prox_cal
$ sync
Jager23 said:
i had the same problem and solved it typing in a terminal emulator
HTML:
$ su$ echo 0 > /sys/devices/virtual/sensors/proximity_sensor/prox_cal$ echo 1 > /sys/devices/virtual/sensors/proximity_sensor/prox_cal$ chown system:system /efs/prox_cal$ chmod 644 /efs/prox_cal$ sync
Click to expand...
Click to collapse
Yes it's definitely works for me...
SM-N900 cihazımdan Tapatalk kullanılarak gönderildi
@dr.ketan..
u are a legend, thanks alot. and for the other how found this..
for whom how is noob like me :angel: u could use terminal emulator from playstore after rooting(of course)..
thank you
Just followed the method using terminal emulator, rebooted and now works perfectly so far!!! Was getting different faults on different ROMs. On lollipop the proximity sensor just wouldn't work at all. Then went back to 4.4.4 and would work but only once (soon as you put the phone to ear during a call then remove it , although the screen would come on, the key pad would be unresponsive.) Which meant I had many voice mails that had built up and was unable to delete them lol.
Thanks again for this method....though I'm not entirely sure what this has exactly done....its worked.
Omg thank you. This works for lollipop n9005 too ?
I've been having this issue since upgrading to Lollipop, I'll be sure to try this!
how?
Jager23 said:
i had the same problem and solved it typing in a terminal emulator
HTML:
$ su
$ echo 0 > /sys/devices/virtual/sensors/proximity_sensor/prox_cal
$ echo 1 > /sys/devices/virtual/sensors/proximity_sensor/prox_cal
$ chown system:system /efs/prox_cal
$ chmod 644 /efs/prox_cal
$ sync
Click to expand...
Click to collapse
thanks, but it didnt work for me. I installed terminal emulator from the play market, then started typing the above, but it said su is not found, and echo etc is not allowed.
ive never used the emulator before and googling the subject did not help. could you explain what am i doing wrong?
You have device rooted?
Sent from my SM-N910G using xda premium
Hello XDA Dev Community!! I`m with You since 2011 ! but never wrote.. So HELLO!
EDIT
I`m not sure why my Q was took out of the topic:
https://forum.xda-developers.com/t/...-a-decryptable-twrp-no-root-required.4086625/ - I won`t argue anyway my question is related to the guide - link above.
EDIT ENT
Just to check with community if all is ok
My phone is Pixel 2, stock Android 11, bootloader unlocked, rooted (Magisk).
Connected phone via usb, entered in CMD:
Code:
adb shell
su
dd if=/dev/block/sdf2 of=/storage/emulated/0/Download/modemst1.bin bs=2048
As I understand I changed location of the output file - if wrong - pls correct me.
In Solid Explorer those 2 files have like HH:MM in name in front of sdf2 and sdf3 and both weigh 0 B.
Output files landed in Download folder like this:
modemst1.bin 256.00 kB
modemst2.bin 1.50MB
Is that right?
Is there any way to open those bin files and check if they are correct?
adb shell info after dd comand looked ok for me:
Code:
128+0 records in
128+0 records out
Ok. iso asking I could check with internet.. so bin is like iso but older..
If I mount it or convert to iso and mount - is there a way to check if it`s backed up correctly? I know that 100% sure I will be after formatting EFS and trying to recover from created files BUT... maybe there is sth I can check before?