yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] SHABBYLEA:
Think the longest I've left it is about 15 mins...

Edit:

Finally... Got a boot from the latest update... Happy bunny...?
[Nokia X] lukino563:
Hey guys,

I made fix for pacman rom for Nokia X, it is tested on my Nokia X and its works :)

Now you can enjoy this rom ;)

This fix mount your internal and external SD Card but in USB connection are few bugs:

1. IN MTP: displayed only SDCARD, internal sdcard is not shown

2. IN PTP: nothing displayed

3. IN UMS: not work

In this installation is flashed latest NULL kernel with modified mount points :)

Requirements:

1, rooted phone

2, installed pacman rom of course :)

3, remounted adb as root or simply booted in TWRP or Philz recovery.

Installation:

1, download NX-PAC-FIX-V2..zip or mounter.zip - link in description

2, unpack zip

3, run NX-PAC-FIX.exe or install.bat or install.sh (LINUX) - you must have your Nokia X turned on and allowed USB debugging OR booted in TWRP or Philz recovery

4, wait for reboot in bootloader - it will flash modified kernel

5, wait for reboot

6, enjoy

CHANGELOG

20141202

- added support for linux - install.sh - you must have installed adb and fastboot

- added mounter.zip for people who dont have a Windows but other systems

- idiotproof protection - just download NX-PAC-FIX-V2.zip and follow instructions :)

INSTALLING ADB AND FASTBOOT ON LINUX

apt-get update
apt-get install android-tools-adb android-tools-fastboot
[Nokia X] sufoalmighty:
Now Internal doesn't work anymore! Thanks though
[Nokia X] lukino563:
It work,the installer flash kernel, you probably not followed tutorial carefully,

you must have remounted phone in adb mode as ROOT to flash the binary to your phone :D

its mounted, but in Settings - Storage not showing capacity, dude ;)
[Nokia X] AssoDiPicche:
It might work on L7 II ? I ported this ROM ...
[Nokia X] lukino563:
sorry, its not working on L7,

this fix is created to be suitable for Nokia X
[Nokia X] AssoDiPicche:
Can you create a port please??
[Nokia X] rangeoshun:
Please, could you share the old zip? As I have OSX running, cannot run .exe files, but can translate the .bat commands in terminal! :)

Thank you!
[Nokia X] sufoalmighty:
you can flash cm11's boot.img in bootloader!
[Nokia X] rangeoshun:
Oh! Thank you very much Sir! :)
[Nokia X] rangeoshun:
Well, that has not solved the issueby itself! MTP mode does not work by flashing the boot.img from CM11-20140828.

What might I have screwed up, or any other suggestions?

Thank you guys!
[Nokia X] sufoalmighty:
it does buddy! btw here's the previous attachment
[Nokia X] lukino563:
This is latest NULL kernel, not CM11s

I dont know what do the old kernel from CM11

Its better to use modified PAC kernel :)
[Nokia X] rangeoshun:
Thank you all, the IMG in mounter.zip worked as advertised! :) The CM11 boot.img did not work for me.
[Nokia X] Burnmode:
Lukino563

You can add F2FS support to this kernel?

I use PAC-MAN with F2FS and i can't fix internal storage.
[Nokia X] 09fp09:
I flashed the Luz Kernel V5 sd card is detected but internal storage is not. I even couldn't find the gapps zip the one which I have does not have google account manager pls help
[Verizon Samsung Galaxy S III] bcook0407:
I bought a Samsung Galaxy S3 (SCH-I535) Verizon on Ebay. My service has been with T-Mobile for about 10 years so I don't want to switch carriers. I have unlocked the phone and am running a T-Mobile SIM card. I have text, talk, and limited data (Edge). Still have the stock ROM and stock recovery. The phone is rooted and running 4.4.2 Kit Kat. The bootloader is still locked and I have installed and ran quite a number of apps trying to unlock it. I read where Safestrap 3.71 would work but when I install it and boot to recovery, I still have stock Verizon recovery. It is loaded with bloatware and I would really like to install a custom ROM that is written specifically for T-Mobile.

