I have the Rainbow 1.4 custom rom for my lumia 710. It has the touchwake setting. I can enable it but when i reboot the phone, i have to re-enable it for it to work. How do I set it so it will work even after the phone reboot. Thanks
I have exactly the same question!! Anyone could help?
Related
Hi,
I'm using this rom: http://forum.xda-developers.com/showthread.php?t=1543521
With the stock rom the screen used to turn on when a notification was issued. With this it doesn't happen. I read about BLN but couldn't find a place where it said that BLN is Ace compatible.
Is there any way to make the soft keys or the screen to turn on?
Thanks
With custom rom your screen light wont turn on, thats normal.
Download BLN from market, don't worry, its compatible
But when I install the BLN control it says that the BLN isn't available and must be flashed...
huh? You just need to download BLN free version and enable it.
Saca-a do Play store e instala, nao tem nd q saber.
that's what I did... For what I've been reading the kernel must support BLN and that seems not be the case.. I'll try later again... gotta flash the phone again since I've must have done something not so good to the operating system
Still... no success... first I flashed the blackhawk for CM7.2 and now I have the message "this liblights does not support BLN" help?
NoLed did the trick
I've noticed that my phone vibrate for a short time while i write a message and stop to work (the same for games)... Fingerprint doesn't work all the time. (Bootloader unlocked + custom rom)
When i flash a Official SBF, the vibration and the fingerprint works fine!
Anybody know why?
Sorry for English...
Fix permissions in clockwork recovery.
Sent from my MB860 using Tapatalk 2
Doesn't worked for me... =/
permissions?
Explain this permissions setting in CWR as I have flashed my phone to latest Olympus build and lost ability to use handset speaker, phone will go dark and unresponsive until I turn on a BT device if I place or take a call, or can use speaker function while answering and let everyone hear me on my call.
Has to be something simple, it worked prior to flash.
ROM: rootbox 2.0 Kernel: siyah 3.5.2
I have a problem with BLN. I disable BLN in the galaxy setting, after I lock and unlock the screen, the LED is turned on.
I change the time out to extweak to "disable", but when I lock the screen led continues on.
How do I turn off completely BLN.
sorry my english is bad, I plan to ask questions in Rootbox topic, but I did not have 10 posts
Uncheck "BLN" at bln card in extweaks, disable led-on-touch, apply settings and reboot.
sanglxagdm said:
ROM: rootbox 2.0 Kernel: siyah 3.5.2
I have a problem with BLN. I disable BLN in the galaxy setting, after I lock and unlock the screen, the LED is turned on.
I change the time out to extweak to "disable", but when I lock the screen led continues on.
How do I turn off completely BLN.
sorry my english is bad, I plan to ask questions in Rootbox topic, but I did not have 10 posts
Click to expand...
Click to collapse
well you cannot completely turn off BLN ma8, all u can do is go to extweaks app
there under BLN tab you set BLN as follows
1) Tick the box under BLN
2) under Notification_timeout - select ur desired time out (1min is ideal)
3) under BLN effect - select it to be steady
4)under LED_timeout - agian select the desired time out (1.5sec is good)
5) under LED_fade out- tick the box
6)under LEDS On with Touch- u tick the same if u want led to be ON after u touch the screen else leave it blank
7)under Led voltage level- drag the bar back to set it 2700mv
after that hit apply changes button and ur done with
I have set up as follows and reboot.
- Extweak.
BLN: uncheck
Notification_timeout: nevertimeout
LED_timeout: disable
led_fadeout: uncheck
led_on_touch: uncheck
- Galaxy setting.
tab sensors:
enable keys blacklight: uncheck
Reboot > LED is still on.
sanglxagdm said:
I have set up as follows and reboot.
- Extweak.
BLN: uncheck
Notification_timeout: nevertimeout
LED_timeout: disable
led_fadeout: uncheck
led_on_touch: uncheck
- Galaxy setting.
tab sensors:
enable keys blacklight: uncheck
Reboot > LED is still on.
Click to expand...
Click to collapse
set it as i have told u in my previous post and see
@thank to Sun90.
I did not see post # 3, while I type post # 4.
Now I set it as you.
if i change other kernel (dream kernel), can i turn off completely?
sanglxagdm said:
@thank to Sun90.
I did not see post # 3, while I type post # 4.
Now I set it as you.
if i change other kernel (dream kernel), can i turn off completely?
Click to expand...
Click to collapse
u cannot completely turn OFF the same ma8, u can disable it on touch,for notification etc. but if u touch the soft keys u see them light up thats why i told to reduce the led voltage so that u can hardly see the same
Not long after I enabled the power saving mode on my S2 the device suddenly shutdown (while in my pocket, battery around 60% full) and couldn't turn on again. After 2 days the S2 suddenly booted again but still won't start up all the time when I want to.
My S2 device never had this issue before (I know it is a well known issue but apparently it should have been fixed in JB?)
Software I use:
- Apolo 4.12 kernel (Regular)
- Neatrom Lite
I am thinking of either hardware starting to fail or maybe the Apolo kernel has a bug that was triggered by enabling the powersafe mode?
I am not sure, anyone that can help/advise me?
It's probably a software issue, JB has tons of bugs. What kinda advise do you want? You need to re-install the rom (and clear cache ofc) and if that doesn't work re-install the stock rom via odin and then install neatrom if you want. And just don't use power save mode until you get an update? It's useless anyway... You can also try another kernel, this seems like a kernel problem.
Power saving actually just have a few advantages like turning of un-needed things like haptic feedback and some other stuff which you could do manually, and the main power saving feature is that it limits the CPU to use only 800Mhz max, this might be having some issues with Apollo kernel (as it works fine with stock or stock based kernel like Philz), but Apollo is a powerful kernel and will let you manually adjust the CPU limits even at your preferred limits manually, so if you want to save battery just manually adjust the settings instead of using Power Saving mode.
Sent from my GT-I9100 using Tapatalk
Perphide said:
Not long after I enabled the power saving mode on my S2 the device suddenly shutdown (while in my pocket, battery around 60% full) and couldn't turn on again. After 2 days the S2 suddenly booted again but still won't start up all the time when I want to.
My S2 device never had this issue before (I know it is a well known issue but apparently it should have been fixed in JB?)
Software I use:
- Apolo 4.12 kernel (Regular)
- Neatrom Lite
I am thinking of either hardware starting to fail or maybe the Apolo kernel has a bug that was triggered by enabling the powersafe mode?
I am not sure, anyone that can help/advise me?
Click to expand...
Click to collapse
It may be a bug in that rom. try another rom
Thank you!
Thank all of you for the help and advise!
I will no longer use the powersafe feature and start using the Apolo kernel again, since that kernel gave me the best battery life.
It might have been a coincidence of course that my S2 died/didn't want to start up no more shortly after using the powersafe feature... however from all of the above advise it seems that I don't need that feature anyway so I feel safe to switch back to the Apolo kernel again with my new installed NeatROM SuperLite 2.4.
If the problem returns I'll be here to post it, it might still be a bug in the Apolo kernel of the NeatROM ... I am not sure. Time will tell, or not if it had to do with the powersafe feature which I won't be using any more.
Thank you all!
Hello,
I've recently bought the Android Car radio Ownice c500. I noticed that the boot time of this device is about 30 seconds.
I already tried several time to make it boot faster like the following things:
- Root and edit the build.prop (quickpoweron=true & (bootanimationoff=1)
- Search if this device had the possibility to hibernate (Sleep mode) Can't find it by the way
- Turn off all of the animations in the developer menu
Unfortunately the boot time is still 30 seconds.
I search the threads about this problem over and over, but no answer can be found.
I've found a rule in the build.prop (persist.sys.shutdown.mode=hibernate)
So that is my last resort then i'm out of options.
I hope someone can give me advice how to boot the Ownice C500 faster.
I will try any method (root, apk, several settings)
I hope you can help me.
Kind Regards,
Stiflerstef