yashsingh1/xdaforums huggingface dataset:
[HTC One X+] ThePhoneGeek:
Made the change, toggled radio off then radio back on to no avail.

Turned radio off, made the change, turned radio back on and same result.

Thanks for the help!!!

MG
[HTC One X+] mickliq:
Are you choosing "GSM/WCDMA, CDMA, and EVDO (PRL)"?
[HTC One X+] ThePhoneGeek:
I have chose that one as well as tried WCDMA Preferred, GSM Only, WCDMA only, GSM auto. Always defaults back to gsm/wcdma/lte auto.

Thx!

MG
[HTC One X+] mickliq:
^ Are you rooted/unlocked bootloader?
[HTC One X+] ac3kill:
You just have to make a apn for 4g network then you just go into apn and select the 4g apn or the lte apn

As far as 3g I donno I can just change mine from lte o hspa hspda or lte but I'm sure there's a 3 g only apn I just don't know it
[HTC One X+] rashad1:
Phone info apk
[HTC One X+] psicobelico:
I used to do this using the code *#*#4636#*#*

It is easier now.. thanks rashad1
[HTC One X+] DornoDiosMio:
Seems no matter which I pick it just resets to the standard option.

If I turn the radio off first I can set whatever I want, but, upon turning back one I still get 'LTE' even if it isn't the selected network type.

EDIT: I see I have the same problem as 'moregadget' in that no matter what I do it just seems to go back to its default settings. It must be some BS AT&T did to prevent us from opting out of the battery sucking LTE connection.

I am on an unlocked bootloader & rooted on the Elegancia 3.1.0 AT&T rom.
[HTC One X+] ThePhoneGeek:
Yep identical problem...

I went back to my original One X for a couple weeks and put the X+ away. I'll come back to it but right now its not fully functional for me.

I have eternal faith in the XDA community and that with more time the genius' here who are much smarter than I will figure it all out... :)

MG
[HTC One X+] ThePhoneGeek:
So I was loading the Team Venom ViperXL+ 1.2.0 ROM yesterday and had a moment where I felt like an idiot. As I was selecting the items on the ROM that I wanted to load I ran across the area where I select what 3G/4G icons I want and I suddenly realized something I haven't seen on the One X+ forum but was prevalent on the original One X.

When you have the AT&T 4G icons in use you can't manually select the network however when you load a ROM that allows you to use the typical H+/3G icons that I believe are on the international version you can.

MG
[Motorola Droid 3] alvin_a_garcia:
Hello,

I've been patiently following this thread http://xdaforums.com/showthread.php?t=1804665 for the past several months. Thanks to the selfless, hard work of Hashcode, dhacker, and also sylentprofet and jarveson (and apologies to anyone I haven't credited), the recent builds seem to have arrived at a level of functionality and stability that I'm thinking of trying to install my first custom ROM (I've already had SafeStrap 3.0.x installed for months).

My question is the following: I understand from the above thread and from Hashcode's blog that now the external SD card will be used as the default storage location. I was wondering what happens when an app is "installed to SD". From my previous experience on an original Motorola Droid, I know that "installing to SD" would move some files to a special directory on the SD card. I was wondering if this would cause collisions if the same app was installed under multiple ROM slots using SafeStrap.

Thank you for entertaining this newbie's question.
[Motorola Droid 3] MrObvious:
Actually the way I understand it is there is still the internal storage and external SD which are the same, but the internal storage gets partitioned separate from the rest of the storage so if you install an app to the SD card, I think it just goes in a regular folder. The system thinks the /system partition is in the regular storage for it but it actually is tricked to the internal storage.

I hope that makes sense.
[Motorola Droid 3] alvin_a_garcia:
Thank you very much for your response.

Is this regular folder on the external SD card? If so, does it mean that this regular folder will be shared by the ROMs in multiple slots if I have the same app installed under the ROM in multiple slots?

