[Q] cm10 gps not lock possible solution - Galaxy Note GT-N7000 Q&A, Help & Troubleshooting

Hi
I'm on official cm10
Direct Download: cm-10-20121103-NIGHTLY-n7000.zip
md5sum: 9242491e8b694aebea44b27ad9634363
Short URL: http://get.cm/get/4BB
Click to expand...
Click to collapse
& my gps not lock satellites after fresh install (full wipe).
In gps test 4 min just 2 or 3 satellites but not fixed (gps signal not "on")
my gps.conf have not good config.
I tried this solution:
rename
Code:
/data/gps/gldata.sto
to
Code:
/data/gps/gldata.sto.back
Change gps.conf in
Code:
/system/etc/gps.conf
Example for Fr:
Code:
NTP_SERVER=fr.pool.ntp.org
NTP_SERVER=1.fr.pool.ntp.org
NTP_SERVER=2.fr.pool.ntp.org
NTP_SERVER=3.fr.pool.ntp.org
XTRA_SERVER_1=0.europe.pool.ntp.org
XTRA_SERVER_2=1.europe.pool.ntp.org
XTRA_SERVER_3=2.europe.pool.ntp.org
XTRA_SERVER_4=http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_5=http://xtra2.gpsonextra.net/xtra.bin
ACCURACY_THRES=80
SUPL_PORT=7276
SUPL_HOST=supl.google.com
For north usa:
Code:
NTP_SERVER=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
XTRA_SERVER_1=0.us.pool.ntp.org
XTRA_SERVER_2=1.us.pool.ntp.org
XTRA_SERVER_3=2.us.pool.ntp.org
XTRA_SERVER_4=http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_5=http://xtra2.gpsonextra.net/xtra.bin
ACCURACY_THRES=80
SUPL_PORT=7276
SUPL_HOST=supl.google.com
Reboot in recovery wipe dalvik-cache
reboot normally
open gps-test app the first run is long (gldata.sto is recreated with another contents)
& now it's work

Related

Wanting to Personalize my G1

Hi guys. Just wondering if anyone can help me. What i want to do is in the 'About Phone' section in 'Settings' i want to make the following changes if possible:
Model Number - change to Peter Griffin G1
Firware Version - 2.6
Mod Version - 9.2
Build Number - 1
I know it may sound a bit silly/stubid but itd be awesome if i could actually do tnat
Thanks in advance
ps im running Herver's 1.1.1 eclair build (its the best at the minute)
If you have adb setup this can easily be done
The information can be found in 1 or 2 files:
build.prop or build.trout.prop
use adb to pull these files as such
Code:
adb pull /system/build.prop /location/you/want/your/file (enter)
adb pull /system/build.trout.prop /location/you/want/your file (enter)
open the files in a txt editor, and look for the relevant fields based on the information already displayed on your phone, if your MOD Version is xROM-Eclair****** like mine or whatever it may say simply use ctrl+f to find that field in the txt editor and modify it. Once you've made all the relevant edits push the files back
Code:
adb push /location/of/file /system/build.prop (enter)
adb push /location/of/file /system/build.trout.prop (enter)
Then reboot your phone
Sorry to bother you again but is this correct :
# begin build properties
# autogenerated by buildinfo.sh
ro.build.version.sdk=7
ro.build.version.codename=AOSP
ro.build.version.release=2.1
ro.build.type=eng
ro.build.user=ctso
ro.build.host=h0meb0x
ro.build.tags=test-keys
ro.wifi.channels=
rild.libpath=/system/lib/libhtc_ril.so
wifi.interface = tiwlan0
# Time between scans in seconds. Keep it high to minimize battery drain.
# This only affects the case in which there are remembered access points,
# but none are in range.
wifi.supplicant_scan_interval = 140
# density in DPI of the LCD of this board. This is used to scale the UI
# appropriately. If this property is not defined, the default value is 160 dpi.
ro.sf.lcd_density = 160
# Default network type
# 0 => WCDMA Preferred.
ro.telephony.default_network = 0
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.url.legal=http://www.google.com/intl/%s/mobile/android/android-dev-phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/android-dev-phone-privacy.html
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=true
ro.ril.hsxpa=1
ro.com.google.locationfeatures=1
ro.ril.gprsclass=10
ro.product.multi_touch_enabled=true
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
ro.com.google.clientidbase=android-tmobile
net.bt.name=Android
ro.config.sync=yes
dalvik.vm.stack-trace-file=/data/anr/traces.txt
#
# RIL Hacks - Thanks Amon_RA
#
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 = 5
ro.modversion= #1
ro.ModelNumber= The Peter Griffin G1
ro.FirmwareVersion= 2.6
ro.BuildNumber= 1
Click to expand...
Click to collapse
push and reboot, to find out, keep a backup of your originals just incase
I was gonna say you should get a phone skin from Zagg or unique skins.
Thanks dude. I finally managed it this morning. Ended up having to change bits in both files
PS Im defo gonna try and get a Peter Griffin skin for my G1

