Develop Bugs

Exactly as I thought, there's another GSM build

There's a build for Israel which is different from the usual GSM build.
baseband - I9250XXKK1
build number - I9250XWKK5_ITL41D
Later tonight I'll upload the build. prop which I got my hands on it.
Will gladly if someone will upload this build.
It includes entire Hebrew android including all menus.
Sent from my Galaxy Nexus using XDA App

The build number isn't that interesting -- the interesting is the software release codename (like yakju, yakjuw, etc. found as part of the build fingerprint.)
According to Google's JBQ, only yakju is built by Google: the rest are Samsung's.
I wonder thus if all the Hebrew L10N is in AOSP, or if some was added by Samsung. I hope for the former, as it'd reduce fragmentation of the localization (different L10N teams using different strings.)
Guess I should finally find the time to look into the ics branch in AOSP and check for myself.

Toda Idan. Glad to see a specific version for you!

It's been known for a while now that there are different builds
http://forum.xda-developers.com/showthread.php?t=1376856
http://forum.xda-developers.com/showthread.php?t=1384458

the question is, is it safe to flash the build and still get OTA?
and how can i get it?
and why google does not merge the full Hebrew support in the AOSP?

idan_mo said:
the question is, is it safe to flash the build and still get OTA?
and how can i get it?
and why google does not merge the full Hebrew support in the AOSP?
Click to expand...
Click to collapse
Can you check what "ro.product.name" is in your /system/build.prop file?

Chirality said:
Can you check what "ro.product.name" is in your /system/build.prop file?
Click to expand...
Click to collapse
I find the firmware on MoDaCo website and flashed it on my nexus using odin.
will upload the build.prop in a few mins
build.prop:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=ITL41F
ro.build.display.id=ITL41F.I9250XWKK9
ro.build.version.incremental=I9250XWKK9
ro.build.version.sdk=14
ro.build.version.codename=REL
ro.build.version.release=4.0.1
ro.build.date=Tue Nov 29 15:26:35 KST 2011
ro.build.date.utc=1322547995
ro.build.type=user
ro.build.user=dpi.sec
ro.build.host=DELL123
ro.build.tags=release-keys
ro.product.model=Galaxy Nexus
ro.product.brand=samsung
ro.product.name=yakjuxw
ro.product.device=maguro
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=maguro
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=yakjuxw-user 4.0.1 ITL41F I9250XWKK9 release-keys
ro.build.fingerprint=samsung/yakjuxw/maguro:4.0.1/ITL41F/I9250XWKK9:user/release-keys
ro.build.characteristics=nosdcard
# end build properties
#
# system.prop for maguro
#
rild.libpath=/vendor/lib/libsec-ril.so
rild.libargs=-d /dev/ttys0
telephony.lteOnCdmaDevice=0
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
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.clientidbase=android-google
ro.error.receiver.system.apps=com.google.android.feedback
ro.error.receiver.default=com.samsung.receiver.error
ro.setupwizard.mode=ENABLED
ro.setupwizard.enterprise_mode=1
ro.config.ringtone=Girtab.ogg
ro.config.notification_sound=Proxima.ogg
ro.config.alarm_alert=Cesium.ogg
keyguard.no_require_sim=true
drm.service.enabled=true
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
ro.opengles.version=131072
ro.sf.lcd_density=320
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
ro.com.google.gmsversion=4.0_r1
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Click to expand...
Click to collapse

idan_mo said:
the question is, is it safe to flash the build and still get OTA?
and how can i get it?
Click to expand...
Click to collapse
It seems that all maguro share the exact same hardware, and only differ by the software installed. If so, then you should be able to flash a different software distribution (yakju*) to any maguro device. YMMV, of course.
Note that non-yakju versions are updated by others, and not by Google.
idan_mo said:
and why google does not merge the full Hebrew support in the AOSP?
Click to expand...
Click to collapse
AOSP isn't yakju. It's like the difference between source code and a distribution of binaries (consider the source composing a Linux distribution with the installation CD.)
You can't find a phone with AOSP pre-installed, but are expected to build it yourself (and that does seem to have Hebrew and Arabic L10N.)

OK, I've few questiond:
1. Any chance for example to merge the Hebrew language files in AOSP or in a costume rom like Revolution HD?
2. will my nexus will have future updates OTA from Samsung with this firmware?
3. Is it possible to flash updates for the yakju version on yakjuwx as they are the same?
The issue is I don't want to lose Samsung full Hebrew support and still have pure Android.
Sent from my Galaxy Nexus using xda premium

