yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] martinza:
Bad news. I could decompile framework-res.apk obtaining readable xml files (I changed software for decompile) with xml-editor but I detect our power_profile.xml file is identical as the file power_profile.xml on Cube M3 Power.
[Android Q&A, Help & Troubleshooting] starbright_:
I also found a way to decompile and compile again (apktool). But bad luck - for some reasons I get a bootloop after changing the /system/framework/framework-res.apk. The permissions / chmod has been set properly.

The new created apk is bigger 21MB vs 19MB. Found a few new files like res/values/arrays.xml (don't know where are they come from).

And some xml files are getting smaller !?

Manifest, rescources.arsc, and Meta.inf are identical to the original.

Edit:

Ok, that was not compiled properly. I used apk manager and now it worked - or better said it is booting again. I just changed battery to 6500 - nothing else. I am courious how it will change the behaviour. As described my problem is, that device shuts down with "0%" but with 3.xxx V - to early imho.
[Android Q&A, Help & Troubleshooting] rauliordache:
Hello.

[MENTION=2492996]starbright_[/MENTION]

Firstly, you need to install the framework. For obtaining a readable xml file, I am using APKTOOL or APK Easy Tool.

Power_profile file isn't good at any chinese provider... They are "same" because it's the default file (posted by the Android Team!). This file should be modified by each firm....

Thanks to user Tehnik_970 from 4pda, we have a modified power_profile.xml

<?xml version="1.0" encoding="utf-8"?>
<device name="Android">
<item name="none">0</item>
<item name="screen.on">100</item>
<item name="screen.full">200</item>
<item name="bluetooth.active">15</item>
<item name="bluetooth.on">5</item>
<item name="wifi.on">5</item>
<item name="wifi.active">200</item>
<item name="wifi.scan">100</item>
<item name="dsp.audio">15</item>
<item name="dsp.video">60</item>
<item name="camera.flashlight">300</item>
<item name="camera.avg">600</item>
<item name="radio.active">250</item>
<item name="radio.scanning">3</item>
<item name="gps.on">55</item>
<array name="radio.on">
<value>2</value>
<value>1</value>
</array>
<item name="modem.controller.idle">0</item>
<item name="modem.controller.rx">0</item>
<item name="modem.controller.tx">0</item>
<item name="modem.controller.voltage">0</item>
<array name="cpu.clusters.cores">
<value>2</value>
<value>2</value>
</array>
<array name="cpu.speeds.cluster0">
<value>299000</value>
<value>442000</value>
<value>598000</value>
<value>819000</value>
<value>1040000</value>
<value>1144000</value>
<value>1235000</value>
<value>1300000</value>
</array>
<array name="cpu.speeds.cluster1">
<value>299000</value>
<value>442000</value>
<value>598000</value>
<value>819000</value>
</array>
<array name="cpu.active.cluster0">
<value>25</value>
<value>48</value>
<value>85</value>
<value>104</value>
</array>
<item name="cpu.idle">10</item>
<array name="cpu.active.cluster1">
<value>25</value>
<value>48</value>
<value>85</value>
<value>104</value>
<value>144</value>
<value>183</value>
<value>228</value>
<value>315</value>
</array>
<item name="cpu.idle">10</item>

<item name="battery.capacity">3500</item>
<item name="wifi.controller.idle">0</item>
<item name="wifi.controller.rx">0</item>
<item name="wifi.controller.tx">0</item>
<array name="wifi.controller.tx_levels" />
<item name="wifi.controller.voltage">0</item>
<array name="wifi.batchedscan">
<value>.2</value>
<value>2</value>
<value>20</value>
<value>200</value>
<value>500</value>
</array>
</device>

By the way, Tehnik have changed the battery itself (with an 8000mAh, at 10-15$), and everything is ok. (Linear discharge from 100-0). So, again, we are thinking that the default battery controller (or maybe the battery itself) is broken...

Anyway, even if there is a faulty battery or not, and even if after replacing with a newer battery everything is "ok", the power_profile.xml should NOT be the same as the one posted on the Android website (because that is just a template !!!).

The interesting part is that, after replacing the battery, everything is good with the default power_profile .... Which is strange....
[Android Q&A, Help & Troubleshooting] starbright_:
Thanks for the info.

Thinking about it I guess that power_profile is less important for the actual % value but for the estimation for usage time ...

Also I found that it seems to be a security feature to switch of the device even at >3.5V. Don't think this is really required. Somewhere I found howto change that.
[Android Q&A, Help & Troubleshooting] rauliordache:
I think I'll try to buy another battery (10-15$ it's okay). I'll lose the warranty, but I'm in the second year, so ....

Now I am using in the 100-40% interval (with a little help from the Voltage level). More important (for me), is the update to Android 8.0 (according to the manufacturer, as I have received an answer on email, in the next months).

The actual Android 7.0 is "good", but it could be better...

PS. Before changing the battery, Tehnik user have changed the power_profile (with the upper version). He had a linear discharge from 75% to 0%. But the max % was 75. All in all, everything is ok (as I have spoken with him), after changing the batt.
[Android Q&A, Help & Troubleshooting] starbright_:
Warranty? Where did you ordered it to get 2y warranty? Imho this is only to get via chinese traders ....

If you have a source for the battery and has been successful with changing, let us know.

Regarding the 75% max. If I charge it stucks to 85% although Voltage is 4.3V. But after unplug/plug power again and reboot it finally switches to 100%.

For me best would be to replace battery% by battery V.

Regarding the power_profile: I think I know why this is required. If you look at a discharge diagram you'l found the voltage is almost constant for a longer time - around 3.8 and 3.6V. (https://androidforums.com/threads/low-battery-shut-off-voltage.468076/)

The voltage you measure depends more on the actual load than on discharge state.

Maybe the power consumption values are used to calculate current load situation and estimate the power state.

Power in % = f(current Voltage, current load)

Do you know why Tehnik states battery to have just 3500mAh? Isn't it 6500?

Do we really have 2 clusters of processors? Imho this are 8 cores, but all are same.

You can find 2 power_profiles for our chipset here:

https://github.com/Deepflex/MokeeOS...works/base/core/res/res/xml/power_profile.xml

and here:

https://github.com/Deepflex/MokeeOS...works/base/core/res/res/xml/power_profile.xml

It would be a huge surprise if we get an update to Android 8/Oreo. But never say never.

At least there is an Oreo release for an existing device with same chipset:

https://xdaforums.com/android/development/rom-official-mados-ulefone-metal-t3709342

After it takes me a day to decompile and compile framework-res.apk I am wondering what can I do with this knowledge.

My modifications right now has been done outside:

- replace Launcher by Nova Launcher

- use an app "Custom Navigation Bar" to get rid of camera button

- use an app to tweak the minimal display brightness to an even lower value
[Android Q&A, Help & Troubleshooting] martinza:
He said that the battery charge up to 70%. I think 70% (3500) -> 100% (5000)... so perhaps the battery max charge is 5000mA. Today I'm going to change my power_profile.xml and comment results in the next days after 2-3 full charge cycles.
[Android Q&A, Help & Troubleshooting] starbright_:
I am wondering, why browsing in internet is often so slow. Hey man, its an 8 core A53! Is maybe Wifi modul, graphic processor or RAM the limit?

This is not really clear to me.
[Android Q&A, Help & Troubleshooting] rauliordache:
This is the problem!

For me, after updating to Android 7.0, I have always GPU load 0%. So every graphic entity is created via CPU.....

I want to ask you guys if you have this problem too. Run separately a movie, game,etc and CPU-Z. What is your GPU load?

Also, please mention if you have the stock Android 7.0, or updated from 5.1 (or even 5.1 itself):)
[Android Q&A, Help & Troubleshooting] starbright_:
[MENTION=8550794]rauliordache[/MENTION]:

I also have a originally Android7 device. GPU shows always "0".

Browsing in internet can make all 8 CPUs busy. Watching a movie make 1 or 2 cores busy. For decoding is a special hardware in the SOC, so this is not done by CPU.
[Android Q&A, Help & Troubleshooting] rauliordache:
It's true. But it's not ok to have GPU load 0% every time. Sometimes maybe it's a must to use the GPU.... (games, FHD videos). Try to run in parallel a FHD video + a CPU load worker: idk ...let's say browsing. You will lose performance in both tasks because, normally, the GPU should render the video and CPU the browser.

It's the same as the tablet has no GPU...... Or a laptop without a dedicated graphic card....
[Android Q&A, Help & Troubleshooting] starbright_:
Sure, GPU should do something.

Are you sure that CPUz shows GPU usage reliable? Hope a few other users (with original Android 6) can test this.

Any hints in dmesg?

BTW: Its hard do see the load, as it doesn't run in backgroud. Is there something better which creates a load diagram over last time?

Edit: In the developer section of settings you can check some GPU settings. Do you see differences after clicking around? I am wondering what are the original setting of Force GPU Rendering and deaktivate HW Overlays ? checked or unchecked?
[Android Q&A, Help & Troubleshooting] 1testi:
That's the problem of any monitoring app. I never found a screenshot of CPU-Z for android showing anything else than 0% GPU usage. Happens in all versions of android, because CPU-Z messures the GPU

the moment it is running. Same as Antutu, you will never have two identical results on the same phone, doesn't matter how often you run it.
[Android Q&A, Help & Troubleshooting] starbright_:
I think GPU is running. Plese check the developer settings, you can overlay the load of the GPU.
[Android Q&A, Help & Troubleshooting] 1testi:
The moment CPU-Z makes its messures it messures its own load of the GPU .... and that is 0%, doesn't matter what is set in developer

options.
[Android Q&A, Help & Troubleshooting] starbright_:
Sorry, I mean you can configure it to show GPU load in dev-settings. As a proof that GPU is doing something.

It is under surveillance, GPU rendering for profile (or simular).
[Android Q&A, Help & Troubleshooting] rauliordache:
Nope. Any settings in Dev-Ops - ON. But always 0% (here). Showing the GPU Load - ON, but it doesn't seem to show a load ...

Force GPU rendering ... ON

Force OpenGL ... ON, etc.

So I am not sure if the GPU is working, but the CPU-Z doesn't show that, or the GPU isn't really working.
[Android Q&A, Help & Troubleshooting] 1testi:
That's simply an "error" with CPU-Z, same as many other monitoring tools has also.

The GPU is running for sure or it wounldn't be possible to run any graphical game. Simply try Antutu to see how good the Mali is.
[Android Q&A, Help & Troubleshooting] starbright_:
Again:

You can configure it to show GPU load in dev-settings. As a proof that GPU is doing something.

It is under surveillance (translated, so maybe not exactly this word), "GPU rendering for profile" (or simular).

What is progress with power_profile.xml?
[Android Q&A, Help & Troubleshooting] martinza:
Where could I download the last TWRP version (3.2.1) for Voyo Q101?

(I'd like to try to install Lineage or RR for Lenovo K4 Note -uses same SoC tan our Voyo-).
[Android Q&A, Help & Troubleshooting] starbright_:
Look for a bricked Voyo Q101. Or a screen glass as a spare part.

My one is broken :(

Someone knows how to replace it?
[Android Q&A, Help & Troubleshooting] martinza:
Official new reléase!!!!

Tomorrow i'll check it.

http://en.myvoyo.com/xiazai/Win Pad/VOYO_Q101/down/
[Android Q&A, Help & Troubleshooting] martinza:
Arggggg... same files!!! same sizes!!! same dates!!! grgrgr
[Android Q&A, Help & Troubleshooting] starbright_:
So typical !
[Android Q&A, Help & Troubleshooting] starbright_:
Get rid of orange state and timeout

What is the best way to get rid of this orange state and especially the timeout ....

The lpk files is not longer available.
[Android Q&A, Help & Troubleshooting] starbright_:
Help!

I had done OEM unlock und flashed the TWRP recovery.

Followd by the supersu-zip.

Now it boots only to TWRP, but not into Android. ItÄs a kind of bootloop into TWRP.

How can I come to boot Android again?

---

Edit:

Could managed that by SP-Flash-Tool:

- Downloaded SP-Flash Tool: https://spflashtool.com/

- Downloaded Voyo FW and unzipped it.

Started Flash-Tool, goto Tab "Download" and selected the scatter file out of the unzipped FW.

Select Firmware Upgrade and started "Download".

Bring the device into Fastboot/Bootloader mode (which I did out of the TWRP).

What I still not understand, what I did wong. Repeated the steps mentioned here:

https://xdaforums.com/showpost.php?p=75136661&postcount=285

But still come into a TRWP bootloop.

but can't boot into android? Not sure what is happened.
[Android Q&A, Help & Troubleshooting] starbright_:
I did reflash firmware with SP-Flash-Tool and changed the recover by the TWRP.

That seems to work.

But after wiping data or even internal sdcard the device doesn't behave.

Either I get the blue start screen (with orange state) or I bootloop to TWRP.

What might be the reason?
[Android Q&A, Help & Troubleshooting] starbright_:
For today I give up. I locked the bootloader, flashed the original FW by SP-Flash tool and did all the steps:

- boot into Android

- enable developer section

- enabled OEM unlock

- enable ADB

- plugged USB cable

- started cmd-shell at PC

- adb devices

- adb reboot bootloader

- fastboot oem unlock

- enable unlock with yes at tablet

- fastboot flash recovery voyo_twrp3_1_1_0_recovery from_jemmini.img

- fastboot reboot

(don't know exactly but boot into TWRP)

- in TWRP:

- select language

- cancel (as I don't know password)

- wipe - extenden - data

- enable adb sideload

- adb sideload failed ???? (falling back to older method, no device found ?!?)

- installed SR5-supersu from external sd-card

- restart boots into TWRP !!!! (instead of announced few reboots .....)

(it doesn't complain anymore about encryption, but that doesn't help me much if I can't boot the system).

HELP!!!

--

I have a full TWRP from anothe Android7 Voyo, which I could try to recover in this device. But there are so many partitions. Don't know which to select and which not.

I tried with the last few partitions system/system install/ data ..

But I get a crash while recovering system install and a tar error while recovering data.

Does my tablet has hardware issues or is the partition scheme changed?
[Android Q&A, Help & Troubleshooting] 1testi:
I' ve read it several times now and i have still no clue, what do you try to achieve.

You fear a hardware issue, why? After flashing with SP-Flash it is booting into android properly, right?

So what do you want to do next? What's your goal?
[Android Q&A, Help & Troubleshooting] starbright_:
Two goals:

Install Twrp and root

Install with twrp the image I created with another voyo, so that I dont have to installiert all from scratch.

Can install TWRP, but can not bootAndroid than

--- Edit ----

Get it working with a complete different approch via SP-Flash-Tool.

Download the Original Voyo FW from their website. Unpack just the scatter file into a empty folder.

Add the recovery.img (with TWRP) into this fold

Start SP-Flash-Tool, Select Download-Tab

Open the scatter file. Press Download button.

Boot tablet into fastboot/bootloader mode.

After that, boot into recovery

Wipe data, install SR5-SuperSu.

Done ! No annoying "Orange State"

I also could restore the backup (system and data) from a second Voyo! :)
[Android Q&A, Help & Troubleshooting] 1testi:
Great you did it.

To replace the recovery.img from the ROM with a TWRP of your choice and flash it with SPF is the best way.
[Android Q&A, Help & Troubleshooting] starbright_:
Couldn't see that way here in this forum
[Android Q&A, Help & Troubleshooting] starbright_:
I didn't noticed that at that time, but working with the SP-Flash-Tool (especially format) destroyed my EMEI, so I can't use in with mobile data plan. I found that manual and it works! Thanks Ben!!

[MENTION=8550794]rauliordache[/MENTION]

Have you been successful with new battery and power-profile?

With the original I just see Display, WLAN and Standby mode as load.
[Android Q&A, Help & Troubleshooting] rauliordache:
[MENTION=2492996]starbright_[/MENTION]

Sorry for the delay. I haven't changed my battery yet .... but I encountered a problem with the GPS. I will detail.

About your IMEI problem - you should never use format option (in SPFT) in order to flash a ROM. Instead, use firmware upgrade. I always use this option when I want a "clean" install on my VOYO :). And I didn't lose the IMEI (which is possible, when formatting NVRAM partition)

GPS Problem

Scenario:

Firstly, we need to get the "GPS Locker" app from Store, in order to get our "real-time" no. of satellites in the notification bar.

Secondly, we need to install Waze and Google Maps (two navi apps, well known in Europe ans US) - in order to do the test.

1. We are turning on the Location. We can choose any option from "Device only (GPS module only)", "High accuracy". The following problem occurs in both situations. Let's choose Device only.

2. Open GPS Locker and get a lock. Very fast, I get a lock in 3-5 seconds (outside) and 10-15 seconds (inside a building).

No. of satellites: 15/17, 16/17, sometimes 18/20. So, no problem with the antenna or other stuff ... Okaaay.

Now, 3. Open Waze or Google Maps and, in the next second (immediately) slide down the notification bar (in order to see the GPS Locker status).

We can see that the no. of satellites decreases drastically, sometimes till 0/20 satelittes ! So, we have no GPS in navi apps. This is the problem I want to emphasize.

Very good reception in GPS status apps (like GPS Locker, GPS test, etc.), but when opening Waze or Google Maps we have a huge drop in the number of satellites available.

Sometimes, it goes down till 0, and after 10-15 seconds fluctuates between 3-4-5-6 satellites, then suddenly back to 0, etc., etc.

Have you / Do you encountere(d) this problem?

PS. LOL. If I do some "action" (like sliding down-and-up, down-and-up the notification area for 10-15 sec - like a crazy man), I am also losing the satellites .... (GPS Locker shows 10-8-5-3 and then 0/19) ..... Very strange ...
[Android Q&A, Help & Troubleshooting] starbright_:
I guess you mix up 2 things:

Sat's which are seen and sat's which are used to calc the position. That makes a huge difference. As for instance some device firmware doesn't use russian satellites, most don't use chinese. Just this is a dramatically dropdown. Some GPS tools show it like 5/20 - that meens it uses five but found 20 satellites.
[Android Q&A, Help & Troubleshooting] rauliordache:
No no, you don't understand.

GPS Locker shows all sats (in our case: GPS + GLONASS). So, after getting a lock, we know the no. of sats used to get the location.

The problem occurs when entering in an app. Any app (I have seen these days). Even if it's a navi app (Waze, Google Maps), or another app (SopCast, VLC), the no. of sats (which should be "constant" - don't take this word literally) goes down.

I will try to make a video. The idea is that, there is an interference between GPS module and firmware. I think.

You can try too. Get GPS Locker from Store, and get a lock. Wait for +14 sats. In parallel, open Waze, and immediately (next second), slide down the notification bar (which should contain the GPS Lock status).

There is no problem in Samsung S6 and S7 for example. You can play how much you want with any app, but GPS no. of sats will be "constant" (+/- 1/2 sats. No drops from 14 to 0 ..).
[Android Q&A, Help & Troubleshooting] haseka:
Hello everyone,

can someone point me to some recommendable glossy screen protectors made of glass, not plastic? Preferably from one of the usual suspects like aliexpress or gearbest etc.

Also I want to replace the built in battery with a battery with more capacity.

Any recommendations for that?

Many thanks in advance :)
[Android Q&A, Help & Troubleshooting] bsoplinger:
I'm pulling my hair out at this point trying to update this tablet to just the plain non-rooted Android 7 image from the VOYO website. I figured that if I got that right I could then try the rooted image...

But I can't get my Windows 10 tablet to install the MTK drivers. I have the tablet in test mode but I'm still getting red X after the installer tells me the driver is i signed. I'm on the current version of Windows so it's Anniversary edition+ which has the whole unsigned driver issue. Do I really need to dig up a USB keyboard and turn off boot mode (don't remember what the special name is) and turn off driver verification just to install it?
[Android Q&A, Help & Troubleshooting] chan200606:
I upgraded from (fake) 6.0 to the latest 7.0 using firmware upgrade in SPFT and I still lose my IMEI. I suspect that's inevitable as the partition table has changed between the two versions hence the NV data will always get lost.

Unfortunately, the SNwriter tool method doesn't work for me - the tool does detect the preloader but then will always time-out trying to detect the kernel port. Luckily for me, I did make a TWRP backup of the 6.0 ROM before upgrading. Restoring the NVRAM and NVDATA partitions from that backup gets me back my IMEI.
[Android Q&A, Help & Troubleshooting] starbright_:
I tried that with Mapfactor, another offline Navigation app. I can't observe a dropdown of "used sats".

And til now I never had 14 sats in use.

At the beginning I thought it just uses GPS, but once (only for a short time) I have seen a single Glonass sat it use.

Again: In use, not in view!
[Android Q&A, Help & Troubleshooting] rauliordache:
Hmm it's strange because I also have not problems with offline navi (I've tried iGO Nextgen). I saw this in the last days ....

Have you tried with an online navi (Waze) ? I always have problems with Waze. If you want to try, immediately after "clicking" on Waze icon, drop down the notification area (with GPS Locker opened). Do you see something about no. of sats?

LE. I have a video posted. No problems in IGO. Problems with Waze+Google Maps ..

https://www.youtube.com/watch?v=seN0nFOzJ-w&feature=youtu.be

Very interesting ... I have flashed 3 or 4 times (with Firmware Upgrade mode) and I still got the IMEI (I'm using the phone + 3G mobile data)
[Android Q&A, Help & Troubleshooting] chan200606:
So you change rom versions (6 to 7 or back) 3 or 4 times without losing IMEI?
[Android Q&A, Help & Troubleshooting] xloupas:
I have recently bought an oem tablet with the same specs as voyo q101 identical except from ram which is 4gb and storage which is 64gb i was wondering if i can flash the firmware of q101 voyo that is android 7 rather than the android 6 that has now any help and directions from anyone will be very helpfull.

P.S There is no back up rom if i am going to attempt to flash the voyo q101 firmware so i guess is oneway street.

I attached and some photos

http://prntscr.com/kfbshh

http://prntscr.com/kfbtbr

http://prntscr.com/kfbtws
[Android Q&A, Help & Troubleshooting] 1testi:
You used "format all", that's the culprit. Don't do that ever. You don't need it.

"download" is the right option for the most operation.

Only if there is a big change, eg different partion layout, you use "firmware upgrade"

.