[9001][ROM][PMEM][KK][4.4.1][KOT49E] CyanogenMod 11.0 by ADC-Team - Alpha 3 (EOL) - Kernel 3.4.x

[DevConnection_Team]

[9001][ROM][PMEM][KK][4.4.1][KOT49E] CyanogenMod 11.0 by ADC-Team - Alpha 3 (EOL) - Kernel 3.4.x

Hi everyone,
We are back! And we are proud to present our build of CyanogenMod 11.0 for the Galaxy S Plus (GT-I9001).

Currently the team is composed by the following members: (in alphabethic order)

[Dev] CastagnaIT, Christopher83, Educk, Ivendor, Krislibaeer
[Tester] smeroni68, ktulu84, Xellar

What's working:
Audio
Receiving and making calls
GPS
Compass
Proximity sensor
Wifi
Bluetooth
USB mass storage
HW accelerated gui
HW accelerated video
Camera
BLNv9
USB/Wifi tethering
VSync
USB OTG (Only FAT32 support) (check HERE the cables needed)
Phantom key presses filtering

Fixed and working:
Screenshot
Multitasking preview
Lockscreen slider shortcuts
Quick panel tiles

Partially working:
Some graphical glitches in Panorama preview
Web browsing with stock brower not really good (install Chrome or other browser for better use)


Not working:
AOSP keyboard do not work if used with swipe (app related bug)
SD swap do not work (not yet implemented)

Screenshots

CM11.0Installation Guide

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

WARNING: TO FLASH YOU MUST USE ONE OF THE RECOVERY OF THE TEAM... IT'S NOT AN OPTIONAL CHOICE!!!

• 20131207 Alpha 3 (DL from Dev-Host)
  MD5SUM: 43d4a53a399e067bccc93a2e95b332a6
  
  ROM:
  • AriesParts: add LowRam status (credits to krislibaeer)
  • ramdisk: mountpoints like in aosp description (credits to krislibaeer)
  • ramdisk: internal_sd noemulated and external_sd auto type (credits to krislibaeer)
  • Synced with CM sources (KitKat v4.4.1 - KOT49E)
  
  20131207 KERNEL: (DL from Dev-Host)
  MD5SUM: aaded2fd824af9c2dda125c952f2f4de
  
  ATTENTION: This kernel is included in the rom... this download is in case of custom kernel installed and want to come back to stock!
  
  • Kernel 3.4.72

• 20131116 ADCT GApps (DL from Dev-Host)
  MD5SUM: 381d117be483cf672ac33887d212d765

Please verify the md5sum to be sure you got the right one.


Previous versions:

• 20131201 Alpha 2 (DL from Dev-Host)
  MD5SUM: 4fd0b5178227f2db23d5269889bed325
  
  ROM:
  • media_codecs: Add Google's VP8 and VP9 decoders for 4.4 (credits to erik96)
  • overlay: remove adb by default cm 11.0 is running (credits to krislibaeer)
  • BoardConfig: remove deprecated usb config (credits to krislibaeer)
  • AriesParts: improve low_ram switch (credits to krislibaeer)
  • BoardConfig: add QCOM_ENHANCED_AUDIO flag (credits to krislibaeer)
  • BoardConfig: add BOARD_HAVE_PRE_KITKAT_AUDIO_BLOB := true flag (credits to krislibaeer)
  • BoardConfig: Enable support for mHeap based screenshots (credits to Christopher83)
  
  20131201 KERNEL: (DL from Dev-Host)
  MD5SUM: 8b42f021aab0ba062f07b791ba3a2d46
  
  ATTENTION: This kernel is included in the rom... this download is in case of custom kernel installed and want to come back to stock!
  
  • Kernel 3.4.71
  • crypto: msm: Check for invalid byte offset field (credits to Mona Hossain)
  • crypto: msm: Check destination buffer write access (credits to Mona Hossain)
  • crypto: msm: Fix issues related to non-zero byteoffset input (credits to AnilKumar Chimata)
  • crypto: msm: Fix null pointer exception in qcrypto_count_sg() (credits to AnilKumar Chimata)
  • crypto: msm: Use scnprintf() instead of snprintf() (credits to AnilKumar Chimata)

