yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] jubeh:
Honestly? I've had the basic version running on my phone since three-four days ago when eclair snapshot was linked, but I hadn't really looked into the issue with the nexus apps and just took it as a given that they wouldn't work on the Dream. It wasn't until a few hours before the release that I had started to look at the problem with those apps (about 48 hours ago), so I asked Simon Walker if I could have my files hosted at AndroidSPIN because I thought I'd be able to make a full working release, alas, I spoke too soon. Although I'm really close, there are two bugs that prevent full usage (the app drawer on Launcher2 and Gallery3D not working right), so I decided to release both versions, one that showed my current work, and another that would be usable day to day. When you asked me about the problem earlier, there wasn't any source, so I couldn't have looked at it and done something about it.

I'm aware of the problem with the nexus wallpaper. Actually, it's present on ALL wallpapers, but only most noticeable with the nexus one (I actually had to fix that one to get the nexus beams to line up right to the background). The problem is on Launcher2 and how it still thinks it's running on an 800x480 screen. I'm still looking through the source to try to find out how to fix it (I've already got the long-press force-close solved on the app drawer, so it's a little progress), but it's a lot of source and my java still rusty. I need more time.

I just read about problems with the MT3G (and even some problems with the Dream) about calls and other stuff. I'll have to look into it. All I can tell you guys is that I tested the rom on the hardware I specified on the OP as required. I run the rom on an ADP1 with Death SPL and the radio that's shared by the Dream/Sapphire.

About the Nexus boot animation? My personal build (the one where I do the debugging/testing) is actually about 80+ MB. It includes nexus boot, /tts folder in system so you don't have to download voice data, a ridiculous amount of ringtones and notification sounds, and both Launcher and Launcher2 and Gallery and Gallery3D on a single build. I had to cut some things out so that either build could also fit on a regular-sized SPL w/o having to use A2SD. For further releases I'm looking at a different way of doing things, maybe (like Cyanogen suggested) linking dalvik-cache to /cache. I want to keep support for both stock/death spl and a2sd/non-a2sd users, and that's why I felt I needed to release the build instead of just the apps. If you've followed my work (tiny hero?), I cater to the non-a2sd crowd.

how doesn't it work? Does it not download, or does it not start. Can I get a logcat?
[G1 Android Development] jubeh:
I don't do donations. People can call me stupid for not doing it, but I have my reservations, so I guess donate to somebody else :D. To me it just feels like begging, and it might be dumb, but I don't do it, plus my work pays pretty well.

I've yet to talk to cyanogen and ask how to get around that problem. He tweeted a while back ago that he had Gallery3D working fine, but there's damn near no way to contact him. Through PM, I imagine the PMs get lost in limbo because his box is full, through twitter, I've tried and it was a no, go. IRC on his wiki, I can never find him :D.

What I noticed is that the home-screen is actually still pretty responsive, just the background lags, but the screens still swipe as they should.

I'm aware of this problem and I'm looking at a fix. It is actually "THE" problem and once I fix it, all will be well and merry.

Are all these problems on MT3G? I kind of tried supporting it, but honestly, I had never done it before ( I don't like releasing for hardware I don't own/can test on). I guess I'll get together with somebody who's got it working on their roms (multi-device support) about what's needed. I had no problems on the Dream, and, I mean, this IS the Dream/G1/ADP1 forum...

I looked into the a2sd thing but couldn't get it to work the way I wanted it. Again, I'll have to work with somebody else to get it working.

It should work, but people are reporting problems, I'll have to look into it.
[G1 Android Development] jubeh:
I can do it right here, the fix was easy.

In order to get it running, just make an drawable-mdpi folder and copy all the stuff from drawable-hdpi over.

There'll be a problem, though, as the art is sized larger than what it should be. The solution is easy, for anything that's not a .9.png, just resize it to 66% of it's size, since the art for mdpi is 2/3s the size of hdpi art.

If fixed the launcher problem for adding home-screen icons from the app-drawer by changing the icons size to 48 and texture size to 64 in AllAppsView.java. There's also a resolution setting right after it of 800x480, but I found that modifying it makes no difference whatsoever.

I'm still looking at other possible fixes. I now know that the problem with the app-drawer is that the code for the rollo effect (that's what they call the top and bottom 3Dish effect) has the borders hard-coded for a certain size, and that's what taking up a lot of space in the app/drawer and moving the icons off of position.

