Related
Hi,
I've being watching all the developments about the emerging tablets and I must say that all Tegra 250 devices look very interesting, although Toshiba Folio 100 already has PCB pads to add more ram... I am sure that Toshiba will add more 500Mb ram on the next Folio to give a better android 2.3 support.
Anyway, here's my question: how can I, or anyone else, recompile the Linux android kernel for Tegra 250 and place it in the FolioMod, well, I'm asking this because I remembered that these tablets are excellent for one thing that many are forgetting...
To watch digital television from a USB TV pen, well, the device has USB host support, it has Linux to manage the devices attached... What else is need ? Video 4 Linux... This is kernel built-in... So, how can I recompile the kernel to add this and other desktop usual features ? Any cons ?
Cheers.
TiagoSilva said:
Hi,
I've being watching all the developments about the emerging tablets and I must say that all Tegra 250 devices look very interesting, although Toshiba Folio 100 already has PCB pads to add more ram... I am sure that Toshiba will add more 500Mb ram on the next Folio to give a better android 2.3 support.
Anyway, here's my question: how can I, or anyone else, recompile the Linux android kernel for Tegra 250 and place it in the FolioMod, well, I'm asking this because I remembered that these tablets are excellent for one thing that many are forgetting...
To watch digital television from a USB TV pen, well, the device has USB host support, it has Linux to manage the devices attached... What else is need ? Video 4 Linux... This is kernel built-in... So, how can I recompile the kernel to add this and other desktop usual features ? Any cons ?
Cheers.
Click to expand...
Click to collapse
I am interested in too, if you make any advance let me know; I am really interested in this!!!!
The process is quite straightforward.
Get the kernel source here: http://tegramid.com/wiki/Main_Page
- unzip the source and cd into the source directory
Get the current kernel config from your device:
Code:
adb pull /proc/config.gz
Unpack and rename the config file
Code:
gunzip config.gz
mv config .config
Adjust the config to your needs.
Now you need the an gcc to compile for arm, the easiest way is to checkout the android source repository (read source.android.com for instructions, actually you would only need the prebuilt toolchain)
Now add the compiler to your path environment variable
Code:
export PATH=<android-source-dir>/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/:$PATH
now you can build the kernel using
Code:
make ARCH=arm CROSS_COMPILE=arm-eabi-
Now you need to repack and flash your new kernel to the device.
An excellent article on how to prepare a new boot.img can be found here:
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
After that simply create an update.zip and flash using recovery.
Note, AFAIK v4l support is already included in the current FolioMod kernel.
WOW
Really thanks, I will try asap!!
Btw according to dmesg output kernel commandline should be:
Code:
[email protected] [email protected] vmalloc=192M video=tegrafb console=ttyS0,115200n8 usbcore.old_scheme_first=1 tegraboot=sdmmc tegrapart=recovery:122000:a00:800,linux:a0e00:1000:800,loader:300:400:800,mbr:700:200:800,system:900:20000:800,cache:20900:80000:800,misc:a0900:400:800,userdata:a1f00:80000:800 boardtype=PR
weeds2000:
So, the kernel is the common Android Tegra 250, have you tried this already ?
I though this could be the thing to do, but I also thought that Toshiba had pulled a fast one by customizing the Android Tegra 250 kernel...
Hum... If this is so, I will buy an Toshiba Folio 100 lol... I hope to add many thing to the kernel... as a programmer I would love to have USB-RS232 adapters too eh eh eh... New horizons then!
I was also thinking, if not this device, the Viewsonic Viewpad 10, that has a BIOS and an Atom, an x86 architecture then, would be much easier to recompile...
It has some modifications ore extra modules.
Compiling the default kernel from the froyo-tegra tree from nvidia failed (not sure what exactly was missing, display simply switched off and it seems there was a kernel panic somewhere)
But yes compiling the kernel from the sources given at the wiki works. I'm running a slightly modified kernel at the moment compiled using the steps given above.
weeds2000:
Its common on embedded devices like most Android devices... The best thing invented is the BIOS lol... Without one, we must hard-code the kernel to map the resources to the specific hardware...
Do you recommend buying a Toshiba Folio 100 ?
Anyway, what modifications have you done (just curious) ?
I would recommend the Folio to someone that can do some modding and is able to flash custom roms to the device.
Before FolioMod the device was pretty much useless to me, but with the modifications done by dexter and the rest of us, it turned out to be a pretty good device.
However I would not order it blind because of the display. Compared to, for example the Galaxy Tab, you can clearly see why the device is that cheap. Viewing angle is really not good on this, so you may want to take a look at a store or something if this bother you or not (it's OK for me though).
Kernel modifications where
- mouse driver (to fix the bug introduced by the rotation fix, without success up to now)
- playing around with the kernel hacking options to get some performance. turning them off however prevent the wifi module to load
- adding utf8 NLS support to the kernel (also this is the default, as this is required to mount NTFS partitions with utf8 support, otherwise some files where missing or have bad encoding and could not be opend by mediaplayer/reader/whatever.
When you do the make config, in the kernel options menu do you recall seeing the video4linux ?
I'm guessing that the tablet only needs that included on the built kernel to fire up TV watching programs, the idea is to load a USB digital TV device and run any Linux TV programs. Not going to MythTV because it might have too many dependencies... and not all libraries are available to ARM...
The view angle doesn't bother me that much, as long as the screen image is flawless eh eh eh, its a media tablet, so, it should be anyway...
One more thing, that key combination to flash the device comes already from factory right? I recall seeing a similar combination on the NVidea Tegra 250 development board. Or does it need the Dexter flasher too ?
I'm new to tablets as you can see lol and I'm seeing lots of tasty looking tablets... I want one that I can use for hack in my (I wish) free time, I guess its just like most people here lol.
The Viewpad 10 is about the same price, has x86 (single core tho) and more 500MB ram and ... a BIOS ... But has pros and cons... damn why can't we have it all... I guess I will try to see some in my hands first. iPad looks great, but lacks connectivity and Apple wants money for a developer membership lol... Android is incredibly but the vendors are crooks that embed the kernel with the hardware instead of adding a BIOS... Windows Mobile is... to limited and simple to use, no console... bah... Is there was one for free I would pick that one, but they all have similar prices... The reviews show that all have pros and cons... oh well...
OK getting mythTV on the device is quite an impressive task.
As not even the c-library is the default glibc known from your desktop PC and may miss a few things here and there. (learned that when trying to port libfuse and ntfs-3g)
To me it seems like v4l is included, this is the config from the multimedia section:
Code:
#
# Multimedia drivers
#
# CONFIG_MEDIA_ATTACH is not set
CONFIG_MEDIA_TUNER=y
# CONFIG_MEDIA_TUNER_CUSTOMISE is not set
CONFIG_MEDIA_TUNER_SIMPLE=y
CONFIG_MEDIA_TUNER_TDA8290=y
CONFIG_MEDIA_TUNER_TDA9887=y
CONFIG_MEDIA_TUNER_TEA5761=y
CONFIG_MEDIA_TUNER_TEA5767=y
CONFIG_MEDIA_TUNER_MT20XX=y
CONFIG_MEDIA_TUNER_XC2028=y
CONFIG_MEDIA_TUNER_XC5000=y
CONFIG_MEDIA_TUNER_MC44S803=y
CONFIG_VIDEO_V4L2=y
CONFIG_VIDEO_V4L1=y
CONFIG_VIDEO_CAPTURE_DRIVERS=y
# CONFIG_VIDEO_ADV_DEBUG is not set
# CONFIG_VIDEO_FIXED_MINOR_RANGES is not set
CONFIG_VIDEO_HELPER_CHIPS_AUTO=y
# CONFIG_VIDEO_VIVI is not set
# CONFIG_VIDEO_CPIA is not set
# CONFIG_VIDEO_CPIA2 is not set
# CONFIG_VIDEO_SAA5246A is not set
# CONFIG_VIDEO_SAA5249 is not set
# CONFIG_SOC_CAMERA is not set
CONFIG_V4L_USB_DRIVERS=y
CONFIG_USB_VIDEO_CLASS=y
CONFIG_USB_VIDEO_CLASS_INPUT_EVDEV=y
CONFIG_USB_GSPCA=m
# CONFIG_USB_M5602 is not set
# CONFIG_USB_STV06XX is not set
# CONFIG_USB_GL860 is not set
# CONFIG_USB_GSPCA_CONEX is not set
# CONFIG_USB_GSPCA_ETOMS is not set
# CONFIG_USB_GSPCA_FINEPIX is not set
# CONFIG_USB_GSPCA_JEILINJ is not set
# CONFIG_USB_GSPCA_MARS is not set
# CONFIG_USB_GSPCA_MR97310A is not set
# CONFIG_USB_GSPCA_OV519 is not set
# CONFIG_USB_GSPCA_OV534 is not set
# CONFIG_USB_GSPCA_PAC207 is not set
# CONFIG_USB_GSPCA_PAC7311 is not set
# CONFIG_USB_GSPCA_SN9C20X is not set
# CONFIG_USB_GSPCA_SONIXB is not set
# CONFIG_USB_GSPCA_SONIXJ is not set
# CONFIG_USB_GSPCA_SPCA500 is not set
# CONFIG_USB_GSPCA_SPCA501 is not set
# CONFIG_USB_GSPCA_SPCA505 is not set
# CONFIG_USB_GSPCA_SPCA506 is not set
# CONFIG_USB_GSPCA_SPCA508 is not set
# CONFIG_USB_GSPCA_SPCA561 is not set
# CONFIG_USB_GSPCA_SQ905 is not set
# CONFIG_USB_GSPCA_SQ905C is not set
# CONFIG_USB_GSPCA_STK014 is not set
# CONFIG_USB_GSPCA_SUNPLUS is not set
# CONFIG_USB_GSPCA_T613 is not set
# CONFIG_USB_GSPCA_TV8532 is not set
# CONFIG_USB_GSPCA_VC032X is not set
# CONFIG_USB_GSPCA_ZC3XX is not set
# CONFIG_VIDEO_PVRUSB2 is not set
# CONFIG_VIDEO_HDPVR is not set
# CONFIG_VIDEO_EM28XX is not set
# CONFIG_VIDEO_CX231XX is not set
# CONFIG_VIDEO_USBVISION is not set
# CONFIG_USB_VICAM is not set
# CONFIG_USB_IBMCAM is not set
# CONFIG_USB_KONICAWC is not set
# CONFIG_USB_QUICKCAM_MESSENGER is not set
# CONFIG_USB_ET61X251 is not set
# CONFIG_VIDEO_OVCAMCHIP is not set
# CONFIG_USB_OV511 is not set
# CONFIG_USB_SE401 is not set
# CONFIG_USB_SN9C102 is not set
# CONFIG_USB_STV680 is not set
# CONFIG_USB_ZC0301 is not set
# CONFIG_USB_PWC is not set
CONFIG_USB_PWC_INPUT_EVDEV=y
# CONFIG_USB_ZR364XX is not set
# CONFIG_USB_STKWEBCAM is not set
# CONFIG_USB_S2255 is not set
CONFIG_RADIO_ADAPTERS=y
# CONFIG_I2C_SI4713 is not set
# CONFIG_RADIO_SI4713 is not set
# CONFIG_USB_DSBR is not set
# CONFIG_RADIO_SI470X is not set
# CONFIG_USB_MR800 is not set
# CONFIG_RADIO_TEA5764 is not set
# CONFIG_DAB is not set
If you mean the Power+Vol UP key combination, this is factory default.
Screen itself is quite OK, watching Sintel or Big Buck Bunny was fun.
weeds2000 said:
OK getting mythTV on the device is quite an impressive task.
As not even the c-library is the default glibc known from your desktop PC and may miss a few things here and there. (learned that when trying to port libfuse and ntfs-3g)
To me it seems like v4l is included, this is the config from the multimedia section:
Code:
#
# Multimedia drivers
#
# CONFIG_MEDIA_ATTACH is not set
CONFIG_MEDIA_TUNER=y
# CONFIG_MEDIA_TUNER_CUSTOMISE is not set
CONFIG_MEDIA_TUNER_SIMPLE=y
CONFIG_MEDIA_TUNER_TDA8290=y
CONFIG_MEDIA_TUNER_TDA9887=y
CONFIG_MEDIA_TUNER_TEA5761=y
CONFIG_MEDIA_TUNER_TEA5767=y
CONFIG_MEDIA_TUNER_MT20XX=y
CONFIG_MEDIA_TUNER_XC2028=y
CONFIG_MEDIA_TUNER_XC5000=y
CONFIG_MEDIA_TUNER_MC44S803=y
CONFIG_VIDEO_V4L2=y
CONFIG_VIDEO_V4L1=y
CONFIG_VIDEO_CAPTURE_DRIVERS=y
# CONFIG_VIDEO_ADV_DEBUG is not set
# CONFIG_VIDEO_FIXED_MINOR_RANGES is not set
CONFIG_VIDEO_HELPER_CHIPS_AUTO=y
# CONFIG_VIDEO_VIVI is not set
# CONFIG_VIDEO_CPIA is not set
# CONFIG_VIDEO_CPIA2 is not set
# CONFIG_VIDEO_SAA5246A is not set
# CONFIG_VIDEO_SAA5249 is not set
# CONFIG_SOC_CAMERA is not set
CONFIG_V4L_USB_DRIVERS=y
CONFIG_USB_VIDEO_CLASS=y
CONFIG_USB_VIDEO_CLASS_INPUT_EVDEV=y
CONFIG_USB_GSPCA=m
# CONFIG_USB_M5602 is not set
# CONFIG_USB_STV06XX is not set
# CONFIG_USB_GL860 is not set
# CONFIG_USB_GSPCA_CONEX is not set
# CONFIG_USB_GSPCA_ETOMS is not set
# CONFIG_USB_GSPCA_FINEPIX is not set
# CONFIG_USB_GSPCA_JEILINJ is not set
# CONFIG_USB_GSPCA_MARS is not set
# CONFIG_USB_GSPCA_MR97310A is not set
# CONFIG_USB_GSPCA_OV519 is not set
# CONFIG_USB_GSPCA_OV534 is not set
# CONFIG_USB_GSPCA_PAC207 is not set
# CONFIG_USB_GSPCA_PAC7311 is not set
# CONFIG_USB_GSPCA_SN9C20X is not set
# CONFIG_USB_GSPCA_SONIXB is not set
# CONFIG_USB_GSPCA_SONIXJ is not set
# CONFIG_USB_GSPCA_SPCA500 is not set
# CONFIG_USB_GSPCA_SPCA501 is not set
# CONFIG_USB_GSPCA_SPCA505 is not set
# CONFIG_USB_GSPCA_SPCA506 is not set
# CONFIG_USB_GSPCA_SPCA508 is not set
# CONFIG_USB_GSPCA_SPCA561 is not set
# CONFIG_USB_GSPCA_SQ905 is not set
# CONFIG_USB_GSPCA_SQ905C is not set
# CONFIG_USB_GSPCA_STK014 is not set
# CONFIG_USB_GSPCA_SUNPLUS is not set
# CONFIG_USB_GSPCA_T613 is not set
# CONFIG_USB_GSPCA_TV8532 is not set
# CONFIG_USB_GSPCA_VC032X is not set
# CONFIG_USB_GSPCA_ZC3XX is not set
# CONFIG_VIDEO_PVRUSB2 is not set
# CONFIG_VIDEO_HDPVR is not set
# CONFIG_VIDEO_EM28XX is not set
# CONFIG_VIDEO_CX231XX is not set
# CONFIG_VIDEO_USBVISION is not set
# CONFIG_USB_VICAM is not set
# CONFIG_USB_IBMCAM is not set
# CONFIG_USB_KONICAWC is not set
# CONFIG_USB_QUICKCAM_MESSENGER is not set
# CONFIG_USB_ET61X251 is not set
# CONFIG_VIDEO_OVCAMCHIP is not set
# CONFIG_USB_OV511 is not set
# CONFIG_USB_SE401 is not set
# CONFIG_USB_SN9C102 is not set
# CONFIG_USB_STV680 is not set
# CONFIG_USB_ZC0301 is not set
# CONFIG_USB_PWC is not set
CONFIG_USB_PWC_INPUT_EVDEV=y
# CONFIG_USB_ZR364XX is not set
# CONFIG_USB_STKWEBCAM is not set
# CONFIG_USB_S2255 is not set
CONFIG_RADIO_ADAPTERS=y
# CONFIG_I2C_SI4713 is not set
# CONFIG_RADIO_SI4713 is not set
# CONFIG_USB_DSBR is not set
# CONFIG_RADIO_SI470X is not set
# CONFIG_USB_MR800 is not set
# CONFIG_RADIO_TEA5764 is not set
# CONFIG_DAB is not set
If you mean the Power+Vol UP key combination, this is factory default.
Screen itself is quite OK, watching Sintel or Big Buck Bunny was fun.
Click to expand...
Click to collapse
Whoa, CONFIG_MEDIA_TUNER and CONFIG_MEDIA_TUNER_SIMPLE on from default ?! Also V4L ?!?! what is going on here?! Is Toshiba thinking about making an docking station with a TV Tuner in it and a custom software to watch TV ?!
Edit: I was dreaming awake... I didn't noticed that you were writing about FolioMod kernel... But it would be fun if they did had added these features...
I used mythTV as an example LOL It has too much dependencies... I could try to get all the dependencies for ARM... or compile some for ARM... but it would take lots of time... TVTime looks better for Android, I'm off to see a real Folio 100 on my hands, I have lots of doubts LOL...
It also seems that radio was not forgotten, CONFIG_RADIO_ADAPTERS on... also a possible digital audio broadcast support... hum...
It could be fun if I or someone managed to get a TV Tunner on Folio, TV on camping, TV on the bed, TV everywhere !
The Android kernel seems to have fewer drivers tho... a pity...
Was anyone successful on compiling tegra 250 image for flashing board
Howto - creating a boot.img with new kernel
Note: I wrote a small guide how to repack boot.img when you have your new compiled kernel (based on http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images but modified for folio). I also included modified perl scripts and binary files needed under linux (ubuntu 10.10) for that (no need to compile tools from sdk). So that swapping a new zImage kernel instead of an old one is a question of seconds
See - Howto - unpack,edit,repack boot.img: http://forum.xda-developers.com/showthread.php?t=915808
hi guys i dont know if this is related to kernel but i would like to get the android policy jar. do you know how to do it?
thanks!
This is quite interesting topic you are discussing here.....
Can you pls gather the information abt the kernel compilation as well as image assembly so others can experiment too ?
What are chances to brick the device during tests ?
Being a linux user for some time I would be very happy to have something like
- either a custom kernel for android for playing
- or linux distribution to run on the device (as Archos 5 IT have dual boot with Linux for example)
perhaps we can gather up to produce something like it for our device ????
thanks
is possible try compiling kernel 2.6.35 for folio?? anyone has tried?
Droid X2 custom build.prop
I've been cruising with some of these edits for quite awhile, and I recently modified them for the Droid X2. Some may find this beneficial, as it is, in my opinion, better than what comes stock. I realize this is pretty basic, but some people don't know what the settings mean. This way they can just drop it in without thinking about it.
Keep in mind, this build ID's, market fingerprint, Blur version will need to be updated with every ROM release version (e.g. 2.3.4).
You may need to double reboot after flashing the ZIP to resume data service.
Now includes permanent rooted ADB thanks to drjbliss. Now you no longer have to send files to your sdcard before su'ing into root via ADB. You can push and pull files directly to /system (or other partition) now
BSR flashable zip:
Download: http://www.multiupload.com/W11VLBH7QV
Mirror: http://www.mediafire.com/?h42cf5ci777b97u
Non-BSR flashable zip - file ONLY:
Download: http://www.multiupload.com/M4FT064X18
Mirror: http://www.mediafire.com/?q8sqe7t9sr1l12l
# ----------------------------------------
# MOTOROLA Droid X2 BLUR Build Prop
# w/ optimizations by navenedrob
# ----------------------------------------
# DO NOT DELETE THIS FILE
# This file contains specific information
# that is needed by the kernel and OS.
# ----------------------------------------
# BEGIN ENV/DEVICE OPTIMIZATIONS
# ----------------------------------------
# Set generic build ID's for OS
ro.build.id=4.5.1A-DTN-117-15
ro.build.display.id=4.5.1A-DTN-117-15
ro.build.version.full=Blur_Version.1.3.232.MB870.Verizon.en.US
# Set SDK version
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.3
# Hardware specific
ro.product.model=DROID X2
ro.product.brand=verizon
ro.product.name=daytona
ro.product.device=daytona
ro.product.board=daytona
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=motorola
ro.product.locale.language=en
ro.product.locale.region=US
ro.board.platform=tegra
# Set market
ro.build.description=daytona-user 2.3.3 4.5.1A-DTN-117-15 110615 release-keys
ro.build.fingerprint=verizon/daytona/daytona:2.3.3/4.5.1A-DTN-117-15/110615:user/release-keys
# Set RILD path
rild.libpath=/system/lib/libmoto_ril.so
# Set CDMA/radio specific properties
persist.ril.uart.flowctrl=1
persist.ril.mux.ttydevice=/dev/ttyHS3
persist.ril.mux.noofchannels=8
persist.ril.modem.ttydevice=/dev/ttySPI0
persist.ril.modem.mode=1
persist.ril.features=0x0C
persist.ril.ecclist=911,*911,#911
persist.ril.mux.retries=500
persist.ril.mux.sleep=2
persist.radio.cdma.min=0
ro.cdma.homesystem=64,65,76,77,78,79,80,81,82,83
ro.cdma.home.operator.numeric=310004
ro.cdma.home.operator.alpha=Verizon
ro.cdma.otaspnumschema=SELC,1,80,99
ro.cdma.nbpcd=1
ro.cdma.data_retry_config=default_randomization=2000,0,0,120000,180000,540000,960000
ro.cdma.sms.latin_encode=true
ro.telephony.default_network=4
ro.kernel.android.ril=yes
cdma.nbpcd.supported=false
# Motorola MMS settings
mot.mms.conn.timeout=30000
mot.mms.socket.timeout=120000
mot.mms.tr.vc.timeout=55000
mot.mms.trm.timeout=240000
mot.mms.abort.prog.lim=90
mot.mms.retry.pic.size=512000
mot.mms.retry.default=false
mot.mms.retry.timeout.1=30000
mot.mms.retry.timeout.2=180000
mot.mms.retry.timeout.3=300000
mot.mms.retry.timeout.4=480000
# Client ID's
ro.com.google.clientid=android-motorola
ro.com.google.clientidbase=android-motorola
ro.com.google.clientidbase.ms=android-verizon
ro.com.google.clientidbase.am=android-verizon
ro.com.google.clientidbase.gmm=android-motorola
ro.com.google.clientidbase.yt=android-verizon
# GMS version
ro.com.google.gmsversion=2.3_r3
# Set BLAN interface
ro.blan.interface=usb0
# WiFi scan interval (decrease for more scans, 120 = 2 minutes)
wifi.supplicant_scan_interval=120
# Dalvik VM performance options
dalvik.vm.startheapsize=8m
dalvik.vm.heapsize=48m
dalvik.vm.execution-mode=int:jit
dalvik.vm.stack-trace-file=/data/anr/traces.txt
dalvik.vm.dexopt-flags=m=y
dalvik.vm.jniopts=warnonly
dalvik.vm.lockprof.threshold=500
dalvik.vm.checkjni=false
persist.sys.purgeable_assets=1
# Gingerbread performance options
debug.sf.hw=1
debug.performance.tuning=1
video.accelerate.hw=1
# USB modes allowed for UI and switching
ro.ngp_available=1
ro.modem_available=1
# Disable persistent media sync
persist.mot.usb.mediasync=0
# Default USB mode
ro.default_usb_mode=0
# Enable HDMI mirror
ro.hdmi.mirror.enable=true
# Enable tethering
ro.tether.denied=false
# Decrease call ring delay for faster answer
ro.telephony.call_ring.delay=1000
# Increase amount of call volume steps
ro.config.vc_call_vol_steps=12
# Enable multitouch and max touch count
ro.product.multi_touch_enabled=true
ro.product.max_num_touch=2
# Set LCD density (grow or shrink UI size)
ro.sf.lcd_density=240
# Change scroll smoothness/speed
windowsmgr.max_events_per_sec=150
# Enable 270 degree rotation
windowsmgr.support_rotation_270=true
# Proximity sensor options
mot.proximity.distance=60
mot.proximity.delay=150
persist.mot.proximity.touch=1
# Pointer event delay
ro.min_pointer_dur=10
# Keyguard properties
keyinputqueue.use_finger_id=true
keyguard.no_require_sim=1
# Motorola settings
ro.mot.ril.danlist=611,*611,#611
ro.mot.deep.sleep.supported=true
ro.mot.hw.calibratedImager=1
ro.mot.eri.losalert.delay=1000
ro.mot.buttonlight.timeout=1
ro.mot.hw.HAC=1
ro.mot.eri=1
ro.mot.bindervm.config=158
ro.mot.setuptype=2
ro.mot.internalsdcard=1
ro.mot.dpmext=true
ro.mot.mynet=false
ro.mot.hidden_keyboards=evfwd
ro.mot.hw.uaprof=http://uaprof.motorola.com/phoneconfig/MotoMB200/profile/MotoMB200.rdf
# Enable/disable stagefright (camera, camcorder, etc)
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
# Media encode/camera values
ro.media.enc.aud.fileformat=qcp
ro.media.enc.aud.codec=qcelp
ro.media.enc.aud.bps=13300
ro.media.enc.aud.ch=1
ro.media.enc.aud.hz=8000
ro.media.camcorder.720p=mp4,h264,30,12000000,aac,128000,44100,2
ro.media.camcorder.d1NTSC=mp4,h264,30,6000000,aac,128000,44100,2
ro.media.camcorder.vga=mp4,h264,30,4000000,aac,128000,44100,2
ro.media.camcorder.cif=mp4,h264,30,1500000,aac,128000,44100,2
ro.media.camcorder.qvga=mp4,h264,15,500000,aac,32000,16000,2
ro.media.camcorder.mms=3gp,h264,15,128000,amrnb,12200,8000,1
ro.media.camcorder.mmsres=qvga
ro.media.camera.focal=3378.6,3378.6
ro.media.camera.principal=1632.0,1224.0
ro.media.camera.skew=0.0
ro.media.camera.distortion=0.0,0.0,0.0,0.0,0.0
ro.media.camera.calresolution=3264,2448
ro.media.capture.shuttertone=1
ro.camcorder.zoom=true
ro.camcorder.videoModes=false
# Set date format to American date format
ro.com.android.dateformat=MM-dd-yyyy
# Disable data roaming to kill overages
ro.com.android.dataroaming=false
# Android Setup Wizard options
ro.setupwizard.enable_bypass=1
ro.setupwizard.enterprise_mode=1
# ENABLED, OPTIONAL, DISABLED
ro.setupwizard.mode=DISABLED
# Set legal options
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
# Set Android default BT name
net.bt.name=Android
# Attempt to keep ADB root
ro.sys.atvc_allow_netmon_usb=0
ro.sys.atvc_allow_netmon_ih=0
ro.sys.atvc_allow_res_core=0
ro.sys.atvc_allow_res_panic=0
ro.sys.atvc_allow_all_adb=1
ro.sys.atvc_allow_all_core=0
ro.sys.atvc_allow_efem=0
ro.sys.atvc_allow_bp_log=0
ro.sys.atvc_allow_ap_mot_log=0
ro.sys.atvc_allow_gki_log=0
# Attempt to make ADB constant
persist.service.adb.enable=1
# ----------------------------------------
# BEGIN OS OPTIMIZATIONS
# ----------------------------------------
# Tweak APP_ADJ parameters
ro.FOREGROUND_APP_ADJ=0
ro.VISIBLE_APP_ADJ=1
ro.PERCEPTIBLE_APP_ADJ=1
ro.HEAVY_WEIGHT_APP_ADJ=2
ro.SECONDARY_SERVER_ADJ=2
ro.BACKUP_APP_ADJ=2
ro.HOME_APP_ADJ=0
ro.HIDDEN_APP_MIN_ADJ=7
ro.CONTENT_PROVIDER_ADJ=14
ro.EMPTY_APP_ADJ=15
# Tweak APP_MEM parameters
ro.FOREGROUND_APP_MEM=2560
ro.VISIBLE_APP_MEM=4096
ro.PERCEPTIBLE_APP_MEM=4096
ro.HEAVY_WEIGHT_APP_MEM=4096
ro.SECONDARY_SERVER_MEM=6144
ro.BACKUP_APP_MEM=6144
ro.HOME_APP_MEM=6144
ro.HIDDEN_APP_MEM=10240
ro.CONTENT_PROVIDER_MEM=11264
ro.EMPTY_APP_MEM=12288
# Tweak net speed
net.tcp.buffersize.default=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.edge=4093,26280,35040,4096,16384,35040
# Tweak 3g speed
ro.ril.hsxpa=2
ro.ril.gprsclass=32
ro.ril.hep=1
ro.ril.hsdpa.category=28
ro.ril.enable.3g.prefix=1
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=268449905
ro.ril.hsupa.category=9
ro.ril.def.agps.mode=2
ro.ril.def.agps.feature=1
ro.ril.enable.sdr=1
ro.ril.enable.gea3=1
ro.ril.enable.fd.plmn.prefix=23402,23410,23411
ro.ril.disable.power.collapse=0
ro.ril.enable.a52=0
ro.ril.enable.a53=1
ro.ril.enable.dtm=1
Click to expand...
Click to collapse
Happy to see this!
...but it says "Invalid Attachment specified. If you followed a valid link, please notify the administrator" when clicking the attached file.
donlad said:
Happy to see this!
...but it says "Invalid Attachment specified. If you followed a valid link, please notify the administrator" when clicking the attached file.
Click to expand...
Click to collapse
Might need to refresh the page. I will make some mirrors.
Refreshing did the trick.
Can we just replace the build.prop that we have and reboot and voila?
donlad said:
Refreshing did the trick.
Can we just replace the build.prop that we have and reboot and voila?
Click to expand...
Click to collapse
Yes, you can
adb push build.prop /sdcard-ext/
adb shell
adb su
mount -o remount,rw /dev/block/mmcblk0p12 /system
cp /sdcard-ext/build.prop /system
chmod 644 /system/build.prop
chown 0.0 /system/build.prop
reboot
Click to expand...
Click to collapse
I'll make a BSR flashable zip... that would be easier eh
navenedrob said:
I'll make a BSR flashable zip... that would be easier eh
Click to expand...
Click to collapse
Yes please!
navenedrob said:
Yes, you can
I'll make a BSR flashable zip... that would be easier eh
Click to expand...
Click to collapse
Yes that would be easy. But could I extract the buildprop and just put it in system and set the other one to building.prop.bak? Possible? I would have to download right to my phone.
donlad said:
Yes please!
Click to expand...
Click to collapse
Ok, updated, try it out, let me know if you have success.
ashclepdia said:
Yes that would be easy. But could I extract the buildprop and just put it in system and set the other one to building.prop.bak? Possible? I would have to download right to my phone.
Click to expand...
Click to collapse
Sure, this is also another possible option.
navenedrob said:
Sure, this is also another possible option.
Click to expand...
Click to collapse
Freaking a I will be trying this tomorrow ..man I have a lot of options for tomorrow.
Now if I do this and then want to tweak something using v6 will I be okay or will there be a problem. I can't see there being a major problem..and I could also just change some values in the build.prop if I want to tweak also correct? This is pretty cool. Can't wait till tomorrow. Sucks I have to work or else I would be tweaking all day.
O yeah and I LOVE how you put in the descriptive lines. Nice touch
And b4 I forget ...the tweak network speeds. What type of results should I be expecting with these values? What is it going to be a major difference when I use speedtest?
navenedrob said:
Ok, updated, try it out, let me know if you have success.
Click to expand...
Click to collapse
Just flashed and it's booted. I have no service. No voice/data signal whatsoever.
EDIT: I rebooted again and signal has resumed.
navenedrob said:
Sure, this is also another possible option.
Click to expand...
Click to collapse
I download the file only version for just pushing into system directly from phone using root explorer? Sry just want to download the right one.
ashclepdia said:
I download the file only version for just pushing into system directly from phone using root explorer? Sry just want to download the right one.
Click to expand...
Click to collapse
That should work. Just make sure the permissions are set right.
navenedrob said:
That should work. Just make sure the permissions are set right.
Click to expand...
Click to collapse
Just to be certain I would be putting the right permission on it I just use the same settings as the permissions for my original build.prop?
They are bottom two in first column. Middle box in middle column. And bottom two in right column?
In the prop it has multi touch up to 4 points, but phone tester still only recognizes 2
Sent from my DROID X2
Thanks man. This has GREATLY improved my 3g speeds & I was running the 3g turbo script before. With this implemented, is there any benefit from running the v6 supercharger? I have both installed, along with all of the latest init.d tweaks & get no lag or redraw now. Gonna test music/video later.
Sent from my DROID X2 using XDA Premium App
garywojdan81 said:
Thanks man. This has GREATLY improved my 3g speeds & I was running the 3g turbo script before. With this implemented, is there any benefit from running the v6 supercharger? I have both installed, along with all of the latest init.d tweaks & get no lag or redraw now. Gonna test music/video later.
Sent from my DROID X2 using XDA Premium App
Click to expand...
Click to collapse
You are scaring me with all those scripts running that try to tweak the same thing at the same tine. Be careful one wrong button and you might end up having to sbf. Good luck hope it works out for ya
ashclepdia said:
You are scaring me with all those scripts running that try to tweak the same thing at the same tine. Be careful one wrong button and you might end up having to sbf. Good luck hope it works out for ya
Click to expand...
Click to collapse
Yeah I know. Getting ready to drop all the v6 stuff now. I'd rather run leaner & cleaner with something set specifically for this phone.
Update: Ok I dropped the v6 stuff after undoing the supercharge in script manager. The 3g tweaks disappeared when the build.prop was overwritten by navenedrob's file so all I'm running now are his tweaks in init.d & everything seems just as snappy. My major issue is with launcher redraws coming out pf sleep or exiting the phone.apk after ending a call. Gonna try this for awhile, so far so good though.
Sent from my DROID X2 using XDA Premium App
Ok I flashed the MOTOBLUR zip and the first time I rebooted all my services were fine does that mean its working? It feels just a tad bit faster but not sure if its actually working?
Sent from my DROID X2 using XDA App
almania6 said:
Ok I flashed the MOTOBLUR zip and the first time I rebooted all my services were fine does that mean its working? It feels just a tad bit faster but not sure if its actually working?
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
Best way to check is to open up the build.prop from /system and see if it matches the one here. If it is there and the same then it worked
Hi,
There exists the thread with the following title
[UPDATE FOR .28][Custom Build Prop] Increase Performance & Battery Life of PRIME
Click to expand...
Click to collapse
In this thread it is explained how to tweak your build.prop file.
While I applaud the intention, I am wondering though why it is recommending to change /system/build.prop since it might prove dangerous.
There are other, safer, alternatives like:
change /data/local.prop
write a shell script with similar lines
eg.
setprop debug.performance.tuning 1;
setprop video.accelerate.hw 1;
...
Easiest way to try if one of the settings offend your tablet is to try it out in a terminal.
Cheers
Is the hardware capable? If so, where do we start?
Just found this:
ed.slatt said:
I believe /proc/config shows options used to compile the linux kernel. I appended references to OTG in /proc/config to this post. "# CONFIG_USB_OTG is not set" suggests otg support has not been compiled into the kernel but "CONFIG_USB_OTG_UTILS=y" makes me think there is a chance. Perhaps some insmod command will load the appropriate module. It’s probably worthwhile to determine what these OTG flags really mean. I’ll try to look into that in the next couple of days.
I would prefer to not recompile the kernel because this device is my everyday phone and I would be in trouble without it. Furthermore, I believe not all hardware supports OTG in the first place and I haven't yet seen a declaration that this device does support it.
Does anybody know what USB chipset is used in the htc incredible 4g lte and whether it supports OTG or USB host mode?
#
# Miscellaneous USB options
#
# CONFIG_USB_DEVICEFS is not set
CONFIG_USB_DEVICE_CLASS=y
# CONFIG_USB_DYNAMIC_MINORS is not set
CONFIG_USB_SUSPEND=y
# CONFIG_USB_OTG is not set
# CONFIG_USB_OTG_WHITELIST is not set
# CONFIG_USB_OTG_BLACKLIST_HUB is not set
# CONFIG_USB_MON is not set
# CONFIG_USB_WUSB is not set
# CONFIG_USB_WUSB_CBAF is not set
.
.
.
#
# OTG and related infrastructure
#
CONFIG_USB_OTG_UTILS=y
# CONFIG_USB_OTG_WAKELOCK is not set
# CONFIG_USB_GPIO_VBUS is not set
# CONFIG_USB_ULPI is not set
# CONFIG_USB_MSM_OTG_72K is not set
# CONFIG_NOP_USB_XCEIV is not set
CONFIG_USB_MSM_OTG=y
# CONFIG_USB_MSM_ACA is not set
CONFIG_MMC=y
# CONFIG_MMC_DEBUG is not set
CONFIG_MMC_PERF_PROFILING=y
CONFIG_MMC_UNSAFE_RESUME=y
# CONFIG_MMC_CLKGATE is not set
# CONFIG_MMC_EMBEDDED_SDIO is not set
CONFIG_MMC_PARANOID_SD_INIT=y
Click to expand...
Click to collapse
jtdogblue said:
Is the hardware capable? If so, where do we start?
Just found this:
Click to expand...
Click to collapse
It was unanswered in that thread because no one knew. No need to start a new thread. Also, this is the wrong forum for a question, that's why we have the Q&A forum.
Congrats to you for getting the S-OFF phone on eBay, though, since we're already in the wrong place.
Stock LG build KOT49I.V50020b US + BusyBox + Root
for LG G Pad 8.3 V500 ONLY!
Android 4.4.2 Kit Kat :victory:
Disclaimer:
Use this at your own risk. I have personally flashed and tested this build on my own device successfully.
I am not responsible for any damage or data loss encountered due to whatever reason.
Please ensure that you make a full backup of your system before flashing anything.
Features:
Official Stock 4.4.2 LG build KOT49I.V50020b US + Stock 4.4.2 Kernel
NO Data Wipe
Doesn't flash over existing Recovery or ABOOT (you keep TWRP and retain loki-exploit)
SuperSU 1.94 + su binary Installed
BusyBox 1.22.1-Stericson Installed
Wipes Dalvik-Cache and Cache partition
External SD R\W fix
Downloads:
LG-V500_KOT49I.V50020B_US_Stock-BB-Rooted.zip (hosted on AndroidFileHost) **NEW**
Mirrors:
LG-V500_KOT49I.V50020B_US_Stock-BB-Rooted.zip (hosted on Copy.com)
md5:
c6016a8e387e3d3983a75532d4963c00
KDZ file for those that want to Flash using that method
(these are unmodified KDZ files, so they are not rooted):
V50020b_00.kdz (From Official LG Servers)
Prerequisites:
TWRP 2.7.0.0 Installed and working (not tested on CWM recovery)
FULL nandroid Backup
At least 3GB free space on internal memory (not including ZIP file)
Install:
Boot into TWRP recovery.
*** Make a Full backup before proceeding. ***
Flash .zip file in TWRP recovery.
Go take a walk, make some coffee, pace around nervously. Keep Calm... this will take a while! Be patient!!
Flash TWRP 2.7.0.1 for 4.4.2 in recovery (if not already installed)
Reboot device.
Enjoy!!
Many Thanks to
@autoprime - for 4.4.2 initial root method
@Drgravy - for TWRP for V500
@Chainfire - for SuperSU and install script
@jazzruby - BusyBox install script
my precious...2nd post.
Original build.prop from release (unmodified)
Code:
Known Issues & Fixes:
Boot loop when booting into TWRP with USB plugged in
FIX: Install TWRP 2.7.0.1 for 4.4.2, this fixes bootloop while USB plugged in, and also fixes screen dimming issue.
Workaround: If running TWRP 2.7.0.0 for 4.2.2 - Unplug USB after device reboots. It should boot into Recovery without issue. Replug USB after TWRP has booted.
Click to expand...
Click to collapse
Can you make an EU version too?
Sent from my LG-V500 using Tapatalk
Do we only have to change the build.prop (like in previous version) to make it the eu version?
nsmart said:
Do we only have to change the build.prop (like in previous version) to make it the eu version?
Click to expand...
Click to collapse
Not sure if that's the only change.. However I do have the official KDZ for GB (which hasn't been released yet) as well.. Can look into it tomorrow. In the mean time I can post the unmodified build prop from that build.
build.prop on this one is wierd..
Locale is set to US and English by default:
ro.product.locale.language=en
ro.product.locale.region=US
Yet target country is SCA
ro.build.target_country=SCA
ro.build.target_region=SCA
Anyways, for those waiting. Upload failed halfway through and had to restart it.. Going to bed now and leaving it uploading..
It will appear in this folder when it's finished. I'll update the OP in the morning.
http://www.androidfilehost.com/?w=files&flid=13555
Is that bug present when rebooting to recovery while device is plugged into USB port?
Downloading now, I see the file is ready...
id10terror said:
build.prop on this one is wierd..
Locale is set to US and English by default:
ro.product.locale.language=en
ro.product.locale.region=US
Yet target country is SCA
ro.build.target_country=SCA
ro.build.target_region=SCA
Anyways, for those waiting. Upload failed halfway through and had to restart it.. Going to bed now and leaving it uploading..
It will appear in this folder when it's finished. I'll update the OP in the morning.
http://www.androidfilehost.com/?w=files&flid=13555
Click to expand...
Click to collapse
So how certain are you that this is really the US KK if the build.prop says otherwise?
You are the man! Downloading now
Sent from my LG-V500 using Tapatalk
First of all, many thanks for the quick work. It installed smoothly and without a hitch. At first view, it is all working fine.
After installing, it did display English (US) as the primary language, though the Keyboard layout was strangely in Portuguese by default. The LG Apps are all good except one: QVoice is missing.
Another sign this is not the real US version is the QRemote. The US Qremote usually has TV and Cable Box. This one has the European defaults TV+DVD+Blu-ray.
That said, the version is unquestionably KitKat, but my initial suspicion is that this is a doctored European version, hence the lack of English language QVoice, and the above details.
id10terror said:
Not sure if that's the only change.. However I do have the official KDZ for GB (which hasn't been released yet) as well.. Can look into it tomorrow. In the mean time I can post the unmodified build prop from that build.
Click to expand...
Click to collapse
So to be clear is this in fact the official US version or is a modified European one with a US build.prop file?
I ask because qvoice and the Qremote are 2 features I do like on 4.2.2 and am wondering based on what I am reading here, if they will work or exist in this version?
Working great, thank you again
Canadoc said:
So to be clear is this in fact the official US version or is a modified European one with a US build.prop file?
I ask because qvoice and the Qremote are 2 features I do like on 4.2.2 and am wondering based on what I am reading here, if they will work or exist in this version?
Click to expand...
Click to collapse
There is no Qvoice at all, and it is not listed in the LG Apps available for download.
Qremote works on my LG TV here in Brazil, just as the original US Qremote did, so no issues, but there is no cable box option (I never used it anyhow). I have an LG G2 phone, and the monster selection of equipment and brands it covers has always made it a more attractive choice for Qremote to me anyhow.
But that is just it, the cable box option is in the US firmware. It is not in the European firmware. Q voice also is in the current firmware 4.2 .2 US version
Sent from my LG-V500 using Tapatalk
Subtleone said:
So how certain are you that this is really the US KK if the build.prop says otherwise?
Click to expand...
Click to collapse
Subtleone said:
First of all, many thanks for the quick work. It installed smoothly and without a hitch. At first view, it is all working fine.
After installing, it did display English (US) as the primary language, though the Keyboard layout was strangely in Portuguese by default. The LG Apps are all good except one: QVoice is missing.
Another sign this is not the real US version is the QRemote. The US Qremote usually has TV and Cable Box. This one has the European defaults TV+DVD+Blu-ray.
That said, the version is unquestionably KitKat, but my initial suspicion is that this is a doctored European version, hence the lack of English language QVoice, and the above details.
Click to expand...
Click to collapse
Canadoc said:
So to be clear is this in fact the official US version or is a modified European one with a US build.prop file?
I ask because qvoice and the Qremote are 2 features I do like on 4.2.2 and am wondering based on what I am reading here, if they will work or exist in this version?
Click to expand...
Click to collapse
Subtleone said:
There is no Qvoice at all, and it is not listed in the LG Apps available for download.
Qremote works on my LG TV here in Brazil, just as the original US Qremote did, so no issues, but there is no cable box option (I never used it anyhow). I have an LG G2 phone, and the monster selection of equipment and brands it covers has always made it a more attractive choice for Qremote to me anyhow.
Click to expand...
Click to collapse
Canadoc said:
But that is just it, the cable box option is in the US firmware. It is not in the European firmware. Q voice also is in the current firmware 4.2 .2 US version
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
You are all correct, this indeed does not look like the Official US build or at least not the final one. Strange thing is I did infact download this directly from LG servers and left the build.prop untouched (just as it appears on the second post.) I have removed "US" from the title and post since we are unsure what this version really is.
Also, I've added a mirror in the OP and links to the KDZ file this is based off of.
Here's the build.prop from the other unreleased KDZ I have.. Looks like Official GB\UK version.
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=KOT49I.V50020a
ro.build.display.id=KOT49I.V50020a
ro.build.version.incremental=.1395552766
ro.build.version.sdk=19
ro.build.version.codename=REL
ro.build.version.release=4.4.2
ro.build.date=Sun Mar 23 14:36:17 KST 2014
ro.build.date.utc=1395552977
ro.build.type=user
ro.build.user=patrickym.kim
ro.build.host=vegita119
ro.build.tags=release-keys
ro.product.model=LG-V500
ro.product.brand=lge
ro.product.name=awifi_open_eu
ro.product.device=awifi
ro.product.board=AWIFI
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=LGE
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=11
ro.board.platform=msm8960
# ro.build.product is obsolete; use ro.product.device
ro.build.product=awifi
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=awifi_open_eu-user 4.4.2 KOT49I.V50020a .1395552766 release-keys
ro.build.fingerprint=lge/awifi_open_eu/awifi:4.4.2/KOT49I.V50020a/.1395552766:user/release-keys
ro.build.characteristics=tablet
# end build properties
#
# from device/lge/awifi/system.prop
#
################################################################
# COMMON system property for this device (geefhd).
# operator-specific property MUST NOT be here.
################################################################
#
# system.prop for surf
#
rild.libpath=/system/lib/libril-qc-qmi-1.so
rild.libargs=-d /dev/smd0
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
ril.subscription.types=NV,RUIM
DEVICE_PROVISIONED=1
debug.sf.hw=1
debug.egl.hw=1
debug.composition.type=dyn
dalvik.vm.heapsize=36m
debug.enable.wl_log=1
persist.hwc.mdpcomp.enable=true
debug.mdpcomp.logs=0
#
# system props for the cne module
#
persist.cne.feature=1
ro.hdmi.enable=true
lpa.decode=true
tunnel.decode=false
tunnel.audiovideo.decode=false
lpa.use-stagefright=true
qcom.hw.aac.encoder=true
#system props for the MM modules
media.stagefright.enable-player=true
media.stagefright.enable-http=true
media.stagefright.enable-aac=true
media.stagefright.enable-qcp=true
media.stagefright.enable-fma2dp=true
media.stagefright.enable-scan=true
mmp.enable.3g2=true
media.aac_51_output_enabled=true
#33395 is sum of supported format flags in AAL
#Formats: AVI AC3 ASF AAC QCP DTS 3G2
mm.enable.qcom_parser=33395
#
# system props for the data modules
#
ro.use_data_netmgrd=true
persist.data.netmgrd.qos.enable=true
#system props for time-services
persist.timed.enable=true
# System props for audio
persist.audio.fluence.mode=endfire
persist.audio.vr.enable=false
persist.audio.handset.mic=digital
persist.audio.lowlatency.rec=false
# System prop to select audio resampler quality
af.resampler.quality=255
# System prop to select MPQAudioPlayer by default on mpq8064
#mpq.audio.decode=true
#
# system prop for opengles version
#
# 196608 is decimal for 0x30000 to report version 3
ro.opengles.version=196608
# system prop for requesting Master role in incoming Bluetooth connection.
#
ro.bluetooth.request.master=true
#
# system prop for Bluetooth Auto connect for remote initated connections
#
ro.bluetooth.remote.autoconnect=true
# system property for Bluetooth discoverability time out in seconds
# 0: Always discoverable
#debug.bt.discoverable_time=0
# System prop to disable a2dp sink which is enabled by default
bluetooth.a2dp.sink.enabled=false
#system prop for switching gps driver to qmi
persist.gps.qmienabled=true
# System property for cabl
#LGE_CHANGE_S 2013.01.31 QCT CABL OFF
ro.qualcomm.cabl=2
#LGE_CHANGE_S 2013.01.31 QCT CABL OFF
# System props for telephony
# System prop to turn on CdmaLTEPhone always
# [email protected] awifi do not use lte telephony feature
#telephony.lteOnCdmaDevice=1
#
# System prop for sending transmit power request to RIL during WiFi hotspot on/off
#
ro.ril.transmitpower=true
#
#Simulate sdcard on /data/media
#
# LGE_CHANGE_S
# If you use Internal-SD with FUSE, comment-out below
# 2012-01-08 [email protected]
#persist.fuse_sdcard=false
# LGE_CHANGE_E
ro.hwui.text_cache_width=2048
#
# Supports warmboot capabilities
#
ro.warmboot.capability=1
#
#snapdragon value add features
#
ro.qc.sdk.audio.ssr=false
ro.qc.sdk.camera.facialproc=true
ro.qc.sdk.gestures.camera=false
# LGE_CHANGE_S [email protected] 2012.4.22 LGE sound profile scenario.
ro.lge.audio_soundprofile=true
# LGE_CHANGE_E [email protected] 2012.4.22 LGE sound profile scenario.
#LGBT_COMMON_SCENARIO supported Bluetooth PAN profile 2012-05-22
ro.bluetooth.PANenable = 1
#LGBT_COMMON_SCENARIO
# System prop for sensor
ro.qc.sdk.sensors.gestures=true
# LGE_CHANGE_S 2012-12-11, [email protected], HDMI block
sys.hdmi.block=unblock
# LGE_CHANGE_E 2012-12-11, [email protected], HDMI block
# Increase texture cache size for FHD models (24MB -> 32MB)
ro.hwui.texture_cache_size=32
#property to check if dynamic resolution change is supported in framework
ro.streaming.video.drs=true
#property to enable user to access Google WFD settings.
persist.debug.wfd.enable=1
#property to choose between virtual/external wfd display
persist.sys.wfd.virtual=0
#system prop for setting rmnet mux mode
persist.rmnet.mux=disabled
# LGE_CHANGE_S, [WiFi][[email protected]], 2013-01-22, Wifi Bring Up
# reserved wifi related property
dhcp.ap.macaddress=
dhcp.wlan0.dns1=
dhcp.wlan0.dns2=
dhcp.wlan0.dns3=
dhcp.wlan0.dns4=
dhcp.wlan0.gateway=
dhcp.wlan0.ipaddress=
dhcp.wlan0.leasetime=
dhcp.wlan0.mask=
dhcp.wlan0.pid=
dhcp.wlan0.reason=
dhcp.wlan0.result=
dhcp.wlan0.server=
dhcp.wlan0.vendorInfo=
dhcp.p2p.dns1=
dhcp.p2p.dns2=
dhcp.p2p.dns3=
dhcp.p2p.dns4=
dhcp.p2p.gateway=
dhcp.p2p.ipaddress=
dhcp.p2p.leasetime=
dhcp.p2p.mask=
dhcp.p2p.pid=
dhcp.p2p.reason=
dhcp.p2p.result=
dhcp.p2p.server=
dhcp.p2p.vendorInfo=
init.svc.dhcpcd_wlan0=
init.svc.dhcpcd_p2p=
init.svc.p2p_supplicant=
init.svc.iprenew_wlan0=
net.dns1=
net.dns2=
net.dnschange=
net.p2p-p2p0-0.dns1=
net.p2p-p2p0-0.dns2=
net.wlan0.dns1=
net.wlan0.dns2=
wlan.driver.status=
persist.sys.security=
persist.sys.hotssid.ksc5601=
wifi.lge.autochannel=
# LGE_CHANGE_S, [WiFi][[email protected]], 2013-01-22, Wifi Bring Up
# LGE_CHANGE_S 2013-05-21 [email protected], Support modem
persist.lge.modem.support=false
# LGE_CHANGE_E 2013-02-19 [email protected], Support modem
#disable gapless mode by default
audio.gapless.playback.disable=true
# LGE_CHANGE_S [awifi][framework][common] the screen auto-brightness adjustment setting
persist.power.useautobrightadj=true
# LGE_CHANGE_E [awifi][framework][common] the screen auto-brightness adjustment setting
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.build.target_operator=OPEN
ro.build.target_country=EU
ro.build.target_region=EU
ro.3lm.build.lg=false
ro.lge.basebandversion=M9615A-CEFWTAZM-4.0.10353
tangible_device_config=T1BCNAOTDO
ro.lge.swversion=V50020a
ro.lge.factoryversion=LGV500AT-00-V20a-EUR-XX-MAR-23-2014+0
ro.config.ringtone=00_Lifes_Good.ogg
ro.config.notification_sound=Lifes_Good_Noti.ogg
ro.config.alarm_alert=Good_Morning.ogg
ro.camera.sound.forced=1
keyguard.no_require_sim=true
ime_feature_0=vibration_pattern:0:25;keyboard_layout:ko=QWERTY
ro.lge.lcd_default_brightness=164
ro.lge.lcd_auto_brightness_mode=false
ro.sf.lcd_density=320
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=128m
dalvik.vm.heapsize=256m
dalvik.vm.heaputilization=0.25
dalvik.vm.heapidealfree=8388608
dalvik.vm.heapconcurrentstart=2097152
wifi.supplicant_scan_interval=20
wifi.lge.patch=true
wifi.lge.sleeppolicy=0
wifi.lge.offdelay=false
wifi.lge.hanglessid=true
wifi.lge.ftm_test=1
wlan.lge.supportsimaka=NO
wlan.lge.wifidisplay=both
dhcp.dlna.using=false
ro.tether.denied=true
wlan.chip.vendor=qcom
wlan.lge.concurrency=MCC
wlan.chip.version=wcnss
wifi.lge.supportp2p5g=gconly
drm.service.enabled=true
lge.signed_image=true
persist.sys.strictmode.disable=true
wlan.driver.ath=0
wlan.driver.config=/data/misc/wifi/WCNSS_qcom_cfg.ini
qcom.audio.init=complete
lpa.decode=true
persist.sys.ats_start=false
persist.sys.strictmode.visual=false
lgemm.player.use_android_origin=false
ro.lge.audio_scenario=SOUNDEXCEPTION
ro.lge.audio_soundexception=true
ro.config.vc_call_vol_steps=6
ro.config.vc_call_vol_default=3
ro.airplane.phoneapp=1
ro.lge.overlay=false
lge.version.verified=NONE
persist.service.main.enable=0
persist.service.system.enable=0
persist.service.radio.enable=0
persist.service.events.enable=0
persist.service.kernel.enable=0
persist.service.packet.enable=0
persist.service.crash.enable=0
persist.sys.ssr.restart_level=3
persist.radio.data_no_toggle=1
ro.carrier=unknown
ro.vendor.extension_library=/system/lib/libqc-opt.so
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=2m
dalvik.vm.heapmaxfree=8m
ro.lge.ps.eco.pv=322
ro.lge.ps.freqlowlimit=1026000
lge.hw.frontkeyled=false
lge.normalizer.param=version2.0/true/13.5/true/8230/1.0/2050/0.55
bluetooth.chip.vendor=qcom
bluetooth.pan=true
persist.service.btui.use_aptx=1
ro.sdcrypto.syscall=378
ro.lge.b2b.vmware=true
service.knockcode.touchfw=0
ro.lge.capp_ZDi_O=true
lge.zdi.actionsend=false
lge.zdi.onactivityresult=true
lge.zdi.dragdropintent=false
ro.lge.capp_almond=true
ro.lge.capp_wfd=true
ro.lge.qslide.max_window=2
ro.lge.irrc.type=sw
ro.com.google.clientidbase=android-om-lge
ro.com.google.clientidbase.ms=android-om-lge
ro.com.google.clientidbase.am=android-om-lge
ro.com.google.clientidbase.gmm=android-om-lge
ro.com.google.clientidbase.yt=android-om-lge
ro.com.google.gmsversion=4.4.2_r1
ro.setupwizard.mode=DISABLED
ro.livewallpaper.map=DISABLED
ro.com.google.apphider=on
persist.sys.dalvik.vm.lib=libdvm.so
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.qc.sdk.izat.premium_enabled=0
ro.qc.sdk.izat.service_mask=0x0
persist.gps.qc_nlp_in_use=0
ro.gps.agps_provider=1
Do any of the versions that you have access to have the quick voice app? I tried to install the 4.2 .2 version into system and fix permissions. And even after a reboot they do not appear to show up.
Also one other interesting things, is that the Q remote app does not show cable box as an option, so it is acting more like the non American version. However what is interesting was I previously had a remote setup including the cable set top box for my home TV. Ironically even though I cannot set up a new cable box, the previously set up when I have remained and is functional. This leads me to believe that there must be a setting somewhere that can be changed that with open up access to more devices on our Q remote app
Sent from my LG-V500 using Tapatalk
Canadoc said:
Do any of the versions that you have access to have the quick voice app? I tried to install the 4.2 .2 version into system and fix permissions. And even after a reboot they do not appear to show up.
Also one other interesting things, is that the Q remote app does not show cable box as an option, so it is acting more like the non American version. However what is interesting was I previously had a remote setup including the cable set top box for my home TV. Ironically even though I cannot set up a new cable box, the previously set up when I have remained and is functional. This leads me to believe that there must be a setting somewhere that can be changed that with open up access to more devices on our Q remote app
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
Seriously, did you not read the 16 posts on this brand new thread
-VZW LG G2 VS980
Canadoc said:
Do any of the versions that you have access to have the quick voice app? I tried to install the 4.2 .2 version into system and fix permissions. And even after a reboot they do not appear to show up.
Also one other interesting things, is that the Q remote app does not show cable box as an option, so it is acting more like the non American version. However what is interesting was I previously had a remote setup including the cable set top box for my home TV. Ironically even though I cannot set up a new cable box, the previously set up when I have remained and is functional. This leads me to believe that there must be a setting somewhere that can be changed that with open up access to more devices on our Q remote app
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
I just flashed the GB version and it has a working QVoice.. I'm going to post a Flashable zip of the GB EU version as well.. then we can look to see if a simple build.prop change can give you the US version of Q Remote, which has Cable Box option.
Any one feel difference between this build and the previus (50018) ?