yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Q&A, Help & Troubleshooting] kks0021:
hey guys i want to know can I already install the HX-Camera-Mod on a custom rom based on 4.2.2?? i nowhere found a right thread.. hope XDA can help :D
[Android Q&A, Help & Troubleshooting] zeratos:
Hello, I want to know if there is a way to disable whatsapp updates, a pop up appears everytime I open the app asking me to update it.

Thanks in advance.
[Android Q&A, Help & Troubleshooting] Jeanbassil:
dear whatsapp service after 3 or 4 updates you do not install will stop supporting your older app with the service, so if you do not update it will stop working as a messenger, the new whatsapp app has a far better ui, very much eye catcher, is much faster and much bug free and richer in features
[Android Q&A, Help & Troubleshooting] fabioalerni:
Yes

Now whatsaap comes with lots of new features it also include delete button , now you can easily deactivate whatsaap from your mobile phone.
[Android Q&A, Help & Troubleshooting] kemroy:
same problem

thats true but i understand his problem cause it gets to me all the time..im using the app on a non gsm tf300t and the newer app doesnt work..so everytime i start it i get that annoying notification..i definitely need help with that.I know its an old thread and all but i still have this problem.
[Android Q&A, Help & Troubleshooting] chr2002:
I know, this is an older thread, but it fits to my question.

Is there a way to disable the automatic Update check in Whatsapp Plus ?

There are to much updates for things which are uninteresting for me. I just need the stealth mode :)

My Partner uses the whatsapp stock version, so i know about new and important updates if the Playstore Version got Updated.

Greetings chris
[Android Q&A, Help & Troubleshooting] SMARTHACKER67:
do anyone know hoe to hack whatssapp

do anyone know hoe to hack whatssapp?

i have read several post but seems like they are not going to work
[Android Q&A, Help & Troubleshooting] karakemal:
Hi,

I was installed whatsapp plus 6.35d now if i try to update update new version installed succesfully 6.43 with double blue tick version but in setting my version is still 6.35d. I uninstalled clean dalvik and cache reboot nothing helps

What may be the problem?
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Dzol Cp:
​

I just wanna share how to edit smali and change a pop message when you clicks again and again at Android Version :fingers-crossed:

Example

To change 'zombie art by Jack Larson' to yours text for example 'Ice Cream Sandwich' :P to have a fully changed Ginger Bread to???? :D

1.Basic knowledge how to compile/decompile using Apktool/Apkmanager/

Tickle My Android(I try it and so easy) Credits to Ticklefish

2.Brain and brave :laugh:

Method :

-Decompile framework.jar

-Find PlatLogoActivity.xml in smali/com/android/internal/app/

-Open with Notepad++(Windows) or gedit(Linux)

-Find this line ["Zombie art by Jack Larson" for GB] ["Ice Cream Sandwich" for ICS] ["Jelly Bean" for JB]

-Change this text to yours "WHATEVER"

-Save and close file

-Recompile your framework.jar file

-Make an CWM package and install/flash it

-Or replace it with Root Explorer or other app and change permissions to 644(rw-r--r--) and restart your phone

-Tell me the Result :D

CREDITS TO : ALUCARD1989PL For his info thread :good:

Original Thread

http://xdaforums.com/showpost.php?p=34563875&postcount=3
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Dzol Cp:
Reserved
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Alucard1989pl:
I'm not a master :D but it's good for ya ;)
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] MicQo:
Error with Decompiling please help me:

I: Baksmaling...
Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
at org.jf.dexlib.Code.Format.Instruction31i$Factory.makeInstruction(Inst
ruction31i.java:82)
at org.jf.dexlib.Code.InstructionIterator.IterateInstructions(Instructio
nIterator.java:85)
at org.jf.dexlib.CodeItem.readItem(CodeItem.java:154)
at org.jf.dexlib.Item.readFrom(Item.java:77)
at org.jf.dexlib.OffsettedSection.readItems(OffsettedSection.java:48)
at org.jf.dexlib.Section.readFrom(Section.java:143)
at org.jf.dexlib.DexFile.<init>(DexFile.java:431)
at org.jf.dexlib.DexFile.<init>(DexFile.java:267)
at brut.androlib.src.SmaliDecoder.decode(SmaliDecoder.java:44)
at brut.androlib.src.SmaliDecoder.decode(SmaliDecoder.java:33)
at brut.androlib.Androlib.decodeSourcesSmali(Androlib.java:73)
at brut.androlib.ApkDecoder.decode(ApkDecoder.java:85)
at brut.apktool.Main.cmdDecode(Main.java:128)
at brut.apktool.Main.main(Main.java:65)
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Dzol Cp:
Upload your framework.jar

