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

Status
Not open for further replies.
Search This thread
By:
Advanced…
jon.marius87

jon.marius87

Senior Member
Aug 24, 2012
166
23
Bucharest
gcarlo_f said:
So, can't get badadroid working back ...
CWM is always launched instead of badadroid, in logs I have:

Code: 
Starting recovery on Tue May  7 14:13:27 2013
framebuffer: fd 4 (480 x 800)
CWM-based Recovery v6.0.2.8
recovery filesystem table
=========================
  0 /tmp ramdisk (null) (null) 0
  1 /boot mtd boot (null) 0
  2 /system ext4 /bada_system/system.img (null) 393216000
  3 /cache ext4 /bada_system/cache.img (null) 18874368
  4 /data ext4 /bada_app/data.img (null) 419430400
  5 /bada_system vfat /dev/block/mmcblk0p1 (null) 0
  6 /bada_user vfat /dev/block/mmcblk0p2 (null) 0
  7 /bada_app vfat /dev/block/mmcblk0p3 (null) 0
  8 /sdcard vfat /dev/block/mmcblk0p2 (null) 0
  9 /external_sd vfat /dev/block/mmcblk1p1 (null) 0

W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
I:Processing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"

ro.boot.serialno=0000045600000123
ro.serialno=0000045600000123
ro.bootmode=unknown
ro.baseband=unknown
ro.bootloader=unknown
ro.hardware=wave
ro.revision=48
ro.emmc=0
ro.boot.emmc=0
ro.factorytest=0
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=mass_storage,adb
ro.build.id=JZO54K
ro.build.display.id=cm_wave-userdebug 4.1.2 JZO54K eng.nikolay.20130506.221327 test-keys
ro.build.version.incremental=eng.nikolay.20130506.221327
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.2
ro.build.date=Mon May  6 22:18:17 MSK 2013
ro.build.date.utc=0
ro.build.type=userdebug
ro.build.user=nikolay
ro.build.host=U12
ro.build.tags=test-keys
ro.product.model=GT-S8500
ro.product.brand=samsung
ro.product.name=cm_wave
ro.product.device=wave
ro.product.board=wave
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=s5pc110
ro.build.product=wave
ro.build.description=cm_wave-userdebug 4.1.2 JZO54K eng.nikolay.20130506.221327 test-keys
ro.build.fingerprint=samsung/cm_wave/wave:4.1.2/JZO54K/eng.nikolay.20130506.221327:userdebug/test-keys
ro.build.characteristics=default
ro.cm.device=wave
ro.rommanager.developerid=cyanogenmod
keyguard.no_require_sim=true
ro.url.legal=[ I AM A NEW USER AND CAN'D POST URLS ]
ro.url.legal.android_privacy=[ I AM A NEW USER AND CAN'D POST URLS ]
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.cm.version=10-20130506-UNOFFICIAL-wave
ro.modversion=10-20130506-UNOFFICIAL-wave
ro.config.ringtone=Orion.ogg
ro.config.notification_sound=Deneb.ogg
ro.config.alarm_alert=Hassium.ogg
ro.opengles.version=131072
wifi.interface=wlan0
mobiledata.interfaces=pdp0,eth0,gprs,ppp0
ro.vold.switchablepair=/storage/sdcard0,/storage/sdcard1
rild.libpath=/system/lib/libmocha-ril.so
ro.sf.lcd_density=240
ro.com.google.locationfeatures=1
ro.com.google.networklocation=1
ro.kernel.android.checkjni=0
dalvik.vm.checkjni=false
ro.vold.umsdirtyratio=20
dalvik.vm.dexopt-data-only=1
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=128m
ro.carrier=unknown
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.tcp.buffersize.gprs
dalvik.vm.stack-trace-file=/data/anr/traces.txt
init.svc.ueventd=running
net.tcp.buffersize.default=4096,87380,110208,4096,16384,110208
net.tcp.buffersize.wifi=4095,87380,110208,4096,16384,110208
net.tcp.buffersize.umts=4094,87380,110208,4096,16384,110208
net.tcp.buffersize.edge=4093,26280,35040,4096,16384,35040
net.tcp.buffersize.gprs=4092,8760,11680,4096,8760,11680
init.svc.recovery=running
init.svc.console=running
sys.usb.config=mass_storage,adb
service.adb.root=1
init.svc.adbd=restarting
sys.usb.state=mass_storage,adb

I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
mount: mounting /bada_app/data.img on /data failed: No such file or directory
W:failed to mount /bada_app/data.img (File exists)
Error mounting /data!
I:Can't partition unsafe device: /dev/block/mmcblk0p2
I:Can't format unknown volume: /emmc

I've also re-installed bootfiles/fota/zimage and cm-10-wave-0.32.zip but nothing to do... suggestions? must I reflash bada?
Click to expand...
Click to collapse

try reflash bada than install version CM0.32 and replace with new version kernel from CM 0.32 :)
 
A

akzwitch

Member
Jul 21, 2012
24
1
gcarlo_f said:
So, can't get badadroid working back ...
CWM is always launched instead of badadroid, in logs I have:

Code: 
Starting recovery on Tue May  7 14:13:27 2013
framebuffer: fd 4 (480 x 800)
CWM-based Recovery v6.0.2.8
recovery filesystem table
=========================
  0 /tmp ramdisk (null) (null) 0
  1 /boot mtd boot (null) 0
  2 /system ext4 /bada_system/system.img (null) 393216000
  3 /cache ext4 /bada_system/cache.img (null) 18874368
  4 /data ext4 /bada_app/data.img (null) 419430400
  5 /bada_system vfat /dev/block/mmcblk0p1 (null) 0
  6 /bada_user vfat /dev/block/mmcblk0p2 (null) 0
  7 /bada_app vfat /dev/block/mmcblk0p3 (null) 0
  8 /sdcard vfat /dev/block/mmcblk0p2 (null) 0
  9 /external_sd vfat /dev/block/mmcblk1p1 (null) 0

W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
I:Processing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"

ro.boot.serialno=0000045600000123
ro.serialno=0000045600000123
ro.bootmode=unknown
ro.baseband=unknown
ro.bootloader=unknown
ro.hardware=wave
ro.revision=48
ro.emmc=0
ro.boot.emmc=0
ro.factorytest=0
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=mass_storage,adb
ro.build.id=JZO54K
ro.build.display.id=cm_wave-userdebug 4.1.2 JZO54K eng.nikolay.20130506.221327 test-keys
ro.build.version.incremental=eng.nikolay.20130506.221327
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.2
ro.build.date=Mon May  6 22:18:17 MSK 2013
ro.build.date.utc=0
ro.build.type=userdebug
ro.build.user=nikolay
ro.build.host=U12
ro.build.tags=test-keys
ro.product.model=GT-S8500
ro.product.brand=samsung
ro.product.name=cm_wave
ro.product.device=wave
ro.product.board=wave
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=s5pc110
ro.build.product=wave
ro.build.description=cm_wave-userdebug 4.1.2 JZO54K eng.nikolay.20130506.221327 test-keys
ro.build.fingerprint=samsung/cm_wave/wave:4.1.2/JZO54K/eng.nikolay.20130506.221327:userdebug/test-keys
ro.build.characteristics=default
ro.cm.device=wave
ro.rommanager.developerid=cyanogenmod
keyguard.no_require_sim=true
ro.url.legal=[ I AM A NEW USER AND CAN'D POST URLS ]
ro.url.legal.android_privacy=[ I AM A NEW USER AND CAN'D POST URLS ]
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.cm.version=10-20130506-UNOFFICIAL-wave
ro.modversion=10-20130506-UNOFFICIAL-wave
ro.config.ringtone=Orion.ogg
ro.config.notification_sound=Deneb.ogg
ro.config.alarm_alert=Hassium.ogg
ro.opengles.version=131072
wifi.interface=wlan0
mobiledata.interfaces=pdp0,eth0,gprs,ppp0
ro.vold.switchablepair=/storage/sdcard0,/storage/sdcard1
rild.libpath=/system/lib/libmocha-ril.so
ro.sf.lcd_density=240
ro.com.google.locationfeatures=1
ro.com.google.networklocation=1
ro.kernel.android.checkjni=0
dalvik.vm.checkjni=false
ro.vold.umsdirtyratio=20
dalvik.vm.dexopt-data-only=1
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=128m
ro.carrier=unknown
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.tcp.buffersize.gprs
dalvik.vm.stack-trace-file=/data/anr/traces.txt
init.svc.ueventd=running
net.tcp.buffersize.default=4096,87380,110208,4096,16384,110208
net.tcp.buffersize.wifi=4095,87380,110208,4096,16384,110208
net.tcp.buffersize.umts=4094,87380,110208,4096,16384,110208
net.tcp.buffersize.edge=4093,26280,35040,4096,16384,35040
net.tcp.buffersize.gprs=4092,8760,11680,4096,8760,11680
init.svc.recovery=running
init.svc.console=running
sys.usb.config=mass_storage,adb
service.adb.root=1
init.svc.adbd=restarting
sys.usb.state=mass_storage,adb

I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
mount: mounting /bada_app/data.img on /data failed: No such file or directory
W:failed to mount /bada_app/data.img (File exists)
Error mounting /data!
I:Can't partition unsafe device: /dev/block/mmcblk0p2
I:Can't format unknown volume: /emmc

I've also re-installed bootfiles/fota/zimage and cm-10-wave-0.32.zip but nothing to do... suggestions? must I reflash bada?
Click to expand...
Click to collapse
have you tried to reflash bada?
 
D

damnjan

Senior Member
Dec 14, 2012
73
5
why i have only 108 MB free on my phone memory(Wave 2 last bada2.0 turko version,i think it is 8) of max 300MB???pls help me...i deleted all and i formated phone too...(new version of cvm10 has 145 MB!)
 
A

akzwitch

Member
Jul 21, 2012
24
1
damnjan said:
why i have only 108 MB free on my phone memory(Wave 2 last bada2.0 turko version,i think it is 8) of max 300MB???pls help me...i deleted all and i formated phone too...(new version of cvm10 has 145 MB!)
Click to expand...
Click to collapse
maybe it is the apps that you installed on phone memory...
Check data usage to see..

Have you deleted previous version of CM10 if you have installed later version?
 
Last edited:
D

damnjan

Senior Member
Dec 14, 2012
73
5
akzwitch said:
maybe it is the apps that you installed on phone memory...
Check data usage to see..

Have you deleted previous version of CM10 if you have installed later version?
Click to expand...
Click to collapse
I don't have anything installed.....but probably cm10 isn't uninstalled if my phone has some bug...i'll try to reinstall bada ....hope it will work
 
H

hunktb

Senior Member
Sep 29, 2012
83
130
@Ravariya

Thanks again for logs and edit to confirm bluetooth not working yet , and for bugreport

I share again my analysis ...
In logcat (similar in bugreport) I see
Code: 
BluetoothEventLoop.cpp(  336): get_adapter_path: D-Bus error: org.freedesktop.DBus.Error.ServiceUnknown (The name org.bluez was not provided by any .service files)

Googling a bit I have found this that seems related, and in this case they found a fix

http://rootzwiki.com/topic/39259-qualcomm-bluetooth-d-bus-problem/

https://github.com/TheWhisp/android_device_samsung_jena/commit/29d33ed695ce6de8780567d1248088023b2e892d



Edit 1:
As it works in S8500, I realized it is very unlikely that the reason for not working to be a bug in source.
After more search about the error message in logs:

1) There is a related bug in Firefox OS, with status "RESOLVED WON'T FIX" ... "Message doesn't seem to be causing any problems so not a blocker."
https://bugzilla.mozilla.org/show_bug.cgi?id=804769

2) Found in several places a "funny" fix; just to delete a directory/file !
http://blog.pfuender.net/archives/61, where also appears the same error message in logs

Fix:
From root shell, delete or rename /data/misc/bluetoothd/XX:XX:XX:XX:XX:XX/sdp

The previous page seems to be the "source" (it is the oldest page I have found about it and it is is from 2010). I have found for example:
http://forum.cyanogenmod.org/topic/32723-unable-to-enable-bluetooth/
In some places the say delete sdp, config or the whole /data/misc/bluetoothd directory... and it worked for some people!

Just to be sure, in my S8500

Code: 
/data/misc/bluetoothd # ls -l
drwxr-xr-x bluetooth bluetooth          2013-03-17 21:07 43:29:B1:55:00:00
drwxr-xr-x bluetooth bluetooth          2013-04-28 15:20 D4:E8:B2:9E:39:DE

The real MAC is the second one (it is the one that appear in bada and in badadroid after Volk204's fix in 0.32 version)

43:29:B1:55:00:00 seems to be something that Cyanogenmod uses by default http://rootzwiki.com/topic/11849-di...ics-port-for-fascinate-build-1/page__st__2010

So this suggest a new test: delete /data/misc/bluetoothd/* and test again ...

For scared people: after removing /data/misc/bluetoothd/* in my S8500, bluetooth continues working. Turning it on creates again just directory with right mac and config file, and searching and pairing creates more files.


Edit 2:
Verified that same error "BluetoothEventLoop.cpp( 337): get_adapter_path: D-Bus error: org.freedesktop.DBus.Error.ServiceUnknown (The name org.bluez was not provided ..." appears in my S8500 where bluetooth works ok.
 
Last edited:
  • Like
Reactions: canis999, Ravariya and Rebellos
A

anuragdc

Guest
Alpha 0.31 Review

WHATS WORKING ::)
WI-FI
CAMERA
CAMERA LED
Playstore and Google search and google Now through gapps-jb-20121011-signed.zip installed through CWM :cowboy:
Accelerometer


WHATS NOT WORKING :(
GPS is not working
Bluetooh (Switches on But cannot search any devices or not visible )
Modem i.e CALL,GPRS,SMS,MMS
No Video Recording SD or HD

If you could fix the other problem It would be Greatfull Thnxxx in Advance.:fingers-crossed:
 
F

florynwk3

Senior Member
Nov 18, 2012
179
43
Bradford
anuragdc said:
WHATS WORKING ::)
WI-FI
CAMERA
CAMERA LED
Playstore and Google search and google Now through gapps-jb-20121011-signed.zip installed through CWM :cowboy:
Accelerometer


WHATS NOT WORKING :(
GPS is not working
Bluetooh (Switches on But cannot search any devices or not visible )
Modem i.e CALL,GPRS,SMS,MMS
No Video Recording SD or HD

If you could fix the other problem It would be Greatfull Thnxxx in Advance.:fingers-crossed:
Click to expand...
Click to collapse

Dude,Call and SMS works but on call it's not working receiving and send sound
 
Last edited:
R

rohit_95

Member
Jul 11, 2011
11
4
New Delhi
No Network - Log

I'm using 0.32 Rom, with S8500. I'm not able to get any network signal. It didn't work with the previous version also. I have attached logs, with me switching airplane mode on & off. I hope you can fix the problem. Thank you in advance :)
 

Attachments

  • Logs.zip
    70 KB · Views: 15
  • Like
Reactions: Rebellos, hunktb and volk204
H

HMIDA92

Senior Member
Mar 3, 2013
67
9
rohit_95 said:
I'm using 0.32 Rom, with S8500. I'm not able to get any network signal. It didn't work with the previous version also. I have attached logs, with me switching airplane mode on & off. I hope you can fix the problem. Thank you in advance :)
Click to expand...
Click to collapse

Same as me and these are logs.:victory:

Important note: for those who couldn't catch logs just try to replace "emmc" in the cmd by "storage/sdcard0".:fingers-crossed::good:

sry 4 bd eng.
 

Attachments

  • logcat.zip
    67.8 KB · Views: 6
  • Like
Reactions: hunktb
C

chemosun

Senior Member
May 11, 2012
53
33
hunktb said:
@Ravariya

Thanks again for logs and edit to confirm bluetooth not working yet , and for bugreport

I share again my analysis ...
In logcat (similar in bugreport) I see
Code: 
BluetoothEventLoop.cpp(  336): get_adapter_path: D-Bus error: org.freedesktop.DBus.Error.ServiceUnknown (The name org.bluez was not provided by any .service files)

Googling a bit I have found this that seems related, and in this case they found a fix

http://rootzwiki.com/topic/39259-qualcomm-bluetooth-d-bus-problem/

https://github.com/TheWhisp/android_device_samsung_jena/commit/29d33ed695ce6de8780567d1248088023b2e892d



Edit 1:
As it works in S8500, I realized it is very unlikely that the reason for not working to be a bug in source.
After more search about the error message in logs:

1) There is a related bug in Firefox OS, with status "RESOLVED WON'T FIX" ... "Message doesn't seem to be causing any problems so not a blocker."
https://bugzilla.mozilla.org/show_bug.cgi?id=804769

2) Found in several places a "funny" fix; just to delete a directory/file !
http://blog.pfuender.net/archives/61, where also appears the same error message in logs

Fix:
From root shell, delete or rename /data/misc/bluetoothd/XX:XX:XX:XX:XX:XX/sdp

The previous page seems to be the "source" (it is the oldest page I have found about it and it is is from 2010). I have found for example:
http://forum.cyanogenmod.org/topic/32723-unable-to-enable-bluetooth/
In some places the say delete sdp, config or the whole /data/misc/bluetoothd directory... and it worked for some people!

Just to be sure, in my S8500

Code: 
/data/misc/bluetoothd # ls -l
drwxr-xr-x bluetooth bluetooth          2013-03-17 21:07 43:29:B1:55:00:00
drwxr-xr-x bluetooth bluetooth          2013-04-28 15:20 D4:E8:B2:9E:39:DE

The real MAC is the second one (it is the one that appear in bada)

43:29:B1:55:00:00 seems to be something that Cyanogenmod uses by default http://rootzwiki.com/topic/11849-di...ics-port-for-fascinate-build-1/page__st__2010

So this suggest a new test: delete /data/misc/bluetoothd/* and test again ...

For scared people: after removing /data/misc/bluetoothd/* in my S8500, bluetooth continues working. Turning it on creates again just directory with right mac and config file, and searching and pairing creates more files.
Click to expand...
Click to collapse

No,It doesnt work.Now S8530 bluetooth address is the real one,same as bada.Volk made the real macaddr can be read by modem fuction.

Sent from my GT-S8530 using xda app-developers app
 
  • Like
Reactions: hunktb
R

Rebellos

Senior Recognized Developer
May 13, 2009
1,353
3,428
Gdańsk
Stevethegreat said:
IIRC wave uses the same chpset as Galaxy S (the original), which in turn does support otg: http://xdaforums.com/showthread.php?t=1450298
...so it is a matter of including a specific driver, is it not?
Click to expand...
Click to collapse
Technically you are right. Practically on chip OTG support does still require dc-dc boost converter onboard to provide 5V output from phone. So while it is nearly sure that wave would communicate with an usb flash drive for instance, it might require externally provided +5V rail. I cant remember now if there is a proper IC on Wave's board. While it is a standard now. It was not back in SGS1 times.
 
  • Like
Reactions: hunktb
H

hunktb

Senior Member
Sep 29, 2012
83
130
HMIDA92 said:
Same as me and these are logs.:victory:

Important note: for those who couldn't catch logs just try to replace "emmc" in the cmd by "storage/sdcard0".:fingers-crossed::good:

sry 4 bd eng.
Click to expand...
Click to collapse

rohit_95 said:
I'm using 0.32 Rom, with S8500. I'm not able to get any network signal. It didn't work with the previous version also. I have attached logs, with me switching airplane mode on & off. I hope you can fix the problem. Thank you in advance :)
Click to expand...
Click to collapse

Thanks for logs. Again sharing what I learn every day
Looking in logs I see calls to some RIL functions not yet implemented:
In both logs

E/RIL-Mocha( 145): Request not implemented: 103
D/RILJ ( 516): [0155]< RIL_REQUEST_REPORT_STK_SERVICE_IS_RUNNING error: com.android.internal.telephony.CommandException: REQUEST_NOT_SUPPORTED

This is related with STK, that after googling I understand is a service offered by some network operators in some SIMs. For example vodafone (rohit_95 operator stated in user info) offers it http://support.vodafone.com.au/articles/FAQ/SIM-Toolkit
 and says "SIM toolkit requires a compatible phone, the menu will not display on phones that do not support it"
Network operator for HMIDA92 is Nedjma (in logs), but I am not able to read arabic to verify if it offers STK services :)

In both logs there are also a lot of errors:
E/RIL-Mocha( 145): Request not implemented: 28
D/RILJ ( 516): [0156]< SIM_IO error: com.android.internal.telephony.CommandException: REQUEST_NOT_SUPPORTED

This seems related for me with some specific communication with SIM maybe related with previous STK. I am just able to get this error log with "Messages > MENU > Settings > Manage SIM card messages"; with my network operator it doesn't appears in logs in any other situation.

I am sure fix this will need more RIL development, but I am not able to guess the development complexity and priority of that, and I think it will be difficult to test if developers and testers SIMs are no STK type. Even a possible patch (if possible) which would allow just to deal with SIM ignoring all STK related info I think will need coding and testing..

So ... any solution for this? Development, so according to "SUPPORT" section in OP, you should either develop it, or wait for a developer answer (Volk204, Rebellos) without waiting an ETA :)
 
Status
Not open for further replies.

Similar threads

V
  • Locked
[ROM][WIP] CM10.1 Badadroid v2.1
Replies
2K
Views
490K
Sandeep Srikantam
Sandeep Srikantam
V
[ROM][WIP] CM11 Badadroid v4.4
Replies
581
Views
273K
U
Union_Jack
V
[ROM][WIP][NAND] Omni 4.4 - 26.01.2016
Replies
615
Views
267K
AlinTecsan
AlinTecsan
Tigrouzen
[ROM] MIUI V4 Jelly Bean Wave v1
Replies
369
Views
109K
M
ManishBansiwal
V
[ROM][WIP] CM10.2 Badadroid v3.1
Replies
265
Views
125K
alcatel4010x
alcatel4010x

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 214
    R
    Rebellos
    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.
    Click to expand...
    Click to collapse
    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.
    Click to expand...
    Click to collapse

    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://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.
    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://xdaforums.com/showthread.php?t=1459391
    View
    52
    V
    volk204
    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
    View
    38
    V
    volk204
    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
    View
    34
    R
    Rebellos
    Gamepower said:
    Pls release it now

    Sent from my GT-S8530 using xda app-developers app
    Click to expand...
    Click to collapse

    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. -.-'
    View
    30
    R
    Rebellos
    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.
    View

New posts