yashsingh1/xdaforums huggingface dataset:
[Android General] zelipukin:
imperial.mack

looks like fstab from qualcomm device. This is not a stock ROM you are using ? LOS ?

Anyway, if same mechanism is in use, look for "forceencrypt=" part in any fstab (could be also in system/etc) or just run search
[Android General] NikosD:
Is there a way to change the volume without pressing the hardware keys during video playback or any other activity with sound ?

I don't want to go to settings for this, I look forward to a solution like the whiteness slider in the curtain or any other tile-based workaround.
[Android General] zelipukin:
NicosD

- gestures

- floating button

- extra navbar button

- voice

- gravity

- volume in notification

I'd prefer extra navbar button to open volume slider or volume in notification - simple, less power consumed, less mistakes
[Android General] NikosD:
Thanks for the answer, but do you mean that all these suggestions really exist in our stock ROM ?

I haven't found any of these !

For example, how can I add the extra navbar button in order to open volume slider ?
[Android General] zelipukin:
NikosD

Third party apps. I use "volume notification" in my another phone with broken vol and "custom navigation bar" in hi9 (to swap back and recent)
[Android General] NikosD:
After a little search, I just installed "Volume Control"

Thank you.
[Android General] Infect_Ed:
Edited because I tagged the wrong person ??

[MENTION=1980576]zelipukin[/MENTION]

I have started my base tree and have boot on TWRP, built from source. Touch axis is jacked up right now. I'll have it fixed up soon. Once I get that solid, I'll start working on getting a solid device tree going to get this thing booting on Pie. This is not a pic of your ported TWRP from hi9 air. This was built by me last night.

https://github.com/chuwi-hi9/android_device_chuwi_hi9pro
[Android General] NikosD:
After flashing a lot of times the official ROM of Chuwi using SPFlashTool and after unlocking the bootloader and rooting the decide, I have two issues that I don't remember having them using the original ROM that came with the tablet:

1) SIM cards

a) I use both slots of SIM cards using two nanosim cards from the beginning that I bought this tablet for mobile phone.

After flashing the ROM, it keeps loosing one of the SIMs and I get warnings that the SIM cards have changed for no reason.

If I open and close the SIM switch it usually fixes or it can be fixed by itself without doing anything, but it's a problem because you have to deal with it many times during a day without a reason, unexpectedly.

b) Just a few minutes ago I was trying to make a phone call and the line dropped after just a few secs of the beginning of the conversation ~15 sec.

The same thing happened when I accepted the call and it happened more than 10 times in a row.

Without moving from my location, I just rebooted the phone and I could eventually make a phone call without dropping the line.

2) WiFi

When I am connected to a WiFi network and I want to change to a different network of the list of the available WiFi networks, it's just impossible!

Whatever I'm trying to do, the tablet just doesn't allow me.

I have to switch off the WiFi network from Settings and then switch it on, in order to select a different WiFi network.

Does anyone have similar problems or have any idea how to solve them ?

Thanks!
[Android General] zelipukin:
I can't say anything about sim cards (I have one in #1 but it's not activated and #2 is for 128gb sd - works good).

Sounds like you have bad sim/phone contact

I have no problem with switching btwn different wifi networks
[Android General] NikosD:
Following your comment I have put the SIMs again in the tray carefully and uninstalled the last two apps regarding volume (a widget and a booster)

Since noon I had no problems with SIMs, phone calling and WiFi network selection!

The last one is a little weird, I don't know.

We'll see in the next few days.
[Android General] Infect_Ed:
Glad you got it fixed. If it happens again, go in your root browser and go to /data/data/com.mediatek.engineermode/shared_prefs/telephony_modem_settings.xml and enable both sims by turning both "false" booleans to "true". That should do the trick.
[Android General] Infect_Ed:
Here's the file
[Android General] Infect_Ed:
That's weird...it didn't upload the screenshot
[Android General] Infect_Ed:
Let's try this again

Lol. It doesn't want to upload. Sorry bro
[Android General] NikosD:
I always use external image repository, like postimage.

BTW, did you manage to complete the TWRP for Hi9 Pro ?
[Android General] Infect_Ed:
I was bricked for a minute ??. But yeah, I think I got it. I need to run some test flashes of some GSI's before I hand it out. #soon
[Android General] NikosD:
We'll, it seems that the SIM problems have gone but the WiFi problem hasn't.

