If you click on the main block itself, it automatically calls the number back. There's no long press expanded menu either. You have to click on the photo (in this case it's a blank photo), which then brings up a popup and then you hit the + icon.How is that not intuitive?
That's the first place I would look to add a new number from someone that called me.
Sorry you're right. Must've been my experiences with JB instead.We must be using different dialers. On my stock kitkat dialer, clicking on the number in call history page brings me to a full history/call details page at which point I can save their number/call it.
Same with the People app.
How is that not intuitive?
That's the first place I would look to add a new number from someone that called me.
From the main dialer I can't tell you how many times I long pressed that number waiting for a menu with 'add to contacts' to pop up
But adding more options and selections in the OS doesn't slow down the overall OS much. It's not introducing a brand new service. For example, the LED notification service already exists. It just lights up as white light only. No customization. No color, no intervals, etc. CM doesn't take any more RAM to run than AOSP.
TouchWiz is more than just additional features, and actually doesn't offer you the level of customization I'd like. TouchWiz is also a theme that increases the # of drawables and changes graphics, etc.
Adding options is NOT the same as TouchWiz.
For example, CM's native LED control is less resource intensive than LightFlow, and eliminates a background app that possibly gets killed and ruins your notifications. CM's brightness control curve eliminates the need for Lux, which is another app that must run in the background. Init.d scripts for custom kernels eliminate the need for custom kernel apps like FKU or fauxcontrol.
The point is there are values in the system that already exist, and by not offering those checkboxes and options in the system UI itself, you're forcing the user to install a 3rd party app which takes up RAM and system resources, slows down boot time, just to add functionality. I'm not saying that Google needs to replace every 3rd party app--just to add a bit more controls into its OS. Right now, I'd argue iOS7 in many aspects has more out of the box options and checkboxes for the user to play with.
You don't even have to go to the call history page, right next to the number is a (blank) contact photo with a tiny arrow in the corner indicating there's more to it. Just tap the contact picture and it shows an option to add to contacts.
that's going to be difficult when drunk
It's closer to 10mb on my side right now. Furthermore, it's a process that must stay alive and not get killed off by Android memory management. Since there's no way to make sure apps/processes are truly unkillable in Android (at least not w/o root), there are times when you have to worry that Lightflow may get killed and you stop getting blinking notifications. In fact that happened this morning when you mentioned RAM and I went to check my usage. I had to restart LightFlow.Many of those 3rd party apps are just exposing things in the system that already exist. I actually use LightFlow and have not noticed it using a lot of resources at all. 3MB of RAM. Big deal.
It's closer to 10mb on my side right now. Furthermore, it's a process that must stay alive and not get killed off by Android memory management. Since there's no way to make sure apps/processes are truly unkillable in Android (at least not w/o root), there are times when you have to worry that Lightflow may get killed and you stop getting blinking notifications. In fact that happened this morning when you mentioned RAM and I went to check my usage. I had to restart LightFlow.
My point is that Lightflow is still an additional requirement to get customized lights. You have to wait for the app to run at startup, which slows down boot. This would not be necessary if you had OS level controls. The same applies for apps like Lux and Quiet Hours apps, which if all implemented in the OS saves you from bloatware and boot times.
I think Xposed is the only way to really implement these features without having an actual app start up.
Battery life on my N5 hasn't been good as usually is. 3 hours today with light/moderate usage and it's at 75% already. Screen 38%, App usage 54%. Of app usage, 41% is Kernal(Android OS).
Possible that some App update has some process that's killing my battery?
You need to provide BBS screenshots, and/or Wakelock detector in addition to the battery screen in order for us to analyze that. App usage at 54% sticks out. What app is it?Battery life on my N5 hasn't been good as usually is. 3 hours today with light/moderate usage and it's at 75% already. Screen 38%, App usage 54%. Of app usage, 41% is Kernal(Android OS).
Possible that some App update has some process that's killing my battery?
You need to provide BBS screenshots, and/or Wakelock detector in addition to the battery screen in order for us to analyze that. App usage at 54% sticks out. What app is it?
PowerManagerService should be when your modem is working. 7 hours is a fuck ton of time. Your modem is held awake by something. With all those tools I mentioned, you should be able to pinpoint the app the next time it happens.I'll have to install Wakelock detector. The numbers are from using GSam Battery Monitor. I'm stock. Any of my installed apps all use less then 1%.
But Kernal(Android OS) is at 38%, Android System is at 3.5%, System(mediaserver is at 2%) and everything else is at less than 1%.
So, I think it's some process running under the Kernal and there are a lot of them running which could be from one the apps, I'm guessing.
Looking at Kernal Wakelock for the last 15 hours:
PowerManagerService.WakeLocks is at 7h 45m
msm_dwc3 at 5r 57m
Everything else less than 2h
I don't have Root access so, I can't get any other info from the app.
http://forum.xda-developers.com/showthread.php?t=2517430I have never once had an issue with LightFlow not working. Plus, all those other settings that custom ROMs add still cause the OS to use more resources. It might not show up as an app taking memory because it is part of one of the core OS processes(like AndroidOS or Android System). My phone still boot quickly as well which doesn't really even matter much since I don't reboot it all that often anyways. Also add in the fact that I don't care about any of the other features I've seen in several detailed review videos of different ROMs.
Plus, none of this takes into account the fact that installing a custom ROM voids the warranty and has the chance of turning your phone into a several hundred dollar paperweight.
http://forum.xda-developers.com/showthread.php?t=2517430
It's far from perfect, and it's a known issue in Android that there's no such thing as unkillable. Launchers can redraw, Chrome windows can need to be reloaded, and LightFlow can be killed.
With that said LightFlow works most of the time, but the reason you need LightFlow is that the service sits there listening to notifications, intercepts the notification and then overwrites the system's LED settings.
By having the functionality built into the OS/framework, there's no 3rd party IFTTT-like app that needs to remain open. The OS has native vibrate and notification APIs. The LED notification is tied to it. Similarly, the OS has native autobrightness functionality already. An app like Lux intercepts the light sensor readings and then overwrites screen brightness outputs. The point in having native OS functionality is you don't need an app sitting there waiting, which is a waste of resources. It's a service that you risk getting killed because it's 3rd party. If it's baked into the OS, it's guaranteed to work.
And while Lightflow alone might not slow down your boot times, having Tasker, LightFlow, BBS, Lux all load up (not too uncommon for a tweaker) is noticeably slower than having CM boot on its own. It's also a far bigger resource drain. Consider the other services that must run in the background (3rd party SMS, Whatsapp, Timely, Google Voice, Google Search) and how some apps ALWAYS insist on running (Facebook, Google+, YouTube) even if you don't use them. There's plenty of apps that load on their own to slow down your system. Why add unnecessary startup apps.
It seems like you didn't even read what I wrote. Sure, having something integrated into the OS means that an app won't be sitting there waiting but the core OS process will be sitting and waiting. For something like LightFlow either the app is waiting for incoming notifications to turn on the LED or the OS is doing the waiting. Same thing for something like Lux. Either part of the OS is sitting and waiting for new sensor data or the app is doing it. Either way something is sitting and waiting for something to happen.
As for the 3rd party apps getting killed sure, it does happen but from my experience it's very rare. Like I said, I'd much rather have a minimum base OS and add what I want (which is very little anyways) than have a ROM that is more bloated. You may not like a stock experience and may not care about keeping your warranty and that's fine. Personally, I'd rather have a stock OS(which CM is far from being) and a useable warranty. There is also other hassels involved with custom ROMs like stability and having to basically do factory reset for updates among other things.
Is it easy to install a clean non-bloated OS onto the Verizon LG G2?
I did read what you wrote. You're not understanding what I'm saying. You don't understand how LightFlow and Lux work. First of all, Android already has a notification API that apps hook into to properly vibrate, ring, and or blink the LED. There just isn't color control or any other custom options that LightFlow offers. As a result in addition to the OS waiting for notifications to come in, LightFlow has to also wait and intercept those notifications and override the LED options.
By having all that built into the OS adds zero additional resource bloat. It's extra code, but your OS is still listening for notifications. You're just giving the user to add LED custom notifications. The LED notification API exists already anyway.
Similar things happen with Lux. Lux intercepts the brightness sensor readings and therefore it must constantly sit there listening and intercepting. Android OS already has brightness sensor readings by default.
Both of these apps must take up system resources and intercept notifications, which doubles the amount of event monitoring that your phone does. Not only does Android do it, these apps read input invents. That's extra bloat.
So in the end, the phone will only be faster with these controls built into the native OS itself. Comparing to TouchWiz is not a fair comparison.
If you don't care about these features, that's fine, but having these OS features does not hurt you at all. If you're so set about running bare bones, why don't you just run a command prompt only and add whatever UI modules you want? Well obviously that doesn't make sense does it for user friendliness.
These features that I'm describing are what Paranoid Android, AOKP, and CM are all doing. They are NOT adding more bloat to the OS. The additional checkboxes, settings screens, etc. are adding controls that already exist in the OS and just making those options available to the user.
Something like Cyanogenmod or AOSP? Probably. It's not guaranteed to work 100% though as its harder to develop for non Nexus phones.
Also, DLeRium, you seem to think about this stuff a lot and have a few opinions on what is best/ideal. I'm curious, do you run a custom ROM, Xposed, both, neither? I've been going back and forth about this myself. Part of me wants the "packaged" customization a ROM provides and to avoid something like Xposed which, while maybe elegant, is essentially a very elaborate hack. On the other hand, I really hate the perpetual beta-ness of custom ROMs and don't think it's the ideal way to be using a phone. Think about it, even for a device like the N5, even 4 months after release, a popular ROM like CM is still not at a stable release yet. You might say the M builds are "stable enough", but they'll still have bugs and aren't production quality. I hate using pre-production software for months and months, and when it finally gets a stable release, the next version of Android is out and the cycle starts over again. For this reason I like the idea of staying with stock, stable firmware and "enhancing" it with Xposed. Curious what your thoughts are about that.
I think the real truth lies somewhere between what jimv1983 and DLeRium are saying. I agree with DLeRium that the OS is already doing several of these things, and adding more apps and third-party services to also do them or replicate them could be considered a type of bloat. To jimv's credit though, you really have no idea how the implemented feature is working in CM. It might be coded poorly, it might be doubling a routine running elsewhere, or hell, it could have a memory leak that ends up hurting you on RAM usage more than LightFlow does! I think everything being done efficiently in the core OS is always going to be most ideal (the too many cooks in the kitchen thing), but that doesn't mean an app like LightFlow is necessarily doing things poorly, inefficiently, or wasting much resources compared to another solution.