Dexter_nlb said:
not sure its worth discussing this topic again and again, as the problem seems to be in the wifi driver and i looked in the sdk release, and no source is included for the wifi driver, so we have to see if toshiba finds a fix for it.
and the same is not so easily found on stock folio's as not many uses it with stock i guess, and those with just a little tech. is already moved away from stock image..
but i would appreciate moving this specific topic into a new thread, as we now got a section where all issues can be posted, and we know it all relate to our folio now
(similar talk is found on elocityA7, Viewsonice got a different wifi hardware, but might just have similar issues too)
Click to expand...
Click to collapse
As requested, here's a new thread about this issue.
Just to resume, the behaviour I see on my folio is high CPU load after each reboot for several (up to 30) minutes caused by the system server process.
Also it seems it goes away after reboot if Wifi is turned off before the device is rebooted.
Anyone NOT having this issue?
(Some screenshots below)
Nemo0815 said:
As requested, here's a new thread about this issue.
Just to resume, the behaviour I see on my folio is high CPU load after each reboot for several (up to 30) minutes caused by the system server process.
Also it seems it goes away after reboot if Wifi is turned off before the device is rebooted.
Anyone NOT having this issue?
(Some screenshots below)
Click to expand...
Click to collapse
having the issue, but in 1.3 it seems like high cpu load doesn't kill performance like it did in earlier version, so i can live with it until there's a fix, if ever. anyway. Android 3.0 might be around the corner soon, so i wouldn't worry too much.
actually randomly I get low CPU load with wifi and other times high cpu load without wifi... so at the moment I did not find what could be the issue.
With the latest 2 patches the system got better and better even if sometimes I get the high cpu load.
I don't think that the wireless driver is responsible for the CPU usage as the interrupts related to the wifi card doesn't raise so much when the system is busy.
I think that it's some app which starts hogging the CPU when detects that there is a network connection
I have some news:
I removed TelephonyProvider.apk from /system/app but after rebooting the system_server process ran at 50% (100% of one core) until I restored the APK and rebooted it again.
So I moved TelephonyProvider.apk to /data/app and after a reboot I uninstalled it with:
Code:
adb uninstall com.android.providers.telephony
The issue is gone now so I suspect that uninstalling a service "in the right way"™ unregisters it from some sort of config (I heard about a service xml file).
As our FolioMod has some services stripped away (isn't it?) it could be that those services are still in the config and system_server runs in a busy loop trying to start them.
This is just a theory, help is appreciated.
teknoraver said:
I have some news:
I removed TelephonyProvider.apk from /system/app but after rebooting the system_server process ran at 50% (100% of one core) until I restored the APK and rebooted it again.
So I moved TelephonyProvider.apk to /data/app and after a reboot I uninstalled it with:
Code:
adb uninstall com.android.providers.telephony
Click to expand...
Click to collapse
How did you move it to data? I cannot do that for some reason ("Cross-device link error"). I tried to uninstall alone and ADB said "success", however after reboot the CPU hog is back again...
teknoraver said:
I don't think that the wireless driver is responsible for the CPU usage as the interrupts related to the wifi card doesn't raise so much when the system is busy.
Click to expand...
Click to collapse
I don't think so either, especially since the CPU hogging stopps after some minutes, even if Wifi is turned on.
Hello teknoraver,
yes the xml is /data/system/packages.xml, and if you want to delete completly a system app you must delete from this archive and from system/app and from //data/data also.
teknoraver said:
I have some news:
I removed TelephonyProvider.apk from /system/app but after rebooting the system_server process ran at 50% (100% of one core) until I restored the APK and rebooted it again.
So I moved TelephonyProvider.apk to /data/app and after a reboot I uninstalled it with:
Code:
adb uninstall com.android.providers.telephony
The issue is gone now so I suspect that uninstalling a service "in the right way"™ unregisters it from some sort of config (I heard about a service xml file).
As our FolioMod has some services stripped away (isn't it?) it could be that those services are still in the config and system_server runs in a busy loop trying to start them.
This is just a theory, help is appreciated.
Click to expand...
Click to collapse
Edit:
Sorry, didn't notice, that this thread was moved to General, moved my post to the kernel tweak section.
http://forum.xda-developers.com/showpost.php?p=10376986&postcount=43
Nemo0815 said:
How did you move it to data? I cannot do that for some reason ("Cross-device link error"). I tried to uninstall alone and ADB said "success", however after reboot the CPU hog is back again...
I don't think so either, especially since the CPU hogging stopps after some minutes, even if Wifi is turned on.
Click to expand...
Click to collapse
1) "adb remount" makes /system writable
2) adb shell
4) su
5a) cp /system/app/TelephonyProvider.apk /data/app
5b) rm /system/app/TelephonyProvider.apk
... reboot ...
adb uninstall com.android.providers.telephony
It worked in my case but not sure yet, if it fixes the problem with cpu load.
p.s. Fix is not working, I still have 50% and above after start with wifi enabled :-(
So that finally it looks like Shrikkelik in this post http://forum.xda-developers.com/showpost.php?p=10439894&postcount=2407 has solved the issue of high cpu load after reboot. It works.
tobr said:
So that finally it looks like Shrikkelik in this post http://forum.xda-developers.com/showpost.php?p=10439894&postcount=2407 has solved the issue of high cpu load after reboot. It works.
Click to expand...
Click to collapse
+1 confirmed, solves the above mentioned problem.
Related
Evening everyone,
For the past 7-8 days i've been having problems with my hero..it became REALLY slow all of a sudden... way more than before..apps have the usual "lag" that well you know lag once a while (only a bit more often)
I tried re-installing my Modaco 3.0, no results..Tried to install modaco 3.1 and villain 2.1 and i had the same "lag".. is it the apps that cause it? the more apps i have installed the laggier it will be? I have around 150 *maybe less maybe more, dont got the phone with me atm*
And on taskiller, advanced task killer and advanced task manager it used to show me the free memory or wtvr 100-120 after every end task..now it starts from 70 and a few seconds after i kill all apps it drops down to 35-40 :S
thx in regards
bump :/ no1?
did you check logcat when the lag occurs?
kendong2 said:
did you check logcat when the lag occurs?
Click to expand...
Click to collapse
nop?;o how do i do that?
you need adb working for that, check some tutorials.
then connect the usb cable, restart the phone and execute "adb logcat" on your pc. you can redirect the output with "adb logcat > logcat.txt", so you can check it in detail or attach it here.
kendong2 said:
you need adb working for that, check some tutorials.
then connect the usb cable, restart the phone and execute "adb logcat" on your pc. you can redirect the output with "adb logcat > logcat.txt", so you can check it in detail or attach it here.
Click to expand...
Click to collapse
i never got adb to work properly ;/ any other ideas?
bump..anyone?its getting slower and slower :S i cant even listen to music now..and i even uninstalled 20+ apps..
You've already been given advice - get ADB working so you can post your logcat. Without more information, it's doubtful that anyone will be able to help you.
One question though - have you tried wiping and setting up your phone from scratch?
Regards,
Dave
yes i tried wiping my phone..even re-installed my modaco rom twice and tried a different rom aswell..and modaco rom 3.0 (prefer 2.9)
and i cant get adb working it keeps saying no access or something like that
i cant even listen to music now bcz the sound gets f***ed up..
Have a look at the services you're running.
You asked whether the more apps the slower your device is.
And the answer is yes.
So, you can always try new apps, but useless ones should leave(even with an app2sd, that'll allowed to to keep tons of apps).
I don't think it'll be very hard, Android uninstall apps fast and easily, not like WM based ones.
Shei77 said:
and i cant get adb working it keeps saying no access or something like that
Click to expand...
Click to collapse
If you want help with this issue, you need to list out precisely what you have tried, and precisely what messages/errors are returned - "no access or something like that" is about as useful as a chocolate teapot when it comes to trying to diagnose your issue!
Regards,
Dave
thx for the answers...
i cant remember what exact error adb was giving me and i cant check it until tonight when i have some spare time...
also i keep task killing and there is no difference... nor with uninstalling :/ appmanager says i have 127 apps :/
hello again people
i currently dont have my computer (thats why i didnt try the adb)
but i have tried some things a m8 told me too and thats dalvik cache wipe and moving log(something) to SD.. i did that and i lost 80MB of INTERNAL memory and my lock screen..i cant drag it down anymore..i have to press menu twice...
but my phone is now faster although WAY slower when writing....
i'll try the adb shell as soon as i get my pc back from the technician!
thx a lot in advance!
http://www.scottsroms.com/showthread.php?510-Quick-Stock-ICS-for-CleanICS
Tachi91 is this working without the reboots for you?
Here's what I posted on the thread at Scott's Roms:
I've had a lot of issues with this causing constant reboots after 10-20 seconds of use.
I ran this right after installing the CleanICS ROM. Initially it hung at the 4g boot animation. I did a battery pull and wiped, and it allowed me to boot.
After that, I have enough time to unlock and page through apps, for example, before it reboots. It continues to reboot after a certain amount of time, consistently.
The only time I didn't have constant reboots was when my data network wasn't being picked up for some reason. As soon as I toggled on 3g or 4g, the reboots began again.
I've wiped and reinstalled CleanICS and this .bat numerous times over the last few hours, all with the same result.
Click to expand...
Click to collapse
I tried
full wipe
flash rom
at bootscreen run bat
wipe cache/dalvik/data
sysui crashed once, shows bootscreen again when trying to call, do other stuff
I have found the problem. Don't replace the settings.apk and settings provider. That is what is causing the crashing.
Can we just remove a chunk out of the .bat file that is causing this. Is it the systemui part?
cincyelite22 said:
Can we just remove a chunk out of the .bat file that is causing this. Is it the systemui part?
Click to expand...
Click to collapse
read the post right above yours lol. Ninja'd
I took out settings.apk and settingsprovider.apk, and haven't had a reboot yet, but the browser constantly FCs.
Edit: Force stop + clearing data for the browser fixed that.
I'm sorry I unwillingly got involved in something unrelated to xda smh..
ANYWAYS
Why can try restoring SettingsProvider.apk and see how that changes things
adb command
adb remount
adb shell mv /system/app/SettingsProvider.bak /system/app/SettingsProvider.apk
Can we take out the browser part then too?
Settings.apk is what gives the Settings Pane the ICS look
SettingsProviders.apk is the corresponding apk BUT its not necessary to have the ICS look in settings ... I just added it as a precaution
SystemUI.apk is the statusbar/Pull Down ... That Crashed but isn't need to keep the system up since it crashed but comes back up without raping Android
Ok Tachi Im testing what you said. Ill let you know if it works
Seems to be working
Question......What does settings provider do?
---------- Post added at 09:31 PM ---------- Previous post was at 09:23 PM ----------
Only thing im noticing is trying to get a data connection. Wifi works but not data
Going to try to wipe data and cache and see if it works
..I'm going to remove some more HTC apps and see if any dependencies get removed and prevents boot loop
... So far the one sure way that i've tested is running the .bat before actually using the ROM.... and to remove the annoying Setup wizard
adb shell rm /system/app/HTCSetupWizard.apk
Would settings provide have any effect on data?
cincyelite22 said:
Would settings provide have any effect on data?
Click to expand...
Click to collapse
Yes and No ... Any and all changes are saved in /data ... now i imagine something that was present in the sense Provider is present in the ICS Provider and would cause and issue
..
But the logcat i see is relating something to com.htc.launcher ... so maybe any apps that rely on Rosie ... like Personalize apk and so on would cause an issue
I just restored the old settings provider. I'll let you know what it does.
Where do you turn on data in the ics settings that might be my problem.
cincyelite22 said:
I just restored the old settings provider. I'll let you know what it does.
Where do you turn on data in the ics settings that might be my problem.
Click to expand...
Click to collapse
Its in the Settings ... in the Sense version is a switch on the pull down.. on ICS Settings I think its under otther i think ... I can't check now ... working on somethin
The Browser FC's on use with this.
Vashypooh said:
The Browser FC's on use with this.
Click to expand...
Click to collapse
Some one said clear data for the browser
and force closing it fixes the problem
Vashypooh said:
The Browser FC's on use with this.
Click to expand...
Click to collapse
Try restoring the Sense Browser .. They can coincide...
adb shell mv /system/apps/Browser.bak /system/apps/HTCBrowser.apk
that just restores the sense Browsers and renames it to HTCBrowser like that it doesn't overwrite the ICS one and you can have both and see if it stables out.... Remediable to clear cache/data and restart afterwards
On my Galaxy Tab 10.1 running 'In Paris V4' with preshoot's kernel I have the following problem:
Android media process hogs CPU (47%, which means 100% for one thread on this dual core device).
The device was running fine for a few months, so the problem is not the ROM/kernel but was caused by something else later on.
I would like to fix this problem (without reformatting/reflashing the whole ROM). If there is no easy solution I just want to disable it, but could not figure out how.
Killing the process helps for some time, but after some minutes/hours the process is back. I tried 'pm disable com.android.providers.media' as well as 'pm disable com.android.providers.media/com.android.media.MediaScannerReceiver' -- both with no result (it helps for a few minutes but then the process is back again!).
I don't know how/where this process is started so that I can make a modification there to disable it or which package I should delete to get rid of the process.
Any help/suggestions are appreciated.
This obviously seems to be the wrong board I am posting that supposedly simple question in -- could somebody please point me in the right direction and I will ask again in a more appropriate board.
I'd say the board is the right one ... but at least I can't help you here, as I don't know the answer .
My only advice would be to flash a newer ROM, isn't inParis kinda "outdated"? I think android.media has something to do with connecting USB devices to the tab, since it's the thing that crashes on ICS KANGs when you plug out your USB stick ... but that's all I can help you with (if it's any help)
mrmagmrmag said:
On my Galaxy Tab 10.1 running 'In Paris V4' with preshoot's kernel I have the following problem:
Android media process hogs CPU (47%, which means 100% for one thread on this dual core device).
The device was running fine for a few months, so the problem is not the ROM/kernel but was caused by something else later on.
I would like to fix this problem (without reformatting/reflashing the whole ROM). If there is no easy solution I just want to disable it, but could not figure out how.
Killing the process helps for some time, but after some minutes/hours the process is back. I tried 'pm disable com.android.providers.media' as well as 'pm disable com.android.providers.media/com.android.media.MediaScannerReceiver' -- both with no result (it helps for a few minutes but then the process is back again!).
I don't know how/where this process is started so that I can make a modification there to disable it or which package I should delete to get rid of the process.
Any help/suggestions are appreciated.
Click to expand...
Click to collapse
Freeze the app with Titanium Backup or use this specific purpose app from the market
https://market.android.com/details?id=com.addz.mediascannerroot
Worked for me
mrmagmrmag said:
On my Galaxy Tab 10.1 running 'In Paris V4' with preshoot's kernel I have the following problem:
Android media process hogs CPU (47%, which means 100% for one thread on this dual core device).
The device was running fine for a few months, so the problem is not the ROM/kernel but was caused by something else later on.
I would like to fix this problem (without reformatting/reflashing the whole ROM). If there is no easy solution I just want to disable it, but could not figure out how.
Killing the process helps for some time, but after some minutes/hours the process is back. I tried 'pm disable com.android.providers.media' as well as 'pm disable com.android.providers.media/com.android.media.MediaScannerReceiver' -- both with no result (it helps for a few minutes but then the process is back again!).
I don't know how/where this process is started so that I can make a modification there to disable it or which package I should delete to get rid of the process.
Any help/suggestions are appreciated.
Click to expand...
Click to collapse
search pershoot's thread... Or check his website... it's there...
@slack04
Thanks a lot -- I used this solution:
http://forum.xda-developers.com/showthread.php?t=1258302
to automatically kill the process once it starts running. No real solution, but it helps until I manage to update the tab to ICS.
mrmagmrmag said:
@slack04
Thanks a lot -- I used this solution:
http://forum.xda-developers.com/showthread.php?t=1258302
to automatically kill the process once it starts running. No real solution, but it helps until I manage to update the tab to ICS.
Click to expand...
Click to collapse
Honestly, I was going to say that you'll spend less time doing the ICS update than looking for this; especially on that ROM (great ROM.... 6 months ago...). I'd suggest go with the last milestone from Romann.
mrmagmrmag said:
@slack04
Thanks a lot -- I used this solution:
http://forum.xda-developers.com/showthread.php?t=1258302
to automatically kill the process once it starts running. No real solution, but it helps until I manage to update the tab to ICS.
Click to expand...
Click to collapse
I would check your media files... delete them or put .nomedia file in all those places.
Next thing to try is to clean dalvik cache.
Thanks -- tried to flash latest Milestone and b26 releases. Unfortunately VPN is not working and I can only download apps via marked when connected to a VPN (even if this does not change my IP as I often just connect to my Router). So -- until VPN is supported with any ICS ROM I am stuck with my old In Paris 4 (with pershoot kernel to mount SMB shares via CIFS).
mrmagmrmag said:
Thanks -- tried to flash latest Milestone and b26 releases. Unfortunately VPN is not working and I can only download apps via marked when connected to a VPN (even if this does not change my IP as I often just connect to my Router). So -- until VPN is supported with any ICS ROM I am stuck with my old In Paris 4 (with pershoot kernel to mount SMB shares via CIFS).
Click to expand...
Click to collapse
I can understand if you'd just rather wait because of having to bother with reinstalling every thing, but it looks like you can change ROMs quickly. So why not goto Task14 while you wait for ICS?
There might be device issue I'm not aware of also, so just wondering.
If you can read this, thank the person that taught you how.
[UPDATE] Version 0.40 is out.
Recent changes:
added the uptime monitor
renamed "battery monitor" to "system monitor"
minor cleanup to make it more compatible with the newer SDK's lint checks
other changes
Download the latest version
Source code available on github
------------------------------------------------------------------------------------------------
[UPDATE] Version 0.36 is out.
Recent changes:
version bump with minor cosmetic changes
This is just a minor maintenance release, no need to upgrade if your 0.35-beta1 is working well.
------------------------------------------------------------------------------------------------
[UPDATE] Version 0.35-beta1 is out.
Recent changes:
improved the monitoring service
added a new option - Only if <100% (will only run the auto-action (reboot or restart service) if the battery reports less than 100% when done charging)
improved the "battery full" detection code, should work better now
other fixes and improvements
Also had to delete some old versions since I hit the 20-attachments-per-post limit.
EDIT: Just realized I uploaded the wrong screenshot. :doh: Corrected.
------------------------------------------------------------------------------------------------
[UPDATE] Version 0.31-beta1 is out.
Recent changes:
hopefully fixed the constant "superuser auth" issue on CM10
------------------------------------------------------------------------------------------------
[UPDATE] Version 0.30-beta1 is out.
NOTE: Due to the significant changes in the settings/preferences part, please uninstall any previous version before installing this one. Thank you.
Click to expand...
Click to collapse
Recent changes:
re-added deleting batterystats.bin as an option (off by default)
moved all preferences to the settings screen
added an option to turn charging on or off, and also an option to automatically turn charging off when USB power detected
added some heuristics to determine when the battery is done charging (if the voltage does not change within 30 minutes, the battery is considered to be done charging) - hopefully this works
bugfixes, general code cleanup
Since new features were added and a significant chunk of the code has been rewritten, this is now considered beta.
This version also makes sure to be as non-intrusive as possible - nothing will happen automatically by default, you need to initiate any actions.
------------------------------------------------------------------------------------------------
[UPDATE] Version 0.21 is out.
Recent changes:
disabled removing the batterystats.bin file - it seems to have only caused problems with not a lot benefit. WARNING: if you're coming from an earlier version, you need to wipe app data for this to work!
changed defaults - now the app won't run the fix automatically when power detected by default, this should make the app completely non-intrusive by default.
------------------------------------------------------------------------------------------------
[UPDATE] Version 0.20 is out.
Recent changes:
added an option to restart the battd service instead of a full reboot - seems to work but this should be considered a beta feature
moved some options to a separate settings screen
cleanup here and there
Also cleaned up the attachments to this post.
------------------------------------------------------------------------------------------------
[UPDATE] Version 0.16 is out.
Recent changes:
better handling of missing or invalid datadir
------------------------------------------------------------------------------------------------
[UPDATE] Version 0.15 is out.
Recent changes:
about box is now shown on first run
rearranged and cleaned up the about text, added the donate link (which hopefully works)
fix for busybox that has the ash applet instead of sh
busybox is no longer required, will try to use system shell if busybox is not found
fixed a progress dialog issue upon screen rotation
uploaded source code to github
------------------------------------------------------------------------------------------------
[UPDATE] Version 0.1 FINAL is out.
Recent changes:
mostly just cosmetic changes
------------------------------------------------------------------------------------------------
[UPDATE] Version 0.1-beta4 is out.
Recent changes:
instead of running hardcoded shell commands, now runs external shell scripts in the app's datadir (so you can modify the scripts to your own liking)
all shell commands/scripts are now executed through busybox instead of default system shell (so busybox is now required)
separated fixing the battd datafiles (which is normally needed every so often) from fixing battd permissions and ownership (which should be needed only once)
cleanup and other improvements
------------------------------------------------------------------------------------------------
[UPDATE] Version 0.1-beta3 is out.
Recent changes:
run fix and recalibration right before auto-reboot too, just in case
------------------------------------------------------------------------------------------------
[UPDATE] Version 0.1-beta2 is out.
Recent changes:
added deleting batterystats.bin
added fixing ownership and permissions of battd and friends
cleaned up the "about" and "licence" texts
possibly other fixes and improvements I forgot about
------------------------------------------------------------------------------------------------
[UPDATE] Version 0.1-beta1 is out.
Recent changes:
hopefully fixed the reboot-when-charged issue
------------------------------------------------------------------------------------------------
[UPDATE] Version 0.1-alpha3 is out.
Recent changes:
fixed some bugs that caused issues on ICS and newer
cleaned up the checkbox logic
slightly improved the UI
other minor fixes and improvements
Many of the issues (namely, "null" errors) should now hopefully be gone.
------------------------------------------------------------------------------------------------
[UPDATE] Version 0.1-alpha2 is out.
Changes include:
(hopefully) fixed su and other issues
added option to reboot the phone when it's done charging (hopefully that actually works )
added real-time battery monitor
general cleanup
other things I forgot
Many issues should now be fixed, but this is still considered alpha-quality software, so be warned.
------------------------------------------------------------------------------------------------
So...
Like many other people, I too am affected by the dreaded "won't charge beyond xx%" battery bug. I know in reality this is probably of little importance since (at least in my case) the battery is getting decent charge and lasts long enough anyway. But I would still like to see it fully charged, at least every so often.
So I did the procedure mentioned in this thread and it worked, but only once - the bug would appear again on the next charge cycle. Then I found this post and tried that too, and it also worked but also only once. So I decided to make this little app.
What the app does is, upon getting notified that the charger has been connected, it will automatically delete files in /data/battd (all except uid - namely cc_data, cc_data_old and powerup). Then all you have to do is wait for the battery to charge as far as it goes and then reboot (and then possibly charge a little more). That's it!
NOTE 1: Obviously for the app to work correctly your phone needs to be rooted.
NOTE 2: This app will not increase your battery life or change it in any way, shape or form. All it does is attempt to fix the percentage display.
Now admittedly, it can get annoying if you connect your phone to the computer just to transfer some files and the app gets triggered anyway because it detected charging. That's why the auto-triggering can also be disabled in the app. You can also leave it permanently disabled and just use the "force calibration" button to calibrate your battery only when you feel like it.
Anyway, I hope the app will be useful at least to some. The app should work on all rooted GB ROMs and possibly on ICS and JB too.
NOTE: this the initial release of the app, and is also my 3rd (if I'm counting them right) Android app as of yet. So be warned, this app is currently alpha-quality. Standard disclaimers apply, although I don't see how it could do any damage.
XDA:DevDB thread:
http://cleanimport.xda/index.php?threads/2468689/
Nice app. Seems simple but useful to all of us. Thanks,ravilov..
It's fantastic, thanks man.
ne1 tried this? does it work or is it placebo, cos my atrix wont pass thru 98% even when i have 4200mh of charge. but i tried Die Hard Calibration from zeppelinrox (same builder of V6 Supercharger) and had several issues on CM7, like wont charge when turned off. I had to flash another rom, Im afraid of having this issues again.
I got error. Its says "error recallobrating battery (null)". I wonder if it is because the app doesn't have root privilege, coz I dont get the requesting root prompt from superuser.
Sent from my MB860 using xda premium
This app will only get ur xx% values back to 100% or 99% without u having to delete any thing manually or pulling the battery. Correct me if i am wrong and thanks for the app ill sure try this.
bimasakti85 said:
I got error. Its says "error recallobrating battery (null)". I wonder if it is because the app doesn't have root privilege, coz I dont get the requesting root prompt from superuser.
Click to expand...
Click to collapse
If you don't get the prompt, the app is not getting required permissions and so it can't work.
Which ROM are you using? Can you go to terminal emulator on the phone and run
Code:
which su
and tell me what it says?
xateeq said:
This app will only get ur xx% values back to 100% or 99% without u having to delete any thing manually or pulling the battery. Correct me if i am wrong and thanks for the app ill sure try this.
Click to expand...
Click to collapse
Correct. It just makes it easier to apply the fix mentioned in the OP.
Wow, someone finally made this process easier! I had to do this every time I woke up in the morning using Root Browser. It only saves me maybe 30 seconds, but those 30 seconds it saves add up! Thanks bud.!
OP, add an auto reboot selection box that is triggered when the phone fully charged.
Sent from my MB860 on CM10
ravilov said:
If you don't get the prompt, the app is not getting required permissions and so it can't work.
Which ROM are you using? Can you go to terminal emulator on the phone and run
Code:
which su
and tell me what it says?
Correct. It just makes it easier to apply the fix mentioned in the OP.
Click to expand...
Click to collapse
I'm getting the null error as well, I'm currently using SuperSu and my su is in /system/xbin/su
Thanks for the app, excited for it to work
Soldier-2Point0 said:
Wow, someone finally made this process easier! I had to do this every time I woke up in the morning using Root Browser. It only saves me maybe 30 seconds, but those 30 seconds it saves add up! Thanks bud.!
Sent from my MB860 on CM10
Click to expand...
Click to collapse
And here I thought it was just me.
Could have used this app this morning myself. I'll check it out and report back.
Edit: Or I would if I wasn't, too, getting an error recalibrating message. I'm running epinter's CM10, and terminal emulator tells me "/system/sbin/su"
natboy said:
I'm getting the null error as well, I'm currently using SuperSu and my su is in /system/xbin/su
Thanks for the app, excited for it to work
Click to expand...
Click to collapse
Same error here, I'm in epinter jb rom.
Edit: the program don't ask for su permission. It's ok?
Edit 2: Unselect both options and press calibrate button. Here the program ask for su access, delete files and prompt for reboot. My battery was in 95% and 4200mA. After reboot, the battery is showing 100%. Excellent.
Enviado desde mi MB860 usando Tapatalk 2
Malaquai said:
Same error here, I'm in epinter jb rom.
Edit: the program don't ask for su permission. It's ok?
Edit 2: Unselect both options and press calibrate button. Here the program ask for su access, delete files and prompt for reboot. My battery was in 95% and 4200mA. After reboot, the battery is showing 100%. Excellent.
Enviado desde mi MB860 usando Tapatalk 2
Click to expand...
Click to collapse
Thanks for that, that worked for me as well. But also on epinter.
Malaquai said:
Same error here, I'm in epinter jb rom.
Edit: the program don't ask for su permission. It's ok?
Edit 2: Unselect both options and press calibrate button. Here the program ask for su access, delete files and prompt for reboot. My battery was in 95% and 4200mA. After reboot, the battery is showing 100%. Excellent.
Enviado desde mi MB860 usando Tapatalk 2
Click to expand...
Click to collapse
Got that prompt too, but now its said error because read only file system. Im using CM9 jokersax.
Sent from my MB860 using xda premium
bimasakti85 said:
Got that prompt too, but now its said error because read only file system. Im using CM9 jokersax.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
As an idea, use root explorer to see how is mounted your file system, mount as R/W if needed, try again with the fix program.
Enviado desde mi MB860 usando Tapatalk 2
Soldier-2Point0 said:
OP, add an auto reboot selection box that is triggered when the phone fully charged.
Click to expand...
Click to collapse
Good idea, I'll try to add that. Unfortunately unlike "charger connected", the "battery full" doesn't broadcast a system-wide event...
I'm working on a workaround for that.
natboy said:
I'm getting the null error as well, I'm currently using SuperSu and my su is in /system/xbin/su
Click to expand...
Click to collapse
Hm, my su is also there. But I'm using Superuser, not SuperSu. Maybe that's the catch? :dunno:
Malaquai said:
Same error here, I'm in epinter jb rom.
Click to expand...
Click to collapse
I guess that could be it too. I'm running CM7, don't have access to ICS or JB right now.
I'm trying to figure out what's causing this, if everything else fails I'll just have to install CM9/CM10 myself.
The rest of you that are affected, can you check if the files in /data/battd are deleted anyway, despite getting an error?
It would help me in pinpointing the problem.
Malaquai said:
Edit: the program don't ask for su permission. It's ok?
Click to expand...
Click to collapse
No, it should ask for permissions first time you run it.
Malaquai said:
Edit 2: Unselect both options and press calibrate button. Here the program ask for su access, delete files and prompt for reboot. My battery was in 95% and 4200mA. After reboot, the battery is showing 100%. Excellent.
Click to expand...
Click to collapse
Hm, that's weird that it works like that. I'll look into this too. Shouldn't be like this.
Can you also check if the files get deleted from /data/battd even when the app reports an error?
bimasakti85 said:
Got that prompt too, but now its said error because read only file system. Im using CM9 jokersax.
Click to expand...
Click to collapse
Well that's funny. So you got the reboot prompt, said yes to it, and then you got the error about read-only filesystem?
Hey buddy. I was getting the null error, but after I de selected both boxes, the prompt showed up.
I recommend you update the app to also delete the files found under /data, /system, /usage stats. See screenshot:
It should delete all the dated usage files except for the one that ends on. Xml. Maybe this will help the system start over fresh. :good:
Sent from my MB860 on CM10
Not sure how you're going to go about getting the battery stats. Briefly looking into it, there's not /proc/acpi, but `dumpsys battery` from a terminal gives battery information
you could do something like `dumpsys battery | grep level | cut -d : -f 2` which gives the value.
Soldier-2Point0 said:
Hey buddy. I was getting the null error, but after I de selected both boxes, the prompt showed up.
Click to expand...
Click to collapse
Yeah, I'm looking into that. Might have an idea what's causing it.
Soldier-2Point0 said:
I recommend you update the app to also delete the files found under /data, /system, /usage stats. See screenshot:
[IMAGE]
It should delete all the dated usage files except for the one that ends on. Xml. Maybe this will help the system start over fresh. :good:
Click to expand...
Click to collapse
Thanks for the tip. This should be pretty easy to add to the app. However I'd rather not delete too much stuff for now. I think I'd rather wait until it's confirmed this has some actual influence on the battery percentage.
natboy said:
Not sure how you're going to go about getting the battery stats. Briefly looking into it, there's not /proc/acpi, but `dumpsys battery` from a terminal gives battery information
you could do something like `dumpsys battery | grep level | cut -d : -f 2` which gives the value.
Click to expand...
Click to collapse
Oh no, Android has a nice API to fetch all that info, no need to twiddle around with random shell pipelines and such.
BTW, there's also cat /sys/class/power_supply/battery/capacity
I figured it had to be in there somewhere, just couldn't find it
ravilov said:
Well that's funny. So you got the reboot prompt, said yes to it, and then you got the error about read-only filesystem?
Click to expand...
Click to collapse
Well I not kidding, it shows up like that. After that prompt asking root access and allowed it, I pressed the force button. But Its says like that, read only file system. Already tried setting read and write from root explorer but It wont help.
Sent from my MB860 using xda premium
---------- Post added at 02:39 AM ---------- Previous post was at 02:34 AM ----------
This is the Screen shot :
Sent from my MB860 using xda premium
So I used the ACS/Shabbypenguin root method (do a Google search, I can't post links...) and followed the directions exactly. Well almost exactly, I knew of some issues so this is what I did...
First I downloaded Superuser & Superuser Elite (I previously paid for it on a different phone).
Then I downloaded the drivers and Odin and both kernals.
I installed the drivers and put my phone into development mode.
Next, I turned off my phone then turned it back on in download mode and flashed the pre-rooted kernal as per the instructions there.
Finally, I went through the process again to flash in the stock kernal.
Now the other users had issues with USB connection and the phone not being recognised, the answer to that was on page 11 of the above linked thread (editing the vold.fstab file). I did this (using ES Root Explorer) as per the instructions and restarted.
Things seemed fine for half a day. Now my phone randomly restarts, but not always randomly. I can perform specific actions to cause it to freeze and reboot (example, simply opening the vold.fstab file does this EVERY TIME, but I was able to copy/paste it to the SD card and then open and edit it and even copy/paste it back, all using ES root explorer, and no crash/reboot unless I open it specifically and yes, that's with having the system mounted as R/W).
Another thing I noticed since rooting, and it still has maintained the rooted status, is that any time my phone restarts or I restart it, I open the system tray and this stupid "tip" toast message comes up that, prior to rooting, only came up once. Now, it comes up only once after a restart but resets every time.
I tried to sign up for the ACS forums but for some reason, I've not gotten a single registration e-mail from them and messaged half their admin with no response (the fact that the site has no cancel account and no re-send activation option troubles me enough as it is and in my opinion, should be internationally illegal).
Anyway, that's the issue, I need to resolve these random restarts, which may or may not be caused by this vold.fstab file.
Also, I connect now (before when I did the fix, it worked), the computer doesn't recognise the phone so I can't even re-flash using Odin, but the phone works (until randomly restarting which is a pain...), so I am at a loss as to what the actual cause was and since nothing I change sticks when it restarts, I have no idea what the deal is.
Some more information...
Nothing I change sticks. I have programs that I uninstalled, but they still show up in the system tray after a reboot (if I click it, it says that the program is not installed, but it still shows up).
I tried swapping back the original build.prop - didn't stick.
I tried factory data reset - didn't do anything.
I tried a restore in BusyboxPro (stericon or something is the dev) - restored but there were some "errors".
Tried temporarily unrooting (Superuser Elite) - nothing.
I read about a power button issue - my power button is fine.
There is something wrong specifically with the OS in some way that certain actions cause it to freeze and restart. I have a game, "Deathworm" that I can play with no issues or freezes. I can do a few things but:
if I get on the mobile browser, sometimes it will freeze and reboot.
if I run AppManagerPro III, sometimes it crashes when calculating the cache size (always when it gets to 70/125 or whatever the total is, but always at 70 if it DOES crash).
Now I went into task manager and went through and cleared all the app data individually app per app. Before when I tried to do this (before restoring in Busybox, before restoring the original build.prop, etc), it would crash when I went into the downloaded tab of the thing to clear the cache. This time it didn't crash on me.
Other root stuff I have installed which was working before the random rebooting issue:
Script manager (free) and V6 supercharger (also unsupercharging wouldn't stick, which I tried before restoring the build.prop manually)
SuperUserElite
App Manager Pro III
SD Maid Pro
ES File Explorer (free version I think)
BusyBox Pro
SU Update Fixer
Screenshot It
After everything I just did, it seems to (for the moment) be working again, I am just waiting to see if it crashes again. So far I have opened and closed App Manager Pro III a few times and it calculated cache sizes with no crash. Right now, SD Maid Pro hasn't crashed yet open, hide certain tabs (clearing the data so I had to reset those options), close, reopen, scanned with system clean and app clean and actually did the app clean, so far no crashes (my phone would normally have crashed by now), cleared databases and no crash.
Also while I was in there, two programs I uninstalled via the system tray (menu button, edit, uninstall) that kept coming back were a buld.prop editor and some wonkey game (Fall down) or something, anyway those were in the downloaded section of task manager and I uninstalled them through there. Maybe that did it?
And no... still freeze, reboot and not saving any changes.
So far I've also tried uninstalling practically everything I installed and those changes aren't persisting (the uninstalled apps remain uninstalled, but reappear in the system tray or on the home screen if I had an icon there for it).
No changes I make to anything persist except things I save or copy to the SD card.
Tried factory reset again, still didn't stick.
So apparently SOME others have this issue without rooting, I can't tell, there's not a ton of reviews that I can find beyond "F*** STRAIGHT TALK CUSTOMER SERVICE THIS PHONE IS CRAP".
I hate to keep bumping this, but every time I have an issue, I am highly detailed in things and I NEVER EVER have EVER gotten a response EVER on this site, EVERRRRRRRRRRRRRR.
I really really really don't want to waste another ~$200 for nothing.
I would appreciate even a response of "yeah I have this problem too".
I don't want this to die like all the other threads I started...
Does anyone even have a clue as to where I can begin attempting to troubleshoot this on my own then?
What tools should I look into or what logs in what folders?
I know this post is very outdated but there may still be someone tinkering with these older phones still as I am.
Over the past few days I have been trying to get this Straight Talk Samsung Galaxy Proclaim rooted and working just for something to do.
I'm not one to ask for help to often so I end up doing a lot of reading and a lot of trial / error.
In my reading I have seen quite a few posts / comments around the net stating not to use the Shabbypenguin root method
as it is very buggy and unstable.... I can not tell you from experience so please do not quote me. I ended up using the TeamProlusion
root method and all has went very well other than a few minor problems I need to work out.
In all honesty I'm not real sure what I may post or may not.... ( Yes I need to REread the rules for sure ) but I
will leave this link for anyone that may be in need... Mods / Admins please feel free to edit this post if this is not permitted and
please accept my apologies.
Please google androidarea51