Hi everyone, here we are... AriesVE Dev Connection Team!!
The first unofficial team work has started analyzing/testing and fixing a problem of battery consumption in the CAF kernel 3.4.
A bunch of dev and tester has fixed in a week of cooperation the battery drain, and we have seen that joining the forces is more helpful in case of common issues...
That is how is born the DevConnection Team.
Currently the team is composed by the following members (in alphabethic order):
This release of CM10.1 is based on Arco development for Galaxy W with the configuration part of Ivendor CM10 rom
Receiving and making calls
USB mass storage
HW accelerated gui
HW accelerated video
USB OTG (Only FAT32 support) (check HERE the cables needed)
Phantom key presses filtering
Some graphical glitches in Panorama preview
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 CM10.1 and gapps-jb zips and put them in /sdcard
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!!
Wipe data, cache and Dalvik cache
Flash the rom file *.zip.
Flash the gapps file *.zip. You must flash gapps after every upgrade to CM10.1 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 CM10.1 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 CM10.1 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.
You can report bugs on our Google Code account. Please search if the bug you want to report has already been reported before you report it.
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
How to prepare SD for patched eMMC use?
The installation process is always the same, you need to partition your external sd in this way:
1) First partition formatted fat32 to use as external storage (set as Primary)
2) Second partition formatted EXT4 (1,5GB at least) to use as /data partition (set as Primary)
NOTE: as you might know the order of these partitions is important!
To wipe data you have to format your EXT4 partition on extSD card or use the patched recovery from here (http://forum.xda-developers.com/show....php?t=2204700)
We did not tried that, but think that should work, and to backup data you can backup your partition or use the same recovery we linked before.
The installation order is ROM -> GAPPS -> EMMC PATCH
For recovery bootloop problem you should at this post
BLNv9 feature recap:
It is activable/deactivable from BLN Control Application (Free or Pro version)
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...
Here you can find the first public version of CM10.1 ION rom and kernel (Alpha 1)
NOTE: This version is published "AS IT IS"... no support is given, no sources published (because still in development)... please do not ask for fixes or other modifications!!!
This version is a full Ion mem allocator system, where has been completely removed the support of cameras. The development on this side will take longer, so we decided to publish this version to let you play a bit with a full ion allocator.
The most important update on this version is the GPU Adreno driver and libs: the drivers are the Vanilla one, because the MR1 has created many problems.
The rom is full working, but the missing of the cameras support will give as result that camera apps will go in FC in case of opening.
We prepared also a stock kernel with enhanced free ram (371 instead of 351MB) by removing as much as possible the ion mem allocation for camera buffer (download available both 351MB and 371MB kernel); to preserve video playback, a part of the buffer must be allocated...
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?