Even after reading the mega-threads on the two setups it's hard to decide which is the better way to go, if you have the choice. You can see the new PX5 octa-core units running either 8.0 or 6.0, so which to buy? The issues I see from the posts include:
- 8.0 hasn't been fully rooted, and rooting might be turn out to be difficult
- while 8.0 looks somewhat "fresh" with the not quite so fresh anymore tile styling, it has that ugly sidebar, which will require rooting to get rid of
- it seems to be hard to autorun apps on 8.0, so you can't just start up into a custom launcher
- does 8.0 really have less problems interfacing with hardware? With the variety of WiFi, Bluetooth, volume control, microphone etc. problems described in these threads, is the old establish 6.0 better at handling them, or does it lack drivers for newer versions of things like CAN bus interfaces or Torque BT adaptors?
- seems you need 8.0 for 4GB ram, does that make 8.0 worth it on its own?
It seems an even split for which version manufacturers are putting on these units. And it seems an equal number of people with 6.0 want to upgrade to 8.0 as people with 8.0 who want to downgrade to 6.0.
So to a new buyer, would you say get 8.0 or 6.0? I don't think there are many PX5's with 7.1 for some reason, which is why I left that out.
Thanks!
I thought there would be lots of people with views on this - no strong opinions? I thought this would be the first thing to consider when choosing a unit...no?
Same questions here as well.
I've a Dasaita px5 2gb 6.0 and now, about a month I've upgraded to malaysk 8.0 rom.
So, talking about 8.0:
-Fully rooted, everything works perfectly with supersu in 8.0 too
- Google maps works with 8.0, with 6.0 it doesn't
-Smooth performance even with 2gb ram.
-Spotify doesn't pop up
-Working custom launchers
-Working torque
-Autostart working with malaysk rom
-CANBUS working normally
-Bluetooth quality a2dp better than 6.0 (sd-968 module)
Problems with 8.0:
-some users that use md725 Bluetooth module related that is not working due to missing drivers, but a few users says it's working.
-apps force close when you do fast boot. It's difficult to decompile mtcmanager.apk and write the whitelist to keep apps in memory.
-Google contacts not syncing properly to work with voice command. There are some methods at xda to try to use mtcdialer, but it's not working for everyone. You can use manually touching the contact, but not working properly for voice command.
-EQ is working, but fader and balance not working for me (this issue I don't know if is happening with other users too)
In general, I think that Android 8.0 even with 2gb ram worth it.
Thanks megatm! Exactly the info that will help a lot of people who are trying to decide.
Much appreciated!
Related
Okay, I'm reverting back to my G3 after using Android N on my Nexus 6 for the past half-a-year, so I'm debating between Fulmics or something Nougat-flavored (RR, Lineage, crDroid, AICP, maybe Beanstalk?)
My priorities look like:
Ability to pass SafetyNet
Ability to enable tethering
High quality Camera (maybe built from G3 Stock?)
Stable
Well supported / vetted
Runs smooth
Can handle Pokemon GO well
Good battery life
Useful multitasking (like Android N's multi-screen & switching controls)
Ability to reply from notifications menu
Smooth, streamlined quick-setting toggles (esp. for tethering, wifi, and flashlight)
Other bells and whistles are fun (Now On Tap, etc.) but not super necessary
The reason I'm leaning towards Fulmics, in spite of it's Marshmallow flavor, is I remember the stock G3 Camera being something exclusive to stock-based ROMs... and from what I gather, that would mean anything built from Nougat would *not* have access to that Camera, right? Do other ROMs still have good Cameras? I remember the G3 being quite finicky in that regard...
That said, I really like some of the Nougat additions I've gotten used to. Notably, I like being able to reply to messages straight from the notifications menu, I like the streamlined style of the toggles, and while I believe Fulmics can do this I like the double-tap-to-switch-apps feature and multi-window feature of the task switcher
I also will need whatever I go with to pass SafetyNet – which it seems any of the ones I listed can so long as I configured Magisk right?
I saw a post SOMEWHERE (can't seem to find it again), I'm sure it was on XDA.. just after I got this tablet and it said that there was an issue with the Kirin SoC not being able to use external cameras. I want to be able to use an endoscope or webcam on my nice fast machine with its decent screen and thought that this tablet would be a lot better than my old Xenon 80c (which I bricked trying to get rid of a trojan - but that's another thread).
My Mediapad is the M2-801L, unlocked, rooted, Android 5.1.1, EMUI 3.1, 3CToolbox Pro, TWRP, SuperSU, Busybox, SELinux switch etc and a few other bits. I have tried all the usual webcam software that was good with my other tablets/phones but none of it will work, due to whatever problem the Kirin has with UVC BUT I can see live video with my FLIR One thermal imager that also has a visible-light camera
Now I'm not incredibly Android literate - I can mess about with permissions and stuff and do some ADB things when it's well explained but I don't understand the FLIR SDK or Android Studio well enough to work things out for myself. I was wondering if anyone had any pointers?
Brian
rooted/magisk samsung S21+ ...stock rom
stock version of google maps removed with titanium backup.
trying to install many different old versions (in the 9.x and 10.x range) just says 'app not installed' ...what the hell is going on here?
Android 11 scoped storage perhaps.
Try coping it off another device running on R with ApkExport then transfer it to the victim device.
11 just sucks elephant balls bad
scoped storage? sounds like got some searching to do.. i also have a rooted LG V30 that i could maybe grab stuff off of. thatd be my only other play to make though..
sraenn said:
scoped storage? sounds like got some searching to do.. i also have a rooted LG V30 that i could maybe grab stuff off of. thatd be my only other play to make though..
Click to expand...
Click to collapse
You're stuck with scoped storage with/after Android 11. It's not fully active on Android 10, at least with older apps. My old copy of WPS office app runs fine on Q. I will continue to test my N10+/Q vs my N10+/PIE variant to see it's effects if any. So far it hasn't raised its ugly head on the Q variant, but I have played with it more then a few hours.
If you could use a rom version of Q or Pie that be best.
Workarounds for it on 11 exist to some extent but without apps coded well with special permissions it will make them useless. It's already causing issues with photo apps (even on Pixels), file explorer apps, any apps that needs access to large user databases.
Do a Google search for scoped storage sucks.
Let me know how Android 11 works for you, good or bad.
Typical battery life on my Pie variant are as follows with a 4300 mAh battery:
7-12%@hrSOT typically 8% for browser and 11% for web vids.
>.5%@hr with tap on AOD at night with cell/internet not disabled.
The Q variant seems to be better or similar but haven't ran it long enough to really know for sure. It's running cool though and not using excessive CPU cycles. Both are optimized almost the same including a package disabler. Q seems a bit snappier, but it's a fresh load vs a 1.5year old load with heavy use.
crap. that kinda sucks. honestly the battery life on my phone is doing well, granted i dont have much on it and the heaviest use it sees is watching youtube (vanced of course). maybe its time to look around for a good android 10 rom, eh..
sraenn said:
crap. that kinda sucks. honestly the battery life on my phone is doing well, granted i dont have much on it and the heaviest use it sees is watching youtube (vanced of course). maybe its time to look around for a good android 10 rom, eh..
Click to expand...
Click to collapse
If you can find a good Android 10 rom, flash it, not losing hardware functionality. That's a tall order. The cam and display firmware will likely be the most troublesome aspects as the stock rom was built on Android 11.
After you clean up the bloatware Samsung usually builds good stock roms. Problem is Google only gives so much leeway to vendors modifying whatever base Android version it's running on.
Android 11 is a mess, Samsung had limited options and couldn't clean it up completely without disabling major "improvements" that are core elements of that OS.
The base Android OS is off the rails, dragging down Samsung with it.
I'm currently on the summer 2021 release of the Verizon stock rom based on Android 11 and ONE UI 3.1, but have been hearing about newer versions based on Android 12. I'm fairly happy with the performance of the existing combination, (the speed and battery life are nothing short of epic) but have never found a solution for the longstanding bug where audio playback inside of Shazam is choppy.
My question to the community is if newer builds of the stock rom fix the choppy Shazam audio playback, and also, whether or not they break the Wichita version of the Google Camera app, which I rely on extensively (unless there's a less-broken distribution that I haven't heard about yet, in which case, lay it on me!).
Well, I finally bit the bullet and chomped down all the dirty/in-place updates for both the stock rom based on Android 11 and Android 12. After I inserted a T-Mobile-branded sim card, it set off a whirlwind of changes, including switching the stock rom from the Verizon rom to the T-Moible one all by itself somehow. Lots of nasty packages to disable, but it calms down well enough after doing so. Among other things, the T-Mobile stock rom is extremely aggressive about software updates. I let it push me around this time, but after getting through the batch, I did disable the obnoxious & pushy updater.
I can confirm that choppy Shazam audio was fixed by one of those (can't remember which one) and that the Google Camera app still works in the new rom, so that's a win. The sidecar widgets are degraded, and the little animation that appears when power is connected looks kind of weird, but everything else is alright, except for the horrible widget shaping on the newer stock Samsung launcher. Also, the friendlier band switching menu is stripped out, requiring use of the dialer code to prompt the more primitive one.
If anyone was on the fence about it, as long as you're okay with those minor caveats, I'd recommend going along for the upgrade.
Hello,
I use an old for today's standards Samsung Galaxy J7 (2016) with a custom Android 10 rom with arm64 and OneUI 2.5 functionalities. Unfortunately, due to 2GB of RAM (even with additional 2GB of ZRAM), it's hard to cope with problems regarding apps in background closing right after roughly 1 minute of not using them (Youtube does this a lot) and sometimes apps lagging just while using them normally. So I'm thinking of flashing a Android 9 ARM32 OneUI 1.0 ROM. (My phone never had Pie update officially, so the switch from 8 to 10 was overwhelming.) But before I do that, I want to know what will I lose if I do, so I can see if it'll be worth it. I know that Google is planning to force devs to ditch ARM32, but before they do I want to feel comfortable with my phone. For now, as I've seen the features I will lose, that are valuable to me, are purely cosmetic, such as Video Enhancer and Edge Lighting. But if there are way more of them, please let me know. Basically I'm asking for a full list of changes from 9 to 10 and OneUI from 1 to 2.5.