So I've been looking at the video codecs issue that blocks YouTube HD and video recording on the Dream. Seems there are two underlying issues, libsgl from donut was merged into a new library, and that theres an API break in libhardware.
On the first issue, its fairly easy to build donut's libsgl.so on eclair with some minor changes to source to get it, build it, and it seems that it works properly (as far as I can tell, the OpenGL 3D interface it binds to has had a stable API). I don't have a strong test case to use it on.
The second problem is more interesting. It seems to me that the problem with the API break is that Qualcomm is using enum's in a way that is absolutely stupid, and added new numbers that broke the magic numbers copybit needs. This causes a set of copybit failures when blitting stuff to the screen. Rebuilding the proprietary libraries would fix the problem, but as we only have libraries built against 1.6, this obviously won't work, so I'm seeing if theres a better solution we can use to solve this problem. Any ideas welcome.
NCommander, you've done amazing work here before
unfortunately, based on my research and trying to merge patches from 1.6 into 2.0 source and vice versa, that this is nearly impossible.
I would expect that the only feasable way would be to make a whole new composition method for android, based loosely off the methods shown in the 1.6 source.
Unfortunately, i think that it will be best to wait for HTC to work with qualcomm, and actually release something. I've heard that the MyTouch will be getting the 2.0/2.1 update, and hope that this release will solve our problems.
Noting is impossible
jcarrz1 said:
NCommander, you've done amazing work here before
unfortunately, based on my research and trying to merge patches from 1.6 into 2.0 source and vice versa, that this is nearly impossible.
I would expect that the only feasable way would be to make a whole new composition method for android, based loosely off the methods shown in the 1.6 source.
Unfortunately, i think that it will be best to wait for HTC to work with qualcomm, and actually release something. I've heard that the MyTouch will be getting the 2.0/2.1 update, and hope that this release will solve our problems.
Click to expand...
Click to collapse
Camera didn't work but now it does. Youtube will work 100% very soon
Interesting.... could we possible encapsulate the existing libhardware and create a new interface to it to translate the new calls (enums) to existing? Just throwing the idea out there - probably too simple and I am missing something not knowing too much of the details. I guess I would think of a libWINE like approach, interface just translates the new expected calls to the old driver....
if all goes well, will this also help speed up things like live wallpapers? (sorry if this is a noob question)
smackdown85146 said:
if all goes well, will this also help speed up things like live wallpapers? (sorry if this is a noob question)
Click to expand...
Click to collapse
In theory, it would allow any opengl call to be handled on the GPU. Not only would the livewallpaper speed up, but you'd have more available CPU time for other operations.
The idea is sound, the tricky part is making them efficient enough to actually be a net benefit. It could decent stopgap until new drivers are released.
????-????
So your saying that the first eclair roms where 1.6 with 2.0 skins?
llxll0m3g4llxll said:
So your saying that the first eclair roms where 1.6 with 2.0 skins?
Click to expand...
Click to collapse
No, not entirely...when the Eclair Roms roms were first being made in the beginning Devs didnt have the drivers for the camera. But, thanks to NCommander we do now =)
Android G1 2.0 Update
T-Mobile Czech Republic officialy announced 2.0 update for G1 for end of January (1-2 weeks). Maybe is better wait for this release.
pinkolin said:
T-Mobile Czech Republic officialy announced 2.0 update for G1 for end of January (1-2 weeks). Maybe is better wait for this release.
Click to expand...
Click to collapse
Isn't january ending... tomorrow?
vincom2 said:
Isn't january ending... tomorrow?
Click to expand...
Click to collapse
yeah, my senses tell me that it is
Yes, but this is Europe, "End of January" is in T-mobile speak half of February :-D. I have Google Translate page with this info, but i'm Junior member without rights :-D.
Eh would probably be too lazy to go back to stock anyways, will just have to wait for those video drivers =)
pinkolin said:
Yes, but this is Europe, "End of January" is in T-mobile speak half of February :-D. I have Google Translate page with this info, but i'm Junior member without rights :-D.
Click to expand...
Click to collapse
This can be "helpfully" for your work on this thread. More info:
http://forum.xda-developers.com/showthread.php?t=625108
http://www.4shared.com/file/207649694/b347bfad/RUU_Sapphire_HTC_Europe_304401.html
Is a full origianl ROM 2.1 for HTC Sapphire, the problem is that it only works on 32A, and I think that this can be a problem.
shawe_ewahs said:
This can be "helpfully" for your work on this thread. More info:
http://forum.xda-developers.com/showthread.php?t=625108
http://www.4shared.com/file/207649694/b347bfad/RUU_Sapphire_HTC_Europe_304401.html
Is a full origianl ROM 2.1 for HTC Sapphire, the problem is that it only works on 32A, and I think that this can be a problem.
Click to expand...
Click to collapse
I don't see anyone in that thread indicating that it's a 2.x ROM, just that it's a potential way to root some newer 32A SPLs. Might help some Rogers people out. Am I missing something? Have you pulled the build.prop?
olearyp said:
I don't see anyone in that thread indicating that it's a 2.x ROM, just that it's a potential way to root some newer 32A SPLs. Might help some Rogers people out. Am I missing something? Have you pulled the build.prop?
Click to expand...
Click to collapse
Its probably the default rom that comes with the phone.
How close is the camera in the g1 to the camera in the Hero ? I keep seeing articles that HTC is releasing 2.1 upgrade for the hero. Will this help the g1 ?
menace said:
How close is the camera in the g1 to the camera in the Hero ? I keep seeing articles that HTC is releasing 2.1 upgrade for the hero. Will this help the g1 ?
Click to expand...
Click to collapse
yup with the 2.1 upgrade ur g1 can take 10mp pics
bakgwailo said:
Interesting.... could we possible encapsulate the existing libhardware and create a new interface to it to translate the new calls (enums) to existing? Just throwing the idea out there - probably too simple and I am missing something not knowing too much of the details. I guess I would think of a libWINE like approach, interface just translates the new expected calls to the old driver....
Click to expand...
Click to collapse
Sounds like ndiswrapper for linux
gregnotcraig said:
Sounds like ndiswrapper for linux
Click to expand...
Click to collapse
doesnt it though
Related
It seems that as of now the new sdk is available for download and so on, that is a great news I can hardly wait to put my hands on a blazing fast 2.0 ROM!!!!!!!!!!! (as soon as someone releases one )
http://developer.android.com/index.html
Everybody that follows Cyanogen on Twitter already knows this man and there's no need for another thread (yea someone already beat you to it)
woo hoo! luckily the dream will be able to handle it
There's already a thread on this. Thanks.
Well, Cyanogen, I hate to break it to you.. but you've got a long night ahead of you. And a long weekend.
matt_stang said:
Well, Cyanogen, I hate to break it to you.. but you've got a long night ahead of you. And a long weekend.
Click to expand...
Click to collapse
Looking forward to what Cyanogen has coming out.. loyal fan of his ROMS.
dilfatx said:
Looking forward to what Cyanogen has coming out.. loyal fan of his ROMS.
Click to expand...
Click to collapse
I wouldn't expect anything this weekend.
chaosan said:
woo hoo! luckily the dream will be able to handle it
Click to expand...
Click to collapse
hopefully the dream will be able to run it, it all depends whether or not htc decides to give use the proprietary drivers to have 2.0 working on our phones.
RT @cyrowski
"Eclair won't build for ADP1 or ADP2 out of the box. Will need to wait on vendors for proprietary drivers."
RT @cyanogen
"cyanogen
Probably will start by backporting features- we need new proprietary drivers for our Dream/Magic devices."
====
jbqueru :
@maxisma Unfortunately, the drop doesn't compile for the ADPs
maxisma :
@jbqueru Whats the problem? Just the drivers in the kernel? Hope not more..
jbqueru :
@maxisma Actually, user-space libraries that talk to the various components (especially media-related stuff).
maxisma :
@jbqueru damn Hope @htc will provide support for our already "outdated" devices.. Thanks for your answer
EDIT:
cyanogen
Just booted Eclair on my G1
Pinesal said:
I wouldn't expect anything this weekend.
Click to expand...
Click to collapse
can't rush art....
just be a good boy and wait for the magic to happen
yoshitoshi said:
can't rush art....
just be a good boy and wait for the magic to happen
Click to expand...
Click to collapse
Already been released.
Sorry had to. Someone toss me in the PUN-tentary.
Honestly,
I have a feeling we won't ever see drivers for 2.0 for the Dream/Magic. I'm with the camp that feels they're being EOL'd only a year in. If HTC doesn't release a 2.0 for dream/magic, then we'll never have fully operational devices past 1.6.
This is pretty much the only thing I *do not* like about Android, is that Google treats backward compatibility the same way Linux does: by not considering it at all. Of course, I can hope I'm wrong, because I'm *not* switching to Verizon, and I don't see anything decent coming down the pipe at T-Mobile.
lotherius said:
I have a feeling we won't ever see drivers for 2.0 for the Dream/Magic. I'm with the camp that feels they're being EOL'd only a year in. If HTC doesn't release a 2.0 for dream/magic, then we'll never have fully operational devices past 1.6.
This is pretty much the only thing I *do not* like about Android, is that Google treats backward compatibility the same way Linux does: by not considering it at all. Of course, I can hope I'm wrong, because I'm *not* switching to Verizon, and I don't see anything decent coming down the pipe at T-Mobile.
Click to expand...
Click to collapse
How did cyanogen just boot donut on his g1?
Frito37 said:
How did cyanogen just boot donut on his g1?
Click to expand...
Click to collapse
He backported features one by one until an official release of Donut was made. Also, booting is different than fully functional. Fwiw, someone out there actually booted up Android on a Treo 650 recently. Doesn't mean any of the drivers worked properly! Same here - booting is only the first step.
lotherius said:
I have a feeling we won't ever see drivers for 2.0 for the Dream/Magic. I'm with the camp that feels they're being EOL'd only a year in. If HTC doesn't release a 2.0 for dream/magic, then we'll never have fully operational devices past 1.6.
This is pretty much the only thing I *do not* like about Android, is that Google treats backward compatibility the same way Linux does: by not considering it at all. Of course, I can hope I'm wrong, because I'm *not* switching to Verizon, and I don't see anything decent coming down the pipe at T-Mobile.
Click to expand...
Click to collapse
That Sony Xperia has the 1700 Mhz band. And it looks sexy as all get out.
Eclair, eclair, eclair, eclair.
Tasting some eclairs now.
coolbho3000 said:
Eclair, eclair, eclair, eclair.
Tasting some eclairs now.
Click to expand...
Click to collapse
Are you really testing it?
dilfatx said:
Looking forward to what Cyanogen has coming out.. loyal fan of his ROMS.
Click to expand...
Click to collapse
Same here since day 1...!!!!!
lotherius said:
I have a feeling we won't ever see drivers for 2.0 for the Dream/Magic. I'm with the camp that feels they're being EOL'd only a year in. If HTC doesn't release a 2.0 for dream/magic, then we'll never have fully operational devices past 1.6.
This is pretty much the only thing I *do not* like about Android, is that Google treats backward compatibility the same way Linux does: by not considering it at all. Of course, I can hope I'm wrong, because I'm *not* switching to Verizon, and I don't see anything decent coming down the pipe at T-Mobile.
Click to expand...
Click to collapse
I don't think you understand Linux then. Linux is about as backward compatible as an OS gets. Can you put Windows on a i386 and expect it to work. No. Linux still boots just fine on a i386 and still runs very decent (Actually, it even runs on a i286). Linux also supports most architectures out there, unlike Windows and Mac. Only OS that supports more I believe is NetBSD.
Open-Android-Alliance wants to replace all proprietary with open source pieces. I don't know if that includes drivers or not. We will see. Actually, I see HTC releasing drivers for 2.0. Just not much after that. I just hope the Linux community can reverse engineer the drivers to create open source version so our phones can keep being updated.
There is no other phone on the market that I would want more right now than the G1. I use *nix for pretty much all my computing needs and having a five row keyboard with all the keys I need in *nix is very important to me.
We will get it working, don't worry
cyanogen said:
We will get it working, don't worry
Click to expand...
Click to collapse
I just might have to buy you a CASE OF BEER!!!!
Update!!!
Looks like Drizzy and the Dream boys unwatermarked the dump and made a G1 rom out of it. I will try to talk to Drizzy and ask if I can have the unwatermarked dump but if not we should be able to re-port this back to CDMA and possibly have Hero 2.1. Just remember this wont work as well with our phone as the official one will but a little taste of an Eclair might be good
http://forum.xda-developers.com/showthread.php?t=592568
Hey guys, didnt know if anyone saw this yet but the Dream devs have a Hero 2.1 dump. Drizzy got it and is sharing it with a couple devs but no Hero devs. Not sure why yet but Im trying to find out. I would assume it's because of watermarking and once they get that worked out then they will release it to us. Some of the Dream users don't like us because we have more ram than them (yes, thats the only reason why) but the devs over in the Dream scene are overall good guys. Drizzy, KingClick, BarakInFlorida, Crykowski and the rest are all good guys so I'm sure once they work things out we will get ahold of it. Lox_Dev (from GSM Hero) is already trying so, let's hope and pray.
Does this mean that HTC already has sense skinned on top of 2.0?? If so, does the Hero 2.1 dump you are talking about mean that we could have Sense on 2.0 before its even officially released by HTC? (And even modified and optimized on top of that?!!!) I'm really excited if any one of your answers will be "yes".
I'm new to all this stuff, but I'm really enjoying it so far! Thanks in advance for answering my questions. God bless!
-alex
alexthearmo said:
Does this mean that HTC already has sense skinned on top of 2.0?? If so, does the Hero 2.1 dump you are talking about mean that we could have Sense on 2.0 before its even officially released by HTC? (And even modified and optimized on top of that?!!!) I'm really excited if any one of your answers will be "yes".
I'm new to all this stuff, but I'm really enjoying it so far! Thanks in advance for answering my questions. God bless!
-alex
Click to expand...
Click to collapse
Yes, pretty much. First, I just want to say that Sense is not a "skin" it is an application but more than that, it is an application framework built by HTC. That said, it looks like HTC has created a Sense for Android 2.1, which hasnt even been released yet and someone from the inside of HTC leaked it out. Now, a Hero guy (E2K) was able to get it from Drizzy apparently but we are still waiting to see if he actually got it or is bsing us.
Also, please note that usually when an HTC dump is leaked this means that it is pretty close to release. They are just sending out to testers and fixing all the bugs. This means that HTC could be giving us a Christmas present soon. Also remeber though that after HTC releases it, Sprint still needs to work their "magic" into it so it may take a little longer than normal. Also, if your phone is rooted us devs will want to make sure nobody loses root in upgrading.
OMGAD release it then ! now
thanks for clarifing
dude thank you. im so tired of everyone calling "Sense U - fu*king - I (USER INTERFACE) its a app. Just like the Adv Launcher. If you dudes could get your mind over having some cool ram additive, rather than all the ammenities of the Dream, than you would realize that you could be running 2.0 like the rest of us, rather than 1.5, and have waaaay more bad ass **** on ur phones!
Examplessss
CubeUI - Samsung Behold 2
TouchWizUI - LG EVE
SenseUI - Hero, Rooted g1's
AndroidUI - Dream, Droid, ADP1, Rogers Dream, Etc....
See its all just a different setting for a different phone .. All thus running on Android OS. Its rather simple. LOOK OUT FOR 2.1
Thanks for the answers! That's great news! I'm rooted and flashed running FRESH 0.6. I plan on NOT getting Sprints update when it comes out, but getting it from you XDA guys in some optimized/tweaked ROM without all the crap they put in to bog it down. I'm so pumped! Thanks again for the answers! God bless!
-alex
georgegreco86 said:
dude thank you. im so tired of everyone calling "Sense U - fu*king - I (USER INTERFACE) its a app. Just like the Adv Launcher. If you dudes could get your mind over having some cool ram additive, rather than all the ammenities of the Dream, than you would realize that you could be running 2.0 like the rest of us, rather than 1.5, and have waaaay more bad ass **** on ur phones!
Examplessss
CubeUI - Samsung Behold 2
TouchWizUI - LG EVE
SenseUI - Hero, Rooted g1's
AndroidUI - Dream, Droid, ADP1, Rogers Dream, Etc....
See its all just a different setting for a different phone .. All thus running on Android OS. Its rather simple. LOOK OUT FOR 2.1
Click to expand...
Click to collapse
Well just because we have Sense doesnt mean we can run other roms. In fact we cant. I have tried porting over tons of different roms to Hero and they never seem to work. Sense is good too. Personally, I prefer it over Vanilla Android. Plus, the HTC apps such as messaging and whatnot are better in my opinion. Personal preference. Once optimized, Rosie flies. Sense isnt bad. I just wanted to say it's an application. Not a skin or anything.
Regardless, hopefully we will have 2.1 soon
sounds Great Im excited...God Bless
Is it really that simple though? I imagine the dump is based off the Euro(GSM) Hero.
Natty_lite said:
Is it really that simple though? I imagine the dump is based off the Euro(GSM) Hero.
Click to expand...
Click to collapse
Most likely is. But 1.6 on up has native CDMA support. Either way, Lox from the GSM dream forums says that the guy who leaked the rom to us just will not give up his source which means that if we do get this we cant release anything. Looks like we are gonna have to wait a few weeks anyway. I also was reading that Drizzy just wasnt thrilled with this build. As it is beta (or *gasp* alpha) there is too much that isnt working. Good news is we know it's coming.
http://twitter.com/Official_Drizzy/status/6156799589 "Official RUU for WWE Hero 2.1....."
Hmm.. does this mean we could possibly see a build for our CDMA Hero sooner than we thought?
Exciting news! I'll be watching this thread closely for any updates. Also, like others have said, I will be coming here for an optimized/bloatware free 2.1 from one of the awesome devs who do great work for our Heros!
chuckhriczko said:
Most likely is. But 1.6 on up has native CDMA support.
Click to expand...
Click to collapse
What does this mean for us? The possibility of cross-platform roms?
Dunno if this has already been posted:
Screenshots
Yeah I really can't wait for that landscape mode on home menu
ruskiyab said:
What does this mean for us? The possibility of cross-platform roms?
Click to expand...
Click to collapse
Possibly, yes. One of the reasons it is so hard to port over roms to our phone is because it is CDMA. 1.5 does not have CDMA built in. For instance, try porting over any GSM rom and it wont work because HTC "hacked" in the CDMA support (i.e. built a custom driver). Since 1.6 and up have built in CDMA support the possiblity for us to make cross platform roms is a lot higher. Not saying definite. Just more possible.
chuckhriczko said:
Possibly, yes. One of the reasons it is so hard to port over roms to our phone is because it is CDMA. 1.5 does not have CDMA built in. For instance, try porting over any GSM rom and it wont work because HTC "hacked" in the CDMA support (i.e. built a custom driver). Since 1.6 and up have built in CDMA support the possiblity for us to make cross platform roms is a lot higher. Not saying definite. Just more possible.
Click to expand...
Click to collapse
Is there something "missing" from Google's 1.6 or 2.0 sources that a build of either of those prevents the CDMA Hero from running them at all? Or will they at least boot up and work with some stuff not working?
I tried installing it on my Sprint hero, well not 2.1 but the 2.0 that works on the gsm, it doesn't work.
chuckhriczko said:
Possibly, yes. One of the reasons it is so hard to port over roms to our phone is because it is CDMA. 1.5 does not have CDMA built in. For instance, try porting over any GSM rom and it wont work because HTC "hacked" in the CDMA support (i.e. built a custom driver). Since 1.6 and up have built in CDMA support the possiblity for us to make cross platform roms is a lot higher. Not saying definite. Just more possible.
Click to expand...
Click to collapse
Yeah. The kernel. I tried booting both but neither even bootup.
you still need to compile the hero cdma radio driver for android 2.x
Can the 2.1 version for Rogers can put onto the T-Mobile version of the HTC Magic or will it be problematic?
Looks like it works on 32a
http://twitter.com/Amon_RA/status/24101277025
http://twitter.com/Amon_RA/status/24113346424
http://twitter.com/Amon_RA/status/24116479740
Yeah i'm curious if it can be ported to us on 32b. Would probably work smoother than those legend ports
Sent from my U20i using XDA App
Anyone know if this has "Smart Dialer"?
Sent from my HTC Dream SparksMod using XDA App
is it sense ui?
asb123 said:
is it sense ui?
Click to expand...
Click to collapse
Yes it is sense
http://www.youtube.com/watch?v=1lNeYGQWymM
Come On Dudes! Do It! A Magic Sense Rom must run good on the G1!
Maybe somebody could replace the Sense UI for the Android original. The hardware is not so different, just a little bit more memory.
I want this ROM ported to HTC Magic 32B because since Android 2.x we always have memory leaks in the camera driver.
I definitely want this ported!
I definitely want this ported too! Especially if it finally bring Sense to the G1 without draining our battery in less than day. Or in another cases requires so many changes that it becomes too unstable.
hmmm what did rogers do that cyanogen didn't?
qipengart said:
Can the 2.1 version for Rogers can put onto the T-Mobile version of the HTC Magic or will it be problematic?
Click to expand...
Click to collapse
Some1 ported to 32b please please please
R3N0V4D0 said:
hmmm what did rogers do that cyanogen didn't?
Click to expand...
Click to collapse
Dude its Sense I love sense = o )
solaresdonis said:
Dude its Sense I love sense = o )
Click to expand...
Click to collapse
this is definitely possible. Most people Dont know that the cause for battery drain is a combination of:
1. swap
2. "optimized kernels"
These both exist to make sense roms usable on our phones, and they do make them usable but they drain battery.
the only advantage that this 32a build with sense may have is optimizations of the apk's and frameworks that could account for a speedier experience, and therefore introduce the possibility of cutting down on the two factors listed above.
It is very possible to do, and in fact easy. If the demand is high enough, i'll do it myself... add ideas/input here.
I definitely am up for a port
Sent from my Htcclay's SuperBad 3G using XDA App
jcarrz1 said:
this is definitely possible. Most people Dont know that the cause for battery drain is a combination of:
1. swap
2. "optimized kernels"
These both exist to make sense roms usable on our phones, and they do make them usable but they drain battery.
the only advantage that this 32a build with sense may have is optimizations of the apk's and frameworks that could account for a speedier experience, and therefore introduce the possibility of cutting down on the two factors listed above.
It is very possible to do, and in fact easy. If the demand is high enough, i'll do it myself... add ideas/input here.
Click to expand...
Click to collapse
Another thing to remember is that 32A's have about 100 mb more ram, so 32B's actually need some of those things to make them more usable. Anybody know anything about the radio that released with it? I mean, is it still a locked down 3.X rogers radio, or is it something 2.X, or even 6.X? Another thing of interest would be bluetooth, but I'm not sure if 32A's and B's share the same bluetooth chip. +1 for the port jcarzz, I would try it myself but I'm still learning. We should also try to extract the camara drivers, the way I understand it in CM5/6 we're using a hacky method with backported donut drivers and a few other things. We could really pull a lot from this.
Okay, so I looked a few things up and answered some of my own questions. It does include a new radio 6.35.16.19, but it's not something we can use. Maybe some of the guys who have JTAG equipment can experiment with flashing it. Since it's not a G1 radio we shouldn't get bluetooth working so cross that off the list too. Still a promising release though.
jcarrz1 said:
this is definitely possible. Most people Dont know that the cause for battery drain is a combination of:
1. swap
2. "optimized kernels"
These both exist to make sense roms usable on our phones, and they do make them usable but they drain battery.
the only advantage that this 32a build with sense may have is optimizations of the apk's and frameworks that could account for a speedier experience, and therefore introduce the possibility of cutting down on the two factors listed above.
It is very possible to do, and in fact easy. If the demand is high enough, i'll do it myself... add ideas/input here.
Click to expand...
Click to collapse
Please my liege. Do it.
Request: Make it awesome .
mejorguille said:
Another thing of interest would be bluetooth, but I'm not sure if 32A's and B's share the same bluetooth chip.
Click to expand...
Click to collapse
No, just like all the early 1.5 Hero roms that were from 32a phone... no Bluetooth.
I did a quick dirty port... got to boot but runs like crap... nonstop FC's and crashes. Really no time to play with it.
fishman0919 said:
No, just like all the early 1.5 Hero roms that were from 32a phone... no Bluetooth.
I did a quick dirty port... got to boot but runs like crap... nonstop FC's and crashes. Really no time to play with it.
Click to expand...
Click to collapse
Hehe I figured so, but I wasn't rooted yet when all the hero rom's started coming out so I didn't know that til now. And I looked through cyanogen's twitter and he mentioned that the camera drivers were tied to the radio so we can't pull that from it either. GL on porting it.
Can 2.3 rom be used on my old G1 ??????
maliamalia said:
Can 2.3 rom be used on my old G1 ??????
Click to expand...
Click to collapse
Probably.
But not yet. Trust that Cyanogen and his army of coders will crack the secrets and port the ROM.
But not yet.
On a related note, hooray for the 6.1 Stable release!
That is all.
which is more stable and fast, CM6.1 or MTtest3 ??
maliamalia said:
which is more stable and fast, CM6.1 or MTtest3 ??
Click to expand...
Click to collapse
Think they're about the same. The MTTest3 is good but I prefer CM6.1 for all the extra goodies that come it it. CMParts etc.
Okey, I will try CM6.1.
I don't think android 2.3 will run fast as 2.2:
2.2 is a port of official froyo from mytouch3G, so it's very optimized.
I hope in android 2.3 on G1, I would try to develop something to port 2.3 but I don't know how can I do.. I think by the official sdk but.. mmh
(I'm a programmer but I never developed roms for phones)
Cyanogen said on Twitter that he currently has no plan to port 2.3, as the OS will most likely be GPU-driven.
Honestly, his 6.1.0 release is pretty great.
XBrav said:
Cyanogen said on Twitter that he currently has no plan to port 2.3, as the OS will most likely be GPU-driven.
Honestly, his 6.1.0 release is pretty great.
Click to expand...
Click to collapse
yeah but now our device is really going to be out of date. :/
Well I think it's about time to upgrade to G2 or Nexus S. There's lot of great phones out there. G1 is rocking long enough I think, it stopped to be fast and responsive from Donut update or so...
Sent from my T-Mobile myTouch 3G using Tapatalk
failed to flash CM6.1,
my G1 with the 2708 kernel and 1.33.0013 SPL.
help me!!
maliamalia said:
failed to flash CM6.1,
my G1 with the 2708 kernel and 1.33.0013 SPL.
help me!!
Click to expand...
Click to collapse
congratz. wrong thread and wrong section.
flash cm6.1
flash gapps
flash latest pershoot kernel
next time go to the right section and provide logs etc
I think we must try to port android 2.3 to our g1!
BTW if 2.3 is too slow for our phones, I'll stay on 2.2, no problems!
I'm waiting for a perfect phone:
slide qwerty
800x480px amoled/superAmoled/superLCD
ram>512
rom>1gb
slot SDXC rolleyes: )
cpu>1ghz (and good performance.. the number isn't sufficient )
possible cpu with dual core
excellent gpu
5mpx camera with flash and 720p 60fps recording (also 1080p 30fps would be perfect ) with good optic and NO HTC PINK HALO
google experience or sense
I ask too much?
Do you think I'll keep G1 for the rest of my life?
It can probably be adapted from the AOSP source, but since it has some new gui thingy w/e that is, it will never be the same on our devices, whats the point in downgrading from something that works quite well atm, 2.2.1
Cyanogen's cm6 isn't one of those roms which have the myTouch base of T-mobile. It's pretty much coded from the Nexus Rom and ASOP.
Sent from my Plain Biff Dream using XDA App
Point of updating to 2.3
Well, for me there's one big reason why I'd like to upgrade to 2.3 - Native SIP.
What I don't understand is why Native SIP hasn't been built-in from 1.0! Now there's a flood of poor and mediocre SIP apps on the market, none of which are very good.
I sure hope 2.3 comes to the G1!
hernick said:
Well, for me there's one big reason why I'd like to
I sure hope 2.3 comes to the G1!
Click to expand...
Click to collapse
But for now I can't see any developer works on 2.3..
When froyo and other old android upgrade has been released a lot of people began to develop test roms (in the beginning unusable roms )
Now I can't see nothing
Kishtsang said:
Cyanogen's cm6 isn't one of those roms which have the myTouch base of T-mobile. It's pretty much coded from the Nexus Rom and ASOP.
Sent from my Plain Biff Dream using XDA App
Click to expand...
Click to collapse
yea, but there are divers from the mytouch, would have been foolish to keep using hacks when was real drivers out there.
maliamalia said:
which is more stable and fast, CM6.1 or MTtest3 ??
Click to expand...
Click to collapse
Having just switched from MT3G-test3 to Cyanogen 6.1, I would have to say they're pretty comparable. If you put my feet to the fire, I'd say MT3g-test3 is slightly faster, especially in regards to installing apps from the market. But the goodies available in Cyanogen are so good that...
Aargh, it's hard to decide. I have a nandroid+ext of both, so I can swap back and forth at will. I might spend a few days with each to see which one I enjoy using more, and report back. One thing making it harder... I have a white G1, which historically has had problems with Cyanogen. But the latest seems to be working a lot better than previous releases.
nagash91 said:
But for now I can't see any developer works on 2.3..
When froyo and other old android upgrade has been released a lot of people began to develop test roms (in the beginning unusable roms )
Now I can't see nothing
Click to expand...
Click to collapse
Don't worry, Google has only released Android 2.3 yesterday. Give the developers some time!
GoodDamon said:
Having just switched from MT3G-test3 to Cyanogen 6.1, I would have to say they're pretty comparable. If you put my feet to the fire, I'd say MT3g-test3 is slightly faster, especially in regards to installing apps from the market. But the goodies available in Cyanogen are so good that...
Aargh, it's hard to decide. I have a nandroid+ext of both, so I can swap back and forth at will. I might spend a few days with each to see which one I enjoy using more, and report back. One thing making it harder... I have a white G1, which historically has had problems with Cyanogen. But the latest seems to be working a lot better than previous releases.
Click to expand...
Click to collapse
SuperBler is really fast too. You should Check it.
I made it for fun and it is NOT usable and will not be before we get official source
http://saraev.ca/signed_120810_223045.zip
working:
- data/radio (no incall microphone)
- wifi
not working: everything else
please do not report bugs. I know whats not working but can fix NOTHING for now
Good job. IMO these ports will be unusable for the next few months until cyanogen comes up with a release.
It was like that with eclair and later froyo. History tends to repeat itself.
Woot Woot, Hopefully once we get the source this can become stable. The magic lives on. Not many froyo builds I tried for the 32a werent that easy on battery life. Hopefully this turns out good. Hope the devs will work together to create a stable rom, instead of having their own builds with pros and cons.
If 2.3 ever starts working on 32A + NR, I am jumping ship asap! I miss vanilla android
eyegor said:
Good job. IMO these ports will be unusable for the next few months until cyanogen comes up with a release.
It was like that with eclair and later froyo. History tends to repeat itself.
Click to expand...
Click to collapse
There is no beginning no end. We are never be alone
HTC planning any updates in the future for "oldest" device? :/
eyegor said:
Good job. IMO these ports will be unusable for the next few months until cyanogen comes up with a release.
It was like that with eclair and later froyo. History tends to repeat itself.
Click to expand...
Click to collapse
I would have to agree with you except for I think I read on Cyanogen's twitter page that they will NOT be supporting first gen devices after CM6.1 which I assume meant NO ported 2.3 for us.
Hopefully I am wrong.
where is that quote? can't see it
good job!!!!!!!! hahahahaha
Did anyone1 tried on OR and cm Bcrook kernel???
i want to make a team for dev this rom to work full on magic..contact me..
nice hopefully it will fully work
Download does not work?
Really impressive work Hope to see this fully working.
what changes are needed for this to boot on 32b?
This is all well and good and I'll try it if I get my repaired phone back and can once again have a spare to play with.
However is it reasonable to expect this to ever be usable? We don't seem to be able to get a fully working 2.2 under the new radio so why would 2.3 ever get enough attention or drivers? I used 2.2 for a long time on the old radio but I really needed to use the new radio and have since gone back to 2.1 since it is now my daily driver again.
This will be great fun once I can put the Magic back to dev use.
I tested this on my g1, with a pershoots kernel over top so that it boots. And I was wondering how you got wifi to work? I tried replacing many things, but still get an error starting wifi supplicant daemon on logcat.
Just curious, not like I expect anything to ever become usable haha
studjuice said:
I tested this on my g1, with a pershoots kernel over top so that it boots. And I was wondering how you got wifi to work? I tried replacing many things, but still get an error starting wifi supplicant daemon on logcat.
Just curious, not like I expect anything to ever become usable haha
Click to expand...
Click to collapse
hm did you replace wlan.ko ? you should
also take a look at init.sapphire.rc:
Ive changed wpa_supplicant service a little because wlan_loader is not used as in eclair/froyo roms. my *wpa_supplicant.exec* loads the firmware and then starts *real* wpa_supplicant.
I realy dont have an idea whether firmware & tiwlan.ini are different for trout/sapphire. if they are you can edit wpa_supplicant.exec to load propper firmware files..
EDIT: this will not be usable untill we get gingerbrad sources published by google. then maybe cyanogen will do a build for us. I heard he will not support sapphire/trout anmore and if and *only if* it is true I will try to make a working one. I hope it isn't true and cyanogen will still suport our devices because he can do it better than me for sure
saibot64 said:
where is that quote? can't see it
Click to expand...
Click to collapse
twitter.com/cyanogen/statuses/8805829046177792
twitter.com/cyanogen/statuses/10393734621433856
*bump* any news, updates, anything?
found this
http://phandroid.com/2010/12/15/gingerbread-source-headed-to-aosp-soon-now-the-real-fun-begins/
Hopefully we can get a working build, dont wanna let the magic die.
Porting
Anyone done any work porting this? I'm currently working to compile this for my fender. Hopefully with the new radio. Which I've read doesn't work, so... anyone found a working one? I'm running eclipse to compile but if you'd like to help, let me know what you use and I'll send you what I've got.