idan_mo said:
1. Any chance for example to merge the Hebrew language files in AOSP or in a costume rom like Revolution HD?
Click to expand...
Click to collapse
Hebrew L10N is already in AOSP (full_maguro builds; You can get one by repo sync; lunch full_maguro-user etc. RTFM)
idan_mo said:
2. will my nexus will have future updates OTA from Samsung with this firmware?
Click to expand...
Click to collapse
According to what Google's GBQ has shared, yakju builds get OTA updates from Google. yakju(.+) builds get OTA updates from Samsung.
idan_mo said:
3. Is it possible to flash updates for the yakju version on yakjuwx as they are the same?
Click to expand...
Click to collapse
yakju and yakjuwx are not the same. They are different software distributions.
The hardware used (maguro,) is probably the same. But again YMMV and usual disclaimer, etc.

What is the stock build number?

I need the stock build number because I'm having issues with the game, 9mm HD, I bought and the their customer service needs my build number for some reason. I don't want to give them my current build number because I'm rooted running a custom ROM and I think they'll abandon my case if they know this.
I'll make sure to hit the thanks button to whoever answers and thanks in advanced.

Tazdeviloo7 said:
I need the stock build number because I'm having issues with the game, 9mm HD, I bought and the their customer service needs my build number for some reason. I don't want to give them my current build number because I'm rooted running a custom ROM and I think they'll abandon my case if they know this.
I'll make sure to hit the thanks button to whoever answers and thanks in advanced.
Click to expand...
Click to collapse
Code:
ro.build.id=GINGERBREAD
ro.build.display.id=GINGERBREAD.EG30
ro.build.version.incremental=EG30
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.4
ro.build.date=Sat Jul 30 23:45:43 KST 2011
ro.build.date.utc=1312037143
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEP-55
ro.build.tags=release-keys
ro.build.PDA=SPH-D710.EG30
ro.build.hidden_ver=SPH-D710.EG30
ro.build.changelist=435734
ro.build.product=SPH-D710
ro.build.description=SPH-D710-user 2.3.4 GINGERBREAD EG30 release-keys
ro.build.fingerprint=samsung/SPH-D710/SPH-D710:2.3.4/GINGERBREAD/EG30:user/release-keys
ro.build.PDA=SPH-D710.EG30
ro.build.hidden_ver=SPH-D710.EG30
ro.build.changelist=435734
ro.product.model=SPH-D710
ro.product.brand=samsung
ro.product.name=SPH-D710
ro.product.device=SPH-D710
ro.product.board=SPH-D710
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.board.platform=s5pc210

Tazdeviloo7 said:
I need the stock build number because I'm having issues with the game, 9mm HD, I bought and the their customer service needs my build number for some reason. I don't want to give them my current build number because I'm rooted running a custom ROM and I think they'll abandon my case if they know this.
I'll make sure to hit the thanks button to whoever answers and thanks in advanced.
Click to expand...
Click to collapse
Are u having the issue where it just magically closes?
Sent from my fingertips to youre eyeballs.....

[ROM] I927UCKI3 [23.09.2011][Android 2.3.5]

I927UCKI3:
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=GINGERBREAD
ro.build.display.id=GINGERBREAD.UCKI3
ro.build.version.incremental=UCKI3
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.5
ro.build.date=Fri Sep 23 11:16:36 KST 2011
ro.build.date.utc=1316744196
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEP-79
ro.build.tags=release-keys
ro.product.model=SAMSUNG-SGH-I927
ro.product.brand=samsung
ro.product.name=SGH-I927
ro.product.device=SGH-I927
ro.product.board=SGH-I927
ro.product.cpu.abi=armeabi-v7a
# Samsung Specific Properties
ro.build.PDA=I927UCKI3
ro.build.hidden_ver=I927UCKI3
ro.build.changelist=601619
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=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=SGH-I927
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=SGH-I927-user 2.3.5 GINGERBREAD UCKI3 release-keys
ro.build.fingerprint=samsung/SGH-I927/SGH-I927:2.3.5/GINGERBREAD/UCKI3:user/release-keys
# Samsung Specific Properties
ro.build.PDA=I927UCKI3
ro.build.hidden_ver=I927UCKI3
ro.build.changelist=601619
ro.tether.denied=false
ro.flash.resolution=1080
# end build properties
Download:
http://hotfile.com/dl/137505177/0a48afe/SGH-I927_ATT_I927UCKI3.rar.html
Pass: sampro.pl

