Related
So is there, or will there, be a way to artificially increase the screen resolution for the Skyrocket (much like this)?
I just moved from the Atrix and the lower screen resolution is killing me with the 4.5" screen. I feel like I'm using an old persons phone with the ginormous buttons and font, plus I hate not being able to fit as much information onto the screen. I'm considering moving to the Atrix 2 just for the resolution issue
Only thing I know of is the app LCD Density Changer from the market. Used it back on my Captivate. Not sure how well it works with the sr, but it was fantastic on my Captivate.
Sent from my SAMSUNG-SGH-I727 using xda premium
First thats hillarious. The atrix/atrix 2 are childs toys compared to the skyrocket. But there is an app called lcd density changer on the market. It requires root. , and if you change the settings apps may show up as unsupported in the market. So you would need to change it back to stock when on the android market.
I know what you mean OP. came from the atrix as well. u can use LCD density changer. along with the market problems (some updates wont even show up until you revert it back)
the touchwiz and its dialer will end up quite wonky as well as they don't adjust to the new resolution well. your option there will be to use a different launcher app/ dialer app.
Well then this solved all my problems! I set it to 200 DPI (instead of the default 240 DPI) and it looks so, so much better.
So far no issues except trying to download apps (I think updating works fine though). Anyone use this regularly and find any specific issues, whether it be with certain applications or whatnot?
Thanks again!
even though i dont use density changer i just go edit the build.prop and change it there.
i have no issues with density less the market stuff, and of course it looks like **** on TW. i have to use another launcher to make it look better. i hate the dead space left on TW when you lower the density.
i leave mine at 210.
Hey guys,
I'm trying (without luck so far) to change the DPI setting on my tablet so that I can have more screen real estate.
I'm running stock (ICS) rooted on my Galaxy Tab 2 7" - this ROM:
http://forum.xda-developers.com/showthread.php?t=1798283
So far, I've tried:
- Editing build.prop myself to change DPI manually
- Using an app from the Play story
- Following the suggestions in this thread: http://forum.xda-developers.com/showthread.php?t=1826067
(no luck at all, because this app doesn't even include the lcd density slider)
In all cases, I either get no result, or I get a black startup screen. After each method/approach, I restore a clean backup from CWM (so the approaches aren't conflicting with each other).
I can't get anything to work. Any suggestions?
Did you try "Rom Toolbox Lite" from the play store. You need root to use it.
Performance > Build.prop Tweaks > LCD density ... pick what you want > Reboot.
Sorry if you tried that already but that's the easiest way to do it as far as i know.
May be because of stock rom try cm10 from www.teamhacksung.org you will not be disappointed i use it now marvellous !!!
Sent from my GT-I9100 using xda app-developers app
Sean_Seany said:
Did you try "Rom Toolbox Lite" from the play store. You need root to use it.
Performance > Build.prop Tweaks > LCD density ... pick what you want > Reboot.
Sorry if you tried that already but that's the easiest way to do it as far as i know.
Click to expand...
Click to collapse
I did indeed try that. Unfortunately, the LCD density simply isn't an option under the Build.prop tweaks menu. I'm guessing that this has something to do with the fact that my build.prop actually contains no reference to LCD density. The normal build.prop entry isn't there. I don't understand the nuts and bolts of this well enough to know why, but somehow, the system is getting its LCD density settings from something other than build.prop.
I've truly read every item in build.prop, and nothing appears to be related to LCD density, even by another name. It just doesn't seem to be in there, which is probably why Rom Toolbox Lite is intelligently removing that particular slider option from my view.
Mohamedselim said:
May be because of stock rom try cm10 from www.teamhacksung.org you will not be disappointed i use it now marvellous !!!
Click to expand...
Click to collapse
I'm completely open to going to CM10, but I'll tell you my reservation (and maybe you can tell me if I'm just missing something obvious):
I tried two or three of the CM10 roms yesterday. In all cases, when I booted to my homescreen, it was stuck in landscape mode. It wouldn't rotate into portrait, no matter what I did. I spent hours combing through threads, trying to figure out why one of the most basic aspects of being a tablet (the ability to rotate orientations) was not working. I finally came across a solution that required downloading a new launcher APK. I applied the solution, and it worked. But it felt glitchy, and the whole user experience situation was a bit disappointing. It didn't feel smooth, not that their was intense lag, but there was a noticeable UI performance hit (at least in my own subjective opinion).
It IS sort of killing me that I can't get the DPI to something more reasonable though - so I'm a motivated CM10-er. I just can't deal with a tablet that I'll practically never use in landscape, being stuck in landscape.
Have you tried setting/display/rotation and ticked autorotate,include lock screen and 0,90,180,270 degrees
You could also try Nova or apex launchers or go launcher hd i use it now
Sent from my GT-I9100 using xda app-developers app
Mohamedselim said:
Have you tried setting/display/rotation and ticked autorotate,include lock screen and 0,90,180,270 degrees
You could also try Nova or apex launchers or go launcher hd i use it now
Click to expand...
Click to collapse
Yep. I think it's actually a known bug.
I have somewhat mixed emotions about eschewing the bloatware of the stock Samsung experience, only to put on a 3rd party launcher after the fact. But that's a philosophical debate best had elsewhere. I think my issue with CM10 or AOSP right now, is that stuff just doesn't seem to work right on the P3113. I could be wrong - in fact, I very well might be wrong. I'm not necessarily as up to date as someone who has owned this tablet for more than 3 days. But in terms of the 10 or so hours I've spent clunking away at it this weekend, it seems like some really obvious stuff is missing. (rotation, etc).
Hey guys,
I'm using an LCD density of 360 on my Nexus 5 by ending the build.prop, this feels comfortable for my use and I'd like to keep it that way. BUT I sorely miss not having phablet ui. Is there a setting I need to be using to change my SystemUI to a particular dpi to switch everything to Phablet UI while still keeping the overall LCD density to 360? I'm using the "App Settings" module in Xposed and have tried just about everything but can't get the Phablet UI to engage. Any advice would be very much appreciated.
Thanks.
the7thson said:
Hey guys,
I'm using an LCD density of 360 on my Nexus 5 by ending the build.prop, this feels comfortable for my use and I'd like to keep it that way. BUT I sorely miss not having phablet ui. Is there a setting I need to be using to change my SystemUI to a particular dpi to switch everything to Phablet UI while still keeping the overall LCD density to 360? I'm using the "App Settings" module in Xposed and have tried just about everything but can't get the Phablet UI to engage. Any advice would be very much appreciated.
Thanks.
Click to expand...
Click to collapse
i want to do this too...anyone willing to help ?
ranasrule said:
i want to do this too...anyone willing to help ?
Click to expand...
Click to collapse
There are 2 things we need to discuss.
1) System UI layout change to Tablet mode or Phablet mode UI. This changes the layout of the Nav Bar, Status bar and Notification area. Google removed this function. There is no way to get it back.
2) Triggered Tablet layout of specific apps. Developers of apps may wish to change the layout of their apps for a tablet. More screen real estate can mean there are better layouts than used for the phone. The only reliable trigger that a developer can use is dpi.
The bigger screen at the same resolution will have a lower dpi than a smaller screen at the same resolution. We can trigger tablet layout in apps by forcing the dpi down system wide using the build.prop. However, different developers will be triggered by different dpi's meaning you may need a dpi so low you cant see it on your small screen before some apps trigger.
You can use the Xposed module named "app settings" to actually change the layout of individual apps to tablet layout. So for example, you can set Chrome to be tablet layout without changing the dpi of the system or tha app itself. That's the only option though. Not all apps have a tablet mode.
rootSU said:
There are 2 things we need to discuss.
1) System UI layout change to Tablet mode or Phablet mode UI. This changes the layout of the Nav Bar, Status bar and Notification area. Google removed this function. There is no way to get it back.
2) Triggered Tablet layout of specific apps. Developers of apps may wish to change the layout of their apps for a tablet. More screen real estate can mean there are better layouts than used for the phone. The only reliable trigger that a developer can use is dpi.
The bigger screen at the same resolution will have a lower dpi than a smaller screen at the same resolution. We can trigger tablet layout in apps by forcing the dpi down system wide using the build.prop. However, different developers will be triggered by different dpi's meaning you may need a dpi so low you cant see it on your small screen before some apps trigger.
You can use the Xposed module named "app settings" to actually change the layout of individual apps to tablet layout. So for example, you can set Chrome to be tablet layout without changing the dpi of the system or tha app itself. That's the only option though. Not all apps have a tablet mode.
Click to expand...
Click to collapse
Thanks for the reply but the request is for Phablet UI...kind of something like this atleast >>> http://forum.xda-developers.com/showpost.php?p=50945366&postcount=750
as far as my Info goes tablet UI is not longer available but Phablet is possible
ranasrule said:
Thanks for the reply but the request is for Phablet UI...kind of something like this atleast >>> http://forum.xda-developers.com/showpost.php?p=50945366&postcount=750
Click to expand...
Click to collapse
For phablet ui, read point 1.
That screenshot is not phablet ui. Its just a lower dpi.
To lower dpi, either do it system wide using build prop or with xposed module "app settings", set dpi for systemui lower. Say maybe 300.
Sent from my Nexus 5 using Tapatalk
rootSU said:
For phablet ui, read point 1.
That screenshot is not phablet ui. Its just a lower dpi.
To lower dpi, either do it system wide using build prop or with xposed module "app settings", set dpi for systemui lower. Say maybe 300.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I thought Google only removed TableUI, but PhabletUI still exists. I could be wrong though.
the7thson said:
I thought Google only removed TableUI, but PhabletUI still exists. I could be wrong though.
Click to expand...
Click to collapse
Maybe I don't know. My understanding was there was 1 UI now. Maybe you need to ask someone in PA team
IF it does exist, there's no way to get it... Unless PA can do it.
Ok, so in the past Huawei has decided on a few of their larger devices to go with 400 DPI instead of the standard 320 DPI that android should be at. This makes the UI a little to large. Sure you can root your phone and tweak the build.prop file for different DPI, but then icons look weird and there's other issues. 400 DPI just looks wrong to me, I'm sure some folks like it, but I really don't
I found something called "App Layout" in the settings today. This is awesome my friends.....
The "Standard" setting is 400 DPI (Default)
"Reduced" looks to be 320 DPI
There's even a custom where you can do per app DPI settings just like you can in Xposed framework!
This is truly a great piece of work from Huawei, Now we can set the DPI where we want it. Nicely done Huawei!
All we need now is to have the memory manager work a little better and I will go on record saying that other than Cyanogen or plain android, this is the best Vendor skin to date. So much you can do with it... I haven't even unlocked or rooted my phone yet and I don't think i'm going to bother (Plus I want to install all the update files without hassle since it seems like they are coming out pretty fast)
omniphil said:
Ok, so in the past Huawei has decided on a few of their larger devices to go with 400 DPI instead of the standard 320 DPI that android should be at. This makes the UI a little to large. Sure you can root your phone and tweak the build.prop file for different DPI, but then icons look weird and there's other issues. 400 DPI just looks wrong to me, I'm sure some folks like it, but I really don't
I found something called "App Layout" in the settings today. This is awesome my friends.....
The "Standard" setting is 400 DPI (Default)
"Reduced" looks to be 320 DPI
There's even a custom where you can do per app DPI settings just like you can in Xposed framework!
This is truly a great piece of work from Huawei, Now we can set the DPI where we want it. Nicely done Huawei!
All we need now is to have the memory manager work a little better and I will go on record saying that other than Cyanogen or plain android, this is the best Vendor skin to date. So much you can do with it... I haven't even unlocked or rooted my phone yet and I don't think i'm going to bother (Plus I want to install all the update files without hassle since it seems like they are coming out pretty fast)
Click to expand...
Click to collapse
Yeah, it's great if you decide to stay stock as you don't have to do much to change the DPI. You can change the DPI also without rooting by opening a command prompt in adb and running a command.
omniphil said:
Ok, so in the past Huawei has decided on a few of their larger devices to go with 400 DPI instead of the standard 320 DPI that android should be at. This makes the UI a little to large. Sure you can root your phone and tweak the build.prop file for different DPI, but then icons look weird and there's other issues. 400 DPI just looks wrong to me, I'm sure some folks like it, but I really don't
I found something called "App Layout" in the settings today. This is awesome my friends.....
The "Standard" setting is 400 DPI (Default)
"Reduced" looks to be 320 DPI
There's even a custom where you can do per app DPI settings just like you can in Xposed framework!
This is truly a great piece of work from Huawei, Now we can set the DPI where we want it. Nicely done Huawei!
All we need now is to have the memory manager work a little better and I will go on record saying that other than Cyanogen or plain android, this is the best Vendor skin to date. So much you can do with it... I haven't even unlocked or rooted my phone yet and I don't think i'm going to bother (Plus I want to install all the update files without hassle since it seems like they are coming out pretty fast)
Click to expand...
Click to collapse
Is this on the new updated roms? Because if can not find this setting on my stock 702 rom version?
Benjiro said:
Is this on the new updated roms? Because if can not find this setting on my stock 702 rom version?
Click to expand...
Click to collapse
I'm on a 703 running B108.
Settings -> Apps -> App Layout
That's what I have...
omniphil said:
I'm on a 703 running B108.
Settings -> Apps -> App Layout
That's what I have...
Click to expand...
Click to collapse
That explains that ... My 702 is still on B103 ... No official updates have come yet for the internal updater.
the only problem though is that the Microsoft Office apps such as Word does not go to tablet mode despite it being set to reducing mode but whenever I tweak the dpi to 320 via adb, it does show in tablet mode but some app icons and task manager are a bit messed up. Other apps such as Facebook or Youtube does seem to display on tablet orientation when in reducing mode.
mcdhol_24 said:
the only problem though is that the Microsoft Office apps such as Word does not go to tablet mode despite it being set to reducing mode but whenever I tweak the dpi to 320 via adb, it does show in tablet mode but some app icons and task manager are a bit messed up. Other apps such as Facebook or Youtube does seem to display on tablet orientation when in reducing mode.
Click to expand...
Click to collapse
I think that has to do with teh odd 1920x1200 rez. If it were 1920x1080 then it probably would detect phone mode/tablet mode correctly
Flash rom KangVIP, you can adjust DPI switching to 400, 380,360,340,320 dpi
http://cn.club.vmall.com/thread-6033530-1-1.html
eennap said:
Flash rom KangVIP, you can adjust DPI switching to 400, 380,360,340,320 dpi
http://cn.club.vmall.com/thread-6033530-1-1.html
Click to expand...
Click to collapse
If I switch the dpi to 320 if I'm using that rom does the UI becomes a bit weird? I just wanna ask because whenever I switch the actual dpi to 320 via adb (with the original B109 rom), some of the icons are smaller and have green background in them and other glitches.
mcdhol_24 said:
If I switch the dpi to 320 if I'm using that rom does the UI becomes a bit weird? I just wanna ask because whenever I switch the actual dpi to 320 via adb (with the original B109 rom), some of the icons are smaller and have green background in them and other glitches.
Click to expand...
Click to collapse
UI will be normal same as original B109 rom but font in app will be smaller.
mcdhol_24 said:
If I switch the dpi to 320 if I'm using that rom does the UI becomes a bit weird? I just wanna ask because whenever I switch the actual dpi to 320 via adb (with the original B109 rom), some of the icons are smaller and have green background in them and other glitches.
Click to expand...
Click to collapse
If you use Nova Launcher, that fixes the icon problem.
For the unlucky ones with 702L. I found a possible fix (still testing) to set the dpi to 320 without issues in SwiftKey being huge for example. Need to be ROOTED. So this is what I did.
1. Edit the build prop and add/change both " qemu.sf.lcd_density=320 " and " ro.sf.lcd_density=320 "
2. Use terminal emulator with
Su
Wm density 320
Reboot.
Now Wm density should show one value not 2 and SwiftKey should work as well.
Cheers.
Nice. Been looking for the SwiftKey fix. So, for this fix to be working do you need to get it rooted? Cheers
On 2nd thought, this SwiftKey problem doesn't exist on other keyboard apps like fleksy, googles own and go keyboard.
Yes you have to be rooted for that. But being rooted has of course a lot of other advantages and is easy to do once the bootloader is unlocked (I used the paid option from the root guide and I was rooted within half an hour).
I tried the other keyboards as well, seems SwiftKey uses other parts of build.prop to get dpi.
Hope I could help.
I'm considering the M5 8.4 to replace my aging Nexus 7 (2013) and would like some feedback on the EMUI software experience.
Do you like the skin? Is it similar to stock Android?
Since there probably won't be many ROM options, how is Huawei's track record with updates?
Thanks,
Rick
Sent from my Pixel 2 using Tapatalk
There should be lots of ROM options shortly if not right away, since the device is Treble compatible as are other EMUI 8.0 devices.
For whatever it's worth:
I am running EMUI - but debloated with Nova installed (I couldn't imagine Android without Nova). I'm also not 100% sure what features are EMUI vs stock Oreo.
There's a "Launch" feature built in to EMUI that allows you to specify which apps are allowed to launch in the background, allowed to be launched by a secondary app, and allowed to run in the background. I like this feature, but if you don't bother setting preferences for each app, EMUI kills background apps somewhat aggressively.
EMUI lets you choose between a collapsible navbar (if rooted you can use Exposed Edge Pro instead), and/or a one-button navigation system using the fingerprint sensor - tap for 'back,' hold for 'home,' swipe for 'recents.' I am using the one-button system in conjunction with Edge Pro and to me it's pretty seamless (but I still have to work on not hitting the sensor by accident).
The dialer and SMS skins are fine. Stock DPI options are a bit high, but you can change via developer options (after every reboot). Stock camera app no longer works if you change the DPI, but you can always use opencamera (or change the DPI back).
The other day I had an issue with background music playback about 45 minutes into streaming music via an old version of eDJing premium. Issues stopped after I disabled Doze (via root app that I had set to run at boot). That's probably an Android issue?
Battery life for me is in line with what I have experienced with every similar phablet I have previously owned.
Anyways, all EMUI 8.0 devices share key things in common, so the dev community is larger than it seems.
Thanks, I appreciate the feedback. I also use Nova and will probably remove some of the reduny apps. I can see myself rooting and using Magisk.
Sent from my Pixel 2 using Tapatalk
In my opinion the emui is not bad.
The personalization of Android that Huawei made is pretty clean.
However they obviusly add some bugs:
- adaptive icons do not works correctly: you can have only the circular one (even with Nova)
- the resolution of the display or the information that the apps get are really strange: some app starts always in landscape, no matter the actual orientation, other render the pages in strange ways when the tablet in turned fron landscape to portait, etc... Really really annoying
- battery optimization is too agressive and it is not (for me) completely clear how to tune it
- every time the launcher is updated, it switch back to its stock launcher, and i have to set the nova again as default (this can be done just in the default app in the settings). Probably this will happen also for other apps.
The hardware is solid and the battery life is good.
The position of the touch sensor and of the hardware buttons are not imho right and a big design failure.
If you keep the tablet in portrait with the touch button in the buttom: the hardware buttons are almost inaccessible unless you have a prehensile bellybutton ?
In landscape if you try to change the volume with the hardware button your finger will touch the touch button and the current app is "closed" (the tablet swith back to the home screen). This is a software feature (bug?) that i will like to change
Inviato dal mio CMR-AL09 utilizzando Tapatalk
Also the Mediapad is now listed as enterprise device. I'd be surprised if they'd stop with updates soon.
As for EMUI:
It's a mixed bag for me. There are 3 annoying bugs which most likely have their origin in EMUI:
- 2 fingers at the same time without instantly moving makes the tablet not recognize the input anymore. (there is a thread on xda about it)
The other 2 are about the keyboard accessory which is probably irrelevant for you (for everybody else):
- flipping the cover from front to back triggers a "refresh", black screen on netflix or a return from edit mode to view mode in xodo pdf
- EMUI always asks if I want to start desktop mode when a keyboard is connected, doesn't matter if you tick the "don't remind me again" checkbox
giovaorama said:
- adaptive icons do not works correctly: you can have only the circular one (even with Nova)
Click to expand...
Click to collapse
Squircle works for me. I think all work. I'm not sure they work how they should. Not that I care.
- the resolution of the display or the information that the apps get are really strange: some app starts always in landscape, no matter the actual orientation, other render the pages in strange ways when the tablet in turned fron landscape to portait, etc... Really really annoying
Click to expand...
Click to collapse
This usually has to do with the apps, not EMUI. Install Rotation Control to force auto rotation across all apps.
battery optimization is too agressive and it is not (for me) completely clear how to tune it
Click to expand...
Click to collapse
This is probably the biggest issue with EMUI. But almost everything is tunable and with root/feedback from other EMUI users, I don't expect this to be a long term issue for anyone. (I started having issues playing music in the background without a charger plugged in - they fixed themselves last night and I'm not sure why. My preferred music player app was last updated in probably 2011, might or might not be a factor.)
every time the launcher is updated, it switch back to its stock launcher, and i have to set the nova again as default (this can be done just in the default app in the settings).
Click to expand...
Click to collapse
I can confirm that you do not have this issue as long as automatic updates are turned off. I have also seen a general improvement after uninstalling updates to Google Webview.
The one EMUI feature I like that I forgot to mention in my previous post, is Eye Comfort. It's a partial blue light filter that works better than any apps I've found on the Play Store.
Nope the adpative icons do not works, and this is something that you may corcern since this is one of the feature of Oreo and the app on oreo only gave icons to works as adpative. The circle one are just ugly.
Regarding the orietation, the same app works all correctly on my previous tablet and on all my other devices.
Root should not be required to solve implementation problem.
The sotck rom must be as much as posdible bug free.
For all this bug we should blame Huawei: have a look to the support fotum for nova launcher or chronus, just to understand the real situation.
As usual what it is important for someone count nothing for the others
Inviato dal mio CMR-AL09 utilizzando Tapatalk
Hi anyone on EMUI in the UK with the 10.8 Wifi version (CMR-W09). Would you please tell me what is the version you are on (Latest). As I am considering going back from Lineage for a short while as there are too many bugs just now. Stupidly I didn't note down what version of EMUI 8 I should be on and there are tonnes of them. Cheers.
generic2 said:
Hi anyone on EMUI in the UK with the 10.8 Wifi version (CMR-W09). Would you please tell me what is the version you are on (Latest). As I am considering going back from Lineage for a short while as there are too many bugs just now. Stupidly I didn't note down what version of EMUI 8 I should be on and there are tonnes of them. Cheers.
Click to expand...
Click to collapse
SHT-W09C432B151 (8.0.0.151) is what you need
Hey there,
It's not a mixed zone for me:
1) If I wanted an Ipad I would have bought that.
2) I do not like limits in terms of app-drawer etc. (fixed this, now using Nova Pro)
3) battery optimization too heavy: hell, using the keyboard with firefox (nebo, playstore, and may more) is almost impossible as the screen brightness lowers even if automatic brightness adjustment is turned off ...
What I love is:
1) Battery live
2) How it all fits together (So the "Iphoneish feeling" that I cried about above is not my taste, but it's a consistent Design at least ...)
I bought the Mediapad mainly because of the Pen, the Hardware, and the Keyboard(if I am not hating it for ausing brightness trouble...) and these are the things that I really like!
I don't mind emui has some good features and of you use Nova you can make it look stock. I like the themes and the book cover feature. I like the battery optimisation it lasts so well.
I'm trying to get ahold of the stock firmware so I can root mine.
Sent from my Pixel 2 using Tapatalk
Lee82UK said:
SHT-W09C432B151 (8.0.0.151) is what you need
Click to expand...
Click to collapse
Thanks very much. Appreciated!
odd1ne said:
I don't mind emui has some good features and of you use Nova you can make it look stock. I like the themes and the book cover feature. I like the battery optimisation it lasts so well.
Click to expand...
Click to collapse
the tab has great features but some disadvantages (brightness bug with keyboard for me ... weird behavior at least)
Best of all certainly is the battery life! And I am using Nova ... That's why the look is not too much of an issue
I do notice the aggressive doze feature.
Sent from my SHT-W09 using Tapatalk
I decided to replace my aging, but beloved, Nexus 7 2013 WiFi (running LineagoOS 15.0) with something a bit meatier. After much consideration, I ordered and received a 32GB M5 8.4 (SHT-W09) from Amazon UK.
First up, the hardware is awesome. I really notice the difference with the move to 4GB RAM and the updated CPU / GPU. The performance is worlds apart from the Nexus 7 - very zippy, very responsive, games run great etc. The display also is a significant improvement - I really like the 16:9 ratio too and don't agree with review feedback that it impacts eBook and web browsing. It works great for those and just looks incredible for movies and TV. No surprises so far, then, given the 5 year old spec of the N7. On the subject of this display, note that both Amazon Prime Video and Netflix now support HD playback on the SHT-W09. Absolutely brilliant. Audio is fine, I'd always listen through Bose BT OE headphones anyway. The lack of 3.5" headphone jack doesn't bother me in the least.
So, on to the OP question about EMUI. To be honest, I really don't like it. The sheer number of junk apps installed is disappointing, especially as some (YouTube, for example) cannot be uninstalled. Note that of the 32GB available, only 16GB was available out of the box. Adoptable storage has been explicitly disabled in EMUI, so there's no option to use external SD as internal storage. A bit disappointing, but a 128GB MicroSD gives plenty of storage for media, if not apps. Within the UI itself, I miss the app drawer button (I'm sure there's an option somewhere) and it all just doesn't feel "familiar" enough for my liking. The Themes idea is great, but the version delivered with the tab only seems to support local themes - there's no "Theme Store" as such, unlike the phone version of the app. As such, customisation feels limited. I've simply installed Nova and couldn't be happier with the end result.
A really worthy replacement for the king of Android tablets, the Nexus 7 2013, so I'd encourage the OP to give it a go!
@mroshaw similar for me. I replaced my Nexus 7 (2012) by the SHT-W09 and I am quite happy. I uninstalled all the apps I do not use (ebay, facebook, some games, ...) and I replaced the laucher with the Pixel-Launcher. The only parts which still remember me that I am running on EMUI are the top bar and the configuration settings, but I can live with that.
I do not regret having it bought. There are not many Android tablets out offering such a build quality and performance for such a price tag.
I am growing to like the emui. It's got some grand security features. Like others, I uninstalled a TON of apps, disabled others, then I put an AOSP P Dark theme (from here on xda). The theme takes care of the notifications bar icons - I didn't really like the emui ones - plus "stock-ifies" most of the UI.
@mroshaw To activate the app drawer button, go to Settings, Display, Home Secreen Stlye, choose Drawer.
To enable SD card storage, Settings, Storage, Default Location. I have 45GBs out of the internal 64GB once I adb uninstalled bloat.
The deal breaker for me with EMUI is the missing option to plug in the tablet via USB and mount its storage to be visible and usable with any files operation (I use Linux only). There is no HiSuite for Linux and doing everything via adb is just a pain in the neck.
Having said that, the alternative is Lineage OS as the currently only alternative ROM, but this breaks two other things which are a deal breaker as well: No Bluetooth connectivity (its just dosn't pair anything properly), so no BT audio, which sucks when there is no headphone jack. Plus, with a custom ROM you lose L1 security in widevine, so no HD streaming with Netflix or Amazon video.
Fortunately, my usage for the tablet is different from my beloved N7; I mainly use it as a score reader for my piano. I wouldn't recommend it as a replacement for the N7; for that I bought the Lenovo Tab 4 Plus and it's a perfect replacement - except there are no custom ROM, But you can root it and the Lenovo UI is pretty much stock.
@DF5JT mtp works for me to access the device's internal and sdcard storage. Probably you need to configure your udev rules to identify your device correctly.