Database Users

Did anyone try running haret on a smartphone?

I ran the latest version 0.36 on my Mio8390 which is using a PXA262 processor
running smartphone 2003.
When I started haret I've got an error message :
EXCEPTION reading coprocessor 15 register 0
twice.
And the detected cpu type is unknown
Anyway i could start the application and open a tcp port
Here is the result of dump cp(0) :
c00: ffffffd2 | c08: ffffffd2
c01: ffffffd2 | c09: ffffffd2
c02: ffffffd2 | c10: ffffffd2
c03: ffffffd2 | c11: ffffffd2
c04: ffffffd2 | c12: ffffffd2
c05: ffffffd2 | c13: ffffffd2
c06: ffffffd2 | c14: ffffffd2
c07: ffffffd2 | c15: ffffffd2
And here is the result of dump mmu:
----- Virtual address map -----
Descriptor flags legend:
C: Cacheable
B: Bufferable
0..3: Access Permissions (for up to 4 slices):
0: Supervisor mode Read
1: Supervisor mode Read/Write
2: User mode Read
3: User mode Read/Write
Error: EXCEPTION reading coprocessor 15 register 2
MMU 1st level descriptor table is at FFFFC000
Virtual | Physical | Descr | Description
address | address | flags |
----------+----------+---------+-----------------------------
Error: EXCEPTION CAUGHT AT MEGABYTE 0!
ffffffff | | | End of virtual address space
It seems that haret is having problem trying to read the CPU registeries,
what could be the problem?
So it means that I have to patch the source of haret before I can use it on a smartphone?
Or is it because of smartphone security policies? something about user-mode, kernel-mode in
wince?
I'm quite a nub but I think I have to know what to read first before I start reading books. Any info or help is appreciated.

aybabtu said:
I ran the latest version 0.36 on my Mio8390 which is using a PXA262 processor
running smartphone 2003.
When I started haret I've got an error message :
EXCEPTION reading coprocessor 15 register 0
...
Any info or help is appreciated.
Click to expand...
Click to collapse
You can try to add this code the the assembler file
and call the functions directly. Worked for
me with wince2.11, where i also had problems:
export |cp15_0|
|cp15_0| proc
mrc p15, 0, r0, c0, c0, 0
mov pc, lr
endp
export |cp15_2|
|cp15_2| proc
mrc p15, 0, r0, c2, c0, 0
mov pc, lr
endp
export |cp15_13|
|cp15_13| proc
mrc p15, 0, r0, c13, c0, 0
mov pc, lr
endp

aybabtu said:
I ran the latest version 0.36 on my Mio8390 which is using a PXA262 processor
running smartphone 2003.
Click to expand...
Click to collapse
Don't forget to post at least the 'dump gpio', FB address,
'dump mmu' and 'pd 0x41300004 4' here when
haret works

