[ROM/DEV] Unofficial CyanogenMod 7.2.0-RC0 "GalaxyMini" Port

Note: This port is 100% built from source, heavily based on my "Galaxy5" device sources. The reason why I have decided to develop/release this ROM is that I prefer to use a vanilla CyanogenMod build (with no customized/extra apps included), and I noticed some issues with all existing builds (e.g. FM radio, audio device routing, native CyanogenMod USB tethering) which I have already fixed in my Galaxy 5 port.

I don't actually own this phone, but I will offer support in my free time while I still have the device in my possession, and sources are provided.

CyanogenMod 7.2.0-RC0 "GalaxyMini" Port
Latest release: v1.2 [26 January 2012]
Latest Google Apps package: official: 20110828

Hey folks,

This is a port of Cyanogen 7.2.0-RC0 (based on Android Gingerbread 2.3.7) for the Samsung Galaxy Mini (GT-S5570) phone. The current port status is stable - most hardware is working correctly, but see post #2 for known issues.

Thanks to all who have contributed/shared code from the Galaxy 5 port, as well as coolya, tj_style and teamhacksung for the kernel patches and reference Tass device configuration.

Pre-requisites:

• Your phone must have a Gingerbread bootloader installed (as it uses the 2.6.35 kernel & Gingerbread proprietary files).
• Any version of ClockworkMod that supports EXT4 partitions. Unfortunately, the build supplied with ROM Manager doesn't seem to be compatible.
• Recommended: ensure that you have a backup of your current ROM and user data.

Installation:
Note 1: you always need to re-install the Google Apps package after installing a full update package.

• Reboot into ClockworkMod. You can do this via adb reboot recovery, or by choosing the Reboot -> Recovery menu if you are already using CyanogenMod.
• If you are upgrading from a stock or custom ROM, you absolutely must perform a data wipe: Select wipe data/factory reset and confirm the operation. Note that you will lose all of your user data, so be sure that you have performed a backup. Otherwise, skip to the next step.
• Choose the option install update from sdcard -> choose zip from sdcard. You will see the two (or three) .zip files in the list.
• You must install the two (or three, if you have a hotfix) files in this exact order:
  • The base package named update-cm-7.X-GalaxyMini-vY.Z-MADTEAM-signed.zip
  • [If exists] The latest hotfix package for the same base package version, named GalaxyMini-vX.Y-hotfixZ.zip
  • The Google Apps package, named gapps-gb-DATE-signed.zip
• Once all packages are installed, you can now reboot.

Installation (hotfix update only):
Note 1: hotfixes are cumulative - this means that you only need to install the latest hotfix, because it contains all the fixes of previous hotfixes.
Note 2: you don't need to re-install the Google Apps package if you are only installing a hotfix update.
Note 3: only install hotfixes that match the full update package version (e.g. v1.5hotfix1 only matches release version v1.5).
Note 4: hotfixes do not require a data-wipe.

• Download the latest hotfix package and transfer to the SD card.
• Reboot into ClockworkMod Recovery.
• Choose install update from sdcard -> choose zip from sdcard, select the hotfix and confirm installation.
• Reboot.

Latest Changelog:
Note: "Data wipe?" only refers to when you upgrade from a previous version of my ROM - not anybody else's. For every other case, follow the guidelines of the Installation section above.

• v1.2 [26 January 2012]
  • Data wipe? Only if you experience problems.
  • Updated CyanogenMod source.
  • Now includes ICS transition and rotation animations (merged officially into CM7.2).
  • Fix for rare issue where notification area items can get "stuck", causing notifications to malfunction.
  • Kernel: removed Samsung's drop_caches code in order to prevent periodic cache flushes that can reduce performance.
  • Wifi: disabled combo scan due to problems with reconnect from idle; tweaked TCP buffering to improve performance.
  • Bluetooth: improved configuration (enabled HFP support, increased max BT connections from 1 -> 3).
  • libaudio: updated code & removed proprietary liba2dp.so.

