[n9005][2014/DEC/01][TWKK] faux123/Yank555.lu kernel 002b3

[Julian Jeremiah]

Yes but we can't excute it can we coz it isn't "rwx'? Screen shot here

Yes, su>enter (as always)

First line of command - Touch wake enabled permissions denied, cannot proceed to next stage

This is what I typed in terminal according to github: /sys/class/misc/touchwake/enabled

File permission is rw-rw-rw-, so everyone can write to that file ...

What exactly did you type (screenshot) ?

JP.

[yank555]

You're not supposed to execute anything in there

You're supposed to write stuff in or read stuff from those files

Hence I wrote :

echo 1 > /sys/class/misc/touchwake/enabled

You need to type all of that.

JP.

[Julian Jeremiah]

Haha ok I used root explorer to enable it. Touchwake is confirmed working on S pen but not fingers

Next question what is the ideal values to set in touchwake/delay and touchwake/proximity_threshold? Default values are 5000ms and 150 respectively. Default value for touchwake/delay is at 5000ms which I think is too fast but on the other hand wouldn't wanna drain the battery too

You're not supposed to execute anything in there

You're supposed to write stuff in or read stuff from those files

Hence I wrote :

echo 1 > /sys/class/misc/touchwake/enabled

You need to type all of that.

JP.

[yank555]

Haha ok I used root explorer to enable it. Touchwake is confirmed working on S pen but not fingers

Next question what is the ideal values to set in touchwake/delay and touchwake/proximity_threshold? Default values are 5000ms and 150 respectively. Default value for touchwake/delay is at 5000ms which I think is too fast but on the other hand wouldn't wanna drain the battery too

Delay, up to your liking, drain is ok unless you use extreme values, it's in ms, so 60000 would be a minute, still acceptable. 0 is infinite btw, not really a great choice, but some wanted it ...

Proxy doesn't need changing unless you have issues during calls (touching the screen with your cheek brings the screen back on).

JP.

Send from my 'proudly eFused' Note 3 (n9005) running Temasek v83 on Yank555.lu htle v1.0a (3.4.90) kernel.

[Julian Jeremiah]

Thanks Yank.. I would set it as infinite (0) if using fingers are functioning

BTW can you include init.d support in your next release? I don't see it thru the change logs in the OP or it is already included?

Haha ok I used root explorer to enable it. Touchwake is confirmed working on S pen but not fingers

Next question what is the ideal values to set in touchwake/delay and touchwake/proximity_threshold? Default values are 5000ms and 150 respectively. Default value for touchwake/delay is at 5000ms which I think is too fast but on the other hand wouldn't wanna drain the battery too

Delay, up to your liking, drain is ok unless you use extreme values, it's in ms, so 60000 would be a minute, still acceptable. 0 is infinite btw, not really a great choice, but some wanted it ...

Proxy doesn't need changing unless you have issues during calls (touching the screen with your cheek brings the screen back on).

JP.

Send from my 'proudly eFused' Note 3 (n9005) running Temasek v83 on Yank555.lu htle v1.0a (3.4.90) kernel.

[yank555]

Thanks Yank.. I would set it as infinite (0) if using fingers are functioning

Well that's the last thing I need to get going, and we're out of alpha and in beta

BTW can you include init.d support in your next release? I don't see it thru the change logs in the OP or it is already included?

Yes can do, but if the ROM has support (ROM-side, not in init.rc, which is kernel-side), scripts will be run twice, which can or cannot be a problem. I'll check with faux if that's ok for him.

JP.

[Julian Jeremiah]

Noted. What do you think of UMS (USB Mass Storage) function?

Yes can do, but if the ROM has support (ROM-side, not in init.rc, which is kernel-side), scripts will be run twice, which can or cannot be a problem. I'll check with faux if that's ok for him.

JP.

[yank555]

Noted. What do you think of UMS (USB Mass Storage) function?

That should be handled by an app, the kernel does support it, it just needs the external SD to be dismounted and made available differently.

It can be done issueing a simple command in terminal, but don't ask me which, too long ago I don't need that anymore, I use SAMBA to access it through Windows file sharing

JP.

PS: init.d support will be in next kernel.

[Julian Jeremiah]

Noted. How about your LED control?

Oh ya before I forget I wanna feedback that I've noticed on several times while I was staring at the CPU in Fauxclock, the min CPU frequency's clock bar tend to manoeuvring around although it happens on an intermittent state, is it a norm?

Noted. What do you think of UMS (USB Mass Storage) function?

That should be handled by an app, the kernel does support it, it just needs the external SD to be dismounted and made available differently.

It can be done issueing a simple command in terminal, but don't ask me which, too long ago I don't need that anymore, I use SAMBA to access it through Windows file sharing

JP.

PS: init.d support will be in next kernel.

[yank555]

Noted. How about your LED control?

LED control, it's in. Sysfs interface described here.

Oh ya before I forget I wanna feedback that I've noticed on several times while I was staring at the CPU in Fauxclock, the min CPU frequency's clock bar tend to manoeuvring around although it happens on an intermittent state, is it a norm?

That's normal, that's Samsung's touchboost at work.

JP.