yashsingh1/xdaforums huggingface dataset:
[Android General] NikosD:
Hello.

Is there a sign, like 4G+ in order to see the change from LTE to LTE Advanced mobile data, when the tablet is in the suitable range of a LTE Advanced network ?

Also, is there a way to check in real-time from the engineering menu or from an app if Carrier Aggregation is used inside the range of LTE advanced network and at what bandwidth ?

Our tablet is LTE advanced compatible category 6, meaning a max download speed of 300Mbps with CA at 20MHz bandwidth.

Thanks!
[Android General] geronracing:
Ya, that's what I am worried about. Can't wait that long, as I need to use it! Hoping that it was something else I was missing...
[Android General] Infect_Ed:
There is stuff missing. No Android auto blobs. After I finish up I'll build it into it if it's that important to you. I just need to find more time. Been busy as hell lately.
[Android General] Vihru:
how its going?
[Android General] geronracing:
You have no idea how awesome that would be! Trying to make a data system for my track car and mirroring through android auto is a must. If I can't get it to work, then I'm going to have to get another tablet.
[Android General] lewmur:
Reset to factory

I have my Hi9 Pro unlocked, rooted and with TWRP installed. But I have decided to sell it and get the 10" model. How do I return it to stock recovery, unrooted and locked?
[Android General] Infect_Ed:
With SP Flashtool and stock firmware that's posted in op
[Android General] lewmur:
X20 or 23

How can I tell if my CPU is X20 or X23? I'm selling it and a potential buyer wants to know.
[Android General] Infect_Ed:
As far as I know, they are all x23. I was previously mistaken.
[Android General] Bdhester123:
The new ones on gearbest say x23. Mine, bought in December. Is x20
[Android General] lewmur:
Antutu benchmark says my hightest CPU speed is 2,330,xxxMhz. I assume that means it's an X23. Is that correct?

Edit: Now I'm really confused. Both Antutu and Device Check from the Play Store, indentify the SoC as an MT6797X and say it is an X27. But the X27's max clock is suppose to be 2.6ghz but my max is 2.3ghz.
[Android General] amg314:
Need detailed CPU info?

Use terminal command (no root needed):

================

cat /proc/cpuinfo

In my tablet:

..............

U implementer : 0x41

CPU architecture: 8

CPU variant : 0x0

CPU part : 0xd03

CPU revision : 4

Hardware : MT6797

..............
[Android General] NikosD:
I tried to download the Netflix app from Google Play but it was impossible and I got a message that it's not compatible with our device.

What is the best way to watch Netflix using this device ?

Update 1:

I downloaded manually the latest Netflix APK from apkmirror and works fine.

Update 2:

Our device has Widevine L3, so even using the UltraHD plan with 2160p source, I managed to get only 960x540 max resolution.

Also, you can get up to 30 fps (no more), 8bit video.
[Android General] KimLe:
**** Finally I got it root*****

- Unlock bootloader

- Flash TWRP (hi9pro_twrp.img)

- Boot into recovery ( screen shows orange state wait 5 seconds to boot into screen to select- recovery/fastboot)

- Format data (****importance step****)

- Mount vendor, Data

- Flash Magisk.

- Flash para.zip

- Flash encryption_prevener_hi9pro.zip (optional)

- Wipe Cache/Davis

Reboot to system.

Screen will shows " orange state..." . But it will boot into system.

In system , install Magisk manager if it does not show up in app drawer.
[Android General] KimLe:
Anyone know to mod the in-call volume. It is really low. Thanks
[Android General] Vihru:
what could we do with root? can we make better performance or something
[Android General] amg314:
https://www.educba.com/rooting-android/
[Android General] Bingley:
Wow, I just got hold of one of these and I cannot believe it's slower & laggier in use generally than my Nexus 7 2013 with a 9.0 rom on!

What the hell is the issue with 8.x on this thing, it should fly but instead feels like its struggling even to just stand still let along do anything useful like browser the web!

Anyone's running acceptably fast/smooth?
[Android General] Infect_Ed:
It's a slow device... Gpu on it is subpar. I was in the middle of bringing it up, but I'm incredibly busy ATM. Will pick it back up in a few weeks when I have more time.
[Android General] Vihru:
take your time! and thanks for the info.
[Android General] NikosD:
According to its specs, Asus Google Nexus 7 2013 is a very slow device nowadays.

