Longgg time Boeffla supporter but development has stopped so I'm looking for a replacement...!
Currently running OxygenOS with Pie... I'm looking for the simplest functionality for fast blinking LED notifications...
Kernel seems to be the only way to achieve this..?
Shout out to Andi/@Lord Boeffla -- I'm really missing your kernel development! I hope your enjoying whatever you are doing with your time now
Thanks in advance!!
There are custom kernels who have those commits you can read in the description of those kernel if they support notification led thing or not. Maybe smartkernel, and ex kernel does support it.
Related
Hey whaddup, I'm certain I have to be careful with how I ask this. I'm on Miui's ROM right now and see tremendous benefit of using an AOSP rom. I had Fresh since I got my Evo and I feel like I have experienced the best of both worlds.
Now I'm looking at Cynogen. What are some of the perks of having Cynogen over Miui? Knowing they both have different strengths, is their more stability in Cynogen? Are alot of the issues in Miui addressed already in Cynogen i.e. MMS problems, Kernal instability, Camera FC, etc.?
I'm thinking about making the transition and just looking for some insight. While I like Miui's interface, if Cynogen has more stability and alot of the issues fixed then I'm on my way.
Thanks
CyAnogen's roms have always been my favorite. MIUI is very different, and that is cool, but it is far too appley for my tastes. In my opinion, CyanogenMod has many more settings features and there is a lot of stuff to play around with. It is also a very very fast and clean rom, so you don't have much of the eye candy that is in MIUI. I would suggest making a nandroid backup of your MIUI setup, and try CyanogenMod out. But I would recommend flashing the nightly build #187. There are a few bugs worked out that are in the RC2, and it includes settings to use the Wimax led for notifications
MIUI is basically an old version of CyanogenMod, skinned to look like iOS. So while CyanogenMod isn't as "polished" as MIUI, it does allow for more customization, and has far more features. In addition, it is constantly in development, and anyone can contribute.
Just a few things that CyanogenMod has lately added:
New kernel (2.6.35.9)
New lockscreen gestures, and Phone + Messaging slide-tabs (like the unlock and sound sliders, but they go directly to your dialer or messaging app of choice).
Notification bar power controls
Latest version of ADW and SuperUser
Always-on or selectable lockscreen music controls
Can hide signal bars in favor of a -dB numerical indicator, or both.
Battery level as text over the actual battery icon.
Have the notification drop-down retract after selecting one of the power controls
Select to have national or international roaming, seperately.
Forced-roaming
HTTP/SOCKS proxy
VPN compatibility
Force an application to install to SD/Internal
Quick unlock (don't have to press OK to unlock)
Menu unlock
Disable unlock slider (in favor of menu or gesture unlock)
"Quiet hours" (disable SMS alerts while you sleep, but not your calls!)
WiMax LED for notifications (haven't seen this in use yet, but I saw the commit for it)
iOS-like rubbery "overcrolling"
Manipulate timeouts for when to lock phone after power button is pressed or screen turns off from inactivity
Built-in equalizer
Music player gestures
WiMax support (hopefully) coming soon!
HDMI support supposedly just around the corner
And there's tons more. Really, someone could write a book and have to update it every week to keep up with the sheer number of tweaks, customizations, and features of CyanogenMod.
Wow.. Thanks to both of you. This is exactly what I was looking for. So now the question is do I go to Nightly or RC. I hear what Leukay is saying about the bugs.
Last 2 question....what is the difference between Nightly and "regular" cynogen? Do I need to partition my SD CArd in order to flash this ROM?
I will be flashing this tomorrow.
I personally always run the nightlys. I like to have the newest builds of roms. No you dont have to partition your SDcard to flash Cyanogen roms.
The RC's are the Nightlies, just they're only made once every now and then, when Team Douche feels confident that the software is fairly stable.
Nightly and "Regular" (Or "Release") are the same thing, just Release is more stable than RC or Nightly, when the team feels that things are smooth enough.
Nightlies have the latest and greatest features (new kernel, new tricks, etc.) and some of the bad features (battery draining features, bugs, etc.).
Makes perfect sense now. Thank you to all of you for the info. Bout to come on over.
Sent from my PC36100 using Tapatalk
Just remember: There are no ETA's, and Nandroid backups are your friend.
Coming from a Galaxy S3, so far have only found one rom that gives the option to toggle fast charge from the notification drawer - BeanStalk Rom (T-Mobile). I was using Slimrom previously, but the S4 versions do not include the option. I'm using Ktoonsez kernel which supports Fast Charge.
1. Where would I start if I wanted to learn how to pick and pull features from different roms or simply add features, such as adding a fast charge toggle?
2. Is there a way to use the custom tile option to add a fast charge toggle?
3. Are the simpler ways of doing this kind of stuff and I just haven't done enough research?
Thanks in advance and please let me know if I can provide more information.
TASL said:
Coming from a Galaxy S3, so far have only found one rom that gives the option to toggle fast charge from the notification drawer - BeanStalk Rom (T-Mobile). I was using Slimrom previously, but the S4 versions do not include the option. I'm using Ktoonsez kernel which supports Fast Charge.
1. Where would I start if I wanted to learn how to pick and pull features from different roms or simply add features, such as adding a fast charge toggle?
2. Is there a way to use the custom tile option to add a fast charge toggle?
3. Are the simpler ways of doing this kind of stuff and I just haven't done enough research?
Thanks in advance and please let me know if I can provide more information.
Click to expand...
Click to collapse
If you know how to compile your own ROM, these commits solves your problem:
https://github.com/kasperhettinga/a...mmit/cd56dbb3c99a13bc101ed700e4e0143a67ad2b5b
https://github.com/kasperhettinga/a...mmit/c4aa1b00cdca748c6a506defc45bee95aa3486ce
Other option is use an app widget: Fast Charge
A starting point! My world for a starting point! I have seen multiple threads on how to compile an author's rom, but have yet to try my hand (I took the path more traveled, social sciences lol). This seems like a problem/solution moment I can use to educate myself. Thank you very much.
Hi all,
A while back I asked what you guys would like to see from a ROM and that never took off however I did take available suggestions to heart.
Let's start with a bit of background. In 2012, I was introduced to the whole concept of Android development. I rooted the device I had at the time, installed CM, and for a while everything was great. What I didn't like and still don't like about CM is that it is somewhat lackluster when it comes to features and what I didn't like about other ROMs at the time was that they had far too many. Eventually I gave AOKP a shot and its been a favorite of mine for a long while.
Jump to the present. I can do a lot more in terms of development, I can do things now that I had only dreamed of doing a few years back. I saw AOSParadox and the idea of a fully optimised AOSP ROM really appeals to me.
Meet AOKParadox: sheer optimisation and freedom without insane decisions, and the lack of features.
Here's the features I plan to use so far:
1. Compilation with the Uber toolchain (ready)
2. CAF applications and optimisations (Sultans drivers and SWE browser are what's planned)
3. Integrated flashtool (maybe flash fire)
4. Boeffla (with Swell-V6 as default along with my other profiles)
5. An Adblocker (thinking AdAway)
6. Aegis (no longer possible)
7. Xposed (I won't support those using it however)
8. ViperAtmos (Viper is ready however Atmos isn't)
9. Integrated SuperSU (Consider it done)
10. A custom HAL (ready for alpha)
11. Layers (will replace CMTE) (CMTE removed, need to find layers commits)
12. A dark mode (ready for alpha)
13. AROMA (... maybe, poses issues for some)
I plan to integrate most of these into the sertings menu. Note that a few of these features may not make it into the final product and I may implement other features... I have to ask permission of course. I can't just steal work from other developers
Any suggestions are incredibly helpful and if a developer would like, I would consider putting your work here too.
I'm going to start work bow and hopefully seed an alpha to those I trust in the coming weeks.
Suggest away,
RJ
Edit: I've realized that the developers of AOSParadox may feel offense due to the name I've chosen, and as such, AOKParadox will no longer be named. Suggestions are welcome.
Would it be posible to add support for cm13 themes or layers?. cuz that would be awesome.
elander said:
Would it be posible to add support for cm13 themes or layers?. cuz that would be awesome.
Click to expand...
Click to collapse
AOKP supports CMTE by default however I could look into layers instead
That sounds like a great idea! I would base your device tree of the CM one and the kernel also. I like that you want to use layers instead of CMTE
Maybe I can assist you in some things, but I'm not an android rom developer.
taaeem said:
That sounds like a great idea! I would base your device tree of the CM one and the kernel also. I like that you want to use layers instead of CMTE
Maybe I can assist you in some things, but I'm not an android rom developer.
Click to expand...
Click to collapse
Definitely. Considering CM uses CAF now I don't have much to do in that respect.. Maybe I'll pull in Sultans qcom drivers. Not sure they'll work yet though. Definitely going to modify the kernel a ton though.
Your assistance would be much appreciated. Thanks.
Although I mentioned modifying the kernel earlier, there is one I'd like to ask to implement. Not giving anything away, but I've contributed a little bit to it on the CM alpha side
Edit: I was just able to give you five likes on one post. Weird..
In my opinion it wouldn't have sense to change kernel cause the built-in one is optimized for CAF sources wich is the main feature of AOSParadox. AOSParadox team will also probably add full Layers support, gestures, an option to switch from hardware keys to navigation bar and a black theme in the upcoming build.
The features that I would like to see added in AOSParadox are:
- OTA updates support
- built-in Viper4Android
- built-in SuperSU
- built-in AdAway
- removed old and ugly AOSP apps like music or browser (this one possibly replaced by CAF browser)
- quick pulldown, notification LED control, long press recent button to open the last used app and customizable power menu (with advanced reboot)
- all these features well-ordered in settings just like CyanogenMod
- apps like Layers Manager, Super SU and Viper4Android integrated in settings
- duble tap to wake in settings without kernel adiutor workaround
Inviato dal mio ONE E1003 utilizzando Tapatalk
Diego98 said:
In my opinion it wouldn't have sense to change kernel cause the built-in one is optimized for CAF sources wich is the main feature of AOSParadox. AOSParadox team will also probably add full Layers support, gestures, an option to switch from hardware keys to navigation bar and a black theme in the upcoming build.
The features that I would like to see added in AOSParadox are:
- OTA updates support
- built-in Viper4Android
- built-in SuperSU
- built-in AdAway
- removed old and ugly AOSP apps like music or browser (this one possibly replaced by CAF browser)
- quick pulldown, notification LED control, long press recent button to open the last used app and customizable power menu (with advanced reboot)
- all these features well-ordered in settings just like CyanogenMod
- apps like Layers Manager, Super SU and Viper4Android integrated in settings
- duble tap to wake in settings without kernel adiutor workaround
Inviato dal mio ONE E1003 utilizzando Tapatalk
Click to expand...
Click to collapse
Oh, I won't be using AOSParadox as a base. I actually looked at their kernel and device tree and it doesn't differ much at all. It would be easier to just fork Ashwins and build from there. CM is CAF based now in this respect. Thru just lack proper qcom drivers. I'm going to see if I can implement Sultans drivers for the One. Obviously jot all of yyrm will work but its worth a shot.
OTAs won't happen. I'm sorry, but I have no way of hosting builds yet.
Layers manager will be implemented
The CAF browser is definitely going to be there
Everything else I've already mentioned and is available from AOKP.
Thanks for the feedback!
I misunderstood, anyway the OTA support isn't that important and your ROM looks promising. I'll give it a try when it comes out ?
Inviato dal mio ONE E1003 utilizzando Tapatalk
Looking good from the features
Just wanted to say that don't use Aegis because it creates lots of problems for apps such as ADM
And Xtreme music sound mod would be great in place of viperatmos
Adesh15 said:
Looking good from the features
Just wanted to say that don't use Aegis because it creates lots of problems for apps such as ADM
And Xtreme music sound mod would be great in place of viperatmos
Click to expand...
Click to collapse
Xtreme music requires SELinux to be disabled last I checked and I'm not one to really do that for more options in terms of equalization. I think Atmos and Viper should suffice. Thanks for the feedback. Maybe it will show up as an option in AROMA whenever I chose to implement it!
RJDTWO said:
Hi all,
RJ
Click to expand...
Click to collapse
Wow, I have no clue about the different ROM types (apart from Slimroms and miui) but one can only admire the level of effort that you are putting in to this! Looking forward to the rom, can't think of anything else than you already put on the list.
Thanks!
Unfortunately Aegis is no longer a possibility. I require special privileges to access specific repos on GitHub...
@RJDTWO Can you port Miui ?
Many users are waiting for Miui on onyx
RJDTWO said:
Oh, I won't be using AOSParadox as a base. I actually looked at their kernel and device tree and it doesn't differ much at all. It would be easier to just fork Ashwins and build from there.
Click to expand...
Click to collapse
Then why call it AOKParadox? :/
I'm here just to wish good luck with the project and say that it is an amazing idea
Not asking for any features in particular just giving you my thumbs up
Quasar said:
Then why call it AOKParadox? :/
Click to expand...
Click to collapse
Have a better suggestion? I'm open to names.
AOSwellP anyone? In honor of the profiles I make?
RJDTWO said:
Have a better suggestion? I'm open to names.
Click to expand...
Click to collapse
Any rules about the names? Things you really want to have in it, like AOK or Paradox? I just finished reading Ready Player One, so I have plenty of names and references
charliebigpot said:
Any rules about the names? Things you really want to have in it, like AOK or Paradox? I just finished reading Ready Player One, so I have plenty of names and references
Click to expand...
Click to collapse
It would be nice to keep AOK in the naming scheme however I'm open to anything really
I don't adding xposed would be a good idea. But it's me
Hey guys,
I know there are three OOS Roms out there.
FreedomOS
xXx no limits
ExperienceOS.
What are the differences?
And is there any OOS rom out there with customizations?
E.g. Center clock...
I know there's a Substratum module for that but i prefer inbuilt customization. Don't ask me why..
I understand where you coming from, OOS is pretty ok but sometimes you just want to have those extra customizations built into the ROM it self instead of having to sideload it with some side effect. For me the thing I miss the most in the use my substratum themes. I like having my system show one color for everything themed out nicely, OOS theme is half way done and limited as it still leaves a portion of other things un-themed. IE keyboard, dialer.
I haven't tried any ROMs yet since my device arrived just today, but so far I'm thinking of giving Freedom OS a shot.
As soon as a LOS based ROM like RR becomes stable, I will be switching to that.
And as soon as an AOSP based ROM releases, I'll be switching to that lol
Agree with you guys.
So anyone knows the difference between those three roms?
Hi to All,
And specially to devs.
I have one question. Do you think it is possible to increase brightness intensity during night mod.
With Oreo and Pie we have now have option to enable night mod which dim the screen and bring blue filter at night.
Altrought the blue filter is weak regarding what APK like c.lumen or f.lux can propose.
The thing is that c.lumen do not work anymore on devices above marshmallow and f.lux stop to work when screen is wake up trough fingerprint or so.
I wonder if there is a way to tweak directly Pie night mod, maybe via magisk mod, so we have deeper blue filter without the need of side APK that work more or less.
Thank you for reading... And answering.
If you're willing to try another app... Night Light works well if you use a kernel that supports KCAL (e.g. ElementalX or blu_spark).
https://play.google.com/store/apps/details?id=com.corphish.nightlight.donate
Note: This is the donate version, there's also a free version. But it's worth every penny.
Will give it a try. Altrought messing with kernel isn't my thing.
I will read carefully the thread about elementalx