Hi everyone,
last week i ordered a Samsung Galaxy S Advance and i'm pretty excited about it. At first, i was very happy the device received the Android 4.1 Jelly Bean update. Now, i'm not really sure if i should update. Of course, Jelly Bean runs nice, but i'm so used to Android Gingerbread on mobile phones. To be honest, isn't it a little weird to have a 'Samsung Galaxy SIII Interface' on this device? Not that i'm fond of Touchwiz, but things will 'feel' different when the update arrives.
Again, is it really worth it updating to Jelly Bean when the current version works just fine?
feel free to discuss
Thanks in 'advance' (hehe),
Anthe
I didn't update into russian JB - waiting for official XEO region, but I am going to update whenever XEO shows up.
By that time they should iron out most bugs found in previous releases so it will be clean and smooth just after update - no need custom kernels or any other bug fixes (or at least I hope for it ;p).
Not that I am afraid of Odin - I had branded ROM but I flashed non-branded rooted stock XEO and for now I am good with that.
I had the same doubt, so a few days back i upgraded to JB (XXLQ4) . So far, i'm very pleased, it runs very smoothly (there is a "butter" effect to it that GB didn't have) but i should clearify that i'm running a custom kernel (cocore E2.8). Also, Jelly Bean's UI is a little more polish in its presentation and functionality. There are a few details like when you press the volume rockers, you can tap an icon and adjust individually the volume for calls, notifications and multimedia (in GB stock ROM you couldn't do this). The camera app now has digital zoom built in (4x) and when recording video you can pause and resume without creating another video file. There are lots of little things like this that make it overall better in my opinion.
Gaming performance is the same as in GB, at least for me (GB also was running with custom kernel, mini cocore 1.4).
The only con i could find with JB is the battery performance, as it is a little bit worst than it was with GB. I'm hoping further kernel development will change that.
So my advice is, YES, you should upgrade to JB if you can live with a little less battery life. If you don't like it you can always downgrade.
Piachnp said:
I had the same doubt, so a few days back i upgraded to JB (XXLQ4) . So far, i'm very pleased, it runs very smoothly (there is a "butter" effect to it that GB didn't have) but i should clearify that i'm running a custom kernel (cocore E2.8). Also, Jelly Bean's UI is a little more polish in its presentation and functionality. There are a few details like when you press the volume rockers, you can tap an icon and adjust individually the volume for calls, notifications and multimedia (in GB stock ROM you couldn't do this). The camera app now has digital zoom built in (4x) and when recording video you can pause and resume without creating another video file. There are lots of little things like this that make it overall better in my opinion.
Gaming performance is the same as in GB, at least for me (GB also was running with custom kernel, mini cocore 1.4).
The only con i could find with JB is the battery performance, as it is a little bit worst than it was with GB. I'm hoping further kernel development will change that.
So my advice is, YES, you should upgrade to JB if you can live with a little less battery life. If you don't like it you can always downgrade.
Click to expand...
Click to collapse
Can you upgrade if you have a custom kernel installed, or do you need to revert back to stock kernel prior to updating to JB?
purplepizza said:
Can you upgrade if you have a custom kernel installed, or do you need to revert back to stock kernel prior to updating to JB?
Click to expand...
Click to collapse
You can update it if you have custom kernel. But with Odin only. Not with OTA or KIES.
Is it easy to downgrade back to Gingerbread? I found some threads about doing it, but i didn't get what they meant. The only thing i did with 'rooting and flashing and stuff' is rooting my Samsung Galaxy Mini 2 and installing a custom recovery (because they told me to do so).
I really like Gingerbread and in my opinion Jelly Bean belongs on more recent, more expansive devices. Like a Galaxy Nexus or a Galaxy SIII.
Why you open this topic if you are satisfied with GingerBread?
Sent from my GT-I9070 using xda premium
Because i know Jelly Bean works great too! It runs on my Asus Transformer Pad Infinity (well.. 4.1 ._.) and on my Nexus 7. I just wanted to know if it IS worth it upgrading (so i don't need to do a lot of things to reverse it ).
Anthe said:
Because i know Jelly Bean works great too! It runs on my Asus Transformer Pad Infinity (well.. 4.1 ._.) and on my Nexus 7. I just wanted to know if it IS worth it upgrading (so i don't need to do a lot of things to reverse it ).
Click to expand...
Click to collapse
I will say from my personal experience:
I'm using the Stock LQ4. Without changes.
The best thing I did was not giving up the LQ4 after a FC/reboot on the first day of use when watching a video. I came from bad experiences with previous Jelly Bean. But ....
I came back after reboot and simply marked the option Settings / Developer options / "Force GPU rendering". It was just what I did since I installed LQ4 six days ago.
Battery life is just the same as on GingerBread. but everything else is better in Jelly Bean. There is no comparison.
This is my personal experience.
But if you still have questions you can expect. If anything happens to me out of the ordinary I certainly will make a report.
But anyway ... You did not read the forum? Your questions have all been answered.
I know i CAN, but it is hardto do so?
To do, WHAT?
I am using JB (LQ4) with cocore 2.8 kernel for two days and it is stable and fast so far.
Jelly Bean is far better than GB. The UI is more polished (aesthetically more pleasing and you need fewer taps to get somehing done), you have butter (smooth UI), better gmail app, significantly faster browsing! Also, my gps works better on JB.
Sent from my GT-I9070
Alright, when my Advance arrives, i'll be glad to update it to Jelly Bean. Thanks everyone!
Related
Hi, fellow Noters!
I have the N7000 Note, with stock GB ROM installed and only rooted, flashed with abyss kernel.
I am in the UK, so I am considering updating/upgrading to ICS... Now, from most of the posts here I gather that most of custom ICS ROMs aren't yet the most stable and people who installed the official ICS have mixed reactions...
Don't get me wrong- I am completely satisfied with my Note and the functionality of the apps as it is, but was just wondering how much improvement would I see, if I installed ICS...
Also, if I want to install official ICS ROM, do I need to unroot first and then flash it with ICS, or just straight on?
Thanks and enjoy the weekend!
Ics is suffing from the brickbug for now, that is not to mention other issues such as baterry drain. So if you are still satiafied with gb then should hold on unrik tge brixk bug is cleared. Cheers.
Sent from my GT-N7000 using XDA
If you want to do an update ics stock , you have to flash with odin 1.85 the rom that you prefere..... it is not necessary performing unroot...
I'm still running GB as it's running great. Nothing really worth upgrading to ICS.
Sent from my GT-N7000 using Tapatalk 2
Stay with GB. If you desperately wants ICS then flash CM9 or PA.
If you want to stay on a Touchwiz rom, then it may be better to stick with Gingerbread as it has less bugs that the TW ICS counterparts. However I would thoroughly recommend AOKP or CyanogenMod 9 if you truly want ICS; it has almost all features fully working (including camera, tethering and full access to all storage) and are both extremely light and quick. Plus both support themeing and have a wealth of customization options.
As for the brick bug, that has been almost eradicated IF you use a safe kernel such as Speed mod 3.3. Of course the worry is non existent on AOSP roms.
Sent via carrier pigeon
Right... Thanks guys for your input!
I am in no rush to get to ICS, as pretty much all the visual stuff can be achieved through some extra launchers and themes while still staying with stock GB ROM.
I am pretty much happy with TouchWizz, but find the Go launcher a bit more faster and easier to use. I go to TW only when I need S Memo and that stuff from the suite...
so, until the bug in the official ICS ROM is fixed, or a very stable custom ICS ROM made, I will stick with GB...
Atomix86 said:
If you want to stay on a Touchwiz rom, then it may be better to stick with Gingerbread as it has less bugs that the TW ICS counterparts. However I would thoroughly recommend AOKP or CyanogenMod 9 if you truly want ICS; it has almost all features fully working (including camera, tethering and full access to all storage) and are both extremely light and quick. Plus both support themeing and have a wealth of customization options.
As for the brick bug, that has been almost eradicated IF you use a safe kernel such as Speed mod 3.3. Of course the worry is non existent on AOSP roms.
Sent via carrier pigeon
Click to expand...
Click to collapse
so you say that flashing Cyanogmod9 rom and Speedmod 33 is a good bet?
can you give instructions on just how to do just that.I've never flashed anything before, but I do have lies and Odin on my PC already and both can see my note.
thanks
jimmbomb said:
...but I do have lies and Odin on my PC...
thanks
Click to expand...
Click to collapse
He, he, he... you mean Kies?
I also sometimes mistype words and it is annoying when the result is actually a proper word, so it completely can confuse the recipient of the SMS, for instance...
I wonder if there are alternatives to the current ordering of letters on keyboards, you know-instead of ASDF-JKLsomething...
yeah.. typing on the note.
using GB keyboard with autospell ..
messes me up alot,cause I rarely proofread.
I Still would like to install the safe Cynamiod 9 and speed mod 33 if someone could walk me thru it.
thanks
First off-hold your guns!
I know JB as such isn't out yet, and can't be expected to be as stable as ICS... But, still- after watching video reviews of some custom ROMs, one asks themselves, if they should give it a go...
Ok, so I am running stock (LAME!!!, I know ) GB, rooted and couple of launchers make it more interesting, sure... However, after browsing through this lovely and extremely helpful forum, I noticed that there are people who are already enjoying the benefits of running JB ROMs, or very good and matured TW based ICS custom ROMs...
1. So, I know ICS stock kernel has been a bit of a problem, what that just 4.03, or did 4.04 fix that?
2.Kill be for being so easily pleased, but I do find my Note and its current ROM already pretty smooth... I know all the bits that ICS makes it better and even more so JB, but considering all the things ICS brought, is there a point of trying JB, except for experimenting?
3. One thing I am so after, is that bit where from the lock screen you have like 3, or 4 options, one of them being going straight into the camera mode. I don't know if that is only JB, but I could really use it, as the old way (press the menu button, swipe to unlock, then press the camera icon) so many times made me miss the scene I wanted to take a photo of. So, any info on that would be much appreciated.
4.So much hype around GN II, but seeing that so many features are being ported to GN I custom ROMs, I am only after a ROM which will have those new and useful S III and GN II bits sawn onto the old(er) jacket.
5. I am in no rush, so do you think that in 3-4 weeks something more stable JB based will be available(official JB update should be rolling out soon, no)?
Big thanks to all you guys here, not just for answering the questions, but also all the tutorials and topics we noobs can find here... Keep up the good work.
See custom jb roms are stable like cm10 aosp liquidsmooth etc.you will feel smooth quality on it and butter project.
Ics 4.0.4 is very stable and has many mods and a good battery life too.
So lastly its your choice which one to flash.
Hit thanks button pleass
Sent from my GT-N7000 using xda app-developers app
Answering the title of your thread, there are no TW-based JB roms yet. All the TW-based ROMs are ICS. So if you are looking for smooth and reliable TW-based ROMs I would go for Kingdroid (ICS). If you want Jelly Bean you have ParanoidAndroid, Liquidsmooth, but these are not TW-based.
And answering the 5 questions in the contents of your post:
1. The problem is not with the kernel, the problem is with the chip itself, the *workaround* is using a modified kernel that does not use the MMC_CAP_ERASE command, so to answer your question, no the problem isn't solved and it won't be solved unless Samsung recalls all the units and gives out new ones without the bug. You will have to be careful when upgrading to ICS/JB because you will need to use safe kernels.
2. Jelly bean is definitely smoother than ICS, it is worth upgrading IMO.
3. That is the ICS/JB unlock screen that comes in stock android, and it is also available in most AOSP/AOKP ROMs. It is not available by default in Touchwiz but you can download that lockscreen from the Play Store as a standalone app and replace it.
4. Not all the Note2 features have been ported to the Note1, for instance the multi-window view is not available on any ROM yet as far as I know.
5. I have made the switch because I can't stand the look of Touchwiz, the complete disregard of Google's Holo design is for me a reason enough to switch to AOSP/AOKP, that said even when official JB ROMs start rolling out I probably won't come back to Touchwiz.
I think that you need a stock ICS TW rom, maybe RocketRom or Alliance v2.1 rom. I have tried a couple JB roms, but it feels like you have giant nexus insted of a great note.
If you want stock, pick up a last 4.0.4 xxlrt or ddlr9 or something similar, depends where you live but it's not too important. After that, just flash PhilZ kernel and you are safe, disable all aplications that you dont need, and thats it.
Or if you want a custom rom which is great like stock and cool like custom, choose rocketrom v12 or alliance v2.1
Hope that helps!
Ooooohhh-dann so...
Well, that clears so many things...
I mean, am no Samsung fan boy. It is just that I edit many pdf docs on the go, and other TW apps are very useful as they bring the functionality and the precision of the S Pen... As I said. I even find stock GB smooth, so I believe ICS should feel like heaven for me.
BIG QUESTION = so, since the problem was the chip, not the stock kernel itself, and the only solution is a modification of kernel, surely Google will include the workaround in a new JB update, no?
I haven't updated OTA to ICS, because I was scared of bricking the phone, or something.... Are the updates incremental, or so I need to update to official ICS and then to JB, or will I be able to go straight to JB (official one)?
I think I might go for Kingdroid (ICS), or Sweet ROM... Though, I from reading their respective threads, I get the idea that less people have issues with Sweet ROM....
Thanks again...
Ota update from GB ROM is safe because GB kernel is safe. Or can download stock ICS from Dr Ketan and flash with pc odin. Then flash appropriate Philz kernel (can do it from stock recovery). You will then be on safe stock kernel (only brick bug is disabled) with advanced CWM recovery. Once on Phils u can backups/restores and flash any ROM u like. Just have to do full wipe before flashing new ROMs.
Sent from my GT-N7000 using xda app-developers app
cmick30 said:
Ooooohhh-dann so...
Well, that clears so many things...
I mean, am no Samsung fan boy. It is just that I edit many pdf docs on the go, and other TW apps are very useful as they bring the functionality and the precision of the S Pen... As I said. I even find stock GB smooth, so I believe ICS should feel like heaven for me.
BIG QUESTION = so, since the problem was the chip, not the stock kernel itself, and the only solution is a modification of kernel, surely Google will include the workaround in a new JB update, no?
I haven't updated OTA to ICS, because I was scared of bricking the phone, or something.... Are the updates incremental, or so I need to update to official ICS and then to JB, or will I be able to go straight to JB (official one)?
I think I might go for Kingdroid (ICS), or Sweet ROM... Though, I from reading their respective threads, I get the idea that less people have issues with Sweet ROM....
Thanks again...
Click to expand...
Click to collapse
You could try ics stock rom with non stock kernel, i my self use notecore and hydracore kernel while i am using ics rom.
This will give you another experience..
Sent from my GT-N7000 using Tapatalk 2
What are the pros and cons of using 4.2.1 vs 4.1.2? I've been a JB (4.1.2) user for a while and I like how it flows, will I run into any kind of major bugs going to the newer versions? I've read about bluetooth headset issues but I don't even own one so no problem there XD some users also say 4.2.1 is actually faster, is that true?
Which ROM do you guys use for a daily driver? (I have my SGS for like 2 weeks and already flashed it like 20 times lol)
I've been using hellybean and I find it is faster and amazingly more stable but it could just be how I use it
Sent from my GT-I9000 using xda app-developers app
there is some 4.2 rom already to SGS+ I9001?
thanks
jbezerra said:
there is some 4.2 rom already to SGS+ I9001?
Click to expand...
Click to collapse
Sorry bro, only saw 4.1.2-based ROMs yet
personally i like 4.2 more, because there's less problem with these roms for me. on 4.1 android system always kept the phone awake but when i switched to 4.2 this annoying problem disappeared. also my battery life is better and the speed too. so i highly recommend you to try one or two new roms
Flashed both CM10 and CM10.1. The 4.2.1. was much more laggy and had much more bugs than 4.1.2 did, so I flashed to CM10 stable and it runs like a charm.
Sent from SGS GT-i9000 using magic.
That is because cm10.1 is nightlys ROMs like hellybean and slim bean are much faster and more stable
Sent from my GT-I9000 using xda app-developers app
I personally use X-Bean 3.0, stable, fast. I'm now stuck at Semaphore 2.6.2s since newer versions do not support WiFi direct.
I'm eager to try a possibly better rom, trying to decide on anything 4.2 based.
4.2.1 is much faster than 4.1.2
in my opinion the Ram management is also much better
for daily use i'm running on HellyBean 4.2.1 by DerTeufel
for me its the stablest, fastest and smoothest Rom for SGS
i use 4.2.1. fishears nightlys. after i found out that he uses the original parition layout and my hardware is given, its the only right choice for me. i was on slim bean before but after 2-3months of use it became veeeery laggy and random reboots.... slim bean is a very good rom but after some usage it caused a lot of problems. i hope fishears wont do the same after a couple of time
I can never settle for a ROM...been like this since I got my SGT7 which was flashed like everyday, lasted on stock for the first week. I'm a flashaholic XD anyway, I've since posting this tried Helly Bean (4.2.1) and was amazed by how smooth it went and flawless then I screwed it up by flashing some random stuff and getting a bootloop, as usual. Then I tried Helly Bean (4.1.2) and was sad to see it was actually slower than the 4.2 version so right I'm on MIUIv4 from miui.us and I'm not sure about it really. Will give feedback whenever but I believe I'll just end up going back to 4.2.1 for the awesomeness of it.
4.1.2 has stopped Development already because of the latest release of Android 4.2 version.
So if a user is satisfied with a stagnant Rom, this is a better choice.
A user can just pick a most stable 4.1.2 Rom and flash it, but expect no more Development on this one.
The beauty of 4.2.1 is its continuous Development. New features are added and new tweaks are introduced everytime.
I'm using 4.2.1 C-Rom Mix v4 and I'm surprised by its fastness and stability.
I really didn't expect an almost perfect 4.2.1 Rom at this early stage of its Development.
AW: [Q] 4.2.1 vs 4.1.2
But according Android Version history the changes in 4.2.1 are not significant nor performant. So no urge really to upgrade in my opinion.
Sent from my GT-I9001 using xda app-developers app
If I remember right, 4.2 introduced the possibility to key in your PIN in landscape orientation. This comes handy if got a desk- or cardock (or both )
Does android 4.1.2 support GL to SD? 4.2.1 doesn't so I'm thinking of downgrading but I need to confirm
From what I read from other threads, it appears that the ICS and JB roms are quite stable enough as a daily driver. I have a few questions regarding these Roms. I'm still running the Apex rom which is an i9000 stock based rom on 2.3.6 for the past year or so. It has been working very well for me. I'm kinda inching to running a JB or ICS rom because of some apps wouldn't run on anything less than ICS or JB.
1. My main concern that stopped me from running ICS or JB is the EU bug. What are the chances of one who never had it before to get it?
2. I know Adobe stopped providing flash support for JB, so now because I'll be running a custom rom, will there be flash support on those roms?
3. The state of 4.2.1 appears to still be in beta for most roms, so I would assume 4.1.2 is more stable than the former, but I would like to know how does 4.1.2 compare with 4.0.4 in terms of stability?
4. I've ran CM7.1 before which was an AOSP rom, but I experienced really bad battery problems. I've tried it a few times, and nothing works to solve it, so I always end up going back to the APex Rom. Because the JB and ICS roms are AOSP-based, how would these roms compare with the stock based roms and CM7 in terms of battery life?
I really want to be sure I want to flash JB or ICS. I would like to breathe some new life into my 2.5 year old phone, but just want to make sure I know what I'm getting into first.
Thanks in advance.
likiud said:
From what I read from other threads, it appears that the ICS and JB roms are quite stable enough as a daily driver. I have a few questions regarding these Roms. I'm still running the Apex rom which is an i9000 stock based rom on 2.3.6 for the past year or so. It has been working very well for me. I'm kinda inching to running a JB or ICS rom because of some apps wouldn't run on anything less than ICS or JB.
1. My main concern that stopped me from running ICS or JB is the EU bug. What are the chances of one who never had it before to get it?
2. I know Adobe stopped providing flash support for JB, so now because I'll be running a custom rom, will there be flash support on those roms?
3. The state of 4.2.1 appears to still be in beta for most roms, so I would assume 4.1.2 is more stable than the former, but I would like to know how does 4.1.2 compare with 4.0.4 in terms of stability?
4. I've ran CM7.1 before which was an AOSP rom, but I experienced really bad battery problems. I've tried it a few times, and nothing works to solve it, so I always end up going back to the APex Rom. Because the JB and ICS roms are AOSP-based, how would these roms compare with the stock based roms and CM7 in terms of battery life?
I really want to be sure I want to flash JB or ICS. I would like to breathe some new life into my 2.5 year old phone, but just want to make sure I know what I'm getting into first.
Thanks in advance.
Click to expand...
Click to collapse
1. To my knowledge the EU bug is only present on ICS ROMs. I encountered it once and had read enough about it that I didn't hit the reset phone button. I went back into recovery and flashed back to jellybean with no permanent harm.
2. I haven't paid much attention to this so potentially yes and no.
3. 4.2.1 is actually pretty stable but is lacking some features that people already running custom JB ROMs have come to rely on. But yes for a fully functional and stable ROM I would suggest avoiding 4.2.1 for the time being.
4. In my opinion battery life is improved over gingerbread no matter what ROM you're running. Of course battery life is a subjective thing. I've seen screenshots where someone had their battery last 2 days on so and so rom. But that person likely didn't touch the phone the majority of those 2 days.
All in all I would suggest you go with jellybean 4.1.2 as they are very stable and honestly smoother and more responsive than ICS.
A couple things before you flash though. First make a backup of your efs folder. You'll thank me later if you end up needing it. Secondly going from where you are to where you want to end up is a major jump in software versions which includes a partition layout change specifically if you are going to Jellybean. So the first time you flash the ROM the flash will complete very quickly(less than 5 seconds). If you try to boot after that flash you'll get stuck in a boot loop. Don't worry though just reboot back into recovery which should have updated with the first flash. Then just flash the ROM again as well as the gapps and you'll be golden.
Sent from my SGH-I897 using xda app-developers app
likiud said:
From what I read from other threads, it appears that the ICS and JB roms are quite stable enough as a daily driver. I have a few questions regarding these Roms. I'm still running the Apex rom which is an i9000 stock based rom on 2.3.6 for the past year or so. It has been working very well for me. I'm kinda inching to running a JB or ICS rom because of some apps wouldn't run on anything less than ICS or JB.
1. My main concern that stopped me from running ICS or JB is the EU bug. What are the chances of one who never had it before to get it?
2. I know Adobe stopped providing flash support for JB, so now because I'll be running a custom rom, will there be flash support on those roms?
3. The state of 4.2.1 appears to still be in beta for most roms, so I would assume 4.1.2 is more stable than the former, but I would like to know how does 4.1.2 compare with 4.0.4 in terms of stability?
4. I've ran CM7.1 before which was an AOSP rom, but I experienced really bad battery problems. I've tried it a few times, and nothing works to solve it, so I always end up going back to the APex Rom. Because the JB and ICS roms are AOSP-based, how would these roms compare with the stock based roms and CM7 in terms of battery life?
I really want to be sure I want to flash JB or ICS. I would like to breathe some new life into my 2.5 year old phone, but just want to make sure I know what I'm getting into first.
Thanks in advance.
Click to expand...
Click to collapse
Yes, flash it still supported. Just not needed by adobe.
Battery problem can come from so many things and usually is user based. We use apps like BetterBatteryStats to narrow it down though.
As for 4.1.2 and 4.2.1. I would highly suggest 4.1.2 for now until 4.2.2 comes out.
agree with BWolf56,
I've running CM10.0 stable release, JB 4.1.2, and have found it to be more stable, smoother, and reliable than stock GB with Corn 7 kernel.
I was also concerned about EU bug.
I couldn't find any evidence than anyone had experienced the EU bug on JB.
Skip ICS and go for it!
Sent from my SGH-I897
I think I'm sold to JB 4.1.2! Thank you for all the replies.
Sent from my SGH-I897 using xda app-developers app
If you want JB, get Galaxy Young S6310.
It's the same phone as mini2, just different design, more RAM, CPU preclocked to 1GHz, and JB 4.1.2 preinstalled. It has the same price as the mini 2.
S6310 has 768MB of RAM. mini 2 only has 512MB. It's enough for 4.1, but not enough for optimal performance. Look at Xperia E, every reviewer has noticed lags with the official 4.1 on it.
I fully agree with TheWhisp's post about how we use drivers not suited for 4.2 (or 4.1 too). Without official LIB's and official kernel, we'll always have a half-baked CM. And that's not TheWhisp's problem. It's Samsung's problem for releasing new models every three seconds, and ditching support for the older models. WE WON'T HAVE JB ON MINI 2! THEY HAVE S6310 FOR THIS PROBLEM!
CM should only be an option, not a necessity that every mini 2 user should install, just because there's nothing else for our phone.
Look at Sony's Live With Walkman, it has 512MB of RAM too. Everyone is reporting better performance on official 2.3.6, than in official 4.0.4!
The BEST thing for our phone would be a new kernel for 2.3.6. Not the squadzone's, because it has some problems with certain stock ROM's. Isn't it sad that we only have ONE custom kernel for 2.3.6. And only TWO good ROM's for mini 2? (CM10 and CM10.1). I knows there's many 2.3.6 ROM's but they are mostly just squadzone's kernel + additional visual tweaks + removed bloatware + useless build.prop modifications, simply because there's nothing else to do with 2.3.6. I know it might sound like I'm begging you, but why don't make a new kernel for 2.3.6? With fix for the famous LK2 no-WiFi bug, and perhaps better performance.
I do not want this phone's development to be stale and almost non-existent.
If I didn't have to start school in 2 days, I would be a developer and help with everything, but there's more important stuff than mini 2. I'm just proposing an idea.
MrMateczko said:
If you want JB, get Galaxy Young S6310.
It's the same phone as mini2, just different design, more RAM, CPU preclocked to 1GHz, and JB 4.1.2 preinstalled. It has the same price as the mini 2.
S6310 has 768MB of RAM. mini 2 only has 512MB. It's enough for 4.1, but not enough for optimal performance. Look at Xperia E, every reviewer has noticed lags with the official 4.1 on it.
I fully agree with TheWhisp's post about how we use drivers not suited for 4.2 (or 4.1 too). Without official LIB's and official kernel, we'll always have a half-baked CM. And that's not TheWhisp's problem. It's Samsung's problem for releasing new models every three seconds, and ditching support for the older models. WE WON'T HAVE JB ON MINI 2! THEY HAVE S6310 FOR THIS PROBLEM!
CM should only be an option, not a necessity that every mini 2 user should install, just because there's nothing else for our phone.
Look at Sony's Live With Walkman, it has 512MB of RAM too. Everyone is reporting better performance on official 2.3.6, than in official 4.0.4!
The BEST thing for our phone would be a new kernel for 2.3.6. Not the squadzone's, because it has some problems with certain stock ROM's. Isn't it sad that we only have ONE custom kernel for 2.3.6. And only TWO good ROM's for mini 2? (CM10 and CM10.1). I knows there's many 2.3.6 ROM's but they are mostly just squadzone's kernel + additional visual tweaks + removed bloatware + useless build.prop modifications, simply because there's nothing else to do with 2.3.6. I know it might sound like I'm begging you, but why don't make a new kernel for 2.3.6? With fix for the famous LK2 no-WiFi bug, and perhaps better performance.
I do not want this phone's development to be stale and almost non-existent.
If I didn't have to start school in 2 days, I would be a developer and help with everything, but there's more important stuff than mini 2. I'm just proposing an idea.
Click to expand...
Click to collapse
Okay, i've corrected some typing errors in your post. Typing errors fixed are in bold.
And, i agree with you.
Errors fixed. Also, Android has not ditched any support for 2.3.6, it still is the second most used version to date, so why not?
MrMateczko said:
Errors fixed. Also, Android has not ditched any support for 2.3.6, it still is the second most used version to date, so why not?
Click to expand...
Click to collapse
Yeah, it's also the stablest one to date. CM7.2 also loads alots of customization than CM9, CM10 or even 10.1 and 10.2.
You are right. I have squadzone kernel but i wanted some better. Someone that could make a new kernel and, why not, also a new rom.
PS: someone should make a list with all roms for our device, like in other forums.
Inviato dal mio GT-S6500 con Tapatalk 2
Yes. I have to agree with you. There no need to wait for official jellybean anymore. I think Samsung also headache how to make a smooth jellybean rom on low end device. For low end device, I think gingerbread is better.
I list down what I want in mini 2 :good:
ROM:
- Based on latest 2.3.6 firmware
- Bloatwares removed
- Deoxeded
- Zipaligned
- Tweaks to make it more faster and smooth compared to stock
- Themed (optional) - Galaxy S4 icon,font, new accuweather, blue statusbar instead of shiny green, percentage battery, beautiful bootscreen
- anything good for user
Kernel
- kernel build based on goals "smooth,fast,battery saving,stable"
- 3 step different freq 200,500,800 MHz (non OC kernel), 4 step 200,500,800,1000 MHz (OC kernel)
- tweaks to make it smooth and stable experience for user
- anything good for user
If only I am capable on doing all this.....:
Thank you for your post, you've bought some interesting ideas. I would personally have the ROM Odexed, as the performance would be better.
I think I would add the 6th step in the OC kernel, which would be 1126MHz, for max performance.
But I'm no kernel compiler. Although I will try to change the squadzone's kernel logo to show S6500 and not S6500D, as it's the wrong model I have.
I'm thinking about sorting stuff out with all the components we currently have. But that takes time.
I don't like huge theming, the only awesome thing for me would be the percentage battery.
Cm 10.1 works even faster than stock for me. Games work well too.
Sent from my GT-S6500 using Tapatalk 2
That's good for you, but this isn't a topic to bash CM10(.1;.2), it's simply an idea that we should have a much wider choices of custom ROMs for mini 2.
Well, we already have plenty. Maybe when thewhisp finishes working on 10.1 which is nearly complete he will grace us with cm 7. Just an idea.
We also need more devs, i dont see many ppl working on jena roms
Sent from my GT-S6500 using Tapatalk 2
Yes I agree with low end device work faster in 2.3.6 than 4.0 and above. My brother own xperia tipo and it is lagging on 4.0.4. I guess it is better if it on 2.3.6. While my sister own mini 2 S6500D running on 2.3.6.
I mention about theming before, it is not heavy theming mate. I also like you. I prefer profesional look and minimalist theme. A theme that have clean,neat and professional look from boot screen to user interface. And yes % battery would be great.
But sadly low end device not much developers, so we may have to wait.
My phone works twice as fast on CM 10.1.
No major bugs or anything.
Overclocked to 1Ghz.
Runs smoother than before.
Works faster than s3 mini on stock (tested with antutu)
I dont see why this phone wont work with oficial jellybean.
Galaxy Music has 512 ram and works grat with oficial jellybean.
meganukebmp said:
My phone works twice as fast on CM 10.1.
No major bugs or anything.
Overclocked to 1Ghz.
Runs smoother than before.
Works faster than s3 mini on stock (tested with antutu)
I dont see why this phone wont work with oficial jellybean.
Galaxy Music has 512 ram and works grat with oficial jellybean.
Click to expand...
Click to collapse
Not the galaxy music only the galaxy star /galaxy star pro / galaxy trend and some other devices can't remember their names now.
Sent from my GT-S6500 using xda app-developers app
Galaxy chat works fine too
Sent from my GT-S6500D using Tapatalk 2
GT-S6310 laggs terribly on 4.1, same as GT-S7560 on 4.0