I was wondering about updates if it turns out that LG won't give them any more.
The V60 is supposed to have project mainline, and so there are, I think, 23 modules that can be updated directly by google (Oh, joy!)
But I'm not sure they are, or how to check when they were, or enable updating.
Looking in /system/apex I see apex modules, all dates Dec 31, 2008. Not very helpful. Would updates go here?
Has anyone seen mainline modules updates for the V60?
Related
I have been looking for a good CM 7.1 based ROM and am having a hard time deciding on one. The main thing I am looking for is the advanced lock screen delay and timeout settings. I cannot tell if this is a difference between CM 7.1 and 7.0.3 or if it is just a setting that some ROMs have and some do not.
Can someone shed some light on this for me? Is there a way to add this functionality? (I care because work enforced a security lock on my phone for email access, but I don't want to have to type i tin EVERY time the screen goes off. iPhones and WinMobile don't. It seems to be a flaw in Android's ActiveSync).
Thanks in advance.
This feature is new in CM 7.1. However, other users have reported success using Delayed Lock + WidgetLocker apps from the market to effect the same functionality, though I am uncertain how well they play with the Exchange server's demands.
Alternately, if you really don't want this security lock feature at all then you can find versions of Email.apk that will just lie to the Exchange server about the phone's configuration. Then you can configure your lock settings however you like. Ah, the classic fallacy of a security model that trusts the client...
I actually like the security of the password. I just wish it behaved like ActiveSyns on every other type of device (Win Mobile, iphone, etc) and let you set a delay (defined by the system administrator) for when the device security locks, not every time the screen goes off.
I wish we had a good CM7.1 ROM. Oh Z, wherefore art thou?
Yeah, running a nightly (or a ROM that pulls from nightly) is currently the only practicable choice to get the feature.
I backported the feature's code to the CM 7.0.3 codebase and built a custom ROM for my own device. I wanted the feature but didn't want to run the unstable nightly on my primary phone. Well, "backport" isn't the correct term, because the feature was developed against 7.0.3 and was rebased to 7.1 for submission to the source repo. But you know what I mean (haha).
organophosphate said:
Yeah, running a nightly (or a ROM that pulls from nightly) is currently the only practicable choice to get the feature.
I backported the feature's code to the CM 7.0.3 codebase and built a custom ROM for my own device. I wanted the feature but didn't want to run the unstable nightly on my primary phone. Well, "backport" isn't the correct term, because the feature was developed against 7.0.3 and was rebased to 7.1 for submission to the source repo. But you know what I mean (haha).
Click to expand...
Click to collapse
Care to share?
rearview said:
Care to share?
Click to expand...
Click to collapse
You know, I realized after posting that I probably look like a jerk for not offering. I apologize. There are issues that seem to preclude this, however.
The target of the relatively minor code changes necessarily included one of the fundamental framework jars.
When I was developing the feature, I only compiled CM for the Droid Incredible. Didn't make sense to compile for platforms I can't use/test, especially given the next point.
It takes my machine 90+ minutes to compile a ROM for a platform.
I believe that if I gave you a flashable update.zip to replace the affected jars it would have a high probability of cacking your ROM and would result in bootloops. Not absolutely certain, but fairly concerned about the possibility. I believe you would have better luck running a nightly that people report as "relatively stable" in the forums (some nightlies are better than others).
When the feature was merged, I really thought CM 7.1 would be out soon. RC1 dropped a month *before* the new feature was merged. That sounds odd in retrospect, because most projects freeze feature additions before entering the RC phase of a release (ie. they accept bugfixes only).
I just assumed it was for an X10 since we were in the X10 forums. Since this phone isn't officially CM supported I'm at the mercy of ROM developers to make a nice CM7.1. There are a couple out there, and they all have issues. One is close, but the dev seems to have gone missing. I hope he returns soon.
Is modifying one jar file all that it would take? Which file? If I knew that I could possibly take the jar file from one of the CM7.1 ROMs for my device (which has issues) and put it into a 7.0.3 that works smoothly and be happy.
rearview said:
Is modifying one jar file all that it would take? Which file? If I knew that I could possibly take the jar file from one of the CM7.1 ROMs for my device (which has issues) and put it into a 7.0.3 that works smoothly and be happy.
Click to expand...
Click to collapse
I like your train of thought. Unfortunately, even if that were to work you would be unable to configure the feature, because the UI is in the CM Settings apk (ie. the apk that makes "CyanogenMod Settings" menu option appear in your Android settings). If you were to also grab the CM 7.1 settings APK and install it, then that would replace the old version. The CM 7.1 version has all sorts of changes, controls for other new features, and so forth; therefore, that would break much of your other functionality.
How conversant are you in software development? You may be able to join one of those CM 7-derived ROM projects for your platform. It should be relatively easy for someone with a CM dev environment configured for your platform to grab these patches via git cherry-pick and build a 7.0.3 "Gold Edition" with this feature added. Because it should be easy, you might be able to persuade one of those custom ROM developers to grab this feature and include it.
If you are interested, here are the links to my patchsets that were merged to implement the feature:
Framework Implementation
CM Settings UI
I believe the patches will merge "nearly cleanly" into a CM 7.0.3 derived branch. That is to say, if there are merge conflicts they will not be substantive and will merely involve wholesale cut/paste reordering of methods within the given class files rather than requiring a rewrite of any part of the actual implementation.
I know that this simple reordering is all I changed between my 7.0.3 development version and the 7.1-derived submission. Seems Steve Kondik did a little further rearrangement to accommodate other patches that had been accepted/merged while mine was pending. Same deal there: still should be relatively simple.
I'm not much of a developer, though I'm an IT guy with some unix background. I'll look at it.
Right now we can sort downloads section via status, last update, creation date. See pic.
Any thoughts on adding a sorting option via Android versions? Maybe even an option(s) to ignore what is 100% not working in certain versions of Android.
Hi there,
I subscribed to the Samsung Electronics Co., Ltd. RSS feed on APKMirror so I see every update of the Samsung apps that get posted, but I've never been able to sideload the apks of Samsung's system apps.
From what I understand of my readings here and there, Samsung decided to lock the apks of their system apps so that they can't be downloaded from websites like APKMirror and be sideloaded.
Still, those apps don't always get updates from the Galaxy Store or Google Play Store.
If I take the example of the Samsung Gallery app only, on my device (which I updated to the latest security patch on Feb. 22nd), I got version 10.0.01.19, while APKMirror already has version 10.0.01.22 dated Feb. 23rd and even version 10.0.03.7 dated Feb. 24th (all of which being supposedly compatible with my device as they are "noarch" and "nodpi")!
So my questions are:
- when the hell do they get updated? (Possibly bundled with monthly security updates?)
- how can I install the latest versions if the updates are not listed in Galaxy Store and/or Google PlayStore?
- why are there frequent updates if they can't be installed?
Hope someone can answer those questions, I really can't wrap my head around this.
Hi, I'm increasingly concerned by snooping and overreach from Google and State actors, and thought one way to limit their reach into my device is by not updating their apps and staying on older stable versions - I think I understand the balance between missing out on new security/bug fixes/features/etc.
I'm using an Android One phone which I do update when security patches are released, so it's only the apps that are backward versions.
What do others think about this approach, or is there an alternative method to keep Google and 5/14 Eyes out of my junk?
CalyxOS is an Android mobile operating system that puts privacy and security into the hands of everyday users. Plus, proactive security recommendations and automatic updates take the guesswork out of keeping your personal data personal.
Learn more out CalyxOS.
Working:
Telephony (Calls and Data)
IMS (RCS, VoLTE and WiFi Calling)
WiFi
Bluetooth
Camera (and flashlight)
Audio (Record and Playback)
Video Playback
Sensors
GPS
DM-Verity Enabled
Encryption
Bugs:
You tell me
Installation:
Wipe /system, /vendor, /cache
Format data
Flash calyxos zip
Notes:
Do NOT flash gapps
It is a user build
Not encrypted by default
I do not work for the calyx institute
Poco F1 does not maintain the android security model as much as the officially supported devices. It does not have complete android verified boot, but dm-verity is enabled
Download:
Get CalyxOS for Poco F1
Kernel Source:
Kernel source
If you like my work, please consider buying me a coffee.
Telegram support
Reserved 1
Reserved 2
Godlike rom! So far only notification delays. I don't know if this is a calyx issue in general or this rom in particular
CalyxOS v3.6.0 is out. Get it here.
Changelog:
• Fixed Encryption
• Switched to user build
• Updated kernel to Ingenium v3.1
• Source upstream (Updated to June patch)
Dev_Mashru said:
CalyxOS v3.6.0 is out. Get it here.
Changelog:
• Fixed Encryption
• Switched to user build
• Updated kernel to Ingenium v3.1
• Source upstream (Updated to June patch)
Click to expand...
Click to collapse
Took a while but thanks for keeping it up with this ROM.
Dev_Mashru said:
CalyxOS v3.6.0 is out. Get it here.
Changelog:
• Fixed Encryption
• Switched to user build
• Updated kernel to Ingenium v3.1
• Source upstream (Updated to June patch)
Click to expand...
Click to collapse
Hi, the Link is not correct.
This is the correct Link: calyxos_beryllium-3.6.0.zip
a170xda said:
Hi, the Link is not correct.
This is the correct Link: calyxos_beryllium-3.6.0.zip
Click to expand...
Click to collapse
Thanks for bringing it to my notice. Updated.
Hi, I wonder why you care about privacy and at the same time recommend Signal/whatsapp/duckduckgo.
Although the rom seems promising.
Glad to see Calyx for our Poco!!! Thanks for your work!
So far I only noticed that the "Display cutout" settings does not work properly (to hide the notch). Otherwise it runs really great!
Dev_Mashru said:
Thanks for bringing it to my notice. Updated.
Click to expand...
Click to collapse
You should also updates the Notes in OP: Not encrypted by default to Encrypted by default, since in ur recent changelog you wrote that you fixed it.
Retrial said:
You should also updates the Notes in OP: Not encrypted by default to Encrypted by default, since in ur recent changelog you wrote that you fixed it.
Click to expand...
Click to collapse
It is still not encrypted by default unlike in A11. Earlier it wouldn't boot if you were encrypted, now you can manually encrypt and it will boot.
Dev_Mashru said:
It is still not encrypted by default unlike in A11. Earlier it wouldn't boot if you were encrypted, now you can manually encrypt and it will boot.
Click to expand...
Click to collapse
Hmm I see. It would be nice if you could work to make it encrypted by default especially in this ROM. However I understand it may need some of your time.
BTW, I checked fast some screenshots, I saw some dots, seems there is a padding issue in status bar. (not sure tho since I checked from screenshots, I haven't tried the ROM yet). If you want take a look at crDroid values here, it may help with padding.
Does this build also receive OTA updates? Wishful thinking I'm sure, but i'm very interested. Do you have any plans to bring your project up to the newest iteration of CalyxOS? I think it's on 4.6.0 now. Any clarity you can offer on how your build copes with updates and what other manufacturer specific updates you've had to keep an eye on would be good to know as well please.
I think your build might have a specific application at the intersection of privacy fanaticism and audiophile listening with external DAC/AMP. The user can luxuriate in the use of interchangeable micro SD storage slots and the infinitely expandable, offline library it affords them. This means they can do away with depending on an internet connection and subscriptions to lossless music services like Qobuz, Tidal, Deezer, etc.
Alternatives in the android-based DAP market often have limited, non-expandable storage, and rely on versions of android which are outdated but no less privacy invasive. Whereas using a Poco F1 with custom ROM opens things up entirely. It also allows users to incrementally upgrade their DAC whilst always relying on this phone as their DAP playing hi-res files over USB. No need to upgrade DAP.
I'm really keen to learn how you built this. I think this phone is an ideal candidate for DIY, cost-effective, privacy respecting lossless listening.
airgappedromproject said:
Does this build also receive OTA updates? Wishful thinking I'm sure, but i'm very interested. Do you have any plans to bring your project up to the newest iteration of CalyxOS? I think it's on 4.6.0 now. Any clarity you can offer on how your build copes with updates and what other manufacturer specific updates you've had to keep an eye on would be good to know as well please.
I think your build might have a specific application at the intersection of privacy fanaticism and audiophile listening with external DAC/AMP. The user can luxuriate in the use of interchangeable micro SD storage slots and the infinitely expandable, offline library it affords them. This means they can do away with depending on an internet connection and subscriptions to lossless music services like Qobuz, Tidal, Deezer, etc.
Alternatives in the android-based DAP market often have limited, non-expandable storage, and rely on versions of android which are outdated but no less privacy invasive. Whereas using a Poco F1 with custom ROM opens things up entirely. It also allows users to incrementally upgrade their DAC whilst always relying on this phone as their DAP playing hi-res files over USB. No need to upgrade DAP.
I'm really keen to learn how you built this. I think this phone is an ideal candidate for DIY, cost-effective, privacy respecting lossless listening.
Click to expand...
Click to collapse
Here is the latest A13 version. (Also use that thread)