yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] :
Perfect Rom only problems I have is text but that works great once I used the regular text app I miss chomp though and the other problem is sometimes my screen isn't responvie any help
[G1 Android Development] grennis:
Agreed

10 chars
[G1 Android Development] kboater:
just wondering, 2.2 should run much better on our MT3G and G1 then 2.1 right? google has said 2.2 is much lighter then 2.1 which should be much better for performance on our older devices correct?

the official 2.2 (released by google) has Jit enabled right? are we thinking that once it is working on ours it will speed it up much more then the 2.1's out?

thanks
[G1 Android Development] crr127:
technically speaking the american version of the mt3g is just a 32b... so it has the same amount of memory as the g1. 32a is the one that has 288meg of ram i believe. either way yes with jit enabled. even without it enabled it should be much quicker on the older devices. plus it is ment to boot without any modding for alot of devices which is gonna make deving for this much easier.
[G1 Android Development] Brantyr:
JIT doesn't appear to be on by default in this ROM - any idea how to enable it?
[G1 Android Development] Lloir:
AWESOME!! EVERYTHING is working (except the gps) dont really need that anyway \o/ \o/ \o/ my new default rom :D

also the APPS2D works :D :D question does anyone know if the new inbuilt APPS2D uses ext partitions or not needed anymore? if not then more normal SDcard space for me
[G1 Android Development] psychoace:
I'm running ADW Launcher and yeah wow this phone is solid, fast and fit. My behold 2 seems to run neck and neck with my G1 now. I'm guessing this rom doesn't even have an OC'd cpu or anything either so big ups. Awesome rom.
[G1 Android Development] DBISGOD:
anyone else having problems with it loosing the sd card and then needing to reformat?
[G1 Android Development] Ohgami_Ichiro:
Well that was Google's Hang up. They wanted a NON EXT/SWAP Apps2SD solution. Give it a shot. I can't wait for CM6 so Jubeh "might" finish this one off. :D

But DANG this thing is fast on a G1. There's still some incompatabilities with some market apps but that's cause they probably haven't been updated.
[G1 Android Development] g1junky:
I Love the speed of this !!!! :eek:

i cant wait to see what cyanogen does with this
[G1 Android Development] jubeh:
Here's the thing. My rom is what it is and nothing more.

I'm seeing a lot of people expecting hack-a2sd to work, others come in with reports that X-program, which was made with the assumption that either root or busybox or other thing is there, then start painting it like there's something wrong.

I like my roms being the least common denominator, I'll repeat it, as close to ADP builds as possible. That means no SU-root (though I added it in because I know what it does and how it does it), though you can still root through adb root. It means no a2sd hack. If official a2sd is enabled from AOSP, or if I can enable it, then I will. As far as JIT is concerned, I'm still looking on how to enable it on the dvm and I think I have a hint now, but I can't test. I don't like "kanging", so if somebody says "oh, you can pull x file from here or y file from there" I might do it, but reluctantly, and even after I do, I'll try to figure out what it is that I did, how it works, and how I can do it myself rather than just say "Oh, that's a fix" and leave it at that. That's why I'm taking my sweet old time. I don't know all of AOSP (I doubt anybody does), and I don't program for a living, all I have on my favor is ~3 years of combined high-school/college computer science classes plus my own hobbyist findings.

I don't take requests, so you'll notice I seem to ignore them. I read ALL posts on the threads I make, and if I get an idea I like, then I'll make the fix and post on first post. I won't make a Magic patch because I've never had one, so I can't test. I'm building this one going blind as it is... I can do it because I know the Dream/Sapphire devices well enough where I can do most of the work without testing, and I won't post a patch that I can't test and guarantee that will work.

Those of us who've done free computer work for other people know exactly what I'm talking about, soon as you touch somebody else's computers to fix something, if something else breaks in the future, they'll assume it was something you did.

I'm not letting that happen with this. If I like your suggestion, then you'll see it implemented eventually, if not, then don't think I ignored your post, I read it and humbly (and silently) declined.

I'll say it once more and for the last time: This rom is meant to be as close to an ADP build as possible. If you don't know what that means, go to developer.htc.com and download the official build for ADP devices. It's very bare, but stable and it has root for those who know how to use it. It's as it was on my hero build, I'm trying to make the build work on the device, not the other way around.

