Database Info

[Q] Nexus 5 camera does not record video

My wife has Nexus 5 (it is completely stock and unrooted with unlocked bootloader) running running Android 4.4.2. Recently, the stock camera app stopped recording videos. Tapping the record button does not do anything while camera works perfectly in photo mode. I factory reset the phone but the problem persists. Any suggestions? Thanks in advance.

lock the bootloader and send it back

shahidhussain said:
My wife has Nexus 5 (it is completely stock and unrooted with unlocked bootloader) running running Android 4.4.2. Recently, the stock camera app stopped recording videos. Tapping the record button does not do anything while camera works perfectly in photo mode. I factory reset the phone but the problem persists. Any suggestions? Thanks in advance.
Click to expand...
Click to collapse
Try to clear data and cache from camera in settings.
If that doesnt work either and you really have done the factory reset, you have to send it to repair bc of an hardware deffect. :crying:

lichti1901 said:
Try to clear data and cache from camera in settings.
If that doesnt work either and you really have done the factory reset, you have to send it to repair bc of an hardware deffect. :crying:
Click to expand...
Click to collapse
I will try that but I think factory resetting clears cache, anyway. The phone camera worked fine previously but now suddenly it stopped.
Thanks anyway.

I have the same problem, when I change the camera app to record nothing happens when I press the red record button. I think the problem started when I upgraded to 4.4.2
Sent from my Nexus 5 using Tapatalk

shahidhussain said:
I will try that but I think factory resetting clears cache, anyway. The phone camera worked fine previously but now suddenly it stopped.
Thanks anyway.
Click to expand...
Click to collapse
And you flashed the right one? Hammerhead-4.4.2
Like i said before, if that doesnt help, you have to send it back to get a replacement.
You need to uncompress each download before use, which creates a new directory for that exact download. That directory contains a ./flash-all.sh script, which handles the various operations, installs the necessary bootloader, baseband firmware(s), and operating system. Note that this operation deletes all user data by default
Click to expand...
Click to collapse
Make yure that data gets wiped also! Dont forget to backup your sdcard bc it gets also wiped.

lichti1901 said:
And you flashed the right one? Hammerhead-4.4.2
Click to expand...
Click to collapse
I did not flash anything. The phone was OTA updated. Please note that the phone received OTA update and when I applied it, it completed its process but did not update (it was still on older android version) and this happened several times (I mentioned this on a separate thread here on XDA old post).

lichti1901 said:
And you flashed the right one? Hammerhead-4.4.2
Like i said before, if that doesnt help, you have to send it back to get a replacement.
Make yure that data gets wiped also! Dont forget to backup your sdcard bc it gets also wiped.
Click to expand...
Click to collapse
I downgraded Nexus 5 from Android 4.4.2 to 4.4 and now the camera is working fine. But I am afraid of updating it back to 4.4.2.

shahidhussain said:
I downgraded Nexus 5 from Android 4.4.2 to 4.4 and now the camera is working fine. But I am afraid of updating it back to 4.4.2.
Click to expand...
Click to collapse
Flash the whole 4.2.2 stock rom in fastboot bro, i have no issues with video recording both on Dalvik and Art runtime

lichti1901 said:
And you flashed the right one? Hammerhead-4.4.2
Like i said before, if that doesnt help, you have to send it back to get a replacement.
Make yure that data gets wiped also! Dont forget to backup your sdcard bc it gets also wiped.
Click to expand...
Click to collapse
gee2012 said:
Flash the whole 4.2.2 stock rom in fastboot bro, i have no issues with video recording both on Dalvik and Art runtime
Click to expand...
Click to collapse
Yes, I did it. Flashed the stock 4.4.2 and everything seems to work fine. However, when I tried updating using OTA after downgrading the update failed and stopped with "Error" message. After flashing 4.4.2 from scratch will hopefully allow smooth future OTA updates. Thanks everyone.

shahidhussain said:
Yes, I did it. Flashed the stock 4.4.2 and everything seems to work fine. However, when I tried updating using OTA after downgrading the update failed and stopped with "Error" message. After flashing 4.4.2 from scratch will hopefully allow smooth future OTA updates. Thanks everyone.
Click to expand...
Click to collapse
Glad you worked it out!
Good thing is - you got a Nexus, so its easy to flash all the stuff and go back to stock/factory image/recovery/...
:highfive:

