yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
When using any ROM, stock or custom, on all of my Android phones, the screen always went black when I placed the phone next to my ear. When I removed the phone from my ear, the screen came back on and I could end the call by clicking a button on the screen.

With a stock ROM, does the screen go off when you place the phonex to your ear and then come back on when you move it away from your ear?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] riche1:
as soon as you make a call the screen goes black and does not come back on, unless the call ends. I can not end the call either unless I press the lock screen button, slide down the notification bar and press hang-up. This is only on all ASOP roms.. This is my girlfriend's phone, mine works fine. I'm on Sprint though. To make sure everything works only on TW, I put a custom TW rom on her phone. The screen turns black on calls, but I can go to the dialer settings and fix this with the leave screen on function. I don't think it's the proximity sensor, unless the sensor works different between ASOP and TW roms.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
Just to confirm, the screen goes black when you place the phone next to your ear and comes back on when you move it away from your ear on a stock TW ROM, correct? If the phone exhibits this behaviour on a stock ROM, the proximity is working. If it does not, I would still conclude the proximity sensor is not working. I have loaded custom ROMs onto 3 different S3 phones and the screens alway came back on when I moved the phone away from my ear without having to touch the power button.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] riche1:
This is correct. It works fine on TW roms , but I have to turn on some function in the dialer settings for it to work after the initial install. My girlfriend said her sister's phone did the same thing ( no root ) and she had to go to the dialer settings to get things back to normal. I believe she said this happened after the ATT 4.3 stock update.

If I use any ASOP rom the screen will go black as soon as a call is made by pushing the call button. The only way to get it to come back on is to get the lock screen up and pull the notification bar down to hang up. She does not care whether she uses a ASOP or TW, but I'm baffled by the issue with ASOP roms since mine works great, but I'm with Sprint. The proximity sensor is working fine in my opinion because all of the TW motion features work flawless. I wanted to get her on an ASOP rom because the battery life is so much better. Sorry for the late reply. Thanks for helping!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
Without making any changes to the stock TW ROM dialer settings, does the screen go black when you place the phone next to your ear and come back on when you move it away from your ear?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] riche1:
If I put a clean install of a TW rom it does not work either. I have to change the dialer settings. My girlfriend told me this happened as soon as she installed the 4.3 update way before I rooted the phone.It happened to her sister too. I did not know about the issue until I rooted. . I doubt it's the recovery I'm using. I had problems installing CM with TeamWin Recovery. I had to use Philz. Like I said, I don't mind keeping her on TW roms and she doesn't care either. It would be great to find out what is causing this. It's got to be something with the proximity sensor detection, but the proximity sensor does work otherwise the TW gestures and features would not right ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
Was the clean install done using a stock 4.3 TW ROM? I didn't know there was a problem with the 4.3 update that affected the proximity sensor.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] riche1:
Originally stock 4.3 updated through ATT is when she started to experience the problems. She fixed by going to dialer/settings leave screen on during calls. I rooted the phone not knowing this had been an issue before. After making sure the stock 4.3 was rooted I installed cyanogenmod and thus the issue was back. There was no way to fix it another than to install a TW rom and go through the dialer/settings. If that settings is not checked then the phone will go black as soon as a call is made. I can't find away around it. I keep forgetting to come back on check here for replies.. sorry for the delayed response. Thanks for the help

Richard
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
The behaviour exhibited by the phone after the update is not right. If it was a software issue, it would have been solved by flashing a custom ROM.

I have flash a few custom ROM and non-custom ROMs onto the d2can (i747m) and none of the phones behaved the way yours does.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] riche1:
she said it was not a problem until the phone was updated to 4.3 through ATT software update. This was way before I rooted the phone. The same thing started with her sister's phone. So.. I'm stumped as to what the problem could be. I rooted it because I thought CM11 might fix the issue and that was not the case. I don't know how I can go about fixing it. I don't want to take a chance in bricking the phone.
[One (M8) Q&A, Help & Troubleshooting] Mazellat:
Is there anybody who can share with me HTC One M8 stock songs, I deleted them wrongly. Please upload thema site and share with me, thanks a lot..
[Nexus 4 Q&A, Help & Troubleshooting] TheKnux:
I somewhat read what the difference between the two were, but I don't quite understand it completely. I was wondering (based on user preference) which is better.