and i try to do it for you and/or pm me what letter you want to replace :D
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] ReadReadz:
How to change background :laugh:
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Dzol Cp:
How you describe? Transparent or replacing with wallpaper?
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Diaz1999:
Hey [MENTION=4421347]dzolcp[/MENTION] are you know how to change CyanogenMod Pop Up Message too?
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] yamin8000:
if you wanna change that it is in systemui.apk/drawable-nodpi
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Diaz1999:
No. That's Jellybean icon, not the background

via XDA for Timescape™
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Dzol Cp:
I'll re-check again for you :D
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] nym_ardika:
Could you make pop up message for zellycream rom and instal with cwm please
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Diaz1999:
I could do that. give me your framework.jar and change to what???
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Diaz1999:
Are you've done with the re-checkment :confused:
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Nobbienoob79:
I was searching for this guide sir thank you :good:
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] ARGHA_DAS:
Awesome One Sir :D
[Nexus 4 Q&A, Help & Troubleshooting] JDYx:
I'm looking to get an N4 in the next few weeks and after having smashing the screen on my Desire I want to get a case or bumper for the N4. I probably prefer a bumper as it allows you to see a lot more of the phone but what have people's experiences been with dropping the phone with a bumper on?

Cheers
[Nexus 4 Q&A, Help & Troubleshooting] Jeanbassil:
if the bumper is thick a bit in the front and makes a bit of space between the screen and the bumper like some thick silicon bumpers then it will protect the screen better if you drop the phone and the bumper protects very well the back of your device and is much more suitable for daily usage, though if you drop a lot your phone or put it anywhere I prefer so much a case, though as the n4's back is less resistant than its screen, a bumper should do the job for you if you need something stylish and better and easier for use
[Nexus 4 Q&A, Help & Troubleshooting] kendiep:
Depends on what you do with your phone. If you like your phone naked, the bumper is amazing, it gives the n4 a sick chrome border (plastic though) but it doesn't cover the front and back from scratches, although you can probably find a screen/back protector for cheap.

If you are scared of dropping it or scratching it, get a silicone or tpu case. They'll at least guarantee some kind of shock resistance and protect your phone a bit better.

In the end, it's all your preference, see if you can go to a store and try on the cases first!

Hope this helps.
[Nexus 4 Q&A, Help & Troubleshooting] JDYx:
Cheers for the response guys, think I'll go with a bumper as I like the device naked, obviously it doesn't provide as much protection but I think it should be pretty good for being dropped occasionally. I just wanna be able to see the whole device :D
[T-Mobile LG G2x] Pain-N-Panic:
After doing as much research as possible and having all the necessary tools to root my phone and flash the ROM I want.....I was wondering if it's encouraged to have a micro SD card in the phone before doing so. Is it safer to have one?

Thanks
[T-Mobile LG G2x] Jeanbassil:
I prefer a micro sd
[T-Mobile LG G2x] Yuvin:
It shouldn't really be safer but I used an SD Card to store all my Roms, gapps, etc, just in case I have to use a cleaner which formats the Internal SD (G2x Scrubber I think)
[T-Mobile LG G2x] Pain-N-Panic:
Appreciate the replies. I think i'm going to go ahead and root my phone and install hellfire without an SD card..

It is possible for me to go ahead and buy one after the fact and use it for future purposes in case I decide to flash a different rom?

Also, for rooting the G2X I have been given 2 ways of doing so. One is to use superoneclick. The other, is to simply manually flash CWM on my PC and from there install a custom rom that is already rooted. The second method was given to me because superoneclick does not work for the G2x if it's on 2.3.4 which is the current update that I am on.
[Samsung Galaxy Nexus] ToMeRv32:
Hey, what is the lightest launcher (using less RAM and fastest.)?

Aokp launcher? Trebuchet? Apex? Nova?

Anything else?

I don't need effects and stuff like that,