The best solution I'm looking at now is just forgetting the app drawer altogether and instead using the app menu from the Home sample.

The last problem I see (again at the app drawer) is that the text cells are separate from the icon cells. I can't find any reference to that code, so I've yet not been able to resize them. I just wish it all were linked to a single parameter in an xml.

There's no secret, I've been posting it all over the thread. All I had to do was create MDPI renditions of the missing HDPI art build the apks. That was the only thing stopping the apps from running. I honestly had no interest on it, that's why I hadn't looked at it. But I had vacations this week, and I had a lot of free time.

I'll do. I took the Network fix from ctso's rom, but I just read from his thread that he got it from you.

Ok guys, here's the question. How do we work together. Should we form a project page or something?

Best I can think right now is have a page set-up working off of a specific source (either mine or cyanogen's, or maybe both), so that all who can work straight off the source can contribute. Then, with some sort of kitchen, the porters can get a compiled version of that source and make their roms with their mods.

I feel, if we really want to work together, we're going to have to find some way of centralizing all the work.

If we keep it out of gtalk, etc, and instead work off of a server, we minimize the drama/infighting and just contribute to what's up on the server. Anybody have better ideas? Anybody even want to try?
[G1 Android Development] xomikronx:
Is it just me? From the screen shot, you have the nexus live wallpaper working?

SWEET?
[G1 Android Development] jubeh:
Yup, working. I recomend the Basic build at this time.

If anybody wants to take a stab at fixing the Launcher2, here's what we're looking to fix:

http://android.git.kernel.org/?p=pl...b;hb=e8697d95fa5f9ba97a1e2bd15f4960d4e59d2213

Starting at line 760 down is the majority of the code handling the 3D effect of the app list.
[G1 Android Development] jubeh:
Also, before I set up a github, here's a simplifed version of my build system:

http://www.androidspin.com/downloads.php?dir=jubeh/Sources/&file=eclair.zip

Just toss .repo on your /eclair directory and repo sync. After it's done, remember to do:

git cherry-pick 18342a41ab72e2c21931afaaab6f1b9bdbedb9fa

at /external/webkit so that the build can complete, and then toss the rest of the package into your eclair repo.

After it's ready, just . build/envsetup and then lunch and select 13 (that should be my userdebug build). Then either make or make otapackage. Warning, otapackage won't apply without changing assert getprop to "dream" instead of "dream-open". Also, it will try to overwrite your recovery, so I suggest you also remove that from the package and the update-script.
[G1 Android Development] nicknowsky:
@jubeh

sorry if I made u repeat urself, i just wanted to know about myt3g support for sure, i appreciate ur hard work
[G1 Android Development] alfie196:
Is the "basic" link broken? Cant seem to download it.

Ne0
[G1 Android Development] Macrophage001:
Hey umm Im trying to try the rom but its stuck at the Android screen. I partitioned everything and wiped and repaired but its still at the android screen. is this normal?
[G1 Android Development] lapalways05:
E:Can't chown/mod /system/xbin/procmem

(No such file or directory)

E: Failure at line 79:

set_perm 0 0 06755 SYSTEM:xbin/procmem

Anyone know why it says this for me?

I Fully wiped. Right Radio, No danger SPL
[G1 Android Development] jubeh:
Can you pull a logcat?

Which version. I wonder if anybody can confirm this info, regular SPL is 69120 byte big, huh?

Do a adb shell df and post results here, maybe I made the big a little too big.
[G1 Android Development] lapalways05:
ugh i'd love to but all i do is download and flash roms. dunno how to do that

and I downloaded the basic one, i'm trying the raw bacon now

edit: Raw bacon has problems too.

E: Can't chown/mod /system/xbin/librank

(no such file..da..da..da.)

E:Failure at line 78:

set_perm 0 0 06755 SYSTEM:xbin/librank
[G1 Android Development] :
this is bad ass live wallpaper is pretty cool we need the damn drivers :) but yeah all in all pretty good job man!!
[G1 Android Development] ilaf0106:
What kind of swap mb do u recommend for ur basic rom