This might also be my last Dream build. With my Dream eating fully-charged batteries in 10 minutes (that's why my Dream "died", I've bought 2 new batteries after the first one died and it seems to be killing batteries), I'm moving my efforts now to Android on the HD2 now that the kernel is finished and the touchscreen driver is almost done. I'll just be making the type of build I make, but for the Leo.
[G1 Android Development] g1junky:
This rom was fun to try out :) but i'm gonna go back to Cyan 508
[G1 Android Development] draven806:
Well thank you for all of your hard work, and I apologize for all of the inconsiderate people who don't realize that you don't have to do any of this, only that you do it as a favor for us. Again thank you for all of your hard work. As soon as I am working again, I will be donating tip you and any other dev whose rom I have enjoyed. Thanks again. And please hold me to my word.
[G1 Android Development] Ohgami_Ichiro:
My thoughts exactly. I was just gonna flash it on and see what it was like but with it being so stable and speedy and no bloat I had to keep using it. I love IT!
[G1 Android Development] Z҉A҉L҉G҉O̚̕̚:
I agree 100%. Some people seem to have an unwarranted sense of self importance and completely disregard the fact that the ROM makers are not obligated to do jack for us.

I only wish I had the money to donate to the ROM devs for making my phone more functional.
[G1 Android Development] wrsg:
thanks for your work on this rom, i believe going 'back to basics' is a good thing.
[G1 Android Development] anomalous3:
no phone is because it lacks libhtc_ril.so and possible a few other things. Kanging from CM 5.0.8 and giving it a whirl. Using pershoot's OC kernel (the N1 version works with froyo so I'm betting ours might too)
[G1 Android Development] jubeh:
hmm, figures

I'll see what the new way to build with htc binaries is
[G1 Android Development] jon6206:
good luck! let us know how it works please. I'm considering making this my project for the night either that or I'm gonna watch the entire last season of Lost
[G1 Android Development] dego19:
adobe flash 10.1 is working??

wifi is broken but with 3g you can watch it ...

??
[G1 Android Development] crunkcory:
I was gonna say, I flashed it and data doesn't work.
[G1 Android Development] kernelzilla:
Was just about to post that, nice one.
[G1 Android Development] innerlogic:
Again, Wifi does work if you push the firmware (Fw1251r1c.bin) to /etc/wifi.

