yashsingh1/xdaforums huggingface dataset:
[Vibrant Q&A, Help & Troubleshooting] Sdobron:
Only worked on user added words in my experience. Any base words can't be deleted.
[Vibrant Q&A, Help & Troubleshooting] ram100987:
so i guess it still comes down to figuring out how to edit the base dictionary then...
[G1 General] KoolKidsKlub:
So the guy who's dumping the AOSP from the Nexus S said "There is no AOSP support any longer for ADP1 ("dream") and ADP2 ("sapphire")." You can read it yourself here http://groups.google.com/group/android-building/browse_thread/thread/298a46f6eaab8c39 I don't know if it's true so please tell me if it's not and please don't flame me if it's not. I guess I'm gonna get a G2 now. What do yall think?
[G1 General] XxKOLOHExX:
Never say never lol, Someone will find a way
[G1 General] cesarbric:
Heard the same awhile ago with Eclair and Froyo.
[G1 General] bigmoew:
This

This

And this.

:D
[G1 General] xaueious:
RAAAAAAAAAGGGGGGGGGGEEEEEEE

Just kidding ;)
[G1 General] Deathwish238:
The Dream can barely handle FroYo, I don't know how well it would handle Gingerbread.

Does anyone actually have their G1 running quickly on a FroYo ROM? CM is pretty damn slow.
[G1 General] roalex:
yes, CM itself can be set up right for once, then are the OTA roms who are with less things...so they run quite good and ofc the AOSP froyo roms.
[G1 General] Deathwish238:
What setup is needed for CM to be fast? I don't need any features, just speed. If there's a better FroYo ROM for that I'm open to switching.

Gingerbread on the Dream will happen...I have no doubt about that. The question is how well it'll run. If only the Dream had a little more RAM...
[G1 General] bonesy:
Come on man when have we "never" been able to get an update? Im gonna take a wild stab in the dark and say we will still be getting roms for at least another 2 years!
[G1 General] MentalDeath:
I don't know about that, because I'm pretty sure Honeycomb or whatever they decide to call Android 3.0 has a minimum requirement for 1GHz processor so the Hero, Sapphire and Dream might be out of luck, especially the Hero because they're still stuck with the 2.6.29 kernel. 3.0 might be possible but I doubt 2 yrs of new Android ROMs is plausible.
[G1 General] ezterry:
AOSP gingerbread running on my Dream..

So seems mostly a go.. will require some poking for a true release but not that bad.
[G1 General] AdrianK:
If it's not officially supported in AOSP, does that mean we'll be without camera drivers?
[G1 General] Since001:
This is so great!
[G1 General] Jurai:
check out the 2708 radio+kernels. By switching to the new radios released for the mytouch + kernel with support, you gain back an extra chunk of ram for os use. Definitely helps out froyo builds
[G1 General] ezterry:
camera (with the minimal poking to get it to compile) is working :)

No release because many bits of this are easy to fix

> wifi works

> camera works

> hw3d I think is working .. but lanuncher/3d gallery/keyboard are running a bit slow .. and we know the port to 2.2 of launcher/keyboard run fine

> bluetooth no-go but that is just because I'm using a sapphire firmware (easy to swap)

> gsensor no go.. I think this will be a relatively easy thing to correct. API change confused it.

Taking a break from testing while I make a repo to work from
[G1 General] Deathwish238:
Honeycomb (Android 3.0 or 2.4....who knows) will not require a 1Ghz CPU.
[G1 General] protomanez:
Still don't understand why you people want gingerbread so much. The time it takes to get something that was never intended to even be ran on the G1 was at least a year or so and that was only with eclair and froyo. We can't run a lot of things because of the lack of ram like jit. Everything lacks now, even the gpu.

Please stop with all this silly nonsense about Gingerbread threads and just be patient. I have little faith in the project, as most original devs have completely moved onto different devices which are easier. Not saying the new devs are bad, I'm just saying we lost a lot of veteran support on the G1.