• 20131124 Alpha 1 (DL from Dev-Host)
  MD5SUM: 877c516052ff1303a1ae84a6a8962cb1
  
  ROM:
  • Change some mount points (credits to Arco68)
  • ariesve: switch to kernel build during compile rom (credits to krislibaeer)
  • Initial support for the hardware tunables framework (credits to Czobor)
  • Overlay: Add custom arrays to base frameworks (credits to erik96)
  • BoardConfig: woraround create the folder /usr to prevent the build from failing (credits to krislibaeer)
  • Disable PhaseBeam scrolling (credits to Michael Bestas)
  • Set ro.telephony.call_ring.multiple=0 (credits to Arco68)
  • ril: Updates for Android 4.4 alias kitkat (credits to krislibaeer)
  • BoardConfig: Use cortex-a8 error on scorpion (credits to krislibaeer)
  • libsensors: fix build error (credits to krislibaeer)
  • overlay: remove disable the home key unlock settings in frameworks_base for now (credits to krislibaeer)
  • recovery: change graphics.c to fit with new changes (credits to krislibaeer)
  • BoardConfig: add TARGET_RUNNING_WITHOUT_SYNC_FRAMEWORK := true new feature on 4.4 (credits to krislibaeer)
  • ariesve: add ro.config.low_ram new feature on android 4.4 (credits to krislibaeer)
  • ramdisk: apply changes to wlan to get it working (credits to krislibaeer)
  • BoardConfig: add USE_SET_METADATA := false, for now we need this because otherwise the flashable zip is not flashable (credits to krislibaeer)
  • overlay:apps: change Phone to Telephony (credits to krislibaeer)
  • ramdisk: changes to sdcard mount Android 4.4 (credits to krislibaeer)
  • ariesve: add a bit debug stuff (credits to krislibaeer)
  • sepolicy: Add policy configuration for SELinux (credits to Christopher83)
  • ril: fix sim PIN handling (credits to Pawit Pornkitprasan)
  • ariesve: build memtrack (credits to krislibaeer)
  • ramdisk: change also usbdisk mount for android 4.4 (credits to krislibaeer)
  • BoardConfig: add flag BOARD_EGL_WORKAROUND_BUG_10194508 := true (credits to krislibaeer)
  • BoardConfig: let camera working again (credits to krislibaeer)
  • overlay: add Enable lockscreen translucent decor (credits to krislibaeer)
  • ramdisk: add KSM by default (credits to krislibaeer)
  • ariesve: Disable JIT cache (credits to krislibaeer)
  • ariesve: disable preloading of EGL/GL drivers in Zygote at boot time (credits to krislibaeer)
  • overlay: add extraFreeKbytes - new feature Android 4.4 (credits to krislibaeer)
  • AriesParts: add low_ram switch (credits to krislibaeer)
  • ril: aligned custom ariesve ril to SamsungExynos3RIL (credits to CastagnaIT)
  • Corrected the ril property and some updates (credits to CastagnaIT)
  • BoardConfig: removed no longer needed BOARD_USE_LEGACY_TOUCHSCREEN (credits to CastagnaIT)
  
  20131124 KERNEL: (DL from Dev-Host)
  MD5SUM: 0560e06571327b4076029e75e84b3483
  
  ATTENTION: This kernel is included in the rom... this download is in case of custom kernel installed and want to come back to stock!
  
  • Kernel 3.4.70
  • msm: kgsl: Avoid turning on GPU clock if already off (credits to Ananta Kishore K)
  • Update defconfigs to enable some netfilter options (credits to Christopher83)
  • Revert "ALSA: fix oops in snd_pcm_info() caused by ASoC DPCM" (credits to Christopher83)
  • Add exFAT support (credits to radu) (Tested on Samsung 64GB SDXC uhs1 PRO card)
  • Update defconfigs for exFAT support (credits to Christopher83)
  • msm: vidc: Reset stop_called state when START is called (credits to Deepak Verma)
  • msm: vidc: set EOS on output buffer pending transaction (credits to Deepak Verma)
  • Clone ion.h to msm_ion.h (credits to Arco68)
  • Add extra free kbytes tunable (credits to Rik van Riel)
  • input: Updates to Phantom Key Presses filter (credits to Christopher83)
  • SELinux: include definition of new capabilities (credits to Eric Paris)
  • msm: vidc: Check validity of userspace address (credits to Deepak Verma)
  • ALSA: pcm: check for integer overflow during multiplication (credits to Phani Kumar Uppalapati)
  • base: genlock: Zero a structure before sending it to user space (credits to Jordan Crouse)
  • qt602240_ts: updated touchscreen driver in according of Multi-touch protocol (credits to CastagnaIT)

