[DUMP] Android 5.0 Lollipop System Dump - Nexus 9 General

[DUMP] Android 5.0 Lollipop System Dump.
This Dump is based on Build : LRX09D
Link : https://www.mediafire.com/?ing4omfs9wf7bw4

Ashutos1997 said:
[DUMP] Android 5.0 Lollipop System Dump.
This Dump is based on Build : LRX09D
Link : https://www.mediafire.com/?ing4omfs9wf7bw4
Click to expand...
Click to collapse
What device is this based on and where did you get it from?

Ashutos1997 said:
[DUMP] Android 5.0 Lollipop System Dump.
This Dump is based on Build : LRX09D
Link : https://www.mediafire.com/?ing4omfs9wf7bw4
Click to expand...
Click to collapse
not the nexus 9 dump
right

Getting excited :highfive:

MRobbo80 said:
Getting excited :highfive:
Click to expand...
Click to collapse
II there
---------- Post added at 11:46 AM ---------- Previous post was at 11:43 AM ----------
not the Nexus 9 or 64bit dump
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=LRX09D
ro.build.display.id=sdk_phone_armv7-eng 5.0 LRX09D 1504858 test-keys
ro.build.version.incremental=1504858
ro.build.version.sdk=21
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=5.0
ro.build.date=Fri Oct 10 00:52:07 UTC 2014
ro.build.date.utc=1412902327
ro.build.type=eng
ro.build.user=android-build
ro.build.host=wpef5.hot.corp.google.com
ro.build.tags=test-keys
ro.product.model=sdk_phone_armv7
ro.product.brand=generic
ro.product.name=sdk_phone_armv7
ro.product.device=generic
ro.product.board=
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.cpu.abilist=armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=
ro.product.manufacturer=unknown
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=generic
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=sdk_phone_armv7-eng 5.0 LRX09D 1504858 test-keys
ro.build.fingerprint=generic/sdk_phone_armv7/generic:5.0/LRX09D/1504858:eng/test-keys
ro.build.characteristics=default
# end build properties
#
# from build/target/board/generic/system.prop
#
#
# system.prop for generic sdk
#
rild.libpath=/system/lib/libreference-ril.so
rild.libargs=-d /dev/ttyS0
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
persist.sys.dalvik.vm.lib.2=libart.so
dalvik.vm.isa.arm.features=default
ro.kernel.android.checkjni=1
xmpp.auto-presence=true
ro.config.nocheckin=yes
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt

When will they release the Lolipop source code?

joshuabg said:
When will they release the Lolipop source code?
Click to expand...
Click to collapse
i want the kernel code so i can start working on it
you know
OCing the CPU
OCing the GPU
etc

USBhost said:
i want the kernel code so i can start working on it
you know
OCing the CPU
OCing the GPU
etc
Click to expand...
Click to collapse
Adding new governors

joshuabg said:
Adding new governors
Click to expand...
Click to collapse
You got it!!
OC gpu to 1ghz
OC the cpu to 3ghz edit well 2.6ghz

USBhost said:
You got it!!
OC gpu to 1ghz
OC the cpu to 3ghz edit well 2.6ghz
Click to expand...
Click to collapse
Will we have to wait for the binaries for camera etc. Like with the nexus 7 2nd generation?

Related

[REF] The weird XWJV1 Gingerbread build.prop and alternatives

