Related
A few of Sony Ericsson's newest devices are queued up to get CyanogenMod Custom ROM. Thanks to recent code submitted by Diogo Ferreira, the bits needed to bring my favorite custom ROM to three smartphones in the Xperia family:
- Xperia Play: r.cyanogenmod.com/#change,7126
- Xperia Neo: r.cyanogenmod.com/#change,7128
- Xperia Arc: r.cyanogenmod.com/#change,7127
Currently the code to add these phones to the CyanogenMod family is awaiting approval to be merged into the CyanogenMod repository. Once that's done we can expect nightly builds to follow not long after.
From that point it's just a matter of time before Release Candidates and a Final Build is available.
Source: http://r.cyanogenmod.com/#q,status:open,n,z
Via: http://pocketnow.com/android/sony-xperia-play-neo-and-arch-getting-cyanogenmod-custom-rom
Woohoo! I am getting a bit sick of my SE ROM, I want a Cyanogen!
very nice, i wasn't expecting official nightlies for our play's
Great!!!!!!!!!
Official CM7 on my Xperia Play is Very very Great
Come on!!!!!!!!
I'd like to hear word from the FreeXperia team. Are they maintaining CM7 officially?
At any rate, I already ROM Manager ready for action ^^
This is only for plays that are bootloader unlockable right? Any progress on unlocking the bootloader on simlocked phones?
RacecarBMW said:
This is only for plays that are bootloader unlockable right? Any progress on unlocking the bootloader on simlocked phones?
Click to expand...
Click to collapse
We're making progress on CDMA phones.
The problem is that simlocked phones don't have RCK_H key so there's nothing to crack the unlock key from. But as said, I'll check it, I have some people willing to test.
Looks as though it has now been merged. Really looking forward 2 flashing nightlies. Cyanogen best mod by a looooooonnnnggggg stretch.
And just in time so that Verizon users can join the party
Hi, I am Diogo Ferreira (submitter of these patches)
I think you'd be happy to know that they are now already merged and in a buildable state with nightlies following soon.
This is not an alternative to FreeXperia work, it is FreeXperia work. We've been all working together to make this happen.
I'd be happy to answer questions you might have.
deovferreira said:
Hi, I am Diogo Ferreira (submitter of these patches)
I think you'd be happy to know that they are now already merged and in a buildable state with nightlies following soon.
This is not an alternative to FreeXperia work, it is FreeXperia work. We've been all working together to make this happen.
I'd be happy to answer questions you might have.
Click to expand...
Click to collapse
Hi Diogo. Glad to hear from you. Does this mean Xperias will be listed on CM homepage under supported devices, and will get official forum's section?
Given that most of the features worked already in the betas (great job by the FX folks), the main question for the Play resides on the camera. What's the status on that?
And for those people who have ROM Manager Premium, will the nightlies come through it as well?
No ETAS on camera. It will be done when it's done but we're looking into it.
As for nightlies, they should be available soon.
deovferreira, is the team making an official kernel as well to compliment the nightly builds? If we are using ROM Manager, then CWM Recovery is essential, and it would be great to have a kernel that had this built in, like the FreeXperia's team does now.
Also, will the ROM be generic for all users? I had quite a few issues with the radio yesterday on my CDMA Play when I tried FreeXperia's latest build. I just wanted to make sure that builds would support all versions of the play, not just the R800i.
Mills00013 said:
deovferreira, is the team making an official kernel as well to compliment the nightly builds? If we are using ROM Manager, then CWM Recovery is essential, and it would be great to have a kernel that had this built in, like the FreeXperia's team does now.
Also, will the ROM be generic for all users? I had quite a few issues with the radio yesterday on my CDMA Play when I tried FreeXperia's latest build. I just wanted to make sure that builds would support all versions of the play, not just the R800i.
Click to expand...
Click to collapse
What is on CM today is on par with what we did for FreeXperia, the kernel has a builtin recovery. You'll see instructions on this soon when nightlies start to hit.
As for CDMA, I am not aware what the differences are. I support a CDMA device (desire-cdma) but it is a PITA since I have no real way to test. What would be good is if someone steps up and tried to maintain a play-cdma port, I imagine the differences would be fairly minimal.
deovferreira said:
What is on CM today is on par with what we did for FreeXperia, the kernel has a builtin recovery. You'll see instructions on this soon when nightlies start to hit.
Click to expand...
Click to collapse
Awesome. The only reason I asked is because of how its different from other devices. The kernel always has to be flashed with fastboot. So I just didn't know how the updates would work or anything like that. I assume we just flash one to start the process and go downhill from there.
deovferreira said:
As for CDMA, I am not aware what the differences are. I support a CDMA device (desire-cdma) but it is a PITA since I have no real way to test. What would be good is if someone steps up and tried to maintain a play-cdma port, I imagine the differences would be fairly minimal.
Click to expand...
Click to collapse
I agree completely. It appears that the kernel was working fine, there is just something in the CM build that was preventing the radio from working correctly. Logcat was telling me that it detected a CDMA mode and enabled it but then the phone module would crash. It was late when I started looking into it though and didn't do a lot of research, but I imagine that someone has encountered this with a CDMA port from a GSM cousin before. I'll do some more investigation this evening.
The boot will always have to be flashed separately using fastboot due to the way the sony ericsson bootloaders transforms the boot image on flashing. System updates will be done using the recovery, as usual. At some point the kernel and system may get out of sync, the symptom would be wifi failing to enable, at which point people would have to flash a new kernel.
As for CDMA, the RIL libraries should be different as should some settings in build.prop.
Awesome. I'll see what I can do this evening, and maybe even pump out a working build from the source for CDMA users.
Guys, stay calm.
this is FreeXperia CM7 "just" as official CM
So that is what you all wanted.
We worked over some time now with Diogo, all of us 3 ( Diogo, jerpela and me) have commited our changes, put them together and worked together.
All will be good See it as a surprise
I'm working for over 1 month now everyday on camera support. For now nothing new, but new knowledge
currently i'm looking into camera for new 4.x Firmware release, maybe SE changed something in a good way for us...
Best Regards
Bin4ry
Team FreeXperia
Ok I just read the thread and maybe I missed it, my xperia play is from Rogers. Will I be able to install cm 7?
Sent from my Play, with XDA Premium.
I'm not understanding how kernels and ROMs connect. Can someone give me some extra insight?
[Hardware] <-- Unique to every phone
--
[Kernel] <--- Tells the OS how to talk to the hardware
--
[ROM] <--- Slightly confused. Is the OS in the Read only Memory, or has this term changed its "street" meaning?
I understand that most ROMs (e.g. CM7 and CM9) include both the kernel and the ROM, but can you flash these separately too?
I have a 1.5 year old thunderbolt that's rooted, and has CM7 which is based on gingerbread. I believe HTC has also released the kernel as open source, which is probably the reason I have CM7
Anyway, I guess what I'm looking for is an answer/guide/forum that explains why I can't install newer versions of android onto the already working/open source kernel I'm already running. Is it accurate to view the kernel as all the phone's drivers, or just the CPU driver? If that statement is true, why can't I load ICS or Jelly Bean onto my already existing set of drivers?
I'm thinking about starting a Wiki on this if 1) it doesn't already exist, and 2) I can wrap my brain around it enough to share with others!
Thanks to anyone with a response!
shadowrelic said:
I'm not understanding how kernels and ROMs connect. Can someone give me some extra insight?
[Hardware] <-- Unique to every phone
--
[Kernel] <--- Tells the OS how to talk to the hardware
--
[ROM] <--- Slightly confused. Is the OS in the Read only Memory, or has this term changed its "street" meaning?
I understand that most ROMs (e.g. CM7 and CM9) include both the kernel and the ROM, but can you flash these separately too?
I have a 1.5 year old thunderbolt that's rooted, and has CM7 which is based on gingerbread. I believe HTC has also released the kernel as open source, which is probably the reason I have CM7
Anyway, I guess what I'm looking for is an answer/guide/forum that explains why I can't install newer versions of android onto the already working/open source kernel I'm already running. Is it accurate to view the kernel as all the phone's drivers, or just the CPU driver? If that statement is true, why can't I load ICS or Jelly Bean onto my already existing set of drivers?
I'm thinking about starting a Wiki on this if 1) it doesn't already exist, and 2) I can wrap my brain around it enough to share with others!
Thanks to anyone with a response!
Click to expand...
Click to collapse
You are correct about the ROM, but ROMs also include the kernel (if it didn't, or no kernel was flashed separately, the device would not boot). Yes, other kernels can be flashed on your existing ROM, but it's not necessarily going to be compatible.
Sort of, but there's a lot more than that. See here and here. Later versions of Android will require newer drivers,etc. which the existing kernel won't provide (they'll be outdated). Back porting and additional coding is theoretically possible, but insanely difficult (many times). Even after this some things may still not work.
Thanks for the insight, I was able to get a lot deeper into this with those links. For anyone else wandering down a similar path, you might as well stop now! Here are a few links:
http://forum.xda-developers.com/showthread.php?t=1039217&page=2#17
http://www.cs.uwc.ac.za/~mmotlhabi/avmk.pdf
http://www.iteachandroid.com/2012/01/what-is-firmware-rom-and-firmware.html
So, if anyone else is still listening, I do have two more questions:
Do any phones have truly open source drivers? (a.k.a. higher probability of allowing old hardware to work with new android OS)
Is there any way to determine which phones will be supported by the custom-ROM community early on? I know the Nexus line doesn't have vendor modified code, is that the direction which would have the highest probability to stay at top of the Custom ROM curve without upgrading devices every year?
Thanks again for any insight! I hope I'm posting this in a Newb-Friendly forum!
shadowrelic said:
Thanks for the insight, I was able to get a lot deeper into this with those links. For anyone else wandering down a similar path, you might as well stop now! Here are a few links:
http://forum.xda-developers.com/showthread.php?t=1039217&page=2#17
http://www.cs.uwc.ac.za/~mmotlhabi/avmk.pdf
http://www.iteachandroid.com/2012/01/what-is-firmware-rom-and-firmware.html
So, if anyone else is still listening, I do have two more questions:
Do any phones have truly open source drivers? (a.k.a. higher probability of allowing old hardware to work with new android OS)
Is there any way to determine which phones will be supported by the custom-ROM community early on? I know the Nexus line doesn't have vendor modified code, is that the direction which would have the highest probability to stay at top of the Custom ROM curve without upgrading devices every year?
Thanks again for any insight! I hope I'm posting this in a Newb-Friendly forum!
Click to expand...
Click to collapse
For both your questions, the Nexus-line devices would be the way to go. They usually have everything working on new Android versions the soonest, and Google always releases their code, etc.
Hi
i can use linux kernel (zimage) to update android kernel if yes ,how ?
thnx
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)
Background:
Ant+ and Health/Sport accessories are not very widespread among smartphone users, but it was one of the major reasons a which I moved from the Nexus 4 to Galaxy S4.
While S4 on 4.3 works great with my Garmin Heart Rate Monitor(HRM), I'm not satisfied with Touchwiz and Knox.
My S4 feels laggy, slow and I want to use stock android, or even any of those KitKat releases.
Many Xperia devices have Ant+ support, and it seems that they manage to cook it into custom roms successfuly.
Target:
Assemble a flashable zip which would allow anyone with an S4 already flashed to 4.3 to use the Ant+ receiver.
Research:
I've spent some time embeddint the Ant+ files (com.dsi.ant.antradio_library.jar and .xml, and the AntHalService.apl) on MakTail's 4.3 GE but ran into an issue that blocked further investigation:
The AntHalService tries to enable bluetooth, can't find the method and reboots the device.
The version is 3.0.0 which is supplied on Stock ROM, and there is already a 3.1.1 available from Ant Alliance which removes the requirement for enabling bluetooth.
I got the source code and compiled the apk, but I can't run it as a System App, so I got stuck. Spent some time trying to workaround it, but no success.
I guess that even when I get hold of a working 3.1.1, there will be new issues, and I'm a complete newbie on ROM cooking.
So I would like help from others, maybe suggesting next steps or getting hands on with me on this project.
XDA:DevDB Information
Ant+ Support for Non-Stock ROMs, a Tool/Utility for the Samsung Galaxy S 4
Contributors
AdrienC
Version Information
Status: Testing
Created 2013-11-25
Last Updated 2013-11-25
Attached is a file with the system files required for ant which I could find after some investigation.
Links:
Here is the source code for the AntHalService.apk which I couldn't run as System service.
https://github.com/ant-wireless/Android_ANTHALService
And the slooow forum:
http://www.thisisant.com/forum/viewforum/30/
to run as system app if you are rooted just manually copy apk to /system/apk
lgkahn said:
to run as system app if you are rooted just manually copy apk to /system/apk
Click to expand...
Click to collapse
won't work due to the signature I guess. Even when I signed with debug keys didn't work. Maybe due to SELinux?
Code:
I/PackageManager( 707): /system/app/AntHalService.apk changed; collecting certs
W/PackageManager( 707): Signature mismatch for shared user : SharedUserSetting{42a56d98 android.uid.system/1000}
W/PackageManager( 707): SELinuxMMAC.assignSeinfoValue
E/PackageManager( 707): Package com.dsi.ant.server has no signatures that match those in shared user android.uid.system; ignoring!
I am going to flash 4.4 GE edition by Jamal http://forum.xda-developers.com/showthread.php?t=2544474 and will try to survive with my Suunto USB Ant+ stick on OTG to allow me to spend more time trying to make this work.
Will update with any progress/issues.
Well, I send a cry for help to @broodplank1337 and got his awesome reply showing availability and this was my reply, which I decided to share as while I waited for help I made some pretty good advance!
While I was waiting for your reply I made some progress....
I replaced the classes.dex from my compiled apk(from java source) into the samsung apk and that was enough to bypass the cert check ( I was pretty sure I tried that before, but must've done something wrong).
I found out the source code is referencing a kernel module that doesn't exist for Galaxy S4, so I ran Dex2Jar and Java Decompiler and I'm now analysing the source code and I think that it somehow passes the instructions directly to the chip.
I'm thinking about trying to change the bluetooth methods it uses to the ones available on AOSP, which is why the 3.0.0 was failing initially.
It'll probably still take some work, but it might be feasible.
The main issue is that I'm new to android coding, and not a java expert, but used to be a programmer and I'm finding my way (and some joy) hacking thru all this code.
Click to expand...
Click to collapse
I'm attaching the source code for AntHalService.apk from Samsung stock roms (version 3.0.0).
I guess I'll have to work over it, as the 3.1.1 I got from AntWireless references an antradioservice.so which Sammy don't have and causes a bootloop.
I am now comparing the smali code between the 3.0.0 and the 3.1.1 to see if I can do an easy patch, but it's not looking very likely...
Lets see how this goes.
Awesome work guys! I'm really looking forward to be able to finally use my AOSP ROM (Paranoid Android at the moment) with Ant+ support! Just broke the Selfloops OTG dongle... I know many people are looking for a solution in the various fitness and sports communities...
Thanks in advance for your work!
Please please get this to work! I'm rooting for you on my side over here! It would make me one very happy s4 user.
Wouldnt it be nice if cyanogenmod one day supported ant+?
We can only dream.
Any luck? Or is there anything people who cannot code can do to help? This is the one thing I want on my android phone currently.
Guys, an update. I kinda gave up for a while. ANT Forums are helpless, and I got kinda tired of looking around. I'll need to have some free time and motivation to dissect the code and try to make it work on the AOSP bluetooth stack.
A good workaround I found is to have a dual boot solution, so you can switch to the Touchwiz ROM for a training.
karimero said:
Awesome work guys! I'm really looking forward to be able to finally use my AOSP ROM (Paranoid Android at the moment) with Ant+ support! Just broke the Selfloops OTG dongle... I know many people are looking for a solution in the various fitness and sports communities...
Thanks in advance for your work!
Click to expand...
Click to collapse
blue6800user said:
Please please get this to work! I'm rooting for you on my side over here! It would make me one very happy s4 user.
Wouldnt it be nice if cyanogenmod one day supported ant+?
We can only dream.
Click to expand...
Click to collapse
blue6800user said:
Any luck? Or is there anything people who cannot code can do to help? This is the one thing I want on my android phone currently.
Click to expand...
Click to collapse
Thanks, hope to eventually come with good news, got kinda sad to hit a wall. But meanwhile, use your favourite rom and dual boot a Touchwiz ROM.
I'm now back to the last released version of 4.3 for Brasil to soon extract the libs and apk's to build a slim TW ROM just for dualbooting.
It'll be an easier workaround. For those with 32GB S4's don't even need to go down this path, just dual boot and be happy!
Thanks for working on this, got the S4 the other day coming from a Bionic that was had ANT+ chipset, but they never turned it on. I too would love a CM 11 with ANT+ support. I will happen, eventually.
ant+ apps on the app store
Hi I'm running 4.4.2 Echoerom on my S4 and just discovered that I'm lacking ANT support despite installing the ant service and apps from the store. Did you try these apps, were you able to make any progress?
Any updates on this ?
I'd like to use ANT+ on my s4 running AOSB.
Any updates for ant+ support in CM11?
The solution of dual boot seems very messy for only that
any news with that?
I'm super late with this, but if anyone is still looking at building ANT+ in to custom ROMs, I have had success building from the ANT Wireless source: check the ANT hardware thread
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!!