yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] fattire:
Lenovo a1 w/3.0 kernel?

Anyone seen this and know what's the deal?

Update: video uploaded 4 months ago... but looks like the build was just released or leaked or something. credit to krylon360 for bringing it to my attention.

The Lenovo A1 is omap3 I'm pretty sure. There is a version of cyanoboot in progress for this device as well, but this is supposedly a 3.x kernel running on omap3 with video.

More info for anyone who may care--

This is an omap3622 w/a 3MP camera, 512 ram, 16GB internal emmc + sd slot. It's got a different touchscreen (a "morgan multi-touch device") and different display panel from Chimei Innolux Display Corporation (model AT070TNA2). If anyone cares.
[Nook Color Android Development] Jasper_Ward:
Oh please be possible for this to be ported to our glorious Nooks... lack of netflix is the only thing holding me back from taking the plung
[Nook Color Android Development] worldindo1:
Edited my old reply. Tested and found out that I sadly have cyttsp. Possibly you and mik_os can work on a mod for the old screens? Just a hope lol.
[Nook Color Android Development] Dj-Gutz:
Is there anything that can be done without the sources? probably not , right?

Hopefully they'll release them before LG OB

The Dev port is not as advanced as you would imagine

On a different note , GSL I9003 has joined CM team officially ( under teamhacksung )

If I'm not mistaken this will be the first omap3 with official cm9 support

We've already determined in the past that it's not possible since it's hardware related
[Nook Color Android Development] krylon360:
Here is mine:

<6>cyttsp_init:I2C Touchscreen Driver (Built Apr 26 2012 @ 23:07:46)

<4>cyttsp:Reseting TMA340

<4>cyttsp:Start Probe 1.2

<6>android_work: did not send uevent (0 0 (null))

<7>hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0000

<4>

<4>cyttsp::found BL, Overriding maxx & maxy

<6>cyttsp_initialize:cyttsp-i2c: Register input device

<6>input: cyttsp-i2c as /devices/platform/i2c_omap.2/i2c-2/2-0022/input/input2

<6>android_work: sent uevent USB_STATE=CONNECTED

<6>cyttsp_initialize:Setting up interrupt 259

<6>cyttsp_initialize:cyttsp_initialize: Create sysfs_group successfully!

<4>cyttsp:Start Probe PASS

<4>max8903_charger_enable: dtct_status 0x04

<6>ft5x06_init() - FT I2C Touchscreen Driver (Built Apr 27 2012 @ 00:22:05)

<3>can't get ft5x06 xreset GPIO

<6>cyttsp_power_on:BL101: f=00 s=11 err=D0 bl=010B bld=010B R=16

<6>cyttsp_power_on:BL102: tver=1100 a_id=AA1D aver=0006

<6>cyttsp_power_on:BL103: c_id=C0C1C2

<6>kxtf9 1-000f: WHO_AM_I = 0x01

<6>input: kxtf9_accel as /devices/virtual/input/input3

<6>using rtc device, twl_rtc, for alarms

<6>twl_rtc twl_rtc: rtc core: registered twl_rtc as rtc0

<6>i2c /dev entries driver

<6>Linux video capture interface: v2.00

<6>omap-previewer omap-previewer: omap-previewer: Registered preview wrapper

<6>omap3isp omap3isp: Revision 15.0 found

<6>omap-iommu omap-iommu.0: isp: version 1.1

<7>Saving csi2 context

<7>Restoring csi2 context

<7>Saving csi2 context

<6>usbcore: registered new interface driver uvcvideo

<6>USB Video Class driver (v0.1.0)

<4>max17042: max17042_init ...

<4>max17042: max17042_probe ...

<4>max17042: next history save at 4294845647

<4>max17042: max17042_probe > IRQ is 260

<4>max17042 GPIO pin read 1

<4>max17042: max17042_device_power_on ...

<4>max17042: max17042_hw_init ...

<4>max17042: BATTERY Detected!

<4>config = 0x2214

<4>Valert = 0xff9b

<4>Salert = 0xff05

<4>config = 0x2214

<4>config = 0x2214

