yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] kyralak:
I think you should follow your own advice, stay on topic
[G1 Android Development] cronin4392:
Tested the ROM out for a bit and its pretty nice. I noticed that my home button didnt work, which was weird.
[G1 Android Development] bootleg16:
tried this out just for fun.

pretty cool to see cyan working on other things other than cupcake.

love the power management widget.

=D
[G1 Android Development] drpfenderson:
Thanks! Sad to see they didn't awesomize it.
[G1 Android Development] indiekid97:
I read an interview with a google dev (JBQ maybe?) asking about the version numbers, and in a rather ironic fashion he stated that there are no definite build numbers until the release is rolled out; rather, the developers work by pastry and the PR guy assigns the numbers.
[G1 Android Development] PhaseBurn:
Quite true. There are things in Cupcake that were not included in the 1.5 release. There's things in Google's internal Donut build that I've played with that I don't see in Cyanogen's build - JBQ is migrating code from the internal tree to the external tree but he's stated he's far from finished.

Google has an internal Donut build that is working with the RIL on the Dream platform - I posted a number of screen shots of it last month when I had access to a phone running it, and it was actually very smooth, very fast, very complete. Gestures worked, IPSec/L2TP VPNs worked, etc... As Donut code gets transitioned from the internal to external repos, our open source builds will get better and better, mainly thanks to people like Cyanogen. Android's next release version (2.0, 1.6, 1.8, whatever it's called) will be a "snapshot" of Donut much like 1.5 was a "snapshot" of Cupcake with certain features enabled that were finished and deemed ready, and other features that weren't not making it into 1.5. Cupcake then became Donut after a few other things went into it, etc.
[G1 Android Development] fearlless:
i'll wait til he's done. he always brings good stuff :D
[G1 Android Development] l3wish:
android showing some love to evdo

Sprint -verizon are sure getting android soon. Look at the evdo icons from the donut build
[G1 Android Development] cyanogen:
The RIL and sensor compatibility is really all that needs fixed for people to actually run this code in its current state.
[G1 Android Development] superg05:
thank jon jon
[G1 Android Development] bigplrbear:
Thank you VERY much for this build, but I think I'll hold off until the networking issues are fixed, as I've only got one G1 and it's my main phone xD
[G1 Android Development] PhaseBurn:
Oh, I know that, and you've done an amazing job don't get me wrong. Didn't mean to imply you hadn't. What I am saying, however, is that there's things that still have yet to be transitioned besides the RIL and sensor code before your build of Donut come close to the Google internal builds.

I posted this pic a month ago today: Donut about screen and as you can see according to the icons at the top, WiFi, bluetooth, and the radio are all 3 working just fine. There's other things that are also in the internal builds I haven't seen in yours yet, because the code isn't there for you to compile. I'm sure that JBQ will get around to porting more of Donut next week, but it's a "work in progress" to sync the internal and external trees.
[G1 Android Development] b0ricuaguerrero:
Soggy indeed :( Hopefully someone can take a crack at this and make at least wifi work. Other than that. CM3.6.8.1 nandroid back up FTW
[G1 Android Development] nolageek:
Curious... anyone play with multitouch in this? (Is it in gallery etc..) Just getting home and it's 3:41 - otherwise I'd flash it myself to check.
[G1 Android Development] b0ricuaguerrero:
Double post sorry
[G1 Android Development] b0ricuaguerrero:
No multitouch in gallery. I tried with browser but I guess it might work with network. Also no auto rotate. Dam I forgot to check if it works on google maps, to tired to flash back.
[G1 Android Development] NeoBlade:
Certainly will be nice to have some of these features over in a build. Going via twitter its nice to see the widgets ported already and I'm sure it's only time before the code matures enough to be fully useable all round. Noticed a few websites have picked up on this as well and ran with it.
[G1 Android Development] bolmedias:
I'd love to try out Donut. Too bad I only have one G1. Can't wait for this to become stable, or at least stable enough.
[G1 Android Development] RaiderX303:
flasing this on my only g1 atm, gonna work on getting network working.

Edit: It appears network does work, just gets very bad reception, also home key doesnt work, call keys dont work, i made a call and couldnt hang up :S
[G1 Android Development] syphern:
argh i only have 1 g1 too so ill wait for a nice stable release! thqanks cyan you the DON!
[G1 Android Development] jroid:
I only have 1 G1 also, all u have to do is do a nandroid, and just restore it after ur done playin with donut :) that simple... atleast cyan's modified recovery makes it that simple :)
[G1 Android Development] cyanogen:
Just to clarify.. Donut itself DOES NOT have multitouch. The kernel in the Android repository DOES have official multitouch (added a couple of days ago), and it's more than what we've been using now, which is a bit of a hack. So even if Donut ships without any multitouch enabled apps, we will still be able to make it work.
[G1 Android Development] dwang:
Is it the same multi touch implementation as the htc hero?
[G1 Android Development] cyanogen:
Dunno, maybe.

