Galaxy S Froyo 2.2.1 wpa_supplicant fix - Galaxy S I9000 General

Hello guys. I know this is for Android development while what im posting should be in general section but i want to point out that on certain custom ROM like Darky ROM, when i apply Voodoo lag fix, my wifi connection on the galaxy S stopped working on WPA/WPA2 EAP.
According to a few sites, this is normal in 2.2.1 as the software itself is buggy. I dont experience this on my Motorola Droid running 2.2.1 but on galaxy s, it doesnt work.
I search in this forum but ive found no ans, so i google it. and apparently theres a bug fix for the wpa_supplicant
http://www.dead-end.info/wp-content/uploads/2010/12/wpa_supplicant_froyo_eap.gz
Download this in replace your current one in system/bin/wpa_supplicant.
Credit goes to Cova at http://www.dead-end.info/2010/12/13/samsung-galaxy-s-froyo-wpa_supplicant-fix.
All developers should replace their WPA_supplicant with these in all the 2.2.1 rom and perhaps 2.3 rom too.
Cheers! Now my galaxy S is able to connect to my home network on wpa2!

Hi,
me run Darky v.7 Rom too, and guess what ... no wifi wpa/wpa2 problems here!
so no need to install stuff like this

Yeah. Only for those who have these problem. i have the problem after i enabled voodoo. I tried reflashing clean and then apply darky rom, i dont have tht problem too. but once i enabled voodoo, the problem came. Ures has voodoo on?

yep voodoo enabled! even on /system

Just for Info:
On 2.6.35 / gingerbread the kernel module bcm43XX.ko at /system/modules/ must match the kernel.
It means when you compile a kernel, you've to use the bcm kernel module which will be compiled with these kernel. Otherwise Wifi won't work at all.
It's not possible to flash another kernel without replacing the module.

Hi
Running darkys 8.0 rom and it's not working on the WPA/WPA2 EAP at work. Tried your file change but it did nothing ..

codeworkx said:
Just for Info:
On 2.6.35 / gingerbread the kernel module bcm43XX.ko at /system/modules/ must match the kernel.
It means when you compile a kernel, you've to use the bcm kernel module which will be compiled with these kernel. Otherwise Wifi won't work at all.
It's not possible to flash another kernel without replacing the module.
Click to expand...
Click to collapse
Good info to know.
Thanks codeworkx

Your File is Not Working Here is Working file with how to do it
http://www.emoiz.com/how-to-connect-samsung-galaxy-s-to-ad-hoc-wifi-network

this worked 100%
you neet to root the phone and use root explorer to acces it, replace the file with the new one, good as new

but this files still doesn't work with WPA-EAP access points

On xwjv1, no need this, as I can connect to most wifi network...
Sent from my GT-I9000 using XDA App

Related

[ROMs][GPL] Tenzo's Stock "Plain" HTC 2.1 ROMs - 2.37.605.4 w/JulyOTA [10-01-10]

