Basically, how quick could we expect a straight AOSP port of 2.1 and how functional will it be? I know that the 2.2 build is missing camera, 4G, and MMS, but will we have those same limitations since the source code of 2.1 is already out?
-------------------------------------
Sent via the XDA Tapatalk App
Nah--we've got the libraries for 2.1 from the original ROM; all we need is access to flash what we desire, and we can put together an AOSP 2.1r2 build in short order (24 hours or less) that's fully-functional.
Shidell said:
Nah--we've got the libraries for 2.1 from the original ROM; all we need is access to flash what we desire, and we can put together an AOSP 2.1r2 build in short order (24 hours or less) that's fully-functional.
Click to expand...
Click to collapse
When you say the libraries I assume you mean because we already have 2.1 on the evo.
I know with the hero it was a ***** to get the camera, cause HTC has not release the .29 kernel source, so we were stuck with the .27 until toast finally built his own .29 kernel. He is such a stud. By the way it was prolly less than a month ago they got the camera in a 2.1 full aosp rom.
I would think it would not be anything like this though.
Roman G said:
When you say the libraries I assume you mean because we already have 2.1 on the evo.
I know with the hero it was a ***** to get the camera, cause HTC has not release the .29 kernel source, so we were stuck with the .27 until toast finally built his own .29 kernel. He is such a stud. By the way it was prolly less than a month ago they got the camera in a 2.1 full aosp rom.
I would think it would not be anything like this though.
Click to expand...
Click to collapse
I think we have a lot more support coming over to the Evo than we had with the Hero. Shouldn't be that long, but its just a matter of getting that kernel source. Your right though, with Toast on our side I dont think anything is impossible. The good thing about Android is you can flash another image in no time at all, so if you wanna see what its all about (Without Camera, MMS, and whatever it was) then you can flip back and fourth just to see the difference. Apps2SDK will be a big plus since we wont be needing to go to the market everytime to get all of our widgets and things back. My mouth is watering as im less than 43 hours from getting her juiced and ready to go!
Thank you for asking this question! (I was going to but was too lazy.) Unfortunately I'm going to wait to get the Evo until there is a way to get AOSP 2.1 (or fully functional 2.2) on it. I hate Sense with a passion. So, good luck everyone and may you quickly make our dreams come true!
Stunna4life888 said:
Shouldn't be that long, but its just a matter of getting that kernel source.
Click to expand...
Click to collapse
We already have kernel source
We tried the 2.1 camera libs in 2.2 (hint came from the fact that Toast saw that the froyo N1 ROM does not replace the camera library as part of its update from 2.1 to 2.2, indicating that the library itself works unmodified between 2.1 and 2.2), but it failed due to a prelink map mismatch: the N1's froyo build expects the camera lib to load itself at location "XYZ" (in memory), as it was built that way for performance reasons, and works that way on the N1. However, the HTC library (different camera) does not load itself at the same location the N1 expects it (call it "ABC"), and was not stripped with the apriori prelink utility. So the framework refuses to load the library because it can't load it where it expects it should be loaded from.
I didn't try an AOSP 2.1 ROM yet, so it feasible that it may load it properly... However, due to the fact that the EVO has hardware that is not supported in Android 2.1 (FFC, 720p video, wimax, HDMI out, etc), HTC has rolled their own framework modfiications. If the camera lib requires any of those modifications (99% guaranteed, it *does*), the library won't be able to find those modified APIs, and will still fail.
Are any devs working on this?
-------------------------------------
Sent via the XDA Tapatalk App
TheBiles said:
Are any devs working on this?
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Yessir. At work now but as soon as I get home I am going to recompile my AOSP build for the Evo and pray that it works. As Maejrep said I don't expect the camera to work (either front or back). I know 4g won't work. But I'm hoping I can get a basic build working and then go from there.
chuckhriczko said:
Yessir. At work now but as soon as I get home I am going to recompile my AOSP build for the Evo and pray that it works. As Maejrep said I don't expect the camera to work (either front or back). I know 4g won't work. But I'm hoping I can get a basic build working and then go from there.
Click to expand...
Click to collapse
I appreciate it! However, it sounds like the same things will be broken in that build as the Froyo build. Kind of disappointing, since I at least want the rear camera working. I don't care about MMS/4G/front cam.
TheBiles said:
I appreciate it! However, it sounds like the same things will be broken in that build as the Froyo build. Kind of disappointing, since I at least want the rear camera working. I don't care about MMS/4G/front cam.
Click to expand...
Click to collapse
Well we will just have to see. That's the thing. The cam theoretically should work however we don't know yet. With the front cam and the HD recording you never know what they did to the libraries. I've been thinking and I don't see why it won't work. I guarantee you 4g won't work off the bat. We might be able to hack that in though.
chuckhriczko said:
Yessir. At work now but as soon as I get home I am going to recompile my AOSP build for the Evo and pray that it works. As Maejrep said I don't expect the camera to work (either front or back). I know 4g won't work. But I'm hoping I can get a basic build working and then go from there.
Click to expand...
Click to collapse
If you need any help testing, feel free to contact me. I am very interested in an AOSP ROM, and I'd be more than happy to help out.
Any update on this, guys?
Related
I've been doing a lot of work recently on getting the camera working on eclair by building the source code to libcamera.so from the parts of the source that were released with the donut drop, then forward-porting the code to eclair.
The result is: http://img37.imageshack.us/img37/6428/20100108232729.jpg (that's the eclair camera app running on my G1 photographing my ugly mug ).
Right now, preview, auto-focus, and taking pics works. Recording video currently crashes the phone. Since this can't easily be dropped into most existing ROMs since the default eclair configuration loads a hard-coded camera stub, and will not load a camera driver. I should hopefully have the last remaining bugs worked out soon and be able to release an alpha version to ROM devs to incorporate into their ROMs.
The source is now available at: http://gitorious.org/eclair-camera-drivers and ready for integration into various ROMs. Please report any bugs encountered.
I'm excited to see this, if you can get the bugs worked out I will bow before you
NCommander said:
I've been doing a lot of work recently on getting the camera working on eclair by building the source code to libcamera.so from the parts of the source that were released with the donut drop, then forward-porting the code to eclair.
The result is: http://img37.imageshack.us/img37/6428/20100108232729.jpg (that's the eclair camera app running on my G1 photographing my ugly mug ).
Right now, preview, auto-focus, and taking pics works. Recording video currently crashes the phone. Since this can't easily be dropped into most existing ROMs since the default eclair configuration loads a hard-coded camera stub, and will not load a camera driver. I should hopefully have the last remaining bugs worked out soon and be able to release an alpha version to ROM devs to incorporate into their ROMs.
Click to expand...
Click to collapse
Well..hmm..what else can i say but fantatic?
And thanks-a-million
nice work!
omg...this is huge...thxxx!! cant wait to have camera working on eclair
great job
many tnx to what you've done
and many more tnx to come during ur time on debugging things.
Good work. I can't wait until you perfect it.
Good job now lets keep the focus and i think its all just a matter of time. I can feel it.
So happeeee!!
Wow, NCommander, that's a hell of a thing. Thanks for making the time to tackle this!
You can't be too excited seeing this! THX a lot! Please just keep on!
HA.... thats awesome.. great job. cant wait till some devs get in contact withyou and start putting some eclair camera roms out there.
im just fine with no video right now. my mt3g is a pitty with no cam.
Best news yet! I'm personally happy!
That's brilliant! Do you think it might work on Android 2.1 as well?
Let the good times roll!
Show me the drivers!!!Show me the drivers!!!we waiting NCommanderthank you for your hard work...
Awesomeness, you tha bomb diggity yo.
THANK YOU! once its on, im upgrading from cyanogen to xROM or whatever 2.x that has the cam.
Awesome!
The lack of a camera is the only thing keeping me from running an eclair ROM full time.
I'm hoping this gets sorted before everyone abandons ship for the Nexus One and Droid and the-next-cool-phone.
I have an HTC Magic 32B. Hope it will work on the Magics.
Will this work on sapphire 32b?
BTW great job!
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
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.
How come it's so hard for devs to get the camera to work along with the HDMI? I mean (keep in mind I have no idea how to do this and am just beginning to learn how to program with Python) couldn't they just copy the set of code from a seperate ROM and put it into their ICS ROM to get it working?
(Just for the record, I'm talking about the Motorola Triumph.)
Whatever, if anybody could just explain why (if you could keep it simple, that'd be a plus too) that would be great. Thanks in advance!
The main problem is due to kernel source which controls the hardware. Without this it can be very hard to get things to work. The same for the HTC inspire. The camera is done with dirty hacks and not completely as the camcorder really doesn't work well and won't until we get the kernel source for the ICS update. This is the main reason I am getting a nexus and not dealing with it anymore
sent from my cell in Arkham