Thanks a lot, Rebellos! I'm gonna let it compile tonight. Let's see if tomorrow I have a surprise when I get up!
Trying the new cache_data.zip as well!
Trying the new cache_data.zip as well!
Last edited:
[ROM] [WIP] CM10 "Jelly Bean" v0.32
- Thread starter Rebellos
- Start date
- Status
-_-
Steps i followed now
First I run Normal Android 4.0 ICS as you said.
Then i Download cache and data.img files you uploaded, also the zimage and system image uploaded here
http://goo.im/devs/Rebellos/cm10-wave-0.01/
Replaced files
Nothing seemed to work
I tired ur new cache and data with ics and it worked fine, but not with Jb
so i suppose problem lies in the system.img file
Im still stuck at boot image.
---------- Post added at 01:52 PM ---------- Previous post was at 01:45 PM ----------
one more thing i noticed
cache_data.zip file is of only 194 kb
but after extraction cache become 39 mb and data become 117 mb
how come?
can a file be compressed so much
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.
Steps i followed now
First I run Normal Android 4.0 ICS as you said.
Then i Download cache and data.img files you uploaded, also the zimage and system image uploaded here
http://goo.im/devs/Rebellos/cm10-wave-0.01/
Replaced files
Nothing seemed to work
I tired ur new cache and data with ics and it worked fine, but not with Jb
so i suppose problem lies in the system.img file
Im still stuck at boot image.
---------- Post added at 01:52 PM ---------- Previous post was at 01:45 PM ----------
one more thing i noticed
cache_data.zip file is of only 194 kb
but after extraction cache become 39 mb and data become 117 mb
how come?
can a file be compressed so much
Last edited:
deeps_17: cache and data is full of zero bytes, so it's can by compressed to this size. I think, you want from Rebellos those file thah have alredy installed JB, don't you? in this case, compression of file must by lower(bigger rar). ask him, or wait.
Hi Rebellos,
Could you please shed some light on the progress of S8530(Wave 2)?
Thank You
Regards
raj7493 :fingers-crossed:
Could you please shed some light on the progress of S8530(Wave 2)?
Thank You
Regards
raj7493 :fingers-crossed:
True that.
What do you mean by "boot logo"/"boot image" - does it show "Badadroid" or animated "Android"? I'm always getting to animated "Android".
it stucks on BadaDROID logo.
if it is work for you, what could be the problem for us??
it stucks on BadaDROID logo.
if it is work for you, what could be the problem for us??
If you have Adnroid sdk then execute ddms and you can get debug information.
I think its system.img probably cause i got all time /system/bin/sh not found
Ok, it seems it compiled, but I get one final error when trying to create OTA files??
This is the output:
I confirm
out/target/product/wave/obj/PACKAGING/target_files_intermediates/cm_wave-target_files-eng.pere.zip
exists, but
out/target/product/wave/cm_wave-ota-eng.pere.zip
isn't being created after the error.
I don't know what this error means. But I get system.img and userdata.img (which I haven't tryed yet) in out/target/product/wave.
This is the output:
Code:
Package target files: out/target/product/wave/obj/PACKAGING/target_files_intermediates/cm_wave-target_files-eng.pere.zip
Package OTA: out/target/product/wave/cm_wave-ota-eng.pere.zip
./device/samsung/wave-common/releasetools/wave_ota_from_target_files -v \
-p out/host/linux-x86 \
-k build/target/product/security/testkey \
--backup=true \
--override_device=wave,GT-S8500,S8500 \
out/target/product/wave/obj/PACKAGING/target_files_intermediates/cm_wave-target_files-eng.pere.zip out/target/product/wave/cm_wave-ota-eng.pere.zip
unzipping target target-files...
running: unzip -o -q out/target/product/wave/obj/PACKAGING/target_files_intermediates/cm_wave-target_files-eng.pere.zip -d /tmp/targetfiles-1Bxajb
--- target info ---
blocksize = (int) 4096
boot_size = (int) 7864320
default_system_dev_certificate = (str) build/target/product/security/testkey
extfs_sparse_flag = (str) -s
fs_type = (str) ext4
fstab = (dict) {'/sdcard': <common.Partition object at 0x1ac6310>}
mkyaffs2_extra_flags = (str) -c 4096 -s 128
recovery_api_version = (int) 2
system_size = (int) 262144000
tool_extensions = (str) device/samsung/wave/../common
userdata_size = (int) 2013265920
using device-specific extensions in device/samsung/common
unable to load device-specific module; assuming none
Traceback (most recent call last):
File "./device/samsung/wave-common/releasetools/wave_ota_from_target_files", line 866, in <module>
main(sys.argv[1:])
File "./device/samsung/wave-common/releasetools/wave_ota_from_target_files", line 834, in main
WriteFullOTAPackage(input_zip, output_zip)
File "./device/samsung/wave-common/releasetools/wave_ota_from_target_files", line 411, in WriteFullOTAPackage
script.FormatPartition("/system")
File "/home/pere/android/system/build/tools/releasetools/edify_generator.py", line 190, in FormatPartition
p = fstab[partition]
KeyError: '/system'
make: *** [out/target/product/wave/cm_wave-ota-eng.pere.zip] Error 1I confirm
out/target/product/wave/obj/PACKAGING/target_files_intermediates/cm_wave-target_files-eng.pere.zip
exists, but
out/target/product/wave/cm_wave-ota-eng.pere.zip
isn't being created after the error.
I don't know what this error means. But I get system.img and userdata.img (which I haven't tryed yet) in out/target/product/wave.
building OTA zip is final stage, which fails because we've got no estabilished partition structure definition yet. You can ignore it, system.img should be fully useful.
I've got no time in next weeks but I will happily merge all patches if you provide me any.
I think ADB and init binary in zImage might be not fully CM10 complaint.
I recommend forking my git repository, change local_manifest to point to yours and modify it, if you want to push any changes you should
a) browse to git project dir
b) do "git remote add my_remote <URL of repo you get on github"
c) "git checkout -b new_branch"
d) commit your changes
e) "git push my_remote new_branch"
Then do pull request on new_branch through github to me
Btw
Is there anyone who got it actually working? If not, I've got no clues what might be wrong.
I've got no time in next weeks but I will happily merge all patches if you provide me any.
I think ADB and init binary in zImage might be not fully CM10 complaint.
I recommend forking my git repository, change local_manifest to point to yours and modify it, if you want to push any changes you should
a) browse to git project dir
b) do "git remote add my_remote <URL of repo you get on github"
c) "git checkout -b new_branch"
d) commit your changes
e) "git push my_remote new_branch"
Then do pull request on new_branch through github to me
Btw
Is there anyone who got it actually working? If not, I've got no clues what might be wrong.
Last edited:
Add this on recovery.fstab :
/system ext3 system
/cache ext3 cache
/data ext3 userdata
tell me, also i dont remeber right /dev/block
you can try liek this :
/system ext3 /dev/block/loop...?
Thanks for the tip Tigrouzen! I haven't tried but will probably try at night.
Also I wanted to comment that I've tried with "my" (the one I obtained after compiling) system.img and it also got stuck at the Badadroid logo, and then also with the "kernel" file I compiled, which renamed to zImage after noticing with an hex editor that they should be the same file (it's about 3 MB bigger than the ICS one) - nothing worked, this time the phone switching off after showing the Badadroid logo for a while. Althought I was advised by Rebellos to forget new zImage for now, since it needs to be fixed.
The trouble is that, for unknown reason, all system.img I already uploaded works for me. At least to show up booting animation ("ANDROID').
In few weeks I'll try to clean the mess and make flashable boot.img.
In few weeks I'll try to clean the mess and make flashable boot.img.
I'm using
BL S8500XXKL5
APPS S8500XXLA1
But seriously I don't think it matters if it gets to badadroid logo.
BL S8500XXKL5
APPS S8500XXLA1
But seriously I don't think it matters if it gets to badadroid logo.
Last edited:
Rebellos i tried to mount all your images in linux and tried to open it in WinImage and i saw empty image in linux and got error in WinImage
I don't know why....
Thanks to nbates. He figured what's wrong - I failed hard and fooled you all, because my system.img doesn't work indeed, and zImage was falling back to bootup from sd card.
Sorry. I'll update it asap. xDD
Sorry. I'll update it asap. xDD
Last edited:
- Status
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
214CM10 "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.
If the Badadroid is restarting before you're able to catch any log:
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:
device name is wave so the build invocation can be brunch waveCode: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
FIRST INSTALLATION
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!):
Releases: http://goo.im/devs/Rebellos/wave - 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://xdaforums.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://xdaforums.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.
- 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 )
- 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)
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://xdaforums.com/showthread.php?t=145939152New 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 logging38New 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 SMS34
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. -.-'300.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. - Enter Bada Settings->General->Memory and make sure you have at least:
