[ROM] [WIP] CM10 "Jelly Bean" v0.32

Status
Not open for further replies.
Search This thread

Rebellos

Senior Recognized Developer
May 13, 2009
1,353
3,427
0
Gdańsk
CM10 "Jelly Bean" for
Samsung Wave I (GT-S8500) & Wave II (GT-S8530)
Alpha 0.32 Release
“Seriously, Don’t Try To Sell This... You’ll Really, REALLY Regret It” Edition


Hey all,

So once again it’s time. Introducing the first alpha development preview of CyanogenMod 10 (based on Jelly Bean) for the Samsung Wave.
This preview is intended only for developers as it is in a very early development stage and not all features of the device are fully working.

Let’s emphasize that-- THIS IS AN ALPHA, RELEASED FOR YOU TO PLAY WITH AND GET A SENSE OF WHAT’S TO COME. AND SOME THINGS DOESN’T WORK. REALLY. IF YOU ARE EXPECTING ANYTHING CLOSE TO PERFECTION, WALK AWAY FROM YOUR COMPUTER, LOWER YOUR EXPECTATIONS FOR AN HOUR OR SO, THEN COME BACK. MORE EXCITING DISCLAIMERS/WARNINGS IN ALL CAPITAL LETTERS CAN BE FOUND BELOW. READ THEM.

FAQ IS RIGHT HERE, CLICK AND READ BEFORE POSTING

WHAT DOESN’T WORK (BUGS/TODO)
Most of the modem (GSM/GPRS) functionallity because there's proprietary protocol between Bada and AMSS used, not implemented in any known Android RIL.
GPS - heavily related with above, as GPS chip is wired to Call Processor
Microphone - most likely related to modem - appears to be controlled by AMSS at some part
Magnetometer (Compass) - haven't looked into it carefully yet
Proximity sensor - haven't looked into it carefully yet

WHAT DOES (SHOULD) WORK
Sound playback
Screen
Wifi/BT
Accelerometer
Camera
Camera LED
Battery Gauge Warning: Don't leave it charging without supervising - if it gets enormously hot, disconnect it - this can literally blow up battery as there is no overheating protection yet. Do not leave it connected on 100% - it'll discharge by 1% all the time, and then recharge, what's very unhealthy for battery.

SUPPORT
You get none. Zero. Zip. We obligate ourselves to providing nothing further. You are on your own and will have to help each other via this thread. This is provided “as-is”, and if you don’t like it, use Bada or other releases.

We basically lack time to give full dedication to this rom, and we’re looking for skilled devs who know the Android, and/or other things that might be relevant.

Please join us on IRC: some people are on #badadroid (freenode).



BUG REPORTS
This is the format for a bug report: “XXXXX isn’t working. Here is how to fix it: [INCLUDE SOLUTION]” Don’t have source? Too bad. You’ll have to wait then.