Why not just use something fast on your G1 that won't fry it's sockets after 5 hours of use?
[G1 General] MentalDeath:
Alright I shall take your word for it.

People just want to have the newest, and humans like pushing limits (in this case of the G1).
[G1 General] zzrssh:
Not only that, look at ezterry's mt3g port of froyo. 2708 radio/kernel + mt3g = hot fastness. Loaded it on two G1s, the gf loves how much faster it is than the other froyo roms we've tried. Probably has to do with the fact ezterry's port is nearly completely stock (it is without the parts update).
[G1 General] Ace42:
(keep hitting thnks buttn by mistake on every post xD)

Anyway I think 2.3 will be too much for the G1/MT3G to handle, it already struggles with 2.2 so 2.3 is over doing it. Battery will not be very good, as most phones with 2.2 now have 512+ ram as the standard. To get the best experience you'll need faster hw to support the effects,apps,etc...2.1 is the furthest i would go w/ a g1, but 1.6 is where the best perf is. I would go with a new phone if you wanna enjoy 2.3.

p.s. not trying to discourage anyone, just stating facts
[G1 General] d3v14n7:
The ASOP froyo roms are surprisingly speedy, especially with the additional memory with the new SPL/Radio combo, don't knock em till you've tried em... They're speedier than any of the 2.1 roms out there on the G1/Dream. Yes, CM froyo roms are sluggish, but that's only because there's so much more stuff added to the rom.

But, I do agree that these handsets are getting old and it's becoming more and more difficult to cram modern roms into so little space, not to mention performance issues with certain apps included in the roms (IE: Gallery 3D etc...). Also many newer apps being released on the market are slowly removing support for mdpi devices, and also require beefier hardware in order to run smoothly...

After the holidays I'll be grabbing a HTC Desire Z and finally retiring my trusty old Dreams/G1s as backup phones, hopefully there is just as much support for those phones as we had for the Dream. We can't complain really, these phones were never supposed to run anything higher than Android 1.6, and yet here we are running froyo (with a possible Gingerbread rom in the works, awesome work EzTerry!) pretty much flawlessly... It just shows the sheer dedication of the devs on these forums.
[G1 General] zzrssh:
You people really are killjoys.

Doing something that is said cannot be done is part of what drives a lot of hackers, the "impossible". Gingerbread will come, and it will be faster than Froyo.

Hats off to you, developers.
[G1 General] ezterry:
BTW any developer out there that wishes to help me out:

repo sync -u git://github.com/ezterry/manifest-gingerbread-DS.git -b gingerbread

proprietary files can be taken from my MT3G-test3 (if you use a HTC magic install note you may want to swap the bluetooth firmware with the cm6.1 one or bluetooth will fail on the dream.. the dream install does this already)

I'll release a binary when it is ready.. but you have the source

--

Developers only: a binary GINGERBREAD-DS-Alpha-20101219-1.zip (md5: bef700cf0e04de003788365de469dd49) now exists

This is mostly to ensure you are using the same proprietary files as there are many bugs.. some with obvious solutions not yet addressed; some with less obvious solutions that need time (and preferably multiple heads)
[G1 General] darkshino:
What differs about proprietary files from cm6.1 which are based on latest MT3G OTA release, aren't they ?
[G1 General] ezterry:
Cyanogen cherry picked them differently and they are for the CM builds so there is one or two missing from CM. And some are not the same for other reasons.

Since my dream/sapphire settings are from aosp froyo its easiest to use the same for the proprietary files even if most of them are the same.
[G1 General] bypass23:
Thanks for the info via private message ezterry :D You clearly saved me alot of time with the work u have done.

My first try to compile aosp 2.3.1 for G1 worked yeah !

I modified a few things for my build :

Using pershoot's 2635.9_ds_32b_radio2708-oc-uv-xtra-ram-fp-121510 zImage since I had no clue what was in there :) and since I'm already using your 2708 hack it worked like a charm

Replaced wlan.ko Wi-Fi do work dropped once only haven't checked logs yet tho reconnected right after...

