Database Develop

1.3 is out!

Got this tweet today:
1.3 Firmware is here! The Award-Winning NOOK Color now has People, Time, SI, Fitness & more. Details: bit.ly/pty5x6
I wouldn't suggest updating until we get a root going on it.

Yep, here is the official info on the B&N site:
Barnes & Noble is providing a firmware update for NOOK Color that contains exciting new features and provides ongoing performance improvements. Among the new features, NOOK Color v1.3 now offers access to special edition NOOK Magazines™ with enhanced interactivity and bonus features. The software update will be automatically downloaded to devices that are registered and connected to Wi-Fi®, beginning the week of August 22nd. There's no need for you to take any action. However, if you'd prefer to update your device immediately, the software update is also available via a manual download offered here, with further instructions below. To check the current software version of your NOOK Color, please click here to learn more.
Get Version 1.3.0 Today
What's new in Ver1.3.0?
The NOOK Color Ver1.3.0 update contains new features and enhancements, including:
Access to a selection of new special edition NOOK Magazines -- People, Time, Sports Illustrated, Fortune, Parents, and Fitness – featuring print edition content, plus video, audio and fun extras.
Access to the largest digital magazine selection available anywhere.
Print subscribers to People, Time, Sports Illustrated, and Fortune get free NOOK editions of those magazines.
Parental control to easily disable the Web browser.
Ongoing enhancements to Wi-Fi connectivity and other performance improvements.

I assume they're still running Froyo

fireware 1.3
Loaded on the stock side of a dual-boot Nook Color.
Seems faster boot so far and a lil faster web browser.
And yes.... still Froyo.

votinh said:
I assume they're still running Froyo
Click to expand...
Click to collapse
2.2.1 - here's the build.prop:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=MASTER
ro.build.display.id=MASTER.1.3.0
ro.build.version.incremental=1.3.0
ro.build.version.sdk=8
ro.build.version.codename=REL
ro.build.version.release=2.2.1
ro.build.date=Wed Aug 17 15:21:14 PDT 2011
ro.build.date.utc=1313619674
ro.build.type=user
ro.build.user=build
ro.build.host=dhabuildimage17
ro.build.tags=test-keys
ro.product.model=NOOKcolor
ro.product.brand=nook
ro.product.name=zoom2
ro.product.overall.name=NOOKcolor
ro.product.device=zoom2
ro.product.board=zoom2
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=BarnesAndNoble
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=omap3
# ro.build.product is obsolete; use ro.product.device
ro.build.product=zoom2
ro.build.sourceversion=full
ro.build.description=1.3.0.521.int.enc.rrdp.s44977
ro.build.updatetype=Full
ro.build.fingerprint=enc/zoom2/zoom2/zoom2:2.2.1/MASTER/1.3.0:user/test-keys
# end build properties
###################################
#Browser Performance Optimizations
###################################
browser.tioptimization=true
connection.concurrent=10
###################################
# system.prop for zoom2
# This overrides settings in the products/generic/system.prop file
#
# rild.libpath=/system/lib/libreference-ril.so
# rild.libargs=-d /dev/ttyS0
# ro.sf.lcd_density=240
ro.sf.widthpixels=600
ro.sf.heightpixels=1024
ro.sf.lcd_density.xdpi=169.33333
ro.sf.lcd_density.ydpi=169.33333
opencore.asmd=1
keyguard.no_require_sim=1
wifi.interface=tiwlan0
alsa.mixer.playback.master=DAC2 Analog
alsa.mixer.capture.master=Analog
#ro.media.dec.aud.wma.enabled=1
#ro.media.dec.vid.wmv.enabled=1
dalvik.vm.heapsize=64m
ro.opengles.version=131072
ro.sf.hwrotation=270
# Define JPEG codec to load. (Set libskiahw with 1 & Set ARM with 0)
jpeg.libskiahw.decoder.enable=1
# Define JPEG Threashold for Image size (bytes)
jpeg.libskiahw.decoder.thresh=1000000
browser.tioptimization=true
connection.concurrent=10
ro.media.dec.aud.wma.enabled=1
ro.media.dec.vid.wmv.enabled=1
#Disable some feature depending on the board capabilities
ro.disable.bluetooth=0
ro.disable.camera=1
ro.disable.hdmi=1
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=false
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=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
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt

lostboy1952 said:
Loaded on the stock side of a dual-boot Nook Color.
Seems faster boot so far and a lil faster web browser.
And yes.... still Froyo.
Click to expand...
Click to collapse
How did you go about updating the stock side? I have Phiremod as the first boot, and stock Nook as the second. I've updated Phiremod before just using Clockwork, but not sure how I'd update the stock side.
thanks!