cr2 said:
... 'dump gpio', FB address,
'dump mmu' and 'pd 0x41300004 4'
Click to expand...
Click to collapse
Thank you for your help.
I signed the code with a privileged certification, then dump gpio and
physical address worked.
Code:
#dump gpio :
GPIO# D S A INTER | GPIO# D S A INTER | GPIO# D S A INTER | GPIO# D S A INTER
------------------+-------------------+-------------------+------------------
0 I 0 0 FE | 21 I 0 0 | 42 I 1 1 | 63 I 1 0 FE
1 I 0 0 RE FE | 22 O 1 0 | 43 O 1 2 | 64 O 1 0
2 I 0 0 RE | 23 O 0 0 | 44 I 1 1 | 65 O 1 0
3 I 0 0 RE FE | 24 O 0 0 | 45 O 1 2 | 66 O 1 0
4 I 0 0 RE | 25 O 0 0 | 46 I 1 2 | 67 I 1 0 FE
5 I 1 0 FE | 26 I 1 0 | 47 O 1 1 | 68 I 1 0
6 O 0 1 | 27 I 1 0 | 48 I 1 0 | 69 I 0 0
7 I 1 0 | 28 I 1 1 | 49 O 1 2 | 70 I 1 0
8 O 1 1 | 29 I 0 1 | 50 O 1 0 | 71 I 1 0
9 I 1 0 | 30 O 0 2 | 51 O 0 0 | 72 I 1 0 FE
10 I 1 0 FE | 31 O 0 2 | 52 I 1 0 | 73 O 1 0
11 I 1 0 | 32 I 1 0 | 53 I 1 0 | 74 O 0 0
12 I 1 0 RE FE | 33 O 1 2 | 54 O 0 0 | 75 O 1 0
13 I 0 0 RE FE | 34 I 1 1 | 55 O 1 0 | 76 O 0 0
14 I 0 0 RE FE | 35 I 0 1 | 56 O 0 0 | 77 O 0 0
15 O 1 2 | 36 I 0 0 | 57 I 1 0 | 78 O 1 2
16 I 1 0 | 37 I 0 1 | 58 O 0 0 | 79 I 1 2
17 O 1 2 | 38 I 0 0 | 59 O 0 0 | 80 O 1 2
18 I 1 1 | 39 O 1 2 | 60 O 1 0 | 81 I 1 1
19 O 1 0 | 40 O 0 0 | 61 O 1 0 | 82 O 1 1
20 O 1 0 | 41 O 0 0 | 62 O 1 0 | 83 I 1 2
#pd 0x41300004 4 :
41300004 | 00017bef | .{..
(What is so special about these four bytes?)
Then I tried to apply your code, but i don't know where should I call those fumctions, I tried calling them right before cpuDetect() or put it inside cpu-pxa.cpp and call them before cpuGetCP(), same effect.
The error message box doesn't show up but there is no message in the wince side console (detected cpu type),
then the same exception show up when I telnet it and when I dump any cp other then cp0.
phrack #63 - Hacking Windows CE said:
...
; SetProcessorMode.s
AREA |.text|, CODE, ARM
EXPORT |SetProcessorMode|
|SetProcessorMode| PROC
mov r1, lr ; different modes use different lr - save it
msr cpsr_c, r0 ; assign control bits of CPSR
mov pc, r1 ; return
END
...
Most of Pocket PC ROMs were builded with Enable Full Kernel Mode option, so all applications appear to run in kernel mode. The first 5 bits of the Psr register is 0x1F when debugging, that means the ARM processor runs in system mode. This value defined in nkarm.h:
// ARM processor modes
#define USER_MODE 0x10 // 0b10000
#define FIQ_MODE 0x11 // 0b10001
#define IRQ_MODE 0x12 // 0b10010
#define SVC_MODE 0x13 // 0b10011
#define ABORT_MODE 0x17 // 0b10111
#define UNDEF_MODE 0x1b // 0b11011
#define SYSTEM_MODE 0x1f // 0b11111
...
Click to expand...
Click to collapse
I guess smartphone is a little bit different from pocketpc?
Oh, btw I have to specify the address 0x81a00000 when I dumped the
rom using itsme's pmemdump, so it means that 0x81a00000 is mapped to 0x0?
I'd better start reading the ARM reference manual.

aybabtu said:
(What is so special about these four bytes?)
Click to expand...
Click to collapse
This is a ClocKENable (CKEN) register, so you have:
LCD,I2C,ICP,MMC,USB,NSSP,I2S,BTUART,FFUART,STUART,
SSP,AC97,PWM1,PWM0
enabled.
Then I tried to apply your code, but i don't know where should I call those fumctions
Click to expand...
Click to collapse
Add them to the wince/asmstuff.asm file,
and modify the cpuGetCP function in
wince/s-cpu.cpp to
Code:
uint32 cpuGetCP (uint cp, uint regno)
{
uint32 result=0xffffffff;
int ok=0;
if (cp > 15)
return 0xffffffff;
if (cp==15)
{
ok=1;
SetKMode (TRUE);
cli ();
switch (regno)
{
case 0:
result=cp15_0();
break;
case 2:
result=cp15_2();
break;
case 13:
result=cp15_13();
break;
default:
ok=0;
break;
}
sti ();
SetKMode (FALSE);
}
if (!ok) Output (L"Invalid register read cp=%d regno=%d\n",cp,regno);
return result;
uint32 value;
selfmod [0] = 0xee100010 | (cp << 8) | (regno << 16);
if (!FlushSelfMod ("read"))
return 0xffffffff;
__try
{
value = ((uint32 (*) ())&selfmod) ();
}
__except (EXCEPTION_EXECUTE_HANDLER)
{
Complain (C_ERROR ("EXCEPTION reading coprocessor %d register %d"), cp, regno);
value = 0xffffffff;
}
return value;
Oh, btw I have to specify the address 0x81a00000 when I dumped the
rom using itsme's pmemdump, so it means that 0x81a00000 is mapped to 0x0?
Click to expand...
Click to collapse
Maybe, but how did you come to using this address ?

The 'dump gpio' shows that the phone is not using the
builtin LCD pins. Then there must be a
video chipset in the phone. Interesting,
because even HTC is saving money on that.

I tried adding SetKMode to the original function, it worked without
calling your functions.
would there be any possible problem?
Maybe, but how did you come to using this address ?
Click to expand...
Click to collapse
Well I got a leaked dump out rom and tried to extract it with itsme's tool.
and i got something similar to these:
Code:
img 00000000 : hdr=81d5352c base=81a00000 commandlineoffset=81a00000
img 00640000 : hdr=82c40878 base=81a00000 commandlineoffset=81a00000
img 01300000 : hdr=82d02dd8 base=81a00000 commandlineoffset=81a00000
img 01380000 : hdr=8356d204 base=81a00000 commandlineoffset=81a00000
there must be a video chipset in the phone
Click to expand...
Click to collapse
There is a MediaQ MQ2100-JBE chipset inside, i'll look for info for this chipset later. And yes this phone is interesting, low price for it's high specification compared to other same generation phones but crappy customer service .
I'll post the result of dump mmu to the point it crash a little bit later.

aybabtu said:
I tried adding SetKMode to the original function, it worked without
calling your functions.
would there be any possible problem?
Click to expand...
Click to collapse
Unlikely.
Well I got a leaked dump
Click to expand...
Click to collapse
Then you can just lookup the static remapping
table.
There is a MediaQ MQ2100-JBE chipset inside, i'll look for info for this chipset later.
Click to expand...
Click to collapse
The datasheet is available here
www.handhelds.org/platforms/hp/ipaq-h22xx/mq-lcd-interface-appnote.pdf

And the mapping table dumped out using itsme's pmemmap:
Code:
v81a00000-83a00000 -> p00000000-02000000
v86000000-86100000 -> pe0000000-e0100000
v86100000-86200000 -> p48000000-48100000
v86200000-88200000 -> p40000000-42000000
v8c000000-8e000000 -> pa0000000-a2000000
v9a300000-9a400000 -> p04000000-04100000
v9c300000-9c400000 -> p08000000-08100000
v9f600000-9f700000 -> p0c000000-0c100000
v9f800000-9f900000 -> p14000000-14100000
Dumped it out and i can only tell that the first 32MB is my rom data.
And many info you gave me which I don't fully understand, guess I have to
read much more before I can thtink about running linux on this phone,
at least I know what to read now.

On a side note, it jumps to 1000h at the beginning of the rom likes the others
wince devices, but starting from 1000h, the content matches the dumped out
NK.exe kernel without the PE header(?).
Wasn't there supposed to be a 256K bootloader?
And at the end of the rom, there are 2 copies of 256K code, in which I found
strings of the bootloader in it, and the second copy is 1 byte different from
the first one, 1:0x00 2:0x01, in the middle of the code.
I'm not sure these are Mitac only layout, just put it here in case anyone
knows.

Oh and there is a Atmel MEGA16L-8MI Microcontroller inside,
don't know what it exactly does but I found strings related to this
in the 'bootloader portion'.

aybabtu said:
And the mapping table dumped out using itsme's pmemmap:
Click to expand...
Click to collapse
v81a00000-83a00000 -> p00000000-02000000
32MB ROM
v86000000-86100000 -> pe0000000-e0100000
Weird.
v86100000-86200000 -> p48000000-48100000
PXA26x Memory Controller
v86200000-88200000 -> p40000000-42000000
PXA26x Peripherals
v8c000000-8e000000 -> pa0000000-a2000000
32MB SDRAM
v9a300000-9a400000 -> p04000000-04100000
v9c300000-9c400000 -> p08000000-08100000
v9f600000-9f700000 -> p0c000000-0c100000
v9f800000-9f900000 -> p14000000-14100000
mmaped devices.
And many info you gave me which I don't fully understand, guess I have to
read much more before I can thtink about running linux on this phone
Click to expand...
Click to collapse
You can also dump/decode the registry and identify the
use of the serial ports.
Your GPIO table suggests that the PXA MMC
controller is used.
Looks good

aybabtu said:
Oh and there is a Atmel MEGA16L-8MI Microcontroller inside,
don't know what it exactly does but I found strings related to this
in the 'bootloader portion'.
Click to expand...
Click to collapse
Battery monitoring or something like that,
maybe keyboard controller.

aybabtu said:
On a side note, it jumps to 1000h at the beginning of the rom likes the others
wince devices, but starting from 1000h, the content matches the dumped out
NK.exe kernel without the PE header(?).
Wasn't there supposed to be a 256K bootloader?
Click to expand...
Click to collapse
Not all wince devices have a bootloader,
wince2.11 and wince2005 un universal for example.
You can also look with 'strings -el' for
other useful strings.

v86000000-86100000 -> pe0000000-e0100000
Weird.
Click to expand...
Click to collapse
Seems to be that 16MB PXA26X NAND Flash ROM

aybabtu said:
v86000000-86100000 -> pe0000000-e0100000
Weird.
Click to expand...
Click to collapse
Seems to be that 16MB PXA26X NAND Flash ROM
Click to expand...
Click to collapse
Built-in ? BTW, does this device support SD cards or only MMC ?

Built-in ? BTW, does this device support SD cards or only MMC ?
Click to expand...
Click to collapse
Built-in, It should be the M-System DiskOnChip MD3831-D16-V3Q18-T inside.
Support both.
And this phone does not support bluetooth, but the clock to BTUART is
enabled :?:

aybabtu said:
And this phone does not support bluetooth, but the clock to BTUART is
enabled :?:
Click to expand...
Click to collapse
It is a normal UART, not blue at all , Himalaya
uses it for the serial cable.

That's not exactly the datasheet of
mq2100...
archive.org show that this was available
for downloads.. oh well

Put the list of all components and the known
information to wiki. That can help other people.

SGS Service Menu

Not sure if it's been posted anywhere here (google didn't show anything) so I thought I'd post the service menus and my configuration. It may come in handy for someone, right?
Note that it's not all the menus but the most interesting ones at least.
Code:
*#197328640#
hhh = hexadecimal
nnn = decimal
MAIN MENU
[1] DEBUG SCREEN
[1] BASIC INFORMATION
UMTS : HOME(CS+PS)
RRC State: IDLE
WCDMA 2100 Band 1
Reg PLMN 240-2, IsPCS? 0
FREQ DL:10737
FREQ UL:9787
CELL_ID:0xhhhhhh <- Disappears when 3G is not available
LAC: 0xhhhh
PSC:hhh
RSCP:-94, ECIO:-5 <- Changing
[2] MM INFORMATION
MM state: IDLE
Reg state: INDEP_REGISTRATION
IMSI attatch status: 1
LU Rej: Norm=0, Period=13
T1312=11, Count=9
T32(10,11,12,13)=0010
T32(20,30,40)=000
Att Rej Cause=0
RAU Rej Cause=9
[3] RR INFORMATION
[4] NEIGHBOUR CELL
[5] GPRS INFORMATION
[6] SIM INFORMATION
[7] HANDOVER
[8] PHONE CONTROL
[9] ANTENNA/ADC
[2] VERSION INFO.
[1] SW VERSION
[1] READ IMEI
IMEI : nnnnnnnnnnnnnnnnn
[2] READ IMSI
"Don't Support it in GSM mobile!"
[3] READ SW VERSION
CP SW VERSION : I9000XXJF3
CP SW COMPILE DATE : Jun 3 20
CP SW COMPILE TIME : 11:25:05
[4] READ FTA SW VERSION
FTA SW VERSION : I9000.012
[5] READ ALL SW VERSION
CP SW VERSION : I9000XXJF3
HW VERSION : MP 0.800
FTA SW VERSION : I9000.012
FTA HW VERSION : REV1.2
RF CAL DATE : 2010.6.15
CSC CODE :
[6] READ CSC CODE
CP SW VERSION : I9000XXJF3
HW VERSION : MP 0.800
FTA SW VERSION : I9000.012
FTA HW VERSION : REV1.2
RF CAL DATE : 2010.6.15
CSC CODE :
[2] HW VERSION
[1] READ HW VERSION
HW VERSION : MP 0.800
[2] WRITE HW VERSION
NOT SUPPORTED
[3] READ FTA HW VERSION
FTA HW VERSION : REV1.2
[4] READ CAL DATE
CAL DATE : 2010.6.15
[5] WRITE CAL DATE
NOT SUPPORTED
[3] UMTS RF NV
[1] RF NV READ
NOT SUPPORTED
[2] RF NV WRITE
MENU NOT EXIST
PRESS BACK KEY
Current Command is 32
[4] GSM RF NV
[1] RF NV READ
NOT SUPPORTED
[2] RF NV WRITE
MENU NOT EXIST
PRESS BACK KEY
Current Command is 42
[5] AUDIO
[1] HANDSET
[1] Volume
[1]SRC Speech RX Volume
[0]0_lvl : 72
[1]1_lvl : 76
[2]2_lvl : 80
[3]3_lvl : 84
[4]4_lvl : 88
[5]5_lvl : 92
[2]DST I2S1 TX Volume
[0]0_lvl : 68
[1]1_lvl : 72
[2]2_lvl : 76
[3]3_lvl : 80
[4]4_lvl : 84
[5]5_lvl : 88
[3]SRC I2S1 RX Volume : 88
[4]DST Speech TX Volume : 88
[5]Sidetone : 0x0
[6]I2S1 Rx Gain : 0x1fff
[7]I2S1 Tx Gain : 0x2000
[2] HandsFree
[1]Gain Analog: 0x7fff
[2]NrCoeffs Real: 0x64
[3]NrCoeffs Complex 1: 0x64
[4]NrCoeffs Complex 2: 0x64
[5]LdAddGain: 0x0
[6]LdAddGainMax: 0x0
[7]LdAddGainMin: 0x1400
[3] NR
[1]UL NR
[1]AttenFactorMinVal : 0x1000
[2]OvEstFacBandZero : 0x2000
[3]OvEstFacBandNoZero : 0x2000
[2]DL NR
[1]AttenFactorMinVal : 0x1000
[2]OvEstFacBandZero : 0x1000
[3]OvEstFacBandNoZero : 0x1000
[4] DRP
[1]UL DRP
[1]Hi Band
[1]LA : -11520
[2]LB : -6144
[3]Gcomp : 0x0
[4]RinfA : 0x100
[5]RAB : 0x100
[6]RB0 : 0x100
[2]Low Band
[1]LA : -15360
[2]LB : -5120
[3]Gcomp : 0x0
[4]RinfA : 0x700
[5]RAB : 0x100
[6]RB0 : 0xb3
[2]DL DRP
[1]Hi Band
[1]LA : -11520
[2]LB : -6144
[3]Gcomp : 0x0
[4]RinfA : 0x100
[5]RAB : 0x100
[6]RB0 : 0x100
[2]Low Band
[1]LA : -16640
[2]LB : -5120
[3]Gcomp : 0x0
[4]RinfA : 0x700
[5]RAB : 0x100
[6]RB0 : 0x99
[5] SER
[1]beta : 31000
[2]overest : 700
[3]thplout : 70
[6] CNI
[1]Rx CNI gain : 20
[2]Tx CNI noise_gain : 16384
[3]Tx CNI noise_floor : 2048
[4]Tx CNI noise_gain_drp : 0
[9] Diamond Solution
[1]DYVE(OFF)
[1]DYVE OnOff : OFF
[2]mic_sensitivity : 5
[3]stepgain 1
[1]Step Gain 1 : 0
[2]Step Gain 2 : 0
[3]Step Gain 3 : 0
[4]Step Gain 4 : 0
[5]Step Gain 5 : 0
[4]stepgain 2
[1]StepGain 6 : 6
[2]StepGain 7 : 8
[3]StepGain 8 : 10
[4]StepGain 9 : 12
[5]StepGain 10 : 14
[6]StepGain 11 : 16
[5]clarity : 8
[6]noise_level : 0x800
[2]Swing Free(OFF)
[1]SF OnOff : OFF
[2]
[3]Voice Booster(OFF)
[1]VB OnOff : OFF
[2]hpf_cutoff : 4
[3]harmonic_level : 8192
[4]boostgain : 6
[5]limit_level : 21
[4]Acoustic Shock Free(OFF)
[1]ASF OnOff : OFF
[2]rms_mode : 2
[3]limit_level : 24
[5]Comport Noise Generator(OFF)
[1]CNG OnOff : OFF
[2]level : 1
[6]1Mic TX(OFF)
[1]1Mix TX OnOff : OFF
[2]Fir_Coeff Table
[1]fir_coeff 0 : 0xffffff49
[2]fir_coeff 1 : 0xfffffce6
[3]fir_coeff 2 : 0xfffffab3
[4]fir_coeff 3 : 0xfffffccb
[5]fir_coeff 4 : 0xfffff0e9
[6]fir_coeff 5 : 0xffffffc7
[7]fir_coeff 6 : 0x3e4a
[3]AEC Table 1
[1]rxmode_onoff : OFF
[2]delay_onoff : OFF
[3]delay : 0
[4]aec_onoff : OFF
[5]aec_rxgain : 0x200
[6]aec_mu : 0x0
[4]AEC Table 2
[1]dtrxg_onoff : OFF
[2]post_onoff : OFF
[3]post_min : 11
[4]post_gain : 11
[5]dtgc_onoff : OFF
[6]rxdet_onoff : OFF
[5]AEC Table 3
[1]rxdet_th_1st : -38
[2]rxdet_hangmax_1st : 6
[3]dtgc_gain_1st : 0x4000
[4]rxdet_th_2nd : -38
[5]rxdet_hangmax_2nd : 6
[6]dtgc_gain_2nd : 0x4000
[7]txdet_onoff : OFF
[6]NS Table 1
[1]iir_onoff: OFF
[2]ns_onoff : ON
[3]rxtx_agc_tbl : 13
[4]weight_ss_ns : 20
[5]ss_gain_ns : 11
[6]ns_gain_ns : 11
[7]NS Table 2
[1]tx_filter_onoff : ON
[2]tx_agc_onoff : ON
[3]in_txgain : 0x400
[4]out_txgain : 0xe40
[5]tx_cng_onoff : OFF
[6]noise_th_bits : 16
[2] HEADSET
[1] Volume
[1]SRC Speech RX Volume
[0]0_lvl : 75
[1]1_lvl : 78
[2]2_lvl : 81
[3]3_lvl : 84
[4]4_lvl : 87
[5]5_lvl : 90
[2]DST I2S1 TX Volume
[0]0_lvl : 75
[1]1_lvl : 78
[2]2_lvl : 81
[3]3_lvl : 84
[4]4_lvl : 87
[5]5_lvl : 90
[3]SRC I2S1 RX Volume : 100
[4]DST Speech TX Volume : 100
[5]Sidetone : 0x0
[6]I2S1 Rx Gain : 0x2d34
[7]I2S1 Tx Gain : 0x2000
[2] HandsFree
[1]Gain Analog: 0x7fff
[2]NrCoeffs Real: 0x32
[3]NrCoeffs Complex 1: 0x6e
[4]NrCoeffs Complex 2: 0x6e
[5]LdAddGain: 0x0
[6]LdAddGainMax: 0x0
[7]LdAddGainMin: 0xa8c
[3] NR
[1]UL NR
[1]AttenFactorMinVal : 0xfa0
[2]OvEstFacBandZero : 0xfa0
[3]OvEstFacBandNoZero : 0x1f40
[2]DL NR
[1]AttenFactorMinVal : 0x1000
[2]OvEstFacBandZero : 0x1000
[3]OvEstFacBandNoZero : 0x1000
[4] DRP
[1]UL DRP
[1]Hi Band
[1]LA : -11520
[2]LB : -6144
[3]Gcomp : 0x0
[4]RinfA : 0x100
[5]RAB : 0x100
[6]RB0 : 0x100
[2]Low Band
[1]LA : -15360
[2]LB : -7680
[3]Gcomp : 0xc00
[4]RinfA : 0x500
[5]RAB : 0x133
[6]RB0 : 0x80
[2]DL DRP
[1]Hi Band
[1]LA : -11520
[2]LB : -6144
[3]Gcomp : 0x0
[4]RinfA : 0x100
[5]RAB : 0x100
[6]RB0 : 0x100
[2]Low Band
[1]LA : -12800
[2]LB : -3840
[3]Gcomp : 0x0
[4]RinfA : 0x500
[5]RAB : 0x100
[6]RB0 : 0x0
[5] SER
[1]beta : 31000
[2]overest : 4000
[3]thploud : 70
[6] CNI
[1]Rx CNI gain : 20
[2]Tx CNI noise_gain : 0
[3]Tx CNI noise_floor : 0
[4]Tx CNI noise_gain_drp : 200
[9] Diamond Solution
[1]DYVE(OFF)
[1]DYVE OnOff : OFF
[2]mic_sensitivity : 5
[3]stepgain 1
[1]Step Gain 1 : 0
[2]Step Gain 2 : 0
[3]Step Gain 3 : 0
[4]Step Gain 4 : 0
[5]Step Gain 5 : 0
[4]stepgain 2
[1]StepGain 6 : 6
[2]StepGain 7 : 8
[3]StepGain 8 : 10
[4]StepGain 9 : 12
[5]StepGain 10 : 14
[6]StepGain 11 : 16
[5]clarity : 8
[6]noise_level : 0x800
[2]Swing Free(OFF)
[1]SF OnOff : OFF
[2]
[3]Voice Booster(OFF)
[1]VB OnOff : OFF
[2]hpf_cutoff : 4
[3]harmonic_level : 8192
[4]boostgain : 6
[5]limit_level : 21
[4]Acoustic Shock Free(OFF)
[1]ASF OnOff : OFF
[2]rms_mode : 2
[3]limit_level : 24
[5]Comport Noise Generator(OFF)
[1]CNG OnOff : OFF
[2]level : 1
[6]1Mic TX(OFF)
[1]1Mix TX OnOff : OFF
[2]Fir_Coeff Table
[1]fir_coeff 0 : 0xffffff49
[2]fir_coeff 1 : 0xfffffce6
[3]fir_coeff 2 : 0xfffffab3
[4]fir_coeff 3 : 0xfffffccb
[5]fir_coeff 4 : 0xfffff0e9
[6]fir_coeff 5 : 0xffffffc7
[7]fir_coeff 6 : 0x3e4a
[3]AEC Table 1
[1]rxmode_onoff : OFF
[2]delay_onoff : OFF
[3]delay : 0
[4]aec_onoff : OFF
[5]aec_rxgain : 0x200
[6]aec_mu : 0x0
[4]AEC Table 2
[1]dtrxg_onoff : OFF
[2]post_onoff : OFF
[3]post_min : 11
[4]post_gain : 11
[5]dtgc_onoff : OFF
[6]rxdet_onoff : OFF
[5]AEC Table 3
[1]rxdet_th_1st : -38
[2]rxdet_hangmax_1st : 6
[3]dtgc_gain_1st : 0x4000
[4]rxdet_th_2nd : -38
[5]rxdet_hangmax_2nd : 6
[6]dtgc_gain_2nd : 0x4000
[7]txdet_onoff : OFF
[6]NS Table 1
[1]iir_onoff: OFF
[2]ns_onoff : ON
[3]rxtx_agc_tbl : 13
[4]weight_ss_ns : 20
[5]ss_gain_ns : 11
[6]ns_gain_ns : 11
[7]NS Table 2
[1]tx_filter_onoff : OFF
[2]tx_agc_onoff : OFF
[3]in_txgain : 0x400
[4]out_txgain : 0xe40
[5]tx_cng_onoff : OFF
[6]noise_th_bits : 16
[3] SPEAKER
[4] BLUETOOTH
[5] HANDSET VT
[6] HEADSET VT
[7] SPEAKER VT
[8] BLUETOOTH VT
[6] COMMON
[1] FTM
[1] FTM : ON
NOT SUPPORTED
[2] FTM : OFF
NOT SUPPORTED
[2] DEBUG INFO
[1] MM REJECT CAUSE
CS Reg State: 0x0
CS Reg Reject Cause: 0x11
CS Net Reject Cause: 255
PS Reg State: 0x0
PS Reg Reject Cause: 0x11
PS Net Reject Cause: 255
[2] LOG DUMP
NOT SUPPORTED
[3] PCM LOGGING(OFF)
[1] Disable
[2] Enable
[3] RF SCANNING
[1] SETTING
[1] WCDMA THRESHOLD
[2] GSM THRESHOLD
MENU NOT EXIST
PRESS BACK KEY
Current Command is 63112
[3] RF SCANNING TIMER
[4] DISPLAY BAND[0~12]
[2] START RF SCANNING
[3] RESULT TO PC
[4] RESULT TO SCREEN
[4] DIAG CONFIG
[1] LOG VIA USB [*]
[2] LOG VIA UART
[3] LOG VIA IPC
[4] SPEED 115200 [*]
[5] SPEED 921600
[6] DBG MSG ON
[7] DBG MSG OFF [*]
[8] RAMDUMP ON
[9] RAMDUMP OFF [*]
[5] WCDMA/GSM SET CHANNEL
[6] NV REBUILD
[7] FACTORY TEST
[1] VBATT
[1] VBATT READ
[2] VBATT WRITE
[2] RTC
[3] AUDIO LOOPBACK
[4] GPRS SETTING
[5] AMR
[6] AUTO ANSWER
[7] SELLOUT SMS
[8] FM RADIO
[9] TOTAL CALL TIME
[8] FORCE SLEEP
[1] AP ONLY SLEEP
[2] CP ONLY LPM
[9] GPS
GPS MODULE IS IN AP SIDE

great this is exactly what I was looking for. Now can you tell me which setting under volume is the ear-piece volume?

Is yours really that quiet?? man.. u deaf?

ah thanks for this. Some new tweaks to try...
BTW anybody knows what "DIAMOND SOLUTION" means? There are some nice potential tweaks under that menu

Anyone already know more about what all these settings do (or some explanation on the terms?).
Trying to find out if I can change something here to improve the audio part of the video recording.

Diamond solution is the settings the phone uses when a headphone is plugged in. It is essentially your music settings of the phone. Lots of tweaks exist in there and yes it has a HARDWARE EQUALIZER right in there. It's called "Fir_Coeff Table".

Nice
Thank you VERY MUCH for this listing antzen !
Did you grab it manually or using some tool ?

supercurio said:
Thank you VERY MUCH for this listing antzen !
Did you grab it manually or using some tool ?
Click to expand...
Click to collapse
I manually typed the whole thing... ;-)

