Develop Bugs

ANDROID SDK 2.0 is released

ANDROID SDK 2.0 is released, and I hope some of you devs/chefs wil use it to build a new custom rom for us Hero fans.
It has the multitouch feature for keyboard etc activated and build in.

O i want 2.0 so bad getting rid of the htc skin called sense (it's fun to have but not more then that!) and go like real android
If i knew enought to cook a (2.0) rom myself i would take this day of from work and will strugle til i get something working for the Hero
I will reward the dev who makes a working 2.0 ROM (with at least 90%+ working hardware) with 50 dollars (ofcourse for the HERO!)

Count my $20 in.

Why did you put this at the dev board? There is a similar one in the discussion board with more information.

As you can see here is where the real money is

You guys don't really seem to realize what it means when the SDK is released.
The same happened when the 1.6 SDK is released.
It's the _SDK_. It's the part used to write programs _FOR_ Android 2.0, not Android 2.0 itself. So with this SDK developers can start making their programs compatible with 2.0, but the actual 2.0 release is still not here.

jaapschaap said:
As you can see here is where the real money is
Click to expand...
Click to collapse
If that's the case I might as well chip in with a twenty ;-p

It's the _SDK_. It's the part used to write programs _FOR_ Android 2.0, not Android 2.0 itself. So with this SDK developers can start making their programs compatible with 2.0, but the actual 2.0 release is still not here.
Click to expand...
Click to collapse
I knew it but because of the TS his story i start believing it can be transfomrt into a ROM

dream owners using eclair rom. not the full rom but usuable. at least they can test it.

dipje said:
You guys don't really seem to realize what it means when the SDK is released.
The same happened when the 1.6 SDK is released.
It's the _SDK_. It's the part used to write programs _FOR_ Android 2.0, not Android 2.0 itself. So with this SDK developers can start making their programs compatible with 2.0, but the actual 2.0 release is still not here.
Click to expand...
Click to collapse
Yes and no.
Take a look at platforms\android-2.0\images\ in your SDK.
;]
Not a rls, but at least something to play with.

adwinp said:
Yes and no.
Take a look at platforms\android-2.0\images\ in your SDK.
;]
Not a rls, but at least something to play with.
Click to expand...
Click to collapse
Those are emulator images, not made for a specific handset, therefore they don't work correctly if you flash then or repackage the contents to update.zip's!
Look at dream board and you'll see the issues with the DEV 2.0 ROM

True, then again, what do we have unyaffs for?

i just want 2.0 to come out, now. with moto droid coming out on nov. 1, it shouldnt be hard to port hopefully. im really in love with android 2.0 and i prefer it to the sense ui, it looks so much nicer

im really excited bout what htc is doing about android2 and their sense, since android2 looks nice now either ;-) hopefully we get a sexy merge of both!

Here's the build.prop, but might as well take a look the the updated apks...
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=ECLAIR
ro.build.display.id=sdk-eng 2.0 ECLAIR 17704 test-keys
ro.build.version.incremental=17704
ro.build.version.sdk=5
ro.build.version.codename=REL
ro.build.version.release=2.0
ro.build.date=Thu Oct 22 01:18:16 PDT 2009
ro.build.date.utc=1256199496
ro.build.type=eng
ro.build.user=android-build
ro.build.host=apa4.mtv.corp.google.com
ro.build.tags=test-keys
ro.product.model=sdk
ro.product.brand=generic
ro.product.name=sdk
ro.product.device=generic
ro.product.board=
ro.product.cpu.abi=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=ldpi
ro.product.locale.region=
ro.wifi.channels=
ro.board.platform=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=generic
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=sdk-eng 2.0 ECLAIR 17704 test-keys
ro.build.fingerprint=generic/sdk/generic/:2.0/ECLAIR/17704:eng/test-keys
# end build properties
#
# 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
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
xmpp.auto-presence=true
ro.config.nocheckin=yes
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt

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.....

[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

A100 ICS Service ROM

Hello guys,
I got my hands on an ICS Service ROM for the A100. I don't know if it can be of any use to devs but you can check it out.
Build.prop extract :
Code:
ro.build.id=IML74K
ro.build.display.id=Acer_AV041_A100_1.037.00_WW_GEN1
ro.build.version.incremental=1336717425
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Fri May 11 14:24:35 CST 2012
ro.build.date.utc=1336717475
ro.build.type=user
ro.build.user=pandora
ro.build.host=pandora06
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

Is this a official stock rom package?
no modding, no addictions?
thanks

It's a Service ROM dude it's not meant for production tablet but for debugging. It might help dev who are working hard on the A100.
If you dn't know what it is don't flash it

paugustin said:
It's a Service ROM dude it's not meant for production tablet but for debugging. It might help dev who are working hard on the A510.
If you dn't know what it is don't flash it
Click to expand...
Click to collapse
+1 its not meant for general use. Stick with the stock or modded stock like flex reaper or green, or cm9 builds.
Tapatalked from my Galaxy S II.