Hardware GL: SOLUTION - G1 Android Development

Seems that the file that stands in the way of hardware GL on DREAM for android 2.x is libhgl.so. Now interesting thing is that I've compared the 32A and DREAM versions of libhgl.so (used stock rogers roms since their versions match), and I've found that the libhgl.so for rogers 32A and DREAM are *identical*.... which means that the GL parts of the 7200A and 7201A are compatible -- i.e. work with the same driver.
Now this guy has apparently released leaked 32A/Hero files and has built a 32A ROM with them, including the applicable libhgl.so... which should be compatible with DREAM/32B..... http://forum.xda-developers.com/showthread.php?t=636212
Is there some stupid obvious thing that I'm missing? Because it sure looks to me like we have all the pieces we need.....

here is what we are missing.
A developer (someone that knows what they are doing) to check this before making asumptions of something working right.

whats this guy talking about ^^^^

death1246 said:
here is what we are missing.
A developer (someone that knows what they are doing) to check this before making asumptions of something working right.
Click to expand...
Click to collapse
What are you getting at? Are you implying that I'm not a qualified developer?
I can assure you that I am.
What I am asking is if there is actually anyone who has looked at this at all, and what their findings were. And I want this information BEFORE I waste several hours of my time building AOSP for DREAM with files dumped from HERO. If someone has tried, but there is some simple thing that is missing, like radio/firmware issues that might interfere with this libhgl.so version running on a DREAM with, for example, a stock radio.
Is this related to those weird kernel changes that HTC made to rogers dream? Might we need to install a rogers dream radio? Might we need to install a HERO radio? There are all kind of weird issues that may need to be worked out even given that the hardware IS compatible!

kingklick said:
whats this guy talking about ^^^^
Click to expand...
Click to collapse
Beats me.... but it *feels* like he's trying to insult me...

Very interesting.

Nice observation.
King, since ur pumping out roms like theres no 2moro Have u tried incorporating his libs into ur rom n seeing if it works ?

I'm not a qualified developer, but I am a 32A user and in case this helps:
To use ROMs based on the new Rogers update I need to install the 1.76.2007 SPL and the 6.35 Radio. I also need to use Amon_RA's Hero recovery. The same thing goes for ahmgsk's ROM, though it isn't stable enough for me to use. ahmgsk does have 3D Gallery and HQ YouTube working.

Daneshm90 said:
Nice observation.
King, since ur pumping out roms like theres no 2moro Have u tried incorporating his libs into ur rom n seeing if it works ?
Click to expand...
Click to collapse
He actually is. Not necessarily from THAT ROM, but likely from the same source... hero 2.1 dump. And not necessarily the files needed for GL. That is why h264 playback is working on his roms now....
He is also employing the 10MB ram hack, which breaks GL even when the drivers are definitely right.
Be aware that just putting the files into place and disabling the 10MB ramhack may not be enough. We are definitely talking about two devices with different memory, so it may require a kernel adjustment. It may also require a radio adjustment.

Rede83 said:
I'm not a qualified developer, but I am a 32A user and in case this helps:
To use ROMs based on the new Rogers update I need to install the 1.76.2007 SPL and the 6.35 Radio. I also need to use Amon_RA's Hero recovery. The same thing goes for ahmgsk's ROM, though it isn't stable enough for me to use. ahmgsk does have 3D Gallery and HQ YouTube working.
Click to expand...
Click to collapse
Note that we aren't working off a rogers dump. I just used the rogers files (to judge hardware compatibility between 7200A and 7201A) because I happen to know that everything in those two devices definitely matches up except the CPU/RAM.
But your observation regarding the SPL and RADIO are *definitely* valid... which is why I'm talking about the possibility of needing to mess with the radio. I don't *think* that the SPL itself has any more to do with it than simply being compatible with the chosen radio.
*** further possibility: likely any problems encountered would be due to memory mapping. It may be possible to manually adjust the libhgl.so to the appropriate mappings. Would require some (at least partial) disassembly/hacking.

Not too sure if it helps but sanpei's rom also had 3d accel.
http://forum.xda-developers.com/showthread.php?t=620782

lbcoder said:
I don't *think* that the SPL itself has any more to do with it than simply being compatible with the chosen radio.
Click to expand...
Click to collapse
I asked about that when initially trying a ROM for the 6.35 radio and my understanding, too, is that the SPL is just required for compatibility with the radio.

