Well thought I would pose the question as curious as to where to go next with our S2's
What are the advantages of the different versions of Android on the S2's and their sub versions??
What I mean by subversions is quite simple really 4.1.2 over say aosp 4.1.2?
We are on 4.1.2 Chameloen (me) 4.1.2 stock rooted(partner)
curios as to whether there's any point moving especially as kitkat onwards there no write to sd which is frigging STUPID!!!!
looking forward to your thoughts and opinions folks...
And thank you to all thoughs who take part..
regards
Lohtse
lohtse said:
Well thought I would pose the question as curious as to where to go next with our S2's
What are the advantages of the different versions of Android on the S2's and their sub versions??
What I mean by subversions is quite simple really 4.1.2 over say aosp 4.1.2?
We are on 4.1.2 Chameloen (me) 4.1.2 stock rooted(partner)
curios as to whether there's any point moving especially as kitkat onwards there no write to sd which is frigging STUPID!!!!
looking forward to your thoughts and opinions folks...
And thank you to all thoughs who take part..
regards
Lohtse
Click to expand...
Click to collapse
Hey,
Samsung doesn't officially release any changelogs, but if you prefer Samsung base roms, i recommend those with their latest base for security purposes and improved user interface (hopefully!)
There main difference between AOSP/AOKP and regular Samsung ROMs are that AOSP teams aren't part of Samsung.
AOSP aims to give people access to the latest of the Android world, as you can see that you can run lollipop on S2, without AOSP teams this wouldn't be even remotely possible as Samsung wants you to buy newer phones. So in that sense AOSP is a great tool.
But Samsung is the company that can ensure stability on their ROMs while AOSP still are nightly (beta) versions with lot of bugs, small maybe but lots.
AOSP/AOKP - Access
Samsung - Stability
If you refrain from using kitkat because of the sd card bug, don't worry. There are many apps and xposed modules that can fix the issue by granting full access to the external sd card.
WardenBerret said:
Hey,
Samsung doesn't officially release any changelogs, but if you prefer Samsung base roms, i recommend those with their latest base for security purposes and improved user interface (hopefully!)
There main difference between AOSP/AOKP and regular Samsung ROMs are that AOSP teams aren't part of Samsung.
AOSP aims to give people access to the latest of the Android world, as you can see that you can run lollipop on S2, without AOSP teams this wouldn't be even remotely possible as Samsung wants you to buy newer phones. So in that sense AOSP is a great tool.
But Samsung is the company that can ensure stability on their ROMs while AOSP still are nightly (beta) versions with lot of bugs, small maybe but lots.
AOSP/AOKP - Access
Samsung - Stability
If you refrain from using kitkat because of the sd card bug, don't worry. There are many apps and xposed modules that can fix the issue by granting full access to the external sd card.
Click to expand...
Click to collapse
Thank you for your reply very useful
but what are apps you have mentioned?
WardenBerret said:
Hey,
Samsung doesn't officially release any changelogs, but if you prefer Samsung base roms, i recommend those with their latest base for security purposes and improved user interface (hopefully!)
There main difference between AOSP/AOKP and regular Samsung ROMs are that AOSP teams aren't part of Samsung.
AOSP aims to give people access to the latest of the Android world, as you can see that you can run lollipop on S2, without AOSP teams this wouldn't be even remotely possible as Samsung wants you to buy newer phones. So in that sense AOSP is a great tool.
But Samsung is the company that can ensure stability on their ROMs while AOSP still are nightly (beta) versions with lot of bugs, small maybe but lots.
AOSP/AOKP - Access
Samsung - Stability
If you refrain from using kitkat because of the sd card bug, don't worry. There are many apps and xposed modules that can fix the issue by granting full access to the external sd card.
Click to expand...
Click to collapse
What sd card bug you are talking about? Are you talking about the music bug? Because I've never heard or a problem where there was some problems with external sd card mounting.
lohtse said:
Thank you for your reply very useful
but what are apps you have mentioned?
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=nextapp.sdfix
I'm still on jellybean so i don't know even if it will show "This app is incompatible with all of your devices." if you have a kitkat rom, since its not official rom. Therefore the Xposed module is much more preferrable imo.
I can't offer any personal guarantees as whether it works or not.
gsstudios said:
What sd card bug you are talking about? Are you talking about the music bug? Because I've never heard or a problem where there was some problems with external sd card mounting.
Click to expand...
Click to collapse
The first kitkat builds had, for some strange reason, disallowed access to external sd cards, if any. Needless to say many people were not happy, and it wouldn't surprise me if the later builds removed this bug.
But if you have this bug, it basically means you can't use your external sdcard for anything unless you have root.
WardenBerret said:
https://play.google.com/store/apps/details?id=nextapp.sdfix
I'm still on jellybean so i don't know even if it will show "This app is incompatible with all of your devices." if you have a kitkat rom, since its not official rom. Therefore the Xposed module is much more preferrable imo.
I can't offer any personal guarantees as whether it works or not.
The first kitkat builds had, for some strange reason, disallowed access to external sd cards, if any. Needless to say many people were not happy, and it wouldn't surprise me if the later builds removed this bug.
But if you have this bug, it basically means you can't use your external sdcard for anything unless you have root.
Click to expand...
Click to collapse
thank you for the links... may give 5.0.2 or 4.4.x a try now....frigging stupid move not allowing write to sd etc in my opinion...... shame the community has to fix Googles screw ups!!
Related
Hello,
I came here desperate for answers that could solve my problem with "M-signature" not working on custom (not SAM-based) ROMs.
"M-signature" (aka "Mobile ID") is a way to connect to bank via phone (you get a special personal SIM card, you go to your e-banking site, enter your phone number, get a pop-up message on phone screen (see attached), enter PIN on the phone and voila - connected into e-bank).
This "M-signature" works on Stock Rom, also on Samsung based ROMs: null_ ROM v25, NeatROM EMC2, UltimaRom v11, but doesn't work with AOSP (Slim Bean, Dragon SlimBean), AOPK/CM (Pac-man), MIUI (_miui.polymorph_)...
Problem is I love Slim Bean or Pac-man and can't really get used to sam-based (they're ugly, i find them slower, battery not appealing, etc.) - could I find a way to make that "M-signature" work on AOSP/AOPK/CM ROMs??
Biggest thanks in advance.
Evaldino said:
Hello,
I came here desperate for answers that could solve my problem with "M-signature" not working on custom (not SAM-based) ROMs.
"M-signature" (aka "Mobile ID") is a way to connect to bank via phone (you get a special personal SIM card, you go to your e-banking site, enter your phone number, get a pop-up message on phone screen (see attached), enter PIN on the phone and voila - connected into e-bank).
This "M-signature" works on Stock Rom, also on Samsung based ROMs: null_ ROM v25, NeatROM EMC2, UltimaRom v11, but doesn't work with AOSP (Slim Bean, Dragon SlimBean), AOPK/CM (Pac-man), MIUI (_miui.polymorph_)...
Problem is I love Slim Bean or Pac-man and can't really get used to sam-based (they're ugly, i find them slower, battery not appealing, etc.) - could I find a way to make that "M-signature" work on AOSP/AOPK/CM ROMs??
Biggest thanks in advance.
Click to expand...
Click to collapse
It shouldn't act like that, android app should be compatible with everything running an android, not only samsung. Unless it's dedicated only to GT-I9300.
I know this won't solve your issue but there are plenty of samsung-based roms with really cool aosp themes, bunch of tweaks and really well made. I don't want to recommend my own work but take a look if you wish, perfect example of stock rom with non-stock look.
JustArchi said:
It shouldn't act like that, android app should be compatible with everything running an android, not only samsung. Unless it's dedicated only to GT-I9300.
I know this won't solve your issue but there are plenty of samsung-based roms with really cool aosp themes, bunch of tweaks and really well made. I don't want to recommend my own work but take a look if you wish, perfect example of stock rom with non-stock look.
Click to expand...
Click to collapse
Thnx JustArchi for answer (at least somebody wrote smth ).
That is not an app - it's a SIM card "feature" (a special, associated with my personal info (from my passport) SIM card which, I guess initiates those "pop-up messages").
It works this way: you go to www.example-mybank.com, enter there my ID and phone number, then (i guess) the special SIM card pushes a message "do you want to connect" (and shows control code to be sure it's your connection), enter your special PIN, and SIM card gives command to my bank "OK, let him in, it's really <Evaldino>" and the e-bank opens up for me
So, I guess it's something with "SIM services" (don't know how to call them - I'm a noob user), which work only on Stock or Sam-based ROMs, so perhaps CM/AOSP/MIUI lack a "module" or smth for these "SIM services" to work...
Also, this M-signature works on all smart devices (not only Samsung, not only Android, also on iOS, maybe even WinOS).
I see no other option as to try those SAM-based (though not really happy about that), so I'll definetely look into your ROM (I like 240DPI, circular battery, if only 4x4 pattern lock for locking screen), because for ex. on ReVolt (Sam-based, yes?) "m-signature" doesn't work (though I kind of liked this ROM)..
To be honest I'm surprised it works at all on a rooted device bearing in mind security etc....many banking apps/features won't work, especially with insecure kernel....I guess for a good reason...although not being particularly tech I wouldn't like to even attempt to explain why!
Please mind you that it may work on AOSP like the nexus builds but not work on CM based roms as they change ALOT of the AOSP code. That includes alot of the security protocols.
Wayne Tech S-III
slaphead20 said:
To be honest I'm surprised it works at all on a rooted device bearing in mind security etc....many banking apps/features won't work, especially with insecure kernel....I guess for a good reason...although not being particularly tech I wouldn't like to even attempt to explain why!
Click to expand...
Click to collapse
You have a point here.. didn'nt even think about that.. However, I'm not very "paranoid" and I don't think it's very insecure (to my little android security understanding)
zelendel said:
Please mind you that it may work on AOSP like the nexus builds but not work on CM based roms as they change ALOT of the AOSP code. That includes alot of the security protocols.
Click to expand...
Click to collapse
But I tried my beloved Slim Bean (AOSP based, right?) - not working.. maybe it's "too much changed" AOSP? What i9300 ROM is "purest" AOSP - I'll try?
Evaldino said:
You have a point here.. didn'nt even think about that.. However, I'm not very "paranoid" and I don't think it's very insecure (to my little android security understanding)
But I tried my beloved Slim Bean (AOSP based, right?) - not working.. maybe it's "too much changed" AOSP? What i9300 ROM is "purest" AOSP - I'll try?
Click to expand...
Click to collapse
There are no pure aosp roms for most devices. They all use something from CM. Be it kernel or some of the coding as aosp only supports the nexus line as a base. Everything else is a fork.
Wayne Tech S-III
So, how did you solved this problem, if you did? I wonder if this problem we are facing is only applicable in Lithuania as I can't even google some more sources on this issue...
valdelis said:
So, how did you solved this problem, if you did? I wonder if this problem we are facing is only applicable in Lithuania as I can't even google some more sources on this issue...
Click to expand...
Click to collapse
There is no way to solve it. It will not work on AOSP based roms.
zelendel said:
There is no way to solve it. It will not work on AOSP based roms.
Click to expand...
Click to collapse
Actually I just flashed this one [ROM][Mar 17] Jellybean 4.2.2 for Endeavoru AOSP Build [Kernel 3.1.10] [JDQ39] #19 and at last it works! Will try to use this ROM for some time to be sure everything works, but it at least the biggest problem is solved.
By the way, I forgot to mention in my first post, I'm on HTC One X (International version with Tegra), but hope there is a workaround for SIII too.
For Samsung Galaxy Mini there is AOSP ROM (http://forum.xda-developers.com/showthread.php?t=2413108)
Up to date as of November 22, 2013.
Modified: Installation guide: V2.0, some other parts including general info, changelog etc.
Added: Swapping guide, quick V2.1 guide, quick updating guide
---------------------------------
Are you experienced with ULTRA B.U.X? Please help me write its own guide (PM me)
---------------------------------
I created a centralized document with information about everything regarding Badadroid. The same questions are often asked over and over again by newbies/noobs (call it however you want to). I decided to write a centralized document that will include general information, a more detailed installation guide for those who struggle or have issues and a FAQ for everything regarding Badadroid.
In order to allow users to add their own feedback and comments I created it in Google Docs - but if a moderator/developer/authorized user here wants me to put everything on this thread just say...
I really hope this will help everyone. More info in the doc itself.
See http://bit.ly/19jWmE1
-------------------------------------------
Did this guide help you? Please hit the "Thanks" button
________________________
Member of Bada Israel
Are you Israeli? Wait for the Hebrew translation
Thx for the work!
Btw, wave doesn't have 512mb ram, (384mb)
Retrete said:
Thx for the work!
Btw, wave doesn't have 512mb ram, (384mb)
Click to expand...
Click to collapse
That's right. I think I confused it with my GPU thanks for the heads up.
Can anyone type the code to activate Zram on NAND tigrouzen rom (V3)? Please
Kiboi said:
Can anyone type the code to activate Zram on NAND tigrouzen rom (V3)? Please
Click to expand...
Click to collapse
Its all ready activated
Nadavs10 said:
I created a centralized document with information about everything regarding Badadroid. The same questions are often asked over and over again by newbies/noobs (call it however you want to). I decided to write a centralized document that will include general information, a more detailed installation guide for those who struggle or have issues and a FAQ for everything regarding Badadroid.
In order to allow users to add their own feedback and comments I created it in Google Docs - but if a moderator/developer/authorized user here wants me to put everything on this thread just say...
I really hope this will help everyone. More info in the doc itself.
See http://bit.ly/19jWmE1
Click to expand...
Click to collapse
Thanks Nadavs10, I think a FAQ is a good idea ... the point is how to ensure every newbie reads it before posting ...
I think it would be nice to join or at least to link this with another FAQ it was started in badadroid project page http://code.google.com/p/badadroid/wiki/FrequentlyAskedQuestions
Some comments:
Does it work for Wave II? YES! Many people ask over and over again the same question. Voice calling works now for Wave II too. If there’s something that isn’t the same for both devices, I will write it.
Click to expand...
Click to collapse
Bluetooth works in S8500 but no in S8530 (see status and this post)
Is it legal? Everything is legal except gapps. Decide for yourself.
Click to expand...
Click to collapse
Both badadroid and gapps are "legal", the difference is licensing model, so developers share badadroid open source code and binaries based in other open source code (android, aries ....) but they do not share gapps as it is google propietary. It is not ilegal to install gapps, but it should be ilegal to include it in badadroid package without google permision, so you have to install it separately.
There are many ROMs like Nand/LS Smook/moviNand. What are these, and what’s the difference? I’ll tell you the truth, I don’t really understand it. If someone knows it would be great for some comment here."
Click to expand...
Click to collapse
I am not an expert, but I am trying to share as I understand:
There are different "custom rom android flavors" (Cyanogenmod, AOKP, MIUI,...) as some communities/developers make some modifications in android source code. Just one example googling http://www.phonearena.com/news/Meet-the-best-custom-ROMs-for-Android_id44353
There are different badadroid roms as some developers try to optimize some points:
--Volk204's CM10.1 rom (and previously Rebellos' CM10) uses the same fota for booting, and it uses "standard" internal storage in our waves, so the uninstallation procedure is simple (another zip through CWM).
--Tigrouzen FnF SD (sorry if the name or some detail is wrong) uses special fota for booting, and it uses Nand memory/external SD storage with SD card partioned. http://code.google.com/p/badadroid/wiki/HardwareDocumentation#Memory Nand is a special memory in our waves that has to be written in a special way, and it is faster, so the unistallation procedure is a full flash of bada firmware. Tigrouzen's rom is more performance oriented and better for game players as far as I know.
hunktb said:
I am not an expert, but I am trying to share as I understand:
There are different "custom rom android flavors" (Cyanogenmod, AOKP, MIUI,...) as some communities/developers make some modifications in android source code. Just one example googling http://www.phonearena.com/news/Meet-the-best-custom-ROMs-for-Android_id44353
There are different badadroid roms as some developers try to optimize some points:
--Volk204's CM10.1 rom (and previously Rebellos' CM10) uses the same fota for booting, and it uses "standard" internal storage in our waves, so the uninstallation procedure is simple (another zip through CWM).
--Tigrouzen FnF SD (sorry if the name or some detail is wrong) uses special fota for booting, and it uses Nand memory/external SD storage with SD card partioned. http://code.google.com/p/badadroid/wiki/HardwareDocumentation#Memory Nand is a special memory in our waves that has to be written in a special way, and it is faster, so the unistallation procedure is a full flash of bada firmware. Tigrouzen's rom is more performance oriented and better for game players as far as I know.
Click to expand...
Click to collapse
Tigrouzen's rom is based on AOSP (Android Open Source Project) wich is basically, a build of the vanilla android sources released by google and the others implicated in the Android primary developement. (even if, tigrouzen included in his rom some code from CM to allow a better customization of the ROM, and so, it's a little bit different from pure AOSP)
Cyanogenmod is a modified open source android rom... it have some major changes in the code itself (compared to AOSP), in the library it uses, etc... it allow a higher personalisation of the UI than the original AOSP rom. (see their official website to find more info about the cyanogenmod project...)
And I would finally said that yes, tigrouzen's rom is released with an high optimisation care (resulting in a really smooth rom) while volk's rom: works on both wave I and II, I would say that it is a little bit more stable (but that's mainly because it's less often udated, several tigrouzen's updates resulted in an broken functionality (see the bluetooth problems in the AOSP thread) wich he quickly fixed anyway.) and I would say (except for the last "mic in call" update) more "hardware development" oriented (that's just my feeling, but it seems to me that volk (and rebellos) are focusing on the perspective of bringing a fully working android sytem to the wave rather than on the optimization of their existing incomplete system. (and honnestly, it's not a bad thing, it keep general development ongoing)).
Weird
Tigrouzen said:
Its all ready activated
Click to expand...
Click to collapse
Hey Tigrouzen i am facing a problem while using yur AOSP 4.3 Rom... I am using the ROM 4.3 LS V2 Revision 3 with SmooK V3 SD Kernel downloaded from http://www.multiupload.nl/HQ3BM7DOTH. The issue is weird as on the first booting of andriod, the netwrok is detected after arnd 20-25 mins but the next tiem the phone is booted in android it never detects network? :/
Any help on this plz wud be rly appreciated... Thanks
ghanii said:
Hey Tigrouzen i am facing a problem while using yur AOSP 4.3 Rom... I am using the ROM 4.3 LS V2 Revision 3 with SmooK V3 SD Kernel downloaded from http://www.multiupload.nl/HQ3BM7DOTH. The issue is weird as on the first booting of andriod, the netwrok is detected after arnd 20-25 mins but the next tiem the phone is booted in android it never detects network? :/
Any help on this plz wud be rly appreciated... Thanks
Click to expand...
Click to collapse
I solved this problem by removing then reinstall the sim, try
Kiboi said:
I solved this problem by removing then reinstall the sim, try
Click to expand...
Click to collapse
Thanks i am trying it right now....the ROM and Kernel which I mentioned are the right versions?
Kiboi said:
I solved this problem by removing then reinstall the sim, try
Click to expand...
Click to collapse
No luck... i cant understand dis issue.. how come sim is detected once and not the other time :/ any network settings which i should specify? or any odr Kernel which might be a solution for this?
ghanii said:
No luck... i cant understand dis issue.. how come sim is detected once and not the other time :/ any network settings which i should specify? or any odr Kernel which might be a solution for this?
Click to expand...
Click to collapse
Try with another sim and tell me if it works
ghanii said:
No luck... i cant understand dis issue.. how come sim is detected once and not the other time :/ any network settings which i should specify? or any odr Kernel which might be a solution for this?
Click to expand...
Click to collapse
move it to the top right corner. It sometimes helps.
Otherwise use an other sim card.
GreekBlood said:
move it to the top right corner. It sometimes helps.
Otherwise use an other sim card.
Click to expand...
Click to collapse
I should move the sim to the top right corner? :/
ghanii said:
I should move the sim to the top right corner? :/
Click to expand...
Click to collapse
Its possible if its old sim, then try get new revision of your sim.
ghanii said:
I should move the sim to the top right corner? :/
Click to expand...
Click to collapse
Go to setting and below bluetooth there is an option of more click on it and then tick use only 2g network
this may help
Maybe "we" collect different external Links in different languages...
Today I saw again German user asked...
Or maybe "we" could use 1 Guide and translate in different languages...
For instance:
English
German
Hindi----> user kktkaran has enough time and energy to do this, instead spxm
.
.
.
Btw.
For few things Screenshots or Video maybe helpfull.
And please, maybe here on XDA 1 copy for reading... So if external Link changed/removed/... it is possible to read here something in Thread.
Thanx in advance.
Best Regards
Tigrouzen said:
Its possible if its old sim, then try get new revision of your sim.
Click to expand...
Click to collapse
i tried a different kernel and it worked fine ver 3.0.85... voice is also clearer. thanks for your help
i am from those people who have problem in wave2 battery like
after restart battery drains to zero or similar level
random shut down problem
so
i have done an experiment which help me thats why i'm sharing it
first of all these problems are because of battery as i think so
1.first remove the battery
2.spin on flat surface if it spin then you can do nothing but replace your battery
3.if doesn't spin check its point of connection and remove any dust or rust
3.last but not least if any thing doesnt work
then
take a "soledring ion" and solder each connecting point of your battery seperately dont let them touch each other so that solder cover connecting points.
now put your battery in phone and test it work or not i.e. your problem solved or not
sorry for bad english
and do it on your own risk and carefully
Asop or badadroid
I'm currently using the ASOP NAND ROM created by Tiguorzen, however it has some call problems similar to old badroid ROM so I'm wondering whether I should shift to badroid project as it seems to get regular updates and ASOP ROM seems like abandoned by tigo(hope not) but ASOP is undobtly the fastes and most streamlined ROM not sure abouy the latest badadroid though.
Are there any clean & simple (i.e. non Samsung based) ROMs out there that support device & SD encryption?
I know CM11 doesn't... but I've not been able to find mention of it in any of the rom descriptions.
If none of the AOSP ones do, then what's the simplest Samsung based one, with encryption, but the least amount of Samsung bloatware?
A.
andybryant said:
Are there any clean & simple (i.e. non Samsung based) ROMs out there that support device & SD encryption?
I know CM11 doesn't... but I've not been able to find mention of it in any of the rom descriptions.
If none of the AOSP ones do, then what's the simplest Samsung based one, with encryption, but the least amount of Samsung bloatware?
A.
Click to expand...
Click to collapse
I think CM11 does, since I'm running a CM11 derived ROM and under settings -> security I have encryption.
Side note: you can remove bloatware from any ROM by yourself so pick any you like.
In stock-based roms, I suggest you give ArchiDroid V1.7.16 a try.
It has device encryption (as well as external SD encryption) and heavily debloated.
Make sure to read the OP, there are a lot of features you need to be aware of.
FPBug: Meet the very first stable kernel for the Galaxy S2 i9100, S2 AT&T i777, S2 Epic 4G Touch d710 and Note n7000 since Gingerbread days
Every single Android 4.x kernel for these devices has had a serious bug (FPBug) that randomly corrupts the state of processes, starting with Samsungs's stock ICS and JB and spanning every custom kernel out there newer than Gingerbread.
STATS: 500+ kernel downloads in 2 days, wow!
RELATED: Make sure you check out my TRIM-enabled kernels updated with the FPBug fix.
UPDATE: A fix for FPBug has been merged into CyanogenMod's cm-11.0 branch! The fix has not made it to the stable/cm-11.0 and cm-12.0 branches yet. Changes: this one and the previous 12. Commits: this one and the previous 12. The 20150111 nightlies are the first official CM 11 nightlies to incorporate the fix.
A little bit of history
As Android got more complex, the effects of this bug grew more visible, to the point of making the platform completely unstable for some users. Complex apps would fail for no reason, GSM, 3G and WiFi connectivity would randomly be lost, music playback would stop and require a reboot, camera would fail, internal storage and SD cards would become inaccessible, installed apps would disappear, users would experience battery drain issues ranging from inability to enter deep sleep all the way to phones becoming very hot, and the list goes on and on.
These failures all seemed unrelated and their cause was very hard to track down. Partly because events happened randomly and were not reproducible, but mostly because the bug undermines the very assumptions programmers deal with when creating any kind of code. And so years passed and the common cause of all this pain was never identified. Many ROM developers abandoned the platform out of frustration.
Then finally this past March, when analyzing the random loss of access to storage, user cgx observed a corruption event for the first time, and a connection between all these unrelated issues, sometimes hypothesized, was suddenly found. The corruption seemed to have happened in the stack, but it was later suspected then confirmed that the corruption actually happened directly in the registers of the floating point unit of the CPU. Yet processes that did not use floating point at all were also affected, because the GCC compiler typically spills registers into the FPU and uses FP and NEON instructions for optimization.
These findings allowed the creation of a stopgap fix for the "music bug" that shielded the FUSE process (which manages access to storage) from corruption in the FPU. The fix was widely applied and effectively eliminated all bugs resulting from sudden loss of storage access and returned the platform to pre-Android 4.3 stability levels: ie, sort of stable enough to be used as a daily driver. Later a working detector for the elusive bug was made and it was confirmed that all kernels since Gingerbread were affected (a thing that was already suspected given that the FirefoxOS people had described similar symptoms in 2012 under stock Samsung ICS). Finally enough of a root cause was hypothesized and a fix was worked out. And if this were not good enough news, user Entropy512, the exynos platform hero who saved us all from brickbug, has hinted that official Lollipop from Omni is now a possibility.
A short description of what the fix does can be found here.
Update
User zeitferne worked non-stop throughout this weekend and made amazing progress. He found a couple of missing commits that are apparently needed for the FPU state tracking to work through power state changes, he discovered that the FPU in CPU0 is the one that actually gets the corruption, he found an explanation why this bug never affected the 4412 platform (Galaxy S3, Note 2, etc), he narrowed down the conditions for the corruption, and finally output an alternative patchset that apparently fixes the FPU state restore optimization rather than just disabling it as mine does.
Kernel developers are encouraged to merge his changes in lieu of mine once enough testing is done and @zeitferne green-lights the patches. This is important as it might fix as-of-yet undetected bugs or prevent bugs arising from future changes. In the meantime, eager maintainers can merge my fix which is by now well tested. Users will only see a small (<< 1% ?) performance increase with zeitferne's patchset and don't really need to bother with this; my advice for them would be to wait for the changes to trickle into their kernel of choice. AMAZING JOB ZEI!!!
2nd UPDATE: @zeitferne has green-lit his patchset! Kernel maintainers merging it please take note: 1) Make sure my fix is removed before applying his, otherwise there will be a small performance hit in the resulting kernel. 2) Both our fixes also affect the 4412 platform (i9300, n7100, etc) in slightly different ways, and the effects of this have not been properly tested. I must recommend that some testing be done before distributing FPBug-fixed 4412 kernels. Please report your test results back to this thread.
WARNING: A problem was reported with zeitferne's patchset.
FOLLOW UP: @zeitferne made some changes to his patchset and initial testing looks good.
AND FINALLY: The patchset was merged into cm-11.0! (See this change and the 12 previous ones.)
Downloads
You will find kernels for various CyanogenMod releases, M-snapshots and nightlies here. These kernels are guaranteed to work only with the exact matching version of CM specified in the last part of their filenames. But in reality they should work with most versions of CM that are close enough. (Don't ask me about this, I don't know, I don't even have any of these phones! Just try them and see for yourself if you are feeling a little adventurous.) For other ROMs i expect this fix to be merged in a matter of days after some more testing is done. Please be patient, and KitKat users can flash my music bug fix in the meantime.
FAQ
Q. I have flashed your music bug fix in the past. Can I flash your kernel?
A. Yes! The music bug fix has no downsides. In fact, as a side effect, that fix makes your phone slightly faster and saves some battery so it should be merged in all ROMs IMHO. If you already have it installed leave it in place, but do not flash it again the next time you upgrade the OS. Please do not flash it just for the sake of optimization: since it is based on CM11 M10, it would actually be a downgrade.
XDA:DevDB Information
FPBug-i9100, Kernel for the Samsung Galaxy S II
Contributors
Lanchon
Source Code: https://www.androidfilehost.com/?w=files&flid=22853
Kernel Special Features:
Version Information
Status: Testing
Created 2014-12-19
Last Updated 2015-01-14
(reserved)
Is the BLN included ?
Lanchon said:
And if this were not good enough news, user Entropy512, the exynos platform hero who saved us all from brickbug, has hinted that official Lollipop from Omni is now a possibility.
Click to expand...
Click to collapse
It's not about i9100 ? Right ?
Can't wait till testing is complete and you merge the fix into your trim kernel for the i9100 lanchon. Thanks to all the programmers, testers and commenters in the bug thread for their hard work.
Sent from my GT-I9100 flowing on SwiftKey in Tapatalk
DarkJohn said:
Is the BLN included ?
It's not about i9100 ? Right ?
Click to expand...
Click to collapse
yes, he refers to the i9100 and the n7000
DarkJohn said:
Is the BLN included ?
It's not about i9100 ? Right ?
Click to expand...
Click to collapse
these are all standard CM kernels. please request features on the CM thread.
Lanchon said:
yes, he refers to the i9100 and the n7000
Click to expand...
Click to collapse
Oh God ! Lollipop
I am anxious
@Lanchon thank you very much for ur hard work [emoji122] [emoji122] [emoji108]
Dammit... Never wanted to use CM again... I think I will have to at least for now until it gets integrated in other kernels
Great Job @Lanchon
i never had any GPS problems on my i9100 before ICS. Since JB it has gotten sooooo much worse. I tried atleast 20 different ROMs (JB, KK) and 5 different Navigation Apps. Nothing helps. Currently i am on CM11 M12 Snapshot. Still not better...
Could this kernel also help me with the GPS Problem??
so no bad battery life any more?
Vidura Dissanayake said:
so no bad battery life any more?
Click to expand...
Click to collapse
Yes exactly. With a little more testing a final version should be coming soon. What an awesome Christmas gift!
Thindboy said:
i never had any GPS problems on my i9100 before ICS. Since JB it has gotten sooooo much worse. I tried atleast 20 different ROMs (JB, KK) and 5 different Navigation Apps. Nothing helps. Currently i am on CM11 M12 Snapshot. Still not better...
Could this kernel also help me with the GPS Problem??
Click to expand...
Click to collapse
No it won't solve gps problems. I've had good luck using GPS status https://play.google.com/store/apps/details?id=com.eclipsim.gpsstatus2 and Faster GPS https://play.google.com/store/apps/details?id=org.fastergps from the Google play store. GPS status will download assistance data (A-GPS) and faster GPS setups the proper ntp server for your area. I get fixes in about 10 seconds now.
Sent from my GT-I9100 flowing on SwiftKey in Tapatalk
Everything is somehow faster with this kernel. I flashed the music bug fix with this kernel. Waiting for trim kernel, it will further accelerate the phone.
I noticed that the phone is not heated as before.
You're a genius because you've done a lot for us, s2 community ... And we know that you do not own this legendary phone
Thank you @Lanchon
Sent from my GT-I9100 using Tapatalk
I dont understand does this feature going to be added to cm11 or do i have to flash a zip to add it?
Alucard said:
I dont understand does this feature going to be added to cm11 or do i have to flash a zip to add it?
Click to expand...
Click to collapse
im not part of the cm team and my crystal ball is acting up lately so i cant answer Q1.
this is a kernel, you need to flash it. please read the downloads section.
DarkJohn said:
Is the BLN included ?
It's not about i9100 ? Right ?
Click to expand...
Click to collapse
Cm12 is available?
Alucard said:
I dont understand does this feature going to be added to cm11 or do i have to flash a zip to add it?
Click to expand...
Click to collapse
Waiting for your review for Spirit ROM once you've flashed it.
Lanchon said:
im not part of the cm team and my crystal ball is acting up lately so i cant answer Q1.
this is a kernel, you need to flash it. please read the downloads section.
Click to expand...
Click to collapse
OK so FPBug-V1-src.zip is a flashable zip for fpbug fix for every rom stock jb and kk?And cm-11-M10-i9100-music-bug-fix.zip is for cm11 m10 only?
---------- Post added at 12:36 PM ---------- Previous post was at 12:33 PM ----------
x3dnd3x said:
Waiting for your review for Spirit ROM once you've flashed it.
Click to expand...
Click to collapse
Im on neatrom now ,will be on kk once a stable kk apolo kernel comes out!
What recovery does this kernel has built in? I use 11.15 cm11 custom build my markox and I want to mare sure that I can reflash the rom in a recovery if it screws up. I never used Odin since I got this phone.
Mockingbird said:
What recovery does this kernel has built in? I use 11.15 cm11 custom build my markox and I want to mare sure that I can reflash the rom in a recovery if it screws up. I never used Odin since I got this phone.
Click to expand...
Click to collapse
Lanchon bases his kernel on stock cm kernel, so cwm recovery is built in.
This is something I've always wanted for my G3, a vanilla ROM that's always up to date with the latest Android version, but without any "extras" and "features" seen in typical ROMs. I don't like having to deal with frequent ROM updates that add new features/create new problems. I just want a clean ROM that works like a Nexus device.
Why does this not exist?
(If it already exists I have not come across it yet)
DavM said:
This is something I've always wanted for my G3, a vanilla ROM that's always up to date with the latest Android version, but without any "extras" and "features" seen in typical ROMs. I don't like having to deal with frequent ROM updates that add new features/create new problems. I just want a clean ROM that works like a Nexus device.
Why does this not exist?
(If it already exists I have not come across it yet)
Click to expand...
Click to collapse
When you say vanilla I'm assuming you mean AOSP, in that case we do have cm12.1, but I don't know if that's what you mean when it comes to "frequent ROM updates"
But if you're asking as to why we don't have a stock 5.1 ROM, that would be because LG hasn't released a base for it yet
6NomoN6 said:
When you say vanilla I'm assuming you mean AOSP, in that case we do have cm12.1, but I don't know if that's what you mean when it comes to "frequent ROM updates"
But if you're asking as to why we don't have a stock 5.1 ROM, that would be because LG hasn't released a base for it yet
Click to expand...
Click to collapse
CM is not aosp based, it's cm based.
Yes, the argument could be made that everything starts with aosp, but AFAIK there is little true aosp left in cm, and mostly custom cm code.
As for the op,
You get what devs decide to build. Your question is borderline offensive.
DavM said:
This is something I've always wanted for my G3, a vanilla ROM that's always up to date with the latest Android version, but without any "extras" and "features" seen in typical ROMs. I don't like having to deal with frequent ROM updates that add new features/create new problems. I just want a clean ROM that works like a Nexus device.
Why does this not exist?
(If it already exists I have not come across it yet)
Click to expand...
Click to collapse
Well, you could always start a stock rom, root it, and use Titanium Backup to remove any feature you don't want and arrive to a "vanilla ROM". The ROM development is a hobby for the dev, so of course there are "frequent ROM updates". By the way, LG has not released the 5.1 yet, they are still on 5.0.1 (23c).
DavM said:
This is something I've always wanted for my G3, a vanilla ROM that's always up to date with the latest Android version, but without any "extras" and "features" seen in typical ROMs. I don't like having to deal with frequent ROM updates that add new features/create new problems. I just want a clean ROM that works like a Nexus device.
Why does this not exist?
(If it already exists I have not come across it yet)
Click to expand...
Click to collapse
Been using validus for days. Works great. No freezes. Don't use the features if you don't want em.