According to this thread over at B&N forums:
http://bookclubs.barnesandnoble.com...folk/m-p/1139798/message-uid/1139798#U1139798
B&N has overclocked to 900mhz on stock.

doncaruana said:
2.2.1 - here's the build.prop:
ro.build.version.incremental=1.3.0
ro.build.date=Wed Aug 17 15:21:14 PDT 2011
ro.build.date.utc=1313619674
ro.build.description=1.3.0.521.int.enc.rrdp.s44977
ro.build.fingerprint=enc/zoom2/zoom2/zoom2:2.2.1/MASTER/1.3.0:user/test-keys
Click to expand...
Click to collapse
Thanks for posting that, I'm updating my other thread with this.

jpeg42 said:
According to this thread over at B&N forums:
http://bookclubs.barnesandnoble.com...folk/m-p/1139798/message-uid/1139798#U1139798
B&N has overclocked to 900mhz on stock.
Click to expand...
Click to collapse
Are they using Dal's kernel?

Any kernel version changes?

what wifi improvements? adhoc/infrastructure fix maybe?

Is it safe to allow the update to go through if you are running CM7 off of SD?
I would hate to find any nasty surprises like a force boot from emmc only.

Imbroglio said:
Is it safe to allow the update to go through if you are running CM7 off of SD?
I would hate to find any nasty surprises like a force boot from emmc only.
Click to expand...
Click to collapse
No way. The boot firmware will always boot the sd card first. If it doesn't, I will personally go to the closest BN store and punch the first staff person I see.

Imbroglio said:
Is it safe to allow the update to go through if you are running CM7 off of SD?
I would hate to find any nasty surprises like a force boot from emmc only.
Click to expand...
Click to collapse
Why not remove your uSD off the NC and let the update runs?

Imbroglio said:
Is it safe to allow the update to go through if you are running CM7 off of SD?
I would hate to find any nasty surprises like a force boot from emmc only.
Click to expand...
Click to collapse
Just remove the SD card and update like normal.
Sent from my NookColor using Tapatalk

lostboy1952 said:
Loaded on the stock side of a dual-boot Nook Color.
Seems faster boot so far and a lil faster web browser.
And yes.... still Froyo.
Click to expand...
Click to collapse
Lostboy, how did you do the update? I was thinking that might be able to by just booting into Nook OS and doing the update. I am dual boot with CM7 nightlies.
--bill

According to the developer of DVD Catalyst 4, the 1.3 update solves the video playback degradation issue that was introduced with 1.2:
http://www.tools4movies.com/2011/08/bn-nookcolor-1-3-update/
That's very good news for anyone who wants to stick with the stock OS.

dsf3g said:
According to the developer of DVD Catalyst 4, the 1.3 update solves the video playback degradation issue that was introduced with 1.2:
http://www.tools4movies.com/2011/08/bn-nookcolor-1-3-update/
That's very good news for anyone who wants to stick with the stock OS.
Click to expand...
Click to collapse
That's good news, that means new video drivers and/or kernel, once B&N releases the source for 1.3 the benefits should come rolling into CM7.

joenathane said:
That's good news, that means new video drivers and/or kernel, once B&N releases the source for 1.3 the benefits should come rolling into CM7.
Click to expand...
Click to collapse
I wasn't aware B&N was releasing any of their source code....

If I am running CM7 on emmc then I don't do anything. Is that right?

[ROM] S5570XWKS7 [15.10.2011][Android 2.3.5]

S5570XWKS7:
Android 2.3.5
Code:
# autogenerated by buildinfo.sh
ro.build.id=GINGERBREAD
ro.build.display.id=GINGERBREAD.XWKS7
ro.build.version.incremental=XWKS7
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.5
ro.build.date=Sat Oct 15 17:15:04 KST 2011
ro.build.date.utc=1318666504
ro.build.type=user
ro.build.user=root
ro.build.host=DELL133
ro.build.tags=release-keys
ro.product.brand=samsung
ro.product.model=GT-S5570
ro.product.name=GT-S5570
ro.product.device=GT-S5570
ro.product.board=GT-S5570
# ro.build.product is obsolete; use ro.product.device
ro.build.product=GT-S5570
ro.product.cpu.abi=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=msm7k
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=GT-S5570-user 2.3.5 GINGERBREAD XWKS7 release-keys
ro.build.fingerprint=samsung/GT-S5570/GT-S5570:2.3.5/GINGERBREAD/XWKS7:user/release-keys
# Samsung Specific Properties
ro.build.PDA=S5570XWKS7
ro.build.hidden_ver=S5570XWKS7
ro.build.changelist=650682
ro.build.buildtag=
# end build properties
Download:
CSC:FOP
http://hotfile.com/dl/133844590/52f89f3/GT-S5570_FOP_S5570XWKS7_S5570OXXKS2_S5570XWKS2.rar.html
CSC:DBT
http://hotfile.com/dl/134566361/137fb74/GT-S5570_DBT_S5570XWKS7_S5570XWKS2_S5570DBTKS1.rar.html
Pass: sampro.pl