Just light and fast one. (of course I want to customize it a bit. 5*4 etc..)
[Samsung Galaxy Nexus] chefthomas99:
I'd have to say Zeam.
[Samsung Galaxy Nexus] Zepius:
could try http://www.droid-life.com/2012/12/0...ay-for-4-a-minimal-launcher-to-say-the-least/
[Samsung Galaxy Nexus] szucsgf:
Holo Launcher is fast, stable, decently customizable, and smaller than Apex or Nova. And it's free. Worth trying.
[Samsung Galaxy Nexus] ToMeRv32:
Ics or jb (HD)?

Thanks everyone I'll try them.

Holo looks exactly like nova so I don't think it will be lighter.

Zeam is definitely lighter but it's too simple for me.
[Samsung Galaxy Nexus] Wh1t3Rose:
I just gave Holo launcher HD a shot. Nova can use 40-50 MB of RAM at times. Holo launcher doesn't even show up under running apps it's that light. And is half the size of Nova in app size. If I use the keep in memory option in Holo launcher settings then it uses 25-30 MB of RAM. Once again that is almost half of nova.

Edit: just noticed in Holo Launcher HD gestures is a free feature while it is a paid feature in Nova

Toro | Xylon | AK Diamond
[Samsung Galaxy Nexus] quivertaotao:
just tryed holo launcher HD, app drawer is not as smooth as nova.

will stick to nova launcher
[Samsung Galaxy Nexus] Wh1t3Rose:
I have no lag issues and I'm underclocked to 920mhz

Toro | Xylon | AK Diamond
[Samsung Galaxy Nexus] buggerthis:
Apex's ram footprint is between 35-45mb. It's always seemed snapper than Nova to me and it has all but a few of the customizations that Nova does
[Samsung Galaxy Nexus] ToMeRv32:
Umm.. Okay.

I'll try it again.
[MDA, XDA, 1010 Software Upgrading] Azh_fx:
can i upgrade my banger o2 xda 32mb one with the latest t-mobile rom?

or am i missing something here?

the winmobile update is the phone edition one!

thanx
[MDA, XDA, 1010 Software Upgrading] Qman:
Yes, but this is the first time I've heard it being called a "banger"!

Where did you get that name from? Is it listed on the device?

Also can you go to Start, Settings, System and post here whats under Device Information.

Thanks,
[MDA, XDA, 1010 Software Upgrading] cruisin-thru:
Qman, "banger" in the UK is usually descriptive of an old rusty car or something well past its prime. As in "I must get rid of this old banger before it rusts away or falls apart".
[MDA, XDA, 1010 Software Upgrading] leef:
My dad usually refers to my mum using the same term :lol:
[MDA, XDA, 1010 Software Upgrading] Qman:
I see...Hehehe! LOL

You guys are to much! :D
[Sprint Samsung Galaxy S III] machx0r:
Just got my Galaxy S3 a few days ago and today when I answered a call the screen immediately went blank and I could not turn it back on until the caller hung up. I've had other calls prior to today and cannot recall if the phone behaved the same way. I've been searching for a solution and everything points to a faulty proximity sensor. I've worked around the problem by disabling "Auto screen off during calls" under "Call settings". This works but it's not perfect since if I forget to manually turn off the screen I'm likely to press buttons with my face.

Under *#0*# -> Sensor -> Proximity Sensor: The PROXIMITY always reads 1.0. The ADC field increases as I get closer to the proximity sensor but never drops below 1 (should it?). Are PROXIMITY and ADC both readings from the same sensor?

Under *#7353# -> Proximity Sensor: It always says "Working" and vibrates. From the other tests in this menu I assume this is the "On" state and that the correct behavior would be to not vibrate and display a different message when the sensor is "Off" (ie: nothing is close to the sensor).

Several test apps (Android Sensor Box, Proximity Sensor, Sensor Test) also report 0cm or something similar indicating that something is close to the sensor.

Thanks in advance for any help :good:
[Sprint Samsung Galaxy S III] topherk:
This may be a stupid question, but do you have a case that might be covering the proxy sensor? I'm also assuming you have cleaned the area where the sensor is. Other than that you might be able to take the phone into the Sprint store and get it replaced. If they won't take it back, call up Samsung customer service. If it's a faulty sensor, they might replace the phone free of charge (others have had good experiences with Samsung customer support)