Is there any way to downgrade this phone to Jelly Bean and get it completely unlocked with a custom recovery and rom? Preferably using a form of d2tmo?
[Verizon Samsung Galaxy S III] ShapesBlue:
Since you have a d2vzw you cannot run a d2tmo rom on a verizon phone. You can however run a d2lte rom on any S3 LTE variant. If you want to hard brick your phone you can run a tmo rom however I wouldn't ever recommend that

From my CM11 S3
[Verizon Samsung Galaxy S III] landshark68:
Also, you cannot downgrade to jelly bean and you cannot unlock the bootloader.
[Verizon Samsung Galaxy S III] ShapesBlue:
I'm normally pretty good about remembering the bootloader thing. Must of been daydreaming that time, thanks man

From my CM11 S3
[Verizon HTC One (M8)] skcitzo:
i had woke up this morning grabbed my phone and it was stuck in a boot loop on the splash screen i have erased and reformatted the recovery partition back to stock re-installed the cwm recovery and still cant access recovery or get it to boot

ps when i get it to try to boot to recovery it jumps back to the hboot i cant factory reset or anything

anybody please help
[Verizon HTC One (M8)] xsteven77x:
Sounds like you flashed the wrong partition. Might be time to run an RUU.
[Verizon HTC One (M8)] skcitzo:
idk i already ruu'ed it it will not let me boot to recovery still
[Verizon HTC One (M8)] dottat:
What is the name of the recovery you are flashing and trying to enter?
[Verizon HTC One (M8)] skcitzo:
the ruuM8_TWRP_2_7.zip
[Verizon HTC One (M8)] dottat:
And it showed it successfully flashed?
[Verizon HTC One (M8)] skcitzo:
got it

its right here this is the right RUU file it was kinda hidden in the forums so here's dottat's thread thanx for the help u guys
[Verizon HTC One (M8)] xsteven77x:
No problem!!
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] Jcossack88:
Hello all!

Since there are so many versions of the Note 4, I was wondering if we need to flash a carrier specific ROM or if we can flash any ROM to the Sprint one? For example, if CM 12 comes out for the T-Mobile variant are we still able to flash it to the Sprint one, and vice versa? Thanks for your time. I tried looking for a similar thread and couldn't find one, so i'm sorry if this is a duplicate. If so please link the correct thread and I'll remove this one. Thanks again.

-Joe
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] dschachm:
You havw to flash sprint versions. Unless they build cm to be universal which they haven't yet. Each ROM is carrier specific for the radios.
[One (M7) Q&A, Help & Troubleshooting] aidendudewow:
Here's what my bootloader says:

*** TAMPERED ***

*** UNLOCKED ***

M7_WLV PVT SHIP S-ON RH

HBOOT-1.54 0000

Radio-1.12.42.1104

OpenDSP-v3.1.120.274.0617

OS-1.10.605.15

eMMC-boot 2048

Nov 8 2013, 00:54:21.23263

The other day I tried flashing a Rom in TWRP and it failed mid-way saying that it couldn't mount the System Partition (that's from my memory, I don't remember the exact message). I looked it up and someone said it may be a problem with my recovery, so after painstakingly booting up a Windows 7 Virtual Machine (I'm running Windows 8.1), I finally flashed Philz CWM. However, the same dumb error happened. Since the ROM failed halfway, I can't get into Android. I've tried factory resetting obviously, but that didn't work. My next thought was to flash an RUU, but since my device is S-ON I cannot. I then tried pushing REVONE (which appeared to be the only one you don't need a ROM to do), but I kept getting errors when Preparing it to S-OFF (I'm assuming because there's no OS?).

So long story short, I can't Flash Roms because my system partition isn't mountable, I can't flash an RUU because I'm not S-OFF and I can't S-OFF because I can't boot into Android.

If anyone has any idea on how to save my phone, get S-OFF, or fix the system partition please help!