wifi dis- and reconnects several times with this rom (sometimes the device doesn't reconnect too).
when i use a rom like S5570XEUKP1 for example, everything's good.
anybody have a solution for this?

no one have this problem with this fw too?

/push......

Nope never had this kinda of problem with this firmware.
I only reverted back to 2.2.1 (for now) because sometimes there was some lag and the animations were not so smooth as the old ones.

something really strange here -.-
when i google my problem with ks7, i don't find more user with same problem.
i reset my router too, but nothing chnages.
i do not understand, i'm at a loss.

ps2011 said:
something really strange here -.-
when i google my problem with ks7, i don't find more user with same problem.
i reset my router too, but nothing chnages.
i do not understand, i'm at a loss.
Click to expand...
Click to collapse
If your router supports it, try to set the WiFi to one of the 1st-6th channels.
I've seen some smartphones acting funny when the router wifi is working at 11-12 channels.

i see now, wifi problem relates not only to ks7, but all 2.3.5. fw's.

added: S5570XWKS7 CSC:DBT Android 2.3.5

Germany.
DBT = GERMANY
Am i right ?

moving this thread to android development

ps2011 said:
i see now, wifi problem relates not only to ks7, but all 2.3.5. fw's.
Click to expand...
Click to collapse
Hmm, maybe you should try to change the wifi settings? Worked for me!
1. >Settings > Wireless and networks > Wi-Fi settings.
2. Press menu-button > Advanced.
3. Change the 'Wi-Fi sleep policy'.
That solved the trick for me at least!

[System Dump] Android 4.1 Jelly Bean SDK...Let the hacking begin!!!

Android 4.1 Jelly Bean SDK Image System Dump
Here you go, I dumped the system of Android 4.1 Jelly Bean from Android 4.1 SDK image.... Let the hacking begin!!!
Download
Android-4.1-JellyBean-SDK-SystemDump.zip
MD5: 9461D2F1ED6B47D939AC8C52AC798A39
Build Prop File Content
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JRN83C
ro.build.display.id=sdk-eng 4.1 JRN83C 391408 test-keys
ro.build.version.incremental=391408
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1
ro.build.date=Sat Jun 23 01:40:53 UTC 2012
ro.build.date.utc=1340415653
ro.build.type=eng
ro.build.user=android-build
ro.build.host=vpak16.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-v7a
ro.product.cpu.abi2=armeabi
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 ro.build.description or .fingerprint
ro.build.description=sdk-eng 4.1 JRN83C 391408 test-keys
ro.build.fingerprint=generic/sdk/generic:4.1/JRN83C/391408:eng/test-keys
ro.build.characteristics=default
# 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
xmpp.auto-presence=true
ro.config.nocheckin=yes
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Click to expand...
Click to collapse
The system dump for Android 4.1 has been pulled from the GSM Galaxy Nexus update, and ready for developers to get their talented little hands on
Download:http://minus.com/lby5qoGOSNGmyS
What i've done until now:
- /system/app
- fonts, framework, media, tts, usr, xbin
- copyed busybox from CM9
- Edited build.prop
- Added some missing files in /system/bin
Doing now:
Unpacking boot.img
Problems:
ramdisk

Sweeeeeeeeeeeetttttt

Let make this post on the top of thread....make easy for all our talent Rom Developer

:good:

oh~ wow!!!

NICE...but it would be better if a moderator or a senior developer makes a thread with more info...AND MAKE IT STICKY.....so that its more helpfull

Does it work, i mean... even a bit on our N7000 ?

Wait for imilka, cm team or kang team
Sent from my GT-N7000 using Tapatalk 2

Nice bro thanks :victory:

sorcio46 said:
Does it work, i mean... even a bit on our N7000 ?
Click to expand...
Click to collapse
ofcourse it will.....we have a dual core 1.4GHZ processor...Its a BEAST...it can take this Bean without much problems ...and this is an update to ICS...so our Note was made for ICS...It can take this too...

Rulinglionadi said:
ofcourse it will.....we have a dual core 1.4GHZ processor...Its a BEAST...it can take this Bean without much problems ...and this is an update to ICS...so our Note was made for ICS...It can take this too...
Click to expand...
Click to collapse
Ya...not much different...can't wait jellybean port at note

Rulinglionadi said:
NICE...but it would be better if a moderator or a senior developer makes a thread with more info...AND MAKE IT STICKY.....so that its more helpfull
Click to expand...
Click to collapse
Dun worried all senior developer will releases their own custom rom soon...

kfheaven said:
Dun worried all senior developer will releases their own custom rom soon...
Click to expand...
Click to collapse
True...we will be seeing a CM 9.1 midNightlies ....soon... :silly:

My body is ready.

Rulinglionadi said:
ofcourse it will.....we have a dual core 1.4GHZ processor...Its a BEAST...it can take this Bean without much problems ...and this is an update to ICS...so our Note was made for ICS...It can take this too...
Click to expand...
Click to collapse
Depending on lib dependancy on kernel drivers the best you can hope for will be a port based on ICS kernel which will be fugly.
Frameworks etc in their compiled state are only reversible to smali and xml so the significance of this isnt great for any real development. First one needs to wait for flagship releases and then the source to drop.
Sent from my GT-N7000 using xda premium

Lol, kinda defeats the whole standardization point,
Should be just as easy as mapping points. The interchangability is on the wrong layer. Wonder why that still isnt possible in OS land
Sent from my GT-N7000 using Tapatalk 2

baz77 said:
Lol, kinda defeats the whole standardization point,
Should be just as easy as mapping points. The interchangability is on the wrong layer. Wonder why that still isnt possible in OS land
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Go for it then
Sent from my GT-N7000 using xda premium

this is for the samsung galaxy note or to sdk on computer ? .

:good:

kfheaven said:
Android 4.1 Jelly Bean SDK Image System Dump
Here you go, I dumped the system of Android 4.1 Jelly Bean from Android 4.1 SDK image.... Let the hacking begin!!!
Download
Android-4.1-JellyBean-SDK-SystemDump.zip
MD5: 9461D2F1ED6B47D939AC8C52AC798A39
Build Prop File Content
Click to expand...
Click to collapse
:good::good::good:All the very Best our whole wishes with you......cant wait to be ported in jellybeam android v4.1.... :good::good::good:

[ROM][ICS]Ideapad K1 Official Release

Hi everyone,
As most of you know Lenovo released the official ICS build for the Ideapad K1 today. The new bootloader will not allow me to boot into recovery partition, so no custom recovery for now. Unfortunately the build released by Lenovo also lacked Google Apps. I have added in the latest Google Apps package including Face Unlock. I have posted two versions of the Rom both rooted and not rooted. The non rooted is 100% stock with Google Apps. The rooted has the latest Superuser.apk and su binary and the latest busybox, and the boot.img has been modified to allow adb remount.
This will wipe your entire device. You will lose all apps and data. I am in no way responsible for your device, as always flash at your own risk.
Instructions
Extract .zip file
In windows:
Double click flash-windows.bat
In linux:
cd into extracted directory
chmod +x flash-linux.sh
sudo ./flash-linux.sh
Downloads
K1_ICS_120607_Rooted.zip
b7762c0c83535eea9e542c6737bd1470
Mirror
K1_ICS_120607_Stock.zip
68499815e3937b96e31dc49c1dd099b6
Mirror
Enjoy!

khanning88 said:
Hi everyone,
As most of you know Lenovo released the official ICS build for the Ideapad K1 today. The new bootloader will not allow me to boot into recovery partition, so no custom recovery for now. Unfortunately the build released by Lenovo also lacked Google Apps. I have added in the latest Google Apps package including Face Unlock. I have posted two versions of the Rom both rooted and not rooted. The non rooted is 100% stock with Google Apps. The rooted has the latest Superuser.apk and su binary and the latest busybox, and the boot.img has been modified to allow adb remount.
This will wipe your entire device. You will lose all apps and data. I am in no way responsible for your device, as always flash at your own risk.
Instructions
Extract .zip file
In windows:
Double click flash-windows.bat
In linux:
cd into extracted directory
chmod +x flash-linux.sh
sudo ./flash-linux.sh
Downloads
K1_ICS_120607_Rooted.zip
b7762c0c83535eea9e542c6737bd1470
K1_ICS_120607_Stock.zip
68499815e3937b96e31dc49c1dd099b6
Enjoy!
Click to expand...
Click to collapse
awsome great job!!!!:good:

Awesome work!! CM9/10 in the near future after kernel source? I volunteer to test if you need testers.

i was about to install this an i realized i left my data cable at work. i guess i get to sleep tonight after all

I know this is probably a dumb question but do I need the apx drivers installed? I'm having problems getting them installed with the official lenovo package ones... Maybe someone could link me to a different place to find them...
(R)EVOLTE

thank you so much khanning88 for this and all your hard work! lenovo should hire you and make you their senior dev.. awesome job! thanks again! =)