Using ADP1 (that's what I have) extract-files for property drivers

Added ChainsDD SuperUser lastest version 2.3.6.1

Added Android Terminal Emulator lastest version 1.0.18 - root confirmed with su

Few more things but not really relevant into making it more snappier at this point I was too much into a rush to run make :eek:

I've tried the modded GingerbreadKB apk/lib that was around seems a bit more responsive but not a huge gain here... maybe simply the zipalign and png opt was done would have to be checked aswell

So to wrap up I've tested these things and they seem to be working :

call/data now mic and speaker do work I've made calls without a problem with headset as I'm waiting for parts to fix my ADP1

Wifi (maybe still an issue for dropping connection need more testing only happened once to me)

Camera (have'nt tested recording but taking photos works)

Bluetooth can see my wireless keyboard but my plantronics 855 died on me so I haven't paired anything yet

Galery3D works but kinda fails, I'm investigating into opengl/3D stuff atm, it could be the slowness we get on kb (launcher aint that bad IMO) since everything is now using opengl in 2.3

Next issue I'll look at is probably Google Apps... that part does'nt look easy but I'll see must try first :rolleyes:

Maybe swap aswell soon could help ! even with your 2708 hack I only have 3-4 meg of ram left without using anything and swap is @ 0 obviously

I don't really had a plan to make another thread with my build, unless you don't mind and people wants it for their 2708 hacked G1 devices. (I released a SDK port of 2.3 and ppl did said aosp was avail in that thread so maybe some wants dunno still alot better than sdk port at this point) It's mostly your work anyways and I always give credits ;) Let me know !

Thanks again ezterry, we're definitely going in the right direction !
[G1 General] bypass23:
Before going to bed I've done some benchmarking on my 2.3.1 build related to openGL and overall performance...

openGL/3D seems to be an issue, getting only 11.5 FPS with neocore on aosp 2.3.1 compared to atleast the double FPS on CM6.1 Also, almost nothing appears correctly during the test, only a few effects can be seen the rest is all black :eek:

I haven't checked logs about it yet... has to be checked

Linpack gives almost the same kinda results... almost half the MFLOPS I had with 2.2.1

I did'nt enable JIT in my build either, maybe it could improve the results... still took less time to execute the benchmark itself tho by almost 10s

That's it for today, I'll keep you guys informed on the progress :D
[G1 General] add119:
I have both htc hero and g1.

Im sorry to say it on paper they both look similar.

Expection of 5 vs 3 megapixes and ram that make the hero look and feel faster.(256 rom/192 ram) vs (512rom/288ram)

But htc hero runs well on android 2.3 os and fast compare to g1 with android 2.2 os.

Im pretty sure that the hero wont end at android 2.3 os with more demand and stable and faster processor then g1 will ever be.

G1 runs great on android 1.6 os, 2.0,2.1 os but android 2.2 os is slow in all the rom minus Froyo for trout that in my opinion is the fast froyo rom the g1 has.

biffmod is the best g1 froyo roms, because of it ability to install as many apps you want in your g1, but u do lose speed on it.
[G1 General] add119:
bro this is the only android 2.3 os roms for g1 so far...

http://xdaforums.com/showthread.php?t=870340
[G1 General] bypass23:
I now have a working aosp 2.3.1 built from source...

Alot has been fixed compared to my SDK port :

call/data with mic

Wifi

Bluetooth

Camera

and more...

I'm looking into openGL & 3D issues atm - should fix the overall lag if it can be sorted out.

I'm pretty sure we will have a working 2.3.1 aosp rom for daily usage eventually... Patience :rolleyes:

Thanks again to ezterry for his 2708 hack & work on aosp 2.3.1 for the G1 !
[G1 General] bypass23:
AOSP 2.3.1 Screenshots

Since ezterry only posted one screenshot, I decided to add a few more :D

Enjoy !
[G1 General] ezterry:
Yes, I'm quite sure this is the issue.. It feels like the angry birds problem, of over using the gpu for an operation the old hardware in our phone is not good at.

Other parts of the system feel up to speed once you stop using launcher2, soft keyboard, and the status bar.. gallery3d needs some tweaking as well but the 3d part is mostly at speed.. thubnails seem to be killing it.

As for most of the extras you added, they will slowly be added to the build, either as prebuild overlays or from source.

Also the kernel in there now is my 20101106 _ 2708 kernel.. but that version is showing its age some with gingerbread, I'm currently testing with the 285 cm nightly 2708 port I made Friday night.

If you don't see the USB debug/mount norification switch to that.. the new kernel has the new API.
[G1 General] bypass23:
Hey ezterry :D

To be honest I haven't tried your alpha directly, since you posted it after your private msg with the github info I was playing with the repo sync.

Did'nt wanted to harass you either with questions, I decided to use pershoot's since it worked with the SDK port. It was a succesful guess :rolleyes:

FYI both usb debug/mount works with pershoot's kernel

But indeed, I'm almost 100% sure all this lag is because of the 3D/openGL. I haven't checked logs much yet since I'm at work but thumbnails in gallery seems to be related to not being able to copy the created smaller thumbnail of the actual image on SD. :confused: (I think there was a similar issue that firerat addressed in his all in one patch script for lwp and 3d programs that need write perms on sd)

I'll dig into it more after work but 3d is what we should look into first IMO
[G1 General] bypass23:
Neocore

Well, I took my 15 minutes break to check the logcat when using Neocore :p

Libs seems to be loading ok :

12-20 11:06:09.337: VERBOSE/Neocore(898): loadNative System.loadLibrary

12-20 11:06:09.347: DEBUG/dalvikvm(898): Trying to load lib /mnt/asec/com.qualcomm.qx.neocore-1/lib/libneocore.so 0x40516238

12-20 11:06:09.357: DEBUG/dalvikvm(898): Added shared lib /mnt/asec/com.qualcomm.qx.neocore-1/lib/libneocore.so 0x40516238

12-20 11:06:21.407: DEBUG/libEGL(898): loaded /system/lib/egl/libGLES_android.so

12-20 11:06:21.437: DEBUG/libEGL(898): loaded /system/lib/egl/libGLES_qcom.so

Some config files are missing tho :confused: :

12-20 11:06:09.367: INFO/Neocore(898): Using native path </data/data/com.qualcomm.qx.neocore/files>

12-20 11:06:09.367: DEBUG/Neocore(898): Neocore_initState mConfigFile = (null)

12-20 11:06:09.367: DEBUG/Neocore(898): Neocore_initState using default config file

12-20 11:06:09.377: DEBUG/Neocore(898): Neocore_initState s_pMe->m_szConfigFileName = config.txt

12-20 11:06:09.467: VERBOSE/Neocore(898): runOnUiThread..run

12-20 11:06:09.467: VERBOSE/Neocore(898): runOnUiThread..configFilePath=null

12-20 11:06:09.467: VERBOSE/Neocore(898): runOnUiThread..getFilesDir()=/data/data/com.qualcomm.qx.neocore/files

12-20 11:06:09.477: VERBOSE/Neocore(898): runOnUiThread..configFilePath=null

12-20 11:06:09.487: VERBOSE/Neocore(898): runOnUiThread..cfg does not exist

I'm going to check if ROMs with fully working openGL/3D has any config files in /data/data/com.qualcomm.qx.neocore/files/

If so I hope we can simply reuse them to fix some of our problems :cool:

Update : no config files from working 3d roms in there

Results :

12-20 11:08:26.617: INFO/QXEngine(898): Neocore v1.9.22

12-20 11:08:26.617: INFO/QXEngine(898): Resolution = 320x480

12-20 11:08:26.617: INFO/QXEngine(898): Fps = 9.6 :mad:

As you can see with these screenshots there is obviously an issue with 3D
[G1 General] bypass23:
Partial fix

Well I still have good news :)

I was able to partially (totally?) fix the 3d issues that we had on aosp 2.3.1 !

It fixed :

On screen Keyboard lag

Changing homescreen lag

Gallery3D is fast and works as expected

But I'm still having the black screen issues in Neocore benchmark :mad: Have'nt tested a game yet will try later...

Update : I've tested 3-4 games and all gfx were fine no glitches, no black screen and on par with fps/speed I had on CM6.1 there seems to be an issue with Neocore itself with aosp 2.3.1... openGL and 3d issues seems FIXED!

Scored an amazing score of 50.2 FPS :eek: LOL prolly due to the fact that almost nothing do appear on the screen during the test itself !

Check the screenshot :cool: :
[G1 General] add119:
That awesome bro hopefully, by spring 2011 you and xda developers have a working rom.
[G1 General] dhkr123:
If anybody is interested in the *complete* story about AOSP 2.3 and Dream....
[G1 General] jeffakajeff:
How come this is not in the dev section?
[G1 General] ezterry:
The op post or some of the spinoff conversation..

The op is in the right place .. the spinnoff will move when I make a thread for my codebase.. within the next 24h.. I've not done so because I've been too busy hacking the repo together. But as it targets something bootable now I'll try to get the ears of any devs wishing to help.
[G1 General] jeffakajeff:
Very good.

\

I just noticed that cyanogen made it so we can build on 32 bit, you should merge those changes ;)
[G1 General] bypass23:
simple hack to compile :)

