On 1/1/21, Tamas Geczy <gt1991@xxxxxxxxx> wrote:
I know I was a bit harsh in that last message, that was before I ate===========================================================
some good pizza and started celebrating the new year. I guess I just
wanted to make my points clear at the time as far as my limitations
and set up but I don't think all people on here have a Windows dislike
either. I think from what I'm seeing in Orca on my Pi, it's improved a
lot since the Vinux days. But that's another topic for another time!
I ended up writing to the forum topic with Omni Rom. I don't know our
chances with Emteria until they add the Pi400 as well to their device
tree. I think Android is sort of OK with a keyboard. I say that
because some Talkback things may require a touch screen, and that's
why I know I'll be investing in one sometime even if it is a 7-inch
one.
Omni has some hope as it is also Microg based. Microg (you can visit
microg.org to read a bit about their mission and such) aims to replace
Google Play-based services with open source generic versions, and from
what I'm seeing, they have done fairly well with this. Even as far as
having a location API for crowdsourced Wi-Fi triangulation.
Unfortunately I think most Microg or Omni roms probably won't include
Talkback. I'm not sure if it included Pico TTS, but the other issue is
that they would have to grab some type of TTS engine that's not Google
TTS. Otherwise all you'll hear is the Talkback earcons but no speech.
Pico may be there but I also haven't seen it in all AOSP roms as of
late so I can't say for sure, didn't check at the time either.
Emteria's image does include launcher, browser, and most things you
need, but again No Talkback or TTS I saw in either of the system app
folders. Again this is a bit on Google to make Talkback part of the
AOSP tree, no? It is on GitHub, but the latest I'm seeing is 6.1.1.
This was 2018's Talkback. We're getting 2+ versions more now, so it
doesn't appear to me that they always commit the latest changes.
Again, unfortunate, as while Talkback is open source, it may not be
the latest. Although I do see some activity from this past October, so
it's clear that Google will keep updating that AOSP Talkback. I just
don't think it's actually within the AOSP tree, else all generic
Androids would also get it.
-Tamas
On 12/31/20, Pranav Lal <pranav.lal@xxxxxxxxx> wrote:
Hi Tamas,===========================================================
I hear you and can empathize with your frustration. I have been down this
root with other android builds, none work because you need the GUI to
enable
adb.
Pranav
-----Original Message-----
From: raspberry-vi-bounce@xxxxxxxxxxxxx
<raspberry-vi-bounce@xxxxxxxxxxxxx>
On Behalf Of Tamas Geczy
Sent: Friday, January 1, 2021 8:28 AM
To: raspberry-vi@xxxxxxxxxxxxx
Subject: [raspberry-vi] Re: Android
Well, I got a try at this Emteria OS, and the results were... Not so
good.
I did get 2 licenses thinking it would work out fine.
My first problems came up when trying to flash. The entire thing is built
with QT5 and it just sucks. Once you click "flash" a dialog asking you for
a
warning prompt to accept card erasing appears. Aira was the only way I
could
get passed this. It also opens up a command prompt in another window
where
you can see progress written to the console.
4 tries later (one SD card got corrupted in this process) I succeeded in
writing it.
I tried it on the Pi400 first. It wouldn't boot. Then I saw that there's
no
dtb file with pi400.bcm2711-rpi-400.dtb file. So they made this Emteria
only
work with Pi 4, not 400 or 4CM.
So I got my Pi 4 4 GB out and tried it there. I got the /data partition
to
create. However, it would not auto connect through Ethernet and I have
zero
computer monitors in this house, that's right both I and my partner is
blind
so we don't keep heavy space wasting monitors around usually. I may get a
smaller 7-inch one just for diagnosing stuff through a screen, but for now
I
really can't hook this up. I just moved as well like a week ago. So nope
nope. I couldn't get it to show up in the ethernet devices of my router
so
that was quite a fail.
I also tried Omni and Lineage. Omni was the only one I could boot, and it
would even show up as an ethernet. But refuse all connections on all
ports
(ADB, SSH.) Pretty much a dead end as far as Android goes on Rpi. Unless
other images exist out there.
Oh and I got Paragon's Linux File Systems for Windows. I know all of you
are
bigtime linux geeks who hate Windows a lot, but Windows is what I've been
using since 3.11, so will never, ever, ever switch to Linux full-time.
Nope
nope. So using Paragon's Linux file system thing I got to copy
talkback.apk
to /system/priv-app and then I tried to hit
alt+CTRL+Z to turn talkback on. I'm not sure if people know, but
Google enabled ALT+CTRL+Z like ChromeVox for Android too!
Unfortunately all of these roms use their own setup wizards. Not the
stock
Android one. So that shortcut may only work when a stock setup wizard is
used.
Again, total fail. What a waste of 6 hours.
-Tamas
On 12/31/20, sanchit <orca4linux@xxxxxxxxx> wrote:
Hi.===========================================================
did anybody tried FydeOS Alpha. Chromium OS on RPi.
On 31-12-2020 10:35, Pranav Lal wrote:
Hi,
Yes, I saw that but the article at least discusses going in a browser
to a website and then side loading.
Pranav-----Original Message-----
From: raspberry-vi-bounce@xxxxxxxxxxxxx
<raspberry-vi-bounce@xxxxxxxxxxxxx>
On Behalf Of kperry@xxxxxxxxxxxxx
Sent: Thursday, December 31, 2020 8:36 AM
To: raspberry-vi@xxxxxxxxxxxxx
Subject: [raspberry-vi] Re: Android
It does mention side loading stuff actually.
-----Original Message-----
From: raspberry-vi-bounce@xxxxxxxxxxxxx
<raspberry-vi-bounce@xxxxxxxxxxxxx>
On Behalf Of Pranav Lal
Sent: Wednesday, December 30, 2020 9:33 PM
To: raspberry-vi@xxxxxxxxxxxxx
Subject: [raspberry-vi] Re: Android
Hi Ken,
The bigger problem I see here is that there is no information in the
article about if adb is enabled. If it is, we are in business because
we can side load quite a lot of what we need.
Pranav
===========================================================
The raspberry-vi mailing list
Archives: //www.freelists.org/archives/raspberry-vi
Administrative contact: <mike.ray@xxxxxxxxxxxxxx>
-----------------------------------------------------------
Raspberry Pi and the Raspberry Pi logo are trademarks of the
Raspberry Pi Foundation.
This list is not affiliated to the Raspberry Pi Foundation and the
views and attitudes expressed by the subscribers to this list do not
reflect those of the Foundation.
Mike Ray, list creator, January 2013
===========================================================
The raspberry-vi mailing list
Archives: //www.freelists.org/archives/raspberry-vi
Administrative contact: <mike.ray@xxxxxxxxxxxxxx>
-----------------------------------------------------------
Raspberry Pi and the Raspberry Pi logo are trademarks of the
Raspberry Pi Foundation.
This list is not affiliated to the Raspberry Pi Foundation and the
views and attitudes expressed by the subscribers to this list do not
reflect those of the Foundation.
Mike Ray, list creator, January 2013
===========================================================
The raspberry-vi mailing list
Archives: //www.freelists.org/archives/raspberry-vi
Administrative contact: <mike.ray@xxxxxxxxxxxxxx>
-----------------------------------------------------------
Raspberry Pi and the Raspberry Pi logo are trademarks of the
Raspberry Pi Foundation.
This list is not affiliated to the Raspberry Pi Foundation and the
views and attitudes expressed by the subscribers to this list do not
reflect those of the Foundation.
Mike Ray, list creator, January 2013
===========================================================
The raspberry-vi mailing list
Archives: //www.freelists.org/archives/raspberry-vi
Administrative contact: <mike.ray@xxxxxxxxxxxxxx>
-----------------------------------------------------------
Raspberry Pi and the Raspberry Pi logo are trademarks of the Raspberry
Pi Foundation.
This list is not affiliated to the Raspberry Pi Foundation and the
views and attitudes expressed by the subscribers to this list do not
reflect those of the Foundation.
Mike Ray, list creator, January 2013
The raspberry-vi mailing list
Archives: //www.freelists.org/archives/raspberry-vi
Administrative contact: <mike.ray@xxxxxxxxxxxxxx>
-----------------------------------------------------------
Raspberry Pi and the Raspberry Pi logo are trademarks of the Raspberry Pi
Foundation.
This list is not affiliated to the Raspberry Pi Foundation and the views
and
attitudes expressed by the subscribers to this list do not reflect those
of
the Foundation.
Mike Ray, list creator, January 2013
===========================================================
The raspberry-vi mailing list
Archives: //www.freelists.org/archives/raspberry-vi
Administrative contact: <mike.ray@xxxxxxxxxxxxxx>
-----------------------------------------------------------
Raspberry Pi and the Raspberry Pi logo are trademarks of the Raspberry Pi
Foundation.
This list is not affiliated to the Raspberry Pi Foundation and the views
and
attitudes expressed by the subscribers to this list do not reflect those
of
the Foundation.
Mike Ray, list creator, January 2013
The raspberry-vi mailing list
Archives: //www.freelists.org/archives/raspberry-vi
Administrative contact: <mike.ray@xxxxxxxxxxxxxx>
-----------------------------------------------------------
Raspberry Pi and the Raspberry Pi logo are trademarks of the Raspberry Pi
Foundation.
This list is not affiliated to the Raspberry Pi Foundation and the views and
attitudes expressed by the subscribers to this list do not reflect those of
the Foundation.
Mike Ray, list creator, January 2013
