yashsingh1/xdaforums huggingface dataset:
[Wildfire Android Development] schiznik:
FYI, updated build went up last night.

The previous build didn’t actually fix anything so I've reverted all those commits & done a massive cleanup of the code.

BTW, could someone confirm whether alternative browsers/cameras/mp3 players work or not.

thanks :)
[Wildfire Android Development] -Howard-:
Ill try the new one soon :) and ill get back to you when i can
[Wildfire Android Development] :
Will flash this ROM this evening and report sometime today. You don't know how i am anticipating a pure AOSP GB ROM.
[Wildfire Android Development] :
The ROM itself is very good. Camera tho still doesn't work. Default music still doesn't play mp3's. The blue line in selection menus i think is a problem of the framework itself (how 'bout getting those LDPI resources from SDK or CM?). The launcher is laggy didn't try other launchers tho. Can be your "Lab Rat" if you need to test something ;)
[Wildfire Android Development] schiznik:
Cheers for the feedback :)

The camera/music problems are due in part to the CM device vendor I'm using at the moment, need to write my own ones. I did pull some ldpi images in from CM but they caused nasty force closes (a rom with no status bar isn't very usable!). Ill look into it further, but Im trying not to pull much in from CM don't want to make another CM clone :)
[Wildfire Android Development] xd.bx:
Hey thanks, I'm looking for a way to correct those issues for my AOSP build. Do you mind sharing which parts needed correction to get it working?
[Wildfire Android Development] schiznik:
They didn't work I'm afraid :(

Ill gladly share the fixes/commits if I manage to get them working.
[Wildfire Android Development] xd.bx:
The laggy screen is puzzling me. I don't think it's a problem with the kernel, because it's compiled from the same sources the one included in cm-7.0.3. Perhaps it's the touchscreen that is not responsive enough, because of the dpi?
[Wildfire Android Development] schiznik:
The kernel is identical to cm's, its the same image. I don't think it's the LCD density that's causing the lag, as that's just a setting in /system/build.prop - its related to the lack of gfx hardware in the wildfire, and the workarounds used in the framework, I've probably missed a patch
[Wildfire Android Development] xd.bx:
So here is arco's reponse to my PM, reposted here with his permission:

Did I mention arco68 is awesome? Because he is :)
[Wildfire Android Development] schiznik:
Nice :)

I know I've got some of those patches to surfaceflinger, but maybe not the libagl ones.

Afaik, the browser errors are due to the GPS not working, so hopefully gpsshim will sort that.
[Wildfire Android Development] xd.bx:
As for the browser there is only a small patch (see my other thread), you'll also want the ARMv6J Dalvik patches and the armv6 mk file. You can also switch back the ARCH to armv5te but performance will be lesser.

I have no idea right now on how to get video capture working. My best guess is that we're missing Omx patches from cyanogenmod to properly call the 2.2 camera libraries.
[Wildfire Android Development] schiznik:
Updated build is up. Biiig thanks to xdbg for the changes. Hopefully the blue lines are gone; next on my list is the GPS
[Wildfire Android Development] schiznik:
xdbg, you're an absolute legend; browser and camera are working in my latest build. Will push it up for download when I can

Big thanks to pepperoni, whatever your. xda username is, for testing builds for me.
[Wildfire Android Development] schiznik:
Aforementioned build is up - http://symphony.schiznik.net/devnull_buzz/

Getting closer to something I'd be happy to call beta!
[Wildfire Android Development] xd.bx:
Hi schiznik,

Just tested your build, here goes:

3G: working

Wi-Fi: working

Browser: working

Audio: working

Camera & Flash (still images): working

Camera (video): not working

Dialer: classic problem of 1 2 3 buttons hidden by bar above

GPS: not working, flooding the logcat with V/libgps ( 128): DeferredActionThread pthread_cond_wait returned

Home screen is still a bit sluggish when moving between them, did you include the gfx patches mentioned by arco68? Also, maybe add a bootanimation? It would help make the user wait through the first boot.
[Wildfire Android Development] xd.bx:
Good news, I think I got gps and screen gfx working thanks to the patches pointed out by arco68. Please have a look at patch-buzz.zip in the other thread.
[Wildfire Android Development] pepperon:
Some very positive message here, I like that.

Quite a few fixes made and looks like there are going to be more. That gfx patch is good news cause yeah I do agree xdbg that screens are a bit sluggish.

Whats the other thread xdbg to get that patch?

Thanks you two!
[Wildfire Android Development] Static-Noise:
Thanks, I'll try that radio hack now, but that app didn't work before.

