all the viperx version reboots while receiving calls! but sometimes it wont reboots....
i've changed it with other rom problem solved,but i love viperx more.... anyone know how to fix it?
Which one are you on now, the JB ? And if you are using the aosp lockscreen mod in the venom tweaks....turn it off and use the standard lockscreen. Might solve your issue
Also Make sure you have deleted the OTA update file from downloads folder.
Apparently recovery goes hyper if you dont (according to viperx thread )
A noobs solution
My One X rebooted on every incoming call, but it didn't do that from the start. So, I tried to backtrack any changes that I might have done to the setting and found that I had enabled “AOSP Lockscreen”.
After unchecking this setting everything was back to normal again.
Maybe this can be of some help to others...
webDing said:
My One X rebooted on every incoming call, but it didn't do that from the start. So, I tried to backtrack any changes that I might have done to the setting and found that I had enabled “AOSP Lockscreen”.
After unchecking this setting everything was back to normal again.
Maybe this can be of some help to others...
Click to expand...
Click to collapse
Yeah it was a problem in a (very old) previous version. Its fixed. That's why this thread is from January
Mr Hofs said:
Yeah it was a problem in a (very old) previous version. Its fixed. That's why this thread is from January
Click to expand...
Click to collapse
Wow, 3.7.0 (my version) is very old...well at least I didn't post a stupid question, just a stupid answer...
What are you saying ! Ow wow another sarcastic reply !? You have it on 3.7.0 ? Then just answer that you still have that problem. Did you install 3.7.0 with a full wipe ? Did you restore stuff from previous builts ?
I will advise you strongly to leave the sarcasm behind if it was ment that way in the first place. It won't get you far here. Then its better to give more info on your situation so we can come up with better solutions. I really hope this is a case of misunderstanding and bad communication.
Edit : I ticked the aosp lockscreen tweak and tested it, no random reboots on 3.7.0 what so ever.
Mr Hofs said:
What are you saying ! Ow wow another sarcastic reply !? You have it on 3.7.0 ? Then just answer that you still have that problem. Did you install 3.7.0 with a full wipe ? Did you restore stuff from previous builts ?
I will advise you strongly to leave the sarcasm behind if it was ment that way in the first place. It won't get you far here. Then its better to give more info on your situation so we can come up with better solutions. I really hope this is a case of misunderstanding and bad communication.
Edit : I ticked the aosp lockscreen tweak and tested it, no random reboots on 3.7.0 what so ever.
Click to expand...
Click to collapse
No, that was no sarcasm, I'm completely new to rooting phones and I thought progress was very quick and that my version had become obsolete very fast, or that I downloaded an old version.
I still have the problem, well not after disabling the setting...
I did a full wipe.
...but I flashed an old version, noticed my mistake, and then flashed 3.7.0.
The problem is that I know I did a full wipe before flashing the old version, but I'm not 100 per cent sure that I did it the second time. It sounds like missed it. So starting all over again would solve my problem? No short cuts?
Sorry about the misunderstanding!
Misunderstandings do happen in life mate, that's why i stated it as nicely i could
I think a full wipe and reinstall of 3.7.0 might solve it. I have a clean installed viper rom and tested now with several workcalls,no issue
Mr Hofs said:
Misunderstandings do happen in life mate, that's why i stated it as nicely i could
I think a full wipe and reinstall of 3.7.0 might solve it. I have a clean installed viper rom and tested now with several workcalls,no issue
Click to expand...
Click to collapse
Sorry, but it didn't solve the problem. I still get reboots when the lock screen is enabled. Even though I swiped and reinstalled.
FWIW
Hmm buggers, i can't really help you on this because i can't reproduce the reboots. Weird ! But at least thanks for testing
webDing said:
Sorry, but it didn't solve the problem. I still get reboots when the lock screen is enabled. Even though I swiped and reinstalled.
FWIW
Click to expand...
Click to collapse
I'm now pretty sure what the problem is.
It's a conflict between the "built-in" screen lock (like pin code or face recognition) and the Viper screen lock. At least on my phone it's impossible to run both (in my case Viper and pin code) simultaneously.
HTH
webDing said:
I'm now pretty sure what the problem is.
It's a conflict between the "built-in" screen lock (like pin code or face recognition) and the Viper screen lock. At least on my phone it's impossible to run both (in my case Viper and pin code) simultaneously.
HTH
Click to expand...
Click to collapse
I’ve been a Beta tester for a an American software company during a period of 7-8 years and I’ve written some simple plug-ins for their web design software. So, I tried to use that experience to do some testing and trying to minimize the number of factors that could trigger the problem.
What I did was a factory reset, a wipe and then I installed 3.7.0.
Before installing any apps, launchers and whatnot, I tried running the phone with both pin code and Viper screen lock enabled.
The result was the same every time.
I then tried to enabled the two settings in different orders, first pin code, then Viper and vice versa, but to no avail.
My conclusion, whatever it’s worth, is that it’s easy to get a problem when two pieces of code are trying to manage the same event. Maybe it’s possible to find the line/lines in the code that might trigger the conflict..?
…or maybe Viper just don’t like Sweden/Swedes?
Well, with a little (bad) luck maybe some other people run into this problem, but there might be very few of us who use Viper in this type of configuration…
I don’t think I can add anything more than this, so I’ll leave this issue in the competent hands of those who wrote Viper.
Thanks!
Related
Hello guys, I have to ask you a question that I can not resolve for months.
I have a HTC TOUCH PRO, and every kernel I try to always have problems.
At first the device works well and is also very fast, but hopelessly after a while it stops. When you first start can last hours and then crash, but already the second hangs after a few seconds.
I've tried almost every kernel, even the "msm-htc-linux-20101204_005141-package.tar" by the comments that seems to be the best for my device, but nothing. I'm desperate and I do not know what to do.
Can you tell me how to solve this?
Waiting for reply.
Thanks to everyone that I will respond.
I'm not sure what your problem actually is. Sounds like the system_server bug... Make a call to voicemail, phone should speed back up.
Also, the newest kernel is 1253. The autobuild service has fallen behind GIT, see this thread to get the most up-to-date GIT commits.
i must only update with this kernel?
master9 said:
i must only update with this kernel?
Click to expand...
Click to collapse
The kernel (zImage) goes hand-in-hand with the modules file.
Still not sure what you mean tho.
The problem is very simply. Any kernel I use the phone freezes.
This kernel (1253) is very very fast, but nothing, however, the phone freezes.
master9 said:
The problem is very simply. Any kernel I use the phone freezes.
This kernel (1253) is very very fast, but nothing, however, the phone freezes.
Click to expand...
Click to collapse
You say it's fast, but the phone freezes...?
Where does it freeze?
XDAndroid is far from 'stable'...
Us Touch Pro owners can't use 1253 due to certain things reported not working with this kernel. 1243 (i believe 124?) works fine.
djdafreund said:
Us Touch Pro owners can't use 1253 due to certain things reported not working with this kernel. 1243 (i believe 124?) works fine.
Click to expand...
Click to collapse
O___o I did not realize that. All RAPH's...? Do we have logs? I need information man!
I'm not sure about all raph's per-say, but in the other normal FRX03 thread (within the past 4 pages i believe, if that) there was a user or two complaining about something not working (i wish i remembered, maybe data) not working, and i told them to revert back because of issues the new kernel(s) had, and he reported back "thanks, that fixed it." So SOMETHING is wrong for sure with Touch Pro's, but don't know for sure if it effect's diamond user's also. Sorry.
Update- Now i remember, it's http://forum.xda-developers.com/showpost.php?p=10590080&postcount=4072, the screen shifting problem. It shift's the screen over to the left by so many pixels, and get's shifted more and more as your using it. It was actually like 14-15 pages back (too much traffic, LOL), but since i use camera a lot, i am using 1214 (last recent one VC did) as i use his camera build, so i can take picture's. I did witness the screen shifting myself in my separate FRX03 build i have (since just use the camera build though solely). But was using 1241 i believe for my non-camera build.
djdafreund said:
I'm not sure about all raph's per-say, but in the other normal FRX03 thread (within the past 4 pages i believe, if that) there was a user or two complaining about something not working (i wish i remembered, maybe data) not working, and i told them to revert back because of issues the new kernel(s) had, and he reported back "thanks, that fixed it." So SOMETHING is wrong for sure with Touch Pro's, but don't know for sure if it effect's diamond user's also. Sorry.
Update- Now i remember, it's http://forum.xda-developers.com/showpost.php?p=10590080&postcount=4072, the screen shifting problem. It shift's the screen over to the left by so many pixels, and get's shifted more and more as your using it. It was actually like 14-15 pages back (too much traffic, LOL), but since i use camera a lot, i am using 1214 (last recent one VC did) as i use his camera build, so i can take picture's. I did witness the screen shifting myself in my separate FRX03 build i have (since just use the camera build though solely). But was using 1241 i believe for my non-camera build.
Click to expand...
Click to collapse
Oh right, that. Screen shifting seems isolated to the RAPH800 and DIAM500. Probably RAPH500 as well, and I'm not sure what the other DIAM is... perhaps there is a DIAM800, not sure. Either way, seems to only be the CDMA devices.
But of course LOL. I personally love my Touch Pro, but WOULD love to upgrade if i had the money. But yeah, the dreaded shift problem til it's fixed. Not a BIG deal for now, since previous kernals will hold us off til that's fixed.
Nothing, i have the same problem
master9 said:
Nothing, i have the same problem
Click to expand...
Click to collapse
You still haven't properly elaborated on your actual problem. Vagueness will get you nowhere, except frustrate people.
I did not understand what you mean. I'm trying everything I was recommended and I can not solve this problem. I try to re-explain.
The problem is very simple: the phone, any kernel I mountains, after a couple of minutes it stops. I can not wait to give other details because the problem is just that.
Everything works (including wireless), the system is fast but is hopelessly blocked.
When you first start working for hours, just minutes after the second start.
master9 said:
I did not understand what you mean. I'm trying everything I was recommended and I can not solve this problem. I try to re-explain.
The problem is very simple: the phone, any kernel I mountains, after a couple of minutes it stops. I can not wait to give other details because the problem is just that.
Everything works (including wireless), the system is fast but is hopelessly blocked.
When you first start working for hours, just minutes after the second start.
Click to expand...
Click to collapse
Seems to be a pretty big language barrier here... "any kernel I mountains"...?
So has Android ever worked for you? What build(s) have you tried?
Sorry, my fault: "any kernel I mount".
Sorry but i can't speak english very well.
I have try a lot of build: kenya, cyanmod, FRG83.R6 ecc..
but the result don't change.
master9 said:
Sorry, my fault: "any kernel I mount".
Sorry but i can't speak english very well.
I have try a lot of build: kenya, cyanmod, FRG83.R6 ecc..
but the result don't change.
Click to expand...
Click to collapse
What about FRX03? I can't really help you with any build but that one - if you're using a different build, you'll need to get help in those threads. Generally if you just throw up a post like this, use FRX03 (or AOSP, whatever) as your base to test off of.
If it works in that build, but doesn't work in one of the others - then it's that build. If they fail in both builds, then it's a general issue with Android - or, you've just done something wrong .
I also think the same thing because no version I work, all give the same problem.
This is my steps:
1 - Extract all the package (eg superfroyo) to the root of SD, also replace the kernel (of course renaming the new kernel in "zKernel") and also the module, copying them always in the root.
2 - Put the file "startup.exe" HARETSTARTUP of the root and put the file "startup.exe" contained in INSTALL-NPKINSTALL in startups.
3 - Starting in the INSTALL file inside the folder NPKINSTALL.
4 - After the procedure I restart the phone and after i start the file "HARET".
At this point the system starts, it's fast and it all works perfectly but crashes for no reason without giving me the opportunity to do anything, I can only do a soft reset.
Kindly tell me if something wrong in the procedure.
Keep in mind, most neopeek variants require two partiations to be setup as primary (one FAT32 and one EXT2). You might find it a tad difficult in finding someone to help you troubleshoot your process unless you seek help from with-in the thread that you downloaded superfroyo or any other neopeek variants. It is rare to find but then again, you could just as easy try out FRX04 and post your feedback in that thread too. See THIS post for info on downloading the FRX04 update file but you will probably need to downoad THIS package first, then update the system.ext2, rootfs and kernel package after the fact. Stinebd has links for the rootfs in his sig.
n-Joie! (Enjoy)
master9 said:
I also think the same thing because no version I work, all give the same problem.
This is my steps:
1 - Extract all the package (eg superfroyo) to the root of SD, also replace the kernel (of course renaming the new kernel in "zKernel") and also the module, copying them always in the root.
2 - Put the file "startup.exe" HARETSTARTUP of the root and put the file "startup.exe" contained in INSTALL-NPKINSTALL in startups.
3 - Starting in the INSTALL file inside the folder NPKINSTALL.
4 - After the procedure I restart the phone and after i start the file "HARET".
At this point the system starts, it's fast and it all works perfectly but crashes for no reason without giving me the opportunity to do anything, I can only do a soft reset.
Kindly tell me if something wrong in the procedure.
Click to expand...
Click to collapse
Again, you're using funky version. As R^72 said, get help with those versions in that thread.
If you want help, at least try FRX03. You haven't even given it a shot. Then you can update to FRX04, and if that all works - then try something more complicated like a Neopeek build!
I need an opinion on this one. I've looked for this problem but it seems not to be clear what is causing it. I have Wildfire S (EU) Marvel. The device is S-On but I unlocked the boot loader and installed CWM. I've already tried several ROMs but it doesn't help to solve the issue. The problem appears during making the call - the screen goes black when you put the phone next to head and after that doesn't want to wake up. The only thing that wakes it up is putting it next to strong light source so I think the light sensor is the one to blame. However automatic backlight seems to be working fine. I really hope that it is not hardware problem. Please give any suggestion to try solving this problem. I would even go for the option to shut down somehow the light sensor because restarting phone after each call is kind of annoying. Thank you in advance for any help you can provide. Sorry for such a long introduction.
anubius said:
I need an opinion on this one. I've looked for this problem but it seems not to be clear what is causing it. I have Wildfire S (EU) Marvel. The device is S-On but I unlocked the boot loader and installed CWM. I've already tried several ROMs but it doesn't help to solve the issue. The problem appears during making the call - the screen goes black when you put the phone next to head and after that doesn't want to wake up. The only thing that wakes it up is putting it next to strong light source so I think the light sensor is the one to blame. However automatic backlight seems to be working fine. I really hope that it is not hardware problem. Please give any suggestion to try solving this problem. I would even go for the option to shut down somehow the light sensor because restarting phone after each call is kind of annoying. Thank you in advance for any help you can provide. Sorry for such a long introduction.
Click to expand...
Click to collapse
long introduction is far better than a short one ...
did you install rom propperly (factory reset/cache clean/dalvik clean)?
did you try using any other dialer app just to check ?
Like this, or this
I think i have read about such problem somewhere, if i find it i will post you the link to it...
also here are some apps to check your proximity sensor :
ProxyLightTester i couldn't find it on market. (not tested)
Proximity Sensor Finder Market link. (tested) and it will report 'all or nothing'
b02 said:
long introduction is far better than a short one ...
did you install rom propperly (factory reset/cache clean/dalvik clean)?
did you try using any other dialer app just to check ?
Like this, or this
I think i have read about such problem somewhere, if i find it i will post you the link to it...
also here are some apps to check your proximity sensor :
ProxyLightTester i couldn't find it on market. (not tested)
Proximity Sensor Finder Market link. (tested) and it will report 'all or nothing'
Click to expand...
Click to collapse
Hi, Thanks a lot for suggestions. So it seems to me that proximity and light sensors work. I tried several software including the one you suggested and the proximity and light sensor respond ok. I also tried different dialer but it doesn't help. I have no idea what can it be. I am thinking to put the device back to the factory state and maybe install official ROM but I am not sure if this will solve the problem. Thank you again for helping. And your device never had this problem?
Never had that problem.. Try reflashing w/o any app2sd gapps and stuff, just clean new rom and try it..
Sent from my HTC Wildfire using xda premium
anubius said:
I am thinking to put the device back to the factory state and maybe install official ROM but I am not sure if this will solve the problem.
Click to expand...
Click to collapse
Before you do that try this build.prop file and see if it helps...Just remove the ".txt" and set your permissions same as the old build.prop file you renamed.
Tera Tike said:
Before you do that try this build.prop file and see if it helps...Just remove the ".txt" and set your permissions same as the old build.prop file you renamed.
Click to expand...
Click to collapse
Thank you guys for all the suggestions I followed your advices but the phone simply refuses to wake up after the call. I am trying to go back to factory default since this is my last hope. Really confused what is causing it.
Hello guys,
I searched for this issue on the forum but it seems that nobody encountered anything like this before.
To begin, I would like to mention that I am running the latest CyanogenMod 11 nightly on an HTC One X (Tegra version).
Since somewhere right after the latest M release, I've been having a couple of issues with the phone:
#1: From time to time, I get a "Lockscreen" isn't responding dialog and it asks whether I want to "Wait" or "Close". Well, if I click on "Wait" the phone becomes unresponsive, as if something was running in the background so hard that it would eat up all the ram and would choke the CPU;
If I click on close, it's a hit or miss situation: sometimes it restarts the lockscreen and takes me back to it, even though I previously unlocked the device and sometimes the phone becomes unresponsive as before.
#2: Besides what I mentioned above, the phone sometimes becomes unresponsive without warning and every time this happens, it always looks and feels as if something is chocking the ram and CPU.
Have any of you guys encountered something like this before and if yes, what can I do to fix it?
If not, is there a way in Android, to pull up a log similar to the Windows Task Manager, that would tell me exactly what was running in the background at a given time and how much memory/CPU cycles it was actually using?
Thank you in advance.
Try your stock rom for a while.
Mr Hofs said:
Try your stock rom for a while.
Click to expand...
Click to collapse
Thank you for your reply however, I haven't used sense roms in a while now, plus, it's a downgrade from KitKat, which is why I am not that fond of this option.
On a different note, I just installed the latest nightly "clean", namely with a full factory reset from recovery, flashed boot.img in fastboot and installed the latest GApps from PA.
I don't get the "Lockscreen is not responding" dialog anymore, but from time to time, the lockscreen still closes and now it either resets on its own, or it forces the OS to reset, after which com.android.systemui starts force closing indefinitely and the phone afterwards requires a hard reset.
Has anyone else encountered something similar? Any help?
I'm saying to use the stock rom for a while just to rule out hardware issues !
Mr Hofs said:
I'm saying to use the stock rom for a while just to rule out hardware issues !
Click to expand...
Click to collapse
Cool, will try that. Thanks.
What kind of hardware issues do you think could cause an issue like this?
Not sure but why stick to a rom that is not working properly, go for safe and go for stock if the issue is gone you can search for the issue that is caused by a rom !
Mr Hofs said:
Not sure but why stick to a rom that is not working properly, go for safe and go for stock if the issue is gone you can search for the issue that is caused by a rom !
Click to expand...
Click to collapse
Fair enough! Thank you!
sometimes my oneplus 3 restart without reason, i have installed the oxygenOS 3.2.7 do someone else have this issue , its just me or? ill post a battery log also.
its really annoying and dunno what do =/
My congrats for the great autonomy ?
The info you've sent are not enough to analyze your reboot issues.
1) Have you rooted your device?
2) If yes, are you running SuperSU, Kingroot, Phh's Superuser? What version?
3) What the apps that are getting root permissions?
4) Are you using Xposed? What version (e.g. v86.6 systemless with Magisk v8, the v86 stock)?
5) Have you tweaked or replaced the stock kernel?
Simone98RC said:
My congrats for the great autonomy
The info you've sent are not enough to analyze your reboot issues.
1) Have you rooted your device?
2) If yes, are you running SuperSU, Kingroot, Phh's Superuser? What version?
3) What the apps that are getting root permissions?
4) Are you using Xposed? What version (e.g. v86.6 systemless with Magisk v8, the v86 stock)?
5) Have you tweaked or replaced the stock kernel?
Click to expand...
Click to collapse
everything is stock, still new of android so and ty
athais said:
everything is stock, still new of android so and ty
Click to expand...
Click to collapse
Much strange.
I'm having an heavily modded OP3 with OOS v3.2.7, never encountered instability.
You should try factory reset asap, there's nothing you may do, since device is completely stock and works for most users.
I can't give you more help, sorry ?
Simone98RC said:
Much strange.
I'm having an heavily modded OP3 with OOS v3.2.7, never encountered instability.
You should try factory reset asap, there's nothing you may do, since device is completely stock and works for most users.
I can't give you more help, sorry ?
Click to expand...
Click to collapse
do you think an update could resolve the issue? in case i could wait an OTA update and if dont fix this issue try a factory reset
athais said:
do you think an update could resolve the issue? in case i could wait an OTA update and if dont fix this issue try a factory reset
Click to expand...
Click to collapse
Not, because OOS is working well for most users, so there is no "fix reboot issues" in any todo list.
Go with factory reset, when you find the needed time.
If problems still persist, contact OnePlus and explain the issue.
I think that some upgrade maybe the cause of your troubles, due to massive change of stuff that the end-users can never see.
You know that Samsung updates often make device slower or keep crashing some system app?
Why excluding that OnePlus have done (involuntary) the same?
Updates are not always guarantee of stability, especially with firmware different than Google stock.
Simone98RC said:
Not, because OOS is working well for most users, so there is no "fix reboot issues" in any todo list.
Go with factory reset, when you find the needed time.
If problems still persist, contact OnePlus and explain the issue.
I think that some upgrade maybe the cause of your troubles, due to massive change of stuff that the end-users can never see.
You know that Samsung updates often make device slower or keep crashing some system app?
Why excluding that OnePlus have done (involuntary) the same?
Updates are not always guarantee of stability, especially with firmware different than Google stock.
Click to expand...
Click to collapse
thank you for all yours advice man, i came up with , waiting next OTA, then try factory reset, and if not solve this issue well, OP support is the way suppose , thank you again !
btw just asking in developer options i saw suspension mode active, can be this that cause truble ?
Flash another room
Seems to be an issue with OOS, I had the same problem, and flashed MIUI 8 and had 0 reboots. But when I flashed Fredoom OS based on OOS 3.2.7 my phone kept rebooting.
athais said:
sometimes my oneplus 3 restart without reason, i have installed the oxygenOS 3.2.7 do someone else have this issue , its just me or? ill post a battery log also.
its really annoying and dunno what do =/
Click to expand...
Click to collapse
Are you using a case? I had a cheap eBay clear case on my phone and it wasn't moulded properly over the power button, there was no indent on the inside for the button to sit in so it used to turn off in my pocket and back on later and produced battery graphs similar to yours.
Hope this is a help.
athais said:
thank you for all yours advice man, i came up with , waiting next OTA, then try factory reset, and if not solve this issue well, OP support is the way suppose , thank you again !
btw just asking in developer options i saw suspension mode active, can be this that cause truble ?
Click to expand...
Click to collapse
Did your problem solved? I am having same problem.
I have the same problem. I am currently on 3.2.8 and also had this problem on beta 9. Few days ago it happened in front of me, the phone was on the desk nothing running in the background. That was kind of the soft reboot, didn't triggered my locked sim, (my sim card is locked needs to enter PIN when phone startup) and after that I checked Settings=>About Phone=>Status, the uptime didn't affected too, seemed nothing was happened. I think this also happened to some other people but they just didn't realize it.
Karthi91 said:
Did your problem solved? I am having same problem.
Click to expand...
Click to collapse
Are you running the latest 3.2.8 and if yes have you tried a factory reset?
Sent from my OnePlus3 using XDA Labs
bonham1988 said:
Are you running the latest 3.2.8 and if yes have you tried a factory reset?
Click to expand...
Click to collapse
Yes.. I'm on 3.2.8 and did factory rest also. No use
---------- Post added at 06:35 AM ---------- Previous post was at 06:32 AM ----------
athais said:
sometimes my oneplus 3 restart without reason, i have installed the oxygenOS 3.2.7 do someone else have this issue , its just me or? ill post a battery log also.
its really annoying and dunno what do =/
Click to expand...
Click to collapse
Same for me. Is your problem solved? Please help me. It is really annoying. I have Pin setup for restart so when boot happens in night, if no input for pin phone stays off.
Can this be related to SIM carrier:Radio drivers?
I dont think so.. Because i havent changed Sim
Karthi91 said:
I dont think so.. Because i havent changed Sim
Click to expand...
Click to collapse
Try using non 4G/LTE SIMS.
I am facing the same problem.
My device is at service center.
Day one:No reboots.I asked them to put some SIM & then check.
I did that after reading your post. No luck. Are they replacing it? How many days since it is in service center?
Facing problem from last 2 weeks.
I submitted once last week.They clean flashed older rom.Worked fine for one day,then reboots started again.
Then this technician had remote session and flashed the rom OnePlus3_16_A.17_161118(OOS 3.2.8):Reboot frequency went too high.
Had to go to Service center for diagnose. 2 days now.No proper response from them.
I had the same issue from several days now, wiped cache, did factory reset, wiped data, nothing worked, I read somewhere that let battery drain down to 0 and then full charge removes electricity or static from the phone, and that may cause random reboots, gonna try that
Belyakovni said:
I had the same issue from several days now, wiped cache, did factory reset, wiped data, nothing worked, I read somewhere that let battery drain down to 0 and then full charge removes electricity or static from the phone, and that may cause random reboots, gonna try that
Click to expand...
Click to collapse
Seriously? That sounds like one of those hilarious Microsoft Answers sort of posts! Running the battery down will not get rid of "electricity or static from the phone", apart from anything else the battery protection circuit would not allow the battery to drop to zero volts as it's not good for li-on batteries.
The Oneplus 3 seems to like to soft restart, mine sometimes decides to do it 3-4 times a night (rarely during the day) and then is fine for awhile. Tell tale sign is the battery graph showing large gaps in the usage pattern. I would suggest that there is an inherent firmware issue judging by the number of people reporting the same issue on a number of different forums.
Hi,
Until yesterday i had LineageOS and everything worked fine.
I installed ViperOS and everything ok too, but without root. But then i made a new installation with superSU this time, and I dont know why NFC turns on and off constantly, even the menu settings that normally shows NFC is gone, I can see NFC state just in quick settings.
I dont think that is ViperOS rom problem, because nobody reported that issue.
I made the wipes cache, davilk, data and system few times, and problem continues. Plus, there are more things that continue from previous installations, and I dont know why because i made clean installations. For ex. it asks for patron before start android always after making clean installations...
Because of that, i think that for everything back to normal state, maybe there is a way to make wipes deeply that i dont know... also for NFC come to normal work, is that so?
Please, give me any help... Thanks
I solved it doing this:
I have installed rom stock by twrp, next one:
https://forum.xda-developers.com/mot...l-sim-t3620551
Then i installed ViperOS. NFC is working ok again.
Regards
xuncall said:
I solved it doing this:
I have installed rom stock by twrp, next one:
https://forum.xda-developers.com/mot...l-sim-t3620551
Then i installed ViperOS. NFC is working ok again.
Regards
Click to expand...
Click to collapse
Glad to hear you solved your issue, but your question should have been in the Viper OS thread.
Jimi Mack said:
Glad to hear you solved your issue, but your question should have been in the Viper OS thread.
Click to expand...
Click to collapse
Thanks, but i dont agree. As i said, ViperOS was not the main aspect of my problem, it was a problem with the phone.