But it's probably specific to certain list of Wifi networks of coffee shops that have a login form as first screen in order to give access (via email, password etc)

I don't know if anyone has the same experience but I don't remember having that problem.

Also, new for me, is an issue very common at Hi9 Air thread that I'm pretty sure I didn't have.

While speaking using a bluetooth handset and having 4G mobile data open, there are continuing disconnections/connections of the bluetooth device.

I'm pretty sure I didn't have this problem before.
[Android General] NikosD:
Hmm...After a reboot the bluetooth handsfree is working fine, even with the 4G mobile data enabled, so probably is not the ROM.

Looks like an app issue, as always and I'll try to do some more troubleshooting.

Update:

It was an app problem interfering with bluetooth that used to work fine though.

I'll probably try again to reuse it or find another one for the same task.
[Android General] NikosD:
Do you think is there any chance the TWRP you are trying to build from scratch could decrypt official ROM userdata partition ?
[Android General] lewmur:
If it was possible to for a third party to decrypt it then the encryption itself would be worthless. The answer is not no but hell no!!
[Android General] NikosD:
[MENTION=4034185]lewmur[/MENTION]

All the other TWRPs for all the other devices can mount and see userdata partition.

If that wasn't the case, then in what way a custom recovery could be useful ?

Unless if all working TWRPs can actually work, because you disable encryption completely with a hack and not because they are capable of mounting encrypted userdata partitions.
[Android General] lewmur:
It is very simple. You format the data partition and then flash a custom ROM. The ROM writes a new data partition that is NOT ENCRYPTED. Now TWRP can access it.
[Android General] NikosD:
This is not the case we have here.

We only have official stock ROM - one and only actually - and in case of Hi9 Air, the TWRP custom recovery used to work with the first two official stock ROMs and I mean it could mount the userdata partition.

But as I read in Hi9 Air, MediaTek released new encryption keys that made TWRP incapable of mounting the latest official stock ROM using those keys.

We, as Hi9 Air, are using this latest official stock ROM with the new encryption keys, that's why we can't mount the userdata partition.
[Android General] zelipukin:
"All the other TWRPs for all the other devices can mount and see userdata partition."

You have to provide pin/password you set up in Android (?)

Sorry, had no experience with TWRP+encrypted userdata.
[Android General] NikosD:
I'm not 100% sure about that, but most of the times if you are asked for a pin/password and you provide it, the TWRP should be capable of mounting the encrypted userdata partition.

Of course you could also leave the userdata without password/pin when setting up ROM or even remove it after the setup and in that case, maybe TWRP could mount the partition without asking anything.

I also have limited experience in encrypted data and TWRP, because I was using it strictly on one phone with custom ROM and without problems, probably because the data were unencrypted or some other unknown reason to me.
[Android General] lewmur:
Encryption works differently on the Hi9 Pro than it does on my Samsung devices. Samsung encrypts the data partition by default and the only way to disable it is formatting it in TWRP. Apparently, with the Hi9 Pro you have to go to /Setup/System/Reset to perform a factory reset to decrypt it. This will, of course, cause you to lose all of your settings, just as formatting it with TWRP would.

To turn encryption back on, go to /Settings/Security and location/Encryption & Credentials/Encrypt Tablet

edit:Even with the tablet encrypted, I was able to backup and restore via TWRP. I first mounted the partitions in TWRP and then did a backup. It gave a couple of errors but completed the backup. I then booted the tablet and performed a factory reset. Booted back to TWRP and did another backup. Got the same errors as I did with it encrypted. Restored the first backup and rebooted. Everything appears to be working. And it is back to being encrypted.
[Android General] NikosD:
With encryption enabled, if you boot to recovery TWRP can you mount the userdata partition using TWRP ?
[Android General] lewmur:
When I boot into TWRP, with encryption enabled, data, cache and microSD are already mounted. I have to mount system and vendor in order to backup.
[Android General] NikosD:
So, how did you do it ?

Did you have to flash the encryption preventer zip file from the first post ?

