Database Develop

[KERNEL][MOD] Increase Touchscreen Sensitivity 4.2.2

4.2.2 Any Rom CWR flashable zip:
e015-AnyRom-4.2.2-v1.zip
-Downgraded touchscreen firmware to e015
-Enable loading of modules
4.2.2 Any Rom CWR flashable zip: (2/23/2013)
Latest e015-hsic-AnyRom-4.2.2-v2.1.zip
e015-hsic-AnyRom-4.2.2-v1.zip
-Downgraded touchscreen firmware to e015
-Enable loading of modules
-msm_hsic_host wakelock fix thracemerin
4.2.1 Any Rom CWR flashable zip:
e015-AnyRom-​4.2.1*http://goo.gl/BgiZz
-Downgraded touchscreen firmware to e015
Matt at http://code.google.com/p/android/issues/detail?id=40445 figured how to downgrade the touch firmware to a previous version, which had better sensitivity. But it won't stick after a reboot, so I compiled a custom kernel with the downgraded touch firmware.
Here's how to make it stick after a reboot. This requires a my custom kernel and also to manually downgrade the touch driver once using terminal or adb.
This will downgrade your touch firmware from E027 to E015.
First, flash my kernel, download links listed above. .
Second, after flashing the flashing the kernel and rebooting, download this file SynaImage.E015.bin*http://goo.gl/4vzd4 and place on the root of the sdcard.
Then open terminal or adb and request root permission.
Then type the following command "echo 1 /sdcard/SynaImage.E015.bin > /sys/devices/virtual/input/lge_touch/firmware"
The screen will not be responsive to touch for a few seconds as the firmware is downgraded.
To check if it downgraded successfully, run this in terminal "cat /sys/devices/virtual/input/lge_touch/fw_ver" you should get "E015" as a response. Try this after rebooting to see if it sticks.
Your done! Now you have a nice sensitive touchscreen.
Credit goes to Matt who figured out how to downgrade the touch firmware here http://code.google.com/p/android/issues/detail?id=40445, comment 42.
This is totally reversible, just flash any kernel or booting into recovery, and the original firmware will update automatically.
CWR Touch will revert the the touch firmware, therefore the touchscreen will be non-responsive for a few seconds when you first boot into recovery, you can use the volume buttons and power button until the touchscreen is responsive again. .
Kernel Source: github.com/reddv1/msm.git
Here's another method to downgrade the touch firmware
Better: http://forum.xda-developers.com/showthread.php?t=2163924
http://forum.xda-developers.com/showthread.php?t=2028289
Sent from my Nexus 4 using Tapatalk 2

Everyone incoporate this into your Kernel's NOW , yes you Faux!
Great find , I might test tonight.

I suggest you make a bigger deal out of the no touch CWM. People are going to miss that and then complain incessantly when they realise.

I'll try it when I get back home, but I thought the screen of the Nexus 4 was perfect !

Hopefully kernel devs incorporate this. Any ideas if TWRP is borked too? I'm not sure if it has anything but touch options.
Sent from my Nexus 4 using Tapatalk 2

lnfound said:
Hopefully kernel devs incorporate this. Any ideas if TWRP is borked too? I'm not sure if it has anything but touch options.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Yeah touch won't work with TWRP either. I can always compile the recoveries with the downgraded touch firmware and that will fix touch in them.
Sent from my Nexus 7 using Tapatalk 2

qwahchees said:
Everyone incoporate this into your Kernel's NOW , yes you Faux!
Great find , I might test tonight.
Click to expand...
Click to collapse
Yeah, they should include it because it doesn't downgrade the touch firmware, unless you downgrade it manually it just helps it stick. And reflashing the same kernel or any kernel will reverse it automatically. Everyone wins.
This option is nice to have until Google or LG update the firmware themselves.
Sent from my Nexus 4 using Tapatalk 2

