Hi there, I always liked aosp/aokp builds, but I never kept them.
I run on samsung based roms.
so there is the question:
customization over features?
only in samsung rom we have the best FM radio, camera, MHL and others
which cannot run on aosp.
can't we mix the frameworks to have the best of 2 worlds?
can we hack samsung apps to run on aosp?
There is no way to get these features working on AOSP/AOKP. But if you use a ROM that is based on Sammys software, you will get these features, plus some tweaks and modifications that give it more speed/better battery/more customisation etc.
firstly, there is a mixed-framework rom afterall. :good:
second:
WHO copies OUR posts and re publishes them with different names in other sites?
http://samsunggalaxyandroid.net/2012/05/samsung-vs-aosp/
Related
I am wondering why there is so much different between rom size of CyanogenMod 7 & MIUI as compare to other roms. These two roms are max of 110 mb where as other custom roms are 250MB to 330 MB even stock is around 300MB.
I know there are no Google apps on those two roms but that doesn't make much difference.
Any one can explain this.
Its because Sammy are bloated because all their proprietary apps.
Sent from HydrOG3N MOD S2.
Technology Evolves, Android Evolves.
HydrOG3N is THE Revolution.
Think about it.
CyanogenMod is a STOCK android Rom built in with no apps. MIUI runs on CyanogenMod's base so its basically the same.
Samsung based roms comes with a lot of built in software including Kies Air, AllShare, TouchWiz interface, Camera apps, etc. This costs memory, and a lot of it too.
Sent from my Samsung Galaxy S II (GT-I9100) using XDA-App
Basically cyogenMod and mui are stripped roms in which you customs with what ever apps.
Other roms are stock roms with common apps added.
Custom roms are stock roms with personalized tweaks and custom themes added for you.
I always freeze the Samsunng bloatware anyway applications like KIES are crap anyway same as most of the bloatware.
Keep seeing this mentioned in rom features and haven't been able to find the difference.
Sent from my Galaxy Nexus using xda premium
Stock anything is just that, the manufacturer stock app or ui, CM (Cyanogen Mod) is a highly tweaked and modified Pure Android (also called Vanilla) experience with no Manufacturer, Carrier or Google bloatware.
Edit: forgot to mention, you may see apps or themes that say CM with them to show that they are compatible with cyanogenmod roms, because not everything may be.
MoPhoACTV Initiative
This is from the Cyanogenmod wikipedia Page
http://en.wikipedia.org/wiki/CyanogenMod
CyanogenMod is a replacement firmware of over 60 smart phones and tablet computers, based on the Android mobile operating system. It offers features and options not found in the official firmware distributed by vendors of these devices. Features supported by CyanogenMod include native theming support (also called the "T-Mobile Theme Engine"), Free Lossless Audio Codec (FLAC) support, a large Access Point Name list, an OpenVPN client, a reboot menu, support for Wi-Fi, Bluetooth, and USB tethering, CPU overclocking and performance enhancements, soft buttons and other "tablet tweaks", toggles in the notification pull-down (such as Wi-Fi, Bluetooth and GPS), app permissions management, as well as other interface enhancements. CyanogenMod is also stated to increase performance and reliability compared with official firmware releases. [2]
CyanogenMod is developed as free and open source software based on the official releases of Android by Google, with added original and third-party code. Although only a subset of total CyanogenMod users elect to report their use of the firmware, [3] as of 26 January 2012, CyanogenMod has recorded over 1.1 million active[4][5]
MoPhoACTV Initiative
Thanks for your input. I welcome all the tweaks and modifications cyanogen and
other developers use as they sometimes are highly beneficial.
Sent from my Galaxy Nexus using xda premium
Most of the AOKP Roms for this device are "Excellent" but all lack one simple feature.....you can't use Dialpad function codes ( like; **87284 for Diag Mode ). As advanced as these Roms are why is it so difficult to add to the Roms? Someone please shed some light on this subject or even a "FIX" would be better. I am definitely no expert at any of this but surely compared to building a Rom, incorporating those functions shouldn't be that big of a deal. Correct me if I'm wrong....
If there is a 4.0+ AOKP Rom for this device that the Dialpad Functions work on PLEASE let me know...Thanks!!
devo3d said:
Most of the AOKP Roms for this device are "Excellent" but all lack one simple feature.....you can't use Dialpad function codes ( like; **87284 for Diag Mode ). As advanced as these Roms are why is it so difficult to add to the Roms? Someone please shed some light on this subject or even a "FIX" would be better. I am definitely no expert at any of this but surely compared to building a Rom, incorporating those functions shouldn't be that big of a deal. Correct me if I'm wrong....
If there is a 4.0+ AOKP Rom for this device that the Dialpad Functions work on PLEASE let me know...Thanks!!
Click to expand...
Click to collapse
in an excerpt from djp952 GeeWiz he explains it best... LINK
http://forum.xda-developers.com/showthread.php?p=40639862
He Says::
the reason those codes don't work is because they are not part of AOSP. GeeWiz 2.9 is Samsung TouchWiz, GeeWiz 4 is AOSP, so those codes do not exist. 772 is to set the serial mode for CDMA diagnostics, right? My kernel doesn't support that either, it was removed when I updated the USB drivers to get rid of all the Samsung proprietary stuff like the CD-ROM mode. It could probably be re-added, but I think most people that would want to do things like this would be better off with a different more feature-rich ROM anyway. The other code seems to be for other CDMA related activities, my knowledge of telephony is limited and I won't be adding support for either of these codes. Sorry. It kinda is what it is. If you want to access everything that Samsung designed into the phone, I think your only real option is stock, GeeWiz 2.9, or other older Gingerbread ROMs based on Samsung's code base.
.
hhp_211 said:
in an excerpt from djp952 GeeWiz he explains it best... LINK
http://forum.xda-developers.com/showthread.php?p=40639862
He Says::
the reason those codes don't work is because they are not part of AOSP. GeeWiz 2.9 is Samsung TouchWiz, GeeWiz 4 is AOSP, so those codes do not exist. 772 is to set the serial mode for CDMA diagnostics, right? My kernel doesn't support that either, it was removed when I updated the USB drivers to get rid of all the Samsung proprietary stuff like the CD-ROM mode. It could probably be re-added, but I think most people that would want to do things like this would be better off with a different more feature-rich ROM anyway. The other code seems to be for other CDMA related activities, my knowledge of telephony is limited and I won't be adding support for either of these codes. Sorry. It kinda is what it is. If you want to access everything that Samsung designed into the phone, I think your only real option is stock, GeeWiz 2.9, or other older Gingerbread ROMs based on Samsung's code base.
.
Click to expand...
Click to collapse
Wow, really :silly::silly:
Hi!
I was wondering whats the status of the AOSP apps now that most of them are replaced by Googles own suite of apps?
Are they completely abandoned, or do they get just updates on new Android versions to make use of the new APIs that come with it?
I've read in a lot of articles that Google stopped all development of AOSP apps because they are focusing on their own apps, but that opens up another question:
If its so, how come nobody from the dev community is doing any work on AOSP apps and submiting those changes back to AOSP?
Does Google forbid or decline commits to AOSP apps?
Im wondering because it doesnt make sense that some custom ROMs develop their own AOSP app replacements instead of submiting improvement changes to the AOSP directly.
Many people use AppLocks to secure certain apps that they wouldn't want others to have access to when they pass over a phone to family or friends. MIUI's inclusion of Applock into it's ROM goes on to prove my point.
Why don't the custom roms then have AppLock implementation directly to the ROM in general? Never seen a custom rom include this feature, although several of them providing a ton of features.
The Applock's implementation directly into the ROM provides better security too (Being part of the system apps) and is a more seamless interface.
I'd be glad if anyone can answer my query.
Also if it's possible do tell me if I can implement Applock into my ROM directly through someway maybe a zip to flash?
thedarkraven said:
Many people use AppLocks to secure certain apps that they wouldn't want others to have access to when they pass over a phone to family or friends. MIUI's inclusion of Applock into it's ROM goes on to prove my point.
Why don't the custom roms then have AppLock implementation directly to the ROM in general? Never seen a custom rom include this feature, although several of them providing a ton of features.
The Applock's implementation directly into the ROM provides better security too (Being part of the system apps) and is a more seamless interface.
I'd be glad if anyone can answer my query.
Also if it's possible do tell me if I can implement Applock into my ROM directly through someway maybe a zip to flash?
Click to expand...
Click to collapse
LineageOS 14.1 has this feature
Noter2017 said:
LineageOS 14.1 has this feature
Click to expand...
Click to collapse
Yeah but then LineageOS 15 again removed it. Why was that? Does that cause problems or affects performance?
thedarkraven said:
Yeah but then LineageOS 15 again removed it. Why was that? Does that cause problems or affects performance?
Click to expand...
Click to collapse
Changing from 14.1 to 15.0 they removed many features and are bringing them back one by one. They currently focus on stability.
Even a simple feature like center clock was added 3 only weeks ago. So it can take a while till App Lock is back