yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] xillius200:
Yes, but hardware acceleration still may be possible on our adreno 130 as we have opengl es 1.1 which can be used to accelerate the UI if we modify android around it. The adreno 130 DOES have support for hardware accleration with opengl es 1.1 and hardware acceleratiin has been used for a while on htc dream just not opengl es 2.0 as not avaliable so we HAVE had/got a form of hardware accleration just not for UI and with the opengl es 1.1 you posted they could infact help but modifiying android to use opengl es 1.1 to obtain full UI hardware acceleration IS possible will just take a lot of time and effort and someone who would sit there and actually do it lol

PS: Like i said we have had hardware accelerated graphics since android 2.1 for htc dream if you dont believe me search the net. cyanogenmod was the one who made hardware acceleration in android 2.1 possible so we could have better youtube, live wallpapers and 3D acceleration. Now we just need that for the UI.
[G1 Android Development] whoshotjr2006:
its not really a matter of if someone *would* take that time to do all the stuff that needs done, its a matter of if they *could* do that stuff. yeah someone on this earth could do it, its not 100% impossible to write a patch that could emulate some gpu things we need, but good luck finding that person. most devs have already passed on it in hero/heroc land or moved on and just dont care about it anymore.

there are people out there that know alot more that us about this stuff, like qualcomm, the openfimg project, and and another guy i saw somewhere wrote a 2d compositor that aimed to help out ics graphics. the only problem is, these guys are insanely talented and knew what they needed to accomplish, but both those projects seem a bit stalled right now, and at least one of them seemed to just move on to completely different projects. and qualcomm already stated its just about technically impossible. if you or anyone else sees another project like these that could help us, pass the message along.

if you know how or know anybody who does, please send them our way. we'd be glad to test. finding someone who has specialty in what we need done is likely not to happen, as if it could have happened by now, it most likely would have.

until then, its better to be realistic with people instead of getting their hopes up
[G1 Android Development] xillius200:
Your so negative!!
[G1 Android Development] whoshotjr2006:
not negative, realistic

by the way, the guys in charge here please check this out: http://xdaforums.com/showpost.php?p=28642855&postcount=16

i cherry picked libs from the buzz, and ended up with youtube! lol

hq doesnt work well, it stutters like mad, but regular actually works close to on par with gingerbread

if it works for you guys (which i cant see why not) then all credit to erwinp at the buzz forums

zip is not flashable, if nobody else wants to create one, let me know. ill do it.
[G1 Android Development] xillius200:
Lol no negative and as you said devs would be on it already lol take miui for example and see how long that took along with many other things for the htc dream xD

Blah ive given up with talking anymore on this subject anyway.
[G1 Android Development] whoshotjr2006:
Yeah lets move on to new topics. Feel like testing YouTube for me?

sent from my heroc running cm7.2
[G1 Android Development] Infinimint:
Let's sum up this conversation :)

Hopefully:

- We get HW Acceleration by someone who knows how to implement it and focus Android entirely around legacy hardware with legacy drivers.

Realisticly:

- We will not be getting hardware acceleration, although we may find other ways to increase the speed and get things working (such as YouTube).

Positively:

- I'm going to buy the CM Storm Quickfire Rapid with Cherry MX Red mechanical keys for ~$90. :D
[G1 Android Development] hrk:
Did you know about these patches? https://github.com/ErwinP/android
[G1 Android Development] tvall:
syncing jellybean. going to work on getting a good cm9 build and a usable aokp build before i work on jb. expect something this week :)

I'm in need of a laptop. if 30-40 people donated $10, id beable to buy something pretty usable. which would mean i can go t starbucks or mcdonalds to download sources, go home to work, then go back to upload. meaning much more dev time. but then id need a way to receive donations....
[G1 Android Development] tvall:
little update (at 0:52....)

