Related
It is really pissing me off that i can't get wifi to work properly when porting Dream roms over to the 32A. I have changed all drivers, a heap of wifi and init files but still nothing.....
We have rebuilt the boot image with the correct kernel, replaced wlan driver, renamed trout files etc......
Wifi will start up and find the networks nearby but will not connect to any.
Anyone have any suggestions? I am hoping there is one little file we are missing that a simple transfer of that file will get it working.....
Radix and I have tried a bit as well as a few others. He might be able to pop in and say exactly what he has done with what files (I am at work so can't remember everything i have tried to change)....
IDEAS?
****edit*** just noticed this tweet from haykuro: "rogers peeps: you may be able to flash all sorts of craziness soon. "
I have had no problem getting WiFi to work on any of the Dream-based ROMS. As long as the wlan.ko matches whatever kernel you are using (from whatever boot.img you are using) it seems to work as normal.
I'd imagine you will never have much success using a different wlan.ko and kernel combination than was compiled for.
is that with 32A or 32B? Interesting on the matching thing- i think we tried that- we used Amon_RAs kernel and wlan.ko.....
Would we have to use the entire boot image and not just the kernel?
MontAlbert said:
is that with 32A or 32B? Interesting on the matching thing- i think we tried that- we used Amon_RAs kernel and wlan.ko.....
Would we have to use the entire boot image and not just the kernel?
Click to expand...
Click to collapse
I use the entire boot.img (I know this is lazy and loses alot of the cool features of the ROM) and then the corresponding wlan.ko from whatever image the ROM came.
ok. I was trying to keep as much of the original intact as possible.....
I've tried replacing the entire boot.img - makes no difference - wifi will load, but not actually get an IP with any of the newer roms (like cyanogen's or JACxROM).
I suspect it's interacting with some of the /system/bin/ files and something has changed in that department that makes it incompatible with our kernel/wlan.ko.
I've tried replacing wpa_supplicant/wpa_cli/wlan_loader and no luck.
Hi Guys
I have tried to put together my own config files for the sapphire, these go in the vendor/htc/sapphire directory after you have extracted the source
by no means are they perfect but i hope they will start some fresh development.
http://www.cminion.com/wordpress/2009/08/11/rolling-your-own-android-rom-for-htc-magic-sapphire/
If something doesnt work, or anyone manages to perfect them let me know so I can repost.
please let me know how you get on
Nice work!
Did you try this for a 32A or 32B board?
Looks interesting... anyone tried this for 32A since 32B don't have this issue in the first place?
I have a 32b and someone is testing it with 32a but we are having trouble compiling today its been fine in the past
cminion said:
I have a 32b and someone is testing it with 32a but we are having trouble compiling today its been fine in the past
Click to expand...
Click to collapse
Well keep us updated if you get anything working for 32A since all of 32A users are stuck with the htc kerel... if you need someone else to test you can pm =D
I've been trying my best at building a kernel for 32A, but no matter what I do it doesn't boot at all.
Does anyone know how you can debug a kernel the kernel's boot process at all? I just get hangs or reboots from any of the kernels I build and I've no idea what is missing or where it's going wrong. If it gave some sort of output then I might be able to figure out what I'm doing wrong! (adb logcat doesn't kick in until AFTER it's booted unfortunately)
How have the 32b users gone with this? Anyone managed to boot one?
cminion said:
Hi Guys
I have tried to put together my own config files for the sapphire, these go in the vendor/htc/sapphire directory after you have extracted the source
by no means are they perfect but i hope they will start some fresh development.
http://www.cminion.com/wordpress/2009/08/11/rolling-your-own-android-rom-for-htc-magic-sapphire/
If something doesnt work, or anyone manages to perfect them let me know so I can repost.
please let me know how you get on
Click to expand...
Click to collapse
Hey, just saw your post and I'm taking a look. So far it's OK, but I think you're missing (at least) the keypad files. Also, a little legal note (in case you didn't know), you aren't legally able to pack the qualcomm libraries on the proprietary/ folder. Not that I really care about it, but I thought you should know since maybe you're going against xda rules by posting copyrighted files -not sure anyway-. Maybe it's better if you leave the propietary folder empty (or just with the minimal stuff like the keymaps, audioparametters and .ini files) and let the extract-files script do the job for whoever uses it to compile. After all, if someone uses this, he already has the libraries on the phone
Anyway, I'm going to compile, if I see something else missing, I'll modify accordingly and send you the changes made, ok?
Regards!
PS: Nice work
EDIT: Okay, I did some little changes on the board file definitions,renamed the folder to sapphire-open (to match dream-open added the keymaps, and a kernel & wlan.ko I had laying around (it's still compiling so maybe the kernel doesn't start, but it still needs an hour or so to end the build, but so far, it's not failing). I have packed it, you can get it here: http://rapidshare.com/files/266633357/sapphire_config.tar
If I see something else I'll repost
Hi guys,
Over at the HTC Hero forum I have been developing a kitchen to help ordinary people learn how to build their own ROM. It allows you to do basic things such as rooting a shipped ROM, adding apps2sd, modifying the task killer memory threshold, etc.
The appropriate settings are now in place to make it work for the Dream.
Here is the link to the kitchen:
http://forum.xda-developers.com/showthread.php?t=633246
Before you flash your new custom ROM made from this kitchen, please make a Nandroid backup first of your existing ROM!
Thank you, and enjoy!
Working so far on Ubuntu, figures I just learned how to use git and make my own EBI1 kernels 2 days ago, thanks for this. I'll let you know once I flash a rom how it goes.
carz12 said:
Working so far on Ubuntu, figures I just learned how to use git and make my own EBI1 kernels 2 days ago, thanks for this. I'll let you know once I flash a rom how it goes.
Click to expand...
Click to collapse
Cool, thanks. I am most concerned about how the wireless tethering option will work on the Dream because it requires a kernel fix for Android 1.5 and 1.6. The kitchen is supposed to do that automatically but it will replace your existing kernel.
BTW looks like you are from my home town of Edmonton!
It's not booting, I used my own nan sys and boot img's, set up a working directory and then rebuilt, long time at rogers screen and then boot animation for a minute then a blank back-lit screen, I'll logcat and post it later, time for work.
Is this compatible with the EBI1 dream?
dsixda said:
Cool, thanks. I am most concerned about how the wireless tethering option will work on the Dream because it requires a kernel fix for Android 1.5 and 1.6. The kitchen is supposed to do that automatically but it will replace your existing kernel.
BTW looks like you are from my home town of Edmonton!
Click to expand...
Click to collapse
I may need to go to EBI0 to test if it replaces the kernel?
carz12 said:
It's not booting, I used my own nan sys and boot img's, set up a working directory and then rebuilt, long time at rogers screen and then boot animation for a minute then a blank back-lit screen, I'll logcat and post it later, time for work.
Is this compatible with the EBI1 dream?
Click to expand...
Click to collapse
What is different about EBI1 from a kernel level? If all you did was extract the system and boot.img, and then build without modifying anything, then that should work.
EDIT: If this is a customized ROM (e.g. with custom kernel) then the update-script file under META-INF\.... may need some manual tweaking. The Option 1 in the menu is recommended only for stock ROMs, because this option creates a simple generic update-script file.
If you are indeed using a custom ROM then I'd try to get the original update.zip file of this ROM, which already has the correct update-script file. Just copy that update-script into your existing kitchen.
Or even simpler, just use the original update.zip file and run Option 11 instead of the Nandroid backup.
carz12 said:
I may need to go to EBI0 to test if it replaces the kernel?
Click to expand...
Click to collapse
I am not familiar with all the different Dreams, but it will replace the kernel if you have a 1.5 or 1.6 ROM.
It works on my rogers dream, I took the original rom for the g1, set up a working directory, replaced the launcher, took out a few apps, replaced the boot.img and wlan.ko with the ebi1 compatible versions I compiled and put in my own prop files, booted right up, thanks for this. Can't test the tethering thing as it'll change the kernel on me.
dsixda said:
I am not familiar with all the different Dreams, but it will replace the kernel if you have a 1.5 or 1.6 ROM.
Click to expand...
Click to collapse
What would happen if I just replaced the wlan.ko and boot.img-kernel in the dream_1_6_update folder with my ebi1 versions? could I test out the add wireless tether option?
carz12 said:
What would happen if I just replaced the wlan.ko and boot.img-kernel in the dream_1_6_update folder with my ebi1 versions? could I test out the add wireless tether option?
Click to expand...
Click to collapse
I'll try this tomorrow. Looks cool.
downloading now, ill let you know how things go tomorrow.
carz12 said:
What would happen if I just replaced the wlan.ko and boot.img-kernel in the dream_1_6_update folder with my ebi1 versions? could I test out the add wireless tether option?
Click to expand...
Click to collapse
I'm not sure exactly what the modified boot.img-kernel in the kitchen has, but I'm guessing it's a couple of networking-related variables that were changed. If your kernel has those modifications then maybe it will work. Doesn't hurt to try
Let me know if it works, then we can use your version for individuals who are cooking Rogers ROMs.
A question: Is it possible to tell that a ROM is for a Rogers Dream (ie. somewhere in the build.prop)? In that way, the script can automatically decide what action to take.
carz12 said:
It works on my rogers dream, I took the original rom for the g1, set up a working directory, replaced the launcher, took out a few apps, replaced the boot.img and wlan.ko with the ebi1 compatible versions I compiled and put in my own prop files, booted right up, thanks for this. Can't test the tethering thing as it'll change the kernel on me.
Click to expand...
Click to collapse
That's great news so far! Thank you
will ROMs created work with MyTouch 3G
nicknowsky said:
will ROMs created work with MyTouch 3G
Click to expand...
Click to collapse
Lets hope I am setting this up now to try it for my touch 3g
nicknowsky said:
will ROMs created work with MyTouch 3G
Click to expand...
Click to collapse
Since it's the HTC Magic, yes it should! Please try and let me know.
I'll create a thread for this in the Magic forum so that people can post their feedback there. Thank you
EDIT: Here's the thread where you can post Magic/myTouch 3G feedback:
http://forum.xda-developers.com/showthread.php?t=651470
Question...What section on the HTC site would I look for the shipped rom.exe...Specific device = Mytouch?
holmes901 said:
Question...What section on the HTC site would I look for the shipped rom.exe...Specific device = Mytouch?
Click to expand...
Click to collapse
Just do a search in XDA for Mytouch/Magic shipped ROMs. Usually there are links to the original ROMs in the Wiki page for your device.
dsixda said:
I'm not sure exactly what the modified boot.img-kernel in the kitchen has, but I'm guessing it's a couple of networking-related variables that were changed. If your kernel has those modifications then maybe it will work. Doesn't hurt to try
Let me know if it works, then we can use your version for individuals who are cooking Rogers ROMs.
A question: Is it possible to tell that a ROM is for a Rogers Dream (ie. somewhere in the build.prop)? In that way, the script can automatically decide what action to take.
Click to expand...
Click to collapse
I'll try it out tonight, the sources I used to compile were wes's and his kernel has tethering support unless I broke it, I've never used tethering before.
carz12 said:
I'll try it out tonight, the sources I used to compile were wes's and his kernel has tethering support unless I broke it, I've never used tethering before.
Click to expand...
Click to collapse
Tethering is actually useful even if you don't need it all the time, eg. if your desktop PC cannot access the internet or your wife is using an iPod touch to access the internet in a restaurant.
So do Rogers Dreams require a special kernel, due to the 911 fix? So I guess the stock ROM update has the proper kernel, but modifications like the wireless tether for a Rogers Dream would require a patched Rogers kernel.
Edit: wasn't even aware of the ROM kitchen before this.
Untested! I don't plan to provide support for these ports!
The reason I am publishing is from my recent trials of compiling my own kernel for new radio 32A Magic. I have learned a lot about what sanpei's kernel consists of and the similarities between our device and the GSM Hero. In particular, the only difference between our ROMs seems to be mainly just the kernel. Everything else is almost identical. As such I want the community to try to use a tested NR kernel, sanpei's 2.6.32.9, and apply it to some different ROMs and report back with results.
We don't need multiple threads of the same kernel on different ROMs. So I'm trying to consolidate some information here.
I can test it on my cousins phone probably this weekend as well. Hoping for some preliminary results till then.
sanpei2.6.32.9_villain_port
This is a repack of sanpei's kernel repacked via ordinary boot.img method, with init.hero.rc copied to init.sapphire.rc
Flash this after you flash Villain ROM:
http://www.villainrom.co.uk/viewtopic.php?f=44&t=680#p11789
2.1 Sense UI ROM
sanpei2.6.32.9_anykernel.zip
This is a repack of sanpei's kernel repacked via Koush Anykernel
The idea is that you can flash most ROMs from old radio using this port with some caveats.
READ THIS BEFORE YOU FLASH
You cannot use this port if:
1) You are NOT on a 6.35 series radio. This rules out any 32Bs or myTouch 1.2
2) the ROM uses squashfs anywhere (open up the update.zip of the ROM and look at /system/modules/lib and /system/
3) modules have special directory structure under /system/modules/lib (such as Cyanongenmod, which has modules under 2.6.xx.x-cyanogenmod instead of just 2.6.xx.x)
4) you use an ext4 apps2sd partition (it will simply not recognize it)
Explanations:
If the ROM uses squashfs, this kernel does not support it and you will need to fix those problems yourself.
There may be other issues involved when you use this kernel. It is recommended that you stick to the one that came with the ROM.
This rules out any Cyanogenmod because of the use of squashfs.
If missing init.sapphire.rc, copy the Hero one (if flashing a Hero ROM) using:
adb shell cp init.hero.rc init.sapphire.rc
Refer to the ROM Bible for reference:
http://forum.xda-developers.com/showthread.php?t=682243
Any new or old ROMs that already use new radio
This is just the kernel carz12 posted repacked:
http://forum.xda-developers.com/showthread.php?t=689652
Credits:
cyanogen for everything
Koush anykernel
sanpei for his version of AOSP kernel with integrated new radio support
And a lot more I might be missing
FYI and FWIW a few weeks back there were a lot of 6.35 roms that were cooked and posted in this forum. They were all using the 2.6.32.9 kernel that Sanpei ported. That is, the boot.img-kernel was the same for all. The ramdisk was changed as you have done and the two were re-packed into the boot.img.
I have successfully applied this approach for maybe 3 or 4 different 1.6 roms and maybe 10 different 2.1 roms.
dsixda's ROM Kitchen makes executing these steps a piece of cake
http://forum.xda-developers.com/showthread.php?t=633246
Then you just replace the wlan.ko module and GPS lib file for wifi and GPS compatibility.
You're probably aware of these details but I thought they might help others.
Tried to flash VillainROM 6.1, but during the flash it aborts saying "Failure at line 2: assert getprop("ro.product.device") == "hero"
How do I solve this?
pellen said:
Tried to flash VillainROM 6.1, but during the flash it aborts saying "Failure at line 2: assert getprop("ro.product.device") == "hero"
How do I solve this?
Click to expand...
Click to collapse
Must have hero recovery not patched recovery by cursor
Ahh...thougt cursors tweaked recovery didn't differ that much. *change recovery*
I am pretty sure the update script can also be modified. The assert statement can be removed and the rom should load fine on the Hero, Cursor and Amon Ra recoveries.
Ok, so now I've flashed VillainROM 6.1 with the sanpei2.6.32.9_villain_port and I can't say it's working especially well
First of all it doesn't ask me to enter the SIM card PIN when i boot, so the mobile connection is dead. Wifi and bluetooth is dead too. The camera flicker, and then fades to black, taking a pic resulted in reboot.
giant_rider said:
FYI and FWIW a few weeks back there were a lot of 6.35 roms that were cooked and posted in this forum. They were all using the 2.6.32.9 kernel that Sanpei ported. That is, the boot.img-kernel was the same for all. The ramdisk was changed as you have done and the two were re-packed into the boot.img.
I have successfully applied this approach for maybe 3 or 4 different 1.6 roms and maybe 10 different 2.1 roms.
dsixda's ROM Kitchen makes executing these steps a piece of cake
http://forum.xda-developers.com/showthread.php?t=633246
Then you just replace the wlan.ko module and GPS lib file for wifi and GPS compatibility.
You're probably aware of these details but I thought they might help others.
Click to expand...
Click to collapse
I completely missed that post actually . Plus it's now closed.
But I wanted to see specifically how well Hero ROMs translate over to Magic ROMs because of what I've been reading about the similar kernels. The thing is that while I know to copy over init.sapphire.rc to resolve some conflicts, I'm not sure what else is involved in porting a ROM right now to get it to work.
I'm new to porting ROMs.
Maybe mods ought to close this one then?
With Eris ports you will be missing SIM card features.
So with 2.6.32.9 bluetooth and wifi break? I was actually expecting bluetooth to work. What works?
I guess I'll do some reading again. But I haven't seen that information posted regarding how to resolve some of the issues of porting ROMs.
I was looking to figure out some of the incompatibility of the kernel I was compiling so I thought this might help
If the Hero ROMs worked well enough I had the idea of modifying the AnyKernel script to add cpio to recovery by updating busybox so that ROMs can be unpacked, modified and repacked all in recovery. It means unpacking the ramdisk gunzip, modifying it and repacking it, essentially adding one script to AnyKernel. But I guess they don't work that well so
xaueious said:
I'm new to porting ROMs......
I guess I'll do some reading again. But I haven't seen that information posted regarding how to resolve some of the issues of porting ROMs.
Click to expand...
Click to collapse
A lot of the issues when porting are not related to the kernel but to the modules and lib files.
Try testing and hacking through some issues. For example, replace the wlan.ko file in the /system/lib/modules folder with one from a similar rom that is working on 32a same radio version. If you're porting Hero, then pull the wlan.ko from one of Capy's roms.
To get camera working, you'll need to replace the camera related libs in the in the /system/lib/ folder with ones from a similar rom that is working on 32a and so on.
Porting involves, at a minimum, replacing the boot.img-ramdisk and the files for stuff that is not compatible with the 32a hardware, radio version, etc.
Once you figure out these basics by experimenting with swapping out stuff with working pieces from a 32a compatible rom on the same radio version, you can then get into making updates to the files in the boot.img-ramdisk yourself, the update-script, the build.prop files, the init files in /system/etc/init.d, etc.
xaueious said:
Maybe mods ought to close this one then?
Click to expand...
Click to collapse
I think it's a good thread. Maybe some of the guys who have been porting roms will add their comments. I may be wrong but I don't there is a how to guide for porting.
anykernel is useful for a direct kernel port like cm5 to EABI1 on same rom scenarios, nice piece of coding by koush though, way many files to change, an update package would work on roms made for your device(proper assert) but most need the update script modified and at least wlan.ko changed.
testing now Flashing
how long does it take to boot?
Working:
USB
Music app (Sound ok)
Gallery 3D OK takes a while to work
Not Working:
Camara
Wifi
Bluetooth
GSM connection
Issues:
Very very long and slow boot alot of patient is required.
Slow Menu Scrolling
Freezes some times (have to take battery)
Reboots alone sometimes
This is a question for someone with really good knowledge of system files within android. I have taken the 3.06.405.1 RUU and cooked it into a rom to use for myself using the dsixda kitchen. Everything works just fine except wifi. I cannot get past the obtaining IP adress when trying to connect to wifi. I have searched through the phone trying to find the files that control wifi and am stumped. Which files would i need to extract from stock rom to make the wifi obtain an IP. I know my router is good because my wife is using it with no issues. When i cooked the rom i had to change the boot.img to one from a rom that i know can boot because the one in the ruu would not get past splash screen. Do i need to try a different boot.img or is there files that i need to replace that are inspire 4g specific.
I have already tried kernels from VU, Klquicksall and lordmod. Any help on this matter would be greatly appreciated.
Gizmoe said:
This is a question for someone with really good knowledge of system files within android. I have taken the 3.06.405.1 RUU and cooked it into a rom to use for myself using the dsixda kitchen. Everything works just fine except wifi. I cannot get past the obtaining IP adress when trying to connect to wifi. I have searched through the phone trying to find the files that control wifi and am stumped. Which files would i need to extract from stock rom to make the wifi obtain an IP. I know my router is good because my wife is using it with no issues. When i cooked the rom i had to change the boot.img to one from a rom that i know can boot because the one in the ruu would not get past splash screen. Do i need to try a different boot.img or is there files that i need to replace that are inspire 4g specific.
I have already tried kernels from VU, Klquicksall and lordmod. Any help on this matter would be greatly appreciated.
Click to expand...
Click to collapse
The wifi is based on the Broadcom 4329 chipset and the bcm4329.ko kernel module is required for wifi operation (it is stored in the /system/lib/modules/ directory on the phone). The module should match the kernel and should have been compiled with the kernel build. You don't mention what kernel you're using so I can't comment further. bcm4329.ko from a different kernel build may work, but with varying degrees of success.
Gene Poole said:
The wifi is based on the Broadcom 4329 chipset and the bcm4329.ko kernel module is required for wifi operation (it is stored in the /system/lib/modules/ directory on the phone). The module should match the kernel and should have been compiled with the kernel build. You don't mention what kernel you're using so I can't comment further. bcm4329.ko from a different kernel build may work, but with varying degrees of success.
Click to expand...
Click to collapse
Thank you very much gene I appreciate it. I did replace that file but did not make sure it matched the kernel. I will give it another shot. And for others that read this I still am using Bindroid as my daily I'm just trying to figure out how to build roms too. I thank all the devs for the great tools available to do so, mainly the kitchen.