reddv1 said:
Yeah, they should include it because it doesn't downgrade the touch firmware, unless you downgrade it manually it just helps it stick. And reflashing the same kernel or any kernel will reverse it automatically. Everyone wins.
This option is nice to have until Google or LG update the firmware themselves.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
You are the man! Thankyou so much, this is something that has irked me from day 1. Thanks again!!!

Has anyone actually tested this?

ace7196 said:
Has anyone actually tested this?
Click to expand...
Click to collapse
Yes, I can confirm it works very well

mrjeffery said:
Yes, I can confirm it works very well
Click to expand...
Click to collapse
please post the new PRS readings. I am interested.
Sent from my GT-I9000 using xda premium

Tried it, nothing really changed for me, still around 0.5/0.6

ace7196 said:
Has anyone actually tested this?
Click to expand...
Click to collapse
Yep! I subscribed the issue and applied the fix directly after it was posted.
I love it! Please Google / LG, fix the "ghost touch" issue without making the screen less sensitive.
@Faux: Include it in your Kernel!
@AlwaysDroid / Apfelschale: PRS is the same though, but the sensivity is better. I tested it today in my daily routine.

this looks promising but I'll probably wait until motley or faux include it in their kernels. Currently running motley since I'm getting this phone RMA'd and wanted to try all the kernels and like it a lot so I don't want to give up those features for a slightly more sensitive screen.

It's nice for some people I'm sure but my phone feels just fine.
I hope kernel devs don't enable this out of the box, or at least provide a way of turning it off and on.

Apfelschale said:
Tried it, nothing really changed for me, still around 0.5/0.6
Click to expand...
Click to collapse
Hasn't changed for anyone, I think prs reading having any substance has been debunked. Some readings saying improvement with no difference in prs reading are in the other thread.
Sent from my Nexus 4 using Tapatalk 2

I've just added this mod to the Nexus 4 Complete Index
Sent from my GT-I9100 using xda premium

DarkRyoushii said:
this looks promising but I'll probably wait until motley or faux include it in their kernels. Currently running motley since I'm getting this phone RMA'd and wanted to try all the kernels and like it a lot so I don't want to give up those features for a slightly more sensitive screen.
Click to expand...
Click to collapse
You don't have to include it in the kernel, just replace the old one and test it. It'll be gone after a reboot.
Everything you need is described here: http://code.google.com/p/android/issues/detail?id=40445#c42

I can definitely see an improvement here. Values gone from around 0.5 to 0.3

Successfully downgraded and jammin. Sticks after reboot. Thanks

Can someone recommend a Stock like rom but not CM?

I would like to change the date to be centered and expand the power off screen to include reboot to name a few.
I am looking for a rom that will be very close to stock with a few mods.
Thanks so much!

stu5797 said:
I would like to change the date to be centered and expand the power off screen to include reboot to name a few.
I am looking for a rom that will be very close to stock with a few mods.
Thanks so much!
Click to expand...
Click to collapse
terminus. its aosp based, not cm based.

Thanks! Can I flash this even though my build number is LRX22C and the termius is LRX22G? I am also on stock 5.0.1 and this is 5.0.2.
Thanks so much!

