Related
I want to know Build.prop every item mean and had searched all over, but only found one page http://www.streakdroid.com/wiki/index.php?title=Build.prop, unfortunally, this page not contain all items, for example:
ro.telephony.default_network
0 = WCDMA Perfered
1 = GSM Only
2 = WCDMA Only
3 = GSM/WCDMA (auto mode, according to PRL)
4 = CDMA / EVDO. Perfered
ro.setupwizard.mode
OPTIONAL = Allow bypass of first start setup
DISABLED = Do not show setup on first start
Click to expand...
Click to collapse
http://www.neopeek.com/viewtopic.php?f=14&t=6313&start=300
Here is other page that mention build.prop
Suggestions, in build.prop try the following and test:
ro.product.cpu.abi=armeabi-v7 [remove or change to] ro.product.cpu.abi2=armeabi-v7 [or] ro.product.cpu.abi2=armeabi-v7a
Technically these shouldn't even be used [keep] ro.product.cpu.abi=armeabi
ro.board.platform=qsd8k [remove]
we have an msm7k not qsd8k [keep] ro.board.platform=msm7k
Only "ro.opengles.version = 65536" is needed as 131072 is for EGL2.0
AFAIK 65536 = EGL 1.0, 65537 = EGL 1.1, 131072 = EGL 2.0
and the version in your libGLES_qcom.so is "OpenGL ES 1.0-CM"
Click to expand...
Click to collapse
Lots of interest in build.prop lately.
Your best option may be to just search on each setting, a lot of people on xda and elsewhere have discussed most of the settings.
What settings do you have questions about specifically?
EDIT: It is also worth noting that build.prop is not the only place some of these settings are located. Some of the more important settings are configured elsewhere using detection routines. (these settings supercede the settings entered in build.prop.)
Not all phones are the same or use the same settings, builds like xdandroid are put together with this in mind.
nice, job
the most important when making, mod builds, build a new ROM, change anything in the system.ext2. IT'S THE END RESULTS. I use this in all my mod builds. notice on the market when looking for and app and the app is not there.
add this to your build.prop. ro.product.cpu.abi=armeabi-v7. you will see a lot more apps. we know this is not for our devices. but we have to try to get the best possible results for everyone. look this is what the new BLAZN build will have. with this and others stuff it runs super fast.
ro.product.cpu.abi=armeabi
ro.product.cpu.abi=armeabi-v7
ro.board.platform=msm7k
ro.board.platform=qsd8k
# The OpenGL ES API level that is natively supported by this device.
# This is a 16.16 fixed point number
ro.opengles.version = 65536
ro.opengles.version = 131072
#0 - mdp composition, 1 - gpu composition
ro.sf.hw=1
#
# ADDITIONAL_BUILD_PROPERTIES
#
keyguard.no_require_sim=true
ro.ril.hsxpa=3
ro.ril.gprsclass=32
ro.ril.hep=1
ro.ril.enable.dtm=1
ro.ril.hsdpa.category=28
ro.ril.enable.a53=1
ro.ril.enable.3g.prefix=1
ro.ril.hsupa.category=9
rild.libargs=-d /dev/smd0
DEVICE_PROVISIONED=1
ro.config.hw_addsettingsdbex=1
ro.config.hw_gcf_mms=true
ro.config.hwft_PNN_function=true
persist.cust.tel.adapt=1
persist.cust.tel.eons=1
ro.config.hwfeature_gps_test=0
ro.config.hwfeature_ecc=true
keyguard.no_require_sim=true
ro.config.lowbattery_shutdown=1
ro.config.hwfeature_wakeupkey=1
ro.config.endkeybehavior=true
ro.config.hw_menu_unlockscreen=false
ro.config.KeyPassToUser=true
ro.media.enc.lprof.duration=30
ro.config.PicMaxSize=3mp
ro.config.hw_temperature_warn=true
ro.config.hw_clocksetting=0
#set network mode CDMA-->4 WCDMA-->0
ro.telephony.default_network=0
ro.cdma.home.operator.numeric=
# Release Bluetooth HW/SW information
ro.bt.chipset = Broadcom BCM4329-B1
ro.bt.version = Bluetooth 2.1 + EDR
ro.bt.stack = Broadcom BTL-A
ro.bt.stack.version = 2.0.50.032
#0x10000010010100100000011 represent bt profile list
ro.bt.profiles = 4270339
# Properties of BTLA stack
service.brcm.bt.activation = 0
service.brcm.bt.srv_active = 0
service.brcm.bt.hcid_active = 0
service.brcm_bt.btld = 0
service.brcm.bt.btld_pid = 0
service.brcm.bt.avrcp_pass_thru = 0
service.brcm.bt.avrcp_toggle = 1
# froyo 2.2.1 blazn add prop
#DTS2010082701201 liyou 20100827 begin
ro.config.hwft_MatchNum=7
#ro.config.hwft_MatchNumShort=7
#DTS2010082701201 liyou 20100827 end
ro.product.factoryversion=0
# 0:nothing; 1:go home; 2:go sleep; 3:go home and then sleep.
ro.config.hw_defaultEndBtnFunc=1
ro.config.hwft_PinPukUnlockscr=true
ro.com.google.clientidbase=hw-smart-phone
ro.config.hw_opta=
ro.config.hw_optb=
ro.config.hw_temperature_warn=true
ro.config.hw_ignore270=true
ro.config.hw_timeformat=true
ro.config.timeformat=24
ro.config.hw_dateformat=true
ro.config.dateformat=dd-MM-yyyy
# DTS2010073101355 wangqing 20100806 end
ro.config.hw_gl=1
#
# QUAIL MODS
#
# UI Tweaks
#ro.config.hw_default_launcher=org.zeam
#ro.config.hw_isCustomize=true
#ro.config.hw_customizeType=02
#ro.config.PopupTwink=true
#ro.config.SetStatusbarText=true
ro.config.hw_boot_animation=true
ro.setupwizard.mode=DISABLED
# Automatically turn display off when idle.
settings.display.autobacklight=true
# To make the phone ring faster when dialing out, I changed
ro.telephony.call_ring.delay=1000
# To make the phone come off of the "black screen" faster in the middle of
# or the end of phone calls when you pull the phone away from your face.
mot.proximity.delay=100
# To enable the hard key lights to stay on while the screen is on and not timeout
ro.mot.buttonlight.timeout=false
# Google has something called a "checkin" service that sends them anonymous
# usage data, bug reports, crash logs, etc, but it fails a lot. When you download
# something from the Market, it sends a message to Google about it, and if it fails
# it just freezes.
ro.config.nocheckin=true
ro.ril.def.agps.mode=1
ro.ril.def.agps.feature=1
ro.ril.enable.fd.plmn.prefix=23402,23410,23411
ro.ril.enable.sdr=1
ro.ril.enable.gea3=1
ro.ril.disable.power.collapse=0
ro.telephony.call_ring.delay=1
ro.config.notification_sound=DearDeer.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.config.ringtone=BussaMove.ogg
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=true
ro.setupwizard.mode=OPTIONAL
ro.media.dec.jpeg.memcap=10000000
rild.libpath=/lib/froyo/libhtcgeneric-ril.so
ro.compcache.default=18
wifi.supplicant_scan_interval=120
ro.sf.lcd_density=210
ro.telephony.default_network=0
# Dalvik VM heap size
dalvik.vm.heapsize=32m
dalvik.vm.execution-mode=int:fast
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
the build.prop is not the only place some of these settings are located. I always look for the best possible results for everyone
THANKS
very good, thanks tiad8, I learn more from your post.
I notice you add bluetooth section,does this mean android support rhod400 bt now?
ok, I know this from your blazn post
Nautis said:
EDIT: It is also worth noting that build.prop is not the only place some of these settings are located. Some of the more important settings are configured elsewhere using detection routines. (these settings supercede the settings entered in build.prop.)
Click to expand...
Click to collapse
Yes, i had noticed this,when I change locale to chinese, only setupwizard is chinese language, system locale need to set at settins->languages
ro.product.locale.language=zh
ro.product.locale.region=CN
I'm just copying and pasting from Xenova from this thread: http://forum.xda-developers.com/showthread.php?t=1239713
I'm just making another post on this subforum because I myself have searched everywhere on the Gnex forums and found NOTHING. After this guy's fix, it was so good, I took the effort to make this to spread it to you guys too! This fix made me cry out of happiness.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
THE FIX
Requirements:
Rooted Device
File Manager: e.g. Root Explorer
1. Searching for NTP server information
Go to http://www.pool.ntp.org/en/
At the right side of webpage, there is "Active Servers". Go in and look for the setting of your 1)region and 2)country
For example, one's region is Europe then you write down the NTP server for that: 0.europe.pool.ntp.org; 1.europe.pool.ntp.org; 2.europe.pool.ntp.org; 3.europe.pool.ntp.org
Then the servers for your country from the list down there and click the link(Example: Switzerland — ch.pool.ntp.org; 0.ch.pool.ntp.org; 1.ch.pool.ntp.org; 2.ch.pool.ntp.org; 3.ch.pool.ntp.org
The "Italic" words are the information you need to jot down for later use
3. Modify the gps.conf file (Most Crucial Stage)
Copy the codes in grey box (in first post) to a notepad, then change the extension name from .txt to .conf then copy to your phone
Use file manager to copy to this location: /etc/gps.conf and replace the original gps.conf
Open and Edit the gps.conf using rootexplorer or others file managers
Change the COUNTRY and REGION in following lines with the info you got from the website just now. Keep other values unchange unless you know what it is. Example of REGION such as NorthAmerica, Asia, Africa, Europe.
Your new gps.conf should look as below:
Code:
NTP_SERVER=0.COUNTRY.pool.ntp.org
NTP_SERVER=1.COUNTRY.pool.ntp.org
NTP_SERVER=2.COUNTRY.pool.ntp.org
NTP_SERVER=3.COUNTRY.pool.ntp.org
NTP_SERVER=0.REGION.pool.ntp.org
NTP_SERVER=1.REGION.pool.ntp.org
NTP_SERVER=2.REGION.pool.ntp.org
NTP_SERVER=3.REGION.pool.ntp.org
NTP_SERVER=COUNTRY.pool.ntp.org <-This is changed from the top line to here. It may works better if we put it here.
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin
# DEBUG LEVELS: 0 - none, 1 - Error, 2 - Warning, 3 - Info
# 4 - Debug, 5 - Verbose
DEBUG_LEVEL =0
# Intermediate position report, 1=enable, 0=disable
INTERMEDIATE_POS=0
# Accuracy threshold for intermediate positions
# less accurate positions are ignored, 0 for passing all positions
ACCURACY_THRES=0
# Report supl ref location as position, 1=enable, 0=disable
REPORT_POSITION_USE_SUPL_REFLOC=1
# Wiper (wifi positioning), 1=enable, 0=disable
ENABLE_WIPER=1
################################
##### AGPS server settings #####
################################
# FOR SUPL SUPPORT, set the following
SUPL_HOST=supl.google.com
SUPL_PORT=7276
SUPL_NO_SECURE_PORT=3425
SUPL_SECURE_PORT=7275
SUPL_TLS_HOST=FQDN
SUPL_TLS_CERT=/etc/SuplRootCert
# FOR C2K PDE SUPPORT, set the following
C2K_HOST=c2k.pde.com
C2K_PORT=1234
CURRENT_CARRIER=common
DEFAULT_AGPS_ENABLE=TRUE
DEFAULT_SSL_ENABLE=FALSE
# TRUE for "User Plane", FALSE for "Control Plane"
DEFAULT_USER_PLANE=TRUE
Make sure the permission of the file is rw-r--r--
MY EXAMPLE FOR CANADIAN GPS FIX:
Code:
[COLOR="Red"]NTP_SERVER=0.north-america.pool.ntp.org
NTP_SERVER=1.north-america.pool.ntp.org
NTP_SERVER=2.north-america.pool.ntp.org
NTP_SERVER=3.north-america.pool.ntp.org
NTP_SERVER=0.ca.pool.ntp.org
NTP_SERVER=1.ca.pool.ntp.org
NTP_SERVER=2.ca.pool.ntp.org
NTP_SERVER=3.ca.pool.ntp.org
NTP_SERVER=ca.pool.ntp.org [/COLOR]
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin
# DEBUG LEVELS: 0 - none, 1 - Error, 2 - Warning, 3 - Info
# 4 - Debug, 5 - Verbose
DEBUG_LEVEL =0
# Intermediate position report, 1=enable, 0=disable
INTERMEDIATE_POS=0
# Accuracy threshold for intermediate positions
# less accurate positions are ignored, 0 for passing all positions
ACCURACY_THRES=0
# Report supl ref location as position, 1=enable, 0=disable
REPORT_POSITION_USE_SUPL_REFLOC=1
# Wiper (wifi positioning), 1=enable, 0=disable
ENABLE_WIPER=1
################################
##### AGPS server settings #####
################################
# FOR SUPL SUPPORT, set the following
SUPL_HOST=supl.google.com
SUPL_PORT=7276
SUPL_NO_SECURE_PORT=3425
SUPL_SECURE_PORT=7275
SUPL_TLS_HOST=FQDN
SUPL_TLS_CERT=/etc/SuplRootCert
# FOR C2K PDE SUPPORT, set the following
C2K_HOST=c2k.pde.com
C2K_PORT=1234
CURRENT_CARRIER=common
DEFAULT_AGPS_ENABLE=TRUE
DEFAULT_SSL_ENABLE=FALSE
# TRUE for "User Plane", FALSE for "Control Plane"
DEFAULT_USER_PLANE=TRUE
4. Reboot
Go setting, turn on your "use GPS satelites" and "Integrate Google Navigation"
Restart the device (normal restart)[/B]
5. Use GPS status and Toolbox
Tool available in market for free, please donate so developers are encouraged for better release in the future[/B]
Open app> tools> manage A-GPS state>Reset
Open app> tools> manage A-GPS state>Download
Optional restart device (not compulsory)
Use GPS status to start fixing satelites
Your satelite fixing speed should VERY FAST now
After get a successul GPS Lock, open your GPS applications and use like normal (e.g. Copilot, Sygic, or TomTom)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
END OF GUIDE
Above all else, THANK XENOVA! You can thank me all you want, I don't care. But PLEASE go to Xenova's thread and thank him too!
Thanks for the tip !
JB
Awesome, definitely going to try this.
Sent from my Paranoid GNex
I opened my GPS.conf as text to check, and this is all that's listed...is this the same for others?
{
"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"
}
Sent from my Galaxy Nexus using Tapatalk 2
Duce HD2 said:
I opened my GPS.conf as text to check, and this is all that's listed...is this the same for others?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
yeah this is a default gps.conf
I tried this and now keep getting: "Unfortunately, the process com.google.process.gapps has stopped".
I double checked the my gps.conf file and it seems I did everything as mentioned... any ideas?
Seriously, I know you are new here but read my posts right above bud. The person who took this information from another post of mine neglects to realize a lot of stuff does not work in this gps.conf file he supplied. They wanted to be a hero stealing research and post references and post it here like it was a solution. First of all, it comes from another phone not a Nexus. Secondly, I posted it just to sort of show people an example of how complicated a gps.conf could be and what I weeded out to get it working on my Nexus. Here is my gps.conf for you so you can see the lines that I stripped out of it that I know work. Of course you will have to update it to reflect your country. Hope it helps you.
I may have a few other lines to add but I want to give it another day or so and go over my results before I pass it on to others. When I am done my testing I will put up a new post for people. For now this should do you fine. Just update the servers, follow the same order.
gps.conf
NTP_SERVER=0.ca.pool.ntp.org
NTP_SERVER=1.ca.pool.ntp.org
NTP_SERVER=2.ca.pool.ntp.org
NTP_SERVER=3.ca.pool.ntp.org
NTP_SERVER=ca.pool.ntp.org
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin
# DEBUG LEVELS:
# 0 - none, 1 - Error,
# 2 - Warning, 3 - Info
# 4 - Debug, 5 - Verbose
DEBUG_LEVEL =0
ACCURACY_THRES=5
INTERMEDIATE_POS=0
ENABLE_WIPER=1
SUPL_HOST=supl.google.com
SUPL_PORT=7276
REPORT_POSITION_USE_SUPL_REFLOC=1
Flukester69 said:
Seriously, I know you are new here but read my posts right above bud. The person who took this information from another post of mine neglects to realize a lot of stuff does not work in this gps.conf file he supplied. They wanted to be a hero stealing research and post references and post it here like it was a solution. First of all, it comes from another phone not a Nexus. Secondly, I posted it just to sort of show people an example of how complicated a gps.conf could be and what I weeded out to get it working on my Nexus. Here is my gps.conf for you so you can see the lines that I stripped out of it that I know work. Of course you will have to update it to reflect your country. Hope it helps you.
I may have a few other lines to add but I want to give it another day or so and go over my results before I pass it on to others. When I am done my testing I will put up a new post for people. For now this should do you fine. Just update the servers, follow the same order.
gps.conf
NTP_SERVER=0.ca.pool.ntp.org
NTP_SERVER=1.ca.pool.ntp.org
NTP_SERVER=2.ca.pool.ntp.org
NTP_SERVER=3.ca.pool.ntp.org
NTP_SERVER=ca.pool.ntp.org
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin
# DEBUG LEVELS:
# 0 - none, 1 - Error,
# 2 - Warning, 3 - Info
# 4 - Debug, 5 - Verbose
DEBUG_LEVEL =0
ACCURACY_THRES=5
INTERMEDIATE_POS=0
ENABLE_WIPER=1
SUPL_HOST=supl.google.com
SUPL_PORT=7276
REPORT_POSITION_USE_SUPL_REFLOC=1
Click to expand...
Click to collapse
Dude. Don't get so butthurt.
I have:
-linked the original thread
-requested people to go to the original thread to thank the OP
-thanked the OP myself in ALL CAPS, as in "THANKS XENOVA!"
-stated I have copied and pasted it from original thread, IN MY VERY FIRST SENTENCE OF THE THREAD
How did I "want to be a hero stealing research and post references and post it here like it was a solution."?
Grow up. The only service I did was to copy and paste it into our forums, so when someone searches GPS fix on our forums, which I had, they would find it. I doubt many people would go to the actual Android Dev forums and search there for a Gnex GPS fix. I have also stated my contributions as such on the 2nd line of text in my OP.
EDIT: Never mind sir. Didn't realize you're from Ottawa. Everything makes sense now.
Duce HD2 said:
I opened my GPS.conf as text to check, and this is all that's listed...is this the same for others?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yea, thats the default. You gotta paste the more detailed GPS.conf over it.
Flukester69 said:
Seriously, I know you are new here but read my posts right above bud. The person who took this information from another post of mine neglects to realize a lot of stuff does not work in this gps.conf file he supplied. They wanted to be a hero stealing research and post references and post it here like it was a solution. First of all, it comes from another phone not a Nexus. Secondly, I posted it just to sort of show people an example of how complicated a gps.conf could be and what I weeded out to get it working on my Nexus. Here is my gps.conf for you so you can see the lines that I stripped out of it that I know work. Of course you will have to update it to reflect your country. Hope it helps you.
I may have a few other lines to add but I want to give it another day or so and go over my results before I pass it on to others. When I am done my testing I will put up a new post for people. For now this should do you fine. Just update the servers, follow the same order.
gps.conf
NTP_SERVER=0.ca.pool.ntp.org
NTP_SERVER=1.ca.pool.ntp.org
NTP_SERVER=2.ca.pool.ntp.org
NTP_SERVER=3.ca.pool.ntp.org
NTP_SERVER=ca.pool.ntp.org
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin
# DEBUG LEVELS:
# 0 - none, 1 - Error,
# 2 - Warning, 3 - Info
# 4 - Debug, 5 - Verbose
DEBUG_LEVEL =0
ACCURACY_THRES=5
INTERMEDIATE_POS=0
ENABLE_WIPER=1
SUPL_HOST=supl.google.com
SUPL_PORT=7276
REPORT_POSITION_USE_SUPL_REFLOC=1
Click to expand...
Click to collapse
Thank you Flukester... I will be checking this out and I would love to hear back after you do more testing.
fredboy said:
Thank you Flukester... I will be checking this out and I would love to hear back after you do more testing.
Click to expand...
Click to collapse
I plan to make a post on it by end of weekend but I am sure my config would be good for anyone given you put the right servers. I had people message me in Germany and parts of USA claiming similar results as mine.
Brought to you from my Galaxy Nexus using Tapatalk.
I should throw some infractions around for so much disrespect of others but instead will be placing user notes for other mods to see if some attitudes don't change!
The linked post clearly states it was tested on an HTC phone AND a Samsung and should work on othersl. Of course there may be some erroneous code in that respect but does not mean it will damage anything. Flukester69 not sure what your problem is with this. If it works or not users will report it. It is not your place to tear down somebody simply trying to help others. No one here gets paid for anything and your disrespect and flaming is not appropriate on XDA.
If I have to come back here there WILL be infractions.
Thread cleaned
FNM
kennyglass123 said:
I should throw some infractions around for so much disrespect of others but instead will be placing user notes for other mods to see if some attitudes don't change!
The linked post clearly states it was tested on an HTC phone AND a Samsung and should work on othersl. Of course there may be some erroneous code in that respect but does not mean it will damage anything. Flukester69 not sure what your problem is with this. If it works or not users will report it. It is not your place to tear down somebody simply trying to help others. No one here gets paid for anything and your disrespect and flaming is not appropriate on XDA.
If I have to come back here there WILL be infractions.
Thread cleaned
FNM
Click to expand...
Click to collapse
I'll send you a pm to explain. sorry.
I don't care to post in this thread as it serves no purpose other than duplication and distraction. There are existing threads where with plenty of information already.
Flukester69 said:
Seriously, I know you are new here but read my posts right above bud. The person who took this information from another post of mine neglects to realize a lot of stuff does not work in this gps.conf file he supplied. They wanted to be a hero stealing research and post references and post it here like it was a solution. First of all, it comes from another phone not a Nexus. Secondly, I posted it just to sort of show people an example of how complicated a gps.conf could be and what I weeded out to get it working on my Nexus. Here is my gps.conf for you so you can see the lines that I stripped out of it that I know work. Of course you will have to update it to reflect your country. Hope it helps you.
I may have a few other lines to add but I want to give it another day or so and go over my results before I pass it on to others. When I am done my testing I will put up a new post for people. For now this should do you fine. Just update the servers, follow the same order.
gps.conf
NTP_SERVER=0.ca.pool.ntp.org
NTP_SERVER=1.ca.pool.ntp.org
NTP_SERVER=2.ca.pool.ntp.org
NTP_SERVER=3.ca.pool.ntp.org
NTP_SERVER=ca.pool.ntp.org
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin
# DEBUG LEVELS:
# 0 - none, 1 - Error,
# 2 - Warning, 3 - Info
# 4 - Debug, 5 - Verbose
DEBUG_LEVEL =0
ACCURACY_THRES=5
INTERMEDIATE_POS=0
ENABLE_WIPER=1
SUPL_HOST=supl.google.com
SUPL_PORT=7276
REPORT_POSITION_USE_SUPL_REFLOC=1
Click to expand...
Click to collapse
where would you be posting it. so i could look out for it.
There has been a flashable .zip for US users for months now posted on Rootzwiki. Mitch's Optimal GPS Settings.
Here is a link to the original thread
http://rootzwiki.com/topic/21453-optimal-gps-settings-for-galaxy-nexus/
All credit to Mitch. I attached a link to the flashable .zip file in this post. No need to edit anything, it just works.
Funny. I tried mitch's before and I don't seem to remember it working for me...
I know these GPS Fixes but I want to know one thing:
I live in Finland but I'm Estonian so I'm not always in Finland.. So can it be edited like adding 2 country names and 2 region names (different region and country), does it mess something up or not?
I don't usually use any "GPS fixes" because in Estonia I can receive the GPS signal in 3 minutes at day, at night something in 6 minutes, but in Finland I have have to wait almost 15 minutes to get GPS signal so then I have to put 3G on to receive the GPS signal faster..
LexusBrian400 said:
There has been a flashable .zip for US users for months now posted on Rootzwiki. Mitch's Optimal GPS Settings.
Here is a link to the original thread
http://rootzwiki.com/topic/21453-optimal-gps-settings-for-galaxy-nexus/
All credit to Mitch. I attached a link to the flashable .zip file in this post. No need to edit anything, it just works.
Click to expand...
Click to collapse
Mitch settings didn't worked for me, I tried several times.
I have read all the posts till now but noone reporting if this works or not... Feedback please !
Edit: You don't have to change this value through gps.conf. I thing it is quicker and easier to do it through fasterGps
To Flukester :
Are you sure about these values ? :
ACCURACY_THRES=5
INTERMEDIATE_POS=0
On mine (i took some frome here, yours and Mitch's) i have "Accuracy_thres=3000" and "Intermediate_pos=1".
JB
I have an AT&T Samsung Galaxy S3 with two problems at hand.
First of all, my GPS does not lock onto any sattelites at all. I've come to realize that this is related to an incorrect configuration file. As far as I know, a # at the beginning of a statement means that that statement is a remark, and not actual code. Thus, it's ignored.
If you look at my gps.conf file below, you will notice that many of the lines contain a # at the beginning. I have a general idea of which should remain. However, I'd like to know all those of which should/can be removed. If someone could just rewrite it removing all the # which should not be included, that would be awesome!
Code:
#Test
NTP_SERVER=time.gpsonextra.net
#Asia
# NTP_SERVER=asia.pool.ntp.org
#Europe
# NTP_SERVER=europe.pool.ntp.org
#North America
# NTP_SERVER=north-america.pool.ntp.org
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra2.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra2.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra2.bin
# DEBUG LEVELS: 0 - none, 1 - Error, 2 - Warning, 3 - Info
# 4 - Debug, 5 - Verbose
DEBUG_LEVEL = 4
# Intermediate position report, 1=enable, 0=disable
INTERMEDIATE_POS=0
# supl version 1.0
SUPL_VER=0x10000
# Error Estimate
# _SET = 1
# _CLEAR = 0
ERR_ESTIMATE=0
# GPS Capabilities bit mask
# SCHEDULING = 1
# MSB = 2
# MSA = 4
# ULP = 0x20
# ON_DEMAND_TIME = 0x10 // yunu.lee
# default = MSA | MSB | SCHEDULING | ULP
CAPABILITIES=0x16
# Accuracy threshold for intermediate positions
# less accurate positions are ignored, 0 for passing all positions
# ACCURACY_THRES=5000
################################
##### AGPS server settings #####
################################
# FOR SUPL SUPPORT, set the following
# SUPL_HOST=supl.google.com
# SUPL_PORT=7276
# FOR C2K PDE SUPPORT, set the following
# C2K_HOST=c2k.pde.com or IP
# C2K_PORT=1234
################################
# Sensor Settings
################################
# Needs to be set explicitly based on sensor
# There is no default value.
GYRO_BIAS_RANDOM_WALK=0.00001
SENSOR_ACCEL_BATCHES_PER_SEC=3
SENSOR_ACCEL_SAMPLES_PER_BATCH=5
SENSOR_GYRO_BATCHES_PER_SEC=3
SENSOR_GYRO_SAMPLES_PER_BATCH=5
# Sensor Control Mode (0=AUTO, 1=FORCE_ON)
SENSOR_CONTROL_MODE=0
# Enable or Disable Sensors for GPS use (0=Enable, 1=Disable)
SENSOR_USAGE=0
# Choose GSIFF sensor provider (1=DSPS, 2=Android NDK)
SENSOR_PROVIDER=2
################################
# Indoor Positioning Settings
################################
# 0: QUIPC disabled, 1: QUIPC enabled, 2: forced QUIPC only
QUIPC_ENABLED = 0
################################
# EXTRA SETTINGS
################################
My second problem has to do with the power_profile.xml file. It was noted that certain S3s had a problem with an incorrect value in the power_profile.xml file, which resulted in Cell Standby topping the list for battery drainage. I have taken a look at that file on my S3, and noticed that I am affected by that incorrect value (34 instead of 3.4).
The problem is that the fixed XML file available for download seems slightly different to the one currently in my S3, in more ways than just that value. I'd like to know whether it's safe to make the switch. Or, does anyone have a fixed power_profile.xml which they wish to share with me, that definitely works on the AT&T S3?
I'm sorry if this has been posted before, but I wasn't able to find anything completely answering my questions. Thanks in advance for the help, and it's much appreciated!
My second problem has to do with the power_profile.xml file.
Click to expand...
Click to collapse
You probably downloaded the XML file like I initially did...and for the same reason...I did NOT want to replace it. But this much smaller flashable CWM fix only changes the VALUE in question...not the whole XML file....as far as I can tell. It has worked for my on my i747m for months. Do a CWM backup first!
themadproducer said:
You probably downloaded the XML file like I initially did...and for the same reason...I did NOT want to replace it. But this much smaller flashable CWM fix only changes the VALUE in question...not the whole XML file....as far as I can tell. It has worked for my on my i747m for months. Do a CWM backup first!
Click to expand...
Click to collapse
Actually, that is the same fix I downloaded. I extracted it just to take a look at it first before doing anything, and noticed that inside, it had a power_profile.xml slightly different to the one currently in my phone. So, I'm not sure whether to flash this or not. Or alternatively, is there any way which I can simply edit this file myself? I've tried several XML editors, but they all show weird symbols throughout, when I open that XML file. Though I can clearly see the value that I need to change, but I don't want to end up saving the file from a program that can't properly read it, ending up with a corrupt file flashed to my phone. Unless, that is how the file actually looks.
Sorry for all the noobish questions, but I have only had my S3 and been on Android for a couple of months now. Was on iOS before, and did a lot of tinkering on that side of the smartphone world.
.Xanadu. said:
Actually, that is the same fix I downloaded. I extracted it just to take a look at it first before doing anything, and noticed that inside, it had a power_profile.xml slightly different to the one currently in my phone. So, I'm not sure whether to flash this or not. Or alternatively, is there any way which I can simply edit this file myself? I've tried several XML editors, but they all show weird symbols throughout, when I open that XML file. Though I can clearly see the value that I need to change, but I don't want to end up saving the file from a program that can't properly read it, ending up with a corrupt file flashed to my phone. Unless, that is how the file actually looks.
Sorry for all the noobish questions, but I have only had my S3 and been on Android for a couple of months now. Was on iOS before, and did a lot of tinkering on that side of the smartphone world.
Click to expand...
Click to collapse
Ok, i will compare tomorrow...and let you know.
themadproducer said:
Ok, i will compare tomorrow...and let you know.
Click to expand...
Click to collapse
Thanks mucho! Much appreciated.
If you could also send me/share your gps.conf file so I can compare it with mine, that would be great! As I believe in addition to many lines being set as a remark, there are several lines also missing within there, such as for AGPS.
.Xanadu. said:
Thanks mucho! Much appreciated.
If you could also send me/share your gps.conf file so I can compare it with mine, that would be great! As I believe in addition to many lines being set as a remark, there are several lines also missing within there, such as for AGPS.
Click to expand...
Click to collapse
For starters, here is my gps.conf file.
There is only one area with slight differences but they are commented out with the # sign so it's irrelevant.
I have the i747m Rogers and you have AT&T. They should be pretty close with most core OS contents...as is this file.
I am assuming you are on Stock ICS? (not JB or custom)
Humor me...download Ulysse Gizmos 1.6.2 and use this to try to lock into sats. Test from outside OR inside but touching a window.
Stay tuned for XML.
PS...Xanadu....name from Rush by any chance?
UPDATE: Upload your stock power_profile.xml file (upload it) and I will check it against mine.
I just compared the FIXED one for the i9300....with my Stock i747m version and the only change is the value 34 to 3.4.
That's why it worked perfectly for me and probably will be EXACTLY the same for you.
Well that's interesting. Our gps.conf files are exactly the same. So, what could be the problem? I'm baffled.
Maybe I should also throw in that I'm using an unlocked AT&T Samsung Galaxy S III outside of the states. I'm in the Caribbean to be exact, if that makes any difference. (?)
I'll also try that app which you mentioned and report back.
As for my power_profile.xml, it's included below for comparison. Thanks!
.Xanadu. said:
Well that's interesting. Our gps.conf files are exactly the same. So, what could be the problem? I'm baffled.
Maybe I should also throw in that I'm using an unlocked AT&T Samsung Galaxy S III outside of the states. I'm in the Caribbean to be exact, if that makes any difference. (?)
I'll also try that app which you mentioned and report back.
As for my power_profile.xml, it's included below for comparison. Thanks!
Click to expand...
Click to collapse
Yes your location could be a huge reason.
You probably need to modify gps.conf for where you are.
When I was running my HD2, I had to do that to optimize the GPS,
but in your case...it's probably even more important.
Look around for an XDA page that focuses on the GPS ZONES for your area.
Start HERE. You may just want to extract certain elements and place them into your gps.conf file as needed.
UPDATE: your power_profile.xml is identical to mine. So go ahead and flash the CWM standby fix. ALWAYS do a CWM backup first!!!
themadproducer said:
Yes your location could be a huge reason.
You probably need to modify gps.conf for where you are.
When I was running my HD2, I had to do that to optimize the GPS,
but in your case...it's probably even more important.
Look around for an XDA page that focuses on the GPS ZONES for your area.
Start HERE. You may just want to extract certain elements and place them into your gps.conf file as needed.
UPDATE: your power_profile.xml is identical to mine. So go ahead and flash the CWM standby fix. ALWAYS do a CWM backup first!!!
Click to expand...
Click to collapse
Thanks for the help! I'll have a look at adding in the GPS zones for my area. I'll also go ahead with flashing the power_profile.xml and report back on how it went.
http://forum.xda-developers.com/showpost.php?p=40207546&postcount=67
Download this files and place it in /system/etc .... permission it to rw r r
then delete all files in /data/gps folder
restart and use gpstest to see results. try it with data on on first try to fix the satellite faster.
popcorn1122 said:
http://forum.xda-developers.com/showpost.php?p=40207546&postcount=67
Download this files and place it in /system/etc .... permission it to rw r r
then delete all files in /data/gps folder
restart and use gpstest to see results. try it with data on on first try to fix the satellite faster.
Click to expand...
Click to collapse
How do I set the permissions? I tried copying and it gave me error saying cannot copy system file. I tried setting the permissions using Root Explorer but didnt work
Use file manager from the google play and go to settings and then slect mount root.
u need to have root before doing this
{
"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"
}
Nebula Rises Again
[Features Coming-Soon]
Available Flavours:
Standard : Close to stock but with CAF updates and some minor additional stuff giving a balanced profile. Uses stock pnp manager and thermal engine.
Advanced : CAF Kernel with added basic HTC stuff. Uses custom thermal engine providing a performance profile. Added with sound mods and updates from higher 4.4 kernels.
EAS: Energy Aware Scheduler- Very intelligent kernel developed by linaro. Decides the frequencies and idle efficiently for smooth experience with great battery life.
Known Bugs: (Work Arounds)
Sound Mod: While playing Music, Switch off/on BoomSound
XDA:DevDB Information
Nebula Kernel, Kernel for the HTC 10
Contributors
Eliminater74, thewalkingdude, indian-mafia
Source Code: https://github.com/DevHTC10/htc10.pme.msm8996.kernel
Kernel Special Features:
Version Information
Status: Beta
Current Stable Version: 7.1.0
Current Beta Version: 7.0.0
Created 2016-09-07
Last Updated 2017-03-25
Downloads:
Downloads
Source: UM 5.5 C1/R1: Android N
Nebula: [Standard Downloads]
Nebula: [Advanced Downloads]
Nebula: [Public Testing Downloads]
Extra's:
@Freak07, Has been kind enough to create a few scripts that are heavy tuned to nebula Kernel only.
Post-826
Post-796
Remember to thank this guy for his hard work...
This was posted with his Permission:
NFO:
Features:
Extra I/O schedulers: BFQ, FIOPS, SOI, FIFO, SIOPLUS, TRIPNDROID, VR, ZEN
Overclock up to 2265MHz big cluster and 1728MHz little cluster
GPU Overclock 133 up to 652mhz
GPU: Full Pixel's GPU Drivers
Sound Control mod that allows users to adjust digital audio gains
Backlight Dimmer
Button Light Notification
KCAL Color Control
Double Tap Fingerprint To Sleep
Fading/Pulsating Notification LED
Sweep2Sleep
Optional Disable FSYNC
Optional Disable magnetic cover
Home button Mapper
Various patches and fixes
[ Features And Additions ]
IOSCHEDS: Added
bfq-iosched
fiops-iosched
sio-iosched
fifo-iosched
sioplus-iosched
tripndroid-iosched
vr-iosched
zen-iosched
GOVS: Added
impulse
elementalx
cpufreq_zzmoove
CPU-Boost
Overclock able
Sound Control By @GuneetAtwal, Modifications by @Eliminater74 to get it to work for HTC, @flar2 for intial modifications
Early Queue Merge (EQM) to BFQ-v7r7 for 3.18.0
Support USB Keyboard
Expose PVS Level visa sys
sys kernel interface to configure linux printk logging
Expose GPU used frequency statistics in a new sysfs (New Condensed Version)
lcd notifier
Notification LED control - V1.1b
msm_adreno_tz: add adrenoboost parameter By @tbalden
homebutton: add sysfs enable and vib_strength
homebutton: make visible to apps
mdss mdp: kcal for htc 10 (pme) Porting By @flar2 And or @tbalden
backlight dimmer
HomeButton: Press to Wake/Sleep By: @tbalden
Many more.. Will Finish later.. as well as more credits......
Thank You To The Following:
@INDIAN-MAfIA <--- Helped so much with this project
@flar2
@buckmarble
@tbalden
@franciscofranco
@Sultanxda
@squid2 (sultanqasim)
@shminer
@osm0sis
@neobuddy89
@Alucard24
@Myself5
@andip71
@RenderBroken
@myfluxi
@dorimanx
@frap129
@Cl3Kener
@nvertigo (First person to teach me to Build roms)
@Chainfire
@Tasssadar
@nkk71
@Captain_Throwback
@ZeroInfinity (Even know we had out Differences)
@Mostafa Wael (same as above)
Proper Way To Report a Bug: [/CENTER]
There are several apps that can do this process for you, Here is one: PlayStore: SysLog
And here is another: PlayStore: Andy Log (ROOT)
ramopps: is an oops/panic logger that writes its logs to RAM before the system
crashes. It works by logging oopses and panics in a circular buffer. Ramoops
needs a system with persistent RAM so that the content of that area can
survive after a restart.
logcat: the logoutput of the Android system
kernel log: (kmsg / dmesg): the kernel messages
Additionally there's the last_kmsg which is a dump of the kernel log until the last shutdown.
radio log: the log outpur ot your System / BB / RIL communication
4
ramopps: Some Documentation on Ramopps
Normal Logcat:
Code:
adb logcat -v time -d > logcat.log
Radio Logcat:
Code:
adb logcat -b radio -v time -d > logcat_radio.log
Ramoops:
Code:
adb shell su -c cat /sys/fs/pstore/console-ramoops > kmsg.txt
Kernel Log:
Code:
adb shell su -c dmesg > dmesg.log
Last_Kmsg: NOTE:
New location of last_kmsg on Android 6.0 and above: /sys/fs/pstore/console-ramoops
Code:
adb shell su -c "cat /proc/last_kmsg" > last_kmsg.log
NOTES:
-v time will include timestamps in the logcats
-d will export the complete log.
If you want to save a continuous log you can remove the -d parameter - then you need to cancel the logging process via CTRL+C.
To export a continuous kernel log use adb shell su -c "cat /proc/kmsg" > dmesg.log (and cancel it via CTRL+C again).
PS: This Document was taked from another XDA Thread Called: [Reference] How to get useful logs
URL: http://forum.xda-developers.com/showthread.php?t=2185929
Also check this one out: [Tutorial] How To Logcat
I only Revived it a bit for ramopps.
I will update this more at a later time..
[DMESG Help Commands]
Code:
Usage:
dmesg [options]
Display or control the kernel ring buffer.
Options:
-C, --clear clear the kernel ring buffer
-c, --read-clear read and clear all messages
-D, --console-off disable printing messages to console
-E, --console-on enable printing messages to console
-F, --file <file> use the file instead of the kernel log buffer
-f, --facility <list> restrict output to defined facilities
-H, --human human readable output
-k, --kernel display kernel messages
-L, --color[=<when>] colorize messages (auto, always or never)
colors are enabled by default
-l, --level <list> restrict output to defined levels
-n, --console-level <level> set level of messages printed to console
-P, --nopager do not pipe output into a pager
-r, --raw print the raw message buffer
-S, --syslog force to use syslog(2) rather than /dev/kmsg
-s, --buffer-size <size> buffer size to query the kernel ring buffer
-u, --userspace display userspace messages
-w, --follow wait for new messages
-x, --decode decode facility and level to readable string
-d, --show-delta show time delta between printed messages
-e, --reltime show local time and time delta in readable format
-T, --ctime show human readable timestamp (may be inaccurate!)
-t, --notime don't print messages timestamp
--time-format <format> show time stamp using format:
[delta|reltime|ctime|notime|iso]
Suspending/resume will make ctime and iso timestamps inaccurate.
-h, --help display this help and exit
-V, --version output version information and exit
Supported log facilities:
kern - kernel messages
user - random user-level messages
mail - mail system
daemon - system daemons
auth - security/authorization messages
syslog - messages generated internally by syslogd
lpr - line printer subsystem
news - network news subsystem
Supported log levels (priorities):
emerg - system is unusable
alert - action must be taken immediately
crit - critical conditions
err - error conditions
warn - warning conditions
notice - normal but significant condition
info - informational
debug - debug-level messages
[LOGCAT Help Commands]
Code:
Usage: logcat [options] [filterspecs]
options include:
-s Set default filter to silent.
Like specifying filterspec '*:S'
-f <filename> Log to file. Default is stdout
-r <kbytes> Rotate log every kbytes. Requires -f
-n <count> Sets max number of rotated logs to <count>, default 4
-v <format> Sets the log print format, where <format> is:
brief color long printable process raw tag thread
threadtime time usec
-D print dividers between each log buffer
-c clear (flush) the entire log and exit
-d dump the log and then exit (don't block)
-t <count> print only the most recent <count> lines (implies -d)
-t '<time>' print most recent lines since specified time (implies -d)
-T <count> print only the most recent <count> lines (does not imply -d)
-T '<time>' print most recent lines since specified time (not imply -d)
count is pure numerical, time is 'MM-DD hh:mm:ss.mmm'
-g get the size of the log's ring buffer and exit
-L dump logs from prior to last reboot
-b <buffer> Request alternate ring buffer, 'main', 'system', 'radio',
'events', 'crash' or 'all'. Multiple -b parameters are
allowed and results are interleaved. The default is
-b main -b system -b crash.
-B output the log in binary.
-S output statistics.
-G <size> set size of log ring buffer, may suffix with K or M.
-p print prune white and ~black list. Service is specified as
UID, UID/PID or /PID. Weighed for quicker pruning if prefix
with ~, otherwise weighed for longevity if unadorned. All
other pruning activity is oldest first. Special case ~!
represents an automatic quicker pruning for the noisiest
UID as determined by the current statistics.
-P '<list> ...' set prune white and ~black list, using same format as
printed above. Must be quoted.
filterspecs are a series of
<tag>[:priority]
where <tag> is a log component tag (or * for all) and priority is:
V Verbose (default for <tag>)
D Debug (default for '*')
I Info
W Warn
E Error
F Fatal
S Silent (suppress all output)
'*' by itself means '*:D' and <tag> by itself means <tag>:V.
If no '*' filterspec or -s on command line, all filter defaults to '*:V'.
eg: '*:S <tag>' prints only <tag>, '<tag>:S' suppresses all <tag> log messages.
If not specified on the command line, filterspec is set from ANDROID_LOG_TAGS.
If not specified with -v on command line, format is set from ANDROID_PRINTF_LOG
or defaults to "threadtime"
Is this gonna be for stock roms?
Nice to see another Kernel for our beloved 10
Keep up mate.
#PowerOf10
reserved
Not sure what blue is lol.its nice to see you here on htc 10 and look forward to trying your kernel.
Welcome and you'll always have a sprint tester here. You can always get a hold of me here or on Google+. Nice to see you back in the drivers seat. :good:
Hey,
Great to see another kernel in development.
I'm currently running a cm based ROM and would be happy to test to see if it works (based on your comments in the second post).
More choice is always good for the community
gillim74 said:
Not sure what blue is lol.its nice to see you here on htc 10 and look forward to trying your kernel.
Click to expand...
Click to collapse
Blue is dev talk for BlueTooth.
jmkarnai01 said:
Welcome and you'll always have a sprint tester here. You can always get a hold of me here or on Google+. Nice to see you back in the drivers seat. :good:
Click to expand...
Click to collapse
I will keep that in mind... I havent even added the sprint dtsi files just yet.... But im getting there.
rav101 said:
Hey,
Great to see another kernel in development.
I'm currently running a cm based ROM and would be happy to test to see if it works (based on your comments in the second post).
More choice is always good for the community
Click to expand...
Click to collapse
I currently have a build now, its running on my device as I type this. But I like to run things on my device for a while
before I feel conferrable enough to release it to the public. Memory Leaks can take up to 3 days before they are noticed.........
I will prob request a few HTC 10 owners that wish to do some testing for me. But them users will have to be willing to join a hangouts group channel
with me, so that I can get instant feedback and send out tests quicker.
One thing people must understand about me, I go for performance.. Stable is a must too.. but Me personally am willing to Risk a fraction of Stableness to gain the performance that
I want. But my key factors are, Temp Control and Speed all while keeping stable enough not to destroy anything..
If anyone remembers me from the LG G3 Threads, I manged to get the G3 clocked up to 3 ghrz stable all the while keeping the temps down to idle 82f and Max active at 120f..
at 3ghrz running though aututu bench marking.. Run all the way though with no issues. LG's are known for heat issues.. So that is my #1 priority..
Also another big thing for me with kernels are options...... I believe a user of his device should have full control over how the kernel runs..
So I try and add as many sysfs options allowing total control of kernel. Now some options are not in any app.. and I dont feel like coding another kernel app..
But since the new Kernel Adiutor allows adding commands to its settings, you can add in the missing options...........
I know my current build running on my device now, allows the CPU Big: to sleep at 92% while the CPU Little: to sleep at 60%.
My personal fav Gov outside the default interactive is zzmoove....
Well enough for now.. Just giving a little nfo on what to expect from me.............
you can also check out my other threads from the G3 and V10 area to see what kinda work I do on kernels..
Nice!
Sent from my HTC 10 using XDA-Developers mobile app
To be fair,
I hardly tax my phone so I might not be the best tester for you but happy to help if you want.
Running European Unlocked phone and preferably will be using CM. Will check out your other dev threads to see about your work
Eliminater74 said:
If anyone remembers me from the LG G3 Threads, I manged to get the G3 clocked up to 3 ghrz stable all the while keeping the temps down to idle 82f and Max active at 120f..
at 3ghrz running though aututu bench marking.. Run all the way though with no issues. LG's are known for heat issues.. So that is my #1 priority..
Click to expand...
Click to collapse
Well you're perfect here xD The HTC10 loves to get really hot and then throttles down.
I'm totally up for putting my 10 back in the Freezer and run some Benchmarks at 3ghz or more^^
Haldi4803 said:
Well you're perfect here xD The HTC10 loves to get really hot and then throttles down.
I'm totally up for putting my 10 back in the Freezer and run some Benchmarks at 3ghz or more^^
Click to expand...
Click to collapse
Its near impossible to run the msm8996 at 3ghrz, Qualcomm lowerd the frq rates cause its 64bit and no need for the higher freq settings.
I am almost positive we can reach 2.0/2.4 which is what the 8996pro aka SnapDragon 821 reaches......
The 821 is just a highly optimized 820....... I study the Dif between them both and see nothing other then coding update.
but when you compare 820 cpu to the 821 cpu, its near identical...........
But the 3ghrz days are over... that was with a 32bit device..........
Nice, i miss some gov's and wish me zzmove and much more Settings like I/O Scheduling i come from the LG G2 and Lord @dorimanx have done a good job for the Device!
I can test on verizon for you
NFO_caution: Ok peepz, I am originally from the LG Threads for the G3 and V10, The HTC Scene is pretty new to me, Before I dug into Kernel Development for the HTC, I did a little
research and testing.. I have T-Mobile Device, My HTC 10 was De-branded and converted to US Unlocked version.... Yes im S-off,
Anyhow, From what I gather, Most devices are now on the 1.9x rom base.. So your device should work, If it doesnt. Then, I am sorry. I dont wanna create back ports on kernels....
This is early testing stages... Use at your own RISK................
I will list all features and more soon................
PS: Yes I added the sprint dtsi files..........
hmm, anyone else get a corrupted external sd card using this kernel?
{
"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"
}
Nebula Strikes Again
What is EAS?
Energy Aware Scheduling (EAS) is an enhancement to Linux power management, unifying CPU power control under the Linux kernel. EAS extends the Linux kernel scheduler to make it fully aware of the power/performance capabilities of the CPUs in the system, to optimize energy consumption for advanced multi-core SoCs including big.LITTLE. With EAS, the Linux kernel will use the task load and a CPU ‘Energy Model’ to control task placement to select the optimal CPU to run on.
[ Features And Additions ]
CPU governors: SCHED, SCHEDUTIL *NEW*
Extra I/O schedulers: BFQ, FIOPS, SIO, FIFO, SIOPLUS, TRIPNDROID, VR, ZEN, MAPLE
Overclock up to 2265MHz big cluster and 1728MHz little cluster
GPU Overclock 133Mhz up to 652Mhz
Sound Control mod that allows users to adjust digital audio gains
Backlight Dimmer
Button Light Notification
KCAL Color Control
Double Tap Fingerprint To Sleep and Sweep To Sleep
Fading/Pulsating Notification LED
Sweep2Sleep
Optional Disable FSYNC
Optional Disable magnetic cover
Home button Mapper
USB FastCharge
Various patches and fixes
Updated with the latest from CAF branch LA.UM.5.5.r1-xxxxx-8x96.0 and EAS from Google's experimental branch.
And Various Other Features...
Known Bugs: (Work Arounds)
Sound Mod: While playing Music, Switch off/on BoomSound
SD Card corruption:
[Untested Fix]
Reboot back to recovery
Mount USB storage
Unmout it
Reboot
[Tested Fix]
Flash the last kernel that worked
Reboot
Flash the latest again
Reboot
XDA:DevDB Information
Nebula: Energy Aware Scheduling, Kernel for the HTC 10
Contributors
Eliminater74, thewalkingdude, INDIAN-MAfIA, prstorero
Source Code: https://github.com/DevHTC10/htc10.pme.msm8996.kernel
Kernel Special Features: Energy Aware Scheduling [EAS]
Version Information
Status: Beta
Created 2017-02-06
Last Updated 2017-09-20
Downloads:
Nebula: EAS: DOWNLOADS
EMPTY
Extra's:
NOTE: @Freak07 Was kind enough to tweak out the init.nebula.rc scripts..
Reserved
reserved 11
Reserved 434
Thank You To The Following: @INDIAN-MAfIA <--- Helped so much with this project
@flar2
@buckmarble
@tbalden
@franciscofranco
@Sultanxda
@squid2 (sultanqasim)
@shminer
@osm0sis
@neobuddy89
@Alucard24
@Myself5
@andip71
@RenderBroken
@myfluxi
@dorimanx
@frap129
@Cl3Kener
@nvertigo (First person to teach me to Build roms)
@Chainfire
@Tasssadar
@nkk71
@Captain_Throwback
@ZeroInfinity (Even know we had out Differences)
@Mostafa Wael (same as above)
Proper Way To Report a Bug: [/CENTER]
There are several apps that can do this process for you, Here is one: PlayStore: SysLog
And here is another: PlayStore: Andy Log (ROOT)
ramopps: is an oops/panic logger that writes its logs to RAM before the system
crashes. It works by logging oopses and panics in a circular buffer. Ramoops
needs a system with persistent RAM so that the content of that area can
survive after a restart.
logcat: the logoutput of the Android system
kernel log: (kmsg / dmesg): the kernel messages
Additionally there's the last_kmsg which is a dump of the kernel log until the last shutdown.
radio log: the log outpur ot your System / BB / RIL communication
4
ramopps: Some Documentation on Ramopps
Normal Logcat:
Code:
adb logcat -v time -d > logcat.log
Radio Logcat:
Code:
adb logcat -b radio -v time -d > logcat_radio.log
Ramoops:
Code:
adb shell su -c cat /sys/fs/pstore/console-ramoops > kmsg.txt
Kernel Log:
Code:
adb shell su -c dmesg > dmesg.log
Last_Kmsg: NOTE:
New location of last_kmsg on Android 6.0 and above: /sys/fs/pstore/console-ramoops
Code:
adb shell su -c "cat /proc/last_kmsg" > last_kmsg.log
NOTES:
-v time will include timestamps in the logcats
-d will export the complete log.
If you want to save a continuous log you can remove the -d parameter - then you need to cancel the logging process via CTRL+C.
To export a continuous kernel log use adb shell su -c "cat /proc/kmsg" > dmesg.log (and cancel it via CTRL+C again).
PS: This Document was taked from another XDA Thread Called: [Reference] How to get useful logs
URL: http://forum.xda-developers.com/showthread.php?t=2185929
Also check this one out: [Tutorial] How To Logcat
I only Revived it a bit for ramopps.
I will update this more at a later time..
[DMESG Help Commands]
Code:
Usage:
dmesg [options]
Display or control the kernel ring buffer.
Options:
-C, --clear clear the kernel ring buffer
-c, --read-clear read and clear all messages
-D, --console-off disable printing messages to console
-E, --console-on enable printing messages to console
-F, --file <file> use the file instead of the kernel log buffer
-f, --facility <list> restrict output to defined facilities
-H, --human human readable output
-k, --kernel display kernel messages
-L, --color[=<when>] colorize messages (auto, always or never)
colors are enabled by default
-l, --level <list> restrict output to defined levels
-n, --console-level <level> set level of messages printed to console
-P, --nopager do not pipe output into a pager
-r, --raw print the raw message buffer
-S, --syslog force to use syslog(2) rather than /dev/kmsg
-s, --buffer-size <size> buffer size to query the kernel ring buffer
-u, --userspace display userspace messages
-w, --follow wait for new messages
-x, --decode decode facility and level to readable string
-d, --show-delta show time delta between printed messages
-e, --reltime show local time and time delta in readable format
-T, --ctime show human readable timestamp (may be inaccurate!)
-t, --notime don't print messages timestamp
--time-format <format> show time stamp using format:
[delta|reltime|ctime|notime|iso]
Suspending/resume will make ctime and iso timestamps inaccurate.
-h, --help display this help and exit
-V, --version output version information and exit
Supported log facilities:
kern - kernel messages
user - random user-level messages
mail - mail system
daemon - system daemons
auth - security/authorization messages
syslog - messages generated internally by syslogd
lpr - line printer subsystem
news - network news subsystem
Supported log levels (priorities):
emerg - system is unusable
alert - action must be taken immediately
crit - critical conditions
err - error conditions
warn - warning conditions
notice - normal but significant condition
info - informational
debug - debug-level messages
[LOGCAT Help Commands]
Code:
Usage: logcat [options] [filterspecs]
options include:
-s Set default filter to silent.
Like specifying filterspec '*:S'
-f <filename> Log to file. Default is stdout
-r <kbytes> Rotate log every kbytes. Requires -f
-n <count> Sets max number of rotated logs to <count>, default 4
-v <format> Sets the log print format, where <format> is:
brief color long printable process raw tag thread
threadtime time usec
-D print dividers between each log buffer
-c clear (flush) the entire log and exit
-d dump the log and then exit (don't block)
-t <count> print only the most recent <count> lines (implies -d)
-t '<time>' print most recent lines since specified time (implies -d)
-T <count> print only the most recent <count> lines (does not imply -d)
-T '<time>' print most recent lines since specified time (not imply -d)
count is pure numerical, time is 'MM-DD hh:mm:ss.mmm'
-g get the size of the log's ring buffer and exit
-L dump logs from prior to last reboot
-b <buffer> Request alternate ring buffer, 'main', 'system', 'radio',
'events', 'crash' or 'all'. Multiple -b parameters are
allowed and results are interleaved. The default is
-b main -b system -b crash.
-B output the log in binary.
-S output statistics.
-G <size> set size of log ring buffer, may suffix with K or M.
-p print prune white and ~black list. Service is specified as
UID, UID/PID or /PID. Weighed for quicker pruning if prefix
with ~, otherwise weighed for longevity if unadorned. All
other pruning activity is oldest first. Special case ~!
represents an automatic quicker pruning for the noisiest
UID as determined by the current statistics.
-P '<list> ...' set prune white and ~black list, using same format as
printed above. Must be quoted.
filterspecs are a series of
<tag>[:priority]
where <tag> is a log component tag (or * for all) and priority is:
V Verbose (default for <tag>)
D Debug (default for '*')
I Info
W Warn
E Error
F Fatal
S Silent (suppress all output)
'*' by itself means '*:D' and <tag> by itself means <tag>:V.
If no '*' filterspec or -s on command line, all filter defaults to '*:V'.
eg: '*:S <tag>' prints only <tag>, '<tag>:S' suppresses all <tag> log messages.
If not specified on the command line, filterspec is set from ANDROID_LOG_TAGS.
If not specified with -v on command line, format is set from ANDROID_PRINTF_LOG
or defaults to "threadtime"
reserved 5
First post!
NFO NEWS: V7.2.2 is accessible from here as well as the others.
I will clean it up as I can.. I am doing 50 things at once here.. and this part is the most pain in the butt of it all...........
V7.3.0 Is in the works.................................................... Its finished for the most part.. but doing some testing to make sure its stable before I push it up............
Please bare with me on this thread................
Thank you all..
Teaser. ?
TheKnux said:
Teaser. ?
Click to expand...
Click to collapse
Well it boots
How does it perform?
The concept of a simple power-performance tunable that is wholly scheduler
centric is implemented by patches [01-04].
This is where we introduce a ‘global task boosting’ knob which is integrated
with schedutil to allow the scheduler to bias OPP selection. These first 5
patches allow to dynamically tune schedutil up to the point where it behaves
like the existing ‘performance’ governor.
Patches [05-07] extend the basic mechanism to use different boost values for
different tasks. This allows informed runtimes (e.g. Android and ChromeOS) to
feed the scheduler with information related to their knowledge about the
specific demand of different tasks and/or use-cases.
Thanks to SchedTune’s defined interface, the scheduler is now able to collect
simple yet powerful information about tasks: how much the user cares about
their performance.
Although it can be argued that something similar is already provided by the
existing concept of task priority, we believe that the proposed interface is
much more generic and can be further extended to support both OPP selection and
task placement, thus leading in the future to a more comprehensive energy-aware
scheduler driven solution.
These patches enable schedutil to service interactive workloads like touch
screen interaction. Only out of tree cpufreq governors like the Interactive
governor were thus far able to service such use cases.
The last patch in the series introduces the concept of ‘negative boosting’.
Negative boosting is beneficial for mobile devices in scenarios where it is
desired to intentionally reduce the performance of a task by running it at a
lower frequency than the one selected by schedutil.
For certain tasks, like compute intensive background operations or memory
bounded tasks, negative boosting can have measurable energy-saving benefits.
In these cases, a negative SchedTune value allows to bias schedutil towards the
selection of a lower OPP. Importantly, this can be achieved using the same
SchedTune interface.
This patch allows to dynamically tune schedutil up to the point where it
effectively replaces the “powersave” governor.
The patches are based on tip/sched/core:
a225023 - sched/core: Explain sleep/wakeup in a better way
For testing purposes an integration branch, providing the required dependencies
as well as a set of debugging tracepoints, is available here:
git://www.linux-arm.com/linux-pb eas/stune/rfcv2
Test results
============
Extensive testing of the proposed solution has already been done as SchedTune
is shipping on a production mobile device, with benefits observed for key
use-cases (e.g. improved responsiveness and performance of key workloads).
The following synthetic focused tests are used to show functional benefits and
report overheads. All these tests have been performed on an HiKey board, an
octa-core (ARM CortexA53 @1.2GHz) SMP platform, running a Debian image on a
mainline kernel and using schedutil configured with a 1ms rate limit value.
Performance boosting validation
-------------------------------
The functional validation of the boost mechanism has been performed considering
a ramp task generated using the rt-app provided by the LISA testing suite [2].
The ramp is configured as a 16ms periodic task which increases its utilization
by 5% every second, starting from 5% up to 60%. The task is pinned to run on a
single CPU and executed with different boost values:
0%, 15%, 30%, 60% and -100%.
The following table reports:
- the value used to boost the task in each experiment
- the rt-app’s reported performance index:
PerfIndex Avg (the higher the better)
which expresses the average time left from completion of a task
activation (i.e. a fixed amount of work) until its next activation
- the CPU average frequency (FreqAvg)
- the actual boost measured for the PerfIndex and FreqAvg
Boost PerfIndex Actual FreqAvg Actual
value Avg Std Boost [MHz] Boost
0 0.53 0.12 0% 606 0%
15 0.61 0.07 17% 658 9%
30 0.68 0.07 26% 739 22%
60 0.71 0.05 40% 852 41%
-100 -98.84 120.00 -2K% 363 -36%
For positive boost values, SchedTune can improve the performance of a task
(i.e. its time to completion) by a quantity which is proportional to the boost
value. This is reported by the increasingly higher values of the PerfIndex Avg
as well as the average frequencies used to execute the task.
For negative boost values the performance is progressively reduced, in the
reported case of -100% boost we verified that the system runs most of its time
at one of the lowest OPPs (thus providing a behavior similar to the powersave
governor) while still running at higher OPPs when other (not negative boosted)
tasks needs to run. That’s why the reported average frequency (363MHz) is
slightly higher than the minimum OPP (208MHz).
A graphical representation of the task’s behaviors at different boost values
and the corresponding CPUs frequencies is available here:
https://gist.github.com/derkling/8be0a8ac365c935b3df585cb24afec6c
Impact on scheduler performance
-------------------------------
Performance impact has been evaluated using the hackbench test provided by perf
with this command line:
perf bench sched messaging --thread --group 25 --loop 1000
Reported completion times (CTime) in seconds are averages over 10 runs:
| | SchedTune (per-task) boost value |
| Schedutil | 0% | 10% | 90% |
------------------+-----------+------------+------------+------------+
CTime | 12.93 | 13.08 | 13.32 | 13.27 |
vs Schedutil [%] | | 1.1% | 3.0% | 2.7% |
SchedTune currently introduces overheads when used on saturated systems such as
the one generated by running the hackbench test. This is possibly due to the
currently used locking schema which can be further optimized.
On the other hand, the SchedTune extension is mainly useful for lightly loaded
systems (mobile devices, laptops, etc.) where the additional overhead has been
verified to be compensated by the performance benefits due to (for example) a
faster task completion. Some of these benefits are reported in the following
section.
ChangeLog
=========
Changes since v1:
- Rebase on tip/sched/core:
A225023 sched/core: Explain sleep/wakeup in a better way
- Integrated with schedutil (in replacement of SchedFreq)
- Improved tasks accounting for correct boostgroups activations
- Added support for negative boosting
- Extensively tested on production-grade devices
Credits
=======
[*] This work has been supported by an extensive collaborative effort between
ARM, Linaro and Google, targeting production devices.
Ufff extensive and intensive
Can`t wait to try it out.
TheKnux said:
Teaser. ?
Click to expand...
Click to collapse
Holy C$$$$!! :good:
As much as i would like to understand, i cant.. I work in the hospital so i i dont have a background.. Hands down to eliminater74, really..
Lite thread cleaning.
I know there will be sides when it comes to development teams but out of respect for everyone involved. Keep the drama off XDA. This includes subtle jabs at each other, or just plain calling out. This will be the only warning as we have already gave out enough warnings to everyone.
Thanks
Wolf
grega_slo said:
Well it boots
How does it perform?
Click to expand...
Click to collapse
And camera works. still waiting for everything to settle, finally got my charge cycle in last night while I was sleeping, so don't know the exact results yet. Amazing so far. Way quicker and more efficient than the old EAS, that's for sure. But, a public version will probably be out soon, so my results wouldn't matter anymore since this is a test build.
Excited to try it out.
Holy.....
Looks like SchedUtil has quite a bit of tuning to get it working as expected.