How to compile Kernel

What you need:
1) Download file in attachment
2) Have a working adb-(windows|mac|linux)
3) A linux os (i used debian!)
I take some scripts (like H-repack and H-unpak from http://wiki.cyanogenmod.com)
I get arm compiler from google git
Let's start!
BUILD KERNEL
1) Download from here http://developer.htc.com/ legend's kernel source
2) Decompress, modify and configure it! (you could use the default .config i extracted from my running kernel)
3) Copy boot.img into the AndroidKernelBuilder folder
4) Enter in AndroidKernelBuilder and run my script
./compiler.sh /path/of/the/kernel/source/
5) wait
Now you have your own kernel repacked and ready to be flashed!
INSTALL
1) copy boot_repacked.img to /sdcard/
2) reboot in recovery
3) adb-linux shell
(from now inside the shell)
# mount /sdcard/
# cat /dev/zero > /dev/mtd/mtd2
# flash_image boot /sdcard/boot_repacked.img
# reboot
Now keep all the fingers you can crossed! (and sorry for all the errors i may have done)
http://www.4shared.com/file/dKJH5kJP/AndroidKernelBuildertar.html
You are the man!
In the week end i'll try to compile by myself.

gps.conf file help

Hi,
can someone please post the original gps.conf file that comes with the Incredible S? I tried to do the gps fix but it seems to not be working (not locking at all) so I want to change it back but I forgot to make a copy of the original file.
for reference - this is what I changed to file to:
NTP_SERVER=asia.pool.ntp.org
NTP_SERVER=0.asia.pool.ntp.org
NTP_SERVER=1.asia.pool.ntp.org
NTP_SERVER=2.asia.pool.ntp.org
NTP_SERVER=3.asia.pool.ntp.org
NTP_SERVER=sg.pool.ntp.org
NTP_SERVER=2.sg.pool.ntp.org
NTP_SERVER=1.asia.pool.ntp.org
NTP_SERVER=3.asia.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
# 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
I'm not sure why it isn't working. I used Astro file manager to go into the original gps file and edited it to say the above, then rebooted, then used the GPS Status tool to try and lock (reset it then downloaded). The tool did not get a lock at all. Then I went to maps and it's moderately accurate but I think it's using cell towers instead of the gps (600 meter accuracy).
so yea, I just want to change it back - I'm sure there's something I'm doing wrong but it's not a huge issue.
EDIT: Also, is there a reason the gps file shows up as a txt file in Astro instead of a conf file?
EDIT 2: Ok weird - I went back into the file and it is like it was originally with no change. I'm not sure why this is. I went to Astro - File Editor - Pasted in the text above in place of the existing file > saved > rebooted...etc. Can't figure it out. The GPS status tool cannot get a lock anyway though - it's been like 5 minutes
Install gps test app from market
Reboot phone and run
If no fix then reset agps and download agps from within the app
Worked for me
Edit..astro doesn't write to system partition I don't think ,try root explore it es explorer (free..set mount on options ) .. to change
your gps.config file
You're rooted right?
Sent from my HTC Incredible S using XDA App
ibrahimh said:
Install gps test app from market
Reboot phone and run
If no fix then reset agps and download agps from within the app
Worked for me
Edit..astro doesn't write to system partition I don't think ,try root explore it es explorer (free..set mount on options ) .. to change
your gps.config file
You're rooted right?
Sent from my HTC Incredible S using XDA App
Click to expand...
Click to collapse
Yea I'm rooted - I tried using ES but it wouldn't let me go higher than SD card so I couldn't get to the file. Anyway I just installed fasterfix and it seems to help so I'll just stick with that. thanks for your response
in case someone needs it here is the original gps.conf
Code:
NTP_SERVER=europe.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
SUPL_HOST=supl.google.com
SUPL_PORT=7276
thanks, good for reference in case I mess this up again

