yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] tekgek:
This is probably a stupid question, but could someone please go over the steps necessary to enable 3d on the G1? I tried following this thread, and modifying boot.img in accordance with what people were suggesting. I am currently running OpenEclair v1.2.2. Any help at all is greatly appreciated.
[G1 Android Development] borodin1:
Here's another stupid question. Is there any benefit from this for 1.6 roms? I am not sure that I want Eclair on my G1 just yet, I would like to stick with Donut for now until I get a device that can actually handle Eclair in it's stock form.
[G1 Android Development] georgefrs:
@tekgek

Getting this working is quite involved, but it will be popping up in various roms including the next version of OpenEclair. We won't have long to wait. If you want to try it out beforehand, there are two roms that have been patched by Case__ earlier in this thread you can install. Follow the instructions in the corresponding links. Those roms aren't meant to be stable day to day roms though, just a proof of concept.

@borodin1

1.6 roms (Donut) already have functioning OpenGL acceleration (along with video decode/encode). So no, no benefit at all. The problem was that the bits that make it work in 1.6 didn't work on the newer roms, but these clever people have managed to get it working again. Once video decode/encode is supported, the Dream and Magic will be able to support Eclair just about as well as they do Donut.
[G1 Android Development] gophergun:
No, the hardware 3D (and indeed, everything) is already working properly with the right drivers on Donut.

EDIT: Sorry, already answered better. :p
[G1 Android Development] borodin1:
Thank you both. I may give it a whirl once it's implemented. Still have horrors from early Hero roms :-)
[G1 Android Development] tekgek:
I'm sure it will, but I am interested in the process itself. I spent the last couple of nights messing around with the init.rc file, but to no avail. I guess what I am asking is, is anyone who knows how the other devs got this working to please share the process, if they can. I think I can speak for a number of people when I say it would be very good to know how to do this ourselves.

Thanks,

tekgek
[G1 Android Development] lbcoder:
32B devices (dream/magic) ***CAN*** handle eclaire in its "stock" form.

Delete the hardware drivers from a GN1 and it'll work badly too.

The very stock (i.e. opensource ONLY) AOSP won't run at all on ***ANY*** hardware.... EVERY device requires specialized drivers to function to its potential.
[G1 Android Development] lbcoder:
Kernel patch + permissions + 32A drivers.
[G1 Android Development] gophergun:
Hm, one thing I keep running into in logcats is this line:

E/copybit ( XXXX): Error opening frame buffer errno=13 (Permission denied)

Does this mean anything to anyone? Any ideas on how to fix it? It seems like it would be easy enough for someone that knew where to look.
[G1 Android Development] tekgek:
Kernel patch: what exactly does that involve?

Permissions: got 'em, in init.rc, easy enough

32A drivers: okay, which library files?
[G1 Android Development] M..N:
Could we use the drivers in the new 2.1 Droid Eris leak?
[G1 Android Development] Case_:
Actually, I don't think any kernel patch is involved as far as Cyanogen sources for Eclar are involved. The kernel images I made are based on vanilla CM Eclair kernel, no patching involved. Just camera driver is backported (or is it "forwardported"? ;) ) from Donut sources to get camera compiled and working.

BTW I've already mentioned most of this somewhere around here, so try searching.
[G1 Android Development] M..N:
So was the CM kernal modified in any way?
[G1 Android Development] mssmison:
You need' HW3D support added to your kerenl,

init developed for android that supports HW3D (most eclair ones do)

than these drivers and the libqcom egl driver.
[G1 Android Development] lbcoder:
They might be compatible, but we really DON'T CARE.

We already have the required drivers.
[G1 Android Development] M..N:
Ok. What was exactly done to the kernal to enable Hardware GL.
[G1 Android Development] ZhekaS:
Is there a fully working (and stable) Eclair rom with these drivers available ?
[G1 Android Development] georgefrs:
It's cool that OpenGL is now working so the drivers for that aren't necessary from the new Droid Eris dump (although they could be a newer version, be interesting to see if the files differ at all from the ones being used at the moment).