Thanks in advanced.
[One (M7) Q&A, Help & Troubleshooting] clsA:
well your phone was s-off at some point because you can't unlock the bootloader otherwise. why is it back to s-on ?

you'll have to try and format data in twrp and sideload a rom to the phone with adb
[One (M7) Q&A, Help & Troubleshooting] aidendudewow:
I'm actually not sure... I ordered the phone off of Ebay rooted and it was S-ON (the device was running CM 10 when I ordered it around a year ago.) I'll flash TWRP and format, and hopefully that will do the trick. Sideloading on CWM doesn't work at the moment. Thanks
[One (M7) Q&A, Help & Troubleshooting] aidendudewow:
I wiped all of the data in TWRP and tried sideloading but got an error. I then tried pushing the zip onto it and got another error (some protocol errors or something), but then after restarting and trying like 10 different times I finally got it to push the zip, and then after like 10 more tries I got it to install. Phew. Thanks for the help :)
[Nexus 6 Q&A, Help & Troubleshooting] altusanimus:
Anytime I make a phone call my phone locks. I know phones typically go black when it's at your ear, but when I pull away, it won't wake up/unlock. The only time it unlocks is at the end of the call. I set it up so that the power button will end my calls but that doesn't really fix my problem. If I have to use the dial pad during the call, I can't.

I read that the proximity sensor might be blocked by a phone case. I removed mine and it's still not working. Any idea what it can be?
[Nexus 6 Q&A, Help & Troubleshooting] jj14:
Do you have a screen protector? If so, remove it and try again.
[Nexus 6 Q&A, Help & Troubleshooting] Loaded1001:
I am something similar happening, when I remove the phone from my ear after a call I cannot end the call because the phone is locked and I have to unlock it with a pattern before I can end the call or wait for the caller to hang up.

Interestingly I also have exactly the same issue as I had with the LG G3 as well, I take a photo and, if I do not have WiFi, the Nexus 6 turns off, it does it every single time - it's fine if I put it into airplane mode though. As this was the same thing that happened on my LG G3 and no one else is reporting this on Nexus 6, I am assuming it must be an app I am installing ?

Is that possible ?

Simon.
[Nexus 6 Q&A, Help & Troubleshooting] Spectre Nine:
I have the same problem, it's really annoying. My phone won't wake when I take it away from my head and it doesn't respond to the power button until the other person hangs up.

Hopefully it'll be fixed with an update.
[Nexus 6 Q&A, Help & Troubleshooting] Trumps:
I am having the same problem. Brand new Nexus 6 that's only a few hours old.
[Nexus 6 Q&A, Help & Troubleshooting] Spectre Nine:
I got rid of my screen protector and it works way better now. Worth a try if you are using one.

Sent from my Nexus 6
[Nexus 6 Q&A, Help & Troubleshooting] zephiK:
If you're using dt2w/s2w/s2s, see http://xdaforums.com/nexus-6/themes-apps/app-s2w-phone-call-disabler-t3018512
[Nexus 6 Q&A, Help & Troubleshooting] ducky06:
I just now am having this issue too. Here's another thread with same type of thing I posted in: http://androidforums.com/threads/black-screen-after-answer-call-on-nexus-4.671499/page-2

Long story short since I already related my post there, I haven't had this problem on lollipop 5.0.1, now after sideloading 5.1, I have this issue. Screen protector is on, but never was issue before. Now all the sudden it's an issue. I feel like it has to be a software issue. Guess i'll need to test few more times before taking off or cutting screen protector; will update with more news.
[Nexus 6 Q&A, Help & Troubleshooting] geebee1932:
Same issue for me. Never had this issue before the update to 5.1. Wonder if I can go back. I have had the phone since early December.

A little testing. Holding the phone away from my face, the screen immediately blanks when a phone number is dialed. Tried rebooting - no help. May try a factory reset.