if i have a 1gb claas2 sd with 1.33.2005 and 26i
[G1 Android Development] jubeh:
With that, I suggest you don't create a swap space and let the default compcache work it instead.
[G1 Android Development] Ace42:
It doesnt have any probs if you dont have Haykuro SPL on dream then it wont install.
[G1 Android Development] iWannaBeAdored:
I am on King's ROM now but I might switch back to this for the widgets. Can I install the widgets on King's ROM?
[G1 Android Development] jroid:
that's cool bro i understand. what's important is that they're fixed now and working great.
[G1 Android Development] ilaf0106:
Do i do compache myself or its on by default just by

installing it
[G1 Android Development] futangclan:
What's different with the Music App? Seems the same to me.
[G1 Android Development] jubeh:
Well that's just odd... Why would you use Green after selecting a name?

j/k. If it's present in all builds, then i'm pretty sure it's a bug in the code. After all, the n1 doesn't have a green key, so that might be it. I'll look into it.
[G1 Android Development] Daneshm90:
Hey Jubeh, i dunno if u read my previous post. But using egl.conf and libGLES_qcom.so from sanpei's rom over on the sapphire threads, i got 3dgallery fully working, smooth as can be. Dunno if it helps considering i have a 32a magic and dreams are 32b, but u never know.

Nice rom btw
[G1 Android Development] iamarock:
Very nice ROM, I really love the live wallpaper feature. My only concern is about the languages included, i am spanish and really like to see more languages included like any other ROM.

Any chances to see this in next updates?

Many thanks
[G1 Android Development] vwrpm:
I have been using the basic rom all day today and I am very impressed. I haven't had any issues at all and the live wallpapers are fantastic. Jubeh, I appreciate your attention to detail with this rom and look forward to trying some bacon when its issues are resolved. This is definately going to continue to be my daily rom.
[G1 Android Development] guitargler:
Flashing Basic right now.. I don't intend to keep it on (Espresso is just too sexy) but there's no harm in giving a bit of feedback about a new rom (Especially since I can just make a bart backup whenever) :D

First impression: snappy flipping between screens, very nice. I had some trouble putting in my WEP key, but that's just because I've gotten so used to HTC's keyboard. Moving on, I found it neccesary to try the one thing I've wanted very much since it was first announced: the neural network live wallpaper. Aside from speed issues, it was excellent. Now all this Live Wallpaper stuff needs to be ported to Heroand my phone will be godly. :D

Anyway, excellent ROM. Works fantastically, and the music app has gotten nearly as good as HTC's.
[G1 Android Development] mrpandainc:
When I make phone calls, the other person cannot hear me, very weird

DANGER SPL (Although not needed)

Latest Radio

Mytouch3g
[G1 Android Development] boimarc89:
I used this ROM while i was in class and tried to call my job and it seems like the phone.apk has a bug. the remote end or the other person cannot hear me while on a call. Has anyone else had this problem
[G1 Android Development] mrpandainc:
Same thing here. Just posted above you. I thought I was tripping.
[G1 Android Development] jenarobfreaky:
Ipad

Check this out LOL, RT @JenaroBfreaky The new #apple #Ipad http://twitgoo.com/ckm1j #android
[G1 Android Development] jubeh:
I now know what the problem is with the mt3g. I'll re-upload the files with the fix and slimmed down a bit so they fit in regular spl, but later. I'm spending the day with my wife and daughter and they're pissed on how I had spent my vacation.

That's not a problem at all. I deliberately removed the languages because that's what I use. Only problem is that additional languages add size to the build, so I might have to remove some things.

I'll test doing that, I don't see how it would be kernel related.
[G1 Android Development] Daneshm90:
Oh wait, u must be looking at his kernel post. Look at the rom he posted. Here:

http://xdaforums.com/showthread.php?t=620782
[G1 Android Development] sinister4g63:
I ave to say, so far this is a fantastic rom! Everything works, no fc's, runs suprisingly smooth with the live wallpaper running. Kudos!
[G1 Android Development] bunu:
just make it required for the Danger SPL. You can do so much more and add more stuff. It can be smoother.
[G1 Android Development] bluenile:
Galaxy Live Wallpaper does not work in Basic Version

@jubeh just to let you know that the Galaxy Live Wallpaper does not work in Basic Version. There is no animation like we see in Nexus video, I just see the simple non-animated wallpaper. All other live wallpapers work as expected.
[G1 Android Development] jubeh:
I knew that. It doesn't work well with the Nexus Launcher either. I haven't even looked into why it doesn't do it, i bet it's just going to do it very slowly