• v1.1 [20 January 2012]
  • Hotfix 1 [20 January 2012]: Improve wifi connectivity (changed from ar6000 -> wext wpa_supplicant driver with combo scan enabled, enable ssid scanning in configuration to fix hidden networks); add missing FM Radio application; updated proprietary files with newer versions and added some missing files to fix keymaps.
  • Data wipe? Only if you experience problems.
  • Updated CyanogenMod source.
  • Kernel: fixed charge reboot issue (thanks to squadzone for tip).
  • Kernel: patched bma_accel_driver.c to enforce minimum poll_delay threshold. This fixes all Google Maps 6.x issues, and will probably also fix lag issues in applications that try to excessively poll sensor data.

• v1.0 [15 January 2012]
  • Hotfix 2 [17 January 2012]: Framework: reduced LatinIME key height in landscape mode (.25in -> .23in). Kernel: tweak smartassV2 CPU scheduler to make better use of the Mini's available CPU frequencies; removed SCHED_HRTICK kernel tweak due to instability/random reboot issue; update CPU & AHB overclock code (CPU overclock up to 864Mhz, but 844Mhz seems to be the maximum stable frequency for my phone; AHB now overclocks at frequencies higher than 400Mhz instead of 480Mhz). Once again: overclock frequencies are not activated until you enable them manually, and you do so at your own risk.
  • Hotfix 1 [15 January 2012]: Framework: enable purging of unused assets by default. Kernel: enable "veno" TCP congestion protocol to improve wireless reception, configuration changes to help battery usage, several stability & performance patches (see github commits), enabled CPU overclock to 768Mhz with 50% AHB overclocking (thanks to kalltkaffe). Note: the kernel will always boot at the safe frequency of 604Mhz; you must manually enable overclocked frequencies in CyanogenMod - Performance -> CPU. I accept no responsibility for damage as a result of using overclocked frequencies!
  • Initial status: everything appears to be working correctly (but I may have overlooked some issues).
  • Based on latest CyanogenMod source (Android version 7.2-RC0)
  • Patched: wpa_supplicant_v6 ar6000 supplicant driver
  • Patched: swap volume control buttons at 90 degrees orientation
  • Patched: enable bcm2049 fm radio & better seek support
  • Kernel: based on teamhacksung's android_kernel_samsung_msm, with additional patches: BFQ IO scheduler (default), interactiveX, smartassV2 (default) cpu schedulers, fix for CyanogenMod native USB tethering, replaced ramzswap driver (for CMParts/compcache/rzscontrol ioctl compatibility).

Source Code:

• Kernel: https://github.com/psyke83/android_kernel_samsung_msm
• Device: https://github.com/psyke83/android_device_samsung_tass

Small_town_boy said:

Gps takes much time to get locked...upto 4-5 min...i think its too long..had same prob in 1.1 also...:-(

Swyped from my first Android device....!

Click to expand...

Click to collapse

It takes just a few seconds for me...

It may be due to the baseband you're using, or you're simply not in a good satellite coverage area. Squadzone has used a lot of fixes from my source, but I notice one of the few things he didn't use from my code is the open-source GPS drivers. The proprietary gps driver (in the stock roms, tjstyle and in Squadzone's rom) may be a bit more tolerant about basebands compared to the open driver (but in my own testing, the open driver was far better). No matter, you may want to try other roms or basebands and compare.

Folks, in a few days I will no longer have access to the Mini any more. For that reason, I'm not sure if there's any sense in continuing to maintain my port. It was fun hacking on a new device and fixing a few bugs (like usb tethering, bt & wifi mac addresses, radio, sensor lag), and I hope you guys enjoy the improvements... . My source will continue to stay on github just in case Squadzone or any other current devs missed any of the important fixes.

@Squadzone: dude, keep up the great work... but please, offer vanilla builds for those who don't like custom themes, etc.
@Everybody else: enjoy your damn Mini while I'm stuck with my inferior G5 with a 2.8" screen...

Further Information

Not working / TODO:

• SIM Toolkit (menus will display, but options/commands do not process properly when selected).
• Battery drains: CyanogenMod doesn't report the battery status properly. Please read this post.

Not working / WONTFIX:

