Has anyone checked this out? It shows your logcat and dmesg on boot. I just installed it on my HTC10 and it is pretty cool when your phone boots up. Something else chainfire has given us that's awesome. He released this in 2014, i can't believe i never seen it.. It was just updated this year November 16, 2018.
https://play.google.com/store/apps/details?id=eu.chainfire.liveboot
Related
I have an LG G watch connected to my Galaxy S5 running CM13.
Even though I have 'Mute phone alerts & calls' turned on in AW, the phone still rings.
This worked properly on CM12.1 and still works if I restore my last twrp backup of CM12.1.
Not sure where to post this because I don't know if it is a problem with Android Wear, Marshmallow, or Cyanogenmod.
I see lots of people posting this problem for lollipop but it appears to have gotten fixed. Now it's back. At least for me.
Anyone else having this problem or is it just me?
Can confirm that I have the same issue since March update. I am running pure nexus April build with April security update and I still face the issue. Seem like a prevelant issue as far as I can read. I really hope google fixes it
SpidySun said:
Can confirm that I have the same issue since March update. I am running pure nexus April build with April security update and I still face the issue. Seem like a prevelant issue as far as I can read. I really hope google fixes it
Click to expand...
Click to collapse
Are you saying you had a version of Marshmallow (CM13) that DID work? If so, what was the last working version?
Thanks
I use Pure nexus rom which is CM based. The Feb build worked like charm and that was marshmallow
SpidySun said:
I use Pure nexus rom which is CM based. The Feb build worked like charm and that was marshmallow
Click to expand...
Click to collapse
I intend to track down the version that broke it so maybe I can spot the actual change and try building with out that change. Could you tell me the last version of CM13 that worked and the first version that didn't? I was a bit late to the CM13 party and the first version I tried was well into March.
Feb update worked
anything after fed doesnt work (atleast in PN rom)
SpidySun said:
Feb update worked
anything after fed doesnt work (atleast in PN rom)
Click to expand...
Click to collapse
Do you have a date for the Feb update that worked? I tried a 3/1 nightly and it doesn't work.
U can check the PN thread for a date
I check the Cyanogenmod site every once in a while, and to my surprise as the title says, CM14.1 was finally released today. I really need my phone right now so I can't mess with it, but I will definitely be installing it in the future a) to start getting up to date android security releases and b) to upgrade to Nougat. I am hoping that CM14.1 will be released for the Nexus 4 soon as I would install it there immediately and use it as both a backup phone and to discover all the features of CM 14, as I never used any CM in the past.
http://get.cm/?device=osprey
Thanks for the heads-up. Appreciated.
Hi, I have a Nexus 6P with a "MegaPixel" rom running on v7.1.1 and the security patch is at Dec 5, 2016
I just got a notification of an update. I tapped install and it just restarted the phone to recovery (TWRP). I rebooted back to system and the notification disappeared.
I tried to check for update but it showed nothing, and the Security patch is still at Dec 5, 2016.
The kernel I am currently running is ElementalX kernel. And yes, it updated to support Feb 2017 security patch.
On another topic, my battery life is ****, and this is the main reason I changed ROM and kernel but it didn't help by much(I am talking about 2.5 screen on time with 50%-70% brightness)
Thanks from advanced
Hi... Just look in the thread of MegaPixel... But it seems like last update was released in December 2016. You can't get last security patch if the dev doesn't update his ROM. You'll have to wait for an update or switch to another one.
As for battery life. It really depends on how you use use your phone. There are a lot of threads which aim to help with battery. I invite you to start reading the forum a little bit, I'm sure you'll find some tweaks to improve it.
Okay. We can understand that 2017 isn't over yet and it is dec 2nd. They still have plenty of time to provide the Oreo Update (and I hope they will stick to their promise).
But where is the KERNEL SOURCE? It have been almost 3 month since the device have launched in India but still no news about the kernel.
Loving my A1 but this thing is frustrating.
I am very confused about the Vendor Security patch for Open Beta 17. I am currently on a Custom ROM and Custom Kernel and when I go to settings>About Phone>Android 9, I get a detail overview of the phone and one of those details is Vendor Security Patch Level and for me it states it's September 5th 2018 while Android Security Patch is September 5th 2019.
My question to those of you reading this is, What should Open Beta 17's Vendor Patch be on ? I find it incredibly hard to believe that the Vendor level hasn't been updated since September 5th of 2018. Please send me a screenshot of your current Vendor Security patch or at the very least tell what the date for Open Beta 17's Vendor Security Patch Level should be. I went ahead and looked with root explorer at the Vendor build.prop and it says the build date of the Vendor is August 30th of 2019 while the security level is September 5th of 2018. To me, this seems like a mistake because I don't think the Vendor Security should be a WHOLE YEAR BEHIND the Android Security Patch.
I know it shouldn't matter and I'm not a big "Security freak" but I like consistency and the screenshot below is my problem. I was told it was OnePlus's fault and there isn't anything we can do about that.
Down below I am leaving two screenshots, One is of the settings>About Phone and the other is the Vendor build.prop.
I would appreciate it if someone told me this is correct and provided me a screenshot or to let me know if it's a mistake done by OnePlus and don't worry about it .Thanks in advance for anyone who replies helping me out with this. Greatly appreciate it.
As you said:
a mistake done by OnePlus and don't worry about it
Click to expand...
Click to collapse
That prop is just a string, OnePlus/custom rom developer can make changes in /vendor daily, but if they don't change that text, it will continue to show an old date, it can also happen in the opposite way.
onliner said:
As you said:
That prop is just a string, OnePlus/custom rom developer can make changes in /vendor daily, but if they don't change that text, it will continue to show an old date, it can also happen in the opposite way.
Click to expand...
Click to collapse
So do I just change the date or is it really September 5th 2018. The build date of the Vendor is August 30th 2019 but the security is September 5th 2018. Should I just change it to August 30th 2019 or leave it alone ?
Edit: I can change it to August 30th 2019 but I don't want it to be false.
Sadistic_Loser said:
So do I just change the date or is it really September 5th 2018. The build date of the Vendor is August 30th 2019 but the security is September 5th 2018. Should I just change it to August 30th 2019 or leave it alone ?
Edit: I can change it to August 30th 2019 but I don't want it to be false.
Click to expand...
Click to collapse
Change it? That wouldn't change anything, it's just text.
onliner said:
Change it? That wouldn't change anything, it's just text.
Click to expand...
Click to collapse
Well it changes the date of the Vendor Security Patch and if the build date for the Vendor is August 30th then maybe they forgot to change the Vendor Date. I don't know how the vendor partition works but it's literally a whole year apart from the Android Security Patch and it doesn't make any sense.
Here the after result of changing the date. I have no way of knowing if the security part of the vendor partition is August 30th 2019 but I've seen other people show me screenshots of the vendor higher than September 5th 2018.
What version of OOS are you on and what is your vendor date, and if you're on a Custom ROM then could you show me a screenshot of the date your vendor is on ?
Well I looked on my device, currently T-Mobile Stock Firmware locked. I dont have the ability to see the Vender partition info like RR shows you.
However, as long as you flash the latest beta and or stable, you will have the latest update for the vendor partition.
I wouldn't worry about the text of the matter. Like the other guy was saying before me. The edits you made don't change anything except what is displayed on that one specific screen. It doesn't change anything in the vendor partition.
Scott said:
Well I looked on my device, currently T-Mobile Stock Firmware locked. I dont have the ability to see the Vender partition info like RR shows you.
However, as long as you flash the latest beta and or stable, you will have the latest update for the vendor partition.
I wouldn't worry about the text of the matter. Like the other guy was saying before me. The edits you made don't change anything except what is displayed on that one specific screen. It doesn't change anything in the vendor partition.
Click to expand...
Click to collapse
Well first off I just want to thank you and the other person as well for replying, seems like anytime I ask this kind of question it gets ignored and probably for a good reason. I do know that changing the text will only change what is displayed but my confusion is that I under the impression they forgot to update the date of the Vendor Security Patch Level. It is the latest Beta (Technically 16 is since they apparently pulled Beta 17 away because of an issue.) and so I have no reason to care about it but it just throws me off because it says September 5th 2018. I'll leave it be and wait for Android 10 firmware to release next month (Hopefully).