[DEV] miniCM10 debug only thread (shakira, robyn and mimmi) 03/06/13 - XPERIA X8 Android Development

[DEV] miniCM10 debug only thread (shakira, robyn and mimmi)
there is 3 thread for miniCM10, each device specific.
things i say in one thread is also applicable to others
for debugging purpose, i need this only thread for the 3 devices to centralize the data
this thread is NOT for asking or requesting anything, it is there for providing test results !
​
post #2 : wifi and tiwlan.ini
post #3 : various build.prop tweaks
post #4 : ?
post #135 : pilu's small tutorial about getting more space in /data
post #82 : old things, archiving
>>>here is a list of some useful commands to know how does your device run<<< (at the end of the post)
to improve miniCM10, you could :
post results after following protocols,
[*]help me to set up test new protocols,
[*]give advices about them
[*]suggest things to investigate IF you can prove it worths to

---

#2 : wifi and tiwlan.ini
The aim of this one is testing two or more tiwlan.ini and observing modification in wifi behavior
default tiwlan.ini :
Code:
# tiwlan-ayame-gen.ini
# Note: The letters in this file are NOT case sensitive.
#=========================== Radio parameters - Start ========================
#--------------------- General Radio Parameters ------------------------
TXBiPFEMAutoDetect = 0 # Unit: Options (0: Manual Mode; 1: Automatic mode), Format: Unsigned, Source: Customer
TXBiPFEMManufacturer = 1 # Unit: Options(Bit 0 - Manufacturer (0: FEM0-RFMD; 1: FEM1-TQS),
# Bit 4..7: Version number ),
# Format: Unsigned, Source: Customer
RefClk = 4 # Unit: Options 5'bXX000 : Bit 0,1,2 - (0: 19.2MHz; 1: 26MHz; 2: 38.4MHz (Default); 3: 52MHz; 4: 38.4MHz XTAL) ;
# 5'bX0XXX : Bit 3 - CLK_REQ type; 0 = wired-OR (Default) , 1= push-pull
# 5'b0XXXX : Bit 4 - CLK_REQ polarity; 0 = Normal (Default) , 1=Inverted, Format: Unsigned, Source: Customer
SettlingTime = 5 # Unit: ms (range 0-15), Format: Unsigned, Source: Customer
ClockValidOnWakeup = 0 # Unit: Options (0: Reference clock not valid; 1: Reference clock is valid and stable), Format: Unsigned, Source: Customer
DC2DCMode = 0 # Unit: Options (Bit0: DC2DC mode (0: btSPI is not used;1: btSPI used mux DC2DC to BT_FUNC2),
# Bit1: Level shifter support (0: No LS, 1: With LS) )
# Format: Unsigned, Source: Customer
Single_Dual_Band_Solution = 0 # Unit: Options (0: Single band. 2.4GHz only; 1: Dual band = 2.4GHz and 5GHz solution), Format: Unsigned, Source: Customer
Settings = 65 # Unit: Options (Bit0: NBI (0: Off; 1: On), Bit1: Telec channel 14 (0: Off; 1: On),
SRState = 00 # Length: 1; Unit: Options (0: Disabled, 1: Enabled); Format: Decimal; Source: TI; Comment: Smart Reflax (proprietary mechanism of TI that identify the # Bit2: FEM0-LB, Bit3: FEM0-HB, Bit4: FEM1-LB, Bit5: FEM1-HB - TX BiP load (0: Internal; 1: External),
# Bit6: LPD Low band, Bit7: LPD High band
# Format: Unsigned, Source: Customer
SRF1 = 07,03,18,10,05,fb,f0,e8,00,00,00,00,00,00,0f,3f # Unit: SRF1 values, Format: Signed, Source: TI
SRF2 = 07,03,18,10,05,f6,f0,e8,00,00,00,00,00,00,00,00 # Unit: SRF2 values, Format: Signed, Source: TI
SRF3 = 07,03,18,10,05,fb,f0,e8,00,00,00,00,00,00,00,00 # Unit: SRF3 values, Format: Signed, Source: TI
RxTraceInsertionLoss_2_4G = 0 # Unit: 1/8dB, Format: Unsigned, Source: Customer
TXTraceLoss_2_4G = 24 # Unit: 1/8dB, Format: Unsigned, Source: Customer
RxRssiAndProcessCompensation_2_4G = ec,f6,00,0c,18,f8,fc,00,08,10,f0,f8,00,0a,14 # Unit: 1/8dB, Format: Signed, Source: TI
#-------------------- Radio parameters for TQS_S_2.6 ---------------
# (for Single bend 2.4G parameters FEM1 (TQS 2.5) HDK20)
FEM1_TXBiPReferencePDvoltage_2_4G = 0177 # Unit: 1mV, Format: Unsigned, Source: TI
FEM1_TxBiPReferencePower_2_4G = 80 # Unit: 1/8dB, Format: Signed, Source: TI
FEM1_TxBiPOffsetdB_2_4G = 0 # Unit: 1/8dB, Format: Signed, Source: Customer
FEM1_TxPerRatePowerLimits_2_4G_Normal = 20,22,22,22,22,29 # Unit: 1/2dB, Format: Signed, Source: Customer
FEM1_TxPerRatePowerLimits_2_4G_Degraded = 1d,1d,1d,1d,1d,28 # Unit: 1/2dB, Format: Signed, Source: Customer
FEM1_TxPerRatePowerLimits_2_4G_Extreme = 19,19,19,19,19,25 # Unit: 1/2dB, Format: Signed, Source: Customer
FEM1_DegradedLowToNormalThr_2_4G = 30 # Unit: 1/10 volts, Format: Unsigned, Source: TI
FEM1_NormalToDegradedHighThr_2_4G = 45 # Unit: 1/10 volts, Format: Unsigned, Source: TI
FEM1_TxPerChannelPowerLimits_2_4G_11b = 50,50,50,50,50,50,50,50,50,50,50,50,50,50 # Unit: 1/2dB, Format: Signed, Source: Customer
FEM1_TxPerChannelPowerLimits_2_4G_OFDM = 50,50,50,50,50,50,50,50,50,50,50,50,50,50 # Unit: 1/2dB, Format: Signed, Source: Customer
FEM1_TxPDVsRateOffsets_2_4G = 01,02,02,02,02,00 # Unit: 1/8dB, Format: Signed, Source: TI
FEM1_TxIbiasTable_2_4G = 11,11,15,11,15,0f # Unit: Codeword, Format: Unsigned, Source: TI/SEMC
FEM1_RxFemInsertionLoss_2_4G = 14 # Unit: 1/8dB, Format: Unsigned, Source: TI
# ---------------------------------------------------------------------
#-------------------- Radio parameters for RFMD_S_3.0 ---------------
#FEM1_TXBiPReferencePDvoltage_2_4G = 356 # Unit: 1mV, Format: Unsigned, Source: TI
#FEM1_TxBiPReferencePower_2_4G = 128 # Unit: 1/8dB, Format: Signed, Source: TI
#FEM1_TxBiPOffsetdB_2_4G = 0 # Unit: 1/8dB, Format: Signed, Source: Customer
#FEM1_TxPerRatePowerLimits_2_4G_Normal = 50,50,50,50,50,50 # Unit: 1/2dB, Format: Signed, Source: Customer
#FEM1_TxPerRatePowerLimits_2_4G_Degraded = 50,50,50,50,50,50 # Unit: 1/2dB, Format: Signed, Source: Customer
#FEM1_TxPerRatePowerLimits_2_4G_Extreme = 50,50,50,50,50,50 # Unit: 1/2dB, Format: Signed, Source: Customer
#FEM1_DegradedLowToNormalThr_2_4G = 30 # Unit: 1/10 volts, Format: Unsigned, Source: TI
#FEM1_NormalToDegradedHighThr_2_4G = 45 # Unit: 1/10 volts, Format: Unsigned, Source: TI
#FEM1_TxPerChannelPowerLimits_2_4G_11b = 50,50,50,50,50,50,50,50,50,50,50,50,50,50 # Unit: 1/2dB, Format: Signed, Source: Customer
#FEM1_TxPerChannelPowerLimits_2_4G_OFDM = 50,50,50,50,50,50,50,50,50,50,50,50,50,50 # Unit: 1/2dB, Format: Signed, Source: Customer
#FEM1_TxPDVsRateOffsets_2_4G = 01,02,02,02,02,00 # Unit: 1/8dB, Format: Signed, Source: TI
#FEM1_TxIbiasTable_2_4G = 15,15,1a,1f,1f,2f # Unit: Codeword, Format: Unsigned, Source: TI
#FEM1_RxFemInsertionLoss_2_4G = 16 # Unit: 1/8dB, Format: Unsigned, Source: TI
# ---------------------------------------------------------------------
#-------------------- Radio parameters for TQS_S_2.5 ---------------
#FEM1_TXBiPReferencePDvoltage_2_4G = 375 # Unit: 1mV, Format: Unsigned, Source: TI
#FEM1_TxBiPReferencePower_2_4G = 128 # Unit: 1/8dB, Format: Signed, Source: TI
#FEM1_TxBiPOffsetdB_2_4G = 0 # Unit: 1/8dB, Format: Signed, Source: Customer
#FEM1_TxPerRatePowerLimits_2_4G_Normal = 1d,1f,22,26,28,29 # Unit: 1/2dB, Format: Signed, Source: Customer
#FEM1_TxPerRatePowerLimits_2_4G_Degraded = 1a,1f,22,24,26,28 # Unit: 1/2dB, Format: Signed, Source: Customer
#FEM1_TxPerRatePowerLimits_2_4G_Extreme = 16,1d,1e,20,24,25 # Unit: 1/2dB, Format: Signed, Source: Customer
#FEM1_DegradedLowToNormalThr_2_4G = 30 # Unit: 1/10 volts, Format: Unsigned, Source: TI
#FEM1_NormalToDegradedHighThr_2_4G = 45 # Unit: 1/10 volts, Format: Unsigned, Source: TI
#FEM1_TxPerChannelPowerLimits_2_4G_11b = 50,50,50,50,50,50,50,50,50,50,50,50,50,50 # Unit: 1/2dB, Format: Signed, Source: Customer
#FEM1_TxPerChannelPowerLimits_2_4G_OFDM = 50,50,50,50,50,50,50,50,50,50,50,50,50,50 # Unit: 1/2dB, Format: Signed, Source: Customer
#FEM1_TxPDVsRateOffsets_2_4G = 01,02,02,02,02,00 # Unit: 1/8dB, Format: Signed, Source: TI
#FEM1_TxIbiasTable_2_4G = 15,15,15,11,15,15 # Unit: Codeword, Format: Unsigned, Source: TI/SEMC
#FEM1_RxFemInsertionLoss_2_4G = 14 # Unit: 1/8dB, Format: Unsigned, Source: TI
# ---------------------------------------------------------------------
#=========================== Radio parameters - End ==========================
the one i use is different in one way :
Code:
FEM1_TXBiPReferencePDvoltage_2_4G = 375 # Unit: 1mV, Format: Unsigned, Source: TI
FEM1_TxBiPReferencePower_2_4G = 128 # Unit: 1/8dB, Format: Signed, Source: TI
so i changed :
FEM1_TXBiPReferencePDvoltage_2_4G = 0177 # Unit: 1mV, Format: Unsigned, Source: TI
FEM1_TxBiPReferencePower_2_4G = 80 # Unit: 1/8dB, Format: Signed, Source: TI​
to
FEM1_TXBiPReferencePDvoltage_2_4G = 375 # Unit: 1mV, Format: Unsigned, Source: TI
FEM1_TxBiPReferencePower_2_4G = 128 # Unit: 1/8dB, Format: Signed, Source: TI​(this second code is the one there use to be in older tiwlan.ini, used before
The idea is that you try both and see if you experience any changes in wifi behavior ...

---

#3 various build.prop tweaks
here are some "tweaks" that xelyt posted :
If you want to test the following tweaks remember to make a backup of your build.prop first. Any feedback will be greatly appreciated.
xelyt said:
Original post here
Hey guys
I'm currently testing two build.prop tweaks that should make things even faster.
The first one is a heapsize optimization:
Code:
dalvik.vm.heapsize=32m
-------------> this exist in build.prop so you don't have to add it again
Code:
dalvik.vm.heapstartsize=5m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=2m
The second one is a way to set a limit for background processes without having to tick it in developer setting every boot
Code:
sys.mem.max_hidden_apps=
I found out that the most used values are: 15 (should be the default value if i'm not wrong), 10, 5, 4, 3
I tried with sys.mem.max_hidden_apps=10 first and it seems to make a noticeable difference in term of smoothness. Amount of free RAM is also increased to about 60mb.
Click to expand...
Click to collapse
and here is another one :
changing dalvik.vm.dexopt-flags
xelyt said:
According to this the dalvik.vm.verify_bytecode property has been superceded by dalvik.vm.dexopt-flags so it doesn't disable bytecode verification anymore. If you want to disable bytecode verification you have to change dalvik.vm.dexopt-flags to v=n,o=v but i don't reccomend this because it could make some apps not working properly. As for the tweaked build.prop i'm sure that you also noticed that i changed
Code:
dalvik.vm.dexopt-flags=m=y
to
Code:
dalvik.vm.dexopt-flags=v=a,o=v,m=y,u=y
(which it's like verify=all, dexopt=verified, registermaps=yes, uniprocessor=yes) in order to build a more optimized dalvik cache
For more info take a look here
Click to expand...
Click to collapse
to apply the new settings, reboot to recovery and wipe cache and dalvik-cache
enjoy!

---

#4
reserved again

---

#5
a last one, in case of

---

This will fix bugs .. good idea ..

---

so i'll try to do my best to find bugs

---

FYI
I have followed the instructions on installation of the ROM to the letter(I can read, yay).
I have only installed the ROM once.
----------------------------------------------------------------------------------------------------
Bug or not..
I have my phone on 3G, a few calls and some internet usage gives approx 50h of battery time -> 10% = 5h
Sometimes when having phone idle it has consumed 20% of the battery during one hour.
This is directly after removing the device from charger.
Checking what has used the power is screen and android system as always, nothing else.
Restart or charge the device resolves the issue.

---

Hey [email protected], glad to see the thread, hopefully we will be able to find something useful.
Remember me talking about the lockscreen bug? I mean if you set
Settings/Security/Show widgets before unlock ON, you can never go back, if you untick it, the widgets will still be displayed, even reboot doesn´t change it. This is not a big issue though, I´m just talking about it because of my suspicion that it might have to do something with the black screen bug. Because five days ago I did a new install from scratch /no restoring at all, wanted to see how default settings work again/ and believe me or not, since then I haven´t seen the black screen at all. Not once. And what was the difference from the previous install? I haven´t touched the above mentioned widgets setting. Just set up my screen lock /using pattern but that´s irrelevant/ and no other changes on security page.

---

mms and qcomuiccstack property in build.prop
i am still looking for data for this :
http://forum.xda-developers.com/showpost.php?p=29018876&postcount=173 --> better look to the #2 post of the current thread, the link was to show i also asked this for miniCM9
thx

---

post #2 updated for more precision, please follow the protocol, i need a lot of data to conclude anything
only then, we will focus a little more on the "hard to wake up" screen bug that is partially solved for next released build

---

No problem here with or without qcomuiccstack
Orange Slovakia (MNO) (mimmi)

---

matmutant said:
post #2 updated for more precision, please follow the protocol, i need a lot of data to conclude anything
only then, we will focus a little more on the "hard to wake up" screen bug that is partially solved for next released build
Click to expand...
Click to collapse
yeah, its hard to wake up device when we in ICS or JB with 600 Mhz
even Xperia 2011 with 1 Ghz cpu have this problem in GB and ICS
I'm already test it with stock rom
it's awesome our mini have Froyo, GB, ICS and JB with only 600 Mhz
just need to wait and gonna post any bug
XD
sorry, out of topic
i just want to share and want to people know, our developers it' s awesome
XD

---

Matmutant can this help in performance? http://forum.xda-developers.com/showthread.php?t=1877183

---

ElmirBuljubasic said:
Matmutant can this help in performance? http://forum.xda-developers.com/showthread.php?t=1877183
Click to expand...
Click to collapse
it might help
please try it, and report back, if it works i'll post something about it here and will ask more people to test it (i can't try it myself atm...)
but doesn't it have the same goal as "force GPU2D rendering" and "disable hardware overlap"? in settings/dev options ?

---

matmutant said:
but doesn't it have the same goal as "force GPU2D rendering" and "disable hardware overlap"? in settings/dev options ?
Click to expand...
Click to collapse
Yeah, exactly, I think we have it already. Maybe dev could explain to us some more.
Note: disable HW overlays setting doesn´t survive reboot

---

matmutant said:
it might help
please try it, and report back, if it works i'll post something about it here and will ask more people to test it (i can't try it myself atm...)
but doesn't it have the same goal as "force GPU2D rendering" and "disable hardware overlap"? in settings/dev options ?
Click to expand...
Click to collapse
Im going to test later..i'll report the battery life and performance tomorrow
Sent from my E15i using xda app-developers app

---

My network is Vodafone P (Portugal) and i can confirm that MMS is working fine for me with both settings. Receiving MMS although has always been an issue for me even on stock Roms, the only thing that always worked for me is disabling "MMS auto-retrieve", but i'm certain that this problem is not Rom-related.
matmutant said:
it might help
please try it, and report back, if it works i'll post something about it here and will ask more people to test it (i can't try it myself atm...)
but doesn't it have the same goal as "force GPU2D rendering" and "disable hardware overlap"? in settings/dev options ?
Click to expand...
Click to collapse
From what i read on that thread, it looks like the purpose is the same, yes. I turned on "force GPU2D rendering" yesterday and so far it looks like it improves performance overall.

---

JBolho said:
My network is Vodafone P (Portugal) and i can confirm that MMS is working fine for me with both settings.
Click to expand...
Click to collapse
ok thx
which device?
and is vodafone P a MNO or MVNO ?

---

matmutant said:
ok thx
which device?
and is vodafone P a MNO or MVNO ?
Click to expand...
Click to collapse
Sorry, my fault for forgetting that info
Vodafone P is a MNO, my device is a X8 (shakira)