I have been investigating several build.prop settings for the leaked XWJV1 beta Gingerbread since it has been leaked, trying to enhance the performance of the firmware and here what I found out so far:
1. build.prop contains lines that is not related to the firmware it self or it's files, in the same time the same function requests 2 files to do the same.
2. build.prop disables functions that should be enabled, these functions have always been enabled on previous 2.2 and 2.2.1 firmwares.
3. build.prop contains lines that has only been used on HTC devices, such as Desire and Nexus One.
4. Bigger heap for dalvik VM.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Let us look at the latest build.prop and default.prop included in the latest XWJS7.
build.prop:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=FROYO
ro.build.display.id=FROYO
ro.build.version.incremental=XWJS7
ro.build.version.sdk=8
ro.build.version.codename=REL
ro.build.version.release=2.2.1
ro.build.date=2011. 02. 16. (수) 14:07:24 KST
ro.build.date.utc=1297832844
ro.build.type=user
ro.build.user=root
ro.build.host=SE-S608
ro.build.tags=release-keys
ro.product.model=GT-I9000
ro.product.brand=samsung
ro.product.name=GT-I9000
ro.product.device=GT-I9000
ro.product.board=GT-I9000
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=s5pc110
# ro.build.product is obsolete; use ro.product.device
ro.build.product=GT-I9000
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=GT-I9000-user 2.2.1 FROYO XWJS7 release-keys
ro.build.fingerprint=samsung/GT-I9000/GT-I9000/GT-I9000:2.2.1/FROYO/XWJS7:user/release-keys
# Samsung Specific Properties
ro.build.PDA=I9000XWJS7
ro.build.hidden_ver=I9000XWJS7
ro.build.changelist=910210
ro.tether.denied=false
# end build properties
#
# system.prop for smdkc110
#
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=240
dalvik.vm.heapsize=48m
dalvik.vm.execution-mode=int:jit
# The OpenGL ES API level that is natively supported by this device.
# This is a 16.16 fixed point number
ro.opengles.version=131072
#
# ADDITIONAL_BUILD_PROPERTIES
#
windowsmgr.max_events_per_sec=55
keyinputqueue.use_finger_id=true
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=2.2_r9
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
ro.com.google.locationfeatures=1
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
keyguard.no_require_sim=true
ro.config.ringtone=01_Samsung_tune.ogg
ro.config.notification_sound=01_Sherbet.ogg
ro.config.alarm_alert=Good_Morning.ogg
ro.opengles.version=131072
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Now let's look at the default build.prop of XWJV1, I have marked the lines by colored numbers:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=GINGERBREAD
ro.build.display.id=GINGERBREAD.XWJV1
ro.build.version.incremental=XWJV1
ro.build.version.sdk=9
ro.build.version.codename=REL
ro.build.version.release=2.3.2
ro.build.date=Mon Feb 21 20:56:37 KST 2011 (1)
ro.build.date.utc=1298289397
ro.build.type=user
ro.build.user=root
ro.build.host=DELL101
ro.build.tags=release-keys
ro.product.model=GT-I9000
ro.product.brand=samsung
ro.product.name=GT-I9000
ro.product.device=GT-I9000
ro.product.board=herring (1)
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=s5pc110
# ro.build.product is obsolete; use ro.product.device
ro.build.product=GT-I9000
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=GT-I9000-user 2.3.2 GINGERBREAD XWJV1 release-keys
ro.build.fingerprint=samsung/GT-I9000/GT-I9000:2.3.2/GINGERBREAD/XWJV1:user/release-keys
# Samsung Specific Properties
ro.build.PDA=I9000XWJV1
ro.build.hidden_ver=I9000XWJV1
ro.build.changelist=31216
# end build properties
#
# system.prop for smdkc110
#
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=240
dalvik.vm.heapsize=64m (4)
ro.opengles.version=131072
# Samsung USB default mode
persist.service.usb.setting=0
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.opengles.version=131072
ro.config.ringtone=01_Minimal_tone.ogg
ro.config.notification_sound=01_Sherbet.ogg (1)
ro.config.alarm_alert=Good_Morning.ogg (1)
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
ro.com.google.locationfeatures=1
ro.setupwizard.mode=DISABLED
ro.com.google.clientidbase=android-samsung
ro.com.google.gmsversion=2.3_r1
wifi.interface=eth0 (3)
wifi.supplicant_scan_interval=15
ro.secdevenc=true (3)
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy (3)
ro.com.android.dataroaming=true (3)
ro.ril.hsxpa=1 (3)
ro.ril.gprsclass=10 (3)
ro.config.notification_sound=OnTheHunt.ogg (1, 3)
ro.config.alarm_alert=Alarm_Classic.ogg (1, 3)
media.stagefright.enable-player=false (2)
media.stagefright.enable-meta=false (2)
media.stagefright.enable-scan=false (2)
media.stagefright.enable-http=true
media.stagefright.enable-rtsp=false (2)
dalvik.vm.dexopt-flags=m=y (3)
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Conclusion:
There have been to much copy and paste in the XWJV1 build.prop file from HTC Desire or Nexus One build.prop files, it's clear that the guy/team that have included this build.prop file in XWJV1 did not work on a Galaxy S device before, and more than that, they did not even check the default build.prop file that Samsung used to use on Galaxy S firmwares.
Just to clarify in a more specific way, the lines in (2) are used to be disabled on HTC devices such as Desire and Nexus One, because the devices will produce bad sound quality when streaming AAC media files. Beside that, lines in (1, 3) are related to Nexus one.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
What I use now on XWJV1 that is installed on my device is a mix between XWJS7 and XWJV1 build.prop files, I have also added a few lines to reduce power consumed by WiFi, and enhancing GPS on the device. This is what I think that the files be, but any new ideas are welcome.
My build.prop file for XWJV1:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=GINGERBREAD
ro.build.display.id=GINGERBREAD.XWJV1
ro.build.version.incremental=XWJV1
ro.build.version.sdk=9
ro.build.version.codename=REL
ro.build.version.release=2.3.2
ro.build.date=Mon Feb 21 20:56:37 KST 2011
ro.build.date.utc=1298289397
ro.build.type=user
ro.build.user=root
ro.build.host=DELL101
ro.build.tags=release-keys
ro.product.model=GT-I9000
ro.product.brand=samsung
ro.product.name=GT-I9000
ro.product.device=GT-I9000
ro.product.board=GT-I9000
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=s5pc110
# ro.build.product is obsolete; use ro.product.device
ro.build.product=GT-I9000
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=GT-I9000-user 2.3.2 GINGERBREAD XWJV1 release-keys
ro.build.fingerprint=samsung/GT-I9000/GT-I9000:2.3.2/GINGERBREAD/XWJV1:user/release-keys
# Samsung Specific Properties
ro.build.PDA=I9000XWJV1
ro.build.hidden_ver=I9000XWJV1
ro.build.changelist=31216
ro.tether.denied=false
# end build properties
#
# system.prop for smdkc110
#
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=240
dalvik.vm.heapsize=48m
# Samsung USB default mode
persist.service.usb.setting=0
# The OpenGL ES API level that is natively supported by this device.
# This is a 16.16 fixed point number
ro.opengles.version=131072
#
# ADDITIONAL_BUILD_PROPERTIES
#
windowsmgr.max_events_per_sec=55
keyinputqueue.use_finger_id=true
wifi.supplicant_scan_interval=120
ro.ril.def.agps.mode=1
ro.ril.def.agps.feature=1
ro.opengles.version=131072
keyguard.no_require_sim=true
ro.config.ringtone=01_Minimal_tone.ogg
ro.config.notification_sound=01_Sherbet.ogg
ro.config.alarm_alert=Good_Morning.ogg
media.stagefright.enable-player=false
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
media.stagefright.enable-rtsp=true
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Click to expand...
Click to collapse
Click to expand...
Click to collapse
And the default.prop file:
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
ro.com.google.locationfeatures=1
ro.setupwizard.mode=DISABLED
ro.com.android.dataroaming=false
ro.com.google.clientidbase=android-samsung
ro.com.google.clientidbase.yt=android-samsung
ro.com.google.clientidbase.am=android-samsung
ro.com.google.clientidbase.vs=android-samsung
ro.com.google.clientidbase.gmm=android-samsung
ro.com.google.gmsversion=2.3_r1
Click to expand...
Click to collapse
Click to expand...
Click to collapse
If you want to try these then just edit your build.prop and any default.prop files using a Note++ and copy to your /system partition as superuser. If you need to try the files that I use then download them from the link below.
Change log:
11-3-2011:
- media.stagefright.enable-player=true in build.prop is changed to false to enable AVI playback. Thanks to jassired
- XDA member MCOGW PM'ed me regarding the lines ro.build.date=(wrong date format)( Samsung date formats are usually as in the lines of XWJS7 are like yyyy. mm. dd. (Korean-sign) hh:mm:ss KST) and ro.product.board=herring along with another line that awaits confirmation. Thnaks MCOGW
12-3-2011:
# Samsung USB default mode
persist.service.usb.setting=0
Is a correct setting, kies cannot connect to the device without it, the attached file is updated.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Thanks Ramad. It's weird: GB was first seen on Nexus S (samsung product) that is so similar to SGS. Where did these lines come from? Has any HTC device got 2.3.x so far?
tsinc said:
Thanks Ramad. It's weird: GB was first seen on Nexus S (samsung product) that is so similar to SGS. Where did these lines come from? Has any HTC device got 2.3.x so far?
Click to expand...
Click to collapse
I think, as I wrote in the post that the guy(s) who made the build.prop file did copy many lines from other places, or he/they is/are only familiar with HTC devices (new worker(s) maybe..), the bottom line is that I think that the build.prop file should be different. Making a bigger heap for dalvik virtual-machine will not make it lag less but more, because of more garbage-collection operations. The device do work fine now with 32MB as heap, but I have increased it to 48MB since I did want to share it and since it's 48MB that Samsung used to use on previous firmwares.
I also noticed the heapsize growing and I suppose it wasn't intentional. I wonder if anybody knows what the dalvik.vm.dexopt-flags=m=y means?
please add this to build.prop for a nice boost. Are we sure this didn't work in JS5? (never heard of it now)
dalvik.vm.execution-mode=int:jit
tsinc said:
Thanks Ramad. It's weird: GB was first seen on Nexus S (samsung product) that is so similar to SGS. Where did these lines come from? Has any HTC device got 2.3.x so far?
Click to expand...
Click to collapse
Let us not forget Nexus One is produced by HTC
Had to set media.stagefright.enable-player=true to false inorder to have AVI playback support with your Build.prop
newmail said:
I also noticed the heapsize growing and I suppose it wasn't intentional. I wonder if anybody knows what the dalvik.vm.dexopt-flags=m=y means?
please add this to build.prop for a nice boost. Are we sure this didn't work in JS5? (never heard of it now)
dalvik.vm.execution-mode=int:jit
Click to expand...
Click to collapse
I have read many places, this so far the one that is easiest to understand: http://www.netmite.com/android/mydroid/2.0/dalvik/docs/embedded-vm-control.html it does not mention m and y modes and I could not find the meaning of these modes anywhere yet.
I did could not see any difference with or without the line 'dalvik.vm.execution-mode=int:jit' this is why I did not add it ,it appears to me that it's enabled as a default setting.
jassired said:
Had to set media.stagefright.enable-player=true to false inorder to have AVI playback support with your Build.prop
Click to expand...
Click to collapse
Confirmed...I have just tested it and AVI(Divx) does indeed work when the line changed to 'false', Quadrant score will suck, but who cares , we need the device to work properly.
[Ramad] said:
....
Confirmed...I have just tested it and AVI(Divx) does indeed work when the line changed to 'false', Quadrant score will suck, but who cares , we need the device to work properly.
Click to expand...
Click to collapse
It has been mentioned before in the XWJV1 thread.
http://forum.xda-developers.com/showthread.php?p=11860843&highlight=build+prop#post11860843
Anyway, I thought again about the HTC (are they really?) lines. The only way that this is possible is if the code was written by NON Samsung employees. And this leads me to another conclusion: maybe Google writes the code for Samsung. Google demonstrates the last version of Android on a top selling company's model (HTC, Samsung etc) and then sells it to the manufacturer. And they are used to HTC models....
Anyway, just speculating....
tsinc said:
It has been mentioned before in the XWJV1 thread.
http://forum.xda-developers.com/showthread.php?p=11860843&highlight=build+prop#post11860843
Anyway, I thought again about the HTC (are they really?) lines. The only way that this is possible is if the code was written by NON Samsung employees. And this leads me to another conclusion: maybe Google writes the code for Samsung. Google demonstrates the last version of Android on a top selling company's model (HTC, Samsung etc) and then sells it to the manufacturer. And they are used to HTC models....
Anyway, just speculating....
Click to expand...
Click to collapse
I did not read the thread you mentioned for a long time now and don't know how far they have reached, but jassired were the first to mention the line change here.
You could be very much right about the Google coding thing, but Samsung did add several other directories, drivers and applications, they should at least check the double lines and other lines(like the line that had Swype disabled) to see if the device is working as it should using these lines.
Just as an example, I'm not using 64MB or 48MB as heap-cache but 32MB and I feel that the firmware is even better than before, not perfect, as I think that the firmware needs to be optimized further. I have to mention here that I use the deodexed version of this beta.
newmail said:
I also noticed the heapsize growing and I suppose it wasn't intentional. I wonder if anybody knows what the dalvik.vm.dexopt-flags=m=y means?
please add this to build.prop for a nice boost. Are we sure this didn't work in JS5? (never heard of it now)
dalvik.vm.execution-mode=int:jit
Click to expand...
Click to collapse
Oops just tried and it seems it was the stagefright that made the difference, not int:jit...