As for flash 10.1, the chance of it working (especially without 3D hardware support) is slim to none. Really, that's the last thing that should be on your wish list at the moment (Full sound support might be a good thing to ask for though :cool:)
[G1 Android Development] jacsonmoore3:
I'll try it but still waiting on the CM6..
[G1 Android Development] jubeh:
I'll try a build kanging hardware files from CM 5.0.8
[G1 Android Development] OtVang:
Trying but Many troubles :( wifi, camera...
[G1 Android Development] sidroc:
Audio just worked for me.
[G1 Android Development] innerlogic:
Then your G1 must be extremely special, because audio (beyond calls) did not work for me as well.

jubeh: You may want to update your OP and post what hardware does and does not work at the moment.
[G1 Android Development] jubeh:
Building otapackage now, there's a hardware file that I couldn't find on cyanogenmod, liblvmxipc.so, so we'll have to do without it, from the name I can't tell what it is, maybe a dvm file
[G1 Android Development] geokuttan:
is it possible to extract the necessary system files from Nexus 1 ?? or is it too different?
[G1 Android Development] jubeh:
I don't know because I can't test
[G1 Android Development] kernelzilla:
Flash 10 wont work until we get a working Market, the 2.1 version doesn't work...

I guess we're gonna have to wait for the mytouch3g OTA to get msm7k compatible froyo gapps...
[G1 Android Development] innerlogic:
It's in CR Froyo Test16 (/system/lib/liblvmxipc.so), but I'm pretty sure just dumping it in probably won't work. May want to try it though.

We have posted in the thread what does/does not work

Works:

Phone

Wifi

Bluetooth

Broken:

3D

Camera

Gapps

Sound (Besides phone)

(Everything else you probably care about)

I might have missed a few things, if anyone else would care to add please do so.

The two are compiled with different processers in mind, you can't really mix and match them together.
[G1 Android Development] grennis:
I dont understand why since the CR and kingklik Froyos both have gapps
[G1 Android Development] Sik-1:
sound works but is extremely low
[G1 Android Development] jubeh:
It should work, I'll test after this build is up.
[G1 Android Development] robuser007:
http://forum.frandroid.com/forum/viewtopic.php?id=12153
[G1 Android Development] Lloir:
Seems to be a bug where apps disappear from app menu after a reboot (when installed to SDCARD) but still show as installed

JUST installed Launcher2.apk and it seems to have fixed it.
[G1 Android Development] robuser007:
I posted this already.
[G1 Android Development] Lloir:
ahh sorry didnt see it my bad :rolleyes:
[G1 Android Development] :
No boot

Hi guys,

Really eager to try this out, but i can't seem to make it boot :(

Downloaded the .zip from the OP, wiped, flashed, G1 boot screen then black(backlight is on) screen. I've left it for 20min+ but nothing. I've read that the bootscreen doesn't work on G1, tried to push another one but that didn't work either. Am i just being impatient?

Any ideas?

Cheers

Hardware: UK Voda G1 (Dream) 32b

SPL: Stock

Radio: 2.22.23.02
[G1 Android Development] lbcoder:
What does your logcat say?
[G1 Android Development] :
I'm at work so cant look :/ i'll have to have a look when i get home

cheers
[G1 Android Development] acejoker25000:
im going to assume its because you have the stock spl and not the danger spl
[G1 Android Development] lbcoder:
That statement is ABSURD.

DeathSPL solves NOTHING.

Assumptions PROVE nothing.

The way to solve a problem is to look at what things *ACTUALLY DO*, not make wild and unfounded guesses.

Also, deathSPL is OBSOLETE.
[G1 Android Development] jubeh:
A clearer version of this would be: There's no way that's the culprit since this rom falls a good 10 MB short of the size of regular SPL. Death SPL is not necessary.
[G1 Android Development] mercenaryhmster:
dude, chill out. to bru192, it sounds like the zip is corrupted, so try re-downloading the file.
[G1 Android Development] lolmensch:
friendly as always...
[G1 Android Development] Babyface1249:
You know lbcoder, it really makes your point a whole lot stronger when you put words in caps or wrap them in asterisks...not. The true absurdity lies in the fact that your post is more absurd than the post you criticized. Nice job.
[G1 Android Development] wrsg:
where you say this might be your last dream build, do you mean you won't be progressing further on this rom? if so, would you possibly be releasing your efforts so far on some open source hosting site?
[G1 Android Development] olearyp:
"Straight AOSP" == http://android.git.kernel.org/
[G1 Android Development] Jigga0o7:
I'm not sure if this counts for anything but in SetCPU the "BogoMIPS" is at 527.15 when the processor is at 528mhz on the default kernel and it's at 460 when the processor is at 576mhz after flashing Pershoot's DS kernel.
[G1 Android Development] olearyp:
It doesn't count for anything. There are actual benchmarks available (I believe Linpack is the most commonly used around here) which will help you compare.
[G1 Android Development] :
back... re-downloaded, checked md5sum, flashed again but still the same... when i try to logcat after first boot, adb doesnt see my phone :/ (can see it in recovery)

anymore ideas?

thanks
[G1 Android Development] kewlguru:
Feedback after using it for a week

After 5 days, I went back to CM5.0.8 (superBAD theme).

Not that I wanted to (I loved the small small nifty things that changed), but was forced to becos of the horrible battery life I faced.

From full charge to empty was just in 5-6hrs.

Touch sensitivity was a bit hard for me. Wouldnt respond easily!

I know this is BETA, but lot of good things in FROYO.

The things I loved the best

1. Full Exchange calendar sync mainly. Big plus from my side.

2. Market was a gem. Real quick. Coming back to CM 5, feels a let down.

3. Connecting to Wifi was real quick, 2-3 sec

4. Browser seemed faster, but cant really tell.

Speed was hot and cold for me

Let me know if any else liked other things on FROYO

/Ash
[G1 Android Development] akivlin:
I didn't try lbcoder's new partition method yet (to emulate DangerSPL partitions) so you could try it but if not you do need DangerSPL installed because the older SPLs result in a black screen. I tested 0.95.0000, 0.95.3000, 10.95.3000 and finally it worked with 1.33.2005. If you do go for DangerSPL, make sure you have a 2.x radio installed and verified on the fastboot screen before installing DangerSPL, and you should be fine.

I'm kinda new to all this but I would think froyo should work on the older SPLs. Anyone know why it doesn't???

Also I built the froyo sources myself with only minor changes to achieve a successful build and my build resulted in the same black screen when using the older SPLs.
[G1 Android Development] draven806:
Yea, I went back to cm 5.0.8 because I needed my camera, and got lazy so I left it for a couple of days, and even with oc to 576 khz and cc, and swap, it was just no comparison to this. Yea it sucks not to have a working camera, or gps, or gallery, and whatever other small little things don't work yet, but imho, the pros far outweigh the cons. So needles to say, I'm back and using this as a daily driver.
[G1 Android Development] jubeh:
NCommander's camera no longer works on Froyo, that's why I'm taking a while with this, trying to get at least that corrected. Everything else is done and working. Well, that and enabling JIT at dvm, but that's trivial once I am able to find where the heck I bookmarked the page that says how to do it....
[G1 Android Development] dferreira:
jubeh, just follow my "Compile AOSP" link on my signature, on the first post you'll find how to activate it. I have it running already, only thing missing really is the camera and GPS.

How did you fix the GPS? Also, can you share the steps to get NCommander's code into AOSP?
[G1 Android Development] jubeh:
Oh, right, it was your post where I saw how to enable Jit, obrigado.

AOSP build is missing pulling gps.conf from 1.6 build. The new AOSP build system is too convoluted, so I made a new manifest to pull /vendor from eclair and removed /device.

Ncommander's camera files, I had them already downloaded as raw files, but you can change your manifest to use his gitorious msm7k project instead, though you'll have to correct a bunch of things (froyo adds libstagefrighthw and other libs), so it's easier to just add the project manually

---edit----

forgot, here's the http project page: http://gitorious.org/eclair-camera-drivers, just pull the raw libcamera2, edit the msm7k Android.mk to add it to the build, and with the old vendor, it should build the lib. It's failing for me at build time, though. Maybe i'm using the wrong gcc version.
[G1 Android Development] dferreira:
Thanks jubeh, I'll try that later tonight.
[G1 Android Development] feronovak:
Sometimes I ask myself why not to do it on my own :) Because I am c# developer and dont know sh*t about linux. I wish I knew and could help with development, this is awesome work and really takes old m32b to another level.