Consider a factory reset of Hi9 Pro or even a replacement if you feel it's not twice as fast at least.
[Android General] Bingley:
It isn't as fast as a new tablet but it's definitely no slouch with aex rom foe general use ie no gaming. I've factory reset twice and it's just too badly optimized I think-android 8should run fine on this setup.
[Android General] Michel177:
but antutu 99500

So I got mine a couple of days ago .I ,of course ,unlocked the bootloader and installed TWRP .I find the tablet (mine came with MT6797X-Helio X27) quite fast .

I only wonder why this tablet does not have a serial number and is not (as received ) play protect certified .
[Android General] Vihru:
is it lagging on launcher or just using it?
[Android General] Bingley:
Mine is mostly ok in launcher, it's the system menus & notification swipe down that is laggy and generally not as responsive as even my old Nexus 7 2013. I'm sure Pie will bring it up to speed to some degree. Is anyone using it with the film screen protector on it? I feel that's causing some of the missing inputs
[Android General] Vihru:
yeah same.. i had film protector on..
[Android General] KimLe:
Is your tablet CHUWI HI9 PLUS CWI532 4G Phablet 4G + 64G - BLACK MT6797 ( X27 )?

This forum is talking about H9 Pro.
[Android General] Michel177:
Chuwi HI9 Pro

Yes my tablet is Chuwi HI9 pro 8.4 pces bought from Banggood .The back of my tablet shows HI 9 pro but with type CWI 532
[Android General] NikosD:
Screen protector was the first thing I removed, it was full of bubbles and an added lag to the touch screen.

Never heard before a Hi9 Pro 8.4" with a real MediaTek Helio X27

Can you run a diagnostic app like DevCheck or Device Info HW and see in Hardware Tab the specs ?

Because my Hi9 Pro is reported as X27 and MT6797X by DevCheck but the CPU cores are:

4xA53

4xA53

2xA72

and the A72 cores are running at 2.3 GHz.

The most important thing is the CPU freq of A72.

[MENTION=9350973]All[/MENTION]

Don't pay too much attention to reported specs but to real-world numbers.
[Android General] Vihru:
i have also hi9 pro cwi532 with x27.. :D thats weird.
[Android General] Michel177:
Is it possible that Chuwi used effectively an MT6797X but limited the max freq to 2.3 gHz ?

Also since this tablet is treble enabled ,would it not be possible to use a treble rom with it ?
[Android General] NikosD:
It's possible.

There are a few treble based ROMs (GSI) based on Android 8.0, 8.1 and even 9.0, but none of them can be installed directly on our device.

We need a developer to customize the ROMs and fix the built-in bugs that all of them have.

And it seems that there is still no developer available for our device.
[Android General] Diomorgan:
ouch, look flashing magisk 18+ is not rooting anymore, I have to switch back to 17.1 and refuse the uoadte of magisk manager, since if you uodate, magisk mangaer 7 won't allow you to update the magisk but just to patch the boot.img.

Doease someone as already the 18+ magisk patched boot .ini to flash with twrp?

Thank you ;)
[Android General] lilhaiti:
Can the resolution be changed on these tablets.
[Android General] amg314:
I am next door guy from 'Chuwi Hi9 Air' thread.

You may check Treble compatibility directly using following terminal command:

*----------------------------------------------------------------------------------------------*

getprop ro.treble.enabled

If:

true = Project Treble supported

false = No Project Treble support

Or thru special app "Treble Check"

*----------------------------------------------------------------------------------------------*

In theory, GSI is hardware isolated and all hardware specific data is concentrated in Vendor.img

Thus, you can try flash any suitable GSI using URL below:

*----------------------------------------------------------------------------------------------*

How to flash a Generic System Image (GSI) on Project Treble supported devices

https://www.xda-developers.com/flash-generic-system-image-project-treble-device/

*----------------------------------------------------------------------------------------------*

I tested several Pie GSI. They all started and worked on my Chuwi with minor issues.

However, the speed of my tablet has slightly decreased, and all the SGI has been adapted for phones small displays.

I have not found any advantages with Treble GSI.

Therefore, I returned to the Oreo stock firmware (Magisk, microG, Xposed, etc.)
[Android General] NikosD:
Try using TWRP to flash Magisk.

It worked for me using Magisk 18 and Magisk Manager v6.1.0

Haven't tried yet newer versions.

---------- Post added at 08:31 PM ---------- Previous post was at 08:23 PM ----------

Yes of course Hi9 Pro is a Treble supported device.