As for the launcher comment, does that fix dialer?
[Wildfire Android Development] schiznik:
Thats not the problem - there are patches to the aosp launcher in the upstream Oxygen code thats incompatible with LDPI devices. This isnt a winzip rom, its built from source ;)
[Wildfire Android Development] Lesicnik1:
That much I know :)

I just didn't know that the problem was upstream ;)
[Wildfire Android Development] Static-Noise:
I think my coding skills won't be good enough to fix it! :)

I'd love to contribute, but I don't want to produce unusable rubbish!
[Wildfire Android Development] sdixit3:
@schiznik - Would it be working on rectifying/resizing the dailer, as this one issue that affect day to day operation of phone? Other issues are secondary and I can live with it.
[Wildfire Android Development] schiznik:
Like I said before, I've tried to fix the dialler, but without success :(

Have you tried any of the 3rd-party diallers to see if they work for you?
[Wildfire Android Development] sdixit3:
I use Touchpal, exdialer. However when in-call i get the default dailer screen with hidden lower row of the dialpad.

Please suggest a work around. I like Oxygen ROM and woud want to continue with it.
[Wildfire Android Development] auleu:
is there an eta for the final build of oxygen rom ?
[Wildfire Android Development] sdixit3:
Looking forward to Oxygen ICS.

However Oxygen 2.3.2 (GB 2.3.7) with all bugs sorted out would be a good final ROM.
[Wildfire Android Development] schiznik:
Installing GBLauncher from the market will get you the aosp launcher if you prefer that to zeam.

Unfortunately Ive fixed all the resizing issues that I can - pm me if you can help, and Ill show you where the source is.
[Wildfire Android Development] Compizfox:
Hi, I just installed this ROM because I want something faster than CM7.2 KANG, but I just keep getting the "Launcher force closed" errors.

EDIT: Nevermind, wiped and reinstalled it again, and selected Zeam. Now it's working, I don't need the stock launcher anyway (ADW ex ftw!) :P
[Wildfire Android Development] spudata:
Hi guys, if anyone is still interested in this rom, I've managed to tweak the dialler to display properly. It should also work with abtekks rom.

Just push the attached Phone.apk to system/app and reboot. Enjoy!
[Wildfire Android Development] auleu:
could someone please make a mirror because all are dead
[Wildfire Android Development] miniAndroidian:
Try this

http://download.schiznik.net/ROMS-buzz/oxygen/update-oxygen-2.3.2-Buzz-TEST-signed.zip :)
[Wildfire Android Development] auleu:
yeah my mistake, the dead link is from oxygen forum

anyone who still uses this, is the default launcher working for you ? mine force closes
[Wildfire Android Development] Rydlis:
Auleu: if you want I can upload the original GB launcher from Abtekks custom rom what works on Oxygen too :)
[Wildfire Android Development] auleu:
yeah i want that too but can i integrate it in the rom before flashing ? thx, still...oxygen is the fastest 2.3.7 out there
[Wildfire Android Development] schiznik:
Wow... no posts since July and now there's a whole bunch of them....

Nice to see people still appreciate the work that went into building this, thanks :)

You can replace the launcher.apk in my with the one mentioned above before flashing to get it "integrated".

Sent from my GT-I9100
[Wildfire Android Development] Rydlis:
Shiznik: We must thanks to you :)

