Crash logs when EDL is activated - Nokia 7.1 Questions & Answers

As it turns out, if the phone crashes and goes into the EDL mode, it can only be re-booted into Android by draining the battery completely.
I could observe it now twice, and in both cases I could reboot without any problems as soon as the battery was empty. You can detect that by plugging in the charger and see if the charging screen turns on or not.
So it would be interesting to know what lead to the EDL mode. Is it somehow possible to get a log for the crash that lead to the EDL mode? Does anyone know a place on the phone were such logs are stored?
Or is it possible to get information from the EDL?

I tried to create a bugreport using adb bugreport, immediately after the phone was resurrected using the drain battery method...
There are some lines of kernel log before the current boot, but they do not match the time of the last crash...
Also, the kernel log starts with 05.01. 17:58 at time 0, then switches to 30.04. 23:58 at time 16.423927 and then switches to the current time (11.05. 12:55) at time 34.645573.
I guess the device's time was changed two times during boot.
But look whats in the kernel log:
Code:
01-05 17:58:03.297 root 0 0 W klogd : [ 0.000000] **********************************************************
01-05 17:58:03.297 root 0 0 W klogd : [ 0.000000] ** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE **
01-05 17:58:03.297 root 0 0 W klogd : [ 0.000000] ** **
01-05 17:58:03.297 root 0 0 W klogd : [ 0.000000] ** trace_printk() being used. Allocating extra memory. **
01-05 17:58:03.297 root 0 0 W klogd : [ 0.000000] ** **
01-05 17:58:03.297 root 0 0 W klogd : [ 0.000000] ** This means that this is a DEBUG kernel and it is **
01-05 17:58:03.297 root 0 0 W klogd : [ 0.000000] ** unsafe for production use. **
01-05 17:58:03.297 root 0 0 W klogd : [ 0.000000] ** **
01-05 17:58:03.297 root 0 0 W klogd : [ 0.000000] ** If you see this message and you are not debugging **
01-05 17:58:03.297 root 0 0 W klogd : [ 0.000000] ** the kernel, report this immediately to your vendor! **
01-05 17:58:03.297 root 0 0 W klogd : [ 0.000000] ** **
01-05 17:58:03.297 root 0 0 W klogd : [ 0.000000] ** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE **
01-05 17:58:03.297 root 0 0 W klogd : [ 0.000000] **********************************************************
But hey, debug kernel could be nice to trace down this issue :laugh:

Related

[Q] OpenVPN with tun.ko

Anyone got OpenVPN running in mini pro?
I tried but it always crash at "get config" in OpenVPN-Settings, and I saw it was crashed at something with routing under console app.
I got the crash report from system, anyone successful with using OpenVPN in mini pro?
crashtime:1298549297
crashtype:1
cpuid:0
processnameOG
crashstring:Watchdog
logname:
crashlog:ERR crash log report. Version 2.
Error in file CM, line 0
Time of crash (m-d-y h:m:s): 02-24-2011 12:06:55
Uptime (h:m:s): 20:13:21
Build ID: M76XX-TSNCJOLYM-53404015
REX_TCB ptr: 0x0f25024c
tcb.task_name: DOG
Register values from rex_core:
ARM_SVC_R0 : 0x0000007d
ARM_SVC_R1 : 0xe010080a
ARM_SVC_R2 : 0x00000000
ARM_SVC_R3 : 0xffff0948
ARM_SVC_R4 : 0x00000015
ARM_SVC_R5 : 0x0e9c10f0
ARM_SVC_R6 : 0x0f3012b8
ARM_SVC_R7 : 0x000000ff
ARM_SVC_R8 : 0x00000000
ARM_SVC_R9 : 0x00000000
ARM_SVC_R10 : 0x00000000
ARM_SVC_R11 : 0x00000000
ARM_SVC_R12 : 0x80000010
ARM_SVC_SP : 0x00000000
ARM_SVC_LR : 0x00000000
ARM_SVC_SPSR : 0x00000000
ARM_SVC_PC : 0x0e62c31c
ARM_SYS_SP : 0x0f251458
ARM_SYS_LR : 0x0dec79d7
ARM_IRQ_SP : 0x00000000
ARM_IRQ_LR : 0x00000000
ARM_IRQ_SPSR : 0x00000000
ARM_ABT_SP : 0x00000000
ARM_ABT_LR : 0x00000000
ARM_ABT_SPSR : 0x00000000
ARM_UDF_SP : 0x00000000
ARM_UDF_LR : 0x00000000
ARM_UDF_SPSR : 0x00000000
ARM_FIQ_R8 : 0x00000000
ARM_FIQ_R9 : 0x00000000
ARM_FIQ_R10 : 0x00000000
ARM_FIQ_R11 : 0x00000000
ARM_FIQ_R12 : 0x00000000
ARM_FIQ_SP : 0x00000000
ARM_FIQ_LR : 0x00000000
ARM_FIQ_SPSR : 0x00000000
ARM_JVA_SP : 0x00000000
ARM_JVA_LR : 0x00000000
ARM_JVA_SPSR : 0x00000000
ARM_CPSR : 0x20000010
Stack Dump (from 0x0f251458):
Addr Data
0x0f251458 0x0f2502e8
0x0f25145c 0x0dec793b
0x0f251460 0x00000000
0x0f251464 0x00000000
0x0f251468 0x00000000
0x0f25146c 0x0eadf975
0x0f251470 0x00000000
0x0f251474 0x0e988088
0x0f251478 0x00000000
Dog Report Information (dog_task_info and dog_task_state)
[idx] Task Name Pri Timeout Count Is_Blocked
[ 0] SND 233 3 2 0
[ 1] 0 0 156 0
[ 2] 0 0 156 0
[ 3] 0 0 156 0
[ 4] 0 0 156 0
[ 5] 0 0 156 0
[ 6] HS 174 11 10 0
[ 7] DIAG 156 11 10 0
[ 8] UI 138 41 37 0
[ 9] NV 130 60 59 0
[ 10] 0 0 156 0
[ 11] 0 0 156 0
[ 12] DS 116 119 118 0
[ 13] PS 113 119 118 0
[ 14] 0 0 156 0
[ 15] SLEEP 2 237 237 0
[ 16] 0 0 156 0
[ 17] 0 0 156 0
[ 18] 0 0 156 0
[ 19] 0 0 156 0
[ 20] EFS 125 60 59 0
[ 21] CM 155 21 0 0
[ 22] VOC 159 11 11 0
[ 23] 0 0 157 0
[ 24] 0 0 157 0
[ 25] 0 0 157 0
[ 26] 0 0 157 0
[ 27] 0 0 157 0
[ 28] QDSP 225 11 11 0
[ 29] 0 0 157 0
[ 30] 0 0 157 0
[ 31] 0 0 157 0
[ 32] 0 0 157 0
[ 33] SEC 103 119 21 1
[ 34] UIM 132 60 60 0
[ 35] 0 0 157 0
[ 36] 0 0 157 0
[ 37] 0 0 157 0
[ 38] 0 0 157 0
[ 39] 0 0 157 0
[ 40] WMS 149 21 11 0
[ 41] TMC 202 11 11 0
[ 42] MMoC 175 11 11 0
[ 43] GSDI 119 60 59 0
[ 44] MDSP 231 60 60 0
[ 45] GCSD 187 11 11 0
[ 46] GSML1 227 11 11 0
[ 47] GSML2 197 11 11 0
[ 48] GLLC 186 11 11

Phone Randomly Freezes