But personally I think I'm going to wait for Chuwi releasing stock Android 9 for our device in summer, unless we are lucky enough and a developer catches Android Pie first.
[Android General] Bdhester123:
I just installed TWRP, lineage os, magisk, and xsposed. super lucky it booted...lol
[Android General] Diomorgan:
whick version of magisk? Can you share the .zip file (if is it legal to do here?) Thank you!
[Android General] Bdhester123:
Prolly don't have enough street cred to share link. I will try and find it.

I initially used the directions for root/TWRP/magisk on the 1st page of this thread with no issues.

This is my first device I have ever tried to play around with the inner workings...so I am a bit curious ?. I have been down the rabbit hole into places of weird code( no experience at all..lol), lots of new languages and programs..it's really quite interesting. I can definitely see the draw it has on people.

---------- Post added at 01:36 AM ---------- Previous post was at 01:18 AM ----------

I am pretty sure I downloaded Lineage OS 15.1. magisk manager v 5.8.0. Magisk 16.6. xsposed 3.1.5 Framework version 90-beta3

I basically installed lineage for hi9 air from the main thread on that device. I took system.img and boot.img from there and flashed with spftool using the hi9pro scatter file from official room release.

The only bug I have found so far is that the wifi is really weak..looking into that now.
[Android General] Diomorgan:
ok, thank you, which ver. of magisk do you have? ??
[Android General] Vihru:
do you mean that you installed lineage from hi9 air to hi9 pro?
[Android General] Infect_Ed:
They are basically the same device in many aspects. I refuse to flash my lineage builds through spft. I am only using twrp to try and flash, as spft is not intuitive to many and can really damage your device if you use it improperly.
[Android General] Diomorgan:
And does it works? ?? the magisk problem anyhow is with ver 18+, 17+ works fine, but thank you for the infos ?
[Android General] Bdhester123:
Yes. Hi9 air, pro, and plus are really similar. But I'm a super noob..so I just got lucky. I have done a ton of research though.

I fixed the wifi issue...not entirely sure if it was rom or a location permission problem. Tablet is working fine. I have used it for a couple of hours. I honestly haven't noticed much difference.. I got rid of all the mtk garbage apps first thing.

I REALLY wish we had kernel source....the thermal throttling is terrible on mine. I have tried .prop tweaks and butchering the thermal config..doesn't really help.

I'm also not the happiest with the touch screen sensitivity/accuracy. I have wasted so many hours looking for something to help with that issue...uhg
[Android General] Michel177:
Update to HI9PRO

So I received an update today .Since I had a TWRP backup ,I went along and tried to install it .

My device restarted into TWRP .It would not start at all into system .I then restored my backup and everything was fine .I downloaded again the update and ,since my device as root ,search for the file .I can not find it .

anybody found a solution ?

Thanks
[Android General] Vihru:
what version?
[Android General] Michel177:
update

000623 release keys 20181115_20181115-2035

313 mB

I tried to fastboot flash the original recovery but I forgot to remove ROOT .I will try eventually....
[Android General] Michel177:
I could not get my system to update even after I replaced boot with the original one as well as the recovery .

So I decided to give phhusson GSI version a try .I use his gsi AOSP 8.1v28 .It seems that everything works quite well .
[Android General] Vihru:
hi9 pro? how you installed it?
[Android General] Michel177:
I had my Chuwi HI9Pro modified to have the rooted boot.img and TWRP installed .I then put the PHHusson 8.1 v28 onto my ext SD .

Then you follow instructions to install GSI i.e. format data ,cache and dalvik .Then you install the system.img using TWRP YOU MUST put the img at system NOT anywhere else .Then reboot .

By the way I also tried phhusson android 9 v110 .It run ok but with some delay .

they are here

https://github.com/phhusson/treble_experimentations/releases
[Android General] nikaiako:
I also installed AOSP 8.1 v.28 on my Chuwi Hi9 pro succesfully a couple of days ago, and it worked quite fine. I took it from here https://github.com/phhusson/treble_experimentations/releases/tag/v28 There is more about it here https://xdaforums.com/project-trebl...-development/experimental-phh-treble-t3709659

I installed it via adb-fastboot using a manual which I found here https://www.xda-developers.com/flash-generic-system-image-project-treble-device/ I was testing the rom for a whole day, and the only problem that i found was that magisk 18.1 coudn't have any modules installed. Every attempt to do so caused the whole system to crash and return to recovery mode. However, magisk 18.1 used to pass the safetynet test completely.

