Samsung Wave I (GT-S8500) & Wave II (GT-S8530)
Alpha 0.1 Release
“Seriously, Don’t Try To Sell This… You’ll Really, REALLY Regret It” Edition
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.
WHAT DOESN’T WORK (BUGS/TODO)
all 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
Screen won’t wake-up properly on S8530 – some improper LG4573 initialization, kernel driver issue
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
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.
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 eleases.
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).
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
|In the Terminal Emulator enter:
Accept request for SuperUser access.
“dmesg > /emmc/dmesg.log”
“logcat > /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.
If the Badadroid is restarting before you’re able to catch any log:
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.
Type 4 commands:
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/1…/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/androi…l_manifest.xml
I do it like this:
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
Instruction updated per 0.06 release and newer! Do not use releases older than 0.06.
Bada 2.0 is required
- 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
- 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!):
- Start Bada.
- Extract zImage from zip and copy it to the Bada’s User partition (the one about 390MB big).
- Copy whole .zip to the Bada’s User partition.
- Flash BOOTFILES and FOTA using Multiloader.
If you have been already using my FOTA bootloaders, you don’t need to flash BOOTFILES.
- Reboot the phone holding Power and Call key.
FOTA set of red messages should appear, after about 15seconds Badadroid logo shows up.
- Be patient, first bootup will keep unresponsible on Badadroid logo for up to 5 minutes.
- CWM Recovery starts, pick:
– install zip from sdcard
– choose zip from sdcard
– cm-10-wave-<release id>.zip
– Yes – install
- 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/show…&postcount=393 (thanks Volk204)
Oleg_k, mijoma, nbates66, anghelyi, Volk204, mikegapinski and many others.
Special thanks to chrmhoffmann for letting me kang his release description.
Releases available there: http://goo.im/devs/Rebellos/wave
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>
Not released, renamed to 0.1
- 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 )
- 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
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)
Platform is starting up! And pretty stable.
Synced with CM Aries kernel sources.
New FOTA is recommended.
Got working recovery, new kernel initramfs structure.
Overall project thread – http://forum.xda-developers.com/show….php?t=1459391
AOSP platform by mikegapinski – http://forum.xda-developers.com/show….php?t=1727865
AOKP platform by anghelyi – http://forum.xda-developers.com/show….php?t=1761034
Pretty owsom Android/Kernel dev tips&tricks: http://omappedia.org/wiki/Android_How-tos
Git HOW-TO by eagleeyetom: http://forum.xda-developers.com/show…php?p=31304826
15-minutes GIT introduction: http://try.github.com