<4>shdntimer = 0x0002

<4>max17042: max17042_verify ...

<6>max17042 1-0036: Version = 0x0092

<6>max17042 1-0036: support ver. 1.0.0 enabled

<4>MAXIM 8903 Charger registering!

<4>MAXIM 8903 Charger Initializing...

<4>MAXIM8903: Request CHARGER FLT IRQ successfully!

<4>max8903_charger_enable: USB CHARGER(500mA) Detected!

<4>MAX8903: Charging is now enabled!

<6>OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec

<6>android_work: sent uevent USB_STATE=DISCONNECTED

<6>device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-devel@redhat.

com

<6>Bluetooth: Bluetooth Driver for TI WiLink - Version 1.0

<6>android_work: sent uevent USB_STATE=CONNECTED

<6>[imoseyon] interactive enter

<6>cpuidle: using governor ladder

<6>cpuidle: using governor menu

<6>MMC LOG:mmc_log_init() - MMC Logging ENABLED.

<6>android_work: sent uevent USB_STATE=DISCONNECTED

<6>android_work: sent uevent USB_STATE=CONNECTED

<6>android_work: sent uevent USB_STATE=DISCONNECTED

<6>omap_pwm_led omap_pwm_led: OMAP PWM LED (lcd-backlight) at GP timer 8/0

<6>Registered led device: lcd-backlight

<6>cyttsp_power_on:SI102: tver=1100 a_id=AA1D aver=0006

<6>cyttsp_power_on:SI103: c_id=C0C1C2
[Nook Color Android Development] afzalarsalan:
Looks like you got yourself a cyttsp touchscreen. Too bad,no more than two fingers for you. :D
[Nook Color Android Development] Henk Poley:
Appears to use a build for Zoom2. Which was used for Nook Color homebrew development too early on. This basically means TI has Linux-3.0 drivers for the PowerVR SGX530 stashed away somewhere internally ?

Edit, the build is from april 17th this year. So should be more up to date than previous video.

Edit2, it appears to use debug builds of the GL libraries. Couldn't really eke out a timestamp. Only looked for ASCII (`strings`) though.

Edit3, libIMegl is at "1.4 build 1.8@550175" instead of "1.4 build 1.6.16.4061" in our nook color builds.

Edit4, files libGLESv1_CM_POWERVR_SGX530_125.so, libGLESv2_POWERVR_SGX530_125.so, libglslcompiler.so, libIMGegl.so also use this 550175 build number.

Edit5, the same build appears to be included for Linaro 12.04 for "panda". But there it's for SGX 540. With some luck the kernel driver is available for "panda" and can be adapted to interface the SGX 530 driver.

Edit6, I'm not sure, but these appear to contain "DDK 1.8" drivers related to graphics on "panda": http://android.git.linaro.org/gitwe...u;hb=e3dd212d367f2e3f42fbf00d7da95d7f94f6cc76.

Edit7, no clue if this is for Linux 3.x though.

Edit8, the README at the top of the tree says "Linux kernel release 3.x" :)

Edit9, the kernel driver version matching these binary blob driver libraries: http://android.git.linaro.org/gitwe...it;h=eb6137bf12f9c5231f23aa976fef0640fe6c9f17
[Nook Color Android Development] Dj-Gutz:
Did I just stumbled a gold mine?

I was just riffing through TI's git checking Henk Poley's zoom2 lead , which got me to nothing special and then I went through the whole list of projects

Check THIS out

The cool part is - I can't find anything comparable on rowboat,defy or whatever sources I looked

Is it possible that it was overlooked for 6 weeks? Or am I missing something and we already knew about this git?

It seems to cover OMX , HWComposer and whole lot of goodies

Are those libs cross-kernel , or would they have to be back-ported?

Can someone confirm?
[Nook Color Android Development] Henk Poley:
Also see my Edit5 and 6 for what appears to be the kernel 3.0 side part of the driver. Maybe any Linaro build for panda contains even more up to date proprietary device driver blobs. The kernel driver references "DDK 1.8@900138" while the above is 1.8@550175, could be different tracking numbers though.