I have to mention here that I don't use twrp at all on my device, and that I tested just system-arm64-aonly-vanilla-nosu version of this aosp rom. I had 20181115 firmware version on my Chuwi when I started installing the aosp.

I posted my report also on a russian forum http://4pda.ru/forum/index.php?s=&showtopic=916841&view=findpost&p=82551546
[Android General] nikaiako:
I am sorry, I just made a mistake stating that. I had no opportunity to check the safetynet test on AOSP, since there were no gapps installed on my Chuwi.

Nevertheless, magisk 18.1 passes the safetynet test on my Chuwi Hi9 pro with the 20181115 firmware quite well.
[Android General] anduril888:
Hello, New to this. I followed the instructions for installing TWRP recovery on my new Hi9 Pro, however when I boot into TWRP recovery the touch is all messed up, most of it responding a few inches below where i press so it is unusable. I tried both twrp images listed in this thread as well as a few other hi9 pro twrp images i found all with the same issue.
[Android General] Infect_Ed:
Works fine for me. The first 5 seconds or so, touch doesn't respond. But as for the mapping I haven't seen that issue. Are you using my twrp?
[Android General] anduril888:
Yes, that is the version I currently have installed from the bottom of the post, https://xdaforums.com/attachment.php?attachmentid=4686842&d=1547538161
[Android General] NikosD:
[MENTION=1980576]zelipukin[/MENTION]

So, it's true.

We have a new official update from Chuwi for Hi9 Pro through "Wireless Update", weighting around ~313 MB, a release date of 15/11/2018 and release notes referring only as "1. Minor bugs"

The message during the installation procedure said that the device will restart in recovery mode and continue the installation from there, after downloading the file and automatically extracting it, so I pressed "Update now".

Unfortunately, I tried to install it using the last state of the device which was rooted, with unlocked bootloader and with custom recovery of TWRP (last version 3.2.3 from Infect_Ed)

The result is that I'm now in a custom recovery (TWRP) boot loop.

I think that the automated installer looked for stock recovery in order to continue installation and not TWRP, that's why it just stops there.

My questions to anyone that can help:

1) Is there a way to continue the installation of the Update via TWRP and avoid the recovery loop ?

2) Is it possible to flash the stock recovery now that I'm in the TWRP boot loop and continue that way the installation ? Will the automated installer see the stock recovery and proceed with the installation ?

3) Is there a way to abort the automated installation by deleting appropriate files from the partition using TWRP file manager and go on the boot process without the update using my previous system ?

How do you suggest to go on ?

Thank you!
[Android General] amg314:
1+2. You may reflash stock recovery.img thru SP Flash tool. If the bootlap disappears, you can try installing the update. If the upgrade fails, you will have to delete the root.

To prevent TWRP bootloop I usually install TWRP and Magisk without rebooting to system:

a. Flash TWRP thru SPFT (Tablet is power off)

b. Push Power+Vol down buttons to reboot to TWRP

c. Install Magisk.zip from External_sd

d. Reboot to System

3. You can switch off OTA updates thru Settings --> System --> Developer Option --> Automatic System updates --> Off))
[Android General] NikosD:
Well, I used SPFlashTool to reflash the stock recovery and after booting the device, it went immediately to system update procedure.

But the progress bar stuck for 10 minutes at the same position, so I powered off the device and tried to delete the root.

My root method is via Magisk and since I'm using stock recovery and I don't have any Magisk uninstaller, I used SPFlashTool again to reflash the stock boot.img file.

Unfortunately, even after going back to original boot.img the progress bar stuck at the same point like the previous state of rooted device for another 10 minutes doing nothing.

What else do I need, besides flashing stock boot.img, in order to delete Magisk root ?

What is the proper way to delete/ uninstall Magisk root without TWRP ?

Any other ideas to proceed with the update installation or avoid it ?

Thanks!
[Android General] amg314:
What is the difference between 'original' and 'stock' boot.img?

The easiest way to uninstall Magisk is to flash following .zip using TWRP or FlashFire:

https://github.com/topjohnwu/Magisk/releases/download/v18.1/Magisk-uninstaller-20190204.zip
[Android General] NikosD:
No difference, just a different word for the same thing.

But in my current status I can't have TWRP, because it's a custom recovery and the automated installation of the Update requires stock recovery.

That's why I got a recovery loop in the first place, because of custom recovery instead of stock.