I was using a ROM that was Non-CAF and now I'm using one that is, and I don't notice a difference really. I was wondering if someone could help me understand better.
[Nexus 4 Q&A, Help & Troubleshooting] parkourz:
+1
[Nexus 4 Q&A, Help & Troubleshooting] Targaeryan:
Caf relates to code aurora forum (Google it).. Its where Qualcomm updates its stuff regularly. While aosp is googles kernel branch. Caf has more updates and optimisations for Qualcomm chipsets. The difference... I can't say there is much since our phones are already quite powerful to handle most things thrown at it.. But again, as I mentioned its optimisations and etc, so on paper better performance, battery and what not. :)
[Nexus 4 Q&A, Help & Troubleshooting] graafschap101:
CodeAurora (CAF) - These are Qualcomm's reference sources for their platform. This is what they provide to OEMs, and what nearly all OEMs base their software off of. As a result - nearly all non-Nexus devices are running kernels/display HALs/etc. that are derived from a CAF baseline.

Google's software baseline, or AOSP - Usually when Google starts working on a new Android version, they'll fork from CAF at the beginning. Very often Google will be adding "new" features specific to the new Android version, while Qualcomm will continue with performance enhancements and bugfixes against the "old" baseline.

So when a new Android revision comes out, you have two baselines: CAF which is usually "ahead" in performance but "behind" in features, and AOSP which is the opposite.
[Nexus 4 Q&A, Help & Troubleshooting] flanker22:
from what i've noticed CAF is better, i get less stuttering this is the sort of thing that optimizations usually improves on.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] djkaozz:
OK first off I going to express my deepest apologies for starting a thread with an issue that has probably been answered 100 times... My problem is that I have tried every possible phrase that I know for search term pertaining to my particular issue and I am still stuck. SO I will be as details as possible and I hope and pray that at LEAST if I get kicked for starting this and the thread being shutdown, that someone will have posted "heres the link numb nuts be more careful next time".

OK so on with my issue. I have a Rogers Samsung Galaxy S4 I337M on 4.3, I tried to use chainfire's latest cf-Autoroot to root my phone and it just failed. Here is the log:

<ID:0/004> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> CF-Auto-Root-jfltecan-jfltevl-sghi337m.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/004> Odin v.3 engine (ID:4)..

<ID:0/004> File analysis..

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

<ID:0/004> Get PIT for mapping..

<ID:0/004> There is no PIT partition.

<OSM> All threads completed. (succeed 0 / failed 1)

<ID:0/004> Removed!!

<ID:0/004> Added!!

<ID:0/004> Odin v.3 engine (ID:4)..

<ID:0/004> File analysis..

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

<ID:0/004> Set PIT file..

<ID:0/004> DO NOT TURN OFF TARGET!!

<ID:0/004> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

<ID:0/004> Removed!!

<ID:0/004> Added!!

As you can see when odin could not find the PIT I downloaded one and retried.

Anyway now I'm stuck on this:

and the top left may be important so here is the clearest shot of that:

Now I have tried to flash stock firmware that I downloaded from sammobile AND samsung update and no matter how many times I try to flash its the same thing over and over again (log):

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> I337MVLUEMK6_I337MOYAEMK6_I337MVLUEMK6_HOME.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/004> Added!!

<ID:0/004> Odin v.3 engine (ID:4)..

<ID:0/004> File analysis..

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

<ID:0/004> Set PIT file..

<ID:0/004> DO NOT TURN OFF TARGET!!

<ID:0/004> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

<ID:0/004> Removed!!

<ID:0/004> Added!!

I then thought about trying Kies. First problem, Emergency firmware did not list my device. Then I tried firmware upgrade and initialize and even though the start button wouldn't show unless I plugged the phone in as download mode, once the firmware was finished downloading and ready to flash it would give me an error saying it couldn't not detect my device.

I am not sure is this is EVERYTHING I could have tried but to MY knowledge it is. Please help :(

And my deepest gratitude to anyway and all who point me to the right direction. I hope I have been as detailed as I possibly can be.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] mattdm:
Point you to the right direction, huh? How about the Q&A, Help & Troubleshooting subforum? Posting questions like this in the development subforum is a no-no.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] djkaozz:
This is a start, my apologies AND a big thank you!
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Buddyjohn:
i encountered this before. although i cannot remember how i fixed it. few things to try though.