More SGS service menu entries ...
Remembered that I'd not completed the documentation of this and here's a bit more of the service menu. (I've updated the original post as well)
I'm not sure if my changes done to the device has affected the service menu in any way but bear that in mind as this device is not 100% default as it was shipped any longer. I've documented my changes here: endoid.wordpress.com/2010/08/08/my-sluggish-samsung-galaxy-s/ (could a moderator perhaps remove the url-restriction?)
Code:
[5] AUDIO
[2] HEADSET
[1] Volume
[1]SRC Speech RX Volume
[0]0_lvl : 75
[1]1_lvl : 78
[2]2_lvl : 81
[3]3_lvl : 84
[4]4_lvl : 87
[5]5_lvl : 90
[2]DST I2S1 TX Volume
[0]0_lvl : 75
[1]1_lvl : 78
[2]2_lvl : 81
[3]3_lvl : 84
[4]4_lvl : 87
[5]5_lvl : 90
[3]SRC I2S1 RX Volume : 100
[4]DST Speech TX Volume : 100
[5]Sidetone : 0x0
[6]I2S1 Rx Gain : 0x2d34
[7]I2S1 Tx Gain : 0x2000
[2] HandsFree
[1]Gain Analog: 0x7fff
[2]NrCoeffs Real: 0x32
[3]NrCoeffs Complex 1: 0x6e
[4]NrCoeffs Complex 2: 0x6e
[5]LdAddGain: 0x0
[6]LdAddGainMax: 0x0
[7]LdAddGainMin: 0xa8c
[3] NR
[1]UL NR
[1]AttenFactorMinVal : 0xfa0
[2]OvEstFacBandZero : 0xfa0
[3]OvEstFacBandNoZero : 0x1f40
[2]DL NR
[1]AttenFactorMinVal : 0x1000
[2]OvEstFacBandZero : 0x1000
[3]OvEstFacBandNoZero : 0x1000
[4] DRP
[1]UL DRP
[1]Hi Band
[1]LA : -11520
[2]LB : -6144
[3]Gcomp : 0x0
[4]RinfA : 0x100
[5]RAB : 0x100
[6]RB0 : 0x100
[2]Low Band
[1]LA : -15360
[2]LB : -7680
[3]Gcomp : 0xc00
[4]RinfA : 0x500
[5]RAB : 0x133
[6]RB0 : 0x80
[2]DL DRP
[1]Hi Band
[1]LA : -11520
[2]LB : -6144
[3]Gcomp : 0x0
[4]RinfA : 0x100
[5]RAB : 0x100
[6]RB0 : 0x100
[2]Low Band
[1]LA : -12800
[2]LB : -3840
[3]Gcomp : 0x0
[4]RinfA : 0x500
[5]RAB : 0x100
[6]RB0 : 0x0
[5] SER
[1]beta : 31000
[2]overest : 4000
[3]thploud : 70
[6] CNI
[1]Rx CNI gain : 20
[2]Tx CNI noise_gain : 0
[3]Tx CNI noise_floor : 0
[4]Tx CNI noise_gain_drp : 200
[9] Diamond Solution
[1]DYVE(OFF)
[1]DYVE OnOff : OFF
[2]mic_sensitivity : 5
[3]stepgain 1
[1]Step Gain 1 : 0
[2]Step Gain 2 : 0
[3]Step Gain 3 : 0
[4]Step Gain 4 : 0
[5]Step Gain 5 : 0
[4]stepgain 2
[1]StepGain 6 : 6
[2]StepGain 7 : 8
[3]StepGain 8 : 10
[4]StepGain 9 : 12
[5]StepGain 10 : 14
[6]StepGain 11 : 16
[5]clarity : 8
[6]noise_level : 0x800
[2]Swing Free(OFF)
[1]SF OnOff : OFF
[2]
[3]Voice Booster(OFF)
[1]VB OnOff : OFF
[2]hpf_cutoff : 4
[3]harmonic_level : 8192
[4]boostgain : 6
[5]limit_level : 21
[4]Acoustic Shock Free(OFF)
[1]ASF OnOff : OFF
[2]rms_mode : 2
[3]limit_level : 24
[5]Comport Noise Generator(OFF)
[1]CNG OnOff : OFF
[2]level : 1
[6]1Mic TX(OFF)
[1]1Mix TX OnOff : OFF
[2]Fir_Coeff Table
[1]fir_coeff 0 : 0xffffff49
[2]fir_coeff 1 : 0xfffffce6
[3]fir_coeff 2 : 0xfffffab3
[4]fir_coeff 3 : 0xfffffccb
[5]fir_coeff 4 : 0xfffff0e9
[6]fir_coeff 5 : 0xffffffc7
[7]fir_coeff 6 : 0x3e4a
[3]AEC Table 1
[1]rxmode_onoff : OFF
[2]delay_onoff : OFF
[3]delay : 0
[4]aec_onoff : OFF
[5]aec_rxgain : 0x200
[6]aec_mu : 0x0
[4]AEC Table 2
[1]dtrxg_onoff : OFF
[2]post_onoff : OFF
[3]post_min : 11
[4]post_gain : 11
[5]dtgc_onoff : OFF
[6]rxdet_onoff : OFF
[5]AEC Table 3
[1]rxdet_th_1st : -38
[2]rxdet_hangmax_1st : 6
[3]dtgc_gain_1st : 0x4000
[4]rxdet_th_2nd : -38
[5]rxdet_hangmax_2nd : 6
[6]dtgc_gain_2nd : 0x4000
[7]txdet_onoff : OFF
[6]NS Table 1
[1]iir_onoff: OFF
[2]ns_onoff : ON
[3]rxtx_agc_tbl : 13
[4]weight_ss_ns : 20
[5]ss_gain_ns : 11
[6]ns_gain_ns : 11
[7]NS Table 2
[1]tx_filter_onoff : OFF
[2]tx_agc_onoff : OFF
[3]in_txgain : 0x400
[4]out_txgain : 0xe40
[5]tx_cng_onoff : OFF
[6]noise_th_bits : 16

dagrim1 said:
Anyone already know more about what all these settings do (or some explanation on the terms?).
Trying to find out if I can change something here to improve the audio part of the video recording.
Click to expand...
Click to collapse
Same here...I'm interested in how to adjust the recording volume or to make the mic less sensible.

Not sure tweaking some of these settings will enable both side voice recording?

pmtan666 said:
Not sure tweaking some of these settings will enable both side voice recording?
Click to expand...
Click to collapse
What do you mean by that? Full Duplex? I am also interested in knowing that... Want to record my calls sometimes.
Also, as of now, I am desperately trying to ENABLE SERVICE MODE as it does not work in DDGJ4 firmware.
Can someone help?
EDIT: GOTCHA!
I found a way to get inside the service mode which does not work otherwise using the usual *#197328640# code. You could follow this on DDGJ4 to get inside:
Use the network info code *#0011#, you reach the below menu:
MAIN MENU
[1] DEBUG SCREEN
[1] BASIC INFORMATION
UMTS : HOME(CS+PS)
RRC State: IDLE
WCDMA 2100 Band 1
Reg PLMN 240-2, IsPCS? 0
FREQ DL:10737
FREQ UL:9787
CELL_ID:0xhhhhhh <- Disappears when 3G is not available
LAC: 0xhhhh
PSC:hhh
RSCP:-94, ECIO:-5 <- Changing
Now just hit the menu button, back (twice) and voila! you are at the ServiceMode home page! hope this helps.
Noticed, no "Audio" menu and hence no "Diamond Solution" in ServiceMode. Seems no hardware tweaks on this firmware with sound (good for me).

I'm also almost sure we could tweak audio recording with this section but we need someone who knows what settings mean what, I've tried playing with some of them to no effect at all.

I think there's an app in the market that you can easily access the sevice menu with a tap. check it out.

Service mode DIAG CONFIG
what's the relevance for the SPEED 115200 and 921600 I changed mine to 921600 long ago and I don't think it matters? I know they're baud rates but for what? Data or? I get the same data streams either way so what's it for?

NV Rebluid
Anyone try this.
[6] COMMON
[6] NV REBUILD
I have some hope that command resolve my IMEI problema, but... no success.
I have JPC firmware. As anyone with an 2.1 firmware try it?

help phone app not producing sound via handset
so I went into the service menu and changed some things and now my phone app doesn't work right....it is fine in speakermode or with a headset attached, but by default it now produces no sound nor does it capture any sound.
I've tweaked gain and volume in the 5.1.1 menu to no avail...
so I was hoping I could understand more about what those menus do.
am I correct in assuming that the phone app would use handset->volume for calls that use the built-in earpiece and speaker? what's partly puzzling to me is that sipdroid, using the same devices, works fine....
I also just generally don't know what a lot of the items are for (I didn't change any of the things I didn't know about, but it would be nice to have a clue).
NR, DRP, SER, and CNI are just acronyms to me. I assume NR is for noise reduction but I have no idea what the others are...
does anyone have a complete list of how it comes out of the box?
thanks...
-alan

same thing :S
@chekovma:
I'm suffering the same problem, did you happen to get your hands on a solution to this?
Does anyone have any feedback on how to solve this problem?
Any assistance would be appreciated.
-aehlayel

I dialed *#197328640# but nothing is happening. My SGS is NON-ROOTED
My FW Info:
PDA: I9000DDJP6
PHONE: I9000DDJP2
CSC: I9000ODDJP5
Build Info: 2010,11

my headset/earphones.only one speaker works
my headset/earphones.only one speaker works out of 2 and in a very low volume.Can i use any service menu selections for this?

[TOOL] Universal Fastboot & Adb Tool

This is my latest creation. Easy to use, it has been created to support all devices compatible with fastboot and adb. Currently, only some basic functions are available, coming soon many more commands
Universal Fastboot & Adb Tool
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
FUNCTIONS
Install Drivers
Unlock Bootloader
Flash Recovery
Reboot Phone (from anywhere to anywhere)
Update the Tool to last version
Complete Wipe from Fastboot
Open a cmd window with fastboot and adb privileged
NOTE
This is the first release and it can have some bug. If you find some bug tell me with a pm or a comment
Before using the tool, make sure that you have turned the oem unlocking, usb debugging.
If you have any problems during installation then first try to update the Microsoft Net freamwork to latest version:
https://www.microsoft.com/it-it/download/details.aspx?id=30653
HOW TO INSTALL
Download .zip file;
Extract all its contents into a folder;
Click on setup.exe;
Click on "Install";
Waiting for the end of the process;
Enjoy your tool
UPDATE
There will be no need to re-download the new tool, but just look for new updates directly from the tool.
In all cases I'll update the link in this thread and report it when there are new updates with its changelog.
(If you have some error during the update, please click continue and if you have some problems after an update please try to unistall the tool and install the lastest tool avaible)
CHANGELOG
#1.0.0.0
Initial Release
#1.0.0.1
Added Huawei Unlock Bootloader support
Added Sony Unlock Bootloader support
Added Some Other Commands (now you can open a free cmd window with fastboot and adb privileged)
General Bugfix.
#1.0.0.2
Added new Fastboot and Adb .exe;
Removed Vendor ID option ( with new Fastboot and Adb .exe is not necessary);
Fix flash recovery and boot;
General Bugfix.
CONTACTS
If you think it necessary to add new features please comments or send me a private message or send me an email to [email protected]
DOWNLOAD
Universal Fastboot & Adb Tool
( Alternative Link )
DONATE LINK
If you want to support the project please consider making a donation, thanks (If you make a donation, please tell me for what tool you have made it).
DONATORS:
- Alberto Pettenò: 2.00 €
- Oliver E. : 3.50 €
- Tunde Alabi: 10.00 $
- Giovanni MacCelli: 5.00 €
- Cristian Godnik: 5.00 €
- Luca Milkovitsch: 5.00 €
- Nicolò Rossini: 2.00 €
- Luigi Pedrini: 1.00 €
- Oscar Davi: 5.00 €
- Claudio Orititi: 2.50 €
- James Goldsbury: 3.00 $
- Abel Varela Carou: 2.00 €
- Juan Carlos Cuevas Barreira: 5.00 €
- scooterofficina: 1.00 €
- Paul Moore: 3.00 GPB
- Mattia Colle: 1.00 €
- Maryan Komar: 2.00 €
- Luigi Ardizzone: 1.00 €
- Maximo76: 10.00 €
- Loïc Payol: 13.37 €
- Antonio Rateni: 2.00 €
- Matteo Verzella: 0.50 €
- Lukas Heddendorp: 2.00 €
- Scott Dare: 5.00 €
- Leonardo F. : 3.00 €
- Andrea Tassotti: 5.00 €
- Stefano Franceschini: 1.00 €
- Евгений Сериков: 1.00 €
- Stian Domben Bardsen: 20.00 €
- Kevin Dang: 2.00 $
- David Lebrun: 5.00 €
- James Hise: 15.00 €
- Daniele Barbana: 0.40 €
- Christophe Van B. : 2.50 €
- Robert Möller: 10.00 €
- Johannes Fleischmann: 5.00 €
- Marco Rigoni: 10.00 €
- Pasquale Rivieccio: 2.00 €
- Jorge Toledo: 5.00 €
- ionel firuti: 10.00 €
- Argel Thulin: 2.00 €
- Tim Altmann: 1.00 €
- Christoph Hackl: 2.00 €
- Joel Vazquez: 10.00 $
- Tommaso Tautonico: 1.00 €
- Fabio Vannoni: 4.50 €
- Willy Andresen: 10.00 $
- Antonino Muscarella: 1.00 €
- Каширин Михаил: 1.00 ₽
- Pietro Brasile: 2.00 €
- Giorgio Frasca: 5.00 €
- Andrea Della Verde: 1.00 €
- RAFAL SZALKA: 2.00 GPB
- marco da silva: 2.00 €
- Jose Rodriguez Martinez Z: 1.00 €
- Francesco Rizzo: 1.00 €
Really thanks to donators​

thanks will give feedback soon

Excelente
Sent from my Pixel XL using XDA-Developers mobile app

mataflakitas said:
Excelente
Sent from my Pixel XL using XDA-Developers mobile app
Click to expand...
Click to collapse
You have tried it on Pixel?

Doesn't work for me. Setup.exe is getting some error

Imresaks said:
Doesn't work for me. Setup.exe is getting some error
Click to expand...
Click to collapse
What windows do you have? Can you send an error screen?

mauronofrio said:
What windows do you have? Can you send an error screen?
Click to expand...
Click to collapse
I have Windows Embedded 8.1 Industry Pro (got it for free xd)
This is the error:
PLATFORM VERSION INFO
Windows : 6.2.9200.0 (Win32NT)
Common Language Runtime : 4.0.30319.42000
System.Deployment.dll : 4.6.1055.0 built by: NETFXREL2
clr.dll : 4.6.1055.0 built by: NETFXREL2
dfdll.dll : 4.6.1055.0 built by: NETFXREL2
dfshim.dll : 6.3.9600.16384 (winblue_rtm.130821-1623)
SOURCES
Deployment url : file:///D:/Desktop/Universal%20ADB%20&%20Fastboot%20tool/Universal_Fastboot_And_Adb_Tool.application
Application url : file:///D:/Desktop/Universal%20ADB%20&%20Fastboot%20tool/Application%20Files/Universal_Fastboot_And_Adb_Tool_1_0_0_0/Universal_Fastboot_And_Adb_Tool.exe.manifest
IDENTITIES
Deployment Identity : Universal_Fastboot_And_Adb_Tool.application, Version=1.0.0.0, Culture=en, PublicKeyToken=72a37ccb40dda1f2, processorArchitecture=msil
Application Identity : Universal_Fastboot_And_Adb_Tool.exe, Version=1.0.0.0, Culture=en, PublicKeyToken=72a37ccb40dda1f2, processorArchitecture=msil, type=win32
APPLICATION SUMMARY
* Installable application.
ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* An exception occurred while determining trust. Following failure messages were detected:
+ Value does not fall within the expected range.
* Activation of D:\Desktop\Universal ADB & Fastboot tool\Universal_Fastboot_And_Adb_Tool.application resulted in exception. Following failure messages were detected:
+ Value does not fall within the expected range.
COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.
WARNINGS
There were no warnings during this operation.
OPERATION PROGRESS STATUS
* [14.10.2016 20:29:57] : Activation of D:\Desktop\Universal ADB & Fastboot tool\Universal_Fastboot_And_Adb_Tool.application has started.
* [14.10.2016 20:29:57] : Processing of deployment manifest has successfully completed.
* [14.10.2016 20:29:57] : Installation of the application has started.
* [14.10.2016 20:29:57] : Processing of application manifest has successfully completed.
* [14.10.2016 20:29:58] : Found compatible runtime version 4.0.30319.
ERROR DETAILS
Following errors were detected during this operation.
* [14.10.2016 20:29:58] System.ArgumentException
- Value does not fall within the expected range.
- Source: mscorlib
- Stack trace:
at System.Deployment.Internal.Isolation.IDefinitionAppId.EnumAppPath()
at System.ActivationContext.CreateFromNameAndManifests(ApplicationIdentity applicationIdentity, String[] manifestPaths)
at System.Deployment.Application.ActivationDescription.ToActivationContext()
at System.Deployment.Application.ApplicationActivator.DownloadApplication(SubscriptionState subState, ActivationDescription actDesc, Int64 transactionId, TempDirectory& downloadTemp)
at System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState& subState, ActivationDescription actDesc)
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
* [14.10.2016 20:29:58] System.ArgumentException
- Value does not fall within the expected range.
- Source: mscorlib
- Stack trace:
at System.Deployment.Internal.Isolation.IDefinitionAppId.EnumAppPath()
at System.ActivationContext.CreateFromNameAndManifests(ApplicationIdentity applicationIdentity, String[] manifestPaths)
at System.Deployment.Application.ActivationDescription.ToActivationContext()
at System.Deployment.Application.ApplicationActivator.DownloadApplication(SubscriptionState subState, ActivationDescription actDesc, Int64 transactionId, TempDirectory& downloadTemp)
at System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState& subState, ActivationDescription actDesc)
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.