cm9 is being a... bad word.. and failing while building libwebcore. i'll probably try to fix it tomorrow. aokp is playing nice. and jellybean... i'm keeping quiet for now. all im saying is so far all is going well. expect a frustrated, curse filled post within a few hours/minutes
[G1 Android Development] tvall:
oops.. double.

works out because i needed to post that jb failed. heres the error:

target thumb C++: libstdc++ <= bionic/libstdc++/src/new.cpp
In file included from bionic/libc/private/bionic_atomic_inline.h:53:0,
from bionic/libstdc++/src/one_time_construction.cpp:15:
bionic/libc/private/bionic_atomic_arm.h:54:4: warning: #warning Rebuilding this source file in ARM mode is highly recommended for performance!! [-Wcpp]
In file included from bionic/libc/private/bionic_atomic_inline.h:53:0,
from bionic/libstdc++/src/one_time_construction.cpp:15:
bionic/libc/private/bionic_atomic_arm.h: In function 'int __cxa_guard_acquire(_guard_t*)':
bionic/libc/private/bionic_atomic_arm.h:156:25: error: unknown register name 'r3cc' in 'asm'
bionic/libc/private/bionic_atomic_arm.h:156:25: error: unknown register name 'r3cc' in 'asm'
bionic/libc/private/bionic_atomic_arm.h: In function 'void __cxa_guard_release(_guard_t*)':
bionic/libc/private/bionic_atomic_arm.h:156:25: error: unknown register name 'r3cc' in 'asm'
make: *** [out/target/product/dream_sapphire/obj/SHARED_LIBRARIES/libstdc++_intermediates/src/one_time_construction.o] Error 1
make: *** Waiting for unfinished jobs....
[G1 Android Development] hrk:
I don't understand if using -Wcpp is going to fix the error... or not.
[G1 Android Development] AndDiSa:
Have a look here. They are facing the same problem. Seems as if the asm code is not written in a way to support armv6.
[G1 Android Development] tvall:
Got through that error. Thanks.

Lets see what breaks next...
[G1 Android Development] tvall:
so i'm going to wait for cm to make some progress on jellybean before i work more.

for now, i found this -> http://review.cyanogenmod.com/#/c/11167/

looks promising. still need to figure out what broke my cm builds.
[G1 Android Development] tvall:
cm is building again. reverted to an older point in webkit. going to figure out exactly where it broke after this build finishes. then i'm going to start adding stuff from all the recent posts here.

edit: build is done. i'll be uploading it here as fast as my tethered, throttled, slow anyway internet allows
[G1 Android Development] Infinimint:
Did you test it yet?
[G1 Android Development] tvall:
nope. was at the park with my girlfriend while it downloads. the mytouch belongs to my girlfriend, so if she allows, i'll test tonight (and test data) then upload while I'm sleeping

edit with testing results: i see no reason to not upload. everything is about the same as the last build, but newer. and i confirmed data is working.

now i go back to work on speeding up the ui....

upload coming soon

this is where jb is currently stuck at :

frameworks/native/opengl/libs/EGL/egl_display.cpp:168:2: warning: #warning "Adreno-130 eglInitialize() workaround" [-Wcpp]
frameworks/native/opengl/libs/EGL/egl_display.cpp: In member function 'EGLBoolean android::egl_display_t::initialize(EGLint*, EGLint*)':
frameworks/native/opengl/libs/EGL/egl_display.cpp:176:13: error: 'i' was not declared in this scope
frameworks/native/opengl/libs/EGL/egl_display.cpp:176:18: error: 'IMPL_HARDWARE' was not declared in this scope
make: *** [out/target/product/dream_sapphire/obj/SHARED_LIBRARIES/libEGL_intermediates/EGL/egl_display.o] Error 1
make: *** Waiting for unfinished jobs....
[G1 Android Development] tvall:
http://dl.dropbox.com/u/19978192/android/update-cm-9.0.0-RC0-dream_sapphire-alpha2.2.zip