Great job man. Just installed. Looks fantastic!
Sent from my K1 using Tapatalk 2

First of all, I would like to express my gratitude to khanning88 for getting things done at this high speed.
However,I have issues on the Play Store. As a number of apps including Google Maps and Chrome cannot be downloaded directly via Play Store, which it said "Your device isn't compatible with this edition". So I have to grab them unofficially. Can we pretend the device to be a Xoom for maximum app compatibility, just like what you did in the rooted HC rom? Or is there any other solution?
Thanks in advance.

I respect your work.great share!

Thanks man ... downloaded both versions. Will flash mine with rooted version and my friend's device using unrooted version.

Recovery?
Awesome work - flashed root version - worked flawlessly.
Now, how can we reinstall CWM recovery - it seems to have disappeared? Installing the special recovery apk and opening does not reboot into recovery. Does anyone know if flashing ICS removed the recovery partition?

camera not working plus some apps dont install.
Flashed rooted version which worked OK. Camera app starts but the screen is black. Camera worked OK on HC 3.2.1. Tablet feels less responsive also.
Lots of my standard apps don't install, play store says they are not compatible. These are apps not games. Like flipboard and my banking app.
At this point I think I'll go back to HC until these items are fixed. And I guess this won't happen until Lenovo release the source and khanning can fix up all the Lenovo mistakes.
Disappointed with what Lenovo produced, given the time they spent working on it. Its a 3 out of 10 from me.