anyway we're working on it ezterry made an awesome job so far no doubt on git

now if ppl cry too much I could post my 2.3.1 with opengl fix and overall lagness we had.

It's up to him, ive used so much of his work even tho we are close to a daily build with my work BUT its up to him /respect

It was slow poke before my patch on home screen / launcher / on screen keybord...

That is fixed atm I think, since most games works fine...

now I'm looking into getting market and gapps working GIMME TIME

I may post or not it's up to ezterry I'm not trying to steal anything.

I used 2.3.1 as of now for 2 days works on a daily use besides market... looking into it atm that was our next goal ! since 3d **** seems to be fixed...
[G1 General] bypass23:
Camera works for pics, not for recording atm

Getting the android market to work is the new challenge IMO...

I cant fix everything in a day :D opengl and 3d was fixed today

Yet thats why ez and I havent released more, you will see a 90% daily use rom really soon...

We won't release non working crap at this point BUT were close :)

My sdk release is just as good Dominating AOSP release... tried it nothing new is working...

We got alot more working... and im not gonna mention that !

We're gonna move to dev when we fell its time to :)

We've done alot within a few days, but I got a job and so does ezterry... be patient what is going to be released will blow ur mind :)
[G1 General] bypass23:
My linux box mb died on me with this newer compile try, so unless ezterry says no I'll post something based on his build (anyway mine was built from his github) adapted to g1 propriety drivers and with root, 3d fix and a few more apps i need to debug... I'll be working on orientation sensors before market as requested by ezterry.

