@freeyia
there is both a network permission and a network restriction option: Faq - DivestOS Mobile
please verify that both are allowed
Yes, I found the fix in that section Broken - DivestOS Mobile
I was really wanting to use Mull, because I always prefer Mozilla over Google.
BTW… I take this opportunity to congratulate you and thank you for your great work with DivestOS, Mull, and other related projects. Your focus on both security and free software is incredible, something that other projects lack, as they either focus on one aspect while invalidating the other, such as preferring proprietary software or implementations for security reasons, or favoring open source despite having security vulnerabilities. In your case, I notice a perfect balance and equilibrium between both situations, so all I can do is congratulate you on the work done.
Hello Tavi, How could I contact you privately?
PM here would be fine, preferably email
A throwaway temp email will do…
@roger I do not provide 1 on 1 support, please use the available existing channels to do so: Community - DivestOS Mobile
ie. ask your question here
Hi @SkewedZeppelin I’ve been using DOS for a while now, and it seems pretty solid. There are some smallish issues I have found, or suggestions I am looking for.
-
I think you maintain the IR Remote app? I have found that many of the buttons for my Sony Bravia do not work, i.e. a critical one is the back button which does nothing.
-
USB has some issues, I am not sure exactly what but I have another phone running Lineage 18.1 (lavender) and when I use a USB C to USB C cable to connect to a Nintendo Switch (using the payload injection app Rekado) it works fine, but the same does not with Alioth using DOS, its not detected.
Now for some advice / suggestions:
-
I would like to know if I can somehow print from my android phone to my local brother printer, I do not want to use the propriety app. I have tried to detect the printer using the settings / printers etc, but it was never detected.
-
I would really like to connect to SAMBA v3/v2 shares locally, using the built in file manager if possible, but if not, a FOSS app, I could not find anything that still worked. I remember long ago, I had used an app which added a section to the hamburger menu of the “Files” app, but that same app no longer does anything, its too old and incompatible. This seems like something that would be really good to have out of the box.
Thank you.
back button which does nothing.
there is actually a training mode if your device has an IR receiver then you can export the generated remote and that can be added to the source code
but the same does not with Alioth using DOS
do other usb devices work? it may not have the particular driver needed enabled/compiled into the kernel for that
detect the printer
it should show up if the printer offers ipp or jet direct, you can also try manually typing in the ip address of the printer
SAMBA v3/v2 shares
you can use the material files app for this and if you save it, it can actually be accessed from other apps that support the native file picker
@SkewedZeppelin Its not regarding support or help with any of your projects.
Can you provide a private channel I can send the message?
Or, if you pm me here I can reply with a burn-once-read pastebin link.
Hello! Could someone inform me if there are plans to update the Poco X3 Pro to version 20.0 of DivestOS?
@Zorosuro
vayu has no working wi-fi under 20.0 due to unknown reasons.
1 Like
@SkewedZeppelin regarding paid feature request, $5000
Hello!
There’s a rather strange inconsistency with Lineage and Divest that I noticed: I use Pixel 4 (aka flame) and Lineage doesn’t support face unlock on it, while Divest appears to support it.
is this a problem with Lineage not properly supporting my rather outdated device or with Divest using a proprietary firmware that is not supplied in LOS?
So does that mean that even on DivestOS 19.1 / 12.1 / Snow Cone v2, which is the version that vayu currently supports, the wifi doesn’t work?
@throwaway11113
LineageOS did support face unlock under Android 13, but they’re now shipping A14 which isn’t compatible with the old blobs. DivestOS is still based off of LineageOS on Android 13 so it still has face unlock.
@Zorosuro
Wi-Fi does work on vayu on 19.1, that is why DivestOS is still shipping 19.1 for it and not 20.0.
I understand, thank you for responding! Can I ask you a question? For someone using banking apps on their phone (Poco X3 Pro Vayu), which would be safer: unlocking the bootloader and installing a custom ROM, or keeping the stock ROM and the bootloader locked? I’m unsure because unlocking the bootloader compromises verified boot, device integrity, and other Android protections. Therefore, I don’t know which option has a smaller attack surface.
P.S.: The Poco X3 Pro has not received security updates from the manufacturer since 2022.
P.S. 2: My banking app works on custom ROMs.
there is actually a training mode if your device has an IR receiver
Unfortunately I don’t think it has. Not sure why some critical buttons should not work as the remote is very common. It is this TX100U - https://www.amazon.com/Gvirtue-RMT-TX100U-Replacement-Sony-TV-Remote-Bravia-Smart/dp/B08NY52WWT
do other usb devices work? it may not have the particular driver needed enabled/compiled into the kernel for that
Normal USB flash drives work fine it seems. Anyway that driver could be incorporated into DOS?
it should show up if the printer offers ipp or jet direct, you can also try manually typing in the ip address of the printer
It seems to be a VPN issue, I have reported the issue.
SAMBA SHARES - you can use the material files app for this and if you save it, it can actually be accessed from other apps that support the native file picker
Ill try this and update back, but is there no way around installing 2 file managers to achieve this task? This would be good to build into DOS, into the default file manager.
remote is very common
the remote database is nearly a decade old, it may not support more recent remotes
that rules out hardware, and likely is just the driver missing, I can take a look to see if it can be enabled
build into DOS, into the default file manager.
I try to keep the system minimal, so this would be out of scope.
@SkewedZeppelin I tried to install DOS on my FP3. Following the steps here: https://divestos.org/builds/LineageOS/fp3/install.html
I’m stuck at step 11. The phone does not show up over USB on any of my systems. (not even as an unknown device in windows, nor in lsusb on linux) So unsurprisingly adb sideload ...etc command ends up with no no devices/emulators found.
I’m at loss why would that be the case. The same device does show up as Android device when booted to fastboot. So I’d say it’s fair to say the cable is probably okay? The first 10 steps influding fastboot update worked as expected.
Have you seen this before? Any advice how can I recover from this situation?
Edit: To provide some more details, the device shows up in lsusb when booted to fastboot as:
Bus 001 Device 019: ID 18d1:d00d Google Inc. Xiaomi Mi/Redmi 2 (fastboot)
But it does not show at all in lsusb output when booted to recovery sitting on the ADB Sideload screen where I’m supposed to adb sideload stuff. Eventually after couple minutes of waiting FP3 will show ERROR: recovery: Timeout waiting for messages from minadbd.
@mprasil please try using a USB 2 port, some devices are weird in USB 3
also try reversing the cable and/or flipping the end
or try running adb as root, perhaps you’re missing udev rules
if you were able to complete step 9 successfully you can instead try to boot the system, but you must install the update again via the Updater app to ensure firmware is installed (this is typically done by this step 11)