Jump to content

[UPDATED]Performance Tweaks etc on Android!.


Guest gauravv

Recommended Posts

SEND ME THE KERNEL & TOLLS for EDITING (Patching) etc.

source:

svn://o2droid.phj.hu/droid

Tools:

for editing source -> any texteditor you prefer

for patching source -> patch (linux binary)

for building -> make & armeabi-toolchain

:huh:

Link to comment
Share on other sites

Guest ashwin Bhagwandin
guy's

i reinstalled on ext3 with latest update

but facing again S.O.D

do i need to install the update again or change the Zimage

did you installed a task killer and the CPU boost tool, i haven't got a SOD since installing these Apps

Link to comment
Share on other sites

Guest elbee72
source:

svn://o2droid.phj.hu/droid

Tools:

for editing source -> any texteditor you prefer

for patching source -> patch (linux binary)

for building -> make & armeabi-toolchain

:huh:

Regarding wifi kernel driver

kernel version is 2.6.31-bfs310, so some kind of modified 2.6.31 linux version?

wifi chip in b7610 architecture is SWB-T30 with wl271 wifi chipset.

http://linuxwireless.org/en/users/Drivers/wl12xx is giving good info to backport the wl1271 driver to 2.6.31 kernel and b7610 arch.

Regarding b7610 architecture

Troubleshooting.pdf from b7610 service_manual displays U203 on page 16 with WLAN pins: WLAN_SDIO_DO/D3, WLAN_EN and WLAN_IRQ.

looked up in s3c6410 user manual SDIO means the chip is connected to one of three SD-MMC controllers (SD/SDIO/MMC).

but why are gpio pins H6-9 not not found with GPIOgfx or HaRET while using wifi under winmo on b7610?

Good luck making wifi work on b7610, could be done with some effort !!

Link to comment
Share on other sites

Regarding b7610 architecture

Troubleshooting.pdf from b7610 service_manual displays U203 on page 16 with WLAN pins: WLAN_SDIO_DO/D3, WLAN_EN and WLAN_IRQ.

looked up in s3c6410 user manual SDIO means the chip is connected to one of three SD-MMC controllers (SD/SDIO/MMC).

but why are gpio pins H6-9 not not found with GPIOgfx or HaRET while using wifi under winmo on b7610?

Good luck making wifi work on b7610, could be done with some effort !!

The B7610 Block diagram contained in the user manual (Troubleshooting) shows WLAN connection via SPI (same as in i8000) So maybe most of the work is done for us??

Bluetooth connection is shown via UARTI

Don't forget, the WLAN module in the B7610 is wireless n cabable too! .wouldn't that be nice? :huh:

Vic

Edited by Vic20
Link to comment
Share on other sites

Guest elbee72
The B7610 Block diagram contained in the user manual (Troubleshooting) shows WLAN connection via SPI (same as in i8000) So maybe most of the work is done for us??

Bluetooth connection is shown via UARTI

Don't forget, the WLAN module in the B7610 is wireless n cabable too! .wouldn't that be nice? :huh:

Vic

yes, i missed that, it clearly says spi on block diagram ...

But why the labels/wires to U203 say WLAN_SDIO_x on page 16?

Inside the U203 box there are also spi labels/functions on the same pins (32-37).

most of the work done? yes and no

* yes because the wl127 kerneldriver and wl217 firmware are both public and 2.6.31 should be supported

* no because the kernel doesn't detect wifi yet (mosci), so wl127 driver must be compiled with our kernel and earlier attempts of this failed

the info on wireless driver page looks solid, so compiling could be done.

after this it should be adapted to the b7610 arch. for this you need info like SDIO/spi bus/address and gpio pins for wlan-enable and wlan-hostwake

sounds simple, but implementing/testing could still be a lot of work ...

PS1: it would be nice to have wifi-n although i don't own a b7610 :-(

PS2: wifi-n would be a nice compensation for having to wait so long for wifi support ....

Link to comment
Share on other sites

* no because the kernel doesn't detect wifi yet (mosci), so wl127 driver must be compiled with our kernel and earlier attempts of this failed

the driver, which is present in our kernel is not the right one - its a 'combined - one' for wl1251/wl1271

we should have a standalone wl1271_spi driver wich is available ...

i have tried to get that merged into our kernel - with less success ...