Any update on this? I have this exact problem. No unlock, not root just pure OTA stock.
1. Video does not record. You press the red button and no timer comes up.
2. A VID_20140126_224910.mp4.tmp file is created 395.54 KB.
3. Time lapse works as do all the other camera functions.
4. The basic Google FAQ has generic instructions if an app does not work so I followed these.
5. in safe mode the camera works fine.
6. Power off and on again. The Video Camera then works fine and creates normal .mp4 files.
Things I have done that may affected the Camera in the first place;
1. Clear cache.
2. Put a .thumbnails file in DCIM to stop the gigantic .thumbnail folder being created.
3. Running nova launcher.
Unlikely these are a factor as I isolated them as an issue and rebooted but worth a mention just in case.
Camera works but have found the it subsequently stopped working again and had to repeat the Google FAQ steps to fix an app.

To answer my own question I found the uninstalling Said It_1.3.37.apk fixed the problem and just to prove it reinstalling brought the problem back.
---------- Post added at 06:01 PM ---------- Previous post was at 05:27 PM ----------
Quick update. the developer emailed me back. He co firmed it does the same on his device and will send an update.

CyanogenMod 11

Bout damn time I made a thread
Sent from my SGH-T699 using Tapatalk

It IS about time.

ok so the cm wiki page says to use cwm. any reason i can't use twrp?

Gibson99 said:
ok so the cm wiki page says to use cwm. any reason i can't use twrp?
Click to expand...
Click to collapse
Shouldn't be any reason you couldn't use TWRP. I'm pretty sure nard himself uses it. The CWM was a CM project for a long time, and still the recovery built within it. Everyone pushes their stuff.

been running M7 for about a day now. had one fc with touchdown, my work email client, but otherwise looks good. surprised i had to manually change build.prop to set the dpi. i'm not blind, so i hate the trend towards gigantic fonts even on smallish screens like this one.
i also wasn't able to use tibu to restore securid from my old phone (vzw droid4) but i suspect that app uses some system properties like imei to create its security, so it can't be moved... not a problem. just have to do clean in stall and reimport the token.
one thing i noticed even in cm11m2 on my d4 as well as on this phone in cm11m7 is that the included sms app doesn't actually have a dark theme, and that sticks out like a sore thumb. even when you check the box for dark theme in the sms app itself, it's still white. not a huge deal obviously but doesn't match the rest of cm's normal polish.

Gibson99 said:
been running M7 for about a day now. had one fc with touchdown, my work email client, but otherwise looks good. surprised i had to manually change build.prop to set the dpi. i'm not blind, so i hate the trend towards gigantic fonts even on smallish screens like this one.
i also wasn't able to use tibu to restore securid from my old phone (vzw droid4) but i suspect that app uses some system properties like imei to create its security, so it can't be moved... not a problem. just have to do clean in stall and reimport the token.
one thing i noticed even in cm11m2 on my d4 as well as on this phone in cm11m7 is that the included sms app doesn't actually have a dark theme, and that sticks out like a sore thumb. even when you check the box for dark theme in the sms app itself, it's still white. not a huge deal obviously but doesn't match the rest of cm's normal polish.
Click to expand...
Click to collapse
The "use dark theme" option only applies to the quick reply pop up windows. The option is conveniently listed in the "quick reply" section.

orange808 said:
The "use dark theme" option only applies to the quick reply pop up windows. The option is conveniently listed in the "quick reply" section.
Click to expand...
Click to collapse
doh, you're right. my point still stands about messaging not matching the rest of cm's theming. i guess they expect people to just use chomp, go, handcent or whatever other app... i like the standard one in cm tho. except for how light it is.

What did change from the blobs for the builds after 14 /06 ?
Running 14/06 now, really good, battery charging issues are gone (i think), because a new kernel/other blobs.
Where can you find more info about blobs changes (propetary) ?

I've been having data and sms issues lately since I switched to cm11 or any of the latest 4.3.3 builds. Was there a recent radio firmware released?