Edit: Errr. those would be for SGX 540 though
[Nook Color Android Development] Dj-Gutz:
Yeah , was about to comment on the SGX540 thing but I see you figured it out :)

I think our SGX drivers are good for now , results on benchmarks prove that ( also referring to the benchmarks TI posted on their release which we got the drivers from )

What we're missing is the new hwcomposer which was introduced in ics ( basically run with gralloc to enable the hw acceleration part for android userspace as far as I know )

and some other features like OMX ( mainly video decoding for us nook users )

EDIT :

The more and more I review what I found in the last post , I think it's what we've been looking for

I've paid attention mainly to the kernel dev but I've always looked on other gits that got property libs and other stuff related to us - And I haven't noticed this one

Any chance that this project was "hidden" up until recently? It's freaking wierd
[Nook Color Android Development] HacDan:
It was noticed a ~month ago or so. Sadly the sources are incomplete to say the least. Not everything is implemented. Keyodi and I believe Fattire have started hacking away at the source, but initial impression is that it is incomplete. And doesn't seem to be on a regular update schedule.
[Nook Color Android Development] Henk Poley:
The A107 update also contains libOMX's:

lib/libOMX.TI.720P.Decoder.so	lib/libOMX.TI.G711.decode.so	lib/libOMX.TI.G726.encode.so	lib/libOMX.TI.JPEG.encoder.so	lib/libOMX.TI.WMA.decode.so
lib/libOMX.TI.AAC.decode.so	lib/libOMX.TI.G711.encode.so	lib/libOMX.TI.G729.decode.so	lib/libOMX.TI.MP3.decode.so	lib/libOMX_Core.so
lib/libOMX.TI.AAC.encode.so	lib/libOMX.TI.G722.decode.so	lib/libOMX.TI.G729.encode.so	lib/libOMX.TI.Video.Decoder.so
lib/libOMX.TI.AMR.decode.so	lib/libOMX.TI.G722.encode.so	lib/libOMX.TI.ILBC.decode.so	lib/libOMX.TI.WBAMR.decode.so
lib/libOMX.TI.AMR.encode.so	lib/libOMX.TI.G726.decode.so	lib/libOMX.TI.ILBC.encode.so	lib/libOMX.TI.WBAMR.encode.so

I guess that also needs a kernelspace counterpart.

And 2 copies of hwcomposer.omap3.so (same md5 sum though)
[Nook Color Android Development] fattire:
Yeah keyodi and I have been working a little with that omap3 3.x source just to play around and get started for when the actual good stuff shows up. It boots up and keyodi has a log, but nothing on screen yet or anything. Very early days.
[Nook Color Android Development] Dj-Gutz:
Fattire , what are your thoughts on fund raising?

I know

you

don't want money contributions ( no idea keyodi's position )

I thought about making a donation fund to attract other developers ( kernel devs mostly ) , by donating them a device or whatever they wish

I'll gladly donate 10 bucks to support this and since NC is at the 100$ mark now , I believe it's possible to raise enough money

Do we actually need other devs? I hate thinking most of the work is on you and keyodi

It actually worked on many other devices ( even NT ) , and if a dev wants to join the party and doesn't have a nook - why not support him?

So my question is since you and keyodi are basically running the show for now , do you support this action?

Much respect to both of you ( and all the other devs out there :) )

EDIT :

Take a look @ platform/hardware/ti/omap3

Seems like a lot of code is being reviewed on the same git I posted earlier

Fattire , can you try to use those commits to see if it gets us any closer?

EDIT 2 :

Seeing this video of the i9003 got me a little bit jealous about how smooth it is :D

[YOUTUBE]7EQIncio0oU[/YOUTUBE]

What's our .35 kernel status? Are you planning to work on it for now till 3.x kernel is completed?
[Nook Color Android Development] HacDan:
Money isn't going to bring people for long term to a project, sadly. Maybe a device, but def. not just the enticement of money.

Sleep is wonky in .35 along with wifi and probably many other bugs.