Auleu: OK, I can send you Launcher.apk in sunday, now I have too slow internet connection :(
[Wildfire Android Development] auleu:
no problem

also is there an updated camera apk ?it looks kinda strange, also the phone apk from above works and its proper resised
[Wildfire Android Development] Rydlis:
I think no, but we can try camera.apk from other Oxygen/DevNull builds
[Wildfire Android Development] auleu:
so do you have time now to upload the launcher? but only if its the original one
[Wildfire Android Development] Rydlis:
here is it: Google Drive
[Wildfire Android Development] auleu:
thx, but is this the original ? or does it have any modifications ?
[Wildfire Android Development] Rydlis:
Its original, but recompile for ldpi devices, i think
[Wildfire Android Development] auleu:
but why is the default launcher within oxygen rom crashes ? only zeam works
[Wildfire Android Development] schiznik:
There were some changes in the upstream Oxygen code that were incompatible with ldpi devices, which I never had the time to look at properly.

Sent from my GT-I9100
[Wildfire Android Development] auleu:
so any known bugs remaining ?
[Wildfire Android Development] erdal67:
Link not working and still the fastest AOSP? Where can.i find screens

Verstuurd van mijn HTC Wildfire met Tapatalk
[Wildfire Android Development] schiznik:
I'll see if I can sort the download links & screenshots out tomorrow. Never know, I might even be able to do another build, don't know if Google have pushed any changes to the aosp code since the last time I built this.
[Wildfire Android Development] kyler084:
Any working link yet? ?
[Wildfire Android Development] Brute.Force:
Good news the download link of oxygen is up again.

Look for the link in second post.

All the credit goes to OP.
[Wildfire Android Development] Stone. Cold:
O.o this one is faster than oxygenv2 strange sticking with this ROM
[Wildfire Android Development] methuselah:
working link now working ??

the working link to this rom is not working anymore again
[Wildfire Android Development] methuselah:
download link is not working

well the download link to this is ROM is not working. i wrote this brefore. but nobody replied. i want to try this ROM It is fast. Can you upload the rom again ?:confused:
[Wildfire Android Development] methuselah:
The Download link is alive

[MENTION=2983097]Fusion10[/MENTION] has uploaded for all the users the download link of this beautiful rom. well anybody who want to download this beautiful and fast rom can download the very file from his skydrive. he don't have enough posts yet for creating any link in the forum so he is unable to post this in the threat....

well enjoy the Rom and the link ;):cowboy:

here is the link : https://skydrive.live.com/redir?resi...nt=file,.zip
[Wildfire Android Development] schiznik:
I've been trying to get my build environment back together for this - have been slightly hampered by the fact that my so-called backups were useless :/

remember people - TEST YOUR BACKUPS, otherwise you might as well not have them.

I've spun up my old VM's for this, resynced all my old repo's from github, but it is not building at present. I think the newer version of GCC on my server is causing issues.

Fingers crossed, I might be able to put up an updated build soon(ish)

Schiz...
[Wildfire Android Development] xd.bx:
Here is the link:

http://xdaforums.com/showthread.php?t=1162273

More specifically, the bundle of patches: http://xdaforums.com/attachment.php?attachmentid=654291
[Wildfire Android Development] schiznik:
Just pushed an updated build out.

The GPSshim is now included, so hopefully that should be working (have seen in the CM thread that a reflash of your radio *may* be needed to kick it back into life)

fingers crossed the lag is gone this time (im sure ive said that before)
[Wildfire Android Development] xd.bx:
Hi,

I'm sorry to say, screen is still sluggish. Could you check that you have the same gfx patches as me? see http://xdaforums.com/attachment.php?attachmentid=654291&d=1310607011
[Wildfire Android Development] schiznik:
Hmm. Pretty sure I do, will check it out later

Is GPS working now?
[Wildfire Android Development] schiznik:
this is going to be interesting... picking apart your .patch files & matching them up to the various commits they came from..

Thank god for "git blame path/to/file" ;)
[Wildfire Android Development] xd.bx:
Damn. I forgot to test GPS! No reason for it to not work though, let me know when you have an updated build available and I'll give it a try.
[Wildfire Android Development] schiznik:
Sorry for the delayed response, havent had any time to look at this recently.

Have added all of the patches to surfaceflinger/libagl, let me know how it goes please :)

Updated build at usual location
[Wildfire Android Development] xd.bx:
The screen lagginess problem is solved in this builed. The keyboard seems more responsive than in my build, did you patch anything? Browser is working fine also. I didn't test the GPS. Finally, video recording doesn't work - same problem as in my build. If you find a fix, let me know :)
[Wildfire Android Development] schiznik:
SWEET! glad we got the lagginess sorted finally :)

I don't think there any any patches to latinIME, will check later

Any chance you could grab gpsstatus from the market and make sure you can get a GPS fix please?
[Wildfire Android Development] :
Tried the LDPI version well only two words F'c kingdom. When i entered the setup menu the statusbar was there for like a few seconds then it got an fc then the setup fc and the launcher fc. Hope you fix it soon

Sent using telephatic powers.
[Wildfire Android Development] :
Sorry for double posting but just tried the not-ldpi everything works perfect! Just the keyboard is unresponssive ( when you press the button the popup is late bcuz you already are pressing a diffrent button and then everything messes up) just like in cm7 or any other GB rom.
[Wildfire Android Development] schiznik:
yeah that build doesnt work too well ;)

Hopefully the build in the main folder is ok, apart from the funky odd sized things, that arise from running an mdpi build on an ldpi device. Theres a few patches that CM have made to the apps to work around this that I need to pull in really.
[Wildfire Android Development] :
Oh and i forgot GPS works finds 6+ satelites wirlthout AGPS and 9+ with AGPS. ;)