Gh0sTly said:
I've been having data and sms issues lately since I switched to cm11 or any of the latest 4.3.3 builds. Was there a recent radio firmware released?
Click to expand...
Click to collapse
Which nightly?
Are you on T-Mo? Are you using a third party messenging app?
Did you wipe your data and cache before you flashed?

Gh0sTly said:
I've been having data and sms issues lately since I switched to cm11 or any of the latest 4.3.3 builds. Was there a recent radio firmware released?
Click to expand...
Click to collapse
which build are you on? i'm running cm11-20140608-Snapshot-M7 (which is 4.4.2, not 4.3.3) and have no issues to report so far. i haven't given it a full shakedown yet - still haven't tried BT or GPS but so far so good. watched netflix on the bus this morning and never had an issue. my wife and i text a lot and haven't had issues w/ that either. this evening i'm going to try out BT with my elm327 obd-ii adapter and if i have time, test audio over an avantree cara adapter. i started google maps a couple times and it found me quickly and accurately but i haven't run gps for more than a minute or so at a time so i don't know how it'll do. maybe i'll turn it on while on the bus this afternoon and see if it works well for the whole ride home.

robuser007 said:
What did change from the blobs for the builds after 14 /06 ?
Running 14/06 now, really good, battery charging issues are gone (i think), because a new kernel/other blobs.
Where can you find more info about blobs changes (propetary) ?
Click to expand...
Click to collapse
I updated ****. we're benefiting vicariously from the d2 kit-kat release
Sent from my Nexus 7 using Tapatalk

After a few minutes of playing with the CM M5 smartphone burned and became slow. Now the smartphone with the stock firmware does not burn more but it is slow. It works well this M7? You recommended me?
For a few months I used CM kitkat but I had to do a wipe. Now I do not know how to install the CM. I'm using the stock firmware.
To install:
1 rooted smartphone.
2 I copy "cm-11-20140608-SNAPSHOT-M7-apexqtmo.zip" in memory of the smartphone.
3 CWM 6.0.1.2 "install zip from sdcard -> choose zip from sdcard" I select "cm-11-20140608-SNAPSHOT-M7-apexqtmo.zip"
4 updates fail
What I'm wrong?
thanks for the help

Balthasar85 said:
After a few minutes of playing with the CM M5 smartphone burned and became slow. Now the smartphone with the stock firmware does not burn more but it is slow. It works well this M7? You recommended me?
For a few months I used CM kitkat but I had to do a wipe. Now I do not know how to install the CM. I'm using the stock firmware.
To install:
1 rooted smartphone.
2 I copy "cm-11-20140608-SNAPSHOT-M7-apexqtmo.zip" in memory of the smartphone.
3 CWM 6.0.1.2 "install zip from sdcard -> choose zip from sdcard" I select "cm-11-20140608-SNAPSHOT-M7-apexqtmo.zip"
4 updates fail
What I'm wrong?
thanks for the help
Click to expand...
Click to collapse
First, use the most up-to-date recovery; I'm pretty sure that cwm 6.0.1.2 isn't it if I see 6.0.4.7 on other devices. I like using TWRP personally, and there's a thread in this forum for that. The outdated recovery is probably the main problem right there for the failed flash.
Second, it doesn't look like you wiped anything in your steps. No factory reset, not even wiping cache and dalvik. Most people do a clean flash (that's a factory reset in recovery) when troubleshooting a failure to install a custom ROM.
Try using the latest recovery, wiping at least cache and dalvik, and see if it helps.
Good luck
Sent from my Nexus 5 using Tapatalk

