The conversion to ION Memory Allocator has been provided by our devs, and thanks to Christopher83 we finally integrate the camera/video capturing functionality by enabling the pmem adsp heap allocation just for camera lib interface (libs are still the old version). All the rest of the allocation is provided via ION heaps. This version is not a full ion, but is a 99% ION and 1% PMEM.
Receiving and making calls
Hardware sensors (Light, Orientation, Compass, Proximity, Acceleration)
Legacy sensors / Virtual sensors (Gravity, Linear acceleration, Rotation vector)
USB mass storage
HW accelerated gui
HW accelerated video
USB OTG (Full FAT, FAT32, NTFS support) (check HERE the cables needed)
MicroSD exFAT support (Tested on Samsung 64GB SDXC uhs1 PRO card)
Phantom key presses filtering
zRam active by default (no more selectable/adjustable in settings -> performance... Only by init.d script)
Note: CM for Galaxy S Plus is provided with no warranty. You are installing this software at your own risk. You may be violating your warranty.
Download CM11.0 and gapps zips and put them in /sdcard
NOTE: To install Release 5 and next releases, you need to update the recovery to ADC Team TWRP v220.127.116.11 or CWM v18.104.22.168.
The recovery update must be done before flashing the rom. If you use a previous version of CWM or TWRP, the flash will generate an error. This is related to full support on Selinux.
ATTENTION: The new dynamic allocation through CMA of ION Heap (to free more ram and dynamically allocate ram when needed from MM features) requires to AVOID the memory management with KSM... if you activate the KSM option, after some time the allocation fail so the 720P recording and playback will be broken!! In this case disable the KSM option inside "Settings -> Performance -> Memory Management" and reboot the phone to fix!!
Rom is now built using Linaro GCC 4.8-2014.04 androideabi toolchain and
Linaro GCC 4.8-2014.04 arm-eabi toolchain optimized for Cortex-A8 cpu by Christopher83 device/samsung/ariesve
- services: Telephony: Move to correct path and fix incall mute feature (credits to Christopher83)
- Remove obsolete LPA prop (credits to arco68)
- Disable retire fence (credits to arco68)
- AriesParts: Update to 4.4 settings style (credits to CastagnaIT)
AriesParts: Remove a string no more used (credits to Christopher83)
AriesParts: Greek translation (credits to chrisg4)
AriesParts: Dutch translation (credits to Marshian)
AriesParts: Polish translation (credits to lexarks)
AriesParts: Chinese translation (credits to zxc123coke)
AriesParts: Hungarian translation (credits to shiftyHungary)
AriesParts: Remove no more used TouchKeyBacklight class (credits to Christopher83)
AriesParts: Reworked LowRam switch (credits to Christopher83)
AriesParts: German translation (credits to Rhonin86)
CameraHAL: Some changes and cleanup for better readability (credits to Christopher83)
CameraHAL: Use the orientation provided by camera info (credits to Christopher83)
GlobalActions: Set the initial status of airplane mode toggle (credits to Christopher83)
Revert "Remove harmful attempts to be helpful in pthread_mutex functions" (credits to Steve Kondik)
Allow forcing HighEndGfx mode (credits to Andrew Sutherland)
Add option to force high-end graphics on low memory devices (credits to Konsta Tuomio)
This option enables some graphics effects like the transparent notification bar.
You can find the new option inside Settings -> Performance -> Force High End Graphics
We built and tested these recoveries, but always remember that we are not responsible for any damage by using these software!!
They are based on safe kernel on emmc side.
Wipe data and cache.
Flash gapps*.zip. You must flash gapps after every upgrade to CM10 since /system is formatted, wiping your previous add-ons.
After you setup your Google account, reinstall the three apps from Market in order to restore most of your apps, call log and SMS history.
WARNING: Do not restore backup data of system apps!
If you restore a bad backup with cached settings in telephony.db in data/data/com.*.*.telephony it can break MMS.
It seems that restoring backups can also break Calendar sync.
Upgrades from previous versions of CM11.0 are the same process as install, except you do not need to wipe anything. Contrary to popular belief, you do not need to even wipe cache and dalvik-cache when upgrading between CM11.0 versions. You only need to wipe if you are doing a major upgrade, switching to a different ROM entirely, or attempting to fix bugs caused by bad backups or corrupt app data.
Please, do not use a custom kernel that is not updated for ION memory allocations.
You can upgrade a previously installed rom that uses PMEM allocations with this ION/PMEM ADSP version.
Arco68 for his huge work for our device
AriesVE Dev Connection Team
Nello96 for Team logo's
anakin174 for the team spare phone
All our sources are on AriesVE-DevCon-TEAM GitHub
For recovery bootloop problem you should at this post
BLNv10 feature recap:
It is activable/deactivable from AriesParts (Advanced Settings) or BLN Control Application (Free or Pro version)
XDA:DevDB Information [GT-I9001][KK 4.4.4] CyanogenMod 11.0 by ADC-Team - Kernel 3.4.x, ROM for the Samsung Galaxy S I9000
The calibration movement is a combined one over all axes, and will result in a residual magnetism removal (reset).
This calibration seems like a stupid game, but really this is the right way to recalibrate with a slow movement following the video shape; it is not important the direction to be used, just do once or more times until you get the calibration.
To know if the calibration has been done, you must know where is approximately the North and look with an app if the needle is pointing there; if yes, try rotating the phone of 90, 180, 270 and finally back to 360 degrees and look if the needle is pointing everytime to North during the rotation... If this easy test give positive results, your phone is calibrated!
Note1: After this procedure, the orientation and magnetic field sensors will give the correct values with all apps.
Note2: Our phone is known to have a native shift of some degrees respect to the North, but this is a hardware limitation due probably to the orientation of the chip welded on the board...
Note3: This procedure can be used also after a new flash of a compatible custom kernel in case of orientation not correct...
LEGACY SENSORS / VIRTUAL SENSOR
This sensors are defined virtual becouse our device don't have the hardware of this sensors,
utilizing some data processing techniques by performing a data fusion of accelerometer and magnetometer sensors,
it is possible extrapolate the data to derive these sensors, in an approximate way.
Please note that not all apps support the virtual sensors
to do a test we recommend the S Tools+ app.
"The rom is stuck at splash screen, bootloop!"
-Use the NEWEST TWRP/CWM from US. Do not use any other recovery except the linked one in the thread!
"I heard on KitKat the statusbar is transparent. Why not in this rom?"
We have enabled the low_ram token by default. This disables the transparent effects and saves ram. If you want the statusbar transparent, open your appdrawer and choose ariesparts. Now go to "Enable/Disable Low Ram" and press the switch button, reboot and done!
"Why I can't add widgets on lockscreen?"
We have enabled the low_ram token by default. This disables in general and depending on app some features to save ram. If you want to add widgets on lockscreen, open your appdrawer and choose ariesparts. Now go to "Enable/Disable Low Ram" and press the switch button, reboot and done!
"Where are the CyanogenMod settings (Battery styles etc..)?"
- CM11 is still WIP, build after build the settings will be there again.
"Will there be builds for the Galaxy W (same chipset)?"
-We dont know. When we finish the work on ION and have some free time, we will discuss about it.
"What is ART?" First - ART is in the "DEVELOPER OPTIONS" for a reason!!
ART is the new selectable runtime virtual machine included in KitKat and intended to replace Dalvik VM in the future.
At the moment, the default runtime virtual machine (VM) on KitKat and the only one available on previous Android versions is Dalvik VM.
Apps, excluding their native parts, are compiled from Java source code (but also written with other high-level languages) to a particular intermediate-level language, called byte-code, architecture independent, portable and runnable on every system that has the same/similar runtime VM. When the app is launched, its various required byte-code parts are loaded from disk, interpreted by the VM, compiled in machine code and then stored in RAM ready for the real execution. This process (known as JIT, just-in-time) requires some time and is not so efficient in terms of execution performance and cpu use, expecially on a device with a single core cpu...
With ART runtime VM every app is compiled directly in machine code when downloaded from Play Store or during the first boot process after enabling this kind of VM.
This means that there's no need to compile again and again the app byte-code when an app is launched, less time required to launch the app, less cpu use, better performance.
At the moment, ART is in an experimental stage and not all apps are supporting it (they simply force closes when launched).
But in the future, this will be surely a second life for our device. (Thanks to Christopher83 for this nice explaination!)
"Why does ART result in a bootloop?"
-The conversion from Dalvik to ART can take around 20 - 60 minutes, depending on how many apps you have installed. The bootanimation will be visible for a long time, so stay petient. BTW - If you installed Xposed framework ART will stop working.
"Why does ART result in app-fc`s?"
-Art is still very very alpha. In fact, there were people who wanted to remove it from the CM builds because of that, but it didnt happen. We recommend you to use Dalvik if you want to use this rom as daily driver.
"Are the DevCon-GApps odexed or deodexed?"
-The DevCon-GApps are made by ktulu84, they are based on CM Gapps DEODEXED and COMPATIBLE with art.
"Gesture typing doesnt work?"
-AOSP Bug, please install Google Keyboard from the Playstore or as .apk. Also Swiftkey works correctly.
"Are 64GB Micro SD cards supported?"
-Yes, they are. Smeroni68 is using one in his phone, and it works very well. (Tested on native exFAT Samsung 64GB SDXC uhs1 PRO card)
"Where are the AriesParts/Advanced settings?"
-CyanogenMod has removed it from settings. You can find the Advanced settings inside the Appdrawer.
"Playstore doesn work after Upgrade to newer build of CM11!"
-Reinstall DevCon-GApps. If this doesn't work format system, flash rom and DevCon-GApps. if this still doesn't work remove google account, reboot your phone and then readd your google account.
"MX-Player says "Not supported Android version"
Update MX-Player from market up to v1.7.21
"Where is the "Performance menu"?"
To add Developer Opitons & Performance menu, you have to open Settings -> Device Info and tap 7 time on Build Number.
with this new build some of the faced problems on previous rom with PMEM builds are now solved.
It's now possible to use both stock browser and other browsers, the apps based on webview works correctly, no more glitches in camera app and Google Maps. Thanks to updated Adreno libs and kgsl kernel drivers you will have better performance and an overall smoothness.
On kernel side, there are also a lot of updates on framebuffer, display, video drivers and some updates for binder and ondemand governor.
You can find also a new added feature:
As explained on Wikipedia, this feature, provided in this kernel as a standalone loadable module, increases performance by avoiding paging on disk and instead uses a compressed block device in RAM in which paging takes place until it is necessary to use the swap space on the hard disk drive.
In few words, the memory pages no more used and so to be swapped are sent to zRam device blocks, compressed and stored in memory instead of disk allowing better performance and also lower memory usage, on the other hand, a little higher amount of cpu is needed to perform compression and decompression of memory pages.
Since we have a device with a low amount of free memory, this feature could be useful to have more free ram.
You can enable it inside System Settings -> Performance -> Memory Management -> zRam by choosing your preferred compression option (18% is the default one).
Seemingly every day, there are a bunch of new devices being released. Some are budget devices and some are … more
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?