• 20131116 ADCT GApps (DL from Dev-Host)
  MD5SUM: 381d117be483cf672ac33887d212d765

Before you install CM11.0: Preparation (First three are optional. If you want to start fresh, these can be skipped)

1. Install AppBak from Market, run it and save a list of all your apps.
2. Install SMS Backup and Restore from Market, run it and backup your SMS history.
3. Install Call Logs Backup and Restore from Market, run it and backup your call log history.
4. Boot into recovery. Make a full backup. You will need this backup later if you decide to go back to your previous ROM and data.

WARNING: Many apps will Force Close crash if you restore data from a previous ROM.

Install

1. Here you can find the CWM Recovery and TWRP built by our Team:
   
   WARNING: TO FLASH YOU MUST USE ONE OF THE RECOVERY OF THE TEAM... IT'S NOT AN OPTIONAL CHOICE!!!
   
   >>>> CWM & TWRP Thread
   
   WARNING: 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!!
   
2. Wipe data and cache.
3. Flash update*.zip.
4. Flash gapps*.zip. You must flash gapps after every upgrade to CM10 since /system is formatted, wiping your previous add-ons.
5. Reboot phone.
6. 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
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.


Credits
CyanogenMod Team
Arco68 for his huge work for our device
AriesVE Dev Connection Team
Nello96 for Team logo's
anakin174 for the team spare phone

Sources
All our sources are on AriesVE-DevCon-TEAM GitHub


FAQ

• For recovery bootloop problem you should at this post
• BLNv9 feature recap:
  • It is activable/deactivable from BLN Control Application (Free or Pro version)
  • You can launch it from Settings->Device->Advanced

XDA:DevDB Information
[GT-I9001][KK 4.4.1] CyanogenMod 11.0 by ADC-Team - Kernel 3.4.x, a ROM for the Samsung Galaxy S I9000

Contributors
DevConnection_Team, smeroni68, CastagnaIT, Christopher83, educk, ivendor, krislibaeer, ktulu84, XeLLaR*
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod

Version Information
Status: Alpha

Created 2013-11-25
Last Updated 2013-12-21

 

[DevConnection_Team]

Calibration of Magnetic/Orientation/Acceleration sensors

MAGNETIC / ACCELERATION / ORIENTATION SENSORS CALIBRATION

This procedure is necessary in case of ROM update and anyway when magnetic sensor has residual magnetism (so it do not give reliable readings).

CALIBRATION PROCEDURE:

1) Standard horizontal calibration through the CM advanced menu, by placing the phone over a flat and horizontal surface and pressing Calibrate touch button

2) Magnetic field calibration by following an 8 shape to be done as shown in this video: HOW TO CALIBRATE ELECTRONIC COMPASS

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 or Rom in case of orientation not correct...

 