reaper000 said:
First, use the most up-to-date recovery; I'm pretty sure that cwm 6.0.1.2 isn't it if I see 6.0.4.7 on other devices. I like using TWRP personally, and there's a thread in this forum for that. The outdated recovery is probably the main problem right there for the failed flash.
Second, it doesn't look like you wiped anything in your steps. No factory reset, not even wiping cache and dalvik. Most people do a clean flash (that's a factory reset in recovery) when troubleshooting a failure to install a custom ROM.
Try using the latest recovery, wiping at least cache and dalvik, and see if it helps.
Good luck
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
i second this. my steps were:
1- boot to download mode, install twrp
2- boot to recovery, flash CM
3- while still in recovery, flash gapps if you want them (make sure you have the correct version of gapps from the CM site)
4- still in recovery, wipe cache and dalvik
5- still in recovery, do factory reset
6- reboot normally (it's called 'system' in twrp) and start using phone
note that there is no need to copy/flash SU at any time because CM is already rooted.

using nightly 22/06 my phone slowed down to unusable slow, flashed 24/06 yesterday.
Never had this before on cm nightly's for the relay.
And the charging (usb) problems aren't over yet (sometimes it works fine for a few hours, sometimes a few minutes).
Did a clean install a week ago (didn't solve anything).

robuser007 said:
using nightly 22/06 my phone slowed down to unusable slow, flashed 24/06 yesterday.
Never had this before on cm nightly's for the relay.
And the charging (usb) problems aren't over yet (sometimes it works fine for a few hours, sometimes a few minutes).
Did a clean install a week ago (didn't solve anything).
Click to expand...
Click to collapse
Ok. Now, find out what version of cpu you have and get some logs to help them track down your problems.
There's a search box in the corner.
I don't have any of the problems you are describing and I am betting the developers do not, either.

orange808 said:
Which nightly?
Are you on T-Mo? Are you using a third party messenging app?
Did you wipe your data and cache before you flashed?
Click to expand...
Click to collapse
I am on T-Mo, I get this via the default android messaging app as well as hangouts, but I also have times where mobile data refuses to work as well.
Right now, I'm having this issue on 11-20140608-Snapshot-M7-apexqtmo. I did wipe data and cache before I flashed. I'm not sure what is causing my issue.
I am tempted to reflash it back to factory, and take it back under my total care and get it replaced for a S5, but I really like my keyboard. :crying:

did you wipe cache and dalvik after flashing the rom? the only quirk i've noticed on m7 is that if i don't reboot every couple of days, my work email program (touchdown) likes to get slow and crashy while composing emails. going to the recent apps drawer and closing everything there usually fixes that. gps and bluetooth work fine even at the same time and battery life is great. after having tried multiple roms on my droid4 and having gps and camera issues, i am pleasently susprised how stable cm is on this relay (which i've only had a couple weeks now).

Gibson99 said:
did you wipe cache and dalvik after flashing the rom? the only quirk i've noticed on m7 is that if i don't reboot every couple of days, my work email program (touchdown) likes to get slow and crashy while composing emails. going to the recent apps drawer and closing everything there usually fixes that. gps and bluetooth work fine even at the same time and battery life is great. after having tried multiple roms on my droid4 and having gps and camera issues, i am pleasently susprised how stable cm is on this relay (which i've only had a couple weeks now).
Click to expand...
Click to collapse
I even tried that too. My phone's about a year and a half old now. I've noticed recently if the keyboard is out, or i'm holding the phone sideways, and I get a call, the phone app crashes over and over till i rotate it upward so the display is vertical, then it stops crashing(all while the phone is still ringing so I can still answer it.)

Bug found with Android 5?

Hi
Every time I reboot the phone while plugged in the wall charger, the SystemUI is in a loop crash until I unplug the cable.... It happens in safe mode too...
Stock rooted Lollipop
Am I the only one with this bug?
Thanks

Matrix_19 said:
Hi
Every time I reboot the phone while plugged in the wall charger, the IU system is in a loop crash until I unplug the cable.... It happens in safe mode too...
Stock rooted Lollipop
Am I the only one with this bug?
Thanks
Click to expand...
Click to collapse
My phone was being EXTREMELY slow after I installed everything and my phone was running. So I rebooted and didn't have any problems like this, but it just doesn't feel as snappy as KitKat. Maybe it's just me... also apparently we didn't get all the new notification sounds

Nope, everything fine here. I made a manual flash and flashed everything exept for userdata.img
Gesendet von meinem Nexus 5

I did the upgrade without wiping userdata. But everything is fine when the cable is not connected and the phone is not booting... Strange

hi guys,
anyway work around on sd bug ?
My internal memory is on '/0' now...
thanks !

Same here. ****ing lag. Takes 20 second to response. Wtf lolipop?

Found this, exactly the same bug on the preview Android L
SystemUI crash loop when … : http://youtu.be/y8KVtFYEs_4

Installed factory image, no problems.

I found, that lag is there if i play music with PVSTAR+ (youtube player) in backround. Lag on lag! I dont now, why i cann't find Freedi music player in Play Store..

snappycg1996 said:
My phone was being EXTREMELY slow after I installed everything and my phone was running. So I rebooted and didn't have any problems like this, but it just doesn't feel as snappy as KitKat. Maybe it's just me... also apparently we didn't get all the new notification sounds
Click to expand...
Click to collapse
its just you. i flashed the factory image, (flash-all.bat script) and lollipop is much faster than stock 4.4.4 (which i was using before the factory images came), so I can tell its faster. I didnt root it yet though..

FYI
I flashed the factory image again, including wiping my data
and this time it's fine.

StajercS said:
I found, that lag is there if i play music with PVSTAR+ (youtube player) in backround. Lag on lag! I dont now, why i cann't find Freedi music player in Play Store..
Click to expand...
Click to collapse
Maybe it was just because I was updating apps last night, but YouTube kept freezing... and etching... I never remember that on KitKat.
thegtfusion said:
its just you. i flashed the factory image, (flash-all.bat script) and lollipop is much faster than stock 4.4.4 (which i was using before the factory images came), so I can tell its faster. I didnt root it yet though..
Click to expand...
Click to collapse
You're right! It seems to have straightened out some, it's way better now. When I rebooted this morning, boot took some time, but it was pretty fast as soon as the lock screen came up.
StajercS said:
Same here. ****ing lag. Takes 20 second to response. Wtf lolipop?
Click to expand...
Click to collapse
I had the same issue... hopefully yours stabilizes. I'm noticing there is still some but mine is better.

StajercS said:
I found, that lag is there if i play music with PVSTAR+ (youtube player) in backround. Lag on lag! I dont now, why i cann't find Freedi music player in Play Store..
Click to expand...
Click to collapse
Try getting rid of MusicFX.apk (it's a guess)
I don't know what you guys did to say that 5.0 is laggy and all about these "bugs". I have two Nexus 5 running stock image and N4 running compiled from source , Nothing wrong everything's fine! :/

Matrix_19 said:
FYI
I flashed the factory image again, including wiping my data
and this time it's fine.
Click to expand...
Click to collapse
Damnit...I'm setting up my phone.. I tried it again and the issue is back.
I don't know if it's started when I set the patern* unlock.

Matrix_19 said:
Damnit...I'm setting up my phone.. I tried it again and the issue is back.
I don't know if it's started when I set the shema unlock.
Click to expand...
Click to collapse
Wipe Cache Partition, if doesn't work wipe data/cache partition with Factory Restore.

I have the same problem as you. First, I have followed method 1 from this thread (http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701) to flash the factory image on my N5. Then, I had System UI crashed in loop like you.
After that, I have flashed again the factory image using method 2 this time. Same problem happened again We have one thing in common, we're using the french UI in Android. I have change my language to english and everything seems fine for now. I'll post later if the system UI crash again.
I have another problem with the french UI in Lollipop, do you have in the search bar "Dîtes 1$s" instead of "Dîtes OK Google"? I've uploaded a screenshot of this .

jeremymolina said:
Wipe Cache Partition, if doesn't work wipe data/cache partition with Factory Restore.
Click to expand...
Click to collapse
done, same thing
loop crash at the boot when plugged in the wallcharger (until I unplug it)
the only way to not have the bug is to set no lock at all (not even slide)

Matrix_19 said:
done, same thing
loop crash at the boot when plugged in the wallcharger (until I unplug it)
the only way to not have the bug is to set no lock at all (not even slide)
Click to expand...
Click to collapse
Same issue here with system in French and pin lock screen.. I'm switching to English to see if it gets fixed..

mke1989 said:
Same issue here with system in French and pin lock screen.. I'm switching to English to see if it gets fixed..
Click to expand...
Click to collapse
thanks, I'm not crazy !!
Maybe it is language related !?

mke1989 said:
Same issue here with system in French and pin lock screen.. I'm switching to English to see if it gets fixed..
Click to expand...
Click to collapse
another factory reset, english language selected , patern lock... reboot twice with the wallcharger connected....
no more issue !
thanks mke1989 !!

OnePlus One Malfunction? Help please

G'day people I've run into something pretty weird with my OnePlus One. I installed the CM12 nightly and booted it up, ran it for a few hours then got ghost touches and the screen became unresponsive at times.
So, having my usual backup of CM11S, I wiped and restored to the latest backup I had and everything was weird. I kept getting ghost touches and reduced responsiveness, and sometimes it would just randomly malfunction and not unlock and just keep the screen off.
Rebooting clears up the problem for about 5 minutes and then it comes back at full blast.
I tried installing the last CM11S update via flashing Calkunins stock XNPH44S zip and still I have all these weird issues that wasn't there before I flashed the CM12 nightly.
Has anyone come across this problem or is it just me and my device? It's seriously a cause for concern, and I'm posting this to both XDA and the OnePlus forums in hopes of getting some sort of help and relief in this situation.
Any assistance is appreciated and I thank you in advance for taking the time to read this.

reflash cm12 nightly and try again.
perhaps use fastboot to flash the partitions .
You might need to find a copy of the first cm11s rom and try that one. I have a feeling your one of the unlucky with firmware sensitivity.
Which date is your phone from? (its on the box)
Sent from my A0001 using XDA Free mobile app

GO back to completely factory fresh, via fastboot commands.
If you still have problems, it's a hardware issue then.

kthejoker20 said:
GO back to completely factory fresh, via fastboot commands.
If you still have problems, it's a hardware issue then.
Click to expand...
Click to collapse
not entirely true, there are different screens, that could be the issue. It was reported in boeffla kernel thread. sesrch throught it and it might contain something useful to try.
also open a support question, Oneplus needs to know how annoying their poor choice of different lcds are
Sent from my A0001 using XDA Free mobile app

bachera said:
reflash cm12 nightly and try again.
perhaps use fastboot to flash the partitions .
You might need to find a copy of the first cm11s rom and try that one. I have a feeling your one of the unlucky with firmware sensitivity.
Which date is your phone from? (its on the box)
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
I'll try to flash CM11S via fastboot to see if it clears up the issue. For now, the date I got mine is 2014-07-16. Shipped to me after 12 days (International shipment via courier)

UPDATE
Flashing CM11S via fastboot resolved all issues as far as I can tell.
Will remain on the lookout for the bugs in the future but for now I'm happy to say it worked for me.
Thank you all again for the advice and guidance, it was appreciated.

GLad it worked for you.
I love when other posters try to punk you when you try to help people.

kthejoker20 said:
GLad it worked for you.
I love when other posters try to punk you when you try to help people.
Click to expand...
Click to collapse
Nobody was trying to "punk" you. There are usually several different potential causes for the same symptom, all he was doing was highlighting that and adding extra information in order to help further (in the case that flashing the stock images didn't help, which has happened many times). He was also trying top help the OP. Calm down.
Transmitted via Bacon

timmaaa said:
Nobody was trying to "punk" you. There are usually several different potential causes for the same symptom, all he was doing was highlighting that and adding extra information in order to help further (in the case that flashing the stock images didn't help, which has happened many times). He was also trying top help the OP. Calm down.
Transmitted via Bacon
Click to expand...
Click to collapse
I thought it was the partition thing too because I had almost the same problem on my HTC Amaze back in 2014, and flashing the OEM RUU helped with sorting things out.
But as for the random screen touches, flashing everything from fastboot helped for only a few hours. The symptoms came back after a while, specifically when I replaced my music and pictures. I'm thinking that I may have a corrupted file on it somewhere but I doubt it'll cause a malfunction like that.
So I tried flashing Franco Kernel, and it seems to have cleared it up..... for now.
It's so frustrating thinking that my device may be defective

UPDATE #2
Flashing Franco Kernel didn't help. Symptoms came back within a couple hours. Will try a custom ROM, specifically AOPK (because I want to )
If that doesn't fix the issue then I've just got to face the fact that I have a defective device (somehow)

Bump
Nothing worked. I contacted the manufacturer but they seem to think doing a factory reset will help. It didn't.
Flashing CM11S via fastboot doesn't help
I really think this is a hardware issue that just emerged from nowhere, probably due to lack of premium or standardized quality adhesive.
There's a really long thread over at the OnePlus forums about a guy who found it was a grounding issue and took some adhesive tape to insulate the area near the proximity sensor (I think? I'll include the link in here somewhere)
Honestly, OnePlus impressed me....at first. But I cannot use a phone that's not working properly.
https://forums.oneplus.net/threads/...-hint-it-was-never-a-software-problem.186235/

Same problem here... I had the first ghost touches after having installed CM12 Nightly.
I was using CM12 built by Daleski75 so far without any issue. The problem does not appear on a regular basis and when it does, a reboot seems to fix it, at least for a few minutes/hours.
I'll try a clean install when the stable version is out (don't really want to wipe now and once more in two/three weeks).
@rdar_93: Did you find a solution? Are you going to send the device back to OnePlus? If it is actually a hardware issue, that will be enough for me, no more OPO. Sending the device back to China after 2 months of use and having to pay for the shipping is not acceptable.
Edit: It's getting worse... I am gonna wipe soon. Here is a short video: drive.google.com/file/d/0B-EYHGTB15_wS1JXdXlmZXVsT0k/view?usp=sharing
I can't post link for now so you'll have to copy and paste it in your browser.
Edit2: After a full wipe and the installation of the latest nightly, the situation seems to be better, even though I will have to use the phone a bit more to see if it happens again. By the way, I lost dt2w and the gestures don't work well, if not at all... When I draw a V, nothing happens, when I draw a circle, the phone behaves as if I did a double tap. Weird. Again, this happens after a wipe+latest nightly installation+wipe again (to be sure ).

sylvain15250 said:
Same problem here... I had the first ghost touches after having installed CM12 Nightly.
I was using CM12 built by Daleski75 so far without any issue. The problem does not appear on a regular basis and when it does, a reboot seems to fix it, at least for a few minutes/hours.
I'll try a clean install when the stable version is out (don't really want to wipe now and once more in two/three weeks).
@rdar_93: Did you find a solution? Are you going to send the device back to OnePlus? If it is actually a hardware issue, that will be enough for me, no more OPO. Sending the device back to China after 2 months of use and having to pay for the shipping is not acceptable.
Edit: It's getting worse... I am gonna wipe soon. Here is a short video: drive.google.com/file/d/0B-EYHGTB15_wS1JXdXlmZXVsT0k/view?usp=sharing
I can't post link for now so you'll have to copy and paste it in your browser.
Edit2: After a full wipe and the installation of the latest nightly, the situation seems to be better, even though I will have to use the phone a bit more to see if it happens again. By the way, I lost dt2w and the gestures don't work well, if not at all... When I draw a V, nothing happens, when I draw a circle, the phone behaves as if I did a double tap. Weird. Again, this happens after a wipe+latest nightly installation+wipe again (to be sure ).
Click to expand...
Click to collapse
I contacted them and they sent me a program to use. It uses fastboot to flash CM11S and probably fix the partitions that are messed up (I'm making an assumption)
UNFORTUNATELY I'm stuck in a bootloop.
I'm so angry, disappointed and depressed at the same time. I paid about $2500 TTD (in my country) which is probably the equivalent to somebody's rent. I had to work a month to save up the money to buy this and it turns out that the device is faulty after a certain amount of time (or at least mine was)
This is BS.
They said to send them a snapshot of what went on with the fastboot thing, so I figure I"ll upload it here too.

rdar_93 said:
I contacted them and they sent me a program to use. It uses fastboot to flash CM11S and probably fix the partitions that are messed up (I'm making an assumption)
UNFORTUNATELY I'm stuck in a bootloop.
I'm so angry, disappointed and depressed at the same time. I paid about $2500 TTD (in my country) which is probably the equivalent to somebody's rent. I had to work a month to save up the money to buy this and it turns out that the device is faulty after a certain amount of time (or at least mine was)
This is BS.
They said to send them a snapshot of what went on with the fastboot thing, so I figure I"ll upload it here too.
Click to expand...
Click to collapse
I guess you didnt unlock bootloader first
Which when you do wipes the phone so you loose all your stuff.
possible workaround is fasboot on custom recovery and then flash the zip that sets unlock status and circumvents the whole format thing
Sent from my A0001 using XDA Free mobile app

bachera said:
I guess you didnt unlock bootloader first
Which when you do wipes the phone so you loose all your stuff.
possible workaround is fasboot on custom recovery and then flash the zip that sets unlock status and circumvents the whole format thing
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
I actually did unlock my bootloader.
PS I also got tired of seeing CM11S try to boot up so I flashed ColorOS (because it's the only rom I had on my laptop. Why not download another 4.4.x AOSP rom? Unstable wifi at school)
So yeah, wifi is not turning on. Gonna try the program again. I wonder if it would work this time?
The conditions aren't as different as before, could work, right?
Honestly I want to wait but they take so long to reply.

UPDATE
After flashing ColorOS I decided to go back and try doing the CM11S via fastboot commands. Still got a bootloop but hey I got the correct fastboot logo now in case if it made a difference.
So I did the compulsory flashing commands when I went from Color to CM11S and still bootlooped.
So I booted into fastboot again
fastboot oem unlock (supposed to unlock bootloader and reboot if it's locked, no reboot if unlocked [assumption])
then rebooted into fastboot again, ran the batch files OnePlus sent to me which essentially flashed CM11S just like you would over fastboot, but with added modems etc.
Successfully booted into CM11S without issues, WiFi works again and so far no symptoms as yet.
Will keep this post updated if anything happens.
My screenshots of the batch file commands OnePlus sent would be found in the attachments.

UPDATE 2
So I think it's fixed permanently this time.
I'm not sure though. It hasn't done anything weird. I will copy my music and photos to see if that would cause anything to happen

I would stay away from os since it messes up partition and people ran into data drop out and modem issues.
Cm11s Roms are the way to go on this hardware.

FYI, when you flash CM12 the radio is overwritten with an alpha/beta radio which causes (well, caused for me) THE EXACT issues OP was having in CM11/S. The CM12 radio (as far as I can tell) ONLY works with CM12 - making going back a PITA.
If you have the baseband in this thread (see screenshot in first post) then that means you are on the experimental radio and are going to have a bad time if you aren't on CM12.
I flashed the latest OTA radio found here and all was right with the world (at least where my OPO was concerned ).

hp13 said:
I would stay away from os since it messes up partition and people ran into data drop out and modem issues.
Cm11s Roms are the way to go on this hardware.
Click to expand...
Click to collapse
I would like to go back to CM11s to check if the situation is better. I tried to flash the lastest CM12 build and it seems to be better but still not as good as before
When I do a wipe and then flash the ROM in TWRP, there are some "folder already up to date", which I would like to avoid. What I would like to do is doing a complete clean install of either CM12 or CM11s plus rewriting the partitions,... So that I'm sure if the problem is still here it is due to an hardware issue.
Is there any chance someone can help me with this? Even with a link... I searched for "write partition" without any luck :-/
Thanks !
EDIT: Do you think the OnePlusRecovery Tool can help me with this?

Recovered from boot loop but constant crashes with older ROM

I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?

I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine

Jst flash a newer modem in recovery

mugoftee said:
I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?
Click to expand...
Click to collapse
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.

PivotMasterNM said:
I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine
Click to expand...
Click to collapse
That won't help, flashing an older build than what was previously installed without wiping properly will cause problems.
KURDKiNG said:
Jst flash a newer modem in recovery
Click to expand...
Click to collapse
Modem has nothing to do with this.

Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine

KURDKiNG said:
Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine
Click to expand...
Click to collapse
Most likely pure coincidence.

Thanks your reply!
Heisenberg said:
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.
Click to expand...
Click to collapse
Actually this is what I did in the very first beginning but I encountered the same rebooting symptoms like after the OTA update. Since it didn't seem to change anything I didn't mention it. I used cm-12.1-YOG4PAS1N0-bacon-signed.

Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.

mugoftee said:
Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.
Click to expand...
Click to collapse
I don't think you have any other option unfortunately.