Hope you get it fixed!
[Sprint Samsung Galaxy S III] machx0r:
Thanks for the response. No screen protector or case. I did clean the entire screen this morning and the behavior didn't change. Was hoping I wouldn't have to take the phone back but then again if this was a common problem with a simple solution my searching this morning probably would have turned up an answer :)
[Sprint Samsung Galaxy S III] CNexus:
Lol yeah, this is the first time I've seen anything about this, and I respond to literally almost every thread, or at least read through each one. But like topherk said, its probably a hardware issue. Would you be able to check to see if the "1.0" value is present on another S3? Maybe its a default of some kind (i would check myself, but my S3 took a 4 story dive recently and is out of service)
[Sprint Samsung Galaxy S III] machx0r:
I don't know anyone else with an S3 but if anyone wants to check their *#0*# -> Sensor screen and tell me what the PROXIMITY and ADC values are when you aren't close to the sensor I'd appreciate it. Maybe I'll hit up the Sprint store and test it on a display model :laugh:

That said the page I discovered the *#0*# menu on has a screenshot and the PROXIMITY is showing 0.0 (I assume he's away from the sensor):

Where as this is mine when I'm away from the sensor:
[Sprint Samsung Galaxy S III] machx0r:
After digging a little deeper it appears that the G3 uses the same IC (a GP2A from Sharp) for both the proximity and light sensor. From looking at the GP2A kernel module code it appears that the ADC values are from the light sensor output and the PROXIMITY value is from the proximity sensor output (0.0 = nothing within 5CM, 1.0 = something within 5CM). The ADC values definitely change and the interpreted light sensor lux values change when I cover it or shine a flashlight into it.