we need a coder therefore ... because the mac80211.h (includes/net/mac80211.h) is missing some functions (at least one ... maybe only two) which i can not

implement ...

@elbee72 i can send you the files / patches which i have used so far in the evening

if i commented 2 lines out - then the module will be build but i think it will not work without this two lines :)

i have compiled and loaded it yesterday, but without changing the gpios in the kernel ... so maybe we are a little step closer ...

i will test that again with some 'gpio-changing' - would be nice if the kernel says something like 'i have found a networkcard but can't use it' :huh:

anything is better than nothing

someone with more coder-skills should have a look at it - i'm willing to test as much as i can :P

Link to comment
Share on other sites

Guest elbee72
i have tried to get that merged into our kernel - with less success ...

we need a coder therefore ... because the mac80211.h (includes/net/mac80211.h) is missing some functions (at least one ... maybe only two) which i can not

implement ...

Yes we need a coder .... but we don't have one who will work on this .... yet ....

But we do have some skilled integrators :huh: so could work ...

maybe the functions are available in the latest version of header file or could be found in repo history?

curious about the sources/patches/errors, but i try to be online this evening.

Link to comment
Share on other sites

Yes we need a coder .... but we don't have one who will work on this .... yet ....

But we do have some skilled integrators :) so could work ...

maybe the functions are available in the latest version of header file or could be found in repo history?

curious about the sources/patches/errors, but i try to be online this evening.

yes ... they are available in later versions of the header-files ... i have seen that yesterday too, but simply replacing the file with a newer one did not work for me, because then serval other errors appears.

i will do some test later ... at the moment i'm still at work ... but in one hour i will be at home ... the functions where rx related (if i remeber rigt IEEE80211_SKB_RXCB was one of them) ... so this should maybe only affect the receiving-functions ... which gives hope that at least the card can be detected ... but im still unsure if i have to build the sdio or the spi module :huh:

(both are available)

Link to comment
Share on other sites

perhaps ... but they are working on a 2.6.32 kernel which supports the wl1271 nativ ...

would be nice if the devs go up to a higher kernel-version ... but i think they wouldn't do that in a short time :)

i do not know anything about the whole spi,sdio thing and our gpios are named in a diffrent way so i do not know wich is GPIO_EN or GPIO_IRQ

do not know anything about the frequency on different clocks too ...

there is too much knowlegde missing to get that done by myself :P

so here we need a specialist

i have spended nearly two weeks to get the keyboard working ... but compared to the network the keyboard was already working ... even if it worked totaly wrong .... i could get closer and closer to the right settings with 'try and error'

that procedure can not work on the wifi as long as it is not recognized at all ... and even if ... the networkthing is much more complicated than the keyboardthing.

if i would spend 4 weeks on that i can go and search me a new girlfriend :huh:

so we need a geek without a gf and with a lot of time ... i would lend my phone for this part - no problem

Edited by mosci
Link to comment
Share on other sites

Guest tjeerdos

hi,

when i had beta1 on ext3 on my storage i had 0 problems. but since i have it installed on ext4 i have problems again.

it freezes often and many sleep of death. so that's not so good for me. maybe there is someone with a tip to solve that.

already have cpu program and taskkiller call light and still the problems.

maybe i should do the beta2 update. and i that doesn't work complete fresh beta2 install. if no good i go back to ext3 i think.

so if there is someone with an idea????

greetssss tjeerdos

Link to comment
Share on other sites

Guest centodue

AHAHAHAHAHA

I have girlfriend too! XD

I would like to reinstall all.

In my post #399 I explained that I formatted 1GB of internal memory of my B7610 as ext3 format.

But to launch start up of Android using Dual boot I copied "Haret.exe, default.txt, zImage" in the root of the external memory (sd card of 8GB, as described for "DualBoot" tool procedure)

SD card is FAT32 format.

The discussion about ext4 is regarding on SDcard or can I use it for internal memory partition if I reinstall?

I would have:

2 partitions on external SD card , one for WM6.5 and the second only for Android.

Is this possible?

What is the better formatting for Android SDcard partition?

I tried to create a second ext3 partition on SD card (6,5 GB FAT32 and 1,5 GB ext3) , but when I used Android ext3 was "invisible" (only FAT32 was exploring).

Thank you to all for your responses

Giorgio

Link to comment
Share on other sites