New rom KJ2

I see on Samfirmware KJ2 for Holland .Can be used with multicsc?
Can't find it... send link please.
vergilcl said:
I see on Samfirmware KJ2 for Holland .Can be used with multicsc?
Click to expand...
Click to collapse
It says KI2
pacc said:
Can't find it... send link please.
Click to expand...
Click to collapse
gee2012 said:
It says KI2
Click to expand...
Click to collapse
It's a provider rom and is BOKJ2
2.3.5
BOKJ2 - TNLKJ2 - BOKJ1
CSC = TNL means T-Mobile.
SamMobile
Finally something new. Hope we get one with the old boot loader up soon.
donalgodon said:
Finally something new. Hope we get one with the old boot loader up soon.
Click to expand...
Click to collapse
Er, it's been up in the carrier firmware thread for days now.
Flashed and... do not know if it's placebo but I feel that KJ2 runs more smoothness and a little bit quicker than KI3...
emilcioran99 said:
Flashed and... do not know if it's placebo but I feel that KJ2 runs more smoothness and a little bit quicker than KI3...
Click to expand...
Click to collapse
It is a bit quicker... every newly flashed ROM is
no wonder its fast, phone keeps flying out of my pocket, because every new firmware is faster than before so now they run on nuclear power
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=GINGERBREAD
ro.build.display.id=GINGERBREAD.BOKJ2
ro.build.version.incremental=BOKJ2
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.5
[COLOR="Red"]ro.build.date=Thu Oct 6 08:34:03 KST 2011[/COLOR]
ro.build.date.utc=1317857643
ro.build.type=user
ro.build.user=root
ro.build.host=DELL149
ro.build.tags=release-keys
ro.product.model=GT-I9100
ro.product.brand=samsung
ro.product.name=GT-I9100
ro.product.device=GT-I9100
ro.product.board=GT-I9100
ro.product.cpu.abi=armeabi-v7a
# Samsung Specific Properties
ro.build.PDA=I9100BOKJ2
ro.build.hidden_ver=I9100BOKJ2
[COLOR="Red"]ro.build.changelist=635147[/COLOR]
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=s5pc210
# ro.build.product is obsolete; use ro.product.device
ro.build.product=GT-I9100
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=GT-I9100-user 2.3.5 GINGERBREAD BOKJ2 release-keys
ro.build.fingerprint=samsung/GT-I9100/GT-I9100:2.3.5/GINGERBREAD/BOKJ2:user/release-keys
# Samsung Specific Properties
ro.build.PDA=I9100BOKJ2
ro.build.hidden_ver=I9100BOKJ2
ro.build.changelist=635147
ro.tether.denied=false
ro.flash.resolution=1080
# end build properties
#
# system.prop for asop5000
#
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=240
dalvik.vm.heapsize=64m
# Samsung USB default mode
persist.service.usb.setting=0
dev.powersave_fps=0
#
# ADDITIONAL_BUILD_PROPERTIES
#
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
ro.com.google.locationfeatures=1
ro.com.google.clientidbase=android-samsung
ro.com.google.gmsversion=2.3_r7
media.stagefright.enable-player=false
media.stagefright.enable-meta=false
media.stagefright.enable-scan=false
media.stagefright.enable-http=true
media.stagefright.enable-rtsp=false
dev.sfbootcomplete=0
ro.com.google.clientidbase=android-samsung
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
ro.com.google.locationfeatures=1
keyguard.no_require_sim=true
ro.config.ringtone=S_Over_the_horizon.ogg
ro.config.notification_sound=01_Sherbet.ogg
ro.config.alarm_alert=Good_Morning.ogg
ro.config.media_sound=Media_preview_Touch_the_light.ogg
ro.opengles.version=131072
ro.setupwizard.mode=OPTIONAL
ro.secdevenc=true
ro.wtldatapassword=true
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Bin using bokj2 for 2 days now.
So far the battery life is sligtly better then ki8 I used before.
Br
Sent from my GT-I9100 using XDA
What version of Swype is included?
3.25.91.33835.33848.4148.oxx
I9100JPKJ2/I9100OJPKJ1/I9100XXKI4 released for THR csc code.
JPKJ2 is available in the firmware thread.
thx, download……
can anyone tell me if the camera shutter noise is always on with the ROM??? eg - you have phone on silence but camera makes noise, i've seen in a few asian ROMS.....guess its to stop dodgy upskirt photos in japan lol.
Still waiting for CF-Root before I try KJ2
Any changelog from ki8?
Sent from my GT-I9100 using Tapatalk
donalgodon said:
Finally something new. Hope we get one with the old boot loader up soon.
Click to expand...
Click to collapse
whats wrong with the new bootloader ?