Imresaks said:
I have Windows Embedded 8.1 Industry Pro (got it for free xd)
This is the error:
PLATFORM VERSION INFO
Windows : 6.2.9200.0 (Win32NT)
Common Language Runtime : 4.0.30319.42000
System.Deployment.dll : 4.6.1055.0 built by: NETFXREL2
clr.dll : 4.6.1055.0 built by: NETFXREL2
dfdll.dll : 4.6.1055.0 built by: NETFXREL2
dfshim.dll : 6.3.9600.16384 (winblue_rtm.130821-1623)
SOURCES
Deployment url : file:///D:/Desktop/Universal%20ADB%20&%20Fastboot%20tool/Universal_Fastboot_And_Adb_Tool.application
Application url : file:///D:/Desktop/Universal%20ADB%20&%20Fastboot%20tool/Application%20Files/Universal_Fastboot_And_Adb_Tool_1_0_0_0/Universal_Fastboot_And_Adb_Tool.exe.manifest
IDENTITIES
Deployment Identity : Universal_Fastboot_And_Adb_Tool.application, Version=1.0.0.0, Culture=en, PublicKeyToken=72a37ccb40dda1f2, processorArchitecture=msil
Application Identity : Universal_Fastboot_And_Adb_Tool.exe, Version=1.0.0.0, Culture=en, PublicKeyToken=72a37ccb40dda1f2, processorArchitecture=msil, type=win32
APPLICATION SUMMARY
* Installable application.
ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* An exception occurred while determining trust. Following failure messages were detected:
+ Value does not fall within the expected range.
* Activation of D:\Desktop\Universal ADB & Fastboot tool\Universal_Fastboot_And_Adb_Tool.application resulted in exception. Following failure messages were detected:
+ Value does not fall within the expected range.
COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.
WARNINGS
There were no warnings during this operation.
OPERATION PROGRESS STATUS
* [14.10.2016 20:29:57] : Activation of D:\Desktop\Universal ADB & Fastboot tool\Universal_Fastboot_And_Adb_Tool.application has started.
* [14.10.2016 20:29:57] : Processing of deployment manifest has successfully completed.
* [14.10.2016 20:29:57] : Installation of the application has started.
* [14.10.2016 20:29:57] : Processing of application manifest has successfully completed.
* [14.10.2016 20:29:58] : Found compatible runtime version 4.0.30319.
ERROR DETAILS
Following errors were detected during this operation.
* [14.10.2016 20:29:58] System.ArgumentException
- Value does not fall within the expected range.
- Source: mscorlib
- Stack trace:
at System.Deployment.Internal.Isolation.IDefinitionAppId.EnumAppPath()
at System.ActivationContext.CreateFromNameAndManifests(ApplicationIdentity applicationIdentity, String[] manifestPaths)
at System.Deployment.Application.ActivationDescription.ToActivationContext()
at System.Deployment.Application.ApplicationActivator.DownloadApplication(SubscriptionState subState, ActivationDescription actDesc, Int64 transactionId, TempDirectory& downloadTemp)
at System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState& subState, ActivationDescription actDesc)
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
* [14.10.2016 20:29:58] System.ArgumentException
- Value does not fall within the expected range.
- Source: mscorlib
- Stack trace:
at System.Deployment.Internal.Isolation.IDefinitionAppId.EnumAppPath()
at System.ActivationContext.CreateFromNameAndManifests(ApplicationIdentity applicationIdentity, String[] manifestPaths)
at System.Deployment.Application.ActivationDescription.ToActivationContext()
at System.Deployment.Application.ApplicationActivator.DownloadApplication(SubscriptionState subState, ActivationDescription actDesc, Int64 transactionId, TempDirectory& downloadTemp)
at System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState& subState, ActivationDescription actDesc)
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.
Click to expand...
Click to collapse
Maybe there are some problem with you windows version, try to click on Universal_Fastboot_And_Adb_Tool.application and not on setup.exe . Tell me what happen

