• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [KERNEL] MiRaGe - SPH-M950/icon optimized for stock JB MD6/MI2 - 10222013

siyangqiu said:
Question about JB: Does this kernel fix issues like freezing and GPS? I reverted to ICS because of those, even though I had Animania's kernel installed.
Click to expand...

I have never seen any freezing or GPS issues, neither received ... yet.
 
I've had my Reverb for only two months. No freeze at all so far. Google Now is very responsive too. Then again, I don't put many apps (less than 300MB total).

Two things I've realized after this kernel so far are my POP3 email deletes messages much quicker and it does free up RAM (50~75MB). Loving it!
 
I really, really hope it's because of something I did, but ... erm ... I had my touch screen go unresponsive on me. :banghead:

I had re-downloaded C Locker and was starting to set it up and tapped the power button. When I tapped the power button again, the screen wasn't responding to touch. I'm really hoping it's because I put the phone to sleep in the middle of setting up a lock screen and playing with security settings. :confused:
 
I was going to say something about that myself... I recently used kies to install jb clean and then installed a few of my usual apps, then installed the kernel. Today I was simply listening to my vm and having the screen go off and on just moving the phone to and from the side of my head was enough to make the screen go unresponsive. It's the only time so far.
 
I have never seen an unresponsive screen yet with MiRaGe or the stock kernel. Since I can't replicate the problem, I can't help without dmesg and/or logcat. We first need to understand how/why it happens. It may not even be related to the kernel.
 
The problem is that it's so random. And always when I turn the screen back on to use the phone. All the buttons and touch buttons at the bottom work, just the regular touchscreen doesn't work like the driver stops responding or something.
 
Mine does it, but very rarely. I just chalked it up to touch screens occasionally freezing on every single touch device I've ever had.
Any electronic device freezes from time to time.
 
I hope it happens to me too, so that I can at least find why it happens. As I said, logcat/dmesg will be very helpful.

In the mean time, I can only recommend revert the lock screen settings to default values and uninstall any app/widget/etc that interferes with the lock screen.

Also, if you are overclocking in any way, make sure the lowest cpu frequency is higher than 245 MHz and highest frequency is a stable value.
 
I've had the unresponsive touchscreen without a lock screen enabled and my incident yesterday happened while I was actually on the phone checking my voicemail.
 
Hmm. I can't find the files in ES Explorer and I never re-installed a terminal emulator, so I'll have to simultaneously wait for next time and hope it never happens.

Thanks.
 
shyFluttershy said:
Hmm. I can't find the files in ES Explorer and I never re-installed a terminal emulator, so I'll have to simultaneously wait for next time and hope it never happens.

Thanks.
Click to expand...

Just the opposite, I hope I can find a way to make it happen on my phone in the mean time :)
 
shyFluttershy said:
Hmm. I can't find the files in ES Explorer and I never re-installed a terminal emulator, so I'll have to simultaneously wait for next time and hope it never happens.

Thanks.
Click to expand...


Catlog is free from the Google Store
https://play.google.com/store/apps/details?id=com.nolanlawson.logcat&hl=en
 
shyFluttershy said:
It looks like a running report of everything that's going on. How do I call up a particular file?

Thanks.
Click to expand...


You can sort results to show only errors, otherwise your touchscreen logs will be in orange/yellow type marked input reader and input dispatcher, with an "I" in a green block.
(If you hit pause while it's running, you'll see what I'm talking about showing what it did when you hit pause.)
You may also want to set it to save logs to your sd card if you're low on internal storage, although logs don't take up much space.
 
shyFluttershy said:
Erk. I think I may have accidentally deleted some log info with CatLog. Not the most user-friendly app, that. :dong:
Click to expand...


It's probably ok, I think that when your touchscreen freezes again, that last bit that occurred at the actual freeze will be the part of the log you'll need, not the whole thing. You can also set it to reset the log every two hundred lines or so, so you don't end up with days worth of logs.
 
sanjuro77 said:
It's probably ok, I think that when your touchscreen freezes again, that last bit that occurred at the actual freeze will be the part of the log you'll need, not the whole thing. You can also set it to reset the log every two hundred lines or so, so you don't end up with days worth of logs.
Click to expand...

Could you please explain how to set this up?

Thank you.
 
Hmm...upon a bit of further research and due to the unpredictability of this error, it looks like getting k_msg capability is gonna help a lot, since you won't be able to use Catlog to save the logs with the touchscreen frozen, and I don't think Catlog saves on its own until you tell it to, and I'm not sure if Catlog holds on to the logs after reboot.
Gonna have to do more research....Though I'm sure mgr666 has some ideas.
 
sanjuro77 said:
Hmm...upon a bit of further research and due to the unpredictability of this error, it looks like getting k_msg capability is gonna help a lot, since you won't be able to use Catlog to save the logs with the touchscreen frozen, and I don't think Catlog saves on its own until you tell it to, and I'm not sure if Catlog holds on to the logs after reboot.
Gonna have to do more research....Though I'm sure mgr666 has some ideas.
Click to expand...

We don't know yet on which side the problem should be fixed, in the kernel or Android. We need to see logcat first to determine if we can eliminate Android and focus on the kernel. If the screen is frozen but kernel is working fine, adb can be used to obtain logcat. The link below has information on using adb to get logcat.
http://forum.xda-developers.com/showthread.php?p=28132214

I have doubt that the kernel is problem since the problem descriptions so far don't mention about spontaneous reboot. When kernel crashes, system most of the time reboots by itself.

Anyway, I have updated the kernel in the OP with several fixes and patches. Some of them might help with this evasive problem too. Let's see. Please post your feedback if there is anything different, good or bad. It seems this build is running find on my phone. Changes are as follows, you can see the details in my repo.

- further kernel config cleanup
- ARM: enable CONFIG_KTIME_SCALAR
- disable CONFIG_OABI_COMPAT
- ARM: 7791/1: a.out: remove partial a.out support
- Set CONFIG_PANIC_TIMEOUT=5, AOSP recommended value
- update ashmem from MiRaGe shooter kernel
- Staging: android: timed_gpio: Fix unreg order

Cheers!
 
You must log in or register to reply here.
Back
Top Bottom