[LEAK][ICS][XXLP2] Android ICS 4.0.3 XXLP2 Leaked |CF-ROOT|14Jan2012

Samfirmware just leaked a new ICS build with build name: XXLP2
I9100XXLP2 DOWNLOAD : Hotfile|Multiupload (ty p4ndA)
Password: Samfirmware.com
Firmware Info:
Flash with: Odin 3 v1.85
Firmware: I9100XXLP2 | Android 4.0.3
Build Date: January 10 2012
Modem: I9100XXLP1
CSC: I9100OXALP2
Change List: 57619
Kernel Version: 3.0.15
WANNA SOM ROOTZ NOA?!
CF Root XXLP2 by Chainfire : http://download.chainfire.eu/138/CF-Root/SGS2/CF-Root-SGS2_XX_OXA_LP2-v5.2-CWM5.zip
Changelog(XXLP2):
-Interface: Nothing changed that much in case of XXLP1.
-Overall speed has slightly increased
learning~
XXLP2 Build.prop:
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=ICS
ro.build.display.id=ICS.XXLP2
ro.build.version.incremental=XXLP2
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Tue Jan 10 10:25:44 KST 2012
ro.build.date.utc=1326158744
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEI-44
ro.build.tags=release-keys
ro.product.model=GT-I9100
ro.product.brand=samsung
ro.product.name=GT-I9100
ro.product.device=GT-I9100
ro.product.board=smdk4210
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=exynos4
# ro.build.product is obsolete; use ro.product.device
ro.build.product=GT-I9100
ro.tether.denied=false
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=GT-I9100-user 4.0.3 ICS XXLP2 release-keys
ro.build.fingerprint=samsung/GT-I9100/GT-I9100:4.0.3/ICS/XXLP2:user/release-keys
ro.build.characteristics=phone
# Samsung Specific Properties
ro.build.PDA=I9100XXLP2
ro.build.hidden_ver=I9100XXLP2
ro.build.changelist=57619
# end build properties
#
# system.prop for smdk4210
#
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=240
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
#wlan.driver.apmode "unloaded"
net.streaming.rtsp.uaprof=http://wap.samsungmobile.com/uaprof/GT-I9100.xml
net.streaming.rtsp.uaprof.bo=http://wap.samsungmobile.com/uaprof/GT-I9100BO.xml
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.opengles.version=131072
ro.sf.lcd_density=240
ro.config.ringtone=S_Over_the_horizon.ogg
ro.config.notification_sound=S_Whistle.ogg
ro.config.alarm_alert=Good_Morning.ogg
ro.config.media_sound=Media_preview_Touch_the_light.ogg
hwui.render_dirty_regions=false
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=128m
dalvik.vm.heapsize=128m
ro.secdirenc=true
ro.secsddecryption=true
ro.secfulldirenc=true
keyguard.no_require_sim=true
ro.com.android.dataroaming=false
ro.com.android.dateformat=MM-dd-yyyy
dev.sfbootcomplete=0
dev.powersave_fps=0
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.0.3_r0
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Waiting for your feed back on this
Source ?
notoriouspk said:
Waiting for your feed back on this
Click to expand...
Click to collapse
Changes.
Interface: Nothing in case of XXKPA.
Battery: Battery feels better.
Faster: Phones looks faster.
Touch: Touch response is better.
Overall: Firmware more stable but still with some bugs.
Facelock: Working.
Task: Task maneger is back.
Source: Samfirmware
Password for the zip file ??
Waiting to
Sent from my GT-I9100 using xda premium
Password???
This LennyUK guy didnt posted the passwd. updated OP with Samfirmware download link. passwd is samfirmware.com
goyagoyago LOL that was quick man
Cool, i hope it's really more stable.
notoriouspk said:
goyagoyago LOL that was quick man
Click to expand...
Click to collapse
lol you're welcome bud
is this a flashable zip via CWM which will install the rom please ?
Hmm Samsung's own Task manager >.<
strenx said:
is this a flashable zip via CWM which will install the rom please ?
Click to expand...
Click to collapse
Nope Odin firmware
Can someone please check if it supports hebrew?
So are they really replacing the awesome ics task manager with the Samsungs one?
Any one tried it.......or im too quick.....!!!!!
Rytkonen said:
So are they really replacing the awesome ics task manager with the Samsungs one?
Click to expand...
Click to collapse
They probably did... im still downloading the firmware. hotfile.. ugh. -.-'
LP1 - CF - Root Kernel by Chainfire: http://goo.gl/pI3Uf
Hi can anyone tell me if upgrading to ICS will wipe all my data? thanks
CF Root file?

