My OP3 starts randomly freezing for some reason and i have to boot it up again.
It happens every 15 minutes
Im on complete Stock without any changes on the latest oos.
Is there anyone experiencing anything simillar and got it fixed?
Happens to me too. Like the touch screen freezes but the buttons work... Is that the same for others?
Never happened for me on a stock build.
Have you tried clearing the cache?
---------- Post added at 01:03 PM ---------- Previous post was at 01:02 PM ----------
Chimechime said:
Happens to me too. Like the touch screen freezes but the buttons work... Is that the same for others?
Click to expand...
Click to collapse
This sounds like an ANR - Application not responding. Does this happen for a specific app?
Related
I have been reading through some of the threads here trying to find solution for my problem and I cant seem to figure out which of the possibilties it is. Ever since I flashed Vicious 4.1.1, I have in call troubles. Sometimes I cant hear them sometimes they cant hear me The call will be going fine then the problem just randomly starts. I tried calling myself and making a steady noise and found that after about 2 sec I started cutting out. I always have 3 if not 4 bars. I read a thread that talked about a mic issue but being that I never had this before jelly bean I have trouble believing that to be the problem. Is there a radio update that is needed going to 4.1.1? Does anyone else have this problem? Does any one have a solution for me? Attached is my phone specs
bump
if problem exists when you are stock then it sounds like you are up for a warrantee replacement.
---------- Post added at 11:40 AM ---------- Previous post was at 11:34 AM ----------
or if you feel especially adventurous, you could try reseating the connector in this photo http://guide-images.ifixit.net/igi/D5VWDvSZo2D3VQQB.thumbnail
There are no waranttee seals. 8)
animal24 said:
if problem exists when you are stock then it sounds like you are up for a warrantee replacement.
---------- Post added at 11:40 AM ---------- Previous post was at 11:34 AM ----------
or if you feel especially adventurous, you could try reseating the connector in this photo http://guide-images.ifixit.net/igi/D5VWDvSZo2D3VQQB.thumbnail
There are no waranttee seals. 8)
Click to expand...
Click to collapse
the problem only started after installing JB
I'm running twa_priv's JB rom (20120801) and am one of only a few people seeing a persistent crash when sliding the volume to zero (not muting, actually sliding down to zero). It's only a nuisance bug since it's easy to avoid but it's bothering me that barely anybody else can reproduce it. I've seen a few other reports in the various JB rom threads so it doesn't seem to be rom specific.
I did an 'adb logcat' and reproduced the crash several times using both Volume Control (app by RubberBigPepper) and the regular volume widget in the status bar (tablet mode). Maybe some clues in there for those smarter than I. The entire logcat is attached. Each time the crash happens the first logged event looks like this:
E/AndroidRuntime( 1425): FATAL EXCEPTION: main
Is this helpful? Anything else I can do to narrow this one down? Does anybody else care? =)
Thanks!
-S
I am also using twa_priv's JB [20120801]. Sliding volume to zero does not crash on my KF, but when I set the volume to mute, I cannot turn it back on. I need to reboot the device to get the sound back.
I'm running the same build and have neither of your 2 issues go figure eh??? You both may benefit from a good wipe front to back and a fresh flash
---------- Post added at 05:30 AM ---------- Previous post was at 05:26 AM ----------
Thepooch said:
I'm running the same build and have neither of your 2 issues go figure eh??? You both may benefit from a good wipe front to back and a fresh flash
Click to expand...
Click to collapse
In fact I have been sitting here running the volume button up and down and muting it while watching hulu trying to duplicate what your experiencing
for twenty minutes without so much as a hiccup
Thepooch said:
I'm running the same build and have neither of your 2 issues go figure eh??? You both may benefit from a good wipe front to back and a fresh flash
---------- Post added at 05:30 AM ---------- Previous post was at 05:26 AM ----------
In fact I have been sitting here running the volume button up and down and muting it while watching hulu trying to duplicate what your experiencing
for twenty minutes without so much as a hiccup
Click to expand...
Click to collapse
I'm not able to replicate the problem either.
Thepooch said:
I'm running the same build and have neither of your 2 issues go figure eh??? You both may benefit from a good wipe front to back and a fresh flash
---------- Post added at 05:30 AM ---------- Previous post was at 05:26 AM ----------
In fact I have been sitting here running the volume button up and down and muting it while watching hulu trying to duplicate what your experiencing
for twenty minutes without so much as a hiccup
Click to expand...
Click to collapse
As I am new to JB on my kindle, the volume issue for me might due to my misoperation. I really enjoy this ROM now.
Well, i think there must be some audio bug, because since i flashed i haven't had audio on build 8-1-2012. And even on build 7-22-2012 a reboot would cause audio loss. I would have to fix it by randomly playing with volume in settings.
I would really want HELP with this problem.
Sent from my MB855 using Tapatalk 2
I also have this volume problem with my Kindle. Did you find any solution or roms which do not have this bug?
I did a full wipe several weeks ago and haven't seen this crash since then. Still using twa_priv's ROM on my KF.
-S
Sent from my Galaxy Nexus using xda premium
I did a full wipe several weeks ago and haven't seen this crash since then. Still using twa_priv's ROM on my KF.
Click to expand...
Click to collapse
It worked. I did a full wipe (External, System, Factory Reset, davlik cache and cache) and the problem went away
Thanks
Once a mute, always a mute
songzi said:
I am also using twa_priv's JB [20120801]. Sliding volume to zero does not crash on my KF, but when I set the volume to mute, I cannot turn it back on. I need to reboot the device to get the sound back.
Click to expand...
Click to collapse
I am experiencing the same issue with the mute button in the notification bar. If I press mute, the little speaker will get a slash through it indicating that it is muted. Pressing the button again will not unmute it. I have to go into the settings and turn the volume up with the sliders. Sometimes i have to do this two or three times before the volume settings will take. Even with the volume turned back up, the volume indicator in the notification bar still shows the device being muted. A reboot will correct. Any thoughts?
Edit: It is doing it in the 09132012 as well as the previous build.
Moved to Q&A
So when I lock the screen and as it turns black, there is a white stripe on right side of the screen. It appears on every rom I install. I don't know if this is normal or it just me.
if it stays its some kind of light spillage just guessing maybe from a bad led display and its just you I have never seen it
---------- Post added at 01:41 AM ---------- Previous post was at 01:41 AM ----------
hardware...
its goes away after it's locked, it doesn't really affect the tablet but its a hell of an eye sore.
oh i forgot there's no issue with the stock rom. i always wipe every thing every time .
very interesting but I would say a harmless issue on a lg lcd
I need help because my phone is maxed out at 1593 mhz which is the max clock speed for the cpu small cluster. The big cluster is working fine. This is NOT a result of KingKernel, it happens on any kernel I run. The cpu usage goes up to 95 or sometimes 100%. I think the task is play services through a battery historian I took, but I'm not sure.
I am currently on Android P preview 5 and it is a literal hot mess. I have reported this to google, but I need some immediate help. Thanks in advance
This happened randomly, it wasn't right after I flashed P, it worked properly before
kingbri said:
This happened randomly, it wasn't right after I flashed P, it worked properly before
Click to expand...
Click to collapse
Doing the same thing on my phone, I've been trying to troubleshoot it, also on dp5. Tried setting it lower in ex kernel manager and resets to 1593 every time. Without even rebooting. Probably play services needs an update....
---------- Post added at 10:53 PM ---------- Previous post was at 10:49 PM ----------
I flashed thedp5 to the b slot and it seems to be trying to settle down now. I had the wrong bb and bl on that slot.
Bryanx86 said:
Doing the same thing on my phone, I've been trying to troubleshoot it, also on dp5. Tried setting it lower in ex kernel manager and resets to 1593 every time. Without even rebooting. Probably play services needs an update....
---------- Post added at 10:53 PM ---------- Previous post was at 10:49 PM ----------
I flashed thedp5 to the b slot and it seems to be trying to settle down now. I had the wrong bb and bl on that slot.
Click to expand...
Click to collapse
It's starting to settle down when flashing from B to A (I had it on B before) good to hear that this isn't happening to only me.
deleted
kingbri said:
It's starting to settle down when flashing from B to A (I had it on B before) good to hear that this isn't happening to only me.
Click to expand...
Click to collapse
Yeah, and it seems my fast charge isn't working as well. Gamn doogle!
Has anyone fixed this? I had this issue since forever and am on lineage os 17.1
When I got my device, the vibration was strong. Now I have no vibration whatsoever. All settings are good. I can't even get haptic feedback. I searched in Google and saw a couple others with this problem. Sounds like a hardware issue to me. Anyone else experiencing this yet? SM-N975F/DS
Dial *#0*# and run vibration test. That should tell you if it's hardware. If it works I would reset it, if it doesn't I would sent back.
pete4k said:
Dial *#0*# and run vibration test. That should tell you if it's hardware. If it works I would reset it, if it doesn't I would sent back.
Click to expand...
Click to collapse
Neat trick. No it doesn't work. I've been hearing many more cases of this popping up. I suspect there'll be many more to come.
Yeah, same to me. I was so convinced that mine is an isolated case that I did not even thought to search for similar threads.
Mine does not work either when running Samsung test trick (*#0*#)
---------- Post added at 12:29 PM ---------- Previous post was at 12:23 PM ----------
awakener777 said:
Neat trick. No it doesn't work. I've been hearing many more cases of this popping up. I suspect there'll be many more to come.
Click to expand...
Click to collapse
You mention "hearing" about many more cases... Where?
big_ipaq said:
Yeah, same to me. I was so convinced that mine is an isolated case that I did not even thought to search for similar threads.
Mine does not work either when running Samsung test trick (*#0*#)
---------- Post added at 12:29 PM ---------- Previous post was at 12:23 PM ----------
You mention "hearing" about many more cases... Where?
Click to expand...
Click to collapse
There's a lot of you look through here
https://us.community.samsung.com/t5/Note10/bd-p/Note10
Any answers?
So my note 10+ started doing this this morning. I do the phone test and it vibrates, but is weaker. Keyboard vibrate doesn't work. Notification vibrate doesn't work, nothing else vibrates. Not sure what is going on.
Edit: looks like something turned my vibration sensitivity way down. Working now!
No problem on my N975F/DS with vibration after official Android 10 update. Vibration test, keyboard feedback, vibrate on phone call also work as before...
@OnnoJ same problem, after update, vibration stop working... altough it could be that it didnt work before i am not 100% sure