It isn't that people are not interested in this device anymore. it's just that people want ICS or Jellybean. Already there's a working CM 9.1 which is a port of Psyke 's cm9.1 for u8160/80 which I'm currently using. Also tilal is working on CM10.1 for u8150 to be published soon.There are also Cm10.1 nightlies for this device at Jenkins.org. It's working port though a bit more work is needed. Much work is going on behind the scenes.
Introduction CyanogenMod is an aftermarket firmware for a number of cell phones based on the open-source Android operating system. It offers features not found in the official Android-based firmwares of vendors of these cell phones.
History (standing on the shoulders of giants)
CyanogenMod has been under development for the U8150 since early 2011. In the beginning marcnvidic started off by getting the Android device tree organized and getting initial builds working. After that tilal6991 made great progress with basic functionality, bugs, etc. I joined initially to learn about the AOSP/CyanogenMod build system, but have helped clean up the device tree, fixing a few bugs, and keeping up with the latest upstream CyanogenMod changes.
Download Note: The CyanogenMod build server builds CM7.x releases for the U8150 once a week. I don't have time to update builds manually here anymore. Find CM builds here: http://get.cm/
Hey, guys and gals. I've got a pretty big update, so I need you to test and give me feedback. subpsyke made a lot of progress all over the board, so I've spent a few days integrating and testing his changes, and I feel it is now stable enough to release for broader testing.
Switch to WPA Supplicant 0_6_x (might fix problems people were having with hidden networks, or something?)
New, reworked libaudio + AudioFilter from Adriano Carrata's work on the U8160
Add optional headset volume attenuation
Fix behavior of the built-in headphones buttons (pause/play/skip track)
Allow tethering the VPN interface (ppp)
Tweak Rotary unlock bottom margin
Tweak Lense unlock bottom offset
Update USB mounting code (no change in functionality)
Now use libOmxCore from CyanogenMod
Now use gralloc.msm7k from CyanogenMod
Now use copybit.msm7k from CyanogenMod
Reduce size of keyboard by some fraction of an inch (saves some space on an already-scrunched display)
Reduce compcache (compressed RAM) to recommended default of 18%
Sync with latest CM7 code
Clean up old app overlay settings and unused build flags
Flash with ClockworkMod Recovery. A wipe shouldn't be necessary... but PLEASE backup with Nandroid / BackupSMS / Titanium / etc first, just in case I'm wrong. I wiped a million times in the process of testing in the last week so I'm not entirely sure.
Lots of changes, guys! Depending on your feedback I'll push some of these features upstream to CM, so please try to be helpful.
I just posted a new nightly for March 6th on the first post. I haven't fixed any new bugs in this release, just synced the latest sources with CyanogenMod upstream. It's up to you if you want to flash. If you're bored, flash it. If you can't be bothered, then skip it.
There are lots of things I still want to look at (especially in the kernel, such as subpsyke's wireless driver, patches from the mainline kernel, simple IO scheduler, etc...) when I get time. CyanogenMod 7.2 might be released soon but I'll keep posting nightlies with fixes whether we're at 7.2 or 7.9!
Yes, when flashing a new ROM (or simply upgrading to "the newer one"...) you'll loose ALL the apps, phonebook, SMS, etc etc...
That's why in both cases (new installation or upgrade) it's suggested to do a "nandroid" (a complete backup done within ClockWorkMod Recovery..latest suggested version is 126.96.36.199..), so when you flash or upgrade to the newer ROM you SHOULD be able to do an "advanced restore" and restore only "user data" from the backup you created.
BUT....actually ClockWorkMod 188.8.131.52 has a bug when you attempt to do an "advanced restore"...it says "no file found"..it's a bug that I encountered on my own U8150-D and also read on some posts...
Asking to everyone in the forum: did you met the same bug when attempting an advanced restore with CWM 184.108.40.206?
If yes, did you managed or found a fix for this bug? (I can remember CWM 220.127.116.11 hadn't the same bug but in some cases gave problems with USB sync...if me not mistake). Shall I downgrade to CWM 18.104.22.168 to make an advanced restore from a restore made with CWM 22.214.171.124 or it'll be better to do a backup of all the apps with Titanium Backup and restore those backup within the new installed ROM?
Thanx for any suggestion/idea.