zapher67 said:
Flashed rooted version which worked OK. Camera app starts but the screen is black. Camera worked OK on HC 3.2.1. Tablet feels less responsive also.
Lots of my standard apps don't install, play store says they are not compatible. These are apps not games. Like flipboard and my banking app.
At this point I think I'll go back to HC until these items are fixed. And I guess this won't happen until Lenovo release the source and khanning can fix up all the Lenovo mistakes.
Disappointed with what Lenovo produced, given the time they spent working on it. Its a 3 out of 10 from me.
Click to expand...
Click to collapse
Camera works fine for me both pics and vids. Tablet seems much more responsive to me. I agree Lenovo did a poor job. Khanning came in in two hours and tripled their output. I have been working on modifing the build prop to get more apps to work.

Excellent work khanning. As far as overclocking goes, would something like that have to wait until the source is released? Or could a custom kernel supporting this be released without it? Just curious, I like to make things go faster...
Only downside is this came out the day before my work week (Fri-Sun) really kicks in gear, maybe by the time I get around to tinkering with this more questions will be answered.
Either way, khanning you really should be on salary by Lenovo for all the business youre saving that company. Thank you again!

These are the build Prop setting I used to get better EA and gameloft compatibility. I am not an expert on build Props and take no responsibility for your actions. Back up your build before making changes. Gmaps and chrome still do not show up in the market with theses settings.
ro.product.manufacturer=samsung
ro.product.model=GT-P7500
ro.build.fingerprint=samsung/GT-P7500/GT-P7500:3.2/HTJ85B/XWKK4:user/release-keys
ro.product.board=GT-P7500
ro.product.brand=Samsung
ro.product.device=GT-P7500
ro.product.name=GT-P7500

Awesome rom. I have ICS on my phone, but this thing really flies and is SMOOOOOTH! Hopefully someone comes up with a working build.prop to show the missing market apps and I will be one happy camper.
Thanks again, Khanning!
---------- Post added at 04:00 PM ---------- Previous post was at 03:40 PM ----------
Also does anyone know why this rom has a Messaging app?

external sd
There are a priblem with the external sd, i cant see it' its only me?

Heres the build.prop settings for the xoom. Just tested and is showing more games/apps
ro.product.manufacturer=Motorola
ro.product.model=Xoom
ro.product.brand=verizon
ro.product.name=trygon
ro.product.device=stingray
ro.product.board=ventana
ro.build.description=trygon-user 3.1 HMJ37 124251 release-keys
ro.build.fingerprint=verizon/trygon/stingray:3.1/HMJ37/124251:user/release-keys
Sent from my Xoom using Tapatalk 2