[ROMs][GPL] Tenzo's Stock "Plain" HTC 2.1 ROMs - 2.37.605.4 w/JulyOTA [10-01-10]
Many of my recent efforts have lead me to take a few steps back in discovering a few things (does that makes sense?). In working on fixes for 3GP Vanilla MMS and the 50% TWS "issue" I have put these together.
Should hopefully help others, especially those new to cooking that want an easy, trouble free base to start with (no "extra fonts" and no "updating" the JulyOTA manually).
EDIT: if you have "issues" with either wired or wireless tether, you can use the apk's attached below. (thanks Conap, bugger561, and T2Noob)
I have built all of these ROMs from the RUU and integrated the JulyOTA. All ROMs are deodexed. Information below:
ROMs built with dsixda's 0.97 Android Kitchen
---------------------------------------------------------------------------
Tenzo-Official2.1-JulyOTA.zip (95.22 MB)
http://www.multiupload.com/UTESX66PBP
md5 - F3047E1D78251A4150367F5265F57457
sha1 - CFDF4720B44F8CB23B3B2489C6CC9EE594D7BC04
Tenzo-Official2.1-JulyOTA.zip
Stock ROM built from RUU
JulyOTA Update applied
ROM Deodexed
Removed System Updates (systemupdater.apk)
Added adb/debug capabilities on by default
Will not update radio, recovery or bootloader
NO ROOT OR ANY EXTRAS
---------------------------------------------------------------------------
Tenzo-Official2.1-JulyOTA-Root.zip (97.01 MB)
http://www.multiupload.com/776C431YTM
md5 - 7241DEB69057FD5E4C857E0A7C621FBA
sha1 - 9AF1C84258C6E30D46E1F69D806BFDC313DDD6B7
Tenzo-Official2.1-JulyOTA-Root.zip
Stock ROM built from RUU
JulyOTA Update applied
ROM Deodexed
Removed System Updates (systemupdater.apk)
Added adb/debug capabilities on by default
Will not update radio, recovery or bootloader
v5 cfs kernel
root (ChainsDD 2.3.6.1)
busybox
wired tether
wireless tether
Changed CPU govenor to "ondemand" (Kernel defaults to "performance")
---------------------------------------------------------------------------
Tenzo-Official2.1-JulyOTA-A2SD.zip (100.17 MB)
http://www.multiupload.com/73RVCD8IWI
md5 - 60FDE63FF4B55266F0321106D6A564DE
sha1 - AE279F1BB88F118B96F4FC03B29C8398516004B8
Tenzo-Official2.1-JulyOTA-A2SD.zip
Stock ROM built from RUU
JulyOTA Update applied
ROM Deodexed
Removed System Updates (systemupdater.apk)
Added adb/debug capabilities on by default
Will not update radio, recovery or bootloader
v5 cfs kernel
root (ChainsDD 2.3.6.1)
busybox
wired tether
wireless tether
Changed CPU govenor to "ondemand" (Kernel defaults to "performance")
A2SD 2.7.5.1 (non busybox run-parts method)
---------------------------------------------------------------------------
Tenzo-Official2.1-Cache.zip (100.17 MB)
http://www.multiupload.com/6AB22H8PQ3
md5 - C9F54A0A5454931C2BB3DEE41B53FD51
sha1 - 0904B696C38A54B1A68557F7DA68A5031026E837
Tenzo-Official2.1-Cache.zip
Stock ROM built from RUU
JulyOTA Update applied
ROM Deodexed
Removed System Updates (systemupdater.apk)
Added adb/debug capabilities on by default
Will not update radio, recovery or bootloader
v5 cfs kernel
root (ChainsDD 2.3.6.1)
busybox
wired tether
wireless tether
Changed CPU govenor to "ondemand" (Kernel defaults to "performance")
A2SD 2.7.5.1 (non busybox run-parts method)
Cache2Cache enabled (Over 150MB+ of Internal Storage)
---------------------------------------------------------------------------
No Spareparts or DevTools!!! Use attachments below if you want/need these.
---------------------------------------------------------------------------
Acknowledgments / Thanks:
dsixda - Android Kitchen - http://forum.xda-developers.com/showthread.php?t=633246
tkirton - Apps2SD - http://forum.xda-developers.com/showthread.php?t=715116
Conap and decad3nce - CFS Kernel - http://forum.xda-developers.com/showthread.php?t=774211
Please donate to one of the Dev's above. Seriously, if it wasn't for them, your phone would suck
10/01/10
Added Cache2Cache Version
Added WiredTether v1.4 (to attached downloads)
09/27/10
Initial Uploads
I just flashed this and now I am having troubles getting wi-fi to work. Whenever I try to enable it, I get an error saying "Unable to start wi-fi". I wasn't having any problems previously with any roms and I just did a full wipe from KaosFroyo V35. Any ideas?
-Allen
THIS HAS BEEN FIXED... SO PLEASE IGNORE THIS POST (UNLESS OF COURSE YOU DL'ED BEFORE I FIXED THE LINKS)
homaygfresh2000 said:
I just flashed this and now I am having troubles getting wi-fi to work. Whenever I try to enable it, I get an error saying "Unable to start wi-fi". I wasn't having any problems previously with any roms and I just did a full wipe from KaosFroyo V35. Any ideas?
-Allen
Click to expand...
Click to collapse
which ROM?
----------------------
crap... it was either the A2SD or ROOT version, yes? my goof... pulling links... will be back up soon
if you don't want to wait/reflash... unzip the attachment and put them in androidsdk\tools folder...
then:
adb remount
adb push tun.ko /system/lib/modules
adb push wlan.ko /system/lib/modules
------------------------------------------
SORRY BOUT THAT!!!
I have the same problem on Tenzo-Official2.1-JulyOTA-Root.
Why don't you just flash PlainJaneT2 which is total Stock with A2sd, and are able to enable JIT through a2sd with By typing "a2sd jit"
Everything works, on it is pretty fast for a HTC rom.
http://forum.xda-developers.com/showthread.php?t=718092
Just wondering Why you made another rom thats already out there...
I didn't mean to take over the thread just curious what the difference between PlainJane and this.
Another question is if you tested wired tether?
Because if you just dropped it in the rom I CAN GUARANTEE that it is not working, thats why I didn't add it to the rom, And If you did get it to work can you tell me how you did it?
If you included SETCPU i suggest you take it off if you don't want to have problems with the SETCPU developer later in the future..... A Member has been kicked because he included apps that developers had told him to get rid of.
This has the newest build of 2.1 by HTC. And wired tether has been updated to work on the Eris and incredible. Plainjane, even though it is older than this and T2 is still better for those who do jot care about JIT or A2SD. I've tried both as well as this and jcase's Rom features the most free memory. I uninstall a lot of stock apps and then add maybe 25-30mb of market apps. Plainjane left new with 95+mb free. This and T2 leave me with roughly 70mb.
bugger561 said:
I have the same problem on Tenzo-Official2.1-JulyOTA-Root.
Click to expand...
Click to collapse
you can do the same thing posted above
t2noob said:
Why don't you just flash PlainJaneT2 which is total Stock with A2sd, and are able to enable JIT through a2sd with By typing "a2sd jit"
Everything works, on it is pretty fast for a HTC rom.
http://forum.xda-developers.com/showthread.php?t=718092
Just wondering Why you made another rom thats already out there...
I didn't mean to take over the thread just curious what the difference between PlainJane and this.
Another question is if you tested wired tether?
Because if you just dropped it in the rom I CAN GUARANTEE that it is not working, thats why I didn't add it to the rom, And If you did get it to work can you tell me how you did it?
If you included SETCPU i suggest you take it off if you don't want to have problems with the SETCPU developer later in the future..... A Member has been kicked because he included apps that developers had told him to get rid of.
Click to expand...
Click to collapse
hmmm
this is completely stock... no extra scripts, no extra fonts, no a2sd, etc. it's stock... with july OTA integrated and deodexed. that's all i did. can you point out where the other completely stock ROM with JulyOTA integrated is? If i missed it, i apologize. again... other than not trashing bootloader, recovery, etc, it's as "stock" as it gets. no symlinks changed in update-script, etc. again, this is the only stock ROM w/July OTA integrated that i've seen on the forum. did i miss something? (Official Obsession is close... but that requires you flash over the update. not easy for beginning cooks trying to customize a ROM... and it's not deodexed)
the "other" 2 ROMs are different as well... one is almost stock, with just latest ChainsDD superuser (root) added (no a2sd), with Conap's CFS kernel. the other is the same, with latest a2sd added (which allows the ability to add cache2cache as well).
i've enjoyed PlainJaneT2... and it is still my base for TT2.1. i've given full props to you with links and request even for donations in that thread. if i've upset you, again, i apologize.
also, no "extra" apps (setcpu, etc) are included... i know the rules
i'm not trying to "ruin" any experience for anyone... or step on anyone's toes. i'm just trying to help out and contribute. certainly have never tried to upset anyone on this forum EVER!
bugger561 said:
This has the newest build of 2.1 by HTC. And wired tether has been updated to work on the Eris and incredible. Plainjane, even though it is older than this and T2 is still better for those who do jot care about JIT or A2SD. I've tried both as well as this and jcase's Rom features the most free memory. I uninstall a lot of stock apps and then add maybe 25-30mb of market apps. Plainjane left new with 95+mb free. This and T2 leave me with roughly 70mb.
Click to expand...
Click to collapse
one thing you can do with a2sd 2.7.5.1 is run the cache on the cache partition.
adb remount
adb shell
a2sd cachepart
when it's done, it will reboot the ROM. pull the battery and clear dalvik (or else you'll get a few FC's when you reboot).
you can try the above with "a2sd cachepartreset" and it "should" clear dalvik for you... but it hasn't worked well for me
t2noob said:
Another question is if you tested wired tether?
Because if you just dropped it in the rom I CAN GUARANTEE that it is not working, thats why I didn't add it to the rom, And If you did get it to work can you tell me how you did it?
Click to expand...
Click to collapse
There was a version of wired tether put up here on xda somewhere that did work with our phones....
Conap said:
There was a version of wired tether put up here on xda somewhere that did work with our phones....
Click to expand...
Click to collapse
added to first post big thanks (as always) Conap!
tenzomonk said:
added to first post big thanks (as always) Conap!
Click to expand...
Click to collapse
The official wired tether 1.4 integrated the fix for our phone. So the latest from the official site will work.
bugger561 said:
The official wired tether 1.4 integrated the fix for our phone. So the latest from the official site will work.
Click to expand...
Click to collapse
good to know thanks......
Hey, I pasted those two files into the correct directory using rootexplorer. I've done it twice now and rebooted, WiFi is still not working.
bugger561 said:
Hey, I pasted those two files into the correct directory using rootexplorer. I've done it twice now and rebooted, WiFi is still not working.
Click to expand...
Click to collapse
try the "new" DL and just flash over (no wipe should be needed). what does it say your "kernel" is under software info?
t2noob said:
Another question is if you tested wired tether?
Because if you just dropped it in the rom I CAN GUARANTEE that it is not working, thats why I didn't add it to the rom, And If you did get it to work can you tell me how you did it?
If you included SETCPU i suggest you take it off if you don't want to have problems with the SETCPU developer later in the future..... A Member has been kicked because he included apps that developers had told him to get rid of.
Click to expand...
Click to collapse
Conap said:
There was a version of wired tether put up here on xda somewhere that did work with our phones....
Click to expand...
Click to collapse
In here, the version that was taken from the EVO guys:
http://forum.xda-developers.com/showpost.php?p=7666883&postcount=12
tenzomonk said:
try the "new" DL and just flash over (no wipe should be needed). what does it say your "kernel" is under software info?
Click to expand...
Click to collapse
I have Conap's CFS #5
sickbox said:
In here, the version that was taken from the EVO guys:
http://forum.xda-developers.com/showpost.php?p=7666883&postcount=12
Click to expand...
Click to collapse
Why use this old 1.2 when the official 1.4 does it cleaner: http://code.google.com/p/android-wired-tether/
Perfect timing on this! My lady is techologically challenged and having a ROM like this is perfect. She kept busting my bawls about not having teeter... Every time I installed it via an APK it would always FC after a bit.
Edit this was on a different rom, so far only issue I've had with this rom is a FC when trying to auto-update google maps.
tenzomonk said:
you can do the same thing posted above
hmmm
this is completely stock... no extra scripts, no extra fonts, no a2sd, etc. it's stock... with july OTA integrated and deodexed. that's all i did. can you point out where the other completely stock ROM with JulyOTA integrated is? If i missed it, i apologize. again... other than not trashing bootloader, recovery, etc, it's as "stock" as it gets. no symlinks changed in update-script, etc. again, this is the only stock ROM w/July OTA integrated that i've seen on the forum. did i miss something? (Official Obsession is close... but that requires you flash over the update. not easy for beginning cooks trying to customize a ROM... and it's not deodexed)
the "other" 2 ROMs are different as well... one is almost stock, with just latest ChainsDD superuser (root) added (no a2sd), with Conap's CFS kernel. the other is the same, with latest a2sd added (which allows the ability to add cache2cache as well).
i've enjoyed PlainJaneT2... and it is still my base for TT2.1. i've given full props to you with links and request even for donations in that thread. if i've upset you, again, i apologize.
also, no "extra" apps (setcpu, etc) are included... i know the rules
i'm not trying to "ruin" any experience for anyone... or step on anyone's toes. i'm just trying to help out and contribute. certainly have never tried to upset anyone on this forum EVER!
Click to expand...
Click to collapse
Like I said I was just asking and playing devils advocate I was gone for a month a half so I have no Idea of what happened I'm just catching up. Take no offense to what I said I was just curious.
first post updated w/new Cache2Cache version

[ROM][TEST] Cyanogenmod 6.1.1 [Deodex-Sign-Zipalign-A2SD]

Howdy.
I think I may have a Cyanogenmod 6.1 Ver ready, but the updater-script needs some updating (I think).
Based on Neopeeks rom, made with the ROM kitchen.
Download link:
http://dl.dropbox.com/u/31118/cm611-u8800test-wk.zip
Don't have a U8800 myself, need someone to test it.
If some more experienced dev could take a look at it i'd appreciate that.
However it should be ready for flashing.
(I don't have a U8800 myself, so I can't test it.)
Thanks for your work ,thought I can't download due to my network
Sent from my u8800 using XDA App
This is for HTC bravo? I think someone allready tried and it didnt work...
Otherwise, got installation aborted...
sanpsa said:
This is for HTC bravo? I think someone allready tried and it didnt work...
Otherwise, got installation aborted...
Click to expand...
Click to collapse
Yes, using bravo as base, but it shouldn't matter, kernel is from U8800 along with drivers.
it seems that the rom is not match with the u8800.
298800577 said:
it seems that the rom is not match with the u8800.
Click to expand...
Click to collapse
could u share more of ur experience with this rom?
What exactly have you changed with this rom? Why did you choose the Desire rom? First up you need a new /system/build.prop then you need to edit the /META-INF/com/google/android/updater-script.orig file so it flashes stuff to the right locations. Then you need to change the ro.product.device so it matches the build.prop file. Then to top it off the bravo uses the MTD partitioning scheme but the u8800 uses the EMMC partitioning scheme. So to put it simply, the rom will not work without many changes.
Yeah it also seems to have modules built for 2.6.35.9 (including a bcm4329 driver whereas this phone uses a Qualcomm RF chip, I believe WCN1312).
atleast some work is going On
Updated the ROM, should work now- Can anyone test?
Doesnt work...
anyone checked? i ve recovery problem i cant apply this rom right now
The update script needs work

Possible Wi-Fi fix for ROMs with incompatible kernels?

For example I want to use GingerDX + FXP028 OC Kernel, but Wi-Fi is not working! As I understand we need to replace wifi driver, that is located in /system/lib/modules/tiwlan_drv.ko If you have FXP028, please post this module.
But I don't know if sdio.ko is needed to. This can be usefull to many people.
Here is all three files from /system/lib/modules
dbts25 said:
Here is all three files from /system/lib/modules
Click to expand...
Click to collapse
Thank you very much, but can you give me FXP028 OC Kernel? The HotFile link is broken.
dbts25 said:
Here is all three files from /system/lib/modules
Click to expand...
Click to collapse
I paste the files in system/llb/modules but i still get wifi error
FXP have wifi drivers inside kernel AFIK, I`m not sure that placing modules can give us anything.
rav3n_pl said:
FXP have wifi drivers inside kernel AFIK, I`m not sure that placing modules can give us anything.
Click to expand...
Click to collapse
You got it wrong... Example I use GingerDX and I WANT to use FXP kernel, but wifi is not working. That's the only reason, I don't use FXP kernel with GingerDX. You can easily fix wifi by replacing modules that are in ROM not kernel.
FXP ROM
velnens123 said:
You got it wrong... Example I use GingerDX and I WANT to use FXP kernel, but wifi is not working. That's the only reason, I don't use FXP kernel with GingerDX. You can easily fix wifi by replacing modules that are in ROM not kernel.
Click to expand...
Click to collapse
Actually, on FXP init.d there's a cpmodules which load the three wi-fi files from the kernel to the system/lib/modules from the rom. Also, there's a modules folder with the exact same files, and two other init.d config files related to wi-fi.
I've tried to copy files from inside the kernel to their correct location within the ROM, set all the permissions, but I was not able to have wi-fi on FXP/GDX combo, which is really a shame.
if you can fix it, please share.
Also, if I made an incorrect statement here, please forgive me as I am a noob.
ok I have to enter at least 10 characters....
edit: decided to wright something anyway I think the "things" in modules folder are libraries not drivers (btw the image is from developer.android.com) and all the drivers are in the kernel (according to...) and all the problems come from kernel...FXP said that they figured out what the problem was in their kernel but didn't share it...I guess it's in the gutlib account...anyway I ain't no dev so don't mind me

[Q] Instructions on HowTo Port existing ROM?

Hello!
Since there is a fully working CM7 for Bravo (thanks Quarkx), does anyone know how can I port an existing ROM from Defy (example: WhiteRabbit 1.3 which is based on CM7)?
Anyways, here is the link of TweetyPeety's ROM: WhiteRabbit 1.3
http://forum.xda-developers.com/showthread.php?t=1510063
Thanks!
When I port Defy roms, I start by replacing the radio files with the ones that BravoMotorola posted in an earlier thread, adding in Quarx's camera libraries, editing media_profiles.xml, and editing the build.prop. There are a few apps included with some Defy roms, like Torch and Rom Updater, that are completely incompatible with the Bravo, and they need to be removed (or never used...).
I've attached a CWM compatible zip that removes the Defy radio, Defy camera libraries, Torch, Rom Updater, media_profiles.xml, and build.prop and replaces them with BravoMotorola's radio, Quarx's camera libraries, updated media_profiles.xml, and a CM72 compatible build.prop. I've tested this with various Quarx, Epsylon3, and Maniac103 CM7 nightlies and always had success.
If you want to use this for other Defy roms (not CM7 based) either remove or edit the build.prop accordingly and check\modify the updater-script to ensure it's compatible with the rom you want to use. By modify the updater-script, I mean to either add or remove apk's or libraries your custom rom may or may not have.
The libraries included are for Gingerbread roms and won't work on Froyo or ICS. Don't bother trying cause you'll bootloop at best, flash the sbf at worst. If anyone is interested, I can make a similar patch for Froyo roms, and an ICS patch for radio and apn settings. And don't bother asking about ICS camera, I've tried many, many, many library combos and no camera or bootloop. Your best bet on ICS camera is to donate to Quarx.
Install the included zip AFTER installing your rom.
Good luck on your Defy rom porting.
Newbery ryViewse
I've been using the White Rabbit 1.3 rom for the past 6 hours or so and have really been enjoying it. It does have a few issues though. The apn settings for att are incorrect so it won't connect (same as CM9) and I can't get usb tethering to work at all. At first, the phone recognizes usb as being connected, then when you enable, it instantly disables and the phone will bootloop every 5 minutes or so. Not really bootloop, but it does reset to the boot screen. It really sucks because this is a good rom I'd like to use but usb tethering is a must for me. Other than the tethering issue, this seemed to be stable rom and its worth trying it out.
I've included a patch to fix the camera, apn problems, and an edited build.prop. Install the rom as usuall, reboot to change to 2nd_boot, go to recovery and install the bravopatch-whiterabbit1.3.zip.
Does anybody know which program controls usb tethering? I suspect usb.apk but I'm not sure. Since I haven't had any problems whatsoever with Epsylon3's 20120212 nightly, I'll try using it's usb.apk and hope it works.
I tried upb.apk and usbd from 20120212 with no success, but it did stop the bootloop issue. I also noticed that this rom was based on KANG 20.02. I've never used or ported a KANG rom, so maybe the tethering issue is kang specific? I'll flash a kang rom tomorrow to check.
full
skeevy420 said:
I've been using the White Rabbit 1.3 rom for the past 6 hours or so and have really been enjoying it. It does have a few issues though. The apn settings for att are incorrect so it won't connect (same as CM9) and I can't get usb tethering to work at all. At first, the phone recognizes usb as being connected, then when you enable, it instantly disables and the phone will bootloop every 5 minutes or so. Not really bootloop, but it does reset to the boot screen. It really sucks because this is a good rom I'd like to use but usb tethering is a must for me. Other than the tethering issue, this seemed to be stable rom and its worth trying it out.
I've included a patch to fix the camera, apn problems, and an edited build.prop. Install the rom as usuall, reboot to change to 2nd_boot, go to recovery and install the bravopatch-whiterabbit1.3.zip.
Does anybody know which program controls usb tethering? I suspect usb.apk but I'm not sure. Since I haven't had any problems whatsoever with Epsylon3's 20120212 nightly, I'll try using it's usb.apk and hope it works.
I tried upb.apk and usbd from 20120212 with no success, but it did stop the bootloop issue. I also noticed that this rom was based on KANG 20.02. I've never used or ported a KANG rom, so maybe the tethering issue is kang specific? I'll flash a kang rom tomorrow to check.
Click to expand...
Click to collapse
work full..
Edit
3g and Usb Tethering don't work. My apologies on that. I only use wifi and 3g only when necessary. Data plans suck. Calls work with good signal, not sure about texting, don't really text much.
It's fully working if you don't require usb tethering . The touchscreen in the installer is sometimes unresponsive when pressing the next and previous buttons, but the menu key works as next and back as back. No other issues with the installer. While it may have been wifi and running a lot of crap in a short time as a basic stress test, I thought the battery drained faster than usual.
The rom is worth checking out. I really like its theme and set up more than anything.
Just tried your patch, yet it I get the bad zip, and aborts... any ideas?
Sent from my MB525 using XDA
ianstump said:
Just tried your patch, yet it I get the bad zip, and aborts... any ideas?
Sent from my MB525 using XDA
Click to expand...
Click to collapse
After typing all of the below, I realized I for got to ask--Did you enable signature verification by accident or have a bad download? I've been using the cm72 patch since the day Quarx released a proper bravo rom and haven't ever had a bad zip error, and the white rabbit patch is identical to the cm72 patch other than the build.prop and apns-conf.xml. I'm not sure if it matters, but I've only used the wr patch with the recovery from epyslon3's latest cm72 nightly 0212.
If its the patch for white rabbit, remove the build.prop from the patch and remove the line
"/system/build.prop"); from /META-INF/com/google/android/updater-script. We probably had conflicting installer options. Once you reboot after updating both zips, make sure to boot into 2nd boot like the installer says...although 2nd init booted it up just fine after the initial post-install bootloop last night for me.
You'll also need to edit the build.prop for the camera and device settings with the ones I included. You also need to make sure do delete strings for flash under OLD Tags as well.
I have a habit of editing the build.prop manually before flashing a new rom, and the one in the patch was also the build.prop in the white rabbit rom, both times I installed it.
#///////////////////////////////////////////////
#OLD Tags///////////////////////////////////////
ro.media.capture.maxres=3m
ro.media.capture.classification=classA
ro.workaround.noautofocus=0
#///////////////////////////////////////////////
#[Product Tags]/////////////////////////////////
ro.product.model=MB520
ro.product.brand=MOTO
ro.product.name=MB520_KOBE
ro.product.device=umts_kobe
ro.product.board=kobe
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Motorola
ro.product.locale.language=en
ro.product.locale.region=US
ro.board.platform=omap3
#///////////////////////////////////////////////
#[Build Tags]///////////////////////////////////
ro.build.product=umts_kobe
ro.build.description=umts_kobe_emara-user 2.3.4 4.5.1-134_DFP-74 1313117579 release-keys
ro.build.fingerprint=MOTO/MB520_KOBE/umts_kobe:2.3.4/4.5.1-134_DFP-74/1313117579:user/release-keys
ro.cm.device=kobe
Tried out latest KANG cherry pick today and its usb tethering works, 3g doesn't however. Tried multiple basebands and replacing radio with no luck. The att apn wasn't correct, and fixing didn't help.
Also, the 3g on White Rabbit doesn't work either. Anybody here port a defy cm7 after 0212? Other than these two I really haven't, and I'm wondering if newer defy cm7's are bravo incompatible, glithcy, or just that the KANG cherry picks don't like us.
I've also since downloaded the White Rabbit patch from here and didn't get any zip errors. Here's how I installed if anybody's interested:
reboot recovery
select WhiteRabbitEdition-1.3.zip
English
Install Type->Custom
Rom Options->Full Wipe, Moto Defy MB525, Google Apps, ICS Standard
Tweaks Options->AGPS Version, CM7 Stock, Off, Gingerbread, Standard
Style Options->ExDialer, ADW Launcher, CM7 DSP Manager
No other changes
Exit Installer
apply bravopatch-whiterabbit1.3.zip
reboot to bootmenu
set 2nd_boot to default
reboot to bootloop
remove and insert battery
power on
enjoy
I just realized I downloaded it wrong. Working great! Thanks!
Sent from my MB520 using XDA
Does usb tethering and 3g work? I never had them working with White Rabbit. To be specific, does turning on wifi then using usb tethering work. I use my phone as a wireless nic instead of running an ethernet cable through the house to my linux box. Kinda hard to update debian with no internet.
Ugh miui Pikachu edition works before I try to make camera work then just bootloops... Darn it's such a good rom!
Sent from my MB520 using XDA App
How were you trying to make the camera work?
I've also heard good things about that rom, just haven't bothered trying it yet.
Also, the latest quarx cm7 nightly is pretty stable. Using it now... my earlier cm7 patch works, but a new line in build.prop is needed and the apn-conf.xml from the white rabbit patch is required unless you like setting up the apn each time. Actually, I've had to change\fix the apn-conf.xml for every cm7 nightly after epsylon3's feb 12 nightly. epsylon3's feb 12 nightly is a real good rom to use if you want a good defy rom to use. I used it as my primary rom till quarx's latest 7 and I'm switching to epsylon's tomorrow.
add to build.prop under #Default Network Type
ro.telephony.ril_class=motow3g
skeevy420 said:
How were you trying to make the camera work?
I've also heard good things about that rom, just haven't bothered trying it yet.
Also, the latest quarx cm7 nightly is pretty stable. Using it now... my earlier cm7 patch works, but a new line in build.prop is needed and the apn-conf.xml from the white rabbit patch is required unless you like setting up the apn each time. Actually, I've had to change\fix the apn-conf.xml for every cm7 nightly after epsylon3's feb 12 nightly. epsylon3's feb 12 nightly is a real good rom to use if you want a good defy rom to use. I used it as my primary rom till quarx's latest 7 and I'm switching to epsylon's tomorrow.
add to build.prop under #Default Network Type
ro.telephony.ril_class=motow3g
Click to expand...
Click to collapse
I tried using the CM7 patch that was posted earlier in the thread and it made it stuck at the M logo
Sent from my MB520 using XDA App
That's the problem, that patch was made for cm7 only.
The steps to PORT CAMERA ONLY to any GB ROM.
Does not work with MS2Ginger2.1
Do everything preflash.
Open WhateverRomForDefy.zip in Archive Manager
Under system/etc, delete cameraCalFileDef5m.bin & cameraCalFileDef8m.bin, and replace mot_ise_imager_cfg.bin & media_profiles.xml from cm7 patch
Under system/lib, replace libcamera.so, libcamera_client.so, & libcameraservice.so with the same from cm7 patch.
Edit build.prop for camera like in post 7 under the OLD Tags. While the post is for WR, the camera changes are the same, & all changes are almost at bottom of build.prop. If you can read, you'll see them....
If the above doesn't work, whatever rom your trying is either
That's how I port roms normally. Again this is bare minimum camera. If that doesn't work, you\we're up the that creek with that rom in regards to the camera. FYI, I do all my rom edits with Archive Manager and GEdit\JEdit on Debian Linux. I'm not sure of the Windows alternative (7zip and Notepad++ I'd imagine) cause I haven't used Windows for anything more than SuperOneClick and other Win exclusive\non-wineable apps since XP was released....Win2K was awesome, I miss it.
skeevy420 said:
That's the problem, that patch was made for cm7 only.
The steps to PORT CAMERA ONLY to any GB ROM.
Do everything preflash.
Open WhateverRomForDefy.zip in Archive Manager
Under system/etc, delete cameraCalFileDef5m.bin & cameraCalFileDef8m.bin, and replace mot_ise_imager_cfg.bin & media_profiles.xml from cm7 patch
Under system/lib, replace libcamera.so, libcamera_client.so, & libcameraservice.so with the same from cm7 patch.
Edit build.prop for camera like in post 7 under the OLD Tags. While the post is for WR, the camera changes are the same, & all changes are almost at bottom of build.prop. If you can read, you'll see them....
If the above doesn't work, whatever rom your trying is either
That's how I port roms normally. Again this is bare minimum camera. If that doesn't work, you\we're up the that creek with that rom in regards to the camera. FYI, I do all my rom edits with Archive Manager and GEdit\JEdit on Debian Linux. I'm not sure of the Windows alternative (7zip and Notepad++ I'd imagine) cause I haven't used Windows for anything more than SuperOneClick and other Win exclusive\non-wineable apps since XP was released....Win2K was awesome, I miss it.
Click to expand...
Click to collapse
Thanks man. I will try later.
Sent from my MB520 using XDA App
Any luck? I have some free time today and can make a pikachu patch if necessary. Currently I'm trying out Idiot to port the WR framework over to Epsy's latest nightly.
Why are most of the cool Droid tools windows/dos based? You'd think there'd be more Linux tools for modding a Linux-based os.
skeevy420 said:
Any luck? I have some free time today and can make a pikachu patch if necessary. Currently I'm trying out Idiot to port the WR framework over to Epsy's latest nightly.
Why are most of the cool Droid tools windows/dos based? You'd think there'd be more Linux tools for modding a Linux-based os.
Click to expand...
Click to collapse
If you want you can me a pikachu patch. I won't have time today to try it out
Sent from my MB520 using XDA App
Got busy with MSGinger today.....I'll have a patch up sometime tomorrow.
marquae11 said:
If you want you can me a pikachu patch. I won't have time today to try it out
Sent from my MB520 using XDA App
Click to expand...
Click to collapse
Here ya go. Got busy with real life the past few days. This isn't flashable, but isn't hard to do either.
Instructions:
Open PikachuEdition2.3.2b.zip
Delete boot.img and devtree.img
Replace files under /system with the ones provided
Make sure to delete the *.jordan.so's under /system/lib/hw
Replace updater-script @ /META-INF/com/google/android/updater-script
When Installing:
Install as Defy
Don't use any Defy+ options or settings, some of them change files we just replaced.
Thanks man! You are helping us alot!

Green fuzz in camera using kernel by whitexp

I am using a GT-S5360T which is Telecom NZ version of Galaxy Y. I seem to be able to install most custom roms released for GT-S5360 fine, but. When using whitexp kernal with stock rom or latest cm7 release I have a green fuzz when accessing camera app. I see other threads with similar problem but nothing pertaining to my particular model.
I have two questions;
1. Is this because my model has the " T " at the end?
2. How can I fix this?
If some one could point me in the right direction I would greatly appreciate it.
well,
for the reason why it has that green fuzz i have exactly no idea since im not the developer of the kernel,
however,
try to use another kernel besides white's kernel,
or contact the dev or post in his kernel thread for further info
this post is approved by the national potato safety regulation
Thanks for reply. I would post there, but..
deathnotice01 said:
well,
for the reason why it has that green fuzz i have exactly no idea since im not the developer of the kernel,
however,
try to use another kernel besides white's kernel,
or contact the dev or post in his kernel thread for further info
this post is approved by the national potato safety regulation
Click to expand...
Click to collapse
I get the " you do not have permission to access this page. This could be due to one of several reasons: " screen when I try to post in the kernel thread. I think cause I'm newbie.
I like this kernel because it boots fast, it has cwm and my boot animation and power on sound play properly. Everything else seems to work with it i.e. busy box, root browser, link2sd, superuser, sys app installer and beats audio drivers and all the standard apps that don't require rooting it is just the camera.
One thing that I can say is that your "T" isnt the cause for this. T just indicates your region, its fine to install any ROM/kernel based on S5360. You might need to contact whitexp for the solution..
I will try contact White..
hitme987 said:
One thing that I can say is that your "T" isnt the cause for this. T just indicates your region, its fine to install any ROM/kernel based on S5360. You might need to contact whitexp for the solution..
Click to expand...
Click to collapse
Thanks, now I know my model isn't the problem I will try contact White... I wonder if anyone else has had the same problem or if everyone else has the same problem, I see no mention of it being a bug.
with CM7, you can have this error
But not with Strock rom ..
I only use my kernel and a lot of other people also not ..
and nobody had this problem with stock rom or custom roms like Creeds, repencis etc.;;
Stock rom & white0.8.0RC3 flashed with Odin3 V1.85
whitexp said:
with CM7, you can have this error
But not with Strock rom ..
I only use my kernel and a lot of other people also not ..
and nobody had this problem with stock rom or custom roms like Creeds, repencis etc.;;
Click to expand...
Click to collapse
Phone S/N :RV1C5OM2X1X
Model :GT-S5360T
Purchase from Telecom store in May this year.
Stock Rom is from http://forum.xda-developers.com/showthread.php?t=1714872
Perhaps you know what I might be doing wrong?
its crazy try a new app (camerazoom or other )
or a new stock rom or a custom rom ...
if no work ... flash other kernel :/
GT-S5360B
whitexp said:
its crazy try a new app (camerazoom or other )
or a new stock rom or a custom rom ...
if no work ... flash other kernel :/
Click to expand...
Click to collapse
I can get Camera to work with your kernel by flashing the PDA and MODEM pieces of the Brazil GT-S5360B firmware before flashing the white.1.3.3 in Odin.
Only problem I have then is my phone doesn't know which way is up or down unless I turn off auto rotate. Then when I flash WhiteXP the WiFi stops working.
...WiFi is fixed with the driver in WiFi fix thread..> http://forum.xda-developers.com/showthread.php?t=2027326
Screen rotation
Does any body know how to fix the problem with the screen rotation?
..

Categories

Resources