Very annoying!
[Nexus 6 Q&A, Help & Troubleshooting] A2CKilla:
Definitely is the screen protector screwing with the senors like everyone is saying and you guys are simply ignoring. I had the same issues off and on back on 5.0, 5.0.1 and on 5.1, but on 5.1 it was permanent. As soon as I took the protector off, everything worked as normal.
[Nexus 6 Q&A, Help & Troubleshooting] geebee1932:
As a brief work around - you can go settings - accessibility - select power button ends call. Works for me till I decide what to do. I have a screen protector on and yep it's covering the prox sensors. Once removed it works as normal. Need to find a new protector that does not cover.
[Nexus 6 Q&A, Help & Troubleshooting] GMoGoody:
Rooted, stock, with screen protector.

Was working fine in 5.0.1 now in 5.1 I have two sensor issues

1) Ambient display does not work at all. When I pick up the device or when I receive a notification sitting on a table.

2) When I receive a call the phone goes completely black. The screen will not turn back on until the call ends.

I do not want to remove the screen protector until I know for sure that is what is causing this.

Sent from my Nexus 6
[Nexus 6 Q&A, Help & Troubleshooting] A2CKilla:
GMoGoody....read bold and listen....
[Nexus 6 Q&A, Help & Troubleshooting] GMoGoody:
A2CKilla. Much thanks. I did read, but it was odd it went from 0% to 100% failure rate after the sw update. I work embedded sw and that is very uncommon for a sensor. I wanted to make sure since I just flashed this morning.

I cut down the protector and everything is good.

Sent from my Nexus 6
[Nexus 6 Q&A, Help & Troubleshooting] ducky06:
*****UPDATE*****

