Related
hello,
their seems to be a few posts on this being ported to BA recently. ow ive got linux running on my BA fairly well (havent got round to setting up gprs etc yet though but thats a different matter) and id be willing to try and get a port of android working, if someone can extract the 3 img files in the android sdk as ive not managed to do that yet ? anyone want to try and help or am i talking of a lost cause
ok, ill post this incase anyone is watching. i made some progress getting andriod running but i keep getting seg fault tryingto run it, any1 who could provide insight let me know pelase
Unfortunately I can't help you but I'll be keeping a VERY close eye on this thread!
Good luck, I'm sure there are a whole load of people who'd buy you a beer if you succeed.
Steve
glad to see someones watching . ill have another play around over weekend see what i can come up with
it will be interesting to see how android works on BA keep up with the good work
Nice.
I like my BA and I don't wont to change it until an open linux mobile is avaible (an open Iphone could be great).
Maybe a sub-forum called "Blue angel linux" could help.
I'm bored or a problem with the actual BA linux is the acces to the wifi chipset?
And this seems noise. And I don't want to pay for having linux on my BA!
http://www.a-la-mobile.com/news/press/pr080114.html
aperles said:
I'm bored or a problem with the actual BA linux is the acces to the wifi chipset?
Click to expand...
Click to collapse
Not the access, but a nice gui/setup.
remember linux is designed primarily for people who know what their doing. yes theirs guis now which help but you stil need command line to use linux properly. except on the iPhone and android from what ive seen
actually there was an earlier thread regarding android. and with 921+ adding 200+ views here, We bet there are people that are REALLY interested porting this.
hope we get it up and running.
anything for our BA.
even alternatives to WM6 are welcome.
well im not having a lot of look, it seems to be segfaulting pretty much constantly. think its down to the busybox shell though so im going to find a newer one and try that later, does anyone know what version of the arm feature set the BA uses. (because from reading http://benno.id.au/blog/2007/11/21/android-neo1973) android only seems to work on devices using ARMv5 featureset. whatever that means)
UPDATE: thats not a problem, the pxa263 in the BA is ARMv5TE so thats ok - gotta love wikipedia (http://en.wikipedia.org/wiki/XScale)
Further update: ok been reading up a bit more and im doing the risky thing of building my own kernel for android see if i can get round these damn segfaults
ok just thought id post up so people done think ive given up here . still havign issues compiling the linux kernel with the android addidtions. mainly because i ahvent got a proper linux machine at home (only virtual pc on this computer)...dont suppose anyone uses linux and has a decent knownledge of compiling kernels on here ??
DJ_Steve said:
ok just thought id post up so people done think ive given up here . still havign issues compiling the linux kernel with the android addidtions. mainly because i ahvent got a proper linux machine at home (only virtual pc on this computer)...dont suppose anyone uses linux and has a decent knownledge of compiling kernels on here ??
Click to expand...
Click to collapse
I've compiled kernels under Linux before, but not for an embedded system like the angel's.
Where did you get the tarballs for everything? And what distro of Linux did you install?
Really, real machine vs virtual machine, in this case, shouldn't matter. It might, but shouldn't.
not so much the fact im using a virtual machine, its the fact im only on a 2mb connection so downloading linux cd images takes ages and since debian is the only distro ive seen which has arm crosscompile tools that work that means 2 dvds or 9+cd images. most of the tarballs ive had to rip direct from the android sdk emulator. i could host them somewhere if someone wants to try and help me out getting a kernel running - after that i think most of android should fall into place on its own, but getting openbinder support in the kernels proving difficult
EDIT/UPDATE: ok just tried installing the arm crosscompiliers on my development dedicated server and it seems to be compiling a kernel as i type (hopefully) so looks to be some progress happening here
Been following your thread with interest.
I should be getting a new PDA from work, so then I could take the risk of bricking my trusty and battered Blue Angel.
Any chance you could post some links to the various bits you are using? Not a step by step (unless you have the time) but the starting points so others can attempt to duplicate your efforts in parallel?
Good luck - I'm rooting for you!
ok, im just tarballing up the files on my webserver now, didnt have any success with kernel, looks like im going to have to take the blueangel drivers etc from the kernel posted on handhelds.org and manually merge the config files into the android kernel image to get it to compile. unless anyone can suggest a way to do that easily (windows or linux routine i dont mind)
the main sites ive used to help out ive listed below
http://benno.id.au/blog/ << somewhere on their theirs a link to the android root filesystem image. (http://benno.id.au/android/system.tar.gz and http://benno.id.au/android/data.tar.gz)
http://nemustech.blogspot.com/2007/12/android-porting-to-real-target-hw.html
http://euedge.com/blog/2007/12/06/google-android-runs-on-sharp-zaurus-sl-c760/
http://handhelds.org/moin/moin.cgi/BlueAngelKernel
the three above above links help even though their not scriptly related to android on blueangel
the rest of the files are in http://radiodmp.net/android-files/ - the 365mb file contains the 2 arm cross compilers and also both the newest blueangel linux kernel and the android kernel - as said above these need merging (android kernel needs to be the one that is the final kernel as its newer i believe
edit: ive just put the system and data tars linked above into the folder on my server also to save people time.
hope that helps
if anyone wants any help drop me a message and ill try and help out. will of course keep trying to sort it myself too
Any update on this?
Actively watching this thread and just wanted to know. I'd love to be able to play with Android.
good to see ppl interested. ive not had time to try and merge the kernels yet, hopefulyl might get chance this week
DJ_Steve said:
good to see ppl interested.
Click to expand...
Click to collapse
Still watching, still interested!
Keep it up.
Steve
ok managed to hack together the two kernels, compiling it as i type - hopefully it'll workon my BA
Hi, yesterday i was trying to launch android on my BA and i DID IT!
It works like ****:
Touchscreen doesn't work (you can activate list scrolling by pushing it on the side)
Some buttons don't work
No sound
Navigation:
D-pad (left, right, up, down)
Enter (on the keyboard, since D-Pad center doesn't work)
!WARNING! there is no end call and back buttons, you can't exit applications
How to? Here is the tutorial:
Create a folder on your memory card
Get the latest HaRET from here http://handhelds.org/~koconnor/haret/
Get the latest zImage from here http://www.angstrom-distribution.org/unstable/autobuild/htcblueangel/
(i use zImage-2.6.21-hh20-r16-htcblueangel.bin)
Rename it to zImage
Put that default.txt
Code:
set kernel zImage
set initrd "initrd-android.gz"
set CMDLINE "rootdelay=3 root=/dev/ram0 ramdisk_size=23504 init=/linuxrc"
boot
Now you need the system - Android
Get that: http://it029000.massey.ac.nz/vogue/initrd-android
Don't forget to rename it to initrd-android.gz
I've got it from here http://it029000.massey.ac.nz/vogue/
it stays in jumping to kernel... i followd the steps above, did you copy pasted the command correctly??
rafyvitto said:
it stays in jumping to kernel... i followd the steps above, did you copy pasted the command correctly??
Click to expand...
Click to collapse
Try different kernel. It works for me
GVG said:
Try different kernel. It works for me
Click to expand...
Click to collapse
Could you please tell us how did you install android on Blue Angel? Procedures and everything else. And also your opinion about it's performance. thank you very much
blackout_pt said:
Could you please tell us how did you install android on Blue Angel? Procedures and everything else. And also your opinion about it's performance. thank you very much
Click to expand...
Click to collapse
Just launch Haret.exe
Speed... hm... Almost like WM6
a lot slower than wm6 the android image should be tweaked in order to have proper drivers for touchscreen keys and sound
wow...very cool, I'll be looking for updates (if there are any)
hi friends,
i tested android and seems a good toy
i did make a rar with all files needed, you need only to extract to SD and run haret
Code:
http://rapidshare.com/files/147524450/android.rar.html
i'm really interested to go further on android.
about my tests, i can conclude two things:
- D-pad works, but not very well
- Touch screen is not working, but i know it detect moves on it
(try to dpad a icon, then touch the touch-screen, you ll see)
I'm not a expert on pocket pc, but i have my skills.
I found an other thing, hardware specification.
Code:
http://www.handhelds.org/moin/moin.cgi/BlueAngelHardware
if the information is right, the touchscreen is from the same family that the vogue one.
To continue this adventure, i need some lights. I know we have a developer from the kernel/Opie/GPE in this forum. If you are him, i need some lights about your work.
The other thing, i'll try to do is asking help to vogue/kaiser android project, to give me some lights how they touchscreen work.
The last thing. All the help is appreciated, everybody is invited in this project and all the help is welcome. And i really need it lol
udapte (23/9/2008)
Well i talk do vogue android project man, and the answer from him is simple. His work was only to port kernel to vogue platform. I will have to find who made the one we are using.
The touchscreen is detected, but somehow it doesn't work.
i have failed .
my BA get a FlashDIsk and ramdisk in WM6 enrironment..
when i run haret ....
after jumping to kernal
an error occur
can't mount SDcard .it's halt..
why...
How about your work? I'm working on this task also. Need more information to make it working. Could you give me some patches for BA's kernel.
Also the SC Card Message, any adivice o workaround?
w0w...
it runs on my BA. Great!
However I cant do anything inside. But thanks to all of you that make this possible.
I'm waiting for the next release, hope it will run faster, and all get better.
Thanks.
Is anything happening with this?
Any news?
Is vogue version working? I have try to build a kernel for BA but false to boot
Will try and report later....
kernel
I have A LOT of, like everything I could find, files to load linux on the Blue Angel. Angstrom, Familiar, QT...somethingsomething... Anyway, it works well except the wireless which I think should work until the thing goes into standby. Would the zImage/initrid files or any of the others help? I'd like to help ya get this working, I think most of the works been done. I must say, however, I am just learning about how this stuff works. I can't code, but I have a BA, lots of experience repairing hardware like ppcs and I really would love the chance to finally give back to this wonderful community after they've given me so much.
It would be great to get this working. It would give my pda2k a whole new lease on life.
any updates on this?
Thanks
so, any news? android would be quite nice.
i concur. i'd liketo see a android on the blueangel, why isnt there one? linux runs fine on it, theres an older android that supposidly boots on it.
cmon somebody make the damn thing work.
This thread is for development related to the Google Android OS running on the CDMA version of the Touch Pro 2.
Special Thanks to all of the GSM developers for taking care of the hard stuff
Last Update Date: 2/27/2010 11:45 PM EST
Current Download Link: http://www.megaupload.com/?d=T0RSJ0AW
For those who still can't get wifi to load with the most recent upload please try the 2 suggestions below:
-Ensure wifi is started in WM prior to initiating haret
-Turn off security on your wireless connection
Instructions:
1) Delete existing android files (ensure data.img is deleted)
2) Extract files from zip onto root of SD card
Use this at your own risk. I doubt any harm will come to you or your phone, but if you get hit by a bus while loading android don't blame me.
Please see post #2 for zImage Downloads, FAQ, Detailed Status and Change Log
Detailed Status and Change Log
Upcoming Changes:
-CDMA Data
-SMS
-Speaker w/o calling prior to loading Haret
Change Log:
2/27/2010 11:45 PM EST
Issues with previous upload. Please try new link.
2/27/2010 10:00 PM EST
-autobuild zImage and my modified rootfs to use CDMA radio
-WIFI thanks to MrPippy
2/27/2010 2:22 PM EST
-Many many new enhancements from the current repository. Still no wifi, data or BT, but some great UI and other hardware updates. Special thanks to phhusson, mrpippy and the rest of the GSM guys for their constant changes!
1/25/2010 1:10 AM EST
-Mic is now functional in calls w/o having to initiate a call in WM
-Power management is now active, screen will turn black
-Keypad response on dial pad has been greatly improved
-Phone can now be fully powered off by holding end key and selecting "Power off"
Please use full download link in post #1
1/12/2010 11:24 PM EST - Updated Keymapping
Working
CDMA Radio - Ability to make and receive calls
Mic
Keyboard
Key Mapping
Power Management
Screen Rotation
WIFI
Not working:
CDMA Data
Speaker
GPS
Camera
Bluetooth
Much Much more...
Notes:
-In order to fully utilize mic / speaker you must place a call in WM prior to loading haret. Easiest method is to call your VM then while connected load haret. If you do not place a call prior to loading haret only your mic will function.
-If you have trouble registering onto your network follow the instructions below:
Go to Settings
Select "Wireless & networks"
Select "Mobile Networks"
Select "Network operators"
(Let the phone search)
Select "Select automatically"
You should now receive a message stating that you have been "Registered on Network"
If this does not work the first time, try it again.
For anyone who is interested in setting up their own dev environment follow my guide below.
Even if you don't have any programming expeierce you may have fun exploring the inner workings of Android.
Quick and Dirty Install Guide to setting up local dev environment by 95-Civic:
1) If you don't already have a linux box setup I would suggest downloading VM ware and finding a free image of Ubuntu.
2) From there head over to
http://source.android.com/download which should walk you through the installation of all packages required to retrieve and compile the source code.
3) It will take several hours to pull in the entire repository. Once download you do not need to compile the android code in order in order to build the kernel, we will use the prebuilt directory
4) Once you have copied the repository you will want to get a copy of linux-on-qualcomm. cd into the android source directory
5) type:
git clone git://gitorious.org/linux-on-qualcomm-s-msm/linux-msm.git
this process may take several hours depending on your internet connection speed
6) Copy the prebuilt directory from the android source over into the new directory created by the command above (linux-msm)
cp -r prebuilt ./linux-msm
7) CD into the linux-msm directory
8 ) Run the following command
make ARCH=arm CROSS_COMPILE=prebuilt/linux-x86/toolchain/arm-eabi-4.3.1/bin/arm-eabi- htc_msm_android_defconfig
9) If no errors are listed you will receive the following message: "configuration written to .config". Continue to step 10
10) Run
make ARCH=arm CROSS_COMPILE=prebuilt/linux-x86/toolchain/arm-eabi-4.3.1/bin/arm-eabi- zImage
11) When complete (if compiled successfully) you will now brand new zImage located in ./arch/arm/boot/zImage
As long as you use the rootfs.img and system.sqsh that I provided in the zip file you should have access to the CDMA radio to make and receive calls. In some cases you will not have access to the radio depending on the default configurations in the htc_msm_android_defconfig file.
Custom config is attached. You will need to unzip and copy the attached file into the linux-msm/arch/arm/configs directory. When running step 8 replace htc_msm_android_defconfig with htc_tp2_cdma_defconfig
This will not have any of the changes, additions, and tweaks I've made to the linux-msm source. However it should give you a fresh bootable image and a great place to start. I would like to create a gitorious clone in the near future but right now any free time is better spent on data.
Happy coding and please feel free to PM with any questions.
Just wanted to thank you for your effort, this is very exciting! Are you planning on following this all the way through until everything is functional and it can flashed on to the phone?
95-civic said:
Working
CDMA Radio - Ability to make and receive calls
Keyboard
Key Mapping
Not working
Just about everything else
Wifi
CDMA Data
Mapping of the End key (I'll post an updated image tomorrow with the correct mapping. Easy fix)
Speaker and Mic (unless you make a call from WM prior to loading Haret)
GPS
Camera
Bluetooth
Many more...
Click to expand...
Click to collapse
I have a GSM phone I see your working on the end key mapping for cdma.
I did ask in the bounty thread about learning how to map and fix end key for tilt 2 gsm your compiled zimage wont work for my gsm phone with the fix will it?
Looking forward to testing your work Civic, great job so far and looking forward to future updates.
Craig
Greatness
Way to go Civic, this is extremely exciting. I have been quite envious of the RAPH800 Android functionality (turned my RAPH800 into insurance for the RHOD400).
I have you bookmarked, will continue to test updated builds and report back.
On this one, nothing new to report on errors - no data, but I did connect to sprint network. I had called my VM before booting, but I had no mic or speaker, will try again.
Thanks and great job!
Great Job
Hi Civic,
I just wanted to thank you for your work, flashed the rom last night, this is the best build thus far.
I did try out your version of XDAndroid and it seems a bit more sluggish/buggy than ones I have used out of the Topaz/TD2 thread.
CDMA radio works for me in both versions.
Obviously No Data or SMS.
One good way to speed up the install on the slower SD cards is to put the card in a memory card reader on a PC and run windows defragmenter on the card.
This is after you have booted into android the first time so you have the 256MB data.img already generated. I personally noticed a speed/fluidity improvement on my 8gb Class 2 SD card (came with BB Storm), however your mileage may vary.
defragmenting works on regular HDD because if a file is spread across different sections of the disk, it takes time to move the head and read those parts of the disk.
defragmenting won't make any difference with solid state media because there are no moving parts and its access time is virtually 0. it doesn't matter if a block of a file is on sector 0 or on sector 308563434, solid state drives access them all with exactly the same speed.
defragmenting on solid state media is a snake oil recipe.
torn8o said:
I have a GSM phone I see your working on the end key mapping for cdma.
I did ask in the bounty thread about learning how to map and fix end key for tilt 2 gsm your compiled zimage wont work for my gsm phone with the fix will it?
Click to expand...
Click to collapse
Shakes head, you do realize why this thread was started. Not to work on GSM, but for CDMA version. There are a TON of GSM android threads right now, but no real CDMA thread.
And 95-civic... THANK YOU!!!
Thanks been waiting for this kind of thread.
I loved using Android on my XV6800 but once I switch to TP2 I lost access to the marketplace (still waiting to see if someone can get wifi working). So I cannot wait to try this for TP2!
Just out of curiosity, what is your end goal? A fully functional flushable android rom (which would be great) or a fully functional harret?
---and I am more that willing to donate some cash for the final result
klynch_gdd said:
Shakes head, you do realize why this thread was started. Not to work on GSM, but for CDMA version. There are a TON of GSM android threads right now, but no real CDMA thread.
And 95-civic... THANK YOU!!!
Click to expand...
Click to collapse
I do realize this is a cdma thread you must have missed this statement
I did ask in the bounty thread about learning how to map and fix end key for tilt 2 gsm your compiled zimage wont work for my gsm phone with the fix will it?
I asked here because an option to help was offered in the prior posts in another thread.
Also, is it possible to get the gsensor working. I find pulling out the stylus to activate landscape to be somewhat annoying. Is that just a temporary thing, will we eventually get to use of the gsensor and the keyboard slide activating the landscape?
It's amazing how such great progress can be made and yet someone has to ask about the gsensor working. Baby steps man. Speakers and Mic are very important. Then data and SMS. Once the basic phone functions are there, I'm sure Civic or someone else will start attacking things like Gsensor. Sorry, not trying to be rude but focus on what's more important and don't worry about the smaller stuff. Kudos Civic. Well done.
On a side note, I also would like to know if you plan to take this all the way to the finished product with a flashable ROM. Either way, you can expect a donation in the next few weeks from me. (Christmas wiped me out!)
Thank you so much!! I love this phone, and I think android on it will blow the nexus one away. I cant stand on screen keyboards!! Keep up the good work and you will be getting my donations and many many thanks!!
new zImage Available
The most recent zImage can be found in post #2. Unzip the zImage to your SD root and over write existing file. Don't forget to delete the data.img file as well.
Not a huge change but I've fixed the key mapping. I've had less than an combined hour over the past 48 hours to get in front of my home computer due to long days at the office this week, next step is to tackle the speaker / mic issue.
Enjoy!
torn8o said:
I have a GSM phone I see your working on the end key mapping for cdma.
I did ask in the bounty thread about learning how to map and fix end key for tilt 2 gsm your compiled zimage wont work for my gsm phone with the fix will it?
Click to expand...
Click to collapse
I don't own a GSM phone so I can't confirm. Try the most recent zImage in post #2, just remove the ".95-civic" from the end of the file and overwrite you existing zImage.
BTW the ".95-civic" will be removed in the next build. Obviously it's just a simple renaming of the file, but we'll call it .CDMATP2 or something along those lines.
drb115 said:
Just out of curiosity, what is your end goal? A fully functional flushable android rom (which would be great) or a fully functional harret?
---and I am more that willing to donate some cash for the final result
Click to expand...
Click to collapse
Would you like me to put a project charter together? lol... j/k
For now I will continue with Harret, but ultimately we all would love to have a flashable rom to utilize the phone's internal memory. Since just above every other htc phone is ahead of us with their android ports, I'm hoping someone figures this part out by the time we catch up!
drb115 said:
Also, is it possible to get the gsensor working. I find pulling out the stylus to activate landscape to be somewhat annoying. Is that just a temporary thing, will we eventually get to use of the gsensor and the keyboard slide activating the landscape?
Click to expand...
Click to collapse
As mentioned in another reply this is low priority on the list, however if you could get everyone else in the group to agree that this is more important that the speaker / mic I'll gladly do this for you.
I am a dangerous noob, know enough to be dangerous literally. I am in search of the easiest to use software to build ROM's.
What I plan to do: Cook a Android ROM for the TP2 that is CDMA compatible.
The questions I have are:
1. What kitchen do you recommend to do this?
2. Is there software to import a .cab to compile a new ROM?
3. Is there software to import a custom ROM and start work from there?
( I would like to use the GSM rom, but rewrite it to CDMA, as most of the GSM drivers are the same)
I think I can get everything I need by using the existing GSM android TP2 cab( thanks to all here for making that), the SPRINT hero ROM (http://developer.htc.com/), and the A rom of the sprint TP2. ( I actually got the GSM android to see the sprint network lastnight with some reg edits)
I have searched here and found tons of programs, but almost all were out of date or 404 errors. Basicly my searches are slow since the servers are loaded up here, and i cannot mine the info i need. If someone could please point me in the right direction it would be GREAT.
Oh yes, I am using windows, but can setup a linux box if needed. or I can use a VMware image if needed, but I would rather build as much as possible in windows.
Please point me in the right direction!
Thank you
I hope all this is just a little bit interesting for some developers because I can't do any further investigations on ANDROID because my device is broken. At the moment it's on the way and I hope I will get a change of my broken HD2. I have summarized some more or less insteresting facts and I hope someone of you will think about all this informations and can work with them.
First at all: I'm not a developer but I have done some search on ANDROID and logged and logged and logged it again. All this is just a collection of facts and results of compare log files.
When you disassemble some Files within Android, you will see that something will not work because it can't. Let me start with the init.rc what is missing or might be wrong:
1. MISSING FOR BLUETOOTH:
Code:
# create mountpoints
mkdir /mnt_data/download 0777 root system
2. WRONG?
Code:
chmod 0666 /dev/ttyHS1
chown root radio /proc/cmdline
chmod 666 /proc/cmdline
There is no ttyHS1 device within the ANDROID. Can't find it.
3. NOT SURE
rfkill is seems not working. Recommendation on the website:
http://www.gitorious.org/openaos-te...5f360fec4c21c1e06d145a5fe?diffmode=sidebyside
Code:
chmod 0666 /sys/devices/platform/wifi_bt/bt_enable 0
write /sys/devices/platform/wifi_bt/bt_enable 1
but based on ANDROID Developer FAQ it should be:
Code:
chmod 0666 /sys/modules/board_[platform]/parameters/bluetooth_power_on
write /sys/modules/board_[platform]/parameters/bluetooth_power_on 1
and this MUST also done after the change:
Code:
on property:persist.service.bluetoothd.enable=0
write /sys/modules/board_htcleo/parameters/bluetooth_power_on 0
...depend of the settings it also could be:
Code:
write /sys/devices/platform/wifi_bt/bt_enable 0
on property:persist.service.bluetoothd.enable=1
write /sys/modules/board_htcleo/parameters/bluetooth_power_on 1
...depend of the settings it also could be:
Code:
write /sys/devices/platform/wifi_bt/bt_enable 1
Also interesting is the command write which is used a lot of times by the init.rc. I don't know where this command is located. But if you open a SHELL on Android and try to "write" something you will see that this command is not available. Can someone explain how this will work when this command is not available????
4. WRONG!
Code:
chmod 666 /dev/uinput
chmod 666 /etc/bluez/audio.conf
chmod 666 /etc/bluez/hcid.conf
chmod 666 /etc/bluez/input.conf
On the one hand this path is not existing and on the second hand the hcid.conf is also not existing. If you take a look only within /etc you will see that /etc/bluetooth is only existing.
5. BT INITIALIZATION
Code:
service hciattach /system/bin/brcm_patchram_plus --enable_hci –enable_lpm --baudrate 3000000 --patchram /etc/firmware/bcm4329.hcd /dev/ttyHS0
user bluetooth
group bluetooth net_bt_admin
disabled
This is also not working at all. If you try to run this command via the shell nothing will happens. And if you need to load the firmware into the device you need also setup this device by nvram.txt which you can see within the bluetooth.c file. The nvram.txt is important to get a valid MAC Address from the hardware. If you take a look into the source code of the BCM4329 you will see additional informations about this.
The second problem is the value of 3000000. This is to small. If you want to work with head set than a value of 4000000 is minimum required. From my point of view this initialization should be:
Code:
service hciattach /system/bin/logwrapper /system/bin/hciattach -s 57600 /dev/ttyHS0 any 4000000 flow
The value 57600 is the minimum value for initialize bluetooth and it could be that this value will downsize the standby drain. Not sure, just an idea.
Why? Lets take a look into the main.conf or hcid.conf:
Code:
# What value should be assumed for the adapter Powered property when
# SetProperty(Powered, ...) hasn't been called yet. Defaults to true
InitiallyPowered = true
# Remember the previously stored Powered state when initializing adapters
RememberPowered = true
This was the reason why I think the initialization speed "...-s 57000 /dev..." should be lowerd down which might also solve the battery drain issue. Again, not sure - just an idea.
Btw, if you open the ADB shell and try hciconfig, hciattach or hcitools non of this are working because there is no Bluetooth Adapter even if you have BT enabled. This tools are requried for BT analyse, test and command options. You can call each of the files within the Shell but whatever you try to do you it will fail because BT is not enabled. Try to run rfkill which could initiate a reset on the BT device. If you try to rfkill ttyHS0 which is the BT adapter on HD2 device this will not work. From my point of view all this problems are not only related to the kernel.
6. TAKE A LOOK INTO THE init.htcleo.rc
Code:
# Make sure we startup btld before hcid
# Set target address to emulator host loopback IF
# Limit baudrate to 460800 to ensure reliable uart operation
service btld /system/bin/logwrapper /system/bin/btld -hwtun 10.0.2.2 -hb 460800 3000000 -lpm 1
# service btld /system/bin/logwrapper /system/bin/btld -lpm 1 -hb 3000000
Not sure what will run first. The init.rc or the init.htcleo.rc. If the init.rc will run first this could be also a problem. Btw, the first value is 460800. From my point of view this is too much for initialization.
7. WiFi INITIALIZATION
Just an example but if you do a Google search for "BCM4329 nvram.txt" you will get more than 3 links. Let me show here an example:
http://android-wifi-tether.googlecode.com/svn-history/r465/trunk/res/raw/tether_edify
Search for Value 4329 and you will see SAMSUNG Device bla, bla – don't know from top of my head:
Code:
!file_exists("/sdcard/android.tether/bcm4329.bin") && ( module_loaded("dhd") || log(insmod("/lib/modules/dhd.ko", "firmware_path=/system/etc/wifi/bcm4329_mfg.bin nvram_path=/system/etc/wifi/nvram_mfg.txt"), "Loading dhd.ko module<br>(bcm4329_mfg.bin from /system/etc/wifi/)"); );
Hmm... That was the reason why I grabbed the SAMSUNG i9000 from a friend of me and double checked the device. If you take a look into the /etc/wifi you will see the nvram.txt. I'm not sure how this will be loaded into the device but the i9000 has the same BCM4329 Chipset.
Now let us take a look into the wifi.c for QUALCOMM devices which is also valid for the HD2:
http://gitorious.org/linux-on-qualc...f8dffe668c0448/libhardware_legacy/wifi/wifi.c
Code:
Line 61: Take a look. Nothing of this is existing on the HD2
Line 71: there is no wlan.ko on the HD2
But now, where the hell the MAC Address is stored for the WIFI Adapter? Just take a look at this location:
Code:
sys/module/board_htcleo/parameters/bdaddress
or use this:
Code:
/system/sysroot/module/board_htcleo/parameters/bdaddress
If you check this file you will see there your current MAC Address of the WIFI device. The stupid MAC for the BT device seems not stored on the device. And this is the point where I guess to need the fu***ing nvram.txt.
I have done a search for some BCM files and found something interesting which is attached as "Broadcom Files.7z." There are some (!) more or less firmware files within (?) and also the famous nvram.txt
For additional informations about WiFi and more just open the wifi_suplicant within the /system/bin directory with a simple text editor and browse down to the end. There you will see also a lot of interesting settings for the WiFi environment.
8. W.t.F. IS THIS STUPID NVRAM.TXT?
Download attached Broadcom.7z and check the txt file within. If you open the file you will see the nearly same content as within the
Code:
/etc/calibration
file.
But this file you can ignore on your HD2 device. Delete it, rename it – do whatever you want and you will see no changes on the device. The more interesting thing is within
Code:
/sys/calibration
Huhhhh...! The same file but less values. But where does it come from??? Currently I don't know.
It seems that the nvram.txt is as same as like a BIOS for the device. The BCM4329 is a BT AND WiFi Chip within one CHIP. It might be wrong but I guess this is the easy explanation for this.
And because of this the thing can't work. First it needs to load the BIOS (nvram.txt) and then it needs the OS for it (BCM4329 Firmware).
Okay here is something by reading and following your examples:
sys/module/board_htcleo/parameters/bdaddress
That lines exists in the current NAND Android roms, but this line:
/system/sysroot/module/board_htcleo/parameters/bdaddress
doesnt exist, not in Rafs rom or in imilka's 0.1 GB sense rom.
But here is my key interest: "bdaddress" is where the BLUETOOTH MAC Address is!
Another interesting thing, in imilka's 0.1 GB Sense rom, I can change this to whatever I want and it Sticks till I reboot, but in Rafs it does not.
Key Question, How do we make this file KEEP the changes we make to it??? I know its a dirty fix but none the less its a FIX!! So anyone got a clue?!??
First of all there is a WRONG that is big like an house
the init.rc "syntax" is not shell syntax.
so as example, command "write" will not work in shell... but only in init.rc
I see also a lot of confusions about stock froyo/gingerbread stuff and sense stuff.
Example: Sense uses it's own stuff for BT so a clean init.rc for sense is really different from the one for a non-sense build.
Also some stuff/commands needs to be changed/replaced to have them working with our hd2 kernel.
I have no time now but really this posts is about 30 different things that cannot be explained all togheter.
My suggestion is to google for "android init syntax" and start from there understanding all the android boot process and the android init syntax.
About the wifi mac address.
The wifi mac address is "read" from the libhardware_legacy.so
normmaly this lib reads the mac address in /etc/calibration
this file is a "kernel" file so you are not able to change it.
You can use a modified libhardware_legacy.so that reads the mac address in /system/etc/calibration so you can change it, as I did on my builds where you can change the wifi mac address.
Unfortunately the modified libs causes other issues like gps not working.
---------------------------------------------------------------------------
About the problem that you cannot write permanetly the changes on stuff inside the folders
/
/etc
/proc
/sys
and so on.. this is because those folders are the "kernel" that normally is read-only
you can make it write enabled but it's not a safe way to proceed...
so is there a chance to fix the issue with the bluetooth mac?!
would be important for me
(can't use my parrot car kit with my wifes hd2 because of the same mac adress )
rafpigna said:
First of all there is a WRONG that is big like an house
the init.rc "syntax" is not shell syntax.
so as example, command "write" will not work in shell... but only in init.rc
I see also a lot of confusions about stock froyo/gingerbread stuff and sense stuff.
Example: Sense uses it's own stuff for BT so a clean init.rc for sense is really different from the one for a non-sense build.
Also some stuff/commands needs to be changed/replaced to have them working with our hd2 kernel.
I have no time now but really this posts is about 30 different things that cannot be explained all togheter.
My suggestion is to google for "android init syntax" and start from there understanding all the android boot process and the android init syntax.
Click to expand...
Click to collapse
Thanks mate! The problem is that I have no clue how to do it but I hope someone outside who has more experience with all this knows what to do.
Btw, I have had also tried to do a simple test with this "write" command by fill a line within /etc/test and also /proc/test which fails. Usually I added some lines into the init.rc to see if this will work.
But I'm not sure if I have had something wrong.
rafpigna said:
About the wifi mac address.
The wifi mac address is "read" from the libhardware_legacy.so
normmaly this lib reads the mac address in /etc/calibration
Click to expand...
Click to collapse
Sorry, but this is not true. Check this:
http://developer.android.com/reference/android/net/wifi/WifiInfo.html
If you check this from Android SDK you will see that the wpa_supplicant is responsible for this. And this would be O.K. if you also check the BCM4329 source code.
First the CHIPSET will be initiated and prepared by the firmware and the nvram.txt and after that the wpa_supplicant do the rest.
How this exactly will work - sorry, too less coding knowledge
A good thing is it to compare the MAC & BT issue with the i9000 devices and Sony X10. The Sony X10 has the same QUALCOM chipset as the HD2.
Here are the files from the original Desire HD 1.8x.
The initrd.zip contains is the original file and the initrd~.7z is the extracted who is interested to read and compare.
see this http://gitorious.org/linux-on-wince...mmit/ce69804632e64b397758c1c9835f06efd0c8cb54
in file arch/arm/mach-msm/board-htcleo.c i see from markinus some changes to file bdaddress.but it is not in the main git tree we use for hd2 kernel
maybe someone kernel developer can see it and make a kernel for testing;
clio94 said:
see this http://gitorious.org/linux-on-wince...mmit/ce69804632e64b397758c1c9835f06efd0c8cb54
in file arch/arm/mach-msm/board-htcleo.c i see from markinus some changes to file bdaddress.but it is not in the main git tree we use for hd2 kernel
maybe someone kernel developer can see it and make a kernel for testing;
Click to expand...
Click to collapse
Looks good, but this is not valid for HD2. This is HTC Tattoo. If you check this code you will see "akm8973".
Damn!
http://nagaraj-embedded.blogspot.com/2011/02/guide-on-adding-wifi-drivers-on-android.html
and
http://www.jetdroid.org/forum/viewtopic.php?f=78&t=456&start=20#p4502
Can someone double check this???? From my point of view this looks quite good...
MrT69 said:
Sorry, but this is not true. Check this:
http://developer.android.com/reference/android/net/wifi/WifiInfo.html
If you check this from Android SDK you will see that the wpa_supplicant is responsible for this. And this would be O.K. if you also check the BCM4329 source code.
First the CHIPSET will be initiated and prepared by the firmware and the nvram.txt and after that the wpa_supplicant do the rest.
How this exactly will work - sorry, too less coding knowledge
A good thing is it to compare the MAC & BT issue with the i9000 devices and Sony X10. The Sony X10 has the same QUALCOM chipset as the HD2.
Click to expand...
Click to collapse
I'm wrong?
Sorry to say, I'm not an andorid guru but maybe I have a little bit more knoledge and trust me in our case, at least with our builds, the mac address is read from the calibration file.
So how is possible that in my builds you can change the wifi mac?
I just take yor desired wifi mac, write it in the /system/etc/calibration file and replace the libhardware_legacy.so that will read from that instead of /etc/calibration
MrT69 said:
Thanks mate! The problem is that I have no clue how to do it but I hope someone outside who has more experience with all this knows what to do.
Btw, I have had also tried to do a simple test with this "write" command by fill a line within /etc/test and also /proc/test which fails. Usually I added some lines into the init.rc to see if this will work.
But I'm not sure if I have had something wrong.
Click to expand...
Click to collapse
Already said... init.rc syntax is not shell syntax!!!
Anyway.. I still miss the purpose of this thread....
Just the first two google search links appearing with a simple "android init.rc" search
http://www.androidenea.com/2009/08/init-process-and-initrc.html
http://elinux.org/Android_Booting
Read that and something will be clearer.
rafpigna said:
I'm wrong?
Sorry to say, I'm not an andorid guru but maybe I have a little bit more knoledge and trust me in our case, at least with our builds, the mac address is read from the calibration file.
Click to expand...
Click to collapse
It might be that I have had something missunterstand but I only want to say by default (!) the MAC Address is not read from the calibration file by ANDROID. Of cause I have had tested your solution and it's working.
So how is possible that in my builds you can change the wifi mac?
I just take yor desired wifi mac, write it in the /system/etc/calibration file and replace the libhardware_legacy.so that will read from that instead of /etc/calibration
Click to expand...
Click to collapse
I know that the MAC Address could be changed within this way. I hope you don't understand it within the wrong way but from my point of view this is only a patch solution. Because of the fact that the BT & WiFi Chip is ONE (!) chip within HD2 there must be an other solution to read and get the MAC address for WiFi AND BT.
Already said... init.rc syntax is not shell syntax!!!
Click to expand...
Click to collapse
I only was asking why and where it was not working. In the mentime I know it because of your feedback. But I have add some lines into the init.rc and the files and changes was not written to the device. That was the reason why I was asking.
Anyway.. I still miss the purpose of this thread....
Click to expand...
Click to collapse
Hope to find some people who will help to fix all this issues and on the second hand I hope to find a solution for the BT and WiFi MAC to get it from the device.
It is proper time to make an open discussion about the 2.2.1 rom and more tweaks closer to HD2 reveal in the community.
MrT69 said:
I know that the MAC Address could be changed within this way. I hope you don't understand it within the wrong way but from my point of view this is only a patch solution. Because of the fact that the BT & WiFi Chip is ONE (!) chip within HD2 there must be an other solution to read and get the MAC address for WiFi AND BT.
Click to expand...
Click to collapse
maybe this is wrong but it is extremely good that in sense roms,you can change at any time wifi mac address.in my city municipality have free wifi hotspot but after sometime reads your wifi mac address and cut the connection for a time.so with dynamic wifi address i can be almost all time everywhere online and this saves me from a slow (because i live in a small greek city and 3g connection is not everywhere) data edge connection.