I can smell that Oxygen coming :)

EDIT: Linpack shows not the greatest scores but thats not what makes rom fast. 3.418 on 528mhz :)
[Wildfire Android Development] Sonny96:
What is Oxygen ?
[Wildfire Android Development] 3xeno:
Pure AOSP ROM for the HTC Desire (And now to other phones)

http://xdaforums.com/showthread.php?t=971904
[Wildfire Android Development] Giac1:
wow looking really good :). finally a rom to replace openfire :). One thing ive noticed is some apps still need scaling. The clock app for example had half the digits cut off. also is the dpi on this rom 120?
[Wildfire Android Development] Sonny96:
thanks for the reply, hope that we'll get Oxygen on our Wildfire
[Wildfire Android Development] schiznik:
I know about the clock (and other apps too), need to pull in a few patches for them.

The LCD density is set at 120 again, iirc it was causing the blue lines in the earlier screenshots.
[Wildfire Android Development] Giac1:
Yeah it happens on sense based roms too. Keep up the amazing work duude :)
[Wildfire Android Development] dud3me:
Hope u can port oxygen too soon! :D
[Wildfire Android Development] schiznik:
Ill be making a start on it soon ...

I'd love to know if anyone's actually using devnull as their daily ROM?
[Wildfire Android Development] -Howard-:
Well im constantly switching between this and CM ;) its nice good work
[Wildfire Android Development] :
Used it but went back to cm7 bcuz of two only things: theme chooser and notification power widget.

I guess porting theme chooser into another GB rom is hard.

Sent using telephatic powers.
[Wildfire Android Development] kevin2516:
Oxygen has the theme chooser :D
[Wildfire Android Development] :
Oxygen but not this one ^^

EDIT: back to this rom again. Man this is smooth compared to cm.
[Wildfire Android Development] dud3me:
I'm gona stick with cm till you get oxygen working though this one works fine too
[Wildfire Android Development] xd.bx:
Hi schiznik,

Did you enable JIT in this ROM? (the dalvik patches) -- if not, could provide a bit of a boost.
[Wildfire Android Development] schiznik:
which patches did you mean? I've only got the two for armvj6 compilation
[Wildfire Android Development] xd.bx:
Cool. That's the ones :)
[Wildfire Android Development] schiznik:
test ldpi build updated - http://bit.ly/oDjQrs
[Wildfire Android Development] xd.bx:
There is a new problem, the launcher is not even showing. This seems to be related to a lack of proper OpenGL support (remember the Wildfire uses software rendering):

E/RenderScript( 204): GL Error, 0x500, from VertexArray::setupGL

E/libEGL ( 204): called unimplemented OpenGL ES API

E/RenderScript( 204): GL Error, 0x500, from VertexArray::setupGL

E/libEGL ( 204): called unimplemented OpenGL ES API

Lots of messages from GPS too. Did you apply the gpsshim patch?
[Wildfire Android Development] schiznik:
Build updated, in the ldpi folder again.

I've completely re-worked the ldpi overlay; maybe, just maybe, it doesnt FC anymore - It wasnt anything to do with the graphics, as the rest of the ROM was (relatively) functional. I was using the ldpi overlay from CM, however something in there was making it crash, I tested a build without those patches which was fine, so I've manually created my own overlay.

w.r.t the GPS, I didnt have a chance to look at a logcat when I was testing it, however I got a fix on a few satellites, so at least it looked to be working.

Oh, one more thing - I've pulled a commit for the msm7225 chip in for the camera, you never know, it might even work...
[Wildfire Android Development] rikee:
very nice... have a couple of suggestions

1. trackpad wakeup

2. on home screen row density should be a litlle bit bigger and rows should go down :)

3. in dialer app image, name and phone number should go a litlle bit up :)

otherwise perfect... will give a test few days ;)
[Wildfire Android Development] f0xy:
Missing my wildfire already :(
[Wildfire Android Development] :
Sorry but i don't think it's gonna happen it's a as close as possible aosp build.

Sent using telephatic powers.
[Wildfire Android Development] schiznik:
1, no

I know about 2

Ill see what I can do about 3
[Wildfire Android Development] schiznik:
Updated the build, its now the latest AOSP code - 2.3.5_r1 - As ever, any feedback most welcome :-)

Unfortunately I havent had a chance to look at the graphics fixes yet.