ICS is out fot GT-I9100G in India

Hey Guys Good news for I9100G users. ICS is out for G variant of Galaxy S2. Rush to service station of your respective cities to get it. See attached screenshots to believe.
rohinmattoo said:
Hey Guys Good news for I9100G users. ICS is out for G variant of Galaxy S2. Rush to service station of your respective cities to get it. See attached screenshots to believe.
Click to expand...
Click to collapse
Im sorry , but neither Samsung India facebook not twitter page has announced or confirmed this !!!! :what:
Is this your phone ...in the screenshot ??
seems legit....tweet sammobile to make sure they notice this!
hopefully this one is true...
This is a troll, a guy called service center in India, nothing, he tried kies update nothing ...
Sent from my GT-I9100G using XDA
i posted too fast, apparently India is receiving it ...
Sent from my GT-I9100G using XDA
so anyone cn cnfirm this? everyone from india is saying they've gotten a notification from samsung saying they cn update their phone at this very moment.. true or nt @[email protected]
India/Unbranded (I9100G/LKGINU)
I9100GXXLPQ/I9100GODDLP7/I9100GDDLP5/I9100GXXLPQ
Showed up a few min ago in @SGS2Update... downloading it.
CONFIRMED!!! It is ICS!
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=IML74K
ro.build.display.id=IML74K.XXLPQ
ro.build.version.incremental=XXLPQ
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Tue May 22 14:34:51 KST 2012
ro.build.date.utc=1337664891
ro.build.type=user
ro.build.user=dpi
ro.build.host=DELL174
ro.build.tags=release-keys
ro.product.model=GT-I9100G
ro.product.brand=samsung
ro.product.name=GT-I9100G
ro.product.device=GT-I9100G
ro.product.board=tuna
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=omap4
# ro.build.product is obsolete; use ro.product.device
ro.build.product=GT-I9100G
ro.tether.denied=false
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=GT-I9100G-user 4.0.3 IML74K XXLPQ release-keys
ro.build.fingerprint=samsung/GT-I9100G/GT-I9100G:4.0.3/IML74K/XXLPQ:user/release-keys
ro.build.characteristics=phone
# Samsung Specific Properties
ro.build.PDA=I9100GXXLPQ
ro.build.hidden_ver=I9100GXXLPQ
ro.build.changelist=607196
# end build properties
#
# system.prop for T1
#
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=240
persist.sys.hdmi.on=0
#HDMI mirror transform
persist.sys.mirroring.transform=0
persist.hwc.docking.enabled=0
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
#wlan.driver.apmode "unloaded"
persist.sys.storage_preload=1
#
#System property for qemu
#
ro.kernel.qemu=0
# Multimedia prop for Smart View
media.enable-commonsource = true
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.opengles.version=131072
ro.sf.lcd_density=240
ro.config.ringtone=S_Over_the_horizon.ogg
ro.config.notification_sound=S_Whistle.ogg
ro.config.alarm_alert=Good_Morning.ogg
ro.config.media_sound=Media_preview_Touch_the_light.ogg
persist.sys.strictmode.visual=false
persist.sys.strictmode.disable=true
hwui.render_dirty_regions=false
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=128m
dalvik.vm.heapsize=128m
ro.secdirenc=true
ro.secsddecryption=true
ro.secfulldirenc=true
keyguard.no_require_sim=true
ro.com.android.dataroaming=false
ro.com.android.dateformat=MM-dd-yyyy
dev.sfbootcomplete=0
dev.powersave_fps=0
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.0_r2
ro.com.google.clientidbase=android-samsung
ro.error.receiver.default=com.samsung.receiver.error
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
ro.com.google.locationfeatures=1
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Would you please provide the download link?
http://www.hotfile.com/dl/157116396/b73d71e/I9100GXXLPQ_I9100GODDLP7_INU.zip.html
From sammobile
Sent from my GT-I9100G using Tapatalk
PDA: I9100GXXLPQ
CSC: I9100GODDLP7
Phone: I9100GDDLP5
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=IML74K
ro.build.display.id=IML74K.XXLPQ
ro.build.version.incremental=XXLPQ
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Tue May 22 14:34:51 KST 2012
ro.build.date.utc=1337664891
ro.build.type=user
ro.build.user=dpi
ro.build.host=DELL174
ro.build.tags=release-keys
ro.product.model=GT-I9100G
ro.product.brand=samsung
ro.product.name=GT-I9100G
ro.product.device=GT-I9100G
ro.product.board=tuna
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=omap4
# ro.build.product is obsolete; use ro.product.device
ro.build.product=GT-I9100G
ro.tether.denied=false
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=GT-I9100G-user 4.0.3 IML74K XXLPQ release-keys
ro.build.fingerprint=samsung/GT-I9100G/GT-I9100G:4.0.3/IML74K/XXLPQ:user/release-keys
ro.build.characteristics=phone
# Samsung Specific Properties
ro.build.PDA=I9100GXXLPQ
ro.build.hidden_ver=I9100GXXLPQ
ro.build.changelist=607196
# end build properties
https://hotfile.com/dl/157116960/433529c/GT-I9100G_INU_I9100GXXLPQ_I9100GODDLP7_I9100GDDLP5.zip.html
True info.
This is true, and sammobile confirmed this info.
---------- Post added at 08:38 AM ---------- Previous post was at 08:30 AM ----------
Direct link:
samsung-updates.com/fw/Samsung-Updates.com-GT-I9100G_INU_1_20120525220024_zn79e5qym2.zip
is this for worldwide G? any issue on bootloader?
Hey guys last time when i got an update my phone got stuck on booth logo so if this happens this time what should i do???
Sent from my GT-I9100G using xda premium
Andrewtst said:
is this for worldwide G? any issue on bootloader?
Click to expand...
Click to collapse
i didnt try it yet but i think its for the worldwide G...
Haxer87 said:
i didnt try it yet but i think its for the worldwide G...
Click to expand...
Click to collapse
Still downloading, later I try. But I believe is World Wide as already got members at facebook I9100G group success flash it.
No issue with bootloader, this is the real official stuff !
Sent from my GT-I9100G using XDA
kldoc said:
No issue with bootloader, this is the real official stuff !
Sent from my GT-I9100G using XDA
Click to expand...
Click to collapse
can i flash using mobile odin?
kldoc said:
i posted too fast, apparently India is receiving it ...
Sent from my GT-I9100G using XDA
Click to expand...
Click to collapse
Seriously!? For the "G" variant? cools.... but im in Malaysia. Hopefully we will get it soon!
I have successfully updated my I9100G to ICS.

