Related
Seems like having SD card inserted causes high IOWait.
User 1%, System 3%, IOW 95%, IRQ 0%
User 5 + Nice 0 + Sys 10 + Idle 0 + IOW 291 + IRQ 0 + SIRQ 0 = 306
Currently running smsBackup+ that restores sms messages from Gmail (1 message in 4 sec)
This also seems to cause reported installation issues:
(thread http://forum.xda-developers.com/showthread.php?t=926507)
Installed several times myself... waited up to 0.5 hour.. still splash screen.
Several processes (com.android.phone, etc) got "Force" or "Wait" messages.
Only after connecting ADB console was i able to see that android was still initializing.. waited for longer and in the end ~1 - 1.5 hours phone booted up.
Are you affected? .. Try removing SD card.. does HD2 boot up within 10 min.? .. then probably you have the same issue.
(not really usable with no SD card.. settings are lost on each boot)
This is discussed very often in the developing thread that you already mentioned: Dev Thread
The first time it needs a lot of time - in my case it was more then one hour before the splash screen was away - for the FCs just press the "Wait" button and wait - after the first time it will become less and less and the device will work quite fast (just the known bugs are still there).
Some people told that they had to wait for 2 or one even for 4 hours before the splash screen was away. I had very strong problems with installing and it did not disappear after 6 hours.
If you have that try the following:
1.) data wipe
2.) d-cache wipe
3.) starting in MAGLDR
4.) USB flasher / DAF.exe
5.) recovery menu / cwm partition sd card (1024/0M)
6.) mounting and transfering .zip
7.) install .zip
8.) reboot
hope i got you right
Here is the autobrightness FIX that should work on any deodexed JVP based ROM (NOT on stock).
Maybe not on some custom kernels - I have not found one yet, but just to warn you
[EDIT]: I've updated the zip with dependant twframework.apk. Now it should work.
HOW TO INSTALL:
- put the zip on your SD card
- Go to recovery (should be CWM compatible)
- install zip from your SD card
- ENYJOY!
With this fix you'll have 5 auto brightness levels.
I've set the following settings that work best for me (and my phone's HW).
5 - at dark (sensor level lower than 20)
35 - inside low light (sensor level lower than 330)
75 - inside at normal light (sensor level lower than 650)
155 - inside at daylight or outside when cloudy or getting darker (sensor level lower than 2610)
255 - outside at daylight (sensor level greater than 2610)
You can monitor the sensor level and changed backlight values with logcat.
I've done the fix based on information from this thread: http://forum.xda-developers.com/showthread.php?t=1130336 (thanks to Lukiqq)
Here are my values in framework-res.apk\res\values\arrays.xml
Code:
<integer-array name="config_autoBrightnessLevels">
<item>20</item>
<item>330</item>
<item>650</item>
<item>2610</item>
</integer-array>
<integer-array name="config_autoBrightnessLcdBacklightValues">
<item>5</item>
<item>35</item>
<item>75</item>
<item>155</item>
<item>255</item>
</integer-array>
Applied this to Stock JVP on K15H-T12 with Jkay theme, entered reboot loop, had to restore phone !!!!
gsw5700 said:
Applied this to Stock JVP on K15H-T12 with Jkay theme, entered reboot loop, had to restore phone !!!!
Click to expand...
Click to collapse
YOur phone is not actually on stock as you are using speedmod's kernel which is definitely a custom one...
When opener says: haven't found kernel that isn't compatible I think he has tried the most often used one like speedmod, voodoo and so on.
I tried it too with JVP and voodoo(stock samsung kernel just with ext4): doesn't work and messed up my battery symbol by somator and his gb mod. Had to reinstall the mod.
Think this thread here is not so useful as I thought.
OK, Was worth a go;-)
flypubec said:
Here is the autobrightness FIX that should work on any JVP based ROM (also on stock).
Click to expand...
Click to collapse
Services.jar in this package is deodexed, stock rom is odexed so it won't work on pure stock ROM. I've already made working package for stock ROM's with Lukiqq settings:
http://forum.xda-developers.com/showthread.php?p=14915073#post14915073
@Bo$s
Will my mod by Somator will be gone after applying ur fix?
I mean things like Battery icon and power menue?
greetz
EDIT: tried ur fix and have to say it didn't work too.
As I assumed all mods by Somator were gone.
Had only crashes and power menue was completely gone.
usefull
/install thanks
Works on my rom kitchen build of JVP with stock theme..
Only downside is that I actually like the stock battery but this comes with one of the % modded ones..
Marty
Bo$s said:
Services.jar in this package is deodexed, stock rom is odexed so it won't work on pure stock ROM. I've already made working package for stock ROM's with Lukiqq settings:
[...]
Click to expand...
Click to collapse
lukiqq so called fix is a bigmess, he is not aware what is he doing
i strongly advise not to use lukiqq fix
MasterJam882 said:
@Bo$s
Will my mod by Somator will be gone after applying ur fix?
I mean things like Battery icon and power menue?
greetz
EDIT: tried ur fix and have to say it didn't work too.
As I assumed all mods by Somator were gone.
Had only crashes and power menue was completely gone.
Click to expand...
Click to collapse
yes it will be gone as it uses same files - i am a bit bored so maybe i will do my version of this fix based on some other lib =) will think about it
but this fix looks way better then lukiqq one - if you cant wait use it
i can confirm, you have to be careful by using lukiqq's fix - but i don't think its totaly useless, because without his initial thoughts i wouldn't have come to an functional autobrighness result. (it didn't work well in stock-jvp)
i did my own research and i came to the conclusion that investigating the behaviour of sensors.default.só does the trick....(im combination with PROPER values in framework-res)
following both jvp-autobrightness-fix-threads i compared stock sensors.so, the one provided by darkky, the one provieded by lukiqq etc..... i realized that stock jvp-sensors (it doesn't matter which "release") floods my logcat (and/or it recognized only some light-ambients resulting in bright or dark - but nothing in between....)
the sensors.default.so provieded by lukiqqq (i guess, it was part of cm-files) recognize more.. 10-160-225-320-640-1280-2600-10240 i think so i started with that and edited my framework-res with that settings
Code:
<integer-array name="config_autoBrightnessLevels">
<item>640</item>
<item>1280</item>
<item>2600</item>
<item>10240</item>
</integer-array>
<integer-array name="config_autoBrightnessLcdBacklightValues">
<item>1</item>
<item>70</item>
<item>116</item>
<item>177</item>
<item>253</item>
</integer-array>
and feel quite good with it.....
(btw: i like the first line in lcdbacklightvalues! now don't need screenfilter anymore bacause its darker than setting the backlight to 0% )
@$omator: if you get a sensors.default.so with better/more/ recognized light-values as the one described above - please tell me!!
and OP maybe use cm7 lib, it should have 10 readings
10, 40, 90, 160, 225, 320, 640, 1280, 2600, 10240
Click to expand...
Click to collapse
still i was able to register 8 of them only - 40, 90 missing
//edit oh so you are using this one - so why not use all 8/10 values =)
//edit2 it was useless, lukiqq values are still a chaos not related much to sensor redings - he is like blindman on a narrow road - i am amazed that he compiled a kernel and let people test it - i would not risk blowing up my phone by this pyromaniac =)
okay, lets say there are 10 readings!
@edit:
i used only the last 4 values (so 5 settings alltogether) because i'm too lazy to patch my services.jar (i think its useless eyecandy with that 10 reading lib!)
i realized that readings 10, 40, 90, 160, 225, 320 are completely nonsense in daily use because the physical light-differents between 10 to 225 are sooo minimalistic imho!
does anyone know if the following scenario is possible: (according to a 10 reading restriction in lib [or kernel..i don't know if its also kernel realated stuff])
instead of using these values
10, 40, 90, 160, 225, 320, 640, 1280, 2600, 10240
the lib should be "forced" to use certain values like these
10, 160, 320, 640, 1280, 2600, 5200, 10240, 15000 (like in stock lib), 20480 (if thats still realistic..i dont like to travel to the sun for testing)
or maybe we could add readings so we get a lib with 20 or even more values (mmhh.. i would love to see a FLUENT change of brightness..so gimme 255 readings xD )
@edit2:
^^
i didn't test his kernel either but i read his topic and most of the pyro-testers were fine with it because of its list of features (including bln)
offtopic: i'm still on dark core, does speedmod have bln support yet?
have no idea - i see no sense in using kernels for 2.3.4 based on 2.3.3 sources mix that produces such bugs as front facing camera bug, brighteness and who knows what else - as for values well sure i see no point in using so much of them but it would be very cool to see smooth smooth changes in brighteness =) question is what is this sensors maximum reading possible, stepping is every 1 lux but the 3000 for max is a myth - even stock .so goes up to 100000 so thats probably the upper limit
@flypubec,
Thanks for pointing me in the right direction. Since, I am running non-stock kernel (Talon 0.31) and ROM (Criskelo v75 + Galaxy Blue theme), I knew your CWM zip file won't work, so finally decided to try my hand in decompiling the apk (from the theme).
However, after copying the .apk file to /system/framework (followed all the steps mentioned in the thread you had linked to, for copying the unsigned framework), after reboot, I am getting tons of reboots and force closes ..
@anyone,
Can someone tell me what the issue could be ? Is it because this method, won't work with themed apk's? If so, what is the alternative?
UPDATE :
Checked the logcat. The following is the error coming related to framework:
D/PackageManager( 1387): scanPackage : /system/framework/framework-res.apk
I/PackageManager( 1387): /system/framework/framework-res.apk changed; collecting certs
D/dalvikvm( 1387): GC_CONCURRENT freed 167K, 41% free 3843K/6407K, external 1710K/1988K, paused 2ms+3ms
D/dalvikvm( 1387): GC_FOR_MALLOC freed 389K, 43% free 4038K/6983K, external 1710K/1988K, paused 19ms
D/dalvikvm( 1387): GC_FOR_MALLOC freed 275K, 43% free 4094K/7111K, external 1710K/1988K, paused 18ms
D/dalvikvm( 1387): GC_FOR_MALLOC freed 349K, 42% free 4243K/7303K, external 1710K/1988K, paused 18ms
D/dalvikvm( 1387): GC_FOR_MALLOC freed 88K, 41% free 4339K/7303K, external 1710K/1988K, paused 19ms
D/dalvikvm( 1387): GC_CONCURRENT freed 253K, 35% free 4921K/7559K, external 1710K/1988K, paused 2ms+3ms
D/dalvikvm( 1387): GC_CONCURRENT freed 435K, 34% free 5507K/8327K, external 1710K/1988K, paused 2ms+3ms
W/PackageManager( 1387): Signature mismatch for shared user : SharedUserSetting{40551fa0 android.uid.system/1000}
D/PackageManager( 1387): scanPackage : /system/framework/twframework-res.apk
W/PackageParser( 1387): /system/framework/twframework-res.apk (at Binary XML file line #2): <manifest> specifies bad package name "touchwiz": must have at least one '.' separator
seems liek a typo in framework-res.apk ?
$omator said:
seems liek a typo in framework-res.apk ?
Click to expand...
Click to collapse
Thanks, for replying..
Seems like the, issue is persisting with the same error ,even after reapplying the theme. (getting the same error in logcat..)..
Is it possible that , the first time I applied this, there was some minor typo, after which none of the flashes, is solving the issue?
(I have tried pushing via adb, cwm and none of them is working?)
I guess, I'll have to reflash the ROM and see, if that works, and then probably continue from there..?
@Somator
Hey m8.
I'm very interested in tiny_gb_mod with brightness fix by you.
Do u think it will come soon?
This would be just awesome.
Thx and greetz
i think easiest way is to fix is to use .so sensor extracted from any 2.3.3 gb out there - try this for first - no changes in framework are needed if you use my tinymod
where do I have to search in such a ROM?
Do I have to flash a 2.3.3 first to extract such a file or is this file accessable in a .tar file?
Maybe someone can send me such a file in here and tell me where I have to move it.
Thx to all here for ur help.
Update: I upgraded my phone with XXKI3 2.3.5 firmware, from XXKH3.
The lag is gone, definitely a big improvement compared to XXKH3 version. The phone is very responsive and fast. Quadrant shows 4200+, pretty impressive:
{
"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"
}
The bootloader was updated, you cannot reset anymore your phone with a download jig. However, Intratech uploaded the old bootloader:
Intratech said:
If you've already flashed a full package from elsewhere and cannot reset your binary counter using the Jig just flash this package in the PDA or Bootloader (Yes both will work) section of Odin to replace the bootloaders and then you can reset the counter: http://www.multiupload.com/LQQBRQVJUD
Click to expand...
Click to collapse
Personally, I flashed the file with Odin (PDA).
The phone ring is set to silent, instead of default "Over the horizon" ringtone. Make sure you change it, your phone is not broken. See the complete list of changes, related to previous ROM.
Guide
I'm posting this procedure in a separate thread, as is easier to be linked into different forum posts. My Bell Canada phone came originally with the UGKG2 firmware, so everything listed below is based on my own experience with this version, I do not know or confirm it will work with other firmware. I currently run the official (?) XXKI3 Gingerbread 2.3.5 firmware, downloaded from samfirmware.com site (see details below). This is a wipe device release.
Personally, I read that other people flashed their phones with a different firmware... but I did not wanted to do it on my phone. I sticked with the same family XXKGx, just to be safe. Please read Electroz's explanation below.
There are 3 types of release builds: leaked, Frankenstein (compiled and tested by devs, based on demand) and official (Kies updates).
The procedure is simple (I presume you are familiar with Odin, Download Mode &Co.):
1) Get yourself the stock firmware and kernel (thank you Intratech)
2) Setup your drivers properly, avoid the Kies insanity (see below)
3) Flash the new firmware (my flash procedure, you can/should skip Re-Partition/PIT as Intratech explained)
4) Flash phone with CF-Root (I used the CF-Root-SGS2_XX_OXA_KI3-v4.1-CWM4.zip file)
5) Wipe (cache + factory reset)
6) Uninstall all Samsung crap and install additional system apps (i.e. Car Home)
7) Flash back the stock KI3 kernel (thank you Intratech, password: [email protected])
8) Wipe (cache + factory reset)
9) Connect your device to a download jig, to reset the flash counter (old bootloader needed)
Phone & Modem Drivers Setup
Note: This procedure was tested with Windows 7 Ultimate 64bits. If you already installed Kies, uninstall all related software/drivers and clean your registry. Or do a clean Windows install just to be safe.
1) With your anti-virus off, put your phone in Download mode and connect the USB cable. Windows Update will start to download right away the modem and USB drivers. Make sure you select the Windows Update option, when asked into driver install window.
2) Once the modem drivers installed, disconnect the cable, reboot the phone in normal mode and reconnect the cable again. A new set of drivers will be installed for the rest of USB interface.
Important: You need do it in the SPECIFIC order mentioned above, or else the modem drivers will not be installed and you will not be able to use properly Odin. I know this because I tried the other way around.
Initial Phone Setup
Once the phone rebooted, you will be welcomed to the Android Setup.
1) First, set the language from English UK to whatever you like.
A Network warning related to Date and Time will pop, tap on Cancel.
2) Tap the Android robot and setup your phone.
There is NO need to change any other settings, the phone will automatically detect the Bell network.
If for some reason it does not, once you completed your basic setup go to:
Settings > Wireless and Network > Mobile networks > Network operators
It will start the scanning and pop 3 Bell networks, pick the first one. Again, this is in case your phone does not work with calls, voicemail or SMS.
Notes
You should uninstall the CWM app once you flashed back the stock kernel, is half useless. I tested the new Superuser app from Android Market, it will properly upgrade to latest version and also upgrade the su binary on XXKI3 firmware. If you plan to poke around your phone with the Terminal, you will lose all the fancy Linux commands. (grep etc.)
Personally, I purchased ChainsDD's Superuser Elite key. It will allow you to pin protect your rooted device, among other useful things that are planned to be added (built-in terminal). I upgraded Superuser to version 3 and everything works properly.
Battery Power Savings
I always leave my phone with all default options, including screen auto-adjust. The only options I turn off are:
Settings > About phone > Software update > Auto update Disabled
Settings > Applications > Samsung Apps > Off
Personally, I have no idea who started the battery calibration myth in S2. It is useless to "overcharge" the battery, as the software has a check to stop automatically the charge once the battery is 100% while the battery itself has a build-in controller that can't be wiped.
Example of battery stats with the phone in idle mode for approx. 18hrs (86%) and 109hrs (2%):
Running Services
I use Wifi N with a Cisco E4200 DD-WRT (phone at 20"), 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
CSC (Cell Site Controller)
The default CSC setting in XXKI3 is KOR. You can check it with: *#272*{IMEI}#
where the {IMEI} value represents the 15 digits of your IMEI (International Mobile Equipment Identity).
I personally used the default option (KOR) and the phone works perfect, with great reception:
There are some people who wonder if they should change the CSC. I will quote Intratech on this matter as he answered perfectly to my question:
Intratech said:
Some people do and some just use the CSC packaged with whichever firmware they flash. As long as your APN and SMS/MMS settings are ok there is no need to flash another CSC package.
Click to expand...
Click to collapse
Fast Dormancy
Some people noticed that their network idle on 3G, instead of HSPA+. That is absolutely normal, because of the "fast dormancy" feature. If enabled, HSPA+ will rapidly disconnect from the network once the information is sent or received. That will penalize the actual network you are on, unless the carrier network and your phone talk to each other in a way that takes battery life as well as network congestion into consideration. For this to work, both networks and smartphones have to implement a standardized version of the fast dormancy feature. Bell Canada supports this feature and by default Fast Dormancy is enabled into XXKI3 firmware.
You can check it with: *#9900#
You should call your carrier to see if they have it implemented. Probably your tech support will look like you are speaking Chinese and escalate it to a more knowledgeable guy. This is the average download speed I get on XXKI3 (network is switching automatically on HSPA+):
There are some reports where people confirmed that the UGKG2 build allowed you to reach faster download speeds (up to 9MB). Personally I think 6MB over a cell network is already more than perfect for tethering, not to mention that there are many factors to be taken into consideration when you deal with a wireless transmission. (location, tower antenna, weather, etc.)
Random Restart
The screen needs minimum 500Mhz to get out of Sleep Mode. Some custom ROM's use a low voltage or "underclock" feature that reduces the power consumption but also the number of CPU steps. That is what makes your phone crash and reboot randomly. If you use an external sdcard, do a sd wipe just to be safe. It should take several hours, so do it over the night. Personally, I did not experienced any random reboots using neither the XXKH3 or XXKI3 firmware.
Some people might have bad battery contacts on their S2. Basically, the phone shuts down while in your pocket. Clean the battery terminals with some audio head tape cleaner and cotton swabs, than make sure the contacts are proper.
You could also have a RAM (hardware) issue. Bad memory degrades fast so you will see your random reboots pop at a faster frequency. If you did all the above and still experience random reboots, run adb logcat to see what is going on at that specific moment. If you get error codes like:
Code:
code 1 (SEGV_MAPERR), fault addr 00000000
you are dealing with bad memory unfortunately and need to service your phone.
Manage system apps with Terminal
Personally, I decided to stick with a terminal for now, I feel more comfortable to see what is going on with my own eyes in my phone. A good alternative to Terminal would be the SystemApp Remover, is faster and more robust compared to Titanium Backup as it does only one task (backup/remove system apps).
I did an output list of all the packages:
Code:
$ pm list packages -f >> /sdcard/packages 2>&1
so I know now where each package is located and what is the associated name.
All I have to do is run:
Code:
$ su
# rm -f /system/app/package.{apk,odex}
# pm clear PACKAGE
# pm uninstall PACKAGE
Running "mount | grep system" tells me right away where and how /system is mounted:
Code:
/dev/block/mmcblk0p9 on /system type ext4 (ro,relatime,barrier=1,data=ordered)
so all I have to do is change the mount perms to write, instead of read:
Code:
# mount -o remount,rw /dev/block/mmcblk0p9 /system
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
Removed System Apps
This is the list of /system apps I removed from XXKI3 firmware:
BuddiesNow.apk
Days.apk
DigitalClock.apk (I use Beautiful Widgets instead)
Email.apk (I use Gmail only)
EmailWidget.apk
GameHub.apk
GenieWidget.apk
install_flash_player.apk
Kies.apk
KiesAir.apk
kieswifi.apk
Kobo.apk
MiniDiary.apk
MusicHub_U1.apk
MusicPlayer.apk (I use Google Music instead)
PolarisOffice.apk
PressReader.apk
ReadersHub.apk
SamsungApps.apk
SamsungAppsUNA3.apk
SamsungIM.apk
SecretWallpaper1.apk
SecretWallpaper2.apk
SevenEngine.apk
ShareApp.apk
SnsAccountFb.apk
SnsAccountLi.apk
SnsAccountMy.apk
SnsAccountTw.apk
SnsDisclaimer.apk
SnsImageCache.apk
SnsProvider.apk
SocialHub.apk
VoiceToGo.apk (I use Car Home instead)
Zinio.apk
Apps ported to Galaxy S2
Some of my favorite apps, not available into Market and ported to Galaxy S2:
Google Car Home
Market Access
Google+ 2.0 (works with a Google Apps account)
Terms
ROM - software stored into read-only memory. ROM retains its contents even when the phone is turned off. ROM is referred to as being nonvolatile, whereas RAM is volatile.
Kernel - portion of the OS that handles drivers, hardware control and access for the rest of the OS.
Modem - handles the communication with your carrier.
Root - superuser privileges in any Linux OS.
yqed said:
I'm posting this procedure in a separate thread, as is easier to be linked into different forum posts. My Bell Canada phone came originally with the UGKG2 firmware, so everything listed below is based on my own experience with this version, I do not know or confirm it will work with other firmware. I currently run the official (?) XXKG3 Gingerbread 2.3.4 firmware, downloaded from samfirmware.com site (see details below).
Personally, I read that other people flashed their phones with a different firmware... but I did not wanted to do it on my phone. I sticked with the same family XXKGx, just to be safe.
Click to expand...
Click to collapse
This is wrong. I'm not sure where you got that XXKG3 is remotely the same as UGKG2, but here's an explanation of the firmware version numbers:
This is standard across most Samsung Phones.
I9000 = Model #
UG = Carrier/Area code. For example, XX = Europe, UG = Bell Mobility Canada.
K = Year = 2011
G = Month = July (H = August, I = September)
2 = Revisions that month for the specific region (aka. UG, XX, XW).
A lot of people on here think the last 3 digits are important and that if you have 2 KG3 firmware that they are the same. However, this is not the case.
You need to go by all 5 letters due to the fact that each firmware is customized by different groups at Samsung. And to prove this, just look at KG2. There are 2.3.3 KG2's and there are 2.3.4 KG2's.
It's actually possible that one area's KG2 could have been newer than another area's KG4. The best way to check, is to look at the build date in the Build.prop for each firmware.
But your assuming that KGx means they're the same is wrong. All that those numbers mean is what month/revision the firmware is. Samsung has several different teams producing firmware independently of each other for different regions. The only letters that mean the firmwares are similar are the country/carrier code (ie. UG, XX, XW).
Also, your idea of what Official firmware is, is flawed. Just because it's on samfirmware, DOES NOT make it official. Most of their firmwares are leaked test builds. If it's not released on Kies, it's not official.
Thanks for the great explanation, much appreciated. It should help many people understand better how the versioning works. About the "official" part, that's the reason why I mark it with a (?). As you said very well, it is official once is released by Samsung through updates.
The thread is related to my own experiences with the Europe MULTI firmware, based on the fact that a Bell phone specs are identical to the Europe model.
Edit: I upgraded to XXKH3 firmware successfully just now, everything works great.
I currently have a Bell branded SGSII with baseband version UGKG2.
I originally flashed it with CF-Root-SGS2_ZS_OZS_KG2-v4.1-CWM4.zip and then I re-flashed it with the original UGKG2 Stock Kernel from Bell.
Now my phone is rooted and stock.
Any positive/negative feedback from users running XXKH3 firmware (2.3.4) would be very much appreciated.
thvpham said:
I currently have a Bell branded SGSII with baseband version UGKG2.
I originally flashed it with CF-Root-SGS2_ZS_OZS_KG2-v4.1-CWM4.zip and then I re-flashed it with the original UGKG2 Stock Kernel from Bell.
Now my phone is rooted and stock.
Any positive/negative feedback from users running XXKH3 firmware (2.3.4) would be very much appreciated.
Click to expand...
Click to collapse
I ran the KH3 firmware briefly with no issues. The only annoying this was when using the program monitor widget I would experience some lag or choppiness when switching homescreens(same on KG6/KH4). On the positive side the gps accuracy and lock time was greatly improved.
Aha, I had no idea as I don't use that widget... thanks for the tip.
I usually hold the Home button until the Task Manager pops, to see the running apps. But I got used already to press the Back key every time I deal with an app... that automatically closes it.
About the GPS, the accuracy is greatly improved indeed. It takes me 1-3secs max to get a lock (with wireless networks disabled) and the accuracy is always 5meters.
Edit: There is a new Digital Clock service running now... I have no idea what makes it start, please let me know. I use Beautiful Widgets on my home screen.
The digital clock service should be part of the digital clock widget. You can try to end the process under running services and see if it stops it.
I downloaded the XXKH3 firmware but I'm not sure which files I should be using with Odin (Bootloader, PDA, Phone & CSC).
KayvinM said:
The digital clock service should be part of the digital clock widget. You can try to end the process under running services and see if it stops it.
Click to expand...
Click to collapse
I use Beautiful Widgets, so DigitalClock.apk should not be starting... Weird.
I just uninstalled the system app, no more running services. It was wasting my battery for nothing.
thvpham said:
I downloaded the XXKH3 firmware but I'm not sure which files I should be using with Odin (Bootloader, PDA, Phone & CSC).
Click to expand...
Click to collapse
See step 3 and skip the PIT file (re-partition unchecked). Also see the Update note into OP.
thvpham said:
I downloaded the XXKH3 firmware but I'm not sure which files I should be using with Odin (Bootloader, PDA, Phone & CSC).
Click to expand...
Click to collapse
I ended up re-downloading the XXKH3 from Intratech's thread and it was much easier flashing the one PDA file.
Now do I need to flash the XXKH3 stock kernel or my default stock Bell kernel?
You need the XXKH3 stock kernel, Intratech has it linked below the actual firmware link.
does it matter if CSC changes?
right now, (before root + update firmware), I still have BMC....
but once it's changed, would that create problems? If yes, what kind of problems. If no, then why do we care about CSC?
Personally, I used the samfirmware files and the phone works great. The pda.bell.ca info is present into ASN also.
Thanks for the responses everyone.
I ended flashing the stock XXKH3 kernel with the firmware. So far the upgrade has been good to me, I noticed improved battery life for the first 18 hours of usage. I will continue to use this build until I find something that is more stable and efficient then this.
A BIG THANK YOU!!!! I finally rooted and unlocked.
Originally: UGKF6
Now: XXKG5
Thanks for the guide!!!
Just 1 question though, do I HAVE TO do a factory after root? Any problem if I don't?
One thing is sure, the battery life degraded compared to XXKG3 firmware.
XXKG3 | XXKH3 (about 4hrs lost)
When I took the screenshot on KG3, I was using the phone for about 2 hours to read a book (notice the sudden drops because of the white screen), while the KH3 was always in sleep mode. So ya, there is a significant change in battery life with a tradeoff for the GPS gains.
I updated the OP.
clb09 said:
A BIG THANK YOU!!!! I finally rooted and unlocked.
Originally: UGKF6
Now: XXKG5
Thanks for the guide!!!
Just 1 question though, do I HAVE TO do a factory after root? Any problem if I don't?
Click to expand...
Click to collapse
Just curious, why you did not used the KH3 to take advantage of amazing GPS? The battery life should be a bit better also, compared to KG5. What do you mean by "do a factory"? You will lose root only if you flash back the firmware, flashing the kernel will not delete the su binary. You want to keep your phone rooted.
I strongly recommend you to spend $1 and get ChainsDD's Superuser Elite key, it will allow you to pin protect your rooted device. I upgraded to 3.0 Beta4 and everything works properly. Worth the dollar in so many ways, not just for securing the su access.
What you use to remove system app.
Thanks
Fizwiz said:
What you use to remove system app.
Thanks
Click to expand...
Click to collapse
I use Titanium Backup PRO. It allows me to backup, freeze and uninstall the unwanted apps.
One thing i have see with the XXKH3. With the KG2 im stable on H+, now im switching between 3G and H+.
Anyone else?
See Fast Dormancy info in OP. Is normal and the intended way to save you battery and bandwidth congestion.
Hi!
I have a Nexus 10 and it's been working flawlessly since I bought it, running CyanogenMod 10.1 most of the time. After I upgraded to 4.4 it started to hang, become unresponsive when being left on with screen turned off for a couple hours. Wouldn't last a night without hanging, regardless if it was being charged or not. Every time after that I had to hard reboot (press power button for longer than 8-10 seconds). This would happen on stock 4.4, stock 4.3, CM 10.2, stock kernel, francoKernel. Even on fresh install with no apps installed.
When I left it connected to USB with ADB logging, I could see that the last thing in the log before it hangs was usually something related to libEGL, GL, GL Operation, glDrawArrays.
For example:
Code:
11-23 13:08:34.250 W/System.err( 1012): java.lang.RuntimeException: GL Operation 'glDrawArrays' caused error 505!
(I found somewhere that this is GL Out of Memory error)
Code:
11-23 13:08:38.955 W/ ( 1012): GLES-MALI OOM error: execution failed (gles_fbp_read_pixels at vendor/arm/mali6xx/gles/src/fb/mali_gles_fb_read_pixels.c:693)
Code:
12-15 21:06:40.813 D/libEGL (16985): glGetIntegerv(GL_FRAMEBUFFER_BINDING_OES, (GLint *) 0x426e3be0);
12-15 21:06:40.813 D/libEGL (16985): glBindFramebuffer(GL_FRAMEBUFFER_OES, 2);
12-15 21:06:40.813 D/libEGL (16985): glGetError();
This is the latest log on CM 10.2 with OpenGL tracing in logcat (just the last part):
http://pastebin.com/6rpmfYca
The full log:
http://www61.zippyshare.com/v/5060489/file.html
This is some previous log:
http://pastebin.com/J9dNBBZS
What is causing this? What app/service is it dying in (there is MovieMaker in the log before the issue happens, but WTH?)? How can I debug this further?
_anarion_ said:
Hi!
I have a Nexus 10 and it's been working flawlessly since I bought it, running CyanogenMod 10.1 most of the time. After I upgraded to 4.4 it started to hang, become unresponsive when being left on with screen turned off for a couple hours. Wouldn't last a night without hanging, regardless if it was being charged or not. Every time after that I had to hard reboot (press power button for longer than 8-10 seconds). This would happen on stock 4.4, stock 4.3, CM 10.2, stock kernel, francoKernel. Even on fresh install with no apps installed.
When I left it connected to USB with ADB logging, I could see that the last thing in the log before it hangs was usually something related to libEGL, GL, GL Operation, glDrawArrays.
For example:
Code:
11-23 13:08:34.250 W/System.err( 1012): java.lang.RuntimeException: GL Operation 'glDrawArrays' caused error 505!
(I found somewhere that this is GL Out of Memory error)
Code:
11-23 13:08:38.955 W/ ( 1012): GLES-MALI OOM error: execution failed (gles_fbp_read_pixels at vendor/arm/mali6xx/gles/src/fb/mali_gles_fb_read_pixels.c:693)
Code:
12-15 21:06:40.813 D/libEGL (16985): glGetIntegerv(GL_FRAMEBUFFER_BINDING_OES, (GLint *) 0x426e3be0);
12-15 21:06:40.813 D/libEGL (16985): glBindFramebuffer(GL_FRAMEBUFFER_OES, 2);
12-15 21:06:40.813 D/libEGL (16985): glGetError();
This is the latest log on CM 10.2 with OpenGL tracing in logcat (just the last part):
http://pastebin.com/6rpmfYca
The full log:
http://www61.zippyshare.com/v/5060489/file.html
This is some previous log:
http://pastebin.com/J9dNBBZS
What is causing this? What app/service is it dying in (there is MovieMaker in the log before the issue happens, but WTH?)? How can I debug this further?
Click to expand...
Click to collapse
I can't offer a solution, but I have the same problem. Mine started when I moved to KitKat. I thought the problem was occurring when on a charger and the charge level reached FULL. But I also have the OLD MovieMaker app loaded. I am going to uninstall it and see if that has any effect.
Have you had any luck tracking down the problem?
rlrbjr said:
I can't offer a solution, but I have the same problem. Mine started when I moved to KitKat. I thought the problem was occurring when on a charger and the charge level reached FULL. But I also have the OLD MovieMaker app loaded. I am going to uninstall it and see if that has any effect.
Have you had any luck tracking down the problem?
Click to expand...
Click to collapse
Hi!
I was able to find some old threads about this aptly named Sleep of Death issue, here for example.
Unfortunately no conclusion, most people seem to return their devices :/
Now I think this is indeed some massive memory leak, becasue I was able to see ADB logs with all processes stopping, and the screen blinking with lock screen once when this happened.
As for MovieMaker, this might be misleading - I froze it in TitaniumBackup but the issue still exists.
My plan now is to write a script that would run
Code:
adb shell dumpsys meminfo
every couple seconds/minutes and plot the memory usage until the issue strikes.
I will report here if I find anything.
Best regards,
anarion
I uninstalled Movie Editor (rather than freezing it) and my system is much better (so far). I have not had a single lockup. It still too early to know if this is a god long term solution but I will keep you informed.
Sent from my Nexus 10 using Tapatalk 4
Hi,
I'm having stability issues for a while now. The device randomly freezes and after a few seconds reboots itself automatically. This happens rarely, about once a week, but it starts to bother me. It happened to me a few times while typing in WhatsApp messenger, a few times while using Waze navigation and sometimes when I opened the camera.
I factory reset my phone, all stock with locked bootloader but the issue persists. Is it a known stability issue with the 6P or is my device requires a repair?
roee88 said:
Hi,
I'm having stability issues for a while now. The device randomly freezes and after a few seconds reboots itself automatically. This happens rarely, about once a week, but it starts to bother me. It happened to me a few times while typing in WhatsApp messenger, a few times while using Waze navigation and sometimes when I opened the camera.
I factory reset my phone, all stock with locked bootloader but the issue persists. Is it a known stability issue with the 6P or is my device requires a repair?
Click to expand...
Click to collapse
Such issues are basically caused by apps, in stock environment. But since you mentioned WhatsApp and Waze, I have never faced any such random reboot ever. However It could be another app, causing this. You might want to check the other apps.
If you don't want to unlock and flash a factory image, I would insist you to go see the service centre.
Hi, I have the same issue with mine, did you find the cause of this?
thanks!
roee88 said:
Hi, I'm having stability issues for a while now. The device randomly freezes and after a few seconds reboots itself automatically. This happens rarely, about once a week, but it starts to bother me. It happened to me a few times while typing in WhatsApp messenger, a few times while using Waze navigation and sometimes when I opened the camera. I factory reset my phone, all stock with locked bootloader but the issue persists. Is it a known stability issue with the 6P or is my device requires a repair?
Click to expand...
Click to collapse
No there is no known stability issue with a "normal" 6P. Until you unlock your bootloader and flash a full Google image using flash-all.bat you cannot rule out a hardware issue. When you unlock the bootloader, the phone will wipe itself, but continue on by flashing a full image. Instructions are on the same page you get the image from. This is what Google always intended images to be used for- restoring a problematic phone with the exact bit-by-bit OS as an untouched phone. It is also the first step they will require when you call tech support. You should also install and run Accubattery to check your battery capacity just to make sure your battery is healthy and not contributing to (or causing) the problem.
I've had the same issue since I got the phone. It happens once every week or two on average, and it results in the phone freezing for 20-30 seconds, followed by a restart. It almost always occurs when I'm interacting with the phone (most often when scrolling in a reddit app), but it has happened once or twice overnight.
I suspect it is a hardware issue as I don't believe that userspace apps should be able to cause this (or at least, they ought not to be able to crash the phone...) and I've heard of other people with the same issues uncommonly.
Can you check your phone's date of manufacture? You can do this by going into fastboot and selecting the barcodes menu option.
Here are some interesting last_kmsg logs from the last two events:
Code:
(missing preceeding logs due to log spam)
[84739.791974]lowmemorykiller: Killing 'android:ui' (18518), adj 906,
[84739.791974] to free 66740kB on behalf of 'kswapd0' (135) because
[84739.791974] cache 316852kB is below limit 322560kB for oom_score_adj 906
[84739.791974] Free memory is 11064kB above reserved
[84739.907688] lowmemorykiller: Killing 'ackageinstaller' (18478), adj 906,
[84739.907688] to free 49900kB on behalf of 'kswapd0' (135) because
[84739.907688] cache 289696kB is below limit 322560kB for oom_score_adj 906
[84739.907688] Free memory is 60508kB above reserved
[84739.908238] lowmemorykiller: Killing 'Jit thread pool' (18481), adj 906,
[84739.908238] to free 49952kB on behalf of 'kswapd0' (135) because
[84739.908238] cache 289696kB is below limit 322560kB for oom_score_adj 906
[84739.908238] Free memory is 60508kB above reserved
[84739.908348] lowmemorykiller: Killing 'FinalizerDaemon' (18486), adj 906,
[84739.908348] to free 50040kB on behalf of 'kswapd0' (135) because
[84739.908348] cache 289696kB is below limit 322560kB for oom_score_adj 906
[84739.908348] Free memory is 60508kB above reserved
[84739.908492] lowmemorykiller: Killing 'HeapTaskDaemon' (18488), adj 906,
[84739.908492] to free 50224kB on behalf of 'kswapd0' (135) because
[84739.908492] cache 289696kB is below limit 322560kB for oom_score_adj 906
[84739.908492] Free memory is 60508kB above reserved
[84739.908977] lowmemorykiller: Killing ':UploadToFolder' (18533), adj 906,
[84739.908977] to free 37892kB on behalf of 'kswapd0' (135) because
[84739.908977] cache 289696kB is below limit 322560kB for oom_score_adj 906
[84739.908977] Free memory is 60508kB above reserved
[84739.909298] lowmemorykiller: Killing 'Jit thread pool' (18538), adj 906,
[84739.909298] to free 37984kB on behalf of 'kswapd0' (135) because
[84739.909298] cache 289696kB is below limit 322560kB for oom_score_adj 906
[84739.909298] Free memory is 60508kB above reserved
[84739.909379] lowmemorykiller: Killing 'FinalizerDaemon' (18541), adj 906,
[84739.909379] to free 38100kB on behalf of 'kswapd0' (135) because
[84739.909379] cache 289696kB is below limit 322560kB for oom_score_adj 906
[84739.909379] Free memory is 60508kB above reserved
Code:
[74660.445598] i2c-msm-v2 f9923000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:10) mode:FIFO slv_addr:0x28 MSTR_STS:0x0d1300c8 OPER:0x00000090
[74660.527433] type=1400 audit(1499172819.129:2262): avc: denied { search } for pid=8882 comm=2048616E646C657220546872656164 name="leds" dev="sysfs" ino=12900 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:object_r:sysfs_led:s0 tclass=dir permissive=0
[74665.643519] type=1400 audit(1499172824.245:2263): avc: denied { search } for pid=8882 comm=2048616E646C657220546872656164 name="leds" dev="sysfs" ino=12900 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:object_r:sysfs_led:s0 tclass=dir permissive=0
[74716.850927] healthd: battery l=59 v=3854 t=24.7 h=2 st=3 c=-281 chg=
[74776.912258] healthd: battery l=59 v=3856 t=25.0 h=2 st=3 c=-276 chg=
[74777.585513] healthd: battery l=59 v=3856 t=25.0 h=2 st=3 c=-276 chg=
[74817.010491]lowmemorykiller: Killing 'ogle.android.gm' (18102), adj 906,
[74817.010491] to free 65452kB on behalf of 'kswapd0' (135) because
[74817.010491] cache 319616kB is below limit 322560kB for oom_score_adj 906
[74817.010491] Free memory is -1968kB above reserved
[74817.011215] lowmemorykiller: Killing 'FinalizerWatchd' (18111), adj 906,
[74817.011215] to free 65660kB on behalf of 'kswapd0' (135) because
[74817.011215] cache 319324kB is below limit 322560kB for oom_score_adj 906
[74817.011215] Free memory is -1772kB above reserved
[74817.012017] lowmemorykiller: Killing 'e.process.gapps' (8732), adj 906,
[74817.012017] to free 37172kB on behalf of 'kswapd0' (135) because
[74817.012017] cache 319032kB is below limit 322560kB for oom_score_adj 906
[74817.012017] Free memory is -1576kB above reserved
[74817.015941] lowmemorykiller: Killing 'ndroid.settings' (18552), adj 906,
[74817.015941] to free 34912kB on behalf of 'kswapd0' (135) because
[74817.015941] cache 318448kB is below limit 322560kB for oom_score_adj 906
[74817.015941] Free memory is -988kB above reserved
[74817.019351] lowmemorykiller: Killing 'droid.apps.plus' (14639), adj 906,
[74817.019351] to free 31976kB on behalf of 'kswapd0' (135) because
[74817.019351] cache 317280kB is below limit 322560kB for oom_score_adj 906
[74817.019351] Free memory is 332kB above reserved
[74817.079463] binder: 8732: binder_alloc_buf, no vma
[74825.687222] SMBCHG: smbchg_external_power_changed: smbchg_external_power_changed: current_limit = 0
[74825.688381] healthd: battery l=58 v=3756 t=25.5 h=2 st=3 c=-895 chg=
[74825.691287] healthd: battery l=58 v=3756 t=25.5 h=2 st=3 c=-895 chg=
[74885.755321] healthd: battery l=58 v=3872 t=26.0 h=2 st=3 c=-135 chg=
[74920.211282] ETHER_TYPE_802_1X [RX]: ver 2, type 3, replay 43
[74920.218014] ETHER_TYPE_802_1X [TX]: ver 1, type 3, replay 43
[74945.819838] healthd: battery l=58 v=3874 t=26.5 h=2 st=3 c=-146 chg=
[75005.881346] healthd: battery l=57 v=3859 t=27.2 h=2 st=3 c=-167 chg=
[75053.911140] lowmemorykiller: Killing 'com.groupon' (14554), adj 906,
[75053.911140] to free 63388kB on behalf of 'kswapd0' (135) because
[75053.911140] cache 320304kB is below limit 322560kB for oom_score_adj 906
[75053.911140] Free memory is 5028kB above reserved
[75053.911919] lowmemorykiller: Killing 'Signal Catcher' (14561), adj 906,
[75053.911919] to free 63436kB on behalf of 'kswapd0' (135) because
[75053.911919] cache 320304kB is below limit 322560kB for oom_score_adj 906
[75053.911919] Free memory is 5028kB above reserved
[75062.511529] QSEECOM: qseecom_load_app: App (widevine) does'nt exist, loading apps for first time
[75062.529198] QSEECOM: qseecom_load_app: App with id 186 (widevine) now loaded
[75062.661885] QSEECOM: qseecom_unload_app: App id 186 now unloaded
[75063.317888] type=1400 audit(1499173221.919:2264): avc: denied { read } for pid=19764 comm="Binder:19752_2" name="address" dev="sysfs" ino=23761 scontext=u:r:priv_app:s0:c512,c768 tcontext=u:object_r:sysfs_mac_address:s0 tclass=file permissive=0
[75063.329706] type=1400 audit(1499173221.926:2265): avc: denied { read } for pid=19764 comm="Binder:19752_2" name="/" dev="tmpfs" ino=5436 scontext=u:r:priv_app:s0:c512,c768 tcontext=u:object_r:device:s0 tclass=dir permissive=0
[75065.942980] healthd: battery l=57 v=3868 t=28.0 h=2 st=3 c=-130 chg=
[75066.149548] QSEECOM: qseecom_load_app: App (widevine) does'nt exist, loading apps for first time
[75066.169144] QSEECOM: qseecom_load_app: App with id 187 (widevine) now loaded
[75066.273057] type=1400 audit(1499173224.876:2266): avc: denied { read } for pid=19764 comm="Binder:19752_2" name="address" dev="sysfs" ino=23761 scontext=u:r:priv_app:s0:c512,c768 tcontext=u:object_r:sysfs_mac_address:s0 tclass=file permissive=0
[75066.277050] type=1400 audit(1499173224.879:2267): avc: denied { read } for pid=19764 comm="Binder:19752_2" name="/" dev="tmpfs" ino=5436 scontext=u:r:priv_app:s0:c512,c768 tcontext=u:object_r:device:s0 tclass=dir permissive=0
[75066.298253] QSEECOM: qseecom_unload_app: App id 187 now unloaded
[75068.648773] QSEECOM: qseecom_load_app: App (widevine) does'nt exist, loading apps for first time
[75068.668092] QSEECOM: qseecom_load_app: App with id 188 (widevine) now loaded
[75068.799579] QSEECOM: qseecom_unload_app: App id 188 now unloaded
[75068.840965] type=1400 audit(1499173227.442:2268): avc: denied { read } for pid=19783 comm="Binder:19752_4" name="address" dev="sysfs" ino=23761 scontext=u:r:priv_app:s0:c512,c768 tcontext=u:object_r:sysfs_mac_address:s0 tclass=file permissive=0
[75068.844863] type=1400 audit(1499173227.446:2269): avc: denied { read } for pid=19783 comm="Binder:19752_4" name="/" dev="tmpfs" ino=5436 scontext=u:r:priv_app:s0:c512,c768 tcontext=u:object_r:device:s0 tclass=dir permissive=0
[75126.007364] healthd: battery l=57 v=3762 t=28.2 h=2 st=3 c=-788 chg=
[75186.069683] healthd: battery l=57 v=3823 t=29.0 h=2 st=3 c=-416 chg=
[75205.536484] SMBCHG: smbchg_external_power_changed: smbchg_external_power_changed: current_limit = 0
[75205.539776] healthd: battery l=56 v=3852 t=28.7 h=2 st=3 c=-192 chg=
[75205.540968] healthd: battery l=56 v=3852 t=28.7 h=2 st=3 c=-192 chg=
[75265.603220] healthd: battery l=56 v=3863 t=29.0 h=2 st=3 c=-134 chg=
Boot info:
Last boot reason: abnormal_reset
Could it be due to this?
[74660.445598] i2c-msm-v2 f9923000.i2c: NACK: slave not responding, ensure its powered: msgs(n:1 cur:0 tx) bc(rx:0 tx:10) mode:FIFO slv_addr:0x28 MSTR_STS:0x0d1300c8 OPER:0x00000090
I'm going to take more last_kmsg logs and see if the same error occurs before each freeze/reboot.
@ceribik But the kernel or it's configuration can. Are you running stock?
Sent from my Nexus 6P using XDA-Developers Legacy app
rchtk said:
@ceribik But the kernel or it's configuration can. Are you running stock?
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
@rchtk I'm running the stock firmware + Magisk root. I don't have anything too invasive with respect to rooted apps besides CF.lumen.
ceribik said:
@rchtk I'm running the stock firmware + Magisk root. I don't have anything too invasive with respect to rooted apps besides CF.lumen.
Click to expand...
Click to collapse
You definitely have a memory problem from the number of OOM you have, which probably ends up by killing a critical process leading to a freeze and reboot. I never had this on stock kernel but that's easy to get if you played a bit with some kernel parameters (which is only possible while rooted).
So to me that doesn't look like a hardware problem but you want to be sure, remove root for a few days and see how stable it is.
rchtk said:
You definitely have a memory problem from the number of OOM you have, which probably ends up by killing a critical process leading to a freeze and reboot. I never had this on stock kernel but that's easy to get if you played a bit with some kernel parameters (which is only possible while rooted).
So to me that doesn't look like a hardware problem but you want to be sure, remove root for a few days and see how stable it is.
Click to expand...
Click to collapse
Shouldn't it be killing non-critical processes first? I'm skeptical that it's due to changing kernel parameters as I've had the issue since I got the phone nearly 2 years ago, and I didn't change anything kernel related then.
The only issue with disabling root is that the issue sometimes takes 2-4 weeks to occur and so I could be waiting a while, and there's no way of knowing for sure (can't prove the existence of an event not occuring). I'll try it in any case.
ceribik said:
Shouldn't it be killing non-critical processes first? I'm skeptical that it's due to changing kernel parameters as I've had the issue since I got the phone nearly 2 years ago, and I didn't change anything kernel related then.
The only issue with disabling root is that the issue sometimes takes 2-4 weeks to occur and so I could be waiting a while, and there's no way of knowing for sure (can't prove the existence of an event not occuring). I'll try it in any case.
Click to expand...
Click to collapse
As far as I remember it will kill first processes which have a higher /proc/pid/oom_adj until memory threshold is reached. As you said, no apps should be able to smash the system.
BTW you should post the complete last_kmsg up to the last line. Could be that some processes are killed but that the real reason is something else, like temp getting to high leading to a shutoff (but without freeze).
Also you could always monitor mem and temp with an app like cooltool.
rchtk said:
As far as I remember it will kill first processes which have a higher /proc/pid/oom_adj until memory threshold is reached. As you said, no apps should be able to smash the system.
BTW you should post the complete last_kmsg up to the last line. Could be that some processes are killed but that the real reason is something else, like temp getting to high leading to a shutoff (but without freeze).
Also you could always monitor mem and temp with an app like cooltool.
Click to expand...
Click to collapse
Ok I kept root on as I wanted to get another full log if it happened again which it did. This time I had cooltool running and the temp and free memory were fine. It said I had ~500MB free, however the last_kmsg log still showed out of memory errors...
https://pastebin.com/EEv0pJs1
I noted the "i2c-msm-v2 f9923000.i2c: NACK: slave not responding, ensure its powered" errors still precede the OOM errors.
@rchtk
Ok I've had another freeze and reboot in the same circumstances, whilst using the app that I've had it most frequently occur in.
This time however, I had stock everything (partitions, kernel, no root). Unfortunately I wasn't able to get a last_kmsg as it was overwritten after I flashed Magisk to get root access for retrieving the logs.
Do you still think it is not a hardware issue?
ceribik said:
@rchtkDo you still think it is not a hardware issue?
Click to expand...
Click to collapse
Using fastboot, see if you can successfully FORMAT system, userdata and cache. If you have bad memory, the format process will fail. Note any error messages, if any. Flash full image using flash-all.bat
As I've recently had this problem, it seems the term "Memory" is being used very loosely.
Lets call it EMMC (storage) and DRAM (random access memory)
I got the random freeze and reboots on fully stock 7.1.2, with no apps open (or maybe some in the background) but it always happened when the phone was not being used. Even occured on 6.0.1 as well.
My issue was definitely hardware related as it even happened after a flash-all.bat factory flash. Was able to format no problem. I ended up RMA'ing it to Huawei before warranty expires.
v12xke said:
Using fastboot, see if you can successfully FORMAT system, userdata and cache. If you have bad memory, the format process will fail. Note any error messages, if any. Flash full image using flash-all.bat
Click to expand...
Click to collapse
But that isn't related to RAM (see the error log)? If it did fail, wouldn't it also run the risk of bricking my device?
ceribik said:
But that isn't related to RAM (see the error log)? If it did fail, wouldn't it also run the risk of bricking my device?
Click to expand...
Click to collapse
No. Formatting is never harmful to the onboard memory, and will sometimes be able to repair a corrupt partition. It will also identify if there are memory problems, especially if it fails to complete successfully. Obviously back your stuff up beforehand.
fastboot format system
fastboot format userdata
fastboot format cache
v12xke said:
No. Formatting is never harmful to the onboard memory, and will sometimes be able to repair a corrupt partition. It will also identify if there are memory problems, especially if it fails to complete successfully. Obviously back your stuff up beforehand.
fastboot format system
fastboot format userdata
fastboot format cache
Click to expand...
Click to collapse
Ok, no errors with formating the system or cache partition.
ceribik said:
@rchtk
Ok I've had another freeze and reboot in the same circumstances, whilst using the app that I've had it most frequently occur in.
This time however, I had stock everything (partitions, kernel, no root). Unfortunately I wasn't able to get a last_kmsg as it was overwritten after I flashed Magisk to get root access for retrieving the logs.
Do you still think it is not a hardware issue?
Click to expand...
Click to collapse
Not sure and even less with some users confirming an RMA solved their problem.
I don't have a working 6p atm so I can't compare memory behaviour but your OOM messages still surprise me (incl. UI getting killed). I could be wrong but I don't think emmc problem and ram can be linked.
When my 6p began bootlooping I tested the complete RAM by compiling "memtester" and ran this from recovery (also badblocks to check emmc). In my case no problem was detected. I don't have a computer for the next two weeks so you'll have to wait if you want to try this also. Or ask for someone to build it for you. When you fastboot flash, the complete image is temporarily stored in RAM so flashing system.img (as part of flash-all) is already a good test (2GB out of 3GB are filled before writing to emmc).
Meanwhile I would reinstall and this time not restoring most apps and be patient. Apps should't be able to do this but I'm not so confident on google design choices nor on this specific device tbh... Could be that a watchdog is kicking once UI cannot restart.
rchtk said:
Not sure and even less with some users confirming an RMA solved their problem.
I don't have a working 6p atm so I can't compare memory behaviour but your OOM messages still surprise me (incl. UI getting killed). I could be wrong but I don't think emmc problem and ram can be linked.
*snip*.
Click to expand...
Click to collapse
It's interesting that you mention watchdog. I just had another two random reboots in a row, this time while the phone was in my pocket (I'm 90% sure there was some pocket touchscreen activity).
The first crash seems to be preceded by an error with controlling the wifi chip (as well as some lowmemorykillers again) and culminates in a ?kernel panic and watchdog reboot:
https://pastebin.com/9hhSYtMQ
The second crash doesn't have any lowmemorykillers but has one of those "i2c-msm-v2 NACK: slave not responding" just before the reboot (although it doesn't state the reboot was unexpected unlike my earlier logs):
https://pastebin.com/ewaYhu2v
I would be interested to try your builds of memtester and badblocks whenever you get the chance to locate them.
Another one:
https://pastebin.com/j34pygRs
I think I will try factory resetting over the weekend, but I'm sceptical it will fix it.