stu5797 said:
Thanks! Can I flash this even though my build number is LRX22C and the termius is LRX22G? I am also on stock 5.0.1 and this is 5.0.2.
Thanks so much!
Click to expand...
Click to collapse
absolutely. if youre on a aosp based rom, you can even try a dirty flaah(not wiping anything. but make a backup in recovery first, just in case. if your on a stock or cm based rom, you will have wipe data(factory reset) first
edit.. just read, youre on stock. so, in recovery before you flash this rom(+gapps, +supersu), you will have to wipe data(factory reset)(nothing else) first. dont wipe whats in your storage!

You could also try this
http://forum.xda-developers.com/nexus-6/themes-apps/modpack-mcr-modpack-nexus-6-r1-t2996168

Sinless is a stock based ROM with the mods your looking for. I've used it since day one. I'm not really asop guy since there tends to be bugs. But to each their own.

Chroma rom. Contains what you need, nothing more and nothing less. Lightweight and stable.
http://forum.xda-developers.com/nexus-6/development/rom-chroma-01-11-2015-t3000003

I would highly recommend Chroma

Using Chroma since a while now. It's solid. Go for it.
Sent from my Nexus 6

Chroma!

suku_patel_22 said:
Using Chroma since a while now. It's solid. Go for it.
Sent from my Nexus 6
Click to expand...
Click to collapse
I haven't seen you in the thread lately! Seen you posting in the Franco Kernel thread often though.
I have some secrets up my sleeve to celebrate being the 2nd most replied thread and 3rd most viewed thread in N6 Android Development forums while celebrating the one-month anniversary of the ROM release

zephiK said:
I haven't seen you in the thread lately! Seen you posting in the Franco Kernel thread often though.
I have some secrets up my sleeve to celebrate being the 2nd most replied thread and 3rd most viewed thread in N6 Android Development forums while celebrating the one-month anniversary of the ROM release
Click to expand...
Click to collapse
Well I am having zero issues with Chroma and am hoping that sensor_ind gets killed and burned.
Hence being there more often.
Well I know one of the secret is the official Chroma theme
Sent from my Nexus 6

Chroma
Chroma Rom has the highest Benchmark so far right after flash.

suku_patel_22 said:
Well I am having zero issues with Chroma and am hoping that sensor_ind gets killed and burned.
Hence being there more often.
Well I know one of the secret is the official Chroma theme
Sent from my Nexus 6
Click to expand...
Click to collapse
Psssh, that's not what I wanted to hear I want people to come back even if there aren't any bugs. Sensor_ind is on the kernel level, try Franco's test kernel. I also updated modified to r14.1 which stops sensor_ind (using Imoseyon's patches)

zephiK said:
Psssh, that's not what I wanted to hear I want people to come back even if there aren't any bugs. Sensor_ind is on the kernel level, try Franco's test kernel. I also updated modified to r14.1 which stops sensor_ind (using Imoseyon's patches)
Click to expand...
Click to collapse
Yeah, I am on his test kernel. Have disabled both msm_hsic_host and sensor_ind already.
Sent from my Nexus 6

424aca said:
Chroma Rom has the highest Benchmark so far right after flash.
Click to expand...
Click to collapse
lmao, seriously???

Super slow Chroma

My phone seems soo slow/bogged down. I am running 12-10 Chroma build with the Elite kernel. Anyone recommend a similar rom? I always clean flash..my memory is plentiful. [emoji21]
Sent from my Nexus 6 using Tapatalk

phillybizzle said:
My phone seems soo slow/bogged down. I am running 12-10 Chroma build with the Elite kernel. Anyone recommend a similar rom? I always clean flash..my memory is plentiful. [emoji21]
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Unless there is something wrong with the ROM, the kernel, or the combination of ROM + kernel, I would suspect there is something else wrong. Maybe settings somewhere, kernel settings maybe? Maybe an app? It would be impossible to know without more information.
That said, you can try another ROM there are plenty out there. Maybe it fixes whatever the problem may be, but my guess would be it would be a coincidence.

cupfulloflol said:
Unless there is something wrong with the ROM, the kernel, or the combination of ROM + kernel, I would suspect there is something else wrong. Maybe settings somewhere, kernel settings maybe? Maybe an app? It would be impossible to know without more information.
That said, you can try another ROM there are plenty out there. Maybe it fixes whatever the problem may be, but my guess would be it would be a coincidence.
Click to expand...
Click to collapse
which rom are you on just curious.
Sent from my Nexus 6 using Tapatalk

Only kernel I've ever used that was as smooth as my N5 was Blu Spark kernel, but unfortunately the dev has ended development on it at 6.0.0

Every Custom Kernel kills camera