option A: download a stock rom from sammobile it is pretty straight forward on the site to select the correct stock rom. be careful when selecting though. make sure you get the correct version to match the bootloader. ex download the 4.4.2 stock rom from rogers if you had 4.4.2. the rom from sammobile is odin flash only. so put it in the pda and make sure your phone is in download mode if you can get to it

option B: if you cant get to download mode then you will have to try the firmware emergency recovery option on the actual samsung keis program. I cannot remember the steps for this but a google search should give directions

if either of these work you will be brought back to square one where you can start the root process over again. this time try a different rooting method. just incase.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] djkaozz:
the problem is i did this and no matter what i am getting the results that are posted in the log above.

any other suggestions out there?

i appreciate the responses so far. thank you
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Buddyjohn:
Did you try the option that doesn't involve Odin? Also try changing USB cables
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Adizzzle:
Use a different computer?
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] djkaozz:
thats another option i have tried to no success. it seems that even with the pit file its failing but no reason as to why
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] djkaozz:
FIXED!!

wow.... i fixed it... the solution is SO STUPID that embarrassed to say it.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Winston.huang:
Help

Do you remember what you did? Because i have the same problem
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] superryo:
i have the same problem. please do share!
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] kopir:
Had the same problem. I was finally able to complete the update only after I inserted a SIM card and rebooted my computer.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] JungleManJack:
Are you for real? I have the same Canadian model as you, EXACT same problem and you find a solution and don't post it... Thanks bro, RIP Harambe
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] audit13:
The problem was probably fixed by flashing a stock rom via Odin, factory wipe, and set up the rom.
[AT&T HTC One (M8)] chizler:
I just got my phone two weeks ago and love it, coming from a Verizon note 2.

I have been reading a lot about unlocking the HTC M8, and it's seems completely different animal compared to unlocking my note 2 was, so I just want to read and learn a lot before I start messing with this phone.

I had my note 2 down to a science flashing and changing stuff around on it. With the HTC it looks like there is a lot of adb stuff that I'm not to familiar with. I have been reading about hansoons tool kit and it looks pretty straightforward, so any more advice you guys could give me would be great.

Thanks in advance.
[AT&T HTC One (M8)] smknutson:
Adb is actually pretty easy. There is a video on YouTube from Sakitech that walks you through it

How to Root your HTC One M8 - Full Guide: http://youtu.be/WuHFcGvUjwA

Another thing I can tell you, is it is much easier to use a Windows7 pc to do this than Win8

But once you go down this path, it's like the old days of ROMs and kernels and custom recoveries. Very exciting.

Sent from my HTC One_M8
[AT&T HTC One (M8)] chizler:
The only pc I have still runs Vista haha.

I'm just nervous I guess because the whole root, unlock and recovery is a little different than I am use too and I'm out of my comfort zone.

I am a crack flasher its like a drug trying different roms and tweaking my phone.

Thanks for the video.
[AT&T HTC One (M8)] an0ther:
It's way easier than Samsung once you are used to adb and fastboot. Don't use a toolkit because you won't learn anything.
[AT&T HTC One (M8)] chizler:
I've watched the videos that smknutson post and it looks pretty straightforward, just got to get the guts up to tear in to my new phone.
[AT&T HTC One (M8)] an0ther:
Message me if you have any questions.
[AT&T HTC One (M8)] chizler:
I will thanks.
[AT&T HTC One (M8)] an0ther:
Also make sure you soff while you still can. Pretty much makes your phone brick proof.
[AT&T HTC One (M8)] akitten007:
Now I know the basic benefits of S-Off, but how does it make the M8 more brick proof? Just wondering if it's worth it
[AT&T HTC One (M8)] an0ther:
You can flash any ruu. Kinda like odining your note back to stock. Currently if you somehow bricked your partitions there is no stock att firmware file. There is a international file that you could flash to fix partitions. If you didn't have super cid you could not do this. Need soff to get super cid. Plus you can remove the tampered text in bootloader, flash newer firmwares way before at&t releases them, truly convert your phone to any m8 variant, truly relock bootloader with no relocked text.