Well A2CKilla, we all just wanted to avoid the inevitable and hope it was a software issue we could just "fix" instead of being a $10, god forbid more, for a screen protector. Always try the more simpler things first than to destroy others first (which I accidentally did btw with my amazing tempered glass, now I must find one that doesn't block the sensor. In my professional opinion, if a sensor worked while having a protector over it on a previous android version, why in the actual F*** would it not work on the newer ones, UNLESS they increased/decreased sensitivity on the code somehow? Well that was my first line of thought anyway.

Also tl;dr PROBLEM WAS INDEED SOLVED BY TAKING OFF TEMPERED GLASS (that previously wasn't an issue at all) AND NOW ALL IS NORMAL.

ps. sensor is literally right next to the top speaker grill on the left side. Best to find a protector that doesn't block that.
[Nexus 6 Q&A, Help & Troubleshooting] A2CKilla:
I really wasn't trying to sound rude at all with what I said, but seriously, there's many a thread about this issue way before 5.1 even came out, and every single time the screen protector was brought up to be the issue, but everyone had to try to find 101 ways for it to not be that, granted my tempered glass protector was less than $5 and I've already found one with the proper cut out for again, less than $5 so I was fine with discarding it, but for so many people to really try and deny something that was the clearly the problem really was sad for a moment. Once again, not trying to sound rude at all but this wasn't the first rodeo about this issue
[Nexus 6 Q&A, Help & Troubleshooting] jongie123:
Wow I never had an issue on 5.0 or 5.0.1 with my tempered glass screen protector. After spending all day thinking it was a software bug and reverting back and trying multiple sources for stock images and ota for 5.1 I decided to remove the screen protector and it worked! Cant believe how 5.1 made the proximity sensor sooo sensitive.
[Nexus 6 Q&A, Help & Troubleshooting] ducky06:
Hey can you link me where you bought it with proper cut outs for sensors? And to clarify its tempered glass I'm after. Thanks :)
[Nexus 6 Q&A, Help & Troubleshooting] thacounty:
This is not acceptable behavior for the device. Mine worked fine, 0 issues before update. Now ambient display is broken and in call the screen goes black. This should be a non issue. My other phone has the sensor covered with a glass protector and it's not a problem at all. This can be fixed, since it was working before. Taking off the protector is not an option for me since I don't have a replacement right now, and should only be a temporary fix at most.
[Nexus 6 Q&A, Help & Troubleshooting] A2CKilla:
http://www.ebay.com/itm/311297199450?_trksid=p2057872.m2749.l2649&ssPageName=STRK:MEBIDX:IT

---------- Post added at 10:09 PM ---------- Previous post was at 10:02 PM ----------

so it's not acceptable for a device to not work properly with something it was never designed nor intended to have? and maybe you were a lucky one because there were many people having this issue and I also stated that it was an off and on issue for me until it was permanent after the 5.1 update. Also, that's another phone, not the nexus, every phone has different settings for their sensors. And technically speaking it is an option for you to take it off, are you forgetting that your screen is gorilla glass???, a type of glass they developed to be scratch resistant, outside of some dust here and there, I've notice no difference having taken mine off until the new one gets here
[Nexus 6 Q&A, Help & Troubleshooting] thacounty:
That is correct. If a device manufacturer says that they don't expect consumers to use screen protectors then they are lying to themselves and everyone else. I had the problem after install of the protector but a reboot fixed it. Guess I was lucky. I would've been more vocal had I known it didn't go away for users.

Ok, that's true, different device, but this is the very first phone I've ever had that had proximity issues with screen protectors on. That's just silly.

No it is not. It may be for you, and that's great, but my phone is cased and screen protected until I sell it. I need to recoup some of the $600 I spent on this when I buy the next nexus. No, I'm aware that the nexus is gorilla glass, but thanks for the update. I want to remind you that it is not scratch proof. I've seen them scratched. You turn them in the right light and they look really bad, but not if you use an sp ;)

I think that maybe you thought I was saying the device is unusable. That's not the case. I can workaround with the power to end call setting, but that doesn't mean I don't want a fix and I think it's worth trying to find. I would guess that at least 50% of the nexus 6s here are screen protected.
[Nexus 6 Q&A, Help & Troubleshooting] tyrnight:
What about using prompts!while in a call?

I have a nexus 6 with a tempered glass protector. I'm using the power button work around, but what about automated systems I call into? I can't bring up the dial pad. And I really don't want to waste my screen protection over this simple change that was made in 5.1...... A fix would definitely be nice.
[Nexus 6 Q&A, Help & Troubleshooting] swamp2:
Same issue here. Stock 5.0 ROM, T-mobile, rooted. Screen goes black via proximity sensor during call but will not come back on when moved away from face. I have NO screen protector!

I had similar issues on my prior Droid DNA that was corrected with an app from Play Store. Preliminary testing on my current Nexus 6 has shown that app "Proximity Fix" is fixing this issue for me.

Update: Sorry false positive. This app is not fixing this issue for me CONSISTENTLY.

Update: The power button to hang up option doesn't fix the issue for me either.

Wow this is a painful problem...
[Nexus 6 Q&A, Help & Troubleshooting] xxsanioutlawxx:
It definitely is. I tried posting a few places and people just skip over them haha. I ordered a new glass protector where there's a cutout for the sensors and I've never had the problem since.
[Nexus 6 Q&A, Help & Troubleshooting] xxsanioutlawxx:
Here's the updated/modified tempered glass protector from xtremeguard. They have a sale going on where you can get two protectors for $9. Code is: Spring90
[Nexus 6 Q&A, Help & Troubleshooting] smatterchu:
New phone no screen protector

I am having this issue with a brand new Nexus 6 64 GB with NO screen protector. It was happening out of the box. Happens even immediately after force closing ALL apps. This needs to be fixed with an update in my opinion.
[Nexus 6 Q&A, Help & Troubleshooting] an0m13:
I'm having the same issue on my Nexus 6 running 6.0, I don't have a screen protector or case. This issue happens on both the stock dialer and hangouts dialer. Also the power button won't turn the screen back on until the other person hangs up.
[Nexus 6 Q&A, Help & Troubleshooting] gujjy:
Solution for 5.1 and higher

Go to setting >accessibility>power button ends call and check it. Then restart the phone. Works like charm after that
[Nexus 6 Q&A, Help & Troubleshooting] pdxcire:
Thank you [MENTION=5646241]gujjy[/MENTION] . Don't know why that was necessary but it DID work beautifully. Only tested short calls but even if screen stays off after away from ear on longer calls at least I can hang up. Only noticed this issue on longer calls +20 minutes, in past. Frustration removed.

LOL. Can't believe this didn't cross my mind. Haumph!? [emoji6]
[Nexus 6 Q&A, Help & Troubleshooting] pdxcire:
Had to turn this off. Longer call resulted in unprompted hang ups ~1 minute into call. Odd. Was worth a shot. Prior test calls were short, to IVR not actual person.
[Nexus 6 Q&A, Help & Troubleshooting] LukeM1283:
I have the exact same problem!
[Sprint LG G3] clark44:
Hello everyone. I have gotton permission from @jholtom to re-open this thread and start building it on my own (we are never alone :D). He will still be here and will still be helping. All credit goes to him, he got this off the ground for the LS990. I'm just here to take over the saddle. Enjoy!

[ROM][Q&A] CM12 Questions and General Thread

Yup. It's finally here. CM12.1 with basically everything* working.

*Working:

Pretty much everything:

WiFi

3G/LTE

Camera (back and front-facing and LED flash,) camcorder works in 1080p, no 4k yet

Sound

Screen (duh)

Proximity, Accelerometer, Gyroscope

GPS

Partial Bluetooth support (FitBit and some other devices not working yet)

SDCard read/write

SMS/MMS

NFC - Yes NFC works now, but needs testing

*Not working:

EVDO Rev. A has some issues with out a patch (its cooked into the unofficial rom already)

CM-12.1 reports of DATA not working, but its working for some Its mostly fixed in 4/23 build, please use ZV8 modem

Installation Instructions:

*NOTE*: You must be Bump'd for this to work. This requires flashing via custom recovery

1. Download this and 5.1 GApps (recommended PA GApps Here. You are going to need to use the Lollipop ones, this is 5.1)

2. Put both on Internal Storage

3. Reboot into recovery

4. BACKUP CURRENT ROM

5. Factory Reset/Wipe if not on CM12, you CAN dirty flash cm12.1 over cm12

6. Flash CM12.1 (no need to wipe System)

7. Flash GApps 5.1

(Optional: flash SuperSU Lollipop Edition for Root. Download here)

8. Reboot

9. wait.. wait ..wait

10. Profit

To get root/SU, enable Developer Options and change "Root Access" options.

Downloads

Official CM Nightly Builds

HERE

Latest Unofficial Builds: 7/21/15

Hrubak's Builds Download from MEGA

Mirror:

Hrubak's Builds Download from AFH

K0nane Server Links:

Repositories are at github.com/jholtom

Kernel sources are at github.com/invisiblek/android_kernel_lge_g3

Using Cyanogenmod Repositories

@invisiblek was pretty awesome in getting this going, much more credit goes to him than me, he really had the base for this, and now I just fix crap for the ls990.

@Berzerker7 @jholtom, shoutout because I stole your thread body.

XDA:DevDB Information

CyanogenMOD 12.1, ROM for the Sprint LG G3

Contributors

clark44, Hrubak, RandomPooka, invisiblek, jholtom, Shelnutt2

Source Code: https://github.com/cyanogenmod

ROM OS Version: 5.1.x Lollipop

ROM Kernel: Linux 3.4.x

Based On: CyanogenMod

Version Information

Status: Nightly

Beta Release Date: 2015-06-23

Created 2014-11-30

Last Updated 2015-07-21
[Sprint LG G3] scottspa74:
So awesome to see this! Thanks mass for taking over. Encouraging.
[Sprint LG G3] crazycori:
Good work, unfortunately I cannot get any data or network connection. WiFi works great however
[Sprint LG G3] PlagaDeRock:
It looks like Bluetooth is struck out so I'm not sure if it's working here or not but if it isn't RandomPooka has the fix for it.
[Sprint LG G3] Cleanser2012:
YYYYEEEESSSSS!!! My pants are soaked
[Sprint LG G3] randyrampage609:
Welcome back good to see you taking the reins
[Sprint LG G3] kangta05:
Not data connection only wifi

Same here