Related
Anyone else?
Fully stock? Do a factory reset from stock recovery.. Should fix it. If you're on a custom rom, do a clean flash. (wiping everything except data)
- Sent from an IceCold Hammerhead!
Thx for the advice.
But was wondering if anyone else is getting them.
I'm trying a few things to fix it as I never had a reboot since I owned the phone in November last year, until 4.4.3
At the moment I'm trying an older radio, but it's hard to pin since my last try of using a 4.4.2 kernel kept me up for 35 hours before it happened again.
got an rma replacement.. still happening
meangreenie said:
got an rma replacement.. still happening
Click to expand...
Click to collapse
Did you restore a nandroid on it or anything?
rootSU said:
Did you restore a nandroid on it or anything?
Click to expand...
Click to collapse
no, is completely fresh
tried everything under the sun over the last month.. factory image installs, running safe mode, no apps installed, new Google account... ect ect
can't stop a soft reboot occurring every 2 or 3 days.. I use to have 'up times' of over a month on 4.4
meangreenie said:
no, is completely fresh
tried everything under the sun over the last month.. factory image installs, running safe mode, no apps installed, new Google account... ect ect
can't stop a soft reboot occurring every 2 or 3 days.. I use to have 'up times' of over a month on 4.4
Click to expand...
Click to collapse
Upgrade to 4.4.4 and see if it sorts out?? You get random reboots even when the phone is in safe mode?
vin4yak said:
Upgrade to 4.4.4 and see if it sorts out?? You get random reboots even when the phone is in safe mode?
Click to expand...
Click to collapse
I'm on 4.4.4.. op was posted when 4.4.3 was out.
I know it's weird, i was very surprised to see my new replacement do it too a little a while a go
.. shrugs
meangreenie said:
I'm on 4.4.4.. op was posted when 4.4.3 was out.
I know it's weird, i was very surprised to see my new replacement do it too a little a while a go
.. shrugs
Click to expand...
Click to collapse
Perform a factory reset and see if it sorts things out??
I'm assuming you're stock, unrooted??
still suffering from this
i have noticed that if location is not set to off, it's much better, where it can run for over a week at time
as soon as i turn location off, I'm lucky to get much over 30 hours before it soft reboots
going back to 4.4 it is completely stable as it always was
Hi there,
yesterday I flashed the latest nightly from CM11.
So far, so good.
But: performance isn´t the same, like on stock 38r
I know flashed the apks from the apps I need, to have CM11 like I want it to.
But, without all the google-stuff on it.
I have to say: Great!
But here is what I ask myself:
Is there a version of 38r, without google-stuff?
Cause CM11 can´t bee the same, like CM11s, just including the gapps g.e.
So, does anybody now about a 38r without google-stuff, but with same performance?
Thx
eshoxx1982 said:
Hi there,
yesterday I flashed the latest nightly from CM11.
So far, so good.
But: performance isn´t the same, like on stock 38r
I know flashed the apks from the apps I need, to have CM11 like I want it to.
But, without all the google-stuff on it.
I have to say: Great!
But here is what I ask myself:
Is there a version of 38r, without google-stuff?
Cause CM11 can´t bee the same, like CM11s, just including the gapps g.e.
So, does anybody now about a 38r without google-stuff, but with same performance?
Thx
Click to expand...
Click to collapse
There's no such thing. If you really want to you could manually remove the apps you don't wish to have on your device. That will cause problems when you want to take an OTA though.
Transmitted via Bacon
timmaaa said:
There's no such thing. If you really want to you could manually remove the apps you don't wish to have on your device. That will cause problems when you want to take an OTA though.
Transmitted via Bacon
Click to expand...
Click to collapse
Thx!
I already feared that it would "end like that".
But anyway.
CM11 is okay, I think I will stay there.
But, timmaaa:
Why would there be problems with OTA?
There would be problems because OTA updates fail if you have any modifications to system files.
Transmitted via Bacon
timmaaa said:
There would be problems because OTA updates fail if you have any modifications to system files.
Transmitted via Bacon
Click to expand...
Click to collapse
Okay, I installed a fresh 38r, skipping google-registration at the first start-up.
Then delete/deactivate everything what sound like "google"...
Till now, everything is fine.
I tried to search for OTAs, searching did well. Just no new OTAs available.
System works fine.
Maybe it will work?
As long as I dont have to pay for what ever...
eshoxx1982 said:
Okay, I installed a fresh 38r, skipping google-registration at the first start-up.
Then delete/deactivate everything what sound like "google"...
Till now, everything is fine.
I tried to search for OTAs, searching did well. Just no new OTAs available.
System works fine.
Maybe it will work?
As long as I dont have to pay for what ever...
Click to expand...
Click to collapse
The phone will still function as a phone without the Google stuff. And you'll still be able to download OTA updates, but they'll fail when they try to install.
Transmitted via Bacon
timmaaa said:
The phone will still function as a phone without the Google stuff. And you'll still be able to download OTA updates, but they'll fail when they try to install.
Transmitted via Bacon
Click to expand...
Click to collapse
Okay, do u think I could flash them manualy via TWRP?
If so and there are no other negativ points, I will give it a try.
Negativ thinks, g.e. looking to APN-problems that could cause a higher phone-bill
If you had uninstalled them with System App Remover by Jumobile, when the next update came out, you could result them, update, then delete them again. That's worked for me since 25R.
What is it in 38r that draws you to it instead of just installing cm11... curious?
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?
Hello everyone,
I know I'm on nightlies and I should expect bugs but I have CM12 installed on my OPO and since recently, when I receive or try to place a call, I get a pop-up saying "Unfortunately, Phone has stopped" as soon as I hit the answer or call button. I noticed that if I didn't press "OK" or "Report" the call still connects. However as soon as I hit either of the buttons, the call disconnects and it brings me back to the dialer. Any ideas ?
Do a clean flash of the latest nightly
Sent From Lollipopified Bacon Goodness!
ek69 said:
Do a clean flash of the latest nightly
Sent From Lollipopified Bacon Goodness!
Click to expand...
Click to collapse
Didn't want to because I'm lazy... but that fixed it
hey, just flashed latest cm12 and gapps ( banks) . But getting google play service has stopped error pop ups since first boot and these pop ups are non stop . Thus making phone almost unusable. Had to disable google play services.
Any fixes ?
I am on unofficial twrp 2.8.6.0 .
jaferiqbal said:
hey, just flashed latest cm12 and gapps ( banks) . But getting google play service has stopped error pop ups since first boot and these pop ups are non stop . Thus making phone almost unusable. Had to disable google play services.
Any fixes ?
I am on unofficial twrp 2.8.6.0 .
Click to expand...
Click to collapse
You can't disable Play Services. You're probably using the wrong gapps, which one did you flash?
Transmitted via Bacon
timmaaa said:
You can't disable Play Services. You're probably using the wrong gapps, which one did you flash?
Transmitted via Bacon
Click to expand...
Click to collapse
Problem fixed .
Just reflashed cm12 with another set of gapps
everything seems to be working fine till now
thanks
jaferiqbal said:
Problem fixed .
Just reflashed cm12 with another set of gapps
everything seems to be working fine till now
thanks
Click to expand...
Click to collapse
can you post a link?? i have the same issue
Omg I thought I was the only one haha. Yeah please which did you use?
animeshkumar2012 said:
can you post a link of the gapps you flashed?? i have the same issue og google play services error
Click to expand...
Click to collapse
edit: im on cm12 nightly 20150405 bacon 5.0.2 lollipop with twrp 2.8.6..
I had the same issue when I flashed 5.1 Gapps on cm12.