H20 feature Implementation - OnePlus 2 General

I noticed in theMM builds of H20os there's a feature to turn phones power on and of on a timer. This is a AWESOME FEATURE! Is it possible to bake that into any of the CM/AOSP-CAF builds available? Is the code open or closed source I can't believe if it is possible it's just been overlooked

Related

Feature request: blacklist

Hi everyone !
I just installed Paranoid Android and it is awesome, but I wasn't sure if I would install PA or CyanogenMod, and one of the killer features of CM is for me the blacklist (block incoming call + messages from select numbers)
Will this functionnality be implemented in PA in the future ?
Thanks a lot !
I'd like this feature to be implemented too, it's the only missing feature i need.
Why i Asked this feature to? Cause I'm paranoid.
I think this is a very important feature and the incall recording. Hope the team can enable them.
Yep , I think it will not be implement
This forum should not be used for feature requests. We have a bug tracker where all bugs and feature requests belong.
#stayparanoid

[REQ] More controll over the Pie Controls

As far as I know there are little to no options to configure the current PA Pie controls. I would love for it to be more configurable. I get that the more configurable options, the more complicated this might get but essentials like swapping back and current apps to me is vital.
Hope this can be implemented.
Everything is open source. Code it up, make it look good, and submit it to gerrit.
#stayparanoid
Pirateghost said:
Everything is open source. Code it up, make it look good, and submit it to gerrit.
#stayparanoid
Click to expand...
Click to collapse
Haha I like your mindset, but if I push my code it would probably cause a third world war. I could replace it with the default Pie Controls but I like the fact that this is more native-ish.
#stayingparanoid
One thing I really miss is the ability to change the google now shortcut, i keep activating it by mistake and i would like to remove it.
PA Pie is my favorite Pie. So much more responsive and quick then other pies that are out there. I also love that PA Pie is stationary. This allows muscle memory accurately gesture correctly every time. So please don't add customization if it involves changing over to Slim or other pies.

RRO vs CM theme engine