Daneshm90 said:
Not too sure if it helps but sanpei's rom also had 3d accel.
http://forum.xda-developers.com/showthread.php?t=620782
Click to expand...
Click to collapse
A heads up: ahmgsk's ROM is build on Sanpei's kernel.

Edit: Rhetorical question. No need to be posted.

edited to be nice

death1246 said:
here is what we are missing.
A developer (someone that knows what they are doing) to check this before making asumptions of something working right.
Click to expand...
Click to collapse
kingklick said:
whats this guy talking about ^^^^
Click to expand...
Click to collapse
lbcoder said:
Beats me.... but it *feels* like he's trying to insult me...
Click to expand...
Click to collapse
Nah I think he's asking what Death1246 was talkin about. Because it didn't make a whole lotta sense.
LesserAnimal said:
Never mind that being the entire point of this thread.
Click to expand...
Click to collapse
and Lol at this ^

So would it be possible to pull the libhgl from kings build and push it to an eclair build?

I don't know if it helps or if I'm being Captain Obvious here, but I've tried just today porting ahmgsk's ROM to 32A old radio (using my Cyanogen-based kernel) and neither video nor 3D does work after this. And pretty much the only thing I've changed is kernel image (with ahmgsk's ramdisk) and wlan.ko, obviously (well, I've moved apps from /system/app to /data/app_s to work around the larger system partition with the new 32A radio, but I don't think that has anything to do with 3D not working). So no, the libhgl doesn't cut it by itself, there's obviously something in-kernel preventing 3D from working on the old 32A/32B radios.

Yes, there are a couple kernel changes that need to be made, and after boot on our Kaiser/Vogue we need to:
Code:
chmod a+rx /dev/msm_hw3dc
chmod a+rx /dev/msm_hw3dm
(we do this in our init.rc)
You also will need working copybit.msm7k.so, libGLES_qcom.so, and an egl.cfg that enables libGLES_qcom.so . There are other .so's that may affect it but those are the only ones I've ever had to move around. This gets OpenGLES mostly working.
I'm no kernel dev but our kernel source can be found here, you can thank dzo and vilord for it.

polyrhythmic said:
Yes, there are a couple kernel changes that need to be made, and after boot on our Kaiser/Vogue we need to:
Code:
chmod a+rx /dev/msm_hw3dc
chmod a+rx /dev/msm_hw3dm
(we do this in our init.rc)
You also will need working copybit.msm7k.so, libGLES_qcom.so, and an egl.cfg that enables libGLES_qcom.so . There are other .so's that may affect it but those are the only ones I've ever had to move around. This gets OpenGLES mostly working.
I'm no kernel dev but our kernel source can be found here, you can thank dzo and vilord for it.
Click to expand...
Click to collapse
WOW THIS IS awesome!
Why didn't i think of that?
i might wait to release a rom though, i'm busy.
How bout it king?

Related

Cyanogen 3.9.6 straightforward sapphire port [32B]