http://android.git.kernel.org/?p=kernel/common.git;a=log;h=refs/heads/android-2.6.29
[G1 Android Development] pixel-painter:
I am so very fortunate enough to have been given a 2nd G1 recently and so I have loaded doughnut and taken some screen shots for you guys of the things I have noticed so far that are different.

Btw Bluetooth seems to pair, but I have not checked the sound yet to see if it actually works.
[G1 Android Development] skepsis:
Hey cyanogen you make any progress with my krispy kreme?
[G1 Android Development] Beast11:
Pretty cool to see where android is going. But still wayy too buggy. I wanted to try out the gestures, but i couldnt find any settings or anything for it... oh well anyways pretty cool stuff...
[G1 Android Development] dragon_76:
Power Strip Widget

I have the G1 update and unzipped it but can't find the Power widget, is there a way to just add the Power widget to Cupcake?
[G1 Android Development] nk02:
power widget is in Settings.apk
[G1 Android Development] cyanogen:
I ported it to Cupcake for CM-3.9.1.
[G1 Android Development] pinetreehater:
Just out of curiosity, why is this update.zip so much smaller than normal ones?
[G1 Android Development] nk02:
but 3.9.1 is not released :P
[G1 Android Development] TunsterX2:
I can only guess the reason, but there's hardly any Google Apps or extras on the ROM due to it being build from the source tree.

I managed to test this earlier on my working G1 (after figuring out the nandroid restore procedure) and seems to be okay. Was very sluggish and buggy (of course). Looks promising though! Keep up the good work cyanogen. :D
[G1 Android Development] pinetreehater:
anyone notice this...Compatibility mode. They realize frameworks are going to break a lot of old apps...

This bodes well for market devs.
[G1 Android Development] Daneshm90:
Neone compile the power widget yet ? the source code Cyan put up on github.
[G1 Android Development] mwenn1:
Has anyone seen anything that might suggest the ability to save apps to the sd card for non rooted phones in this update? That is the one feature I am really hoping for.
[G1 Android Development] maxisma:
Not possible.

