running imilkas aosp v07 and have noticed that when i tether to my mbp it downloads suuuuper slow, on stock it used to fly. anyone know how to fix this?
a detailed response would be awesome as im pretty new to the custom rom game.
proably because stoick was gingerbread with fully written driverts for the device and the ICS is a leak and has hacked drivers etc to make it work on the device, there is no guarantee its going to be the same until samsung release ics
thanks for the input mate but i doubt there's no way to rectify it without waiting for official ics. otherwise it would be listed as a bug...which its not.
Related
Hi folks,
This is a noob question. I am unable to find any post related to stock Froyo for Galaxy S. Is something like this out yet ?
By stock I mean, Android as Google release it, without any reseller trash on it.
Thanks in advance
there is no froyo for SGS yet, at least not officially
much less a stock froyo
there are tons of phone killing Beta froyos if you feel brave
Thanks for letting me know. I am not confident yet in any beta out there, although a lot of phones are using it without any issue...
Hoping that stock will be released soon.
Thanks
It won't (be released soon).
Currently there are community efforts going on to try and get stock 2.1 run on the SGS but they still have a way to go.
After that, once samsung releases the sources for 2.2 they can start trying to get a stock 2.2 running. They have to wait for Samsung because of drivers and such.
Hoping that what they've learned from 2.1 can largely be reused there's a good chance a stock/AOSP 2.2 ROM could make it's way relatively fast to the SGS but for now, don't hold your breath.
Ladduro said:
Hi folks,
This is a noob question. I am unable to find any post related to stock Froyo for Galaxy S. Is something like this out yet ?
By stock I mean, Android as Google release it, without any reseller trash on it.
Thanks in advance
Click to expand...
Click to collapse
I really don't think it can ever be called stock. All releases have to be configured and customised to the platform they are running on. With Linux or Windows it is all on the disk and web server, drivers etc etc. You cannot do this with phone firmware as the download would be huge.
And just like Windows or Linux there are some stock programs that each will install. So what can we call "stock"? Even the Nexux 2.2 has to be configured to it.
By stock/vanilla Android, I meant of course a modified one that includes drivers for SGS, but does not include any customer UI made by Samsung.
So stock UI, no additional garbage (iPhone garbage style in SGS case) would be what I really need to see on my phone.
Or maybe a faster way for this is to modify current Samsung ROM and remove TW and Samsung's apps.
Thanks
Ladduro said:
By stock/vanilla Android, I meant of course a modified one that includes drivers for SGS, but does not include any customer UI made by Samsung.
So stock UI, no additional garbage (iPhone garbage style in SGS case) would be what I really need to see on my phone.
Or maybe a faster way for this is to modify current Samsung ROM and remove TW and Samsung's apps.
Thanks
Click to expand...
Click to collapse
Have a look in the Dev threads. There are several Roms that do that.
Hi Tehpriest,
Can you route me to a ROM mentioned by you ? I searched but in vane... no result.
Thanks
+1. Have been seeking a stock UI-based ROM for i9000T for a while now, with no luck.
Cheers!
There seems to now be some skilled developers starting to get Cyanogen 6 (a vanilla version of Froyo) onto the Galaxy S. Assuming they get it running - which I think is likely when Samsung release the source for their spin on Froyo - it will take a while before it's stable and fully featured.
There's a steep learning curve for working out how to backup then flash your phone with a new rom. It took me three days to go through forum posts working it out, and I've now got a beta version of Froyo working fine. My advice is to get Samsung's official upgrade Froyo when it's out and wait until the devs get a chance to get something better running.
Also, use 'Launcher pro' from the market to replace Samsung's launcher, which makes things a whole lot more familiar.
official froyo is out, the wait should be shorter now
I am hoping too for this. I really like to benefit of OOB Android experience as Galaxy S is my first android phone.
Looking forward to see if it... hopefully soon.
wasnt CyanogenMod working on a release for the galaxy s?
Hey guys, been out of the loop for a while as I've been settled on JPY for a few weeks now. However, I saw a friend flash his Desire today with Oxygen, a gingerbread-based AOSP ROM. All the SGS ROMs I can find so far are based on the stock Samsung firmware - is there any work being done on a full AOSP ROM like Oxygen or Cyanogen? I can't find any details about this anywhere.
I am very curious about this question. Because if answer is simply no, it's time to sell Galaxy S. Gingerbread will be the last update from Samsung and AOSP could be the future of this phone then CM7 for SGS seems to have big problems and it's the only AOSP ROM for SGS which I'm aware of...
What big problems?
I'm using CM7 for a month right now and it's pretty stable if i can say. Yes, it lacks some features and some bugs are not fixed yet (theres a workaround tho), but if you follow it's thread the progress they make are great. They're already into mainline, so probably it will reach RC status in a month/maybe less, who knows.
After the devs are done, i think there will be a custom ROM based on CM7/AOSP.
~drz
CM7 is getting there. And with Gingerbread coming out, that should make things easier for the dev.
Yes, but with no source then there is nothing big. GB leak, only helped them with "less" important stuff (FM radio, etc.)
~drz
If we have CM7 and kernels for 2.3, and leaks of 2.3 from the i9000 and are able to use gingerbread base from nexus s ( think thats what cm7 uses? i cant remember...so if its wrong just insert name of correct phone back there), why is it that we havnt seen anything other than Cyanogen mod and MIUI (which doesnt even count cause its still just the CM7 base) on the 2.3 homefront? I am by no means complaining, just kind of confused. I would think that devs would be chomping at the bit to get their hands on 2.3 for their phones and start their rom modding magic. Anyone have some insight on this other than some sort of sarcastic remark or derogatory comment? lol
we only have the aosp source. and with that why port a basic aosp rom if you can have cyanogen? also there is miui. these are probably the most requested roms on any android version on any phone. an m9 port would be nice but i think the devs that can make the aosp ports better are part of these two projects. so rather than waisting time porting aosp and doing something original and asking the cm7 guys how they fixed this or that they are helping the cm7 and miui projects. also there are still problems and limitations with cm vs samsung. cm7 cant use the camera to it's full abilities. also samsung music player supports more codecs. plus the samsung roms are easier to port allowing time to work on features and tweeks. the reason the i9000 gingerbread hasnt bee built into a captivate rom is that without kernel source the roms would not be as functional as a 2.2.1 port or even cm7 because they would have problems reorienting the sensor mapping and remapping the headset. when samsung source drops there will be much more gingerbread roms and when cm7 is official there will be spinoffs
No source, no kernel, no ROM.
Sent from my Captivate
I am using Samsung Galaxy S android version 2.2, I want to update it to Ice Cream Sandwich 4.0 or which ever is available. I read the instructions but I did not understand anything from it. I am doing it for the first time so I want to know step by step details or if there is any video. I also want to know few things
1- Will android market work
2- Will the phone have lags or speed get slower in the video it did not but I want to know.
3- Will I get all feature of Ice Cream Sandwich
4- In future if company releases 4.0 for galaxy s can I roll back the changes and turn it back to the original version which was there and if yes then how??
I have never tried such thing so I want to be sure before I do it. It looks pretty good in the video.
Firstly, welcome to xda. There currently isnt a proper samsung version of ICS for the galaxy s. What there is are several custom roms people have made based on ics, which if you read through their posts you will see that most of them still have issues and/or bugs. If you check this out http://forum.xda-developers.com/showthread.php?t=1363593 these guys are getting closer every time to a full working version of ics for the galaxy s.
So, choices for you are wait until samsung release a full version of ics (which looks very doubtful) or flash the afore mentioned ics rom or flash a different rom that takes your fancy. Myself I am flicking between this http://forum.xda-developers.com/showthread.php?t=1344489 (my current rom) and saurom.
Once you decided what you wanna do, then let us all know and we will guide you in the right direction.
My advice is to stay on samsung based ROMs for now. ICS ports are still alpha, although some people are using them for everyday. On the other hand, most GB XXJV? and XWJW1 roms are running quite fast on the Galaxy S. Coming from 2.2 you will see a big difference going into 2.3.6.
My personal choice is SURFACE v8 (http://forum.xda-developers.com/showthread.php?t=1155776) with the IceCreamS theme (http://forum.xda-developers.com/showthread.php?t=1386990).
Good luck!
I would like to knw when the full working version of ICS is available so tht before I update I could assure myself being safe to update the phone. I am not waiting for Samsung update but I want a proper Rom which suits the phone
Samsung said it won't be releasing any official ICS on Galaxy S. So all ICS work is made by dev teams, using the ICS source code and ICS releases on similar hardware (Nexus S). Most (all?) ICS ROMs are based in teamhacksung ICS port. You can see them in the Development forum (OneCosmic, Surface v1, MyICS, ...)
Some devs will say that their roms are release-candidate, finished or even official, but be careful with this, the teamhacksung port is in alpha stage (build 11) (http://forum.xda-developers.com/showthread.php?t=1363593). Moreover, there is no public roadmap for an official version and the devs don't like to be asked on ETAs.
I suggest you to read that thread to see what is and is not working in each build. Also, you can get answers to most of your questions (except ETA) on the CM9 discussion thread in this forum (http://forum.xda-developers.com/showthread.php?t=1387937).
SO Is it safe now to update with current available roms or to wait till the final version releases without any bugs becoz I hv gone thru Q&A dept and der are lots of complains sleep problem headset recognition problem and many more
skhan33 said:
SO Is it safe now to update with current available roms or to wait till the final version releases without any bugs becoz I hv gone thru Q&A dept and der are lots of complains sleep problem headset recognition problem and many more
Click to expand...
Click to collapse
Given that you have no experience flashing custom ROMs, I would also have to suggest avoiding the alpha ICS builds right now. Things will probably go wrong, whether majorly or minorly, that you aren't accustomed to dealing with.
Wait until a stable version is available, or at the very least a beta. However, in the mean time, I would definitely recommend flashing to 2.3.6. As someone else already mentioned, it will be a nice upgrade over 2.2, and it's an easy way to learn the basics of flashing ROMs.
Good luck!
First get to Gingerbread and then go for ICS if you really want to.
Hey everyone,
I'm starting development on the android OS (Stage3d/air3.3)
I would like to do some on-device testing as the emulators are not displaying my work (haven't determined the problem yet..blank white screens)
I've gotten my hands on a Rogers Samsung Captivate (fresh brand new out of the box).
I believe its on android 2.3.
I would like to upgrade it to one of the newer roms (4.0 or 4.1) so that way i can work with one of the newer environments.
I've seen some guides on how to do it (dont need help here..forum search function worked well for that), but i am flooded with rom choices.
Does anyone have a suggestion for a ROM I can use that will allow me to do my testing where i wont run into bugs related to the ROM? i prefer that the only bugs i run into are related to my coding and not the rom.
Would be much appreciated, thanks in advance.
Clarification: this device will only be used for testing my app/games development and not the other fancy things i can do with android. for example..
-skype video being green would not be a bug that concerns me..
-but wifi not working may be a bug that concerns me.
-my app displaying green due to a ROM bug would be a concern
Just go with Paranoid Android or Helly Bean
x9x9x9x9x9 said:
Just go with Paranoid Android or Helly Bean
Click to expand...
Click to collapse
[email protected] names.
thanks alot. i will compare the two and make a decision much appreciated
Aocp 2.1 ics is very stable, as is slim ics. Bugs are still being worked out of the jelly bean 4.1 ROMS, so maybe wait a little for those.
wwcjr91 said:
Aocp 2.1 ics is very stable, as is slim ics. Bugs are still being worked out of the jelly bean 4.1 ROMS, so maybe wait a little for those.
Click to expand...
Click to collapse
thanks alot, i havent chosen yet, so i will consider these two as well. much appreciated
I've decided to go with [ROM] 4.0.4 - ICS - AoCP CP 2.1 - The Collective {8/14/2012]
seems smooth so far, will be testing out loading of apps tomorrow.
thanks alot guys. hopefully ill be able to upgrade to 4.1 when the bugs seem to be worked out