Details here:
http://android.modaco.com/content/h...-for-sapphire-magic-tested-on-vodafone-magic/
This is a very straightforward port of Cyanogen's awesome 3.9.6 ROM to run on the HTC Sapphire / Magic (tested on the Vodafone Magic).
Apply as any other update.zip (via modified recovery image).
It's FAST!
P
is this for 32A?
zidane said:
is this for 32A?
Click to expand...
Click to collapse
cant u read?????????????????? VODAFONE = 32B
Paul,
What did you change to get Compcache working? I'm already running 3.9.5 on my 32B and don't really want to reflash just for the sake of being able to push a couple of modified files
Cheers
So this is with cyno 3.9.5 kernel right?
i think i can read better than you
What's the difference between this port and the jerpelea (or something) port?
isnt this the same as jerpleas port?
Same as Jerpelas and all the other 'ports' that use the trick I found of renaming init.trout.rc in boot.img to init.sapphire.rc.
I've asked a couple of the devs to include this file by default to avoid the plethora of threads here that are just dream roms which pretty much anyone can get running in a couple of minutes.
At the moment the 'real' development work is mainly in the dream forum, lucky for 32b owners they run perfectly 32A, wait for the ports
Waiting for the Drizzy/JAC new hero port tonight - it's meant to be damn fast,and they think they can get it to 'cupcake' speeds
re: posts above...
Correct, it's using Cyanogen's kernel (hence compcache functions correctly).
Correct, it's for 32B.
Correct, it's using a tweaked boot.img with a renamed RC.
I think it's a valid post because not everyone has the ability / time / inclination to download the ROM, extract the boot.img, rename the file, rebuild the boot.img and then resign the resulting zip.
As always, I created this for my own use and thought i'd share!
I also have asked Cyanogen (via Twitter) to include a sapphire.rc in future revisions. Here's hoping!
P
dazcox5181 said:
Same as Jerpelas and all the other 'ports' that use the trick I found of renaming init.trout.rc in boot.img to init.sapphire.rc.
I've asked a couple of the devs to include this file by default to avoid the plethora of threads here that are just dream roms which pretty much anyone can get running in a couple of minutes.
At the moment the 'real' development work is mainly in the dream forum, lucky for 32b owners they run perfectly 32A, wait for the ports
Waiting for the Drizzy/JAC new hero port tonight - it's meant to be damn fast,and they think they can get it to 'cupcake' speeds
Click to expand...
Click to collapse
So your saying this has the cyan 3.9.5 kernal intact?
offcina said:
cant u read?????????????????? VODAFONE = 32B
Click to expand...
Click to collapse
Can you be polite?????????????????
Gimpeh said:
So your saying this has the cyan 3.9.5 kernal intact?
Click to expand...
Click to collapse
Yes indeed...
P
I think that with this ROM, libwebcore.so from CM3.6.8.1 and the Noverca Audio*.csv files, I can actually use my Magic for what it's supposed to be used for!
Until tomorrow at least
modaco said:
Yes indeed...
P
Click to expand...
Click to collapse
Splendid! Thanks so much. Do you plan on continuing support of Cyan roms?
Thanks Modaco,
all the apps and the cache, to ext3 partition. Good rom. Wifi runs ok , it goes so fast. For me, the most important advantage, the apps and the cache, to sd!.
Thanks guy
compcache is working, wifi wont start.
I'm pretty sure that jerpelea had to get a different wlan.ko for it to work on his.
This just keeps looping on the Android splash screen. Is it because I am using Amon_Ra's 1.2 recovery???
I am using 1.2 and had no troubles.
Just WiFi wont start.
I have tried replacing it with the wlan.ko from jerpelea's rom.
It doesnt like it.
xordis said:
I am using 1.2 and had no troubles.
Just WiFi wont start.
I have tried replacing it with the wlan.ko from jerpelea's rom.
It doesnt like it.
Click to expand...
Click to collapse
I dont get it! I had similar problems with newer Cyanogen build than what I am on. Also the QTek rom does the same.
It seems to me that any ported ROMs which all you supposedly need to do is run 'update.zip' fail with a boot loop for me.
I don't know why it's only with ported ROMs though..... It's driving me mad!!!

[32A][ROM][PORT] ZeroXd 5.1 w/ Amon_RA's v1.1.0 Kernel [Sept. 7 2009]

