Hi, I'm not an Android expert in any way but I'm prototyping an app that runs Tensorflow deep learning models for image processing on this tablet.
I convert various models from Keras to TF-Lite in various modes, trying to find the best-performing method - comparing normal FP32 with quantisation to FP16 and INT8, and running each in CPU mode and on the GPU and NNAPI delegates.
NNAPI is supposed to assign compatible operations to the chip that runs them fastest, ie most INT8 stuff to the Hexagon DSP. Except my timings show 8b models running faster in CPU, or no difference, or worse, like it's always falling back to CPU. Suspicious!
Looking at the ai-benchmark com ranking (sorry, new account, can't do links) rankings and comparing the Tab S6 with a high-performing SN855 device like the Galaxy S10+ shows that their CPU perf is more or less equal, but quantised perf is WAY too low on the Tab S6.
From the paper arxiv org 1810.01109.pdf
...Qualcomm delivers these drivers in the software images provided to its OEM customers, which then in turn determine when and how to include them to end devices: with their initial release or later over the air in subsequent software updates. As a result, their presence and actual version might vary significantly across the phones on the market.
Click to expand...
Click to collapse
This suggests to me that Samsung haven't bothered including the NNAPI drivers for the tab S6! So what, they only do it for the premium products? Personally I'd say a £600 tab is pretty premium.
Am I right about this and if so is there anything I can do? Any way to get the drivers in, a custom ROM that includes them? I'd buy something else but there's not a lot of choice with tablets, this seems to be the most powerful one available. I'd love one with a Kirin 990 but no such thing exists yet AFAIK.
"Qualcomm’s first NNAPI driver for running quantized neural networks on Hexagon DSPs was introduced in the Android
O-MR1, though it was not used in any commercial devices
at that time and first appeared only later in the OnePlus 6
and Xiaomi Mi8 with the next Android version. In Android
P, these drivers got additional support for running float models on the Adreno GPU. Yet, they are currently not present
in the market."
I'd say there is little to no support by OEMs
gottahavit said:
...
I'd say there is little to no support by OEMs
Click to expand...
Click to collapse
The ai-benchmark com ranking list (that i can't link) shows many Snapdragon 855 devices with high performance that can only be due to NNAPI support I believe. But anyway, as there aren't any better tablets about, I wonder if there's a way to make a ROM that adds those drivers? I know nothing about custom Android builds.
Related
Ok, I have looked this up as many ways as I possibly could and to no avail.
I am pretty sure the info I am looking for is out there, I am just having the worst time accessing it.
What I would like to know is why certain devices run on certain OS's.
is it just one factor or multiple factors? I suspect the latter[?]
and if so, what factors primarily play a role in deciding what OS goes on what device?
I know what I am asking really serves no purpose to most, but I am one of those who likes to know as much as possible.
much thanks in advance and please do forgive me for the huge lapse
The 1st factor is the device manufacturer. A clear example: SE says that Xperia X8 doesn't support versions above 2.1, so it didn't release actualizations. But now, we have even ICS on X8
The 2nd factor is the availability of drivers for the desired Android version (the drivers can come from a oficial ROM, or from the chipset manufacturer), and/or the coders interested in the device.
For many devices (specially low-end devices) this is the most important factor.
RoberGalarga said:
The 1st factor is the device manufacturer. A clear example: SE says that Xperia X8 doesn't support versions above 2.1, so it didn't release actualizations. But now, we have even ICS on X8
The 2nd factor is the availability of drivers for the desired Android version (the drivers can come from a oficial ROM, or from the chipset manufacturer), and/or the coders interested in the device.
For many devices (specially low-end devices) this is the most important factor.
Click to expand...
Click to collapse
hmm, well that is very informative and I thank you
RoberGalarga said:
The 1st factor is the device manufacturer. A clear example: SE says that Xperia X8 doesn't support versions above 2.1, so it didn't release actualizations. But now, we have even ICS on X8
The 2nd factor is the availability of drivers for the desired Android version (the drivers can come from a oficial ROM, or from the chipset manufacturer), and/or the coders interested in the device.
For many devices (specially low-end devices) this is the most important factor.
Click to expand...
Click to collapse
While this is true another factor is the popularity of the device. Why would anyone waste time on developing for a device that no one is interested in? It also depends on the value of the device. Its normal that the high-end ones will receive updates before the mid-range devices. But as the guy above said for xperia the same is with my LG. We also made a half functional ICS and the only big problem is the screen which works only 50%
Sent from my Optimus Me using xda premium
Everywhere I go I see guide for porting ROMs/recoveries/etc and they're all for MTK devices, and I don't mean to be a noob but I want to know why they are so different. I know they have a different chipset, but they all run android and should all correspond to the same rules. Could anyone experienced give me an overview of what the difference is between Qualcomm and Mediatek devices that makes it so much easier to build for Mediatek.
There is a difference at the GPL policy as I read somewhere... whereas quallcomm is open-source and mediatek isn't?
Also quallcomm is much further at Hardware level in comparison to Mediatek, In which Mediatek serves for a good low-cost replacements for infamous brands.
Also the energy consumption is less then Quallcomm's
But the difference for those 2 sorts, I couldn't say anymore then I told you .
Hello dear people, I hope I can be forgiven for asking a potentially stupid question.
With my 850F batteries failing, I am hoping to get some more months out of this once expensive phone. So I've been looking at some custom ROMs to see if they make a difference. But it seems like the fingerprint reader never works. People tell me it's because the driver source isn't available.
So, is this a question of legality (the driver cannot legally be included with roms) or of possibility (the driver is deeply dug in)? Because if it's the former, I was wondering if there's some file I can take out of the stock firmware and put onto my phone to make the fingerprint reader work with any rom?
Also, I would like to express my dissatisfaction with the terrible support Samsung has given for this phone. We got one late update from Kit Kat to Lollipop. It looks so vanilla it makes one wonder why it took so long. The black background colors from Kit Kat changed to white, a terrible choice for an OLED screen. So with regard to the already meager battery, this update has been a regression.
I'm trying to get as many months out of this phone as I can until the next generation of phones comes out. I love the Samsung hardware but I might look for brands that are either more frequent with updates or open source enough so that custom firmware development is not hindered by unsupported hardware.
I'm thinking the next phone should just be under 5 inch and powerful enough to be a desktop computer running full Linux, like Ubuntu OTA 11 (if someone introduces Android compatibility) or Maru OS, so I don't have to carry around a laptop anymore.
Fingerprint scanner works fine with all Samsung based ROMs (OzcanROM and EpsilROM) only CM ROMs (CM and ResurrectionRemix) don't support it (aswell as heart rate monitor)
93drago said:
Fingerprint scanner works fine with all Samsung based ROMs (OzcanROM and EpsilROM) only CM ROMs (CM and ResurrectionRemix) don't support it (aswell as heart rate monitor)
Click to expand...
Click to collapse
I hadn't even thought of the heartrate monitor yet!
Yes, I tried those non-Samsung ROMs. I thought if I use the Samsung-based ROMs, I might as well use the Samsung ROM.
Because they use proprietary drivers, and samsung does not disponibilize them, well, when marshmallow launch, its is POSSIBLE that Samsung bundle the source code with a generic fingerprint driver, as fingerprints reader support is a generic and system wide thing in MM, just like when hardware acceleration via GPU was an propietary thing in android 2.3 and being default on android 4.0
Hi
I was figuring buying a Spark X. I see the Spark series have no entry here, so I wander I had a good idea. Although, following various links here I think I found the man Porridgek3 works on this X model from a somewhat old COS13.0.2 (comparing to COS13.1.4 for others, e.g. Swift series).
Not being a coder myself I can't read the code at github, so I'd like if this is not stupid question/request to read a thread about what are the changes from stock COS13 to the Porridge custom CM13.
Thank you and happy new year to everyboby at XDA.
The Spark devices are pretty poor. They all have Mediatek processors and updates are much slower than for other Wileyfox devices.
flibblesan said:
The Spark devices are pretty poor. They all have Mediatek processors and updates are much slower than for other Wileyfox devices.
Click to expand...
Click to collapse
My aim is not to have a speed daemon. I search something with good and removable battery (Spark X has one and as about same hardware than Spark/Spark+, I guess the autonomy would be better), and I could easily remove the bloatware (stock CN13 would help, I believe, to switch to CMod if exists).
I currently have a Liquid-MT (my first smartphone) for which by chance there was a custom ROM available based on GB-2.3.6, and it was so difficult for me to jailbreak it that I decided to keep it as is until now when mechanical problems with the internal microphone make replacement nearly mandatory.
Also, I'm focused to keep as far away as possible from google and GAFAs I have no confidence in Samsung so I don't even try to know if their devices are easy to make free. That's why I was so happy to discover my target from a single European manufacturer (at least designer) that ships his own with CN, and I easily accept to have a poor camera inside, only 802.11bg and basic 4G. I also know that the Spark X has poor dpi compared to other Sparks because of larger screen, and accept this as a consequence of my decision on battery... an so on...
Not being very much aware in ROMs, I don't know by which tail to catch the beast. I don't really choose for a model, instead I exclude others: GAFA, big Broth, God keeps me away! High end... for tainted kids (or their backward parents), out! Chinese, let's them make phones for ... themselves. So what does remain? Here is my way.
SparkX continued
Hi, how did things go with the sparkx ? I have one here and after no updates for a long time the updates arrived and bumped to nougat and I began to feel like i was signing my life away.
A while back I found an old release of sailfish for my ZTE open C so ive been making steps towards porting sailfish to the sparkx. still in early stages but i am confident it is possible.
1stStep said:
My aim is not to have a speed daemon. I search something with good and removable battery (Spark X has one and as about same hardware than Spark/Spark+, I guess the autonomy would be better), and I could easily remove the bloatware (stock CN13 would help, I believe, to switch to CMod if exists).
I currently have a Liquid-MT (my first smartphone) for which by chance there was a custom ROM available based on GB-2.3.6, and it was so difficult for me to jailbreak it that I decided to keep it as is until now when mechanical problems with the internal microphone make replacement nearly mandatory.
Also, I'm focused to keep as far away as possible from google and GAFAs I have no confidence in Samsung so I don't even try to know if their devices are easy to make free. That's why I was so happy to discover my target from a single European manufacturer (at least designer) that ships his own with CN, and I easily accept to have a poor camera inside, only 802.11bg and basic 4G. I also know that the Spark X has poor dpi compared to other Sparks because of larger screen, and accept this as a consequence of my decision on battery... an so on...
Not being very much aware in ROMs, I don't know by which tail to catch the beast. I don't really choose for a model, instead I exclude others: GAFA, big Broth, God keeps me away! High end... for tainted kids (or their backward parents), out! Chinese, let's them make phones for ... themselves. So what does remain? Here is my way.
Click to expand...
Click to collapse
Google Pixel 6 series' Tensor dominates the Exynos 2100 and Snapdragon 888 in real-world GPU benchmarks
The Google Pixel 6 was put through Geekbench a few days ago and performed decently. The phone has now made the trip over to 3DMark in an attempt to gauge its GPU's prowess. The result? Supremacy over current flagship chipsets. Tensor's Mali-G78 MP20 GPU hits hard, it appears.
www.notebookcheck.net
Wouldn't be surprised if there are hard coded features designed to steal more of your privacy and personal data by Google in the Tensor chipset currently or planned for the future.
Andrologic said:
Wouldn't be surprised if there are hard coded features designed to steal more of your privacy and personal data by Google in the Tensor chipset currently or planned for the future.
Click to expand...
Click to collapse
And? Everyone has your info by now. No point in making a scene over it. Either get the phone or don't.
Andrologic said:
Wouldn't be surprised if there are hard coded features designed to steal more of your privacy and personal data by Google in the Tensor chipset currently or planned for the future.
Click to expand...
Click to collapse
One more reason to run custom ROM, de-google the phone and disallow connections to Google servers. At least that's my plan.
Diablo2424 said:
One more reason to run custom ROM, de-google the phone and disallow connections to Google servers. At least that's my plan.
Click to expand...
Click to collapse
Indeed. Always. However with custom chipsets they may be moving towards weaponizing hardware based blockers for doing those things. Plus god knows what backdoors may be built into these wonderful chipsets. Have zero trust in Google. Effective firewall'ing may become the best/last line of defense. But let's see...
Andrologic said:
Indeed. Always. However with custom chipsets they may be moving towards weaponizing hardware based blockers for doing those things. Plus god knows what backdoors may be built into these wonderful chipsets. Have zero trust in Google. Effective firewall'ing may become the best/last line of defense. But let's see...
Click to expand...
Click to collapse
Very true, that's why that last line of defense with firewall'ing is always a fail-safe - provided it doesn't cripple the device from being usable. I just did some searching and see that the CalyxOS team so far is saying they are planning on supporting the Pixel 6, but of course they don't know what they don't know yet, as it's not in anyone's hands. I would be surprised if LineageOS doesn't build a ROM as well.