Google is too scared that normal people (who can't root) copy/pirate apps.
[G1 Android Development] mwenn1:
I would think that if Microsoft can do it with windows mobile, Google can figure it out for Android. If they aren't going to allow it they need to work with the manufacturers to get more storage space on the phones.
[G1 Android Development] pinetreehater:
I don't see why they can't secure the apps (at least the network dependent ones) with an IMEI report. Sure you can spoof your IMEI, but not many are going to go thru the trouble.

Co-pilot secures their app this way. At least I am pretty sure they do. There is a .xml file in the co-pilot folder that contains my IMEI...
[G1 Android Development] raineth:
The power widget is provided by the Settings app on donut, so it will require some (hopefully minor) backporting.
[G1 Android Development] Daneshm90:
He said he already ported it...when someone asked for an apk he said the source code he put up so if we can compile we can use
[G1 Android Development] testing567:
I would think that the simplest solution would be to only allow non-protected apps to be installed to the sd card and not offer the option for protected apps. But then I guess they would have to build a new framework that would allow for individual apps to be installed in different locations instead of all in the same folder. I bet the real reason there not doing it is there concerned with how running apps off the stock slow sd card would affect overall performance of the phone.
[G1 Android Development] DemoShadow:
is it just me for does your home and send buttons not work? and their is not press menu to unlock screen after sleep... and under settings their is a Speech synthesis, any thoughts on that?
[G1 Android Development] pinetreehater:
Yeah, I tried to use the setting.apk hoping it would just work....should have known better. Didn't work out too well.

That's why people like Cyanogen and JF make the big bucks......
[G1 Android Development] raineth:
Here are a couple more new features I haven't seen screenshots of yet...

The CPU/network/screen usage statistics have a new interface in Settings → About phone → Battery use:

Pressing the home button when you're already at the home screen brings up the gesture input¹, which you can assign to a shortcut:

You need to tap the shortcut at the bottom of the screen after you draw a recognized gesture, so you'll know whether or not it was properly recognized. More screenshots of the gesture creation process attached:

¹ the word in #android is that gestures in the home screen won't be supported in the final donut release — the support that's currently there is just a demonstration/test of the new gesture API
[G1 Android Development] anon1ski:
I really don't know what thats all about. they need to include compatability in the new frameworks FOR that, not a setting to reboot to different framework pieces/settings. I dont understand why they would even do that in the first place.
[G1 Android Development] chrismiceli:
Any word regarding WPA enterprise support without modifying wpa_supplicant manually?
[G1 Android Development] otto888:
How did you get the home key working? I have tried this,and nothing happens.
[G1 Android Development] pinetreehater:
Ditto...was just about to ask.	raineth, how did you get that working?
[G1 Android Development] otto888:
Well,I'm trying to push keylayout stuff from another build,seeing if that will work....anyone got any ideas what raineth did for this?

EDIT:bootloop'd
[G1 Android Development] raineth:
I didn't have to do anything special to make my home button work. Since I was using cyanogen's fw with his apps2sd stuff, I did need to do a couple of things to even make it to the home screen:

mount /system/sd manually — mount /dev/block/mmcblk0p2 /system/sd

rename my old home screen database (I had stuff on screen 3, which makes the stock launcher barf) — mv /data/data/com.android.launcher/databases/launcher.db /data/data/com.android.launcher/databases/launcher.db.bak

I'm restoring from backups and I'll reflash to make sure I didn't do something else and forget about it.

Update: The 2 steps above are enough to make the home button work for me. There is a new table in launcher.db to store gestures — maybe it's not upgrading correctly and renaming it out of the way is the magic bullet?
[G1 Android Development] otto888:
Care to share your launcher.db? Some of us come from a JACHero build. :P
[G1 Android Development] raineth:
If you delete it, the system will recreate it with defaults.
[G1 Android Development] otto888:
And your using the recreated defaults?
[G1 Android Development] raineth:
Yes. I've edited my earlier post.
[G1 Android Development] otto888:
Hmmm....did same steps and still doesn't work...did you do a reboot after that?

EDIT:Rebooted,still the same......are you sure you didn't do anything else?
[G1 Android Development] raineth:
After my reflash, I executed both commands before the launcher had even started. Before that, it would crash while starting, so I couldn't use anything until I'd made the changes anyway. I'm not sure what's different about my setup than yours, but you're obviously not the only person experiencing the problem. What exactly are your symptoms? It boots to the home screen and everything but the home button works? Have you tried looking at logcat for clues?
[G1 Android Development] otto888:
Did you execute both commands via adb shell? I'll try wiping/reflashing and doing this. and the call button doesn't work,but i think everyone has that bug too.

EDIT:Heres how I did it. Force stoped Home via settings,cleared data,used commands,went back to home
[G1 Android Development] rushless:
Mr. Guy has posted on the Android dev site that multi touch is not in the code and not all of the content mentioned in the repository is in the code right now. People may have got a little too excited too early. About two months early perhaps.
[G1 Android Development] raukodur:
does donut have text entry via writing on the screen with your finger? Also, any chance it has good voice recognition software which lets your write stuff (e.g. emails) using (accurate) voice to text interpretation?

That would really take out the need for a hardware keyboard for longer pieces of prose.
[G1 Android Development] DMaverick50:
the $40 dollar samsung phone i had 6 years ago had voice to text ability and it was flawless. That the g1 doesnt come equipped with it is pathetic and baffling.
[G1 Android Development] cyanogen:
This is my fault, I was quoted and didn't research enough. There is code in the Android kernel GIT that is a brand new API for multitouch on the Synaptics driver, but there is no code in the Android framework itself to support it yet. I should have dug deeper, but I was just posting off the cuff as I went thru the new code and it snowballed across a dozen different sites. I already apologized to JBQ and Romain :)

It DOES mean that even if it doesn't ship with whatever they release, us hackers can still use it!
[G1 Android Development] wizern23:
have you got anywhere with making it a stable usable build?
[G1 Android Development] brian_v3ntura:
johnnylicious

read what i posted here

http://xdaforums.com/showthread.php?t=540744&page=2

kinda surprising to me.
[G1 Android Development] ScottGood:
I wanted to run this to check it out for myself, but I get stuck at the 2nd splash screen, I'm currently on CM 3.9, I tryed and got stuck, I wiped and got stuck, only way out is to pull the battery, 3-finger-salute won't work, any idea for running this?
[G1 Android Development] cyanogen:
Not yet. The problem is that HTC's proprietary hardware drivers (sensors, RIL) don't agree with the code in Donut. I'm just starting to learn those parts of the the Android code so I can't answer why it doesn't work yet.
[G1 Android Development] Droid8Apple:
Yeah

I think they let the "chat-room" disease take effect. It's all every page is on here with the exception of the few important things. waht's the .apk, does it directly toggle, etc. Those are things i want to read. Helpful. Of course it's slow- It's not CYAN's build. not even close. of course no aps2sd, of course no GSM. Of course you are to wipe because in essence it's a DIFFERENT build. something CYAN took time out of modifyng the ROMs we love to just show us what the "donut crew" is doing. not him. and maybe also to give a sneak peek of what he will implement in his ACTUAL builds. So thanks for taking the time CYAN, but back to work on the good sh*t LOL. ;)
[G1 Android Development] Droid8Apple:
Throwing this out there.