I'm about to format everything because bluetooth headset doesn't work OK eventually and I would like to have a working TWRP this time, mounting userdata partition.
[Android General] lewmur:
As far as I recall, all I did was install TWRP after unlocking. I know I didn't install the preventer zip because I'm still encrypted. I did install Magisk.
[Android General] NikosD:
I think that's impossible.

Just flashing TWRP leads to recovery loop if you don't root the device and if you flash Magisk like you did, then you get an encrypted not mountable userdata partition by TWRP.

At least this is the experience by most of us - if not all - here.
[Android General] lewmur:
What versions are you using? I installed TWRP-322-Chuwi_hi9_pro_04 and Magisk 17.1. My build version is 000623
[Android General] NikosD:
Exactly the same!
[Android General] lewmur:
Well here are some screenshots showing it worked for me.
[Android General] NikosD:
OK, but what makes you think you have an encrypted userdata partition ?

I just read that Magisk Manager prevents userdata encryption by default, so you don't need the prevent_encryption zip file in order to disable encryption and for TWRP to work with our stock ROM.

I think all we need is a careful series of steps with specific order of flashing Magisk and TWRP to work everything.
[Android General] lewmur:
My /Settings/Security and Location/Encryption and credential setting says my device is encrypted. As to the order of install, I don't see any possibility other than TWRP via fastboot and then Magisk via TWRP. Where did you read that Magisk prevented data encryption? I just read the opposite here https://xdaforums.com/newreply.php?do=newreply&p=78281445
[Android General] NikosD:
After numerous tests with the tablet, I managed to

have an unlocked, rooted device with working TWRP (aka it mounts the /data partition) and probably encrypted too

!

I started using SPFlashTool and flashing stock ROM.

My main concern is that I REALLY DON'T KNOW HOW THAT HAPPENED (!)

A few comments regarding some previous posts and tests that failed with my procedure:

That centainly didn't work!

After formatting data and flashing the prevent_encryption zip, I couldn't boot to system.

I had endless recovery loops, I could only boot to TWRP.

That didn't work too.

It's exactly the same like "format data" from TWRP, meaning that after rebooting to system and then back to recovery TWRP, the /data partition can't be mounted.

I can see now that my tablet says the same thing but I'm not sure the data are really encrypted.

There are a lot of other ways to root the device and flash TWRP besides those you mention.

The link you provided is not working, regarding Magisk, it redirects to my post.

I read about Magisk and not encrypted data partition here:

https://xdaforums.com/doogee-mix/how-to/fixed-how-to-remove-data-encryption-twrp-t3757595

So, let's summarize:

All the posts here in this thread including the first one, are inaccurate.

I personally believe that we all have unlocked, rooted devices with TWRP working with user data partition BY CHANCE.

I DARE you to provide a working solution step by step for someone who is flashing from the beginning the stock ROM using SPFlashTool.

Cheers!
[Android General] lewmur:
You DARE me??? What are you, in the 5th grade?? I have a working tablet with working TWRP, rooted with Magisk. If you think I'm going to start over and chance losing that in order to accept a childish dare, you have another think coming!:p

---------- Post added at 11:20 AM ---------- Previous post was at 11:14 AM ----------

Maybe that's your problem. I started with the stock ROM that came with the tablet. Used ADB Fastboot to unlock the tablet and flash TWRP recovery.
[Android General] NikosD:
Well, don't take it that personal!

The challenge is for everyone here [MENTION=1980576]zelipukin[/MENTION], [MENTION=7987739]Infect_Ed[/MENTION] and all the people having rooted devices and working TWRP.

I thought that too, maybe the flashed stock ROM is different than original ROM that came with the tablet, although I don't think so.

BTW, I'm 42 yo but still like to dare people like a child ;)
[Android General] zelipukin:
device encrypted (?) - 1st picture

no, it's not - 2nd picture
[Android General] chadamir:
How close are we to GSI? Has anyone used xposed on the tablet? Any issues?
[Android General] zelipukin:
It is treble enabled though not google play certified.

Anyone wants to try to flash gsi ?

I do not. Happy with current system as it is.

Every android update brings more pain than benefits (because I'm too old, yes, I'm still using Windows 7).

I've tried xposed(under magisk) but gave up same day.
[Android General] NikosD:
Agree. I don't think the device is encrypted with a working TWRP recovery.

One question:

