[Kernel][Sony5.x][Z/ZL]Zombie[23.12.15]

kingvortex

Senior Member
Mar 25, 2010
5,042
3,967
0
Strange thing happened yesterday...
I just pressed fix permissions in twrp...
All data got wiped...Internal memory was encrypted....(could only see it through twrp...not phone)
:(
It's never been a good idea to use "Fix permissions". If you follow any of Chainfire's threads, he has always advised against it. As far as I know, it will break something with SELinux since Lollipop as well (unless that is now fixed).

Anyway, in short; don't do it!
 

langeveld024

Senior Member
Jun 7, 2012
1,720
805
113
About the hotplug thing, I've seen this happening in my sister's xperia sp.
Where completely disabling any form of hotplugging reduced power consumption.

However, I'm still using kk (i know u dont support it anymore) and eagerly waiting for niaboc to release its ROM but I never tried disabling hotplug myself.
So, is this general for all android phone's? If so, why do we use mpdecision as default?

Keep up the good work! regards
 
  • Like
Reactions: Tommy-Geenexus

Tommy-Geenexus

Senior Member
Apr 30, 2013
2,769
2,576
193
I live on a Stone Hill.
About the hotplug thing, I've seen this happening in my sister's xperia sp.
Where completely disabling any form of hotplugging reduced power consumption.

However, I'm still using kk (i know u dont support it anymore) and eagerly waiting for niaboc to release its ROM but I never tried disabling hotplug myself.
So, is this general for all android phone's? If so, why do we use mpdecision as default?

Keep up the good work! regards
Its not general for all Phones, but for all Phones up to 4 Cores, hence why Google disabled hotplugging on the Nexus 6.

Newest Octa SOC's work more efficient with hmt scheduling, hotplugging shouldn't be touched there.
 

creison

Senior Member
Dec 31, 2011
271
33
0
Rio de Janeiro
Hi,
I`m unable to acess Philz in recovery, only TWR, I`v already tryed pressing volume + and - but Only TWR showsUp, M`i doing a wrong sequence to enter in Philz recovery or it`s simply not present?
Thanks in advance!
 

Tommy-Geenexus

Senior Member
Apr 30, 2013
2,769
2,576
193
I live on a Stone Hill.
New build is up!

Changelog:
* Merged security enhancements (done by @Olivier Via PR, thanks)
* Cleaned up thermal driver (which could solve some mysterious reboots, as i noticed there was some hotplug stuff mistakenly left)
* Reworked APQ-Hotplug ( Now with full own workqueue stuff to ensure the driver works as intended)

I highly advise everyone to upgrade to this build.
 

comax70

Senior Member
Jul 4, 2013
958
135
0
milan
New build is up!

Changelog:
* Merged security enhancements (done by @Olivier Via PR, thanks)
* Cleaned up thermal driver (which could solve some mysterious reboots, as i noticed there was some hotplug stuff mistakenly left)
* Reworked APQ-Hotplug ( Now with full own workqueue stuff to ensure the driver works as intended)

I highly advise everyone to upgrade to this build.
Flashed v3 test...[emoji12]
 
  • Like
Reactions: Tommy-Geenexus

w_ayon

Senior Member
Jun 2, 2014
73
4
0
After activation of d2w from kernel auditor app, at first it worked normally bt after sometime touch screen acted strangely. I couldnt unlock the screen. If i touch somewhere it takes somewhere else.i had to reboot my z.after rebooting everything works as b4. Anyone facing this prblm?

Sent from my C6602 using XDA Free mobile app
 

gcgspain

Senior Member
Jan 12, 2009
221
43
0
Vigo
After activation of d2w from kernel auditor app, at first it worked normally bt after sometime touch screen acted strangely. I couldnt unlock the screen. If i touch somewhere it takes somewhere else.i had to reboot my z.after rebooting everything works as b4. Anyone facing this prblm?

Sent from my C6602 using XDA Free mobile app
The same thing has happened to me twice on v2 and just once on a v3. I thought the cause could be related to gravity box xposed module as I use the lock screen option to use a blurred last screen as lock screen.
Basically what happens is that the phone wakes up and there's no way to unlock the screen, only once I got through only to not be able to do the unlock pattern as the touch screen did not read the screen swypes correctly. I had to power off holding power button and volume up.

Enviado desde mi GT-N5110 mediante Tapatalk
 

langeveld024

Senior Member
Jun 7, 2012
1,720
805
113
The same thing has happened to me twice on v2 and just once on a v3. I thought the cause could be related to gravity box xposed module as I use the lock screen option to use a blurred last screen as lock screen.
Basically what happens is that the phone wakes up and there's no way to unlock the screen, only once I got through only to not be able to do the unlock pattern as the touch screen did not read the screen swypes correctly. I had to power off holding power button and volume up.

Enviado desde mi GT-N5110 mediante Tapatalk






After activation of d2w from kernel auditor app, at first it worked normally bt after sometime touch screen acted strangely. I couldnt unlock the screen. If i touch somewhere it takes somewhere else.i had to reboot my z.after rebooting everything works as b4. Anyone facing this prblm?

Sent from my C6602 using XDA Free mobile app
Yeah that's normal behaviour for our Z.
Not kernel specific.
I face that issue on any ROM/kernel since dt2w was introduced. (Only when enabled)
Sometimes I had no problems for a while and then all of a sudden boom! It was back again! So I just disabled it and now I keep it disabled.
The phone is much more usable without it than with it.

:)