Database Info

[Q] Swap to wake problem....

i have installed the faux kernel and bricked kernel with swap to wake function, and when i swap to lock screen , sometime the phone will screenshot itself
Can anybody know how to fix it?
Sorry for my bad english

goddestroyer said:
i have installed the faux kernel and bricked kernel with swap to wake function, and when i swap to lock screen , sometime the phone will screenshot itself
Can anybody know how to fix it?
Sorry for my bad english
Click to expand...
Click to collapse
You have used tweaks to make one of the capacitive buttons take a screenshot on long press. Either remove this or don't keep any button pressed for long while sweeping.

goddestroyer said:
i have installed the faux kernel and bricked kernel with swap to wake function, and when i swap to lock screen , sometime the phone will screenshot itself
Can anybody know how to fix it?
Sorry for my bad english
Click to expand...
Click to collapse
You need to disable to htc Screenshot feature.. Then sweep to wake works properly
Use any file explorer
(you need to give r/w access to system)
Go to /system
And open build.prop
Chk for this line
ro.htc.framework.screencapture = true
Change it to
ro.htc.framework.screencapture = false
Save the file
Exit and reboot
This will resolve the issue
Sent from my pyramid.. Through blazing fast sonic waves

thanks for both of your reply
i will try and see this work or not

[KERNEL] My kernel patches

Hi everybody!
This thread is dedicated to containing all the kernel (and some other kernel-related) patches I create/port for our device. So I think it could help our kernel developers to focus on actual SGR-related work without worrying about examining and implementing everything that already have been created for other devices from scratch. I'll update this thread with all information whenever I do something related to the goal. I plan to make this a huge thread so please help us to keep it organized and ask common questions in the Q&A thread (in General section) or in PM (if nobody can answer your question). Thanks in advance!
BLN mod
What is BLN?
- Refer this article for more information.
What do I need to try it out on my device?
- Download my CWM-flashable zip from the following link (This installs my kernel plus my modified liblights (of course it makes a backup of the original one first)):
http://www.mediafire.com/?1cnua9uw3ckoiqk
What features does this kernel have?
version 3.1.10 (for ICS stock firmwares)
eMMC_ERASE_CAP disabled (totally safe to use)
it includes AOSP vibrator fix (it works with my pre-alpha CM10 build too) -> Hybrid kernel
Wi-Fi MAC address changing implemented
Keychord support enabled (start services using hardware keys -> revert to original MAC address by pushing 'volume down', 'volume up' and 'power' buttons simultaneously)
BLN support
- Download 'BLN Control - Free' or 'BLN Control - Pro' app from the Play Store. The pro version has some really nice additional features all of which are supported in my mod.
What do I need to enable it in my kernel?
- Apply my attached patch ('bln.patch') in your kernel source dir with 'patch -p1 < bln.patch'. This patch includes the BLN mod port from SiyahKernel3 (SGSII kernel). I removed its wakelock and earlysuspend dependency, our touchscreen driver has a different structure from that of SGSII touchscreen driver and it works without those quite well. I also added some cleanups regarding the original key led sysfs entries.
- Find 'Device Drivers->Input device support->Touchscreens->Atmel MXT224E Touchscreen Interface' in menuconfig and enable 'BLN Support' under it.
What do I need to enable it in my rom?
- Use a kernel that supports BLN.
- Extract 'system/lib/hw/lights.n1.so' from the CWM-flashable zip (in the link I previously attached) and put it into the appropriate folder.
- Optionally include BLN Control app.
Why do I need a special liblights?
- The original liblights doesn't support notifications since we don't have a led for that purpose. Epsylon3 uploaded the open source version of liblights he uses for CM7.2 to his GitHub. However, that unfortunately doesn't support stock Samsung roms (Button backlight doesn't work.), so I had to hack it a little to make it work. By default, the stock rom can set the brightness of the button backlight according to light conditions. I tried several options but didn't notice any difference in brightness, so my modified version returns 255 (0xFF) as brightness whenever it's set to some non-zero value (zero means turning it off). I also added support for BLN through the common Android notification way.
I uploaded its sources to GitHub:
https://github.com/Adam77Root/liblights_bln
Keychord support
What is it?
- If it is enabled in the kernel, init can start services triggered by hardware keys.
Why should I use it?
- I made a simple yet quite reasonable use of it. I created a service in my init.rc, which runs a script ('/system/xbin/resetmac.sh') that turns Wi-Fi off and resets the original MAC address by writing an invalid one ('13:37:13:37:13:37') into the '/efs/wifi/.mac.info' file. This runs whenever I push 'volume down' (114), 'volume up' (115) and 'power' (116) buttons simultaneously. (I had to disable bugmailer first.) You can find keycodes in '/system/usr/Generic.kl'.
- Example code ('init.rc'):
Code:
service resetmac /system/bin/sh /system/xbin/resetmac.sh
class main
disabled
oneshot
keycodes 114 115 116
- Example code ('/system/xbin/resetmac.sh') (chmod it to 700):
Code:
svc wifi disable
echo 13:37:13:37:13:37 > /efs/wifi/.mac.info
What do I need to enable it in my kernel?
- Simply enable 'Device Drivers->Input device support->Miscellaneous devices->Key chord input driver support' in menuconfig.
- Of course it has advantages only if you enable something in your init files too.
Wi-Fi MAC address changing
Please refer my previous thread for more information and on how to use/implement it.
Every custom modification to devices have risks. Use these at your own risk!
Have fun and enjoy!

