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.
Related
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!
This is not a thread to say ‘thanks’ to developers. Only post here if you have some input in this development progress, by either fixing bugs, or coming up with ideas (and ideally, try your idea and report what happens).
Having that said, let’s move on to where we are at the moment. Currently, we have a build which is based upon Ice Cold Sandwich 6.2 Test Edition for the HTC Desire HD. This build boots up by flashing my custom kernel on it, based on Flyer HC Original Kernel Source, with some patches:
-Quota2 Support
-Genlock Support
-Updated KGSL driver by applying Lord Clockans patches from his kernel
The ZIP we are working on now, can be downloaded here:http://w728685.open.ge.tt/1/files/9iI3CbF/0/blob?download
This ZIP contains a build which is mainly Lord Clockans ICS, with essential changes in the ROM to get it booting (we used LeeDroid’s Flyer HC as the donor ROM). This ROM is made for a HoneyComb HBOOT!
After you have flashed that ZIP, this is the kernel you need: http://ge.tt/9iI3CbF/v/1
You MUST flash this kernel to get it up and running, or it’ll just loop in the logcat complaining about unsupported stuff.
This set should do the following:
-Boot up (bootanimation resets after some time, it’s ok, it will boot within 5 minutes).
-Touchscreen works after you did this: open ADB Shell (by entering ‘adb shell’ on your pc,), and send the command “echo ‘1’> /sys/android_touch/event_google”. Now touchscreen should be working. (For some reason the file 90flyerhacks in /system/etc/init.d doesn’t do its job. If anyone has a clue > say so!) Also, the ntrig.c file in /drivers/input/touchscreen/ is modified in the kernel, don’t know if it helped though.
-Full Hardware Accceleration
-Screen is bugged at certain moments (seems to happen especially during things concering wallpapers. Rendering a wallpaper, showing a heavy LWP, etc.). The build.prop file contains some lines such as:
ro.fb.mode=1
debug.composition.type=gpu/mdp
debug.fb.rgb565=0
Perhaps we have to change these lines to get it running without issues (strange thing is, logcat doesn’t seem to make an issue about this). We can also try a recompile of the kernel using the entire driver folder from Lord Clockans kernel (it’s in /drivers/gpu/msm/ in his kernel, and /drivers/video/msm/gpu/kgsl_adreno205_hc in ours, moving the folder to where it should be causes issues, so we keep it like this for the time being).
-Sound is working
-Backcamera seems to be working fine, haven’t tested frontcamera.
-Hardware buttons under the screen aren’t working, and this should be a low
priority for now. It isn’t ideal to use them in ICS anyway (different button functions in comparison with the softbuttons), and I think we shouldn’t focus on this for now.
-GPS switch can be enabled, haven’t tested whether it works.
-Bluetooth switch can be enabled, but turns off automatically after about ten seconds.
-WiFi switch can’t be changed, logcat tells us that it can’t connect with /dev/rfkill, applying this patch in the ramdisk could fix it:
https://github.com/OpenSensation/an...mmit/da09360d70888a7e126871ab2ae5b218514cad18
-Power button and Volume buttons work fine.
-Pen works after we send the event_google command mentioned before.
If the ROM immediately reboots within 10 seconds and it seems like it’s looping, and you can’t even logcat, hold down Power and Volume Down until you get to HBOOT, select FASTBOOT, and enter ‘fastboot erase cache’ in the CMD/Terminal, and reboot, and it should work.
And that’s about it for the current things we know I think. If you manage to fix something, please write down and report what you did to fix it, so we can keep a list. I will work on a vendor folder using the known information, so we can compile a ROM from source, made for our device.
And last, but not least: don’t post here asking for release dates. We will do our utmost best to bring ICS experience to the Flyer, but do not bug us. Thanks.
Now let’s get this up and running guys! I will keep a log of what is fixed and what is not, so we can keep the thread organized. Else we’ll have 50 ZIPs around, not knowing which one is the right one et cetera.
Source code of kernel: http://github.com/Chaosz-X
Ramdisk will be uploaded tomorrow.
Donations are much appreciated, as I'm developing and building atm on a 1.67GHz Dual core...
Donations can me made to [email protected] using Paypal.
i suggest creating two repos... one for ROM and one for kernel... that way single file changes can be tracked even on ROM front, not just kernel...
willing devs can fork those repo and send pull requests to main repo when they get stuff working
I'm not a developer, and I have nothing but love for all the great devs that worked so hard to bring ICS to the Flyer.
Might I suggest, however, that instead of pursuing CM9 builds, the next effort be centered around porting the Android Open Kang Project (AOKP) ROM? In terms of features and customizations, it's considerably ahead of CM9, with numerous supported devices to boot.
I think this ROM, versus CM9, would give users the most flexible and dynamic ICS experience for their Flyer.
Chaosz-X said:
-Touchscreen works after you did this: open ADB Shell (by entering ‘adb shell’ on your pc,), and send the command “echo ‘1’> /sys/android_touch/event_google”. Now touchscreen should be working. (For some reason the file 90flyerhacks in /system/etc/init.d doesn’t do its job. If anyone has a clue > say so!)
Click to expand...
Click to collapse
Does it work if you add
write /sys/android_touch/event_google 1
to the init.rc file?
Could you post the init.rc file where you trigger the init.d scripts?
nickiberli said:
Does it work if you add
write /sys/android_touch/event_google 1
to the init.rc file?
Could you post the init.rc file where you trigger the init.d scripts?
Click to expand...
Click to collapse
yes that should work correctly
No, I didn't add that. I'll try it tomorrow (or one of you, if you have a Linux machine ready. Laptop with Ubuntu is having some issues atm, can fix it tomorrow).
So, assuming that's working, let's get to the display. We know that it causes issues, but how?
-Logcat doesn't error (except for HtcEbdLog, saying something about rotation, which seems to happen when glitches occur. Perhaps we need to swap the files?)
-At the very beginning, it does tell that initOverlay failed. This overlay-thing is baked in the ROM, and can be disabled in the ROM itself by setting an option to 'false' in the vendor setup. We don't know if it fixes the issue, but since the attempts to add this functionality to the kernel failed, it could be a better idea to fix it in the ROM to get rid of the error.
Any other suggestions?
Edit: and before I forget, tomorrow I'll check the ZIP for what is changed in comparison with the ROM it is based upon, so we know what we have to add in to a new build too.
Chaosz-X said:
No, I didn't add that. I'll try it tomorrow (or one of you, if you have a Linux machine ready. Laptop with Ubuntu is having some issues atm, can fix it tomorrow).
So, assuming that's working, let's get to the display. We know that it causes issues, but how?
-Logcat doesn't error (except for HtcEbdLog, saying something about rotation, which seems to happen when glitches occur. Perhaps we need to swap the files?)
-At the very beginning, it does tell that initOverlay failed. This overlay-thing is baked in the ROM, and can be disabled in the ROM itself by setting an option to 'false' in the vendor setup. We don't know if it fixes the issue, but since the attempts to add this functionality to the kernel failed, it could be a better idea to fix it in the ROM to get rid of the error.
Any other suggestions?
Edit: and before I forget, tomorrow I'll check the ZIP for what is changed in comparison with the ROM it is based upon, so we know what we have to add in to a new build too.
Click to expand...
Click to collapse
u want me to add stuff to that ramdisk?
start a github repo for the ramdisk and ROM too... trust me... its VERY helpful...
I'll start installing Ubuntu within 30 minutes, and will add everything to a GitHub by tonight within about 3 hours I think.
Chaosz-X said:
I'll start installing Ubuntu within 30 minutes, and will add everything to a GitHub by tonight within about 3 hours I think.
Click to expand...
Click to collapse
thats great... it should make keeping track of changes much easier and other interested devs can contribute if they want...
Hello, all.
Attempting to help by working on the build.prop settings. I'm S-OFF with revolutionary and have my device fully configured with the Honeycomb HBOOT/radio/bootloader/etc.
After flashing the ROM and the kernel, the device would immediately reboot upon attempting to return to the main recovery menu. I had to fastboot oem rebootRUU and reflash Globatron's PG41IMG-WIFI-light-B10 zip to get recovery back.
The device never proceeded to the boot animation.
Thracks said:
Hello, all.
Attempting to help by working on the build.prop settings. I'm S-OFF with revolutionary and have my device fully configured with the Honeycomb HBOOT/radio/bootloader/etc.
After flashing the ROM and the kernel, the device would immediately reboot upon attempting to return to the main recovery menu. I had to fastboot oem rebootRUU and reflash Globatron's PG41IMG-WIFI-light-B10 zip to get recovery back.
The device never proceeded to the boot animation.
Click to expand...
Click to collapse
I can confirm this happened to me also. The only difference is that I was using the kernel for a port of mine, and it did the same thing.
Yes, it is known that for some reason, Go Back already reboots the device. It's no problem though, it works fine anyway. If it is really looping the bootanimation every ten seconds, keep Vol Down and Power pressed, until you get to HBOOT. Select FASTBOOT, and enter 'fastboot erase cache' in the terminal. Then reboot on the device, and it should boot up fine.
Also, kernel won't work on Honeycomb, haven't checked why it doesn't though (and I won't btw, our goal is not to make a new kernel for Honeycomb, but for ICS, where it does its job fine).
Kernel source is uploaded to my Github: http://github.com/Chaosz-X
Edit the CROSS_COMPILE for your toolchain, and it should compile fine (it does here).
Will add the link to the OP within 5 minutes, ramdisk will be uploaded tomorrow.
If chaos has a device tree set up for the Flyer/View, no build prop editing should be necessary, can just submit requests - but I don't notice it on the git.
Thanks for uploading, I'll have a look and see what has changed so far. It's a little difficult to keep track of the changes since there are no commits that document the patches applied over time, but I'll try to make do with what you've got.
Is this straight from flyer HC kernel source?
I may be doing this wrong, but the touch screen commands do not seem to be working for me
Cimer said:
I may be doing this wrong, but the touch screen commands do not seem to be working for me
Click to expand...
Click to collapse
You have to type it in manually. Copying and pasting does not work, at least it did not for me. I think the issue is with the '
lawguy said:
You have to type it in manually. Copying and pasting does not work, at least it did not for me. I think the issue is with the '
Click to expand...
Click to collapse
It may just be me, I tried manual too. I had to use http://forum.xda-developers.com/showthread.php?t=1379875 since I'm stuck on Windows 8..maybe something is up with that. I guess I will just need to sit and wait =/
Cimer said:
It may just be me, I tried manual too. I had to use http://forum.xda-developers.com/showthread.php?t=1379875 since I'm stuck on Windows 8..maybe something is up with that. I guess I will just need to sit and wait =/
Click to expand...
Click to collapse
Hang tight for now. Wifi Does not work and the screen freaks out. I'm sure that these things will be fixed soon.
Going to upload ramdisk source within an hour, and try to apply a fix for WiFi, and try to fix the touchscreen by using the command in init.rc mentioned here earlier.
The new modem arrived, I have Internet again, so we have remote access to our Linux machine and can start compiling etc again
Indeed, we're grabbing AOKP source code now. Within about 2 hours we think, we'll start compiling the ROM for the HTC Flyer. Don't know if it will work out, but we have to start somewhere
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
GEEWIZ 3.4 SCH-I500 JZO54K JELLY BEAN 4.1.2 ROM/KERNEL
RETIRED -- GEEWIZ 3.4 WAS THE FINAL RELEASE OF GEEWIZ BASED ON ANDROID 4.1
OTHER AVAILABLE GEEWIZ VERSIONS:
GeeWiz 4 - AOSP Jelly Bean 4.2: http://forum.xda-developers.com/showthread.php?t=2088224
GeeWiz 3.4 is a ROM for the Samsung Fascinate, based on AOSP Jelly Bean 4.1. Like it's predecessors of the same name, GeeWiz doesn't aim to provide a lot of bells and whistles or incorporate all of the latest and greatest tweaks and enhancements developed by the community; the aim is to provide a basic, stable, functional device.
GeeWiz 3.4 uses a modified version of the GeeWiz 2.8 Gingerbread (Linux 2.6) kernel with a number of very specific tweaks/hacks in order to continue to support the proprietary Samsung RFS file system and other features I wanted to carry over. As a result, this ROM may not be used in conjunction with any other Kernel, and this Kernel cannot be used in conjunction with any other ROM. Please consider it a "matched set", and they will always be updated/distributed together. XDA community developed enhancements to the ROM or Kernel are encouraged, and will be given prominent feature status in this post.
Your device needs to be set up as stock or stock-like (e.g. GeeWiz 2.8) before installing this ROM/Kernel. If you are currently running with an MTD-based platform, the device must be reverted back to the original OEM volume format. Please refer to the forum/thread were you acquired your current ROM for guidance on how to revert the device as necessary.
Installing this ROM/Kernel or any other provided component(s) will void your device's warranty, and I cannot be held responsible for any damages of any kind (including data loss) that are incurred either directly or indirectly by these packages and components. What you do to your device is ultimately your problem!
FEATURES
Android Jelly Bean AOSP build JZO54K (android-4.1.2_r1)
Google Apps version JZO54K from the Galaxy Nexus
All devices (GPS, compass, orientation, camera, flash) are functional
Wifi (WPA/WPA2) and Bluetooth Tethering support
Supports OEM DBDATA volume to keep performance reasonable
Supports both RFS and EXT4 formatting on all volumes
OEM USB modes (CD-ROM/Kies/MTP) replaced with standard Android Mass Storage
Advanced Battery Settings: Maximum Charge, Automatic Recharge Point
Advanced CPU Settings: Maximum/Minimum Clock Speed, Governor Selection
Advanced In-Call Volume Boost Selection
Backlight Notifications built into system, controlled by the OS
Supercurio Voodoo Sound 10
Fascinate Dock audio simulates a true USB audio device for seamless output path switching
Custom Dock options - Enable BLN, Stay Awake, Enable audio output
CREDITS
While it would be impossible to remember/cite every possible reference that was used during development, I would like to specifically thank the following teams/individuals for making their work public so that others could learn from it and in more cases than not, shamelessly "borrow" it:
jt1134 - A primary source of knowledge for all things Samsung Fascinate
sgtkwol - Maintains a Linux 2.6 kernel for the Epic that provided a vast amount of reference material for the kernel updates
pawitp - Fixed my video driver changes to eliminate a 'microlag' issue (thank you!)
Entropy512- Customizations to allow WPA/WPA2 Wifi Tethering to work on the Galaxy S
teamhacksung - Maintains a large repository for all Galaxy S devices, I can't count how many code compares I did against their material
Cyanogenmod - The fact that this ROM can make a call at all is thanks to this team. So much of this effort is based on theirs!
rxwookie - A long-time supporter of all things GeeWiz and always takes the time to help other folks out here. I think he probably knows more about GeeWiz than I do!
ACTIVATION AND PROVISIONING
While I have no reason to believe that activation/provisioning wouldn't work properly on this ROM, it is a difficult thing to test on CDMA networks. Until it's been established that activation/provisioning is indeed working properly, I suggest you do not use anything like the ODIN "EFS Clear" option that may affect it. If the phone was properly provisioned before installing this ROM, it should maintain that provisioning. I have successfully activated a Fascinate on this ROM, but have not tested the process enough to be fully confident with it.
KNOWN ISSUES
USB Mass Storage / ADB may not work after device has been docked
After docking and removing the device from a Samsung Fascinate dock, USB Mass Storage and/or ADB may stop working. When this occurs, the only way to restore USB connectivity is to power off the device and power it back on. Rebooting is not sufficient and will not alleviate the problem.
FIRST-TIME INSTALLATION RECOMMENDATION
This ROM performs significantly better when the device uses the EXT4 file system. Unfortunately, using ODIN will always format the device with the RFS file system. Unlike previous versions of GeeWiz, the new "Full Wipe" ODIN package has been modified such that it will format the data volumes (DATA, DBDATA, CACHE) with the EXT4 file system on the first boot. This is now the recommended installation method for first-time installation.
If the "Full Wipe" ODIN package is not used, please note that your data must be wiped manually if coming from another ROM to avoid problems, and I strongly recommend converting, at minimum, the data volumes of the device (DATA, DBDATA, CACHE) to the EXT4 file system.
UPGRADING FROM GEEWIZ 3.2/3.3
GeeWiz 3.2.x/3.3.x Versions can be upgraded directly to GeeWiz 3.4 without a need to wipe the device data or revert the file system back to RFS. The EDIFY update-zip below is compatible with most, if not all, recoveries and will work regardless of if the device is formatted with RFS or EXT4.
Your Dalvik-cache will be automatically wiped, so the first reboot will take a long time
Due to problems with some Google services after a kernel change, the Google Services Framework package will have its data cleared during installation. You will be prompted to accept Google's location services again
DOWNLOADS
EDIFY Update-Zip (ClockworkMod / GeeWiz Recovery) Compatible Downloads
GeeWiz 3.4 ROM/Kernel (EDIFY Update-Zip)
http://www.mediafire.com/file/ascgikdaqdg3ai5/geewiz-3.4-syskernel-01122013.zip
MD5: 6b2e280f9d51492febec43b8b9fa3bd4
GeeWiz 2.8 Recovery (EDIFY Update-Zip)
http://www.mediafire.com/file/5fxee76vrxv28eq/geewiz-2.8-recovery-04162012.zip
MD5: 9869d3138279d99f1237a442f7573cad
ODIN Compatible Downloads
GeeWiz 3.4 ROM/Kernel/Modem/Recovery/Data Wipe Full Update (ODIN)
This will delete all user data from your device, replace your RECOVERY with GeeWiz Recovery as well as replace your modem with the EH03 revision. Your data volumes will be formatted with EXT4 on the first boot
http://www.mediafire.com/file/2266vgo7uma5xmk/geewiz-3.4-fullwipe-01122013.tar.md5
MD5: 0d6c2cf955d0024c925c2d10ce046e1d
GeeWiz 3.4 ROM/Kernel (ODIN)
http://www.mediafire.com/file/jzfwybqu6ns70ay/geewiz-3.4-syskernel-01122013.tar.md5
MD5: 46e17141a8f8a8ae48001c3e4653e088
GeeWiz 2.8 Recovery (ODIN)
http://www.mediafire.com/file/h5gov2c1r8836tj/geewiz-2.8-recovery-04162012.tar.md5
MD5: b70d4063dffaa9cd89629f307d3beae5
SOURCE CODEThe entire baseline for GeeWiz is available on github: https://www.github.com/djp952.
Device repo: android-platform-device-samsung-atlas3g (branch android-4.1.2_r1)
Kernel repo: android-kernel-atlas (branch android-4.1.2_r1)
Please see post #2 of this thread for an overview of how to build the GeeWiz ROM/Kernel from source as well as how to package your modifications. I would be happy to include any XDA community developed modifications or enhancements to the baseline as featured packages, add-ons or patches for GeeWiz!
Disclaimer: djp952 reserves the right to mercilessly kang your changes and assimilate them when you fix things that he was unable to. djp952 will also give you *major* props and full credit for the fix, so it's not that bad, right?
HOW TO BUILD THE GEEWIZ 3 ROM AND KERNEL
A common request I've gotten is how to build either the GeeWiz ROM or kernel from source. I think GeeWiz 3 is a little less intimidating as a first step for getting into AOSP builds since it doesn't stray too far from the Android baseline, and the kernel is based on Samsung's stock model for the device rather than the enhanced MTD model. Whatever the reason, I'm happy to try and describe how I build these components and generate the packages that I post for the community. Sometimes it's normal, sometimes it's a bit wonky, but as long as I don't miss anything important it should be a workable process for anyone that would like to get into building custom Android builds.
I think GeeWiz 3 would be a great learning tool, it works as-is but leaves enough room for additional customizations and enhancements that it may be a better place to start than jumping into something like Cyanogenmod or AOKP as your first project. It's up to date at the moment with the latest Android code as well, so that's a definite bonus as opposed to working with something like Gingerbread where tricks you learn may not apply to the next project you take on.
BUILD ENVIRONMENT
I use Ubuntu 12.04 Desktop x64 for my Android build environment, and even though Google states that this environment is "Experimental", I've not run into any issues with it. To get started, simply follow the directions Google has provided here:
http://source.android.com/source/initializing.html
If you are running on Windows x64, I can also recommend using a Virtual Machine as your build environment. I like Oracle VirtualBox the best, but the stock Fascinate code by Samsung has major USB problems with it, you won't be able to use ADB or Heimdall. For Fascinate-specific development I recommend VMWare Player since it can work with the stock USB. Note that you need an x64 OS and a CPU with Virtualization Support to host an x64 guest OS regardless of the software you choose. The best performance and compatibility will come from installing Linux natively on your system.
DOWNLOAD GEEWIZ SOURCE TREE
Once your environment is set up, you of course need some source code. I've opted to use Google's repo tool and AOSP manifests to control the source tree, so the first thing you need is the Google repo tool. Follow the first section of this document, entitled "Installing Repo":
http://source.android.com/source/downloading.html
I have two separate "builds", or in Android terms Manifests out there. One is called DEFAULT and includes just changes to AOSP necessary to support the Fascinate. The other is called CUSTOMBUILD and adds the light OS customizations I have done. Since I never use DEFAULT and I'm not sure t even builds at the moment, we're going to use CUSTOMBUILD, or as it's called here at XDA "GeeWiz".
Open a terminal window to your home directory (~/)
mkdir android
mkdir android/platform
cd android/platform
repo init -u https://github.com/djp952/android -m custombuild.xml -b android-4.1.2_r1
What we just did was initialize the repository for AOSP, but haven't downloaded anything yet. The -u argument to repo tells it where to find the manifest XML files. In this case, my github "android" repo. The -m tells it what manifest to use. The -b tells it what branch to pull. This is important because like most folks, I have multiple branches out there. I have been indicating at the very end of the first post what the current active branch is, android-4.1.2_r1 right now.
At this point, I suggest going into the ~/android/platform/.repo/manifests directory and having a look at the manifest file. (.repo is a hidden folder). Open up custombuild.xml in GEDIT and you can see that I've taken the AOSP manifest and simply replaced portions of it to point into my own github repos for things I've changed. I'll try to include details on how I manage this below so you could do something similar if you want to.
The most time-consuming part of building Android is downloading the code. Can't go much farther without it, so get yourself a cup of coffee and a good book ...
In the terminal, at the ~/android/platform directory
repo sync
The SYNC command uses the manifest to go get all the code. Most of it is going to come from Google, but all the bits I've altered will come from my github instead. It's going to take a very long time to download.
BUILD GEEWIZ ROM
Once downloaded, we have to choose what device to build for. GeeWiz has two target devices, "atlas" and "atlas3g" (Technically, there are three as I use the same build for "toro" - VZW Galaxy Nexus). Atlas is the Wifi-only target known here as "GeeWiz Media". Atlas3G adds to that changes required to include voice/data support (mostly courtesy of Cyanogenmod!). Let's assume if you're reading this, you're interested in Atlas3G.
In the terminal, at the ~/android/platform directory
source build/envsetup.sh
lunch
The "Lunch Menu" (haha Google) will present you with a list of device builds to choose from. You can select by number, or you can type in anything not on the menu. As of this writing, the build we want is #8, full_atlas3g-userdebug. userdebug generates a generally release-quality build, but doesn't odex (pre-optimize) the APKs and has some additional debugging support you wouldn't ordinarily find. You could also type in full_atlas3g-eng for an "Engineering" build or full_atlas3g-user for a "Release" build. I think you'll prefer userdebug most of the time.
Select 8 - full_atlas3g-userdebug
make -j4 rompackage
This will kick off the build. It will take a long time the first time through. The rompackage argument is something I added to AOSP to support the Fascinate. This will build the EDIFY update-zip that I upload for everyone and use to generate the ODIN packages (more on that later). On typical Android devices, you would use otapackage (update-zip install) or updatepackage (fastboot install) instead. Fascinate is a special needs child, so it gets a special needs build process.
Once it's done, provided I didn't forget anything important here, you'll have a full ROM/Kernel package ready to be flashed via Clockworkmod or GeeWiz Recovery in the ~/android/platform/out/target/product/atlas3g folder. It will be named along the lines of full_atlas3g-rom-YYYYMMDD.HHMMSS.zip. Making a package for ODIN involves more steps, but I'll get to that. First I have to tell you how to build a modified Kernel ...
BUILDING THE GEEWIZ KERNEL
The Atlas and Atlas3G repos have a pre-compiled kernel in them that is packaged with the ROM build. This section will describe how to build and include customized versions of that kernel. First step is, of course, to get the source code. Both ROMs share a kernel but due to differences in the ramdisk (initramfs), they are built independently.
In a Terminal, at the ~/android directory
git clone https://github.com/djp952/android-kernel-atlas.git
cd android-kernel-atlas
git branch android-4.1.2_r1 remotes/origin/android-4.1.2_r1
git checkout android-4.1.2_r1
Now the build environment needs to be set up. I use the compiler provided with AOSP to build the kernel as this is how Google does it. If you are using a different compiler, or have put your AOSP tree into a different location, you may have to modify these commands slightly.
In a Terminal, at the ~/android/android-kernel-atlas directory
export ARCH=arm
export SUBARCH=arm
export CROSS_COMPILE=arm-eabi-
export PATH=~/android/platform/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin:$PATH
NOTE: From this point forward, don't close that Terminal, otherwise you will have to execute the environment export commands again.
The kernel is built in three steps. This is necessary because the Fascinate doesn't conform to Android's models and we have to include the ramdisk (initramfs) in the kernel image. The first step is to select which device you are building the kernel for, which in this case will be "atlas3g_defconfig". (The other configuration for GeeWiz Media is called "atlas_defconfig").
make atlas3g_defconfig
This initializes the kernel build for Atlas3G. Since we need to build the ramdisk as part of the kernel, the next step is to generate any loadable kernel module (.ko) files that need to be part of that ramdisk
make modules
The way I have the kernel set up, it will pull the necessary files for the ramdisk by looking at the device "initramfs.list" file, in the AOSP tree. The file that describes the atlas3g ramdisk, for example, is in ~/android/platform/device/samsung/atlas3g. If you examine this file you can see that it lists where all the files should come from, relative to the kernel source root directory. This explains why I went through how to build the AOSP tree before the kernel, the kernel depends on the AOSP build. Provided everything is in the right place, it's time to build the kernel
make
This executes the main kernel build. Should any ramdisk files be missing, it will error out early on and let you know what the problem is. Assuming everything goes well, your kernel will be in the ~/android/android-kernel-atlas/arch/arm/boot directory. It's named zImage and it's the combined kernel/ramdisk required for the Fascinate.
This zImage file can now be flashed directly to the device with Heimdall, packaged up for ODIN, etc. However in order to make it part of your AOSP build and corresponding EDIFY update-zip, we have to copy it into the AOSP tree and rebuild the ROM. It's a bit tedious, and other folks have different and more streamlined ways of accomplishing this, but this method has worked for me.
cp ~/android/android-kernel-atlas/arch/arm/boot/zImage ~/android/platform/device/samsung/atlas3g/kernel
cd ~/android/platform
source build/envsetup.sh
lunch full_atlas3g-userdebug
make installclean
make -j4 rompackage
This set of commands will clean out and rebuild your ROM package with the updated kernel.
CREATING ODIN PACKAGES
While not the most popular way for people to install your ROM, no guide would be complete without describing how to generate the ODIN-based installation packages. I like to provide a "Full Wipe" ODIN package that will take care of resetting the device while flashing the new ROM/Kernel, it's an easy way for people that are comfortable with ODIN to just completely replace the contents of their phone with your stuff. For this section, I'm going to assume that you are using GeeWiz Recovery, version 2.8 or later. Other recoveries will work, but as you may expect I'm most familiar with the one I made and I know for certain it has all the necessary features in place.
The ODIN factoryfs.rfs file must be generated by formatting the SYSTEM volume with RFS and then installing your ROM:
Copy your generated EDIFY update-zip to the SDCARD
Reboot into GeeWiz Recovery
Wipe the device data by selecting Wipe Device Data and then Wipe all User Data (Factory Reset)
Press the HOME key to return to the main menu
Format the SYSTEM volume with RFS by selecting Manage Volumes / Format Volumes / Format SYSTEM / Format SYSTEM [rfs]
Press the HOME key to return to the main menu
Select Install Update Package, and choose your EDIFY update-zip to install
After the installation is complete, reboot the phone by selecting Exit from the main menu. Not rebooting the device after the flash will result in a bad ODIN file more often than not. Trust me on this one.
After the device has fully booted, reboot it back into GeeWiz Recovery. The next step will be to generate a backup of the RFS-formatted SYSTEM volume to ultimately use with ODIN. GeeWiz Recovery can create these by choosing to execute a "raw dump" of the volume:
Select Manage Volumes / Backup Volumes / Backup SYSTEM / Backup SYSTEM [raw dump]
GeeWiz Recovery tries to keep volumes unmounted after it's done working, so the SDCARD must be mounted before the contents can be accessed with ADB:
Press the HOME key to return to the main menu
Select Manage Volumes / Mount Volumes / Mount SDCARD
GeeWiz Recovery will store the backup as /sdcard/backup/volume/SYSTEM-YYYYMMDD.img.gz, so as an example, I might pull it to my home folder with this command:
adb pull /sdcard/backup/volume/SYSTEM-20121022.img.gz ~/
The .gz file will contain a compressed copy of the backup, just open it up, extract the file, and then rename it to factoryfs.rfs. This is the SYSTEM volume for ODIN. There are also a number of other files you can include in your ODIN package to perform various other flash or wipe operations (I'll tell you where to get them, too)
boot.bin - Will replace the primary bootloader. VERY DANGEROUS to include, I strongly recommend against including it.
cache.rfs - Will wipe the CACHE volume; necessary if you want the device to boot into recovery automatically and run a command
dbdata.rfs - Will wipe the DBDATA volume
factoryfs.rfs - Will replace the SYSTEM volume
modem.bin - Will replace the CDMA modem
movinand.bin - Will wipe the DATA, PREINSTALL and FOTA volumes
param.lfs - Will replace the parameter block. Semi-dangerous to include, but required to ensure an initial boot into recovery mode
recovery.bin - Will replace the RECOVERY kernel and ramdisk
Sbl.bin - Will replace the secondary bootloader. VERY DANGEROUS to include, I strongly recommend against including it.
zImage - Will replace the BOOT kernel and ramdisk
To generate an ODIN-compatible tarball, gather the files you want to include and execute the following commands from a Terminal. Replace tarfilename.tar with the name you want to give the tarball, and replace file file file file with the names of the files from the table above you want to include:
tar --format=ustar -cf tarfilename.tar file file file file
md5sum -t tarfilename.tar >> tarfilename.tar
mv tarfilename.tar tarfilename.tar.md5
NOTE: If you rename the .TAR file, it will invalidate the MD5 checksum and you will have to md5sum it again.
OK, where to get the files. You can access a "full stock" ODIN package for the Fascinate, like the EH03 version that is available here on XDA to get copies of all the stock versions of these files. Or, you can use the ones from my ODIN "Full Wipe" package if you'd like as well. My ODIN tarball has a gimmick that you may find useful. If you include my copies of cache.rfs, param.lfs and recovery.bin, the device will initially reboot into recovery and automatically format the CACHE, DATA and DBDATA volumes with the EXT4 file system. It's a relatively simple trick, but an effective one to help improve the performance of your ROM. I also like to provide a "syskernel" tarball that includes only factoryfs.rfs and zImage. The benefit of this is that it will not wipe out any of your user's data. The downside is that the user may be responsible for going into Recovery on their own and executing any steps your EDIFY update-zip would have typically taken care of, like clearing the Dalvik-cache.
==================
For now, that pretty much sums it up! I can expand on this, or perhaps more appropriately compress it (I am a tad verbose!) based on feedback and how useful this little guide ends up being for everyone. Let me know -- PM me or post here in this thread, I'll see it either way!
reserved post
reserved 3
Downloading now. Will reply with the results soon
Just have one question though. I am on a voodoo kernel ie kgb with geewiz 2.9 rom. And I will be using the edify update method to flash the 3.2 rom. Do I need to convert the file system to ext? Or can I just flash it over the existing setup.
Thanks in advance
edit...I flashed the JB rom on the above setup. The phone is stuck at the big X logo. Doesnt seem to go beyond that. So i went back to stock froyo. Then flashed GW 2.8.1. Booted properly. Everything working fine. Next i flashed geewiz recovery & converted files to ext4. rebooted. works fine too. Flashed JB rom. Phone still stuck at the X logo.
Kindly help...
Sent from my SCH-I500 using xda app-developers app
swapnilss said:
Downloading now. Will reply with the results soon
Just have one question though. I am on a voodoo kernel ie kgb with geewiz 2.9 rom. And I will be using the edify update method to flash the 3.2 rom. Do I need to convert the file system to ext? Or can I just flash it over the existing setup.
Thanks in advance
edit...I flashed the JB rom on the above setup. The phone is stuck at the big X logo. Doesnt seem to go beyond that. So i went back to stock froyo. Then flashed GW 2.8.1. Booted properly. Everything working fine. Next i flashed geewiz recovery & converted files to ext4. rebooted. works fine too. Flashed JB rom. Phone still stuck at the X logo.
Kindly help...
Sent from my SCH-I500 using xda app-developers app
Click to expand...
Click to collapse
Let me follow those exact steps and see what happens. Mandatory silly question: did you wipe data after installing the JB rom?
Just to clarify to make sure I do the same thing, you went back to stock Froyo (ED05), not stock Gingerbread (EH03)?
It will sit at the X logo for quite some time after flashing the ROM, since it has to dalvik all the apps. "Quite some time" in this case means like 3-5 minutes though. It does take much longer than Gingerbread to do this, but it's not some craziness like half an hour.
:crying:
edit: If I can't duplicate this, I can post a kernel update where debugging is ON by default so we could use ADB to see what it's hanging up on, but I will totally understand if you don't want to go through all that effort. Been there!
Odined back to stock. Loaded full wipe 3.2 and everything is golden. MMS, WiFi etc works great.
Did have to restart before WiFi would start. ROM is a little laggy at first but once it settles performance is on par with other JB Roms:thumbup:
Thanks Mr.GeeWiz: looks great for a "beta"
Edit: speakerphone works great also, sweet^o^
Sent from my SCH-I500 using xda app-developers app
I still think in overall the ROM is laggy.
WiFi requires restart each time you switch it off.
Whatsapp is not working after SMS code verification.
Thanks DJP952
i decided to give this a try. everything works great. wifi did not require a reboot for me. camera, mms, wifi all work great. a little sluggish getting started, but pretty stable nonetheless. great work DJ. thanks
djp952 said:
Let me follow those exact steps and see what happens. Mandatory silly question: did you wipe data after installing the JB rom?
Just to clarify to make sure I do the same thing, you went back to stock Froyo (ED05), not stock Gingerbread (EH03)?
It will sit at the X logo for quite some time after flashing the ROM, since it has to dalvik all the apps. "Quite some time" in this case means like 3-5 minutes though. It does take much longer than Gingerbread to do this, but it's not some craziness like half an hour.
:crying:
edit: If I can't duplicate this, I can post a kernel update where debugging is ON by default so we could use ADB to see what it's hanging up on, but I will totally understand if you don't want to go through all that effort. Been there!
Click to expand...
Click to collapse
Hi djp,
I forgot to mention that I have bought the handset from Reliance (mobile service provider in India ). And that puts a limitation on me as I am not able to wipe the data dalvik and cache whenever I flash my phone to a new rom. If I do the data wipe I lose my 1x/3g Connectivity and I cannot restore it (tried various options like data fix files, apn restore etc etc) unless I flash the stock rom from Reliance (EK10 Froyo. No official gb rom for India yet ). Hence whenever I flash roms I do not wipe data. But in spite of that I have never faced any problems. Infact now the number of user apps is close to 100 and I can still flash any touchwiz rom (geewiz 2.8, 2.9, tsm resurrection and 2.2 etc without any problems. I am in no way promoting my method of not wiping but I have no other choice.
With the given restrictions that I have, please advise me how and what I can do to successfully flash JB rom. Currently there are no user apps in my device so clearing dalvik should not be a problem.
Sent from my SCH-I500 using xda app-developers app
swapnilss said:
Hi djp,
I forgot to mention that I have bought the handset from Reliance (mobile service provider in India ). And that puts a limitation on me as I am not able to wipe the data dalvik and cache whenever I flash my phone to a new rom. If I do the data wipe I lose my 1x/3g Connectivity and I cannot restore it (tried various options like data fix files, apn restore etc etc) unless I flash the stock rom from Reliance (EK10 Froyo. No official gb rom for India yet ). Hence whenever I flash roms I do not wipe data. But in spite of that I have never faced any problems. Infact now the number of user apps is close to 100 and I can still flash any touchwiz rom (geewiz 2.8, 2.9, tsm resurrection and 2.2 etc without any problems. I am in no way promoting my method of not wiping but I have no other choice.
With the given restrictions that I have, please advise me how and what I can do to successfully flash JB rom. Currently there are no user apps in my device so clearing dalvik should not be a problem.
Sent from my SCH-I500 using xda app-developers app
Click to expand...
Click to collapse
Ah, I see your point. When you had problems with activation, were you wiping data using Recovery or using the "Factory Reset" option in the OS? The latter, at least the Samsung version of it, will indeed nuke your activation. However, using Recovery to do it *shouldn't* affect anything. The activation stuff is stored in some secret location that recovery doesn't affect. I honestly have no idea where it's even stored, I used to think it was on the "EFS" volume, but as it turns out it's not!
I've never spent any real time trying to figure out a more surgical way to wipe data other than nuking the DATA and DBDATA partitions completely. Unfortunately, I don't really have the necessary knowledge to be able to do it any other way. While I'm relatively confident that wiping data through Recovery won't hurt, of course I cannot be 100% certain of that.
I apologize that I don't know enough about the non-Verizon models to be more confident in a recommendation for you. From what I know of the SCH-I500 CDMA, wiping outside of the Samsung OS, changing the modem version, or using the evil "EFS Clear" option in ODIN has never affected activation for me.
Sorry sir. Without a wipe, this one's not going to work. Just too far removed from the stock ROMs.
I can duplicate the Wifi issue and am looking into it. For me, it just took a REALLY long time for it to turn on, like 10 minutes. I think I know what I've done that might cause this and hope to fix it Getting the logs now.
edit: I think I see what the problem is, not sure why it hasn't been an issue with the "Media" version. I have to dynamically load and unload the Wifi driver to prevent bad things from happening, this isn't the usual way it's done. The OS is set up to start the Wifi "supplicant" automatically, when it probably shouldn't be. The supplicant can't load if the wifi driver isn't up yet. Sometimes it works, sometimes it doesn't, and when it doesn't Wifi will be hosed until the OS sorts it out. I have two solutions to try, the first is to see how Android behaves if I don't allow the supplicant to be started as part of the "main" service class, the second is to figure out that aforementioned bad thing and do it more properly. I'll get it. Sorry for the bug
Thanks for trying this guys! I never expected it to be as good as the "big" ROMs, and I wish I could do something about it being so ungodly slow for a while. It seems to pick up and work properly after all the apps have been updated and it's had a chance to do all the Google backups and whatnot that it wants to do.
One problem I saw yesterday for the first time that you might need to watch out for ... The battery TANKED in a matter of 2 hours for some reason. It looks like Google Search went off the reservation. I've also seen "GPS Status and Toolbox" destroy the battery if you don't close it all the way (long-press HOME, then swipe it away).
Oh, one cool feature we have now ... "Take Bug Report". Check in Settings/Developer options to see it. What this does is collect all kinds of logs and information about the phone and make an e-mail out of it. The default sends it to your GMail account. It's about 3MB, but it will be nice to have something everybody can use to gather logs for problem resolution rather than asking folks to hack around in ADB. So, if you run into weirdness, you can click that button, wait a while and watch scary "shell has been granted superuser permissions" pop up a lot, and you'll ultimately end up in GMail with something you can send you me or post parts of here! Great that Google added that in an accessible way finally!!
For the folks having trouble with turning Wifi on and off, I have an experimental/test patch for you. This patch will replace the GeeWiz 3.2 kernel with an updated version that changes the ramdisk/initramfs such that the wifi services are not started until Android requests them to be started. It may affect Wifi and Bluetooth Tethering, but my testing of the change here for both showed no ill-effects:
GeeWiz 3.2.1 Wifi Patch [Experimental] [EDIFY update-zip]
REMOVED: Please use official patch in the DOWNLOADS section of the main post
NOTE: You will be asked to re-opt-into the Google Location service on the first boot, this is normal. I clear the "Google Services Framework" app on any kernel change now to avoid the well known Jelly Bean issues with losing connection to Google Services when you alter the kernel. This may have been fixed with JZO54K, but why risk it when all you have to do is click "Agree"
You may have to reboot once more after installing this to clear up the Wifi on/off problems so that the Android settings are synchronized with the changes. If after a second reboot this does not solve your problem, please let me know!
Rollback: This change can be rolled back by installing the EDIFY update-zip for GeeWiz 3.2 again on top of it without wiping data. I can also package/provide a more specific rollback that only undoes the changes if necessary.
Please let me know if this solves your Wifi issues or not, so that I can either post it as a primary patch for GeeWiz 3.2 (and GW Media 3.2) or take another crack at solving it Thanks!!!
djp952 said:
Ah, I see your point. When you had problems with activation, were you wiping data using Recovery or using the "Factory Reset" option in the OS? The latter, at least the Samsung version of it, will indeed nuke your activation. However, using Recovery to do it *shouldn't* affect anything. The activation stuff is stored in some secret location that recovery doesn't affect. I honestly have no idea where it's even stored, I used to think it was on the "EFS" volume, but as it turns out it's not!
I've never spent any real time trying to figure out a more surgical way to wipe data other than nuking the DATA and DBDATA partitions completely. Unfortunately, I don't really have the necessary knowledge to be able to do it any other way. While I'm relatively confident that wiping data through Recovery won't hurt, of course I cannot be 100% certain of that.
I apologize that I don't know enough about the non-Verizon models to be more confident in a recommendation for you. From what I know of the SCH-I500 CDMA, wiping outside of the Samsung OS, changing the modem version, or using the evil "EFS Clear" option in ODIN has never affected activation for me.
Sorry sir. Without a wipe, this one's not going to work. Just too far removed from the stock ROMs.
Click to expand...
Click to collapse
Hi!
Wiped data dalvik and cache & now I am on JellyBean. Thanks djp952. :good::good::good:
This Rom looks great and apart from the Wifi issue ( havent got time to update my phone with the patch for wifi issue as yet) which takes some time to start or sometimes just rebooted my phone altogether, everything seems to work fine. Had a problem verifying Whatsapp but used their "Verify by Call" method and now its working fine too. Battery life seems good to me as of now. Liked the inbuilt BLN.
Sadly, as i mentioned before, i lost my 1x/3g connectivity (nothing to do with this Rom) and thats Ok for a day or two till i try & figure out something to enable it again. By the way, i have always done the wipe through recovery only. Never used the factory reset option in settings menu. And that means the 1x/3g settings get wiped out the moment I wipe Data (note: wiping dalvik & cache does not affect it).
Anyways , looking forward for more developments on this rom from you.
edit... The stock gallery does not seem to show all the files available in that folder. I have 1400 plus pics in that DCIM folder and the stock gallery shows 1000 or sometimes 500 only.
QuickPic
swapnilss said:
The stock gallery does not seem to show all the files available in that folder. I have 1400 plus pics in that DCIM folder and the stock gallery shows 1000 or sometimes 500 only.
Click to expand...
Click to collapse
We are a little off topic, but... I too have had nothing but problems with the stock Gallery application... not loading at all, not showing pictures, generally being grumpy (okay, so I get that way too sometimes), etc.
Try Quickpic (http://market.android.com/details?id=com.alensw.PicFolder) , it's a free app that is a gallery replacement (ad-free too!). Just make it the default and you should be set. If, for some reason, you don't like it... Just uninstall and revert back.
As for the Jellybean ROM... too sweet! I love having an original Galaxy S with JB running on it! I get questioned all the time what phone I have, because it's running the latest Android build and doesn't look like any out there right now.
Sent from my SCH-I500 using xda app-developers app
I'll load up some huge amount of photos and have a look at Gallery. I could switch from using the Google Nexus version to the AOSP, if it shows any improvements. One bonus we could get there is that I enabled widescreen photos in the AOSP branch Didn't include it for various reasons, one I recall was that it would crash if you tried the "face detect" option.
I'll have a look -- maybe it can be fixed! I also have to download this "Whatsapp" that people are using ... never heard of it What does it do?
Thanks as always for the feedback guys! Glad it's going pretty well thus far
FYI for any aspiring developers, I've started making a "HOW TO" guide for building GeeWiz from scratch in Post #2:
http://forum.xda-developers.com/showpost.php?p=33011164&postcount=2
I've gotten as far as how to make the AOSP ROM and compile the kernel. At minimum, I need to add how to make the ODIN files as well, but maybe later. Depending on level of interest, I can go into as much as anyone wants there, short of how to make actual code changes (but I could try to help offline). I think describing how to get from source to the flashable files is a good first step, I'll see how it goes from there
DJ, you should link this on the home page of GeeWiz 2.9, so more folks can get this. Also, I think you should name it JellyWiz...
Can I ask what this is ?
AndroidGee209 said:
Can I ask what this is ?
Click to expand...
Click to collapse
JellyBean for the Fascinate, with GeeWiz recovery and kernel
---------- Post added at 03:53 PM ---------- Previous post was at 03:51 PM ----------
where can i find the compass?
CM10 Jelly Bean 4.1.2 for Samsung Wave I and II (S8500/30)
Welcome Back!
When i saw it... That speed.. That stability... I said that i need to do IT!
Continuing Development on CM10!
http://forum.xda-developers.com/showthread.php?t=1851818
,,Head'' of this project is @Rebellos . Big :good: for him. He made awesome ROM. But.. leaved it.. So i want to finish it!
This is BETA version. I'm not responding for dead devices and SD Card. YOU HAVE BEEN WARNED
What work:
MODEM ( I can see signal, can send text messeages but NO Network connection, NO calling)
and all without BUGs
Bugs:
Microphone - something with Audio. Trying to repair it.
Compass - Like in Rebellos build
Battery loading - It Work BUT: 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.
And tell me what bugs more you see
I have no IRC channel, only this thread and working Private Messeage
Big thanks to Rebellos, Oleg_k, mijoma, nbates66, anghelyi, Volk204, mikegapinski, hunktb, autra, Tigrouzen and many others..
How to install it:
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:
HTML:
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.
Be patient, first bootup will keep unresponsible on Badadroid logo for up to 5 minutes.
8. CWM Recovery starts, pick:
- install zip from sdcard
- choose zip from sdcard
- cm-10-wave-<release id>.zip
- Yes - install
9. Reboot holding the Power key
Changelog:
First the same like in Rebellos thread... http://forum.xda-developers.com/showthread.php?t=1851818
I will upload version with only working Modem
0.4 - Link soon.
- Modem ,,work" - we can send Text Messeages. Only it now
- Some change with audio codec, maybe microphone now work? I can test, please tell me.
other ported jellybeans
If there is any other ported jellybean rom(s) that has fixes on the bug(s) of this ROM, we can use their files and fix problems for this ROM, doing same thing as blue59 tutorial for porting ROMS to Wave.
Yeah? Go and try to make something on JB 4.1.2 without errors
ghoslslender124 said:
Yeah? Go and try to make something on JB 4.1.2 without errors
Click to expand...
Click to collapse
I can't make a rom because i need linux to compile and i am using a netbook (1gb RAM) (1.86GHz CPU), so i think it will take much time
But what i mean is ROMs already made by someone that are jellybean so we can copy their rom files (ex: sensor.blabla) to fix problems on current one, or if someone could compile one it even better
Actually, mosts of the issue can be solved by simply tracking and adding almost all commits done (except specific to a new android version ones) since original project changed branch.
But it's a quite boring work...
Also, i think you can directly use the ril from lasts roms with few changes, it will enable all network and battery stuff.
In my opinion an Ice Cream Sandwich or even GB (but GB is ugly) port would have more sense, but it's a quite harder work.
Tigrouzen did it for Ice Cream Sandwich and it worked quite well.