Hey guys,
I've recently bought a Pioneer Appradio 2 and I am looking for the least bloated rom that still supports HDMI via MHL out.
I do like the KK roms, but unfortuanately, the phone.apk (Dialer) doens't like the landscape format and will not display properly on the head unit. So I guess I'm stuck with 4.3 or lower..
What the slimest, least bloated rom that will fulfill my requirements?
This is only an answer you can determine based on your own research and testing.
Head over to the development threads and give them all a run. :good:
As these type thread almost always become arguments over which rom is best, and as XDA is not a support site. Members are expected to read and do their own research into matters such as these.
Related
First of all, let me apologize if this has been asked before. I did numerous searches but could not find any relevant information.
I'm currently on an Omega Jellybean Rom but I'm quite unsatisfied with the experience I'm getting from my phone. Samsung Dialer/Contacts and Messenger are slow to open and it doesnt really quite feel like a phone running Jellybean (yes ive tried alternative apps such as exdialer with the missed call patch).
I recall the JB experience i got from my galaxy i9003 (crappy asian galaxy S) which was a lot more enjoyable/smoother than what im getting now on the S3. Therefore the plan to switch to PA
Now the question is, aside from the issues mentioned on the PA thread (camera getting stuck when taking pics w/ front cam, no FM out, no TV out) are there any other issues or things that I'll be trading off by switching to PA?
Can I get a general consensus regarding PA vs sammy roms? Advantages/Disadvantages? Looking forward to your input
sicmofo said:
First of all, let me apologize if this has been asked before. I did numerous searches but could not find any relevant information.
I'm currently on an Omega Jellybean Rom but I'm quite unsatisfied with the experience I'm getting from my phone. Samsung Dialer/Contacts and Messenger are slow to open and it doesnt really quite feel like a phone running Jellybean (yes ive tried alternative apps such as exdialer with the missed call patch).
I recall the JB experience i got from my galaxy i9003 (crappy asian galaxy S) which was a lot more enjoyable/smoother than what im getting now on the S3. Therefore the plan to switch to PA
Now the question is, aside from the issues mentioned on the PA thread (camera getting stuck when taking pics w/ front cam, no FM out, no TV out) are there any other issues or things that I'll be trading off by switching to PA?
Can I get a general consensus regarding PA vs sammy roms? Advantages/Disadvantages? Looking forward to your input
Click to expand...
Click to collapse
I'd suggest you give Viking Rom a try, I'm a fan of trim Roms and Vikings weighs in a 425 meg, is super smooth and battery life is outstanding.
Viking is a JB rom. I have never experienced any of the issues you mention with the ROM.
sicmofo said:
First of all, let me apologize if this has been asked before. I did numerous searches but could not find any relevant information.
I'm currently on an Omega Jellybean Rom but I'm quite unsatisfied with the experience I'm getting from my phone. Samsung Dialer/Contacts and Messenger are slow to open and it doesnt really quite feel like a phone running Jellybean (yes ive tried alternative apps such as exdialer with the missed call patch).
I recall the JB experience i got from my galaxy i9003 (crappy asian galaxy S) which was a lot more enjoyable/smoother than what im getting now on the S3. Therefore the plan to switch to PA
Now the question is, aside from the issues mentioned on the PA thread (camera getting stuck when taking pics w/ front cam, no FM out, no TV out) are there any other issues or things that I'll be trading off by switching to PA?
Can I get a general consensus regarding PA vs sammy roms? Advantages/Disadvantages? Looking forward to your input
Click to expand...
Click to collapse
I am a big fan of Paranoid Android, always used their ROM, but recently changed to Omega due to Dualboot compatibility, and to be honest, it is a lot more stable than other ROMs I have found.
Omega v2.0 is awsome with the aosp/aokp UI style and Omega v29 is the standard Android UI. Worth doing a Dual Boot with the both of them.
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
Hello All,
Did ask this question in the main thread, however it might have been ignored, due to the heavy influx of posts. So I am using a custom ROM rootbox stable 4.0 on my SGS-II. Just wanted to ask that I maybe planning to buy the following type of bluetooth tags, once they become stable enough for main stream use.
1. http://www.sticknfind.com/
2. http://www.indiegogo.com/projects/button-trackr-find-lost-items/x/2060164?c=home
According to the information gathered these devices require "Bluetooth Low Energy" (BLE) enabled cellphones and the required software implementation profile to work on. Apparently in the Android domain only Samsung is providing it in S3, S4 and Note 2 only in stock ROM.
Just wanted to ask that does RootBox or any other leading custom ROMs supports this BLE profile, and if not at the moment, is there any plan to include it in the stable upcoming releases.
Thanks for the responses. Great work all the AOKP, Cyanogen, Paranoid, MIUI Developers.
HyperEscape said:
Hello All,
Did ask this question in the main thread, however it might have been ignored, due to the heavy influx of posts. So I am using a custom ROM rootbox stable 4.0 on my SGS-II. Just wanted to ask that I maybe planning to buy the following type of bluetooth tags, once they become stable enough for main stream use.
1. http://www.sticknfind.com/
2. http://www.indiegogo.com/projects/button-trackr-find-lost-items/x/2060164?c=home
According to the information gathered these devices require "Bluetooth Low Energy" (BLE) enabled cellphones and the required software implementation profile to work on. Apparently in the Android domain only Samsung is providing it in S3, S4 and Note 2 only in stock ROM.
Just wanted to ask that does RootBox or any other leading custom ROMs supports this BLE profile, and if not at the moment, is there any plan to include it in the stable upcoming releases.
Thanks for the responses. Great work all the AOKP, Cyanogen, Paranoid, MIUI Developers.
Click to expand...
Click to collapse
I am in the same boat as you. Need it to see my Casio GB-6900 Smart Watch which runs on LE. I have tried all nighly builds from haashcode and the rest of the soup. Not one has support for BLE. I hope they think of supporting this in their future release.
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.
I bought my Galaxy S5 a couple of months ago and I still have this S2. I'm really not sure what to do with this phone. Not gonna sell it away because it is an awesome phone.
But here I'm planning: (I'm sure there are a lot of people like me, not sure what to do with their old S2 now.)
- build a media center.
But this requires sammy ROM so it could be connected to the TV using HDMI.
- try out new ROMs.
Yeah awesome idea.
- use it as an IP Camera.
- use it as an "iPod"
I have some questions regarding these choices.
1) shall I stick to sammy jellybean or upgrade to KitKat? I'm currently using kikat on this S2 but I would like to use it on the TV
2) will it have any problems if I let my S2 stick on he charger 24/7? If only I would like to use it as an IP camera. Will it have any effects on the battery/motherboard?
I hope fellow S2 members can discuss all this here. Thanks!
Sent from my GT-I9100 using Tapatalk
I am not an s2 user anymore for 1,5 years but.
1) you can stick to jellybean stock if you want it for your tv but I suggest to use a custom rom based on stock jellybean, look in the dev forums there are a couple of it.
2) I am not sure or you will have any problems but just like on a laptop and other devices its not good to let a battery charge for 24/7 so google it for sure for your own safety/phone life.
I also hope for you that other s2 member are going to discuss here with you
I dont see the point to stay on kitkat if you already have the s5. So I suggest to downgrade to an custom stock base rom since it would be also probably more bug free.
I really recommend using a custom stock rom such as neatrom for pure stability. If you prefer a little extra performance (and some new features), go with a kitkat rom such as cyanogenmod or paranoid android (and the list can go for ages).
I decided to go with JB NeatROM. Thanks for the advice guys! I find it more stable and faster as compared to KitKat. (Probably because I didn't use JB for months)