---------- Post added at 11:16 PM ---------- Previous post was at 11:14 PM ----------

Granted you would have to really try to mess up your partitions.
[AT&T HTC One (M8)] akitten007:
Thanks for the quick response, forgot about RUU's. I was worried coming from the awesome modding community of the S3, but I'm glad to see this device is just as open and has plenty of support. Good thing returned that S5:p
[AT&T HTC One (M8)] supitsronnie:
Is their any way to "S-On" if I need to for some reason? I'm waiting to unlock because I don't want to use HTCDev. I don't know how long I can wait though haha.
[AT&T HTC One (M8)] an0ther:
Yes but it throws a security flag.
[AT&T HTC One (M8)] supitsronnie:
Okay thanks. That is what I'm trying to avoid- if I have a hardware defect I would like to be able to flash stock like it was never unlocked.
[AT&T HTC One (M8)] an0ther:
There is no way to do that atm. Hardware defects are usually covered. HTC doesn't void all warranty. I know one person that broke their screen and they said just make sure bootloader is locked when it gets back to them. I always recommend insurance through carrier.

---------- Post added 30th April 2014 at 12:00 AM ---------- Previous post was 29th April 2014 at 11:58 PM ----------
[AT&T HTC One (M8)] nuwayman:
I too am coming from a note 2. Just like the OP. I'm loving this phone. Had it for 2 weeks now. About to take the plunge soon cause my flashing addiction is getting to me. I guess my question is are the roms from the international m8 be used on this phone as well? Along with the kernels? Sorry for the sounding like a newbie. It's just been years since I've had HTC. The last time was in Windows mobile days.
[AT&T HTC One (M8)] redpoint73:
It should be kept in mind that S-off means all security checks are off. That includes device check. So you have to be careful to only flash mods meant for this device. Accidentally flashing something meant for another device can brick the phone, if for instance it overwrites hboot. Seen it happen on the One X/XL (flashing an ENDEAVORU ROM on an EVITA). But stay in this device forum section, and you will be fine.

With the proper care, I agree that s-off gives more recovery options.

---------- Post added at 12:41 PM ---------- Previous post was at 12:39 PM ----------

You must have had some kind of learning curve with your previous device. Every device can be a bit (or very different) and especially different manufacturers. But just take the time to do the proper reading and understanding, and you will be fine.
[AT&T HTC One (M8)] Phoneguy589:
I'm new to the HTC as well. I had the Motorola Atrix which I unlocked the bootloader via fastboot but still was nervous as anything. I had the S4 and just got this. ADB is my weakness and I've read about the supercid but wasn't sure what the purpose of doing it was off I was rooted and unlocked. Welcome to the M8 .
[AT&T HTC One (M8)] chizler:
Yeah its not been to bad of a learning curve just different, previously all my rooting and unlocking has been with Samsung.

I have already rooted my m8 unlocked and s-offed, just waiting on a stock RUU just to have a another back up just in case.
[AT&T HTC One (M8)] Phoneguy589:
I just s-off'd my wifes phone, removed tampered from both, and removed the red test from splash screens. I little slow trying to make sure I get everything exact but all went smooth. Great support in this forum.
[AT&T HTC One (M8)] jdk2:
Nice.

And slow is not such a bad thing with these $700 phones :D
[G2 Q&A, Help & Troubleshooting] JoInT.il:
Hi, i have d802, rooted, TWRP recovery and stock 4.2.2 rom. Cant turn on NFC function. I just push on, a button became blue(ON), than, after like 2-3 sec it became grey again(OFF). I can turn on direct beam, but it doesn't work too, cant transfer a photo.That's basicly all. Anyone heard smtg like this or know how to fix it? Factory reset allready tried, doesn't help.
[MDA II, XDA II, 2060 General] frr149:
Hi,

I just installed the mp3 path on my xdaII and used the new popup menu to set it as a ringtone. However, it doesn't work: the old ringtone is still selected.

What am I doing wrong?
[Xperia Z2 Tablet Q&A, Help & Troubleshooting] Chefproll:
Hi there !

It seems many Z2s have creaking and touchscreen problems, sometimes developing after some days of use.

