Related
http://www.engadget.com/2010/03/10/htc-legend-already-trickling-into-customers-waiting-hands/
so it seems some people are getting these phones early now if im correct this phone runs android 2.1 with sense. maybe someone who gets one of these can get us a dump for the devs.
I've had the whole ruu for a few weeks and ported it to work. It's basically the same as the 2 2.1 roms everyone is building from now. Other then fm radio that we already know won't work on our devices. The legend builds are also older builds then the Eris build I ported. The heroc build fresh released with the .29 kernel is actually newer then the Eris build by one day. And the most current build of 2.1 I've found. The only reasons I haven't released the legend build. Is for one we have newer builds and two it has issues with our speaker and Mic. The build is exactly the same as flipz heroc build. So were not gonna gain much from building off of if. It's also a gsm build that will need a lot of fixing to be as functional as the current newer builds. In my opinion its not worth the time to port something older then the current builds.
toastcfh said:
I've had the whole ruu for a few weeks and ported it to work. It's basically the same as the 2 2.1 roms everyone is building from now. Other then fm radio that we already know won't work on our devices. The legend builds are also older builds then the Eris build I ported. The heroc build fresh released with the .29 kernel is actually newer then the Eris build by one day. And the most current build of 2.1 I've found. The only reasons I haven't released the legend build. Is for one we have newer builds and two it has issues with our speaker and Mic. The build is exactly the same as flipz heroc build. So were not gonna gain much from building off of if. It's also a gsm build that will need a lot of fixing to be as functional as the current newer builds. In my opinion its not worth the time to port something older then the current builds.
Click to expand...
Click to collapse
The one thing i saw on the vids, of note, was the browser's enhanced text selection features (think it had translate, wikipedia, n some other stough whenever you select text)..is that something port-able?
KERKEDAGAIN said:
The one thing i saw on the vids, of note, was the browser's enhanced text selection features (think it had translate, wikipedia, n some other stough whenever you select text)..is that something port-able?
Click to expand...
Click to collapse
i didnt see that in it. ill boot it up tonight sometime and check.
had no idea it was gsm lol oh well. i just keep hopin to get ahold of that friend stream widget lol
too bad it's gsm. that's a sharp looking phone.
ya it sure is the unibody and all would be nice and the optical trackball
that was in the build also. lol ok fine ill fix audio and make a build it wont be tonight though. i gotta have some time. been working on this aosp multitouch issue. i dont use aosp but i want to know those who do dont have to suffer without a camera
nbroneobi said:
ya it sure is the unibody and all would be nice and the optical trackball
Click to expand...
Click to collapse
http://www.droiddog.com/android-blog/2010/03/pershoots-2-6-32-kernel-tutorial/
did u see this to bad its gsm as well lol
toastcfh said:
that was in the build also. lol ok fine ill fix audio and make a build it wont be tonight though. i gotta have some time. been working on this aosp multitouch issue. i dont use aosp but i want to know those who do dont have to suffer without a camera
Click to expand...
Click to collapse
let me ask you this, why put all the effort into this 2.1 port when the official update will be coming soon and then you will have to make another rom but fully functional already.
no offense, just seems like it's kinda pointless when we have the update coming this month.
toastcfh said:
that was in the build also. lol ok fine ill fix audio and make a build it wont be tonight though. i gotta have some time. been working on this aosp multitouch issue. i dont use aosp but i want to know those who do dont have to suffer without a camera
Click to expand...
Click to collapse
if i wanted aosp i would of gotten anything besides a hero but the interface seemed so much nicer with sense it really was the whole decision for me with sense on this phone.
to me the biggest reason for continuing all these 2.1 roms. when the official comes out whenever its suppose to to me is that once the official actually does come out its alot easier to work with since the dev's are familiar with it
nbroneobi said:
if i wanted aosp i would of gotten anything besides a hero but the interface seemed so much nicer with sense it really was the whole decision for me with sense on this phone.
Click to expand...
Click to collapse
well your not everyone
fixxxer2008 said:
let me ask you this, why put all the effort into this 2.1 port when the official update will be coming soon and then you will have to make another rom but fully functional already.
no offense, just seems like it's kinda pointless when we have the update coming this month.
Click to expand...
Click to collapse
well just because we have a sprint 2.1 build doesnt mean we will get what all other buildsa have. we may not get friendstream and if thats the case then we will need new frameworks to support it. once sprint releases 2.1 doesnt make it the end of the road for porting other builds. one build may have some new function built into it. take espresso for example... its ui was totally different then any other. then we move on to other builds. some dont include certain htc apps. its almost like htc has a catalog with a gang load of options. the carrier or buyer may not wanna pay for a colorful ui they may only want it gray scale like eris is. or they may want all the colored icons like flipz's build and legend. every build is different. beleive this as soon as sprint gives us a 2.1 build. it will be extreamly simple to make an update.zip of it. no porting required at all. at this point i only want sprint to release because then that means we will get kernel source for .29. at that point if we already havent ported it ourselves(like last time) we can move on to bigger better things. but... as ive already seen were gonna need source for some of these new builds. our device is old and needs more space. so were gonna need to compile modules to squash the system down to a usable size and use other modules like ramswap and such to make up for or lack of hardware. were being outdated fast. android is finally developing into something to kick the other os's asses.
ps i do stuff to help everyone. whether i use their builds or not.
I am wondering about something concerning the new trackpad replacing the trackball in these new devices. How is this haedware switch going to affect recovery (if at all)? I mean will just "tapping" the trackpad work just as pushing the track button. Just something to think about.
troyboytn said:
I am wondering about something concerning the new trackpad replacing the trackball in these new devices. How is this haedware switch going to affect recovery (if at all)? I mean will just "tapping" the trackpad work just as pushing the track button. Just something to think about.
Click to expand...
Click to collapse
well when u boot into recovery. it loads ur kernel and all of its drivers. im sure that it can be made aware of a trckpad if its not already.
I love the build of the device but after the hero I don't think ill settle for a inferior processor again especially after reading the reviews.
some people prefer aosp to sense. when i first bought the phone i liked sense but honestly after a few months i found that sense isnt worth the space its code takes up.
@toast
does the legend Rom have FriendStream and NewsReader?
I have been trying to get these to run under fresh 2.0 but it just will not work
zippy-man said:
@toast
does the legend Rom have FriendStream and NewsReader?
I have been trying to get these to run under fresh 2.0 but it just will not work
Click to expand...
Click to collapse
hey don't mean to step on toasts toes or anything but ya i've tried to install the friendstream apk from a few different 2.1 apps and its a no go and im not sure why but as of now and from what i have seen they don't work
I'm a fr00b
Feel free to... scold me
andershizzle said:
I'm a fr00b
Feel free to... scold me
Click to expand...
Click to collapse
hah, good question. I'll cover the basics you can do the rest of the research, essentially CM6 is a customer Rom, (stands for Cyanogenmod version 6) for android devices. You can learn more by visiting cyanogenmod.com
<opinion>
Also, cyanogenmod would happen to be my favorite custom rom, a lot of extra features are included, its pretty well optimized and you can expect updates often. I've personally used Cyanogen on the Mytouch and Nexus one, and I can't wait to see a version on the Vibrant, once an official stable version comes out, you can probably expect Android 2.2 and a lot of optimizations that would may the vibrant what it should have been on launch day.
</opinion>
Also I hate to throw this in, being a fairly new poster and all (and not being a mod) but I believe that this thread would belong in the vibrant general forum as opposed to the dev forum. Just a heads up so you don't get flamed in the future
andershizzle said:
I'm a fr00b
Feel free to... scold me
Click to expand...
Click to collapse
Don't worry, we won't scold you. It's not your fault being new and all.
http://wiki.cyanogenmod.com
I just wish you would realize that your question is for general section
stillyone said:
I just wish you would realize that your question is for general section
Click to expand...
Click to collapse
Helpful post, alludes to something I remember mentioning
@andershizzle: if you do decide on running any roms such as CM6, the best tip that can be offered is to make sure you understand what you are doing and read any instructions carefully before you proceed, and make sure you understand the instructions too. Remember to ask for help before doing something that might turn your phone into a $500 paperweight (or in the vibrants case its more of an expensive decoration since I wouldn't trust it to hold down paper. It'd probably blow away too.)
Aphotix said:
Helpful post, alludes to something I remember mentioning
@andershizzle: if you do decide on running any roms such as CM6, the best tip that can be offered is to make sure you understand what you are doing and read any instructions carefully before you proceed, and make sure you understand the instructions too. Remember to ask for help before doing something that might turn your phone into a $500 paperweight (or in the vibrants case its more of an expensive decoration since I wouldn't trust it to hold down paper. It'd probably blow away too.)
Click to expand...
Click to collapse
I haven't laughed so loud at any post on XDA as I did with this little comment. Funny, its probably true. LOL!
Aphotix said:
you can probably expect Android 2.2 and a lot of optimizations that would may the vibrant what it should have been on launch day.
Click to expand...
Click to collapse
Not being a 'nit-picker', but CM6 uses 2.2 (froyo). CM5 is 2.1 (eclair) and CM4 was 1.6 (donut). Hmm....now I'm getting hungry.
But yes, I'm definitely looking forward to see CM6 on the Vibrant. Only downside is it will look like the stock CM6 (meaning our Vibrant png's will be replaced ).
Guess I might start working on the replacement Vibrant theme.
Moved to General forum. The development forum is only for development threads. (Threads with actual development happening.)
Questions should always be in the General forums (or Q&A if your device has a Q&A forum.)
MINUS Stl said:
Not being a 'nit-picker', but CM6 uses 2.2 (froyo). CM5 is 2.1 (eclair) and CM4 was 1.6 (donut). Hmm....now I'm getting hungry.
But yes, I'm definitely looking forward to see CM6 on the Vibrant. Only downside is it will look like the stock CM6 (meaning our Vibrant png's will be replaced ).
Guess I might start working on the replacement Vibrant theme.
Click to expand...
Click to collapse
When I'd made the decision to move from my N1 to Vibrant, I was all excited to find out there was going to be a CM for Vibrant. Now, I don't care so much. Vibrant has so many things I was already replacing that it's cut down on my apps somewhat.
I got into rooting for App2SD, and with my Vibrant it just isn't necessary now to run a custom rom. I will miss the undervolting and overclocking, though I sort of hope someone will work on kernels which will work with the stock build. I did a simple root just to use my root apps. Otherwise, Vibrant is pretty good for me.
BTW, this isn't any sort of anti CM post ... I love the work he and his cronies do, and some times I hope that they'll get snapped up by one of the big guys out there. They should be making bank for their talents.
Well I feel like an idiot for posting in the Dev section. Accident. Lmao.
Anyways I've flashed ROMs on a Touch Pro 2 (WinMo *cough*terrible) before so I'm decently familiar with that.
Is CM6 like, Stock 2.2? I'm looking for a stock-as-possible ROM, is that what I should be getting?
Hehe, guess I'll just try it when it comes. But thanks for all info.
Will we be able to install CM6 with ROM Manager?
andershizzle said:
Well I feel like an idiot for posting in the Dev section. Accident. Lmao.
Anyways I've flashed ROMs on a Touch Pro 2 (WinMo *cough*terrible) before so I'm decently familiar with that.
Is CM6 like, Stock 2.2? I'm looking for a stock-as-possible ROM, is that what I should be getting?
Hehe, guess I'll just try it when it comes. But thanks for all info.
Click to expand...
Click to collapse
If you look at his changelog on his site he shows you the common Froyo bits and then shows the bits for different phone types. I would call it a Custom/Stock Hybrid
Pneumatic said:
Will we be able to install CM6 with ROM Manager?
Click to expand...
Click to collapse
From browsing the vibrant forum on cyanogenmod.com it looks like mostly speculation at this point.
davbran said:
From browsing the vibrant forum on cyanogenmod.com it looks like mostly speculation at this point.
Click to expand...
Click to collapse
It's not speculation. There is active development for the Vibrant going on. It's just not far along enough yet for an experimental release.
You can follow wesgarner and scepterr on Twitter for the latest updates since they're heading the Vibrant branch. Wes is primarily focused on the MT3G Slide a the moment though since he promised to work on that one first and it's farther along, but he has also been actively working on the Vibrant too.
I just want CM6 on Vibrant to see Wes work his hiney off
No, not really. But I know he will.
The CM team adds a year to our gadgets. All I really want is to get rid of the stinky calendar app right now, and I can do that without CM6 (4,5 or 7, whatever). In eight months, though, when 1.5 or 2gH processors are selling, some ingenious JIT tweak revolutionizes speed, and/or the size of Google Earth becomes more commonplace, I'm going to want CM. I'm going to want it to be in its ruts, hashed & rehashed. Im not necessarily expecting it, but I sure am gonna want it, and be grateful if it's there for me and my old phone.
The CM team is also willing to try new stuff, and can get a load of people to test it. So Apps2SD started where? Got popular how? It's stock now?
CM is open source, and has got a lot of people using and understanding what open source is. The social aspect of software is all too often misunderstood, or just plain dismissed. XDA-developers has revolutionized software as we know it. We'd all be spoon fed M$ users without this site, and possilby without CM specifically. These guys will be in software history textbooks.
So, I'm working donations into my budget. I'ts much cheaper than buying a new phone every few months, or putting up with stock software on old hardware. I will pay these guys as long as they're willing to work their magic.
(By the way, every once is a while I crack out my old Tmo MDA, just for kicks for a few hours. It works beautifully thanks to a custom ROM. Thinking about giving it to my Mom just so she can have a Tmo "smartphone." I love XDA. I love open source, even when it's not exactly.)
Its runnning lightning fast, just flashed it to see it run for a few minutes, i cbf with stock roms, had enough with my past acer liquid device lol, anyways its an alpha rom like eugene said DO NOT REPORT BUGS, barak and him knows them already, link here: http://forum.xda-developers.com/showthread.php?t=757000 , picture running it on my captivate here: http://twitpic.com/2fri63
wow...hopefully well get a good data and radio from that rodgers captivate
TheTodFather said:
wow...hopefully well get a good data and radio from that rodgers captivate
Click to expand...
Click to collapse
Wtf are you talking about? if your thinking roger will release a clean stock rom, im sorry to say this but its not going to happen, it will be themed just like all the other SGS variants also same samsung apps etc..
rafyvitto said:
Wtf are you talking about? if your thinking roger will release a clean stock rom, im sorry to say this but its not going to happen, it will be themed just like all the other SGS variants also same samsung apps etc..
Click to expand...
Click to collapse
I think he meant the radio. Since att crippled our radios uplink speed. (Hsupa disabled). Could be wrong. But i think that's what he meant.
jasonyump said:
I think he meant the radio. Since att crippled our radios uplink speed. (Hsupa disabled). Could be wrong. But i think that's what he meant.
Click to expand...
Click to collapse
Oh yeah, the radio should be usefull to us.
rafyvitto said:
Wtf are you talking about? if your thinking roger will release a clean stock rom, im sorry to say this but its not going to happen, it will be themed just like all the other SGS variants also same samsung apps etc..
Click to expand...
Click to collapse
Was it necessary to be ugly?
I apologize for not explaining myself thoroughly.
No I was referring more to getting a dump off the rodgers captivate so we can get that firmware that only Rodgers releases and hope that hsupa is enabled. Because regardless of roms this captivate has been an awesome phone but what ATT did to this is unjustified and borderline illegal. Those @ssholes farked this phone up real good and it going to be awesome to get this thing free and 100% up and running.
Back to the them of this topic...
Vanilla rom would be nice as long as there is no att restrictions and this phone is 100% free .
TheTodFather said:
Whats it necessary to be ugly?
I apologies for not explaining myself thoroughly.
No I was referring more to getting a dump off the rodgers captivate so we can get that firmware that only Rodgers releases and hope that hsupa is enabled. Because regardless of roms this captivate has been an awesome phone but what ATT did to this is unjustified and borderline illegal. Those @ssholes farked this phone up real good and it going to be awesome to get this thing free and 100% up and running.
Back to the them of this topic...
Vanilla rom would be nice as long as there is no att restrictions and this phone is 100% free .
Click to expand...
Click to collapse
Yes this is a 100% android stock 2.1 aosp rom, about the rodgers dump, it would be nice to have a look at it, but since there hasn't been any dump as of yet, were gonna have to wait.
do i go back to stock to use this?
Does this work on the captivate
Sent from my SAMSUNG-SGH-I897 using XDA App
This looks sooooo badass.
I just got the stock messaging application and the stock music player on my Captivate, now I see this. If they had data working I would be flashing it right now, but I rely heavily on data so I'll wait for the bugs to be worked out.
I really just hate TouchWiz and can't wait for a real vanilla experience.
Looks sexy, how hard would it be to fix the radio for us to use it? Also has anyone benched this beast?
N!ghtgold said:
Does this work on the captivate
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Did you seriously ask just ask that?
yes it does. as it wouldnt be posted in the captivate section with the OP stating it runs on his captivate, and provided a picture of it running on his captivate.
jasonyump said:
Did you seriously ask just ask that?
yes it does. as it wouldnt be posted in the captivate section with the OP stating it runs on his captivate, and provided a picture of it running on his captivate.
Click to expand...
Click to collapse
Dude he didn't wanna read through the massive amount of posts in this thread (10) or the OP. I don't blame him! (it was hard keeping a strait face while typing that lol)
Now I am definitely interested in this because there is no point in running Touchwiz since it does seem to be pretty buggy and eventhough it is very colorful, I am using the latest launcher pro and prefer it but if I can get vanilla 2.1 running on my Captivate and be running data properly, then I will flash my phone with this.
Cheers,
Charlie
Clienterror said:
Looks sexy, how hard would it be to fix the radio for us to use it? Also has anyone benched this beast?
Click to expand...
Click to collapse
that question + how hard would it be to fix the camera?
i tried to flash this with clockwork. it said install completed, so i rebooted the phone. it booted up normally but after the att screen it just sat at a blank screen for twenty minuts before i nandroided back to what i had before. i NEED this rom on my phone. anyone have any advice
igm503 said:
i tried to flash this with clockwork. it said install completed, so i rebooted the phone. it booted up normally but after the att screen it just sat at a blank screen for twenty minuts before i nandroided back to what i had before. i NEED this rom on my phone. anyone have any advice
Click to expand...
Click to collapse
Did you wiped data/factory reset? Dalvik cache? If not do so and reflash.
thanks ill try that
i tried all that stuff and got same results
What advantage does a Vanilla Rom, have over stock w/Home Screen Replacement?
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?
Never say never lol, Someone will find a way
Heard the same awhile ago with Eclair and Froyo.
This
KoolKidsKlub said:
I'm gonna get a G2 now
Click to expand...
Click to collapse
This
XxKOLOHExX said:
Never say never lol, Someone will find a way
Click to expand...
Click to collapse
And this.
cesarbric said:
Heard the same awhile ago with Eclair and Froyo
Click to expand...
Click to collapse
RAAAAAAAAAGGGGGGGGGGEEEEEEE
Just kidding
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.
Deathwish238 said:
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.
Click to expand...
Click to collapse
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.
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...
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!
bonesy said:
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!
Click to expand...
Click to collapse
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.
AOSP gingerbread running on my Dream..
So seems mostly a go.. will require some poking for a true release but not that bad.
If it's not officially supported in AOSP, does that mean we'll be without camera drivers?
ezterry said:
AOSP gingerbread running on my Dream..
So seems mostly a go.. will require some poking for a true release but not that bad.
Click to expand...
Click to collapse
This is so great!
Sent from my HTC Dream using XDA App
Deathwish238 said:
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...
Click to expand...
Click to collapse
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
AdrianK said:
If it's not officially supported in AOSP, does that mean we'll be without camera drivers?
Click to expand...
Click to collapse
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
MentalDeath said:
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.
Click to expand...
Click to collapse
Honeycomb (Android 3.0 or 2.4....who knows) will not require a 1Ghz CPU.
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?
Deathwish238 said:
Honeycomb (Android 3.0 or 2.4....who knows) will not require a 1Ghz CPU.
Click to expand...
Click to collapse
Alright I shall take your word for it.
protomanez said:
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?
Click to expand...
Click to collapse
People just want to have the newest, and humans like pushing limits (in this case of the G1).
Jurai said:
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
Click to expand...
Click to collapse
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).
protomanez said:
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?
Click to expand...
Click to collapse
(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
So why is it that gps works on 2.2 bland 2.2.1 but not 2.3? Just wonderibg
Sent from my SGH-T959 using XDA Premium App
I believed this is because the devs don't have actual source code yet.
we need drivers and the only way to come about hose would be an official vibrant gb kernel.
Im no expert but... wouldn't a person like eugene be able to make the drivers it would work?
Honestly, how much smarter are the people at samsung than the people on this forum???
I hope that was a joke.. the effort required to develop drivers for GPS without source code is immense for anyone that wasn't directly involved in the software development for the phone, hence no GPS working with 2.3 on the vibrant. The GPS in the i9000 galaxy s isn't the same as the vibrant, and there isn't a 2.3 rom leaked or released for the vibrant. That's why our 2.3 roms don't have GPS functioning.
Sent from my HTC HD2 using XDA Premium App
jwleonhart said:
Im no expert but... wouldn't a person like eugene be able to make the drivers it would work?
Honestly, how much smarter are the people at samsung than the people on this forum???
Click to expand...
Click to collapse
Eugene told the vibrant community to proverbially suck it if I recall correctly.
Sent from my HTC Vision using XDA Premium App
jwleonhart said:
Im no expert but... wouldn't a person like eugene be able to make the drivers it would work?
Honestly, how much smarter are the people at samsung than the people on this forum???
Click to expand...
Click to collapse
That's like me asking you to build an engine from scratch. I mean, you've probably been in a car. You may even know how to drive it. Maybe change out the washer fluid? Fill it up with gas? Maybe even change the oil!
So if you can do all of that, you should be able to design, fabricate, and build a fully functional, great engine from scratch... Right? It's a pretty important piece of a car - sure - but you work with cars every day!
Not trying to be (too much of) an ass here, but really. Coding drivers is a difficult, very time-consuming task. There's a bit of a difference between coding to directly interact with the hardware, and hooking into existing APIs and modifying existing code. Has nothing to do with smarts. It has to do with resources. Easy testing access to the direct hardware. Money. Time.
I don't really know what's involve in the GPS drivers but I would think that if we get the source for 2.2.1 and make it work, it shouldn't be that that to make it work in 2.3. I am missing something here? I wrote up some linux drivers before, it's not exactly a sacred thing.
brulee said:
I don't really know what's involve in the GPS drivers but I would think that if we get the source for 2.2.1 and make it work, it shouldn't be that that to make it work in 2.3. I am missing something here? I wrote up some linux drivers before, it's not exactly a sacred thing.
Click to expand...
Click to collapse
You're missing the point because you're not even seeing what your typing. No we don't have source for 2.2.1 but do you not see those first two numbers. This means that because 2.2.1 is still Froyo we didn't need to update the GPS drivers because they didn't change. Now we are talking about Gingerbread which is 2.3 and a completely new build.
Think of it in terms of windows. When Vista SP1 was released it meant very little when it came to hardware for those already running Vista. Now when Win 7 came out some of you drivers had to be updated. Some things didn't work right off and if you've purchased any hardware in the last 5 years such as a mouse or keyboard you've likely seen the sticker saying Vista compatible or Win 7 compatible.
Does any of this make sense?
Sent from my GT-I9000 using XDA Premium App
How about this for a related and potentially dumb question. What's the technical reason why a vibrant 2.2 kernel couldn't be used with a 2.3 system. In the Linux desktop arena, a huge variety of kernels can be used with a huge variety of userland.
brulee said:
I don't really know what's involve in the GPS drivers but I would think that if we get the source for 2.2.1 and make it work, it shouldn't be that that to make it work in 2.3. I am missing something here? I wrote up some linux drivers before, it's not exactly a sacred thing.
Click to expand...
Click to collapse
then you should have no problem getting us gps on 2.3...
funeralthirst said:
then you should have no problem getting us gps on 2.3...
Click to expand...
Click to collapse
I would just like to say that you have made my morning. Thank you. ===================================================
explodingboy70 said:
You're missing the point because you're not even seeing what your typing. No we don't have source for 2.2.1 but do you not see those first two numbers. This means that because 2.2.1 is still Froyo we didn't need to update the GPS drivers because they didn't change. Now we are talking about Gingerbread which is 2.3 and a completely new build.
Think of it in terms of windows. When Vista SP1 was released it meant very little when it came to hardware for those already running Vista. Now when Win 7 came out some of you drivers had to be updated. Some things didn't work right off and if you've purchased any hardware in the last 5 years such as a mouse or keyboard you've likely seen the sticker saying Vista compatible or Win 7 compatible.
Does any of this make sense?
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Thank you for your answer @explodingboy. I know when there is a new version of OS, most if not all drivers have to be ported over. You actually answer my question though -- you don't even have source for 2.2.1!
P.S. I am new on this forum and there is some rule here that I have to wait 5 minutes to edit my post. :-(
Captivate must've gotten their leak because their GPS works
dcontrol said:
Captivate must've gotten their leak because their GPS works
Click to expand...
Click to collapse
On 2.3? Can you post a link to this as proof?
Sent from my SGH-T959 using Tapatalk
dcontrol said:
Captivate must've gotten their leak because their GPS works
Click to expand...
Click to collapse
The captivate users are lucky in that their GPS works with the i9k files. Its been that way for most if not all of the i9k 2.2.1 roms from Samsung.
Sent from my SGH-T959 using XDA App
geoffcorey said:
The captivate users are lucky in that their GPS works with the i9k files. Its been that way for most if not all of the i9k 2.2.1 roms from Samsung.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I honestly don't get this. Hardware wise (excluding supported bands) the captivate and the vibrant have the same gps chip. The only difference is software wise: the vibrant uses one software/driver implementation, the captivate another (Which honestly makes no sense.....). In *theory*, the drivers/software implementation should work with our gps chip. Correct me if I'm wrong (Note: I've used the plumbob gps fix for the captivate with some success on the vibrant).
compuguy1088 said:
I honestly don't get this. Hardware wise (excluding supported bands) the captivate and the vibrant have the same gps chip. The only difference is software wise: the vibrant uses one software/driver implementation, the captivate another (Which honestly makes no sense.....). In *theory*, the drivers/software implementation should work with our gps chip. Correct me if I'm wrong (Note: I've used the plumbob gps fix for the captivate with some success on the vibrant).
Click to expand...
Click to collapse
its probably because the north korean samsung made the vibrant and the south korean samsung made the captivate and you already know they dont get along.
Re
Here's the confusing thing for me, we had gps for 2.2 after eugene made it work with the leak from the i9k. So now that we have a 2.3 release from Samsung what makes it different. Did gingerbread somehow make gps different. My point is that when we were first getting 2.2 roms gps came quick.
edit: Im not complaining just curious.
compuguy1088 said:
I honestly don't get this. Hardware wise (excluding supported bands) the captivate and the vibrant have the same gps chip. The only difference is software wise: the vibrant uses one software/driver implementation, the captivate another (Which honestly makes no sense.....). In *theory*, the drivers/software implementation should work with our gps chip. Correct me if I'm wrong (Note: I've used the plumbob gps fix for the captivate with some success on the vibrant).
Click to expand...
Click to collapse
Totally agreed with your assessment! There must be some hardcoded data for the Asian built version vs. North American. Would a binary diff give us some hints? But then if you don't have the source, you can't rebuild the damn thing!