Guest tjeerdos
AHAHAHAHAHA

I have girlfriend too! XD

I would like to reinstall all.

In my post #399 I explained that I formatted 1GB of internal memory of my B7610 as ext3 format.

But to launch start up of Android using Dual boot I copied "Haret.exe, default.txt, zImage" in the root of the external memory (sd card of 8GB, as described for "DualBoot" tool procedure)

SD card is FAT32 format.

The discussion about ext4 is regarding on SDcard or can I use it for internal memory partition if I reinstall?

I would have:

2 partitions on external SD card , one for WM6.5 and the second only for Android.

Is this possible?

What is the better formatting for Android SDcard partition?

I tried to create a second ext3 partition on SD card (6,5 GB FAT32 and 1,5 GB ext3) , but when I used Android ext3 was "invisible" (only FAT32 was exploring).

Thank you to all for your responses

Giorgio

i don't know if it will work but somewhere in here. there was told what to do if android didn't see it...........

don't know where sorry

anyways i think we all be single soon thanks to android hhahahaha lol

greets tjeedos

Link to comment
Share on other sites

Guest elbee72

Yes, making wifi work on b7610 is a big job, and the people working on this are no experienced devs, so it could take us ages to get stuff working. So I would like to summarise what we did till now and what several people think what has to be done to make it work. If a regular dev or wannabe dev (like us) would like to help out, he/she is very welcome and has a head start with our findings. Also if people abandom this little project (we like to keep our girlfriends) others can pick up where they left.

Roadmap to make wifi work on b7610

1) [70%] what hardware is used for wifi in what way

2) [90%] what driver(s) to use and getting it compiled

3) [10%] get the chip initialized / activated at boot

4) [00%] send and receive commands to chip through spi bus

5) [00%] adapt driver/module so it get recognised by kernel

6) [00%] debug till all works ;-)

ad1:

vic20 disected his phone and updated a lot hardware info on the wiki. So we have a SWB-T30 which contains a TI wl1271 chipset. Chip info shows it has three cores (wifi, bluetooth and FM rx/tx), can be driven/connected to SPI or SDIO bus (same pins), and has two WLAN signal lines (WL_EN and WLAN_IRQ). The service manual shows a block diagram wifi is driven by SPI and signals are called WLAN_EN, WLAN_IRQ. Signals of SPI (4pins)/SDIO (6pins) bus are combined and labeled: WLAN_SDIO_D0/3, WLAN_SDIO_CLK, WLAN_SDIO_CMD. Not clear yet if SPI bus for wlan is preset by hardware or selectable by software.

It is not clear yet how wl1271 pins are connected to the s3c6410 processor. Mosci and I use are still using HaRET and GPIOgfx to find out how b7610 wifi related GPIO pins are used in winmo. Also wifi related GPIO pins of I8000 are traced to give som insight (although the i8000 wifi uses a broadcom chipset). Also gpio calls in the kernel/driver sourcecode are studied to figure out how they are/can be used.

ad2:

The kernel version in our Android build is 2.6.31 which contains only some (but not usefull) wl12xx support. The current linux kernel does support wl1271 for both SPI and SDIO driving. Mosci has managed to compile the new wifi driver for our older kernel version with little loss in functionality. A better compile could be possible, but we first want some signs of live from the chip before tuning the driver/module.

ad3:

Sandor made the wifi work for i8000 with a SPI libertas driver, what was "a hell of a job". In the i8000 init code the wifi is set up (line 251+) by driving GPIO pins to select, power on and reset (parts of) the chip. We first have to find the right pins before we can even turn on the chip. Without a turned on chip we can't send commands to the chip so the kernel cant recognise the chip. So back to ad1: finding the right WLAN GPIO pins.

Link to comment
Share on other sites

Guest ErnstJanF
Yes, making wifi work on b7610 is a big job, and the people working on this are no experienced devs, so it could take us ages to get stuff working. So I would like to summarise what we did till now and what several people think what has to be done to make it work. If a regular dev or wannabe dev (like us) would like to help out, he/she is very welcome and has a head start with our findings. Also if people abandom this little project (we like to keep our girlfriends) others can pick up where they left.

Roadmap to make wifi work on b7610

1) [70%] what hardware is used for wifi in what way

2) [90%] what driver(s) to use and getting it compiled

