[Q] Nexus 7 kernel w/ gesture support? - Nexus 7 Q&A, Help & Troubleshooting

Is there Nexus 7 kernel with gestures support like on SGS2 with Siyah kernel:
http://forum.xda-developers.com/showthread.php?t=1831254
Very nice feature, for example wake device by swiping screen.

in the work the sweep2wake in bricked kernel.we have to wait until dev do it,becsause a simple porting of the features from htc's devices don't works as expected with our elan touchscreen's drivers,and he has to re-write big part of code.HERE you can see an experimental video of it in action

Related

Fvourite Rom & Kernel Setup?

What is you favorite and most importantly WHY?.
I'm currently on rootbox 3.8 which is a great rom, and very customizable witht he navrings, lockscreens shortcuts. And the kernel I am no using (since today) is the Matr1X 7.5. I can't judge the battery life yet but the fact it supports double tap screen to turn screen on and swipe to turn it off is fantastic.
So whats your favourite and why?
F*** Messed up title. Mod change it svp
Cm + franco
Sent from my Nexus 4 using xda premium
Carbon + Franco! I've read good things about both pieces and have been testing them together for a week or so; i must say, they both work marvelously.
CM + Matr1x.
I have really enjoyed the speed and stability that this combination has. Franco seems a little slower to me, but it is a great dependable Kernel. Trinity is also really nice. Carbon and ParanoidAndroid would be my two other favorite Roms, but due to CM being on a nightly update basis using CyanDelta it is quite nice to see new features daily rather than rolled out a lot at a time.

25% Off *Franco Kernel Updater* til MIDNIGHT ONLY

Makes it $4.11 in the Play store.
Updater is a bit of an understatement...
It keeps track and downloads updates but it's also a kernel performance tuner like TricksterMOD. It rates 4.8 stars and has received 6k+ reviews.
It also works with non-Franco kernels though you'll need to use Franco Kernel to take full advantage of some functions specially built into his kernel.
This is the only app of its calibre (that I know of) that allows you to set values for specific apps. Sure, there's SetCPU but that's a bit antiquated and -besides- that's the only thing SetCPU does, really.
See the link for all the technical stuff, features and reviews:
https://play.google.com/store/apps/details?id=com.franco.kernel
P.S. Double check, but I'm thinking the supported device list is only intended for the actual kernel. Spread too thin our I'd verify for y'all=)
Gah! Okay, supported device list applies to the app and includes:
* Galaxy Nexus
* Asus Google Nexus 7 2012
* Asus Google Nexus 7 2013
* LG Nexus 4
* LG Nexus 5
* Samsung Nexus 10

DT2W/S2W Wake/Sleep features

Hey guys,
I'm looking for a good Kernel with this features available for my Nexus 4.
I have a Nexus 7 2013 and I'm using ElementalX with these features and I just can't get enough of it.
Help a brother out!
I personally use Faux' kernel, which has those features. Whether it's good or not for you depends on your interpretation of "good"

[Q] A question about features on AOSP based roms for SGS5

