Related
Hi all,
Is it normal for wifi to drain 1% every 5-10 mins on standby? Where as when I'm on 2g mobile data I get 40-45mins for every 1%. I've investigated this for 6 hours and it consistently shows the same result.
My setup:
Same Apps and setup. Wifi Cisco E3000 and 20 feet away from my room.
I also placed my phone 6feet away and still get the same batt drain.
I get a 120-190mah as per batterymonitor app on wifi and only 20-30mah on 2g
Thouhts?
My battery consumption on a 2.3.4 XXKG3 rooted S2, without Samsung crap:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Check your running services, you will know rightaway what is killing your battery.
Yes, that is possible. It all depends on your situation. For some people mobile data drains more battery then wifi. And for some wifi drains more then mobile data.
Nothing to worry about.
yqed said:
My battery consumption on a 2.3.4 XXKG3 rooted S2, without Samsung crap:
Check your running services, you will know rightaway what is killing your battery.
Click to expand...
Click to collapse
How the heck can your battery last that long? I barely touched my phone and its down to 50 in hours. Does it matter if I'm on KH3? I live in Nz but imported my phone I think from Taiwan or hk. Will I be able to use KG3?
WiFi drains battery if it is continually searching for a signal when non is present i find .
jje
I prefer to use wifi when possible just because the battery consumption is less than 3G.. i remember one time I forgot the phone at night with wifi turned on and connected, after 7-8 hours i had lost only 2%
I leave wifi and data both turned on, all the time. That way it just uses whatever's available and I don't have to worry about it. With very minimal use (only a few calls and a handful of SMS) I can get 4 days out of my phone. I have a tablet and am usually in front of a PC, so the phone rarely gets used as anything more than a phone!
Anyway, wifi is not your issue. Have you looked into freezing the wifi sharing app? (You don't have to actually be sharing wifi for this to be a relevant thing to do!)
JJEgan said:
WiFi drains battery if it is continually searching for a signal when non is present i find .
jje
Click to expand...
Click to collapse
this is correct, if you have a good Wi-Fi signal the battery drain should be les than 3G but if not then it's gonna be worse.
thanks for the rep guys. I notice that my wifi scans continuously eventhough its using my home network. It's like scanning every 20 secs or so. Ss that normal?
With regards to Apps, and I've frozen everything I can think of that might cause a drain like beautiful widget, setting all my snyc to manual except my google account. I don't receive too much push email. I've frozen the usual culprits like wifi sharing/manager, all samsung Apps, disable fast dormancy, disable auto backup by google.
3 hours ago I frozen juicedefender and when I checked batt still drained 1% 5-15mins.!!! I'm now trying viber frozen.
I'm running out of Apps to freeze!
Is it possible that my phone drains more batt by using wifi N? Btw, as my first post says I already tried to put my phone closer to my router and I still get the same drain. Damn!!!
---------- Post added at 11:40 PM ---------- Previous post was at 11:35 PM ----------
Does having kh3 have anything to do with it? If I change modems will I benefit from it? Could it be rom related - I remember when I first rooted I was on lp and I think the batt was better. I'm now on cog1. 5.1. But I'd imagine it's more of the kernel
Edit: I forgot to mention that I'm getting 60-80% Android OS
Kepster said:
thanks for the rep guys. I notice that my wifi scans continuously eventhough its using my home network. It's like scanning every 20 secs or so. Ss that normal?
With regards to Apps, and I've frozen everything I can think of that might cause a drain like beautiful widget, setting all my snyc to manual except my google account. I don't receive too much push email. I've frozen the usual culprits like wifi sharing/manager, all samsung Apps, disable fast dormancy, disable auto backup by google.
3 hours ago I frozen juicedefender and when I checked batt still drained 1% 5-15mins.!!! I'm now trying viber frozen.
I'm running out of Apps to freeze!
Is it possible that my phone drains more batt by using wifi N? Btw, as my first post says I already tried to put my phone closer to my router and I still get the same drain. Damn!!!
---------- Post added at 11:40 PM ---------- Previous post was at 11:35 PM ----------
Does having kh3 have anything to do with it? If I change modems will I benefit from it? Could it be rom related - I remember when I first rooted I was on lp and I think the batt was better. I'm now on cog1. 5.1. But I'd imagine it's more of the kernel
Edit: I forgot to mention that I'm getting 60-80% Android OS
Click to expand...
Click to collapse
Personally, I kept it short and simple. I flashed the XXKG3 generic ROM that is compatible with my Bell distributor then I installed CF-Root and started to uninstall the apps, not "freezing" them (no idea why is called freeze, as the command is "# pm disable PACKAGE").
I use Wifi N with a Cisco E4200 DD-WRT (phone at 20") as well Beautiful Widgets and I never disabled any of the system services you mentioned in your post, you should NOT play with them. You are trying blindly to see if you improve your battery when in fact you are hurting it by killing processes that are needed by system apps (there is your drain). And Juice Defender saves you a bit of battery than use it on its app... not a big advantage. Just start from fresh with a stock ROM and clean your way up, the right way... don't just disable/uninstall what you "think" it might help. And stop installing "optimization" apps, how do you know they actually help if you do not monitor them? Get your system cleaned first, then start installing one app at the time while checking the stats available in your OS, not some fancy app. DocRambone posted a very good list, related to safe applications to be removed. Did you looked at that list? Personally, I uninstalled only half of them.
These are my running services:
Code:
PID USER VSZ STAT COMMAND
1 root 508 S /init
2 root 0 SW [kthreadd]
3 root 0 SW [ksoftirqd/0]
4 root 0 SW [migration/0]
5 root 0 SW [watchdog/0]
9 root 0 SW [events/0]
11 root 0 SW [khelper]
15 root 0 SW [async/mgr]
16 root 0 SW [pm]
19 root 0 SW [suspend]
20 root 0 SW [sync_system_wor]
151 root 0 SW [s5p-tmu]
337 root 0 SW [sync_supers]
339 root 0 SW [bdi-default]
341 root 0 SW [kblockd/0]
356 root 0 SW [khubd]
359 root 0 SW [kseriod]
394 root 0 SW [irq/331-max8997]
434 root 0 SW [kmmcd]
527 root 0 SW [kondemand/0]
540 root 0 SW [pet_watchdog/0]
549 root 0 SW [khungtaskd]
550 root 0 SW [kswapd0]
599 root 0 SW [aio/0]
612 root 0 SW [crypto/0]
1237 root 0 SW [sec_jack_wq]
1240 root 0 SW [irq/350-sec_hea]
1245 root 0 SW [spi_gpio.3]
1262 root 0 SW [svnet_txq]
1274 root 0 SW [file-storage]
1300 root 0 SW [irq/328-mxt224_]
1306 root 0 SW [irq/325-k3g]
1312 root 0 SW [irq/326-proximi]
1315 root 0 SW [cm3663_light_wq]
1316 root 0 SW [cm3663_prox_wq]
1366 root 0 SW [mali_dvfs]
1369 root 0 SW [mali-pmm-wq]
1378 root 0 SW [sii9234_wq]
1379 root 0 SW [irq/481-mhl_int]
1380 root 0 SW [irq/496-mhl_wak]
1383 root 0 SW [irq/343-max1704]
1394 root 0 SW [kstriped]
1396 root 0 SW [kmpathd/0]
1398 root 0 SW [kmpath_handlerd]
1399 root 0 SW [ksnapd]
1400 root 0 SW [kconservative/0]
1414 root 0 SW [ktflash_requlat]
1429 root 0 SW [usbhid_resumer]
1432 root 0 SW [binder]
1441 root 0 SW [irq/333-IPC_HOS]
1452 root 0 SW [mmcqd]
1481 root 0 SW [l2cap]
1482 root 0 SW< [krfcommd]
1488 root 0 SW [dynamic hotplug]
1501 root 0 SW [melfas_touchkey]
1506 root 0 SW [fimc0_iqr_wq_na]
1509 root 0 SW [fimc1_iqr_wq_na]
1512 root 0 SW [fimc2_iqr_wq_na]
1515 root 0 SW [fimc3_iqr_wq_na]
1518 root 0 SW [hdcp work]
1529 root 0 SW [tvout resume wo]
1535 root 0 SW [sec-battery]
1538 root 384 S /sbin/ueventd
1761 root 0 SW [Si4709_wq]
1782 root 0 SW [jbd2/mmcblk0p9-]
1784 root 0 SW [ext4-dio-unwrit]
2563 root 0 SW [jbd2/mmcblk0p7-]
2564 root 0 SW [ext4-dio-unwrit]
2566 root 0 SW [jbd2/mmcblk0p1-]
2567 root 0 SW [ext4-dio-unwrit]
2570 root 0 SW [jbd2/mmcblk0p10]
2571 root 0 SW [ext4-dio-unwrit]
2579 system 868 S /system/bin/servicemanager
2580 root 6616 S /system/bin/vold
2581 system 1972 S /system/bin/notified_event
2583 root 732 S /system/bin/debuggerd
2584 radio 9512 S /system/bin/rild
2585 system 4624 S /system/bin/npsmobex
2586 system 8476 S /system/bin/drexe
2590 bluetoot 1372 S /system/bin/dbus-daemon --system --nofork
2591 root 932 S /system/bin/installd
2592 keystore 1804 S /system/bin/keystore /data/misc/keystore
2594 system 14192 S /system/bin/tvoutserver
2595 shell 800 S /system/bin/sh /system/bin/rtc_log.sh
2612 shell 780 S /system/bin/immvibed
2907 wifi 2644 S /system/bin/wpa_supplicant -Dwext -ieth0 -c/data/wifi/bcm_su
3374 media 56536 S < /system/bin/mediaserver
3375 root 15472 S /system/bin/netd
3376 root 126m S zygote /bin/app_process -Xzygote /system/bin --zygote --star
3391 system 276m S system_server
3496 root 0 SW [iscan_sysioc]
3497 root 0 SW [dhd_watchdog]
3498 root 0 SW [dhd_dpc]
3499 root 0 SW [dhd_sysioc]
3502 system 152m S com.android.systemui
3511 app_99 168m S com.sec.android.inputmethod.axt9
3521 radio 155m S com.android.phone
3522 app_66 148m S android.process.media
3528 app_53 134m S com.sec.pcw.device
3532 system 134m S com.samsung.bt.avrcp
3536 bluetoot 134m S com.broadcom.bt.app.system
3544 app_12 176m S com.sec.android.app.twlauncher
3604 app_54 173m S com.google.process.gapps
3631 app_12 148m S android.process.acore
3688 app_84 135m S com.sec.android.app.FileTransferManager
3777 app_36 137m S com.sec.android.widgetapp.weatherclock
3927 app_38 136m S com.sec.android.widgetapp.apnews
4193 app_91 137m S com.sec.android.app.clockpackage
4220 app_16 137m S com.android.providers.calendar
4234 app_100 134m S com.sec.android.daemonapp.accuweather
4255 app_78 159m S com.google.android.gm
4333 app_81 174m S com.cooliris.media
4366 app_119 144m S com.google.android.apps.reader
4376 app_103 170m S com.levelup.beautifulwidgets
4435 app_37 138m S com.sec.android.widgetapp.stockclock
4453 app_16 138m S com.android.calendar
4476 system 156m S com.android.settings
4486 app_112 177m S com.google.android.music
4633 app_82 137m S com.sec.android.app.fm
4752 app_40 135m S com.sec.android.app.samsungapps.una
6623 app_68 185m S < com.google.android.apps.maps
9014 dhcp 916 S /system/bin/dhcpcd -ABK eth0
10732 graphics 139m S com.sec.android.app.screencapture
11958 system 138m S com.wssyncmldm
11989 system 135m S com.sec.android.providers.drm
11997 app_1 139m S com.smlds
12037 app_102 139m S com.skype.raider
13094 app_5 141m S jackpal.androidterm
13136 app_115 135m S com.noshufou.android.su
13170 app_68 149m S com.google.android.apps.maps:NetworkLocationService
13180 app_68 144m S com.google.android.apps.maps:FriendService
13503 app_83 141m S com.sec.android.app.FileTransferServer
13579 root 0 SW [flush-179:0]
13646 shell 1684 S /sbin/ext/busybox sh /sbin/sleep 3600
13651 shell 1676 S /sbin/ext/busybox /sbin/sleep 3600
13707 app_68 154m S com.google.android.apps.maps:HotpotService
13788 system 135m S com.android.MtpApplication
13825 app_5 796 S /system/bin/sh -
13858 root 796 S sh -
13966 root 1684 S /sbin/ext/busybox sh /sbin/ps
13971 root 1716 R /sbin/ext/busybox /sbin/ps
Compare it with yours and see what is running extra. Here are the visual running services and my battery after 29hrs (just for reference, the proper way is to look into a terminal):
I will do what you said bro and start from scratch! Never thought I'm actually causing more drain by disabling some Apps! One more question bro. Which Apps did you remove from the list?
Thanks again!
Certain routers are known to drain battery life on our SGS2s. I'm fairly certain some D-Link routers are known offenders in this regard. I can't be certain about you're router, but if you have access to different wifi connections, you should do a little testing.
Fiddling about in your router settings and upgrading your router firmware may help.
I'd link the threads where I came across the info, but I can't seem to find them atm.
Kepster said:
I will do what you said bro and start from scratch! Never thought I'm actually causing more drain by disabling some Apps! One more question bro. Which Apps did you remove from the list?
Thanks again!
Click to expand...
Click to collapse
DocRambone's list is very helpful. Technically, you can remove all that list and it won't cause any issues to your phone. However, I wanted to keep some of the apps like the NDLA, Analog Clock (for alarms), Memo, etc. Just go with your usage and uninstall what you think you will never use. Is always easier to remove it later, instead of putting it back. I don't remember exactly which apps I uninstalled (not disabled), I did it the hard way through terminal.
Many people recommended Titanium but I feel much more comfortable to see what is going on. SystemApp Remover is very good alternative to Terminal, IMO.
Here it is a list of the package manager commands:
Code:
# pm
usage: pm [list|path|install|uninstall]
pm list packages [-f] [-d] [-e] [-u] [FILTER]
pm list permission-groups
pm list permissions [-g] [-f] [-d] [-u] [GROUP]
pm list instrumentation [-f] [TARGET-PACKAGE]
pm list features
pm list libraries
pm path PACKAGE
pm install [-l] [-r] [-t] [-i INSTALLER_PACKAGE_NAME] [-s] [-f] PATH
pm uninstall [-k] PACKAGE
pm clear PACKAGE
pm enable PACKAGE_OR_COMPONENT
pm disable PACKAGE_OR_COMPONENT
pm setInstallLocation [0/auto] [1/internal] [2/external]
The list packages command prints all packages, optionally only
those whose package name contains the text in FILTER. Options:
-f: see their associated file.
-d: filter to include disbled packages.
-e: filter to include enabled packages.
-u: also include uninstalled packages.
The list permission-groups command prints all known
permission groups.
The list permissions command prints all known
permissions, optionally only those in GROUP. Options:
-g: organize by group.
-f: print all information.
-s: short summary.
-d: only list dangerous permissions.
-u: list only the permissions users will see.
The list instrumentation command prints all instrumentations,
or only those that target a specified package. Options:
-f: see their associated file.
The list features command prints all features of the system.
The path command prints the path to the .apk of a package.
The install command installs a package to the system. Options:
-l: install the package with FORWARD_LOCK.
-r: reinstall an exisiting app, keeping its data.
-t: allow test .apks to be installed.
-i: specify the installer package name.
-s: install package on sdcard.
-f: install package on internal flash.
The uninstall command removes a package from the system. Options:
-k: keep the data and cache directories around.
after the package removal.
The clear command deletes all data associated with a package.
The enable and disable commands change the enabled state of
a given package or component (written as "package/class").
The getInstallLocation command gets the current install location
0 [auto]: Let system decide the best location
1 [internal]: Install on internal device storage
2 [external]: Install on external media
The setInstallLocation command changes the default install location
0 [auto]: Let system decide the best location
1 [internal]: Install on internal device storage
2 [external]: Install on external media
For some reason I couldn't upload screen capture photos of my usage our lack thereof but basically with minimal apps installed I still get a drain from 100 to 76% in 6 hours over wifi-with 2 signal bars. Android os 91%, display 8%, cell standby 5%, idle 3%.
Checked running apps and saw fotaclient, fb, drm, Settings, maps, viber, setcpu, go launcher, syncimds, google services, voice command. I'm assuming this are normal background apps. I've got a strong feeling that my router doesn't like my phone. I will try to keep my pyotr idle but this time on data connection
Sent from my GT-I9100 using XDA App
Problem solved! It was indeed my e3000 that's causing the excessive drain! I just separated my 2.4 and 5ghz signal and voila! After 8 hours out only drained 8%! Woohoo!
Sent from my GT-I9100 using XDA App
Some users had reported wifi drain for KH3 radio. When i was on stock 2.3.3, freezing wifi sharing, wifi sharing manager and switching to KG5 modem did the trick. KH3 also caused higher battery temp when compared to Kg5...
Kepster said:
Problem solved! It was indeed my e3000 that's causing the excessive drain! I just separated my 2.4 and 5ghz signal and voila! After 8 hours out only drained 8%! Woohoo!
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Just to add, I see you are on 2Degrees, I get higher drain on my 2Degrees than my Vodafone...whilst I suspect that 2Degrees have weak reception in my area, and usually runs on 2G, I presume the phone is still searching for 3G network...hence uses more power. Just out of curiousity did you buy your SGS2 from Vodafone or Telecom? Chur.
droidphile said:
Some users had reported wifi drain for KH3 radio. When i was on stock 2.3.3, freezing wifi sharing, wifi sharing manager and switching to KG5 modem did the trick. KH3 also caused higher battery temp when compared to Kg5...
Click to expand...
Click to collapse
I confirm that XXKH3 drains faster the battery compared to XXKG3, but look at the GPS gains... whoaaa, pinpoint location in less than 3 seconds with a 5meters accuracy. Really happy to finally use my GPS properly, it is worth the increased battery drain. From my tests, the new firmware decreased the battery life by about 4 hours... I can live with that, in exchange of a great GPS.
Yeah GPS locking was brilliant in KH3... But i use wifi and data connection more, than GPS. KH3 drained more battery on standby also. May be it's causing more wakelocks...
Hi Galaxy SII gurus
I run "intratech" 'official stock firmware' with corresponding
"cf-root", I have done so for various gingerbread and I am doing now
for various ICS.
currently
GT-I9100_XEN_I9100XWLPD_I9100XXLPW_I9100XENLP5.tar.md5
CF-Root-SGS2_XX_NEE_LPD-v5.5-CWM5.zip
Once system is stable it runs stable for days/weeks, -but-, my
problem (as also mentioned in xda thread 1635302) is that, when I boot
(this problem has been there with gingerbread and is still there with
ICS):
- system_server uses CPU (load and temperature rise)
- watchdog kills android processes (linux kernel stays up)
and, this goes on in a loop, often for hours. I need to power off and
try again (say, next day when battery again charged and temperature
dropped).
Only with -much- luck it happens that the system boots to a cam
state. and then I can use the phone normally. In fact, it works
perfectly then.
Recently this problem seems to become more prevalent and I have not
been able to use the phone for several days (each time I boot it goes
into, and, not out of, the watchdog loop). In practice, what happens
is that
- all applications (including launcher die)
- system goes back to the animated samsung logo
this loop goes on.
I searched a bit and it seems other people have reported this too but
I don't find a solution. Any help is appreciated.
'top', right after boot
Mem: 824396K used, 26136K free, 0K shrd, 36632K buff, 250616K cached
CPU: 53.1% usr 0.9% sys 0.0% nic 45.7% idle 0.0% io 0.0% irq 0.0% sirq
Load average: 2.84 1.85 0.74 2/1595 6055
PID PPID USER STAT VSZ %MEM CPU %CPU COMMAND
2082 1830 system S 401m 48.2 0 52.4 system_server
5628 1830 app_208 R 297m 35.8 0 0.5 berserker.android.apps.sshdroidpro
...
I use ssh and rsync to backup to a linux server, so I have a some
files that may be of interest (note that ssh and rsync are not killed
so I can incrementally backup).
/data/log/ contains a file
-rw------- 1 1000 1000 677553 Jun 5 06:07 dumpstate_sys_watchdog.txt.gz
/data/system/dropbox/ -many- files (presumably one per loop)
-rw------- 1 1000 1000 14416 Jun 5 06:07 [email protected]
-rw------- 1 1000 1000 0 Jun 5 06:08 [email protected]
-rw------- 1 1000 1000 261 Jun 5 06:08 [email protected]
for example, I have these files 58 times on 'Jun 5 ' only.
I have captured dmesg and logcat in a file screenlog.txt as follows
- freshly booted phone
- do a first 'dmesg'
- start 'logcat'
- start google play market app and update 2 apps
**** watchdog ****
- wait a bit
- do another 'dmesg'
The information is somewhat overwhelming but one can 'grep' for
watchdog, temperature and system_server processes 2082 and 7102, and
what else..., like, it seems cpu1 turns off/on all the time after
watchdog. Also, sorting the logs gives nice view per category.
Again any help is appreciated!
Thanks
Hi everybody
I feel a bit ashamed to reply my own post, but, here is what I can say
about progress:
I have (in approximately one week) once been able to get a 100% stable
system, but then, after some hours/day of playing around, time came to
reboot, and, since then, I am in the same system_server watchdog loop
for days now: I can do a little bit of work (I am configuring apex
GIU) and then: 'the watchdog barks'.
Searching Google does not tell me enough about this system_server
watchdog boot loop situation, so I hope for rescue here.
Note that I use stock rom with just cf-root.
have a good weekend
ok then, hate to reply again ...
seems a cwm wipe of dalvik cache and regular cache can do wonders:
I booted into stable system again
spoke too soon :-( android boot loop again
here is my guess: I think SD card might have errors ...
final verdict: only complete wipe and reinstall works, (and it works)
however, having literally wiped and formatted nearly everything, ...
only heimdall could flash (others did no longer recognise GSII).
all runs well now (albeit with less apps and less data)
Hello folks! how are you doing?
Since we've seen Alpha kernel is still an alpha and we need to provide developers with every detail of our device we can.
I've decided to search through threads and get some commands from there to gather the information required:
You can gather these data by downloading Terminal Emulator from the market or by properly installing Google SDK and doing an adb shell then running the commands.
If commands do not seem to work at first glance, please reboot the phone then try again running the commands below.
Edit 1:
For all the people having problems not mentioned on the bug list, please report the problems in this spreadsheet
https://docs.google.com/spreadsheet/ccc?key=0AkQTVc3TvAUxdFNBOWFFRzNneWRHcW56MEtLVGJqdVE#gid=0
There are several sheets to fill with the mentioned problems
Edit 2:
For all users who might have problem gathering Tegra Revision, Speedo ID, CPU Process, Core Process; please install leaked rom / AtrICS, reboot and try searching again.
Else; please send me the dmesg command output via PM and I'll upload the results.
Please note that I'll discard dmesg from kernels that are not the leaked and/or 3.1
---
Identify Memory type:
Grab a terminal then run after a reboot
Code:
su -
dmesg | grep LPDDR2
Types of Memory
LPDDR2 MR5: 0x0003 (0x0303) = Elpida (Manufactuer)
LPDDR2 MR6: 0x0000 (0x0000) \
LPDDR2 MR7: 0x0000 (0x0000) / = 50nm
LPDDR2 MR8: 0x0054 (0x5454) = 1GB
LPDDR2 MR5: 0x0003 (0x0303) = Elpida (Manufactuer)
LPDDR2 MR6: 0x0001 (0x0101)\
LPDDR2 MR7: 0x0000 (0x0000)/ = 40nm
LPDDR2 MR8: 0x0054 (0x5454) = 1GB
LPDDR2 MR5: 0x0006 (0x0606) = Hynix (Manufacuter)
LPDDR2 MR6: 0x0000 (0x0000)\
LPDDR2 MR7: 0x0000 (0x0000)/ = 54nm (Note that this is still 54nm for MR7 = 0x0001 (0x0101))
LPDDR2 MR8: 0x0054 (0x5454) = 1GB
---
Identify which Panel Type do we have:
After a fresh reboot
Grab a terminal
Code:
su -
dmesg | grep atag
or
Code:
su -
dmesg | grep panel
Examples:
Code:
dmesg | grep atag
mot_parse_atag_motorola: panel type: 0x80000740
or
Code:
dmesg | grep panel
<6>[ 0.000000] parse_tag_motorola: panel_size: 0x740
---
Identify Tegra Revision:
Code:
su -
dmesg | grep Tegra
then search for something similar to
Code:
"Tegra Revision: AXX prime"
---
Well, let's see if we can help Atrix Kernel Team to improve the kernel with this useful information
Also, if anybody would like to contribute showing how to gather more data; that'd be awesome and I'll edit this post
Thanks guys, have a good day!
You are the man!!!....good work my friend...:good:
Thanks for this.
Thanks
This is super helpful. Now if I can just get my post count up high enough to post to dev forums....
Types of Memory
LPDDR2 MR5: 0x0003 (0x0303) = Elpida (Manufactuer)
LPDDR2 MR6: 0x0000 (0x0000) \
LPDDR2 MR7: 0x0000 (0x0000) / = 50nm
LPDDR2 MR8: 0x0054 (0x5454) = 1GB
Identify which Panel Type do we have:
dmesg | grep panel
<6>[ 0.000000] parse_tag_motorola: panel_size: 0x740
However, using command: "dmesg | grep Tegra" doesnt give me anything close to any revision information.
Seems like you ran dmesg a little too late. You need to run it as soon as possible upon bootup.
ravilov said:
Seems like you ran dmesg a little too late. You need to run it as soon as possible upon bootup.
Click to expand...
Click to collapse
Is it supposed to be a capital T in tegra? I rebooted several times and get the same stuff every time
I tried dmesg | grep revision
and got this:
CPU: ARMv7 Processor [411fc090] revision 0 (ARMv7), cr=10c53c7d.
vintage47 said:
Is it supposed to be a capital T in tegra? I rebooted several times and get the same stuff every time
Click to expand...
Click to collapse
No idea, but you can use grep -i Tegra, that should make capitalization irrelevant.
Solved, I was looking on dmesg from old kernel
--------------------------------------------------------------------------------------------------------------------------
Hello,
how I find the Tegra Revision, Speedo ID, CPU Process, Core Process that request Kristianp in my dmesg? I am stupid or it show diferent?
best regards,
Ferenc.
I cant find the tegra revision either. I can see the first thing in the log, but not the tegra revision.
Do after a fresh reboot in leaked kernel and Rom ( 10.1 epinter is mine)
Reboot when SD Card is present
Dear JhonnyX:
As I cannot write in the Google Docs Spreadsheet, please find the information from my Atrix Below. The Bug is the reboot when entering deep sleep with SD card inserted.
Sorry but I could not find my Atrix Revision on the early dmesg.
Best regards
Javier
ingelectronico said:
Dear JhonnyX:
As I cannot write in the Google Docs Spreadsheet, please find the information from my Atrix Below. The Bug is the reboot when entering deep sleep with SD card inserted.
Sorry but I could not find my Atrix Revision on the early dmesg.
Best regards
Javier
Click to expand...
Click to collapse
PM'ed you regarding the missing info
Also, users who might have spreadsheet access problem, please let me know via PM.
new fields
I want to add my info on the modem drops spreadsheet.
How do I find what values my phone has for these fields?
Speedo ID
CPU Process
Core Process
CPU governor
Connect the phone to usb and activate adb. Reboot. As soon as finished reboot, use adb shell and type dmesg > /mnt/sdcard/dmesg.txt
Now search that file.
This has been answered many tines before.
Next time use search
Enviado desde mi MB860 usando Tapatalk 2
Hello all,
I got a Sony Xperia P (LT22i) last christmas and I have been using a freexperia built ROM ever since. The ROM uses a Cyanogenmod 4.0.4 internally. Unfortunately my phone is often quite slow to respond to user input up to the point where it doesnt even unlock the screen when I press the button. If I use htop via adb I see the following:
Mem: 798852K used, 21644K free, 0K shrd, 17748K buff, 306296K cached
CPU: 56.3% usr 38.9% sys 2.9% nic 0.5% idle 0.0% io 0.0% irq 1.1% sirq
Load average: 5.29 5.61 5.30 4/690 6823
PID PPID USER STAT VSZ %VSZ %CPU COMMAND
4063 4010 system S 384m 47.7 90.1 system_server
791 2 root SW 0 0.0 3.9 [kworker/0:2]
6323 4010 app_66 S 330m 41.0 3.2 net.osmand
3 2 root SW 0 0.0 0.3 [ksoftirqd/0]
1536 1 system S 62044 7.5 0.2 /system/bin/surfaceflinger
863 2 root SW 0 0.0 0.2 [mmcqd/1]
4962 4927 root R 1900 0.2 0.1 top
10 2 root SW 0 0.0 0.1 [ksoftirqd/1]
6212 2 root SW 0 0.0 0.1 [kworker/0:0]
1667 1 root S 5512 0.6 0.1 /sbin/adbd
840 2 root SW 0 0.0 0.1 [kworker/u:4]
3666 2 root SW 0 0.0 0.1 [kworker/u:5]
591 2 root SW 0 0.0 0.1 [av8100_thread]
6590 2 root SW 0 0.0 0.1 [kworker/1:2]
5130 4010 app_65 S 345m 42.8 0.0 {ockplus.android} org.adblockplus.andr
4306 4010 app_41 S 322m 40.0 0.0 {enmod.trebuchet} com.cyanogenmod.treb
4263 4010 app_46 S 318m 39.5 0.0 {e.process.gapps} com.google.process.g
4340 4010 radio S 310m 38.5 0.0 {m.android.phone} com.android.phone
5787 4010 app_64 S 303m 37.7 0.0 {android.youtube} com.google.android.y
5712 4010 system S 302m 37.6 0.0 {ndroid.settings} com.android.settings
The system_server seems to use up the entire CPU time causing my problems. Is there a way to fix the problem, if yes, who would I talk to about this?
Alternatively I would like to use another ROM. I have heard that my device has some quirks making it very hard to use most ROMs (most notably a broken audio driver?). For this reason I originally chose the freexperia builds despite the fact that that android version is not exactly up-to-date.
Is there another ROM that will work properly with my device?
Also I would like to know how to back up the relevant data: When I installed the current ROM, android wouldn't start until I reset the device and wiped the data in the process. I dislike every kind of backup that uses "the cloud" for obvious reasons. I just want to copy the data onto my laptop via USB (without using an App, free or not). I tried using "adb backup" but I am not sure which options I have to select to obtain the relevant data without having a >> 1 GB size BLOB on my laptop. Any ideas about that?
You would have more luck looking in your device specific subforum instead of general area.
http://forum.xda-developers.com/xperia-u
Hello!
My Nord 2 will be plugged in 24/7 because I use it for E2E testing. I need to optimize battery so it wont swell up.
Is there any working solutions for doing it? Or is there a way to put battery charging to idle so main power will be drawn from usb.
I tried Magisk ACC plugin, but it seems it is not running. Shell has supperuser power on magisk
ADB shell:
"acc
/system/bin/sh: <stdin>[2]: acc: inaccessible or not found
accd,
/system/bin/sh: <stdin>[3]: accd,: inaccessible or not found"
Also same error in ACC app, magisk have given supperuser access for that app:
"/system/bin/sh: <stdin>[3544]: acc: inaccessible or not found"
when i execut acc.sh in /data/adb/vr25/acc/ folder then i cant get ACCD running there. Well it runs for a minut then turns off
"
Advanced Charging Controller v2021.8.31 (202108310)
Copyright 2017-2021, VR25
GPLv3+
(i) accd is not running
1) Language
2) All commands
3) Documentation
4) Start/restart daemon
5) Stop daemon
6) Export logs
7) Charge once to #%
8) Uninstall
9) Edit config.txt
a) Reset battery stats
b) Test charging switches
c) Check for update
d) Flash zips
e) Battery info
f) Exit
#? b
(!) Charger must be plugged to continue...
(i) Alright, this may take a minute or so...
(!) [/proc/mtk_battery_cmd/current_cmd 0::0 0::1 /proc/mtk_battery_cmd/en_power_path 1 0] won't work
(i) Press any key to continue..."
Hi, I'm the developer of acc.
Have you tried a slow charger or USB charging?
Refer to README > Troubleshooting.
This is a kernel/adapter issue.
Edit
Just noticed that you're not using the latest acc release.
Since you're facing issues, upgrading is a must.
Regardless, don't skip the documentation.
I am using PC USB connection for charging. Should ACC daemon allways run? It works for a minute and then stop. Do you mean oneplus nord 2 battery charging management have same kernel issue as you mentioned in ACC thread?
I have tested different versions to be sure. v2021.8.31 came from Magisk for first.
AccA is latest 1.0.35 Daemon/API 202109200
New ver.:
Advanced Charging Controller v2021.9.20 (202109200)
Copyright 2017-2021, VR25
GPLv3+
(i) accd is not running (PID 12046)
1) Language
2) All commands
3) Documentation
4) Start/restart daemon
5) Stop daemon
6) Export logs
7) Charge once to #%
8) Uninstall
9) Edit config.txt
a) Reset battery stats
b) Test charging switches
c) Check for update
d) Flash zips
e) Battery info
f) Undo upgrade
g) Exit
#? b
(!) Charger must be plugged to continue...
(i) Alright, this may take a minute or so...
(!) [/proc/mtk_battery_cmd/current_cmd 0::0 0::1 /proc/mtk_battery_cmd/en_power_path 1 0] won't work
This is usually a kernel and/or power adapter issue.
The daemon should be running to control charging.
The #1 reason for it to stop is total charging switch failure.
That is, all charging switches fail to respond.
In that case, it finds no reason to keep running.
Share a log archive (acc -le) and the output of acc -p.
Where can i get those logs? From /data/adb/vr25/acc-data/logs/ ? Might it be acc-logs-OP515BL1.tar.gz file?
Somehow "pull" and "cp" are not working on me with adb shell. Is there any better tools for pulling files and logs? There is many tools witch are not working with my phones and cant find root folders, google is to big.
@VR25 Hi! I attached all logs from ACC-data logs folder. Will it help?
CapnRene said:
@VR25 Hi! I attached all logs from ACC-data logs folder. Will it help?
Click to expand...
Click to collapse
Perfect!
I found potential charging switches.
Test the following commands one by one and report the ones that work:
su -c acc -t /sys/devices/virtual/oplus_chg/battery/mmi_charging_enable 1 0
su -c acc -t /sys/devices/platform/charger/enable_sc 0 1
su -c acc -t /sys/devices/platform/charger/enable_sc 1 0
su -c acc -t /sys/devices/virtual/oplus_chg/battery/stop_charging_enable 0 1
su -c acc -t /sys/firmware/devicetree/base/charger/usb_charger_current_suspend 0 1
Note
One/some of the commands may trigger a reboot.
That's not a big deal. Just move to the next on the list.
First line got response:
OP515BL1:/ # su -c acc -t /sys/devices/virtual/oplus_chg/battery/mmi_charging_enable 1 0
(!) Charger must be plugged to continue...
(i) Alright, this may take a minute or so...
(i) [/sys/devices/virtual/oplus_chg/battery/mmi_charging_enable 1 0] works
- battIdleMode=true
As i understand i need to change switch now to get it working?
su -c acc -s s="/sys/devices/virtual/oplus_chg/battery/mmi_charging_enable 1 0"
You should be all set after running that.
The next release will include the new switch.
Edit
Since the device will be plugged in 24/7, you may want to run `acc 3920` to set it up.
Essentially, this will keep the battery voltage between 3870-3920 millivolts.
3920 is said to be the sweet spot for longevity.
Not 100% sure did it work, need to test it a litte to be sure. It seems it updated log
OP515BL1:/ # su -c acc -s s="/sys/devices/virtual/oplus_chg/battery/mmi_charging_enable 1 0"
/system/bin/acc[580]: export: 1: is not an identifier
(i) Alright, this may take a minute or so...
(i) /data/adb/vr25/acc-data/logs/acc-logs-OP515BL1.tar.gz
My bad
It should have been
su
acc -s s="/sys/devices/virtual/oplus_chg/battery/mmi_charging_enable 1 0"
VR25 said:
My bad
It should have been
su
acc -s s="/sys/devices/virtual/oplus_chg/battery/mmi_charging_enable 1 0"
Click to expand...
Click to collapse
It worked! Ty! I set my swich to turn on 59% and off 60% for optimal ressult.
It seems that those are not working or maybe i have made some mistake somewhere:
shutdown capacity
charge current
charge voltage
CapnRene said:
It worked! Ty! I set my swich to turn on 59% and off 60% for optimal ressult.
It seems that those are not working or maybe i have made some mistake somewhere:
shutdown capacity
charge current
charge voltage
Click to expand...
Click to collapse
From the documentation:
# shutdown_capacity (sc) #
# When the battery is discharging and its capacity/voltage_now_millivolts <= sc and phone has been running for 15 minutes or more, acc daemon turns the phone off to reduce the discharge rate and protect the battery from potential damage induced by voltage below the operating range.
# sc=-1 disables it.
# [Beta] if the file /data/adb/vr25/acc-data/warn exists, accd posts Android shutdown warning notifications at sc + 5% or sc + 200 mV.
The last two features are not supported by all devices.
I'm yet to see a MediaTek device that supports at least one of the those.
Please ask further questions in the actual forum, so that other users can help you whenever I'm unavailable.