However from what I understand the new Droid Eris dump is fully working with Camcorder and Video (I could be wrong, I couldn't find any reports to the contrary though). I wonder if there is anything from the dump that might help us with those aspects on 32B?
[G1 Android Development] lbcoder:
@georgefrs: ERIS dump works fully.... on ERIS.

HERO dump (from where we got the drivers) ***ALSO*** works fully.... on HERO.

CAMERA drivers are NOT COMPATIBLE -- the hardware is different.

We HAVE video drivers.

Just be patient.

@ZhekaS: No. Wait. Not much longer. You won't have to ask, the first proof of concept system image was Case_'s, the first mostly functional system image will probably be OE 1.3, and as soon as that hits, you'll see a bunch of kiddy dev's releasing copies of it under their own names and trying to take credit for it.
[G1 Android Development] lbcoder:
You can read the source?

http://github.com/openeclair?

If you can't read the source, then there's nothing anyone could really explain to you about it that would give you a better understanding anyways...
[G1 Android Development] st0kes:
Just a tad patronising, if OE are first with 3D acceleration it doesn't make everyone else 'kiddy devs'. Plus most people on XDA do give credit where it is due.
[G1 Android Development] Case_:
Did I really write it so uncomprehensibly? Quote myself from today, this very thread, just a few posts before your question:

"Actually, I don't think any kernel patch is involved as far as Cyanogen sources for Eclar are involved. The kernel images I made are based on vanilla CM Eclair kernel, no patching involved."
[G1 Android Development] Firerat:
I can confirm this, I have just complied a kernel for CaNNon's eclair, since the wifi wasn't working in the ones Case made for the other ROMs.

I didn't do anything to the source, just grabbed CM's eclair branch

mind you, the Camera isn't working :(

Case_ , I think you did mention that you had to take the camera from the Donut kernel's tree, so I'm going to have look at that.

PS, big thanks to Case_ , I would have never done it without you pointing the way :D
[G1 Android Development] Case_:
Yeah, had to take the camera from Donut (surprisingly enough, it works). The eclair msm_camera doesn't even compile for me, seems like there's some missing variable declarations, I think (or something like that).
[G1 Android Development] Ohsaka:
Just installed the patched Cannon Eclair ROM on my G1. Got 26.4 FPS in the Neocore benchmark. Pretty cool. I will try and post some higher quality video on Youtube later tonight.
[G1 Android Development] ttc_smokee:
nvm... i'll let somebody else deal with it
[G1 Android Development] Ohsaka:
Youtube video is uploaded. Even using my good Logitech webcam, it still doesn't do it justice. 24+ frames/sec is SMOOTH in person...

http://tinyurl.com/3dneocore
[G1 Android Development] speedysilwady:
wow that looks really awesome! thanks for recording a video and sharing! does the galaxy wallpaper work?
[G1 Android Development] Ohsaka:
Not really.... it looks like it is trying hard though, lol.

Logcat shows the following:

03-05 00:54:03.331: INFO/ActivityManager(2739): Start proc com.android.wallpaper for service com.android.wallpaper/.galaxy.GalaxyWallpaper: pid=4053 uid=10016 gids={1006}
03-05 00:54:03.431: DEBUG/ddm-heap(4053): Got feature list request
03-05 00:54:03.641: INFO/ActivityManager(2739): Displayed activity com.android.wallpaper.livepicker/.LiveWallpaperPreview: 619 ms (total 619 ms)
03-05 00:54:03.781: DEBUG/dalvikvm(4053): Trying to load lib /system/lib/librs_jni.so 0x0
03-05 00:54:03.801: DEBUG/dalvikvm(4053): Added shared lib /system/lib/librs_jni.so 0x0
03-05 00:54:03.811: VERBOSE/RenderScript(4053): RS Launching thread
03-05 00:54:03.821: VERBOSE/RenderScript(4053): setSurface 320 480 0x11bdd0
03-05 00:54:03.831: VERBOSE/RenderScript(4053): initEGL start
03-05 00:54:03.831: DEBUG/libEGL(4053): loaded /system/lib/egl/libGLES_android.so
03-05 00:54:03.851: DEBUG/libEGL(4053): loaded /system/lib/egl/libGLES_qcom.so
03-05 00:54:03.861: DEBUG/EGL.oem(4053): smi: offset=10000000, len=00700000, phys=0x0
03-05 00:54:03.861: DEBUG/EGL.oem(4053): ebi: offset=00000000, len=00800000, phys=0x16500000
03-05 00:54:03.861: DEBUG/EGL.oem(4053): reg: offset=20000000, len=00100000, phys=0xa0000000
03-05 00:54:03.882: DEBUG/gralloc(2739): allocating GPU size=307200, offset=0
03-05 00:54:03.891: VERBOSE/RenderScript(4053): GL Version OpenGL ES 1.0-CM
03-05 00:54:03.891: VERBOSE/RenderScript(4053): GL Vendor QUALCOMM, Inc.
03-05 00:54:03.891: VERBOSE/RenderScript(4053): GL Renderer Q3Dimension MSM7500 01.02.08 0 4.0.0
03-05 00:54:03.891: ERROR/RenderScript(4053): Error, OpenGL ES Lite not supported
03-05 00:54:05.231: ERROR/libEGL(4053): called unimplemented OpenGL ES API
03-05 00:54:05.813: DEBUG/gralloc(2739): allocating GPU size=307200, offset=307200
03-05 00:54:05.821: ERROR/libEGL(4053): called unimplemented OpenGL ES API
03-05 00:54:06.272: DEBUG/gralloc(2739): allocating GPU size=307200, offset=614400
03-05 00:54:06.272: ERROR/libEGL(4053): called unimplemented OpenGL ES API
03-05 00:54:06.724: DEBUG/gralloc(2739): freeing GPU buffer at 0
03-05 00:54:06.724: DEBUG/gralloc(2739): allocating GPU size=307200, offset=0
03-05 00:54:06.731: ERROR/libEGL(4053): called unimplemented OpenGL ES API
03-05 00:54:07.178: DEBUG/gralloc(2739): freeing GPU buffer at 307200
03-05 00:54:07.181: ERROR/libEGL(4053): called unimplemented OpenGL ES API
03-05 00:54:07.627: ERROR/libEGL(4053): called unimplemented OpenGL ES API
03-05 00:54:08.076: ERROR/libEGL(4053): called unimplemented OpenGL ES API
[G1 Android Development] axlastro:
So maybe a link to this pre-alpha rom for us to get the taste... megaupload, rapidshare, anything...
[G1 Android Development] Firerat:
its in CaNNoN's Complete Eclair thread

its nothing new really, we were using Case_'s AMeclair Patches, but wifi wasn't working, so i just tookmy cue from Case and complied

cyanogen-cm-kernel-2.6.29-6 eclair branch, fixed up the init.rc and well, that was it really.

Camera was broken so I just kinda skipped over that ;)