mauronofrio said:
Maybe there are some problem with you windows version, try to click on Universal_Fastboot_And_Adb_Tool.application and not on setup.exe . Tell me what happen
Click to expand...
Click to collapse
Also doesn't work
Here's the error:
PLATFORM VERSION INFO
Windows : 6.2.9200.0 (Win32NT)
Common Language Runtime : 4.0.30319.42000
System.Deployment.dll : 4.6.1055.0 built by: NETFXREL2
clr.dll : 4.6.1055.0 built by: NETFXREL2
dfdll.dll : 4.6.1055.0 built by: NETFXREL2
dfshim.dll : 6.3.9600.16384 (winblue_rtm.130821-1623)
SOURCES
Deployment url : file:///D:/Desktop/Universal%20ADB%20&%20Fastboot%20tool/Universal_Fastboot_And_Adb_Tool.application
Application url : file:///D:/Desktop/Universal%20ADB%20&%20Fastboot%20tool/Application%20Files/Universal_Fastboot_And_Adb_Tool_1_0_0_0/Universal_Fastboot_And_Adb_Tool.exe.manifest
IDENTITIES
Deployment Identity : Universal_Fastboot_And_Adb_Tool.application, Version=1.0.0.0, Culture=en, PublicKeyToken=72a37ccb40dda1f2, processorArchitecture=msil
Application Identity : Universal_Fastboot_And_Adb_Tool.exe, Version=1.0.0.0, Culture=en, PublicKeyToken=72a37ccb40dda1f2, processorArchitecture=msil, type=win32
APPLICATION SUMMARY
* Installable application.
ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* An exception occurred while determining trust. Following failure messages were detected:
+ Value does not fall within the expected range.
* Activation of D:\Desktop\Universal ADB & Fastboot tool\Universal_Fastboot_And_Adb_Tool.application resulted in exception. Following failure messages were detected:
+ Value does not fall within the expected range.
COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.
WARNINGS
There were no warnings during this operation.
OPERATION PROGRESS STATUS
* [14.10.2016 20:39:57] : Activation of D:\Desktop\Universal ADB & Fastboot tool\Universal_Fastboot_And_Adb_Tool.application has started.
* [14.10.2016 20:39:57] : Processing of deployment manifest has successfully completed.
* [14.10.2016 20:39:57] : Installation of the application has started.
* [14.10.2016 20:39:57] : Processing of application manifest has successfully completed.
* [14.10.2016 20:39:58] : Found compatible runtime version 4.0.30319.
ERROR DETAILS
Following errors were detected during this operation.
* [14.10.2016 20:39:58] System.ArgumentException
- Value does not fall within the expected range.
- Source: mscorlib
- Stack trace:
at System.Deployment.Internal.Isolation.IDefinitionAppId.EnumAppPath()
at System.ActivationContext.CreateFromNameAndManifests(ApplicationIdentity applicationIdentity, String[] manifestPaths)
at System.Deployment.Application.ActivationDescription.ToActivationContext()
at System.Deployment.Application.ApplicationActivator.DownloadApplication(SubscriptionState subState, ActivationDescription actDesc, Int64 transactionId, TempDirectory& downloadTemp)
at System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState& subState, ActivationDescription actDesc)
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
* [14.10.2016 20:39:58] System.ArgumentException
- Value does not fall within the expected range.
- Source: mscorlib
- Stack trace:
at System.Deployment.Internal.Isolation.IDefinitionAppId.EnumAppPath()
at System.ActivationContext.CreateFromNameAndManifests(ApplicationIdentity applicationIdentity, String[] manifestPaths)
at System.Deployment.Application.ActivationDescription.ToActivationContext()
at System.Deployment.Application.ApplicationActivator.DownloadApplication(SubscriptionState subState, ActivationDescription actDesc, Int64 transactionId, TempDirectory& downloadTemp)
at System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState& subState, ActivationDescription actDesc)
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.

Imresaks said:
Also doesn't work
Here's the error:
PLATFORM VERSION INFO
Windows : 6.2.9200.0 (Win32NT)
Common Language Runtime : 4.0.30319.42000
System.Deployment.dll : 4.6.1055.0 built by: NETFXREL2
clr.dll : 4.6.1055.0 built by: NETFXREL2
dfdll.dll : 4.6.1055.0 built by: NETFXREL2
dfshim.dll : 6.3.9600.16384 (winblue_rtm.130821-1623)
SOURCES
Deployment url : file:///D:/Desktop/Universal%20ADB%20&%20Fastboot%20tool/Universal_Fastboot_And_Adb_Tool.application
Application url : file:///D:/Desktop/Universal%20ADB%20&%20Fastboot%20tool/Application%20Files/Universal_Fastboot_And_Adb_Tool_1_0_0_0/Universal_Fastboot_And_Adb_Tool.exe.manifest
IDENTITIES
Deployment Identity : Universal_Fastboot_And_Adb_Tool.application, Version=1.0.0.0, Culture=en, PublicKeyToken=72a37ccb40dda1f2, processorArchitecture=msil
Application Identity : Universal_Fastboot_And_Adb_Tool.exe, Version=1.0.0.0, Culture=en, PublicKeyToken=72a37ccb40dda1f2, processorArchitecture=msil, type=win32
APPLICATION SUMMARY
* Installable application.
ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* An exception occurred while determining trust. Following failure messages were detected:
+ Value does not fall within the expected range.
* Activation of D:\Desktop\Universal ADB & Fastboot tool\Universal_Fastboot_And_Adb_Tool.application resulted in exception. Following failure messages were detected:
+ Value does not fall within the expected range.
COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.
WARNINGS
There were no warnings during this operation.
OPERATION PROGRESS STATUS
* [14.10.2016 20:39:57] : Activation of D:\Desktop\Universal ADB & Fastboot tool\Universal_Fastboot_And_Adb_Tool.application has started.
* [14.10.2016 20:39:57] : Processing of deployment manifest has successfully completed.
* [14.10.2016 20:39:57] : Installation of the application has started.
* [14.10.2016 20:39:57] : Processing of application manifest has successfully completed.
* [14.10.2016 20:39:58] : Found compatible runtime version 4.0.30319.
ERROR DETAILS
Following errors were detected during this operation.
* [14.10.2016 20:39:58] System.ArgumentException
- Value does not fall within the expected range.
- Source: mscorlib
- Stack trace:
at System.Deployment.Internal.Isolation.IDefinitionAppId.EnumAppPath()
at System.ActivationContext.CreateFromNameAndManifests(ApplicationIdentity applicationIdentity, String[] manifestPaths)
at System.Deployment.Application.ActivationDescription.ToActivationContext()
at System.Deployment.Application.ApplicationActivator.DownloadApplication(SubscriptionState subState, ActivationDescription actDesc, Int64 transactionId, TempDirectory& downloadTemp)
at System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState& subState, ActivationDescription actDesc)
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
* [14.10.2016 20:39:58] System.ArgumentException
- Value does not fall within the expected range.
- Source: mscorlib
- Stack trace:
at System.Deployment.Internal.Isolation.IDefinitionAppId.EnumAppPath()
at System.ActivationContext.CreateFromNameAndManifests(ApplicationIdentity applicationIdentity, String[] manifestPaths)
at System.Deployment.Application.ActivationDescription.ToActivationContext()
at System.Deployment.Application.ApplicationActivator.DownloadApplication(SubscriptionState subState, ActivationDescription actDesc, Int64 transactionId, TempDirectory& downloadTemp)
at System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState& subState, ActivationDescription actDesc)
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.
Click to expand...
Click to collapse
I think there are some problem with your windows version, if you want i can send you all file without setup

mauronofrio said:
I think there are some problem with your windows version, if you want i can send you all file without setup
Click to expand...
Click to collapse
Would be nice. Thanks