Stay tuned :rolleyes:
[G1 General] bypass23:
2.3.1 needs java6 (64 bit) and some workaround needs to be made on the compiling computer I had left for that (i686)

You dont need 64bit tho...

If u need more info on how to do it let me know :) I'll help you
[G1 General] jeffakajeff:
I know I already worked around it and compiled a version

Sweet deal.
[G1 General] ezterry:
BTW if you are here about my gingerbread repo.. lets move the talk to the new topic http://xdaforums.com/showthread.php?p=9987685#post9987685
[G1 General] add119:
Hey can u put A2SD On this roms?
[G1 General] mr.pnutt:
G1 Chromatic Dream(Android 2.2 Froyo)
[G1 General] zzrssh:
You're asking them to put the cart before the horse. Give it time.
[Nexus One Android Development] aliwaqas:
hi,

Chris Soyars has just released the AOSP Gingerbread ROM for Nexus One. According to him, this build is only workable on nexus one's with 35.0017 hboot.

Here is the reference link.
[Nexus One Android Development] rori~:
Let the play begin :cool:
[Nexus One Android Development] houzuoguo:
well done!!

I wonder if there is a way to upgrade hboot?...
[Nexus One Android Development] martin0285:
Why wouldn't there be?

http://xdaforums.com/showpost.php?p=7197502&postcount=1
[Nexus One Android Development] Frankenstooge:
As do I... I'm sitting on 35.0012.