I'd like to ask what would be the state of each of the next features on SGS5 (any of its models) when moving to an AOSP based rom (like CM, Omni, PA, ...) :
1. MHL/HDMI
2. Screen recording.
3. Calls recording
4. hovering with the fingers.
5. touching with gloves
6. sensors
7. IR
8. Any TW app (camera, keyboard, etc...)
By state, I mean, how well would it function, if at all.
Also, I'd like to ask (as I don't really own the device) : what would you miss the most in case you moved from stock-Samsung rom to AOSP-based rom?
Any feature I didn't mention ?
AndroidDeveloperLB said:
I'd like to ask what would be the state of each of the next features on SGS5 (any of its models) when moving to an AOSP based rom (like CM, Omni, PA, ...) :
1. MHL/HDMI
2. Screen recording.
3. Calls recording
4. hovering with the fingers.
5. touching with gloves
6. sensors
7. IR
8. Any TW app (camera, keyboard, etc...)
By state, I mean, how well would it function, if at all.
Also, I'd like to ask (as I don't really own the device) : what would you miss the most in case you moved from stock-Samsung rom to AOSP-based rom?
Any feature I didn't mention ?
Click to expand...
Click to collapse
Sadly, most of these functions have not been carried over to AOSP based roms. Most of these functions seem to arrive on Cyanogenmod first.
I do know that Cyanogenmod is currently supporting IR but it is not complete enough to run 100% daily driver. They're having GPU video/image rendering issues in some apps, camera isn't properly configured. It's all stuff being worked on but I am sure all of these functions are on Cyanogenmod's to-do to support all of the hardware features of most devices.
Glove sensitivity functions perfectly in cyanogenmod, most sensors work perfectly as well. The eye-tracking features are likely not ever going to be a part of AOSP roms. Hopefully Hover gets picked up by more manufactures and becomes a part of AOSP and the SDK for apps, it has great possibilities for better intuitive interfaces.
stevey500 said:
Sadly, most of these functions have not been carried over to AOSP based roms. Most of these functions seem to arrive on Cyanogenmod first.
I do know that Cyanogenmod is currently supporting IR but it is not complete enough to run 100% daily driver. They're having GPU video/image rendering issues in some apps, camera isn't properly configured. It's all stuff being worked on but I am sure all of these functions are on Cyanogenmod's to-do to support all of the hardware features of most devices.
Glove sensitivity functions perfectly in cyanogenmod, most sensors work perfectly as well. The eye-tracking features are likely not ever going to be a part of AOSP roms. Hopefully Hover gets picked up by more manufactures and becomes a part of AOSP and the SDK for apps, it has great possibilities for better intuitive interfaces.
Click to expand...
Click to collapse
I see. Not even screen recording?
Is this the situation with all of the variants of the device?
I wonder how well other devices (even of other manufacturers) are supported by CM (and other AOSP based roms).
I assume Nexus is one of the best ones that they support.
AndroidDeveloperLB said:
I see. Not even screen recording?
Is this the situation with all of the variants of the device?
I wonder how well other devices (even of other manufacturers) are supported by CM (and other AOSP based roms).
I assume Nexus is one of the best ones that they support.
Click to expand...
Click to collapse
Screen recording is in the works on Cyanogenmod and in the process of being built for compatibility on all devices. It's a lot of work to build software in compatibility will all hardware. Nexus devices to get the extra bit of love because those devices are arms wide open to the developer community. Samsung, LG, and HTC are getting hit hard by locked bootloaders on the two giant carriers verizon and AT&T... if those bootloaders were not locked, I am sure that the flagship devices from those companies would be getting a LOT more developer support, especially from Cyanogenmod team.
Such as, the Galaxy S3 (and a moment for the S4) were the last devices that were getting insta-written AOSP code and compatibility support for AOSP based roms while the majority of them were bootloader unlocked/unlockable. The Galaxy S5 is being developed for, just a bit slowly, sadly. AT&T and Verizon models are totally bootloader locked with no current workaround.
The nexus devices may seem to be better supported by the developers but the Nexus devices aren't as complex and have a more basic hardware layout lacking alot of the extras and premium features of the samsung, htc, and LG family- those devices require more attention.
stevey500 said:
Screen recording is in the works on Cyanogenmod and in the process of being built for compatibility on all devices. It's a lot of work to build software in compatibility will all hardware. Nexus devices to get the extra bit of love because those devices are arms wide open to the developer community. Samsung, LG, and HTC are getting hit hard by locked bootloaders on the two giant carriers verizon and AT&T... if those bootloaders were not locked, I am sure that the flagship devices from those companies would be getting a LOT more developer support, especially from Cyanogenmod team.
Such as, the Galaxy S3 (and a moment for the S4) were the last devices that were getting insta-written AOSP code and compatibility support for AOSP based roms while the majority of them were bootloader unlocked/unlockable. The Galaxy S5 is being developed for, just a bit slowly, sadly. AT&T and Verizon models are totally bootloader locked with no current workaround.
The nexus devices may seem to be better supported by the developers but the Nexus devices aren't as complex and have a more basic hardware layout lacking alot of the extras and premium features of the samsung, htc, and LG family- those devices require more attention.
Click to expand...
Click to collapse
I see. So it takes a lot of work.
Say, you mentioned the SGS3. I have this device. Do you think it will ever support screen recording on CM ? Currently it's very very slow. I've tried the special customized rom that's based on Note 2, and this feature worked fine there. I've left this rom because of some reasons I don't remember about (maybe stability).
All those features are available in samsung based custom roms. Why does it have to be AOSP based?
Sent from my SM-G900F using Tapatalk

[Q] Custom kernel Android 6

I would like to ask if someone knows whether a custom kernel is about to be released. It has been shown for every nexus device that custom kernels can really boost performance (io scheduler, cpu-gpu governor). I just wonder why there is lack of custom kernels for nexus player which is the only nexus device where battery drain is of no concern!
adding ntfs and exfat support as well would be nice.

Categories

Resources