Does changing SPL/ROM affect coverage?
sorry but its a simple question but i cant find any answer in the forums for it, does anyone know this??
Perhaps yes, perhaps no.
I'm not sure exactly which threads I've seen it in, but I've seen a couple complaints about how the reception became terrible after updated the rom or the spl. I've also read threads which claimed the opposite. To be honest with you, I'm pretty sure it might be 90% perception, and 10% something goes wrong every now and again.
What I mean by that is, sometimes people see it as being faster, better, or slower and worse, because they're full of expectations. That or their opinions have become influenced by other posts.
Technically speaking, unless the radio is change in the phone, it shouldn't make a difference either way. There are, however, situatuations where certain radios don't play well with different carriers and such.
You'll just have to give things a try and see where you go from there. Before doing anything, however, I'd recommend backing up your current rom. You can always go back to square one, that way.
Caid.
444
Nope, SPL shouldn't make any difference. What can make a difference is the Radio firmware, and the ROM you're using (more accurately, the radio interface libraries you're using), though RIL shouldn't make that difference either, unless you use old libraries with newer radio firmware or something like that...
yah the RIL doesn't really make difference for calls and data but for GPS the correct RIL library is key
Changing ROM can affect the data throughput, have a look at the file init.rc :
Most ROM's :
Code:
# Define TCP buffer sizes for various networks
# ReadMin, ReadInitial, ReadMax, WriteMin, WriteInitial, WriteMax,
setprop net.tcp.buffersize.default 4096,87380,110208,4096,16384,110208
setprop net.tcp.buffersize.wifi 4095,87380,110208,4096,16384,110208
setprop net.tcp.buffersize.umts 4094,87380,110208,4096,16384,110208
setprop net.tcp.buffersize.edge 4096,87380,110208,4096,16384,110208
setprop net.tcp.buffersize.gprs 4096,87380,110208,4096,16384,110208
Vodafone ROM :
Code:
# Define TCP buffer sizes for various networks
# ReadMin, ReadInitial, ReadMax, WriteMin, WriteInitial, WriteMax,
setprop net.tcp.buffersize.default 4096,87380,110208,4096,16384,110208
setprop net.tcp.buffersize.wifi 4095,87380,110208,4096,16384,110208
setprop net.tcp.buffersize.umts 4094,87380,110208,4096,16384,110208
setprop net.tcp.buffersize.edge 4093,26280,35040,4096,16384,35040
setprop net.tcp.buffersize.gprs 4092,8760,11680,4096,8760,11680
As you can see the edge and gprs TCP buffer sizes differ, this does change the data throughput depending on what your network supports...
Related
Im a new nexus s owner, and produ of it. i did notice that my phone wouldnt switch from umts to hspa during a large data load (heavy browsing, youtube, speedtest).
Im running the latest nightly (cm7 36 i think) and the awesome vmax bionix kernel (i miss linda the robotic voice from my vibrant days, cmon team whiskey bring her back man!)
Anyways, i decided to take a peek at the build.prop file and i noticed it was missing a few things.
I added a few things, and although your mileage may vary; i was finally able to hit 4-5mb download speeds about 60% of the time with a beastly 2mb upload speed. before this mod i was hitting 1.5-2.2mb download and about 600-800mb upload.
just
adb pull /system/build.prop
open the build file with a text editor and add these lined of code:
(just copy and paste)
ro.ril.hsxpa=2
ro.ril.gprsclass=12
ro.ril.hep=1
ro.ril.enable.dtm=1
ro.ril.hsdpa.category=8
ro.ril.enable.a53=1
ro.ril.enable.3g.prefix=1
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
ro.ril.hsupa.category=6
Then save the file. Type in the following two lines:
adb remount (hit enter)
adb push build.prop /system/build.prop
this also fixed the bloody crashing market too btw!!!!!
go ahead and reboot. i had to reboot two times btw, dunno why but it didnt work right at first.
please go ahead and post your before and after results!
MOD; if this is posted in the wrong section please accept my apologize and feel free to move into another section; thnx
ima try it now
Stock
Hi. Would this work on Stock rom do you think? Regards Andy
murdoch1 said:
Hi. Would this work on Stock rom do you think? Regards Andy
Click to expand...
Click to collapse
Honestly I don't know. Pull the build.prop. if it's missing these values then go for it. Plz post before and after!
Testing now also. Used root explorer to change not at computer to push at the moment to push
hehehe... that setup made my data speed worse. maxed out at 800kbps
i deleted all but the first two lines, then changed the second line to..
ro.ril.hsxpa=2
ro.ril.gprsclass=10
Click to expand...
Click to collapse
and then data speed was improved
These added lines where in the original cm7 alpha build.prop. i have a little speed increase with 3 & 12
jerrycycle said:
These added lines where in the original cm7 alpha build.prop. i have a little speed increase with 3 & 12
Click to expand...
Click to collapse
I heard, sadly they're gone now
Tried gprs 10 but got slower speeds. Went back to 12
I just tried the OP's settings on my Nexus One and they did make a difference. I'm usually around 1.x down but I just pulled 2.5-2.7 mbps in multiple tests.
Up speeds are a bit faster but not by much.
Using CM7 nightly build 38.
Thanks for this... Could someone please explain what the different settings mean...I am having this issue where sometimes (even though I have full reception) when people phone it goes straight through to voicemail and i have a feeling its to do with the internet on the phone, so perhaps fiddling with the above settings may help solve my problem...
Thanks in advance
I also changed the second line back to =10 not 12. I also left all the other lines of text. Speed has gone from 1.5 down and 648 up to 4.5 down and 2.5 up. Thanx a bunch.
Sent from my Nexus S using XDA App
Holy crap I'm now getting (in average) 3.5 down whereas I used to get 2.5. Thanks!
I added the first 2 lines of text.
Changed the 12 to 10.
Went from 1.8 to 2.5 down ( average) Up went from 1.5 to 2.5 ( Average)
Top speed went from 2mbps to 3 down.
now trying the config.
ro.ril.hsxpa=2
ro.ril.gprsclass=12
Wow! 3.6 mbps down!
Average around 3 down
up stayed around the same as before. topping out at 2.5.
is there a specific spot I have to put this in? or can I just put it at the very end?
edit: I put it at the end and it worked. was averaging 3.4 down and 1.75 up before. I'm still getting the same upload speeds but that doesn't really bother me. I am however getting about a 4.5 average for download now! thanks for the tip! im on stock 2.3.2 by the way.
Sent from my Nexus S using XDA App
seems like its working, will have to test for a couple more days but its looking good so far.
why is this in Q&A? not sure. thanks for the bump
Is there an explanation somewhere (even link to the source?) about these parameters?
I am constantly being 3g disconnected but I don't remember that happening to my previous phone (HTC Magic) with the same provider. Maybe I need to pull out both build.prop and compare.
ykphuah said:
Is there an explanation somewhere (even link to the source?) about these parameters?
Click to expand...
Click to collapse
I found quite a bit of threads with just a quick google search. This seems to be the most specific/thorough, from the cyanogen forums. What's interesting is that the thread there says the guy found it on xda, but no link, and I didn't see it here, but I didn't look that hard:
There are many ro.ril parameters which I found from /system/lib/libhtc_ril.so:
ro.ril.a53.%s (gprs encryption algorithm)
ro.ril.ecc.%s
ro.ril.def.agps.mode.%s (network assisted gps)
ro.ril.def.agps.feature.%s (network assisted gps)
ro.ril.def.agps.mode (network assisted gps)
ro.ril.def.agps.feature (network assisted gps)
ro.ril.oem.ecclist (emergency call codes)
ro.ril.oem.nosim.ecclist (emergency call codes)
ro.ril.gprsclass (http://www.cellular-...g_schemes.shtml)
ro.ril.hsdpa.category
#ro.ril.hsdpa.category :
# Cat 1 = 1.2 Mbit/s
# Cat 2 = 1.2 Mbit/s
# Cat 3 = 1.8 Mbit/s
# Cat 4 = 1.8 Mbit/s
# Cat 5 = 3.6 Mbit/s
# Cat 6 = 3.6 Mbit/s
# Cat 7 = 7.2 Mbit/s
# Cat 8 = 7.2 Mbit/s
# Cat 9 = 10.1 Mbit/s
# Cat 10 = 14.0 Mbit/s
# Cat 11 = 0.9 Mbit/s
# Cat 12 = 1.8 Mbit/s
# Cat 13 = 17.6 Mbit/s
# Cat 14 = 21.1 Mbit/s
# Cat 15 = 23.4 Mbit/s
# Cat 16 = 27.9 Mbit/s
# Cat 19 = 35.3 Mbit/s
# Cat 20 = 42.2 Mbit/s
# Cat 21 = 23.4 Mbit/s
# Cat 22 = 27.9 Mbit/s
# Cat 23 = 35.3 Mbit/s
# Cat 24 = 42.2 Mbit/s
# Cat 25 = 46.8 Mbit/s
# Cat 26 = 55.9 Mbit/s
# Cat 27 = 70.6 Mbit/s
# Cat 28 = 84.4 Mbit/s
ro.ril.hsupa.category
#ro.ril.hsupa.category :
# Cat 1 = 0.73 Mbit/s
# Cat 2 = 1.46 Mbit/s
# Cat 3 = 1.46 Mbit/s
# Cat 4 = 2.93 Mbit/s
# Cat 5 = 2.00 Mbit/s
# Cat 6 = 5.76 Mbit/s
# Cat 7 = 11.5 Mbit/s
ro.ril.hsxpa
ro.ril.enable.nitz (network informed time zone)
ro.ril.enable.network_identify
ro.ril.enable.dtm (Dual Transfer Mode)(ro.ril.enable.dtm : Only set this to 1 if your network allows simultaneous transfer of Circuit switched (CS) voice and Packet switched (PS) data over the same radio channel (ARFCN).
qos (quality of service)
ro.ril.qos.maxpdps
ro.ril.qos.traffic.class
ro.ril.qos.max.ul
ro.ril.qos.max.dl
ro.ril.qos.guarantee.ul
ro.ril.qos.guarantee.dl
ro.ril.qos.delivery.order
ro.ril.qos.max.sdu
ro.ril.qos.delivery.err.sdu
ro.ril.qos.transfer.delay
ro.ril.qos.traffic.priority
ro.ril.always.laccid
ro.ril.fast.dormancy.rule
ro.ril.fd.scron.timeout
ro.ril.fd.scroff.timeout
ro.ril.fast.dormancy.plmn
ro.ril.enable.3g.prefix (=1 shows "3g" on lock screen next to network name, =0 does not)
ro.ril.3g.long.name
ro.ril.htcmaskw1.bitmask
ro.ril.htcmaskw1
ro.ril.enable.homezone
ro.ril.enable.vt
ro.ril.enable.regucid
ro.ril.enable.hsdpaind
ro.ril.enable.a52
ro.ril.enable.a53
ro.ril.enable.dcm.feature
ro.ril.enhance.htcdis
ro.ril.enable.tim.feature
ro.ril.enable.korea.stk (Korean Sim Tool Kit)
ro.ril.enable.hsupaind
ro.ril.enable.gea3 (gsm security algorithm)
ro.ril.enable.managed.roaming
ro.ril.enable.enhance.search
ro.ril.disable.mcc.filter
ro.ril.search.first.pnn
ro.ril.enable.ncell.ind (neighboring cell)
ro.ril.enable.enhance.nws
ro.ril.radio.svn
ro.ril.wp.feature
ro.ril.emc.mode
ro.ril.ucsq.mode
ro.ril.disable.power.collapse (said to be an ultra-low power state when phone is in idle, saving battery) (so does =1 mean "yes, please disable the power collapse mode", and =0 mean "oh, please leave power collapse mode on")
ro.ril.enable.cnap (Caller Name Presentation)
I would like to compile a list of what these all mean, I know what a few are (ecc=emergency calling codes)(agps=assisted gps), but some are just impossible to search/find meanings for. If anyone knows of a list of meanings for these, please post it. Otherwise, throw in your answers, and i'll add it tho this list.
Also, the numerical options one can use next to each, ie., 0=off, 1=on, and so forth.
Click to expand...
Click to collapse
Im tried this running on the stock 3.2.3 never modified. I did see a bump from about 2 to 5 down but only for the fist 2 or 3 min or so because the internet just stopped working and the phone would freez on me. i copied the original file back and the phone worked perfect again but i went back to about 2 down. i then tried changing the 2nd line from 12 to 10 and the down speed jumped from 2 to about 4 but again only for the first 2 or 3 min and the phone started freezing again... the upload speed didn't go over 200mb on either by the way... i followed the steps one by one and did everything right... has anyone else had this problem and if yes have you found a fix???
I tried the ro.ril.gprsclass=10 and 12 and I don't really notice any difference. I think reception sucks in general in a 30+ floor building at work and when I'm home, I seem to be in a crappy reception area too. My reception dbm is usually -90 to -97 and ASU 8-10. I never really see my UMTS change to HSDPA even after the change.
didnt not work for me only thing happen was that i lost the signal
hi! I was very convinced of the fact that the q is not able to do edge.
Now I am curious about the download/upload-speed one can expect from gprs. If I do a speed test on 2g only (phone info shows 1:gprs) I receive approximately 200 kbps down and around 100-130kbps up. Ping is around 200ms.
According to some internet research the speeds stated above are way to good for gprs only. So may be one is able to verify/or decline my guesses.
What are the possible/average edge speeds and what may one expect from real gprs speeds.
Are those speeds still correct?
http://www.elektronik-kompendium.de/sites/kom/0910141.htm
THX for help!
Sent from my awesome XT897
kecksk0enig said:
hi! I was very convinced of the fact that the q is not able to do edge.
Now I am curious about the download/upload-speed one can expect from gprs. If I do a speed test on 2g only (phone info shows 1:gprs) I receive approximately 200 kbps down and around 100-130kbps up. Ping is around 200ms.
According to some internet research the speeds stated above are way to good for gprs only. So may be one is able to verify/or decline my guesses.
What are the possible/average edge speeds and what may one expect from real gprs speeds.
Are those speeds still correct?
http://www.elektronik-kompendium.de/sites/kom/0910141.htm
THX for help!
Sent from my awesome XT897
Click to expand...
Click to collapse
According to QXDM diagnostic information I observed, the Photon Q modem is using MCS (EDGE Modulation and Coding Schemes) all the way up to MCS-9, while the RIL still reports only GPRS connection.
So the Photon Q actually does EDGE. The only issue is that the RIL is not reporting it. RIL signals GPRS technology (1) while EDGE (2) is in use.
In practice, the limiting factor therefore is just the small size of buffers defined by net.tcp.buffersize.gprs property that are in use when net.tcp.buffersize.edge should be used instead.
So I recommend to set the net.tcp.buffersize.gprs property to the net.tcp.buffersize.edge values to enjoy the full advantage of EDGE speed.
kabaldan said:
...
So I recommend to set the net.tcp.buffersize.gprs property to the net.tcp.buffersize.edge values to enjoy the full advantage of EDGE speed.
Click to expand...
Click to collapse
The for the fast feedback, will you describe how to do that? Is it a build.prop? Will it be included in ongoing cm10 mod?
Sent from my awesome XT897
kecksk0enig said:
The for the fast feedback, will you describe how to do that? Is it a build.prop? Will it be included in ongoing cm10 mod?
Sent from my awesome XT897
Click to expand...
Click to collapse
Assuming I have not misunderstood kabaldan...
You need a rooted system to apply properties. You can get current buffer values (adb shell or su in Terminal)
GPRS:
Code:
getprop net.tcp.buffersize.gprs
EDGE:
Code:
getprop net.tcp.buffersize.edge
To set them:
Code:
setprop net.tcp.buffersize.gprs $(getprop net.tcp.buffersize.edge)
or if that fails
Code:
setprop net.tcp.buffersize.gprs `getprop net.tcp.buffersize.edge`
but it will not survive a reboot. So you should get edge values with getprop and hardcode it as a comma separated sequence into /system/build.prop
e.g.
Code:
su
mount -o remount,rw /system
cp /system/build.prop /system/build.prop.backup
echo net.tcp.buffersize.gprs=$(getprop net.tcp.buffersize.edge) >> /system/build.prop
reboot
The ">>" in the above command is very important!
get/setprop is a part of toolbox which is included in stock rom as well so I'd expect it to work on rooted stock rom (I can't verify as I'm using CM10).
I could notice in *#*#4636#*#* (called "Test", if I remember correctly it was called "Testing phone" in ASA14)
that it changed sometimes to EDGE after disabling the phone (on ASA14). Only for a moment, because the
phone was being disabled. It didn't stay EDGE on reenabling the phone.
I had no connection (because of wrong APN, wasn't aware of) and so I tried different things in "Test" and noticed it.
If like me after installing Lollipop you're experiencing the GPS going nut, a bad battery drain or the WiFi showing an exclamation mark dropping the connections these could be your solutions!
GPS LOSING SIGNAL (it needs root):
OBSOLETE - GPS is now fixed in 18.6.A.0.182
After reading some complaints about the GPS not working in Lollipop I checked it in my phone and I discovered it was indeed behaving poorly. In my case it does get the signals from the satellites, computes the position and other value and then after just few seconds it starts all over again. Comparing the 5.1.1 /etc/gps.conf file with the the one in KitKat and some suggested in the internet I tested few changes and I managed to make it fully operational just changing a single parameter:
Actually it seems the gps.conf file from KitKat does fix the issue. It happened that I made a mess with the file permissions (umask is set by default to 0077). @nunu00 made me notice that it worked for him. So I tested it again, and after fixing the file permissions it does seem to do the job.
You can find a copy of the KK file in http://forum.xda-developers.com/showpost.php?p=63285443&postcount=2.
As root make a backup of the original /etc/gps.conf and copy it over (as gps.conf. Remove the ".txt" postfix). Be sure the file is readable by everyone. Then reboot the phone and the GPS will be back to normal.
Additionally (but not necessarily) one may want to use an NTP server for his or her geographical region, like for example, if one is in Europe should comment out the stock NTP server and set instead the European one:
Code:
#Test
# NTP_SERVER=time.gpsonextra.net
#Asia
# NTP_SERVER=asia.pool.ntp.org
#Europe
[B]NTP_SERVER=europe.pool.ntp.org[/B]
#North America
# NTP_SERVER=north-america.pool.ntp.org
Even better on can add the NTP server, if available, for the Country, like I did for Italy:
Code:
#Italy
NTP_SERVER=it.pool.ntp.org
All other servers must obviously be commented out.
I/O WAIT ALWAYS AT 50% (it needs root):
Lollipop added in the Xperia M2 the compressed virtual memory, also known as zram. It is a feature that I personally like (I implemented it in the kernel for my crappy low range/low memory/low quality Samsung phone I had previously) as long as it works as it must. At the cost of little CPU time one can benefit from few hundreds megabytes of more usable RAM. Unfortunately in Lollipop it seems bugged, since the zram makes the process kswapd0 in constant I/O Wait (about 50%), which may degrade the max performances and also keeps at least two cores running at 1190MHz, draining the battery. One can see it with the "busybox top" command (busybox is installable in /data/local/tmp by anyone - no root needed):
Code:
Mem: 733016K used, 152060K free, 0K shrd, 40788K buff, 180220K cached
CPU: 1.2% usr 7.4% sys 0.0% nic [B][COLOR="red"]47.3% idle[/COLOR] [COLOR="Blue"]43.8% io[/COLOR][/B] 0.0% irq 0.0% sirq
- Solution 1: enable the "laptop mode" and change the swappiness value
It has been reported by @semil and confirmed by @linuxct that changing the swappiness value to something between 40-60 improves it (with zram enabled). Obviously you need root. Just make a /etc/init.d script with the following line
Code:
sysctl -w vm.swappiness=60
(you can change 60 to 40 or else while testing) or add it to /etc/init.d/00stop_ric. It changed nothing in my phone, though, so I tried tampering with other parameters and eventually I've been successful. Appending after the command above the following two lines
Code:
sysctl -w vm.laptop_mode=1
sysctl -w vm.drop_caches=1
finally the kernel moved out of the I/O wait. In my phone with 130-140 apps installed it always takes a about 10 minutes after boot, so be patient while testing. The two parameters above are non destructive and they get rewritten after each boot, so they can't make things worse than what they already are.
After the update 18.6.A.0.182 the IO Wait is still there. I did some some tests and I could raise the swappiness to 90. The IO Wait still goes down, but theoretically giving a slightly better "multitasking" than with a 40 or 60 value.
- Solution 2: disable the zram
Well, the trick is simple: disable the zram and the iowait has gone. To disable it as root one needs to execute
Code:
swapoff /dev/block/zram0
At any time. But it is obviously suggested to put the command in a script in /etc/init.d (just add it at the end of /etc/init.d/00stop_ric). And this is how the idle and iowait times are now:
Code:
Mem: 780028K used, 105048K free, 1000K shrd, 2284K buff, 149080K cached
CPU: 3.9% usr 4.9% sys 0.0% nic [B][COLOR="Red"]91.0% idle[/COLOR] [COLOR="RoyalBlue"]0.0% io[/COLOR][/B] 0.0% irq 0.0% sirq
WIFI DROPPING CONNECTIONS SHOWING AN EXCLAMATION MARK:
If you see an exclamation mark on the right of the WiFi status icon it means that Lollipop can't access the Internet still being connect to a WiFi AP. This is apparently due to some incompatibility between the new drivers and the Captive Networks, the Hot Spots showing as open but that indeed require a web login to be used.
- Solution 1: Disable the Capitve Networks all together:
The good news is that as regular users (non root) we can still switch it off. From a terminal emulator app or via "adb shell" (google to know how to install and play with the latter) simply type:
Code:
settings put global captive_portal_detection_enabled 0
and reboot. To re-enable it give the command:
Code:
settings put global captive_portal_detection_enabled 1
To check the current state (I'd suggest to do it before setting it. It should report 1) type:
Code:
settings get global captive_portal_detection_enabled
To run it via a Terminal emulator on the phone you need to have UID shell. Just execute first:
Code:
su shell
and then one of the commands above. But one needs the phone to be rooted for that.
UPDATE: In 18.6.A.0.182 as soon as I enable the Global Captive Support I get the exclamation mark. It doesn't drop the connection anymore but it is quite annoying.
- Solution 2: Disable the check for open/public networks:
This is still under investigation, but it seems to do the job. Simply go to the WiFi Settings/Advanced and disable the open networks notification. UPDATE: I still get the exclamation mark but it doesn't drop the connection.
GOOGLE SEARCH BAR ANIMATIONS AND VOICE SEARCH (requires root):
In the Xperia Home we can now have the Google search bar (to hide it just "swipe in" two fingers in the screen as when we add widgets and touch the hide button on the right of the bar. Which is my most favorite solution). The ugly thing is that when touching the bar Google Now opens with no animation. Also the option to enable "voice search" from any screen isn't available anymore. The value of "ro.config.low_ram " in /system/buil.prop is set to "true". An user suggested that changing (as root) it to "false" as in below
Code:
ro.config.low_ram=false
should fix it. Always make a backup of build.prop file before modifying it!!
I tested it myself and the option to have the voice search in all screens did appear indeed. I didn't see any changes in the animations, though.
LITTLE ICONS IN XPERIA HOME:
If like me you have been shocked by the new huge icons in the Xperia Home, so much that you were already thinking about switching the home launcher, don't fret: the small icons are still there!! Simply "swipe in" two fingers in the screen and together with the ability of adding widgets, changing themes and else on the bottom right there is the new "Home Settings". Click on it and you get the option to have the new rotating Xperia Home and.. yes, the smaller lovely icons back!
ENABLE MULTI USER (it needs root):
Due to the low amount of RAM (see the need for the zram above) and internal memory Sony doesn't support the multi user option in Lolliopop 5.1.1 for devices with 1GB. To enable it just add to the /system/build.prop file the following two lines:
Code:
fw.show_multiuserui=1
fw.max_users=3
where 3 users mean the main account, the guest account and a second account. Always remember to make a backup of the stock build.prop before any modification! If one just wants to test it without messing up with build.prop, the same behavior is achievable withthe following commands:
Code:
setprop fw.show_multiuserui 1
setprop fw.max_users 3
Unfortunately it is missing the user icon in the top right of the notification panel and frankly it is a lag fest. Which should be the reason why Sony removed it.
To disable it first delete any account you have eventually created (otherwise I'm afraid you end up wasting precious internal memory for nothing), restore the build.prop file in case it has been modified and reboot. Everytthing will be back to normal.
[CONTINUE]
--------------------
I hope this helps. If you have any other suggestion/solution, please write about them in the thread and I will add them in the main post. Also this is not a thread about getting help, use the forum for it. Still questions about the mentioned tips are welcome
RAISE ALL MAX VOLUMES (it needs root):
Many complains that in Lollipop 5.1.1 the volumes went lower. There seems to be a solution for it. As suggested by @Ciptraandoni in the files
Code:
/etc/mixer_paths.xml
/etc/mixer_paths_VY55.xml
/etc/mixer_paths_VY58.xml
Look for the lines:
Code:
<ctl name="RX1 Digital Volume" value="84" />
<ctl name="RX2 Digital Volume" value="84" />
<ctl name="RX3 Digital Volume" value="84" />
<ctl name="RX4 Digital Volume" value="84" />
Raising the value 84 by a little bit in all files improves the max volumes. I personally tested it. With the value 88 it was fine, then raised them to the value 91 I have got some distortion. So do it at your own risk. Also always remember to backup your system files first!!
TRIM YOUR NAND (it needs root):
Since Android 4.3 Google introduced the Trim (see link) in the kernel, which should restore the performances on SSD/NAND after a long use. It should be executed regularly by Android (not sure when), still after manually trimming my ext4 partition in the SD card it reported more than 9 GB cleaned. To execute it yourself first check if fstrim is available on your busybox. As root type in the terminal:
Code:
busybox fstrim
If present you'll get the list of options, otherwise an error. If fstrim is available type ("-v" is the verbose option):
Code:
busybox fstrim -v /system
busybox fstrim -v /data
busybox fstrim -v /cache
then, as usual, you can put the last three lines in a /etc/init.d script (they don't take very long. less if recently trimmed).
ONE SHOT KITKAT ROOTING:
@linuxct made a modified rootkit script which exploits one of the latest KK vulnerabilities, allowing to root KK without the need to downgrade the kernel. With my help he also modified the script to disable the RIC in one shot.
You can find the instructions in here.
This isn't directly Lollipop related, but since we need to go through a rooted KK to have a rooted Lollipop i thought to add it here.
IMPROVE THE APPEARANCE OF YOUR ROM
Click on the Google Play button on my signature and download one of my themes. Most are free! Also don't forget to rate them 5 stars.
Great! I thought it was my router problem (WRT160NL + DDwrt), but I'll disable that wifi option. Thanks!
linuxct said:
Great! I thought it was my router problem (WRT160NL + DDwrt), but I'll disable that wifi option. Thanks!
Click to expand...
Click to collapse
You're very welcome, amigo.
Also you may want to try to mess up with the router's QoS settings. But if working (I can't test it myself) that will fix it only for your router. The solution above is much more general. Not sure what are the downsides, but in case, on a weak signal, just manually disable the WiFi yourself and use 3G/4G (the radio?).
Miche1asso said:
You're very welcome, amigo.
Also you may want to try to mess up with the router's QoS settings. But if working (I can't test it myself) that will fix it only for your router. The solution above is much more general. Not sure what are the downsides, but in case, on a weak signal, just manually disable the WiFi yourself and use 3G/4G (the radio?).
Click to expand...
Click to collapse
I have QoS disabled, but I noticed that in both routers I have (160NL and Archer C20i), the exclamation mark only appears when I'm far from them, in another room for example. So it's because of the poor signal, even though some times it shows all bars (max. signal) and the warning. :silly:
I'm going to stay with the setting on 0, and if it still shows the exclamation mark, then I'll try configuring my routers. Grazie
linuxct said:
I have QoS disabled, but I noticed that in both routers I have (160NL and Archer C20i), the exclamation mark only appears when I'm far from them, in another room for example. So it's because of the poor signal, even though some times it shows all bars (max. signal) and the warning. :silly:
I'm going to stay with the setting on 0, and if it still shows the exclamation mark, then I'll try configuring my routers. Grazie
Click to expand...
Click to collapse
Just out of curiosity, when showing the exclamation mark does it switch to 3G/4G? In my case it just drops all connections, and to add insult to injury it happens even few cm from the "router" (which is actually the internet shared via MacBook since the WiFi fried in my router).
Miche1asso said:
Just out of curiosity, when showing the exclamation mark does it switch to 3G/4G? In my case it just drops all connections, and to add insult to injury it happens even few cm from the "router" (which is actually the internet shared via MacBook since the WiFi fried in my router).
Click to expand...
Click to collapse
It drops all connections. I noticed once, because Whatsapp web stopped working. Then I check the phone and the exclamation mark is there. Turn it off and on and it works again.
And yes, I was very near my router, let's say 50cm?
linuxct said:
It drops all connections. I noticed once, because Whatsapp web stopped working. Then I check the phone and the exclamation mark is there. Turn it off and on and it works again.
And yes, I was very near my router, let's say 50cm?
Click to expand...
Click to collapse
Ok, same experience then. So it's better staying off and good riddance!!
Not had any WiFi problems all I know is I have min 50mps home broadband with 5ghz and 2.5ghz networks my data connection is running fine on 4G/3.5G battery is definitely worse but I was running amplify, greenify with a de-bloated ftf and getting 6hrs plus sot regularly it's gonna take me a while to get used to normal battery life again
D2303 5.1 lollipop customised NCB rooted de-bloated LB t2u nut dual recovery x-reality+supervivid
Hello
I have also this wifi problem but i don't understand how to fix it.
I tried, as it's written, to write the command in a terminal app, but it said that i don't have the permission to execute it.
My phone is rooted and i tried also somehow to have the sudo but it didn't work either.
Someone could explain to me what should i do ?
Thank you.
[email protected] said:
Not had any WiFi problems all I know is I have min 50mps home broadband with 5ghz and 2.5ghz networks my data connection is running fine on 4G/3.5G battery is definitely worse but I was running amplify, greenify with a de-bloated ftf and getting 6hrs plus sot regularly it's gonna take me a while to get used to normal battery life again
D2303 5.1 lollipop customised NCB rooted de-bloated LB t2u nut dual recovery x-reality+supervivid
Click to expand...
Click to collapse
Well, you probably remember that I was complaining about KK battery life. Now staying with WiFi and applying the tweaks above, in about 17h I had a drop of 24%. about 70min usage. In other words it was less than 1.5%!!
I'll test it in 4G, but my signal is crap, so I don't expect much . Still the Stamina mode (completely enabled, with the usual apps in white list, like Whatsapp) seems to do a great job, finally.
Niklaus89 said:
Hello
I have also this wifi problem but i don't understand how to fix it.
I tried, as it's written, to write the command in a terminal app, but it said that i don't have the permission to execute it.
My phone is rooted and i tried also somehow to have the sudo but it didn't work either.
Someone could explain to me what should i do ?
Thank you.
Click to expand...
Click to collapse
That's weird. I just doubled checked and it works with both the user and root accounts. i mean, there is little to explain, you just have to type this command:
settings put global captive_portal_detection_enabled 0
I am not sure either what you mean with "i tried also somehow to have the sudo ". To "sudo" in a rooted android you just type "su". "su -c <command>" to run a command (like "su -c id". That should report user 0 and group 0).
Okay thank you, finaly i did it.
I still couldn't do it without typing "su". Thank you.
I dont know if its ok this, but i Just use my celphone today on facebook and whatsapp and a hour of videos on YouTube, without you tip (i Just used with wifi)
I got roughly 5.5hrs screen on time yesterday with no changes to settings. Still not sure about how fast the battery drains though
D2303 5.1 lollipop customised NCB rooted de-bloated LB t2u nut dual recovery x-reality+supervivid
Is there appreciable difference in performance between zram on and off ? Antutu Benchmark shows 19421 points for ON zram and 19889 points for OFF
dark90 said:
I dont know if its ok this, but i Just use my celphone today on facebook and whatsapp and a hour of videos on YouTube, without you tip (i Just used with wifi)
Click to expand...
Click to collapse
Pantalla is screen? And you have got 9+ hours? You're more than fine then. Indeed I am not sure if that iowait thing is a general problem. Can anyone with the zram on and possibly busysbox installed, check the iowait average values using the command
Code:
busybox iostat
I wonder if it is anything wrong with my installatiom, but I had the issue even just after wiping the data.
[email protected] said:
I got roughly 5.5hrs screen on time yesterday with no changes to settings. Still not sure about how fast the battery drains though
Click to expand...
Click to collapse
Yeah, I can't manage to make a real battery evaluation myself. I am still connected many times with adb and that charges the phone, ruining all battery statistics.
~Patryk said:
Is there appreciable difference in performance between zram on and off ? Antutu Benchmark shows 19421 points for ON zram and 19889 points for OFF
Click to expand...
Click to collapse
Well, technically on small jobs the zram does reduce slightly the performances. You see the benefits when you open a previous application, it should have the app screen as you left it more often than when it is turned off.
BTW any chance you can do the test mentioned above? The one about iostat.
Miche1asso said:
Can anyone with the zram on and possibly busysbox installed, check the iowait average values using the command
Code:
busybox iostat
Click to expand...
Click to collapse
Average of 14%. Bouncing from 13.3% to 14.5% in my case.
Oh, BTW, yes, CE1 has zRAM, but Algerian FTF was working worse than this one.
EDIT: Now it went up to 25.04%. Well, sh*t. The values I took before were after a reboot, so, when the device is fresh, just restarted, it only uses a 14~15%, but after opening apps it goes up
linuxct said:
Average of 14%. Bouncing from 13.3% to 14.5% in my case.
Oh, BTW, yes, CE1 has zRAM, but Algerian FTF was working worse than this one.
EDIT: Now it went up to 25.04%. Well, sh*t. The values I took before were after a reboot, so, when the device is fresh, just restarted, it only uses a 14~15%, but after opening apps it goes up
Click to expand...
Click to collapse
Indeed. Mine is stuck at 30-40%. Even higher as you can see from the "top" output in the first post (but that's for a single moment). This is what I get now with zram disabled about one night after reboot :
Code:
avg-cpu: %user %nice %system %iowait %steal %idle
14.00 1.79 10.87 4.13 0.00 69.21
And now I reboot the phone not touching the zram. here now just after boot:
Code:
avg-cpu: %user %nice %system %iowait %steal %idle
24.30 3.89 31.94 14.59 0.00 25.29
Which would be ok, but it is raising. Indeed now, just after few minutes..
Code:
avg-cpu: %user %nice %system %iowait %steal %idle
13.67 2.82 17.22 31.39 0.00 34.91
31.39% and it keeps raising. Nope, disabled it stays.
Just to be clear, since a picture it worth 100 words, this is the effect of having an high iowait:
The CPU stays most of the time at full frequency. Often just for doing nothing but waiting for kswapd0 trying to access the RAM.
Miche1asso said:
Indeed. Mine is stuck at 30-40%. Even higher as you can see from the "top" output in the first post (but that's for a single moment). This is what I get now with zram disabled about one night after reboot :
Code:
avg-cpu: %user %nice %system %iowait %steal %idle
14.00 1.79 10.87 4.13 0.00 69.21
And now I reboot the phone not touching the zram. here now just after boot:
Code:
avg-cpu: %user %nice %system %iowait %steal %idle
24.30 3.89 31.94 14.59 0.00 25.29
Which would be ok, but it is raising. Indeed now, just after few minutes..
Code:
avg-cpu: %user %nice %system %iowait %steal %idle
13.67 2.82 17.22 31.39 0.00 34.91
31.39% and it keeps raising. Nope, disabled it stays.
The CPU stays most of the time at full frequency. Often just for doing nothing but waiting for kswapd0 trying to access the RAM.
Click to expand...
Click to collapse
Clear enough. Just added swapoff to my 00stopric. Now let's see how multitasking goes
Code:
su
swapoff /dev/block/zram0
fails for me... Central Europe prerooted, flashed with twrp. My %iowait is around 23% and counting...
Edit: After an restart, it executed the command just fine, and my idle time is normal.
But now there is another problem - I cannot open 00stop_ric as a text, to add the command... tried both es explorer and total commander... any idea?
Hello.
I activated the Bluetooth HCI snoop log on my Nokia 7 plus.
I restarted the phone, and connected it to different bluetooth devices.
But i can't find the logfile. Where should i find it?
adb pull /sdcard/Android/data/btsnoop_hci.log
adb pull /sdcard/data/btsnoop_hci.log
adb pull /sdcard/btsnoop_hci.log
adb pull /btsnoop_hci.log
returns always "remote object ... does not exist"
This is what /etc/bluetooth/bt_stack.conf looks like:
# Enable trace level reconfiguration function
# Must be present before any TRC_ trace level settings
TraceConf=true
# Trace level configuration
# BT_TRACE_LEVEL_NONE 0 ( No trace messages to be generated )
# BT_TRACE_LEVEL_ERROR 1 ( Error condition trace messages )
# BT_TRACE_LEVEL_WARNING 2 ( Warning condition trace messages )
# BT_TRACE_LEVEL_API 3 ( API traces )
# BT_TRACE_LEVEL_EVENT 4 ( Debug messages for events )
# BT_TRACE_LEVEL_DEBUG 5 ( Full debug messages )
# BT_TRACE_LEVEL_VERBOSE 6 ( Verbose messages ) - Currently supported for TRC_BTAPP only.
TRC_BTM=2
TRC_HCI=2
TRC_L2CAP=2
TRC_RFCOMM=2
TRC_OBEX=2
TRC_AVCT=2
TRC_AVDT=2
TRC_AVRC=2
TRC_AVDT_SCB=2
TRC_AVDT_CCB=2
TRC_A2D=2
TRC_SDP=2
TRC_SMP=2
TRC_BTAPP=2
TRC_BTIF=2
TRC_BNEP=2
TRC_PAN=2
TRC_HID_HOST=2
TRC_HID_DEV=2
# This is Log configuration for new C++ code using LOG() macros.
# See libchrome/base/logging.h for description on how to configure your logs.
# sample configuration:
#LoggingV=--v=0
#LoggingVModule=--vmodule=*/btm/*=1,btm_ble_multi*=2,btif_*=1
# PTS testing helpers
# Secure connections only mode.
# PTS_SecurePairOnly=true
# Disable LE Connection updates
#PTS_DisableConnUpdates=true
# Disable BR/EDR discovery after LE pairing to avoid cross key derivation errors
#PTS_DisableSDPOnLEPair=true
# SMP Pair options (formatted as hex bytes) auth, io, ikey, rkey, ksize
#PTS_SmpOptions=0xD,0x4,0xf,0xf,0x10
# SMP Certification Failure Cases
# Set any of the following SMP error values (from smp_api_types.h)
# to induce pairing failues for various PTS SMP test cases.
# Setting PTS_SmpFailureCase to 0 means normal operation.
# Failure modes:
#
# SMP_PASSKEY_ENTRY_FAIL = 1
# SMP_PAIR_AUTH_FAIL = 3
# SMP_CONFIRM_VALUE_ERR = 4
# SMP_PAIR_NOT_SUPPORT = 5
# SMP_PAIR_FAIL_UNKNOWN = 8
# SMP_REPEATED_ATTEMPTS = 9
# SMP_NUMERIC_COMPAR_FAIL = 12
#PTS_SmpFailureCase=0
Click to expand...
Click to collapse
After Nougat I had to take a bug report instead
You may not still be looking this info, but for the sake of anyone else who may be... It may depend on your Android version. From my own experience it was always right there in the main directory, but as soon as my Nokia 5 upgraded past Android 6 Marshmallow, the HCI snoop log is no longer generated, and now if I want Bluetooth logs I take a bug report, send it to myself, and pull Bluetooth logs out of it. It's a bit more fiddly, but it works.
schorsch81 said:
Hello.
I activated the Bluetooth HCI snoop log on my Nokia 7 plus.
I restarted the phone, and connected it to different bluetooth devices.
But i can't find the logfile. Where should i find it?
adb pull /sdcard/Android/data/btsnoop_hci.log
adb pull /sdcard/data/btsnoop_hci.log
adb pull /sdcard/btsnoop_hci.log
adb pull /btsnoop_hci.log
returns always "remote object ... does not exist"
This is what /etc/bluetooth/bt_stack.conf looks like:
Click to expand...
Click to collapse
My device is redmi note 8 pro, and I have flashed corvus, havoc, and evolution x. All three load app which depend on internet slow to load and/or even disconnecting. Especially for call of duty mobile, was the app that loads longer, reconnects and even disconnects (leading to me having to restart and login again). I'm comparing this to stock miui 12 rom, global version. I'm not sure is it related to kernel, but all roms have different kernels and all have this problem. Maybe its a related to mediatek chips? Or is there some thing i can install that improves connectivity? Hope someone can shed light on this. Thank you
Try to increase the time between Wi-Fi network scans
By default, Android scans for nearby Wi-Fi networks every 15 seconds when you have Wi-Fi enabled. This helps when you're moving around between multiple access points, but for the most part, the high interval only serves to drain your battery and slow down over-all performance. If you'd rather have your phone or tablet wait for 5 minutes before it looks for nearby Wi-Fi networks again, add the following line to the end of your Android's system file called build.prop:
Code:
wifi.supplicant_scan_interval=300
Try to increase system's TCP buffers size
That can help increase the speed of a slow Internet connection, especially when using mobile networks. You do so by adding these lines to build.prop file:
Code:
net.tcp.buffersize.default = 4096,87380,256960,4096,16384,256960
net.tcp.buffersize.wifi = 4096.87380,256960,4096,16384,256960
net.tcp.buffersize.umts = 4096,87380,256960,4096,16384,256960
net.tcp.buffersize.gprs = 4096.87380,256960,4096,16384,256960
net.tcp.buffersize.edge = 4096,87380,256960,4096,16384,256960
Also, prescribing Cloudflare’s DNS servers in some cases reduces the ping time. You again alter build.prop accordingly:
Code:
net.rmnet0.dns1 = 1.1.1.1
net.rmnet0.dns2 = 1.0.0.1
net.dns1 = 1.1.1.1
net.dns2 = 1.0.0.1
Wow a reply! Thanks a lot! Wells I'm back on my stock rom now, but basing on your recommendations, are you saying custom roms have settings that are slow/standard? I'm still new to the custom rom thing and a noob at entering codes... But yea I used call of duty mobile as my benchmark since thats my go to game. For miui stock I'd say loads the game in 30 seconds, where as custom roms loads it in 1min plus... I'm using home internet all by myself and speed is good.
Also one more point is that when I turn off the screen, then when turn it back on again (in like a few minutes) and re enter the app, on custom roms, its like its completely disconnected from the internet, it cannot load anymore unless i restart the app... but on miui it loads for around 5 seconds and its reconnected. I think I'm repeating myself here. but yea. thanks!