However I'm happy to say that I have gone back and got the camera working again buy pulling the code from the donut branch, again taking my cue from Case_.

PS when I say camera working it takes a picture, not video.

Preview window can be a little gabbled just after a shot, same as with any Eclair ROM tbh.

As I said , nothing new just a little more functional for CaNNon's ROM
[G1 Android Development] ahmgsk:
bro is this video of my rom??

just asking!!
[G1 Android Development] speedysilwady:
he said it was Canon's rom i believe
[G1 Android Development] ahmgsk:
okay thx -> np
[G1 Android Development] phillyboi47:
help?

Iight I'm asking this Cuzco I wanna be cautious. I understand you have to patch ur current rom. To get the drivers to work, but which patch should I go by? I'm running complete eclair.
[G1 Android Development] Firerat:
post #667 in ce thread if you want to try it
[G1 Android Development] kingklick:
cant get it to compile...

what fixes do i need to make to camera ...........
[G1 Android Development] Firerat:
drivers/media/video/msm/ from Donut to Eclair

then a few additions to some headers and board.trout.c

deadlink

its a bit clumsy, I might have a better look and make it neater

but tbh I no C coder, the little I have learnt in the past I have forgotten :(
[G1 Android Development] pakett86:
em really looking forward on some development in this thread...why is it here so "quiet" here? :confused:
[G1 Android Development] axlastro:
Because development for the G1 has almost died... It's probably time to move on.
[G1 Android Development] lbcoder:
DREAM development is NOT dead.

The reason this thread is quiet is because it has come to fruition! This thread has served its purpose!

The information and procedures uncovered here are now being applied to new builds!

There are (as found within this thread) several proof-of-concept system images around, there are also some hacked-up-but-functional system images around incorporating these changes, and the hopefully soon-to-be-released OpenEclaire 1.3 holds a LOT of promise. The beta for that is private, but apparently GL based functions, i.e. Launcher2 (include live wallpapers) and the new Gallery are working *really slick* on DREAM.

References:

http://code.google.com/p/openeclair/issues/detail?id=263

http://twitter.com/ChrisSoyars/status/10458404017

:D
[G1 Android Development] axlastro:
Well maybe we are a bit spoiled by new roms going out every day :)

As I said it's almost dead - not quite and could be easily revived if there are more people like you to do the job instead HTC and GOOGLE. Personally, I'm not a big fan of changing my handset every year, especially if there isn't something much better around. There's one question though :