There are a ton of different music players being made daily, especially for CM's stuff.

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

They're more than likely much better than what the donut-crew could come up with anyhow. thought i would share my search result with ya. :)
[G1 Android Development] wc326:
is flash 9 or 10 working in the browser???
[G1 Android Development] linuxrebel:
I noticed PPTP VPN in a screenshot.

Is there any way that this VPN capability can be taken out of this and put into 4.0? Or put into any other build for that matter.
[G1 Android Development] njuncos:
seeing as how there is no network connections working, I doubt it, lol. but seriously, i believe there is no flash working just yet.
[G1 Android Development] rondey-:
That would be very well note worthy as well as a couple of dozen posts of if/when it will be ported to x rom. :)
[G1 Android Development] wc326:
but is flash 10 or 9 included in the browser...
[G1 Android Development] rushless:
It is all good! It is just that some seem to have not learned from the premature cupcake days. At least here most understand and do not cry when things are not as over-expected. My undertanding is this phase of Android is more for devices later in the year. The uniform days of just the G1 is gone now, so the main frame work of Android will beome more complex to piece meal and make a rom for a specific device. Things will get real wild now, though perhaps not in a good way.

The rule of thumb will be the more main memory the device has, the easier the rom to build.... I guess that is obvious.
[G1 Android Development] IRIE4IPIER:
you seem to post alot of useless posts also, when will you start to develope something in this 'DEVELOPMENT FORUM'? leave the noob policing to the OPs or the forum moderators.
[G1 Android Development] jubeh:
guys, you shouldn't really keep expecting flash support from "donut", or "cupcake", or whatever other misguided idea you might have about android releases. Currently, flash player technology is owned by Adobe, and they licensed it to HTC for release in their Hero device. The flash plugin present in hero is an early version of the one you should be expecting from Macromed.... ahem, adobe in the near future. We don't know their distribution plans yet. I'm sure most hw manufacturers will pay to have flash support out of the box on their devices, but Adobe might offer too a plugin download from their site for capable devices.

TLDNR; Google doesn't make flash, Adobe does. (Although there currently is Gnash and Swfdec available as open sauce, so Google could theoretically use it in Android...)
[G1 Android Development] raukodur:
can anyone give me a half definite answer on this?
[G1 Android Development] morbidrealities:
I kinda agree

You're not a mod or an op...let them do their jobs and you do yours....you're all over quite a few forums and I appreciate what you offer...reviews and such...but, let the mods do their jobs...unless you're Batman aka billionaire vigillante and can pull off the whole "man in tights with a underage boy playing with your "batarang" thing" then leave it alone...let the stupid post stupid and just scroll past it....leave the regulating to the mods who keep the insults to themselves and obviously do a damn good job of it.