That alienates the people not wanting to do the SPL jump. It's just easier for me to remove some things away for people with regular SPL and make a full one for people with death SPL.

I tried swapping the files and it won't work. I'm pretty sure it's related to the kernel or framework (or both), so I'd need to make it from source. I'll ask the guy how he did it.
[G1 Android Development] jubeh:
I checked this on the Dream, but I'm not getting any errors. Could you put a logcat? I'm pretty sure it's related to the key mappings.
[G1 Android Development] j0hnZ:
Using it on the MT3G, the rom is pretty awesome. Except for the whole mic not working, I guess there will be a fix to this soon though. I also am not sure if it is supposed to be like that but in the horizontal view the virtual keyboard on the middle sides of the keypad are transparent and show the message underneath.

I guess I'll flash back to cyanogen until it's fixed.
[G1 Android Development] jubeh:
I got clues to fixing the Launcher problems. I gotta dissect AOSP's yet undocumented renderscript library :(
[G1 Android Development] jubeh:
Alright. The nexus wallpaper tracking issue is fixed. I think I also fixed the mt3g sound issue already, and I'll work on adding the languages and trimming the size down a bit, then I'll put out a "Basic" v2 (fixes mt3g, adds all languages, and trims sizes) and a "Bacon v0.2" which fixes all of the above plus the Nexus wallpaper tracking. I'll focus on adding community-loved features in v3 and v0.3 like a2sd and support for init.sh scripts in /sdcard. Maybe after that (hopefully) Basic will stay at v3 and Bacon will move to v1 when I get the Laucher fixed (IF I get the launcher fixed, I'm looking at the code, and it's sad, but this thing is specifically written for a portrait-only 800x480 display).

I don't know wheter I'll eventually merge them, but I know that Basic will only go so far, and Bacon will go all the way to being "real" 2.1 for he Dream.
[G1 Android Development] jubeh:
I'm going to have to get the Launcher2 to stay fixed on Portrait mode, even with the keyboard open. Switching it to Landscape mode breaks many things (for one, it seems to lose input to switch screens/press icons after switching).
[G1 Android Development] futangclan:
Have you checked out the optimized Nexus Launcher.apk shafty made? It works great.
[G1 Android Development] jubeh:
affraid that's not what I'm looking for. that's just a nicely-themed Launcher, not the actual nexus-one launcher, ie, it won't support live wallpaper input, or have the quick screen switcher, or the new app drawer.

I might use those pngs and theme my launcher with them, though
[G1 Android Development] jubeh:
I've made a little progress. At least now I know EXACTLY what's wrong with the Launcher. As I mentioned before, I have already fixed the problem with the dragging/dropping of apps, I just resized the icon size to 48 and icon background to 64 in AllAppsView.java.

I wanted to test something, so I changed my phone to an hdpi screen (240 dpi), my theory was that the Launcher was hard-coded, so it was made specifically for that resolution/density. When I loaded the Launcher in hdpi and opened the app drawer, this is what I got.

This was a stock Launcher2 without the app drag/drop fix. The icons were lined up correctly, and dragging/dropping worked.

Now I know there's two problems. One, the app icon and app name is now handled on two different layers. The reason we're not getting a correct view is because the app-text layer is still set to hdpi, and I can't find a way to resize it down. The solution, I guess, would be to force the icons to stretch.

The other problem is, again, that the rollo areas, the 3Dish animations at top and bottom, are set to be an exact size, I think it's about 75 pixels high. These won't adjust to new screen sizes, so they end up covering the actual part where the app icons are being displayed, and since they're on a layer higher than the "Home" icon, you end up pressing the app icon instead of the "Home" icon.

I see two solutions to that problem, get rid of the rollo areas (ideal solution) or re-specify the touchable area where the apps reside so that they don't overlap with the rollo part. I had actually tried it before with limited sucess (ie, you were able to press the home button which had misteriously disapeard), but it still wasn't perfect/pretty.

I really wish somebody who had more coding experience would have a look at it.
[G1 Android Development] trystlore:
Fantastic Start