A call to the community to use RRO instead of CM's theme manager.
https://plus.google.com/+SykoPompos/posts/5M7tzmgHZpu
Sony intent on having swappabale themes worked with google to devise the current implementation of rro that provides a much more secure way of going about it.
They modified the asset manager to accept apks with just resources and map out the id of each resource in android and then overlay the modified resources at just runtime so those resources can map out to rro's changed or new resources to act like they were always part of those resources but only as long as that apk is there and loaded into the system.
With this system, it provides security because the system is already given permission but still confined in all of android but it is also powerful because new resources can made to add features, translations and so forth very quickly (OEMS are actually using it now to prototype )
With this system in place, the code was merged into aosp for lollipop, unfortunately with google keeping lollipop source mostly hidden, nobody realized that it broke in the process until 5.0 was already out and Sony quickly patched it in aosp for the next release (the 5 commits that need to be cherry picked for rro to properly work)
This means that future stock builds of android has this native theme engine built into it and Sony and Samsung and HTC are actually already using it (rumor is this works already in gpe Sony and Samsung lollipop builds) so it makes sense for the community to embrace it and build on it as our own project.
Cm though decided instead of embracing RRO (maybe they didn't know about it) ported their legacy code up for the theme engine with so much effort instead of looking for a new way with 13,000+ lines of code instead of probably about 200 lines of code to adapt the theme engine into was was already there so there is a ton of redundant code that is completely ridiculous.
Click to expand...
Click to collapse
Just started learning about this. Do themes have to be RRO specific or do CM themes work?
@sandys1
A thread to link to a G+ page does not constitute as a development thread.
This belongs in general.
tholmes8291 said:
Just started learning about this. Do themes have to be RRO specific or do CM themes work?
Click to expand...
Click to collapse
I think the security model differs in RRO , so I suppose it is different. I was not able to find a lot of documentation though.
sandys1 said:
I think the security model differs in RRO , so I suppose it is different. I was not able to find a lot of documentation though.
Click to expand...
Click to collapse
Yeah me neither. Thx
Two issues with this.
1. Nothing in your post is even remotely related to development.
2. RRO aka Layers, is still in beta. I doubt it will be anymore bug free than CM's Theme engine. (see post here).
You didn't link to a github, or any other form of code repository for developers to use. So I'm not sure what you're calling for them to use... Pulling a G+ post into their code repo won't do a whole lot. The only repos I can find for the group developing this is: https://github.com/BitSyko as you can see, they really don't have anything related to usable code posted.
So do you have links that would be useful for coders... or is this just another "HEY EVERYBODY CHECK OUT THIS COOL NEW THING I READ ABOUT!" post?
*edit*
After an hour or so of searching around... Here's the link you should have provided...
http://forum.xda-developers.com/and...o-apps-rro-t3012172/post58406220#post58406220
Post 2 provides the links to the code changes that must be included in the rom to use their layers (rro) system.
tholmes8291 said:
Just started learning about this. Do themes have to be RRO specific or do CM themes work?
Click to expand...
Click to collapse
They have to be RRO Specific. See their Wiki
Thread moved in the correct section.
We should have a list of which Roms support
Liquid Smooth supports it sorta? Although the dark and blue overlay does nothing for me

[Q] BEST lollipop rom for g3 --stock vs aosp--

hi my friend i have the verizon lg g3, running on kitkat custom stock rom.. skydragon!!
i want to know about what rom have more satbility, battery perfomance
im looking for this on a stock custom rom:
lollipop rom
no problem with xposed
everything works like a charm...
lg smart cover and smart cover works running xposed too
no crash in the more setting.
battery perfomance
system stability
PD: i know that some thread have a quick cover app.. to replace the stock app.. and its working with the g3 plus xposed! somebody test it or can review that!
if the rom is AOSP what rom is better and contain the following features:
double tap to sleep everywhere
double tap to wake
knock code
lg quick circle cover &smart weather
infrared controller
system stability
battery performance
some way to use google now theme with appdrawer folder?
PD: i know that some thread have a quick cover app.. to replace the stock app.. and its working with the g3 plus xposed! somebody test it or can review that!
i really feel very thankfull about the answer of this thread..
thnks you in advance
And I want a wife who has hot friends and will not sleep with anyone else but will let me hook up with said hot friends at will...
The point is: It's give and take; you have to figure out what is most important and go with it.
I may suggest that you learn a little more about Android, licensing, and the differences between stock and AOSP before laying out your list of demands, because many of these are just not possible.
Stock:
Xposed is currently in an alpha state on Lollipop, requires the removal of the smart weather and cover apps, in order to function on KitKat and Lolllipop alike. Going to the "More settings...." will produce a crash as a result of this removal. That is clearly noted in numerous threads for Xposed on LG.
AOSP/CM:
Knock code is an LG feature that requires their framework and, I think, a kernel module, too; no dice on AOSP.
You can get double tap to wake, double tap anywhere to sleep on lockscreen, and double tap on status bar anywhere. The implementation on status bar only is far smarter.
Quick cover is available; not sure about the circle..
LG Weather is an LG app and requires their framework; no dice. There are far better options available anyway.
The IR may not lend itself to every app, but the QRemote app has been ported and works great.
Google Now is available.
App drawer folders are a feature of certain launchers and most work fine on AOSP ROMs.
You may test anything that you like where it comes to Xposed. I'm sure that the devs would appreciate detailed feedback.
epidenimus said:
And I want a wife who has hot friends and will not sleep with anyone else but will let me hook up with said hot friends at will...
The point is: It's give and take; you have to figure out what is most important and go with it.
I may suggest that you learn a little more about Android, licensing, and the differences between stock and AOSP before laying out your list of demands, because many of these are just not possible.
Stock:
Xposed is currently in an alpha state on Lollipop, requires the removal of the smart weather and cover apps, in order to function on KitKat and Lolllipop alike. Going to the "More settings...." will produce a crash as a result of this removal. That is clearly noted in numerous threads for Xposed on LG.
AOSP/CM:
Knock code is an LG feature that requires their framework and, I think, a kernel module, too; no dice on AOSP.
You can get double tap to wake, double tap anywhere to sleep on lockscreen, and double tap on status bar anywhere. The implementation on status bar only is far smarter.
Quick cover is available; not sure about the circle..
LG Weather is an LG app and requires their framework; no dice. There are far better options available anyway.
The IR may not lend itself to every app, but the QRemote app has been ported and works great.
Google Now is available.
App drawer folders are a feature of certain launchers and most work fine on AOSP ROMs.
You may test anything that you like where it comes to Xposed. I'm sure that the devs would appreciate detailed feedback.
Click to expand...
Click to collapse
My work around for double tap to sleep anywhere was to use slim actions and place it on the home screen as well as double tap on status bar or nav bar.
I've been on aicp for a while now and really enjoying it. Very solid and a lot of features.

Less frequent notifications

Does PAC already include this type of feature? I don't want to run another module if it's already implemented and I just can't find it.

Categories

Resources