So now I'm not so sure if it's possible for it to be a hardware issue or if it's a software issue caused by some weird state. Think I'll try a factory reset and see if the situation changes...
[Sprint Samsung Galaxy S III] xblackvalorx:
Have you ever installed a flip cover app?
[Sprint Samsung Galaxy S III] machx0r:
No, pretty standard apps installed and nothing specific to motion or proximity (aside from the handful of test apps I've installed to see what the proximity sensor readings are).
[Sprint Samsung Galaxy S III] CNexus:
Interesting...

Lol, i would recommend going to the Sprint store (if its not a hassle) and testing it out with their S3 on display, surefire way of knowing if something got borked with yours

I dont know whether they would charge for this or not, hopefully they dont, but you could also ask the reps to check it over for you and say you've been having some weird behavior with your incoming calls and the screen on/off events
[Sprint Samsung Galaxy S III] Xiamen:
Exactly what's been happening with my Samsung Galaxy Note 2 running stock firmware (rooted) with no screen protector. Been searching the internet for months and tried several proximity screen off apps to no avails. After countless tests and trials I am convinced that the proximity sensor when activated is stuck "near" (PROXIMIY = 1.0 at ADC level <= 12) unless there is bright enough ambient light. If some gurus could shade some lights on how to set the proximity threshold "prox_thresh" to be greater than 12 (say 30) (and that setting will stick after restart) that would be great!
[Sprint Samsung Galaxy S III] esdwa:
I have the same problem with my brand new TMobile Galaxy Note 2 where proximity sensor does require a lot of ambient light in order to switch the screen on and off during the call. I noticed that the screen protector is part of the problem so I removed it and it helped a bit but not always. I was afraid the sensor is broken itself and requested for replacement phone however I tried the *#0*# combination to test the sensor and found that ADC (analog to digital converter) output changes as I approach the sensor. With no proximity ADC shows value of between 11 and 15 and it is increasing smoothly to 140 as I move closer and furthermore reaches 190 as I press my finger against the screen. So the proximity sensor hardware actually works just fine it is the software layer including driver that possibly creates a problem which results in Proximity value being always equal 1.0 despite of ADC output precisely following the actual proximity. Several applications available call play market follows the Proximity value therefore making sensor based ofperation difficult or useless. I hope that upcoming system update will address the flaw making sensor based functions to work finally as they should.
[Sprint Samsung Galaxy S III] keeperjones:
Galaxy S3 proximity sensor replacement

Same issue here. A few things that may be of interest. My issue did not start after an update, it just started happening out of the blue. It is not because of being dirty or a because of a case. When I get into the diagnostic screen, the proximity sensor reads 0 and then goes to 1 when you get in proximity. It then stays at 1 and won't go back to 0. The ADA changes values, apparently correctly. The one thing that I thought was interesting, if I flash a bright LED flashlight on it, it does go back to zero. It is almost like it is not as sensitive to light all the sudden. This light trick works no matter how far away the light is. I am thinking the sensor is going bad.

I see several options to replace it on eBay, I changed out the screen last year, so I know how to change out the front camera and sensor. The only OEM ones I see are used or from China. Has anyone ever tried any of these, OEM or otherwise? They are cheap, I think I will give it a shot.
[Sprint Samsung Galaxy S III] keeperjones:
SOLVED

Just a heads up, I fixed my problem with a new front facing camera and sensor off of ebay. It took less than 10 minutes to put it in and it works great now. It was $5.99 shipped.
[Sprint Samsung Galaxy S III] Gryncc:
try this

On Samsung devices like i9100 (Galaxy S3) or N7100 (Note II) you can do the following if you have root permissions:eek:n Android Terminal App or adb shell do:Code:$ su $ echo 0 > /sys/class/sensors/proximity_sensor/prox_cal $ echo 1 > /sys/class/sensors/proximity_sensor/prox_calThe 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:Code:$ cat /sys/class/sensors/proximity_sensor/stateThe 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.*

This work on the first try for me try it and c if it help u
[Sprint Samsung Galaxy S III] sea2summit:
I can now stop pulling out my hair...

Worked like a charm! Original values were evidently not properly calibrated, but the above approach reset the values such that the display now switches off (in phone calls) at approximately 8 cm, and following hang up, immediately powers on.

Thank you
[Sprint Samsung Galaxy S III] UltimateByte:
God, i've been looking for that information for dozens of years (felt this way at least).

And i find it the day i put my phone back to stock for an RMA !

I went back to root, and tried those lines in the ROM Toolbox Pro's terminal, it says " can't create /sys/class etc. permission denied", what's wrong please guyz ?? I tried several ways to re root, root checker says "status : rooted, ID : uid=0(root) gid=0(root), SuperUser (can't find), BusyBox : /system/xbin/busybox, Su : /system/xbin/su => maybe that's the issue, am i badly rooted ?

Isn't there a no root solution, a very simple way to calibrate ? While looking for a solution, I heard about Als-Ps calibration, doesn't it exist on the N7100 ?

Any help would be very appreciated.

EDIT : OK, i typed "su" to get the terminal to get the SU request, and typed the command, rebooted the phone : the issue's still there.

I'm a noob to Android Terminal, so i tried putting

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

into it, but it didn't work, then i tried

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

and it didn't work, so i had to remove the first "$" to get it to work

(so it looks like "su $ echo 0 > /sys/class/sensors/proximity_sensor/prox_cal $ echo 1 > /sys/class/sensors/proximity_sensor/prox_cal")

Am I doing something wrong ?
[Sprint Samsung Galaxy S III] julianbl:
Thank you Gryncc!!! it worked for me in im i9500. I did it with ADB Shell... the comands where...

su

echo 1 > /sys/class/sensors/proximity_sensor/prox_cal

the 0 did nothing, so I tried 1 and after reset, the sensor worked again!

Regards,

Julián
[Sprint Samsung Galaxy S III] gdstheking:
can u post a screen shot for commands to be used.

a video will be most appreciable,,
[Sprint Samsung Galaxy S III] Nirak:
This is how it looks like,

2 separate commands, echo 0 = reset, echo 1 = calibrate

For me it worked till i restarted device.

Gonna send it in for repair now.
[Sprint Samsung Galaxy S III] vaghotstuff:
Yes it works on note 2 even.but how to stop it going away after restart any thing permanent? ??
[Sprint Samsung Galaxy S III] Dildozebub:
I am having the same problem as everyone else in this thread. I have tried the shell commands, but saw no success. I recently just flashed to Carbon over from PAC Rom and thought maybe it was an issue with the rom install. Went back to stock, without root, to no avail. I even replaced the front facing camera and proximity sensor on my phone (I had $10 and free 2 day shipping from Amazon).

It really sucks because I can't use any touch tone dialing services like for my bank or even activating my GVoice account on my phone. What else is there to do?

Edit: Wow... Literally minutes after I posted this I decided to tear my phone down again to see if it was an error on my part, and lo and behold it was. There was a tiny piece of what looked like a paper towel covering the opening for the sensor. /facepalm
[Sprint Samsung Galaxy S III] ciko84:
Hey guys, same problem here :/ thx for " echo 1 > /sys/class/sensors/proximity_sensor/prox_cal " but i am waiting a permanent way to fix this too :)