Hello guys, I've recently upgraded from a Galaxy Nexus to a Galaxy S III, skipping the Nexus 4 for reasons I should explain only if asked.
I've been reading a lot of posts from AOSP advocates defending Samsung's TouchWiz, which makes for a rather worrying reading.
Now, I'm quite pleased with stock TW Jellybean, it's really smooth, fast, stable and not bloated at all. However, I wanted to try some AOSP roms since developers clearly had some time to work on them, and Samsung has certainly released JB source code to overcome some driver-related issues that there might have been. My question is: is TW still the best option or are there some AOSP roms that are stable, fast and working on every aspect? I'm talking about tethering, data connection, auto-brightness, battery life, bluetooth, camera... the stuff meant to work at its best on a stock TW rom.
Thanks for your help.
Well actually for me the AOSP ROMs are smoother and have all the features I could probably need....but
Samsung didn't released the sources as they told us and because of that (and a couple of proprietary reasons with Microsoft)
We can't make a fully functional camera(slight camcorder/flash stuff that have never affected me)
Can't have exfat sdcards
Can't have native FM radio
(Reason why we are not really officially supported by Cyanogenmod in their M builds)
But that's about it...I would really recommend you to try them...unless you need a Samsung specific feature like AllShare or AllShare control if you have a SmartTV...or want the extra features in the camera (BurstShot ShareShot) that I really never used..... and a lot of those features are now in CM10.1 like HDR and that stuff.
Those are my two 2 cents of the theme
Sent from my GT-I9300 running AOKP Build 6
Related
Hi all,
First of all, I'm amazed and gobsmacked at how much work all the devs put into their respective ROM's, it's amazing the effort and hard work ppl put in. Passion is alive and well on XDA
Now, to business. I have my Galaxy SII, a Galaxy S, and an Acer Iconia A500. I've flashed them all with their respective ICS. I would think (and hope) that probably out of all of them, the SII has the biggest dev base and most power. The ICS ROMs for the A500 and S are almost perfect. They run completely vanilla with no or almost no bloat, they look and behave the same (icons for network activity inside the bars for example, contacts app looks the same) and have had no hiccups whatsoever.
Come the SII, the only ROMs I've seen are cooked from Samsung sources with their phone and contacts apps, they crash and reboot and if it weren't that I have gone past the point of no return in regard to effort I'd have gone back to Gingerbread days ago.
Is anyone out there developing a completely vanilla "Google" rom that isn't themed to look like ICS, but actually uses the ICS apps etc. I can't understand how the Iconia and SI can have this while the SII seemingly doesn't.
Can anyone open my eyes on this? I'd love to get something as stable onto my SII as I have with my other devices, ICS is brilliant to use on them...and barely bearable on my beloved SII.
Cheers
<:3)~
Ummmm correct me if I am wrong but that's exactly what the CM team are trying yo to do....
And you can already download and install that, so long as you are happy with the bugs at present.
Unless you meant something else???
Sent from my GT-I9100 using XDA App
You miss reading the cm9 thread. Check it out....its still alpha.
Sent from my GT-I9100 using Tapatalk
I'm more curious about the fact I would have thought the SII having a bigger user and dev base...certainly more than the A500 I thought it would have the most stable and mature code base - yet it seems the opposite is true.
I've been running 4.0.3 on my SI for weeks now and its never bugged out. Installed the A500...and Oh wow its like a brand new tablet!! I wonder is it because of Exynos or some other reason we can't have the same stability and performance right now.
Sent from my Acer Iconia A500 using Tapatalk
Your ignorance and disrespect is pretty bad (even if you don't mean it). I think you should do some reading for a while and get yourself acquainted with what's involved.
I didn't ask this to be dissed by someone...I'm sure even you would agree the development cycle and challenges for all three devices would be similar given they all use different processors. So is it easier to compile for the A8 and Tegra than the A9?
I have been looking and downloading a number of ROMs...and if someone has created a ROM in a similar vein to Thor's on the A500 and Onecosmic's on the SI, well I'd be grateful for the heads up...in fact I'm just about to download and test the Pure ROM I just spied over in dev...so see how that goes. Still I'd be happy for someones *constructive* input.
Of course I'm claiming ignorance...if I knew I wouldn't ask...geez lol
Sent from my Acer Iconia A500 using Tapatalk
It's a wonder no one bothers doing a straight AOSP compile for any device, really. CyanogenMod comes the closest. There are a few people who played with doing a straight AOSP, but they base it off CM's work and strip out the extras.
When I wanted the AOSP experience with Gapps, I installed CM7 on my SGS and installed the stock Gingerbread launcher. It was the closest I got.
Trebuchet is basically the stock ICS launcher with features added, so it won't be so bad. You can also replace it with the stock launcher as well.
Try Airbus 360s ics rom that's aosp and is fantastic he should be releasing beta 2 tonight.
sent from my iPhone 4S.
haha I bet that confused ya
You're question is a bit noob so don't expect much answers.
Here is a short one to sum it for you:
AOSP - Pure android base without modification.
CM - almost pure with modifications.
STOCK - Hardware Manufacturer (eg. Samsung's) "official originated" release.
Stock - can have it all. CAUSE - Samsung has sources and support/docs for ALL hardware API of the device.
CM/STOCK - While there are some changes BOTH use the same origin.
To sum it, for proper functionality BOTH use SAME kernel/libs base.
So if some hardware functionality broken in one it'll be broken in other =
If CM9 haz no h/w decoding === APPLIES for AOSP.
Another thing to keep in mind, CM9 currently is in the process of adding CM features so current builds are very close to AOSP with functionality.
SUM IT UP:
if (CM9 != working) AOSP.isNotWorking()!
ttg said:
if (CM9 != working) AOSP.isNotWorking()!
Click to expand...
Click to collapse
That's a piece of horrible code, dude
Will it be MIUI, Cyanogenmod or something else? Share your desires and maybe devs will listen
Definately MIUI.
Using it on my EVO 3D atm, and I loooooove it!
Definitely Cognition Rom
Will be happy to see custom ROMs, but as long as they incorporate the awesome samsung features
I am only looking to put ROMs on this phone that are proven stable - and keep the features of the SGSIII intact. I don't want a phone that needs this workaround to get a feature to work.
I hope BootManager PRO works for this phone because I do like to keep several ROMs at hand at once. I really love the ICS blues and I have seen some amazing things evolve from a stock AOSP 4.0.X ROM over at the GNex forums. So we just need to wait and be amazed with the features that will be introduced to the world of Android via this phone's development section
Kernels on the other hand - this is where I am mostly concerned. We know pretty much NOTHING about the way a quad core kernel should be dealt with... These will be the main subject of my attention as we get into early development stages.
We shall see what some of our amazing developers who have proven they make kernels their bi***es can do with a new kernel. I am also interested in the kernel that Samsung has developed for it and how exactly this works in our favor here at XDA.
The main point is while most ROMs can be considered close... Kernels will be quite different and will be everyone's main focus - making our quad core beasts run with optimal battery life!
Checkrom
Skickat från min GT-I9100 via Tapatalk 2
I'd like to see a CM9 hybrid\tablet mode rom with per-app dpi capabilities that comes with a free high class escort.
I will use any "rooted" rom that is stable enough .... so far we don´t know is it possible to change bootloader.
Cyanogenmod of course
Probably..... stock rom, bloatware removed (will keep all the good stuff), custom kernel and custom themes
Sent using TCP/IP
CheckRom 100% the most popular and best ever ROM for the SGSII no other ROM comes close, i still use it and have used nothing else for a long time, SGSII ICS ROM's still nowhere near as good as CheckRom although i hear CheckRom ICS will be landing shortly for the SGSII although ill be selling my phone and getting the Galaxy S3
Slim ICS, as don't see much need for all the extra stuff apart from eye tracking to keep the screen on, S-Voice functionality goes in one ear and out the other, NFC not for me, Social tagging can leave me alone, shame the screen is sub standard to the SGS2.
Still loving my SGS 1 but am due an upgrade so may as well get this, hopefully the GPS is not as ****e as the SGS is. ended up buying an iPhone 3GS just to use with TomTom.
Now if you could give me TomTom on the SGS3 then you'd be talking.
Definitely checkrom with a new kitchen. And if we can get a siyah kernel then its over!!!!!!!!
cm9
miui
slim
aokp
Hi guys,
can you help me understanding the main pros/cons for going with Samsung JB or an AOSP rom on the Galaxy S3?
I've tried searching the forum but without luck, anyone got a thread link where this is covered?
My first Samsung (S3) phone is on its way by mail, and I'm trying to decide which type of rom to choose.
Off course I see the obvious stuff like:
Open vs Closed source
Stock vs Custom UI
But, except for the above; why should I choose an optimized (de-odexed, de-bloated etc. etc.) Samsung JB rom over an AOSP rom?
From what I can understand custom kernels also exists for both rom types, so that wouldn't be an argument right?
I'm not familiar with the current HW support in AOSP rom's for the S3. Generally this has been where roms for my HTC phones have differed in the past. What's the status with the S3, do AOSP support most of the stuff or is there still some way to go?
Please shed some light for me :fingers-crossed:
And please don't compare specific rom's against each others. I'm trying to understand this at higher level, I will off course test several rom's and make up my own mind about what specific rom release is best suited for me.
Samsung roms will have all the things mentioned in the ads such as direct call, smart stay, multi window etc. Aosp won't have these as they are samsungs additions. Samsung will have touchwiz launcher as default, which comes with a lot of samsung only widgets. Aosp will have vanilla launcher (with some extra functions and tweaks).
Sammy roms generally have better camera than aosp. Aosp is considered to have better battery usage although I can't really tell from my experience of using both types.
Deodexed means it's easier to develop themes for, as the external odex files are repackaged into the apks directly. But it will take a while longer when booting, as odex files are meant to speed up this process. As for the actual usage, not much difference.
Debloated means getting rid of bloatware that come with your phone, sich as chaton, google talk etc. There will be quite a lot of apps that you don't use but will be present and wasting your phone resources. Debloating is done by some developers but you can do most of ot yourself as long as you're rooted.
Hope this clears things. But these are all general, as you wished it to be. Some aosp will have different launcher options etc, so will sammy roms. As for what you go with, I'll leave it up to you.
Sent from my GT-I9300 using xda premium
Thanks
xcly said:
Samsung roms will have ...
Click to expand...
Click to collapse
Thanks a lot xcly, this clears up some stuff for me
You say that Sammy roms have better camera, what about the rest of the HW support on AOSP? The rest of the stuff (GPS, Accel, Gyro etc.) works ok?
From what I can gather from your post (and reading around) the choice boils down to two main points for me
HW support
Kernel (stability and performance, ofwhich battery performance is derived)
I don't care much for the 'Samsung features' (direct call, smart stay, multi window etc.) and the launcher can always be customized.
Additionally my previous experience is that the continious devlopment done on AOSP (with nightlies etc.) gives a nice feeling of continous improvement that you miss from manufacturer roms. For manufacturer roms you're relying on manufacturer relase schedules and leaks. But off course, one can argue that there is continous development through hacking, back-porting and kernel improvements for these roms as well..
Ultimately I think Ill just have to try out the most popular roms of both types before I'm able to decide what type I go with as a daily driver.
As for kernels most of then support both aosp and sammy so don't worry about it too much. Gps wifi and the lot work well on both as well.
Samsung didn't release any source code for its processor so aosp roms can never realise the full potential. Never had any trouble using aosp so I wouldn't say there is a huge difference, but I guess some advanced users will miss the hw side of things..
Sent from my GT-I9300 using xda premium
Simple to say
TouchWiz UI and pure Android UI.
Other things basically are very similar
Sent from my GT-I9300 using xda premium
Haha nice. All my words in a single sentence
Sent from my GT-I9300 using xda premium
Here is some personal feeling about them.
As you can see from my signature that I had Nexus S and Galaxy Nexus before, and after I lost my GNex, I tried to buy a Nexus 4, but it kinda like mission impossible as it's serious outta supply, so I was forced to make compromise and go with Galaxy S III, which is very nice phone through some thing I don't like such as hardware button and soft key (because GNex uses virtual button on screen which is completely customizable ).
I have been using AOSP ROM for over a year (well, it's outta options actually as they are Google's sons but Samsung didn't make a ROM for them even they are manufactured by Samsung , and 3 month with Sammy ROM.
Even I got my S3, the first thing I have done is flash AOSP ROM and get my feeling about GNex back, but unfortunately due to some reasons, I couldn't make it become GNex-like and realize it is something fool, so I tried Sammy stock ROM.
My first feeling about it is a little prettier than AOSP ( through there's countless themes for AOSP, I am just talking about default theme ) and some Sammy features are very interesting and attractive. (IMHO, I'd say it is more user-friendly to users ) which is why I decided to stay with it , but after all these times, I didn't actually use these features much except multi windows and slide to dial...
OK, sorry for my non sense words and my bad English just can exactly express what I trying to say...
Sent from my GT-I9300 using xda premium
FoxHound rom is all you need.
crDroid is the most stable Sammy Tom out there with the option of having an AOSP theme & not installing all the bloatware that Samsung Roms are notorious for.
Sent from my GT-I9300 using xda app-developers app
don't turn this thread into a best rom one
A quick follow up question
Just a quick follow up question regarding HW support:
Whats the status for AOSP roms regarding MHL, does it work?
I recently saw a video where a guy paired his phone with a PS3 controller and played games on his HD TV. Would this possible on non-Sammy roms?
Can't help you much on that. Never tried mhl on my s3, aosp or otherwise. You're better off asking/searching in cm thread. If it works on cm, it'd probably work on other aosp roms too.
Sent from my GT-I9300 using xda premium
Pedro80 said:
Just a quick follow up question regarding HW support:
Whats the status for AOSP roms regarding MHL, does it work?
I recently saw a video where a guy paired his phone with a PS3 controller and played games on his HD TV. Would this possible on non-Sammy roms?
Click to expand...
Click to collapse
You need to read the relevant rom threads or logically ask in those threads .
jje
Hi everybody
Recently I noticed a large interest in the subject custom ROM for Mega. Especially a lot was written about the AOSP. Please express, what do you expect after installing such ROM and why you do not like TW?
Another thing are stock ROM's stripped of almost all s-apps and other software deemed unnecessary in order to recover memory. Please share your opinions on the advisability of such action. Did you really needed all this reclaimed memory?
-reserved-
I expect most of the new features for S4 and Note 3 to be available in this ROM.
I still dont know if we can expect full 4.3 update. Some web sites claim that Mega wont receive this "Premium package" update whatever that means. I dont think that Mega 6.3 is a mid class smartphone and it would be plain stupidity if we stay out of good updates. So very important part for a custom RoM is the availability of the latest Samsung goodies from the flagman like S4 for instance.
Also I think that TW is not so bad, I like its interface.
celeronix said:
I expect most of the new features for S4 and Note 3 to be available in this ROM.
Also I think that TW is not so bad, I like its interface.
Click to expand...
Click to collapse
Hmm, I was asking about expectation towards AOSP custom ROM-s as such CM or MIUI. As you probably know, many futures in Samsung stock ROM depends heavily on TW. Massive striping stock Samsung ROM from all s-apps could even cripple your phone. But installing AOSP ROM will means clean-out all samsung dependencies, so there will be not possible to run futures from S4 or GN3. maybe I'm wrong, let somebody correct me.
I think so TW is not so bad either and was curious why some people are so opposed to it. I was user of Motorola Defy which actualization stops on Android 2.3 so custom ROM's were only alternative. Now I am not so eager to strip my Mega to bare AOSP.
Yeah I missed the point of AOSP rom a little bit, but I strongly believe that a Samsung device without TW loses its advantages. I've been using Galaxy S with AOSP for a long time but I was forced to do it because of the lack of updates after 2.3.6
Samsung says that the new 4.3 update will bring new and fast TW without lags and constant refreshing. This makes me think that porting the new SW is better than Aosp roms. Of course there should be some roms based on CM cause many people preffer stock android instead of customized one.
I just want CM because it allows you to port MIUI v5. I have always been a fan of MIUI roms.
This is a question about custom ROMs...it's the first time I'm really looking for one, and before anyone suggests CM - that is useless to me due to lack of functioning MHL.
So I'm looking for a ROM that has all the phone features functional (as in "in a usable for daily life degree").
I'm an Android game/app reviewer and I've been looking at apps for screen recording, but seeing how none of them allow for a reasonable experience on a Galaxy S2, I'll stick with external capture...and since I can't afford any better device right now, I thought I'd turn to custom ROMs for a while.
...so any suggestions?
[btw, I'm using the Galaxy S2 GT-i9100 international variant]
Not gonna recommend a cusROM as that's against XDA rules....but as a general answer, have you looked at the 'hybrid' ROMs?..... Samsung based but without the bloat and with the added customizability of aosp/aokp.
If MHL is a Sammy standard, then they *should* include it
This might be my S2, or it might be my W...but it's definitely CM
keithross39 said:
Not gonna recommend a cusROM as that's against XDA rules....but as a general answer, have you looked at the 'hybrid' ROMs?..... Samsung based but without the bloat and with the added customizability of aosp/aokp.
If MHL is a Sammy standard, then they *should* include it
This might be my S2, or it might be my W...but it's definitely CM
Click to expand...
Click to collapse
Technically, my question is about something pretty much no ROM developer ever addressed so it shouldn't be against the rules o_o
Anyway, is there any "list" topic of place where I can find hybrid roms only?
Look for alliance rom or biftor rom or neat rom ect ect. Sammy based roms are hybrid roms.