gilberthcordova said:
There are a priblem with the external sd, i cant see it' its only me?
Click to expand...
Click to collapse
Are you rooted? If you are then you can use a root file explorer and go to mnt>sdcard2
---------- Post added at 05:25 PM ---------- Previous post was at 05:24 PM ----------
dodgepot said:
Heres the build.prop settings for the xoom. Just tested and is showing more games/apps
ro.product.manufacturer=Motorola
ro.product.model=Xoom
ro.product.brand=verizon
ro.product.name=trygon
ro.product.device=stingray
ro.product.board=ventana
ro.build.description=trygon-user 3.1 HMJ37 124251 release-keys
ro.build.fingerprint=verizon/trygon/stingray:3.1/HMJ37/124251:user/release-keys
Sent from my Xoom using Tapatalk 2
Click to expand...
Click to collapse
Can you confirm if it is showing Chrome and Google Maps?

me_is_rushin said:
Are you rooted? If you are then you can use a root file explorer and go to mnt>sdcard2
---------- Post added at 05:25 PM ---------- Previous post was at 05:24 PM ----------
Can you confirm if it is showing Chrome and Google Maps?
Click to expand...
Click to collapse
It still shows incompatible

Quad Kern Android 5.1 Autoradio - Erisin - Alternativer ROM

Hello,
The devices which have Android 5.1 are already on the market. I'm thinking of buying the following device:
- ES3060P Erisin with Android 5.1
- Quad-Core RK3188 1608MHz Cortex A9 CPU
- Touchscreen, 1024*600
My concern is that the update to alternative ROMs (like Malaysk) will be not possible due to the MCU FW. According to the specification of the device the MCU Version is "MTCD-LM-V1.21_1". Unfortunately I have not found this firmware here in the board or somewhere else in the internet. I have started a request to the manufacture – to receive the MCU firmware- , without response yet.
What do you think? And what is your preference and why?
a) Shall I buy an older device with Android 4.4.4 which known / available MCU FW.
b) Or shall I buy the new device, with the hope that the MCU FW "MTCD-LM-V1.21_1" will be supported in the future, so alternative ROMs can also be installed on this device.

It's still too early to know and precisely understand what MTCD stands for and what means in regard to current MTCB head units.
So future 5.1.1 ROMs compatibility between MTCB and MTCD is still unknown, but in any case there will be very likely modded 5.1.1 ROMs dedicated to these new MTCD HUs too.

@ themissionimpossible: Thank you. So I think to go the save way and to buy a android 4.4.4 unit with “classic” MCU for alternative ROMs.
BTW I got a response from Erisin seller:
"For your questions, we are sorry to tell you that, we have no idea about the MCU, because we are directly book the unit from the factory. But we are sure that, you can not install alternative images from XDA Developers."
The interesting thing is that the unit has a build in CAN-BUS-Decoder. In contrast, the units based on Andriod 4.4.4 have an externl CAN-BUS-Decoder.
"And about the Can bus Decorder, it is build-in this radio, so it is ready for you to use after installation."

Konst80 said:
@ themissionimpossible: Thank you. So I think to go the save way and to buy a android 4.4.4 unit with “classic” MCU for alternative ROMs.
BTW I got a response from Erisin seller:
"For your questions, we are sorry to tell you that, we have no idea about the MCU, because we are directly book the unit from the factory. But we are sure that, you can not install alternative images from XDA Developers."
The interesting thing is that the unit has a build in CAN-BUS-Decoder. In contrast, the units based on Andriod 4.4.4 have an externl CAN-BUS-Decoder.
"And about the Can bus Decorder, it is build-in this radio, so it is ready for you to use after installation."
Click to expand...
Click to collapse
Hi !
I want to buy this unit . Can help with some pictures from back to see how is this new model ?
How i's the botton like oem bmw or ... ?
From where he send to you europe or China ?
Thanks .

Marius B said:
Hi !
I want to buy this unit . Can help with some pictures from back to see how is this new model ?
How i's the botton like oem bmw or ... ?
From where he send to you europe or China ?
Thanks .
Click to expand...
Click to collapse
I have decided to buy the lollipop unit "Quad Kern Android 5.1 Autoradio DAB+ GPS Opel Vauxhall Astra Vectra Corsa 3060GE" on eBay. It was send from UK to Germany without trouble. The CAN BUS decoder is already build in and there is no additional adapter between the radio and Opel connector needed. So it was pretty easy to install it.
Regarding the lollipop 5.1.1 android, I don't know if there are advantages compared to android 4.4.4. The lollipop runs pretty stable till yet and it boots fast. I think it uses the same apps (Audio Player, Radio, GPS Navigation etc.) which are used for android 4.4.4. So in summary I like this radio. But I'm using it for just one week, so I hope my opinion will not change in the future.
Do you have specific question regarding the unit I bought?