What exactly "screen saver" option in settings is doing with this tablet ?
[Android General] zelipukin:
Screensaver helps to drain your battery more efficiently than just a black screen :)
[Android General] NikosD:
That's for sure, but besides testing when I select "activate now", I can't see it in action during normal use.

When exactly is activated and under what condition ?

Just checking it.
[Android General] lewmur:
Have you ever seen a tablet that was used for retail display, where you can see an image of the demo screen burned into the LCD? As the name implies, a screensaver is designed to keep that from happening by displaying a constantly changing screen or a blank screen.

---------- Post added at 09:00 AM ---------- Previous post was at 08:55 AM ----------

I think you will find those exact same screens on a brand new device that hasn't even been unlocked. The fact that there is a entry to allow encrypting doesn't mean the device isn't already encrypted.

edit; It would be nice if someone who hasn't modified their tablet could let us know what their settings say.

BTW; This is the link that I meant to post about Magisk and data encryption. https://github.com/topjohnwu/Magisk/issues/404
[Android General] NikosD:
IIRC, before disabling encryption with just a rooted and unlocked device, when I tap the encryption button the tablet did nothing.

It didn't open a new screen offering me the ability to encrypt it, probably because it was already encrypted.

It was like a disabled option.
[Android General] zelipukin:
Will upload back-to-encryption.zip for those who want to go back to encrypted userdata and didn't back up an original fstab.mt6797 ("encrypt tablet" from settings didn't wwork for me w/o fstab)
[Android General] DeveloperOne:
suddenly my tab went into loop of twrp, cant boot into system, what should I do

---------- Post added 3rd December 2018 at 12:16 AM ---------- Previous post was 2nd December 2018 at 11:58 PM ----------

nevermind i did twrp recover of para backup and it was fixed, thanks op, i panicked lol

By the way is there any way to improve the scrolling performance, its so choppy especially when i use s9 or oneplus 5 as my phone and come to tab it feels very choppy and annoying
[Android General] chadamir:
I can't get fastboot to see the device. I installed the mediatek drivers. I went into device manager and found a device called android that had an exclamation mark but no drivers I tried to use would work on it. Any ideas?

Edit: got it and flashed. Is the failed to mount data thing in twrp normal? Also now it's stuck on the chuwi logo at boot. It's not restarting, just stuck?
[Android General] zelipukin:
DeveloperOne

I don't have anything(flagship) in my hands to compare, here is a short video of how scrolling looks on my hi9.

Any idea what could cause that recovery loop ?

chadamir

You are talking about ADB/fastboot drivers, not about

Mediatek preloader VCOM drivers ?

Anyway, there are too many pitfalls to discuss and it's better to look for a help at dedicated forums
[Android General] chadamir:
I unlocked and flashed the fast boot and twrp then wiped then flashed the encrypt thing. I restarted and it was stuck on chuwi logo. I then tried flashing magisk but still stuck. When I try to wipe nothing happens. It says data can't be mounted. I just tried again.
[Android General] zelipukin:
You said "wipe" and "data can't be mounted".

Have you wiped your data partition instead of formatting it ? If you format userdata it should be visible under TWRP. Try to repeat steps, except unlocking and flashing TWRP, obviously.
[Android General] chadamir:
I stupidly formatted the system partition without a backup. I can't get spflashtool to see it. Miracle box isn't working either. I may try another pc that hasn't had so many drivers installed on it. Not really sure why spflashtool won't connect. Is there a way to flash the rom through twrp?

Can I flash the system.img through fastboot?

Edit Im back in via fastboot.
[Android General] zelipukin:
Try to fastboot flash system

fastboot flash system system.img
[Android General] NikosD:
The scrolling performance is something very relative, based mainly on previous experiences and always compared to a different device.

Coming from an ancient flagship of 2012, a Samsung Note II, with an AnTutu benchmark score of around ~33.000, this tablet is very fast at ~105.000 score.

If you compare this device with flagships of today, like S9 or OnePlus 5 having scores of more than 250.000, then it's definitely slow.

Especially in case of scrolling, even my Note II seems speedier sometimes due to the very low screen resolution of 720p.

So, even if Hi9 Pro has a more than average fast processor, the GPU can't always cope with the enormous screen resolution of 2560x1600 (!)

Don't get me wrong, the display and the huge resolution is the main reason for me buying this tablet, but the Mali T880 MP4 at 780MHz GPU sometimes looks like having lack of performance.