Also, keep in mind that the i9003 will be smoother because of the simple fact that it is rendering far fewer pixels.
[Nook Color Android Development] Dj-Gutz:
Obviously I didn't mean throwing money on devs... Devices mainly , But if it goes well and enough money is raised I don't see why not also use it to make bounties if specific bugs exist ( we can make a poll to decide how to split the money )

Anybody thinking of .37 since TI is using it for now?

I'm pretty sure it can do wonders , I've used many phones ( no other tablets) before and after h/w acceleration on ics and it does wonders - even on slower gpus

I'm sure it will be harder for the GPU but , the SGX530 is a great GPU and I wouldn't dismiss it
[Nook Color Android Development] Dj-Gutz:
Maybe TI is merging their drivers?

http://review.omapzoom.org/#/c/21348/1/drivers/gpu/pvr/pvrversion.h

Seems like A1 leak is coming along , sound and wifi is working now

Let's hope for some sources soon
[Nook Color Android Development] TDO:
Do you have a link for the A1 ICS leak with working WIFI drivers?
[Nook Color Android Development] Henk Poley:
Lenovo A1 ICS with working WiFi: http://xdaforums.com/showthread.php?p=25800658

And here (German & English) :: http://www.android-hilfe.de/lenovo-ideapad-a1-forum/239646-a1-isc-preview-v1-1-wifi-works.html
[Nook Color Android Development] leapinlar:
Good news fellow phone gui users. CM has added the ability to customize the navigation bar in phone gui mode. Go to settings, system, navigation bar and it will tell you how to do it. You can move the buttons around, add buttons, change how they perform, etc. Just download my latest patch (5/18) to get into phone gui mode and use it on today's (5/18) CM9 ROM. I don't see these options in the tablet gui, but I may be just missing it. Go to my tips thread in my signature if you want to find out more.
[Nook Color Android Development] sednafx:
I wonder what I did wrong. I know I am typing the key in correctly.

Update: Tried toggling wifi on and off, same goes for airplane mode. No go. I have a D-Link DIR-655. My wifi works fine in CM7.
[Nook Color Android Development] michaeljr10wv:
OK, installed to a SD to test. I can't seem to get gapps flashed. I have CM7 installed internally.

Any ideas?

Mike
[Nook Color Android Development] BaileyJ205:
Thanks Rick
[Nook Color Android Development] gambit07:
Nope, I actually had problems with cm7 recognizing my connection with wpa but everything has been good so far on ics
[Nook Color Android Development] JustisLewis:
My reaction: http://www.youtube.com/watch?v=VLnWf1sQkjY

But how could you do this to me during finals week :p
[Nook Color Android Development] dreamhunterr:
fattire,

I was wondering if there was any interest in starting to report bugs, even if minor ones.

I think it'd be nice to document even minor bugs so eventually someone can fix them.

I don't exactly where to report them. if on the issue tracker of your github or in the CyanogenMOD bugtracker because some might not be device specific.
[Nook Color Android Development] Homer_S_xda:
I had the same issue. If you are using Verygreen's 1.3, it is expecting gapps to be have "gb" in the zip file name. Fake it out by changing "ics" to "gb" in the file name. Then boot to SDcard recovery using the boot menu.

Seems to have worked for me...

Update... spoke too soon, "Nfc Service has stopped" loop. Have to look up the fix for that one.

Homer
[Nook Color Android Development] danvee:
If it's anything like some of the other releases, the "emmc" means for internal memory and not for SD card install.

I may be wrong though.....
[Nook Color Android Development] fattire:
Here's how to report a bug at this point:

"Hey everyone. I just wanted to report that I fixed a bug. [DESCRIPTION OF FIXED BUG GOES HERE] You're welcome!"
[Nook Color Android Development] afzalarsalan:
What should I wipe with this rom?
[Nook Color Android Development] JustisLewis:
/Data, /System
[Nook Color Android Development] Sjflowerhorn:
Baaaaaaaaahhhhh CTFU, I almost just fell out of my seat.
[Nook Color Android Development] Midnitte:
Sounds like he got it flashed ok though, perhaps it doesnt matter?
[Nook Color Android Development] joenathane:
ICS feels like a different OS, almost like moving from Windows to a Macintosh, it'll take a bit to get used to. Also I'm finding the menu button being on the upper right of apps weird, the UI feels a bit split. Overall I'm glad this is turning into more of a proper tablet, especially multi-pane apps.

I was having issues getting gapps to work correctly, I wiped data and cache several times and tried both the 20111124 and 20111125 gapps for ICS and the wizard would keep crashing after connecting to wifi. I finally wiped everything, system, boot, data, cache, reflashed and that finally did the trick. Just thought I share in case anyone else experiences something similar.
[Nook Color Android Development] Dj-Gutz:
Finally got around to flash it :) Amazing work so far! and now endless fun :D

here is the gapps I used ( credits : defy ics thread ) , flashed immediately after flashing the rom

http://download.clockworkmod.com/test/gapps-20111128.zip

Market , Calendar Sync ( with Hebrew & RTL support :) ) , Gmail - All good

Youtube - Non-HQ Works ( not smooth ) , HQ causes FC - Is there a way to configure it to non-hd on start?

Browser bookmark sync doesn't work

Usb host - WORKS! ( but still a little goofy with external power , I think we need to automate the external vbus option )

Audio doesn't work , not news there , But I thought I could get around that with a USB DAC - Couldn't :\

That's It for now I think :)

Man , I LOVE ICS!

---------- Post added at 07:21 AM ---------- Previous post was at 07:15 AM ----------

Using DIR-615 ( with DD-WRT ) & WPA2 - working right out of the box

have you checked your mac filtering maybe? I'm not using it..
[Nook Color Android Development] gotrubberducky:
Thats teh gapps i used too, worked without issues so far.
[Nook Color Android Development] alton987:
I have a DIR655 and I can not connect also
[Nook Color Android Development] marlonbr:
HOLY ****!

You guys can't imagine how you made me happy with this build! My Nook was never this good before!

THANK YOOOOOOOOOOOUUUUUUUUUUUUUUUUUU!
[Nook Color Android Development] Dj-Gutz:
Is anyone else have issues with charging?

Using OEM Charger & OEM Cable - Doesn't recognize charge ( green led ) unless it's plugged before system loading ( but then it's stuck on "Charging" )

Using OEM Charger & Regular Cable - Works fine ( and also that's the only way to free it from the "charging" status after booting with the oem cable )
[Nook Color Android Development] zorvalth:
I just wanted to share that i installed the new ADW Launcher EX which is on sale right now for 10 cents and it perform incredibly smooth. There is a nice dock and there is all ics features like drag and drop folders.
[Nook Color Android Development] Dj-Gutz:
@kernel devs ,

Is the HWUI acceleration defy got now is portable to our .32 kernel?

Source
[Nook Color Android Development] fattire:
Which repo/branch?
[Nook Color Android Development] Dj-Gutz:
tpruvot / android_device_motorola_jordan
[Nook Color Android Development] afzalarsalan:
I think this would be the commit in question. If I am correct, we already have implemented this in our open-gl builds.

---------- Post added at 05:05 PM ---------- Previous post was at 05:01 PM ----------

What I found interesting is how he has certain things blacklisted such as trenchbucket and the wallpapers from using open-gl acceleration. Maybe this is the solution to the freezes we are having with the open-gl builds
[Nook Color Android Development] Dj-Gutz:
Not exactly , they also blacklisted a couple of other stuff which doesn't exist on our sources ( I'm not sure the changes that goes into the openl-gl builds do more than USE_OPENGL_RENDERER := true )

I'm trying to locate the kernel source itself to see if anything was changed there recently

Edit :

Looks like you beat me to the punch :)

Also look at this those changes are embedded on different parts of the system , that's why I gave his front page link instead of a specific repo

Edit 2 :

Another interesting commit , and basically a whole lot of egl/omx/gralloc/graphics related on that branch

as I stated a while ago they seem to have some level of OMX enabled
[Nook Color Android Development] chadamir:
The galaxy s which is a 3630 also has hw accel http://xdaforums.com/showthread.php?t=1338636
[Nook Color Android Development] Dj-Gutz:
Galaxy S I9000 is not Omap3630

