Dear XDA,
just looking for a friendly discussion here. With Android O dev preview, it has blocked apps from drawing on the UI due to a security issue. But to my knowledge it just forces a system wide notification with the ability to turn off the ui elements, and gives the option to allow ui drawing (hiding the notification) per app and if the apps use the newer API can show up as a trusted app. But so many tech articles says otherwise. Are these really a big security loop hole in your opinion? Like for example after the nougat update, os monitor stopped working and the dev stopped support due to a security patch. So I am wondering if android is really getting more closed to security updates or is this just articles fear mongering? I mean I am all up for security and lucky for me all my apps such as emulators, settings, tools, linux containers and such so far I have not needed to root at all and it has really helped me since I use mobile payment on my s7 edge. I do dabble into rooting on my nexus 7 but rooting hasn't been mandatory, unless ofcourse most of my app breaks because of android updates, then I would have to root. So is android really becoming more closed or are these security updates actually required??
Hey all,
I'm new to this forum but excited to be a part.
I have an application "*****ute" in the Google Play Store and here's the source code:
hxxps://github.com/hexag0d/*****ute_mobile_android_a2
My app uses Android WebKit WebView and since the Chrome 71 update, WebRTC no longer works inside the app. Does anyone know if it would be possible to downgrade to the Chrome 70 WebClient and what problems that would cause for other apps on the device?
WebRTC no longer works in Brave either.
Another question I have is if it's possible to force my WebView to use an older chrome client? Or, could I change the WebView to not use chromium?
This issue in Chromium supposedly won't be resolved until March, at the earliest.
Hi,
I have the same problem. Did you find any solution?
I mainly use my phone for apps, usual call/txt and 1 game that I'm playing. The feature that I will miss is probably the Magnification.
I saw LineAge OS 17.1 on the other thread, but I'm not sure if I will pull the trigger. That means I have to do alot of backups etc.
Have you guys upgraded yours and what's your experience so far?
Hi
I recently upgraded to Lineage OS - there's an unofficial build by @derf elot which I have been using as my daily driver for 6 months or so. Works really well on all fronts EXCEPT for apps that require any kind of verified device security and Safety Net.
Because you have to unlock the bootloader, your chances of passing SN are slim to none (I could not get it to work on a G8343) so you can kiss apps that require Google Play verification goodbye (Banking apps, Netflix, a few Authenticator apps, etc.)
If you can do without those apps, then I have no issues running LOS.
Hello! Thanks for replying to my question.
Did you notice a significant performance increase? I mainly use it for apps and 1 games anyway.
And does LineAge has Magnification too on Accessibility?
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)
hello all
wondering if anyone here has any idea why the new directv app will not work on my android 11 box.the older directv on the go app works fine but its being discontinued soon.the new app returns the error"issue on our end.try again later.care code 500".any ideas guys and gals?
thanks
brayneeac said:
hello all
wondering if anyone here has any idea why the new directv app will not work on my android 11 box.the older directv on the go app works fine but its being discontinued soon.the new app returns the error"issue on our end.try again later.care code 500".any ideas guys and gals?
thanks
Click to expand...
Click to collapse
There are DIRECTV apks going back to 2016 that you can sideload and use especially when:
-- Crashing.
-- Won’t open.
-- Won’t respond.
-- Isn’t working properly.
-- Discontinued.
Not to mention that new updates may have many bugs that you may not be comfortable with. Developers tend to keep their apps updated with the latest version of Android. So, if you have an old or even new Android version, the new interface and features compatible with new Android version may break the app.
Your device hardware may not be compatible with the updated version of the app.
You may not like the newly added features or the interface overhaul.
Your favorite feature may get removed for any reason.
The updated version may get filled with ads.