3) [10%] get the chip initialized / activated at boot

4) [00%] send and receive commands to chip through spi bus

5) [00%] adapt driver/module so it get recognised by kernel

6) [00%] debug till all works ;-)

ad1:

vic20 disected his phone and updated a lot hardware info on the wiki. So we have a SWB-T30 which contains a TI wl1271 chipset. Chip info shows it has three cores (wifi, bluetooth and FM rx/tx), can be driven/connected to SPI or SDIO bus (same pins), and has two WLAN signal lines (WL_EN and WLAN_IRQ). The service manual shows a block diagram wifi is driven by SPI and signals are called WLAN_EN, WLAN_IRQ. Signals of SPI (4pins)/SDIO (6pins) bus are combined and labeled: WLAN_SDIO_D0/3, WLAN_SDIO_CLK, WLAN_SDIO_CMD. Not clear yet if SPI bus for wlan is preset by hardware or selectable by software.

It is not clear yet how wl1271 pins are connected to the s3c6410 processor. Mosci and I use are still using HaRET and GPIOgfx to find out how b7610 wifi related GPIO pins are used in winmo. Also wifi related GPIO pins of I8000 are traced to give som insight (although the i8000 wifi uses a broadcom chipset). Also gpio calls in the kernel/driver sourcecode are studied to figure out how they are/can be used.

ad2:

The kernel version in our Android build is 2.6.31 which contains only some (but not usefull) wl12xx support. The current linux kernel does support wl1271 for both SPI and SDIO driving. Mosci has managed to compile the new wifi driver for our older kernel version with little loss in functionality. A better compile could be possible, but we first want some signs of live from the chip before tuning the driver/module.

ad3:

Sandor made the wifi work for i8000 with a SPI libertas driver, what was "a hell of a job". In the i8000 init code the wifi is set up (line 251+) by driving GPIO pins to select, power on and reset (parts of) the chip. We first have to find the right pins before we can even turn on the chip. Without a turned on chip we can't send commands to the chip so the kernel cant recognise the chip. So back to ad1: finding the right WLAN GPIO pins.

What about sending an email to Samsung and ask them how it works? :huh:

Link to comment
Share on other sites

What about sending an email to Samsung and ask them how it works? :huh:

hehe i have tried that a while ago ... thank you for your request ... unfortunatly we can not help you :P

but feel free to try again ... maybe you will have more luck :) would be great

Link to comment
Share on other sites

Guest elbee72
Is there any easy way to find out how it is done within windows at machine level? Maybe Daskalos can help here.

Vic

the more easy the better !!!

I think gpiogxf is pretty easy (winmo app), and if you have the triggered pins for several actions, you can "zoom in" with haret to see the exact timing and sequence. Haret was a little challenge to get working on b7610 because the commands used for i8000 didnt work (and some analysing tools for easy haret log reading couldnt be used). But mosci made a nice tool so gpio's can be traced with little effort. After the sequence of some pins you have to make a educated guess what the pin is for. This is not the hard part, so i think we can manage that. The real challenges are ahead ... chip handshake/making spi work ...

Link to comment
Share on other sites

Guest tjeerdos
Seems the Light and Proximity sensors have been fixed, see first post in i8000 thread. Here

hi,

where can i find the files. or aren't they ready for download jet? don't realy understand that

thanks

Link to comment
Share on other sites

http://o2droid.phj.hu/trac/browser/kern_oI.../sensor/optical

Maybe you can copy it in your droid files?

you can copy this files - but it will make zero changes

thats source-code wich needs to be compiled before it can be used in any usefull way.

simply wait until the official update comes arround or ... if you are able to do so -> compile a kernel & modules yourself

but even then you don't know if you have to make more changes too (e.g. which modules to load, in which order ... and so on)

... so just be patient until the devs advised you to do a update

Edited by mosci
Link to comment
Share on other sites

Guest tjeerdos
you can copy this files - but it will make zero changes

thats source-code wich needs to be compiled before it can be used in any usefull way.

simply wait until the official update comes arround or ... if you are able to do so -> compile a kernel & modules yourself

but even then you don't know if you have to make more changes too (e.g. which modules to load, in which order ... and so on)

... so just be patient until the devs advised you to do a update

okay thanks i think i have to be patient. i don't know how to do the things you just said haha.

tjeerdos

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.