This is thread for devlopment and discussion for cm10.1 (BCM21654)
myself working on Samsung galaxy pocket neo duos(S5312)
@Alonso1398 working on Samsung galaxy music
Contibutors:
@k2wl @Unjustified Dev @Alonso1398 @dhinesh77 @psych.half
Status for Cm10.1 on pocket neo duos (s5312)
Status for Cm10.1 on pocket neo duos (s5312)
First bootable cm 10.1 rom on S5312/S5310
Whats working ?
vibration
hardware buttons
external-sdcard
apps install
egl
camera(video recording force close because of antibanding feature)
sound
sensors
bluetooth ( minor bug only => unable to connect to any devices)
Wi-Fi
Storage
Ril,
whats not working ?
Source:
https://github.com/dhinesh77/android_device_samsung_corsica
Status for Cm10.1 on galaxy music
Status for Cm10.1 on galaxy music
Compiling again... I think thus time the bluedroid problem didn't show, hope it ends without more errors, also a question, when you managed to get to bootanimation, did you disabled hadware rendering by just editing build.prop?
Enviado desde mi GT-S6010L mediante Tapatalk
Alonso1398 said:
Compiling again... I think thus time the bluedroid problem didn't show, hope it ends without more errors, also a question, when you managed to get to bootanimation, did you disabled hadware rendering by just editing build.prop?
Enviado desde mi GT-S6010L mediante Tapatalk
Click to expand...
Click to collapse
for the first time disabled hardware rendering, due to that all apps force closes, after fixing egl force close error solved
dhinesh77 said:
for the first time disabled hardware rendering, due to that all apps force closes, after fixing egl force close error solved
Click to expand...
Click to collapse
Soo now finished compiling and installed but got a bootloop. Something interesting is that if restore boot from stock via cwm, it passes the bootanimation and a window that says android upgrading appears but when it finishes, then makes the bootanimation again and do the same eternally.
Updated a lot my device tree based on yours. Here is the device tree, the only folder that didn't modified was overlay, also the files from rootdir are the ones from my device (except init.recovery.rhea_ss_ivoryss.rc).
This are the files I'm using as proprietary blobs. Also I haven't modified my kernel source and had to comment"TARGET_USERIMAGES_USE_EXT4" from boardconfig.mk because for some reason was giving errors while compiling.
Also when trying taking logcat via adb it stucks on - waiting for device -
I was so close of getting it to boot :crying:
Edit: I think the files from the rootdir folder on my tree are the ones that should be edited, so already edited them to be like from your tree and I'm compiling again
Edit2: Editing those files to much do even worse, get stucked on the device logo so most of the files from rootdir are still the ones from the device. Also updated the system.prop file that was forgetting but still didn't worked to past bootanimation. Been really hard trying to fix it, could someone give me a hand?
Alonso1398 said:
Soo now finished compiling and installed but got a bootloop. Something interesting is that if restore boot from stock via cwm, it passes the bootanimation and a window that says android upgrading appears but when it finishes, then makes the bootanimation again and do the same eternally.
Updated a lot my device tree based on yours. Here is the device tree, the only folder that didn't modified was overlay, also the files from rootdir are the ones from my device (except init.recovery.rhea_ss_ivoryss.rc).
This are the files I'm using as proprietary blobs. Also I haven't modified my kernel source and had to comment"TARGET_USERIMAGES_USE_EXT4" from boardconfig.mk because for some reason was giving errors while compiling.
Also when trying taking logcat via adb it stucks on - waiting for device -
I was so close of getting it to boot :crying:
Edit: I think the files from the rootdir folder on my tree are the ones that should be edited, so already edited them to be like from your tree and I'm compiling again
Edit2: Editing those files to much do even worse, get stucked on the device logo so most of the files from rootdir are still the ones from the device. Also updated the system.prop file that was forgetting but still didn't worked to past bootanimation. Been really hard trying to fix it, could someone give me a hand?
Click to expand...
Click to collapse
yup sure i will.....from two days broad band is not working so I can't come to online. ....
you can take logs without adb too... if rom didn't booted just return back to cwm and flash aroma file mAnager and go to data/tombstones in that folder many files present. . copy allfiles to sd view in gedit ... error message will be in Brown colour... this helps to fix all bugs. .. I fixed for pocket neo like this method only.. since adb is working only after authorizing pc in development settings...
dhinesh77 said:
yup sure i will.....from two days broad band is not working so I can't come to online. ....
you can take logs without adb too... if rom didn't booted just return back to cwm and flash aroma file mAnager and go to data/tombstones in that folder many files present. . copy allfiles to sd view in gedit ... error message will be in Brown colour... this helps to fix all bugs. .. I fixed for pocket neo like this method only.. since adb is working only after authorizing pc in development settings...
Click to expand...
Click to collapse
Thanks a lot, didn't know that trick of aroma file manager, now finally made it boot :victory::victory:
Status:
Whats working?
-It boots
-Touch
-Hardware buttons (home fixed and now wakes the device)
-Camera (all modes)
-Vibration
-Rotation
-CRT effect
-Sound
-Wi-fi
-Bluetooth (it can receive files but not sure if it can send)
-Storage (both internal and external)
-Button for start reproducing music tough it can't stop it
-Microphone
-Ril
What's not working?
-fm radio
Notes:
-For some reason the glow effect wile sliding is orange instead of blue
Edit: Link to the thread here
Great going guys . Hatsoff to ur work. Waiting for completion
Sent from my GT-S6012 using Tapatalk
Alonso1398 said:
Thanks a lot, didn't know that trick of aroma file manager, now finally made it boot :victory::victory:
Status:
Whats working?
-It boots
-Touch
-Hardware buttons (home fixed and now wakes the device)
-Camera (I think)
-Vibration
-Rotation
-CRT effect
What's not working?
-Sound
-Ril
-Wi-fi
-Bluetooth
-Storage (both internal and external)
-No baseband
Notes:
-The button for start reproducing music I think it works but since there's no music because of storage problems, it can't reproduce anything but long pressing the button will open Apollo
-For some reason the glow effect wile sliding is orange instead of blue
-Also is it me or the unlock glow thing is kinda small?
Click to expand...
Click to collapse
Nice, i amanged to mount external storage but not internal memory, though external storage is working still many apps not opening because of no internal storage(since internal is seted as default)...
Latest strategy:
1.Wifi Hotspot working (but normal WIFI not working)
2. Bluetooth able to turn on and searching devices, but unable to connect to that..
3. Hardly tried still ril coulnt be fixed
dhinesh77 said:
Nice, i amanged to mount external storage but not internal memory, though external storage is working still many apps not opening because of no internal storage(since internal is seted as default)...
Latest strategy:
1.Wifi Hotspot working (but normal WIFI not working)
2. Bluetooth able to turn on and searching devices, but unable to connect to that..
3. Hardly tried still ril coulnt be fixed
Click to expand...
Click to collapse
I made dual boot to speed up process but for some reason every build made isn't booting even if I know it's going to boot and tombstones sometimes aren't generated so will going to download source again...
I keeped a booting build and fixed sound for it, so my next step is try fixing storage (since both internal and external aren't working)
Alonso1398 said:
I made dual boot to speed up process but for some reason every build made isn't booting even if I know it's going to boot and tombstones sometimes aren't generated so will going to download source again...
I keeped a booting build and fixed sound for it, so my next step is try fixing storage (since both internal and external aren't working)
Click to expand...
Click to collapse
bro over 95% of all bugs solved except one thats is ril
dhinesh77 said:
bro over 95% of all bugs solved except one thats is ril
Click to expand...
Click to collapse
Lol, I'm like turtle speed fixing problems then will try too with ril
Alonso1398 said:
Lol, I'm like turtle speed fixing problems then will try too with ril
Click to expand...
Click to collapse
any progress regarding ril ?
dhinesh77 said:
any progress regarding ril ?
Click to expand...
Click to collapse
Not so far, and this error 7 problem is worrying me, the builds shouldn't give that error since the device tree is almost the same as before when I was on the vbox, so being slowed down trying to fix it but I think my only actual solution is being replacing system folder on older flashable builds also storage seems like a headache for my device, already looked at your tree but still not working
Alonso1398 said:
Not so far, and this error 7 problem is worrying me, the builds shouldn't give that error since the device tree is almost the same as before when I was on the vbox, so being slowed down trying to fix it but I think my only actual solution is being replacing system folder on older flashable builds also storage seems like a headache for my device, already looked at your tree but still not working
Click to expand...
Click to collapse
dont worry bro i am here to help you between , all issues on samsung pocket neo duos is solved including ril....
Thanks a lot, the weird not installing problem it still there, however I can take the old working build and replace the system folder and boot.img with new ones compiled so somehow that way I can still be working however replacing the META-INF from the new builds doesn't work. I'm trying to apply the fixes for my device so now so far internal storage is finally working but external still doesn't, now that camera opens, discovered that camcoder isn't working for me, and bluetooth its activating but actually don't know if it can connect to other devices.
Thanks a lot for the help you are offering, really.
Edit: Wi-fi fixed however still without baseband and ril
Enviado desde mi MW0711 mediante Tapatalk
hi bro , i saw on github that you have merged pull request, w8ing for outcome
dhinesh77 said:
hi bro , i saw on github that you have merged pull request, w8ing for outcome
Click to expand...
Click to collapse
Thanks a lot for those pull requests, they fixed external storage tough internal just needed some changes. However ril still isn't working, I think that even my phone doesn't detect the sim card. Also I think microphone isnt' working too
At least most functions are working now thanks to you :highfive:
Alonso1398 said:
Thanks a lot for those pull requests, they fixed external storage tough internal just needed some changes. However ril still isn't working, I think that even my phone doesn't detect the sim card. Also I think microphone isnt' working too
At least most functions are working now thanks to you :highfive:
Click to expand...
Click to collapse
Do you patched the patches mentioned by pawitp in thread for grand duos ? ....
Related
A new release is ready the final Degu.
For both gen7/8 you will need to flash the latest zImage and initramfs included in the download links. <-- not needed if you already have flashed the latest with Crow. no changes in kernel or initramfs for Degu release.
Also to be sure you will need to delete your data.img and let it create a new one or copy your own if you use an image more then 256mb.
For setting up your device look here http://dev.openaos.org/wiki/AndroidInstall_CM7_Gingerbread
Links updated crow release 27-01-2013
For gen7:
http://www.openaos.org/wp-upload/gen7/2013-01-27/
For gen8:
http://www.openaos.org/wp-upload/gen8/2013-01-27/
If you have any issus post them by creating a new ticket see http://dev.openaos.org/wiki/IssueTracking on howto.
Known issues are here: http://dev.openaos.org/wiki/AndroidTicketsFor2.3
If it works well or you have issues you can also leave a reply.
BTW camera should partly work on gen8, tested on a 101IT taking photos. Video recording will freeze the app. Not tested with apps that use the cam only with the included camera app.
A43IT has a different camera, so I don't know if it will work.
Thanks,
divx118
Usefull links for setting up the devices:
Gen7 devices: http://dev.openaos.org/wiki/SettingUpMultiRootGen7
Gen8 devices: http://dev.openaos.org/wiki/SettingUpMultiRootGen8
General info: http://dev.openaos.org/wiki/AndroidInstall_CM7_Gingerbread
Building your own image: http://dev.openaos.org/wiki/AndroidBuildEnvironment
Degu final (27-01-2013)
------------------------------------------------------------------------------------------------------------------------------------
Changelog:
- Smoother youtube video playback for gen8
- More apps in the market available for gen7 and gen8 (also thanks to utopik for this)
- Internal storage should now properly display free available memory for gen7 and gen8
- Fixed bookmark for gapps in the browser for gen7 and gen8
- Overal speed improvement.
Unfortunately you will need a fresh data.img to let these fixes take effect.
Crow final (25-12-2012)
------------------------------------------------------------------------------------------------------------------------------------
First don't forget to flash he new zImage (kernel) and initramfs it is in the archive kernel_gen7_20120512_114451.tar.gz for gen7 and kernel_gen8_20120409_002900.tar.gz for gen8 unpack it (with winrar if you are on windows) and only use "zImage" and "initramfs.cpio.gz"
Changelog see http://www.openaos.org/archives/821
Bull final (09-04-2012)
------------------------------------------------------------------------------------------------------------------------------------
First don't forget to flash he new zImage (kernel) and initramfs it is in the archive kernel_gen7_20120512_114451.tar.gz for gen7 and kernel_gen8_20120409_002900.tar.gz for gen8 unpack it (with winrar if you are on windows) and only use "zImage" and "initramfs.cpio.gz"
Only for gen7: If you flash the new kernel and initramfs also delete the old menu.lst when it is there. If you have custom lines in there add them later after you first booted in the new menu.lst that is created.
Only for gen8: If you first boot the image it happens sometimes that omap_vout isn't loaded correctly this means it can't create the overlay for playback video and uses the software renderer. If you just reboot it is ok. It only happens atleast to me on the very first boot.
Some improvements first the kernel and initramfs:
- Correct orientation of the bootmenu for A101IT
- Updated the kernel with latest archos GPL release which means that the ones with broken USB host on their A101IT it gets working again when booting stock through the bootmenu.
- For gen7 updated initramfs to match the one from gen8
- Added unionfs support, so you can have root with rw access on stock android.
Improvements on Gingerbread:
- smoother camera because of using the overlay to display the stream. Known issues: - display is cropped so you don't see the whole camera - Recording still doesn't work.
- Youtube app works.
- Hardware accelerated video for atleast youtube app and some mp4 files, maybe more if someone can test some different formats that would be nice. Rotation does work for youtube app, there are still some issues when rotating playing a regular mp4.
- On gen8 you can also play hw accelerated flash videos in the browser now, of course not all pages will work.
- wifi location should work now. <-- same for gen7
- Fix not enough storage when installing apps by moving /cache also to the data.img. <-- same for gen7
- Update to latest CM code. <-- same for gen7
RC2 (24-12-2011)
------------------------------------------------------------------------------------------------------------------------------------
This will be the final Bull release or there must be some major bugs discovered in the next few days.
There is now a new feature added (thanks to illifant). The data is now in a separate image "data.img" if it is not there it will be auto created. 256 MB is standard. You can replace it with a bigger one from the download link gen8_data.img.tar.bz2.
If you unpack with for example winrar you see three images 256MB, 512MB, 1024MB just pick a size and copy that to the root of your archos. Rename it to "data.img"
As mentioned you don't have todo this if you want to use 256MB that will be created automaticly.
All your data, apps and gapps are in data.img. So on a next upgrade you won't have to reinstall everything again.
Also the size of the actual image is reduced, for gen7 it is 180MB and for gen8 256MB.
Don't forget to flash the new zImage (kernel) and initramfs it is in kernel_gen7_20111224_181411.tar.bz2 for gen7 and kernel_gen8_20111224_213037.tar.gz for gen8 unpack it with winrar and only use "zImage" and "initramfs.cpio.gz"
(if not specified otherwise the fixes are for gen7 and gen8)
Gingerbread Image:
- Deep sleep improved, however to work properly keep adb disabled. (it is now disabled by default.)
- Charging A43 for USB and wall charger is fixed (gen8)
- External sd-card is now mounted on /mnt/storage/sdcard (same as on archos firmware).
- Updated with latest CM code.
- New modules from updated kernel build (gen8)
- Other small fixes see the closed tickets.
zImage and initramfs.cpio.gz:
- Initramfs script updated, if it fails it will now display an error message instead of just rebooting.
- Kernel updated to latest archos firmware (2.4.81) kernel (gen8)
RC1 (06-11-2011)
------------------------------------------------------------------------------------------------------------------------------------
Somethings that are changed since anoa release:
(if not specified otherwise the fixes are for gen7 and gen8)
- Fixed headphone speaker switch
- partly camera working for atleast A101IT I think also A70, don't know for A43IT because it has a different cam. (gen8)
- Fixed permission errors when using ext3 formatted internal memory
- Fixed some browser crashes. Due to using v8 javascript engine again instead of jsc
- Fixed crash when going to browser settings
- Fixed deep sleep which should be working now.
- Fixed mounting/unmounting external sdcard.
- Calibration app included for A32 and A43. (Under settings)
- Updated to latest CM code
- Kernel updated to latest sources from archos firmware 2.4.65
- Fixed correct rotation for A101, only bootmenu is still upsidedown.
- GPS working for gen7 devices
- some other small things
Tips:
1) Playing youtube videos on CM fail with standard player http://pastebin.com/YAZc0z74 , but can be done with mobo player or mx player by using for example opera mobile and setting the user agent to desktop.
i'll give it a try now
The Bootmenu doesn't start. It hangs on the first Archos Screen (before OpenAOS).
It don't creates the menu.lst file also.
(Archos 101 G8)
airwolf1544 said:
The Bootmenu doesn't start. It hangs on the first Archos Screen (before OpenAOS).
It don't creates the menu.lst file also.
(Archos 101 G8)
Click to expand...
Click to collapse
I'm having the same issue.
(Archos 70 8GB)
airwolf1544 said:
The Bootmenu doesn't start. It hangs on the first Archos Screen (before OpenAOS).
It don't creates the menu.lst file also.
(Archos 101 G8)
Click to expand...
Click to collapse
You are right, something went wrong with the upload of the zImage, if you check md5sum it is wrong. I will post when it is fixed. Should be soon.
divx118
EDIT: zImage is fixed now if you already downloaded it just redownload
hey - great to hear about further development - sadly the gen8 links seems to be down ...
www.openaos.org/wp-upload/gen8/2011-11-06/ReleaseCandidate_UNSUPPORTED/
Error: Connection interrrupted
Perrhaps just partial - will try again later
EDIT: working now again
After choosing "Gingerbread-Entry" in Aos-Menu my 101 shortly shows the "openaos"- Bootlogo and then reboots in Archos-Standard.
What is wrong?? I used all files from the Link mentioned above.
Any ideas?
P.S: Reload of the files is not possible because it seems like openaos.org is down ;-(
We are having some issues with dev.openaos.org which will hopefully soon be solved.
The problem you have is a corrupted zImage. It should be fine now once you can redownload it.
Sorry for the inconvenience,
divx118
EDIT: wrote too soon, seems the links are accessible again
Hubelbert said:
After choosing "Gingerbread-Entry" in Aos-Menu my 101 shortly shows the "openaos"- Bootlogo and then reboots in Archos-Standard.
What is wrong?? I used all files from the Link mentioned above.
Any ideas?
P.S: Reload of the files is not possible because it seems like openaos.org is down ;-(
Click to expand...
Click to collapse
Is the name right? openaos-gingerbread.img.gz
airwolf1544 said:
Is the name right? openaos-gingerbread.img.gz
Click to expand...
Click to collapse
Yes that should be correct, just tested it myself. Just deleted my image, menu.lst flashed the initramfs and kernel and booted.
divx118
Oops sorry, need some more coffee this morning it was meant for Hubelbert.
Nice work..
Bugger - I sholdn't have installed UrukDroid yesterday (I read you can add Uruk to Mulitiboot, but what if its already installed?)
Whats the fixes/updates with this release please, or is it on the site?
SWFlyerUK said:
Bugger - I sholdn't have installed UrukDroid yesterday
Whats the fixes/updates with this release please, or is it on the site?
Click to expand...
Click to collapse
- Fixed headphone speaker switch
- partly camera working for atleast A101IT I think also A70, don't know for A43IT because it has a different cam.
- Fixed permission errors when using ext3 formatted internal memory
- Fixed some browser crashes. Due to using v8 javascript engine again instead of jsc
- Fixed crash when going to browser settings
- Fixed deep sleep which should be working now.
- Fixed mounting/unmounting external sdcard.
- Calibration app included for A32 and A43. (Under settings)
- Updated to latest CM code
- Kernel updated to latest sources from archos firmware 2.4.65
- some other small things
divx118
hey divx - do we have any working way of dualboot urukdroid and Cyanogen?
For me this is the major reason for less contribution on openAOS - as i need a working stable device for dialy use - but also really want to help u with cyanogen...
Searched for it some time ago already but due to the different kernels this was really hard to figure out...
anyway will try yours again now and check out the new release
FrEcP said:
hey divx - do we have any working way of dualboot urukdroid and Cyanogen?
For me this is the major reason for less contribution on openAOS - as i need a working stable device for dialy use - but also really want to help u with cyanogen...
Searched for it some time ago already but due to the different kernels this was really hard to figure out...
anyway will try yours again now and check out the new release
Click to expand...
Click to collapse
Unfortunately not, maybe in the future when we can boot different kernels. We just follow the archos kernel sources with some minor additions to also allow booting of other linux distros. We want however always be able to boot stock android with our kernel which gives you btw root access, because of using unionfs.
I don't know how much difference there is between the urukdroid kernel and ours never looked at it.
divx118
So far it is running smooth. Great job guys.
I noticed 3 things so far.
1) my speakers make a "pop" sound when the device goes into and comes out of sleep. They also did that in Anoa.
2) I can swipe between the different home screens OK, but if I try to use the desktop dots next to the dock then ADW force closes.
3) Camera worked great the first time, then the second time I went back in it, it is green and gray colored. Tried changing the color effect settings of the camera and it looks the same every time. Rebooting fixed the greenish look and I have been in it multiple times now and it is staying normal so not sure what caused it the first time.
marcusmarcus said:
So far it is running smooth. Great job guys.
I noticed 3 things so far.
1) my speakers make a "pop" sound when the device goes into and comes out of sleep. They also did that in Anoa.
2) I can swipe between the different home screens OK, but if I try to use the desktop dots next to the dock then ADW force closes.
3) Camera worked great the first time, then the second time I went back in it, it is green and gray colored. Tried changing the color effect settings of the camera and it looks the same every time. Rebooting fixed the greenish look and I have been in it multiple times now and it is staying normal so not sure what caused it the first time.
Click to expand...
Click to collapse
1) Yes I noticed that too, I will see if I can poke one of the archos guys to know what is causing this issue.
2) Yes, it is a known issue. If you go into ADWlauncher settings the dots will disappear. I know what is causing the problem just need some time to create a proper fix.
3) Never had this on the 101. What kind of device do you have? A101 A70 or A43
Thanks for reporting back,
divx118
BTW there are still some problems accessing dev.openaos.org if the downloadlink doesn't work try again later.
divx118 said:
1) Yes I noticed that too, I will see if I can poke one of the archos guys to know what is causing this issue.
2) Yes, it is a known issue. If you go into ADWlauncher settings the dots will disappear. I know what is causing the problem just need some time to create a proper fix.
3) Never had this on the 101. What kind of device do you have? A101 A70 or A43
Thanks for reporting back,
divx118
BTW there are still some problems accessing dev.openaos.org if the downloadlink doesn't work try again later.
Click to expand...
Click to collapse
1) I was incorrect about my speakers popping in Anoa, they crackled in that, so the pop I think is an improvement
2) that's good news. I don't use the dots as I prefer to swipe, I just accidentally click one and that is how I found out.
3)I have an A70 8GB. I'm not sure what would have caused it, I have not been able to reproduce it since rebooting the device.
marcusmarcus said:
3)I have an A70 8GB. I'm not sure what would have caused it, I have not been able to reproduce it since rebooting the device.
Click to expand...
Click to collapse
Good to know it works on the A70, it wasn't tested yet.
divx118
You are right. I forgot a 'dot' between img and gz
Now everything is fine and it works very smooth. Seems even smoother than Urukdroid.
Great job. I continue testing.
This thread has been superseded by this thread: http://forum.xda-developers.com/showthread.php?t=1366897
Changelog in Second Post:
Screenshots attached at bottom:
Link to Alpha8
This tarball also contains a userdata image where most of the gapps are.
People whose rotation/bluetooth doesn't work: Try flashing this new boot.img and see if it fixes it.
I will not be uploading any more flashable zips as they seem to be broken
Working:
Wifi
MMS
Calling (People I talk to say they can hear me better than the could when i was on CM7)(Probably coincidence)
Bluetooth (works for babijoee but broken for me)
TouchScreen (Multitouch)
Sound (Flawless)
GPS (works for me)
Accelerometer (rotation) (works for babijoee but broken for me)
Home button
3g (seems to like radio 5.08.00.04)(works for me)
Headphone jack
Network Stats and Quota
Click to expand...
Click to collapse
Not Working:
Trackball
Camera
USB mass storage (use adb)
Hardware Accelaration
Wifi Signal Strengh Icon in Status Bar.
Click to expand...
Click to collapse
Questions? Check out this FAQ (thanks alex_mobile)
Anyone that wants to colaborate
Join us in #ics_desire_nexus_dev on freenode
My nick is drewis.
Any help is welcome.
To flash the img files.
Code:
tar xjf ics-passion-alpha*.tar.bz2
adb reboot bootloader
fastboot -w
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot reboot
I'm using blackrose hboot (standard partitioning) but i dont think it matters what hboot you use.
Don't tell me whats wrong with it (i already know that) Tell me how to fix it!
Here's my sources to get you started:
I have set up an organization on git hub where you can follow the progress
https://github.com/ics-passion-dev
[Note:] I am updating these regularly.
Get source (cm ics repos)
Code:
repo init -u git://github.com/ics-passion-dev/android.git -b ics
repo sync
Fix Audio.
Code:
cd hardware/msm7k
git fetch http://review.cyanogenmod.com/p/CyanogenMod/android_hardware_msm7k refs/changes/03/10303/1 && git cherry-pick FETCH_HEAD
Build it.
Code:
. build/envsetup.sh
lunch full_passion-userdebug
mka
Note: The above is not enough to get a clean build you will need to debug some minor errors.
On amd hexacore w/ 12gb ram takes 40 minutes. (where CM7 takes 14)
CHANGELOG
CHANGELOG
Alpha8 Link to Alpha8
New apn list from cm
Update gapps with ones from koush's NS build.
Headphone fix (thanks zivan56)
Back to pershoot's BFS kernel as base.
Added network stats and quota to kernel.
Built with opengl enabled (currently causing blank screen)(REMOVED)(still no HWAccel)(disable Window/Transition effects makes it much nicer)
Alpha7 Link to: Alpha7
Same as alpha6
Rebuilt with openjdk (this is aosp after all)
Added Gmail and Market
Market: login, try and download an app (only one), it will error. Reboot. Open market and it should start downloading. Then you're good.
Market: I wiped and now market does not work. same error. Can't seem to fix it.
Change to IntersectRaven's 2.6.38.8 AVS Kernel based on pershoot's
Alpha6 Link to: Alpha6
Added liba2dp for audio over bluetooth. (untested) (removed: caused build problems)
AUDIO FIX: a real audio fix (thank you firesnatch [sean neeley])
Head phone jack does not work yet. plays through speaker while plugged in.
added back all apps but VideoEditor and its libs and Camera
added back all ringtones and notifications
switched back to userdebug build
No gapps: Sorry. They were deleted when i rebased my tree. But they had issues anyway. So not bothering with them on this release.
gralloc's back (hence the lag) Disabling animation in developer settings helps.
3g seems to start the connect/disconnect thing after a while of non use. fix is either reboot. or go into setting and disable mobile data for a minute then turn it back on.
Alpha5: Link to Alpha5
switched from userdebug to eng variant
got su back and some bluetooth files (still broke for me)
removed most sounds (ringtones,notifications) to save some space
removed apps: Camera, VideoEditor, libWnnJpnDic, PinyinIME, Email, Exchange, libvideoeditor_jni, libvideoeditorplayer, libvideoeditor_core
Added Gapps: Market wont show up untill you sign in through settings
Issues: screen now flashes an orange outline on edge of screen when you click some buttons
Alpha4: Link to Alpha4 as system and boot images
Home button works! (thanks again to rampv78)
Removed soft buttons
Changed lcd density back to 240
Alpha3:Link to Alpha3 as a flashable zip
Rebase latest changes in CM tree.
Try new GPS code in CM gerrit.
Better Audio fix: Still broken but more stable (closer to working out a real fix)
Leave out gralloc since we dont have HW Acceleration yet.
Alpha2:Link to Alpha2 as a flashable zip
changed ro.sf.lcd_density to 220 to fix softkeys
build with gralloc: kind of makes it laggy if it bothers you delete /system/lib/hw/gralloc.qsd8k.so (but not gralloc.default.so)
Working:
Calling: (mic works they can hear you)
Sound/Mic: sort of (thanks to tip from rapmv78 and the Desire guys)
Gps: I think (might just be googles location features even though its unchecked in settings)(tested by visiting maps.google.com in browser with wifi off)
Not Working:
3g: still very sporadic (a few reboots fixes it somtimes)(maybe i need to update to latest radio)
Home button
Trackball
Alpha1: Link to Alpha1 as system.img and boot.img
Migrate source to CM repos
Using ICS init (alpha0 used CM7)
Pershoots CM7 2.6.38.8 Kernel
Added Soft Buttons to give us a working home button (although this causes the bottom row of the keyboard to be half way covered up) You can fix this by changing ro.sf.lcd_density to 220 or 200 in /system/build.prop
Not working:
3g (severe connect/disconnect issues)
Audio
Home button
Trackball
Some other stuff I can't remember
texasice said:
I would like to get a functioning ICS build as soon as possible. Anyone that wants to colaborate im hangin out in #cyanogenmod-dev on freenode with nick drewis. There is no way I will be able to do this by myself. So any help is welcome.
Pic below is a first build
Issues:
nothing works except touchscreen but it is still broken. It acts like a trackpad.
But it did boot on the first try so thats something.
Click to expand...
Click to collapse
I would really like to help you. And I am also very excited about having ICS running on my nexus one. I'm a java developer. Please let me know if I would be useful building ICS on nexus one?
Thanks.
Update:
Bluetooth is working: I can pair my logitech dinovo keyboard to it and navigate.
Wifi is scanning but not connecting to wpa.
No progress on touchscreen acting like a trackpad. Upside multitouch works.
Did you manage to get GL acceleration working?
Does this help for the touchscreen issue? The touchscreen was working well on the SDK port
http://forum.xda-developers.com/showpost.php?p=18711543&postcount=55
Just use the IDC file from my SDK port.
sunnybhai said:
Does this help for the touchscreen issue? The touchscreen was working well on the SDK port
http://forum.xda-developers.com/showpost.php?p=18711543&postcount=55
Click to expand...
Click to collapse
dr1337 said:
Just use the IDC file from my SDK port.
Click to expand...
Click to collapse
Yup. fixed it.
dr1337 said:
Did you manage to get GL acceleration working?
Click to expand...
Click to collapse
No i havent even looked at that.
nice work
Will we get a test build to play with?
skitty said:
Will we get a test build to play with?
Click to expand...
Click to collapse
Soon. I've been trying to upload one but my internet f-ing blows and it keeps failing. Right now its no better than the sdk port.
Wifi turns on but won't connect.
3g won't stay connected
no audio
Touchscreen works thought
mms works
Great news! I wish I could help somehow. Why don't you collaborate with drew garen? I'm sure he could help you.
Sent from my HTC Flyer P510e using XDA App
this is awesome work , have you tried contacting any of the developers or contributors from TeamDouche ... they may help you to resolve any issues !!
Have you try to contact @drewgaren to ask him which trick did he use to correct the problems he was having with first sdk port?
Maybe he can share some drivers file which can be helpful.
Thanks for all the work you put in this DEV.
F.
Wow! Great initiative guys, good luck and hope move developers can contribute.
amazing work guys
I've since upgraded from an N1 but still use it to play around with builds so if you need testers i'd be more than happy to help!
great work
keep going
Keep Going guys, i wish i can help but i have no idea about developing at all.
Need help?
If you need help on development work, I might be able to help. I am also a Java developer. Thanks and keep up with the good work!
Finally we get CWM Recovery for Dell Strek Pro.
[StreakPro][Recovery][Beta]Clockwork Mod 6.0.1.1
http://forum.xda-developers.com/showthread.php?p=29847686#post29847686
This CWM made by manii
and I am a tester (because SPro launch only in Japan)
I already asked to Cyanogen mod and AOKP.
But Kang said "we don't support dell" and Cyanogen mod no answer
I'm looking for custom rom developers.
Please help me
Regards.
Sent from my GS01 using xda premium
Help
Anyone figured out how to enter into recovery mode of dell GS01?:crying:
hatoo said:
Finally we get CWM Recovery for Dell Strek Pro.
[StreakPro][Recovery][Beta]Clockwork Mod 6.0.1.1
http://forum.xda-developers.com/showthread.php?p=29847686#post29847686
This CWM made by manii
and I am a tester (because SPro launch only in Japan)
I already asked to Cyanogen mod and AOKP.
But Kang said "we don't support dell" and Cyanogen mod no answer
I'm looking for custom rom developers.
Please help me
Regards.
Sent from my GS01 using xda premium
Click to expand...
Click to collapse
It's in the works. CM10.1 compiles just fine, but i'm getting bootloops due lack of ion support in 2.6 kernel. I've managed to (mostly) port spro-specific things to CodeAurora's 3.4 kernel and fixed all compilation errors, but spro's device configuration routine is sort of different from vanilla msm8260 (some things are being configured by aboot, yet it's performing some checks that are unclear to me at the moment). Currently kernel fails to boot and device is getting into the blink-camera's flash-and-switch-screen-off mode (same mode device gets when it's turned on with volume-up+volume-down keys).
Oh, and by the way: i've tried to contact both Compal (odm and actual kernel developer for spro) and Dell to get information about what kernel was used in that unreleased 062-world wide dell rom. Compal's mailserver refused to deliver my message, and Dell's opensource departament people responded only once askung if i seek information on 2.6 kernel. I've re-stated that i'm seeking information on 062 rom and 3.x kernel - no word from them since then
So, we're up to ourselves with this one. If anyone's capable and willing to help with resolving 3.4 kernel boot issues - drop a line into this thread - i'll upload my current kernel tree to github.
---------- Post added at 10:03 PM ---------- Previous post was at 09:59 PM ----------
Anyone figured out how to enter into recovery mode of dell GS01?:crying:
Click to expand...
Click to collapse
Power+volume up+home if i recall it correctly. Another way is to issue
Code:
fastboot boot your-recovery-image-name.img
while in fastboot mode.
For those who it may concern
Here's a list of my SPro-related repos (in order of appearance):
2.6 kernel - original dell sources bumped to .14 along with other additions. should be suitable for ics-based roms.
caf-3.4 kernel - my current point of interest.
device/dell/msm8660-common and device/dell/streakpro - device source trees for cyanogenmod 10.1, both based on htc pyramid device trees.
While I've never had a SPro, good luck with it.
Awesome!
I use GS01 as my main device, so I'm looking forward to your custom ROM!
Sort of update.
Dell responded:
I apologize for the delay. I have learned that we did not update to 3.x. I think you may have the latest versions. Thank you for your inquiry.
Click to expand...
Click to collapse
So, we're on our own. Great..
Request
Trying to figure if androidboot.serialno= is really unique per-device.
I would like to ask StreakPro owners to post output of their device's cat /proc/cmdline output here. Command should be issued as root user, so you'll need to install TheManii's Superuser.zip via cwm.
Thanks in advance.
Is this ok?
kibuuka said:
Trying to figure if androidboot.serialno= is really unique per-device.
I would like to ask StreakPro owners to post output of their device's cat /proc/cmdline output here. Command should be issued as root user, so you'll need to install TheManii's Superuser.zip via cwm.
Thanks in advance.
Click to expand...
Click to collapse
# cat /proc/cmdline
cat /proc/cmdline
console=ttyHSL0,115200,n8 androidboot.hardware=qcom androidboot.emmc=true androi
dboot.hw_id=5 androidboot.serialno=205108 androidboot.baseband=msm
hatoo said:
# cat /proc/cmdline
cat /proc/cmdline
console=ttyHSL0,115200,n8 androidboot.hardware=qcom androidboot.emmc=true androi
dboot.hw_id=5 androidboot.serialno=205108 androidboot.baseband=msm
Click to expand...
Click to collapse
Yep just what I needed, thanks hatoo.
kibuuka said:
Yep just what I needed, thanks hatoo.
Click to expand...
Click to collapse
Hi Kibuuka!
What about DS5 ICS development, are still working on it?
Regards...
Dell steak 5 can't enter fastboot and always restarting somebody help me pls
unlock
Not really the right thread to ask that, but not able to get into fastboot or not able to get into recovery?
Dell Streak Pro GS01 (E mobile)
Kindly requesting for help with my phone mentioned above,
i was looking for methods to root, i ran super one click and got my phone stuck on the E mobile logo,
i cannot find any support on the internet,
am so frustrated
shakes1883 said:
Kindly requesting for help with my phone mentioned above,
i was looking for methods to root, i ran super one click and got my phone stuck on the E mobile logo,
i cannot find any support on the internet,
am so frustrated
Click to expand...
Click to collapse
First of all - as a rule of thumb you're better NOT to use one-click solutions for anything - these ARE evil.
Let's think you don't want to/can't disassemble it.
You'll need:#1 drivers for Spro - grab it here, #2 fastboot and adb binaries - grab these, #3 one of the stock ROMs - TheManii did a great job collecting them - select one containing SPro in filename from here, #4 CWM recovery image - grab this one (courtesy of TheManii) and #5 - superuser flasheable package (by TheManii as well)
You have to wait until phone's battery is fully drained.
After that you need to connect it to pc. It will enter so called "charge-only state" (charging battery animation). Wait until it fully charges (LED will become green). Disconnect it from pc/power supply now.
Then you'll need to turn it on by pushing power button AND volume down at the same time to enter fastboot mode - screen will go black with two lines on it:
Code:
FATBOOT!!!!
Version 0.5
Connect your phone to pc - you'll see third line
Code:
USB cable connected
and windows will ask for drivers for device (if you don't have them installed already)
After drivers installation you're set to fix you problem.
Open command prompt and cd to a dir containing adb and fastboot binaries (let's assume full path is y:\adb\ and you have copied CWM image into this folder):
Code:
cd y:\adb\
Then boot (we don't flash it this time preserving your device's warranty ) into CMW recovery
Code:
fastboot boot y:\adb\SPro-6.0.1.2.img
You'll see good'ol CWM recovery screen. Navigate to "Mounts and storage", then select "mount USB storage". Your pc will now be able to access phone's internal and external storage. Now copy ROM image of choice and superuser package to either of phone's partitions you've connected to pc on previous step.
Select Unmount in CWM menu (AFTER you did a safe device removal in windows - thin precaution will save you some nerves).
Navigate to "install zip from sdcard", then to "choose zip from sdcard", select ROM image you've copied previously, select "Yes - Install update-zip-you-have-selected.zip"
CWM will install ROM image for you.
Now do the same selecting superuser package instead of ROM image and install it as well.
Select "reboot system now". If everything's ok you'll see your device booting into your newly installed ROM. If it doesn't - get to fastboot mode again, boot CMW image and do a factory reset using it ("wipe data/factory reset").
I'll just leave it here
Not creating separate thread for this, just teasing a bit .
http://www.mediafire.com/download/oje1t47k1ght15w/cm_streakpro-ota-3ead3941fd.zip
Summary: cyanogenmod-10.1 for StreakPro
NOT suitable for everyday use as of yet (mediaserver lockup bug is showstopper here), testing purposes only.
prerequisites:
baseband that is newer than 061 to get gsm voice working. (tested using baseband taken from MIL_2.0.12.0)
CWM recovery (to install it )
Working:
Boot
Speaker/wired headset/handset audio
Voice calls
Wifi
adb is enabled by default
3d seem to be working (gfxbench runs just as fine as on 061-World-Wide-Dell ROM)
Sensors (partially, there seem to be a problem with proximity sensor in phone app)
Hardware buttons (+button leds)
Touchscreen
Top LED (behaves differently, green while charging, blinks white on unread sms/email)
Battery stats (consumption measurement values are taken from similar device (htc pyramid) - if someone has access to real values for SPro - please share)
Buggy/not working at all:
Mobile data (known, working on fixing it)
Tethering (haven't touched it yet)
Bluetooth (haven't touched it yet)
UMS (internal/external SD are recognized and accesseable by apps, but pc mounting fails due to Settings segfault)
Camera (halfway there - cameras are being recognized by system/applications but currently we're unable to capture image. i'm working on it)
Mediaserver seem to be locking up boot process 9 times of 10. adb shell killall mediaserver will resume it.
You're encouraged to issue adb shell pm disable com.android.providers.media/com.android.providers.media.MediaScannerReceiver
to make mediascanner stop eating battery and cpu time like crazy.
No video in Youtube app. (haven't touched it yet)
Mute switch (low priority, got several options how to fix it, have to decide which is better)
bug reports aren't really needed, i'm aware of problems current build has and slowly (tbh - very slowly, shortage of spare time) progressing on those.
if someone's able/wishes to help fixing bugs - device tree and kernel are on my github.
kibuuka said:
Not creating separate thread for this, just teasing a bit .
http://www.mediafire.com/download/oje1t47k1ght15w/cm_streakpro-ota-3ead3941fd.zip
Summary: cyanogenmod-10.1 for StreakPro
NOT suitable for everyday use as of yet (mediaserver lockup bug is showstopper here), testing purposes only.
prerequisites:
baseband that is newer than 061 to get gsm voice working. (tested using baseband taken from MIL_2.0.12.0)
CWM recovery (to install it )
Working:
Boot
Speaker/wired headset/handset audio
Voice calls
Wifi
adb is enabled by default
3d seem to be working (gfxbench runs just as fine as on 061-World-Wide-Dell ROM)
Sensors (partially, there seem to be a problem with proximity sensor in phone app)
Hardware buttons (+button leds)
Touchscreen
Top LED (behaves differently, green while charging, blinks white on unread sms/email)
Battery stats (consumption measurement values are taken from similar device (htc pyramid) - if someone has access to real values for SPro - please share)
Buggy/not working at all:
Mobile data (known, working on fixing it)
Tethering (haven't touched it yet)
Bluetooth (haven't touched it yet)
UMS (internal/external SD are recognized and accesseable by apps, but pc mounting fails due to Settings segfault)
Camera (halfway there - cameras are being recognized by system/applications but currently we're unable to capture image. i'm working on it)
Mediaserver seem to be locking up boot process 9 times of 10. adb shell killall mediaserver will resume it.
You're encouraged to issue adb shell pm disable com.android.providers.media/com.android.providers.media.MediaScannerReceiver
to make mediascanner stop eating battery and cpu time like crazy.
No video in Youtube app. (haven't touched it yet)
Mute switch (low priority, got several options how to fix it, have to decide which is better)
bug reports aren't really needed, i'm aware of problems current build has and slowly (tbh - very slowly, shortage of spare time) progressing on those.
if someone's able/wishes to help fixing bugs - device tree and kernel are on my github.
Click to expand...
Click to collapse
WOW! AMAZING! Never expect Streak pro will have CM. Thank you so much for you work.
Finally!!
So nice ROM!!
I love you Kibu lol
Please Support Custom rom dell streak pro
I know many xda dev community is a good: Good:, the dell streak pro help you make a rom version 4.x so it works better : O
thanks!
- CPU: Qualcomm MSM8260A Snapdragon, 1.5 GHz Dual-Core Processor
- RAM: 1 GB Memory: 4 GB
- External Memory MicroSD (T-Flash) up to 32 GB
- Camera: 8.0 MP, support LED flash, autofocus
- Cinematography: FullHD 1080p @ 30fps
- Battery capacity: 1520 mAh
- Super AMOLED Plus display with 16 million colors Resolution giai540 x 960 pixels Size 4.3 inches
- OS: 2.3.5 Androi
are looking forward to the help of kibuuka well as helping people in xda
kibuuka said:
Not creating separate thread for this, just teasing a bit .
Summary: cyanogenmod-10.1 for StreakPro
NOT suitable for everyday use as of yet (mediaserver lockup bug is showstopper here), testing purposes only.
prerequisites:
baseband that is newer than 061 to get gsm voice working. (tested using baseband taken from MIL_2.0.12.0)
CWM recovery (to install it )
Working:
Boot
Speaker/wired headset/handset audio
Voice calls
Wifi
adb is enabled by default
3d seem to be working (gfxbench runs just as fine as on 061-World-Wide-Dell ROM)
Sensors (partially, there seem to be a problem with proximity sensor in phone app)
Hardware buttons (+button leds)
Touchscreen
Top LED (behaves differently, green while charging, blinks white on unread sms/email)
Battery stats (consumption measurement values are taken from similar device (htc pyramid) - if someone has access to real values for SPro - please share)
Buggy/not working at all:
Mobile data (known, working on fixing it)
Tethering (haven't touched it yet)
Bluetooth (haven't touched it yet)
UMS (internal/external SD are recognized and accesseable by apps, but pc mounting fails due to Settings segfault)
Camera (halfway there - cameras are being recognized by system/applications but currently we're unable to capture image. i'm working on it)
Mediaserver seem to be locking up boot process 9 times of 10. adb shell killall mediaserver will resume it.
You're encouraged to issue adb shell pm disable com.android.providers.media/com.android.providers.media.MediaScannerReceiver
to make mediascanner stop eating battery and cpu time like crazy.
No video in Youtube app. (haven't touched it yet)
Mute switch (low priority, got several options how to fix it, have to decide which is better)
bug reports aren't really needed, i'm aware of problems current build has and slowly (tbh - very slowly, shortage of spare time) progressing on those.
if someone's able/wishes to help fixing bugs - device tree and kernel are on my github.
Click to expand...
Click to collapse
hope you help fix bugs present in nodules rom, dell community treak pro users have been waiting for this day ever. thank you very much
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
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://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
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.
its always stuck at badadroid boot image
tried with both
Mikegapinski release and anghelyi's release
not able to boot into jelly bean
yeah! Rebellos is best!
stuck at boot.
but 4.0.4 slim is still better than this release
I've uploaded new package and updated link. Hope now it does contain correct image.
@Up:
U say? Sherlock.
Rebellos said:
I've uploaded new package and updated link. Hope now it does contain correct image.
@Up:
U say? Sherlock.
Click to expand...
Click to collapse
stucks on boot logo.
but im not sure whats the problem, the system file or the zImage file.
can someone give me a work zImage file?
Rebellos said:
I've uploaded new package and updated link. Hope now it does contain correct image.
@Up:
U say? Sherlock.
Click to expand...
Click to collapse
Again bad img
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.
Rebellos said:
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.
Click to expand...
Click to collapse
I'll try it now.
THANK AGAIN!
Rebellos said:
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.
Click to expand...
Click to collapse
Hi Rebellos
the same is with new system.img
Could you please upload img without archiving? Probably problem is with your archiver
shaiws said:
stucks on boot logo.
but im not sure whats the problem, the system file or the zImage file.
can someone give me a work zImage file?
Click to expand...
Click to collapse
Here you have everything you need, the initramfs is the zImage without compiling.
https://github.com/Rebell/bdroid
best regards.
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 http://goo.im/devs/Rebellos/cm10-wave-0.01/
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.
Rebellos said:
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
Click to expand...
Click to collapse
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.
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.
Click to expand...
Click to collapse
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.)
Click to expand...
Click to collapse
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.
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??
deeps_17 said:
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??
Click to expand...
Click to collapse
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.,,
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
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.
Hi guy!
After some days without any answer, i have worked on Kitkat.
It seems that it boots on my tab.... :angel:
Wait the fist release on 2.6.29 kernel
And 2.6.37 for A70S2 (HC and FROYO)
:good::fingers-crossed::good:
Bizcuite
Amazing Biz... you are my hero :good:
airwolf1544 said:
Amazing Biz... you are my hero :good:
Click to expand...
Click to collapse
I will to become all red stop stop please lol
Well it rests a lots of works!!!!
I have just boot logo.
I will try to boot it with 2.6.29 kernel, but it must be ok and have the same result (only BT and upnp should (/could) not worked).
For 4 days i will be at home and works when i have times to work on it.
Bizcuite
bizcuite said:
i will become all red stop stop please lol
well it rests a lots of works!!!!
I have just boot logo.
I will try to boot it with 2.6.29 kernel, but it must be ok and have the same result (only bt and upnp should (/could) not worked).
For 4 days i will be at home and works when i have times to work on it.
Bizcuite
Click to expand...
Click to collapse
ready to test sir!
Wow, just wow. Amazing!
Sharpen you swords (charge your batteries) and get ready for fiiiiiiight (and get ready for teeeeeeeeest)
bizcuite said:
I will to become all red stop stop please lol
Well it rests a lots of works!!!!
I have just boot logo.
I will try to boot it with 2.6.29 kernel, but it must be ok and have the same result (only BT and upnp should (/could) not worked).
For 4 days i will be at home and works when i have times to work on it.
Bizcuite
Click to expand...
Click to collapse
I know its much work.. but you try it..
airwolf1544 said:
I know its much work.. but you try it..
Click to expand...
Click to collapse
Oooooh yes its lots of work. And patience to wait the compilation finish it...
I recompile all atm. I had forgotten to include all device.mk file maybe I will have trebuchet at first start (yes I compile cm11 ).
Gpu driver and libs seems to work... I have the boot logo (and a crash system. Bootloop)
First screenshot is near
Bizcuite
Sent from my GT-N7100 using xda app-developers app
Just a question: Are you gonna make this use ART, cause that's what I guess u will do and that's something that I guess will make the tab faster, but as far as I understand as of now ART makes a lot of apps not work (at least for now till they are updated)?
Ranomez said:
Just a question: Are you gonna make this use ART, cause that's what I guess u will do and that's something that I guess will make the tab faster, but as far as I understand as of now ART makes a lot of apps not work (at least for now till they are updated)?
Click to expand...
Click to collapse
You have the choice. you can choose in dev option dalvik or art.
Or chane an option in buid.prop, set libdvm to libart or inverse.
I have a boot failure at start, i try to fix it.
Bizcuite
Welcome Kitkat
Bizcuite
bizcuite said:
Welcome Kitkat
Bizcuite
Click to expand...
Click to collapse
I would like to try also kitkat on my 101, gen. 8 :good:
greeting
mika67 said:
I would like to try also kitkat on my 101, gen. 8 :good:
greeting
Click to expand...
Click to collapse
It will be possible with 2.6.29 kernel i think.
ATM on A70S2 - Gen9 kernel 2.6.35-7:
-TS working
-3D working
-Soft button activated on my tab (to see on others tabs)
Not working:
-sound (don't know why atm)
-BT (just have to configure init.rc)
-Wifi (recompile all with Wlan option, must work after)
-looooots of thing that i have not tested.
Another thing, Kitkat must have system in a different partition, you will have to install 3 image files in the sdcard (root of system, system and data).
I think that i will use directly the internal sdcard partition and write partitions directly on the sdcard (like a real partition, not an image -> better perf ). BUT a wipe of the sdcard is necessary (one time).
Bizcuite
bizcuite said:
It will be possible with 2.6.29 kernel i think.
ATM on A70S2 - Gen9 kernel 2.6.35-7:
-TS working
-3D working
-Soft button activated on my tab (to see on others tabs)
Not working:
-sound (don't know why atm)
-BT (just have to configure init.rc)
-Wifi (recompile all with Wlan option, must work after)
-looooots of thing that i have not tested.
Another thing, Kitkat must have system in a different partition, you will have to install 3 image files in the sdcard (root of system, system and data).
I think that i will use directly the internal sdcard partition and write partitions directly on the sdcard (like a real partition, not an image -> better perf ). BUT a wipe of the sdcard is necessary (one time).
Bizcuite
Click to expand...
Click to collapse
Send me something to test - I am getting exited!
bizcuite said:
It will be possible with 2.6.29 kernel i think.
Another thing, Kitkat must have system in a different partition, you will have to install 3 image files in the sdcard (root of system, system and data).
I think that i will use directly the internal sdcard partition and write partitions directly on the sdcard (like a real partition, not an image -> better perf ). BUT a wipe of the sdcard is necessary (one time).
Bizcuite
Click to expand...
Click to collapse
Hi biz,
I think that with the first test would be not so bad if the installation only with
3 image file would take place (simpler installation).
If the new system has then beta status could one then the partition
on the internal SD card drove through .
Are already curious on the new system
greeting
mika67 said:
Hi biz,
I think that with the first test would be not so bad if the installation only with
3 image file would take place (simpler installation).
If the new system has then beta status could one then the partition
on the internal SD card drove through .
Are already curious on the new system
greeting
Click to expand...
Click to collapse
Partitions directmy wrote on the internal sdcard will be option at start.
Now. The main PB is the wifi hal. Because wpa supplicant v0.6 and wl1271 driver has been deleted from the code source of Android. I try to compile it for 2.6.35 (more easy because drivers are updated).
Let me see if there is a way to have wifi for 2.6.29 kernel.
Bizcuite
Sent from my GT-N7100 using xda app-developers app
ready to test for 101IT when you have something
Will the touchscreen be as difficult to make work as the last kernel you worked on these last few weeks ?
Cheers!
4qu4rius said:
ready to test for 101IT when you have something
Will the touchscreen be as difficult to make work as the last kernel you worked on these last few weeks ?
Cheers!
Click to expand...
Click to collapse
I don't know
But it will be more easy to fix than with CM9 (first experience in android compilation for remember )
FYI:
I had few time to try the new image that i have compiled.
It's compiled with CM options (wasn't the case in CM9). Bootlogo is CM, themes doesn't crashed, but it lakes a little thing to fix.
I will try to fix wifi this week end if i have more times to dev.
I progress about it, ATM i try with 2.6.35 (only for A70S2), and i hope that it will worked with 2.6.29 (for all others tabs), mac80211 module is included into this kernel, but maybe the driver cannot be compatible
Bizcuite
bizcuite said:
I don't know
But it will be more easy to fix than with CM9 (first experience in android compilation for remember )
FYI:
I had few time to try the new image that i have compiled.
It's compiled with CM options (wasn't the case in CM9). Bootlogo is CM, themes doesn't crashed, but it lakes a little thing to fix.
I will try to fix wifi this week end if i have more times to dev.
I progress about it, ATM i try with 2.6.35 (only for A70S2), and i hope that it will worked with 2.6.29 (for all others tabs), mac80211 module is included into this kernel, but maybe the driver cannot be compatible
Bizcuite
Click to expand...
Click to collapse
Biz
Any progress on this?
Thanks
Mikerla said:
Biz
Any progress on this?
Thanks
Click to expand...
Click to collapse
Yes and no, i work on it when i have times.
I try to find any ways to have a working wifi. I use CM11 wifi drivers but i cannot use it correctly (myukernel or CM11 is not configured properly).
When i have a working wifi i will upload an alpha release.
For screen and navigation button, i think that there will have no pb with it. The managment about this is very different.
To fix:
-Wifi
-external/internal sdcard not seen
-OMX codecs
-Sound HAL
-BT
-ALL
Bizcuite