Thanks jubeh and all other developers for your time and efforts. You deserve much more than just my thanks.

Fero
[G1 Android Development] he3:
Forgive me, but I thought you were dropping this project. Im actually happy if you aren't!

I like non-CM, no real reason.

Ive been running this since last Friday and its flawless(beta). So are you going to up the changes when your done?
[G1 Android Development] jubeh:
To quote Carmack, "when it's done". I'll release when I'm happy with it.
[G1 Android Development] he3:
Excelent! Thats the same MS reply too.
[G1 Android Development] Firerat:
from kings thread, thought you guys would be interested
[G1 Android Development] jubeh:
Oh, well.

To be fair. I've always said that I put out builds so that other people can work on them, etc.

I, for example, dislike a2sd hack, other people like it, so if they use my builds and add the hack, then that serves a different part of the populace.

I do this for the learning, but this time around I guess I got a little excited and released something I wasn't able to test.

My new ADP1 should arrive next week, so I can keep working on it.

My real goal, though, is to figure out how to fix all these damn problems AOSP keeps tossing on us myself, or at least use somebody's else's source fixes and not just blobs, that way I can read what's going on and learn moar!
[G1 Android Development] he3:
I'm glad you released it. Running like butter since last Friday. Sans a couple things, but overall worth it IMHO. Thanks again.
[G1 Android Development] grennis:
Statements like this are why I am also a C# developer who knows nothing about linux
[G1 Android Development] thefan0820:
Sorry, I tried reading through the entire thread, but got kind of lost around page 20 and picked backed up around 37. So sorry if this has been answered before. Are you able to connect to wifi to sign in to your google account? Because I'm running pre-paid T-Mobile (USA) which has no data, in case you're wondering.
[G1 Android Development] jubeh:
You should be able to. Heck, you don't even have to!, you can skip the setup. Anyway, yeah, wifi works.
[G1 Android Development] thefan0820:
Okay, thanks. I know that in old default G1 builds they'd make you sign in, and you'd have to do some tricks with ADB to get it to load to the Wifi screen so you could connect the phone to your google account, so I was concerned that since it was almost straight from AOSP, it would be the same way. Thanks! I'll see how it goes. Hopefully I'll be enjoying some tasty froyo tonight!
[G1 Android Development] jubeh:
Actually, straight from AOSP there's no signing required. The provision package sets up your phone without having to sign in to anything. The Google Setup Wizard is pretty much the same provision package with an UI that requires you (depending on configuration) to set up your google account and other settings before provisioning your phone.