Imresaks said:
Would be nice. Thanks
Click to expand...
Click to collapse
i can send it to you tomorrow through private message

mauronofrio said:
i can send it to you tomorrow through private message
Click to expand...
Click to collapse
Yes can you please

Imresaks said:
Yes can you please
Click to expand...
Click to collapse
Sent

mauronofrio said:
Sent
Click to expand...
Click to collapse
Thanks

Thanks, this is a nice program. Is the vendor ID needed for unlocking boot loader on my P6?? I have windows 10 and I used the EXE file.
Universal_fastboot_and_ABD_tool file, not the setup file. Installed and had program on my screen.
thank you,
Jim

duhsquid said:
Thanks, this is a nice program. Is the vendor ID needed for unlocking boot loader on my P6?? I have windows 10 and I used the EXE file.
Universal_fastboot_and_ABD_tool file, not the setup file. Installed and had program on my screen.
thank you,
Jim
Click to expand...
Click to collapse
What problem? I dont know all device that need vendor id, but nexus 6p dont need vendor id

Uninstall
Mauronofrio,
How can I uninstall the Tool.
I keep getting a error messages when I want to use the tool: "Cannot start the application, please contact the developer", or if I want to re-install the tool: "You cannont start the Universal_Fastboot_And_Adb_Tool from this location because it is already started from an other location".
Any tips are much appreciated.
Greetings
Harald

777.300 said:
Mauronofrio,
How can I uninstall the Tool.
I keep getting a message when I want to use the tool or if I want to re-install the tool: "You cannont start the Universal_Fastboot_And_Adb_Tool from this location because it is already started from an other location".
Any tips are much appreciated.
Greetings
Harald
Click to expand...
Click to collapse
Go in the Control Panel and go in application, you can find the app and you can unistall it

mauronofrio said:
Go in the Control Panel and go in application, you can find the app and you can unistall it
Click to expand...
Click to collapse
Pfffffff, thats strange. Tried to uninstall it several times via Revo Uninstaller Pro and that did not work.
Now via Control Panel the uninstall worked, strange.
Thanks for the quick reply, now after re-installation all working fine now.
Great Tool, thanks for the development.

Segmentation Fault in all customs ROMs

The Segmentation Fault error is fixed on LineageOS. It will be fixed progressively in any other ROM in the upcoming updates.
Infinite thanks to @wzedlare, and the other persons and devs that helped us. Im gonna request to mods to close this thread
And over again thanks to all! I'm so happy now!
On certain devices a series of binaries, shell/ADB commands are not working correctly.
Most of the time when one of these binaries I invoked the crash with a "Segmentation fault" error (SIGEGV 11). If the command/binarie is executed multiple times, at some point it works without the error. (1 of 30 times approximately).
These commands/binaries are very important for Root applications, but are not limited to them.
As a result many applications that need ROOT work very sporadically, and some not root apps are affected too.
If you are suffering the same problem, please share your logcats, the app or the command affected, and your device model, in order to get more information about the problem to help the devs and other users.
Affected ROMs and Devices ​
So far all customs ROMs for Cedric are affected. It appears to be related to a Cedric variant with Dual SIM, removable battery and 3GB of RAM. Mostly sold in Europe trough Amazon.
Known affected apps and Workarrounds:​
SuperSu and MagikSU(all versions): Devices rooted with Magisk or SuperSu, suffer from the error almost every time that SU binarir is invoked. The visible symptom is that although according the info provided by the application (Magisk manager says that the device is correctly rooted), the requests to get root permission will not popup because the binarie is crash almost 29 to 30 times. As a result these options for root are almost useless.
LineageOS SU By itself works correctly, the binarie will not crash, but the other commands still will be affected. Is the most funtional root option for affected devices!!
Secure Settings, BetterBattery stats, AutoTools ADB commands to Grant permissions can be executed multiple times. Once authorized, they work correctly.
Super Doze To change doze settings you need to press apply button multiple times. There is no way to know when the change was actually applied except using ADB.
Nap Time it's useless to change doze settings, but force doze is working.
Greenify, Servicely The will pop out an error every time that trying to stop every single app. In short they are useles.
Titanium BackUp and Link2SD To freeze or unfreeze an app you must tap multiples times until it work.
Disable Services Tap multiple times until it work.
LiveBoot After installed it will work only 1/30 reboots (Useless)
Known affected binaries​
pm
am
settings
adb backup
Magisk Su, and Super Su
Disclaimer​:
I'm not a developer. I created this topic to help other users, to find a workarounds to the error. I'm not a developer. I created this topic to help other users, to find a way to dodge the error.
In addition I hope to raise awareness about this problem and help the devs with the information that is recopiled.
Screenshots Examples and Logcats of the error​
Logcat: http://cloud.tapatalk.com/s/59...279dd2/2017-07-25-12-12-33.txt
Series of post in LineageOS Thread talking about the issue: https://forum.xda-developers.com/g5/development/7-1-x-lineageos-14-1-moto-g5-t3611973/page48
Tipical Crash message after invoking a command:
Code:
08-23 19:04:28.670 12408 12408 I chatty : uid=0(root) app_process expire 847 lines
08-23 19:04:28.694 11748 11748 W Atfwd_Sendcmd: AtCmdFwd service not published, waiting... retryCnt : 4
08-23 19:04:28.715 12408 12408 F libc : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x9c in tid 12408 (app_process)
08-23 19:04:28.716 402 402 I chatty : uid=0(root) /system/bin/debuggerd expire 2 lines
08-23 19:04:28.777 12410 12410 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
08-23 19:04:28.778 12410 12410 F DEBUG : LineageOS Version: '14.1-20170811-UNOFFICIAL-cedric'
08-23 19:04:28.778 12410 12410 F DEBUG : Build fingerprint: 'motorola/lineage_cedric/cedric:7.1.2/NJH47F/43d07c81c5:userdebug/test-keys'
08-23 19:04:28.778 12410 12410 F DEBUG : Revision: '0'
08-23 19:04:28.778 12410 12410 F DEBUG : ABI: 'arm'
08-23 19:04:28.778 12410 12410 F DEBUG : pid: 12408, tid: 12408, name: app_process >>> app_process
[/Quote]
Click to expand...
Click to collapse

Great thread! My device is also affected and matches the mentioned specs.

I've got the recommended LineageSU method installed but normally don't use ADB. The only application I did try to use is Liveboot, where the test mode fails to start quite often. Transferring files via USB won't work on the first try, but I don't know how to tell if that is related. My device also is the European G5 with triple slot, 16GB and removable battery, type XT1676 or M2675. Currently running the unofficial LineageOS 14.1 build by @wzedlare from August, 2017.

ektus said:
I've got the recommended LineageSU method installed but normally don't use ADB. The only application I did try to use is Liveboot, where the test mode fails to start quite often. Transferring files via USB won't work on the first try, but I don't know how to tell if that is related. My device also is the European G5 with triple slot, 16GB and removable battery, type XT1676 or M2675. Currently running the unofficial LineageOS 14.1 build by @wzedlare from August, 2017.
Click to expand...
Click to collapse
The easiest way to check if a problem is caused by the segmentation fault is open a terminal emulator session (you can install any terminal emulator from the Playstore), and write:
su
logcat | grep "signal 11 (SIGSEGV)"
It will filter the logcat showing the Segmentation Fault errors. If you get new errors when performing an certain action, or opening certain app, it's affected by the error.
Enviado desde mi Moto G5 mediante Tapatalk

The easiest way to check if a problem is caused by the segmentation fault is open a terminal emulator session (you can install any terminal emulator from the Playstore), and write:
su
logcat | grep "signal 11 (SIGSEGV)"
Click to expand...
Click to collapse
That one shows quite a number of results, at a first glance most with
Code:
signal 11 (SIGSEGV), code 1 (SEGV_MAPPER), fault addr 0x9c in tid xxxxx (zygote)
and one of each with
Code:
(app_process)
and
Code:
(Downloadmanager)
The fault addr is always the same except for the Downloadmanager where it's
Code:
code 2 (SEGV_ACCERR), fault addr 0x200006464
.
Regards
Ektus.

Just for reference and to add to the discussion started in the Moto G5 TWRP thread, I never had any such issuess. My model is the 3GB dual sim version, bought at Amazon Germany. LineageOS with root addon.

Don't know if it is of importance but it never got to boot a clean system with changed filesystem. Tried to change /data to ext4, also tried it with /system as f2fs but nothing worked. This also happened with the new TWRP 3.1.1.
I also tried to flash phh supersu with noverity. But could only boot to bootloader which gave me an error.
Just wanted to share my attempts. I have limited knowledge of the fundamentals of segmentation so I just tried whatever I could find.

floydburgermcdahm said:
Just for reference and to add to the discussion started in the Moto G5 TWRP thread, I never had any such issuess. My model is the 3GB dual sim version, bought at Amazon Germany. LineageOS with root addon.
Click to expand...
Click to collapse
F***! what will be the difference between your device and mine?
Did you ever use the rooted stock ROM?
Can you please, share these numbers from the sticker behind your battery, to know your exact device variant:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks for your help!
Enviado desde mi Moto G5 mediante Tapatalk

Anyone affected with segmentation fault error, o with a device with Dual SIM, please share these numbers.
A picture is not necessary, just the numbers. It's behind the battery
Enviado desde mi Moto G5 mediante Tapatalk

Here is mine.
Edit: if picture is too small, it is the same phone as yours...

Just for reference my phone doesn't have any issues with root function
XT1675
2+16gb
All other numbers are the same
The FCC ID is the registration code for the United States
Federal Communications Commission
First three letters are grantee code - the rest is product code
I think the type relates to the battery size

mrfrantastic said:
Here is mine.
Edit: if picture is too small, it is the same phone as yours...
Click to expand...
Click to collapse
Let's see if @floydburgermcdahm has exactly the same device. Perhaps there is more than one 3gb Dual SIM Variant.
floydburgermcdahm said:
I never had any such issuess. My model is the 3GB dual sim version, bought at Amazon Germany. LineageOS with root addon.
Click to expand...
Click to collapse
Enviado desde mi Moto G5 mediante Tapatalk

andyro2008 said:
Let's see if @floydburgermcdahm has exactly the same device. Perhaps there is more than one 3gb Dual SIM Variant.
Click to expand...
Click to collapse
Mine is: XT1676, 3+16GB, FCC ID: IHDT56VF4, Type: M2675
So, no idea what the difference between our devices might be. I did use the stock ROM briefly, but never rooted it. Went straight to LOS with root addon.
Yeah and thanks for reminding me that the bloody case is a ***** to open!

floydburgermcdahm said:
Mine is: XT1676, 3+16GB, FCC ID: IHDT56VF4, Type: M2675
So, no idea what the difference between our devices might be. I did use the stock ROM briefly, but never rooted it. Went straight to LOS with root addon.
Yeah and thanks for reminding me that the bloody case is a ***** to open!
Click to expand...
Click to collapse
So if you type "pm" in a terminal you don't get a segmentation fault?