In addition, a lot of Z2 Tablets seem to suffer of a warped, bent chassis: Just peek along the sides of the Z2, check if it's bent, curved.

My Z2 had NO creaking and NO touchscreen issues right from the start - but both problems came up after about two days of use, both issues showed up at the same time. And my Z2 is a "banana" Z2, it's chassis is bent, putting the device under constant physical tension.

Maybe there's a connection; let's find out !

---

Please reveal the following:

1) Z2 Tablet model (Wi-Fi/LTE, RAM size, serial number*, date of manufacture - see below)

2) Firmware version

3) Color (maybe different backplanes cause different stress on the chassis)

4) Market (Europe, USA, Asia, etc. - have a look at the box the Z2 came in; there's an information about the country it was made for)

5) Country of manufacture (I guess it's China for all Z2s produced - but you never know...)

6) Days of use

7) Bent ?

8) Touchscreen problems ?

9) Creaking/loose feel at the bezel (especially at the right hand side, in landscape mode) ?

10) Only if you dare: Bubbles emerging from the bezel area (not speakers) if submerging the Z2 ?

* Serial number: You don't need to mention the full number. Just have a look at the sticker on the box, "SN –": Example: 430101690000142

"141" is the serial number.Replace the last two ciphers with an "x". Result: "1XX". If your serial number is "54321", use this: "543XX"

This way, you don't have to reveal your full serial number - but we still get an idea of the production batch number.

Thank you. :)

Date of manufacture (thanks to LitoNi for pointing me to this):

It's here:

This is how it looks like if your Z2 is bent:
[Xperia Z2 Tablet Q&A, Help & Troubleshooting] Chefproll:
1) LTE, 16 GB, 1XX

2) 17.1.A.2.55

3) Black

4) Europe, France (bought at the German Sony online shop, delivered to Germany)

5) China

6) 12 days (problems started at day 2)

7) Bent !

8) Touchscreen problems !

9) Creaking issues !

10) Didn't dare. ;)
[Xperia Z2 Tablet Q&A, Help & Troubleshooting] Skogstoken:
1) Wifi 32 gb, Build week: 14w11

2) 17.1.A.2.36

3) Black

4) Europe, Bought via Sony swedish online shop.

5) China

6) 9 days, had creaking and touch problems from the start.

7) Slighty bent but hardly noticably.

8) Touchscreen problems!

9) Creaking issues!

10) Bubbles coming from chassi when fully submerged, top right corner when in landscape mode.
[Xperia Z2 Tablet Q&A, Help & Troubleshooting] hillbicks:
1) SGP511 E1/B Wifi version

2) 17.1.A.2.36

3) black

4) Intended for France, bought in germany

5) China

6) 4 days

7) Nope

8) None so far, the only touchscreen issue I'm facing is that I have to be really accurate when touching the buttons. But the touchscreen itself is responding just fine

9) Nope, feels absolutely solid.

10) Haven't tried that yet.

Hope this helps. :)
[Xperia Z2 Tablet Q&A, Help & Troubleshooting] Crozar:
1) LTE, 16 GB

2) 17.1.A.2.36

3) white

4) comtel. (Imports from Asia, mostly Singapore for quality purposes)

5) China

6) 7 days (problems started 2nd day)

7) not sure if bent.

8) Touchscreen problems sometime

9) Creaking sounds is my only concern

10) http://youtu.be/QW1A0SuaUIQ
[Xperia Z2 Tablet Q&A, Help & Troubleshooting] Chefproll:
Next Z2 just arrived. Again, a "banana", creaking at the left (!) bezel side right out of the box, slightly larger gaps between aluminum and plastic at the side faces than my first Z2, so build quality appears to be even lower. :/

Serial number is 2410, serial of my first Z2 is 142 (funny, same numbers, just reversed) - so there's more than 2000 Z2 produced between first and second device - but still the same problem. :/

Instant return to Sony.

1) LTE, 16 GB, 24XX

2) Didn't check, didn't even start the tablet

3) Black

4) Europe, France (bought at the German Sony online shop, delivered to Germany)

5) China

6) 1 day (bent, creaking right out of the box)

7) Bent !

8) Not checked

9) Creaking issues !

10) Not checked