• Kies. Don't expect Kies to support any custom ROMS.

Before you ask...
I have no interest or intention to further "mod" the ROM with any kind of hacks or customizations (like custom apps, themes, Swype, etc.). My only aim is to have a 100% stable port of CyanogenMod code. Any such requests will be ignored.

Reporting bugs
You must follow these instructions exactly, or I will ignore your requests. Provide the following information:

• The version of the ROM you are using (to confirm that you have the latest release)
• Report any customizations you have made to the ROM (themes, system apps, etc.)
• Describe the problem clearly, including steps on how I can reproduce the issue.
• Provide a logcat from your system taken just after the issue has occurred. To take a logcat, you enter this command from your PC: adb shell logcat -d >c:\logcat.txt. Copy and paste this log to pastebin.com, and provide the link.
• If I ask you to re-test the issue after a data-wipe, do the following: reboot into ClockworkMod, perform a full backup, then data-wipe, reboot and retest the issue, giving a new log if necessary. You can then reboot into ClockworkMod and restore your data backup.

bravovn said:

How about the battery?
I very like CM7 but Cm7 of tjstyle and squadzone is fast running out of battery.
Other device when use CM7 the battery is so good, but i don't know CM7 for Mini is fast running out of battery. When I use stock, it charging 3 hours to full but Cm7 charging 2 hours is full.
Battery is big problem of CM7 for me.
I hope your rom will fix this problem.

Click to expand...

Click to collapse

This is the second Samsung msm7k phone I have used, and I realized something important related to Samsung's kernel battery drivers for the entire range of msm7k devices (Europa, Callisto, Tass, Ace, and others): they suck.

Usually, an Android battery driver will expose its status in specific system nodes. These are the commonly used ones:

/sys/class/power_supply/battery/level - the battery level (integer value of 0 - 100, representing the percentage of battery charged).
/sys/class/power_supply/battery/status - the charging status ("Charging", "Full", "Discharging", etc.)
/sys/class/power_supply/battery/batt_vol - the battery's current voltage

Samsung drivers use these same system nodes, but the values it exports for level and batt_vol are completely useless. I have observed - even on a stock rom - that the level properly can reach the value of 100 hours before charging truly completes. Only the status properly reports the battery's true state accurately.

Samsung has patched the framework in their official ROMs to only check the status property. CyanogenMod, on the other hand, judges the battery state using both the level and status properties, for two main aspects of the framework:

1. CyanogenMod's lockscreen charging status text, judges the battery as being charged when level reaches 100. This is usually a accurate way to judge the battery status for standard battery drivers, but Samsung's drivers are not standard. On my Huawei U8160 phone, for example, the level properly is accurate; 100 means 100% charged. Samsung's drivers are not accurate, however.

2. CyanogenMod's lockscreen battery icon (and notification bar battery icon), appears to use the status property to judge what icon it should draw. When the status property is "Charging", it draws an icon with a "lightning" symbol. When the status property is "Full" (i.e. charged), or "Discharging", it draws the icon without the lightning symbol.

Considering the two items above, only the icon is accurate for Samsung phones.

Sorry if I didn't explain myself well (it's late here), but this is what you need to know in a nutshell:
1. When the battery level is at 100%, the battery may not really be charged 100%.
2. The CyanogenMod lockscreen charging status text is usually incorrect. If it says "Charged", ignore it and read the next point.
3. The CyanogenMod lockscreen charging icon (as well as the battery notification bar icon) always tells the truth. If the green battery icon contains the white "lightning" symbol, then the battery is still charging. If the battery icon is simply green with nothing inside, your battery is really charged.
4. An alternative way to check the true charging status of the battery is to open Spare Parts -> Battery information. When Battery Status says "Full", you can be sure that the battery is really charged.

Hari23 said:

WIFI gets disconnected often and reconnects after a long time :/
anyone having this issue ?
Get reconnected quickly if i got to wifi setting

Click to expand...

Click to collapse

It's a bug in wpa_supplicant. It'll be fixed in the next release.

I'm going to do a full rebuild possibly tonight, as the ICS transition animations and other effects have been officially ported to CM7.