enjoy
[G1 Android Development] tvall:
not making any progress on jellybean... need to listen to my own advice and wait...

going to work on hw acceleration later today or tonight
[G1 Android Development] frankdrey:
Will try right now. :D
[G1 Android Development] SlashSpeed:
I wish you luck. I hope you succeed.
[G1 Android Development] ryree0:
Edit:

Actually, I'm not sure why you are not loading up /system/usr/icu/icudt46l.dat, the file is included in the rom; however...

So, try unzipping the rom, then manually pusing icudt46l.dat into /system/usr/icu and setting the correct permissions.

@Tvall: The error seems to be on his end, after looking through the rom.
[G1 Android Development] tvall:
well... it works on my girlfriend's mytouch 3g 1.2.... i'll look into it soon. sorry.
[G1 Android Development] tvall:
got past the egl errors (by cheating and commenting out the line that was causing the error). now stuck at libaudio errors......
[G1 Android Development] frankdrey:
Psh. I installed the ROM normally. Didn't touch anything

I can't try what you said to do right now.

Need my phone today :p
[G1 Android Development] xanda143:
Is this still being developed
[G1 Android Development] hrk:
The last dev related post was less than 24 hours ago.
[G1 Android Development] tvall:
cm9 alpha2.2 was released yesterday. any more current than that would have to be nightly builds, which i don't see necessary at this point. a new aokp build is coming eventually. and cm9 will have some speed work done, unless i go to jellybean and skip finishing cm9. this is definitely still being developed. i took a break from looking up linaro stuff (cm dropped the idea, so i probably wont mess with it) to reply to your post.
[G1 Android Development] rosser725:
Does CM9 work better than Aokp?
[G1 Android Development] tvall:
maybe. cm9 is a little more up to date. cm also has official support for armv6. I had to patch in armv6 support for aokp. aokp is also missing some aoos (like music). test both and temm me which is better for you
[G1 Android Development] rosser725:
alpha2.2 just stays at the boot animation
[G1 Android Development] xanda143:
Prob could have googled this bjt u were online I want to know what is the diff between cm9,aokp and aoskp. I know cm is like the official mod of roms that most devs

Build their own roms what are the other two and I don't think u should skip this and go to jelly bean

