Camera Sensor bug still present?

---

Hi francisco,

I've been following this thread and would like to thank you for your hard work in making a very lean kernel which sports a good battery saving/conservative governor.

I do have one question for you which stems from you original post regarding the camera sensor being left open by the gtalk app on bootup, causing battery drain.
Can you tell me if this bug was resolved as through one of your kernel builds or if this is something that isn't controlled by the kernel at all and needs to be fixed by through rom/software update.

Please let me know.

Thanks,
cchhat01

Originally Posted by Franzac

Hm, I'm sorry but its still not working but thanks for helping

Anyone else experiencing this?

Do I need to set a flag somewhere so that init.d scripts are executed?

Try "echo 1 >>" with two brackets.

Getting sleep of death in random occurrences. Will investigate more about it and will report my findings here.

I bet it's connected with hotplug tho. Long shot.

delete

10char

ETA on next release at all?

Sent from my Galaxy Nexus using xda premium

Originally Posted by franciscofranco

You're doing it wrong:

#!/system/bin/sh

echo 1 > /sys/module/dsscomp/parameters/hotplug_enabled

I have read the logcat and I cannot see there is a step running script in init.d

I doubt the function is not running correct.

Besides, I think you need to remount /sys

so add follow code first

mount -o remount sysfs /sys

Originally Posted by EddyOS

ETA on next release at all?

Sent from my Galaxy Nexus using xda premium

Franco juuuust said don't ask for an ETA. But as a rule of thumb never ask for an ETA. Its rude. This is not Franco's job this is something he does because he loves it and he wants to give to the community.


Sent from my Galaxy Nexus using XDA App

Originally Posted by Thracks

Try "echo 1 >>" with two brackets.

The double ">>" is used to append to a file, so this won't change anything. Tried it and had no effect.

Originally Posted by Booker-T

I have read the logcat and I cannot see there is a step running script in init.d

I doubt the function is not running correct.

Besides, I think you need to remount /sys

so add follow code first

mount -o remount sysfs /sys

Thanks, but this does not work either. It seems like the script is not executed at boot time, because if I run it manually when I am in the OS it works.

I use Bigxie build 9 and this bootloader if this is important.

Sorry for annoying you all, I am just interested in how the init.d stuff works.

And thanks to everyone that tries to help

Originally Posted by sishgupta

Franco juuuust said don't ask for an ETA. But as a rule of thumb never ask for an ETA. Its rude. This is not Franco's job this is something he does because he loves it and he wants to give to the community.


Sent from my Galaxy Nexus using XDA App

1. Didn't see he'd said not to ask
2. Was asking because it's not really a 'nightly' if it's days between updates

#12 still going strong btw

Originally Posted by Franzac

The double ">>" is used to append to a file, so this won't change anything. Tried it and had no effect.



Thanks, but this does not work either. It seems like the script is not executed at boot time, because if I run it manually when I am in the OS it works.

I use Bigxie build 9 and this bootloader if this is important.

Sorry for annoying you all, I am just interested in how the init.d stuff works.

And thanks to everyone that tries to help

YES, I am doubting the init.d is not working but I don't know whether it is function of kernel or rom