Flashed 15 different times today, stock OOS 7.0. camera works fine on stock, even with magisk installed. As soon as I flash any custom kernel the camera app gets unknown error. Tried clearing cache, etc everything. Only stock kernel works. What gives?

You might want to read the kernel threads for help. Seems like if it was a kernel issue like you claim then someone else might have noticed it. Sounds like user error to me

954wrecker said:
You might want to read the kernel threads for help. Seems like if it was a kernel issue like you claim then someone else might have noticed it. Sounds like user error to me
Click to expand...
Click to collapse
Thanks brain.

Magisk is the reason for those errors, im using custom kernel since android 7.0 with system less superSU only, I already tried three different custom kernels here and they didn't gave me any camera errors

J4DedPrez said:
Thanks brain.
Click to expand...
Click to collapse
Wow, smartass answer for someone who can't flash a kernel without breaking the camera.
Actually, the answer is the solution you need, search and read.

exaflare said:
Magisk is the reason for those errors, im using custom kernel since android 7.0 with system less superSU only, I already tried three different custom kernels here and they didn't gave me any camera errors
Click to expand...
Click to collapse
Thank you friend, sometimes being nice and giving the simple solution is the simplest method.

Migdilu said:
Wow, smartass answer for someone who can't flash a kernel without breaking the camera.
Actually, the answer is the solution you need, search and read.
Click to expand...
Click to collapse
Typical XDA user... It's a real shame kids these days act the way they do

J4DedPrez said:
Typical XDA user... It's a real shame kids these days act the way they do
Click to expand...
Click to collapse
What it's a shame is that there are people who don't know how to read.

Magisk does work with custom kernels, but the order you flash them in is important. Magisk alters certain files in the /boot partition, which is also where the kernel is located. You should flash Magisk first over a clean ROM prior to flashing any custom kernels, or else you may run into issues. If an update for Magisk is pushed, you should also install it in the following order:
1) Dirty flash ROM (or stock kernel)
2) Flash Magisk
3) Flash custom kernel
I'm currently using Magisk v11.6 with Franco's r16 on OOS 4.1.0 without a problem.

Don't mean to be rude, but did you flash the compatible kernel; and not using adb sideload problems; on TWRP 3.0.4-1?
If you did, well then Magisk seems to be a problem for you.
And do post logs next time of you encounter a problem until and unless you are sure you everybody can reproduce that problem with the steps mentioned (which should be though)

If you're still in Android 7.0 (like me), do not use the latest custom kernel release, it will break your camera (Unknown Error). I think it's because the dev has rebased their kernel to the new Android 7.1.1.
Currently, I'm still on FredomOS 2.5 (OOS 4.0.3) and its combined with BluSpark v.72 (last release before the 7.1.1 rebase).
I don't want to use the latest OOS update since it's still full of annoying bugs.

In my opinion only people who understand what they are doing with this kind of stuff should get the oneplus 3 or 3t as it isn't very noob friendly and takes someone that is some what an advanced user or at least knows a little about flashing ROMs and kernels etc..... Or at least is willing to search around and read before they complain to everyone that they can't figure it out. If you want a phone that is simple and noob use friendly then go to Samsung or Apple. not oneplus as phone from this company are aimed at the intermediate up to power user that understands how to solve irregular problems. I've had none of these issues even when I was using my oneplus x. I use the unofficial RR with ex kernel and no problems with camera or anything and great battery life. Bottom line is (in my opinion anyways) oneplus phones are for the more technically savvy so if you aren't some one like that expect to run in to difficulties and have to do some deep research in certain cases. But this is a great community here at xda and we are all willing to help as much as we can but patience is a must.

Anova's Origin said:
Magisk does work with custom kernels, but the order you flash them in is important. Magisk alters certain files in the /boot partition, which is also where the kernel is located. You should flash Magisk first over a clean ROM prior to flashing any custom kernels, or else you may run into issues. If an update for Magisk is pushed, you should also install it in the following order:
1) Dirty flash ROM (or stock kernel)
2) Flash Magisk
3) Flash custom kernel
I'm currently using Magisk v11.6 with Franco's r16 on OOS 4.1.0 without a problem.
Click to expand...
Click to collapse
Same exact order as you, even flashed fresh ROM and kernel only. Can't explain it at all. For now, I'm on stock with no custom kernel but have magisk.

mrinmaydhar said:
Don't mean to be rude, but did you flash the compatible kernel; and not using adb sideload problems; on TWRP 3.0.4-1?
If you did, well then Magisk seems to be a problem for you.
And do post logs next time of you encounter a problem until and unless you are sure you everybody can reproduce that problem with the steps mentioned (which should be though)
Click to expand...
Click to collapse
No sideload, using most recent TWRP, and yes, I will have logs to post tomorrow. As a quick flasher I never really bother for the logs, but this time I'm getting down to the bottom of this. I'll have logs tomorrow

motherninja said:
If you're still in Android 7.0 (like me), do not use the latest custom kernel release, it will break your camera (Unknown Error). I think it's because the dev has rebased their kernel to the new Android 7.1.1.
Currently, I'm still on FredomOS 2.5 (OOS 4.0.3) and its combined with BluSpark v.72 (last release before the 7.1.1 rebase).
I don't want to use the latest OOS update since it's still full of annoying bugs.
Click to expand...
Click to collapse
This is exactly the issue. Thank you
se7ensde said:
In my opinion only people who understand what they are doing with this kind of stuff should get the oneplus 3 or 3t as it isn't very noob friendly and takes someone that is some what an advanced user or at least knows a little about flashing ROMs and kernels etc..... Or at least is willing to search around and read before they complain to everyone that they can't figure it out. If you want a phone that is simple and noob use friendly then go to Samsung or Apple. not oneplus as phone from this company are aimed at the intermediate up to power user that understands how to solve irregular problems. I've had none of these issues even when I was using my oneplus x. I use the unofficial RR with ex kernel and no problems with camera or anything and great battery life. Bottom line is (in my opinion anyways) oneplus phones are for the more technically savvy so if you aren't some one like that expect to run in to difficulties and have to do some deep research in certain cases. But this is a great community here at xda and we are all willing to help as much as we can but patience is a must.
Click to expand...
Click to collapse
:good:

Flashing kernels made for 7.1.1 on 7.0 FW.

954wrecker said:
You might want to read the kernel threads for help. Seems like if it was a kernel issue like you claim then someone else might have noticed it. Sounds like user error to me
Click to expand...
Click to collapse
Normal, helpful, response(don't be discouraged by some).
J4DedPrez said:
Thanks brain.
Click to expand...
Click to collapse
Douche response.
Migdilu said:
Wow, smartass answer for someone who can't flash a kernel without breaking the camera.
Actually, the answer is the solution you need, search and read.
Click to expand...
Click to collapse
Obvious observation.
J4DedPrez said:
Thank you friend, sometimes being nice and giving the simple solution is the simplest method.
Click to expand...
Click to collapse
Hypocrisy.

Hi all !
This discussion might be related with my issue explained here:
https://forum.xda-developers.com/oneplus-5/help/camera-flashlight-youtube-t3886260
but only thing is I never flashed custom kernels, issue appears after a official update !
Any opinion, ideas ?
Thanks

[KERNEL] [Android 12] [v12.9] MVK - Maximum Velocity Kernel

For those familiar with Velocity Rom this is the kernel I build for it. Velocity hasnt been on XDA as a rule so Im sure not many are familiar. Velocity is my personal Rom Ive been building for years and have shared with all that are interested. This isnt and will never be an "official development project" but will always exist as long as I continue to develop Android roms.
Velocity is focused on speed, stability, and efficiency and not on adding every imaginable feature. As this is my personal Rom it will have everything I deem useful to me and/or that doesnt compromise the goals of the project.
I dont add every conceivable governor, I/O scheduler, or other user tweakable options. In fact, I typically remove all the options and keep the best. This is designed as a plug and play kernel, not something to be changed. Its also not designed for other Roms.
Please do not ask for features, ETA's, or related. Again, this is my personal kernel for my personal Rom and will be shared accordingly. That said, I do encourage healthy, friendly dialog in my threads.
Flashing instructions
1) Reboot to bootloader
2) Fastboot boot 'bootimage_name'.img to make sure it boots with no issues
3) Reboot to bootloader again
4) Fastboot flash boot 'bootimage_name'.img
5) Buckle up for safety - optional of course
Changelog
Download
Source

Thanks for this!
It's great to see another person building for our device. Not that the others aren't doing great work, but the more the merrier.

Once Q source drops, the real fun will begin. I can see potential for crazy speed and battery life over 10 hrs SOT on Q. Im coming from Shamu (Nexus 6) so this is quite a change in use and development. I think Im getting a good handle on what makes it tick though.

Question, am running bootleggers rom, kernel flashed fine and everything smooth, only thing wifi was broken, I wiped dalvik and restart phone issue still persist.
Tmobile 3axl

jsanta11 said:
Question, am running bootleggers rom, kernel flashed fine and everything smooth, only thing wifi was broken, I wiped dalvik and restart phone issue still persist.
Tmobile 3axl
Click to expand...
Click to collapse
Not surprising. This is why I stated it works on stock but no idea on custom ROMs. I can cook a boot image if you want to try that, but that would also be based on stock.
Boot image is up in the same folder if you want to try that, but this really is designed to run on either my Rom or stock. Once velocity is out I won't be building stand alone kernels.

ctfrommn said:
Not surprising. This is why I stated it works on stock but no idea on custom ROMs. I can cook a boot image if you want to try that, but that would also be based on stock.
Boot image is up in the same folder if you want to try that, but this really is designed to run on either my Rom or stock. Once velocity is out I won't be building stand alone kernels.
Click to expand...
Click to collapse
My bad I overlooked that part.. Understood, I'll wait till you cook up the rom and rock with it.. Thanks in advance

Android 10 kernel coming soon. Got it all working correctly now. Will be a magisk patched boot.img for now as that seems to work best.

I don't see any files in the pixel 3a xl folder

Which file is the correct one to download? Folders are showing as empty?

oranget said:
Which file is the correct one to download? Folders are showing as empty?
Click to expand...
Click to collapse
I just updated all the folders and OP. I just uploaded the build to the current link in the OP.

Kernel flashed great....running it now. Will reply soon on overall usage. I flashed it through EX kernel manager.

V10.1 uploaded......see changelog for differences

ctfrommn said:
V10.1 uploaded......see changelog for differences
Click to expand...
Click to collapse
And so it begins. Thank you my friend!

Yes, expect a lot of builds for the next week or two. I'm trying to work on the ROM side too but 10 is very different than Pie and so it's slow going.

Works nicely. Thanks for your effort!

sysak said:
Works nicely. Thanks for your effort!
Click to expand...
Click to collapse
How is your battery life compared to the previous version?

Wasn't on it long enough but I would expect they would be the same. Honestly I won't get a good battery cycle until I'm done getting this where I want it. I'm already several versions newer than 10.1

ctfrommn said:
Wasn't on it long enough but I would expect they would be the same. Honestly I won't get a good battery cycle until I'm done getting this where I want it. I'm already several versions than 10.1
Click to expand...
Click to collapse
Well, thank you for your continued work.

v10.2 up

I had an issue with touchscreen not working when waking up from sleep on 10.2. I use the fingerprint and if i unlock the phone from sleep (always on display showing) touch wont work but if i wake it, switch off the screen with the button and unlock again quickly then it's ok. Reverted to 10.1