Love how both run on the mytouch cant wait for A2SD and Tether (a necessity for me). loved the beta cant wait for the N1 app tray to be fixed and the gallery. Keep up the good work. Will happily test new ones as they come out.:D
[G1 Android Development] jubeh:
getting there :D
[G1 Android Development] trystlore:
Woot. Just a thought, i noticed some of the Eclair roms use the settings driven wired tether. Would that be an .apk or set of that could be pushed into these? Just wondered as that is the main reason i have to keep switching back and forth between roms.
[G1 Android Development] FatBoyExtraordinaire:
Seems like this is coming along real nice. *Keeps fingers crossed for A2SD*
[G1 Android Development] sceptikart:
hello guys,

i know it's a silly question but i want to be sure that everything will work ok flashing this rom... so the question is if the phone has to be rooted before flashing this rom!

thanx in advance!
[G1 Android Development] trystlore:
Yes as with loading up the other roms root is a neccesity. along with SPL and custom recoverys i am sure. IMHO wanting to try roms with out root always seems to be a bit of "the cart before the horse". Not a flame but loading up roms (even some of the base ones) some times requires more then just "click this" as well as hardware adjustments or scripting to get it fluid on your hardware. Failure on something obvious "such as updated radio" can lead to bricks as many threads will attest. I won't assume, you don't realize this, only that maybe general research into the rom development and the standard "root is required" answer that shows up at least once in almost every rom will keep you from any possable flames in the future. that said, root.. partition if mentioned in the reqs and just follow the devs advice and you will do fabulous.:D
[G1 Android Development] jubeh:
The code for this thing is horrendous. Lazy coding at it's worst. I've narrowed down to two files, I'm now SURE that's all I need. /src/com/android/launcher2/AllAppsView.java and /res/raw/rollo3.c (most of the work is in rollo3.c).

I've gotten all the icons to aling up on a grid sucessfully, but I'm having an issue when, on the bottom rows, clicking on any of the icons in the last row will register on the row above it. Also, as of yet, the icon to go back home is inaccessible. Really, horrible coding, I'm going to have to rewrite that whole function (drawFrontGrid) and even then, it will just be a horrendous thing to do... I'll just force it to work on a 480x320 screen and completely ignore 800x400 screens...

---edit---

but that'll be another day. I've had had enough android for a month. Now I'll just wait to get my US-Spec HD2 :D
[G1 Android Development] Daneshm90:
Yo jubeh,u try asking shafty ? he seems to be really experienced in coding, just look at his signature with ALL those languages :).
[G1 Android Development] galize:
Basic runs perfectly, RawBeacon too but launcher is really awfull. I install back basic.

Thx a lot, i hope to follow new developpement in the future.
[G1 Android Development] jubeh:
and as fast as it came, it's over

I'm discontinuing work on this progress while awaiting for a response from google on solving all the Launcher's problems, 3D acceleration, and, if possible, fixes for at least being able to play back video.

I'm also focusing now more on my HTC HD2 :D. 1 GB storage, 576 MB RAM, who needs an N1 :D.
[G1 Android Development] JAguirre1231:
I need an N1
[G1 Android Development] FatBoyExtraordinaire:
Sad to hear that, but from what i read, it's pretty good now so at least the people have that.
[G1 Android Development] jubeh:
I'll make a couple fixes issues for both on the issues when running on MT3G. Rather than make another release, I'll just patch those and replace the download links.

Again, soon as I get the Launcher problem fixed, Gallery 3D working, a better understanding of a2sd (is that the only missing feature keeping some people away from these roms?), and a better understanding of building most of what I can from source rather than copying files and doing post-editing on a build (ie, get the build system to configure the update-script the way I want it, or not having to crack open the boot image to set ro.secure to 0), then I'll release another build.

I'm learning as I go, but it gets tiring.
[G1 Android Development] KDerrida:
I'm having this exact problem. I'm running Cyanogen SPL, with the correct radio. What's wrong and how do I fix it?
[G1 Android Development] klon000:
Looks like you don't have the Danger/Haykuro SPL installed. And maybe it's necessary. I had the same error while trying to install diferrent roms on standard SPL.
[G1 Android Development] KDerrida:
Oh, man, the first post didn't say that I need Haykuro. Is it easy to update my SPL from the SPL?

EDIT: Oh, yeah, google says it is. Sorry.

Other edit: Yeah, I just installed this build and it's badass. Thanks for the help!