*gnashes teeth*
[Nexus One Android Development] baseballfanz:
How to find what hboot version you have?
[Nexus One Android Development] ElChibo:
go to fastboot..
[Nexus One Android Development] Frankenstooge:
If you are running CM like it says in your sig, reboot to bootloader and check the top of the screen.
[Nexus One Android Development] Calex93:
Sweet.. Gingerbread already :)

I do have the aforementioned H-boot, but seeing as it does not have market, I'm not that willing to try just yet.
[Nexus One Android Development] baseballfanz:
Thanks guys. 33.xxxx something LOL. I need a magnifying glass to read it
[Nexus One Android Development] aliwaqas:
So who is in the flashing process..as of right now ;)
[Nexus One Android Development] sergioalvarezmac:
Installing the Korean FRF91, your SPL updates to 35.0017.

Look at this: http://xdaforums.com/showpost.php?p=7197502&postcount=1
[Nexus One Android Development] Frankenstooge:
Can't you just flash Google Apps separately? Been having to do that with CM anyway.
[Nexus One Android Development] Calex93:
Can't download now as I'm at work.. :( Has anyone flashed this yet?
[Nexus One Android Development] ms79723:
Just grab the apps from the WIP gingerbread build
[Nexus One Android Development] El Daddy:
CAUTION! Flashing the .35 Hboot changes your recovery partition. If you are using Amon 2.0.0 it may cause problems if you have bad blocks. Amon discussed the issue here about a week ago: http://xdaforums.com/showpost.php?p=9690514&postcount=1467

You can flash an older version of Amon and it should be ok. It fixed mine at least.

0.35.0017 Hboot file attached

Md5:b0669d79f3ace07fdd3e1c03d88d2c68
[Nexus One Android Development] ElChibo:
you just can flash a gapps so it would work id assume.. so just get it from goo-inside.me
[Nexus One Android Development] ElChibo:
flash in clockwork?
[Nexus One Android Development] Imperial.mack:
just flash this as is?
[Nexus One Android Development] musashiken:
Do I need to unlock my bootloader to flash the newer Hboot? I'm still on 0.33.0012.
[Nexus One Android Development] AndroidStop:
Gratz ;-) ....
[Nexus One Android Development] dadennis:
worked fine for me, had bootloops all the time. then i installed latest cm nightly, booted it up one time, then installed gingerbread-rom and it works perfectly
[Nexus One Android Development] vegetaleb:
I am interested by gingerbread but I will not flash it before having TB wake and colors :rolleyes:
[Nexus One Android Development] brian6685:
Actually working great for me. Evrything works except camera and that small white screen bug is there sometimes....but its definately usable. Nice work
[Nexus One Android Development] Fatal1ty2787:
Am I the only one who doesn't see the notification bar? even after a reboot and a wipe?
[Nexus One Android Development] wildchild048:
same hear no notification bar
[Nexus One Android Development] Garner:
Flashed perfectly

flashed over the latest cyan nightly with success liking the rom just dont have the screen off animation? :confused:
[Nexus One Android Development] GlenH:
Flashed over Enomthers rom, and seems to work, but like others, I'm missing the notification bar.

Will try with a clean flash.....

Edit: wipe+flash produces boot loops. Seems like something is missing in the rom........
[Nexus One Android Development] kfir:
That sucks, Galaxy S dudes already have a ported ROM...

http://www.engadget.com/2010/12/18/samsung-galaxy-s-receives-gingerbread-port-right-from-the-nexus/
[Nexus One Android Development] vegetaleb:
It's normal because it's easier to get it directly from Samsung Nexus S to Galaxy S, it's pretty much the same hardwares