My TWRP worked perfectly even mounting every partition of the device, since they were decrypted.

The issue here is the update installer which requires stock recovery and it boots automatically in recovery mode.

Probably one way to avoid this situation could be number 3) of my initial questions aka to delete the files of the update that force the automatic installation in stock recovery mode.

But how ?

P.S

I could also revert to TWRP, uninstall properly Magisk and then go back to stock recovery and try again.

But I don't think it will work.
[Android General] amg314:
Use following TotalCommaner search (in /data first):

*.zip --> Size > 20 M --> Not later 2 days (choose right value))

*---------------------------------------------------------------------------*

You may try flash this zip thru adb sideload option in your stock recovery or TWRP.
[Android General] NikosD:
Well, I reflashed TWRP using SPFlashTool and then flashed Magisk unistaller via TWRP and then back to stock recovery via SPFlashTool.

After boot, I have the same picture again:

The device goes immediately to recovery mode and starts installing the update but after a few seconds the progress bar sticks forever at the same point as always.

Now, my question is this:

How on earth could someone install this update besides having a pure stock ROM ?

I mean is the unlocked bootloader the problem or some app is prohibiting the installation ?

Is the only way to install an official Update to go back to stock ROM via a factory reset or using SPFlashTool stock firmware ?

That would be extremely irritating.

There must be another way.

---------- Post added at 04:20 PM ---------- Previous post was at 03:55 PM ----------

I reflashed TWRP and mounted the /sdcard partition to Windows Explorer and didn't find anything.

Also, I mounted every partition I see inside TWRP and using its File Manager I searched almost everything, but didn't find anything useful.

Maybe I don't look at the right places.

I finally did a wipe cache/ dalvik cache from inside TWRP with no result.

It keeps booting at recovery mode trying to install the OTA Update.

I'm out of new ideas right now.
[Android General] Michel177:
updating original system

I am /was with TWRP rooted and with AOSP8.1from PHHUSSON .I wanted to test the new update .Here is how I did it

Under TWRP I install boot-verified.img into the boot partition .

I format data ,dalvik and cache .

I install system.img from the downloaded original OS .

I booted the OS and downloaded the update (313mb) .

I restarted into twrp .I installed recovery-verified.img (from original OS).

Went back to OS and ask to update .

It got stuck at about 25% .After a few restart ,I decided ,since I was going away ,to let it continue to try updating .

When I came back the system was back on .It certainly took more than 30 min .

I did not see any big change .So I went back to AOSP 8.1
[Android General] NikosD:
Well, after wiping cache and dalvik cache I reflashed stock recovery and reboot a few times because initially I got an error when it went to recovery mode.

After second reboot, for unknown reasons, I saw my stock bootanimation logo of Chuwi and not the one that I had before (flashed by me using TWRP long time ago) so I realized that some kind of reset had eventually happened!

Indeed, the system loaded with all my apps and configuration untouched!

And because I'm a little stubborn, I re-downloaded and installed again the OTA update using stock recovery this time and leaving the update unattended.

After approximately 25 minutes, the system was updated to the latest OTA update of 15/11/2018.

I see no visual differences other than the security update which went from 05/06/2018 to 05/10/2018.

But I have a new problem now.

I reflashed Infect_ed's TWRP v3.2.3 using SPFlashTool and this time with my device unrooted, the custom recovery can't see/ mount the partitions due to the encryption.

How can I root the device with Magisk and decrypt the partitions using TWRP, without formatting data ?

I don't have an external SD card.
[Android General] nikaiako:
Well, I think you'd better patch the boot.img from the stock firmware with the magisk manager 7.0, and after that you just flash the patched boot via sp flash tool in a "download only" mode (you should check only one box there, the "boot", without checking "preloader").

Or you can take the patched boot here https://www.dropbox.com/s/axlfc3zw60q8crx/patched.boot.magisk.18.1.for.20181115.img?dl=0

You may install magisk manager 7.0 first, then flash the patched boot, then reload your device, and voila, magisk is there and working.

I used this way of rooting my device with my userdata encripted. (I also do not have twrp installed, just the stock recovery.)
[Android General] NikosD:
I'll definitely grab your patched boot.img and root the device, but I like having a working TWRP capable of mounting the partitions, without wiping my data.

Ok, one step at a time.
[Android General] nikaiako:
This is just to note that you can flash things that you need, i.e. system.img or vendor.img, or both via spft without losing your data. Just do not check the preloader box (and the other boxes you do not need).