And to IRIE4PIER, just because he isn't a developer doesn't mean he posts uselessly, sp?. You most certainly haven't read his many enlightening reviews on apps and ROMs.

Yeah, yeah, yeah....my 3rd or 4th post and I'm stirring the sh&%. Love you all.

Cyan, thanks for doing what you do for all of us. I wouldn't enjoy this damn phone as much as I do without your hard and underappreciated work.
[G1 Android Development] soloxp:
I'm working on the vpn
[G1 Android Development] mookie3three:
Guys with the mention of WPA Enterprise being included in Donut, is there any news on proxy settings being global and not just the browser and also being able to connect to authenticated proxies? I know no one can test this at present seeing the network doesn't work but is the option there? cheers
[G1 Android Development] lbcoder:
Define "global". If you mean publishing the proxy settings for applications to pick up on, that is fine. The correct behavior is for each application to determine use of a proxy for itself. The reason for this is that proxys are very much PROTOCOL DEPENDENT and can lead to severe compatibility issues. That means that an HTTP proxy will only support HTTP communications, so you don't want to just throw your network data straight at some unknown proxy since it will most likely break most things. If you just want to throw all your network traffic at some particular server to distribute as appropriate, then you aren't after a proxy, you're after VPN.

BTW: if you notice the android.net.Proxy class, you will see that the proxy settings ARE available to any application that requests them. Been there since 1.0.
[G1 Android Development] iamsoinsane:
Probably already been noted, "Connected to phone and Media Audio" Stereo support? :)
[G1 Android Development] linuxrebel:
Thank you!

I'm "learning" java via Android at the moment I've found the apk in question that seems to hold the vpn capability (or at least the UI to start the trace) called com.htc.resources.apk (in the /system/framework dir) however I'm still too damn new to be able to get this correctly imported into Eclipse.

If however, I come across anything approaching useful I'll post here. Otherwise I trust in more experienced hands. (Linux I know cold, java I don't) If there is anything I can do to support you, let me know. Again Thanks!
[Touch Pro, Fuze General] garak0410:
Hi!

I finally got around to flashing my phone with the Energy ROM with 6.5 on it. The pictures I've seen of 6.5 show a Zune like interface but I don't see it in my version. Were can I find this?

Thanks!

Brian
[Touch Pro, Fuze General] AkumaMax:
that would be the chrome interface.

Go into Settings/Home Then click on Items then click on Windows Default.

The one thing I wish it had was Zune support!
[Touch Pro, Fuze General] garak0410:
You're awesome! Thanks! Loving the new ROM...and to add another comment...the VPN is much more stable that it was on my stock FUZE rom.
[Touch Pro, Fuze General] paperWastage:
disable touch flo in Settings>Today

enable the default Windows theme
[Touch Pro, Fuze General] garak0410:
Thank's again for all of the tips...I did notice that once I disabled TouchFlow, it is no loger a choice to select again. Why is that?

Thanks!
[Touch Pro, Fuze General] AkumaMax:
It should be. Unless the flash went wrong. Just do the same steps just scroll down untill you see Touchflo3d or something like that.
[Touch Pro, Fuze General] garak0410:
Nope....TouchFlo3D is totall gone as an option.
[Touch Pro, Fuze General] gmanfuzing:
go to the second tab and then scroll down , its there i promise . i also recommend making sure you have the newest mercury build.
[Touch Pro, Fuze General] garak0410:
Man...I promise you it isn't there....ha. I go to START, SETTINGS, TODAY, 2ND TAB and it is no longer there. I'll search for that latest ROM you mentioned.
[Touch Pro, Fuze General] garak0410:
I loaded the latest ROM you suggested...same thing...if I switch to WINDOWS DEFAULT, there is no way back to TouchFlo 3D...it just goes away.

That isn't a big deal if it wasn't for the fact that after that, I began to have display problems (icons and today screen would start melting and smearing together.)
[Touch Pro, Fuze General] AkumaMax:
sounds like some bad flashes. IMO try Flashing the stock ROM to your phone and then flashing the new one. BTW just to make sure after the ROM is done flashing you are Pressing the volume down button and the center circle button while soft resetting to have a good solid flash right?