Hope i can ask it here and not in general.
I read, a Gingerbread AOSP isn't possible because of missing drivers.
But what about a Froyo port? Drivers could maybe extracted?
Couldn't this fix all the strange lags, etc which still exist in Modaco ROM (ok, the ROM is absolutely grate compared to original LG crap), but still suffers some strange lags (e.g. selecting a widget,.)
Thanks for an answer
Related
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
Hi,
Does any one know which Android Version Samsung OFFICIALLY fixed the stalling/lag issue for the SGS i9000? Is it even officially fixed?
Just that I'm recommending a phone for someone I'm not too close with and dont feel like loading on CM7 for a stranger
Searching only gives me millions of results for One Click and Voodoo solutions. I don't want to tell this person to go through these steps.
Thanks!
2.2.1 is pretty smooth and fast. 2.3.3 also, but there are issues with battery life and stuff that can be fixed but require knowledge. So, I think 2.2.1 ROMs are the best option for someone who doesn't want to deal with custom roms and kernels and rooting. Of, course a custom rom and kernel or just a custom kernel can make the phone not just smooth but blazing fast.
Hm, can you confirm that the Stallling issue is actually fixed from 2.2.1 onwards?
Specifically the problem when you click Market/Market > MyApps/Maps/Contacts and it takes ~30 seconds for it to load.
I'm not too concerned general chipiness/lack of finger-tracking smoothness.
Sorry for the paranoia , just that i hated the stalling before I was on CM7.
Officially? None. Samsung have repeatedly announced that users of their latest updates "will experience smoother performance".
They announced that with 2.2 and 2.2.1 and I'm on JVH and can confirm even JVH benefits from not running on the rfs filesystem. Yet they've never acknowledged a specific issue that creates lag, even though everyone on this forum knows exactly why and how to fix it.
Actually all stock samsung Roms run on rfs file system including the 2.3.3 ones (which means JVH too). The problems you're talking about are generally fixed by changing the file system from the stupid samsung's rfs to usual linux ones - ext4 or ext2 (ext 2 makes it extra quick in the GUI coz it quite improves the read-write speed) - everything opens immediately. Just stock 2.2.1 with changed file system will make the phone open the things you're talking about right away
Thanks for the replies.
So basically the problem exists for all Samsung ROMs, just to a lesser extent from 2.2.1 onwards. As proven by http://www.youtube.com/watch?v=g1B2fstyrRA, 2:13 mins. How annoying!
Hm, not sure i can reccommend an unhacked SGS
I would say 2,2,1 usable without any lagfix ,
Before needed a lag fix .
But ten million users on 2.1 dont know what needs fixing lag whats that ???
SGS 2 no lag .
jje
Let me start by saying Thank you to any developer making these things possible. I'm enjoying my phone more then before!
We get used to take fast pictures on our phone's... For every little nonsense...
It's a thing we expect on our phones we buy these day's.
I am having issues with CM7 to get the camera working and i saw somewhere they have removed the camera from their rom.
Now, Froyo has the cam working but the speed of my phone is very slow with Froyo. I like CM7 for it's simplicity and speed and ofc it's way better then that crappy stock rom that come's with the X8.
Now for my questions;
Why did Cyanogenmod remove support for the camera?
Why does it work in Froyo and not in Cyanogen?
And, if possible, could i speed up Froyo by overclocking or tweaks?
Froyo cant run some of my app's like swiftkey x for example...
Do i have to make a choice between speed/camera?
Thank you!
(sorry for bad grammar, English isn't my first language .)
Why did Cyanogenmod remove support for the camera?
The CyanogenMod by FreeXperiaTeam is being built from sources, which means they are writting all drivers from nothing, not just modifying them from some other ROMs. As Sony Erricson didnt gave FXP camera drivers so they couldnt finish up that ROM. They also droped a support for our X8 as well as for X10 mini/pro because of their old hardwer.
Why does it work in Froyo and not in Cyanogen?
Froyo that our X8 has is also custom ROM based on CyanogenMod but version 6. For a long time we hadnt had working camera on Gingerbread based ROMs. The thing is developers used patched Stock 2.1 drivers in Froyo and that wasnt possible until our great dev Doixanh managed to patch that drivers to work on 2.3 (Gignerbread) as well.
And, if possible, could i speed up Froyo by overclocking or tweaks?
Of course you can. But I would sugest you to install GingerDX by Doixanh. It is fully working and really smooth CM7 ROM and it will even run on stock kernel.
Froyo cant run some of my app's like swiftkey x for example...
Probably because they are not compatible. Using older versions might solve that problem.
Do i have to make a choice between speed/camera?
GingerDX.
Godra said:
Why did Cyanogenmod remove support for the camera?
The CyanogenMod by FreeXperiaTeam is being built from sources, which means they are writting all drivers from nothing, not just modifying them from some other ROMs. As Sony Erricson didnt gave FXP camera drivers so they couldnt finish up that ROM. They also droped a support for our X8 as well as for X10 mini/pro because of their old hardwer.
Why does it work in Froyo and not in Cyanogen?
Froyo that our X8 has is also custom ROM based on CyanogenMod but version 6. For a long time we hadnt had working camera on Gingerbread based ROMs. The thing is developers used patched Stock 2.1 drivers in Froyo and that wasnt possible until our great dev Doixanh managed to patch that drivers to work on 2.3 (Gignerbread) as well.
And, if possible, could i speed up Froyo by overclocking or tweaks?
Of course you can. But I would sugest you to install GingerDX by Doixanh. It is fully working and really smooth CM7 ROM and it will even run on stock kernel.
Froyo cant run some of my app's like swiftkey x for example...
Probably because they are not compatible. Using older versions might solve that problem.
Do i have to make a choice between speed/camera?
GingerDX.
Click to expand...
Click to collapse
Thank you, sir!
I've just installed GingerDx v022-update.zip as a custom zip over CM7. Camera has small problems but that isnt a big issue. Menu is fast enough.
Even swiftkey is working on Ginger while i got massive error's using it with Froyo.
I think ill stick to GingerDx. Thanks for the info!
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.