If you report bugs, please don’t be disappointed if we can’t fix them immediately (or even never). It’s not because we don’t care, but because we don’t have time or don’t know how to fix it.
Please attach logcat and dmesg dump in your bug report. Dmesg should contain messages from both - bootup and issue occuring (you can't dump it 1 hour after bootup, rather 2 minutes after)
How to dump logs - Google for "android logcat dmesg" Or... whatever, here's one of 3204109 methods available.
In the Terminal Emulator enter:
"su"
Accept request for SuperUser access.
"dmesg > /emmc/dmesg.log"
"logcat -b system -b radio -b events -b main > /emmc/logcat.log"
Download them from phone, archive and upload them.
Note: You might need to change /emmc/ to /tmp/, /sdcard/, or something that will help you obtaining these logs.
Privacy warning: Your logcat might contain sensitive information like your IMEI, IMSI, cell stations you were nearby, numbers you called and got calls from and SMS sent and received. If you don't want to publish this info - send them privately to one of developers.
If the Badadroid is restarting before you're able to catch any log:
Download http://goo.im/devs/Rebellos/wave/bterm.exe
Try to start kernel normally, when you see Badadroid logo start holding the middle key pressed. Keep the middle key pressed until phone restarts and shows the text: FOTA DOWNLOAD MODE & bTerm
Connect phone to PC.
Start bterm.exe
Type 4 commands:
Code:
open
dumpram 0x4FF00000 0x100000
close
exit
There should appear file called dump_ram_0x4FF00000.0x00100000.bin - pack it and attach it to your bug report.

Bug reports without logs are completely useless.

NOTE: DEVELOPERS WANTED. Please contact us if you are a developer with something to contribute.
I do heavily encourage to work together on the better, common project instead of making kang releases and demanding money for somebody else's work.
Read as: If you think you can make something better than this by doing less and muchazo Ctrl+C Ctrl+V - you suck, go figure the rest.

HOW TO BUILD
I do recommend perfect tutorial by fattire: https://docs.google.com/document/d/19f7Z1rxJHa5grNlNFSkh7hQ0LmDOuPdKMQUg8HFiyzs/edit?hl=en_US
Of course you have to init with -b jellybean and modify some steps.
local manifest to use: https://raw.github.com/Rebell/android_wave_local_manifest/jellybean/local_manifest.xml
I do it like this:
Code:
cd ~
mkdir wave
cd wave
repo init -u git://github.com/CyanogenMod/android.git -b jellybean
cd .repo
wget https://raw.github.com/Rebell/android_wave_local_manifest/jellybean/local_manifest.xml
cd ..
repo sync -j8
cd vendor/cm/
./get-prebuilts
cd ../../
. build/envsetup.sh
brunch wave
device name is wave so the build invocation can be brunch wave


FIRST INSTALLATION
Bada 2.0 is required

  1. Enter Bada Settings->General->Memory and make sure you have at least:
    • 370MB of free "System" memory
    • 150MB of free "User" memory
    • 400MB of free "Applications" memory
  2. Download 3 packages: BOOTFILES, armlinux_boot and selected release for your device (please pay attention if it's S8500 or S8530 BOOTFILES and FOTA you're choosing!):
    Releases: http://goo.im/devs/Rebellos/wave
  3. Start Bada.
  4. Extract zImage from zip and copy it to the Bada's User partition (the one about 390MB big).
  5. Copy whole .zip to the Bada's User partition.
  6. Flash BOOTFILES and FOTA using Multiloader.
    If you have been already using my FOTA bootloaders, you don't need to flash BOOTFILES.
  7. Reboot the phone holding Power and Call key.
    FOTA set of red messages should appear, after about 15seconds Badadroid logo shows up.
  8. Be patient, first bootup will keep unresponsible on Badadroid logo for up to 5 minutes.
  9. CWM Recovery starts, pick:
    - install zip from sdcard
    - choose zip from sdcard
    - cm-10-wave-<release id>.zip
    - Yes - install
  10. Reboot holding the Power key

You can remove installation .zip from the User partition from Android level by connecting through USB in MTP mode.
Do not remove zImage file and modem directory.
Normal bootup is available using Power+Call keys
CWM Recovery mode is available using Power+Volume Up keys
CWM Flashing does overwrite zImage. So every next update you can just flash .zip through CWM.

HOW TO UNINSTALL
Follow the steps there: http://forum.xda-developers.com/showpost.php?p=35107469&postcount=393 (thanks Volk204)

THANKS TO
Oleg_k, mijoma, nbates66, anghelyi, Volk204, mikegapinski, hunktb, autra, Tigrouzen and many others.
Special thanks to chrmhoffmann for letting me kang his release description.


CHANGELOG
Releases available there: http://goo.im/devs/Rebellos/wave
0.32 - original releasenotes and link http://forum.xda-developers.com/showpost.php?p=41131519&postcount=2408 - courtesy of Volk204
  • Incorrect LCD type detection in S8530 with HWREV 0x5 has been fixed. LCD should work on ~99% of Waves 2. (Thanks to Rebellos)
  • Bluetooth MAC is correct.
  • Modem directory moved to /data/radio (experimental patch)
  • RIL: Fixed handling SMSC number in national format
  • Corrections to the key mapping. Still to be polished. Call key as BACK, Middle as MENU, long press - recent apps, End Call as ENDCALL, long press show power off menu (fixed correct power off process), short press "Go to Home"(it is not real HOME key, but it revert to HOME screen in most of cases), lock as HOLD - only screen on/off (framework patch)
    Key mapping visualisation: http://img203.imageshack.us/img203/6838/badadroidv032.jpg
  • Upstream CM patches.

0.31
  • Screen waking up has been fixed for S8530 with LCD type 3. (kernel only update, thanks to Volk204 for providing a quick fix, people with working S8530 screen doesn't need to update!)
    You can overwrite only zImage on bada_user partition if you don't want to download whole zip.
0.3
  • Fixed fetching incorrect NITZ date and time when network didn't provide proper data (like 1971/1/1/ 01:00:00).
  • Fixed showing up No signal/Network unavailable when phone did actually register into network.
  • Proximity sensor is working. There's no light sensor in Wave.
  • Compass is working. Might need some further calibration.
  • USSD requests are working. (Network codes like *#1234# to check your account balance etc.)
  • Basic outgoing calls are possible. NO SOUND YET
  • RIL logs has been moved from systemlog to radiolog - In future reports please attach all logs! I updated logcat fetching instructions.
  • SIM recognition and detection in most of the cases should be fixed.
  • Preferred network mode (2G/3G) selection. (Probably the choice won't persist between restarts)
  • S8530 screen is waking up properly now. Couldn't test it on S8530 with screen type 3, so this might need a fix for these.
  • Random screen crash due to MMC driver going crazy should be fixed on some boards - it MIGHT cause issues on other boards - it'd be visible on dmesg.
  • Experimental Samsung RIL Socket (originally done by Paul Kocialkowski) utilisation to control calling sound pathes. More to come in next releases.
  • Better S8500 touchscreen calibration (thanks to Tigrouzen)
  • Airplane mode

0.2
Almost all of the features in this release were implemented by Volk204, send him a big beer.
  • Real IMEI reading out of NVdata.
  • SIM card unlocking with PIN.
  • Registering to mobile network.
  • Incoming call support, answer/hangup option. NO AUDIO RECEIVING OR SENDING DURING CALL YET No outgoing calls yet.
  • Receiving SMS.
  • Sending SMS.
  • Time from network updates (NITZ)
  • Tons of other important things you won't even notice nor imagine how much effort did it take.
  • Upstream CM10 changes.

0.1
FOTAs update is required to the version with "for_0_07" name.
To update from older versions - first manually unpack zImage from archive just like during first installation, then after rebooting you can continue installation.
  • Kernel and platform are now unified for both Wave1 and Wave2 - only FOTA used does differ between models.
  • SD Card should get detected on all of the devices now.
  • Fixed backlight on Wave2 - LCD waking up is still not working properly.
  • Fixed kernel panic due to WiFi initialization fault - thanks Volk204.
  • WiFi is working on Wave2 now - thanks chemosun
  • Much better HW key handling - big kudos to Volk204.
  • Increased system partition size to 375MB (should be big enough to fit GApps in it now and leave some "living space")
  • Implemented experimental battery charger and fuel gauge driver - Warning: Don't leave it charging without supervising - if it gets enormously hot, disconnect it - this can literally blow up battery as there is no overheating protection yet.
    Do not leave it connected on 100% - it'll discharge by 1% all the time, and then recharge, what's very unhealthy for battery.
  • Included Mocha-IPC and Mocha-RIL drivers, very basic, very buggy, but should bootup modem into Low-Power-Mode and read battery status. (C CODERS WANTED)
  • Fixed mounting of internal sd card as main storage - it should be possible to fully use features like Market and Camera without external-SD card.
  • CM10 mainline patches.
  • FOTA bootloader does now support recovery boot by holding volume-up key only (no need to hold middle key anymore). Needs update of FOTA.
  • Enabled overclocking to 1.2GHz and 1.4GHz. <Volk204>
  • JPEG buffers patch from Aries, so there's even more RAM available (~250MB) <Volk204>
  • Fixed "Advanced Settings" derived from Galaxy S. <Volk204>
  • Fixed TVOut. <Volk204>
  • Simple IO scheduler pulled from Aries. <Volk204>
  • Vibrator intensity control from Aries. <Volk204>

0.07
Not released, renamed to 0.1

0.06
  • Reworked whole installation procedure, .imgs relocated and resized.
  • Cache(18MB) + System(250MB) goes to bada_private partition
  • Data(400MB) goes to bada_apps.
  • zImage is kept on bada_user (390MB), bada_user also becomes user storage (internal sd card) on Android, so it's shared with Bada
  • Pulled Torch fix into release. (Herpderp me, forgot it in 0.05)
  • Cleaned up unnecessary things in platform (auto-brightness for example)
  • Recovery should be fully working by now. Including flashing things like gapps and stuff. (gapps: http://goo.im/gapps/gapps-jb-20121011-signed.zip )
0.05
  • Fixed screen problems on S8500. Thanks to Volk204.
  • LED flash is working, together with Torch apk. Thanks to Volk204.
  • 29MB RAM more is available to the userspace now. Again, thanks Volk204. :)
  • Improved S8530 touchscreen calibration.
  • Improved S8530 backlight regulation levels.
  • Latest CM10 changes.
  • FOTA has been updated, it does produce debug output to the screen instead of UART, this should help debugging "won't bootup" troubles.
  • FOTA and BOOTFILES are included in .zips
0.04
Added support for S8530, thanks to Tigrouzen and Volk204 for testing and support. Please report bugs in LCD driver in this thread, Wifi is not working yet
Latest CM10 source base (including goodies like CM File Manager)
0.03
Platform is starting up! And pretty stable.
Synced with CM Aries kernel sources.
New FOTA is recommended.

0.02
Got working recovery, new kernel initramfs structure.

0.01
Initial release.


MORE LINKS
Overall project thread - http://forum.xda-developers.com/showthread.php?t=1459391
 
Last edited:

MrXJKz

Senior Member
Aug 25, 2012
75
9
0
Hi Rebellos,

I just registered for your project, I'm interrested in. I'm new to all this things, like customs firmware etc. I've tested the Android 4 ICS on Wave S8500 and the missing thing is just Modem (GSM?).

I'm very interrested in your project. I want to test it, but. I'm just a noob in this all things like I've said it... I very want a functional Android on Wave S8500. So, keep it this great work please!

Thanks you.

Sorry for my bad English sir.
 
  • Like
Reactions: cnwilli

shaiws

Senior Member
Dec 28, 2011
305
29
28
Lod
I rechecked previous and this release and both .img works for me. So updated link once again. This time archive does contain zImage I'm using aswell.

PS: Remember you are welcome to join #badadroid if you got some patches or are just seeking for friends.

I'll try it now.
THANK AGAIN!
 
  • Like
Reactions: cnwilli

volk204

Inactive Recognized Developer
Mar 15, 2011
366
2,274
123
Moscow region
I rechecked previous and this release and both .img works for me. So updated link once again. This time archive does contain zImage I'm using aswell.

PS: Remember you are welcome to join #badadroid if you got some patches or are just seeking for friends.


Hi Rebellos

the same is with new system.img
Could you please upload img without archiving? Probably problem is with your archiver
 
  • Like
Reactions: Sedors and SERGHi

Perepandel

Senior Member
Aug 6, 2012
52
13
28
Gandia
www.pandelground.com
My first attempt was only with system.img and zimage and, of course, I got stuck on the Badadroid logo screen too.
Second attempt I also copied cache and data images from my working "Polishblood" image. It also gets stuck on the logo screen.
Haven't tryied the unpacked files yet. But I didn't receive any error messages when extracting the packed ones.
 
Last edited:

rosli_2252

Member
Jul 2, 2012
25
9
0
Initramfs is part of zImage, not zImage itself.

I don't know why your tries are stuck. Remember you need cache and data images too.
There are unpacked files

Dear Rebellos, i have tried your packed version and unpacked version with no luck. I just stuck at badadroid logo.
In your opinion, what would be the problems?
mikegapinski version and slim version work well in my wave. I have included all file needed but i get no luck with yours.

Maybe that you are using different bootloader or you do something with the bootloader? I not rushing anything, i am just eager to test your jellybean build. I am aware that it will be slow and lack of many features but it does not stopping me to try out your build.

I am really happy that you spend your precious time and energy to make this build. i, one of wave owner, really appreciate your effort.
 
Last edited:

Perepandel

Senior Member
Aug 6, 2012
52
13
28
Gandia
www.pandelground.com
OK, I get this compilation error:

Code:
make: *** No rule to make target `vendor/samsung/wave-common/proprietary/cypress-touchkey.bin', needed by `out/target/product/wave/system/vendor/firmware/cypress-touchkey.bin'.  Stop.
make: *** Waiting for unfinished jobs....

Confusing parts start in point #4 of fattire's tutorial:

4. Next, install the proprietary files per the original instructions and run the ./setup-makefiles.sh script in android/system/device/bn/encore.

There's no setup-makefiles.sh in android/system/device/wave/ no android/system/device/wave-common/ , although I suspect this part is not that important.

As there it says that

(if that doesn’t work for some reason, try typing add_lunch_combo cm_encore-userdebug manually.)

I tryied doing that and got same error. But I'd say that my first attempt took only half an hour or so, and on second attemp, after doing an add_lunch_combo cm_encore-userdebug, took significantly longer. Could that be possible?

I start the compilation process with a . build/envsetup.sh, than "brunch wave", but also I want to note that 1st time I made a . build/envsetup.sh then "lunch" and there I didn't find a "wave" in the list of devices.
 

deeps_17

Senior Member
May 31, 2012
74
35
0
Denver
deepakkaku.co.cc
:(

well
tried 20 times now, nothing worked

its still stuck at boot image.

All
Files present in phone mem are
cache.img
datd.img
polishblood_Nightly1.img (rebellos's img renamed)
zImage (latest)

I also tried not renaming the systemimg to polishblood

all in vain

anybody else facing this problem??
 

shaiws

Senior Member
Dec 28, 2011
305
29
28
Lod
well
tried 20 times now, nothing worked

its still stuck at boot image.

All
Files present in phone mem are
cache.img
datd.img
polishblood_Nightly1.img (rebellos's img renamed)
zImage (latest)

I also tried not renaming the systemimg to polishblood

all in vain

anybody else facing this problem??

Same..
I think we should give to rebellos time, and we will get a working B

@Rebellos maybe you should uploud the all file that you are using in your wave.,,
 
Last edited:

mfernandopf

Member
Jul 9, 2012
8
0
0
Hello,

I've also tried to, but i'm stock at logo, also after i tried some photos and videos are missing from my SD Card.

It worked fine before with ICS.

Thanks anyway
 

Rebellos

Senior Recognized Developer
May 13, 2009
1,353
3,427
0
Gdańsk
system.img should not be renamed.
I've added clean system_cache.zip into http://goo.im/devs/Rebellos/cm10-wave-0.01/ though it's empty and JB seems to be stuck on boot animation with it. You might try first running ICS and then upgrading to JB image.
@Building issues:
I forgot to push one commit. Did it now so after "repo sync" you should be able to go. :)
 
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 214
    CM10 "Jelly Bean" for
    Samsung Wave I (GT-S8500) & Wave II (GT-S8530)
    Alpha 0.32 Release
    “Seriously, Don’t Try To Sell This... You’ll Really, REALLY Regret It” Edition


    Hey all,

    So once again it’s time. Introducing the first alpha development preview of CyanogenMod 10 (based on Jelly Bean) for the Samsung Wave.
    This preview is intended only for developers as it is in a very early development stage and not all features of the device are fully working.

    Let’s emphasize that-- THIS IS AN ALPHA, RELEASED FOR YOU TO PLAY WITH AND GET A SENSE OF WHAT’S TO COME. AND SOME THINGS DOESN’T WORK. REALLY. IF YOU ARE EXPECTING ANYTHING CLOSE TO PERFECTION, WALK AWAY FROM YOUR COMPUTER, LOWER YOUR EXPECTATIONS FOR AN HOUR OR SO, THEN COME BACK. MORE EXCITING DISCLAIMERS/WARNINGS IN ALL CAPITAL LETTERS CAN BE FOUND BELOW. READ THEM.

    FAQ IS RIGHT HERE, CLICK AND READ BEFORE POSTING

    WHAT DOESN’T WORK (BUGS/TODO)
    Most of the modem (GSM/GPRS) functionallity because there's proprietary protocol between Bada and AMSS used, not implemented in any known Android RIL.
    GPS - heavily related with above, as GPS chip is wired to Call Processor
    Microphone - most likely related to modem - appears to be controlled by AMSS at some part
    Magnetometer (Compass) - haven't looked into it carefully yet
    Proximity sensor - haven't looked into it carefully yet

    WHAT DOES (SHOULD) WORK
    Sound playback
    Screen
    Wifi/BT
    Accelerometer
    Camera
    Camera LED
    Battery Gauge Warning: Don't leave it charging without supervising - if it gets enormously hot, disconnect it - this can literally blow up battery as there is no overheating protection yet. Do not leave it connected on 100% - it'll discharge by 1% all the time, and then recharge, what's very unhealthy for battery.

    SUPPORT
    You get none. Zero. Zip. We obligate ourselves to providing nothing further. You are on your own and will have to help each other via this thread. This is provided “as-is”, and if you don’t like it, use Bada or other releases.

    We basically lack time to give full dedication to this rom, and we’re looking for skilled devs who know the Android, and/or other things that might be relevant.

    Please join us on IRC: some people are on #badadroid (freenode).



    BUG REPORTS
    This is the format for a bug report: “XXXXX isn’t working. Here is how to fix it: [INCLUDE SOLUTION]” Don’t have source? Too bad. You’ll have to wait then.

    If you report bugs, please don’t be disappointed if we can’t fix them immediately (or even never). It’s not because we don’t care, but because we don’t have time or don’t know how to fix it.
    Please attach logcat and dmesg dump in your bug report. Dmesg should contain messages from both - bootup and issue occuring (you can't dump it 1 hour after bootup, rather 2 minutes after)
    How to dump logs - Google for "android logcat dmesg" Or... whatever, here's one of 3204109 methods available.
    In the Terminal Emulator enter:
    "su"
    Accept request for SuperUser access.
    "dmesg > /emmc/dmesg.log"
    "logcat -b system -b radio -b events -b main > /emmc/logcat.log"
    Download them from phone, archive and upload them.
    Note: You might need to change /emmc/ to /tmp/, /sdcard/, or something that will help you obtaining these logs.
    Privacy warning: Your logcat might contain sensitive information like your IMEI, IMSI, cell stations you were nearby, numbers you called and got calls from and SMS sent and received. If you don't want to publish this info - send them privately to one of developers.
    If the Badadroid is restarting before you're able to catch any log:
    Download http://goo.im/devs/Rebellos/wave/bterm.exe
    Try to start kernel normally, when you see Badadroid logo start holding the middle key pressed. Keep the middle key pressed until phone restarts and shows the text: FOTA DOWNLOAD MODE & bTerm
    Connect phone to PC.
    Start bterm.exe
    Type 4 commands:
    Code:
    open
    dumpram 0x4FF00000 0x100000
    close
    exit
    There should appear file called dump_ram_0x4FF00000.0x00100000.bin - pack it and attach it to your bug report.

    Bug reports without logs are completely useless.

    NOTE: DEVELOPERS WANTED. Please contact us if you are a developer with something to contribute.
    I do heavily encourage to work together on the better, common project instead of making kang releases and demanding money for somebody else's work.
    Read as: If you think you can make something better than this by doing less and muchazo Ctrl+C Ctrl+V - you suck, go figure the rest.

    HOW TO BUILD
    I do recommend perfect tutorial by fattire: https://docs.google.com/document/d/19f7Z1rxJHa5grNlNFSkh7hQ0LmDOuPdKMQUg8HFiyzs/edit?hl=en_US
    Of course you have to init with -b jellybean and modify some steps.
    local manifest to use: https://raw.github.com/Rebell/android_wave_local_manifest/jellybean/local_manifest.xml
    I do it like this:
    Code:
    cd ~
    mkdir wave
    cd wave
    repo init -u git://github.com/CyanogenMod/android.git -b jellybean
    cd .repo
    wget https://raw.github.com/Rebell/android_wave_local_manifest/jellybean/local_manifest.xml
    cd ..
    repo sync -j8
    cd vendor/cm/
    ./get-prebuilts
    cd ../../
    . build/envsetup.sh
    brunch wave
    device name is wave so the build invocation can be brunch wave


    FIRST INSTALLATION
    Bada 2.0 is required

    1. Enter Bada Settings->General->Memory and make sure you have at least:
      • 370MB of free "System" memory
      • 150MB of free "User" memory
      • 400MB of free "Applications" memory
    2. Download 3 packages: BOOTFILES, armlinux_boot and selected release for your device (please pay attention if it's S8500 or S8530 BOOTFILES and FOTA you're choosing!):
      Releases: http://goo.im/devs/Rebellos/wave
    3. Start Bada.
    4. Extract zImage from zip and copy it to the Bada's User partition (the one about 390MB big).
    5. Copy whole .zip to the Bada's User partition.
    6. Flash BOOTFILES and FOTA using Multiloader.
      If you have been already using my FOTA bootloaders, you don't need to flash BOOTFILES.
    7. Reboot the phone holding Power and Call key.
      FOTA set of red messages should appear, after about 15seconds Badadroid logo shows up.
    8. Be patient, first bootup will keep unresponsible on Badadroid logo for up to 5 minutes.
    9. CWM Recovery starts, pick:
      - install zip from sdcard
      - choose zip from sdcard
      - cm-10-wave-<release id>.zip
      - Yes - install
    10. Reboot holding the Power key

    You can remove installation .zip from the User partition from Android level by connecting through USB in MTP mode.
    Do not remove zImage file and modem directory.
    Normal bootup is available using Power+Call keys
    CWM Recovery mode is available using Power+Volume Up keys
    CWM Flashing does overwrite zImage. So every next update you can just flash .zip through CWM.

    HOW TO UNINSTALL
    Follow the steps there: http://forum.xda-developers.com/showpost.php?p=35107469&postcount=393 (thanks Volk204)

    THANKS TO
    Oleg_k, mijoma, nbates66, anghelyi, Volk204, mikegapinski, hunktb, autra, Tigrouzen and many others.
    Special thanks to chrmhoffmann for letting me kang his release description.


    CHANGELOG
    Releases available there: http://goo.im/devs/Rebellos/wave
    0.32 - original releasenotes and link http://forum.xda-developers.com/showpost.php?p=41131519&postcount=2408 - courtesy of Volk204
    • Incorrect LCD type detection in S8530 with HWREV 0x5 has been fixed. LCD should work on ~99% of Waves 2. (Thanks to Rebellos)
    • Bluetooth MAC is correct.
    • Modem directory moved to /data/radio (experimental patch)
    • RIL: Fixed handling SMSC number in national format
    • Corrections to the key mapping. Still to be polished. Call key as BACK, Middle as MENU, long press - recent apps, End Call as ENDCALL, long press show power off menu (fixed correct power off process), short press "Go to Home"(it is not real HOME key, but it revert to HOME screen in most of cases), lock as HOLD - only screen on/off (framework patch)
      Key mapping visualisation: http://img203.imageshack.us/img203/6838/badadroidv032.jpg
    • Upstream CM patches.

    0.31
    • Screen waking up has been fixed for S8530 with LCD type 3. (kernel only update, thanks to Volk204 for providing a quick fix, people with working S8530 screen doesn't need to update!)
      You can overwrite only zImage on bada_user partition if you don't want to download whole zip.
    0.3
    • Fixed fetching incorrect NITZ date and time when network didn't provide proper data (like 1971/1/1/ 01:00:00).
    • Fixed showing up No signal/Network unavailable when phone did actually register into network.
    • Proximity sensor is working. There's no light sensor in Wave.
    • Compass is working. Might need some further calibration.
    • USSD requests are working. (Network codes like *#1234# to check your account balance etc.)
    • Basic outgoing calls are possible. NO SOUND YET
    • RIL logs has been moved from systemlog to radiolog - In future reports please attach all logs! I updated logcat fetching instructions.
    • SIM recognition and detection in most of the cases should be fixed.
    • Preferred network mode (2G/3G) selection. (Probably the choice won't persist between restarts)
    • S8530 screen is waking up properly now. Couldn't test it on S8530 with screen type 3, so this might need a fix for these.
    • Random screen crash due to MMC driver going crazy should be fixed on some boards - it MIGHT cause issues on other boards - it'd be visible on dmesg.
    • Experimental Samsung RIL Socket (originally done by Paul Kocialkowski) utilisation to control calling sound pathes. More to come in next releases.
    • Better S8500 touchscreen calibration (thanks to Tigrouzen)
    • Airplane mode

    0.2
    Almost all of the features in this release were implemented by Volk204, send him a big beer.
    • Real IMEI reading out of NVdata.
    • SIM card unlocking with PIN.
    • Registering to mobile network.
    • Incoming call support, answer/hangup option. NO AUDIO RECEIVING OR SENDING DURING CALL YET No outgoing calls yet.
    • Receiving SMS.
    • Sending SMS.
    • Time from network updates (NITZ)
    • Tons of other important things you won't even notice nor imagine how much effort did it take.
    • Upstream CM10 changes.

    0.1
    FOTAs update is required to the version with "for_0_07" name.
    To update from older versions - first manually unpack zImage from archive just like during first installation, then after rebooting you can continue installation.
    • Kernel and platform are now unified for both Wave1 and Wave2 - only FOTA used does differ between models.
    • SD Card should get detected on all of the devices now.
    • Fixed backlight on Wave2 - LCD waking up is still not working properly.
    • Fixed kernel panic due to WiFi initialization fault - thanks Volk204.
    • WiFi is working on Wave2 now - thanks chemosun
    • Much better HW key handling - big kudos to Volk204.
    • Increased system partition size to 375MB (should be big enough to fit GApps in it now and leave some "living space")
    • Implemented experimental battery charger and fuel gauge driver - Warning: Don't leave it charging without supervising - if it gets enormously hot, disconnect it - this can literally blow up battery as there is no overheating protection yet.
      Do not leave it connected on 100% - it'll discharge by 1% all the time, and then recharge, what's very unhealthy for battery.
    • Included Mocha-IPC and Mocha-RIL drivers, very basic, very buggy, but should bootup modem into Low-Power-Mode and read battery status. (C CODERS WANTED)
    • Fixed mounting of internal sd card as main storage - it should be possible to fully use features like Market and Camera without external-SD card.
    • CM10 mainline patches.
    • FOTA bootloader does now support recovery boot by holding volume-up key only (no need to hold middle key anymore). Needs update of FOTA.
    • Enabled overclocking to 1.2GHz and 1.4GHz. <Volk204>
    • JPEG buffers patch from Aries, so there's even more RAM available (~250MB) <Volk204>
    • Fixed "Advanced Settings" derived from Galaxy S. <Volk204>
    • Fixed TVOut. <Volk204>
    • Simple IO scheduler pulled from Aries. <Volk204>
    • Vibrator intensity control from Aries. <Volk204>

    0.07
    Not released, renamed to 0.1

    0.06
    • Reworked whole installation procedure, .imgs relocated and resized.
    • Cache(18MB) + System(250MB) goes to bada_private partition
    • Data(400MB) goes to bada_apps.
    • zImage is kept on bada_user (390MB), bada_user also becomes user storage (internal sd card) on Android, so it's shared with Bada
    • Pulled Torch fix into release. (Herpderp me, forgot it in 0.05)
    • Cleaned up unnecessary things in platform (auto-brightness for example)
    • Recovery should be fully working by now. Including flashing things like gapps and stuff. (gapps: http://goo.im/gapps/gapps-jb-20121011-signed.zip )
    0.05
    • Fixed screen problems on S8500. Thanks to Volk204.
    • LED flash is working, together with Torch apk. Thanks to Volk204.
    • 29MB RAM more is available to the userspace now. Again, thanks Volk204. :)
    • Improved S8530 touchscreen calibration.
    • Improved S8530 backlight regulation levels.
    • Latest CM10 changes.
    • FOTA has been updated, it does produce debug output to the screen instead of UART, this should help debugging "won't bootup" troubles.
    • FOTA and BOOTFILES are included in .zips
    0.04
    Added support for S8530, thanks to Tigrouzen and Volk204 for testing and support. Please report bugs in LCD driver in this thread, Wifi is not working yet
    Latest CM10 source base (including goodies like CM File Manager)
    0.03
    Platform is starting up! And pretty stable.
    Synced with CM Aries kernel sources.
    New FOTA is recommended.

    0.02
    Got working recovery, new kernel initramfs structure.

    0.01
    Initial release.


    MORE LINKS
    Overall project thread - http://forum.xda-developers.com/showthread.php?t=1459391
    52
    New version is out

    http://www.multiupload.nl/ILSX6BFYFI

    Changelog 0.32 Version

    • Incorrect LCD type detection in S8530 with HWREV 0x5 has been fixed. LCD should work on ~99% of Waves 2. (Thanks to Rebellos)
    • Bluetooth MAC is correct.
    • Modem directory moved to /data/radio (experimental patch)
    • RIL: Fixed handling SMSC number in national format
    • Corrections to the key mapping. Still to be polished. Call key as BACK, Middle as MENU, long press - recent apps, End Call as ENDCALL, long press show power off menu (fixed correct power off process), short press "Go to Home"(it is not real HOME key, but it revert to HOME screen in most of cases), lock as HOLD - only screen on/off (framework patch) http://img203.imageshack.us/img203/6838/badadroidv032.jpg
    • Upstream CM patches.

    Big thank you to Rebellos for his help and also hunktb for testing, debugging and logging
    38
    New update is coming
    Changelog:
    - reading real IMEI from nv_data
    - entering and verification sim pin code
    - mobile operator identification
    - incoming call notification (with phone number )
    - incoming call answering, but audio is not working at all during call, because need to implement sound and mic packets handling in RIL
    - incoming call hangup (reject)
    - receiving SMS
    34
    Pls release it now

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

    I won't until I get 3000 thanks and 400 more "please" posts, aswell some donations, release is ready for a month already but I'm just waiting for that. -.-'
    30
    0.3
    • Fixed fetching incorrect NITZ date and time when network didn't provide proper data (like 1971/1/1/ 01:00:00).
    • Fixed showing up No signal/Network unavailable when phone did actually register into network.
    • Proximity sensor is working. There's no light sensor in Wave.
    • Compass is working. Might need some further calibration.
    • USSD requests are working. (Network codes like *#1234# to check your account balance etc.)
    • Basic outgoing calls are possible. NO SOUND YET
    • RIL logs has been moved from systemlog to radiolog - In future reports please attach all logs! I updated logcat fetching instructions.
    • SIM recognition and detection in most of the cases should be fixed.
    • Preferred network mode (2G/3G) selection. (Probably the choice won't persist between restarts)
    • S8530 screen is waking up properly now. Couldn't test it on S8530 with screen type 3, so this might need a fix for these.
    • Random screen crash due to MMC driver going crazy should be fixed on some boards - it MIGHT cause issues on other boards - it'd be visible on dmesg.
    • Experimental Samsung RIL Socket (originally done by Paul Kocialkowski) utilisation to control calling sound pathes. More to come in next releases.
    • Better S8500 touchscreen calibration (thanks to Tigrouzen)
    • Airplane mode.

    Once again most of the network functions got implemented by Volk204.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone