[KERNEL][GPL][N4] franco.Kernel - r217
- Thread starter franciscofranco
- Start date
Don't know not running for me.will try to redownload.
Sent from my iPad using Tapatalk iOS 7
Have you tried
Code:
dmesg | grep PVSEdit: hmmm...the code above is now returning Nominal for me, but fKu still says Slow...? Cataclysm Sep 07 2013, franco kernel r184 JWR, fKu 10.3.3
Sent from my Nexus 4 using Tapatalk 4
Last edited:
Yes had it here....
Uninstall it, reboot, and reinstall, it worked like a sharme with me.
I think my phone runs hotter on Franco kernel compared to stock PA kernel... Any explanation behind this?
Sent from my Nexus 4 using Tapatalk 4
Sent from my Nexus 4 using Tapatalk 4
Aliens.
Sent from my Nexus 4 using Tapatalk 4
Sent from my Nexus 4 using Tapatalk 4
How to install fifa 2014 on N4? I thought its for tablets only. Thanks
With AK47's.
Tablets only, where did you get that from??
I downloaded and installed it perfectly fine on my N4 this morning.
PS. I'm running Cataclysm + Franco.
Franco....less paddel and more «Milenstone4»
Enviado desde mi Nexus 4 usando Tapatalk
Enviado desde mi Nexus 4 usando Tapatalk
True, true, heheheFranco....less paddel and more «Milenstone4»
Enviado desde mi Nexus 4 usando Tapatalk
Large Franco, by far the best kernel
Enviado desde mi Nexus 4 usando Tapatalk
I tried downloading the game yesterday and it says that my device is not supported. Will try later after work.
here FKU and terminal both say fastest so it's identical information
Gesendet von meinem Nexus 4 mit Tapatalk 4
Last edited:
Well in my opinion too many FCs reported here to be considered milestone. I had zero on Franco kernels til this releae (so had logging off) and had two FCs with R184 on Cataclysm which has never had problems up to this release. For now back to R183 and 6 hrs SOT/19 on, no problems. Sorry about the logs Chief.
Question for Paranoid Android and franco kernel users
Paranoid Android ROM users do you guys have any issues at all when installing franco's kernels? like force closes or anything the "breaks" Im thinking of trying out PA for the first time cause Ive been stock and kinda want to change things up a bit but my worry is that ill have issues people experience when not using just stock ROM. (Which seems to be the major reason people have issues?) Thanks for any help or insight
Paranoid Android ROM users do you guys have any issues at all when installing franco's kernels? like force closes or anything the "breaks" Im thinking of trying out PA for the first time cause Ive been stock and kinda want to change things up a bit but my worry is that ill have issues people experience when not using just stock ROM. (Which seems to be the major reason people have issues?) Thanks for any help or insight
Everything ok here. The only thing you have to do is download and flash jwr version manually since fku is downloading jss version.Paranoid Android ROM users do you guys have any issues at all when installing franco's kernels? like force closes or anything the "breaks" Im thinking of trying out PA for the first time cause Ive been stock and kinda want to change things up a bit but my worry is that ill have issues people experience when not using just stock ROM. (Which seems to be the major reason people have issues?) Thanks for any help or insight
Enviado de meu Nexus 4 usando Tapatalk 4
Indeed! They changed the bloody build.id to JLCsomething, which fúcks FKU not-so-smart detection algorithm! :'(
Same thing happens on cm, just have to download and flash manually
Sent from my Nexus 4
Just dropping by, been on Franco for 6 months now, tried others every now and then. I always come back to Franco and purity. My favorite combo. Except maybe pa now that you are on the team. Its always felt much slower than other Roms to me, but I love the features. Hopefully that changes. But thanks for the great kernel!!
Sent from my Nexus 4 using Tapatalk 4
Sent from my Nexus 4 using Tapatalk 4
Ok I have a small gift for all of you that run FK for almost a year on this device. I always said that I would never implement any of those functionalities to wake the device without pressing the power button - point is that LG G2 has brought this feature, Oppo N1 has something very similar and... I've been getting emails that users are having the Power Buttons wore off. Initially I implemented this on the new Nexus 7 as a challenge and to have some fun. Couple code lines later I had the functionality working fine and dandy. The device deep sleeps and the only thing that is being kept active is the digitizer for this to work. I sent it to a couple of people and they enjoyed it specially because it worked better than other Kernels that had implemented similar options. Good, so lets try and implement it on Mako. It's 100% my code, pretty simple, and easy to understand. Please refer to git (I just pushed the code) for how it works in the touch driver and input subsystem.
By default this option is disabled, but you can enable it by doing:
echo 1 > /sys/module/lge_touch_core/parameters/touch_to_wake
After this is enabled you can power up the display by double tapping just like the LG G2, and you can swipe from whenever you want on the display and it will power up. There is a 100ms (0.1s) minimum interval where the algorithm will detect touch events so filter ghost touches and some unintended shít. It seems very low value, but when we're touching the screen the digitizer is capturing hundreds of touch events every minute, and dozens every second. So this works as a filter.
If you're using touch_control and you want to test this, please disable the module and reboot your device or you'll most likely get into some **** problems. And the same thing other way around.
Oh and interactive is back to default, it just gives me more consistence results all around.
Attached goes two test zips, flash, enable the touch thingy, test, and report back.
By default this option is disabled, but you can enable it by doing:
echo 1 > /sys/module/lge_touch_core/parameters/touch_to_wake
After this is enabled you can power up the display by double tapping just like the LG G2, and you can swipe from whenever you want on the display and it will power up. There is a 100ms (0.1s) minimum interval where the algorithm will detect touch events so filter ghost touches and some unintended shít. It seems very low value, but when we're touching the screen the digitizer is capturing hundreds of touch events every minute, and dozens every second. So this works as a filter.
If you're using touch_control and you want to test this, please disable the module and reboot your device or you'll most likely get into some **** problems. And the same thing other way around.
Oh and interactive is back to default, it just gives me more consistence results all around.
Attached goes two test zips, flash, enable the touch thingy, test, and report back.
Last edited:
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone