yashsingh1/xdaforums huggingface dataset:
[HTC Aria Android Development] munjeni:
Ok, here is mine modified cyanogenmod gingerbread kernel with all latest stable changes -> https://gitorious.org/cyanogenmod-2...46b2287c/diffs?diffmode=sidebyside&fragment=1

ics kernel will push to git latter!
[HTC Aria Android Development] Darius_bd:
Another one here ^^^^
[HTC Aria Android Development] sweetnsour:
Hey guys, I'm from the LG Optimus One forum. I've noticed that the HTC Aria also uses ARMv6 and has an Adreno 200 gpu. I've been trying to ask users to "petition" Qualcomm to see if they can release drivers (for hardware acceleration) compiled for ARMv6. As you may or may not know, Qualcomm recently released drivers but they were only for ARMv7. If you guys can set aside some time to do so, that would be great:

http://xdaforums.com/showthread.php?t=1551784
[HTC Aria Android Development] rkrishnan2012:
Im pretty sure there are a bunch of petitions already, and I think qualcomm has moved out of the armv6 phase. Sorry, but I think we are out of luck along that route.
[HTC Aria Android Development] sweetnsour:
You never know unless you try :)

Not to mention that Qualcomm released the drivers due to people petitioning its forums (if I have read those forums correctly)
[HTC Aria Android Development] munjeni:
Hey, this device -> http://xdaforums.com/showthread.php?t=1448697 have cm9 rom with hw aceleration :eek:, not have time now to research how hi fixed it, but if someone have more time please post here link for possible fix, I will try to fix!
[HTC Aria Android Development] tad1993:
I am getting really anxious to see ICS on our beloved Aria. It's going to be an awesome ROM!
[HTC Aria Android Development] munjeni:
Hey, got hw aceleration partialy working and camera also :) http://paste.ubuntu.com/895380/ problem is SIGSEGV with libgsl.so... anyone know whats use of the libgsl.so ?

EDIT:

fixed SIGSEGV :)... was problem with refresh rate code that I created... guys, I must to say its faster than software emulated:D

Need to port netlink qtaguid from kernel 3 (have some problems now) and than I will create new thread with mine cm9 build
[HTC Aria Android Development] dustinhayes93:
Can't wait man =D
[HTC Aria Android Development] Cryptecks:
This is excellent news! Please let us know as soon as it's good to start testing.
[HTC Aria Android Development] rkrishnan2012:
by "port" do you mean re-write the code or do you mean tweak it to work with our aria?

Regardless, this is great news. Thank You!
[HTC Aria Android Development] rooterdam:
Ugh..!

That´s been so sought after it´s unbelievable!

Awesome!
[HTC Aria Android Development] WinSuk:
Nice work! :)

I think another thread would just clutter it up more though...
[HTC Aria Android Development] bigfoot7375:
I think he earned the privilege to start a new thread... :D
[HTC Aria Android Development] tebuddy:
Competition is good. Besides, some users, like myself flash a rom and switch back and forth as each new update comes out. I think I have active nandroids of MIUI, This ICS, and Sense all keeping me occupied.

Ty to the devs, post more so I can thank every single one of your posts!
[HTC Aria Android Development] munjeni:
I agre but... I don't want to create confusion with changes that I made to android source and kernel source (I don't know if it is compatible with rom in this thread), so I'll make a new post with the cm9 that is compatible with kernel that I use

I am not here to compete, I'm here to learn something!
[HTC Aria Android Development] tebuddy:
Of course I did not mean to suggest that we should manipulate people into continuous updates. Just that naturally, different devs work in different ways depending on their experience and skill level. As we have all seen, we have numerous skilled developers here all striving to perfect their builds and contribute to each others.

Its entirely healthy and in good spirit is what I should have said :).
[HTC Aria Android Development] dustinhayes93:
Can't wait for you to release this ^_^
[HTC Aria Android Development] crxlvr:
i think working as a team you guys will get a decently running version of ics out faster than trying different things individually. The progress seems so close to breaking the barriers, keep plugging away guys. I cant wait for ics to run nicely on my little aria.
[HTC Aria Android Development] KillerBeaver:
Great work everyone! I'm superexcited to be able to use ice cream sandwich on my little aria. I never would have expected to have such great development and developers, for such a long time, on a phone that didn't generate much buzz. Thanks again and again.
[HTC Aria Android Development] munjeni:
As I promised here is cm9 http://www.2shared.com/file/D8FVPgcQ/cm_liberty-ota-engroot.html, have some partialy-initial changes to adreno things but stil it not working :mad: but I enabled debug for hw so you will be abble to see whats happen and maybe fix it! Other than I fixed (partialy) camera hal and have some minor fixes like imported netfilter from other kernels (qtaguid and quota2... etc) so please try and let me know if it is better than before, and if you have idea for possible fix please post it here
[HTC Aria Android Development] dustinhayes93:
I tried it and it does seem a bit more faster but not allot... I was expecting to see a big improvement after you saying you had HWA working correctly... Maybe its just me though. Im not complaining cause this is a step forward though! :D

Good job and thanks for your hard work :)

EDIT: I do notice the settings menu to be ALLOT faster. Scrolling works perfectly... No lag at all unlike before... Also youtube videos play with sound, but its laggy. Idk if this was the same before but i think last time i tried youtube on ics it froze?
[HTC Aria Android Development] rkrishnan2012:
I can confirm that youtube did not work for me before... :)
[HTC Aria Android Development] WinSuk:
This could be the problem.. http://xdaforums.com/showpost.php?p=21783787&postcount=42

I looked and it doesn't exist..
[HTC Aria Android Development] dustinhayes93:
So it's looking for that folder? Or files in the missing folder?
[HTC Aria Android Development] s0be:
There's more necessary, if you build the kernel from here:

http://git.cryptomilk.org/projects/marvel/kernel_htc_msm7227.git/log/?h=ics

It'll create that /dev/kgsl-3d0 file, but there' still problems. Permissions perhaps? We may need changes to init to fix it too.
[HTC Aria Android Development] s0be:
indeed, using that kernel and chmod 0777 /dev/kgsl*:

D/libEGL ( 1420): loaded /system/lib/egl/libGLES_android.so

D/libEGL ( 1420): loaded /system/lib/egl/libEGL_adreno200.so

D/libEGL ( 1420): loaded /system/lib/egl/libGLESv1_CM_adreno200.so

D/libEGL ( 1420): loaded /system/lib/egl/libGLESv2_adreno200.so

V/AmazonAppstore.SoftwareEvaluator( 1420): OpenGL ES Version String: 0x00010000
[HTC Aria Android Development] WinSuk:
Awesome! :)

Just have to change /dev/kgsl to /dev/kgsl* in the ueventd file (pretty sure)

I tried building and using that kernel before, but it wouldn't accept it.. has it changed since then and works?
[HTC Aria Android Development] munjeni:
Hi thanks, I not understand now. What kernel you using for now?

same here... you using marvel kernel and new kgsl driver? Smoother with gingerbread or smoother with ics?
[HTC Aria Android Development] s0be:
this is me using a self compiled liberty kernel from the Marvell tree. I have not tried it with GB/Froyo/Etc so I can't speak for anything other than ICS. I have been really busy this week so not a lot of documenting. Can't remember which kgsl /sys/lib/egl stuff I used so here's my md5sums:

adb shell md5sum /system/lib/egl/*
e3bb52e4efd7703afe626c6d5e6ead23 /system/lib/egl/egl.cfg
2a3894a7fe9a8e0f611010b57cfe06c1 /system/lib/egl/libEGL_adreno200.so
813af42106863115027dda532cd757bc /system/lib/egl/libGLES_android.so
7b8fb48299fd92d82ecc3aba4336b4f8 /system/lib/egl/libGLESv1_CM_adreno200.so
6941dcb2d8118e711be98571042e2e45 /system/lib/egl/libGLESv2_adreno200.so

I might finally have time tonight to attack this some more, but I'm not sure... IRL stuff is killin me here smalls.
[HTC Aria Android Development] munjeni:
Ok dude, thanks! So we are using ~same andreno libs. In my cm9 build:

e3bb52e4efd7703afe626c6d5e6ead23 /system/lib/egl/egl.cfg
2a3894a7fe9a8e0f611010b57cfe06c1 /system/lib/egl/libEGL_adreno200.so
b8a2e98a6203a22062a20f2783178e87 /system/lib/egl/libGLES_android.so
7b8fb48299fd92d82ecc3aba4336b4f8 /system/lib/egl/libGLESv1_CM_adreno200.so
6941dcb2d8118e711be98571042e2e45 /system/lib/egl/libGLESv2_adreno200.so
71bc1ff3de014d057185ef39304aecc0 /system/lib/egl/libq3dtools_adreno200.so

I working now with ics kernel... will push all changes to git that I aplied from my gingerbread kernel in preparation for ics. When I finish I will give you link! Also will try kgsl driver from marvel git in next few days... will try to fix gps...

EDIT:

here is my kernel repo that I used for our cm9 build

Latest 2 commits is fix for:

so usage meter working!
[HTC Aria Android Development] crxlvr:
so in lamens terms, what is the status of this ics, and is their a new version that we should be trying?
[HTC Aria Android Development] WinSuk:
Not sure if it effects us, but some changes were made to hardware_qcom_display..

http://review.cyanogenmod.com/#q,status:merged+project:CyanogenMod/android_hardware_qcom_display,n,z

https://github.com/CyanogenMod/android_hardware_qcom_display/commits/

Just thought I would give a heads-up :p
[HTC Aria Android Development] s0be:
Yeah, been following that. Compiling a kang right now with my kernel integrated, as well as these changes. It might fix the issue in that it fixes a fd issue in the exact area we're having issues.
[HTC Aria Android Development] s0be:
Here's my view on the status: Stable pre-alpha. It's not feature complete, but I've been using it for a daily driver for a while. GPS,camera, and Adreno200 aren't really working right now. I need to get HWA working by friday so my GF can play plants vs zombies, or I may die. Once HWA is working, there's still a bit of cleanup needed in that area to get HWA FAST and working fully. After which point, GPS will probably be the next thing integrated(I know that someone posted fixes for this, but it's always best to work on 1 thing at a time, so you have less things causing regressions), and finally the ever painful camera repair.
[HTC Aria Android Development] s0be:
Build failed in libQcom_ui. Gotta afk for about 5 hours, will look into upon return. If you get anywhere, post/push to github please.
[HTC Aria Android Development] munjeni:
I got compiled :) using all commits from 23.Mar. to 25.Mar. from here -> https://github.com/CyanogenMod/android_hardware_qcom_display/commits/

+

liberty/BoardConfig.mk:

#COMMON_GLOBAL_CFLAGS += -DREFRESH_RATE=60 -DMISSING_EGL_EXTERNAL_IMAGE -DMISSING_EGL_PIXEL_FORMAT_YV12 -DMISSING_GRALLOC_BUFFERS -DUNABLE_TO_DEQUEUE
#BOARD_USE_QCOM_PMEM := true
TARGET_GRALLOC_USES_ASHMEM := true
COMMON_GLOBAL_CFLAGS += -DQCOM_HARDWARE
COMMON_GLOBAL_CFLAGS += -DREFRESH_RATE=60 -DMISSING_GRALOC_BUFFERS -DMISSING_EGL_PIXEL_FORMAT_YV12 -DMISSING_EGL_EXTERNAL_IMAGE

+

liberty/include/linux/msm_mdp.h -> http://paste.ubuntu.com/899384/

+

comented line in hwcomposer.cpp:

//dev->device.enableHDMIOutput = hwc_enableHDMIOutput;

Going to try new build :D
[HTC Aria Android Development] FlyinHi:
Sorry, not a dev, but the lack of hardware acceleration is what's causing this rom to run so slowly?
[HTC Aria Android Development] munjeni:
yes, just that!

EDIT:

tried new build and it have black screen :mad: -> http://paste.ubuntu.com/899402/ ... mising /dev/genlock
[HTC Aria Android Development] s0be:
Backporting genlock is probably a bad goal... why are you trying (asking honestly)
[HTC Aria Android Development] munjeni:
Done it without any warning in compiling but hw still not working ...will try with new kgsl
[HTC Aria Android Development] s0be:
Did you add permissions for /dev/genlock to uevent?
[HTC Aria Android Development] s0be:
adding permissions for /dev/genlock fixed it....
[HTC Aria Android Development] s0be:
Doing one more build right now, might have the kinks of preliminary hw-accel worked out.
[HTC Aria Android Development] s0be:
Nope, bad things happened... will resume tomorrow.
[HTC Aria Android Development] s0be:
Next thing to look at is

CONFIG_MSM_KGSL_PAGE_TABLE_SIZE=0xFFF0000

I'm going to test a smaller value (currently that's 255mb, gonna try a reasonable 64mb to see if maybe we're just running into address space/ram issues maybe?)
[HTC Aria Android Development] s0be:
Nope, that wasn't the issue. It looks like the kgsl driver isn't finding our adreno chip. Perhaps liberty is wired differently than marvel. Will compare our old kgsl driver's probe routine with the current one to see if that's the difference. Has anyone seen a marvel dmesg from shortly after boot to see what it shows? This might help.
[HTC Aria Android Development] munjeni:
Yes I added genlock permision to ueventd and imported kgsl sucesfully from marvel kernel but again hw now working:( http://paste.ubuntu.com/900646/ ...how you got adreno partialy initiated... I can not get it... eglInitialize(0x1) failed (EGL_SUCCESS)

edit:

I don't have now any mmu page faults in dmesg using new kgsl ... in old kgsl driver I had some mmu faults! Here is dmesg http://paste.ubuntu.com/900655/

How you got this? -> V/AmazonAppstore.SoftwareEvaluator( 1420): OpenGL ES Version String: 0x00010000

edit:

after adding permision for kgsl-3d0 to ueventd, got something now:

- dmesg http://paste.ubuntu.com/900714/

- logcat http://paste.ubuntu.com/900716/
[HTC Aria Android Development] s0be:
You need to have /dev/kgsl-3d0 perm'd as well as /dev/genlock. Will snag ya an excerpt here in a sec. I'm gettins as far as the kgsl driver erroring on ashmem fd's and the blank screen, but completing init.
[HTC Aria Android Development] munjeni:
Same as me! And yes, I have kgsl-3d0 + with permisions in ueventd + genlock permision... previous post updated

eglLockWindowSurface: failed to map the memory for fd=13 offs=614400... ashmem problem?

---------- Post added at 05:40 PM ---------- Previous post was at 05:36 PM ----------

Forgot to say: I have compiled with comented line CONFIG_MSM_KGSL_PAGE_TABLE_SIZE

---------- Post added at 05:45 PM ---------- Previous post was at 05:40 PM ----------

This is interested line in log:

E/Adreno200-EGL( 114): eglLockWindowSurface: invalid memory type for fd=13 offs=614400, flags=676d736d

Invalid memory type? Wtf
[HTC Aria Android Development] munjeni:
Ok, but message invalid memory type! What this mean? I have:

#BOARD_USE_QCOM_PMEM := true

TARGET_GRALLOC_USES_ASHMEM := true

So maybe we need ashmem instead of pmem?
[HTC Aria Android Development] s0be:
I'm trying the other way, I'm gonna disable ashmem to see if we can get anywhere. Invalid memory type could mean lots of things. Looking at kgsl.c, that error likely stems from it being passed a fd that's mapped as non ashmem, and it expects ashmem.
[HTC Aria Android Development] munjeni:
hmm... I found something from my log about gps... ok that have not priority now but I think this will fix gps?

ln -s /dev/oncrpc/3000008c:00020002 /dev/oncrpc/3000008c:00020000
[HTC Aria Android Development] themacman1000:
I like watching you guys do all this trouble shooting. It's better than TV, at least for me. :D

Sent from my HTC Intruder
[HTC Aria Android Development] SectorNine50:
It's interesting, isn't it?

I'd love to help out, but quite frankly have no idea where I would even start... :confused:

By the way, I live near the other Portland, the one on the other side of the country from you! :)
[HTC Aria Android Development] s0be:
That's probably just something missing in our .config and/or something that's missing in th smd/rpc code (we didn't port ANYTHING from our own kernel, so there might be issues there)
[HTC Aria Android Development] s0be:
Can't disable ashmem, as the kgsl driver only works with it. It may be possible to update the kgsl driver to use pmem, but not gonna look into that route for now.
[HTC Aria Android Development] Darius_bd:
What keeps me wondering if this is the usual work devs have to do to make something work or if this little Aria is one tough nut to crack.

Either way, it's fascinating. I think I know how my parents felt when I was talking with my cousin about how to make the printer work.
[HTC Aria Android Development] s0be:
What it really comes down to is where a device falls in an android version's lifetime. If a device comes out RIGHT at the end of one android version (say, Froyo), and happens to get upgraded to the next version, odds are good that you'll have an easy time porting the code to future android versions... with the asterisk on the fact that significant changes in the android kernel can make for MASSIVE amounts of work to gain some things.

Another big key is how close the device is to one of the reference platforms (like mahi-mahi, etc) which generally get 'good' support from the ground up. In our case, we're running into a small issue in that our kernel was released with an old version of the adreno200 kgsl driver. Porting a driver from one kernel to another can be as easy as copying some files, or a royal PITA. We were lucky to have a very similar phone (the wildfire s) that has a very skilled dev working on the kernel. Using their work as a jumping off point makes it MUCH easier to get ours going. Much easier is, of course, relative because it's still really hard to get useful information as to why this is failing as we're battling closed source libraries (black boxes). We can see what goes into and comes out of the box, but don't have much insight into what it's actually doing.
[HTC Aria Android Development] themacman1000:
Portland, Oregon? Or the one in Maine? Cuz I've lived in both? And why do you mention this? :P

Sent from my HTC Intruder
[HTC Aria Android Development] themacman1000:
Edit: Never mind you meant Oregon. So you saw my local on my profile?

Edit #2:I derped and quoted instead of editing. :D

Sent from my HTC Intruder
[HTC Aria Android Development] s0be:
It also appears on hte left side of your post.
[HTC Aria Android Development] themacman1000:
Oh, its been about 3 months since I've used the website. :D Usually I just use Tapatalk.

Sent from my HTC Intruder
[HTC Aria Android Development] crxlvr:
Where did you guys learn this stuff. I thought I was pretty techy but I know nothing of programming other than basics.

Sent from my rooted phone
[HTC Aria Android Development] s0be:
I jumped in feet first with reckless abandon and no fear that I'd brick my phone... (On HTC Hero CDMA). Prior to that, I read a lot of the LKML mailing list.
[HTC Aria Android Development] eoghan2t7:
new armv6 ICS drivers have been released ;)

http://www.box.com/s/70aa8c3a8171c52727a3
[HTC Aria Android Development] tebuddy:
oh mein gott
[HTC Aria Android Development] rooterdam:
LOL!!

Thanks buddy, I needed that one!
[HTC Aria Android Development] jacobas92:
Forgive my ignorance but does this mean HW accel pretty soon?
[HTC Aria Android Development] eoghan2t7:
possibly after some extra coding to the source code/kernel source and stuff im not a dev im still learning so i could be wrong :p
[HTC Aria Android Development] jacobas92:
Sweet! really is a shame though, I'm upgrading on the 2nd. It'll still be fun to play with.
[HTC Aria Android Development] WinSuk:
Using the marvel kernel and the new arm6 files from qualcomm, it's displaying the first frame of the boot animation (white), and that's it.. freezes on that, but does finish booting up.. (and shows renderer : Adreno (TM) 200)

First error in the logcat:

I/Adreno ( 110): ioctl code 0x40140931 (IOCTL_KGSL_TIMESTAMP_EVENT) failed: errno 22 Invalid argument

which shows a few times, then a little farther down:

E/libgenlock( 167): genlock_wait: GENLOCK_IOC_WAIT failed (err=Connection timed out)
E/Adreno200-EGLSUB( 167): GetBackBuffer() genlock_wait failed
E/Adreno200-ES20( 167): <gl2_surface_swap:41>: GL_OUT_OF_MEMORY
E/Adreno200-EGL( 167): <qeglDrvAPI_eglSwapBuffers:3345>: EGL_BAD_ALLOC
E/Adreno200-ES11( 167): <qglDrvAPI_glTexImage2D:1913>: GL_OUT_OF_MEMORY
E/Adreno200-ES11( 167): <qglDrvAPI_glTexSubImage2D:2055>: GL_OUT_OF_MEMORY

and it just loops that for awhile..

I don't have the detailed log output turned on for EGL if that would even help..

I'll try to do stuff, but probably won't get anywhere :p
[HTC Aria Android Development] WinSuk:
Sorry for double post but... OMG!!

Got it working with munjeni's rom, the marvel kernel, and kgsl-3d0 + genlock added to the ueventd! (and new drivers of course)

Dunno if there's hwaccel, but it's much faster and stuff is correctly rendering like Gallery and the hold-home-button thumbnails

Live wallpapers still don't work, but that's because they don't support MDPI (from what I've read)

Edit: reverted this commit, and the wallpaper isn't scrolling, so I don't think hwaccel is working..

The "ioctl code 0x40140931 (IOCTL_KGSL_TIMESTAMP_EVENT) failed: errno 22 Invalid argument" is still there too...

Edit 2: Took out all the graphics stuff from the ueventd except kgsl-3d0 and it still works.. (kgsl-3d0 is needed. Tried it without, didn't work)

Some of it might be needed for hwaccel though
[HTC Aria Android Development] s0be:
Recompile your kernel with a smaller page size in the KGSL driver? Right now kgsl is set to use 256mb pages by default, which could explain OOM errors.
[HTC Aria Android Development] s0be:
Found the problem, the timestamp event was introduced in the 3.8 version of the KGSL driver. It's in the tiamat tree, working on merging changes now.
[HTC Aria Android Development] WinSuk:
Did you see the post after that? :p I got it working, no more out of memory errors.. but the timestamp one is still getting spammed in the logcat.

And I have pretty much no idea what I'm doing kernel-wise, I can build it and that's about it :p

Trying to build the rom from source now, but I'm stuck on this error:

hardware/qcom/display/libqcomui/qcom_ui.cpp:435: error: 'eglGetRenderBufferANDROID' was not declared in this scope

Think it needs to be defined in the include files, but I don't know where and what to set it to...

All these changes to qcom/display has caused it to not build anymore :-\

E: Nevermind, fixed it. (needed the QCOM_HARDWARE cflag put back in)
[HTC Aria Android Development] s0be:
http://pastebin.com/scNHdF5r

That patch will add the missing ioctl event. It boots with working HWA, but then deadlocks....
[HTC Aria Android Development] s0be:
After a cold boot, this patch seems to be stable... freaking SMOOTH too.
[HTC Aria Android Development] munjeni:
User space qualcomm armv6 binary is out? :eek: When? :eek:
[HTC Aria Android Development] dustinhayes93:
Anyway to get a zip of this? I gotta find my aria. Little bro lost it O.o
[HTC Aria Android Development] s0be:
Building a ROM out of it right now... I don't have an actual zip (I use fastboot for all my testing)
[HTC Aria Android Development] s0be:
Build failed, here's a kernel updater zip. You'll need to manually install the new libs for this to work.

[upload failed... pushing to a webserver]

http://liberty.s0be.com/liberty-kernel-1.zip
[HTC Aria Android Development] dustinhayes93:
Alright. Found my aria. Gonna be fun.

You guys think cm9 will be officially for Aria since the drivers are released?
[HTC Aria Android Development] s0be:
It seems quite probable, especially now that HW Accell works.
[HTC Aria Android Development] dustinhayes93:
OK. Took cm9 zip, added the new libs, then installed and flashed kernal... I'm still getting lag though =/
[HTC Aria Android Development] s0be:
Dunno, I'm running my own kang.... can't really upload it.
[HTC Aria Android Development] dustinhayes93:
Ill try more with it... maybe can get it.

Can't get it to work. Oh well. Ill keep watching the thread!!
[HTC Aria Android Development] munjeni:
How you resolved:

frameworks/base/media/libstagefright/ACodec.cpp:172: error: expected primary-expression before 'struct'
frameworks/base/media/libstagefright/ACodec.cpp:172: error: expected ',' or ';' before 'struct'
frameworks/base/media/libstagefright/ACodec.cpp:3006: error: expected '}' at end of input
make: *** [out/target/product/liberty/obj/SHARED_LIBRARIES/libstagefright_intermediates/ACodec.o] Error 1

Do you want to post your ACodec.cpp