I think i found out how to provoke the /init bug.
Maybe this is only one way the bug can be triggered, at least it is something to start with.
I already posted my experience at AndroidPit.
The bug appears to be related to the hardware menu and back keys with respect to my HTC Legend.
Pressing both buttons at the same time causes the bug to appear.
Doing the same with USB-Debugging activated causes the phone to vibrate a few times. After a short while it works perfectly.
If,you have Watchtower e.g. installed go to Processes and try it.
With USB-Debugging deactivated you can see how the /init process shows up just seconds after pressing "menu" and "back" at the same time.
Didn't find anything to the cause yet, so I hope it does help ... maybe even HTC in case they are reading this.
Is no one able or willing to confirm this?
Why is no one interested in finding out what causes the /init bug?
Why is not everyone experiencing the problems? Is it maybe a spwcial app
Related
I've read the other threads about this issue, it seems to be related to the keyboard for me, or maybe that's a completely different issue.
The most annoying thing for me, more so than the touchscreen failing, is something where it's like a key is being pressed repeatedly, very fast. For example, the start menu was opening and closing extremely rapidly. During this time, the touch screen might work, but anything I open is closed immediately. Even hard resets, taking out the battery while the device is on don't help. And when it eventually subsides, the touchscreen isn't working. The other thing that opens and closes rapidly is the task manager that comes with a lot of firmwares (Shaps for one).
I'm planning on seeing if I can take this device in, seeing as how we bought it not long ago. Just wondering as to the causes, as I've spent quite a few hours trying and trying to fix this.
When I pull out the keyboard, at the point when it goes 'click', that will sometimes trigger the rapidly flicker start menu and such issue.
The thing about the task manager puzzles me though - the start menu button is a hardware key, but there isn't one for the task manager in the upper right. So what would be triggering that?
Technology can be so bloody annoying.
Thanks for any answers,
-David
I find that my Minis' on/off button is unresponsive occasionally and I was wondering if anyone else felt theres was also?
Ive only had this issue when the phones locked and I bring it in and out of showing me my status. It appears the bottom icons have to light up before it will react to my press of the on/off button again.
Same for me ! Sometime I need to remove battery to restart using my HD MINI ...
Any solution ?
hi there
i think i have bad news!!!
my phone is Unresponsive sometime and some time turn display on show me you want turn off divece???
do you remember this problem on Nexus one????
i think our PDA had that problem too!!!
it's just my idea but i think it's true!!
any idea??
brutaled said:
I find that my Minis' on/off button is unresponsive occasionally and I was wondering if anyone else felt theres was also?
Ive only had this issue when the phones locked and I bring it in and out of showing me my status. It appears the bottom icons have to light up before it will react to my press of the on/off button again.
Click to expand...
Click to collapse
I have the same problem, sometimes, the button is not responsive. There should be a solution for it. Someone has to report to htc.
I have the same problem, i think that it is caused by either to many running applications or by a application that hangs.
for the most i just have to wait a minute or two and then it works again.
Last time i connected the charger, it also worked and i have also tried to call the phone from another phone. it also worked.
/Floffy
Floffy said:
I have the same problem, i think that it is caused by either to many running applications or by a application that hangs.
for the most i just have to wait a minute or two and then it works again.
Last time i connected the charger, it also worked and i have also tried to call the phone from another phone. it also worked.
/Floffy
Click to expand...
Click to collapse
yes... I think it's because of many programs... I have this when I'm doing something and I push the button fast to turn of the screen and suddenly remember I forgot something and push it again to turn on... I think It's normal!!
sometimes it's anything but normal, but i found a soft reset (or hard reset for that matter) often is the solution. So it's most likely an application or process that hangs, leaving it for a few minutes and then trying to unlock it usually does the trick
Having some weird issues. Sorry if this has been posted before, I have searched but hard to narrow down.
Not sure if this is a hard/soft issue but its happened for long time even on clean installs on all CM roms I have tried.
My nexus seems to randomly go crazy where all of a sudden touch will lock up or have serious delay or it will just start pressing buttons on its own without any interaction and only way to solve is to power off as power menu will just dissapear so cant hot reboot or anything else.
Does it sound familiar to anybody or anybody know of cause/solution?
TheATHEiST said:
Having some weird issues. Sorry if this has been posted before, I have searched but hard to narrow down.
Not sure if this is a hard/soft issue but its happened for long time even on clean installs on all CM roms I have tried.
My nexus seems to randomly go crazy where all of a sudden touch will lock up or have serious delay or it will just start pressing buttons on its own without any interaction and only way to solve is to power off as power menu will just dissapear so cant hot reboot or anything else.
Does it sound familiar to anybody or anybody know of cause/solution?
Click to expand...
Click to collapse
Does this happen only while plugged in? using a different charger may be the issue.
Else there should be a problem with the digitizer!
nijom said:
Does this happen only while plugged in? using a different charger may be the issue.
Else there should be a problem with the digitizer!
Click to expand...
Click to collapse
No it happens randomly whether charger is in or not. Thankfully it doesnt happen often but every once in a while and just need to reboot.
Something like this happening with me, only on a Secondary User when the Immersive Mode is activated. My touchscreen looks up while using Play Books or MX Player. I've made a video about it as well.
Posted on both xda and the AOSP Issue Tracker page but didn't get any responses yet.
xda thread: http://forum.xda-developers.com/showthread.php?p=47515069#post47515069
AOSP Issue Tracker: https://code.google.com/p/android/issues/detail?id=62366
Regards,
UsmanJ
Hi guys
dont know if anyone else is experiencing this - i think i saw a few other fellows mentioning this but my s7edge has moments (every 2 weeks or so) when it goes completely unresponsive - it gets frozen on whatever page i am at that moment (weather, play store, Facebook or whatsapp) and nothing else works (not even physical buttons like back, task manager or worse - power off/restart button)
the only way to fix it is to simulate a battery removal (vol.down+power)
when restarting it goes back like nothing happened
I was hoping the update they roll would solve this but guess not
what is puzzling is that it doesnt seem to be hardware related, but i just cannot figure out what the F is going on
has anyone else experienced this or has any idea what could be the culprit?
tim2london said:
Hi guys
dont know if anyone else is experiencing this - i think i saw a few other fellows mentioning this but my s7edge has moments (every 2 weeks or so) when it goes completely unresponsive - it gets frozen on whatever page i am at that moment (weather, play store, Facebook or whatsapp) and nothing else works (not even physical buttons like back, task manager or worse - power off/restart button)
the only way to fix it is to simulate a battery removal (vol.down+power)
when restarting it goes back like nothing happened
I was hoping the update they roll would solve this but guess not
what is puzzling is that it doesnt seem to be hardware related, but i just cannot figure out what the F is going on
has anyone else experienced this or has any idea what could be the culprit?
Click to expand...
Click to collapse
This happened to me one day when I was charging the phone. The stopped.
Sent from my Star-Tac
The only time I've seen this was when trying to get Helium backup going (which I still can't get to work).
I would suspect you've got some app that's trying to do some background process and freezes up, or grabs all the phone's resources.
6P - Rooted, Stock, Xposed w/Amplify, Greenify, & Gravity Box.
Android v. 6.0.1 w/ 8/5/16 Security Patch.
Build number MTC20F.
Kernel version 3.10.7.-g909746b.
I'm getting 2 or 3 Sleep of Death (SOD) occurrences a day. Fingerprint scanner, nor power button press wakes it. I have to do a hard reset to turn it back on. I did a factory wipe about two weeks ago when it was getting to be that every time it slept it wouldn't wake up and it was better for a short while, but it's popping up again.
My research has shown that apps can cause it, but I have no way of narrowing down what's causing it at all. It's getting super frustrating at this point.
So my questions are:
1) Is there a way to figure out what's causing the SOD? I can't seem to find a pattern or figure out what's triggering it, so it's not like I can turn a logger on to figure it out before it happens.
2) Once I figure it out, what can I do about it? Or is there something I can do to prevent it without figuring out what directly is causing it?
Hopefully there's a solution that's obvious that I'm missing here. I'd rather not go through the factory reset process again, as it happened again after I reset the last time.
Help is sorely needed.
I use gravity box but not greenify. I use Recently instead of greenify with no problems. Not sure what Amplify is but I use the XML hack to raise headphone volume. Hope this helps.
RRuszczyk said:
6P - Rooted, Stock, Xposed w/Amplify, Greenify, & Gravity Box.
Android v. 6.0.1 w/ 8/5/16 Security Patch.
Build number MTC20F.
Kernel version 3.10.7.-g909746b.
I'm getting 2 or 3 Sleep of Death (SOD) occurrences a day. Fingerprint scanner, nor power button press wakes it. I have to do a hard reset to turn it back on. I did a factory wipe about two weeks ago when it was getting to be that every time it slept it wouldn't wake up and it was better for a short while, but it's popping up again.
My research has shown that apps can cause it, but I have no way of narrowing down what's causing it at all. It's getting super frustrating at this point.
So my questions are:
1) Is there a way to figure out what's causing the SOD? I can't seem to find a pattern or figure out what's triggering it, so it's not like I can turn a logger on to figure it out before it happens.
2) Once I figure it out, what can I do about it? Or is there something I can do to prevent it without figuring out what directly is causing it?
Hopefully there's a solution that's obvious that I'm missing here. I'd rather not go through the factory reset process again, as it happened again after I reset the last time.
Help is sorely needed.
Click to expand...
Click to collapse
I think the best way to diagnose and pinpoint the issue would be by obtaining logs. Haven't used xposed in a while though I think it has a log mechanism you can refer to. If you check the logs for keywords such as "error", "reboot", or "restart, etc. that may narrow down the processes causing the issue.
blitzkriegger said:
I think the best way to diagnose and pinpoint the issue would be by obtaining logs. Haven't used xposed in a while though I think it has a log mechanism you can refer to. If you check the logs for keywords such as "error", "reboot", or "restart, etc. that may narrow down the processes causing the issue.
Click to expand...
Click to collapse
Just checked. The logs are automatically cleared when the phone reboots or resets, so no way I can tell to get the logs before the SOD occurs.
RRuszczyk said:
Just checked. The logs are automatically cleared when the phone reboots or resets, so no way I can tell to get the logs before the SOD occurs.
Click to expand...
Click to collapse
Then try to capture a system-wide log instead. This article may help. Do the logcat after you have experienced the bug. I'm sure it will point out what's causing the issue.
Other than taking the logcat approach you can try eliminating possible culprits. If you suspect it may either be amplify or gb then temporarily disable each module within xposed then observe if the problem persists.