---reserved---

---another one---

I'm on Frankenstein ROM 4.0.2 and ardatdat 4.2b4 right now, is it safe to flash your kernel plus bln mod directly,and do I need to mount/system before flashing and clear cache and dalvik cache after???
Sent from my GT-I9103 using Tapatalk 2

khpatel4991 said:
I'm on Frankenstein ROM 4.0.2 and ardatdat 4.2b4 right now, is it safe to flash your kernel plus bln mod directly,and do I need to mount/system before flashing and clear cache and dalvik cache after???
Sent from my GT-I9103 using Tapatalk 2
Click to expand...
Click to collapse
I'm on that rom too. It is safe.
Sent from my GT-I9103

I flashed the kernel,wiped cache and dalvik cache, downloaded bln mod pro but not able to understand the patch part,can you explain the procedure in detail,about how to apply the patch
Sent from my GT-I9103 using Tapatalk 2

khpatel4991 said:
I flashed the kernel,wiped cache and dalvik cache, downloaded bln mod pro but not able to understand the patch part,can you explain the procedure in detail,about how to apply the patch
Sent from my GT-I9103 using Tapatalk 2
Click to expand...
Click to collapse
You don't have to patch anything. That part id for kernel devs. My kernel already contains it.
Sent from my GT-I9103

This is awesome bud !
I'm yet to try cause I have to use NTFS pen drives during the next few days, will flash it after that. I had a small request if possible look into it.
I was going through dev sicopat's threads & I found that he had enabled BLN for the stock SMS app by modding it. The link to the MOD is currently down as it was uploaded on multiupload which had shut down for some time. But I'm searching for an alternate link, will notify you if I find one.
Here's the link to the ROM's thread: http://forum.xda-developers.com/showthread.php?t=1164516 (Check Post no. 2, Updates: v3.0).
If possible can you MOD the stock ICS SMS, stock ICS Samsung Email app(not Gmail) / Social Hub for enabling BLN in them ? As per Sicopat's thread as of now this can't be enabled even if we download the BLN Control Pro app & we've to use 3rd party apps. Maybe you can get in touch with him to enable the same.
Hope it'll be possible for you to do so. Cheers !

First of all thanks Adam. This is a long awaited MOD; I have been missing notification LEDs since my change from HTC to SGR.
I have installed your zip through CWM, wiped cache and dalvik cache and bought BLN control app.
The test looks fine, but I have yet to get it to work with an SMS application. I still just use the stock application which doesn't give LED notification.
But I experienced an issue with the modded kernel related to touch. It however disappeared after having the screen off for a few minutes.
When I held icons and try to move them to another position, it lost my touch after 1-1½ second. Similarly I couldn't flick halfway to a new page and hold it there for more than 1½ second.
I'll give an update if it comes back, but this is the first time I have experienced such an issue, and therefore I expected it to be related to this modification.
BR, MHCA

mhca said:
But I experienced an issue with the modded kernel related to touch. It however disappeared after having the screen off for a few minutes.
When I held icons and try to move them to another position, it lost my touch after 1-1½ second. Similarly I couldn't flick halfway to a new page and hold it there for more than 1½ second.
Click to expand...
Click to collapse
Hm, I haven't experenced such problem yet. Pls update me on this when it happens one more time and I'll investigate on it.
Sent from my GT-I9103