You meant the Galaxy SL I9003 , and they got some level of H/W acceleration too , but they use 2.6.35 kernel which isn't matured on the nook - instead the devs are focusing on 3.x kernel which is great , but will take a while longer

The defy is running 2.6.32.9 , very similar to ours ( keyodi "upgraded" to 2.6.32.59 which is newer a couple of weeks ago )

If we can use the defy sources for now till 3.x is at least bootable , This will be a big step forward to daily-driver
[Nook Color Android Development] afzalarsalan:
I would think that the flag he has put in basically tells the system not to use EGL acceleration because it is flagged as "missing" from the board. I don't know much about programming so I could be completely wrong.
[Nook Color Android Development] frankusb:
Well since you got me browsing....

Is this why overclocking to 1.3GHz is not advised?

And this is the corresponding framework change I think to utilize the white/black lists.

It seems this is a very good find that should provide a way to avoid apps that cause problems.

Frank
[Nook Color Android Development] Dj-Gutz:
So , Tanguy Pruvot ( epsylon - defy ) comitted THIS , is it supposed to make any difference to us?

Also , new work began on 3.x kernel @ I9003

hillbeast should recieve a device soon , he started his git for 3.4 kernel

They got at least 2 more skilled developers ( dhiru , codeworxx ) that are working on it

keyodi/fattire , I hope you're in contact with them - Let's hope for some good news asap :)
[Nook Color Android Development] KnowledgeBroker:
Hey, I've always loved you guys, so many of you have made such great contributions I wouldn't even know where to start asking.. but since you guys are good without source and made so much happen..

My amaze 4g has had little development, mainly because we didn't have s-off or ICS - and now that we have both, we don't have a kernel dev.. the source for our phone hasn't been posted yet(the OFFICIAL ICS only came out a few days ago), but in the past we have dealt with not having wifi source.

I guess my question is, is anyone here willing to help us get things going? We have a bounty thread - or I should say we have been discussing it - I think for the right kernel dev we would buy multiple phones for! Or perhaps you can point me toward someone you think is up to the challenge and actually has the time?

Technically we need a GOOD dev in general, we are having issues gettings radio and a few other things working on our CM9 build, even with the leaked ICS kernel.. so yea, if anyone is interested maybe you can come say hi in the thread above? But what we DEFINITELY lack is a kernel dev, we can probably get other things going if we can get a really great kernel going on..

Thanks in advance, so much of how you guys have done things restore hope in how people can interact with each other.. awesome people.

SBD
[Nook Color Android Development] byproxy:
what's the latest kernel for this and where does one find it? thanks!
[Nook Color Android Development] HacDan:
Please keep it on topic. This has nothing to do with ICS development for the Nook Color.
[Nook Color Android Development] KnowledgeBroker:
No, but it is the same general principal as the guy you responded to in this post a few pages back(I have been following development here for a long time, my nook color is very happy) there is now and then a desire for other developers working on the nook color.. we are in the same position except without having a fattire or any of the other capable people here(and our problem is simpler).

Trust me, there is no attempt to hijack this thread(I doubt it is even possible), but if a contributor saw my post and decided to help us with OUR device(to get cm9) like so many have the nook color - this seemed much more pleasant than just assailing people via PM.
[Nook Color Android Development] fattire:
There is no surer way to kill any chance of collaboration. Bounties usually do the opposite of what was desired. See HP Touchpad or Nook Tablet for just two examples. You're asking for trouble.

A 3.0 build is currently running on NC, but it's got some serious problems, including no wifi, sluggish touchscreen, no sound, and of course nothing fancy like hw-accelerated video. As far as I know, there isn't even source for the omx stuff, no full working source for omap3 or anything...

For details you might wanna hop on irc, channel #nookcolor.
[Nook Color Android Development] jwzg:
TBH, the fact there has been no bounty started yet is a testament to the maturity of Fattire and the entire crew here. Welcome to the old XDA, newbs.