[KERNEL][03-March-2015][SHIELD-TABLET-WWLTE/USLTE/WI-FI][OC-CPU+GPU/UV/FIOPS/XZ/ETC]

[Shaky156]

I got a million FCs with this new one. Completely unusable, I tried clearing dalvik, fixing permissions etc and nothing helped. Also wifi doesn't seem to be able to connect but I could barely even test anything since everything kept closing.

Bugs????
1. From terminal/command line adb pull /proc/last_kmsg
2. Upload to pastebin/gdrive/devhost
3. Link the uploaded file in this thread along with the description about the issue.
​

From the OP, cant do much without a log.

 

[Gil Smash]

From the OP, cant do much without a log.

I'll try and grab a log for you when I get home, sorry not trying to hate on you or anything just a word of warning. I'm out right now and flashed this like a dumbass with no backup and just wanted to let people know. Keep a backup! Don't be like me!

 

[Shaky156]

I'll try and grab a log for you when I get home, sorry not trying to hate on you or anything just a word of warning. I'm out right now and flashed this like a dumbass with no backup and just wanted to let people know. Keep a backup! Don't be like me!

The issue that exists is most likely caused by:
The system was mounted by recovery upon boot before installing zip, which is read only system, in this condition the files cannot be copied to the system, which would cause these issues.
This is noted in the kernel release post
But yes do provide logs

 

[Gil Smash]

The issue that exists is most likely caused by:
The system was mounted by recovery upon boot before installing zip, which is read only system, in this condition the files cannot be copied to the system, which would cause these issues.
This is noted in the kernel release post
But yes do provide logs

I saw that, it's not listed as mounted in TWRP. How else would I know if it were mounted?

 

[xanthrax]

no FC issues whatsoever but I've noticed a drastically decrease of the responsiveness, sound glitches, global low performance comparing to v1 with no matter what governor
I'll give another try, switching to optimized from power control prior flashing not after as I've done it first
The minimum cpu freq doesn't stick below 1224 or trickster doesn't match properly with this kernel /Tablet
I'll be back
I'm using the latest stock 2.2.1, twrp 2.8.5 multirom
sent from my Darkside of SHIELD Tablet

 

[Shaky156]

no FC issues whatsoever but I've noticed a drastically decrease of the responsiveness, sound glitches, global low performance comparing to v1 with no matter what governor
I'll give another try, switching to optimized from power control prior flashing not after as I've done it first
The minimum cpu freq doesn't stick below 1224 or trickster doesn't match properly with this kernel /Tablet
I'll be back
I'm using the latest stock 2.2.1, twrp 2.8.5 multirom
sent from my Darkside of SHIELD Tablet

Thatll be fixed on next update, if you set the shield power control to optimized you can set the minimum cpu freq

Edit: Fix: http://d-h.st/39Ul

 

[xanthrax]

Thatll be fixed on next update, if you set the shield power control to optimized you can set the minimum cpu freq

Edit: Fix: http://d-h.st/39Ul

just re-flashed v1.1 with optimized set up prior flash
the freq stays at the value I want {51000} that's cool but screen responsiveness is the same, I barely can write something...
I'll give a try to the fix right now
which log do you prefer, dmesg, last_ksm? in case of, you know, more complains [emoji4]...

sent from my Darkside of SHIELD Tablet

 

[xxsashixx]

Thatll be fixed on next update, if you set the shield power control to optimized you can set the minimum cpu freq

Edit: Fix: http://d-h.st/39Ul

Thanks for the fix the responsive seems to be fixed

 

[xanthrax]

yes, it seems, slightly better but still graphical and sound glitches, interactive gov
I'll play around with it a bit more

sent from my Darkside of SHIELD Tablet

 

[jdenman03]

I know someone else mentioned this already but I second implementing dt2w functionality. At least have the option for it. I HATE our power button with a passion and I've ran numerous versions of the elemental x kernels on other devices and loved the dt2w feature. Its usually very minimal battery drain.

 

[Shaky156]

I know someone else mentioned this already but I second implementing dt2w functionality. At least have the option for it. I HATE our power button with a passion and I've ran numerous versions of the elemental x kernels on other devices and loved the dt2w feature. Its usually very minimal battery drain.

+1 I have to agree with you, I not a big fan of the power button either, it isn't impossible to do, I have taken a look into this and have done some work on it but with my current schedule I'm too busy to release anymore updates for now

I have tested audio and using FIOPS reduces the audio glitch compared to other schedulars. I have an idea on whats causing it but as i have said before right now is a busy time so there wont be an update anytime soon

 

[Shaky156]

To expand on my previous reply, i have implemented double tap to wale feature, when the screen is off, touching the screen registers but does not wake up the screen so it is pretty close

 

[thefiqs]

Is this kernel working with all WIFI versions like WWLTE or just WIFI US?

 

[FoxyDrew]

Is this kernel working with all WIFI versions like WWLTE or just WIFI US?

Supported Device Versions:
World Wide LTE
US LTE
WI-FI

Also, it's in the title of the thread...

 

[Käsebrot]

Can't unlock. No response from Touchscreen.

 

[xanthrax]

Can't unlock. No response from Touchscreen.

Which recovery do you have?
Have you tried other kernel before?

 

[Käsebrot]

Which recovery do you have?
Have you tried other kernel before?

PhilZ Recovery and i tried the Kernel by SuperPichu.

 

[xanthrax]

I'm facing the same problem... I've flashed the stock kernel 2.2.1 but still the same.
Im afraid that we must try to dirty flash the stock ROM, the latest one and root and flash recovery again if you need
The tablet touch doesn't respond after few minutes of deep sleep but I'm not sure whether is related to this kernel or some leftovers from another one, I tried pichu kernel as well before this one

 

[Käsebrot]

I'm facing the same problem... I've flashed the stock 2.2.1 but still the same.
Im afraid that we must try to dirty flash the stock ROM, the latest one and root and flash recovery again if you need
The tablet touch doesn't respond after few minutes of deep sleep but I'm not sure whether is related to this kernel or some leftovers from another one, I tried pichu kernel as well before this one

So, flashed the newest stock Rom and SuperSu, cleared cash and dalvik. All is fine.

 

[xanthrax]

So, flashed the newest stock Rom and SuperSu, cleared cash and dalvik. All is fine.

Great, as I didn't have time to do it, can you try again to see if the touch screen issue comes from this kernel? Only if you want but I suspect pichu kernel
I'll do it myself tomorrow anyway
Thanks