Have you tried some more demanding games with this "private beta" rom and how does it perfor, as most of the patched roms (like king's and lazlo) perform like they have the ram hack enabled during gameplay, even when it's not.
[G1 Android Development] lbcoder:
I'm not involved in the beta testing for OE.

Ram hack kills 3D.

So if 3D is gone, you get sucky performance.

As long as 3D is working, the performance will be fine.
[8525, TyTN, MDA Vario II, JasJam General] frankie13:
how do i get internet radio to the headset tried bttoggle no luck and bt audio no joy there for my t-mobile mda vario 2 :(
[HD2 General] Bib_x:
Hi,

i´m looking for a app to count my outgoing calltimes and sms.

I tried homescreen plus plus (HS++) but it seems not to work properly. The calltimes and sms aren´t counted right.
[HD2 General] Shadowdh:
How does it miscount...?? I have been using it for a while now and it seems to be pretty accurate...
[HD2 General] Bib_x:
I made some tests. I called someone, but after that the calltimes were the same as before the call.

Today calltimes is allways 0, and the month calltimes are now at 9 minutes, but i called out much more this month.

Settings are right, i checked this a few times.
[HD2 General] rat_2665:
I use CalltimeApp für Pocket PC V1.08. It's accurate so far. But you have to create your own plan in a xml-file.
[HD2 General] Bib_x:
Is there a today plugin for CalltimeApp too? I only want to use a app with todayplugin.
[HD2 General] rat_2665:
No, I don't think so. The last version of the program is from 2006.
[Touch CDMA Android Development] m0rph3us:
Hey guys, i trying to create my own eclair port, everything is working well, i have even solved the data problem on nike... I am trying to add the android market, does anyone know what files i need?

Thanks!
[Touch CDMA Android Development] myn:
Vending.apk ?
[Touch CDMA Android Development] m0rph3us:
I have the vending.apk in the app folder, but once booted android it is not in the menu with the other applications, same thing happens for example with the terminal.apk...
[Touch CDMA Android Development] myn:
Make sure you're using Market for 2.x.

You can also verify this by using Astro and attempt to install /system/app/Vending.apk.
[Touch CDMA Android Development] m0rph3us:
The problem was that i had not installed gtalk service and some other dependencies, now the market is installed but whe i try to start it it closes immediately, logcat gives auth errors, maybe i have to setup a google account in the setupwizard first... Thank you.
[Nexus One General] MasterTP:
Wow!:eek: I guess that the Nexus One being a "Google" branded phone won't get this update:

http://www.mobiletechworld.com/2010...ceive-divx-playback-support-in-future-update/
[Nexus One General] APrinceAmongMen:
Very interesting.

I'm sure with that release it will get ported to Nexus if it isn't rolled out by Google.

Good to hear. :)
[Nexus One General] SBS_:
If you need root to get that app (if/when it arrives) I would probably have to do it. Was going to keep my N1 stock, but if divx support arrives and it's good I just can't live with stock. Hopefully Coreplayer gets their release out before this so I don't have to do it :p

Converting files produces excellent results, but it takes way too much time to get good re-encodes (20ish minutes doing 2 passes on a 3.7GHz Quadcore).
[Nexus One General] Namuna:
The coreplayer looks very promising, but it's NOT free. This divx push would be.
[Nexus One General] hoss_n2:
every update can be ported to nexus one
[Nexus One General] galaxys:
We should be cool with a ported one :cool:
[Nexus One General] JHaste:
ive got 10 street cred that says nexus gets divx support before the bravo is released ;)
[Nexus One General] MasterTP:
HEeh I think that once the update is release it will be ported to the Nexus on in less than a few hours.
[Nexus One General] lbcoder:
DivX, like XVid, is simply H263. This is ***ALREADY SUPPORTED***.

Your only stumbling block may be in demuxing the container and recognizing the FOURCC identifier, so if you are having these problems, just remux it!!! You don't even need to transcode!
[Nexus One General] bradsh1:
I have seen this said too many times to count. If that is really the case, why has NO ONE released a divx player? xyflash doesn't count because it is totally broken and barely plays video.
[Nexus One General] sinbot:
yxflash actually works really well for me.
[Nexus One General] yostral:
That is wrong.

Xvid and DivX are implementations of MPEG-4 Part 2 Advanced Simple Profile (ASP).

H263 is a little part of it : it's only one of the possible quantization matrices.

MPEG-4 Part 2 is much bigger and more powerfull than just H263.

So being able to decode H263 doesn't mean being able to decode Xvid or DivX.
[Nexus One General] nenco:
For divx?? i dont see a divx since h264 exist
[Nexus One General] SBS_:
As I said, converting is a real PITA. Been a long time since I ripped my own DVDs to put it that way.
[Nexus One General] Ruben1123:
I'm a bit confused on this. What specific content uses this extension? DVDs...?
[Nexus One General] daveid:
And don't forget to mention the encoding options used for a computer vs. those for a mobile device. Typically the number of consecutive B-frames used can have a great impact upon compatibility for portable players (and even stand-alone DivX players).