So what's different about this ROM?

Rockwig said:
So what's different about this ROM?
Click to expand...
Click to collapse
Well, we dont know until we try it. A letter change is usually a bigger update than a letter so we know at least a few things have i changed, i hope it has the black gallery fix...

Usually when I ROM is posted, a change log is posted as well. That would be nice in this. At least so there is some idea on what people could be flashing.

Rockwig said:
Usually when I ROM is posted, a change log is posted as well. That would be nice in this. At least so there is some idea on what people could be flashing.
Click to expand...
Click to collapse
Looking at his other posts, I think its an update to the official stock firmware. Probably leaked.

Nice thanks!

Has anyone tried this rom yet? Any news on the differences?
Sent from my SAMSUNG-SGH-I927 using XDA App

This is a firmware update leaked by Samsung. It will be stock, no root, no CW Recovery. All carrier bloatware will be in place.
Assuming this works the same as the I897 leaks, you'll need Odin to install it.
Przekret is great posting the newest "official" leaks so when you see him posting ROMs it's safe to assume it'll be a stock leak. He has been great in providing leaks for the I897 devs and us ROM flashaholics.

Thanks so much.It is always nice to see new updates and people willing to share with us ;-)

is this the latest stock rom?

As far as I know the latest version is 2.3.6.

shinydesert said:
As far as I know the latest version is 2.3.6.
Click to expand...
Click to collapse
Can u provide me a link or a system dump?i m gonna make a custom rom.

I was able to download it last Friday night,but right after that I changed the kernel and installed a rooted 2.3.5 version.
Last night I checked for new updates and the device downloaded the new update but the installation failed,if you think there is a way to find those new files I will be more than glad to dig into the phone.

any noticeable difference b/w the 2?(performance,i mean)
u shud have had a nandroid backup

sakindia123 said:
any noticeable difference b/w the 2?(performance,i mean)
u shud have had a nandroid backup
Click to expand...
Click to collapse
I don't think 2.3.6 added anything significant other than a really minor 'feature' so I suggest working with 2.3.5 if no one comes forth with a 2.3.6 dump soon.

vil33 said:
I don't think 2.3.6 added anything significant other than a really minor 'feature' so I suggest working with 2.3.5 if no one comes forth with a 2.3.6 dump soon.
Click to expand...
Click to collapse
so i started makin a rom based on this.
Ps-U have a hell lot of bloatware!

This is a stock firmware leak...that alone should tell you it will have all of at&t's bloatware in it.

Rogers ROM is a better starting point in my opinion. It's very similar to AT&T but there is manual operator setup in networks and delivery reports for messages. Both features are missing in AT&T ROM but are quite useable.

too bad.i already made the rom as i couldnt find any other

SGH-I927/ATT/I927UCKI3/I927ATTKI3/I927UCKI3
from this (2.3.5) somebody have 4 files version with pit?
I looking for...!!!

[Q] Acer ICS Leak to Acer ICS Official

I have the leaked version of ICS installed on my A100, I didn't get the Official version over the air. Is there any way to downgrade to Honeycomb to get the official as the leaked version has been giving my tablet camera issues with green flickering etc.

Here is my build.prop
build.prop
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=IML74K
ro.build.display.id=Acer_AV041_A100_0.009.00_WW_GEN1
ro.build.version.incremental=1331290290
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Fri Mar 9 18:52:40 CST 2012
ro.build.date.utc=1331290360
ro.build.type=user
ro.build.user=pandora
ro.build.host=pandora03
ro.build.tags=release-keys
ro.build.sku=WW_GEN1
ro.product.model=A100
ro.product.brand=acer
ro.product.name=a100_ww_gen1
ro.product.device=vangogh
ro.product.board=vangogh
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Acer
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=vangogh
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=a100_ww_gen1-user 4.0.3 IML74K 1331290290 release-keys
ro.build.fingerprint=acer/a100_ww_gen1/vangogh:4.0.3/IML74K/1331290290:user/release-keys
ro.build.characteristics=tablet
# end build properties
ro.opengles.version=131072
wifi.interface=wlan0
keyguard.no_require_sim=1
ro.dinfo.version=1.0
ro.cpu.vendor=nVidia
ro.cpu.speed=1.0 GHz
ro.cpu.version=T20
ro.sf.lcd_density=160
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.error.receiver.system.apps=com.acer.android.nidus
acer.sync.adb.mode=ENABLED
ro.setupwizard.mode=DISABLED
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
ro.com.google.clientidbase=android-acer
drm.service.enabled=true
ro.product.modelalias=A100
ro.tether.denied=true
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