Are you sure that it is real Android 5.1.1? In some of the Head Units i saw some modified GUI-Versions, which has only the look of Android 5. Does the settings say 5.1.1 too?

Konst80 said:
Do you have specific question regarding the unit I bought?
Click to expand...
Click to collapse
One question about SWC...
Do you have the "short click" and "long click" settings, same as you can see at min.4:11 of this JY 5.1 video: https://youtu.be/1hiDFFfdWVg ?
Thanks

Konst80 said:
I have decided to buy the lollipop unit "Quad Kern Android 5.1 Autoradio DAB+ GPS Opel Vauxhall Astra Vectra Corsa 3060GE" on eBay. It was send from UK to Germany without trouble. The CAN BUS decoder is already build in and there is no additional adapter between the radio and Opel connector needed. So it was pretty easy to install it.
Regarding the lollipop 5.1.1 android, I don't know if there are advantages compared to android 4.4.4. The lollipop runs pretty stable till yet and it boots fast. I think it uses the same apps (Audio Player, Radio, GPS Navigation etc.) which are used for android 4.4.4. So in summary I like this radio. But I'm using it for just one week, so I hope my opinion will not change in the future.
Do you have specific question regarding the unit I bought?
Click to expand...
Click to collapse
Please make a pictures from about to see if is 5.1. Thanks.
Send by phone

Marius B said:
Please make a pictures from about to see if is 5.1. Thanks.
Send by phone
Click to expand...
Click to collapse
I have make some picture showing the lollipop 5.1.1. I have currently no doubt, that it's not lollipop. Anyway if there are further possibility to check it truley lollipop so let me know.
Also the last two pictures are showing the look of notification bar and task switcher, which are typically for lollipop as far I know.

popeye70 said:
One question about SWC...
Do you have the "short click" and "long click" settings, same as you can see at min.4:11 of this JY 5.1 video: https://youtu.be/1hiDFFfdWVg ?
Thanks
Click to expand...
Click to collapse
It's curious, but the tool seems not to work correctly or I'm doing something wrong. I can't reconfigure the buttons yet. I think I have to contact the manufacturer... Anyway I have a attached the picture of the standard configuration. Unfortunately I can't answer your answer yet.

Konst80 said:
I have make some picture showing the lollipop 5.1.1. I have currently no doubt, that it's not lollipop. Anyway if there are further possibility to check it truley lollipop so let me know.
Also the last two pictures are showing the look of notification bar and task switcher, which are typically for lollipop as far I know.
Click to expand...
Click to collapse
take a look at your build prop that should tell us.
But I thought multiple people confirmed its a modified Kit Kat Rom

I order today this unit and tell me that is lollipop version.
Send by phone

Send by phone