Building CyanogenMod for Samsung Galaxy Note 10.1 N8000 (GSM)

I am building CyanogenMod for my Samsung Galaxy Note 10.1 N8000. Here is the guide.
When I typed
Code:
breakfast n8000
, the output was as follows.
Code:
including vendor/cm/vendorsetup.sh
ls: cannot access device/*/n8000/cm.mk: No such file or directory
build/core/product_config.mk:233: *** Can not locate config makefile for product "cm_n8000". Stop.
Device n8000 not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Traceback (most recent call last):
File "build/tools/roomservice.py", line 76, in <module>
result = json.loads(urllib.request.urlopen(githubreq).read().decode())
File "/usr/lib/python2.7/urllib2.py", line 126, in urlopen
return _opener.open(url, data, timeout)
File "/usr/lib/python2.7/urllib2.py", line 406, in open
response = meth(req, response)
File "/usr/lib/python2.7/urllib2.py", line 519, in http_response
'http', request, response, code, msg, hdrs)
File "/usr/lib/python2.7/urllib2.py", line 444, in error
return self._call_chain(*args)
File "/usr/lib/python2.7/urllib2.py", line 378, in _call_chain
result = func(*args)
File "/usr/lib/python2.7/urllib2.py", line 527, in http_error_default
raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
urllib2.HTTPError: HTTP Error 403: Forbidden
ls: cannot access device/*/n8000/cm.mk: No such file or directory
build/core/product_config.mk:233: *** Can not locate config makefile for product "cm_n8000". Stop.
** Don't have a product spec for: 'cm_n8000'
** Do you have the right repo manifest?
I executed breakfast without a device as the guide suggests.
If you do not put a device, the script will output a list of available devices to build for (limited to those CM builds nightlies for, which isn't necessarily complete), and you can then choose yours.
Click to expand...
Click to collapse
And there was nothing containing n8000
Code:
including vendor/cm/vendorsetup.sh
You're building on Linux
Breakfast menu... pick a combo:
1. full-eng 19. cm_e980-userdebug 37. cm_jfltexx-userdebug 55. cm_serranoltexx-userdebug
2. cm_apexqtmo-userdebug 20. cm_evita-userdebug 38. cm_m7att-userdebug 56. cm_skyrocket-userdebug
3. cm_captivatemtd-userdebug 21. cm_exhilarate-userdebug 39. cm_m7spr-userdebug 57. cm_superior-userdebug
4. cm_crespo-userdebug 22. cm_flo-userdebug 40. cm_m7tmo-userdebug 58. cm_t0lte-userdebug
5. cm_d2att-userdebug 23. cm_galaxysbmtd-userdebug 41. cm_m7ul-userdebug 59. cm_tilapia-userdebug
6. cm_d2cri-userdebug 24. cm_galaxysmtd-userdebug 42. cm_m7vzw-userdebug 60. cm_toroplus-userdebug
7. cm_d2mtr-userdebug 25. cm_grouper-userdebug 43. cm_maguro-userdebug 61. cm_toro-userdebug
8. cm_d2spr-userdebug 26. cm_hammerhead-userdebug 44. cm_mako-userdebug 62. cm_tsubasa-userdebug
9. cm_d2tmo-userdebug 27. cm_hercules-userdebug 45. cm_manta-userdebug 63. cm_ville-userdebug
10. cm_d2usc-userdebug 28. cm_i9300-userdebug 46. cm_mb886-userdebug 64. cm_vs980-userdebug
11. cm_d2vzw-userdebug 29. cm_jflteatt-userdebug 47. cm_mint-userdebug 65. cm_xt897-userdebug
12. cm_d800-userdebug 30. cm_jfltecan-userdebug 48. cm_odin-userdebug 66. cm_xt897c-userdebug
13. cm_d801-userdebug 31. cm_jfltecri-userdebug 49. cm_otter-userdebug 67. cm_xt907-userdebug
14. cm_d802-userdebug 32. cm_jfltecsp-userdebug 50. cm_otter2-userdebug 68. cm_xt925-userdebug
15. cm_deb-userdebug 33. cm_jfltespr-userdebug 51. cm_p1-userdebug 69. cm_xt926-userdebug
16. cm_dlx-userdebug 34. cm_jfltetmo-userdebug 52. cm_pollux-userdebug 70. cm_yuga-userdebug
17. cm_dogo-userdebug 35. cm_jflteusc-userdebug 53. cm_pollux_windy-userdebug
18. cm_e975-userdebug 36. cm_jfltevzw-userdebug 54. cm_serrano3gxx-userdebug
... and don't forget the bacon!
Which would you like? [aosp_arm-eng]
Then I tried lunch
It’s used EXACTLY like breakfast, the only difference being the choices you have to build with it, and how it configures the device. Using lunch, you can choose non-official or non-standard builds for your device
Click to expand...
Click to collapse
The output was the same.
There is nothing about N8000 again.
Has anybody built CyanogenMod Android for Samsung Galaxy Note 10.1 N8000 successfully?
Have you included the 8013 as well I believe the only difference is the cellular radio file which I believe can be added for your device?
tubas..... tubas everywhere....
n8000 only has cm-10.2 and I'm guessing you're trying to build cm-11.
mamenyaka said:
n8000 only has cm-10.2 and I'm guessing you're trying to build cm-11.
Click to expand...
Click to collapse
I ran
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.2
So the version I'm trying building is 10.2
Red Planet said:
I ran
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.2
So the version I'm trying building is 10.2
Click to expand...
Click to collapse
Then you have to manually add the n8000 repos.
Look at this file: https://github.com/mamenyaka/android/blob/phablet-saucy/local_manifest_samsung.xml
and use appropriate CM repos and branches. Place file in .repo/local_manifests/

[GUIDE] [HOW-TO] [4.0-4.4] [CM9/10/10.1/10.2/11] [ICS/JB/KK] PORTING ROMs'

This is guide that deals with porting ROM's [4.0-4.4] in 9 SIMPLE STEPS!
What type of ROM can i port using this GUIDE?
Any ROM (except Stock/manufacturer based)
ROMs' from similar devices
From same Resolution devices
What do I need??
A machine to work on. Duh!
BASE & PORT ROMs
Notepad++(if on windows)
Special ingrediant
What is BASE Rom:
The ROM which is Developed For your Mobile..​
What is PORT Rom:
The Rom Which you want to port to your Device.
just keep checking all ROM's from the forum and find one of your choice that you would like to port to your device.​
So now we have a BASE and a PORT ROM.
Next we need a Machine to work on(but obvious) (I'd be using a Win 7 PC here)
Lets Start!
Step 1:
Take ANY clean AOSP/CM ROM , which has been developed for your device as BASE ROM.
And the ROM you want to port as PORT ROM
Extract both of them, and name the folders appropriately.
It should look like this now.
{
"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"
}
​
Step 2 : Delete app, font, framework, media [and priv-app if porting Kitkat].
​Step 3: Copy app, font, framework, media [and priv-app if porting Kitkat] from PORT to BASE folder.
​
NOTE: If You find any extra file or folder in system folder of PORT ROM than copy them to your base rom system folder.
Step 4: Open etc in both PORT & BASE.
Step 5: Open init.d folder and
**Delete all files except 00banner from BASE.
**Copy all files from PORT except 00banner to BASE.
Step 6: Open Permissions in both BASE & PORT
**Copy all files{EXCEPT platform.xml and handheld_core_hardware.xml} from PORT to BASE
​
Step 7: Get to the build.prop and open both in notepad++
replace following line from PORT to BASE.
ro.config.ringtone=
ro.config.notification_sound=
ro.config.alarm_alert=
Click to expand...
Click to collapse
Also copy any other lines or tweaks you find in build.prop like this one
You can edit the following to what you wish or leave them as they are.
ro.build.id=
ro.build.display.id=
ro.build.date=
ro.modversion=
Click to expand...
Click to collapse
Step 8: Open both ROMs' updator-script
(get to them by going to >>> BASE/PORT folder > Meta-inf > com > google > android > here)
and delete all the lines setting permissions {set_perm() or set_metadata()} from BASE updator-script
Copy all set_perm()/set_metadata() lines from PORT to BASE updator-script.Save it !
>>> As a precaution you can check the file/folder name in set_metadata/set_perm lines exists in your BASE ROM or not, for instance SEMC devices do not have a firmware folder in vendor and if you set permission for a file/folder that does not exist in your ROM then probably you would be getting a Status 6 error while flashing.
IF YOU ARE HAVING BOOTLOOP THEN COPY THESE LIB FILES TO BASE ROM FROM PORT ROM:
libandroid_runtime.so
libandroid_servers.so
libmedia_jni.so
Click to expand...
Click to collapse
Step 9:
If you are porting ROM's which have features like say, Xperia Walkman, then those apps have their dependencies too.
So copy all unique files(which are only in PORT folder) from following folders of PORT to appropriate Folders of BASE:
lib
etc
bin
Now just zip the BASE folder flash it and post it! ​
IF YOUR BASE ROM HAS ISSUES THEN YOUR PORTED ROM TOO WILL HAVE ISSUES.
DON'T FORGET TO GIVE CREDITS TO THE DEVELOPER OF PORT ROM..
IF IT HELPED YOU THAN PRESS THANKS AND RATE THIS POST 5 STARS...
Cheers
The Guide is based on @rishabh.raj37 's Guide.
All credit for the Guide goes to him
Second and third posts are also from the original thread.
Click to expand...
Click to collapse
How to logcat?
Many of you are having problems while porting and I know that those problems cannot be solved simply by guesswork..
There is a solution to find the problems which are causing BOOTLOOPS OR OTHER PROBLEMS IN YOUR PORT ROM..
The SOLUTION IS TO TAKE A LOGCAT..
LOGCAT ARE OF TWO TYPES:
In your Phone(if the ROM is booting)
Through adb(if you are stuck in bootloop)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
In your Phone:
There are two ways to take LOGCAT in mobile:
FIRST WAY--THROUGH APPS WHICH ARE MADE TO TAKE LOGCAT:
There are two apps which you can use to take a LOGCAT..
They are aLogcat or Catlog.
Taking logcat through apps is very easy.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
SECOND WAY--THROUGH TERMINAL EMULATOR
SEE THE INSTRUCTIONS BELOW TO TAKE A LOGCAT THROUGH adb
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
HOW TO MAKE PC READY FOR LOGCAT?
IN WINDOWS:
Download Android SDK From Here
Install or Extract it to your desired Directory..
You also need to install Java JDK.
Download it here
In the Guide, we are taking C: as the Root Directory and android as the main Folder
Navigate to Android SDK folder and open 'SDK Manager.exe'
Only check 'Android SDK Tools' and 'Android SDK Platform-tools'
First connect the device via USB to your computer
Be sure to have USB debugging enabled
Now Navigate to C:/Android/android-sdk/platform-tools/
Now Open a Command Prompt there By holding Shift+Right Click Button
Click to expand...
Click to collapse
IN LINUX:
IMPORTANT: If someone has a 64bit linux then they need to download 32-bit libs
for this, before all these steps run this:
Code:
sudo apt-get install ia32-libs
Make sure that you have Android-SDK and JDK downloaded on your PC
If you have not installed them, Android SDK from here and Java JDK in this way:
Code:
sudo add-apt-repository ppa:ferramroberto/java
sudo apt-get update
sudo apt-get install sun-java6-jdk sun-java6-jre sun-java6-plugin
OR
$ sudo add-apt-repository ppa:sun-java-community-team/sun-java6
$ sudo apt-get update
$ sudo apt-get install sun-java6-jre sun-java6-bin sun-java6-jdk
OR You Can Simply Do This: (Credits to @Androguide.fr)
This process saves a lot of storage. It uses the Ubuntu Touch ppa:
Code:
sudo add-apt-repository ppa:phablet-team/tools
sudo apt-get install android-tools-adb
You can also install fastboot in the same fashion:
Code:
sudo apt-get install android-tools-fastboot
Then follow the Below Instructions Carefully:
Make a new directory by this command in terminal:
Code:
mkdir android
Then extract the downloaded SDK by
Code:
tar -zxvf ~/Downloads/android-sdk_r21.0.1-linux.tgz
Then move it to the directory we just made
Code:
mv android-sdk-linux ~/android/sdk
Then open android sdk manager by
Code:
android/sdk/tools/android
This will open Android sdk manager. Just select android sdk tools and android sdk platform tools for adb and then select install packages
Go into your Home folder and Press CTRL+H (This is done to show hidden folders and files)
Look for the file '.bashrc'
Open it and put the following or similar:
Code:
export PATH=$PATH:~/android/sdk
export PATH=$PATH:~/android/sdk/platform-tools
export PATH=$PATH:~/android/sdk/tools
You will need to add something for any devices to be recognized:
Open terminal(Ctrl+alt+T) and enter:
Code:
sudo gedit /etc/udev/rules.d/51-android.rules
Enter the following in the file:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="0502", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="413c", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0489", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="091E", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="12d1", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0482", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0955", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="10A9", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="04dd", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="19D2", MODE="0666"
Now save and close the file, and in terminal enter:
Code:
sudo chmod +x /etc/udev/rules.d/51-android.rules
Now Type:
Code:
sudo gedit /etc/rc.local
This will open a file
now add the line mentioned below just above where it is written exit 0
Code:
/home/user/android/sdk/platform-tools/adb start-server
"Enter your username in place of user"
After this we don't need to cd to adb directory..We just have to type adb devices and the phone will surely show up.
Now that everything is installed
Open terminal and type:
Code:
android
android
Or, if it doesnt work
Code:
cd ~/android/sdk/tools
./android
Click to expand...
Click to collapse
HOW TO TAKE LOGCAT?
To verify that the device is connected Type:
Code:
adb devices
Now type:
Code:
adb logcat > logcat.txt
The LOGCAT will be Saved in the logcat.txt File
You can also type:
Code:
adb logcat -f logcat.txt
or
Code:
adb logcat -v long > logcat.txt
With the -v flag & the long argument, it changes output to long style, which means every line of logcat will be on its own line (makes it a little neater, imo)
Note: When outputting to a file, you will see a newline, but nothing printed, this is normal. To stop logcat from writting to a file, you need to press ctrl+c.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Meanings of symbols in a logcat !
You usually see this at the start of a sentence in logcat .
I/> ===> Information
S/> ===> Silent
D/> ===> Debug
W/> ===> Warning
E/> ===> Error
F/> ===> Fatal
Click to expand...
Click to collapse
Click to expand...
Click to collapse
CREDITS:
blahbl4hblah
paxChristos
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Build.prop and Updater-Script Terminology and Guide to Edit it
Thanks to @ rishabh.raj37
Standard build.prop properties
Please read the hashed out lines : It is selfexplanatory.
So the normal build properties start with:
Code:
# begin build properties
# autogenerated by buildinfo.sh
This mentions that the build prop is built by build info shell script during the compilation of the ROM.
Code:
#First up the build id (Here JZO54K) is the build id for the version number for Jellybean 4.1.2
ro.build.id=JZO54K
#It is the version of the ROM which appears in the about phone. This is a cm10 build by sakindia123.
ro.build.display.id=cm_pico-userdebug 4.1.2 JZO54K eng.sakindia123.20121117.161006 test-keys
#This is the software development kit version which is needed and used for building the ROM.
ro.build.version.incremental=eng.sakindia123.20121117.161006
ro.build.version.sdk=16
#3's codename.
ro.build.version.codename=REL
#This is the android version of the ROM.
ro.build.version.release=4.1.2
#This is the time and date of when the ROM and Kernel were built together. (ROM only).
ro.build.date=Sat Nov 17 16:10:21 GMT 2012
#More details in the kernel.
ro.build.date.utc=1353168621
#Userdebug ROMs has usb debugging set to 0 and eng are for general release.
ro.build.type=userdebug
#Name of the person building the ROM & kernel.
ro.build.user=sakindia123
ro.build.host=build1
#Test keys suggests that the ROM is not an official version of the ROM. Release keys are for official releases.
ro.build.tags=test-keys
Click to expand...
Click to collapse
This part of the build prop shows the information about our phone and not the build of the ROM of our phone.
Code:
#Model of our device
ro.product.model=HTC Explorer A310e
#Brand of device. ( In some case carrier ) for which the android version has been made for.
ro.product.brand=htc_europe
#Name is an alternative ( codename ) of the device during its development. For Explorer its pico, for Nexus 7 : grouper for Nexus 4 : mako for SG Ace its cooper etc.
ro.product.name=pico
ro.product.device=pico
ro.product.board=pico
#It is the first instruction set (CPU + ABI convention type) of the code. Ours is an arm type arch cpu and abi version 7a )
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
#Name of manufacturer.
ro.product.manufacturer=HTC
#Language of the software ( read ROM)
ro.product.locale.language=en
#Region of operation of software.
ro.product.locale.region=US
ro.wifi.channels=
#Name of board on which software has been built.
ro.board.platform=msm7x27a
# ro.build.product is obsolete; use ro.product.device
ro.build.product=pico
# Do not try to parse ro.build.description or .fingerprint Never attempt to modify this value ! This can lead to bootloop (possibly hard brick) of your phone. This is the unique fingerprint of the software of your phone.
ro.build.description=cm_pico-userdebug 4.1.2 JZO54K eng.sakindia123.20121117.161006 test-keys
ro.build.fingerprint=htc_europe/htc_pico/pico:2.3.5/GRJ90/207463.1:user/release-keys
ro.build.characteristics=default
ro.cm.device=pico
# end build properties
#
Click to expand...
Click to collapse
System properties::
What is RIL?
A Radio Interface Layer (RIL) is a layer in an operating system which provides an interface to the hardware's radio and modem on e.g. a mobile phone.
Code:
#These are basically the links between your phones hardware and software , i.e. it tells your phone where to find the libs for RIL and also detects whether you have any arguments in place of the operation of your libs to provide to the vendor.
rild.libpath=/system/lib/libhtc_ril.so
rild.libargs=-d /dev/smd0
rilswitch.vendorlibpath=/system/lib/libhtc_ril.so
#
ril.subscription.types=NV,RUIM
#Architecture of baseband radio.
ro.baseband.arch = msm
#ro.ril.ecc.HTC-xxx=nnn,nnn,nnn
#These are basically the emergency call numbers(codes) for your phone. Its different according to your region. ( here xxx ) . The numbers can be 911 , 101,100 etc etc ( here nnn)
ro.ril.ecc.HTC-GCC=999,112,997
ro.ril.ecc.HTC-WWE=999
ro.ril.ecc.HTC-Dutch=112
ro.ril.ecc.HTC-SPA=112, 911,112, 911
ro.ril.ecc.HTC-FRA=112,911
ro.ril.ecc.HTC-ITA=112,911
ro.ril.ecc.HTC-EastEurope=112
#Something to do with GPRS, AFAIK.
ro.ril.enable.a52.HTC-ITA=1
ro.ril.enable.a53.HTC-ITA=1
ro.ril.enable.a52=0
ro.ril.enable.a53=1
#HSDPA category : High speed downlink packet access category. ( 8 == 7.2 mbit/s )
ro.ril.hsdpa.category=8
#HSXPA : High speed ( type ) packet . ( values 1- HSDPA 2-HSDPA/HSUPA ( High speed uplink packet access )
ro.ril.hsxpa=1
#Something to do with 3G.
ro.ril.fast.dormancy.rule=1
#
ro.ril.disable.fd.plmn.prefix=23402,23410,23411,23420,27202
#Ability of enabling data roaming.
ro.ril.enable.managed.roaming=1
#Class of GPRS network that needs to be routed to phone.
ro.ril.gprsclass=10
#No sim emergency call codes list
ro.ril.oem.nosim.ecclist=911,112,999,000,08,118,120,122,110,119,995
#
ro.ril.emc.mode=2
#This is somehow related to mobile data and its stablility. ( adding skipbrokendatacall adds stability ).
ro.telephony.ril.v3=signalstrength,singlepdp,skipbrokendatacall
#
ro.ril.htcmaskw1.bitmask = 4294967295
#
ro.ril.htcmaskw1 = 14449
#Related to ril audio.
ro.ril.update.acoustic.table = 1
#
ro.ril.avoid.pdp.overlap = 1
#Default type of data connection.
ro.telephony.default_network = 0
Click to expand...
Click to collapse
Wi-Fi Related:
Code:
# Time between scans in seconds. Keep it high to minimize battery drain.
# This only affects the case in which there are remembered access points,
# but none are in range.
wifi.supplicant_scan_interval=180
wifi.interface=eth0
wifi.softap.interface=eth0
Click to expand...
Click to collapse
Density(DPI) Related:
Code:
# density in DPI of the LCD of this board. This is used to scale the UI
# appropriately. If this property is not defined, the default value is 160 dpi.
ro.sf.lcd_density = 160
Display and OpenGLrelated
Code:
# View configuration for QVGA
view.fading_edge_length = 8
view.touch_slop = 15
view.minimum_fling_velocity = 25
view.scroll_friction = 0.008
Code:
# The OpenGL ES API level that is natively supported by this device.
# This is a 16.16 fixed point number
ro.opengles.version = 131072
Code:
# For no auto focus devices
ro.workaround.noautofocus = 1
# Increase SKIA decode memory capability for progressive jpg file
ro.media.dec.jpeg.memcap = 20000000
# For QC perf binary hooks
# src:vendor/qcom/proprietary/android-perf/release/lib/<CPU arch>/libqc-opt.so
ro.vendor.extension_library=/system/lib/libqc-opt.so
Additional Build Properties:
Code:
# Misc.
#There is a provision.apk in system/app requires this line.
DEVICE_PROVISIONED=1
#Enabling certain audio libs.
htc.audio.alc.enable = 1
htc.audio.swalt.enable = 1
#Least amount of RAM that can be given to any application to run.
dalvik.vm.heapsize=48m
#OpenGL 2.x.x
ro.opengles.version = 131072
#this is actually the software composition method. CAF suggests mdp for msm7x27a boards
debug.composition.7x27A.type=mdp
#media.stagefright is nothing but the type of media framework that is being supported and its various properties are in the build.prop. ( type of media playback : local media as well as online streaming like 3gp mpeg mp4 etc etc ).
media.stagefright.enable-player=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
media.stagefright.enable-fma2dp=true
media.stagefright.enable-aac=true
media.stagefright.enable-qcp=true
ro.use_data_netmgrd=true
persist.data.ds_fmc_app.mode=0
#It is the pixel format of RGB 565 with a constant value of 4
ro.staticwallpaper.pixelformat=RGB_565
#Something to do with app + data cache.
ro.max.fling_velocity=4000
#HTML Related.
httplive.enable.discontinuity=true
#Some thing with surface flinger hardware, aka our gpu.( probably framerate)
dev.pm.dyn_samplingrate=1
#Probably sampling rate of all media. ( Sound , picture quality etc etc . )
dev.pm.dyn_sample_period=700000
com.qc.hardware=true
#Something to do with the processes of above names.
com.qc.hdmi_out=false
#--
debug.camcorder.disablemeta=0
debug.qctwa.statusbar=1
debug.qctwa.preservebuf=1
debug.enabletr=false
#debug surface flinger hardware. One of the best known tweaks , i.e. GPU Hardware acceleration.
debug.sf.hw=1
#Encoding media quality (jpeg)
ro.media.enc.jpeg.quality=100
#Setupwizard ( google or otherwise ) enabling
ro.setupwizard.mode=OPTIONAL
#Related to Hardware acceleration settings
hwui.print_config=choice
hwui.disable_vsync=true
#By pass setup wizard.
ro.setupwizard.enable_bypass=1
#Media decoding of audio and video of wma and wmv formats respectively.
ro.media.dec.aud.wma.enabled=1
ro.media.dec.vid.wmv.enabled=1
#Sync enabled at bootup.
ro.config.sync=yes
#something to do with phone storage. ( probably install location .. not sure)
ro.phone_storage=0
#hardware platform. msm7x27a.
ro.hw_plat=7x27a
#Hwui
hwui.use.blacklist=true
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Original thread-
[REF] Build prop terminology [INFO]
Click to expand...
Click to collapse
Click to expand...
Click to collapse
CREDITS:
akshat.shenoy for his hard work
Click to expand...
Click to collapse
The Guide is based on @rishabh.raj37 's guide , complete credits go to him.
Moderators please feel free to move the thread if i posted in wrong section
Thanks
Awesome work dude!!!!
:good::good:
That's very interesting. I will give it a try when I have some time
Sent from my Xperia Z using Tapatalk

Categories

Resources