My NFC worked fine when I was on stock, rooted, and unlocked bootloader. When I "Custom ROM'ed" My NFC didn't work on the custom ROM flashed(CM 10.2 Nightly). But it didn't bother me due to it being a custom ROM and all. But I lgpnst(spelled right?) Back to stock ZVC and the NFC is not working. It makes me switch it on but when I leave the setting then return it turns back off. How can I fix this issue?
Thanks.
SevenGPLuke said:
My NFC worked fine when I was on stock, rooted, and unlocked bootloader. When I "Custom ROM'ed" My NFC didn't work on the custom ROM flashed(CM 10.2 Nightly). But it didn't bother me due to it being a custom ROM and all. But I lgpnst(spelled right?) Back to stock ZVC and the NFC is not working. It makes me switch it on but when I leave the setting then return it turns back off. How can I fix this issue?
Thanks.
Click to expand...
Click to collapse
*bump*
Can anyone help me?
Related
Hey guys
I'm having a problem with my P936. I installed CM 10.1.3 and when I put the phone to charge while powered off, it won't stop "charging" if I unplug the charger. The screen stays on with the battery filling up and I need to take off the battery to completely turn it off. This has happened with other CM 10 versions that I used and it won't happen if it is turned on.
Does anyone know this issue and a way to fix it?
I am a newbie since my first flash was this week, but did you flash the rom correctly? Cleaning the caches and the memory?
Truepeace said:
I am a newbie since my first flash was this week, but did you flash the rom correctly? Cleaning the caches and the memory?
Click to expand...
Click to collapse
Yes I did all of that. The problem has happened with all CM roms that I flash into the phone it is not specific with this version 10.1.3.
Did you try a stock rom?
I am using Avatar ROM with Wind Kernel and charging is working without any issues.
audit13 said:
Did you try a stock rom?
I am using Avatar ROM with Wind Kernel and charging is working without any issues.
Click to expand...
Click to collapse
Stock rom works fine. It only happens with Cyanogenmod with the stock or Wind Kernel.
smash_07 said:
Stock rom works fine. It only happens with Cyanogenmod with the stock or Wind Kernel.
Click to expand...
Click to collapse
Very strange because Avatar is based on CM10.1.
audit13 said:
Very strange because Avatar is based on CM10.1.
Click to expand...
Click to collapse
It maybe a fault in my phone but that also seems very strange since stock roms work fine there is no apparent reason for this to happen with custom roms. If the phone is on then it charges correctly.
Maybe it needs to be re-unbricked? Not sure what else can be done at this point.
Hello,
So I've flashed before Slimbean, but had problems with the "can't connect to camera" problem, so I decided to flash Slimkat 4.4.4 which fixed the camera problem.
New problem now is that i can't get any gps signal. I can turn it on, but no signal. Anyone have a solution to this, or is experiencing the same problem?
Downloaded from here: http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1074-d2att-d2tmo
drakemiller40 said:
Hello,
So I've flashed before Slimbean, but had problems with the "can't connect to camera" problem, so I decided to flash Slimkat 4.4.4 which fixed the camera problem.
New problem now is that i can't get any gps signal. I can turn it on, but no signal. Anyone have a solution to this, or is experiencing the same problem?
Downloaded from here: http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1074-d2att-d2tmo
Click to expand...
Click to collapse
Hi, the link you provided points to build 4. You can find build 9 which is the latest slimkat here http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1183-d2lte
This is the one I have for my Koodo I747M. *note camera seemed a little buggy in some instances, so I installed open camera. Seemed to work a lot better.
I'll give it a try, thanks for the help. Quick question, will this work on my phone model without bricking? I only tried the at&t not the d2lte.
Also can you send me the link for this open camera you were talking about for my device as well?
drakemiller40 said:
I'll give it a try, thanks for the help. Quick question, will this work on my phone model without bricking? I only tried the at&t not the d2lte.
Also can you send me the link for this open camera you were talking about for my device as well?
Click to expand...
Click to collapse
I'd imagine it should be ok, since we have the same phone pretty much I'm on koodo which is pretty much telus without the customer service hehe. for kitkat at the end of development they basically lumped a d2att, d2tmo etc together. (this has reverted for the lollipop builds out there).
The last OTA I got was FOB1, so you may want to go to stock to ota to the latest updates from telus. Just so you have the latest bootloader/firmware. But that's up to you of course.
It's a google play app open source, the slimkat one I had seemed to lockup when switching from front to back camera and from camera to video. https://play.google.com/store/apps/details?id=net.sourceforge.opencamera&hl=en
What are you using to flash them?
serathe said:
I'd imagine it should be ok, since we have the same phone pretty much I'm on koodo which is pretty much telus without the customer service hehe. for kitkat at the end of development they basically lumped a d2att, d2tmo etc together. (this has reverted for the lollipop builds out there).
The last OTA I got was FOB1, so you may want to go to stock to ota to the latest updates from telus. Just so you have the latest bootloader/firmware. But that's up to you of course.
It's a google play app open source, the slimkat one I had seemed to lockup when switching from front to back camera and from camera to video. https://play.google.com/store/apps/details?id=net.sourceforge.opencamera&hl=en
What are you using to flash them?
Click to expand...
Click to collapse
Im not very experienced lol and got lost on:
"The last OTA I got was FOB1, so you may want to go to stock to ota to the latest updates from telus. Just so you have the latest bootloader/firmware. But that's up to you of course. "
I'm using TWRP
Ah, ok I just keep a backup in case anything goes bad flashing roms. If you use TWRP to flash them it only affects the boot image, data and system. So if you have problems you can restore from backup nice and easy.
I'm swapping between a few right now. So far my only uh oh experience was when I tried to upgrade TWRP, no problems with roms. But I use TWRP as well, works great.
Basically the baseband version on our phone, it's the radio and bootloader. Before I had rooted it I had gotten the latest updates by checking for updates. It downloaded and upgraded to FOB1 (Baseband I747MVLUFOB1), then I rooted and played with flashing. Not sure if you made a backup of your original install before trying another rom. But it's not a necessity for slimkat, I don't believe.
serathe said:
Ah, ok I just keep a backup in case anything goes bad flashing roms. If you use TWRP to flash them it only affects the boot image, data and system. So if you have problems you can restore from backup nice and easy.
I'm swapping between a few right now. So far my only uh oh experience was when I tried to upgrade TWRP, no problems with roms. But I use TWRP as well, works great.
Basically the baseband version on our phone, it's the radio and bootloader. Before I had rooted it I had gotten the latest updates by checking for updates. It downloaded and upgraded to FOB1 (Baseband I747MVLUFOB1), then I rooted and played with flashing. Not sure if you made a backup of your original install before trying another rom. But it's not a necessity for slimkat, I don't believe.
Click to expand...
Click to collapse
Yeah I always create a nandroid and backup my IME.
drakemiller40 said:
Hello,
So I've flashed before Slimbean, but had problems with the "can't connect to camera" problem, so I decided to flash Slimkat 4.4.4 which fixed the camera problem.
New problem now is that i can't get any gps signal. I can turn it on, but no signal. Anyone have a solution to this, or is experiencing the same problem?
Downloaded from here: http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1074-d2att-d2tmo
Click to expand...
Click to collapse
First thing to try for GPS problems is taking off the back cover and snugging up all the little screws around the phone. Sometimes they work their way loose and the GPS antenna seems to be the first thing to suffer from it.
If that doesn't cure it you might need to flash a stock or at least stock based ROM and rebuild the nvram. Here's a link that describes how to do that if you need to.
So I took out my age old xperia M(single sim) a couple of days ago and installed cm 12.1 on it. The only issue I'm facing with it is that if I keep the phone on standby for a while the phone completely and silently shuts itself off. When this happens it doesn't turn on with the power key as well so the only way to turn it on after this happens is by removing and re inserting the battery and then pressing the power button. (phone boots normally then)
This problem only appears when the phone is in standby. I could use it 2hrs straight and the phone would keep functioning normally as long as I don't keep it on standby for a long period.
I've tried tons of different cm12.1 roms and factory reset the phone multiple times but the problem is there with every single rom. Haven't tried any rom that isn't based on 12.1 yet.
Strange thing is that this standby dead thing doesn't happen when there is a music app that's playing some song while in standby. Even if the phone is on silent and media volume is 0. So the temporary fix is to keep playing some song and keep media volume at 0. I would be really happy if someone comes up with a permanent solution though. Thanks. Any help would be greatly appreciated
Was the problem present on the stock ROM?
elmkzgirxp said:
Was the problem present on the stock ROM?
Click to expand...
Click to collapse
I have the same problem with CM based roms, went back to stock and it doesn't have this issue, could it be something to do with ambient display/doze?
kurtbvb said:
I have the same problem with CM based roms, went back to stock and it doesn't have this issue, could it be something to do with ambient display/doze?
Click to expand...
Click to collapse
No, I don't think so. Which version did you come from? I would suggest flashing 15.4.A.1.9 first because most custom ROMs use it as base and doesn't offer full compatibility with older versions.
elmkzgirxp said:
Was the problem present on the stock ROM?
Click to expand...
Click to collapse
Nope. My sister had been using this phone on 4.3 since 1yr now. I decided to use it as a secondary media device when she got a new phone. When I first unlocked my bootloader after rooting the device went into bootloop. So had to restore it to stock 4.1 Indian (couldnt find 4.3 indian ftf) using flashtool (took 2 days and tons of researching to get the drivers working). Then I rooted it again and flashed twrp and cm 12.1. Have been facing this problem ever since.
It's driving me crazy now. Might go back to stock if it doesn't get fixed
Edit - also just checked the sim slot isn't working either. Tried multiple 12.1roms but it won't get detected. Didn't realise this before as I'm using this as a media device and don't need sim card working anyway.
RagzyB said:
Nope. My sister had been using this phone on 4.3 since 1yr now. I decided to use it as a secondary media device when she got a new phone. When I first unlocked my bootloader after rooting the device went into bootloop. So had to restore it to stock 4.1 Indian (couldnt find 4.3 indian ftf) using flashtool (took 2 days and tons of researching to get the drivers working). Then I rooted it again and flashed twrp and cm 12.1. Have been facing this problem ever since.
It's driving me crazy now. Might go back to stock if it doesn't get fixed
Edit - also just checked the sim slot isn't working either. Tried multiple 12.1roms but it won't get detected. Didn't realise this before as I'm using this as a media device and don't need sim card working anyway.
Click to expand...
Click to collapse
Do what I said to @kurtbvb too, as it may just be base incompatibility. Flash everything except the TA partition (if present) and wipe /data and /cache.
elmkzgirxp said:
Do what I said to @kurtbvb too, as it may just be base incompatibility. Flash everything except the TA partition (if present) and wipe /data and /cache.
Click to expand...
Click to collapse
So do I flash stock 4.3 using twrp or do I need to flash the ftf file using flashtool ?
RagzyB said:
So do I flash stock 4.3 using twrp or do I need to flash the ftf file using flashtool ?
Click to expand...
Click to collapse
Flashtool. Some files are required which custom recoveries can't flash.
Just flashed the above mentioned ftf file and then rooted the phone, installed twrp and then cm 12.1 based rom. Everything runs perfect now. No random shut downs and Sim card works as well.
Thanks you so so much
It used to work but just noticed today it isn't any more. GPS will still find me, but it won't travel along with me in google maps and none of the satellites lock on using GPS toolbox. It shows 20 or more satellites available but none lock. If I do a search for nearby places it gets it right every time but it won't lock on to any satellites. I am rooted, I tried changing the rom and even loading a fully stock one and it still isn't working. I don't get how some of this stuff will work but I can't get any full lock.
Is this likely a device issue or something that I can fix?
I am also having this issue with my Pixel (non XL). Next weekend I will try and reset the device but I have had this issue for a few months now. I am not sure if it's software or a hardware problem.
JAYNO20 said:
It used to work but just noticed today it isn't any more. GPS will still find me, but it won't travel along with me in google maps and none of the satellites lock on using GPS toolbox. It shows 20 or more satellites available but none lock. If I do a search for nearby places it gets it right every time but it won't lock on to any satellites. I am rooted, I tried changing the rom and even loading a fully stock one and it still isn't working. I don't get how some of this stuff will work but I can't get any full lock.
Is this likely a device issue or something that I can fix?
Click to expand...
Click to collapse
Did you change kernels as well.
Way back in the day I had an issue like you described and the only way to resolve was to restore backup in which gps worked.
Then fire up phone confirm GPS lock. Then do all the flashing.
The only solution I ever knew to this issue was to restore a backup or start over from factory images.
parakleet said:
Did you change kernels as well.
Way back in the day I had an issue like you described and the only way to resolve was to restore backup in which gps worked.
Then fire up phone confirm GPS lock. Then do all the flashing.
The only solution I ever knew to this issue was to restore a backup or start over from factory images.
Click to expand...
Click to collapse
Yeah I changed the kernel. I tried completely unrooting and flashing a fully stock roms (March and April ROM) then reflashing the rooted rom I'm on (pure nexus) and even a non stock kernel (ElementalX) and it still won't lock.
JAYNO20 said:
Yeah I changed the kernel. I tried completely unrooting and flashing a fully stock roms (March and April ROM) then reflashing the rooted rom I'm on (pure nexus) and even a non stock kernel (ElementalX) and it still won't lock.
Click to expand...
Click to collapse
I assuming no back up then if you didnt restore that.
In my experience i dont recall flashing the stock rom alone enough to undo the change to the kernel that screwed up GPS.
It wouldnt lock on stock rom?
try flashing stock kernel by itself maybe?
parakleet said:
I assuming no back up then if you didnt restore that.
In my experience i dont recall flashing the stock rom alone enough to undo the change to the kernel that screwed up GPS.
It wouldnt lock on stock rom?
try flashing stock kernel by itself maybe?
Click to expand...
Click to collapse
Hey,
Flashing stock firmware actually includes the stock Kernel by the way. :good:
Cheers...
It didn't lock on any of the stock roms I flashed (which as user 5.1 stated included the stock kernel) but it used to work fine before on stock roms and even on pure nexus at one time. Not sure what happened or why it just stopped locking onto satellites.
JAYNO20 said:
It didn't lock on any of the stock roms I flashed (which as user 5.1 stated included the stock kernel) but it used to work fine before on stock roms and even on pure nexus at one time. Not sure what happened or why it just stopped locking onto satellites.
Click to expand...
Click to collapse
Hey,
I don't think it will fix it, since several ROMs didn't... But did you try reverting to an older version which used to work. You likely did it already. Just in case you didn't...
Otherwise you may try contacting Google or whom you bought your device, report your issue and see if they are already aware of the situation with others users maybe? As it sounds like a hardware issue...
Looks like you are far of being alone here: https://www.google.fr/search?q=goog...j0l2.8956j0j4&sourceid=chrome-mobile&ie=UTF-8
Good luck...
5.1 said:
Hey,
I don't think it will fix it, since several ROMs didn't... But did you try reverting to an older version which used to work. You likely did it already. Just in case you didn't...
Otherwise you may try contacting Google or whom you bought your device, report your issue and see if they are already aware of the situation with others users maybe? As it sounds like a hardware issue...
Looks like you are far of being alone here: https://www.google.fr/search?q=goog...j0l2.8956j0j4&sourceid=chrome-mobile&ie=UTF-8
Good luck...
Click to expand...
Click to collapse
Yup I did try that already. I am ordering a replacement tonight.
Wifi of my OP3 can not be activated anymore. Also, latest build 5.0.5 bootloops (maybe because of that). I tried msmdownloadtool to restore to OOS 3.1.2 and it booted up again, but no wifi possible. I then tried unlocking the bootloader and installing a custom (omni) rom, but still wifi can not be activated. So, is this a hardware fault?
Lownita said:
Wifi of my OP3 can not be activated anymore. Also, latest build 5.0.5 bootloops (maybe because of that). I tried msmdownloadtool to restore to OOS 3.1.2 and it booted up again, but no wifi possible. I then tried unlocking the bootloader and installing a custom (omni) rom, but still wifi can not be activated. So, is this a hardware fault?
Click to expand...
Click to collapse
Without a logcat there is no way of telling. Best advice would be to make sure you are completely stock (rooted for logcat) and go from there.
zelendel said:
Without a logcat there is no way of telling. Best advice would be to make sure you are completely stock (rooted for logcat) and go from there.
Click to expand...
Click to collapse
I will try, but the last time I tried booting the latest stock rom, the phone bootlooped. Probably because of the wifi. I will flash it again through twrp and hope for the best