Original Thread
Credits to TwistedUmbrella and Amon_RA for the kernel ofc!
Casper's Shadow - ZeroXd 5.1 w/ Amon_RA's v1.1.0 kernel [rapidshare]
For Ringtones and other "Extra Stuff" download Resources.zip from oringinal thread. Maybe on next update I'll include them already into the original ROM archive...
Note: Just install normally! No need to type anything into the terminal as the original thread states because this port replaces ramdisk and kernel so no need
Hi thanks for another fine release..aft trying out ur jac release and this rom.. i find this not as fast as the jac one..if u could improve on the jac rom it will surely be an incredible rom..really like the speed and lightness on the jac rom..thanks once again..
I only do the ports This is not my work. I merely repack the files for easier installation and for those that don't have linux
covertless said:
Hi thanks for another fine release..aft trying out ur jac release and this rom.. i find this not as fast as the jac one..if u could improve on the jac rom it will surely be an incredible rom..really like the speed and lightness on the jac rom..thanks once again..
Click to expand...
Click to collapse
HAHAHA, lol, HAHAHAHAHAHA. Wow, hahahahaha. Ok. Sorry. Ok, seriously... anyway... You might wanna throw the kernel on this
Most Recent:
G1 / MT3G: http://twistedumbrella.slackdev.com/ZeroXd-5.1r2.zip
MD5: 0d10525b55ed6c97b7741a70aa113cdb
Execute Terminal and enter the following commands:
rwsystem
magic
This configures the system to the specific device. This is until I finish automation.
LEDs have been restored to 93%
(and delete system/bin/magic and system/bin/sapphire, as they dont affect a swapped kernel)
I think it'll shut this kid up. Unless he has no idea what partitioning an sd card does, in which case this will still be slow. It's based on some newer source and some improved scripts and optimizing. Can't say its faster, but at least itll even out.
L10nH34Rt said:
I only do the ports This is not my work. I merely repack the files for easier installation and for those that don't have linux
Click to expand...
Click to collapse
Okay my bad, anyway what I meant to say was thank you for the effort in porting over for the 32a.
twistedumbrella said:
HAHAHA, lol, HAHAHAHAHAHA. Wow, hahahahaha. Ok. Sorry. Ok, seriously... anyway... You might wanna throw the kernel on this
Most Recent:
G1 / MT3G: http://twistedumbrella.slackdev.com/ZeroXd-5.1r2.zip
MD5: 0d10525b55ed6c97b7741a70aa113cdb
Execute Terminal and enter the following commands:
rwsystem
magic
This configures the system to the specific device. This is until I finish automation.
LEDs have been restored to 93%
(and delete system/bin/magic and system/bin/sapphire, as they dont affect a swapped kernel)
I think it'll shut this kid up. Unless he has no idea what partitioning an sd card does, in which case this will still be slow. It's based on some newer source and some improved scripts and optimizing. Can't say its faster, but at least itll even out.
Click to expand...
Click to collapse
Anyway twistedumbrella, are you as what your name describes? Your comments are uncalled for and not needed in this community. Please grow up and get a life. I am new here, so would appreciate if you could give positive feedbacks instead of insults.
@covertless: He is right though... On my magic this ROM is *MUCH* faster than the JACxHEROski one
@Twisted: Ok will throw the kernel and include full instructions based on your post here!
Thank you for your work!
p.s. If I delete /system/bin/magic and /system/bin/sapphire will we still be able to run rwsystem and then magic?
*L10nH34Rt: Great could you release the ported version when its done?
P.S. I am not saying he is wrong, anyway I appreciate that there are people like you and him contributing to this community by working hard on the dev of roms. Not sure as to why he had to assume that non programmers like me are "kids".
Sure I will later today when I get to my linux box
covertless said:
Hi thanks for another fine release..aft trying out ur jac release and this rom.. i find this not as fast as the jac one..if u could improve on the jac rom it will surely be an incredible rom..really like the speed and lightness on the jac rom..thanks once again..
Click to expand...
Click to collapse
Wait, even he says "jac rom"i think he is talkin about older zero releases which are using jac kernel vs new amonra kernel, or is he not? Because there is no hero port who can outperform xero's speed with proper adjustments atm.
Nyanna said:
Wait, even he says "jac rom"i think he is talkin about older zero releases which are using jac kernel vs new amonra kernel, or is he not? Because there is no hero port who can outperform xero's speed with proper adjustments atm.
Click to expand...
Click to collapse
I was referring to L10nH34Rt's port of the JACxHEROski-v1.7r2 w/ Amon_RA's 1.1.0 kernel.
http://forum.xda-developers.com/showthread.php?t=549873

[MOD] No More Need for [PORT][32B] with Hero ROMs

Yes, you read that title correctly. We are wasting time, energy, and file size making these ports when all the builds could be "co-ed"
I have already done this in my builds, but not everyone wants to use mine (I know, I was sad, too) so I will look into if the script being used can be rewritten to use my new standard. Until such time, Here is an update add-on that will convert all the newest Hero ROMs into co-ed versions. This is also dependednt on the concept that all current ROMs are using JACs kernel.
Deported Version 1.0
http://twistedumbrella.slackdev.com/Deport-1.0.zip
MD5: d3846db3b372a9d2a0bfca47bf6409f2
Copy to root of SD and flash like any other update. Kudos.
just download
have just downloaded, will def. give it a try....
I am sorry, but pls don't shout at me for being dumb.... but should i flash this first then flash the Hero rom... tks.
So I have a 32a magic. So I can load any 32b rom out there and then apply your patch?? as long as its using the jac kernel?? Just wanting to make sure before I try it out. It just seems all to easy. haha
twistedumbrella said:
Yes, you read that title correctly. We are wasting time, energy, and file size making these ports when all the builds could be "co-ed"
I have already done this in my builds, but not everyone wants to use mine (I know, I was sad, too) so I will look into if the script being used can be rewritten to use my new standard. Until such time, Here is an update add-on that will convert all the newest Hero ROMs into co-ed versions. This is also dependednt on the concept that all current ROMs are using JACs kernel.
Deported Version 1.0
http://twistedumbrella.slackdev.com/Deport-1.0.zip
MD5: d3846db3b372a9d2a0bfca47bf6409f2
Copy to root of SD and flash like any other update. Kudos.
Click to expand...
Click to collapse
same question from me..
HuMpS 97 DoHc said:
So I have a 32a magic. So I can load any 32b rom out there and then apply your patch?? as long as its using the jac kernel?? Just wanting to make sure before I try it out. It just seems all to easy. haha
Click to expand...
Click to collapse
HuMpS 97 DoHc said:
So I have a 32a magic. So I can load any 32b rom out there and then apply your patch?? as long as its using the jac kernel?? Just wanting to make sure before I try it out. It just seems all to easy. haha
Click to expand...
Click to collapse
tried on my 32A device. first flashed a G1/MT3G image (ZeroXD 6.13r2). After this i flashed deported and made a reset. Nothings happens. DDMS didn't detect my device again. Back to my old rom
Device up again with old image
regards
endebe
HuMpS 97 DoHc said:
So I have a 32a magic. So I can load any 32b rom out there and then apply your patch?? as long as its using the jac kernel?? Just wanting to make sure before I try it out. It just seems all to easy. haha
Click to expand...
Click to collapse
NO people!
When Twist said its CO-ED it means that it can be used on a G1 and a MyTouch
NOT co-ed as in 32A and 32B
Im almost 100% sure this is ONLY for a 32B
Lakers3408 said:
NO people!
When Twist said its CO-ED it means that it can be used on a G1 and a MyTouch
NOT co-ed as in 32A and 32B
Im almost 100% sure this is ONLY for a 32B
Click to expand...
Click to collapse
This would be correct. Co-ed meaning both t-mobile branded devices. 32A requires a different kernel, but im sure those users knew that. So one boot image could not be "dual kernel" and i dont have the time to make that many changes to the existing one to make it go either way
Okay so basically, i install the hero rom first and then this mod? because i just tried this with micro hero v1.4 and it got stuck at the vodafone screen(used logcat and there was error), but then when i installed micro hero on its own it boots.????
great work on this Twisted. You're a genius.
what is the difference of to have or not to have this MOD?
I dón´t taste any difference.
Do I flash this before flashing a ROM? Also, I'm guessing I still have to wipe before flashing the ROM, correct?

Chances of Eclair on 32A (MT3G LE Fender)?

I've tried KiNgxKxlick-AOSP21-v161_signed.zip with the 32A patch and all. It does boot but no touch screen functionality.
What's the chances of being able to get eclair working on the device as defined in my signature?
kbeezie said:
I've tried KiNgxKxlick-AOSP21-v161_signed.zip with the 32A patch and all. It does boot but no touch screen functionality.
What's the chances of being able to get eclair working on the device as defined in my signature?
Click to expand...
Click to collapse
The chances of 2.1 on Fender are excellent given that T-Mobile announced it would be pushing 2.1 to the Fender and MT3G 1.2 models this spring. As far as a customized ROM, I seriously doubt there will be anything until the phones receive the official update.
Did you actually get the ROM runnning?
C0dy said:
Did you actually get the ROM runnning?
Click to expand...
Click to collapse
Yea it actually ran, just said "Press the Android to Start"... well couldn't press it The 32A patch was from the G1 forum on here as opposed to the slightly newer one for magic on this sub-forum.
Also the Radio looked like it was connecting to. For all I know touchscreen, bt, and headphone jack could have been unsupported, but surprising to see it actually booted.
Twiddles thumbs waiting.
kbeezie said:
Twiddles thumbs waiting.
Click to expand...
Click to collapse
you can wait all you want. there is a whole new touch screen with new drivers tied to the kernel. we have yet to figure out how to get them into any other rom.
We are trying. Belive me, once we get somethign working, Wes, Criffmon and myself will let all of you know.
For now, find criffmons posts in the android themes section and use one of our themed fender roms. that is all you will gett o work. I have tested everything for a month now, even flashing the fender kernel over roms does nothing because files have been changed.
Please be patient
I think we're stuck with themes and whatnot as opposed to custom ROMs until HTC releases the kernel source. Bug @htc on Twitter for the source!
crypysmoker said:
you can wait all you want. there is a whole new touch screen with new drivers tied to the kernel. we have yet to figure out how to get them into any other rom.
We are trying. Belive me, once we get somethign working, Wes, Criffmon and myself will let all of you know.
For now, find criffmons posts in the android themes section and use one of our themed fender roms. that is all you will gett o work. I have tested everything for a month now, even flashing the fender kernel over roms does nothing because files have been changed.
Please be patient
Click to expand...
Click to collapse
I'm not complaining... I'm just waiting
wpbcubsfan said:
I think we're stuck with themes and whatnot as opposed to custom ROMs until HTC releases the kernel source. Bug @htc on Twitter for the source!
Click to expand...
Click to collapse
I personally wouldn't mind eclair ala fender as nothing more than the stock rom they come out with + superuser/busybox. Kinda what I'm doing now but with 1.6

[STOPPED][ROM][32B;G1]DarchLegend[Fast][WG kernel]

First thank to all dev's! Particulary bcrook and sanpei.
Original link
Hi,
after many test and hours, here is my second ROM!! I will port villain's ROM tomorrow, I can0t active wireless connecionts on this ROM!
really, it is a port of DarhLegendv5.0.5 , ported to 32B (and G1 perfect SPL too(?))
To port this, I've used a WG kernel with RAM hack.
Partition Layout: Fat 32 ;; EXT 2/3/4 ;; SWAP
Wipe : data/factory reset, dalvik-cache, SD:ext partition
So, the links..!:
DarchLegendv505.Artifexed.v01.BETA
works:
most things!
don't work:
wifi, BT, camera
Change Log:
v01 : BETA release
Thank to say what you think about this port!
Whats the point of announcing a ROM without actually announcing anything other than the fact it is coming ? Seriously ..
No offense or anything .. thanks for putting time and effort into building a rom.. just saying that this thread is kind of pointless if you're not actually announcing anything ..
He's announcing the announcement
look there goes santa with the 2.1 update
shawn1224 said:
He's announcing the announcement
Click to expand...
Click to collapse
Ive noticed alot of devs have been doing that in the cdma hero forums. Kinda like how tmo, sprint, at&t tell you your gonna get 2.1 update except this is actually gonna happen.
if the rom didnt have a release date then say something but since its tomorrow then just chill i am starting to think people join to flame people
all i wanna know is does is it going to fix our tethering problem.
Aeikozz said:
all i wanna know is does is it going to fix our tethering problem.
Click to expand...
Click to collapse
it should I know i got it on sprint hero but i dont know what is gained or lost in a port. I do want to add thankyou to the devs that make roms cuz I know I get sensitive when people say something bad about my work and they just let it roll of them like water. Also I like the idea of telling you when the next release is cuz you aren't stuck in limbo wondering how things are going
how is it going with this production
32B Wifi with Hero ROM
Hi,
anyone can help me?
I can't active the Wifi with DarchLegend on my 32B.
The wlan.ko is OK.
Wich file(s) must I change?
thank in advance
The wlan.ko needs to be built together with the kernel. You can't just take a wlan.ko and stick it in a ROM.
dferreira said:
The wlan.ko needs to be built together with the kernel. You can't just take a wlan.ko and stick it in a ROM.
Click to expand...
Click to collapse
Well basically you can, but then you'd have to use the same kernel build that was used to build that wlan.ko. Every time kernel is compiled, modules for it need to be recompiled with it.
klothius said:
Well basically you can, but then you'd have to use the same kernel build that was used to build that wlan.ko. Every time kernel is compiled, modules for it need to be recompiled with it.
Click to expand...
Click to collapse
Yes, that was what I meant
Artifex14 said:
Hi,
anyone can help me?
I can't active the Wifi with DarchLegend on my 32B.
The wlan.ko is OK.
Wich file(s) must I change?
thank in advance
Click to expand...
Click to collapse
yes, the kernel and wlan.ko correspond.
tethering support must be compiled into the kernel I believe.
Re: 32B Wifi with Hero ROM
ok, so, I don't understand, because I've did it!
Otherwise to change? In init.heroc.rc?
Sent from my Hero using the XDA mobile application powered by Tapatalk
sooo....tomorrow was yesterday
eyegor said:
sooo....tomorrow was yesterday
Click to expand...
Click to collapse
lol yeah was thinking that too
Yes, but I can't active the Wifi......otherwise, the ROM is stable, fast, with compcache,...
I'm uploading a non Wifi ROM, and if anyone can help me, thank in advance (the wlan.ko is right!)
The file is uploaded.
Artifex14 said:
The file is uploaded.
Click to expand...
Click to collapse
Thankyou will let you know how it is

Categories

Resources