BTW, all the sources for this ROM are eventually going to be pushed up to the DevNull github site - https://github.com/devnull-project/
[Wildfire Android Development] Giac1:
using the latest update now, so far looks really good :). Although I did reboot randomly once. Also theres one thing ive noticed in just about every gingerbread based rom, the scrolling, especially in settings, is far laggier than any froyo or sense based rom. What could cause this? is it simply the fact that gingerbread is less optimized for low end hardware? And yes before you ask I did OC to over 700MHz
[Wildfire Android Development] schiznik:
Thanks for the feedback :-)

I've never tried a wildfire with anything other than stock (and DevNull of course), and never side by side, so I cant comment with any accuracy, however I always remember the stock ROM being horrendously slow.

Gingerbread isnt even remotely optimised for the hardware in this phone, in fact Google removed support for the CPU, which I've re-added from CM. Also, there is no support for ldpi devices in pure AOSP.

Does running it OC'd make much difference? every time I've flashed this ROM, its always seemed incredibly quick at stock speeds. As a test, I rebooted my Desire and the wildfire I've been testing on - somehow the Wildfire was first back to the lockscreen after pressing reboot on both at the same time.

What sort of cf-bench scores do you get with it overclocked? I've put a few images of it running at stock up here.
[Wildfire Android Development] Giac1:
Honestly overclocking in gingerbread makes almost zero impact on ui performance. scrolling feels just as sluggish at stock and at 768mhz. However games do respond well to overclocking. Emulating zelda with gameboid is alot faster than at stock. I have got a few setcpu benches I did on stock aosp openfire, we can compare those. Also the scrolling with that rom was much smoother. I've actually tried sense ui eclair and its even faster at scrolling and ui transitions. Its strange that the desire is slower at rebooting, perhaps its due to a lighter rom on the wildfire. I've got some cf-benchmarks I did at 768mhz, unfortunately the xda app wont let me upload them. Ill give you the overall scores instead

Native score 810

Java 379

Overall 551

Edit:

I found a bug with the camera, the icons for flash/exposure etc appear distorted.
[Wildfire Android Development] schiznik:
Cool, quite a bit faster then, still not anywhere near an SGS2 though ;)

I know about the camera icons (they all still work dont they?) - Its yet another issue caused by the gfx libraries / lack of hardware. Would it be possible to check CM7 to make sure they're ok there, and I'll see what patches they might have made to fix it. I expect when/if I can get the video recording working, they'll sort themselves out.
[Wildfire Android Development] Giac1:
yes they do indeed work, and yes cm7 doesn't have this bug.
[Wildfire Android Development] schiznik:
Thanks :)

I'll have a look and see what I can sort out
[Wildfire Android Development] widmo100:
Can you add more localizations?
[Wildfire Android Development] schiznik:
Hey, been busy with real life recently so haven't had a chance to work on this for a while. DevNull is english only, Oxygen will include all available locales.

If there is a specific locale you require, I might be able to build one for you.
[Wildfire Android Development] sdixit3:
I meant @710Mhz.

I am not sure, but felt JD4.2 more responsive compared to CM7?
[Wildfire Android Development] :
Of course it's more responsive than CM7. CM has become a lot less fluent in 2.3.

Any news on Oxygen, schiznik?

Sent using telephatic powers.
[Wildfire Android Development] -SmOgER:
I think i'am the only one getting gallery bug on every single rom (even stock) :D images are way too much sharpened, making photos look like s**t (any way i can edit-tune this?), fishbowl gallery works perfect.
[Wildfire Android Development] schiznik:
I've been waiting for the oxygen sources to be updated to 2.3.5, which they are now. Should be able to make a start over the next few days
[Wildfire Android Development] :
Yay :D

/randomcharz
[Wildfire Android Development] sdixit3:
@schiznik. Thats good news. Thx.
[Wildfire Android Development] :
Whats the difference between this and oxygen rom?

Sent from my Desire HD
[Wildfire Android Development] auleu:
when does a stable version will be release ?is this based on latest 1.0.3 ?
[Wildfire Android Development] schiznik:
Oxygen will include mods such as notification Widgets, DevNull is as close to aosp source as possible
[Wildfire Android Development] schiznik:
Originally it was based on that, now its the 1.1v that's available on other phones, although I need to integrate it with the main devnull sources

I guess I can give it a version number if that will make it "stable" - I don't have the phone so I haven't been able to give it an extended test.
[Wildfire Android Development] xd.bx:
Hey,

Feel free to PM me anytime you need to test a new version :)
[Wildfire Android Development] pepperon:
is it possible to get fm radio to work?

has anyone tried that yet?

ta
[Wildfire Android Development] schiznik:
Nope, because its not included. Will be in oxygen when I get round to starting it :)