For me, scrolling performance is not that fast but it's definitely not that slow either.

---------- Post added at 10:32 AM ---------- Previous post was at 10:04 AM ----------

From my experience with SPFlashTool, the main reason of not seeing the device is because I connect the cable too early.

You have to load the tool and press the "Download" or "Firmware+Update" button and AFTER these, you connect the cable.

SPFlashTool is very stable if you have already installed the drivers properly and follow the above guideline.

Is everything OK now with your tablet ?
[Android General] DeveloperOne:
Wow yours look better than mine in regards of scrolling, have you done any mods? I am running stock rooted, European model with x20, any suggestions

about the recovery loop I'm not sure, I just turned off the tablet because it wasnt in use, when i turned it on later it went into the loop

---------- Post added at 03:55 PM ---------- Previous post was at 03:37 PM ----------

I agree, its a really inexpensive device at 120$ so I dont mind if it stays slow, but something seemed off, even the video above shows faster performance than mine, I checked for updates but its running latest rom. So i dont know. It just isnt close to the performance you would expect from a device scoring 105k on antutu.
[Android General] chadamir:
Everything is OK with my tablet now and I have root.

Edit: has anyone installed xposed yet? Also has anyone noticed massive idle drain on this device? Definitely loses 1 percent or more per hour even in deep sleep.
[Android General] NikosD:
The video very cleverly shows mainly text-based scrolling performance.

In real world, scrolling in a browser a page full of mixed text, graphics, video, ads etc sometimes it just seems to stuck and needs a push to proceed aka to scroll again.

But more or less, I get the performance you see on that video on my device too.

Try scrolling simple text pages and then maybe a factory reset could refresh your device.

But if it was slow from the beginning, check the temperature by touching the device on the back.

High temps could throttle the device.

Last time I checked it out, it lost 4% in 7 hours during sleep with WiFi, Bluetooth and mobile phone use ON (GPS and battery optimization OFF)

I'll check it again the next few days with the above settings and with Flight mode ON to see the difference.
[Android General] zelipukin:
Old Farter says:

Look at this screenshot. This is from my old Android 6 phone. You dont even need 3rd party app (like WLD that is not working on Android 8) to check what app is draining your battery. Just look through app list for "keep awake" time and if you find something enormous just delete that application. I'm not talking about "No WakeLock" xposed module where you can control wakelocks or similar, none of this stuff works under Android 8. I was pretty sure from the beginning (and it is) that the producer didnt bother to fill up power_profile.xml (part of framework-res.apk) with actual power consumption values for each hardware part. Well, you can fill it up by yourself but who can tell me how much mAmps takes wi-fi in scanning mode f.e. ??? but this is normal for chinesses brands. Also, for some reason, not all used user apps (system services ? Users don't have to know anything about system services running on their phones) shown under battery statistic.

I hope (scared) some day google will make an exact copy of ios, so there will be no worries about anything but emojis.

The whole world is going to hell.

chadamir I can only confirm that your problem is 3rd party app, my tablet lost 3% slipping 8 hours today (only wi-fi was on, everything else - off). There are no excessive kernel wakelocks (and this is only good thing in this message). I froze quite a few google services, use "Greenify" (at least something is working in 8.0) and I have a firewall keeps blocking many apps and some services from internet. But I dont't think it makes a big difference.
[Android General] NikosD:
Where is this app list in our tablet ? I can see the list of apps but with no battery use info.

:)

Today's test says this:

In 5 hours of sleep it dropped just 1% from 20% to 19%

This time I had Bluetooth OFF along with GPS and although I had WiFi and mobile phone ON, I got no email or any other message.

I have also seen based on my previous experience that battery drop is not the same for all battery percentage.

E.g 98% to 97% is different than 56% to 55%

I'll repeat the test during different initial percentage.
[Android General] chadamir:
I tweaked some stuff on the tablet and got about 2% overnight which is fine for me (Using L speed). I actually had the issue without installing anything so I dont think it's third party. Anyone played around with GSI yet? Doesn't android pie have a better battery manager or something?
[Android General] Vihru:
i have now hi9 pro, so can you tell me shortly, how to get rooted? unlock bootloader? install twrp? install magisk?