Thank you again.
[Motorola Droid 3] MrObvious:
If it's on the external SD then yes it is.
[Motorola Droid 3] Thiago AmP:
I had the same doubt when I recently started using ROMs on my Droid3. This thread helped me a lot.

I have lots of apps in my stock ROM that I've installed before rooting it. Do I have to install it all again on external SD? If yes, do I have to use a new flashed ROM or the stock ROM?
[Motorola Droid 3] spunker88:
On minimoto I noticed it was using the exact same sd configuration as stock, perhaps because its stock based. On CM10 the external SD card is the default /sd card but you can still access the internal sd.

Regardless of how the sd card is configured you'd still have to reinstall apps when going to another ROM. I recommend using Titanium Backup then its quite simple to restore apps on another ROM. For SD data you could just manually copy and paste the folders from the internal to external SD.
[Motorola Droid 3] Thiago AmP:
Thanks! So, a separate partition on SD Card would be a waste of "space", since the ROM's doesn't share acess to this partition. I've only tried with CM10, I'm going to try with MavROM and Minimoto, but i'm almost sure that I'll end backing all up with Titanium.
[Motorola Droid 3] RealPariah:
Sort of kind of. Basically this would be useful if you want to share apps and their settings between the custom and Stock ROMs installed on your phone [may be odd on an app by app basis depending on a few things but a good number *should* work [I dont use external SD as it eats the battery and is MUCH slower than using the /data partition so haven't tested this], so following should be close if not 100% correct

You would in stock ROM set your apps2SD app up [I DO NOT advise you to use the sdcard function found in manage apps>app area instead you should be using an app like Link2SD that actually creates a partition on your external SD and formats it to EXT3 or EXT4 [suggest using EXT4]. This way things like widgets still work whereas they don't when using the built-in android function [this happens as android uses a folder on the SDCard [which is FAT32 by default] and file permissions needed to run Widgets and some code can't be copied as needed on to a FAT32 partition so by using an app that partitions [or the recovery can do this but you would still need an app to manage which apps are in this partion] the SDCard app instead actually formats part of the card to the EXT 3 or 4 File system so it is the same as the /data partion so Android can copy EVERYTHING and nothing is affected and broken.

So you open your SDCard app manager in Stock ROM and format the External SD [THIS WILL ERASE EVERYTHING RUN APPROPRIATE BACKUPS BEFORE PARTIONING [move them to a computer and back if you dont have enough internal storage to absorb your data]]

When that completes open the app again [usually needs a restart first to mount the new partition before continuing].

Once you get that done open the Manager app and select the apps to move to this new partition.

CUSTOM ROM: Now once that is done boot in to safestrap and either setup a Custom ROM or change to it's boot slot. Next boot in to Custom ROM and install the same SD Card App Manager you used in Stock.

Next, once you open it it should say it found a partition and ask if you want to use it if it doesn't and just lists the app view the settings in the Manager app and HAVE IT SETUP AN EXISTING PARTITION. DONT PARTITION YOUR SDCard AGAIN [or all your newly moved data will bite it].

Now restart and allow it to boot back in to the Custom ROM again. Once this happens all the apps you moved to the SDCard partition should magically appear and be usable.

SO LONG AS YOUR STOCK AND CUSTOM ROMs ARE THE SAME VERSIONS DONT DO THIS IF YOU HAVE ICS ON THE SAFE SIDE AND JELLYBEAN AS A CUSTOM ROM IT WILL MOST LIKELY CAUSE ALL KINDS OF PROBLEMS
[Android Q&A, Help & Troubleshooting] Nishchay1:
i was able to root my device using Bin4ary method but when i try unrooting it shows me this error

Suggest me a proper solution ! I really need to unroot my device !

Will be waiting for your reply !

Please help !!!! :(

NOTE : I dont have any stock rom available for the device so i cant flash it to unroot my device

PS : i have Super SU installed . What will happen if i remove supersu.apk from system/app ? will the device get unrooted ?

i am using karbonn a21
[Android Q&A, Help & Troubleshooting] satan89:
Uninstalling supersu will not unroot phone but without it no app can get root permission.

Why are you trying unroot?

Sent from my ST21i
[Android Q&A, Help & Troubleshooting] Nishchay1:
There is an option in SuperSU to unroot phone . What about that ?

PS:Need to give it to a service center for faulty wifi device
[Android Q&A, Help & Troubleshooting] satan89:
I think that will only remove supersu and other root apps. You can try that. Or just uninstall it. Either ways its unlikely they will ask about root or check at service center.

worst case you have to pay service fee only.

Hit Thanks if I helped you!
[Android Q&A, Help & Troubleshooting] fantamedo:
Try Factory reset and wipe cache via recovery
[Android Q&A, Help & Troubleshooting] Lifehacker7:
Factory reset ain't gonna unroot!
[Android Q&A, Help & Troubleshooting] satan89:
And if you have custom recovery that too might void warranty

Hit Thanks if I helped you!
[Galaxy Note II Q&A, Help & Troubleshooting] CrazyEngineer:
I found out that the proximity sensor on my Note II isn't working as it should. Whenever I am on call, the screen goes off, but doesn't lit up when I move the phone away from my ear. I've investigated and found that calibrating the proximity sensor could solve the problem.

I've searched around but haven't found the right steps to calibrate the proximity sensor on Note 2. The 'Phone Tester' app shows weird behavior of the sensor. It sometimes just keeps waiting for the data and sometimes shows 'Far' , 'Near' status correctly. But once I move my hand near the sensor and then move it away, the status remains 'Near'.

I'd really appreciate recalibration procedure & any other recommended fix.
[Galaxy Note II Q&A, Help & Troubleshooting] Laynee1:
I would like to know the solution too

Handwritten from my Note 2
[Galaxy Note II Q&A, Help & Troubleshooting] sunking25:
I have same problem too
[Galaxy Note II Q&A, Help & Troubleshooting] abdo9119:
I think from check list call *#0*#:laugh:
[Galaxy Note II Q&A, Help & Troubleshooting] rumy:
Did any of you figure out a fix to this issue?
[Galaxy Note II Q&A, Help & Troubleshooting] bushako:
To calibrate the proximity sensor you need to edit the build.prop, file. Quickest way I do this is by using Romtoolbox pro which has that option. Once in the build prop up editor you'll see the option to recalibrate the proximity sensor. You'll need root access.

Sent from the Rabbit Hole
[Galaxy Note II Q&A, Help & Troubleshooting] rumy:
Where exactly in the build.prop is this setting. I access it using root explorer and scanned through the entire file and saw nothing that would hint at the proximity sensor calibration.
[Galaxy Note II Q&A, Help & Troubleshooting] bushako:
Sent from the Rabbit Hole
[Galaxy Note II Q&A, Help & Troubleshooting] rumy:
I don't have that in my build.prop I am running ARHD9.0

What exactly does that do. Does it just delay the screen from going of when on your face? In that case I have already disabled the proximity sensor during calls.

I am starting to wonder if this is a hardware fault.
[Galaxy Note II Q&A, Help & Troubleshooting] mariosraptor:
Can you try this? If you use and it does not work once removing it will restore your factory values.

http://db.tt/C7PJnQgt
[Galaxy Note II Q&A, Help & Troubleshooting] yushir0:
It looks like the proximity threshold is set too low in the kernel and causes this to misbehave when the sensor gets a little dirty.

For example: If you open the diagnostic menu by dialing *#0*# and look under sensors if your ADC value for the sensor is anything over 12, the proximity sensor will register that something is close to the phone. That value can be temporarily adjusted by setting prox_thresh under /sys/devices/virtual/sensors/proximity_sensor to something higher (like 30).

Unfortunately, it looks like changing this value doesn't "stick" and the next time the sensor is accessed, something changes it back to the default of 12.

I'm guessing that the default value is set in the kernel at compile time. Maybe someone can talk of the kernel devs into tweaking the value.
[Galaxy Note II Q&A, Help & Troubleshooting] icbraz:
anyone found a solution to this yet?

Hi, is rooting the phone the only way to get this working? So annoying... Maybe will just send this galaxy note 2 back for a refund, tried for a long time to get this fixed, I think it started after the last android update I thought they'd have done something about it by now...
[Galaxy Note II Q&A, Help & Troubleshooting] greaty:
On Samsung devices like i9100 (Galaxy S3) or N7100 (Note II) you can do the following if you have root permissions:

On Android Terminal App or adb shell do:

$ su
$ echo 0 > /sys/class/sensors/proximity_sensor/prox_cal
$ echo 1 > /sys/class/sensors/proximity_sensor/prox_cal

The zero resets the actual calibration offset.

The one does an auto calibration (read sensor value, set offset to this sensor value, write calibration offset to "/efs/prox_cal" which is read while device is booting).

Best for calibrate your sensor is to keep it dark, the glass have to be clean and the sensor free (so that the sensor doesn't measure anything).

The calibration offset is stored in efs, thats why you can make full wipe and use other ROMs without the need of recalibration.

You can check the running config by:

$ cat /sys/class/sensors/proximity_sensor/state

The first value is the calibration Offset, the second one is the sensor threshold (threshold is set at compile time).

Open *#0*# to see "sensors" and check if your proximity sensor is now working properly.

Because in Kernel code (copyright by Samsung) for the device driver is somthing like this autocalibration, i bet that there is a secret menue or code that does the calibration too. But until someone discovers this secret we have to have root permissions to do a proximity sensor calibration.
[Galaxy Note II Q&A, Help & Troubleshooting] marcmy:
Hey, I've been looking for a fix for prox sensor on my Note 2 ever since I installed Paranoid back in december/january, went back to stock and it was still broken. This fixed it!! So thank you :) I have just one issue, it seems to go back to being broken when I reboot the phone. Is there any way to prevent this? Also the *#0*# doesn't work for me and the cat command returns just a 0. Thanks.

EDIT: it might help to note that I'm running cyanogenmod 10.1 nightly now

EDIT2: I figured it out! I did a search for prox_cal and found one in /sys/devices/virtual/sensors/proximity_sensor with the values 18,9. i put those values in the empty /efs/prox_cal. It now works on boot. :)
[Galaxy Note II Q&A, Help & Troubleshooting] aHcVolle:
working great on my i9505 thanks !!!!
[Galaxy Note II Q&A, Help & Troubleshooting] adrianjayy:
Hello, so I had a very similar experience in flashing Paranoid and then my sensor went bezerk. It seems to be just not turning on with the phone, but the front camera does work fine. I was able to get it working a few days ago by flashing the stock rom and kernel multiple times, but I decided to get bold and reflash the Neak kernel and poof, that was over. Not another few flashes would bring my sensor back. At this point I don't even know what to do.

Thought it might also be worthwhile to mention: the light sensor also does not work and when I looked through the files in the sys/class/sensors for both proximity and light sensors the runtime status is unsupported.
[Galaxy Note II Q&A, Help & Troubleshooting] Skipjacks:
A full Odin restore should reset all these values and the whole thing should work right immediately as long as the sensor hardware hasn't gone bad, right?
[Galaxy Note II Q&A, Help & Troubleshooting] vaghotstuff:
Easy FIX!!!!!

I took a can of compressed air and blew it through the top earpiece grill a few times and Voila, it works great now!!

I actually used a Old perfume can which perfume was over and it was only pressing Gas OFF!! :P:P :good::good::good::good:
[Galaxy Note II Q&A, Help & Troubleshooting] mcelicalderon:
Finally Fixed My Sensor

Finally, this fixed my problem. I don't know why, but the other solution worked one time while using a CM 10.2 nightly

$ su
$ echo 0 > /sys/devices/virtual/sensors/proximity_sensor/prox_cal
$ echo 1 > /sys/devices/virtual/sensors/proximity_sensor/prox_cal

But, when I upgraded to the latest nightly, this stopped working. It wouldn't work even if y restored my stock ROM backup using TWRP, I even flashed a stock image with odin and the sensor would still malfunction.

Today I followed this steps using the values returned for my phone and it finally worked! I did this.

$ cat state #finger on the sensor to test if the sensor is working properly
120
$ cat state #blank value
10

This returned 255 #finger on the sensor and 69 #blank value

and when I did

cat /sys/devices/virtual/sensors/proximity_sensor/prox_cal

this returned 47,60,45.....so my offset was 47. Ths sum of offset and #blank value was 47 + 69 = 116 that is equal to 74 in HEX.

so I did

$ echo -en $'\x74' > /efs/prox_cal

and then

$ chown system:system /efs/prox_cal
$ chmod 644 /efs/prox_cal
$ sync

After that I rebooted my phone from the terminal using que command

$ reboot

and that was it! Now my sensor is fixed and survives reboot. Thanks!
[Galaxy Note II Q&A, Help & Troubleshooting] mcelicalderon:
Not True

Sadly, no. I would have thought so too, but recently I did a full Odin restore and that didn't fix the problem. I-m not sure why, as I thought that wipped everything on my phone. I believe it has something to do with the fact that doing a full ODIN restore won't necessarily restore your EFS partition, and I believe that's where the problem is. Actually be very careful not to wipe you EFS partition using ODIN as that's where your device's info is stored (That's what I found searching online).

But, as I said in my lateest post in this thread, following the steps described in this post about echoing your calibration values to you /efs/prox_cal file actually fixed my problem. Good luck!
[Galaxy Note II Q&A, Help & Troubleshooting] jeromechin:
It worked!!

This worked immediately!! Thank you so so much! I could not believe it! I thought I damaged the sensor after dropping the phone.

Thanks!! :good::good::good::good::victory:
[Galaxy Note II Q&A, Help & Troubleshooting] czar22:
so I did

$ echo -en $'\x74' > /efs/prox_cal

and then

$ chown system:system /efs/prox_cal
$ chmod 644 /efs/prox_cal
$ sync

After that I rebooted my phone from the terminal using que command

$ reboot

-- Error

' not found

---------- Post added at 08:47 AM ---------- Previous post was at 08:40 AM ----------

after many attempt's i try the "Blow Air" method ---

and Succes

Thxxxxxx...
[Galaxy Note II Q&A, Help & Troubleshooting] korval:
Thanks! Worked like a charm!
[Galaxy Note II Q&A, Help & Troubleshooting] azawarai:
Codes worked on i9500. Thanks!
[Galaxy Note II Q&A, Help & Troubleshooting] Fataldose:
Thanks a lot man.
[Galaxy Note II Q&A, Help & Troubleshooting] gdstheking:
can u provide me ur proximty_sensor folder using root explorer

under sys/class/sensors/ from here u have to backup the folder make it zipped an attach here..:confused:
[Galaxy Note II Q&A, Help & Troubleshooting] andr_lee:
I can't believe it!!!!

I executed this procedure just as a longshot after trying so many other things. And my Galaxy S4 works perfectly now. Unbelievable!!! Thanks :)
[Galaxy Note II Q&A, Help & Troubleshooting] gdstheking:
bingo......worked like a charm,

but value remains 51(51,51,51)
[Galaxy Note II Q&A, Help & Troubleshooting] azawarai:
sorry i didnt see your reply.

thats normal value because sensor is reading the minimum value as 51 now. this process makes 51 to 0.

51 is new 0.:good:

by the way it survives rom changes either.
[Galaxy Note II Q&A, Help & Troubleshooting] LiMunnn:
Hello friends, I have a problem with samsung s4 (proximity sensors) sensor as the non-stop running, I went to test the ADC 130, and when you put your finger on the sensor, then the 255, I tried to change the value in / sys / class / sensors / proximity_sensor /prox_cat but I could if my phone is rooted, if someone can help me please
[Galaxy Note II Q&A, Help & Troubleshooting] vchawla:
Same for my S4. Air can method only got me down from 255 to 160 with the sensor uncovered. This procedure restore my proximity sensor such that it is now usable again.
[Galaxy Note II Q&A, Help & Troubleshooting] Ammar Saood:
FIXED. Thanks to mcelicalderon, Finally Fixed

Methods that worked for me.

Method 1.

Blow Air it will solve your prob hopefully.

Method 2.

go to samsung code *#0*#. then SENSORS and Read your Proximity sensor values.

<<< DECISION >>>>>

####Calibration isnot needed if ####

.

your phone doesnt vibrate in normal but does so when u physically put your finger on the Sensor.

#### Calibration needed if ####

.

your phone is vibrating in this menu no matter what, you put your finger on the sensor or not

Follow these steps

1. download Android Terminal from store

2. type these commands to calibrate automatically

$ su

# echo 0 > /sys/devices/virtual/sensors/proximity_sensor/prox_cal

# echo 1 > /sys/devices/virtual/sensors/proximity_sensor/prox_cal

Reboot and see if it works.go to *#0*# and check if it continuously vibrating or only does so when you put your finger on the SENSOR.

<<<< IF Continuously Vibrating Follow these steps>>>>

you need to manually put values in ur /efs/prox_cal.it Reads Hexadecimal value. so you have to convert your decimal values into HEX.

##### FIND YOUR Decimal Values and pushing them into /efs/prox_cal ######

Method : finding two values for calibration . offset + normal value.

##.. FINDING OFFSET ######

cat /sys/devices/virtual/sensors/proximity_sensor/prox_cal

note down the values it returns.. mine is 5,64,100.. you only need the 1st value which is 5.

### FINDING NORMAL STATE ######

cat /sys/devices/virtual/sensors/proximity_sensor/state

note down the value if returns. mine is 64

now ADD OFFSET value + Normal Value

5 + 64 = 69

Convert in Hexadecimal which is 45.

<<<<<<<<<<< Pushing the value in /efs/prox_cal >>>>>>>>>>>>>>

# echo -en $ '\x45' > /efs/prox_cal

then

# chown system:system /efs/prox_cal

# chmod 644 /efs/prox_cal

# sync

# Reboot

All done. after that go to *#0*# then SENSORS and move your finger on the sensor, yout phone will Vibrate only when you put your finger on the sensors.

Manual method worked for me.

ENJOY.
[Galaxy Note II Q&A, Help & Troubleshooting] wujh:
I was using S4 MINI

When my finger on the sensor to test ,The maximum value of only to 7, with white paper to cover the value may to 14 (more than 10) Action

How to use the manual adjustment value from (0,10) to (0,5), Because I enter # echo -en $ '\x05' > /efs/prox_cal ,Will become (5,10), To take action as more than 10

When I enter $ echo ‘0,5’ > /efs/prox_cal ,Will become (171256880,58), Use white paper will not operate。(14<58)

How do I enter in order to reduce "Cancelation Threshold"=5 , prox_cal value from (0,10) to (0,5)

Sorry, my English is not good, hoping to understand what I mean
[Galaxy Note II Q&A, Help & Troubleshooting] Ammar Saood:
Read my post u wl hv more clarity

http://xdaforums.com/showthread.php?p=48468330
[Galaxy Note II Q&A, Help & Troubleshooting] wujh:
Thank you for your answer.

I have tried this method but without effect.

Because my hand to cover the sensor, the value only to 7, so I want to adjust this value back 10 to 5(prox_cal 0,10->0,5), when it will hand to cover the action, without the use white paper
[Galaxy Note II Q&A, Help & Troubleshooting] peter_baum:
be careful about spaces

I think there should not be any space between the dollar sign and the single quoted string. Try

$ echo -en $'\x0a' > /efs/prox_cal

instead of

$ echo -en $ '\x0a' > /efs/prox_cal