[DevConnection_Team]

Reserved

F.A.Q - CyanogenMod 11

"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!

"Is it PMEM or ION?"
- At the moment CM11 is based on PMEM. We are working on ION in the backround and it should be ready soon.

"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 XeLLaR*, he kept the odex files to let ART work for experiments. Long story short: odexed.

"Why are all browsers except for Opera and Chrome so laggy?"
-Google changed the native browser engine from WebKit to Chromium. This means only Chrome based browsers will work usable on CM11 till we update the rom from PMEM to ION.

"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. You should do this everytime you flash a rom!

"When will you release the ION Roms?"
-As soon it is ready for public release and our tests are finished!

"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.

"Where is the AOSP Calendar App?"
-Not longer present in AOSP,CM - use Google Calendar from Playstore, it looks exacly the same.


​

 

[janesz1981]

hmhm great! :] its pmem or ion?

 

[XeLLaR*]

Have fun with it guys!

P.S: Its PMEM
And thanks to Krislibaeer we included something very special and unique in the AriesParts.
You can switch between Android 4.4's Low Ram and Normal mode at any time.
The Low_Ram token sets a special mode where some features such as Transparent statusbar are disabled, but saving around 40-60MB Ram (depends on installed apps).


Gesendet von meinem GT-I9001 mit Tapatalk 2

 

[mitza4fun]

Amazing work !! Thanks a lot !!

 

[TwinHeadedEagle]

Amazing, thank you so much, will flash immidiately

 

[TheTechnolgyhelper]

Great work Team I wait a bit when the Rom will be more stable

Gesendet von meinem GT-I9001 mit Tapatalk

 

[Nello96]

Performance are a little bit better than 4.2.2, i noticed no lag at all in UI. The problems are just the glitches included in OP, but it's really really nice for an alpha 1.

Also, little glitch in lockscreen if using PIN Unlock, but i think it's a source problem. Am I wrong or Cyano Team hasn't realeased a stable release for any device yet? You were so fast! Great guys, keep it up!

 

[isouzz]

Thank you, I wait impatiently that the rom is stable.

 

[przemekamag]

Amazing !!!!! Thank you !!

Wysłane z mojego GT-I9001 przy użyciu Tapatalka

 

[Laurentyu1995]

That's AWESOME !!!

Sent from my GT-I9001 using xda app-developers app

 

[rboy28]

Cool. Thanks guys
Just wait for feedback from others - but I'm trying CM10.2 R1 for the next time before switching to this ^^

 

[shiftyHungary]

Wow. Such awesomeness
Immediate install, been waiting this eagerly :cyclops: I bet there'll be a stable release in a week, with such a dev team :highfive:
Nice to see these old devices ain't dead yet :cowboy:

 

[DevConnection_Team]

Important features introduced in latest builds

Hi guys,
inside this first build you can find:
- Better memory management for our device that has a low amount of free memory (credits to Arco68 and krislibaeer)
- The touchscreen driver has been updated, it's no more a legacy touchscreen (credits to CastagnaIT)
- The old RIL class (phone and network data connection) has been replaced by SamsungExynos3RIL, more updated and supported by CM (credits to CastagnaIT)
- exFAT filesystems support (credits to radu)
- Phantom key filter module V2, updated to be more reliable when HOME key filtering is enabled, also with more permissive settings (credits to Christopher83)
- Low Ram switch inside AriesParts (credits to krislibaeer)

 

[oscarmalo]

thank youuu!!!!

 

[w4v3]

Big thanks to you guys!

 

[GamaPL]

It's really great, that KitKat is coming for our device but i was wondering what are the differences between Android 4.3.1 and android 4.4 according to S+

 

[sgspluss]

Compare both OPs then you will know
Also this are Alpha and CM10.2 are in Releasephase...

 

[TwinHeadedEagle]

Cannot find Battery look and similar options that existed in 4.2.2? Any thoughts?