[Q]Does fimware GT-P3100 will work on GT-P3100B?

Hello
I just really wonder so much about my Galaxy tab 2 7". As we already know that the global model number is GT-P3100 but it's really strange to mind. It shows GT-P3100B which is really strange to me and i'm really hard to fin a ROM to restore it back after flash. Anyone has any idea about it?
begin build properties
# autogenerated by buildinfo.sh
ro.build.id=IML74K
ro.build.display.id=IML74K.P3100BDCALE3
ro.build.version.incremental=P3100BDCALE3
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Fri May 11 23:37:09 KST 2012
ro.build.date.utc=1336747029
ro.build.type=user
ro.build.user=dpi
ro.build.host=DELL131
ro.build.tags=release-keys
ro.product.model=GT-P3100B
ro.product.brand=samsung
ro.product.name=espressorfdc
ro.product.device=espressorf
ro.product.board=piranha
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=omap4
# ro.build.product is obsolete; use ro.product.device
ro.build.product=espressorf
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=espressorfdc-user 4.0.3 IML74K P3100BDCALE3 release-keys
ro.build.fingerprint=samsung/espressorfdc/espressorf:4.0.3/IML74K/P3100BDCALE3:user/release-keys
ro.build.characteristics=tablet
# Samsung Specific Properties
ro.build.PDA=P3100BDCALE3
ro.build.hidden_ver=P3100BDCALE3
ro.build.changelist=CL_LABEL
# end build properties
#
# system.prop for maguro
#
# 131072 is decimal for 0x20000 to report version 2
ro.opengles.version=131072
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttys0
telephony.lteOnCdmaDevice=0
persist.sys.storage_preload=1
# System property for Default Brightness
ro.lcd_brightness=140
Click to expand...
Click to collapse
If both p3100 and p3100B have the same cpu and gpu, i think it will work. Idk, im just a noob after all.
I brought the same Galaxy tab 2 7.0 in thailand and is the same model (p3100b)
I'm with the same problem... does anyone can help us??
Thanks!
ofwise said:
I brought the same Galaxy tab 2 7.0 in thailand and is the same model (p3100b)
Click to expand...
Click to collapse
Supposedly the only difference between the P-3100 and B is the antenna. That's why the B is "optimized for 850 MHz (DTAC and True)". But both models are identical otherwise.

Categories

Resources