And as for the hardware accel work diligently plz and thanks for all the work
[G1 Android Development] blaster44:
Working good for me. Orange HTC magic.
[G1 Android Development] demkantor:
cm9 refers to cyanogenmod 9, that is the cyanogen teams tweeks to android vanilla ics (android 4.0.x) aokp is kanged tweeked roms, developed by the kanged team (sometimes a kanged rom would just mean ported to some but specificaly ported from kang source. there is no aoskp, just aosp, stands for android open source platform. this is the vanilla rom, the one android makes before any dev or any phone company/carrier adds there own codes, apps, ui, etc

think of these terms as where the sorce of the rom is built from, everything starts aosp, but if a dev starts of a cm tree then the rom is their version of a cm rom and what you expect from cm should be in that rom.
[G1 Android Development] Infinimint:
AOSP (Android Open Source Project) is the standard Android operating system developed by Google & the Open Handset Allience.

CM (CyanogenMod) is an aftermarket android firmware developed by the CM Team with the goal of bringing the joy of stock AOSP to all devices. However, it also includes a large assortment of tweaks and mods to accomodate the wants of the users.

AOKP (Android Open Kang Project) is another aftermarket firmware developed by the AOKP team that includes an enormous assortment of tweaks and mods with more being added all the time. The name refers to the term "kang" coined by CyanogenMod which basically means to steal others work and lazily throw it together although in this case the term is not used literally.

So basically:

- AOKP = Stock

- CM = Stock + Mods/Tweaks

- AOKP = Stock + Tons of Mods/Tweaks
[G1 Android Development] :
I see that most Dream users have bootloop because there is no sd-ext script.

Magic has 512mb nand compared to Dream's 256mb nand, that is why it works on Magic.

Dream runs out of space for dalvik-cache and it causes bootloop.

Try to push this script (name it as 04ad2ext or similar) into /system/etc/init.d, remember to chmod 777 it.

#!/system/xbin/busybox sh
# Simple apps2ext script -jianC/e334
# based on CM "apps2sd" script

busybox=bb
logwrapper=ll

if [ ! -d /sd-ext ]; then
$bb mount -o rw,remount -t rootfs rootfs /
$bb mkdir -m 771 /sd-ext
$bb chown 1000:1000 /sd-ext
$bb mount -o ro,remount -t rootfs rootfs /
fi

if [ -n /dev/block/mmcblk0p2 ]; then
$ll echo "+++ Mounting SD-EXT +++"
busybox mount -o noatime,nodiratime -t auto /dev/block/mmcblk0p2 /sd-ext
if [ $? -eq 0 ]; then
echo "+++ Successfully Mounted +++"
echo "+++ Enabling Apps2Ext +++"
for i in app-private app dalvik-cache; do
if [ ! -d /sd-ext/$i ]; then
$bb install -m 771 -o 1000 -g 1000 -d /sd-ext/$i
fi
if [ -d /data/$i ]; then
$bb cp -a /data/$i/* /sd-ext/$i/
$bb rm -r /data/$i
ln -s /sd-ext/$i /data/$i
fi
done
else
$ll echo "--- Mount SD-EXT Fail ---"; exit 1
fi
else
$ll echo "--- A2ext not mounting ---"; exit 0
fi

sync
[G1 Android Development] xanda143:
Thank u both for these they realy helped and i know not hust me:thumbup::thumbup::):)
[G1 Android Development] frankdrey:
Yes, I thought so.

Thank you :)

Will try once I get a new phone.

I'm getting an LG G2x in a few days (for $100!!!!), and then ill be able to do all kinds of crazy shizz on my G1.
[G1 Android Development] Infinimint:
Haha best of luck ;)
[G1 Android Development] xanda143:
Hey the dowbload link for the partition map is down fix please
[G1 Android Development] blaster44:
Found bugs:

lights(I fixed this)

screenshooter

camera, camcorder

hadrware acceleration

microphone

gallery
[G1 Android Development] blaster44:
Hey, think logic. Magic may have two radios, old and new. On old radio on magic work ROMs from G1. On new radio, work ROMs from hero. Both radios have gingerbread support. On both radios, gingerbread's kernels working on ICS. PowerPlop was port ROM from Hero mainly trough swapping kernel. He used normal gingerbread kernel. Gingerbread never was support hardware acceleration, kernel which used PowerPlop is old as others kernels. But working. Working on ICS, supporting ICS camera and... supporting hardware acceleration(?!). Yeah, this ROM have working HW acceleration. On old gingerbread kernel. How is that possible?

OK.

In my opinion problem lies in ROM only. Maybe in libs. Maybe in graphic drivers. Maybe only in build.prop lines. But in ROM, not kernel. Sometimes the solution is simple and ingenious. I haven't huge knowledge about android and certainly smaller than you. As PowerPlop. He ported ICS from hero, becouse he did not know that it can not be.

I fixed lights in this ROM simply swapping some files/one file from PowerPlop's ROM. This is only example. As I wrote, i haven't huge knowledge about android, so I don't know where is files responsible for HW acceleration. I want to help you, but i lack the knowledge. I don't know what files I can try swap for achieve the effect and not take bootloop.

PS.

Sorry for my bad English, I hope that you understand.
[G1 Android Development] tvall:
/sytem/lib/egl/ conains the graphics libs. libGLES_android.so is for software rendering. libGLES_qcom.so is the hardware one. egl.cfg controlls what gets used when. hardware is currently intentionally disabled because with it, the screen just goes black. so the issue is either that lib, or something in the rom. haven' figured it out yet. you could try swapping that file and enabling it in the config.
[G1 Android Development] xanda143:
uhhm i know its not perfect or done and i didnt flash kernel in post i flashed cronmods stand alone is this laggy bad and it keeps asking me to restart for network...grade ui from 1-10 please
[G1 Android Development] blaster44:
Can I do something with microphone? For me not working.
[G1 Android Development] frankdrey:
Ok, so the problem with the G1 is that CMTD seems to be not working, because a lot of system files don't get copied. :/

Or maybe i need to increase it. I'll try 150 for /system
[G1 Android Development] Infinimint:
Haha I think I figured out how to fix it ;)
[G1 Android Development] frankdrey:
Oh whoops my fault. I was writing the mtd file wrong xD

Here's the rom with the a2ext script above included. I'm about to test it.

http://www.sendspace.com/file/okx21p
[G1 Android Development] blaster44:
Only for me microphone not working?
[G1 Android Development] frankdrey:
Okay, MTD is just not working.

The partitions aren't resizing.

On United CWM.
[G1 Android Development] demkantor:
use amonra, cmtd isn't working right with united right now... soon I hope! can't wait for a fully working touch recovery!
[G1 Android Development] tvall:
Well even though I am a member of united and we do have that recovery, I am using cwm 2.5.0.7 on my girlfriend's phone. Been too lazy to change it.
[G1 Android Development] frankdrey:
So, I finally got it to flash correctly.

Now it shows the CM9 boot animation instead of the stock android.

But it still won't boot.

http://pastebin.com/hn0j43BT
[G1 Android Development] blaster44:
Anybody have this problem too?
[G1 Android Development] tvall:
Give it like 20 minutes to boot.

I haven't tested it yet
[G1 Android Development] frankdrey:
Ahhh, yes it booted in like 20 minutes. I just turned it on and put it in my pocket 30 minutes ago :P and i take it out and it's on!

It's actually not half bad. Biggest problem is that on the G1 we have dalvik on ext, and that makes everything slow in general. But its really stable. Other than low FPS (most likely due to dalvik on ext, I think from my past experience with sense launcher lagging until i moved dalvik to nand), it's really nice. There isn't a notification bar but i think i musta pocket set that :P I'll figure it out :D

Maybe if we can figure out a way to stick some rarely loaded system files on ext and move dalvik back to data, it'll be nice! :D
[G1 Android Development] tvall:
Next release will have a script for dalvik (and apps maybe) on ext, possibly odexed, and hopefully with some progress on hw accel
[G1 Android Development] xanda143:
hey is the first kernel in your post for 32b and does anyone know a way i can remove or freeze cmtd as it isnt compatible to do alot of stuff if i want to use a rom that dosnt use it can i just not flash the cmtd boot
[G1 Android Development] tvall:
The kernels are for 32b (2708+ and ebi0) and 32a or (ebi1)

You need custommtd for this rom to fit. You could always modify it to put lots of stuff on /sd-ext or something, but that's a lot more work than remembering to flash fr-remove.zip when you change roms
[G1 Android Development] frankdrey:
I don't think you understood what I meant :P

Moving dalvik to ext is a bad idea. Really bad. It slows us down a ton. You Mytouch users are lucky you have enough space :D

Moving apps to ext is fine, but dalvik should stay on data. Although we don't have enough room for even that :S

My idea is to do the necassary hard work to move rarely used system files to ext, and leave room for dalvik on ext
[G1 Android Development] tvall:
With ics, there is not much choice. The device I use as my daily has164mb system, 178mb data, and 110mb cache and you run out of space quickly without moving stuff. Works okay with dalvik on ext. I'll release a couple test builds (lacked a, 1, and lemon, so no one knows which is which) one will have the script I was thinking of using, one will just move apps, and one will be the current build. Good plan?

I don't want to put system files on ext because the phone would need that specific card to boot at all.
[G1 Android Development] frankdrey:
Ok, sure.

I think ill try moving some system stuff to ext, since I don't ever take out my card :P
[G1 Android Development] blaster44:
Any way to solve screenshooter and prewievs in recent? On new radio this problems exists too.
[G1 Android Development] tvall:
I've seen a patch for fixing screenshot, haven't added it yet. Will do soonish...
[G1 Android Development] Infinimint:
HOW DID YOU GET PAST THIS? I NEED TO KNOW!!!

(yeah i'm yelling, it's urgent)

Edit: After reading more, I installed Amon Ra, that didn't fix it.
[G1 Android Development] blaster44:
Can you give link?
[G1 Android Development] :
It's probably a github patch that needs to be integrated into the source..
[G1 Android Development] frankdrey:
On Amon_Ra, flash the recovery MTD. Reboot, open console, and type cat /proc/mtd to make sure mtd set correctly. Normally the mtd's start with 05 or so for data and system. Now, system should be a lot bigger. I also gave it about 160 mb for system.

Then you flash the ROM, gapps, kernel, boot MTD and reboot.

If you did mtd correctly, you'll have the cm9 boot anim instead of the stock android boot anim. Now just wait 30 minutes :D
[G1 Android Development] Infinimint:
Okay, here's the deal: I'm working on a HUGE project that the whole community can benefit from and the only thing stopping me from finishing it is this error. I'd give more details, but I want it to be a secret until the release. (It's not a new recovery btw)

I already flashed AmonRa. I did not flash CustomMTD since the partition sizes are already large enough on the Magic, and the system size of the rom is only 72.4MB

I cannot get past the MyTouch 3G Green Screen. The error repeats itself even after waiting for 30 minutes.
[G1 Android Development] tvall:
Lol, secret projects. If people knew where to look, it wouldn't be so secret.

If I knew what was causing it, I'd help. But I'm assuming the devs of the project you're working on did something to the audio. Try building without audio, maybe that'll get it booting for now
[G1 Android Development] Infinimint:
Precisely ;)

I thought about it, but before I do that, I'm going to try again with CM7 repos (which should work perfect).
[G1 Android Development] hrk:
Try compiling with debug information, it'll be way easier to understand what's wrong. SIGSEGV means a bad memory access, most likely a bad de-referencing (bad pointer).

I'm surprised that the memory address of the error is deadbaad :eek:
[G1 Android Development] tvall:
you're practically yelling "I have a secret project I'm working on! You can see everything I'm doing and probably even build it yourself, but its still a secret!"

I'd try without the libaudio first, then use the cm7 one.
[G1 Android Development] frankdrey:
My problem was that some libs didn't copy, because I ran out of space because custom mtd wasn't working.

Lol 0xDEADBEEF!!! (I wonder if anyone will recognize this:P, its a joke a buncha psp devs I know have on irc)
[G1 Android Development] Infinimint:
Would you be able to elaborate a little bit on this? Is is a command I need to run or a repo of some sort?
[G1 Android Development] hrk:
I'm not really familiar with the Android build system, but if you're using gcc to compile the native libraries, then it's just a matter of passing the right flags (i.e.: -g should be the one to produce debug information).

This should give a more verbose output in crashes in native libraries (C code), which may help understanding where the issue is.

EDIT: Check this out: http://www.kandroid.org/online-pdk/guide/build_system.html

From what little I can understand about Android Build System, it looks like it's just a matter of calling

make -j4 PRODUCT-generic-eng

instead of

make -j4 PRODUCT-generic-user
[G1 Android Development] Infinimint:
Oh, I'm pretty sure I had made an eng build... lemme check real quick.

EDIT: Yeah, it is eng.
[G1 Android Development] hrk:
Then I don't have a clue. :| The memory dump didn't contain source code references, so that means there's something else missing and I don't know how to enable it.
[G1 Android Development] :
@tvall: when I run repo sync, I don't seem to get the updated version of your source with the fixed bugs..