+1. A link to which HC to download would be nice!

Possible fix
Just came across this a manual way to put the official update on using the same procedure we used for the leak. Going to give it a try hopefully It doesn't botch my tablet.
http://forum.xda-developers.com/showthread.php?t=1611696

citricube said:
Just came across this a manual way to put the official update on using the same procedure we used for the leak. Going to give it a try hopefully It doesn't botch my tablet.
http://forum.xda-developers.com/showthread.php?t=1611696
Click to expand...
Click to collapse
Ok cool. Tell me how it goes. Im not sure if I wanna try anything because I dont wanna ruin the tablet...its still pretty good with our leak.

Success
In terms of functionality the upgrade went through to the current Official release however my green flickering camera glitch isn't resolved It's either b/c I rooted my tablet or It's just a hardware error -__-

Camera
I was initially still having camera issues even after I patched on the OTA update. However, after a factory reset it seems to be working so far. Going to keep my eye on it and see If the issue comes back as It has many times.

I have two A100 tablets. One is running the latest leaked version of ICS and the other got the OTA update. About Tablet reports the same version for the Image Version and the Build Number on both tablets.

Thanks, sorry about the delay
It was just a hardware issue had it sent into Acer Service Center and they replaced my camera component. I'm not having good luck with my A100 though lol. I pressed the reset button when the tablet was running sluggish the other day and it hung up on the android logo. Tried fixing it and messed it up even more!
hahne said:
I have two A100 tablets. One is running the latest leaked version of ICS and the other got the OTA update. About Tablet reports the same version for the Image Version and the Build Number on both tablets.
Click to expand...
Click to collapse

[ROM][SGH-T889 / T0LTETMO][4.4.4][UNOFFICIAL] CyanogenMod 11 - Builds of opportunity

As many of you know the GSM Note 2 is supported by CyanogenMod in a unified build format. This work is simply monumental with a beautiful product. Many in the T-Mobile Note 2 community are reluctant to use the unified build for a variety of reasons.
Nicktastique and rmanne picked up the mantle and provided us with device specific unofficial CM11 builds. As rmanne has transitioned to a new device, I saw that I would be able to give back to the T889 community and pick up the yoke and keep us moving forward.
My product is no more than a straight source built t0ltetmo build as the CM11 spec is drawn up for the t0ltetmo on the CM github. All source is available at the CM git. I make no changes unless noted (in the remote chance that changes occur they will be documented/git referrenced).
I make no promises or warranty of any kind, all flashing is done at your own risk and should not be thought to be the responsibility of anyone other than the person deciding to flash the ROM. While I will attempt to help you work through issues, I do not plan on integrating non-CM commits or "fixes" with very few exceptions.
I plan on putting up new builds weekly if not a bit more frequently if I am inspired. If I see a change in CM commits that looks promising I expect that I would post a new build.
Flashing instructions:
Using the most current TWRP, ClockworkMod, or PhilzTouch recovery; wipe data, system, cache, and dalvik (especially if coming from a different ROM).
Flash the unofficial CM .zip file from the link below
Flash the gapps of your choice (CM or PA are good)
Boot phone and let sit on a stationary flat surface.
Do not touch the device for 10 minutes to allow the caches to build.
Reboot the device and set up
cm-11-20150322-COUGMADE-t0ltetmo.zip
cm-11-20150313-COUGMADE-t0ltetmo.zip
cm-11-20150222-COUGMADE-t0ltetmo.zip
cm-11-20150206-COUGMADE-t0ltetmo.zip
cm-11-20150116-COUGMADE-t0ltetmo.zip
cm-11-20150107-COUGMADE-t0ltetmo.zip
cm-11-20150101-COUGMADE-t0ltetmo.zip
cm-11-20141220-COUGMADE-t0ltetmo.zip
cm-11-20141216-COUGMADE-t0ltetmo.zip
cm-11-20141212-COUGMADE-t0ltetmo.zip
cm-11-20141209-COUGMADE-t0ltetmo.zip
cm-11-20141206-COUGMADE-t0ltetmo.zip
cm-11-20141201-COUGMADE-t0ltetmo.zip
cm-11-20141126-COUGMADE-t0ltetmo.zip
cm-11-20141027-COUGMADE-t0ltetmo.zip
cm-11-20141020-COUGMADE-t0ltetmo.zip
cm-11-20141011-UNOFFICIAL-t0ltetmo.zip
cm-11-20141002-UNOFFICIAL-t0ltetmo.zip
cm-11-20140921-UNOFFICIAL-t0ltetmo.zip
cm-11-20140914-UNOFFICIAL-t0ltetmo.zip
cm-11-20140906-UNOFFICIAL-t0ltetmo.zip
cm-11-20140831-UNOFFICIAL-t0ltetmo.zip
cm-11-20140826-UNOFFICIAL-t0ltetmo.zip
cm-11-20140818-UNOFFICIAL-t0ltetmo.zip
cm-11-20140810-UNOFFICIAL-t0ltetmo.zip
cm-11-20140806-UNOFFICIAL-t0ltetmo.zip
CyanogenMod Gapps
PA Gapps (good variety of options)
All source code for CyanogenMod is available in the CyanogenMod Github.
CM t0lte git
CM t0ltetmo git
DonkeyCoyote Samsung Vendor git
Props and credit to:
CyanogenMod team (especially t0lte maintainers codeworkx and madmack for their hardwork toward insuring that the Note 2 is kept in the loop).
UtkarshGupta for providing advice in working through build issues on compiling Omni that translated to quick work on CM.
Rmanne for assistance in getting running by help with troubleshooting the build process.
And certainly not least mattlowry for being solid from his first posts in the doubleshot community, evolving along with weekendsR2short to porting for the doubleshot, and elevating his game on the Note 2. His advice and example made the unfathomable become doable.

