Related
UPDATE 8/24! Please go to the site and download the latest version RC1b which corrects 2 small bugs people have reported. It now sets the proper permissions on batt-diag so it runs, and it changes the way the program tries to SU so that you can choose to not have the program attempt to run SU if your rom has trouble running su from terminal;
---Original Below---
I decided to create a new forum for the latest battery tweak as so much has changed since the initial versions.
To get things started, I'll just say that collin_ph battery tweak is a collection of scripts designed to make the hero (for now) last longer on battery, run faster, and run better. The tweak includes CPU management, Battery Management, Disk Performance Boost, Scheduler Boost, LED Fix, Audio Quality boost and other features to improve the usability of your Hero.
Instructions: Go to http://www.primoweb.com/froyo to download the latest version and get the documentation.
Boot into recovery and flash the zip file.
After reboot, you may run batt-cfg from shell or terminal (Note, that the scripts will all request root access, so there's no longer a need to su before running them).
to run batt-cfg
go to terminal in the phone or use adb shell from your PC
once there, type
batt-cfg
It will pull up a menu of choices. For further info, see http://www.primoweb.com/froyo
You can load a 691 mhz default (most Cyanogen kernels now only support up to 691 mhz anyway), or, if you have an uncapped kernel, you can choose a 768 mhz setting. Note: Both settings actually run at 691 when on battery and only run higher when plugged in.
The basics of how the battery is extended is that this tweak causes your phone to scale down (to lower frequencies) faster and to scale up slower. In stock configuration, the cpu scales up when only under 70% load -- while part of this tweak causes it not to scale until it's at 95% load, avoiding unnecessary scaling and battery drain. A second (and arguably more important) feature, is that as the battery drains, it lowers the maxumum CPU frequency. So when you have 1% battery left, you may be running at 468mhz instead of 691. Another plus is that the phone runs in a "higher performance" mode while charging via AC, and another mode to make sure the phone is actually charging when connected bia USB, in addition to the settings mentioned above when the phone is on battery.The best part is that almost every parameter in the system is adjustable through terminal or adb shell using a program called batt-cfg -- just run it and you'll be presented with a menu of options.
I'm constantly updating the documentation, so please check back often as I'll update this thread until there's a final 3.0 version. We're already working on a 4.0 which will be available on the market. We'll post more info there as it happens at www.tweaktool.com
COMPATIBILITY NOTES:
This tweak only works with clockable kernels. A lot of ROMS have reclockable or overclockable kernels which should work. I recommend Froyo roms, but I have heard of the tweak running with 2.1 releases. The main incompatibility seems to be with the service startup-- on some roms, the service doesn't automatically start up.
to verify if your rom is compatible and that the tweak is working, reboot.
Then go to terminal or adb shell and type:
pidof batt.sh
if it returns a number, then the service is running. If not, you'll have to start it manually every time the phone reboots by going to terminal or adb shell and typing
batt-cfg
then choose the option to save and exit. This will manually start or restart the service. Note: if your rom does not start the service automatically, you'll have to do the above batt-cfg procedure after EVERY boot or battery tweak will not run.
If you're a ROM developer, you'll can probably make your ROM compatible by adjusting your rom (ramdisk) to call (import) /system/etc/init.local.rc from init.rc -- assuming your ROM has an overclockable kernel like fresh, darch, or others.
ROMS based on unclockable kernels like Damage Control, won't work without a kernel upgrade and may still not start the service automatically upon reboot.
Thanks to Decad3nce for testing and improving several parts of the battery tweak.
So to flash this tweak and have it working on the latest Froyo nightly, do we need to flash overclockfix.zip ??
I had to flash this fix almost with ever nightly, coz the frequency list would not show up when i need to customize tweak settings.
I was reading the documentation and saw the CFS tweaks are disabled by default. Will this correct the GPS issue that was on beta 10?
Froyo Hero to the rescue
Thank you for all your work on this, got 12 hrs on 50% today with beta 10 and Decad3nse #8, 768 pre-set, most time I've ever gotten outa my Hero. Flashed your RC1 (with Darch's RC1) about 45mn ago and used custom settings to jack-up the max to 768 across the board, min.s and intervals stock. Thank you for explaining the 768 pre-set is really 691! Gonna sit on what I've got for a day and then try w/ Darch's "fix" kernel. Hope I can keep the max on batt @ 768 'cause it seems to make my Hero more responsive/less laggy.
I was not able to use the batt-diag in adb shell. I'll report back tomorrow how the tests go.
What is the procedure for installing this if you're currently running Beta 10? Do you have to wipe, reflash, etc or can you just flash the update and reconfigure in adb?
it made my hero laggy!!!
ToxicToastKatz said:
What is the procedure for installing this if you're currently running Beta 10? Do you have to wipe, reflash, etc or can you just flash the update and reconfigure in adb?
Click to expand...
Click to collapse
Follow the uninstall steps form the documentation
How do I uninstall it?
adb shell
batt-rm.sh
Follow the prompts and the tweak will be uninstalled.
Click to expand...
Click to collapse
Then flash the new version, this is how I have been doing it.
Excellent tweak! Used it through Beta and now enjoying the RC. Well done!
wow.. the way things are going i don't think i am going to jump into a evo... i am loving my hero so much.... thank you for all your hard work..
OK I don't know if its just me but when I go into batt-cfg it just runs whoami uid o
Batt-cfg root
Or something like that over and over again. It worked on beta 10 but not like this I don't understand
8/22 RC1 update does not have a working batt-diag, says not found. I am getting "89" when I do "pidof batt.sh"
imb951 said:
8/22 RC1 update does not have a working batt-diag, says not found. I am getting "89" when I do "pidof batt.sh"
Click to expand...
Click to collapse
Thanks for the notes on batt-diag. I'll look into it and release a fix this evening. Thanks.
Papa Smurf151 said:
OK I don't know if its just me but when I go into batt-cfg it just runs whoami uid o
Batt-cfg root
Or something like that over and over again. It worked on beta 10 but not like this I don't understand
Click to expand...
Click to collapse
hmm.. what rom are you running? It sounds like the code I've got in to detect root (and ask for it if necessary) is causing an issue with what you're running. All it does is a whoami to see if you are logged in as root, if not, it su's and relaunches itself.
I'm getting the same root problem with 8/22 nightly.
Sent from my HERO200 using XDA App
Papa Smurf151 said:
OK I don't know if its just me but when I go into batt-cfg it just runs whoami uid o
Batt-cfg root
Or something like that over and over again. It worked on beta 10 but not like this I don't understand
Click to expand...
Click to collapse
hmm.. what rom are you running? It sounds like the code I've got in to detect root (and ask for it if necessary) is causing an issue with what you're running. All it does is a whoami to see if you are logged in as root, if not, it su's and relaunches itself.
collin_ph said:
hmm.. what rom are you running? It sounds like the code I've got in to detect root (and ask for it if necessary) is causing an issue with what you're running. All it does is a whoami to see if you are logged in as root, if not, it su's and relaunches itself.
Click to expand...
Click to collapse
I'm using my red dawn rom with a modded ramdisk to allow for the battery tweak. The beta 10 worked and even the rc1 asked for su and I said allow the the whoami just kept going and going. I uninstalled via ur instructions on ur site and flashed again and same results
RC1 kept crashing my phone. Right after saving settings it would freeze them hard reset and get stuck at the htc screen. I've reverted back to beta 10. The only problem I've ever had with beta 10 is I would have random hard resets when charging. I really can't even pin point it on this tweak but its the only thing that I could think that would do it.
zachslavin said:
RC1 kept crashing my phone. Right after saving settings it would freeze them hard reset and get stuck at the htc screen. I've reverted back to beta 10. The only problem I've ever had with beta 10 is I would have random hard resets when charging. I really can't even pin point it on this tweak but its the only thing that I could think that would do it.
Click to expand...
Click to collapse
Were you doing the updates through ADB or terminal? When would it hard lock up.. during save changes?
CFS Tweaks and Decad3nce Kernel
I understand from reading the Kernel info, that the CFS on this tweak needs to be disabled first....did you make CFS tweaks on by default? Arent we supposed to flash the kernel first, then disable cfs tweaks and reboot? Im confused as to the order in which things are flashed. WIPE, ROM, GSHITZ, BLACKMOD, KERNEL#7, COLLINS RC1. Then go to term EMU and disable CFS, then save then go back into batt-cfg and choose option 1 768 and save and exit then reboot. Woudl that be correct?
Q&A for [ROM] [Xoom] [4.4.4] TeamEOS - The Revival || Nightlies
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] [Xoom] [4.4.4] TeamEOS - The Revival || Nightlies. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
[ROM] [Xoom] [4.4.4] TeamEOS - The Revival
Hi, i installed EOS 4 on my XOOM 3G Version earlier i was using EOS 3 and on that time every thins was ok, but now i am facing mobile network cutoff issue. before network cutoff i am getting following massage, " Unfortunately, the process com.android.phone has stopped".
Installed Version : EOS-full_everest-20141030.112337.zip
Below is the attachment of the error.
Kindly help
please support me to resolve this issue.
eos4
Hi, i installed EOS 4 on my XOOM 3G Version earlier i was using EOS 3 and on that time every thins was ok, but now i am facing mobile network cutoff issue. before network cutoff i am getting following massage, " Unfortunately, the process com.android.phone has stopped".
Installed Version : EOS-full_everest-20141030.112337.zip
Below is the attachment of the error.
Kindly help
Xoom 4GB HK Partition
Hi all
I own a Xoom HK version, now up and running 4.4.4.
Can't seem to find a fix for the issue, but I know that this works for EOS 2 and 3.
If someone can help me with what needs to be done (I am learning albeit slowly about Android internals), I can test it on my Xoom and hopefully provide the patch back to the community
Hi all,
I' ve installed EOS-full_everest-20141110.083307.zip and was thinking everything was fine.
I' ve used chrome and sometimes it hangs. Thinking the problem was in flashplayer I've removed it and tried again, but no luck on this.
I've then installed ElementalX-Xoom-2.1.zip and things was a little better, but chrome still freeze.
I've noticed that when chrome die, the cpu remain high ( up to 10, as load value using the EOS cpu indicator in status bar ) and the first process shown is still com.android.chrome.
I've installed the Dolphin and I had 12 hours of working until the next hang.
After rebooting I connected via adb and have seen this in last_kmsg:
Code:
[10896.104646] CPU1 is up
[10896.109888] PM: early resume of devices complete after 4.951 msecs
[10896.112106] tegra_grhost tegra_grhost: resuming
[10896.112429] tegra_grhost tegra_grhost: resumed
[10896.113095] spdif_set_sample_rate: spdif_clk rate 5644800
[10896.113367] tegra_avp_resume()+
[10896.113722] tegra_avp_resume()-
[10896.114255] tegradc tegradc.0: resume
[10896.114521] tegradc tegradc.1: resume
[10896.479928] PM: resume of devices complete after 369.079 msecs
[10896.481152] Restarting tasks ... done.
[10896.500903] suspend: exit suspend, ret = 0 (2014-11-14 13:36:57.592991000 UTC)
[10897.673738] select 24797 (m.android.email), adj 15, size 7804, to kill
[10897.673823] send sigkill to 24797 (m.android.email), adj 15, size 7804
[10897.673862] select 24797 (m.android.email), adj 15, size 7804, to kill
[10897.673871] send sigkill to 24797 (m.android.email), adj 15, size 7804
[10898.246179] wake lock wlan_rx_wake, expired
[10898.276521] suspend: enter suspend
[10898.276717] PM: Syncing filesystems ... done.
[10898.278696] Tegra cpufreq suspend: setting frequency to 216000 kHz
[10898.280803] Freezing user space processes ... (elapsed 0.03 seconds) done.
[10898.317282] Freezing remaining freezable tasks ...
[10898.816821] active wake lock wlan_wake
[10898.817449]
[10898.817821] Freezing of tasks aborted
[10898.819660]
[10898.820237] Restarting tasks ... done.
[10898.834487] suspend: exit suspend, ret = -16 (2014-11-14 13:36:59.926574001 UTC)
[10899.816176] wake lock wlan_rx_wake, expired
[10899.819815] suspend: enter suspend
[10899.820013] PM: Syncing filesystems ... done.
[10899.822260] Tegra cpufreq suspend: setting frequency to 216000 kHz
[10899.824257] Freezing user space processes ... (elapsed 0.02 seconds) done.
[10899.854565] Freezing remaining freezable tasks ...
[10905.354917] active wake lock wlan_wd_wake
[10905.355641] active wake lock wlan_wake
[10898.817821] Freezing of tasks aborted
[10898.819660]
[10898.820237] Restarting tasks ... done.
[10898.834487] suspend: exit suspend, ret = -16 (2014-11-14 13:36:59.926574001 UTC)
[10899.816176] wake lock wlan_rx_wake, expired
[10899.819815] suspend: enter suspend
[10899.820013] PM: Syncing filesystems ... done.
[10899.822260] Tegra cpufreq suspend: setting frequency to 216000 kHz
[10899.824257] Freezing user space processes ... (elapsed 0.02 seconds) done.
[10899.854565] Freezing remaining freezable tasks ...
[10905.354917] active wake lock wlan_wd_wake
[10905.355641] active wake lock wlan_wake
[10905.355999]
[10905.356385] Freezing of tasks aborted
[10905.356831] kswapd0 D c062e5a8 0 23 2 0x00080000
[10905.357902] [<c062e5a8>] (schedule+0x210/0x930) from [<c062f400>] (schedule_timeout+0x208/0x2c0)
[10905.358408] [<c062f400>] (schedule_timeout+0x208/0x2c0) from [<c062df2c>] (wait_for_common+0xa4/0x1cc)
[10905.358939] [<c062df2c>] (wait_for_common+0xa4/0x1cc) from [<c008e36c>] (schedule_on_each_cpu+0x104/0x134)
[10905.359471] [<c008e36c>] (schedule_on_each_cpu+0x104/0x134) from [<c0101024>] (compact_nodes+0x14/0x1cc)
[10905.359785] [<c0101024>] (compact_nodes+0x14/0x1cc) from [<c0495630>] (lowmem_shrink+0x2b8/0x354)
[10905.360291] [<c0495630>] (lowmem_shrink+0x2b8/0x354) from [<c00d8b70>] (shrink_slab+0x168/0x1f8)
[10905.360796] [<c00d8b70>] (shrink_slab+0x168/0x1f8) from [<c00db24c>] (kswapd+0x744/0xca8)
[10905.361300] [<c00db24c>] (kswapd+0x744/0xca8) from [<c0092698>] (kthread+0x80/0x88)
[10905.361620] [<c0092698>] (kthread+0x80/0x88) from [<c003d448>] (kernel_thread_exit+0x0/0x8)
[10905.363131]
[10905.363380] Restarting tasks ... done.
[10905.379481] suspend: exit suspend, ret = -16 (2014-11-14 13:37:06.471571000 UTC)
[10905.382592] suspend: enter suspend
after this there is a lot of:
Code:
[17343.633736] x=947 y=1040
[17343.718972] x=899 y=1074
[17343.724346] x=860 y=1092
[17343.733179] x=830 y=1101
[17343.742014] x=806 y=1108
[17343.750832] x=789 y=1113
...
...
...
[17388.580375] select 23235 (ndroid.exchange), adj 15, size 7006, to kill
[17388.580491] select 23701 (id.gms.wearable), adj 15, size 7055, to kill
[17388.580555] select 24925 (lutions.Meteo3b), adj 15, size 7340, to kill
[17388.580660] select 24971 (facebook.katana), adj 15, size 15358, to kill
[17388.580727] send sigkill to 24971 (facebook.katana), adj 15, size 15358
and at the very end
Code:
[17678.720483] x=89 y=124
[17678.720679] x=89 y=124 time=1733001
[17679.720397] x=62 y=100
[17679.720613] x=62 y=100 time=1733101
[17692.323590] Hard reset buttons pushed
Can this be usefull ?
Unfortunally I need to use my XOOM so I would revert to EOS 4.0 nightly ( crossing fingers )....
That's sad as when it's working, it's very fast and nice.
Pigi
I have the following problems:
Google maps will not run
Chrome hangs and freezes
BBC iplayer starts to play and then freezes
I downloaded and installed the latest rom from your link in the forum yesterday. I installed the full current pa gapps package from your link in the forum yesterday as well.
I also tried loading the CM11 big part and the omnirom big part roms with the same gapps.
Both seem to have the same problem which suggest to me that the issue is with gapps.
I have tried uninstalling updates in google play but the problem persists.
Thanks for all the hard work that you put into this rom. I am a newcomer to flashing roms so it could well be something that i'm doing wrong.
Please can somebody point me in the right direction for fixing my issues.
Thanks
Robert
update:
Just reinstalled with 4.4.2 GAPPS from Omnirom thread and so far so good. Can anyone recommend a later GAPPS package that works well?
stanfr0 said:
I have the following problems:
Google maps will not run
Chrome hangs and freezes
BBC iplayer starts to play and then freezes
I downloaded and installed the latest rom from your link in the forum yesterday. I installed the full current pa gapps package from your link in the forum yesterday as well.
I also tried loading the CM11 big part and the omnirom big part roms with the same gapps.
Both seem to have the same problem which suggest to me that the issue is with gapps.
I have tried uninstalling updates in google play but the problem persists.
Thanks for all the hard work that you put into this rom. I am a newcomer to flashing roms so it could well be something that i'm doing wrong.
Please can somebody point me in the right direction for fixing my issues.
Thanks
Robert
Click to expand...
Click to collapse
Chrome 33.0.1750.170
Google maps currently has a problem with the ROM
BBC iPlayer... Who knows??
All of this is in the thread, bud.
Encrypted /data and 3G not working together
I'm seeing issues with 3G on a UK Xoom (MZ601) with encrypted /data partition.
EOS4 worked fine — no problems with 3G and encrypted /data.
The current 4.4.4 builds don't seem to play nicely, however. 3G is fine on a non-encrypted Xoom, but as soon as I enable encryption I lose 3G connectivity.
I was using the 20140709.222056 build for some time, and managed to get some connectivity by changing ril-daemon to class late_start in init.rc and reflashing boot.img. Then I would sometimes have data when the device booted, but other times it would say "no SIM card" on the lock screen (I couldn't predict why — it seemed to be some kind of race condition).
Have just installed the 20141120.110555 build, and so far haven't managed to get 3G working at all with encrypted /data.
I'd love to get this working — any debugging info I can give? Thanks.
cantab said:
I was using the 20140709.222056 build for some time, and managed to get some connectivity by changing ril-daemon to class late_start in init.rc and reflashing boot.img. Then I would sometimes have data when the device booted, but other times it would say "no SIM card" on the lock screen (I couldn't predict why — it seemed to be some kind of race condition).
Have just installed the 20141120.110555 build, and so far haven't managed to get 3G working at all with encrypted /data.
Click to expand...
Click to collapse
OK, I've now got 20141120.110555 working very intermittently. I've replaced bootanimation.zip with the one from 20140709.222056 (which doesn't contain any partX displayed after boot has finished), and as long as I type my decryption password quickly enough when prompted I can get working 3G. But a slowly-typed password still results in "no SIM card".
I think this probably confirms my theory that there's some race condition going on.
Anyone any pointers on further things to try? Thanks.
welcome back TeamEOS !
Was using the non official cyanogen for xoom, but switched imediately when I discover you guys were back
Two quick questions:
Where can I find the performance settings in thr ROM to change cpu min and max ?
Are you thinking to have a merged status navigation bar like launcher2.apk for 4.2
Keep the very good work !
Performance settings
welcome back TeamEOS !
Was using the non official cyanogen for xoom, but switched imediately when I discover you guys were back
Two quick questions:
Where can I find the performance settings to change cpu min and max ? Could not find it anywhere.
Are you thinking to have a merged status/navigation bar like launcher2.apk for 4.2
Keep the very good work !
Cant run stingray_cdma
Stuck on moto dual core logo. So i can send u logcat ,but will it be useful?
N3phastus said:
welcome back TeamEOS !
Was using the non official cyanogen for xoom, but switched imediately when I discover you guys were back
Two quick questions:
Where can I find the performance settings to change cpu min and max ? Could not find it anywhere.
Are you thinking to have a merged status/navigation bar like launcher2.apk for 4.2
Keep the very good work !
Click to expand...
Click to collapse
I may be able to help with one of your questions. I have been running TeamEOS 4.4.4 nightlies since the beginning and it is now OC'd to 1400. I downloaded the TricksterMod app from Google Play and with it you can adjust cpu min and max as well as governor etc.
What recovery to install the ROM from?
What recovery should I use to install the ROM?
what is the minimal version of TWRP that supports this version?
should it be BigPart or not?
I have tried both, however, the device doesn't boot, stuck on dual core moto logo
I have stingray_cdma XOOM
brewer75 said:
I may be able to help with one of your questions. I have been running TeamEOS 4.4.4 nightlies since the beginning and it is now OC'd to 1400. I downloaded the TricksterMod app from Google Play and with it you can adjust cpu min and max as well as governor etc.
Click to expand...
Click to collapse
Thanks.
I saw it somewhere in the forum and I'm using it, just wonder if this option is not hidden in the rom itself. Just pushed CPU to 1.6, dunno what other settings could be improved ...
Rom is very stable, only problem I noticed is random freezes in Chrome, I deleted everything and reflashed with nano-gapps with stock browser, until now, no freezes.
I'd really like to see the bars merged, to have a little more display
Hello, how can I enable ethernet on this Rom?
MfG,
Delta_VII
Xoom Stingray_CDMA version
here is "/proc/last_kmsg" View attachment log.txt . This version stucks on "moto dual core" boot screen! Thanks!!!
not moving forward from the M logo
Hi,
Thanks for your effort and excellent work but I need some help, i can't move forward from the M logo, i tried TWMR bigpart with Cyanogenmod 4.4.4 and Omni 4.4.4 and both works fine but when i try yours nothing appears to be working, i already try a clean installation ( format again with bigpart and wipe everything except sd card) but nothings seems to be working. The main thing i want to try, is to get back my CDMA signal because since i tried the stock rom 4.1.2 i was not able to get any Data working there, my xoom is a just CDMA with no sim or LTE upgrade and i already tried 2 basebands on it the one with the last version of the stock room and the one that gets installed with the IMML update but no luck, if by any chance you have the first baseband it would be great i guess its something like 2.00.
Thanks!!!
Hey,
Can someone tell me how to check my flash memory? After 2-3 weeks of using my phone I get trouble with some apps like SwiftKey which is forgetting the settings and poping up with the first time usage wizard.
I already wiped everything and then it works for some weeks as I said but its really annoying. I am using the Cyanongenmod 12 .
Thanks
md
Edit:
When I get the wizard I can see following in the logcat:
03-06 11:44:44.962 11586-11614/com.touchtype.swiftkey E/SharedPreferencesImpl﹕ Couldn't rename file /data/data/com.touchtype.swiftkey/shared_prefs/com.touchtype.swiftkey_preferences.xml to backup file /data/data/com.touchtype.swiftkey/shared_prefs/com.touchtype.swiftkey_preferences.xml.bak
03-06 11:44:44.964 11586-11586/com.touchtype.swiftkey E/SpannableStringBuilder﹕ SPAN_EXCLUSIVE_EXCLUSIVE spans cannot have a zero length
03-06 11:44:45.545 11586-11614/com.touchtype.swiftkey E/SharedPreferencesImpl﹕ Couldn't rename file /data/data/com.touchtype.swiftkey/shared_prefs/com.touchtype.swiftkey_preferences.xml to backup file /data/data/com.touchtype.swiftkey/shared_prefs/com.touchtype.swiftkey_preferences.xml.bak
03-06 11:44:47.417
But no problem to rename the file by my own
Posting this to see if I might be able to get some help. I have intermediate knowledge of Android OS, so I'm looking for step by step help. I currently have no PC access which makes all of this much harder. Device I'm currently on is ZTE Zmax Pro, (no root on marshmallow 6.0.1)which probably won't be any help in this situation. I've looked through several threads but haven't found something I can really use. I even looked into a couple 1 click root apps, but they didn't work. Not only that but I'd rather do it manually anyways.
Here's all my device information for the Lenovo Tablet
Model: TB-8504F
Build Number: TB-8504F_S000053_180205_ROW
Build Version: NMF26F
(not sure if needed but providing anyways)
Local Storage is 16gB
I added 32gB microSd
API lvl: 25
CPU: arm64-v8a
os.arch: aarch64
Kernel: Linux Version 3.18.31-perf-gfedb9ec-dirty
ANDROID_ASSETS=/system/app
-Environment Variables (12)-
ANDROID_BOOTLOGO=1
ANDROID_DATA=/data
ANDROID_ROOT=/system
ANDROID_SOCKET_zygote=8
ANDROID_STORAGE=/storage
ASEC_MOUNTPOINT=/mnt/asec
BOOTCLASSPATH=/system/framework/core-oj.jar:/system/framework/core-libart.jar:/system/framework/conscrypt.jar:/system/framework/okhttp.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/telephony-common.jar:/system/framework/voip-common.jar:/system/framework/ims-common.jar:/system/framework/apache-xml.jar:/system/framework/org.apache.http.legacy.boot.jar:/system/framework/dolby_ds2.jar:/system/framework/dolby_ds1.jar:/system/framework/tcmiface.jar:/system/framework/WfdCommon.jar:/system/framework/oem-services.jar:/system/framework/qcom.fmradio.jar:/system/framework/qcmediaplayer.jar:/system/framework/telephony-ext.jar
DOWNLOAD_CACHE=/data/cache
EXTERNAL_STORAGE=/sdcard
PATH=/sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin
SYSTEMSERVERCLASSPATH=/system/framework/services.jar:/system/framework/ethernet-service.jar:/system/framework/wifi-service.jar
-------------------------------------------------
I appreciate any support or feedback. Thank you!
Cryntic said:
Posting this to see if I might be able to get some help. I have intermediate knowledge of Android OS, so I'm looking for step by step help. I currently have no PC access which makes all of this much harder. Device I'm currently on is ZTE Zmax Pro, (no root on marshmallow 6.0.1)which probably won't be any help in this situation. I've looked through several threads but haven't found something I can really use. I even looked into a couple 1 click root apps, but they didn't work. Not only that but I'd rather do it manually anyways.
Here's all my device information for the Lenovo Tablet
Model: TB-8504F
Build Number: TB-8504F_S000053_180205_ROW
Build Version: NMF26F
(not sure if needed but providing anyways)
Local Storage is 16gB
I added 32gB microSd
API lvl: 25
CPU: arm64-v8a
os.arch: aarch64
Kernel: Linux Version 3.18.31-perf-gfedb9ec-dirty
ANDROID_ASSETS=/system/app
-Environment Variables (12)-
ANDROID_BOOTLOGO=1
ANDROID_DATA=/data
ANDROID_ROOT=/system
ANDROID_SOCKET_zygote=8
ANDROID_STORAGE=/storage
ASEC_MOUNTPOINT=/mnt/asec
BOOTCLASSPATH=/system/framework/core-oj.jar:/system/framework/core-libart.jar:/system/framework/conscrypt.jar:/system/framework/okhttp.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/telephony-common.jar:/system/framework/voip-common.jar:/system/framework/ims-common.jar:/system/framework/apache-xml.jar:/system/framework/org.apache.http.legacy.boot.jar:/system/framework/dolby_ds2.jar:/system/framework/dolby_ds1.jar:/system/framework/tcmiface.jar:/system/framework/WfdCommon.jar:/system/framework/oem-services.jar:/system/framework/qcom.fmradio.jar:/system/framework/qcmediaplayer.jar:/system/framework/telephony-ext.jar
DOWNLOAD_CACHE=/data/cache
EXTERNAL_STORAGE=/sdcard
PATH=/sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin
SYSTEMSERVERCLASSPATH=/system/framework/services.jar:/system/framework/ethernet-service.jar:/system/framework/wifi-service.jar
-------------------------------------------------
I appreciate any support or feedback. Thank you!
Click to expand...
Click to collapse
Try with #King_root
https://kingroot.net
Sent from my [device_name] using XDA-Developers Legacy app
I've tried that a few times already. First time was after I unboxed the device(stock firmware I believe?). Went through 3 software updates while trying in between each one as well. I'll go ahead and try again though. I'll post update.
Kingroot Update: Ran root process, hangs at 01% for about a minute until jumping to 15%. Got to 16% and process stopped. Was prompted to either Reboot or release memory. After reboot, the root process went up to 23%. Third time around it goes to 19% and keeps doing it. Do I keep this process going or am I wasting my time? Does the software try a different method each time? There's only 18 root requests too. Not sure how popular this tablet is but that means it's being rooted easily or nobody has one lol
Is it the lenovo tb 8504f you want to root because we have the same device and i know how to root it very easy please answer me i also need your help
Hey, I got a little problem with my Tab2 10.1 - with different ROMs and even with stock firmware, I always get nearly 100% CPU usage by "other processes".
Im getting that information by the app "System Panel 2". And the tab runs like sh*t... What can I do now? Im not that new to rooting and flashing, but something like this never happend to me... :crying:
Its a Tab 2 10.1 WiFi (P5110)...
I tried:
- (clean) flash of different ROMs
- (dirty) flash of old backups
- wipe of everything (incl. Internal Storage etc...)
- flashing stock FW with Odin
- tried phh's superuser instead of SuperSU
- tried in terminal "setenforce 0" (or something like that)
Some flashes run the first minutes like always and some of them are from the beginning sh*tty to use, cant even open settings app...
Hope anyone got an idea for that problem :/
Chriss97ST said:
Hey, I got a little problem with my Tab2 10.1 - with different ROMs and even with stock firmware, I always get nearly 100% CPU usage by "other processes".
Im getting that information by the app "System Panel 2". And the tab runs like sh*t... What can I do now? Im not that new to rooting and flashing, but something like this never happend to me... :crying:
Its a Tab 2 10.1 WiFi (P5110)...
I tried:
- (clean) flash of different ROMs
- (dirty) flash of old backups
- wipe of everything (incl. Internal Storage etc...)
- flashing stock FW with Odin
- tried phh's superuser instead of SuperSU
- tried in terminal "setenforce 0" (or something like that)
Some flashes run the first minutes like always and some of them are from the beginning sh*tty to use, cant even open settings app...
Hope anyone got an idea for that problem :/
Click to expand...
Click to collapse
Finally I got it!!! I dont know why, but it was my SD Card... I unplugged it and boom, no problems anymore...
I wiped the SD Card and now I can use it like before without this weired problem. Huh...
SD card formatting stopped high CPU on custom ROM. Thanks!
Thank you!
This solved my problem with a custom rom (NAOSPROM 7.1.2 december with OpenGapps pico) on my Samsung Galaxy Tab 2.
After installing gave me alternating high CPU after a reboot. One time reboot gave a low CPU and than next time high.
'Simple OS Monitor' (great tool) just showed system_server around 16-17% hardly ever lower. Stopping almost all non essential system apps and all user apps. Didn't make any difference. Even removing SD card.
A network reset seemed to do something, but hardly.
But then after formatting SD card, putting back the files I had stored there, except the Android .secure android folder, I rebooted and all was well. CPU usage of system_server went from 17 to 1 % and total CPU to normal
So Samsung Galaxy Tab 2 works well with NAOSPROM 7.1.2 custom rom ... but don't forget to format your SD (when you experience high CPU usage).
Just in case somebody finds this information. Like I did yours.