transitoyspace said:
take a look at your build prop that should tell us.
But I thought multiple people confirmed its a modified Kit Kat Rom
Click to expand...
Click to collapse
Here is my build.prop, I have't found anything referencing android 4.x.x. What do you think transitoyspace?
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=LMY48Y
ro.build.display.id=rk3188-userdebug 5.1.1 LMY48Y eng.root.20160307.201022 test-keys
ro.build.version.incremental=eng.root.20160307.201022
ro.build.version.sdk=22
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=5.1.1
ro.build.version.security_patch=2015-12-01
ro.build.version.base_os=
ro.build.date=2016年 03月 07日 星期一 20:14:11 CST
ro.build.date.utc=1457352851
ro.build.type=userdebug
ro.build.user=root
ro.build.host=wuwq
ro.build.tags=test-keys
ro.build.flavor=rk3188-userdebug
ro.product.model=rk3188
ro.product.brand=rockchip
ro.product.name=rk3188
ro.product.device=rk3188
ro.product.board=rk30sdk
# 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=rockchip
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=rk3188
# ro.build.product is obsolete; use ro.product.device
ro.build.product=rk3188
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=rk3188-userdebug 08032016.10:34:33
ro.build.fingerprint=rockchip/rk3188/rk3188:5.1.1/LMY48Y/root03072012:userdebug/test-keys
ro.build.characteristics=tablet
# end build properties
#
# from device/rockchip/rk3188/system.prop
#
#
# system.prop
#
#rild.libpath=/system/lib/libreference-ril.so
#rild.libargs=-d /dev/ttyUSB2
# Default ecclist
ro.ril.ecclist=112,911
ro.opengles.version = 131072
wifi.interface=wlan0
rild.libpath=/system/lib/libril-rk29-dataonly.so
rild.libargs=-d /dev/ttyACM0
persist.tegra.nvmmlite = 1
ro.audio.monitorOrientation=true
#NFC
debug.nfc.fw_download=false
debug.nfc.se=false
#add Rockchip properties here
ro.rk.screenoff_time=2147483647
ro.rk.screenshot_enable=true
ro.rk.def_brightness=200
ro.rk.homepage_base=http://www.google.com/webhp?client={CID}&source=android-home
ro.rk.install_non_market_apps=false
sys.hwc.compose_policy=6
sys.wallpaper.rgb565=0
sf.power.control=2073600
sys.rkadb.root=0
ro.sf.fakerotation=false
ro.sf.hwrotation=0
ro.rk.MassStorage=false
ro.rk.systembar.voiceicon=false
ro.rk.systembar.tabletUI=false
ro.rk.LowBatteryBrightness=false
wifi.interface=wlan0
ro.tether.denied=false
sys.resolution.changed=false
ro.default.size=100
persist.sys.timezone=Asia/Shanghai
ro.product.usbfactory=rockchip_usb
wifi.supplicant_scan_interval=15
ro.factory.tool=0
ro.kernel.android.checkjni=0
#set default lcd density to Rockchip tablet
ro.sf.lcd_density=240
ro.adb.secure =0
sys.hwc.enable=1
persist.sys.root_access=0
persist.sys.boot.check=false
ro.product.manufacturer9=HengChangTong
ro.product.model9=H660000
ro.product.customer=HCT4
ro.product.hostname=Android
ro.product.instruction=PDF
ro.product.videogesture=false
ro.product.bluetoothname=CAR KIT
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.target.product=tablet
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=pixiedust.ogg
ro.carrier=unknown
ro.config.alarm_alert=Alarm_Classic.ogg
ro.rksdk.version=RK30_ANDROID5.1.1-SDK-v1.00.00
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=80m
dalvik.vm.heapsize=384m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=8m
camera2.portability.force_api=1
persist.sys.strictmode.visual=false
dalvik.vm.jniopts=warnonly
ro.rk.bt_enable=true
ro.factory.hasUMS=true
persist.sys.usb.config=mass_storage,adb
testing.mediascanner.skiplist=/mnt/internal_sd/Android/
ro.factory.hasGPS=false
ro.factory.storage_suppntfs=true
ro.factory.without_battery=false
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=5.0_r2
ro.sf.lcdc_composer=0
debug.hwui.render_dirty_regions=false
keyguard.no_require_sim=true
ro.com.android.dataroaming=true
ril.function.dataonly=1
ro.config.enable.remotecontrol=false
ro.product.version=1.0.0
ro.product.ota.host=www.rockchip.com:2300
persist.sys.dalvik.vm.lib.2=libart.so
dalvik.vm.isa.arm.features=default
dalvik.vm.lockprof.threshold=500
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

Konst80 said:
Here is my build.prop, I have't found anything referencing android 4.x.x. What do you think transitoyspace?
Click to expand...
Click to collapse
Hi ! Can make for me some pictures from settings can function and special function. Thanks.
Send by phone

If you go to the "Android version 5.1.1" and tap on it several times really quickly.. what happens?
https://www.youtube.com/watch?v=KLig30I19KI

Konst80 said:
Here is my build.prop, I have't found anything referencing android 4.x.x. What do you think transitoyspace?
Click to expand...
Click to collapse
ro.build.version.sdk=22
Usually when you change this it will cause a bootloop.
5.1=22
5.0=21
Kitkat watch=20
4.4=19
so yes this looks like its the real deal

to clear things up:
Joying tried the ROM 5.1 on the older units and we ended up with black screen.
The new head units you see with Android 5.1 have a modified motherboard and have a different ROM. so I am very sure that the Malaysk ROM would not work on them as is.
Joying is working to develop the ROM 5.1 for the old hardware now and it expected to be released in May.

doctorman said:
to clear things up:
Joying tried the ROM 5.1 on the older units and we ended up with black screen.
The new head units you see with Android 5.1 have a modified motherboard and have a different ROM. so I am very sure that the Malaysk ROM would not work on them as is.
Joying is working to develop the ROM 5.1 for the old hardware now and it expected to be released in May.
Click to expand...
Click to collapse
@Malaysk dont work now but in future maybe. From where do you know that don't work on this unit. I make some changes for old unit. I use oem rom with changes that I make.
Send by phone

Marius B said:
@Malaysk dont work now but in future maybe. From where do you know that don't work on this unit. I make some changes for old unit. I use oem rom with changes that I make.
Send by phone
Click to expand...
Click to collapse
considering the Original ROM does not work on the new units it is reasonable to assume that malaysk rom will not work till it is updated.