Mine

Gimme

How is it so far?

Everything seems to be working fine, just as with the unified build, t0lte.
The only thing I was hoping to see in the t0ltetmo build was getting rid of the 'US' as the network provider in the pulldown handle and lockscreen and show T-Mobile instead. Of course I could xpose and change it, but was hoping not to have to do that.
Other than that, the build is solid and bug-free as far as my usage matters.
Thanks for the build, OP!

carlz28 said:
Everything seems to be working fine, just as with the unified build, t0lte.
The only thing I was hoping to see in the t0ltetmo build was getting rid of the 'US' as the network provider in the pulldown handle and lockscreen and show T-Mobile instead. Of course I could xpose and change it, but was hoping not to have to do that.
Other than that, the build is solid and bug-free as far as my usage matters.
Thanks for the build, OP!
Click to expand...
Click to collapse
Yup. The carrier network label has been the bane of my post-build existence. It iritates me too. I figured that someone would mention it on the first page.
Selective-spn-conf.xml doesn't seem to do much for it either. That is my first order of business once I get my other ROM project working (the one I was planning on before rmanne picked up a new device).

nice!

Coug76 said:
Yup. The carrier network label has been the bane of my post-build existence. It iritates me too. I figured that someone would mention it on the first page.
Selective-spn-conf.xml doesn't seem to do much for it either. That is my first order of business once I get my other ROM project working (the one I was planning on before rmanne picked up a new device).
Click to expand...
Click to collapse
No worries! Its one of those OCD things that bugs me on any ROM/device. Wish I could help narrow down the issue but I have no coding/devving/ROM building skills.
2 days running now and no other issues. Definitely a DD build!

New build is up.

Coug76 said:
New build is up.
Click to expand...
Click to collapse
still couldn't figured out how to change the network name?

zain0300 said:
still couldn't figured out how to change the network name?
Click to expand...
Click to collapse
No. I don't have a timeline either. I do this for fun, in my spare time. It may be tomorrow. It may be next month. I am also working on another project as well.

Coug76 said:
No. I don't have a timeline either. I do this for fun, in my spare time. It may be tomorrow. It may be next month. I am also working on another project as well.
Click to expand...
Click to collapse
i never asked when are you gonna fix it

What don't u try to edit build.prop
Sent from my SGH-T889 using XDA Free mobile app

sipher26 said:
What don't u try to edit build.prop
Sent from my SGH-T889 using XDA Free mobile app
Click to expand...
Click to collapse
What did you get to work? I am hoping to trip over something soon. I have been mucking around in the .conf files for a while now.