I'm really happy with BLN. Thanks!

It would be great if merged to a voodoo kernel.
Sent from my GT-I9103 using xda app-developers app

Thanks Adam, you are the one!
May I ask for your permission to add the BLN modification to my kernel? Thanks very much.
---------- Post added at 02:29 AM ---------- Previous post was at 01:53 AM ----------
I will try to implement it in my kernel. Thx.
Sent from my GT-I9103 using xda premium

ardatdat said:
May I ask for your permission to add the BLN modification to my kernel? Thanks very much.
Click to expand...
Click to collapse
Of course! I'm happy that you find them useful.
Sent from my GT-I9103

Adam77Root said:
Hm, I haven't experenced such problem yet. Pls update me on this when it happens one more time and I'll investigate on it.
Sent from my GT-I9103
Click to expand...
Click to collapse
I just experienced issues again. It is quite annoying when trying to hold down a key on the keyboard to type a number instead of a letter. Failed multiple times.
I then tried holding home screen icons and most of the times it just opened the application as if I had clicked them.
I don't know how you will be able to investigate it, such things can probably be hard to replicate.

How to change deep sleep state in STOCK 4.1.2

Hello guys & Gals
In this tutorial we will be learning how to change deep sleep state in STOCK ROMS/STOCK based ROMS in Samsung galaxy S Advance.
First of all What is deepest sleep State?
"CPU on the Mobiles have variable speeds, like CPUs on laptops. We can work at 200, 500, 800, 1000, 1200 and 1400 MHz, depending on what application we're running.
When there's nothing to do, the CPU should go into "deep sleep" state, which means basically stopped, so it consumes very little power."
By default, Deep sleep state will be 3 in STOCK JB and can be increased till maximum 5.
Now lets start with it.
Requirements:
Samsung galaxy S advance running any STOCK based ROM
Rooted
Root explorer
Terminal emulator
Kernel having init.d support (CoCore-E/EP 6.0 or above)
Instructions
First Download the deepsleep.zip
Extract the zip and you will be getting a file
Copy the file to your phone in Internal storage/Memory card.
Open root explorer and give it root permissions.
Now navigate to System/etc and make a folder named"init.d" if it is not there.
Long press the folder and some options will pop out.
Click on permissions and tick the first 9 brackets(i.e change the permission to 0777)
Now Change Ownership to root root 0:0
Next move the file "deepsleep" from the Storage to the init.d folder.
Change the permissions and the ownership same as you did for the init.d folder.
Reboot your phone.
How do I know That my Deep sleep state has been changed to 4?
Open Terminal Emulator and type the following commands & you should be getting your answer.
su
cat /d/cpuidle/deepest_state
Click to expand...
Click to collapse
You can change deep sleep state to 5 by editing the deepsleep file in init.d and replacing 4 by 5. (similar to make it 3)
NOTE: Don't Use Deep Sleep State 5 on pegasusq(sio governors), It may cause system instability. Instead use indemand+cfq in deep sleep state 5. (but still you may encounter random reboots)
Enjoy better battery backup in standby mode.
If you are using CM10.1/10.2 there is a option to change deep sleep state in settings>advance>deep sleep. You will not be needing any script in CM.
init.d script by anantttt
This is my first post on XDA, So do thank me if you like it & sorry for any typos.
:fingers-crossed:
#PEACE

Thanks man
I'm using the valor 4 with the init.d script
So, i must think that the pegasusq + sio or noop or row scheduler and deep at 4 work normal? i'm using in this moment ondemandq + noop as test

FabioSan said:
Thanks man
I'm using the valor 4 with the init.d script
So, i must think that the pegasusq + sio or noop or row scheduler and deep at 4 work normal? i'm using in this moment ondemandq + noop as test
Click to expand...
Click to collapse
I am using Deepsleep 4 with PegasusQ + SIO on CM 10.1. Without problems. Deepsleep 5 makes reboot, but 4 is working good.

shut_down said:
I am using Deepsleep 4 with PegasusQ + SIO on CM 10.1. Without problems. Deepsleep 5 makes reboot, but 4 is working good.
Click to expand...
Click to collapse
I'm using Ondemandq + noop + deep at 4 no problems But i'm not sure if it's better pegasusq, ondemandq or hotplug xD
Off Topic closed

