Yank555.lu Android Stuff

Hello,

A feedback after a week (almost) with A5, no more reboot problem, maybe another thing not related to the kernel could be responsible for my previous problem.

Very reliable kernel, very stable, my favorite by now.

I read that init.d support will be available in the next kernel, do you mean it doesn't work in a5? As I am cooking a custom rom, it's an important point for me before releasing it .

Thanks for your next answer and keep the good work .

ezaechiel wrote:Hello,

A feedback after a week (almost) with A5, no more reboot problem, maybe another thing not related to the kernel could be responsible for my previous problem.

Very reliable kernel, very stable, my favorite by now.

I read that init.d support will be available in the next kernel, do you mean it doesn't work in a5? As I am cooking a custom rom, it's an important point for me before releasing it .

Thanks for your next answer and keep the good work .

Not yet included, indeed, but will add it as soon as I get to it

JP.

Great news, thanks a lot, as I think I will release my custom on xda with your kernel as default one . If you give me the permission for sure (and giving you credits for kernel )

ezaechiel wrote:Great news, thanks a lot, as I think I will release my custom on xda with your kernel as default one . If you give me the permission for sure (and giving you credits for kernel )

No problem, but give also credit to faux

JP.

For sure faux and you

Yank,

I could have accidentally off my phone thru power button, Im not aware though but now touchwake isn't working? Any solution? Touchwake is enabled.

Julian Jeremiah wrote:Yank,

I could have accidentally off my phone thru power button, Im not aware though but now touchwake isn't working? Any solution? Touchwake is enabled.

Powersuspend mode is set to what ?

Remember it defaults to 1 (userspace mode), and that needs fauxclock running to work.

Set it to anything else (0,2,3) and it will work. I'd suggest to use 0 or 3.

JP.

Yes you're right default is 1 and 0 would not work either, only 3 does thanks it's working again now

yank555 wrote:

Julian Jeremiah wrote:Yank,

I could have accidentally off my phone thru power button, Im not aware though but now touchwake isn't working? Any solution? Touchwake is enabled.

Powersuspend mode is set to what ?

Remember it defaults to 1 (userspace mode), and that needs fauxclock running to work.

Set it to anything else (0,2,3) and it will work. I'd suggest to use 0 or 3.

JP.

I'm looking at GPU, set at 320 by default and doesn't budge. Usually its at max 450 and drops to 389 or 200 while at rest..

Edit... I'm wrong it does scale down but 450 is a no go
also min cpu freq while screen on is a never ending cycle between 300 and 2.2 at rest. Drops to 300 for a mille second and scales back up regardless of gov.. There are no open apps and should be at idle set speed of 300

jdidtht wrote:I'm looking at GPU, set at 320 by default and doesn't budge. Usually its at max 450 and drops to 389 or 200 while at rest..

On which GPU governor ?

JP.

PS : Don't use simple governor yet...

Send from my 'proudly eFused' Note 3 (n9005) running Temasek v85 on Yank555.lu htle v1.0b-beta2 (3.4.91) kernel.