I'm going download this tomorrow and try and see build.prop where the edit can be done or not
Sent from my SGH-T889 using XDA Free mobile app

sipher26 said:
I'm going download this tomorrow and try and see build.prop where the edit can be done or not
Sent from my SGH-T889 using XDA Free mobile app
Click to expand...
Click to collapse
Here is the build.prop. If you let me know I can try it out as I have a nandroid sitting on my SD card all the time.
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=KTU84Q
ro.build.display.id=cm_t0ltetmo-userdebug 4.4.4 KTU84Q bd05cc81b5 test-keys
ro.build.version.incremental=bd05cc81b5
ro.build.version.sdk=19
ro.build.version.codename=REL
ro.build.version.release=4.4.4
ro.build.date=Sat Aug 9 22:04:17 PDT 2014
ro.build.date.utc=1407647057
ro.build.type=userdebug
ro.build.user=cougatron
ro.build.host=cougatron-MS-7793
ro.build.tags=test-keys
ro.product.brand=samsung
ro.product.name=t0ltetmo
ro.product.board=smdk4x12
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=t0ltetmo
ro.product.model=SGH-T889
ro.product.device=t0ltetmo
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=t0ltetmo-user 4.1.2 JZO54K T889UVBMB4 release-keys
ro.build.fingerprint=samsung/t0ltetmo/t0ltetmo:4.1.2/JZO54K/T889UVBMB4:user/release-keys
ro.build.characteristics=default
ro.cm.device=t0ltetmo
# end build properties
#
# from device/samsung/t0ltetmo/system.prop
#
#
# system.prop for t0ltetmo
#
rild.libpath=/system/lib/libril-qc-qmi-1.so
rild.libargs=-d /dev/ttyS0
ro.telephony.default_network=9
telephony.lteOnGsmDevice=1
ro.sf.lcd_density=320
ro.lcd_min_brightness=20
# System property ril adb log on
persist.radio.adb_log_on=1
# For sys info indication
persist.radio.add_power_save=1
# System property for SIM
persist.radio.apm_sim_not_pwdn=1
ro.com.google.clientidbase=android-samsung
ro.com.google.clientidbase.ms=android-tmobile-us
ro.com.google.clientidbase.am=android-tmobile-us
ro.com.google.clientidbase.yt=android-samsung
ro.com.google.clientidbase.gmm=android-samsung
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.rommanager.developerid=cyanogenmod
ro.com.google.clientidbase=android-google
keyguard.no_require_sim=true
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.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.build.selinux=1
persist.sys.dalvik.multithread=false
persist.sys.dun.override=0
persist.sys.root_access=1
ro.cm.version=11-20140810-UNOFFICIAL-t0ltetmo
ro.cm.releasetype=UNOFFICIAL
ro.modversion=11-20140810-UNOFFICIAL-t0ltetmo
ro.cmlegal.url=http://www.cyanogenmod.org/docs/privacy
persist.sys.recovery_update=false
ro.cm.display.version=11-20140810-UNOFFICIAL-t0ltetmo
ro.config.notification_sound=Argon.ogg
ro.config.alarm_alert=Hassium.ogg
ro.config.ringtone=Orion.ogg
ro.carrier=unknown
ro.telephony.ril_class=SamsungQualcommRIL
mobiledata.interfaces=pdp0,wlan0,gprs,ppp0
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
ro.zygote.disable_gl_preload=1
ro.opengles.version=131072
ro.bq.gpu_to_cpu_unsupported=1
debug.hwui.render_dirty_regions=false
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=2m
dalvik.vm.heapmaxfree=8m
persist.sys.dalvik.vm.lib=libdvm.so
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt

sipher26 said:
I'm going download this tomorrow and try and see build.prop where the edit can be done or not
Sent from my SGH-T889 using XDA Free mobile app
Click to expand...
Click to collapse
Any luck?

New build up.

looks to me that it is showing your region.local instead of your service provider

mattlowry said:
looks to me that it is showing your region.local instead of your service provider
Click to expand...
Click to collapse
I'm trying to figure out how to fix it and am getting frustrated with it. That same behavior is present in the official builds of CM and Omni. I have been digging through the source git for AOKP to see if I can tell how they are making it work. I can only work on it after the kids are in bed but before I sleep. My eyes are starting to cross...