There are a lot of variables that can keep people from playing their video collection from their PC on their phones (or other PMP's).
[Android Apps and Games] espy360:
I am looking for someone who wants to partner up and develop an app for my company. I can't offer any up front money but if you develop it and maintain it, you keep all profits from it being sold on the market. contact me at on Gmail - espinoza21
[myTouch 3G, Magic Android Development] kaiya215:
if i were to extract the radio image from the tmobile ota update from the DMD64 ota file,

and flash it to my mytouch3g that is currently on 1.33.2005 engineering with cyanogen recovery1.4 using adb... would it reboot fine? or which engineering spl should i update to after the radio flash using the cm-recovery or should it be amonRa's recovery in order for this to work right?...

any insight... just trying to keep the radio to the newest for tmobiles network speed....
[myTouch 3G, Magic Android Development] kbeezie:
What's your exact phone specs?

Can be found on the Fastboot screen (Back + Power)

For example the information you see in my signature.
[myTouch 3G, Magic Android Development] kaiya215:
sapphire pvt 32b end s-off h

hboot-1.33.2005 (sapp30000)

cpld-10

radio-2.22.19.26i

apr20,2009 15:30:43

ive updated to the radio i speak about b4 but only going about it without custom recovery only the standard and using the opal- updatefiles and renaming them to update each time

like

coc10 to drc92

then

drc92 to dmd64

and my signal and os were running excellent but not rooted

thats why i wonderd if i could go about it thisway using adb and fastboot and whatnot.
[myTouch 3G, Magic Android Development] 5[Strogino]:
I'm not sure about 1.33.2005, need to check what Hboot is inside DRC92-update, according info what DMD64 is update from DRC92.

I explored DMD64 update - there is no new Hboot - only radio, recovery and other files.

My two cents (i didn't say "yes" or "no")

p.s. found this, it seems like T-Mobile installed SPL 1.33.0007 into new regular MT3G (I bought mine in october 2009, SPL was 1.33.0006)

http://xdaforums.com/showthread.php?t=624835
[Touch CDMA Android Development] dommo15:
On the android my camera seems to have a sepia look to it when its running does anyone have a way around it or a fix to get it like winmo's camera
[Touch CDMA Android Development] PaceyWhitter:
It is being worked on, it has trouble in low light.

One thing you can do is hold VolDn when taking the picture, that increases the exposure time, you have to be very still though or these pictures will be blurry.
[Touch CDMA Android Development] cp0020:
When your in the camera press the volume button up or down to make it better
[Touch CDMA Android Development] cp0020:
Too late lol :/
[Windows Mobile Development and Hacking General] tsalta:
Hello guys im posting this Thread because i search almost everywhere and i can`t find the right place.

Befor i found in one website 3 Diferent cabs for Louder RIngtones depends how louder you wana ring your phone and yes this work in wm 6.5 and etc also

The problem is that i forgot from where i get them and i google it but i can`t find them anymore also i search over xda and again nothing..

I remember that some person from XDA wrote here link for them and this is how i find them befor a year.

If anyone know for what im talking about please let me know

Regards
[Windows Mobile Development and Hacking General] mitsi:
Try this, but back-up first.
[Windows Mobile Development and Hacking General] tsalta:
Thank you but its not this.

The cabs im looking for was Uploaded in one site and they was 3 Diferent Cabs one for Louder, for more Louder and for Maximum Louder this cabs are called something Ringtone Booster or Audio Booster i found them by incident when i search befor for Ringdelay FIX

I google them but i can`t find them i think that the site not appear on google.

The cab`s work perfect on WM 6.5 and they was made exactly for HTC devices.
[Windows Mobile Development and Hacking General] ZzFDKzZ:
Cool would be interested in this too.
[Windows Mobile Development and Hacking General] tsalta:
I dont find the Cabs but i found here on XDA one reg file that increase the ringtone sound and work cool on my Blackstone wm 6.5
[Windows Mobile Development and Hacking General] liamhere:
is this what you are looking for?

http://xdaforums.com/showthread.php?t=428170&highlight=loud+ringtone
[Touch Pro, Fuze General] Hard12kill:
Hi,

I am just curious about how to listen to these. A buddy sent me an iphone app to Radioreference.com. I can pull these up on my home PC, but unable to get my fuze to open them correctly. I can listen to my local Police, Fire and EMS as well as many others across the country.

My fuze wants to download them as a file but not open and play them.

Would appreciate any help.

Thanks:)
[Touch Pro, Fuze General] lukesan:
Try to search for wunderradio.

Fantastic little app that you can use to listen to radiostations from all over the world and also the scanners that you are looking for.