You are using my script. Dah anyways, why did you open another thread when I already explained in a tutorial to make init.d scripts. See this
http://forum.xda-developers.com/showthread.php?t=2503884
But still good work

anantttt said:
You are using my script. Dah anyways, why did you open another thread when I already explained in a tutorial to make init.d scripts. See this
http://forum.xda-developers.com/showthread.php?t=2503884
But still good work
Click to expand...
Click to collapse
Sorry dude i too got that script from another person and really didn't know who made it.
Right now i am online from my cell so will edit your name in document afterwards when i will be on my pc.

FabioSan said:
Thanks man
I'm using the valor 4 with the init.d script
So, i must think that the pegasusq + sio or noop or row scheduler and deep at 4 work normal? i'm using in this moment ondemandq + noop as test
Click to expand...
Click to collapse
Try using pegasusq instead of ondemand.

Ankurzl said:
Try using pegasusq instead of ondemand.
Click to expand...
Click to collapse
I'm using Pegasusq + noop from some days but sincerly i don't see sensible differences ._.
At least the battery is that, and also the phone u.u

[Q] Installed Linaro r61, /sys/android_touch gone and can't create the folder

So I recently installed Linaro kernelr61 via Franco Kernel Updater, I've been using linaro since r30 and it always has had problems with Sweep to wake and sleep, not setting on boot and whatnot, but I've always found a way to force these options by editing the files in /sys/android_touch, but this time the folder is gone and I can't create it even with SU, I just want to extend the life of the power button on my Nexus 5, so if you know how to activate these options or know about a kernel that has it easier please help.
Appreciate it beforehand

J05HU4 said:
So I recently installed Linaro kernelr61 via Franco Kernel Updater, I've been using linaro since r30 and it always has had problems with Sweep to wake and sleep, not setting on boot and whatnot, but I've always found a way to force these options by editing the files in /sys/android_touch, but this time the folder is gone and I can't create it even with SU, I just want to extend the life of the power button on my Nexus 5, so if you know how to activate these options or know about a kernel that has it easier please help.
Appreciate it beforehand
Click to expand...
Click to collapse
Flash kernel in recovery instead of using the FKU app. The thread has a flashable zip

You can't create in /sys. This Is a directory created and managed by the kernel. This directory is effectively read only. You can edit files but the kernel resets most on a reboot anyway.
If the file you want isn't there, its because the kernel doesn't use it or there is a problem with the kernel, in which case, post in the kernel thtead
Sent from my Nexus 5 using Tapatalk

rootSU said:
You can't create in /sys. This Is a directory created and managed by the kernel. This directory is effectively read only. You can edit files but the kernel resets most on a reboot anyway.
If the file you want isn't there, its because the kernel doesn't use it or there is a problem with the kernel, in which case, post in the kernel thtead
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Except he doesn't have 10 posts

Lethargy said:
Except he doesn't have 10 posts
Click to expand...
Click to collapse
Cant tell that from tapatalk

[Q] Double Tap To Wake on S.H.I.E.L.D. Rom

Hi,
I have installed S.H.I.E.L.D. ROM about 2 days ago... many thanks to @Tkkg1994... the ROM seems perfect so far.
The only thing (maybe a bug?) is "double tap to wake" that is too sensitive. Only a soft touch and display switch ON.
There is a solution? Some string or value in some system file?
Thanks a lot for answer

You have a functional dt2w? How come? It is only in settings and need a custom kernel to wake up.

agarth said:
You have a functional dt2w? How come? It is only in settings and need a custom kernel to wake up.
Click to expand...
Click to collapse
It's enabled in S.H.I.E.L.D. Rom... I think it has default kernel B165 with enabled value in .xml file. Maybe it is default supported in stock kernel...

Really!
How we can do it with stock rom 158 + Root?

On SHIELD ROM, I have:
Build.prop file in folder:
/System (string added by me)
/System/vendor
with this string: ro.config.hw_easywakeup=true
On /System/emui/base/xml
file:
hw_easywakeupmotion_config.xml
string:
<EasyWakeUpMotion name="Double_Touch" support="1" value="0" flag="0" keycode="131" />
In Settings>Smart Assistance>Motion Control
SCREEN OFF GESTURES - Double Touch

same here, hope someone can figure out why it's so sensitive. one tap would wake up the screen.