Hey guys,
New to the OPO, just came from the galaxy note 2 and love the phone but have an issue.
When I am in an app like Facebook and am scrolling, while I am mid scroll (haven't lifted my finger from the screen) it opens a picture or the comments section for some reason.... Anyone else having this issue and is there a possible fix?
Thank you!
Update your ROM. ROMs with older touchscreen drivers are known to cause this.
I have this problem also on 38R ... I had also that touchscreen issues like people said here after 38R update but yesterday it gone.
Sent from my OnePlus One using Tapatalk
zephiK said:
Update your ROM. ROMs with older touchscreen drivers are known to cause this.
Click to expand...
Click to collapse
How do I update from 38R, when I go into settings and try to update, it says no updates found!
arty93 said:
How do I update from 38R, when I go into settings and try to update, it says no updates found!
Click to expand...
Click to collapse
Flash a custom kernel such as Franco kernel.
Sent from my One A0001 using Tapatalk
Pretty new to android... Can someone point me in the right direction with how to root, install new custom kernels and whatever else I would need to get rid of this lag issue! Thank you!
arty93 said:
Pretty new to android... Can someone point me in the right direction with how to root, install new custom kernels and whatever else I would need to get rid of this lag issue! Thank you!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon
timmaaa said:
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon
Click to expand...
Click to collapse
Okay i have unlocked my bootloader and rooted my device. should i update to another rom to fix this scrolling lag or update the kernel?
arty93 said:
Okay i have unlocked my bootloader and rooted my device. should i update to another rom to fix this scrolling lag or update the kernel?
Click to expand...
Click to collapse
You can do either, the choice is entirely yours, just remember to make a backup first.
timmaaa said:
You can do either, the choice is entirely yours, just remember to make a backup first.
Click to expand...
Click to collapse
Are there any ROMs out there that are better then the 11s? Also to make a backup in TWRP do I just go into download mode and hit back up and select all three options?
arty93 said:
Are there any ROMs out there that are better then the 11s? Also to make a backup in TWRP do I just go into download mode and hit back up and select all three options?
Click to expand...
Click to collapse
The term 'better' is very subjective, only you can answer that after testing out some ROMs. What do you mean by 'download mode'? Go into recovery, select backup from the main menu, name sure system, data, and boot are checked, and swipe to backup.
Transmitted via Bacon
timmaaa said:
The term 'better' is very subjective, only you can answer that after testing out some ROMs. What do you mean by 'download mode'? Go into recovery, select backup from the main menu, name sure system, data, and boot are checked, and swipe to backup.
Transmitted via Bacon
Click to expand...
Click to collapse
Okay yes this what I did for backing up! What is your preference of ROM?
arty93 said:
Okay yes this what I did for backing up! What is your preference of ROM?
Click to expand...
Click to collapse
I like several ROMs, and there's really no point in me telling you what they are because everyone has different tastes and different needs from a ROM. I can only suggest you check a few out, read their feature sets, and try them.
Transmitted via Bacon
Related
Hi all.
How can I wipe my Nexus 5 so it is a plain Kit Kat 4.4.2 (like the day I received it) and just root it? it's currently in 4.4.2 and rooted, but with a lot of stuf in it too. My main concern is how to wipe once it's rooted, and how to reroot.
For those who like to read, a little more info:
I have a Nexus 5 which received 2 days ago. I come from an iPhone 5S, so... pretty newbie...
I unlocked the bootloader and rooted the device after unboxing, and have been using it since. Problems are:
1. I just found out about CWM and its capabilities, and I intend to use the backups a lot.
2. I kind of ****ed up with a couple of apps I regret installing.
3. After a backup I just did today, it asked to whether or not fix the recovery (or something like that). Selected YES, nothing happened. It then asked to fix the root... said YES and screwed it completely. I had to put SuperSu in the phone as a ZIP and manually install it again to recover my root access. It kind of looks "dirty" now, lol.
Anyways, I'd like to make a whole device backup from CWM with Kit Kat out of the box, no extra apps installed. Just rooted. Then install all my stuff, sync contacts and so on, and make another backup.
That's why I want to erase the device and have it all clean (just rooted).
Thanks!
Start here http://forum.xda-developers.com/showthread.php?p=47156064
Then go here
http://forum.xda-developers.com/showthread.php?p=47025283
jd1639 said:
Start here http://forum.xda-developers.com/showthread.php?p=47156064
Then go here
http://forum.xda-developers.com/showthread.php?p=47025283
Click to expand...
Click to collapse
Thanks! Can link 2 be replaced with just running CF-Auto-Root? That's what I used the first time and worked great.
rwed said:
Thanks! Can link 2 be replaced with just running CF-Auto-Root? That's what I used the first time and worked great.
Click to expand...
Click to collapse
It can, but I'd recommend you do it per the link.
jd1639 said:
It can, but I'd recommend you do it per the link.
Click to expand...
Click to collapse
Mmm. OK. And why? (Just curious at this point)
rwed said:
Mmm. OK. And why? (Just curious at this point)
Click to expand...
Click to collapse
Because the 2nd method furnishes you with knowledge and experience to help you understand and learn things that cf auto root "automates" for you. Using our recommended method, you will have a head start in knowing how to do things you may need to do to recover your device from various scenarios.
...for example, had you used that method last time - applying logic and knowledge, you may not have created this thread
Sent from my Nexus 5 using Tapatalk
rootSU said:
...for example, had you used that method last time - applying logic and knowledge, you may not have created this thread
Click to expand...
Click to collapse
lol OK. Thanks guys.
I come from iOS after several years. Please bear that in mind.
We're just offering you the benefit of our collective experience. Some of us have been doing this for years so please understand - we're not giving you grief. We have your best interests in mind
Sent from my Nexus 5 using Tapatalk
rootSU said:
We're just offering you the benefit of our collective experience. Some of us have been doing this for years so please understand - we're not giving you grief. We have your best interests in mind
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Oh please, I know. I was just hiding my ignorance under the iOS carpet.
Will give a read to both links tomorrow. Will definitely do link1 on friday if I find the time, and will then consider either doing link2 or going the CF-Auto-Root way.
I'll let you know how this all ends.
Again, thanks!
Update:
Followed steps in link1. Everything went fine.
Gave a deep read to link2. Found it understandable and easy to do and follow, but decided to go the CF-Auto-Root way just because I had done it before and worked nicely...
Everything OK. Something weird happened -again- though. After the clean restore and root, I installed CWM and proceeded to make a backup of the plain system. After it, it asked to fix root again. I had previously said YES, which lead to a broken root, so I said NO this time. Same thing happened!! I lost root and had to manually install SuperSu 1.93 from ZIP in CWM... Why does this happen?
Anyways, I have another question. If one day I decide to restore from this backup I just made, will it be exactly as doing a complete restore following link1?
Thanks!
jd1639 said:
Start here http://forum.xda-developers.com/showthread.php?p=47156064
Then go here
http://forum.xda-developers.com/showthread.php?p=47025283
Click to expand...
Click to collapse
rootSU said:
Because the 2nd method furnishes you with knowledge and experience to help you understand and learn things that cf auto root "automates" for you. Using our recommended method, you will have a head start in knowing how to do things you may need to do to recover your device from various scenarios.
...for example, had you used that method last time - applying logic and knowledge, you may not have created this thread
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Stop using cwm... use twrp or philz which can turn the nag off.
Sent from my Nexus 5 using Tapatalk
rwed said:
Update:
Followed steps in link1. Everything went fine.
Gave a deep read to link2. Found it understandable and easy to do and follow, but decided to go the CF-Auto-Root way just because I had done it before and worked nicely...
Everything OK. Something weird happened -again- though. After the clean restore and root, I installed CWM and proceeded to make a backup of the plain system. After it, it asked to fix root again. I had previously said YES, which lead to a broken root, so I said NO this time. Same thing happened!! I lost root and had to manually install SuperSu 1.93 from ZIP in CWM... Why does this happen?
Anyways, I have another question. If one day I decide to restore from this backup I just made, will it be exactly as doing a complete restore following link1?
Thanks!
Click to expand...
Click to collapse
Flash this in cwm http://d-h.st/YpG. It'll put twrp on
Oh damn it... Really? OK, a couple of quick questions:
1. Did reinstalling SuperSu leave junk in the file system?
2. Will flashing TWRP leave anything either?
My OCD would probably make me restore again if the answer to any of those questions is yes.
rootSU said:
Stop using cwm... use twrp or philz which can turn the nag off.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
jd1639 said:
Flash this in cwm http://d-h.st/YpG. It'll put twrp on
Click to expand...
Click to collapse
rwed said:
Oh damn it... Really? OK, a couple of quick questions:
1. Did reinstalling SuperSu leave junk in the file system?
2. Will flashing TWRP leave anything either?
My OCD would probably make me restore again if the answer to any of those questions is yes.
Click to expand...
Click to collapse
No to both your questions.
jd1639 said:
No to both your questions.
Click to expand...
Click to collapse
Thank you very much!
I just saw that TWRP is in version 5.7.3 in the Play Store. Any reason why you linked to 2.6.3.4? I'm asking because I guess it'll update as soon as I boot. Right?
rwed said:
Thank you very much!
I just saw that TWRP is in version 5.7.3 in the Play Store. Any reason why you linked to 2.6.3.4? I'm asking because I guess it'll update as soon as I boot. Right?
Click to expand...
Click to collapse
Not for the nexus 5. I think you're looking at cwm.
jd1639 said:
Not for the nexus 5. I think you're looking at cwm.
Click to expand...
Click to collapse
I saw it here: https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager
rwed said:
I saw it here: https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager
Click to expand...
Click to collapse
I just looked at it. I'm not sure what that is. The file I linked you to is the latest image from goo.im which is the official twrp depository.
jd1639 said:
I just looked at it. I'm not sure what that is. The file I linked you to is the latest image from goo.im which is the official twrp depository.
Click to expand...
Click to collapse
I'll just install your file, specially if you can't even tell what that thing I linked is. Thank you jd. :good:
rwed said:
Thank you very much!
I just saw that TWRP is in version 5.7.3 in the Play Store. Any reason why you linked to 2.6.3.4? I'm asking because I guess it'll update as soon as I boot. Right?
Click to expand...
Click to collapse
That's the twrp manager. Different things. One is an app and one is a recovery
Sent from my Nexus 5
Hi
can you help me either to put another language into the phone, or help me put cyanongen instead of the color Os i got with the oneplus i bought-
i tried the https://www.youtube.com/watch?v=QDKOEtN9pbo but it fails as soon as i install from sdcard.
i dont know any other method that works.
Thanks a lot!
METAL66 said:
Hi
can you help me either to put another language into the phone, or help me put cyanongen instead of the color Os i got with the oneplus i bought-
i tried the https://www.youtube.com/watch?v=QDKOEtN9pbo but it fails as soon as i install from sdcard.
i dont know any other method that works.
Thanks a lot!
Click to expand...
Click to collapse
Go to my guide thread here:
http://forum.xda-developers.com/showthread.php?t=2839471
Follow Sections 1-4 and then Section 8.
Transmitted via Bacon
Dear Timmaa
after Code:
fastboot oem device-info
It should have a couple of lines there, both with the flag set to true.
Please note: this will erase all user data from your device, it is best to do this before turning your phone on for the first time, otherwise make sure you backup anything important.
the fastboot is still on the screen, how do i move to step 2 ? just remove the cable? force restart or how ?
Are you saying that fastboot isn't working?
Transmitted via Bacon
timmaaa said:
Are you saying that fastboot isn't working?
Transmitted via Bacon
Click to expand...
Click to collapse
i see fastboot in english and chinese on the phone, i do the commands on cmd prompt, but nothing happens to the phone when i finish the steps.
You didn't answer my question though, is fastboot working? Are you getting a response in your command prompt when you enter commands? Try this:
Code:
fastboot devices
What's the result?
Transmitted via Bacon
yes it was working in the cmd, everything was fine, except the step of the .img
now when i start the phone, i have an icon on top saying supersu is ready to root, tap to root.
METAL66 said:
yes it was working in the cmd, everything was fine, except the step of the .img
now when i start the phone, i have an icon on top saying supersu is ready to root, tap to root.
Click to expand...
Click to collapse
Your posts are very vague, it's really difficult to help unless you're going to provide detailed information.
Transmitted via Bacon
ok i will try to make a very detailed answer, sorry. await the answer in few hours.
detailed video of how i did it
timmaaa said:
Your posts are very vague, it's really difficult to help unless you're going to provide detailed information.
Transmitted via Bacon
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=4N0evbwCNgI&feature=youtu.be
hope this works better ?
timmaaa said:
Your posts are very vague, it's really difficult to help unless you're going to provide detailed information.
Transmitted via Bacon
Click to expand...
Click to collapse
did you see my video ?
METAL66 said:
did you see my video ?
Click to expand...
Click to collapse
Yes I got time to watch your video. Everything you're doing is correct, the reason that your attempts to flash a recovery with fastboot failed is because there was a major flaw in my guide, somehow I had left the command incomplete the last time I edited it. I've fixed it now though. So, if you still have the downloaded recovery named as 'recovery.img' the correct command is this:
Code:
fastboot flash recovery recovery.img
The reason you couldn't find the 'update cm recovery' option in Developer Options is because my guide is more aimed at people who have the international model and therefore have CM11S installed on their device, 'update cm recovery' is a CM11S option and so isn't present on ColorOS.
I'm sorry it's taken me so long to get back to you, but thankyou for taking the time to make such a clear and descriptive video to outline the problem you were having. If you have any further questions I'd be happy to help you.
Transmitted via Bacon
timmaaa said:
Yes I got time to watch your video. Everything you're doing is correct, the reason that your attempts to flash a recovery with fastboot failed is because there was a major flaw in my guide, somehow I had left the command incomplete the last time I edited it. I've fixed it now though. So, if you still have the downloaded recovery named as 'recovery.img' the correct command is this:
Code:
fastboot flash recovery recovery.img
The reason you couldn't find the 'update cm recovery' option in Developer Options is because my guide is more aimed at people who have the international model and therefore have CM11S installed on their device, 'update cm recovery' is a CM11S option and so isn't present on ColorOS.
I'm sorry it's taken me so long to get back to you, but thankyou for taking the time to make such a clear and descriptive video to outline the problem you were having. If you have any further questions I'd be happy to help you.
Transmitted via Bacon
Click to expand...
Click to collapse
Thank you timmaa., it worked just few minutes before you sent the answer.
again thanks for your attention.
METAL66 said:
Thank you timmaa., it worked just few minutes before you sent the answer.
again thanks for your attention.
Click to expand...
Click to collapse
Cool, glad you got it sorted out. If you have any questions in future please don't hesitate to ask here:
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon
Thanks, now there are some problems with the network, is this normal? can it be solved?
METAL66 said:
Thanks, now there are some problems with the network, is this normal? can it be solved?
Click to expand...
Click to collapse
What kind of problem? Are you still on ColorOS or are you on CM11S now?
Transmitted via Bacon
timmaaa said:
What kind of problem? Are you still on ColorOS or are you on CM11S now?
Transmitted via Bacon
Click to expand...
Click to collapse
i am now on CM11, i guess, the color os version, is not intended for international sale? internet is not working at all ! ? i mean the sim card internet, the wifi is fine
METAL66 said:
i am now on CM11, i guess, the color os version, is not intended for international sale? internet is not working at all ! ? i mean the sim card internet, the wifi is fine
Click to expand...
Click to collapse
The ColorOS version is the same as the international version apart from missing just one LTE band. Have you double checked your APN settings? Go into Settings/Mobile Network/Access Point Names and make sure they're correct.
Transmitted via Bacon
timmaaa said:
The ColorOS version is the same as the international version apart from missing just one LTE band. Have you double checked your APN settings? Go into Settings/Mobile Network/Access Point Names and make sure they're correct.
Transmitted via Bacon
Click to expand...
Click to collapse
Thanks, it worked perfectly, i dont know why the APN settings were empty, but now it works.
perfect, thanks a lot timmaaa
No problems [emoji3]
Transmitted via Bacon
I get the following error:
Unfortunately the process com.android.systemui has stopped
The error just keeps repeating if I press OK.
What I did to get this error was:
Backup current ROM using TWRP
Flash a Lollipop ROM (that didn't work)
Restore my backup
and now I'm screwed
I've read somewhere about Italians having this issue and that it had to do with low battery level. I have now recharged my phone to 95% but still no dice And my phone is running US English (though I'm in Denmark).
I'm running CM11 M11.
Can anyone help?
Clean flash.
Transmitted via Bacon
timmaaa said:
Clean flash
Click to expand...
Click to collapse
And how would I do that if I cannot transfer zip files to my phone?
And would I be able to restore my backup afterwards?
You didn't say anything about not being able to transfer zips to your phone, but I'm assuming you mean while booted into Android because of the persistent error. TWRP 2.8.x has MTP enabled so if you connect your phone to your PC while booted into that recovery you can copy a zip across to flash. And no, you can't restore your backup afterwards, the whole point of a clean flash is that it's a clean flash, completely fresh. Plus, restoring a backup after flashing a ROM would overwrite the ROM you just flashed, making it a pointless exercise. Plus, the backup that you have is obviously corrupt and that's what's causing your problem.
In short: download a ROM zip (and gapps), flash the latest TWRP to your phone (if you don't already have it), copy the zips to your phone, perform a full wipe (system, data, cache, dalvik cache), flash the ROM + gapps, reboot and start fresh.
Transmitted via Bacon
The only backup you should be restoring using TiBu after flashing a ROM are user apps, and certainly not system apps. Restoring system apps will cause problems in 99.9% of all cases.
I'm kind of thinking that it's my TWRP that has some issue. I've tried restoring 3 or 4 different backups and they all come up with the same error.
I'll update my TWRP when I get home and hopefully get a bit further...
Gamm86 said:
The only backup you should be restoring using TiBu after flashing a ROM are user apps, and certainly not system apps. Restoring system apps will cause problems in 99.9% of all cases.
Click to expand...
Click to collapse
He's talking about a nandroid backup, not a TiBu backup.
Transmitted via Bacon
timmaaa said:
He's talking about a nandroid backup, not a TiBu backup
Click to expand...
Click to collapse
I know, just talking about restoring backups in general after flashing a ROM.
Hence why I said "The only backup you should be restoring..."
EDIT* misread the OP. My posts were indeed a bit out of context...
Did a clean install - no dice
Then did an install without gapps and then I get to the initial setup where I have to choose language. And then it reboots - over and over. It completely bypasses any indication that there is a SIM card in the phone.
When trying to restore my previous backups I also go straight to my home screen bypassing SIM unlock and phone unlock.
Any other suggestions?
Have you tried step 8 from the following thread: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Gamm86 said:
Have you tried step 8 from the following thread: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Click to expand...
Click to collapse
Either that or this automated tool:
http://forum.xda-developers.com/showthread.php?t=2970390
Transmitted via Bacon
Gamm86 said:
Have you tried step 8 from the following thread: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Click to expand...
Click to collapse
Nope. But I'm going to now Stay tuned...
Well... it's a different bootanim than CM11 - first indication that something has happened
But then Reboot from the language selection screen
I guess I'm coming to an end in terms of my phones life
kroogar said:
Nope. But I'm going to now Stay tuned...
Well... it's a different bootanim than CM11 - first indication that something has happened
But then Reboot from the language selection screen
I guess I'm coming to an end in terms of my phones life
Click to expand...
Click to collapse
Not necessarily. Do you have any signal whatsoever? Can you navigate to Settings/About Phone and see your IMEI? Don't post it here but let me know if it's still showing up.
Transmitted via Bacon
Hmm, sounds like a hardware issue to me if you can't even get passed the welcome setup without your phone rebooting... Especially after a FULL factory reset.
Does the reboot start as soon as you touch the screen? This might indicate some kind of malfunction between hardware and drivers.
Raise a ticket on the OnePlus website and request for an RMA. You might also want to file a Paypal claim to speed things up.
timmaaa said:
Not necessarily. Do you have any signal whatsoever? Can you navigate to Settings/About Phone and see your IMEI? Don't post it here but let me know if it's still showing up.
Click to expand...
Click to collapse
I can't navigate as I'm blocked by the error message. I do know my IMEI from my Google dashboard though.
I'm still puzzled by the fact that it doesn't recognize my SIM card at all.
Okay - breakthrough: I downloaded the package from this post: http://forum.xda-developers.com/oneplus-one/general/tool-oneplus-one-return-to-stock-t2970390
Ran all 3 ONEPLUS ONE - x.bat and now it has prompted me to unlock my sim card. Got through to wifi so I have higher hopes this time around Will see how it goes...
kroogar said:
I can't navigate as I'm blocked by the error message. I do know my IMEI from my Google dashboard though.
I'm still puzzled by the fact that it doesn't recognize my SIM card at all.
Click to expand...
Click to collapse
Whether you know your IMEI or not isn't the point, it's whether it's still present on your device that matters. There have been cases where the IMEI simply disappears (along with your baseband) and having no signal is a consequence of that. I hope you made a backup of your EFS at some point because it's looking like this is what's happened.
Have you tried the automated tool I linked to a few posts back?
Transmitted via Bacon
timmaaa said:
Have you tried the automated tool I linked to a few posts back?
Click to expand...
Click to collapse
Se my updated previous post
kroogar said:
Se my updated previous post
Click to expand...
Click to collapse
Ok, so you're all good now? You have mobile signal? You can see your baseband version and IMEI in the settings menu?
Transmitted via Bacon
timmaaa said:
Ok, so you're all good now? You have mobile signal? You can see your baseband version and IMEI in the settings menu?
Click to expand...
Click to collapse
Yes I see it and I can send and receive text messages.
Now I'm going to try to restore one of my previous backups again
Thanks a ton for all the help to the both of you. If I could I'd /dcc you a cold one.
kroogar said:
Yes I see it and I can send and receive text messages.
Now I'm going to try to restore one of my previous backups again
Thanks a ton for all the help to the both of you. If I could I'd /dcc you a cold one.
Click to expand...
Click to collapse
Be careful, I firmly believe it's a backup that caused this problem, and you might not be so lucky next time. I'd seriously suggest just clean flashing now or you could be inviting the devil to your doorstep.
Transmitted via Bacon
Hi All,
I've installed TugaPower V35 and currently upgrading to 36. I have an issue with the scrolling sensitivity.
When scrolling a list, like contacts, I require to use a long and really fast flick on the screen in order to get just this very small push in the scrolling speed.
In some cases I experience ghosting or weird touch issues that disabling me from typing a message.
can someone please guide me for a fix?
Thanks!
please, anyone?
Why not actually ask in the Tuga thread?
Transmitted via Bacon
because it's not rom related.
I stated what I'm running currently in order to provide somewhat useful info. but its not rom related.
Have you tried a wipe and fresh install of CM11S?
Transmitted via Bacon
I didn't. Is this really going to solve this?
If I'm on 5.0.2, then how an older version will amend this issue?
gil80 said:
I didn't. Is this really going to solve this?
If I'm on 5.0.2, then how an older version will amend this issue?
Click to expand...
Click to collapse
It isn't about going forwards or backwards, it's about undoing any modifications/bugs/firmware mismatches by returning the device to a stock configuration (flashing the fastboot stock images). If anything is going to fix your problem, this is your best bet.
Transmitted via Bacon
Ok. So from my current version, can you please direct me to the best guide on how to go back to latest stock and then at least unlock and root?
thanks!
You'll find full instructions in section 8 of my guide thread. You don't need to relock your bootloader, and just root again as you normally would.
Transmitted via Bacon
Thank you, sir!
What do you think about: http://forum.xda-developers.com/one...conv6cm11s-t2861173/post55109051#post55109051
Should I try this ROM as this is tweaked but still CM11
gil80 said:
Thank you, sir!
What do you think about: http://forum.xda-developers.com/one...conv6cm11s-t2861173/post55109051#post55109051
Should I try this ROM as this is tweaked but still CM11
Click to expand...
Click to collapse
You can try the ROM, but you still need to wipe and flash the stock images first.
Transmitted via Bacon
Yep, I thought so. Ok, I'll try that, though experience tells me that I won't get it resolved.
My wife has the OPO and I installed latest cm12 nightly and her phone doesn't have these issues... I bought mine 2nd hand and that is my punishment.
gil80 said:
Yep, I thought so. Ok, I'll try that, though experience tells me that I won't get it resolved.
My wife has the OPO and I installed latest cm12 nightly and her phone doesn't have these issues... I bought mine 2nd hand and that is my punishment.
Click to expand...
Click to collapse
It may not get it resolved, but it's still worth a try, and it's your best hope.
Transmitted via Bacon
I'm not sure if this is related, but try with boeffla kernel ( http://forum.xda-developers.com/one...ernel-boeffla-kernel-1-0-2-0-beta-09-t2899974 )
and with this firmware: https://www.androidfilehost.com/?fid=95916177934519251 (credits to katinatez, pulled from this thread: http://forum.xda-developers.com/oneplus-one/development/rom-cm11-temasek-build-t2870743 )
I'm having a similar problem and it seems to be better now. Let me know
Fede
Hey guys,
So I flashed this rom two weeks back http://forum.xda-developers.com/oneplus-one/development/rom-paranoidandroid-5-0-alpha1-t2956478
after running cm12s nightlies for a while. The capacitive keys stopped working after I flashed this rom with the PA gapps and they still don't work after trying multiple roms + relocking unlocking bootloader and flashing 44s. Kinda frustrated cause I don't know what I can do. Any ideas?
Thanks
How did you flash 44S?
Transmitted via Bacon
I first tried flashing it through twrp. Then I used the OnePlus customer support recovery tool to get it back to stock 44s. No luck zz
Sanjitha.d said:
I first tried flashing it through twrp. Then I used the OnePlus customer support recovery tool to get it back to stock 44s. No luck zz
Click to expand...
Click to collapse
By recovery tool you mean flashing with fastboot, right?
Transmitted via Bacon
Naah it was an actual tool that OnePlus customer support gave me that restored the device t to stock. But yeah I was in bootloader when I used it. Essentially it reverted the software to factory.
So I was wondering if there were any deeper settings that might have changed. The buttons still light up but don't respond to touch.
Sanjitha.d said:
Naah it was an actual tool that OnePlus customer support gave me that restored the device t to stock. But yeah I was in bootloader when I used it. Essentially it reverted the software to factory.
So I was wondering if there were any deeper settings that might have changed. The buttons still light up but don't respond to touch.
Click to expand...
Click to collapse
That's what I meant, that's flashing with fastboot. The only thing I can think of doing is completely wiping your phone including user data (back up important files first) and flashing the stock images again, but manually this time. You can find a download and instructions in section 8 of my guide thread.
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon
Alright, I've also tried manually flashing the stuff myself but I'll do it according to your guide to see if it works. You don't think it could be anything software/firmware related after that yeah? I remember there was a guy who said that he had to do a full wipe to make the cap keys to work on the initial pa thread but actually no idea on how this screwed up lel
Yeah, no luck man. I flashed everything manually but no luck zz. There's nothing else I could change to see if it's the problem yeah? I'm pretty sure the problem isnt physical as I haven't dropped it or done any harm to it.
I don't know much about kernels and stuff but that wouldnt be the problem either right?
No other stock firmwares or radios or something I havent heard about?
Sanjitha.d said:
Yeah, no luck man. I flashed everything manually but no luck zz. There's nothing else I could change to see if it's the problem yeah? I'm pretty sure the problem isnt physical as I haven't dropped it or done any harm to it.
I don't know much about kernels and stuff but that wouldnt be the problem either right?
No other stock firmwares or radios or something I havent heard about?
Click to expand...
Click to collapse
So you wiped the whole phone? Even the internal storage? If so, and the problem persists, it's suggesting a hardware problem. You could try a custom kernel though just in case, it wouldn't hurt.
Transmitted via Bacon
timmaaa said:
So you wiped the whole phone? Even the internal storage? If so, and the problem persists, it's suggesting a hardware problem. You could try a custom kernel though just in case, it wouldn't hurt.
Transmitted via Bacon
Click to expand...
Click to collapse
Sorry for the inconvenience but could you suggest a couple? (for cm12 nightlies if possible)
Thanks
And there should be no other software things I could change right?
I was reading before about oneplus not using double sided tape on their digitizers and using glue instead and as such sometimes touch responsiveness in some places might of been removed in some of the earlier models. Although oneplus said that was just a software glitch but iderrrnooooo.
Thanks for the help man c:
Sanjitha.d said:
Sorry for the inconvenience but could you suggest a couple? (for cm12 nightlies if possible)
Thanks
And there should be no other software things I could change right?
I was reading before about oneplus not using double sided tape on their digitizers and using glue instead and as such sometimes touch responsiveness in some places might of been removed in some of the earlier models. Although oneplus said that was just a software glitch but iderrrnooooo.
Thanks for the help man c:
Click to expand...
Click to collapse
Can't really suggest one because I don't use them, but you'll find them all listed in my index thread here:
http://forum.xda-developers.com/showthread.php?t=2843675
I can't think of anything else on the software/firmware side of things, everything has been wiped and reflashed.
Transmitted via Bacon
I have a similar issue. The softkeys stopped working right after i unlocked the bootloader. They light up but do not respond. can anything be done? I unlocked the bootloader via adb.