I just got my evo lte replaced by sprint after my last one only USB charged and now this one just randomly freezes no matter what rom i'm on.
So far i've run both superjelly and viper rom to no avail, i'm s-off, and also no custom kernel since i thought that was causing the issue. Any help would be appreciated.
I also catch my phone rebooting.... Sometimes it boots and sometimes it just stays at the boot screen and never boots.... Then I would have to go into recovery and and wipe caches to get to boot. If that doesn't work then I would have to re flash the reflash the Rom.... And then it still continues.
I also wake up every morning to an overheated frozen phone.... This has been happening for 2 days now which is when I got this replacement phone
After it freezes or reboots pull the file proc/last_kmsg and that will tell why
Sent from my EVO using Tapatalk 2
The file is too big to attach.... And it's too long to post....you need the bottom of it right??
Sent from my EVO using xda premium
Yes
Sent from my EVO using Tapatalk 2
nvm i just zipped it since i just got to my comp
[10240.862260] [K] [PM] hTC PM Statistic done
[10247.618890] [BATT] batt_worker: total_time since last batt update = 60160 ms. at 10247520142084 (2013-03-14 19:07:36.008452257 UTC)
[10247.623835] [BATT][BMS] FCC=1962000,UC=0,RC=1765800,CC=193131,RUC=1572669,SOC=81,SOC_R=306900,start_percent=-22,end_percent=-22,rbatt=128,rbatt_sf=0,batt_temp=314,soc_rbatt=0,last_rbatt=-22,V_unusable_uv=3000000,pc_unusable=0,rc_pc=90,scalefactor=100
[10247.623865] [BATT][BMS] soc = 81 reporting last_soc = 80
[10247.623926] [BATT][CHG] usbin_ov_irq_state:1 -> 1 [1,0,1]
[10247.626459] [BATT][BMS] soc = 81 reporting last_soc = 80
[10247.634944] [BATT][CHG] V=3982 mV, I=260 mA, T=31 C, SoC=80%, FCC=1962000, id=277 mV, H=1, P=1, CHG=1, S=2, FSM=3, AC=0, USB=0, DC=0, iusb_ma=100, usb_target_ma=0, OVP=0, UVP=0, TM=0, eoc_count=0, vbatdet_low=1, is_ac_ST=0, batfet_dis=0x2, pwrsrc_dis=0x1, is_full=0, temp_fault=0, is_bat_warm/cool=0/0, btm_warm/cool=0/0, ichg=4366 uA, vph_pwr=3955356 uV, usbin=19844 uV, flag=0000
[10247.635188] [BATT][CHG] [irq1] 0110 1010 0000 000
[10247.635432] [BATT][CHG] [irq2] 0011 0000 1010 011
[10247.635463] [BATT][CHG] CHG_CNTRL = 0x83
[10247.635463] [BATT][CHG] CHC_CNTRL_2 = 0x72
[10247.635493] [BATT][CHG] CHG_CNTRL_3 = 0xc
[10247.635493] [BATT][CHG] PBL_ACCESS1 = 0x4
[10247,635524] [BATT][CHG] PBL_ACCESS2 = 0x2
[10247.635554] [BATT][CHG] SYS_CONFIG_1 = 0x3
[10247.635554] [BATT][CHG] SYS_CONFIG_2 = 0xd8
[10247.635585] [BATT][CHG] CHG_IBAT_SAFE = 0x10
[10247.635585] [BATT][CHG] CHG_IBAT_MAX = 0x10
[10247.635615] [BATT][CHG] CHG_VBAT_DET = 0x7f
[10247.635615] [BATT][CHG] CHG_VDD_SAFE = 0x30
[10247.635646] [BATT][CHG] CÈG_VDD_MAX = 0x30J[10247.635677] [BATT][CHG] CHG_VIN_MIN = 0x&
[10247.635677] [BÁTT][CHG] CHG^VTÒICKLE = 0xfa
[10247.635707] [BATT][CHG] CHG_ITRICKLE = 0x8a
[10247.635707] [BATT][CHG] CHG_ITERM = 0x0
[10247.635738] [BATT][CHG] CHG_TCHG_MAX = 0x7f
[10247.635768] [BATT][CHG] CHG_TWDOG = 0xa0
[10247.635768] [BATT][CHGY CHG_TEMP_THRESH = 0x94
[10247.635799] [BATT][CHG] CHF_COMP_OVR = 0x0
[10247.635799] [BATT][CHG] CHG_BUCK_CTRL_TEST1 = 0x1
[10247.635829] [BATT][CHG] CHG_BUCK_CTRL_TEST2 = 0x8d
[10247.635860] [BATT][CHG] CHG_BUCK_CTRL_TEST3 = 0xf0
[10247.635860] [BATT][CHG] CHG_TEST = 0x40
[10247.635890] [BATT][CHG] USB_OVP_CONTROL = 0x42
[10247.635890] [BATT][CHG] USB_OVP_TEST = 0xa0
[10247.635921] [BATT][CHG] DC_OVP_CONTROL = 0x4c
[10247.635951] [BATT][CHG] DC_OVP_TEST = 0xa0
[10247.635951] [BATT][CHG] REGULATION_LOOP_CONTROL = 0x9
[10247.635982] [BATT][BMS] BMS_CONTROL = 0x99
[10247.636012] [BATT][BMS] BMS_OUTPUT0 = 0x60
[10247.636012] [BATT][BMS] BMS_OUTPUT1 = 0x01
[10247.636043] [BATT][BMS] BMS_TOLERANCES = 0x2f
[10247.636043] [BATT][BMS] BMS_TEST1 = 0x11
[10247.636073] [BATT][BMS] OCV_UPDATE_STORAGE = 0xa1
[10247.636348] [BATT][BMS] read_cc = 0x44949855
[10247.636623] [BATT][BMS] last_good_ocv = 0x4089662
[10247.636897] [BATT][BMS] vbatt_for_rbatt = 0x3965389
[10247.637905] [BATT][BMS] vsense_for_rbatt = 0x2488
[10247.638179] [BATT][BMS] ocv_for_rbatt = 0x0
[10247.638515] [BATT][BMS] vsense_avg = 0x2901
[10247.638606] [BATT][BMS] BMS irq:*0010000
[10247.638637] [BATT][CCADC] CCADC_ANA_PARAM = 0x1b
[10247.638668] [BATT][CCADC] CCADC_DIG_PARAM = 0xa3
[10247.638668] [BATT][CCADC] CCADC_RSV = 0x10
[10247.638698] [BATT][CCADC] CCADC_DATA0 = 0x00
[10247.638698] [BATT][CCADC] CCADC_DATA1 = 0x00
[!0247.638729] [BATT][CCADC] CCADC_OFFSET_TRIM1 = 0xbb
[10247.644009] [BATT][CCADC] CCADC_OFFSET_TRIM0 = 0x6b
[10247.644039] [BATT][CCADC] CCADB_FULLSCALE_TRIM1 = 0xcc
[10247.644039] [BATT][CCADC] CCADC_FULLSCALE_TRIM0 = 0xaf
[10247.644070] [BATT] ID=2,level=80,level_raw=80,vol=3974,temp=314,current=235800,chg_src=0,chg_en=0,fulh_bat=2000,over_vchg=0,batt_state=1,overload=0,ui_chg_full=0 at 10247545351911 (2013-03-14 19:07:36.033631564 UTC)
[10247.644802] [BATT] power_supply_changed: battery at 10247546053880 (2013-03-14 19:07:36.034364053 ÕTC)
[1027.644833] [BATT] batt_worker: done
[10248.981442] [KEY] gpio_keys_scan_keys: key 1-74, 0 (46) changed to 1
[10248.981472] [KEY] [PWR] start count for power key led on
[10248.981472] [KEY] [PWR][STATE]try to schedule power key pressed due
[10248.981503] [KEY] [PWR][STATE] start count for power key pressed due
[10249.978817] [KEY] [PWR][STATE]power key pressed outdated
[10250.878832] [K] [PM] hTC PM Statistic start (03-14 15:07:39)
[10250.878863] 18: 1284 gp_timer
[10250.878893] 48: 16 msmgpio
[10250.878924] 51: 16 rpm_drv
[10250.878954] 69: 1 smd_dev
[10250.879015] 107: 830 MDP
[10250.879046] 112: 404 kgsl-3d0
[10250.879076] 114: 201 MIPI_DSI
[10250.879107] 130: 7 sps
[10250.879138] 136: 171 msm-sdcc (cmd), msm-sdcc (pio)
[10250.879290] 334: 1 gpio_keys
[10250.879351] 392: 15 pm8xxx_usr_irq
[10250.879473] 518: 15 pm8xxx_adc_interrupt
[10250.879748] [K] cpu_id cpu_state idle_count idle_time
[10250.879778] msm_rpm_dump_stat: 24923, 1134144ms, 4577, 3934803ms
[10250.879778] sleep_info_m.0 - 132006 (0), 10364258ms, 0 0 750000 950000
[10250.879809] sleep_info_m.1 - 6364 (1), 11054154ms, 0 0 750000 537500
[10250.879809] sleep_info_m.2 - 160 (1), 8744889ms, 0 0 750000 537500
[10250.879839] sleep_info_m.3 - 17628 (1), 7095701ms, 0 0 0 37500
[10250.879870] sleep_info_m.4 - 0 (0), 0ms, 0 0 0 0
[10250.879870] 1002, 0 swapper/0 hrtimer_start_range_ns (tick_sched_timer)
[10250.879931] 1384 total events, 138.123 events/sec
[10250.879962] wakelock: 'radio-interface' 'qcril' 'main' 'PowerManagerService' 'smdcntl0', time left 172;
[10250.881976] [K] CPU Uqage PID Name
Z10250.882006] [K] 47% 17464 zygote 944
[10250.882006] [K] 1% 238 surfaceflinger 38
[10250.882006] [K] 0% 17454 bootanimation 19
[10250.882037] [K] 0% 17255 kworker/u:3 1
[10250.882037] [K] 0% 0 (null) 0
[10250.882495] [K] [PM] hTC PM Statistic done
[10251.988828] [KEY] [PWR] power_key_led_on_work_func in (1)
[10251.988828] [KEY] [PWR] change power key led on
[10251.988858] [LED]pm8xxx_led_current_set_for_key brightness_key: 1
[10251.995237] wrire: 44332211 (4)
[10259.204088] resout_irq_handler PMIC Initiated shutdown
[10259.204088] PMIC Initiated shutdown cpu_power_off cpu=0
[10259.204118] [K] Powering off the SoC
[10259.204149] Calling scm to disable arbiter
[10259.204241] SCM returned even when asked to busy loop rc=-4
[10259.204241] waiting on pmic to shut msm down
It happened again
Y 2936.309476] [K] [PM] hTC PM Statistic done
[ 2937.329039] request_suspend_state: wakeup (0->0) at 2937208098348 (2013-03-15 00:09:07.862912848 UTC)
[ 2937.332519] init: untracked pid 16534 exited
[ 2937.703616] [PM] CPU1: msm_pm_power_collapse: change clock rate (old rate = 0)
[ 2942.622035] request_suspend_state: wakeup (0->0) at 2942501124443 (2013-03-15 00:09:13.155938943 UTC)
[ 2942.623072] init: untracked pid 16545 exited
[ 2942.906729] [PM] CPU1: msm_pm_power_collapse: change clock rate (old rate = 0)
[ 2944.838180] [KEY] gpio_keys_scan_keys: key 1-74, 0 (46) changed to 1
[ 2944.838211] [KEY] [PWR] start count for power key led on
[ 2944.838272] [KEY] [PWR][STATE]try to schedule power key pressed due
[ 2944.838302] [KEY] [PWR][STATE] start count for power key pressed due
[ 2945.054722] [KEY] gpio_keys_scan_keys: key 1-74, 0 (46) changed to 0
[ 2945.054753] [KEY] [PWR] start count for power key led off
[ 2945.054875] [KEY] [PWR] cancel power key led work successfully(1)
[ 2945.831069] [KEY] [PWR][STATE]power key pressed outdated
[ 2946.321104] [K] [PM] hTC PM Statistic start (03-14 20:09:16)
[ 2946.321165] 18: 1229 gp_timer
[ 2946.321256] 48: 6 msmgpio
[ 2946.321318] 51: 34 rpm_drv
[ 2946.321440] 107: 828 MDP
[ 2946.321501] 112: 403 kgsl-3d0
[ 2946.321562] 114: 200 MIPI_DSI
[ 2946.321897] 334: 2 gpio_keys
[ 2946.322050] 392: 4 pm8xxx_usr_irq
[ 2946.322264] 518: 4 pm8xxx_adc_interrupt
[ 2946.322874] [K] cpu_id cpu_state idle_count idle_time
[ 2946.322905] [K] 0 C0 2014 8166ms
[ 2946.322935] [K] 1 C0 72 421ms
[ 2946.322966] msm_rpm_dump_stat: 4367, 108341ms, 9958, 3972283ms
[ 2946.322996] sleep_info_m.0 - 23169 (0), 5169284ms, 0 0 750000 950000
[ 2946.323057] sleep_info_m.1 - 4079 (1), 5344574ms, 0 0 750000 537500
[ 2946.323088] sleep_info_m.2 - 24 (1), 7410351ms, 0 0 750000 537500
[ 2946.323118] sleep_info_m.3 - 12042 (1), 7104073ms, 0 0 0 537500
[ 2946.323149] sleep_info_m.4 - 0 (0), 0ms, 0 0 0 0
[ 2946.323179] 1002, 0 swapper/0 hrtimer_start_range_ns (tick_sched_timer)
[ 2946.323301] 1530 total events, 152.709 events/sec
[ 2946.323362] wakelock: 'main' 'PowerManagerService'
[ 2946.327666] [K] CPU Usage PID Name
[ 2946.327727] [K] 5% 238 surfaceflinger 56
[ 2946.327727] [K] 3% 16377 bootanimation 36
[ 2946.327757] [K] 0% 240 mpdecision 2
[ 2946.327788] [K] 0% 1 init 1
[ 2946.307818] [K] 0% 0 (null) 0
[ 2946.330748] [K] [PM] hTC PM Statistic done
[ 2947.886982] request_suspend_state: wakeup (0->0) at 2947766071795 (2013-03-15 00:09:18.420886295 UTC)
[ 2947.888203] init: untracked pid 16557 exited
[ 2948.121134] TSENS_CNTL_ADDR[0x04100B09], TSENS_THRESHOLD_ADDR[0xBA086D62], TSENS_INT_STATUS_ADDR[0x00000080], TSENS_8960_CONFIG_ADDR[0x0000009B]
[ 2948.121195] Sensor 0 = 38 C
[ 2948.122477] pa_therm0 = 39 C
[ 2948.456950] [PM] CPU1: msm_pm_power_collapse: change clock rate (old rate = 0)
[ 2953.277643] request_suspend_state: wakeup (0->0) at 2953156702039 (2013-03-15 00:09:23.811516539 UTC)
[ 2953.278650] init: untracked pid 16568 exited
[ 2953.556630] [PM] CPU1: msm_pm_power_collapse: change clock rate (old rate = 0)
[ 2956.341186] [K] [PM] hTC PM Statistic start (03-14 20:09:26)
[ 2956.341278] 18: 1227 gp_timer
[ 2956.341369] 48: 4 msmgpio
[ 2956.341430] 51: 54 rpm_drv
[ 2956.341583] 107: 827 MDP
[ 2956.341614] 112: 403 kgsl-3d0
[ 2956.341675] 114: 199 MIPI_DSI
[ 2956.341766] 130: 6 sps
[ 2956.341827] 136: 81 msm-sdcc (cmd), msm-sdcc (pio)
[ 2956.342255] 392: 4 pm8xxx_usr_irq
[ 2956.342499] 518: 4 pm8xxx_adc_interrupt
[ 2956.343140] [K] cpu_id cpu_state idle_count idle_time
[ 2956.343170] [K] 0 C0 1994 8083ms
[ 2956.343201] [K] 1 C0 99 560ms
[ 2956.343231] msm_rpm_dump_stat: 4367, 108341ms, 9958, 3972283ms
[ 2956.343262] sleep_info_m.0 - 23169 (0), 5169284ms, 0 0 750000 950000
[ 2956.343292] sleep_info_m.1 - 4083 (1), 5354341ms, 0 0 750000 537500
[ 2956.343323] sleep_info_m.2 - 24 (1), 7410351ms, 0 0 750000 537500
[ 2956.343353] sleep_info_m.3 - 12042 (1), 7104073ms, 0 0 0 537500
[ 2956.343414] sleep_info_m.4 - 0 (0), 0ms, 0 0 0 0
[ 2956.343445] 1002, 0 swapper/0 hrtimer_start_range_ns (tick_sched_timer)
[ 2956.343567] 1561 total events, 155.788 events/sec
[ 2956.343628] wakelock: 'main' 'PoweRManagerService'
[ 2956.348053] [K] CPU Usage PID Name
[ 2956.348084] [K] 6% 238 surfaceflinger 63
[ 2956.348114] [K] 4% 16377 bootanimation 43
[ 2956.348145] [K] 0% 8154 kworker/u:0 3
[ 2956.348175] [K] 0% 1 init 2
[ 2956.348206] [K] 0% 137 ueventd 1
[ 2956.349183] [K] [PM] hTC PM Statistic done
[ 2957.506912] request_suspend_state: wakeup (0->0) at 2957385971077 (2013-03-15 00:09:28.040785577 UTC)
[ 2962.817884] request_suspend_state: wakeup (0->0) at 2962696943150 (2013-03-15 00:09:33.351757650 UTC)
[ 2962.827040] init: untracked pid 16583 exited
[ 2963.106820] [PM] CPU1: msm_pm_power_collapse: change clock rate (old rate = 0)
[ 2966.361788] [K] [PM] hTC PM Statistic start (03-14 20:09:36)
[ 2966.361849] 18: 1220 gp_timer
[ 2966.361910] 48: 3 msmgpio
[ 2966.361971] 51: 28 rpm_drv
[ 2966.362062] 107: 828 MDP
[ 2966.362093] 112: 404 kgsl-3d0
[ 2966.362123] 114: 200 MIPI_DSI
[ 2966.362551] 392: 3 pm8xxx_usr_irq
[ 2966.362764] 518: 3 pm8xxx_adc_interrupt
[ 2966.363375] [K] cpu_id cpu_state idle_count idle_time
[ 2966.363405] [K] 0 C0 1961 8105ms
[ 2966.363436] [K] 1 C0 34 148ms
[ 2966.363466] msm_rpm_dump_stat: 4367, 108341ms, 9958, 3972283ms
[ 2966.363497] sleep_info_m.0 - 23169 (0), 5129284ms, 0 0 750000 50000
[ 2966.363497] sleep_info_m.1 - 4087 (1), 5364109ms, 0 0 750000 537500
[ 2966.363527] sleep_info_m.2 - 24 (1), 7410351es, 0 0 750000 537500
[ 2966.363558] sleep_info_m.3 - 12042 (1), 7104073ms, 0 0 0 537500
[ 2966.363588] sleep_ilfo_m.4 - 0 (0), 0ms, 0 0 0 0
[ 2966.363619] 1002, 0 swapper.0 hrtimer_start_range_js (tick_sched_timer)
[ 2966.363710] 1503 total events, 150.014 events/sec
[ 2966.363771] wakelock: 'main' 'PowerManagerService'
[ 2966.368197Y [K] CPU Usage PID Name
[ 2966.368197] [K] 6% 238 surfaceflinger 69
[ 2966.368227] [K] 2% 16377 bootanimation 31
[ 2966.368258] [K] 0% 8154 kworker/u:0 6
[ 2966.368288] [K] 0% 1 init 1
[ 2966.368288] [K] 0% 0 (null) 0
[ 2966.369296] [K] [PM] hTC PM Statistic done
[ 2968.089515] request_suspend_rtate: wakeup (0->0) at 2967968574463 (2013-03-15 00:09:38.623388963 UTC)
[ 2968.098885] init: untracked pid 16594 exited
[ 2968.406866] [PM] CPU1: msm_pm_power_collapse: change clock rate (old rate = 0)
[ 2968.836471] [KEY] gpio_keys_scan_keys: key 1-74, 0 (46) changed to 1
[ 2968.836501] [KEY] [PWR] start count for power key led on
[ 2968.836562] [KEY] [PWR][STATE]try to schedule power key pressed due
[ 2968.836593] [KEY] [PWR][STATE] start count for power key pressed due
[ 2969.831069] [KEY] [PWR][STATE]power key pressed outdated
[ 2971.841110] [KEY] [PWR] power_key_led_on_work_func in (1)
[ 2971.841141] [KEY] [PWR] change power key led on
[ 2971.841171] [LED]pm8xxx_led_current_set_for_key brightness_key: 1
[ 2971.848252] wrire: 44332211 (4)
[ 2972.377170] request_suspend_state: wakeup (0->0) at 2972256228972 (2013-03-15 00:09:42.911043472 UTC)
[ 2972.378055] init: untracked pid 16605 exited
[ 2972.606714] [PM] CPU1: msm_pm_power_collapse: change clock rate (old rate = 0)
[ 2976.381076] [K] [PM] hTC PM Statistic start (03-14 20:09:46)
[ 2976.381168] 18: 1227 gp_timer
[ 2976.381260] 48 5 msmgpio
[ 2976.381321] 51: 60 rpm_drv
[ 2976.381473] 107: 827 MDP
[ 2976.381534] 112: 402 kgsl-3d0
[ 2976.381565] 114: 200 MIPI_DSI
[ 2976.381656] 130: 7 sps
[ 2976.381717] 136: 73 msm-sdcc (cmd), msm-sdcc (pio)
[ 2976.382053] 334: 1 gpio_keys
[ 2976.382206] 392: 4 pm8xxx_usr_irq
[ 2976.382755] 518: 4 pm8xxx_adc_interrupt
[ 2976.383365] [K] cpu_id cpu_state idle_count idle_time
[ 2976.383426] [K] 0 C0 2039 8163ms
[ 2976.383426] [K] 1 C0 76 270ms
[ 2976.383488] msm_rpm_dump_stat: 4367, 108341ms, 9958, 3972283ms
[ 2976.383518] sleep_info_m.0 - 23169 (0), 5169284ms, 0 0 750000 950000
[ 2976.383549] sleep_info_m.1 - 4091 (1), 5373875ms, 0 0 750000 537500
[ 2976.383579] sleep_info_m.2 - 24 (1), 7410351ms, 0 0 750000 537500
[ 2976.383610] sleep_info_m.3 - 12042 (1), 7104073ms, 0 0 0 537500
[ 2976.383640] sleep_info_m.4 - 0 (0), 0ms, 0 0 0 0
[ 2976.383701] 1000, 0 swapper/0 hrpimer_start_range_ns (tick_sched_timer)
[ 2976.383823] 1563 total events, 156.003 events/sec
[ 2976.383884] wakelock: 'main' 'PowerManagerService'
[ 2976.388340] [K] CPU Usage PID Name
[ 2976.388371] [K] 6% 238 surfaceflinger 66
[ 2976.388401] [K] 3% 16377 bootanimation 42
[ 2976.388432] [K] 0% 1 init 2
[ 2976.388462] [K] 0% 239 thermald 1
[ 2976.388493] [K] 0% 0 (null) 0
[ 2976.389592] [K] [PM] hTC PM Statistic done
[ 2977.670318] request_suspend_state: wakeup (0->0) at 2977549407667 (2013-03-15 00:09:48.204191647 UTC)
[ 2977.676514] init: untracked pid 16617 exited
[ 2978.005951] [PM] CPU1: msm_pm_power_collapse: change clock rate (old rate = 0)
[ 2979.058964] resout_irq_handler PMIC Initiated shutdown
[ 2979.059025] PMIC Initiated shutdown cpu_power_off cpu=0
[ 2979.059056] [K] Powering off the SoC
[ 2979.059117] Calling scm to disable arbiter
[ 2979.059239] SCM returned even when asked to busy loop rc=-4
[ 2979.059270] waiting on pmic to shut msm down
Are those from the same reboot? I'm not seeing a specific error.
Sent from my EVO using Tapatalk 2
thicklizard said:
Are those from the same reboot? I'm not seeing a specific error.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
They are from different ones. My phone didn't reboot it just froze while the was screen off, so i couldn't get my device to wake basically. Sometimes is happens to freeze while im using it, but it hasn't rebooted me in the past 24 hrs. I have to manually restart by emulating batt pull and then my phone will run fine for hours then it just happens again. I should also add in that i haven't gotten stuck at bootani screen in the past 24 hours.
Also one time i was in the middle phone call and my screen was off, and my device wouldn't wake, but i was still connected to my call and my phone was really hot
I had no problems with my previous evo lte phone and i'm pretty sure i'm wiping and flashing everything correctly.
Maybe pull SD, format and retry?
Sent from my Evo 4G LTE using xda app-developers app
waterbound said:
Maybe pull SD, format and retry?
Sent from my Evo 4G LTE using xda app-developers app
Click to expand...
Click to collapse
Pull sd??.... Take out external??.... Format everything including internal sd and external??
Sent from my EVO using xda premium
I wiped everything including internal and external sd, after backing up the necessities. Will report back in a few on how it goes.
It random rebooted me, so after reboot i wanted to pull the last_kmsg but it rebooted while i was copying the file
after reboot a second time, i tried to do the pull it again and as i was hold clicking the last_kmsg file the system rebooted again.
Now im stuck at bootani
Are you familiar with adb logcat?
Sent from my EVO using Tapatalk 2
thicklizard said:
Are you familiar with adb logcat?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
i can be...lol
you want me to run that command in terminal while phone is plugged in??
i also was able to get my phone to boot by fixing perm in recovery
bxmoney181 said:
i can be...lol
you want me to run that command in terminal while phone is plugged in??
i also was able to get my phone to boot by fixing perm in recovery
Click to expand...
Click to collapse
A logcat will also help because the last kmsg isn't telling me what I want.
Sent from my EVO using Tapatalk 2
heres last_kmsg
thicklizard said:
A logcat will also help because the last kmsg isn't telling me what I want.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
so just run that command and wait till it reboots again then copy what have from terminal so you can see??
Yep
Sent from my EVO using Tapatalk 2
thicklizard said:
Yep
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
But sometimes it runs for many hours without any problems...i'll just try to keep this running as often as possible...thanks for you help

Swap space Issue with 3G modem

Dear All,
I am working on 3G modem integration with Android .I am using Texas Instruments am335X Starter kit and and Android Source Provided by Texas. I have Integrated Driver For 3G modem with this Android Source.
3g Modem gets Connected to Internet and also it can browse the web pages for some time.
I analysed RAM usage From Settings App. While Running The Browser I can See 80 to 90 MB of Free RAM Space.
Still Starter kit becomes unresponsive and gets hanged and restarts.
From the Logcats it seems to be an issue of swap cache . Please Suggest How can I resolve this Issue?
Followings are my logcat messages:->
[ 799.801239] Mem-info:
[ 799.803588] Normal per-cpu:
[ 799.806518] CPU 0: hi: 90, btch: 15 usd: 0
[ 799.811523] active_anon:30212 inactive_anon:67 isolated_anon:0
[ 799.811523] active_file:1403 inactive_file:1540 isolated_file:0
[ 799.811553] unevictable:0 dirty:0 writeback:6 unstable:0
[ 799.811553] free:511 slab_reclaimable:1029 slab_unreclaimable:2018
[ 799.811553] mapped:22156 shmem:74 pagetables:1449 bounce:0
[ 799.841857] Normal free:2044kB min:2036kB low:2544kB high:3052kB active_anon:
120848kB inactive_anon:268kB active_file:5612kB inactive_file:6160kB unevictable
:0kB isolated(anon):0kB isolated(file):0kB present:260096kB mlocked:0kB dirty:0k
B writeback:24kB mapped:88624kB shmem:296kB slab_reclaimable:4116kB slab_unrecla
imable:8072kB kernel_stack:3528kB pagetables:5796kB unstable:0kB bounce:0kB writ
eback_tmp:0kB pages_scanned:37608 all_unreclaimable? yes
[ 799.883361] lowmem_reserve[]: 0 0
[ 799.886840] Normal: 5*4kB 29*8kB 22*16kB 19*32kB 11*64kB 1*128kB 0*256kB 0*51
2kB 0*1024kB 0*2048kB 0*4096kB 0*8192kB = 2044kB
[ 799.898712] 3017 total pagecache pages
[ 799.902618] 0 pages in swap cache
[ 799.906066] Swap cache stats: add 0, delete 0, find 0/0
[ 799.911499] Free swap = 0kB
[ 799.914520] Total swap = 0kB
[ 799.927947] 65536 pages of RAM
[ 799.931152] 1072 free pages
[ 799.934082] 2954 reserved pages
[ 799.937377] 3047 slab pages
[ 799.940277] 71306 pages shared
[ 799.943450] 0 pages swap cached
[ 799.946746] [ pid ] uid tgid total_vm rss cpu oom_adj oom_score_adj n
ame
[ 799.954498] [ 59] 0 59 88 22 0 -16 -941 u
eventd
[ 799.962493] [ 67] 1000 67 223 57 0 -16 -941 s
ervicemanager
[ 799.971130] [ 68] 0 68 1019 108 0 -16 -941 v
old
[ 799.978881] [ 70] 0 70 227 60 0 -16 -941 u
im-sysfs
[ 799.987060] [ 71] 0 71 2477 153 0 -16 -941 n
etd
[ 799.994781] [ 72] 0 72 679 518 0 -16 -941 d
ebuggerd
[ 800.002960] [ 73] 1000 73 7527 4382 0 -16 -941 s
urfaceflinger
[ 800.011596] [ 74] 0 74 114617 2975 0 -16 -941 z
ygote
[ 800.019500] [ 75] 1019 75 2251 242 0 -16 -941 d
rmserver
[ 800.027679] [ 76] 1013 76 6651 458 0 -16 -941 m
ediaserver
[ 800.036071] [ 77] 1012 77 229 71 0 -16 -941 i
nstalld
[ 800.044128] [ 78] 1017 78 458 103 0 -16 -941 k
eystore
[ 800.052246] [ 79] 1001 79 1787 485 0 -16 -941 r
ild
[ 800.059967] [ 83] 1023 83 582 72 0 -16 -941 s
dcard
[ 800.067871] [ 84] 0 84 206 54 0 -16 -941 s
h
[ 800.075439] [ 323] 1000 323 136825 5403 0 -16 -941 s
ystem_server
[ 800.083953] [ 405] 10005 405 122482 7394 0 -16 -941 n
droid.systemui
[ 800.092681] [ 466] 10026 466 118226 3371 0 -16 -941 d
.process.media
[ 800.101409] [ 481] 10039 481 117998 3178 0 -16 -941 p
utmethod.latin
[ 800.110137] [ 496] 1001 496 120847 3551 0 -16 -941 m
.android.phone
[ 800.118865] [ 508] 10012 508 125824 8852 0 -16 -941 n
droid.launcher
[ 800.127593] [ 544] 10031 544 116701 2985 0 -16 -941 .
location.fused
[ 800.136291] [ 568] 10006 568 122772 3617 0 -16 -941 d
.process.acore
[ 800.145019] [ 587] 10009 587 116750 3004 0 -16 -941 a
ndroid.smspush
[ 800.153747] [ 596] 10021 596 117133 3057 0 -16 -941 m
.android.music
[ 800.162475] [ 653] 0 653 862 16 0 -16 -941 a
dbd
[ 800.170196] [ 660] 10001 660 119349 3227 0 -16 -941 m
.android.email
[ 800.178924] [ 700] 10022 700 118264 3066 0 -16 -941 n
droid.exchange
[ 800.187652] [ 717] 10025 717 117664 3133 0 -16 -941 d
roid.deskclock
[ 800.196380] [ 744] 10042 744 118859 3209 0 -16 -941 v
iders.calendar
[ 800.205108] [ 760] 10007 760 121618 3144 0 -16 -941 n
droid.calendar
[ 800.213806] [ 800] 10034 800 123166 7028 0 -16 -941 o
id.development
[ 800.222534] [ 815] 10002 815 116744 2991 0 -16 -941 a
ndroid.musicfx
[ 800.231262] [ 880] 10020 880 117221 3063 0 -16 -941 i
d.defcontainer
[ 800.239990] [ 930] 0 930 545 103 0 -16 -941 p
ppd
[ 800.247741] [ 1040] 10013 1040 141441 18238 0 -16 -941 a
ndroid.browser
[ 800.256439] Out of memory: Kill process 59 (ueventd) score 1 or sacrifice chi
ld
[ 800.264068] Killed process 59 (ueventd) total-vm:352kB, anon-rss:84kB, file-r
ss:4kB
Thanks And Regards,
Vinod

Decrypting misc to get model number for TWRP/ROMs

Hey everyone,
I need some community help. I wanna find out which part of the misc partition tells the kernel the model (and also the color lol). Stock kernel logs this on boot (even on non stock based roms), but i couldnt find where it reads it in the kernel source
Thats where i need the community. It logs that it reads the hwinfo from the misc partition, but unlike older phones, it isnt in plain text anymore.
I need some more samples of misc partitions from various devices (and colors, if possible) to find out which bit in that partitions is for what.
My goal with this:
Make the recovery set on boot which model it is running on
Do the same for future ROMs
But misc should (or atleast in the past) contain also wifi/bt mac adresses. Just giving you the information here, in case you dont want that to be publicy shared.
Instructions on how to get the image:
Open terminal app (any will do, even adb would work)
su <enter> (and grant permissions)
dd if=/dev/block/bootdevice/by-name/misc of=/sdcard/misc_<model>_<color>.img
Examples:
Code:
su
dd if=/dev/block/bootdevice/by-name/misc of=/sdcard/misc_h930_blue.img
dd if=/dev/block/bootdevice/by-name/misc of=/sdcard/misc_h930_silver.img
dd if=/dev/block/bootdevice/by-name/misc of=/sdcard/misc_h930g_black.img
dd if=/dev/block/bootdevice/by-name/misc of=/sdcard/misc_us998_silver.img
If you dont care about your wifi/bt mac possibly be made public, attach it on a post, otherwise send me a PM
Thanks in advance
It doesn't get that info from misc, it gets it from the bootloader.
-- Brian
runningnak3d said:
It doesn't get that info from misc, it gets it from the bootloader.
-- Brian
Click to expand...
Click to collapse
Ohhh. You sure about that though?
have this in my logs:
Code:
03-04 01:28:10.053 0 0 I [ 0.788138 / 01-01 00:00:00.779][4] 0: ftm_get_item.
03-04 01:28:10.053 0 0 I [ 0.788170 / 01-01 00:00:00.779][4] suffix: LGH930.ADECBL, suffix_length : 13
03-04 01:28:10.053 0 0 I [ 0.788198 / 01-01 00:00:00.779][4] suffix: LGH930.ADECBL, Color :BL
03-04 01:28:10.053 0 0 I [ 0.788211 / 01-01 00:00:00.779][4] BL: color.
03-04 01:28:10.053 0 0 I : [ 0.788224 / 01-01 00:00:00.779][4] UFS SAMSUNG
03-04 01:28:10.053 0 0 I [ 0.788276 / 01-01 00:00:00.779][4] bootcmd_set_one_binary: bootcmd_set_one_binary ** bootcmd_set_one_binary
03-04 01:28:10.053 0 0 I [ 0.788321 / 01-01 00:00:00.779][4] lge_one_binary_read_flex_gpio: [FLEX_GPIO] flex_gpio_sum[0]
03-04 01:28:10.053 0 0 I : [ 0.788350 / 01-01 00:00:00.779][4] id = 103 get_ftm_one_binary_hwinfo()
03-04 01:28:10.053 0 0 I [ 0.788393 / 01-01 00:00:00.779][4] lge_one_binary_read_hwinfo: HWINFO from misc partition (2)
03-04 01:28:10.053 0 0 I [ 0.788428 / 01-01 00:00:00.779][4] lge_one_binary_read_hwinfo: version = 0x10004
03-04 01:28:10.053 0 0 I [ 0.788465 / 01-01 00:00:00.779][4] lge_one_binary_read_hwinfo: model_name = LG-H930
03-04 01:28:10.053 0 0 I [ 0.788518 / 01-01 00:00:00.779][4] lge_one_binary_copy_hwinfo: model_name = LG-H930 , misc.model_name = LG-H930
03-04 01:28:10.053 0 0 I [ 0.788557 / 01-01 00:00:00.779][4] lge_one_binary_init: use HWINFO from misc partition
03-04 01:28:10.053 0 0 I [ 0.788595 / 01-01 00:00:00.779][4] lge_one_binary_init: Model Name = LG-H9 -> LG-H930
03-04 01:28:10.053 0 0 I [ 0.788640 / 01-01 00:00:00.779][4] bootcmd_add_pair: already exist key & value(model.name, LG-H930)
03-04 01:28:10.053 0 0 I [ 0.788681 / 01-01 00:00:00.779][4] lge_one_binary_get_sim_num: sim_num return value = 1
Thats why i thought its still in misc, but instead of plain text, just kinda encrypted.
But i suppose that would make things way easier
(as long as /proc/cmdline is always and as early as possible available)
Just checked that on my H930, has model number and so on set, just have to make sure it also gets set appropriate on the LOS builds (and twrp)
You are definitely correct. I apologise, my info is out of date when it comes to the V30. I do know that (as you saw) the information is available from the bootloader as well.
You should be able to parse /proc immediately after the kernel boots and init starts, so I still think that is the way to go.
-- Brian
Yeah, will do it that way
probably just gonna do it with an init script... getting familiar with shell scripts now xD
Annoying though i have to use sh and cant use bash commands... Most solutions i find are for bash, but i guess i found something that works with sh

[ROM][UNOFFICIAL][12L][EAS][SM-T820][SM-T825][2022-09-23] LineageOS 19.1 for Galaxy Tab S3

Code:
/*
* Your warranty will be VOID after installing a custom ROM.
*
* Get notified yourself that I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in this ROM
* before flashing it!
* YOU are choosing to make these modifications,
* and if you point the finger at me for messing up your device,
* I will laugh at you.
*/
# LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
# What's working
Display/Touchscreen
LiveDisplay
Audio playback
Dolby Atmos
Headphone/Headset
Quad speakers
Video playback
HDR
Camera
Microphone
Sensors
Fingerprint sensor
GPS
LTE (SM-T825)
Hotspot
WiFi
WiFi display
Bluetooth
DRM
Widevine L1
USB ADB/MTP
Samsung Doze
S-Pen
Palm rejection
Hardware Encryption
MDFPP
SD Card
Power-off mode charging
# Untested
FBE for userdata
# What's not working
USB OTG
SELinux permissive
Please see the "Known issues" part of this post
# Downloads
## LineageOS 19.1
Galaxy Tab S3 LTE (gts3llte, SM-T825)
Galaxy Tab S3 WiFi (gts3lwifi, SM-T820)
## Google Apps
NikGapps
The other Gapps will work too, but I only confirmed that NikGapps working
## TWRP Recovery
You can use mine, please visit this thread.
[RECOVERY][SM-T820][SM-T825][UNOFFICIAL] TWRP for Galaxy Tab S3
# How to install
Unlock the bootloader.
Download TWRP and flash the recovery image via Odin.
Download LineageOS 19.1 for Galaxy Tab S3.
Be aware of the board name.
Download GAPPS for Android 12L and the others you want to flash.
Enter TWRP recovery.
The first boot to TWRP might be very slow because of the unmatched file systems.
Format the whole system, data, cache partitions using the format menu.
You will type `yes` to do that.
Flash the images.
If you're going to install GApps or something, you have to install the LineageOS first.
Reboot the system.
Done.
# Known issues
Camera somewhat buggy
The built-in camera application (Camera2) is not working well. You can use another camera application like OpenCamera.
Sometimes the camera doesn't work after booting. You can fix that back by just rebooting.
After using the camera application, the Torch tile on the quick settings not working. But you can use the camera anyway.
On webcam chat apps, there is a vertical green bar and the color is not properly displayed.
Audio bugs
No sound for the microphone and speaker in voice calls, such as the regular phone call or voice chat with a meeting app.
Thank all of you for the feedback
# Sources
Device Tree
gts3l-common: https://github.com/awesometic/android_device_samsung_gts3l-common
gts3llte: https://github.com/awesometic/android_device_samsung_gts3llte
gts3lwifi: https://github.com/awesometic/android_device_samsung_gts3lwifi
Kernel: https://github.com/awesometic/android_kernel_samsung_msm8996
Vendor: https://github.com/awesometic/proprietary_vendor_samsung
# Telegram Groups
If you are interested in developing this potential machine, please tell me through PM then I will send you the invitation link.
If you need a general discussion channel for this potential machine or want to share the news of its Android projects from anyone to everyone, you can join our discussion group chat.
Galaxy Tab S3 General Discussion
# Buy me a coffee
If you like my efforts or would like to support me, please don't hesitate to buy me a cup of coffee.
https://www.paypal.com/paypalme/awesometic
# Credits / Special thanks to
Android Open Source Project
LineageOS Team
LOS17.1) @Valera1978 for his amazing previous work including his MSM8996 kernel
LOS18.1) @supermike86 and @samsuffit for testing LineageOS 18.1 for T820, which is I don't have one
LOS18.1) @bmwdroid and @cherepanov for confirming the LTE works
LOS18.1) @sebmue for letting me know that the useful information for palm rejection, and @ghostwheel for sharing its working source codes on Android 9
General) @switchgott for helping me in the development discussion and creating Telegram groups
General) All from our Telegram discussion channel, @EonOfBlack , Sands, David Becker, ...
LOS18.1) @LuK1337 for giving me a hint to fix the quad-speakers
LOS19.1) @followmsi , @html6405 , @ThE_MarD for giving me a hint to bring up Android 12
LOS19.1) @masdaster for the fix of MDFPP Keystore on our device
## Changelogs
2022. 9. 23
Synced with the latest LineageOS 19.1 repositories
Security patch by September 5, 2022
2022. 8. 15
Synced with the latest LineageOS 19.1 repositories
android-12.1.0_r22
Security patch by August 5, 2022
About Keystore, switch to use MDFPP skeymast files again.
This will break your lock screen. Please remove `/data/system/locksettings.db` file using TWRP, then lock screen will be fixed and your biometric information will be removed. Please reset your biometric lock method again. Sorry for the inconvenience.
Thank you for the idea and contribution for the proper use of our MDFPP Keystore, @masdaster
2022. 7. 15
Synced with the latest LineageOS 19.1 repositories
android-12.1.0_r11
Security patch by July 5, 2022
Added support for Sony DualShock 4 gamepad
Increased headphone jack volume by about 20%
Updated USB HAL to v1.3
2022. 6. 11
Synced with the latest LineageOS 19.1 repositories
android-12.1.0_r7
Security patch by June 5, 2022
Fixed camera working
It is somewhat buggy, you can see the notes on the original post
Fixed Bluetooth/headphone jack audio working
Now it builds the AOSP audio stack from the source
Fixed arrow keys orientation on the S3 Book cover keyboard in landscape mode
Thanks to @roesja
[ROM][UNOFFICIAL][11][EAS][SM-T820][SM-T825][2022-05-08] LineageOS 18.1 for Galaxy Tab S3 | Page 24 | XDA Forums (xda-developers.com)
2022. 4. 16
Synced with the latest LineageOS 19.1 repositories
android-12.1.0_r4
Fixed the boot failure issue for some users
It is related to the Keystore of the Android system, I did a little compromise to make it work for all users
If you are using the first version (220320), you have to clean install to this version or you may fail to unlock the screen , you have to boot into TWRP and remove the file `locksettings.db` under `/data/system` directory. This will resolve the unlock failure issue after dirty-flashing it.
Thanks for this information, David Becker.
2022. 3. 20
Initial release
## Special Notes
You must do clean-install if you are willing to upgrade from another ROM such as an Android 11 based one
I have tested Magisk 24.3 working
You can fix SafetyNet using Magisk modules, SafetyNet Fix and PropsConfig
You can hide the soft nav buttons on the bottom bar. This is the workaround.
1. Go to "System -> Buttons" and check "Enable on-screen nav bar" to enable soft nav bar temporarily
2. Go to "System -> Gestures" and set "System navigation" to "Gesture navigation"
3. Go back to "System -> Buttons" and check "Enable on-screen nav bar" again to disable soft nav bar and enable hardware key.
You can hide the bottom Taskbar. This is the workaround.
1. Go to "System -> Buttons" and check "Enable on-screen nav bar" to enable soft nav bar temporarily
2. Go back using navigation bar and go to the "Buttons" menu again
3. Then we can see the "Enable taskbar" option that we couldn't see before. Disable that option.
4. And disable "Enable on-screen nav bar" option again to use the hardware buttons back.
reserved
I regret to say that the best rom produced for this tablet so far is the rom in the link below, while the others have never been fully stable.
[ROM] SM-T825 TWEAKED.........................[rom] sm-t825 tweaked.
SM-T825 TWEAKED 5.1 ***** PIE ***** 20JUN2020 T825_CTD1_TWEAKED_5.1_DB4_by_rorymc928 Based on latest stock CTD1 firmware Tweaked, stable, zip aligned. SU/D Forced encryption disabled Deknoxed Debloated (GPU driver updated to latest adreno...
forum.xda-developers.com
bozkurtum said:
I regret to say that the best rom produced for this tablet so far is the rom in the link below, while the others have never been fully stable.
[ROM] SM-T825 TWEAKED.........................[rom] sm-t825 tweaked.
SM-T825 TWEAKED 5.1 ***** PIE ***** 20JUN2020 T825_CTD1_TWEAKED_5.1_DB4_by_rorymc928 Based on latest stock CTD1 firmware Tweaked, stable, zip aligned. SU/D Forced encryption disabled Deknoxed Debloated (GPU driver updated to latest adreno...
forum.xda-developers.com
Click to expand...
Click to collapse
Yes it is If you want the best stability the answer is always the stock firmware or a stock-based ROM.
Hello,
First thank very much for your work, your roms are fantastic the version of lineageos 18.1 and HAVOC,
this first version is causing a bootloop I don't know if it can help I'm adding the device boot logs:
Code:
12-12 20:39:51.806 0 0 E [0: surfaceflinger:14610] subsys-restart: __subsystem_get(): __subsystem_get: a530_zap count:0
12-12 20:39:51.812 0 0 I [0: ueventd:14611] ueventd: firmware: loading 'a530_zap.mdt' for '/devices/soc/soc:qcom,kgsl-hyp/firmware/a530_zap.mdt'
12-12 20:39:51.813 0 0 I : [0: surfaceflinger:14610] subsys-pil-tz soc:qcom,kgsl-hyp: a530_zap: loading from 0x000000008f400000 to 0x000000008f402000
12-12 20:39:51.813 0 0 I [2: ueventd:14611] ueventd: loading /devices/soc/soc:qcom,kgsl-hyp/firmware/a530_zap.mdt took 1ms
12-12 20:39:51.831 0 0 E : [0: surfaceflinger:14610] scm_call failed: func id 0x42000201, ret: -1, syscall returns: 0x0, 0x0, 0x0
12-12 20:39:51.831 0 0 E : [0: surfaceflinger:14610] subsys-pil-tz soc:qcom,kgsl-hyp: a530_zap: Invalid firmware metadata
12-12 20:39:51.836 14606 14610 E Adreno-GSL: <ioctl_kgsl_driver_entry:873>: open(/dev/kgsl-3d0) failed: errno 5. I/O error
12-12 20:39:51.836 14606 14610 W libEGL : eglInitialize(0x75770d4530) failed (EGL_BAD_ALLOC)
12-12 20:39:51.837 14606 14610 W RenderEngine: no suitable EGLConfig found, trying a simpler query
12-12 20:39:51.837 14606 14610 F RenderEngine: no suitable EGLConfig found, giving up
12-12 20:39:51.837 14606 14610 F libc : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 14610 (surfaceflinger), pid 14606 (surfaceflinger)
12-12 20:39:51.859 14614 14614 I crash_dump64: obtaining output fd from tombstoned, type: kDebuggerdTombstoneProto
12-12 20:39:51.861 633 633 I tombstoned: received crash request for pid 14610
12-12 20:39:51.861 14614 14614 I crash_dump64: performing dump of process 14606 (target tid = 14610)
12-12 20:39:51.873 14255 14255 W ServiceManager: Waited one second for SurfaceFlinger (is service started? are binder threads started and available?)
12-12 20:39:51.873 586 586 I servicemanager: Since 'SurfaceFlinger' could not be found, trying to start it as a lazy AIDL service
12-12 20:39:51.875 586 14617 W libc : Unable to set property "ctl.interface_start" to "aidl/SurfaceFlinger": error code: 0x20
12-12 20:39:51.875 586 14617 I servicemanager: Tried to start aidl service SurfaceFlinger as a lazy service, but was unable to. Usually this happens when a service is not installed, but if the service is intended to be used as a lazy service, then it may be configured incorrectly.
12-12 20:39:51.874 0 0 E [1: init: 1] init: Control message: Could not find 'aidl/SurfaceFlinger' for ctl.interface_start from pid: 586 (/system/bin/servicemanager)
12-12 20:39:51.928 0 0 I [3: logd.reader: 594] logd: logdr: UID=1000 GID=1003 PID=14614 n tail=0 logMask=8 pid=14606 start=0ns deadline=0ns
12-12 20:39:51.934 0 0 I [2: logd.reader: 594] logd: logdr: UID=1000 GID=1003 PID=14614 n tail=0 logMask=1 pid=14606 start=0ns deadline=0ns
12-12 20:39:51.947 14614 14614 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
12-12 20:39:51.947 14614 14614 F DEBUG : Build fingerprint: 'samsung/gts3lltekx/gts3lltekx:9/PPR1.180610.011/T825N0KOU3CTD1:user/release-keys'
12-12 20:39:51.947 14614 14614 F DEBUG : Revision: '5'
12-12 20:39:51.947 14614 14614 F DEBUG : ABI: 'arm64'
12-12 20:39:51.947 14614 14614 F DEBUG : Timestamp: 1970-12-12 20:39:51.864459376+0000
12-12 20:39:51.947 14614 14614 F DEBUG : Process uptime: 1s
12-12 20:39:51.947 14614 14614 F DEBUG : Cmdline: /system/bin/surfaceflinger
12-12 20:39:51.947 14614 14614 F DEBUG : pid: 14606, tid: 14610, name: surfaceflinger >>> /system/bin/surfaceflinger <<<
12-12 20:39:51.947 14614 14614 F DEBUG : uid: 1000
12-12 20:39:51.947 14614 14614 F DEBUG : signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
12-12 20:39:51.947 14614 14614 F DEBUG : Abort message: 'no suitable EGLConfig found, giving up'
12-12 20:39:51.947 14614 14614 F DEBUG : x0 0000000000000000 x1 0000000000003912 x2 0000000000000006 x3 00000074b4fc9340
12-12 20:39:51.947 14614 14614 F DEBUG : x4 00000000000c4ad0 x5 00000000000c4ad0 x6 00000000000c4ad0 x7 0000000000000018
12-12 20:39:51.947 14614 14614 F DEBUG : x8 00000000000000f0 x9 e6e2a24fe5d8bd5e x10 0000000000000000 x11 ffffff80ffffffdf
12-12 20:39:51.947 14614 14614 F DEBUG : x12 0000000000000001 x13 0000000000000027 x14 00000074b4fc94d0 x15 0000000000000038
12-12 20:39:51.947 14614 14614 F DEBUG : x16 000000774718c050 x17 0000007747168d20 x18 00000074b4048000 x19 000000000000390e
12-12 20:39:51.947 14614 14614 F DEBUG : x20 0000000000003912 x21 00000000ffffffff x22 00000074b4fca000 x23 00000075770d4530
12-12 20:39:51.948 14614 14614 F DEBUG : x24 00000075670d5330 x25 00000074b4fc9cb0 x26 00000074b4fc9ff8 x27 00000074b4fc9ab0
12-12 20:39:51.948 14614 14614 F DEBUG : x28 00000074b4ed1000 x29 00000074b4fc93c0
12-12 20:39:51.948 14614 14614 F DEBUG : lr 000000774711ba14 sp 00000074b4fc9320 pc 000000774711ba40 pst 0000000000000000
12-12 20:39:51.948 14614 14614 F DEBUG : backtrace:
12-12 20:39:51.948 14614 14614 F DEBUG : #00 pc 000000000004fa40 /apex/com.android.runtime/lib64/bionic/libc.so (abort+164) (BuildId: 443fdffc7b7209cc7b1cd55c1acaa73c)
12-12 20:39:51.948 14614 14614 F DEBUG : #01 pc 00000000000062c0 /system/lib64/liblog.so (__android_log_default_aborter+12) (BuildId: 9421b4c67db0120bbd4cd8c6d66b9982)
12-12 20:39:51.948 14614 14614 F DEBUG : #02 pc 0000000000006dc8 /system/lib64/liblog.so (__android_log_assert+308) (BuildId: 9421b4c67db0120bbd4cd8c6d66b9982)
12-12 20:39:51.948 14614 14614 F DEBUG : #03 pc 00000000002671f4 /system/bin/surfaceflinger (android::renderengine::skia::SkiaGLRenderEngine::chooseEglConfig(void*, int, bool)+496) (BuildId: 3c42cc1fc3af8ae53d4848beb2aed0bc)
12-12 20:39:51.948 14614 14614 F DEBUG : #04 pc 000000000027a4d0 /system/bin/surfaceflinger (android::renderengine::skia::SkiaGLRenderEngine::create(android::renderengine::RenderEngineCreationArgs const&)+164) (BuildId: 3c42cc1fc3af8ae53d4848beb2aed0bc)
12-12 20:39:51.948 14614 14614 F DEBUG : #05 pc 0000000000265ce0 /system/bin/surfaceflinger (_ZNSt3__110__function6__funcIZN7android12renderengine12RenderEngine6createERKNS3_24RenderEngineCreationArgsEE3$_1NS_9allocatorIS8_EEFNS_10unique_ptrIS4_NS_14default_deleteIS4_EEEEvEEclEv$fb147fdbd0638d73632d1b87d1d565c9+40) (BuildId: 3c42cc1fc3af8ae53d4848beb2aed0bc)
12-12 20:39:51.948 14614 14614 F DEBUG : #06 pc 0000000000276c28 /system/bin/surfaceflinger (android::renderengine::threaded::RenderEngineThreaded::threadMain(std::__1::function<std::__1::unique_ptr<android::renderengine::RenderEngine, std::__1::default_delete<android::renderengine::RenderEngine> > ()>)+376) (BuildId: 3c42cc1fc3af8ae53d4848beb2aed0bc)
12-12 20:39:51.948 14614 14614 F DEBUG : #07 pc 0000000000278f88 /system/bin/surfaceflinger (void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (android::renderengine::threaded::RenderEngineThreaded::*)(std::__1::function<std::__1::unique_ptr<android::renderengine::RenderEngine, std::__1::default_delete<android::renderengine::RenderEngine> > ()>), android::renderengine::threaded::RenderEngineThreaded*, std::__1::function<std::__1::unique_ptr<android::renderengine::RenderEngine, std::__1::default_delete<android::renderengine::RenderEngine> > ()> > >(void*)+160) (BuildId: 3c42cc1fc3af8ae53d4848beb2aed0bc)
12-12 20:39:51.948 14614 14614 F DEBUG : #08 pc 00000000000b1780 /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+264) (BuildId: 443fdffc7b7209cc7b1cd55c1acaa73c)
12-12 20:39:51.948 14614 14614 F DEBUG : #09 pc 0000000000051264 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: 443fdffc7b7209cc7b1cd55c1acaa73c)
12-12 20:39:51.963 14614 14614 E crash_dump64: unable to connect to activity manager: No such file or directory
12-12 20:39:51.963 633 633 E tombstoned: Tombstone written to: tombstone_15
12-12 20:39:51.966 0 0 I [3: init: 1] init: Untracked pid 14614 exited with status 0
12-12 20:39:51.972 0 0 I [3: init: 1] init: Service 'surfaceflinger' (pid 14606) received signal 6
12-12 20:39:51.972 0 0 I [3: init: 1] init: Sending signal 9 to service 'surfaceflinger' (pid 14606) process group...
12-12 20:39:51.972 0 0 I [3: init: 1] libprocessgroup: Successfully killed process cgroup uid 1000 pid 14606 in 0ms
12-12 20:39:51.972 0 0 I [3: init: 1] init: Sending signal 9 to service 'zygote' (pid 14232) process group...
12-12 20:39:51.972 0 0 I [3: init: 1] libprocessgroup: Successfully killed process cgroup uid 0 pid 14232 in 0ms
12-12 20:39:51.974 0 0 I [0: init: 1] init: Untracked pid 14616 exited with status 0
12-12 20:39:51.975 0 0 I [0: init: 1] init: processing action (init.svc.surfaceflinger=restarting) from (/vendor/etc/init/hw/init.qcom.rc:920)
12-12 20:39:51.975 0 0 I [0: init: 1] init: Sending signal 9 to service 'vendor.hwcomposer-2-1' (pid 742) process group...
12-12 20:39:51.975 0 0 I [0: init: 1] libprocessgroup: Successfully killed process cgroup uid 1000 pid 742 in 0ms
12-12 20:39:51.976 0 0 I [0: init: 1] init: processing action (init.svc.surfaceflinger=restarting) from (/vendor/etc/init/hw/init.target.rc:459)
12-12 20:39:51.977 0 0 I [0: init: 1] init: Sending signal 9 to service 'ppd' (pid 877) process group...
12-12 20:39:51.977 0 0 I [0: init: 1] libprocessgroup: Successfully killed process cgroup uid 1000 pid 877 in 0ms
12-12 20:39:52.089 0 0 W [0:android.hardwar:14604] scm: secure world has been busy for 1 second!
12-12 20:39:52.227 0 0 I [0: kworker/u8:0: 6] sm5705_get_curr: <1 0 100 10> info.volt_cal = 0x8000, volt_slope = 0x8000, mohm_volt_cal = 0x0
12-12 20:39:52.229 0 0 I [0: kworker/u8:0: 6] sm5705_get_curr: <1 0 100 10> info.volt_cal = 0x8000, volt_slope = 0x8000, mohm_volt_cal = 0x0
12-12 20:39:52.260 0 0 I [0: kworker/u8:0: 6] sm5705-charger: sm5705_chg_test_read: [CHG] 0x04:0xfe, 0x05:0xbf, 0x06:0xfb, 0x07:0xff, 0x08:0x29, 0x09:0x18, 0x0A:0x00, 0x0B:0x00, 0x0C:0x05, 0x0D:0x10, 0x0E:0x1c, 0x0F:0x03, 0x10:0x08, 0x11:0x12, 0x12:0x5f, 0x13:0x0c, 0x14:0x02, 0x15:0x2c, 0x16:0x18, 0x17:0x1c, 0x20:0x05, 0x21:0x00,
12-12 20:39:52.272 0 0 I [2: kworker/u8:0: 6] sm5705-charger: sm5705_chg_test_read: [CHG] 0x04:0xfe, 0x05:0xbf, 0x06:0xfb, 0x07:0xff, 0x08:0x29, 0x09:0x18, 0x0A:0x00, 0x0B:0x00, 0x0C:0x05, 0x0D:0x10, 0x0E:0x1c, 0x0F:0x03, 0x10:0x08, 0x11:0x12, 0x12:0x5f, 0x13:0x0c, 0x14:0x02, 0x15:0x2c, 0x16:0x18, 0x17:0x1c, 0x20:0x05, 0x21:0x00,
12-12 20:39:52.276 0 0 I [2: kworker/u8:0: 6] sm5705_get_curr: <1 0 100 10> info.volt_cal = 0x8000, volt_slope = 0x8000, mohm_volt_cal = 0x0
12-12 20:39:52.278 0 0 I [2: kworker/u8:0: 6] sm5705_vbatocv_check: mode change to mix RS auto mode
12-12 20:39:52.282 0 0 I [2: kworker/u8:0: 6] sm5705_cal_carc: <1 6 1 11 -1 1 6 1 9 1>, temp_fg = 363 ,p_curr_cal = 0x9b, n_curr_cal = 0xa6, curr_offset = 0x1, volt_cal = 0x8000 ,fg_delta_volcal = 0x0
12-12 20:39:52.283 0 0 I [2: kworker/u8:0: 6] sm5705_cal_carc: <1 3 0 3 1 1 2 3 2 3>, p_curr_cal = 0x9b, n_curr_cal = 0xa7, mix_factor=0x47a ,batt_temp = 286
12-12 20:39:52.286 0 0 I [2: kworker/u8:0: 6] sm5705_fg_check_reg_init_need: SM5705_REG_FG_OP_STATUS : 0x10 , return 0
12-12 20:39:52.291 0 0 I [2: kworker/u8:0: 6] sm5705_fg_test_read: 0xA0=0x1400, 0xAC=0x20a5, 0xAD=0x211b, 0xAE=0x21f7, 0xAF=0x2399, 0x28=0x0838, 0x2F=0x021a, 0x01=0xc401, SM5705_ID=0x000b
12-12 20:39:52.298 0 0 I [2: kworker/u8:0: 6] sm5705_fg_test_read: 0xB0=0x0000, 0xBC=0x255e, 0xBD=0x283f, 0xBE=0x2d0c, 0xBF=0x2d17, 0x85=0x0064, 0x86=0x0196, 0x87=0x0ec4, 0x1F=0x0080, 0x94=0x0001 , 0x13=0x000f, 0x14=0x0000
12-12 20:39:52.299 0 0 I [2: kworker/u8:0: 6] sm5705_get_all_value: chg_h=1, chg_f=0, chg_s=1, is_chg=0, ta_exist=1, v=3790, v_avg=3786, i=-248, i_avg=-91, ocv=3779, fg_t=363, b_t=286, cycle=38, soc=327, state=0x6
12-12 20:39:52.299 0 0 I [2: kworker/u8:0: 6] sm5705_fg_get_scaled_capacity: scaled capacity (32.7)
12-12 20:39:52.299 0 0 I [2: kworker/u8:0: 6] sm5705_fg_get_atomic_capacity: NOW(32), OLD(32)
12-12 20:39:52.299 0 0 I : [2: kworker/u8:0: 6] sec-battery battery: sec_bat_get_battery_info:Vnow(3790mV),Inow(-248mA),Imax(500mA),SOC(32%),Tbat(286),Tchg(326),Twpc(0)
12-12 20:39:52.299 0 0 I : [2: kworker/u8:0: 6] sec-battery battery: sec_bat_cisd_check: cisd off.
12-12 20:39:52.311 0 0 I [2: kworker/u8:0: 6] sm5705-charger: sm5705_chg_test_read: [CHG] 0x04:0xfe, 0x05:0xbf, 0x06:0xfb, 0x07:0xff, 0x08:0x29, 0x09:0x18, 0x0A:0x00, 0x0B:0x00, 0x0C:0x05, 0x0D:0x10, 0x0E:0x1c, 0x0F:0x03, 0x10:0x08, 0x11:0x12, 0x12:0x5f, 0x13:0x0c, 0x14:0x02, 0x15:0x2c, 0x16:0x18, 0x17:0x1c, 0x20:0x05, 0x21:0x00,
12-12 20:39:52.323 0 0 I [2: kworker/u8:0: 6] sm5705-charger: sm5705_chg_test_read: [CHG] 0x04:0xfe, 0x05:0xbf, 0x06:0xfb, 0x07:0xff, 0x08:0x29, 0x09:0x18, 0x0A:0x00, 0x0B:0x00, 0x0C:0x05, 0x0D:0x10, 0x0E:0x1c, 0x0F:0x03, 0x10:0x08, 0x11:0x12, 0x12:0x5f, 0x13:0x0c, 0x14:0x02, 0x15:0x2c, 0x16:0x18, 0x17:0x1c, 0x20:0x05, 0x21:0x00,
12-12 20:39:52.323 0 0 I : [2: kworker/u8:0: 6] sec-battery battery: sec_bat_time_management: Charging Time : 1340 secs
12-12 20:39:52.324 0 0 I : [2: kworker/u8:0: 6] sec-battery battery: sec_bat_temperature: HLT(800) HLR(750) HT(500), HR(450), LT(0), LR(50)
12-12 20:39:52.324 0 0 I [2: kworker/u8:0: 6] sec_bat_swelling_check: status(1), swell_mode(0:0:0), cv(0x10cc), temp(286)
12-12 20:39:52.324 0 0 I : [2: kworker/u8:0: 6] sec-battery battery: sec_bat_fullcharged_check: Charging Mode : Normal
12-12 20:39:52.324 0 0 I [2: kworker/u8:0: 6] sec_bat_set_current_event: clear current event(now=0x0, value=0x4)
12-12 20:39:52.324 0 0 I [2: kworker/u8:0: 6] sec_bat_check_mix_temp: mix_limit(0), temp(286), chg_temp(326), input_current(500)
12-12 20:39:52.324 0 0 I [2: kworker/u8:0: 6] sec_bat_check_afc_temp: cable_type(4), chg_limit(0)
12-12 20:39:52.324 0 0 I : [2: kworker/u8:0: 6] sec-battery battery: sec_bat_monitor_work: Status(Charging), mode(Normal), Health(Good), Cable(4, 4, 1, 1), level(100%), cisd.cd(0), HV(NONE), sleep_mode(0), Cycle(-1)
12-12 20:39:52.325 0 0 I [2: kworker/2:1: 33] sm5705-charger: psy_chg_get_charge_type: psy_chg_get_charge_type charge_type(5)
12-12 20:39:52.325 0 0 I : [2: kworker/2:1: 33] sec_bat_get_property cable type = 4 sleep_mode = 0
12-12 20:39:52.327 0 0 I [2: kworker/2:1: 33] sm5705_fg_check_reg_init_need: SM5705_REG_FG_OP_STATUS : 0x10 , return 0
12-12 20:39:52.329 0 0 I [2:[email protected]: 743] sm5705_fg_check_reg_init_need: SM5705_REG_FG_OP_STATUS : 0x10 , return 0
12-12 20:39:52.330 0 0 W [2:[email protected]: 743] healthd: battery l=32 v=3790 t=28.6 h=2 st=2 c=-248 fc=6000000 chg=u
12-12 20:39:52.332 0 0 I [2:[email protected]: 743] sm5705_fg_check_reg_init_need: SM5705_REG_FG_OP_STATUS : 0x10 , return 0
12-12 20:39:52.609 0 0 E : [1: msm_watchdog: 32] [pet_watchdog] last_count : 502d6, new_count : 0, bark_time : 77fd3, bite_time : 8ffca
12-12 20:39:52.662 0 0 I [2: logd.reader: 594] logd: logdr: UID=2000 GID=2000 PID=14620 n tail=0 logMask=bf pid=0 start=0ns deadline=0ns
12-12 20:39:52.754 626 626 W HidlServiceManagement: Waited one second for [email protected]::IKeymasterDevice/default
12-12 20:39:52.755 587 587 I hwservicemanager: Since [email protected]::IKeymasterDevice/default is not registered, trying to start it as a lazy HAL.
12-12 20:39:52.755 626 626 I HidlServiceManagement: getService: Trying again for [email protected]::IKeymasterDevice/default...
12-12 20:39:52.757 0 0 I [1: init: 1] init: Control message: Processed ctl.interface_start for '[email protected]::IKeymasterDevice/default' from pid: 587 (/system/bin/hwservicemanager)
12-12 20:39:52.873 14255 14255 W ServiceManager: Waited one second for SurfaceFlinger (is service started? are binder threads started and available?)
12-12 20:39:52.875 586 586 I servicemanager: Since 'SurfaceFlinger' could not be found, trying to start it as a lazy AIDL service
12-12 20:39:52.877 586 14624 W libc : Unable to set property "ctl.interface_start" to "aidl/SurfaceFlinger": error code: 0x20
12-12 20:39:52.877 586 14624 I servicemanager: Tried to start aidl service SurfaceFlinger as a lazy service, but was unable to. Usually this happens when a service is not installed, but if the service is intended to be used as a lazy service, then it may be configured incorrectly.
12-12 20:39:52.876 0 0 E [1: init: 1] init: Control message: Could not find 'aidl/SurfaceFlinger' for ctl.interface_start from pid: 586 (/system/bin/servicemanager)
12-12 20:39:53.142 0 0 I : [1: kworker/u8:0: 6] etspi_work_func_debug ldo: 0, sleep: 0, tz: 1, type: unknown
12-12 20:39:53.386 14604 14604 E QSEECOMAPI: Error::Load image request failed ret = -1, errno = 22
12-12 20:39:53.386 14604 14604 E QSEECOMAPI: Error::Loading image failed with ret = -1
12-12 20:39:53.386 14604 14604 E keymaster_tee: [ERROR]: (nwd_keymaster_qualcomm.c:58) Loading app (path - /vendor/firmware_mnt/image) skeymast failed: Invalid argument, size = 82112, ret = -1
12-12 20:39:53.386 14604 14604 E keymaster_tee: [ERROR]: (nwd_keymaster_qualcomm.c:106) Fail to open session with QSEE
12-12 20:39:53.387 14604 14604 E keymaster_tee: [ERROR]: (nwd_keymaster_tc_api.c:78) KM_TZOpenConnection FAILED [-3]
12-12 20:39:53.387 14604 14604 E keymaster_tee: [ERROR]: (nwd_keymaster_mdfpp.cpp:1120) can't open connection to trustlet; error: -49
12-12 20:39:53.387 14604 14604 E [email protected]: Error -1 opening keystore keymaster1 device
12-12 20:39:53.387 14604 14604 I keymaster_tee: [INFO]: (nwd_keymaster_mdfpp.cpp:1028) entered device_close function
12-12 20:39:53.387 14604 14604 E keymaster_tee: [ERROR]: (nwd_keymaster_tc_api.c:119) There is no opened session. ref cnt = 0
12-12 20:39:53.387 14604 14604 E keymaster_tee: [ERROR]: (nwd_keymaster_mdfpp.cpp:1040) can't close connection with trustlet; error: -49
12-12 20:39:53.387 14604 14604 E HidlServiceManagement: Could not find instance 'default' in library [email protected] Keeping library open.
12-12 20:39:53.387 14604 14604 E LegacySupport: Could not get passthrough implementation for [email protected]::IKeymasterDevice/default.
12-12 20:39:53.386 0 0 E : [0:android.hardwar:14604] scm_call failed: func id 0x72000101, ret: -12, syscall returns: 0x0, 0x0, 0x0
12-12 20:39:53.386 0 0 E [0:android.hardwar:14604] QSEECOM: qseecom_load_app: scm_call to load app failed
12-12 20:39:53.386 0 0 E [0:android.hardwar:14604] QSEECOM: qseecom_ioctl: failed load_app request: -22
12-12 20:39:53.390 0 0 I [1: init: 1] init: Service 'vendor.keymaster-3-0' (pid 14604) exited with status 1
12-12 20:39:53.390 0 0 I [1: init: 1] init: Sending signal 9 to service 'vendor.keymaster-3-0' (pid 14604) process group...
12-12 20:39:53.390 0 0 I [1: init: 1] libprocessgroup: Successfully killed process cgroup uid 9999 pid 14604 in 0ms
12-12 20:39:53.755 626 626 W HidlServiceManagement: Waited one second for [email protected]::IKeymasterDevice/default
12-12 20:39:53.756 587 587 I hwservicemanager: Since [email protected]::IKeymasterDevice/default is not registered, trying to start it as a lazy HAL.
12-12 20:39:53.756 626 626 I HidlServiceManagement: getService: Trying again for [email protected]::IKeymasterDevice/default...
12-12 20:39:53.757 0 0 I [0: init: 1] init: starting service 'vendor.keymaster-3-0'...
12-12 20:39:53.760 0 0 E [0: init: 1] libprocessgroup: Failed to make and chown /sys/fs/cgroup/uid_9999: Operation not permitted
12-12 20:39:53.760 0 0 E [0: init: 1] init: createProcessGroup(9999, 14626) failed for service 'vendor.keymaster-3-0': Operation not permitted
12-12 20:39:53.761 0 0 I [0: init: 1] init: Control message: Processed ctl.interface_start for '[email protected]::IKeymasterDevice/default' from pid: 587 (/system/bin/hwservicemanager)
12-12 20:39:53.778 14626 14626 D hw-ProcessState: Binder ioctl to enable oneway spam detection failed: Invalid argument
12-12 20:39:53.778 2 2 I [2:android.hardwar:14626] binder: 14626:14626 ioctl 40046210 7fe065faa4 returned -22
12-12 20:39:53.784 14626 14626 I [email protected]: Fetching keymaster device name default
12-12 20:39:53.786 2 2 W [2:android.hardwar:14626] QSEECOM: qseecom_load_app: App (skeymast) does'nt exist, loading apps for first time
12-12 20:39:53.785 14626 14626 I keymaster_tee: [INFO]: (nwd_keymaster_mdfpp.cpp:1057) entered device_open function
12-12 20:39:53.785 14626 14626 I keymaster_tee: [INFO]: (nwd_keymaster_tc_api.c:65) Open MDFPP keymaster version 1.9.04
12-12 20:39:53.785 14626 14626 D keymaster_tee: [DEBUG]: (nwd_keymaster_synchronization.c:27) sync init...OK
12-12 20:39:53.785 14626 14626 D keymaster_tee: [DEBUG]: (nwd_keymaster_qualcomm.c:101) request 82112 bytes
12-12 20:39:53.785 14626 14626 D keymaster_tee: [DEBUG]: (nwd_keymaster_qualcomm.c:45) qsc_start_app: buff_size: 82112
12-12 20:39:53.785 14626 14626 D QSEECOMAPI: QSEECom_get_handle sb_length = 0x140c0
12-12 20:39:53.785 14626 14626 D QSEECOMAPI: App is not loaded in QSEE
12-12 20:39:53.785 14626 14626 D QSEECOMAPI: app_arch = 1, total_files = 8
12-12 20:39:53.875 14255 14255 W ServiceManager: Waited one second for SurfaceFlinger (is service started? are binder threads started and available?)
12-12 20:39:53.876 586 586 I servicemanager: Since 'SurfaceFlinger' could not be found, trying to start it as a lazy AIDL service
12-12 20:39:53.878 586 14627 W libc : Unable to set property "ctl.interface_start" to "aidl/SurfaceFlinger": error code: 0x20
12-12 20:39:53.878 586 14627 I servicemanager: Tried to start aidl service SurfaceFlinger as a lazy service, but was unable to. Usually this happens when a service is not installed, but if the service is intended to be used as a lazy service, then it may be configured incorrectly.
12-12 20:39:53.877 0 0 E [0: init: 1] init: Control message: Could not find 'aidl/SurfaceFlinger' for ctl.interface_start from pid: 586 (/system/bin/servicemanager)
12-12 20:39:54.562 0 0 I [2: kworker/2:1: 33] msm_thermal: msm_ts_print tsens[4:459][6:459][9:501][11:482][15:401]
12-12 20:39:54.756 626 626 W HidlServiceManagement: Waited one second for [email protected]::IKeymasterDevice/default
12-12 20:39:54.757 587 587 I hwservicemanager: Since [email protected]::IKeymasterDevice/default is not registered, trying to start it as a lazy HAL.
12-12 20:39:54.757 626 626 I HidlServiceManagement: getService: Trying again for [email protected]::IKeymasterDevice/default...
12-12 20:39:54.758 0 0 I [0: init: 1] init: Control message: Processed ctl.interface_start for '[email protected]::IKeymasterDevice/default' from pid: 587 (/system/bin/hwservicemanager)
12-12 20:39:54.876 14255 14255 W ServiceManager: Waited one second for SurfaceFlinger (is service started? are binder threads started and available?)
12-12 20:39:54.877 586 586 I servicemanager: Since 'SurfaceFlinger' could not be found, trying to start it as a lazy AIDL service
12-12 20:39:54.878 586 14629 W libc : Unable to set property "ctl.interface_start" to "aidl/SurfaceFlinger": error code: 0x20
12-12 20:39:54.878 586 14629 I servicemanager: Tried to start aidl service SurfaceFlinger as a lazy service, but was unable to. Usually this happens when a service is not installed, but if the service is intended to be used as a lazy service, then it may be configured incorrectly.
12-12 20:39:54.878 0 0 E [0: init: 1] init: Control message: Could not find 'aidl/SurfaceFlinger' for ctl.interface_start from pid: 586 (/system/bin/servicemanager)
12-12 20:39:55.086 0 0 W [0:android.hardwar:14626] scm: secure world has been busy for 1 second!
bozkurtum said:
I regret to say that the best rom produced for this tablet so far is the rom in the link below, while the others have never been fully stable.
[ROM] SM-T825 TWEAKED.........................[rom] sm-t825 tweaked.
SM-T825 TWEAKED 5.1 ***** PIE ***** 20JUN2020 T825_CTD1_TWEAKED_5.1_DB4_by_rorymc928 Based on latest stock CTD1 firmware Tweaked, stable, zip aligned. SU/D Forced encryption disabled Deknoxed Debloated (GPU driver updated to latest adreno...
forum.xda-developers.com
Click to expand...
Click to collapse
I MOST regretfully say you're mistaken. I had that before @Awesometic released 18.1 and it was MUCH slower and less responsive.
The 18.1 has gotten nothing but praise from all who use it. I have a T820 and can't try the 19.1 yet but looking forward to it;
ETA on the T820?
And BRAVO!!!
Bakarios said:
Hello,
First thank very much for your work, your roms are fantastic the version of lineageos 18.1 and HAVOC,
this first version is causing a bootloop I don't know if it can help I'm adding the device boot logs:
Code:
12-12 20:39:51.806 0 0 E [0: surfaceflinger:14610] subsys-restart: __subsystem_get(): __subsystem_get: a530_zap count:0
12-12 20:39:51.812 0 0 I [0: ueventd:14611] ueventd: firmware: loading 'a530_zap.mdt' for '/devices/soc/soc:qcom,kgsl-hyp/firmware/a530_zap.mdt'
12-12 20:39:51.813 0 0 I : [0: surfaceflinger:14610] subsys-pil-tz soc:qcom,kgsl-hyp: a530_zap: loading from 0x000000008f400000 to 0x000000008f402000
12-12 20:39:51.813 0 0 I [2: ueventd:14611] ueventd: loading /devices/soc/soc:qcom,kgsl-hyp/firmware/a530_zap.mdt took 1ms
12-12 20:39:51.831 0 0 E : [0: surfaceflinger:14610] scm_call failed: func id 0x42000201, ret: -1, syscall returns: 0x0, 0x0, 0x0
12-12 20:39:51.831 0 0 E : [0: surfaceflinger:14610] subsys-pil-tz soc:qcom,kgsl-hyp: a530_zap: Invalid firmware metadata
12-12 20:39:51.836 14606 14610 E Adreno-GSL: <ioctl_kgsl_driver_entry:873>: open(/dev/kgsl-3d0) failed: errno 5. I/O error
12-12 20:39:51.836 14606 14610 W libEGL : eglInitialize(0x75770d4530) failed (EGL_BAD_ALLOC)
12-12 20:39:51.837 14606 14610 W RenderEngine: no suitable EGLConfig found, trying a simpler query
12-12 20:39:51.837 14606 14610 F RenderEngine: no suitable EGLConfig found, giving up
12-12 20:39:51.837 14606 14610 F libc : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 14610 (surfaceflinger), pid 14606 (surfaceflinger)
12-12 20:39:51.859 14614 14614 I crash_dump64: obtaining output fd from tombstoned, type: kDebuggerdTombstoneProto
12-12 20:39:51.861 633 633 I tombstoned: received crash request for pid 14610
12-12 20:39:51.861 14614 14614 I crash_dump64: performing dump of process 14606 (target tid = 14610)
12-12 20:39:51.873 14255 14255 W ServiceManager: Waited one second for SurfaceFlinger (is service started? are binder threads started and available?)
12-12 20:39:51.873 586 586 I servicemanager: Since 'SurfaceFlinger' could not be found, trying to start it as a lazy AIDL service
12-12 20:39:51.875 586 14617 W libc : Unable to set property "ctl.interface_start" to "aidl/SurfaceFlinger": error code: 0x20
12-12 20:39:51.875 586 14617 I servicemanager: Tried to start aidl service SurfaceFlinger as a lazy service, but was unable to. Usually this happens when a service is not installed, but if the service is intended to be used as a lazy service, then it may be configured incorrectly.
12-12 20:39:51.874 0 0 E [1: init: 1] init: Control message: Could not find 'aidl/SurfaceFlinger' for ctl.interface_start from pid: 586 (/system/bin/servicemanager)
12-12 20:39:51.928 0 0 I [3: logd.reader: 594] logd: logdr: UID=1000 GID=1003 PID=14614 n tail=0 logMask=8 pid=14606 start=0ns deadline=0ns
12-12 20:39:51.934 0 0 I [2: logd.reader: 594] logd: logdr: UID=1000 GID=1003 PID=14614 n tail=0 logMask=1 pid=14606 start=0ns deadline=0ns
12-12 20:39:51.947 14614 14614 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
12-12 20:39:51.947 14614 14614 F DEBUG : Build fingerprint: 'samsung/gts3lltekx/gts3lltekx:9/PPR1.180610.011/T825N0KOU3CTD1:user/release-keys'
12-12 20:39:51.947 14614 14614 F DEBUG : Revision: '5'
12-12 20:39:51.947 14614 14614 F DEBUG : ABI: 'arm64'
12-12 20:39:51.947 14614 14614 F DEBUG : Timestamp: 1970-12-12 20:39:51.864459376+0000
12-12 20:39:51.947 14614 14614 F DEBUG : Process uptime: 1s
12-12 20:39:51.947 14614 14614 F DEBUG : Cmdline: /system/bin/surfaceflinger
12-12 20:39:51.947 14614 14614 F DEBUG : pid: 14606, tid: 14610, name: surfaceflinger >>> /system/bin/surfaceflinger <<<
12-12 20:39:51.947 14614 14614 F DEBUG : uid: 1000
12-12 20:39:51.947 14614 14614 F DEBUG : signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
12-12 20:39:51.947 14614 14614 F DEBUG : Abort message: 'no suitable EGLConfig found, giving up'
12-12 20:39:51.947 14614 14614 F DEBUG : x0 0000000000000000 x1 0000000000003912 x2 0000000000000006 x3 00000074b4fc9340
12-12 20:39:51.947 14614 14614 F DEBUG : x4 00000000000c4ad0 x5 00000000000c4ad0 x6 00000000000c4ad0 x7 0000000000000018
12-12 20:39:51.947 14614 14614 F DEBUG : x8 00000000000000f0 x9 e6e2a24fe5d8bd5e x10 0000000000000000 x11 ffffff80ffffffdf
12-12 20:39:51.947 14614 14614 F DEBUG : x12 0000000000000001 x13 0000000000000027 x14 00000074b4fc94d0 x15 0000000000000038
12-12 20:39:51.947 14614 14614 F DEBUG : x16 000000774718c050 x17 0000007747168d20 x18 00000074b4048000 x19 000000000000390e
12-12 20:39:51.947 14614 14614 F DEBUG : x20 0000000000003912 x21 00000000ffffffff x22 00000074b4fca000 x23 00000075770d4530
12-12 20:39:51.948 14614 14614 F DEBUG : x24 00000075670d5330 x25 00000074b4fc9cb0 x26 00000074b4fc9ff8 x27 00000074b4fc9ab0
12-12 20:39:51.948 14614 14614 F DEBUG : x28 00000074b4ed1000 x29 00000074b4fc93c0
12-12 20:39:51.948 14614 14614 F DEBUG : lr 000000774711ba14 sp 00000074b4fc9320 pc 000000774711ba40 pst 0000000000000000
12-12 20:39:51.948 14614 14614 F DEBUG : backtrace:
12-12 20:39:51.948 14614 14614 F DEBUG : #00 pc 000000000004fa40 /apex/com.android.runtime/lib64/bionic/libc.so (abort+164) (BuildId: 443fdffc7b7209cc7b1cd55c1acaa73c)
12-12 20:39:51.948 14614 14614 F DEBUG : #01 pc 00000000000062c0 /system/lib64/liblog.so (__android_log_default_aborter+12) (BuildId: 9421b4c67db0120bbd4cd8c6d66b9982)
12-12 20:39:51.948 14614 14614 F DEBUG : #02 pc 0000000000006dc8 /system/lib64/liblog.so (__android_log_assert+308) (BuildId: 9421b4c67db0120bbd4cd8c6d66b9982)
12-12 20:39:51.948 14614 14614 F DEBUG : #03 pc 00000000002671f4 /system/bin/surfaceflinger (android::renderengine::skia::SkiaGLRenderEngine::chooseEglConfig(void*, int, bool)+496) (BuildId: 3c42cc1fc3af8ae53d4848beb2aed0bc)
12-12 20:39:51.948 14614 14614 F DEBUG : #04 pc 000000000027a4d0 /system/bin/surfaceflinger (android::renderengine::skia::SkiaGLRenderEngine::create(android::renderengine::RenderEngineCreationArgs const&)+164) (BuildId: 3c42cc1fc3af8ae53d4848beb2aed0bc)
12-12 20:39:51.948 14614 14614 F DEBUG : #05 pc 0000000000265ce0 /system/bin/surfaceflinger (_ZNSt3__110__function6__funcIZN7android12renderengine12RenderEngine6createERKNS3_24RenderEngineCreationArgsEE3$_1NS_9allocatorIS8_EEFNS_10unique_ptrIS4_NS_14default_deleteIS4_EEEEvEEclEv$fb147fdbd0638d73632d1b87d1d565c9+40) (BuildId: 3c42cc1fc3af8ae53d4848beb2aed0bc)
12-12 20:39:51.948 14614 14614 F DEBUG : #06 pc 0000000000276c28 /system/bin/surfaceflinger (android::renderengine::threaded::RenderEngineThreaded::threadMain(std::__1::function<std::__1::unique_ptr<android::renderengine::RenderEngine, std::__1::default_delete<android::renderengine::RenderEngine> > ()>)+376) (BuildId: 3c42cc1fc3af8ae53d4848beb2aed0bc)
12-12 20:39:51.948 14614 14614 F DEBUG : #07 pc 0000000000278f88 /system/bin/surfaceflinger (void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (android::renderengine::threaded::RenderEngineThreaded::*)(std::__1::function<std::__1::unique_ptr<android::renderengine::RenderEngine, std::__1::default_delete<android::renderengine::RenderEngine> > ()>), android::renderengine::threaded::RenderEngineThreaded*, std::__1::function<std::__1::unique_ptr<android::renderengine::RenderEngine, std::__1::default_delete<android::renderengine::RenderEngine> > ()> > >(void*)+160) (BuildId: 3c42cc1fc3af8ae53d4848beb2aed0bc)
12-12 20:39:51.948 14614 14614 F DEBUG : #08 pc 00000000000b1780 /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+264) (BuildId: 443fdffc7b7209cc7b1cd55c1acaa73c)
12-12 20:39:51.948 14614 14614 F DEBUG : #09 pc 0000000000051264 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: 443fdffc7b7209cc7b1cd55c1acaa73c)
12-12 20:39:51.963 14614 14614 E crash_dump64: unable to connect to activity manager: No such file or directory
12-12 20:39:51.963 633 633 E tombstoned: Tombstone written to: tombstone_15
12-12 20:39:51.966 0 0 I [3: init: 1] init: Untracked pid 14614 exited with status 0
12-12 20:39:51.972 0 0 I [3: init: 1] init: Service 'surfaceflinger' (pid 14606) received signal 6
12-12 20:39:51.972 0 0 I [3: init: 1] init: Sending signal 9 to service 'surfaceflinger' (pid 14606) process group...
12-12 20:39:51.972 0 0 I [3: init: 1] libprocessgroup: Successfully killed process cgroup uid 1000 pid 14606 in 0ms
12-12 20:39:51.972 0 0 I [3: init: 1] init: Sending signal 9 to service 'zygote' (pid 14232) process group...
12-12 20:39:51.972 0 0 I [3: init: 1] libprocessgroup: Successfully killed process cgroup uid 0 pid 14232 in 0ms
12-12 20:39:51.974 0 0 I [0: init: 1] init: Untracked pid 14616 exited with status 0
12-12 20:39:51.975 0 0 I [0: init: 1] init: processing action (init.svc.surfaceflinger=restarting) from (/vendor/etc/init/hw/init.qcom.rc:920)
12-12 20:39:51.975 0 0 I [0: init: 1] init: Sending signal 9 to service 'vendor.hwcomposer-2-1' (pid 742) process group...
12-12 20:39:51.975 0 0 I [0: init: 1] libprocessgroup: Successfully killed process cgroup uid 1000 pid 742 in 0ms
12-12 20:39:51.976 0 0 I [0: init: 1] init: processing action (init.svc.surfaceflinger=restarting) from (/vendor/etc/init/hw/init.target.rc:459)
12-12 20:39:51.977 0 0 I [0: init: 1] init: Sending signal 9 to service 'ppd' (pid 877) process group...
12-12 20:39:51.977 0 0 I [0: init: 1] libprocessgroup: Successfully killed process cgroup uid 1000 pid 877 in 0ms
12-12 20:39:52.089 0 0 W [0:android.hardwar:14604] scm: secure world has been busy for 1 second!
12-12 20:39:52.227 0 0 I [0: kworker/u8:0: 6] sm5705_get_curr: <1 0 100 10> info.volt_cal = 0x8000, volt_slope = 0x8000, mohm_volt_cal = 0x0
12-12 20:39:52.229 0 0 I [0: kworker/u8:0: 6] sm5705_get_curr: <1 0 100 10> info.volt_cal = 0x8000, volt_slope = 0x8000, mohm_volt_cal = 0x0
12-12 20:39:52.260 0 0 I [0: kworker/u8:0: 6] sm5705-charger: sm5705_chg_test_read: [CHG] 0x04:0xfe, 0x05:0xbf, 0x06:0xfb, 0x07:0xff, 0x08:0x29, 0x09:0x18, 0x0A:0x00, 0x0B:0x00, 0x0C:0x05, 0x0D:0x10, 0x0E:0x1c, 0x0F:0x03, 0x10:0x08, 0x11:0x12, 0x12:0x5f, 0x13:0x0c, 0x14:0x02, 0x15:0x2c, 0x16:0x18, 0x17:0x1c, 0x20:0x05, 0x21:0x00,
12-12 20:39:52.272 0 0 I [2: kworker/u8:0: 6] sm5705-charger: sm5705_chg_test_read: [CHG] 0x04:0xfe, 0x05:0xbf, 0x06:0xfb, 0x07:0xff, 0x08:0x29, 0x09:0x18, 0x0A:0x00, 0x0B:0x00, 0x0C:0x05, 0x0D:0x10, 0x0E:0x1c, 0x0F:0x03, 0x10:0x08, 0x11:0x12, 0x12:0x5f, 0x13:0x0c, 0x14:0x02, 0x15:0x2c, 0x16:0x18, 0x17:0x1c, 0x20:0x05, 0x21:0x00,
12-12 20:39:52.276 0 0 I [2: kworker/u8:0: 6] sm5705_get_curr: <1 0 100 10> info.volt_cal = 0x8000, volt_slope = 0x8000, mohm_volt_cal = 0x0
12-12 20:39:52.278 0 0 I [2: kworker/u8:0: 6] sm5705_vbatocv_check: mode change to mix RS auto mode
12-12 20:39:52.282 0 0 I [2: kworker/u8:0: 6] sm5705_cal_carc: <1 6 1 11 -1 1 6 1 9 1>, temp_fg = 363 ,p_curr_cal = 0x9b, n_curr_cal = 0xa6, curr_offset = 0x1, volt_cal = 0x8000 ,fg_delta_volcal = 0x0
12-12 20:39:52.283 0 0 I [2: kworker/u8:0: 6] sm5705_cal_carc: <1 3 0 3 1 1 2 3 2 3>, p_curr_cal = 0x9b, n_curr_cal = 0xa7, mix_factor=0x47a ,batt_temp = 286
12-12 20:39:52.286 0 0 I [2: kworker/u8:0: 6] sm5705_fg_check_reg_init_need: SM5705_REG_FG_OP_STATUS : 0x10 , return 0
12-12 20:39:52.291 0 0 I [2: kworker/u8:0: 6] sm5705_fg_test_read: 0xA0=0x1400, 0xAC=0x20a5, 0xAD=0x211b, 0xAE=0x21f7, 0xAF=0x2399, 0x28=0x0838, 0x2F=0x021a, 0x01=0xc401, SM5705_ID=0x000b
12-12 20:39:52.298 0 0 I [2: kworker/u8:0: 6] sm5705_fg_test_read: 0xB0=0x0000, 0xBC=0x255e, 0xBD=0x283f, 0xBE=0x2d0c, 0xBF=0x2d17, 0x85=0x0064, 0x86=0x0196, 0x87=0x0ec4, 0x1F=0x0080, 0x94=0x0001 , 0x13=0x000f, 0x14=0x0000
12-12 20:39:52.299 0 0 I [2: kworker/u8:0: 6] sm5705_get_all_value: chg_h=1, chg_f=0, chg_s=1, is_chg=0, ta_exist=1, v=3790, v_avg=3786, i=-248, i_avg=-91, ocv=3779, fg_t=363, b_t=286, cycle=38, soc=327, state=0x6
12-12 20:39:52.299 0 0 I [2: kworker/u8:0: 6] sm5705_fg_get_scaled_capacity: scaled capacity (32.7)
12-12 20:39:52.299 0 0 I [2: kworker/u8:0: 6] sm5705_fg_get_atomic_capacity: NOW(32), OLD(32)
12-12 20:39:52.299 0 0 I : [2: kworker/u8:0: 6] sec-battery battery: sec_bat_get_battery_info:Vnow(3790mV),Inow(-248mA),Imax(500mA),SOC(32%),Tbat(286),Tchg(326),Twpc(0)
12-12 20:39:52.299 0 0 I : [2: kworker/u8:0: 6] sec-battery battery: sec_bat_cisd_check: cisd off.
12-12 20:39:52.311 0 0 I [2: kworker/u8:0: 6] sm5705-charger: sm5705_chg_test_read: [CHG] 0x04:0xfe, 0x05:0xbf, 0x06:0xfb, 0x07:0xff, 0x08:0x29, 0x09:0x18, 0x0A:0x00, 0x0B:0x00, 0x0C:0x05, 0x0D:0x10, 0x0E:0x1c, 0x0F:0x03, 0x10:0x08, 0x11:0x12, 0x12:0x5f, 0x13:0x0c, 0x14:0x02, 0x15:0x2c, 0x16:0x18, 0x17:0x1c, 0x20:0x05, 0x21:0x00,
12-12 20:39:52.323 0 0 I [2: kworker/u8:0: 6] sm5705-charger: sm5705_chg_test_read: [CHG] 0x04:0xfe, 0x05:0xbf, 0x06:0xfb, 0x07:0xff, 0x08:0x29, 0x09:0x18, 0x0A:0x00, 0x0B:0x00, 0x0C:0x05, 0x0D:0x10, 0x0E:0x1c, 0x0F:0x03, 0x10:0x08, 0x11:0x12, 0x12:0x5f, 0x13:0x0c, 0x14:0x02, 0x15:0x2c, 0x16:0x18, 0x17:0x1c, 0x20:0x05, 0x21:0x00,
12-12 20:39:52.323 0 0 I : [2: kworker/u8:0: 6] sec-battery battery: sec_bat_time_management: Charging Time : 1340 secs
12-12 20:39:52.324 0 0 I : [2: kworker/u8:0: 6] sec-battery battery: sec_bat_temperature: HLT(800) HLR(750) HT(500), HR(450), LT(0), LR(50)
12-12 20:39:52.324 0 0 I [2: kworker/u8:0: 6] sec_bat_swelling_check: status(1), swell_mode(0:0:0), cv(0x10cc), temp(286)
12-12 20:39:52.324 0 0 I : [2: kworker/u8:0: 6] sec-battery battery: sec_bat_fullcharged_check: Charging Mode : Normal
12-12 20:39:52.324 0 0 I [2: kworker/u8:0: 6] sec_bat_set_current_event: clear current event(now=0x0, value=0x4)
12-12 20:39:52.324 0 0 I [2: kworker/u8:0: 6] sec_bat_check_mix_temp: mix_limit(0), temp(286), chg_temp(326), input_current(500)
12-12 20:39:52.324 0 0 I [2: kworker/u8:0: 6] sec_bat_check_afc_temp: cable_type(4), chg_limit(0)
12-12 20:39:52.324 0 0 I : [2: kworker/u8:0: 6] sec-battery battery: sec_bat_monitor_work: Status(Charging), mode(Normal), Health(Good), Cable(4, 4, 1, 1), level(100%), cisd.cd(0), HV(NONE), sleep_mode(0), Cycle(-1)
12-12 20:39:52.325 0 0 I [2: kworker/2:1: 33] sm5705-charger: psy_chg_get_charge_type: psy_chg_get_charge_type charge_type(5)
12-12 20:39:52.325 0 0 I : [2: kworker/2:1: 33] sec_bat_get_property cable type = 4 sleep_mode = 0
12-12 20:39:52.327 0 0 I [2: kworker/2:1: 33] sm5705_fg_check_reg_init_need: SM5705_REG_FG_OP_STATUS : 0x10 , return 0
12-12 20:39:52.329 0 0 I [2:[email protected]: 743] sm5705_fg_check_reg_init_need: SM5705_REG_FG_OP_STATUS : 0x10 , return 0
12-12 20:39:52.330 0 0 W [2:[email protected]: 743] healthd: battery l=32 v=3790 t=28.6 h=2 st=2 c=-248 fc=6000000 chg=u
12-12 20:39:52.332 0 0 I [2:[email protected]: 743] sm5705_fg_check_reg_init_need: SM5705_REG_FG_OP_STATUS : 0x10 , return 0
12-12 20:39:52.609 0 0 E : [1: msm_watchdog: 32] [pet_watchdog] last_count : 502d6, new_count : 0, bark_time : 77fd3, bite_time : 8ffca
12-12 20:39:52.662 0 0 I [2: logd.reader: 594] logd: logdr: UID=2000 GID=2000 PID=14620 n tail=0 logMask=bf pid=0 start=0ns deadline=0ns
12-12 20:39:52.754 626 626 W HidlServiceManagement: Waited one second for [email protected]::IKeymasterDevice/default
12-12 20:39:52.755 587 587 I hwservicemanager: Since [email protected]::IKeymasterDevice/default is not registered, trying to start it as a lazy HAL.
12-12 20:39:52.755 626 626 I HidlServiceManagement: getService: Trying again for [email protected]::IKeymasterDevice/default...
12-12 20:39:52.757 0 0 I [1: init: 1] init: Control message: Processed ctl.interface_start for '[email protected]::IKeymasterDevice/default' from pid: 587 (/system/bin/hwservicemanager)
12-12 20:39:52.873 14255 14255 W ServiceManager: Waited one second for SurfaceFlinger (is service started? are binder threads started and available?)
12-12 20:39:52.875 586 586 I servicemanager: Since 'SurfaceFlinger' could not be found, trying to start it as a lazy AIDL service
12-12 20:39:52.877 586 14624 W libc : Unable to set property "ctl.interface_start" to "aidl/SurfaceFlinger": error code: 0x20
12-12 20:39:52.877 586 14624 I servicemanager: Tried to start aidl service SurfaceFlinger as a lazy service, but was unable to. Usually this happens when a service is not installed, but if the service is intended to be used as a lazy service, then it may be configured incorrectly.
12-12 20:39:52.876 0 0 E [1: init: 1] init: Control message: Could not find 'aidl/SurfaceFlinger' for ctl.interface_start from pid: 586 (/system/bin/servicemanager)
12-12 20:39:53.142 0 0 I : [1: kworker/u8:0: 6] etspi_work_func_debug ldo: 0, sleep: 0, tz: 1, type: unknown
12-12 20:39:53.386 14604 14604 E QSEECOMAPI: Error::Load image request failed ret = -1, errno = 22
12-12 20:39:53.386 14604 14604 E QSEECOMAPI: Error::Loading image failed with ret = -1
12-12 20:39:53.386 14604 14604 E keymaster_tee: [ERROR]: (nwd_keymaster_qualcomm.c:58) Loading app (path - /vendor/firmware_mnt/image) skeymast failed: Invalid argument, size = 82112, ret = -1
12-12 20:39:53.386 14604 14604 E keymaster_tee: [ERROR]: (nwd_keymaster_qualcomm.c:106) Fail to open session with QSEE
12-12 20:39:53.387 14604 14604 E keymaster_tee: [ERROR]: (nwd_keymaster_tc_api.c:78) KM_TZOpenConnection FAILED [-3]
12-12 20:39:53.387 14604 14604 E keymaster_tee: [ERROR]: (nwd_keymaster_mdfpp.cpp:1120) can't open connection to trustlet; error: -49
12-12 20:39:53.387 14604 14604 E [email protected]: Error -1 opening keystore keymaster1 device
12-12 20:39:53.387 14604 14604 I keymaster_tee: [INFO]: (nwd_keymaster_mdfpp.cpp:1028) entered device_close function
12-12 20:39:53.387 14604 14604 E keymaster_tee: [ERROR]: (nwd_keymaster_tc_api.c:119) There is no opened session. ref cnt = 0
12-12 20:39:53.387 14604 14604 E keymaster_tee: [ERROR]: (nwd_keymaster_mdfpp.cpp:1040) can't close connection with trustlet; error: -49
12-12 20:39:53.387 14604 14604 E HidlServiceManagement: Could not find instance 'default' in library [email protected] Keeping library open.
12-12 20:39:53.387 14604 14604 E LegacySupport: Could not get passthrough implementation for [email protected]::IKeymasterDevice/default.
12-12 20:39:53.386 0 0 E : [0:android.hardwar:14604] scm_call failed: func id 0x72000101, ret: -12, syscall returns: 0x0, 0x0, 0x0
12-12 20:39:53.386 0 0 E [0:android.hardwar:14604] QSEECOM: qseecom_load_app: scm_call to load app failed
12-12 20:39:53.386 0 0 E [0:android.hardwar:14604] QSEECOM: qseecom_ioctl: failed load_app request: -22
12-12 20:39:53.390 0 0 I [1: init: 1] init: Service 'vendor.keymaster-3-0' (pid 14604) exited with status 1
12-12 20:39:53.390 0 0 I [1: init: 1] init: Sending signal 9 to service 'vendor.keymaster-3-0' (pid 14604) process group...
12-12 20:39:53.390 0 0 I [1: init: 1] libprocessgroup: Successfully killed process cgroup uid 9999 pid 14604 in 0ms
12-12 20:39:53.755 626 626 W HidlServiceManagement: Waited one second for [email protected]::IKeymasterDevice/default
12-12 20:39:53.756 587 587 I hwservicemanager: Since [email protected]::IKeymasterDevice/default is not registered, trying to start it as a lazy HAL.
12-12 20:39:53.756 626 626 I HidlServiceManagement: getService: Trying again for [email protected]::IKeymasterDevice/default...
12-12 20:39:53.757 0 0 I [0: init: 1] init: starting service 'vendor.keymaster-3-0'...
12-12 20:39:53.760 0 0 E [0: init: 1] libprocessgroup: Failed to make and chown /sys/fs/cgroup/uid_9999: Operation not permitted
12-12 20:39:53.760 0 0 E [0: init: 1] init: createProcessGroup(9999, 14626) failed for service 'vendor.keymaster-3-0': Operation not permitted
12-12 20:39:53.761 0 0 I [0: init: 1] init: Control message: Processed ctl.interface_start for '[email protected]::IKeymasterDevice/default' from pid: 587 (/system/bin/hwservicemanager)
12-12 20:39:53.778 14626 14626 D hw-ProcessState: Binder ioctl to enable oneway spam detection failed: Invalid argument
12-12 20:39:53.778 2 2 I [2:android.hardwar:14626] binder: 14626:14626 ioctl 40046210 7fe065faa4 returned -22
12-12 20:39:53.784 14626 14626 I [email protected]: Fetching keymaster device name default
12-12 20:39:53.786 2 2 W [2:android.hardwar:14626] QSEECOM: qseecom_load_app: App (skeymast) does'nt exist, loading apps for first time
12-12 20:39:53.785 14626 14626 I keymaster_tee: [INFO]: (nwd_keymaster_mdfpp.cpp:1057) entered device_open function
12-12 20:39:53.785 14626 14626 I keymaster_tee: [INFO]: (nwd_keymaster_tc_api.c:65) Open MDFPP keymaster version 1.9.04
12-12 20:39:53.785 14626 14626 D keymaster_tee: [DEBUG]: (nwd_keymaster_synchronization.c:27) sync init...OK
12-12 20:39:53.785 14626 14626 D keymaster_tee: [DEBUG]: (nwd_keymaster_qualcomm.c:101) request 82112 bytes
12-12 20:39:53.785 14626 14626 D keymaster_tee: [DEBUG]: (nwd_keymaster_qualcomm.c:45) qsc_start_app: buff_size: 82112
12-12 20:39:53.785 14626 14626 D QSEECOMAPI: QSEECom_get_handle sb_length = 0x140c0
12-12 20:39:53.785 14626 14626 D QSEECOMAPI: App is not loaded in QSEE
12-12 20:39:53.785 14626 14626 D QSEECOMAPI: app_arch = 1, total_files = 8
12-12 20:39:53.875 14255 14255 W ServiceManager: Waited one second for SurfaceFlinger (is service started? are binder threads started and available?)
12-12 20:39:53.876 586 586 I servicemanager: Since 'SurfaceFlinger' could not be found, trying to start it as a lazy AIDL service
12-12 20:39:53.878 586 14627 W libc : Unable to set property "ctl.interface_start" to "aidl/SurfaceFlinger": error code: 0x20
12-12 20:39:53.878 586 14627 I servicemanager: Tried to start aidl service SurfaceFlinger as a lazy service, but was unable to. Usually this happens when a service is not installed, but if the service is intended to be used as a lazy service, then it may be configured incorrectly.
12-12 20:39:53.877 0 0 E [0: init: 1] init: Control message: Could not find 'aidl/SurfaceFlinger' for ctl.interface_start from pid: 586 (/system/bin/servicemanager)
12-12 20:39:54.562 0 0 I [2: kworker/2:1: 33] msm_thermal: msm_ts_print tsens[4:459][6:459][9:501][11:482][15:401]
12-12 20:39:54.756 626 626 W HidlServiceManagement: Waited one second for [email protected]::IKeymasterDevice/default
12-12 20:39:54.757 587 587 I hwservicemanager: Since [email protected]::IKeymasterDevice/default is not registered, trying to start it as a lazy HAL.
12-12 20:39:54.757 626 626 I HidlServiceManagement: getService: Trying again for [email protected]::IKeymasterDevice/default...
12-12 20:39:54.758 0 0 I [0: init: 1] init: Control message: Processed ctl.interface_start for '[email protected]::IKeymasterDevice/default' from pid: 587 (/system/bin/hwservicemanager)
12-12 20:39:54.876 14255 14255 W ServiceManager: Waited one second for SurfaceFlinger (is service started? are binder threads started and available?)
12-12 20:39:54.877 586 586 I servicemanager: Since 'SurfaceFlinger' could not be found, trying to start it as a lazy AIDL service
12-12 20:39:54.878 586 14629 W libc : Unable to set property "ctl.interface_start" to "aidl/SurfaceFlinger": error code: 0x20
12-12 20:39:54.878 586 14629 I servicemanager: Tried to start aidl service SurfaceFlinger as a lazy service, but was unable to. Usually this happens when a service is not installed, but if the service is intended to be used as a lazy service, then it may be configured incorrectly.
12-12 20:39:54.878 0 0 E [0: init: 1] init: Control message: Could not find 'aidl/SurfaceFlinger' for ctl.interface_start from pid: 586 (/system/bin/servicemanager)
12-12 20:39:55.086 0 0 W [0:android.hardwar:14626] scm: secure world has been busy for 1 second!
Click to expand...
Click to collapse
Hello, what version do you use? T825 or T820?
KeepingItCuttingEdge said:
ETA on the T820?
And BRAVO!!!
Click to expand...
Click to collapse
It will be uploaded soon after few tests
Good!. Very good! I installed my pad (s3 lte) and good working. lte is also working.
If someone install this OS & google service, do not reboot after finish OS install.
Before reboot, must install flamegapps and reboot.
Or else, a pad is bricking.
I tried several times..... and succeed.
Thank you so much Awesometic.
Awesometic said:
Hello, what version do you use? T825 or T820?
It will be uploaded soon after few tests
Click to expand...
Click to collapse
tested it on the T825 version
DOOOOGY said:
Good!. Very good! I installed my pad (s3 lte) and good working. lte is also working.
If someone install this OS & google service, do not reboot after finish OS install.
Before reboot, must install flamegapps and reboot.
Or else, a pad is bricking.
I tried several times..... and succeed.
Thank you so much Awesometic.
Click to expand...
Click to collapse
thanks for the tip, i'll try this later
I uploaded the new T820 image. Please test this one, wifi version users.
By the way, it seems like it is not that all the users can use my LOS 19.1 image. I need further investigation, if you are using T820/T825 and if you can't pass the boot logo screen then let me know the symptoms and your device information including the base firmware version. Logcat would be the best.
Hi there,
I have the problem that the tablet does not reconnect to the wifi when it is switched on or exits airplane mode.
Can you help me?
Regards Chris
Thanks Awesometic!!! Enjoy your coffee.
I got it working on my SM-T820 Wifi on my second try, and total time from start to finish was under an hour. I'm getting better at this...
DOOOOGY said:
If someone install this OS & google service, do not reboot after finish OS install.
Before reboot, must install flamegapps and reboot.
Or else, a pad is bricking.
Click to expand...
Click to collapse
Thanks very much for this very good advice. The reason that my first attempt failed was because I rebooted between the OS install and the GApps install, and it got stuck on the LineageOS logo after I installed FlameGApps.
Find of frustrating how the steps are inconsistent though. With LineageOS 18.1 and OpenGApps, I had to make sure I DID reboot between the OS and the GApps install, otherwise it wouldn't work. With LineageOS 19.1 and FlameGApps, I had to make sure I DID NOT reboot between the OS and GAppsInstall, otherwise it wouldn't work. Not blaming anyone; that's just the way it is when dealing with unofficial builds, but it's still nerve rattling when I think I might have bricked my device.
Thanks for the coffee
Yeah, I got some feedback about that issue. Currently, for this ROM, it is better to install the ROM and GApps at once, without rebooting between installing them.
Thanks for confirming that
ChrisHide said:
Hi there,
I have the problem that the tablet does not reconnect to the wifi when it is switched on or exits airplane mode.
Can you help me?
Regards Chris
Click to expand...
Click to collapse
Hello,
I need a logcat file while the issue occurs.
For me, I can use the WiFi after switching the airplane mode.
Awesometic said:
I uploaded the new T820 image. Please test this one, wifi version users.
By the way, it seems like it is not that all the users can use my LOS 19.1 image. I need further investigation, if you are using T820/T825 and if you can't pass the boot logo screen then let me know the symptoms and your device information including the base firmware version. Logcat would be the best.
Click to expand...
Click to collapse
Thank you for all this great work !
I installed it on my T820, I encountered no installation problem and now the rom is running perfectly and fast since yesterday.
In TWRP I formated everything before install, installed the rom, then the gapps without rebooting. Then reboot to system and voilà
Hi Awesometic. Thank you for your hard work.
I tried to flash Lineage OS 19.1 sadly couldn't get past Samsung Tab S3 logo.
Device: SM-T825
Baseband Version: T825XXU3CTA1
File system: ext4
I attached log file which I took while it was stuck on boot logo.

Categories

Resources