TheFixItMan said:
Just for reference my phone doesn't have any issues with root function
XT1675
2+16gb
All other numbers are the same
The FCC ID is the registration code for the United States
Federal Communications Commission
First three letters are grantee code - the rest is product code
I think the type relates to the battery size
Click to expand...
Click to collapse
I tried a strace with the command "pm". Something of this can be useful? Can it be something related to libraries? Those "No such file or directory" are weird. The full log files, one from a successfull pm and another for a failed one, are attached. Thanks for your atention, i hope you could help us.
Code:
openat(AT_FDCWD, "/system/lib/libart.so", O_RDONLY|O_LARGEFILE) = 5
fstat64(5, {st_mode=0, st_size=1, ...}) = 0
read(5, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0\0\0\0\0004\0\0\0"..., 4096) = 4096
_llseek(5, 5888928, [5888928], SEEK_SET) = 0
read(5, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 4096) = 1320
_llseek(5, 4584364, [4584364], SEEK_SET) = 0
read(5, "\0.symtab\0.strtab\0.shstrtab\0.inte"..., 4096) = 4096
_llseek(5, 4584348, [4584348], SEEK_SET) = 0
read(5, "libart.so\0\0\0\21\r\350\370\0.symtab\0.strtab"..., 4096) = 4096
close(5) = 0
openat(AT_FDCWD, "/system/lib/.debug/libart.so", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/debug/system/lib/libart.so", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory)
clock_gettime(CLOCK_MONOTONIC, {7390, 135831818}) = 0
openat(AT_FDCWD, "/system/lib/libandroid_runtime.so", O_RDONLY|O_LARGEFILE) = 5
fstat64(5, {st_mode=0, st_size=1, ...}) = 0
mmap2(NULL, 1075276, PROT_READ, MAP_PRIVATE, 5, 0) = 0xaaada000
close(5) = 0
openat(AT_FDCWD, "/system/lib/libandroid_runtime.so", O_RDONLY|O_LARGEFILE) = 5
fstat64(5, {st_mode=0, st_size=1, ...}) = 0
read(5, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0\0\0\0\0004\0\0\0"..., 4096) = 4096
_llseek(5, 1074116, [1074116], SEEK_SET) = 0
read(5, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 4096) = 1160
_llseek(5, 1073810, [1073810], SEEK_SET) = 0
read(5, "\0.shstrtab\0.interp\0.note.android"..., 4096) = 1466
_llseek(5, 1073782, [1073782], SEEK_SET) = 0
read(5, "libandroid_runtime.so\0\0\0o\223i\206\0.sh"..., 4096) = 1494
close(5) = 0
openat(AT_FDCWD, "/system/lib/libandroid_runtime.so", O_RDONLY|O_LARGEFILE) = 5
fstat64(5, {st_mode=0, st_size=1, ...}) = 0
read(5, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0\0\0\0\0004\0\0\0"..., 4096) = 4096
_llseek(5, 1074116, [1074116], SEEK_SET) = 0
read(5, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 4096) = 1160
_llseek(5, 1073810, [1073810], SEEK_SET) = 0
read(5, "\0.shstrtab\0.interp\0.note.android"..., 4096) = 1466
_llseek(5, 1073782, [1073782], SEEK_SET) = 0
read(5, "libandroid_runtime.so\0\0\0o\223i\206\0.sh"..., 4096) = 1494
close(5) = 0
openat(AT_FDCWD, "/system/lib/.debug/libandroid_runtime.so", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/debug/system/lib/libandroid_runtime.so", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/system/bin/app_process32", O_RDONLY|O_LARGEFILE) = 5
fstat64(5, {st_mode=0, st_size=1, ...}) = 0

Sorry repeated post

andyro2008 said:
I tried a strace with the command "pm". Something of this can be useful? Can it be something related to libraries? Those "No such file or directory" are weird. The full log files, one from a successfull pm and another for a failed one, are attached. Thanks for your atention, i hope you could help us.
Code:
openat(AT_FDCWD, "/system/lib/libart.so", O_RDONLY|O_LARGEFILE) = 5
fstat64(5, {st_mode=0, st_size=1, ...}) = 0
read(5, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0\0\0\0\0004\0\0\0"..., 4096) = 4096
_llseek(5, 5888928, [5888928], SEEK_SET) = 0
read(5, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 4096) = 1320
_llseek(5, 4584364, [4584364], SEEK_SET) = 0
read(5, "\0.symtab\0.strtab\0.shstrtab\0.inte"..., 4096) = 4096
_llseek(5, 4584348, [4584348], SEEK_SET) = 0
read(5, "libart.so\0\0\0\21\r\350\370\0.symtab\0.strtab"..., 4096) = 4096
close(5) = 0
openat(AT_FDCWD, "/system/lib/.debug/libart.so", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/debug/system/lib/libart.so", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory)
clock_gettime(CLOCK_MONOTONIC, {7390, 135831818}) = 0
openat(AT_FDCWD, "/system/lib/libandroid_runtime.so", O_RDONLY|O_LARGEFILE) = 5
fstat64(5, {st_mode=0, st_size=1, ...}) = 0
mmap2(NULL, 1075276, PROT_READ, MAP_PRIVATE, 5, 0) = 0xaaada000
close(5) = 0
openat(AT_FDCWD, "/system/lib/libandroid_runtime.so", O_RDONLY|O_LARGEFILE) = 5
fstat64(5, {st_mode=0, st_size=1, ...}) = 0
read(5, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0\0\0\0\0004\0\0\0"..., 4096) = 4096
_llseek(5, 1074116, [1074116], SEEK_SET) = 0
read(5, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 4096) = 1160
_llseek(5, 1073810, [1073810], SEEK_SET) = 0
read(5, "\0.shstrtab\0.interp\0.note.android"..., 4096) = 1466
_llseek(5, 1073782, [1073782], SEEK_SET) = 0
read(5, "libandroid_runtime.so\0\0\0o\223i\206\0.sh"..., 4096) = 1494
close(5) = 0
openat(AT_FDCWD, "/system/lib/libandroid_runtime.so", O_RDONLY|O_LARGEFILE) = 5
fstat64(5, {st_mode=0, st_size=1, ...}) = 0
read(5, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0\0\0\0\0004\0\0\0"..., 4096) = 4096
_llseek(5, 1074116, [1074116], SEEK_SET) = 0
read(5, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 4096) = 1160
_llseek(5, 1073810, [1073810], SEEK_SET) = 0
read(5, "\0.shstrtab\0.interp\0.note.android"..., 4096) = 1466
_llseek(5, 1073782, [1073782], SEEK_SET) = 0
read(5, "libandroid_runtime.so\0\0\0o\223i\206\0.sh"..., 4096) = 1494
close(5) = 0
openat(AT_FDCWD, "/system/lib/.debug/libandroid_runtime.so", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/debug/system/lib/libandroid_runtime.so", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/system/bin/app_process32", O_RDONLY|O_LARGEFILE) = 5
fstat64(5, {st_mode=0, st_size=1, ...}) = 0
Click to expand...
Click to collapse
Both them lib files are present in system/lib
I don't have any knowledge of coding to be of assistance

mrfrantastic said:
So if you type "pm" in a terminal you don't get a segmentation fault?
Click to expand...
Click to collapse
Nope.

Since we only have a very small number of affected devices it is obviously difficult to extrapolate general statements. But for now(!) it seems(!) that there are models which are not affected by the fault although they match (on first glance) OP's and my phone's specs. On the other hand there are (again: for now) only devices with above mentioned serial number affected by the fault.
Since we tried different ROMS with different sources could it be kernel related? I am assuming that all ROMS at least partially share the same kernel. And if so, how do we get someone to try to fix the kernel?
The next common denominator might be either TWRP or SU...

At least Xposed is NOT affected in any way by the Segmentation fault error, so you can use it without problem.
Enviado desde mi Moto G5 mediante Tapatalk

Stuck on 2G on Pixel Experience

Hi,
I have been using this PixelExperience on redmi 3s for some time and I have been very happy with it. Recently I changed provider and I installed the new sim card roughly at the same time of the latest PixelExperience update.
I am having a minor problem but is bugging me. I used to have my main SIM card in SIM slot 1 and SD card on SIM slot 2. Now it looks like SIM 2 is my main card and on SIM 1 I can only get 2g (EDGE). For this reason if I want LTE I have to sacrifice my SD card. I have tried to "force" LTE on SIM1 but it will just not connect. I tried to reset network settings but nothing changed.
I am inclined to think that this is not related to the new network as I have tried to put it sim cards from other networks and I get the same symptom.
Could it be related to something in the latest PixelExperience update??
TIA

Hi,
still better than me, i've no data at all on both slot ... tried many things (force wcdma only, gsm only) played with APN.
I recently moved to MNVO operator and since data is not working anymore ... (tested a lot of rom in android 9 and 10). I can confirm that my new operator is using the same network as the old one I had, and it was working on it.
I tried the sim card in another phone and it works perfectly (mi 9).
It seems that the driver modem it bugged, if anyone has an idea ...
Here the logcat when I enable data (filtered on Qlms)
Spoiler: logcat
2020-12-06 00:22:47.642 2008-16629/? W/QImsService: ImsConfigImpl : Ignore VoWiFi Roaming enable/disable
2020-12-06 00:22:47.645 2008-16628/? I/QImsService: ImsSenderRxr : [0145]> REQUEST_SET_IMS_CONFIG [SUB0]
2020-12-06 00:22:47.645 2008-16628/? I/QImsService: ImsSenderRxr : REQUEST_SET_IMS_CONFIG request to ImsRadio: token 145 item:29 boolValue:false intValue:1 strValue:null errorCause:0
2020-12-06 00:22:47.651 2008-2106/? I/QImsService: ImsRadioResponse : Set config response received.
2020-12-06 00:22:47.651 2008-2106/? I/QImsService: ImsSenderRxr : [0145]< REQUEST_SET_IMS_CONFIG [SUB0]
2020-12-06 00:22:47.651 2008-2260/? I/QImsService: ImsConfigImplHandler : Message received: what = 1
2020-12-06 00:22:47.651 2008-2260/? I/QImsService: ImsConfigImpl : Notifyall
2020-12-06 00:22:47.656 2008-2008/? I/QImsService: ImsRadioUtils : buildServiceStatusInfo srvType = 3 rat = 14 enabled = 2
2020-12-06 00:22:47.656 2008-2008/? I/QImsService: ImsSenderRxr : [0146]> REQUEST_SET_SERVICE_STATUS [SUB0]
2020-12-06 00:22:47.656 2008-2008/? I/QImsService: ImsSenderRxr : REQUEST_SET_SERVICE_STATUS to ImsRadio: token -146
2020-12-06 00:22:47.656 2008-2008/? W/QImsService: ImsSenderRxr : mImsRadio V1.6 is null. invoking mImsRadio.setServiceStatus()
2020-12-06 00:22:47.658 2008-2008/? I/QImsService: ImsRadioUtils : buildServiceStatusInfo srvType = 25 rat = 14 enabled = 2
2020-12-06 00:22:47.658 2008-2008/? I/QImsService: ImsSenderRxr : [0147]> REQUEST_SET_SERVICE_STATUS [SUB0]
2020-12-06 00:22:47.658 2008-2008/? I/QImsService: ImsSenderRxr : REQUEST_SET_SERVICE_STATUS to ImsRadio: token -147
2020-12-06 00:22:47.658 2008-2008/? W/QImsService: ImsSenderRxr : mImsRadio V1.6 is null. invoking mImsRadio.setServiceStatus()
2020-12-06 00:22:47.659 2008-2008/? I/QImsService: ImsRadioUtils : buildServiceStatusInfo srvType = 0 rat = 14 enabled = 0
2020-12-06 00:22:47.659 2008-2008/? I/QImsService: ImsSenderRxr : [0148]> REQUEST_SET_SERVICE_STATUS [SUB0]
2020-12-06 00:22:47.659 2008-2008/? I/QImsService: ImsSenderRxr : REQUEST_SET_SERVICE_STATUS to ImsRadio: token -148
2020-12-06 00:22:47.659 2008-2008/? W/QImsService: ImsSenderRxr : mImsRadio V1.6 is null. invoking mImsRadio.setServiceStatus()
2020-12-06 00:22:47.660 2008-2008/? I/QImsService: ImsRadioUtils : buildServiceStatusInfo srvType = 0 rat = 19 enabled = 0
2020-12-06 00:22:47.660 2008-2008/? I/QImsService: ImsSenderRxr : [0149]> REQUEST_SET_SERVICE_STATUS [SUB0]
2020-12-06 00:22:47.660 2008-2008/? I/QImsService: ImsSenderRxr : REQUEST_SET_SERVICE_STATUS to ImsRadio: token -149
2020-12-06 00:22:47.660 2008-2008/? W/QImsService: ImsSenderRxr : mImsRadio V1.6 is null. invoking mImsRadio.setServiceStatus()
2020-12-06 00:22:47.660 2008-2106/? I/QImsService: ImsRadioResponse : SetServiceStatus response received.
2020-12-06 00:22:47.660 2008-2106/? I/QImsService: IFRequest : [0147]< REQUEST_SET_SERVICE_STATUS error: 2
2020-12-06 00:22:47.660 2008-2260/? I/QImsService: ImsConfigImplHandler : Message received: what = 2
2020-12-06 00:22:47.661 2008-2106/? I/QImsService: ImsRadioResponse : SetServiceStatus response received.
2020-12-06 00:22:47.661 2008-2106/? I/QImsService: ImsSenderRxr : [0146]< REQUEST_SET_SERVICE_STATUS [ 2 0 1][SUB0]
2020-12-06 00:22:47.661 2008-2260/? I/QImsService: ImsConfigImplHandler : Message received: what = 2
2020-12-06 00:22:47.662 2008-2008/? I/QImsService: ImsService : enableIms :: slotId=0
2020-12-06 00:22:47.662 2008-2008/? I/QImsService: ImsSenderRxr : [0150]> REQUEST_IMS_REG_STATE_CHANGE [SUB0]
2020-12-06 00:22:47.662 2008-2008/? I/QImsService: ImsSenderRxr : REQUEST_IMS_REG_STATE_CHANGE request to ImsRadio - token:150 RegState1
2020-12-06 00:22:47.678 2008-2106/? I/QImsService: ImsRadioResponse : SetServiceStatus response received.
2020-12-06 00:22:47.679 2008-2106/? I/QImsService: ImsSenderRxr : [0148]< REQUEST_SET_SERVICE_STATUS [ 1 0 0][SUB0]
2020-12-06 00:22:47.679 2008-2106/? I/QImsService: ImsRadioResponse : SetServiceStatus response received.
2020-12-06 00:22:47.679 2008-2260/? I/QImsService: ImsConfigImplHandler : Message received: what = 2
2020-12-06 00:22:47.679 2008-2106/? I/QImsService: ImsSenderRxr : [0149]< REQUEST_SET_SERVICE_STATUS [ 1 1 0][SUB0]
2020-12-06 00:22:47.679 2008-2260/? I/QImsService: ImsConfigImplHandler : Message received: what = 2
2020-12-06 00:22:47.683 2008-2106/? I/QImsService: ImsRadioResponse : Got registration change response from ImsRadio.
2020-12-06 00:22:47.683 2008-2106/? I/QImsService: ImsSenderRxr : [0150]< REQUEST_IMS_REG_STATE_CHANGE [SUB0]
2020-12-06 00:22:47.683 2008-2008/? I/QImsService: ImsServiceSubHandler : Message received: what = 9
2020-12-06 00:24:29.909 2008-2008/? E/QImsService: ImsServiceSub : [1] onSubscriptionsChanged unable to process due to SubscriptionInfo is null
2020-12-06 00:24:29.910 2008-2008/? E/QImsService: ImsConfigImpl : onSubscriptionsChanged unable to process due to SubscriptionInfo is null
2020-12-06 00:24:50.320 2008-2106/? I/QImsService: ImsRadioIndication : onServiceStatusChanged()
2020-12-06 00:24:50.320 2008-2106/? I/QImsService: ImsRadioIndication : onServiceStatusChanged_1_6()
2020-12-06 00:24:50.320 2008-2106/? I/QImsService: Class : Num of SrvUpdates = 5
2020-12-06 00:24:50.320 2008-2106/? I/QImsService: Class : networkMode = 0 status = 0 restrictCause = 0 registered = 2
2020-12-06 00:24:50.320 2008-2106/? I/QImsService: Class : RTT: copySrvStatusList rtt mode = 2
2020-12-06 00:24:50.320 2008-2106/? I/QImsService: Class : networkMode = 0 status = 0 restrictCause = 0 registered = 2
2020-12-06 00:24:50.320 2008-2106/? I/QImsService: Class : RTT: copySrvStatusList rtt mode = 2
2020-12-06 00:24:50.320 2008-2106/? I/QImsService: Class : networkMode = 0 status = 0 restrictCause = 0 registered = 2
2020-12-06 00:24:50.320 2008-2106/? I/QImsService: Class : RTT: copySrvStatusList rtt mode = 2
2020-12-06 00:24:50.320 2008-2106/? I/QImsService: Class : networkMode = 0 status = 0 restrictCause = 0 registered = 2
2020-12-06 00:24:50.320 2008-2106/? I/QImsService: Class : RTT: copySrvStatusList rtt mode = 2
2020-12-06 00:24:50.320 2008-2106/? I/QImsService: Class : networkMode = 14 status = 0 restrictCause = 0 registered = 2
2020-12-06 00:24:50.321 2008-2106/? I/QImsService: Class : RTT: copySrvStatusList rtt mode = 2
2020-12-06 00:24:50.321 2008-2106/? I/QImsService: ImsSenderRxr : [UNSL]< UNSOL_SRV_STATUS_UPDATE [[email protected], [email protected], [email protected], [email protected], [email protected]][SUB1]
2020-12-06 00:24:50.326 2008-2008/? I/QImsService: ImsServiceSubHandler : Message received: what = 4
2020-12-06 00:24:50.326 2008-2008/? I/QImsService: ImsServiceSub : [1] Received event: EVENT_SRV_STATUS_UPDATE
2020-12-06 00:24:50.326 2008-2008/? I/QImsService: ImsServiceSub : [1] type = 0 status = 0 isValid = true
2020-12-06 00:24:50.326 2008-2008/? I/QImsService: ImsServiceSub : [1] Call Type 0has num updates = 1
2020-12-06 00:24:50.326 2008-2106/? I/QImsService: ImsRadioIndication : onServiceStatusChanged()
2020-12-06 00:24:50.326 2008-2008/? I/QImsService: ImsServiceSub : [1] StatusForAccessTech networkMode = 0 registered = 2 status = 0 restrictCause = 0
2020-12-06 00:24:50.326 2008-2106/? I/QImsService: ImsRadioIndication : onServiceStatusChanged_1_6()
2020-12-06 00:24:50.326 2008-2008/? I/QImsService: ImsServiceSub : [1] type = 3 status = 0 isValid = true
2020-12-06 00:24:50.326 2008-2008/? I/QImsService: ImsServiceSub : [1] Call Type 3has num updates = 1
2020-12-06 00:24:50.326 2008-2106/? I/QImsService: Class : Num of SrvUpdates = 5
2020-12-06 00:24:50.326 2008-2106/? I/QImsService: Class : networkMode = 0 status = 0 restrictCause = 0 registered = 2
2020-12-06 00:24:50.326 2008-2106/? I/QImsService: Class : RTT: copySrvStatusList rtt mode = 2
2020-12-06 00:24:50.326 2008-2106/? I/QImsService: Class : networkMode = 0 status = 0 restrictCause = 0 registered = 2
2020-12-06 00:24:50.326 2008-2106/? I/QImsService: Class : RTT: copySrvStatusList rtt mode = 2
2020-12-06 00:24:50.326 2008-2106/? I/QImsService: Class : networkMode = 0 status = 0 restrictCause = 0 registered = 2
2020-12-06 00:24:50.326 2008-2106/? I/QImsService: Class : RTT: copySrvStatusList rtt mode = 2
2020-12-06 00:24:50.326 2008-2106/? I/QImsService: Class : networkMode = 0 status = 0 restrictCause = 0 registered = 2
2020-12-06 00:24:50.326 2008-2106/? I/QImsService: Class : RTT: copySrvStatusList rtt mode = 2
2020-12-06 00:24:50.326 2008-2106/? I/QImsService: Class : networkMode = 14 status = 0 restrictCause = 0 registered = 2
2020-12-06 00:24:50.326 2008-2106/? I/QImsService: Class : RTT: copySrvStatusList rtt mode = 2
2020-12-06 00:24:50.326 2008-2106/? I/QImsService: ImsSenderRxr : [UNSL]< UNSOL_SRV_STATUS_UPDATE [[email protected], [email protected], [email protected], [email protected], [email protected]][SUB0]
2020-12-06 00:24:50.327 2008-2008/? I/QImsService: ImsServiceSub : [1] StatusForAccessTech networkMode = 0 registered = 2 status = 0 restrictCause = 0
2020-12-06 00:24:50.327 2008-2008/? I/QImsService: ImsServiceSub : [1] type = 1 status = 0 isValid = true
2020-12-06 00:24:50.327 2008-2008/? I/QImsService: ImsServiceSub : [1] Call Type 1has num updates = 1
2020-12-06 00:24:50.327 2008-2008/? I/QImsService: ImsServiceSub : [1] StatusForAccessTech networkMode = 0 registered = 2 status = 0 restrictCause = 0
2020-12-06 00:24:50.327 2008-2008/? I/QImsService: ImsServiceSub : [1] type = 2 status = 0 isValid = true
2020-12-06 00:24:50.327 2008-2008/? I/QImsService: ImsServiceSub : [1] Call Type 2has num updates = 1
2020-12-06 00:24:50.327 2008-2008/? I/QImsService: ImsServiceSub : [1] StatusForAccessTech networkMode = 0 registered = 2 status = 0 restrictCause = 0
2020-12-06 00:24:50.327 2008-2008/? I/QImsService: ImsServiceSub : [1] type = 25 status = 0 isValid = true
2020-12-06 00:24:50.327 2008-2008/? I/QImsService: ImsServiceSub : [1] Call Type 25has num updates = 1
2020-12-06 00:24:50.327 2008-2008/? I/QImsService: ImsServiceSub : [1] StatusForAccessTech networkMode = 14 registered = 2 status = 0 restrictCause = 0
2020-12-06 00:24:50.327 2008-2008/? I/QImsService: ImsServiceSub : [1] disabledFeature = 4
2020-12-06 00:24:50.328 2008-2008/? E/QImsService: ImsServiceSub : [1] handleSrvStatusUpdate :: tracker null; not updating global VT capability
2020-12-06 00:24:50.329 2008-2008/? I/QImsService: ImsServiceSubHandler : Message received: what = 4
2020-12-06 00:24:50.329 2008-2008/? I/QImsService: ImsServiceSub : [0] Received event: EVENT_SRV_STATUS_UPDATE
2020-12-06 00:24:50.329 2008-2008/? I/QImsService: ImsServiceSub : [0] type = 0 status = 0 isValid = true
2020-12-06 00:24:50.329 2008-2008/? I/QImsService: ImsServiceSub : [0] Call Type 0has num updates = 1
2020-12-06 00:24:50.329 2008-2008/? I/QImsService: ImsServiceSub : [0] StatusForAccessTech networkMode = 0 registered = 2 status = 0 restrictCause = 0
2020-12-06 00:24:50.329 2008-2008/? I/QImsService: ImsServiceSub : [0] type = 3 status = 0 isValid = true
2020-12-06 00:24:50.329 2008-2008/? I/QImsService: ImsServiceSub : [0] Call Type 3has num updates = 1
2020-12-06 00:24:50.329 2008-2008/? I/QImsService: ImsServiceSub : [0] StatusForAccessTech networkMode = 0 registered = 2 status = 0 restrictCause = 0
2020-12-06 00:24:50.329 2008-2008/? I/QImsService: ImsServiceSub : [0] type = 1 status = 0 isValid = true
2020-12-06 00:24:50.329 2008-2008/? I/QImsService: ImsServiceSub : [0] Call Type 1has num updates = 1
2020-12-06 00:24:50.329 2008-2008/? I/QImsService: ImsServiceSub : [0] StatusForAccessTech networkMode = 0 registered = 2 status = 0 restrictCause = 0
2020-12-06 00:24:50.329 2008-2008/? I/QImsService: ImsServiceSub : [0] type = 2 status = 0 isValid = true
2020-12-06 00:24:50.329 2008-2008/? I/QImsService: ImsServiceSub : [0] Call Type 2has num updates = 1
2020-12-06 00:24:50.329 2008-2008/? I/QImsService: ImsServiceSub : [0] StatusForAccessTech networkMode = 0 registered = 2 status = 0 restrictCause = 0
2020-12-06 00:24:50.329 2008-2008/? I/QImsService: ImsServiceSub : [0] type = 25 status = 0 isValid = true
2020-12-06 00:24:50.329 2008-2008/? I/QImsService: ImsServiceSub : [0] Call Type 25has num updates = 1
2020-12-06 00:24:50.329 2008-2008/? I/QImsService: ImsServiceSub : [0] StatusForAccessTech networkMode = 14 registered = 2 status = 0 restrictCause = 0
2020-12-06 00:24:50.329 2008-2008/? I/QImsService: ImsServiceSub : [0] disabledFeature = 4
2020-12-06 00:24:50.329 2008-2008/? I/QImsService: ImsServiceClassTracker : updateFeatureCapabilities video false voice false