Actually, way back when I thought I could do it I was going to make a setup wizard for my own roms to set up things such as oc, compcache/linux swap, etc at boot, then it would call setup wizard, and then finish the provisioning. Ah, to be noob and stupid....
[G1 Android Development] studjuice:
Could someone take the spareparts from the alpha release of CM6 for nexus, and convert it into a D/S version? I really want to get spare parts into this, so i can change font colors.

Or point me in the direction of doing it myself if that's faster?
[G1 Android Development] jamesd86:
i know the adb command was given earlier in the thread but are there terminal commands that would allow the installation of programs to sd?
[G1 Android Development] jubeh:
There you go. Freshly built, just for you.
[G1 Android Development] studjuice:
Whoa, no rush jubeh... take it easy man

remind me to never face duel you in a quick draw

EDIT: No good, still won't install correctly. adb gives "[INSTALL_FAILED_OLDER_SDK]" so it still won't work with 2.2 :(
[G1 Android Development] jubeh:
weird, this is straight out of the build system i have setup.

have you tried adb push to /data/app instead?
[G1 Android Development] Firerat:
no idea if this will work

its from Cyanogen's github froyo branch, target dream
[G1 Android Development] Ace42:
I uploaded some missing apps:

Dev tools

term

Lwp(Starts then closes:( )Tried star lwp

spare parts

carhome

Custom locale

Jubeh is it possible to fix LWP support currently?
[G1 Android Development] Firerat:
Ace, have you got the 114 data partition now?
[G1 Android Development] studjuice:
well i ended up getting it to work, but the spare parts DOESN'T have the settings for changing the text colors so that was semi-pointless.

It didn't work using "adb install" which confused me (didn't think of trying to just push) so i took open your spareparts you gave me and the nexus one and compared them to see what was different. when i saw it was just a number here and there in the AndroidManifest.xml i went and changed a spareparts.apk from the latest superbad build to those numbers in the nexus ones, added in a missing line so that it would show the correct icon and name in the launcher and that made a correct working awesome SpareParts.apk for froyo!

and since i used apk manager i tried using the compile/sign/install all in one step option to install it and it worked so i never tried another option with the new good apk

View attachment com.android.spare_parts-2.apk
[G1 Android Development] XxKOLOHExX:
Wouldn't you need to edit service.jar to take advantage of that ??
[G1 Android Development] studjuice:
uhhh, maybe? I wouldn't know... this is kinda my first day messing with rom's. lot's of guess and check...

I'll go check if it works i guess :P

EDIT: Tried adding battery %. didn't add it after reboot. so nope doesn't work. :(
[G1 Android Development] XxKOLOHExX:
LOL alright :D let me know what you find :D
[G1 Android Development] Ace42:
You might not be able to use the spare parts from another rom to edit such features as those...
[G1 Android Development] studjuice:
Yep you were right. I didn't get what i wanted accomplished :( but i learned valuable stuff doing it :)
[G1 Android Development] Lloir:
there is another Froyo rom out btw which has spare parts and live wallpapers...they both work on this rom if you take the APK's out and install onto this Froyo.
[G1 Android Development] lefeudedieu:
Hello

Froyo 32B here with wifi, bluetooth, sound, apps2sd (with command) ok

Possibility oc 576mhz 4.1 Linpack

querty here :

http://www.androidinforum.fr/htc-dream-android/

and thank you to jubeh giant_rider for their work

edit ;sorry for gps no work on 32B
[G1 Android Development] jubeh:
LWP won't work without some modification. Basically, from having a quick look at it, libRS isn't loaded unless you build for msm8k. I haven't built with libRS yet, so I don't know if it'll work.

There were some changes that made libRS require msm8k, so maybe building the initial versions (the ones from when I first built eclair and got LWP working) or retrofitting them to froyo could work.

About the spare parts thing, basically, what cyanogen did was add some code to change properties, settings, etc, but, like it was mentioned some parts were tied to the framework.

If you want those parts then you're basically wanting to run CM. Remember, I'm making this to be as close to ADP builds as possible. This is a build for people who just want to use their phone and have root rather than spend loads of time modifying and tweaking.

The issue with apps not showing up at market has to do with the build fingerprint. Anybody have any idea which one gives you the most apps? I'm thinking using the 2.1 hero atm since that's the most recent hvga device.
[G1 Android Development] wrsg:
are you going to be releasing anything on a public source repo e.g. github?