I'm on the v30+ and just received the attached message.
What's the date for the security patch?
My phone says Android version 7.1.2, Android security patch level: Oct 1, 2017
Performance - Can't say that I notice any difference, but this thing has always been smooth and fluid for me. I do notice that the AOD definitely moves around more than it used to.
Security - Any way to tell if the KRACK exploit has been addressed?
Signal strength indicator - Don't really care one way or the other.
I imagine KRACK hasn't been patched, given that the October 1 security level doesn't include it, but that's one of the changes in this update.
jlbattagli said:
Performance - Can't say that I notice any difference, but this thing has always been smooth and fluid for me. I do notice that the AOD definitely moves around more than it used to.
Security - Any way to tell if the KRACK exploit has been addressed?
Signal strength indicator - Don't really care one way or the other.
Click to expand...
Click to collapse
KRACK is such a big deal that I am sure it would have been mentioned in the log had the patch been included.
Related
Info:
Target Device: SM-T560NU only (gtelwifiue)
OS: Android 6.0.1 Marshmallow
Variant: LineageOS 13.0
Status: Usable as daily driver, but still to be considered experimental
This project is a side project of mine to bring Lineage 13.0 back to the SM-T560NU.
I recently purchased one of these, and use a few apps that have not been updated in years. These apps do not work on Nougat, therefore I needed Marshmallow.
vince2678 had a great Lineage 13.0 build, but had started to shift his efforts towards the more popular and updated Android Nougat by the time that I got this tablet. vince had started to warn that he was going to be dropping Marshmallow to focus on Nougat.
Therefore, using his code base, and attempting to apply some more modern patches to keep Lineage 13.0 up to date, I started creating my own builds in private. There was one single, obsecure link to it, on my website, and it was discovered. Since the community has shown interest in this project, and vince has now officially dropped support for 13.0, I am willing to release my private builds.
Please keep in mind that while vince's builds were designed to be as stock as possible, my builds are tailored towards my needs.
They are not perfect, but they work for me. There are still some issues to be ironed out, and sometimes new issues sneak in when you think you are just building a security update
But, since you wanted them, here they are. At the time of this post there is only one, but this will grow over time, when I have spare time to try to fix any issues and apply security updates.
All builds use my optimized kernel.
Releases and known issues:
You can find my builds over at:
https://losupd.zefie.net/builds/full/?C=M;O=D
lineage-13.0_j199_20170720
Android Security Patch Level: July 1, 2017
USB MIDI Support (example video of controlling Logic Pro X with the SM-T560NU)
No changes to previous issues in this build (same issues apply)
lineage-13.0_j196_20170617
Android Security Patch Level: June 1, 2017
AudioFX is missing (disabled in build due to unsolved issue in ROM causing crashes)
Updater is untested. You may or may not get a notification when a new build is available.
Flashing the recovery that comes with these builds is advised against. It may work but is untested. Use my TWRP Build.
Device encryption does not yet work
There is a strange issue that prevents you from taking still images using the built-in camera app. Preview and video works. As a workaround, use any third party camera app. I suggest Open Camera.
Just flashed it, everything works great so far.
Ive tried and liked very much
Smooth and lightweight
So far for me the camera dont work but i can record video
Also the encrypt tablet option does not seem to work (I select the option in the security part of the settings screen, it restarts tablet and thats it)
Other than that it seems to be perfect
Thanks for all the hard work
Solidium said:
Ive tried and liked very much
Smooth and lightweight
So far for me the camera dont work but i can record video
Also the encrypt tablet option does not seem to work (I select the option in the security part of the settings screen, it restarts tablet and thats it)
Other than that it seems to be perfect
Thanks for all the hard work
Click to expand...
Click to collapse
I knew about the encryption but the camera issue is interesting and strange. I just tried it and see what you mean.
I will see what I can do about these issues in the next update, which will probably be mid-august.
Thanks for the report.
The issue seems to be with the Camera app itself, and not any issues with communicating with the hardware (despite the error message), since other camera apps appear to work fine.
In the mean time, if you would like to take still images with this build, I would suggest this great and free (ad free as well) camera app from the play store:
https://play.google.com/store/apps/details?id=net.sourceforge.opencamera&hl=en
I have just tested it (with both rear and front cameras) and it can take still images.
560?
Is it compatible with T560 only ? Whats the difference between T560 and T560NU maybe US Market? or what the difference and where i can get a custom Recovery for the Tab?
bluedesire said:
Is it compatible with T560 only ? Whats the difference between T560 and T560NU maybe US Market? or what the difference and where i can get a custom Recovery for the Tab?
Click to expand...
Click to collapse
This is for the T560NU only, not T560. From what I know they have entirely different processors so there is no way for a universal ROM.
Thanks for this amazing rom. I noticed following: can't change the size of analog clock and sound on the speaker is not very strong.
jon355 said:
Thanks for this amazing rom. I noticed following: can't change the size of analog clock and sound on the speaker is not very strong.
Click to expand...
Click to collapse
The clock issue is likely upstream, since I can't think of anything I did that would prevent resizing of widgets, and other widgets appear to be resizable.
But I will look into it.
Speaker issue noted, there was some issue with the internal mic being too low that I tweaked, I may have to check the values for the speaker.
Edit: personal tests show speaker volume is fine. any louder could damage the speaker. if the volume is low, check that the tablet is not laying on a soft surface or something that would otherwise muffle the speaker in the back. When not obstructed, the speaker volume seems fine to me.
Any progress on Audio FX and Camera issues?
Jacsd said:
Any progress on Audio FX and Camera issues?
Click to expand...
Click to collapse
Unfortunately I have not had the time to work on this in a while. When I don't have time I just update the source and build (and hope it works) for the security updates. This only takes a couple of minutes as the build process does all the work. One should be coming in the next few weeks. Once the automated build finishes, I test it locally for about an hour and if its good, I release it.
I am not sure when I will have time to actually sit and go through the code to try to debug it to fix the outstanding issues. This can take hours or even days of dedicated time which I just don't have at the moment due to trying to keep my bills paid.
Stay tuned to this thread for updates though, and I apologize for the delay.
zefie said:
The clock issue is likely upstream, since I can't think of anything I did that would prevent resizing of widgets, and other widgets appear to be resizable.
But I will look into it.
Speaker issue noted, there was some issue with the internal mic being too low that I tweaked, I may have to check the values for the speaker.
Edit: personal tests show speaker volume is fine. any louder could damage the speaker. if the volume is low, check that the tablet is not laying on a soft surface or something that would otherwise muffle the speaker in the back. When not obstructed, the speaker volume seems fine to me.
Click to expand...
Click to collapse
After uninstalling 3rd party music app, volume is good again.
EDIT:
Unfortunately I am discontinuing this ROM. I made this ROM for my personal use, and it is no longer useful to me, and I do not have the time to debug it. Therefore, I am discontinuing it. The current builds and source will remain up, and if you guys are not having the issues I am having, and would like me to continue doing security updates, I will, so long as it still compiles without much work on my part.
There will be no updates to the existing issues though.
Despite my previous aversion to Android N, I would highly suggest vince's Lineage OS 14.1 builds. They have come a long way since I last tried them, and Android N isn't so bad after all
I haven't gotten a chance to do a logcat or anything, but I'm getting an instant bootloop after installing Nova Launcher.
It wasn't an issue until Nova updated a few weeks ago, and it affects both your builds. That's my favorite launcher, but I guess I can live without it
EDIT: I see that you're discontinuing this, so I guess this post is more of an FYI to other users.
I just finished setting up my P2XL from Google and noticed that the security patch level is Sept 5, 2017 while my older PXL is October 5, 2017.
Baseband, kernel & build don't match (no surprise - P2XL all newer)
Both phones show no updates available. Running on Verizon with no issues.
Noticing a few differences in settings sounds section too...
Odd...
Is this project treble?
No
halleyrokz said:
Is this project treble?
Click to expand...
Click to collapse
That is the security patch level of android. You can get more info about project treble here.
For everyone getting excited over Treble should keep this in mind
"Project Treble doesn’t necessarily mean that all handsets will see updates instantaneously, as Google is not handling them directly. OEMs are still free to tweak and skin the OS, as well as embed their own software into the Android OS release. So there’s still going to be some time taken for OEMs to build and test their own particular take on Android."
zelendel said:
For everyone getting excited over Treble should keep this in mind
"Project Treble doesn’t necessarily mean that all handsets will see updates instantaneously, as Google is not handling them directly. OEMs are still free to tweak and skin the OS, as well as embed their own software into the Android OS release. So there’s still going to be some time taken for OEMs to build and test their own particular take on Android."
Click to expand...
Click to collapse
Spot on. Treble just eliminates the need for new drivers, so OEMs don't need to wait for part manufacturers (like Qualcomm). But OEMs (Samsung, LG,...) are still the main culprit when it comes to wait times or not getting updates at all.
If community can make a custom ROM for a 5+ year old device, so can an OEM. Drivers are obviously there, they're just not interested in updating anything for more than 2 years (even less in case of low and mid range devices). Treble can't change that.
The only real solution would be "one size fits all" system, that gets pushed directly by Google to ALL devices - like desktop systems. But that would probably be way to big for available storage on phones ...
Sent from my OnePlus 3 using Tapatalk
Explorer23 said:
The only real solution would be "one size fits all" system, that gets pushed directly by Google to ALL devices - like desktop systems. But that would probably be way to big for available storage on phones ...
Click to expand...
Click to collapse
We're going very offtopic here, but the topic interests me so, eh.
If we're talking about size here, we can follow a method that has been used in Linux live systems for a while now: a tarred (.tar) or squashed (squashfs) images. These provide a small yet ”fast enough” images that can be smaller than their uncompressed counterpart. Size is not of the constraint nowadays with these at developers disposal.
Alternatively, you can have a system that Treble tries to achieve: a base image (AOSP), OEM-specific changes and drivers, and abstraction for said drivers and changes. This system still relies on OEMs (and SoC manufacturers to an extent) to actively update their changes to the base system (and we know how lazy some OEMs can be with their updates).
But this is very offtopic, so let me offset the talk a little.
------------
To OP: No, that is not Treble. Treble isn't something you can quite see in user space (i.e Settings app). What you're pointing out is the security patch level, that is, how "updated" your current system are to the security patches Google are providing.
The level is laid out in date, so "November 1 2017" would be a fairly recent update. These patches get updated monthly, and seeing that you're using OxygenOS, means that you'll have to wait for OnePlus to push the security update after Google pushes them.
F4uzan said:
We're going very offtopic here, but the topic interests me so, eh.
If we're talking about size here, we can follow a method that has been used in Linux live systems for a while now: a tarred (.tar) or squashed (squashfs) images. These provide a small yet ”fast enough” images that can be smaller than their uncompressed counterpart. Size is not of the constraint nowadays with these at developers disposal.
Alternatively, you can have a system that Treble tries to achieve: a base image (AOSP), OEM-specific changes and drivers, and abstraction for said drivers and changes. This system still relies on OEMs (and SoC manufacturers to an extent) to actively update their changes to the base system (and we know how lazy some OEMs can be with their updates).
But this is very offtopic, so let me offset the talk a little.
------------
To OP: No, that is not Treble. Treble isn't something you can quite see in user space (i.e Settings app). What you're pointing out is the security patch level, that is, how "updated" your current system are to the security patches Google are providing.
The level is laid out in date, so "November 1 2017" would be a fairly recent update. These patches get updated monthly, and seeing that you're using OxygenOS, means that you'll have to wait for OnePlus to push the security update after Google pushes them.
Click to expand...
Click to collapse
There never can be a one size fits all OS. Even Linux can't really pull that off for every device.
See this is another thing that will never happen. Oems will never upload their code changes to aosp as Google intends. Most of the time due to the fact that they don't write the code for the different parts like BT, Wifi chips etc. This code comes others which is closed sourced and paid for.
Treble will most likely never become much. Already too many people misunderstand what it does. That i can't blame people for. Things like the xda portal that are giving out bad info is gonna cause a huge amount of drama over it.
I'm on the final Pie version PQ3A.190801.002 rooted with Magisk.
Reasons that others have decided to stay with Pie for now:
1) No TWRP
2) Battery life worse on 10 (for some)
3) Reported issues with colors
I reviewed the security bulletins but there are multiple severe and critical issues patched with every release, so it's hard to tell which are significant threats.
I read the thread that clarifies that it is not possible to apply security patches without installing Android 10.
I'm happy with Pie, and lean toward "if it aint broke don't fix it" unless there are significant security issues.
Can anyone comment on other data points that should be considered while deferring the update to Android 10?
I mean, there is not anything that is game changing about it. My battery is a little better actually. Lack of TWRP is something, but it does force you to figure out how to do things in a new way, which might be the only way in the future. After going from DU on Pie to stock on 10 I simply set my phone up exactly the same, so I really see little difference. I learned a bit about making Magisk modules in order to systemlessly change some things, guess that was a personal benefit (I have to modify vendor partition to get VoLTE and such to work properly).
I would tend to agree though, if it ain't broke don't fix it. I see no substantial changes in the phone's functionality.
Hi, just posting this in order to have more information on this update, the changelog states only an update of the security patch up to February 2022 security patches, nothing else is said.
I've seen a few bugs on 13.0.3.0 such as bubbles of chat cannot be closed when in landscape, you must go in portrait orientation to close the bubble of chat.
But I don't know if anything has changed about Battery Life, I haven't had issues with the 120hz/60hz refresh rate of the screen so far.
I hope this post will help people in better knowing what the upgrade fixes and what it doesn't and also if it introduces new issues or not.
For me it fixes the incredibly laggy notification shade (on 13.0.3 it was like a slideshow, now after the 13.0.4 update is is buttery smooth). I also noticed that apps that support material you / monet now use the wallpaper color. My battery life is the same, no issues on that front.
i have a strange issue, sometime the first 4 cpu cores get stuck at 1800mhz
verified with aida64
happens randomly after long standby or long charging and increase idle power usage significantly. I have to enable and disable ultra battery saver to get them unstuck
I've also had an issue, had to reboot my POCO F3, and the update disappeared... I can't even force it manually, the update is no longer here no matter how much I check, seems like a very useful bug....
Furthermore, I'm probably going to move on to LOS 19 or DivestOS (a more secure focused fork of LOS) when we have an official support out for the POCO F3, then I'll update the firmware inside the recovery I guess
AkechiShiro said:
I've also had an issue, had to reboot my POCO F3, and the update disappeared... I can't even force it manually, the update is no longer here no matter how much I check, seems like a very useful bug....
Furthermore, I'm probably going to move on to LOS 19 or DivestOS (a more secure focused fork of LOS) when we have an official support out for the POCO F3, then I'll update the firmware inside the recovery I guess
Click to expand...
Click to collapse
Have the exact same issue
Appeared a couple of times , could not update at that time due to low battery, after charge update dessapeared and cant get it back
Clear the cache for the updater app. That might help.
_j3roen said:
Clear the cache for the updater app. That might help.
Click to expand...
Click to collapse
I can confirm that. Clearing Updater cache brought the update immediately.
I also did the update, but my cache must have cleaned itself alone somehow, I noticed now that some chat bubbles are even more buggy in landscape for instance.
Material You has been added, support in most apps, like for instance in a browser, your navigation bar has now an orange tint, before it did not, many apps that do support Material You, I guess are affected by this new feature.
I have no idea however where you can configure such.