Android on Vogue [ramdisk thread], One Build, Two Phones Complete. FIXED - Touch CDMA General

Here's where I'll try and keep everyone updated on the rootfs img; Pmos has mostly put this together with help from enatefox and a little from me (very little lol)
The current bundle is available on google code. HERE
Currently;
Contains two zimage files, one for the old keymap and one for the new, just rename whichever you like to zimage
Supports both kaiser and vogue builds;
It supports all old and new builds, so whether it's based on squashfs (system.sqsh) or cramfs (system.img) it will boot properly.
09-07 package changelog;
Now supports both vogue and kaiser 100%. This means you don't need a special build for your kaiser to enable wifi, automatically detects the vogue or kaiser on boot and enables or disables wifi by default. Great work PMOS!!
Same as before, includes both keymaps, download, copy to device and rename zimageoldbuttons or zimagenewbuttons to zimage, boot and enjoy!
09-08- Sorry guys, fixed files uploading now.
09-06 package changelog;
Changes over the current repository version are:
- Kaiser detection at init
- separate *.init.rc files for kaiser and vogue
- userinit.sh/user.conf system (adapted from the dream userinit.sh system).
- separate user.conf files for each build type (hero, rogers, ion)
- misc tweaks configurable in the *.conf files
- compcache and swap configurable in the *.conf files
- /bin/ramzswap removed (included in userinit.sh)
- dos2unix conversion of *.conf files
- renice script included in userinit.sh and selectable in *.conf

mssmison said:
Here's where I'll try and keep everyone updated on the rootfs img; Pmos has mostly put this together with help from enatefox and a little from me (very little lol)
The current bundle is available on google code. HERE
Currently;
Contains two zimage files, one for the old keymap and one for the new, just rename whichever you like to zimage
Supports both kaiser and vogue builds; (work in progress) the idea is go get any system build to work on either phone, it's a work in progress thus far,
It supports all old and new builds, so whether it's based on squashfs (system.sqsh) or cramfs (system.img) it will boot properly.
Click to expand...
Click to collapse
This will probably be "reset" to the current codebase and changes applied to that. Much cleaner that way.
Current state is a bit messy. Too many different versions around.
Anyway, the changes aren't substantial, yet.

Thanks for keeping my userinit in there.

zenulator said:
Thanks for keeping my userinit in there.
Click to expand...
Click to collapse
Haven't done anything yet zen.
Was making modifications "on top" of your modifications anyway...
As we discussed before, calling a script in the sdcard at init time makes it easy to experiment new things at development time.
On the other hand, It's a security hole, and makes it easy for users to mess up things when they open the script in windows notepad and save it with windows formating.
Don't really have a strong opinion on this.
What's your take?

pmos69 said:
Haven't done anything yet zen.
Was making modifications "on top" of your modifications anyway...
As we discussed before, calling a script in the sdcard at init time makes it easy to experiment new things at development time.
On the other hand, It's a security hole, and makes it easy for users to mess up things when they open the script in windows notepad and save it with windows formating.
Don't really have a strong opinion on this.
What's your take?
Click to expand...
Click to collapse
Well before I put out this version of userinit. I had another version based off the g1 userinit.conf. Basically rootfs calls userinit.sh and userinit.sh checks userinit.conf to get it's settings. That way you keep userinit.conf as a plain text file and have something like the following inside it.
compcache=1
compache_disk_size=XXXX
linuxswap=0
linuxswap_size=XXXXX
renice.txt=0
ascii_art=0
ascii_art_file=zen
and just change the values in userinit.conf from 0=off to 1=on and userinit.sh interprets those values and executes them. And also I'm not sold on the compcache disk size being that large. I ran the latest hero with out compcache or swap and it still seemed just as fast. The only problem I had was reload time for rosie because it gets pushed out of memory. And there is no need for compcache disksize to be set that high for cupcake/donut builds because it doesn't need it. So maybe after rootfs auto detects builds it will load the correct userinit to set up compcache/swap with settings specific to the build.

zenulator said:
Well before I put out this version of userinit. I had another version based off the g1 userinit.conf. Basically rootfs calls userinit.sh and userinit.sh checks userinit.conf to get it's settings. That way you keep userinit.conf as a plain text file and have something like the following inside it.
compcache=1
compache_disk_size=XXXX
linuxswap=0
linuxswap_size=XXXXX
renice.txt=0
ascii_art=0
ascii_art_file=zen
and just change the values in userinit.conf from 0=off to 1=on and userinit.sh interprets those values and executes them. And also I'm not sold on the compcache disk size being that large. I ran the latest hero with out compcache or swap and it still seemed just as fast. The only problem I had was reload time for rosie because it gets pushed out of memory. And there is no need for compcache disksize to be set that high for cupcake/donut builds because it doesn't need it. So maybe after rootfs auto detects builds it will load the correct userinit to set up compcache/swap with settings specific to the build.
Click to expand...
Click to collapse
Yup, that makes a lot of sense and it's easy to implement.
Will work on that latter tonight (over here) if family allows and get back to you on that...

new package uploading, changlog in first post.

Using the basefile package uploaded 9/6/09 along with zen's xrom, I have been re-experiencing an intermittent wakeup problem.
Waking up from sleep occasionally takes a few presses of the power button - I think this is due to the new bundle files. When vilrod initially made the new button configuration, we had this problem, then he was able to fix it - i think it was something in the rootfs.
Anyways, thanks for all the work guys.

tatnai said:
Using the basefile package uploaded 9/6/09 along with zen's xrom, I have been re-experiencing an intermittent wakeup problem.
Waking up from sleep occasionally takes a few presses of the power button - I think this is due to the new bundle files. When vilrod initially made the new button configuration, we had this problem, then he was able to fix it - i think it was something in the rootfs.
Anyways, thanks for all the work guys.
Click to expand...
Click to collapse
I guess it depends on which button layout you are using.
The zImage with the old button layout was just a quick hack made for mssmison by request. It wasn't tested a lot.

pmos69 said:
I guess it depends on which button layout you are using.
The zImage with the old button layout was just a quick hack made for mssmison by request. It wasn't tested a lot.
Click to expand...
Click to collapse
using the new button layout.

tatnai said:
using the new button layout.
Click to expand...
Click to collapse
:-/ Then I don't exactly know what could be wrong.
Recent updates can hardly account for that, since they focused on other things, but I can't guarantee that, of course.
There's a new update under testing now. We'll see how that goes...

pmos69 said:
I guess it depends on which button layout you are using.
The zImage with the old button layout was just a quick hack made for mssmison by request. It wasn't tested a lot.
Click to expand...
Click to collapse
I don't think it's from the old button layout, I've been experiencing it on most of the newer builds we've been putting together, even before the new rootfs setup.

tatnai said:
using the new button layout.
Click to expand...
Click to collapse
Me also - new button layout and wakeup intermittently takes a few presses of the power button; seems to be since new basefiles.

that's +1 from me on the wake up issue... not that it's a big deal considering everything else that works so well on these builds ^^

does re-nicer load with the current setup or do I have to do something to get it running after booting?

i used the base files w/ the xrom143r.sqsh on kaiser. Booted fine, but when i enable wifi, it can't find any networks during the scan..though i have a xrom143.img from entefox that had wifi and it works good..

ajclai08 said:
i used the base files w/ the xrom143r.sqsh on kaiser. Booted fine, but when i enable wifi, it can't find any networks during the scan..though i have a xrom143.img from entefox that had wifi and it works good..
Click to expand...
Click to collapse
Then stick with the other one. I didn't put WiFi in the last xrom. And there isn't much difference between them.

I'm using the stuff from the latest basefiles and zens latest hero build and the home screen restarts on EVERY return..
I notice that there's no swap or anything created on boot and i have multiple fsck files forming with each boot, dunno if that plays a part..is there anything i need to do to get it running @ full capacity?

KERKEDAGAIN said:
I'm using the stuff from the latest basefiles and zens latest hero build and the home screen restarts on EVERY return..
I notice that there's no swap or anything created on boot and i have multiple fsck files forming with each boot, dunno if that plays a part..is there anything i need to do to get it running @ full capacity?
Click to expand...
Click to collapse
Just checked, and there's a problem with the posted zip.
Some files missing and others not needed.
Going to ask mssmison to fix it...

pmos69 said:
Just checked, and there's a problem with the posted zip.
Some files missing and others not needed.
Going to ask mssmison to fix it...
Click to expand...
Click to collapse
WHEEEWW...i was scared i was gonna get flamed for Frankensteining (figured itd be ok but wasnt sure). Cool biz..lookin forward to the update!

Related

Can't boot Linux on Magician

Hi all,
I have a Qtek s100 reported to be the same as the magician
I tried booting Linux angstrom using Haret following the instructions from the wiki.
I also tried openmoko and QTOPIA following instructions there : http://linuxtogo.org/~htcpxa/htcmagician/
All tries ended the same way : Haret starts, displays a few lines, says "jumping to kernel", the screen becomes white, and nothing else happens. After a while , the screen is not illuminated anymore, and touching the touchscreen doesn't light it up, whereas the keys do.
I tried changing the runlevel, changing the root= to see if it was due to a bad support of the card reader, nothing changed.
Has anyone already had this problem and solved it ?
Thanks a lot,
Thomas
Hi
I have the same problem.
Try image from http://linuxtogo.org/~ph5/tmp/ - it's work great for me .
You can also boot other images like from http://excogitation.de/lastik/ which are the newest but you have to extract kernel and modules from http://linuxtogo.org/~ph5/tmp/Angst...-2008.1-test-20080216-magician.rootfs.tar.bz2 image and replace them in the image You want to use. Do not forget to copy also http://linuxtogo.org/~ph5/tmp/zImage-2.6.21-hh20-r13-magician.bin to use with haret.
Greets
PS
Sorry for my english
Thanks, I found a working kernel...
GPE works well, but it's not really easy without a stylus... But I like gomunicator, and I can recompile it with my smscenter...
I tried OM 2007.12, but "read sms" crashes, and upgrade crashes my install
OM 2008 doesn't start X...
Which distro did you find most functional ?
Thomas
i'm testing now Angstrom-x11-gpe from http://excogitation.de/lastik/ ( fast but it don't have apps for dialing and sms ). I tried image with opie (but it didn't worked for me) and with Angstrom-openmoko from http://www.linuxtogo.org/~ph5/tmp/ which is for me to slow to use (high memory usage) but the most functional.
Are you able to update packages?? I have some problems with this - i can connect to Magician over ssh, but i can't connect from it to the internet - coul you explain how are you connecting your magician to the computer?? are you using linux box?? what commands are you using.
Thanks
help with my magician ....the touchscreen doesn't work with angstromn x11 gpe... solution?? sorry for my bad english
newbie on PDA, seasoned on Liux
Hi,
I come from a lot of Linux background (since 2003)...
As the matter of fact I'm all the time on Linux, expect when I play a game from time to time (COD,MOH...)
So,
I did join this forum (great one!) and read posts a bit...
Found the OM and OPIE2 (QTOPIA?) images and only got booting with the MO2008 one
So i tweaked the SD ext2 partition a bit:
If (when) i used the 2.6.21 hh20 kernel it booted both the QT and the GTK based images
(one replaces the zImage in both the VFAT partition and in the /boot folder IMO?)
But...
The OPIE2 (Qtopia?) is a by far more pleasant experience:
1. back is always obvious
2. Input method is nice
3. the GUI is more polished
4. more themes per default
A. I missed a terminal
B. I missed a GUI for ipkg
C. I missed hardware support (hal,alsa,sound,sgm,gprs)
D. I missed bluetooth (stack?)
E. I missed networking (USB?)
F. no standard GNU suite: pico,mc,bpe
Then the OpenMoko didn't brill either:
1. It apparently had SGM support
2. It had decent input options
3. It worked acceptably well and almost fast
4. Terminal app (a whole lot more LINUX)
The cons:
A. It wasn't always clear where one is
B. It wasn't always clear where the 'bailout' button is
C. the hardware keys seemed not to work
D. far less apps onboard the image
E. Didn't stay long enough to see it all (must try again)...
F. no standard GNU suite: pico,mc,bpe
so, can we make one decent one?
I try to help?
cest73 said:
Hi,
I come from a lot of Linux background (since 2003)...
As the matter of fact I'm all the time on Linux, expect when I play a game from time to time (COD,MOH...)
So,
I did join this forum (great one!) and read posts a bit...
Found the OM and OPIE2 (QTOPIA?) images and only got booting with the MO2008 one
So i tweaked the SD ext2 partition a bit:
If (when) i used the 2.6.21 hh20 kernel it booted both the QT and the GTK based images
(one replaces the zImage in both the VFAT partition and in the /boot folder IMO?)
But...
The OPIE2 (Qtopia?) is a by far more pleasant experience:
1. back is always obvious
2. Input method is nice
3. the GUI is more polished
4. more themes per default
A. I missed a terminal
B. I missed a GUI for ipkg
C. I missed hardware support (hal,alsa,sound,sgm,gprs)
D. I missed bluetooth (stack?)
E. I missed networking (USB?)
F. no standard GNU suite: pico,mc,bpe
Then the OpenMoko didn't brill either:
1. It apparently had SGM support
2. It had decent input options
3. It worked acceptably well and almost fast
4. Terminal app (a whole lot more LINUX)
The cons:
A. It wasn't always clear where one is
B. It wasn't always clear where the 'bailout' button is
C. the hardware keys seemed not to work
D. far less apps onboard the image
E. Didn't stay long enough to see it all (must try again)...
F. no standard GNU suite: pico,mc,bpe
so, can we make one decent one?
I try to help?
Click to expand...
Click to collapse
I just stumbled upon your post by accident - and it seems there isn't much interest in Magician in general
anymore - so in short there won't be full linux support for Magician (unless pH5 - or someone else (you?) finishes it).
Well actually the hardware is almost 100% supported (apart from IrDA, sound recording and camera)
(see here - but afaik the userspace stuff is missing so it doesn't work with the mentioned images.
Usbnet is working (to get you started look here or here)
If know/are interested to expedite userspace you probably don't need any help setting up a build environmend
(but you can always ask me).
The info on the wiki could also be useful.
The Camera is an OV9650 that's also used in
Motorola A780 (driver available for an earlier kernel)
HTC Alpine, HTC Sable, HTC Universal, HTC Wizard
Also I will reassemble a Magician I have lying around in parts if you need a tester
(or provide a nice image with good support).
Don't know if you had that OM image ... but there is one with Phone working.
(if you update it to the current state (well some months ago) through ipkg
the phone breaks (of course - new dialer), but sound (alsa) sarts working).
excogitation said:
Also I will reassemble a Magician I have lying around in parts if you need a tester
(or provide a nice image with good support).
Don't know if you had that OM image ... but there is one with Phone working.
(if you update it to the current state (well some months ago) through ipkg
the phone breaks (of course - new dialer), but sound (alsa) sarts working).
Click to expand...
Click to collapse
If you're interested take a look here:
http://forum.xda-developers.com/showthread.php?t=408069
That's the main thread about this subject.
The Camera is an OV9650 that's also used in
Click to expand...
Click to collapse
Camera is OV9640. Also used in FS720.
It seems Magician revisions have two different cameras, but I don't know differences...
Since I have the parts lying around I just took a look and it's definitely an OV9650 - and I'm fairly certain there aren't 2 different cameras - if you definitely have an ov9640 - then there are 2 different ones.
There are 2 different LCD's though - but that has already been taken care of by pH5 (that's why on some Magicians the hh17 and earlier kernels won't boot - again if I remember correctly).
I just took a look and found some stuff related ... I'll attach it here so maybe it can save you some time. (notes in the files may be German)
Since xda-devs doesn't want my file ... I put it here: ov9650 stuff
Also check here especially the driver and m560x ov9650.
wow amazing!
If we can get enough ppl working, an Android port could be a viable project in the future.
If you need a tester, I once managed to boot linux in the past, and i have a spare SD card for testings.
Thank you guys!
iRiKi said:
wow amazing!
If we can get enough ppl working, an Android port could be a viable project in the future.
If you need a tester, I once managed to boot linux in the past, and i have a spare SD card for testings.
Thank you guys!
Click to expand...
Click to collapse
Well I highly doubt that's going to happen any time soon - but Android "runs" on Apache so that should get someone interested started.
iRiKi said:
wow amazing!
If we can get enough ppl working, an Android port could be a viable project in the future.
If you need a tester, I once managed to boot linux in the past, and i have a spare SD card for testings.
Thank you guys!
Click to expand...
Click to collapse
linux yes
android ?????
after some emails with people involve with linux there seems to be issues in porting the android kernel
if you wanna help with the linux port head there
http://forum.xda-developers.com/showthread.php?t=408069&page=7
Just a bump to a thread
maybe this should be make sticky, for who knows when the last Magician with Linux user is going to break down?
They might want to slump together a linux build mean while?

[PRJ][AND][LNX] OPANDROID (The Wing-Linux Opal branch)

Please, don't reply with a quote of this post.
Wing Linux​
This thread is a continuation to what happened in the LINUX BOOTS at OPAL! Thanks to linwizard project! thread. I thought it's about time a proper thread is made to get this project the attention it needs.
What is Wing Linux all about
Wing Linux aims to bring Linux and Google's Android operating systems to OMAP850-based devices.
Wait, did you say Linux AND Android?
Yep, you did read that right. If you're running Wing Linux, you are simultaneously running Ångström and Android on top of that. That means you get all of the cool Linux functionality with the intuitive interface and usability of Android.
For more information about Wing Linux please visit the official site. It'll save you from having to read through this whole thread
If I installed Wing Linux, will I lose WM? / Will this brick my device?
No. There's no flashing involved here. Still, it's best practice to have thing backed up before doing anything. I've heard of a few cases were people lost some files from there SD cards.
Great! How can I try this?
I'm glad you asked!
Installation is very easy and smooth, all you have to do is following these simple steps:
Navigate to the Wing Linux site.
On the navigation menu to the right of the main page, you'll find a "Download" link. Obviously, you're supposed to click it
Once the download completes, you'll end up with a zip file that contains a few cab files and 4 text files. Please do open these files using notepad for a quick look. They contain plenty of useful information.
After extracting that zip, and hopefully taking a look at the text files, you'll need to move two of the cab files to your device: rootfs and opal.
From your device, install the two cabs (navigate to them using your favourite file explorer then click them) and make sure to install both files to storage card.
Before proceeding any further, make sure that you still have at least 250MB of free space on your storage card. If you don't then you'll need to do some clean up before you can continue.
Also, make sure to close any open application, otherwise you'll lose any unsaved progress in any of them.
Open the brand new wing-linux short-cut in your start menu.
Hit run.
While Linux is booting up. You'll be asked to input a size for the image file used as storage for Wing Linux (consider it like virtual hard disk). Don't touch anything and just wait, default value (250MB) will be used after a couple of seconds.
Grab yourself a cup of coffee/tea/beer/... then sit back and relax. Installation will take a while.
When everything is over, you'll get a calibration screen. Try your best to get a good calibration on the first time as fixing it later takes some work.
Enjoy Android
Key-map for Android
As the Opal doesn't have that many keys, some changes had to be made:
D-Pad + Centre: works normally.
Green: Dialer.
Red: Default behaviour under Android is like this:
Short press: puts device in standby. This can be changed in the settings (which I recommend).
Long press: Display menu to turn off device, put device in airplane mode...
Volume Up: menu key (it's the key that unlocks the screen as well).
Volume Down: back/cancel.
Power button: It's working, but it doesn't do anything because it's functionality doesn't work in Android yet.
Okay, I'm done playing around and I want to go back to WM.
That's easy:
Click and hold the red button and you'll get a menu.
Select "Shutdown" and the phone will reboot.
Once the phone boots again, you'll be in WM.
I want to completely get rid of Wing Linux
Eh, it's your loss.
Un-install both cabs as you would do for any application.
Check if there's still a folder called "linux" in the root of your storage card.
If there's one, delete it.
What works and what does not work:
For details look at this page here. In short:
For the time being, these stuff work:
Making/receiving calls, although you won't be able to hear the other side during phone calls. But there's a small workaround for that:
When in windows mobile, start Wing Linux during a phone call, that way you'll have sound in Android during calls.
Sending/receiving SMS.
GPRS also works. If your carrier/service providers details are included already, it'll work out of the box. Otherwise you'll need to set up a new APN under settings.
For the time being, these stuff do not work:
Battery (will always report it's 100% full).
Bluetooth
WIFI
Camera
Sound (other than what you'll get with the workaround)
Vibration
LED notifications
Standby/Suspend mode.
Unlocking SIM (Android will accept the PIN code but it won't connect to network, you'll need to disable PIN from WM).
FAQ
Q: When I let the phone sit for a while it goes to a text screen that just rolls android_power_suspend messages?
Right now these message are normal, just hit any key or the screen to go back. The suspend portion of Android is being actively worked on so just hang tight!
Q: I installed and booted Wing Linux and when I attach it via USB to my Windows computer it asks me for a driver for an "Ethernet Gadget". Where can I get this?
Linux has this driver natively. For Windows, there's no driver right now, if you know where we can find one (that is free to distribute legally) please do share it with us.
Q: When I boot for the first time the installer hangs at partitioning 0%, is it not working?
Walk away from your phone, this part will take some time. It will only have to do this on initial install so have faith.
Q: Can I install this to my phone's internal memory?
Not presently. Although the cab file will install, you won't be able to boot from internal memory. Ensure you install to your storage card.
Q: Does this run emulated under Windows Mobile?
Not at all! Although it's started from inside Windows Mobile, HaRET completely replaces Windows with Linux in memory, so you actually are booting native Linux -- No emulation at all.
Q: I successfully entered my PIN and unlocked my SIM card through Android, but I can't get on the network. Why?
This is a known issue -- unlocking a SIM card works, but Android does not follow through with connecting to the network. The best solution to this for now is to remove the PIN from your SIM card.
Q: I opened an application but how to I get back to the main page or quit the program? Where is my back button?
Check the keymap posted above.
Q: When will X work on Opal?
In due time. The project is made of volunteer effort working in their spare time. If you'd like the development to speed up, feel free to give a hand!
Not every single one of the people working on this is a developer. Some, like me, are learning as they go. And none is able to dedicate all his time for this project.
Q: I messed up with the calibration. How can I re-calibrate the screen?
Go to storage card, then go to the folder called 'linux'. You'll find a file called default.txt
In that file, look for the line that says "set CMDLINE", add "reset_ts" to it (between the two quotations). Then boot normally.
Remember to remove that once you're satisfied with the calibration.
(If Microsoft Word asks you to save it in their format, always say no)
Q: I waited a lot but the device won't finish booting after installation. What should I do?
First of all, try resetting the phone and booting Wing Linux again. In most of the cases, this'll work. If that doesn't work, try deleting the "rootfs" file from "/Storage Card/linux". If you don't see that file, delete rootfs.img instead. Then boot back in and it should start installing from scratch.
If you're still having issues, remove everything (refer to the "I want to completely get rid of Wing Linux" section) and reinstall the two cabs.
Q: What version of Android is Wing Linux running?
Right now, it's running Cupcake (1.5). An upgrade is planned.
Q: What version of Ångström is Wing Linux running?
Latest as of time of posting.
Q: I'm trying to use the virtual terminal but the enter button on the virtual keyboard won't do anything. Is that normal?
It happens occasionally. Try pressing the d-pad in various directions then hit then enter button again.
Q: Can I SSH to the phone?
Yes you can
Code:
sudo ifconfig usb0 10.100.0.2 up
ssh [email protected]
The password is "wing".
Q: Is installing to a dedicated partition supported?
Yes it is, for more information check the 'INSTALL' file included in the zip, and that can also be found under /storage card/linux
Q: How can I set up a development environment to help with coding?
Take a look here.
Q: How can I get in contact with developers?
Through this thread, the project's forums and on the IRC channel at #wing-linux on Freenode.net. Please, do not use E-Mails, PMs, IMs...
Personal thanks from me to the following people for making this a reality:
darkstar62 for being the main man behind the whole project. And for going easy on me despite my noobness
The people at Linwizard for creating the base kernel and helping throughout development.
kshaurya for helping me to get the Opal branch started
raditzgds, life02 and zenned for helping to get the touchscreen working on Opal.
HTC for this nice device.
Google for Android.
The people behind Ångström for the base system.
I hope I didn't forget anyone...
Please, don't reply with a quote of this post.
Release Informations
Released Versions:
0.1 released on 2009-02-16
0.2 released on 2009-05-26
0.3pre3 released on 2009-06-14
0.3 released on 2009-06-16
0.4pre1 released on 2009-07-04
0.4pre2 released on 2009-07-25
0.4pre3 released on 2009-08-12
0.4pre4 released on 2009-08-12
0.4 released on 2009-11-09
0.4.1 released on 2009-11-19
0.4.2 released on 2009-11-21
Planned Releases:
Nothing is currently set in stone. Next release can be either 0.4.3 or 0.5.
Things to look forward for in the next release.
Hopefully: Sound and there might be some changes concerning Android.
Latest Change Log:
Will be updated on next release.
Please, don't reply with a quote of this post.
How to help with testing and development on Opal:
The people behind Linwizard and Wing-Linux are in need of the results of running this test:
ali1234 said:
Hi,
Thanks to everyone who came to our sprint and tested things. We got a
basic kernel booting on several platforms.
After looking at the results I started to look at the LCD detection
code. I would like to ask everyone to run this test and send me the
results.
I need testers with any omap7xx phone. You only need to run a haret
script and mail me the output, no kernel boot in necessary. The test
scripts are here:
http://al.robotfuzz.com/~al/htc/lcd1.zip
You need a modified version of haret which is included. Unpack the zip
to the phone's internal memory and run haret. Press the "boot" button
like normal. It won't boot linux, it will run the tests instead. Your
screen will flicker during the test, it is normal. It will generate
lcdlog.txt. Mail that file to me or the list, along with any
information you have about your phone. Especially if you have an
after-market LCD, or you know what model of LCD you have for another
reason.
The test works by rapidly switching between LCD mode and GPIO mode on
the LCD controller pins, to check which pins are tied high, low, or
are floating. It does this 30 or so times. Any pin that changes value
is deemed floating. The others are tied high or low (1 or 0). Ignoring
floating pins (zero them) and you get a code which identifies the
panel type of the phone.
More about the LCD detection, including device database and log
processor: https://sourceforge.net/apps/trac/linwizard/wiki/LCDDetect
Thanks
Click to expand...
Click to collapse
While the quote tells you to email the results to ali1234, it would be best if you PM them to me and I'll handle passing them forwards.
Very nice thread with all the info needed
musikmonk that rom is ready contact me today eve or tom i will send u... then u can do testing works.
good discription brother........
i have tried it out already....but sound wifi etc not working.....hopefully the developers will solve the problems in next build....
indresh88 said:
good discription brother........
i have tried it out already....but sound wifi etc not working.....hopefully the developers will solve the problems in next build....
Click to expand...
Click to collapse
I guess you dont know that musikmonk himself is one of the developer of android for omap 850 devices
i downloaded it from the web to my mobile...took me a couple of hours but was worth it.
installation was a breeze.
wifi is not a necessary for me...so i am okay with it...
there are some probs tho...like the battery percentage...it is stuck at 100%. even after fiddling with it, it remained the same.
i rebooted to wm to find that battery was about 45%. this issue is critical...i feel. what about you guys??
btw...my sincere thanks to all who toiled so hard...without getting paid...to port this amazing os.
hats off to you guys...and do keep up the good work.
i'm testing android from some week
i test version 0.4.2 and the 0.4.3 pre4
bluetooth don't work... when I turn on the bt the scrren increase brightnees...
for the audio problems if you start winglinux during a call audio works
now i want try your kernel
jagan2 said:
I guess you dont know that musikmonk himself is one of the developer of android for omap 850 devices
Click to expand...
Click to collapse
Thanks But I'm still faaaaaar from being a developer. I'm just learning.
freelancer81 said:
there are some probs tho...like the battery percentage...it is stuck at 100%. even after fiddling with it, it remained the same.
i rebooted to wm to find that battery was about 45%. this issue is critical...i feel.
Click to expand...
Click to collapse
Ah, I forgot to mention that . I added it to the not working section now.
Right now, wing-linux is using a fake battery driver that always reports battery as 100% full. There's still no working driver and I'm afraid that it might be a long time till there is one.
gp.triple said:
i'm testing android from some week
i test version 0.4.2 and the 0.4.3 pre4
bluetooth don't work... when I turn on the bt the scrren increase brightnees...
for the audio problems if you start winglinux during a call audio works
now i want try your kernel
Click to expand...
Click to collapse
Please do try that kernel and tell me how it goes for you.
nice work MusikMonk, i m so happy to see development for android on our phones
Bluetooth works on mine, but not all the time(once in 10 it doesn't)
Thank you so much for sharing your work
Edit: Sometimes,network problems occur after changing kernel
i try your new kernel
now when i start bluethoot its start
but don't discovery my sonyericsson w950i
and the s.e. don't find the opal
but the opal find other device...
soon as possible i try to connect other device and give you some feedback
i hope that you can understand my bad english
one question...
it is possible tu build the kernel 2.6.30 or successive?
its contains more driver
mrushabh said:
nice work MusikMonk, i m so happy to see development for android on our phones
Bluetooth works on mine, but not all the time(once in 10 it doesn't)
Thank you so much for sharing your work
Edit: Sometimes,network problems occur after changing kernel
Click to expand...
Click to collapse
Can you please tell me what you tried for bluetooth? I could use some details.
And about network problems, that's normal. It randomly happens with wing-linux, it isn't something specific to that kernel.
Most of the times switching to aeroplane mode and back works. Sometimes you'll have to reboot.
gp.triple said:
i try your new kernel
now when i start bluethoot its start
but don't discovery my sonyericsson w950i
and the s.e. don't find the opal
but the opal find other device...
soon as possible i try to connect other device and give you some feedback
i hope that you can understand my bad english
one question...
it is possible tu build the kernel 2.6.30 or successive?
its contains more driver
Click to expand...
Click to collapse
Does it always find that other device or does it only find it sometimes?
About using a new kernel, there are some problems with that. darkstar62 is working on moving upstream to latest kernel and he submitted some patches to the linux-omap tree to get his device (Herald/Wing) supported some were accepted, others are pending.
I tried these patches on Opal but memory card and usb didn't work. I'm waiting till the patches are complete to try again because, right now, I don't know how to fix them myself. I had a couple of ideas that I tried, but none worked.
Oh, and your English is okay. I can understand you fine.
MusikMonk said:
Does it always find that other device or does it only find it sometimes?
i had few time to try this morning
one time bt start and find some device
one time bt don't start
and one time bt start but don't find any device
as soon as possible i'll do other test
Click to expand...
Click to collapse
Click to expand...
Click to collapse
im glad the network problem is not related to the kernel..
as for the bluetooth, it can find my other phone but somehow cant connect with it, also when set to discoverable also no other device finds it
Thank you all I really appreciate your help with testing.
If you guys have the time, can you also give this kernel a test:
http://dl.dropbox.com/u/1944361/zImage-09-02-10
Edit:
Oh, and can you please give me details such as:
What was the bluetooth state in WM (off/on/hidden/discoverable)?
If you're using WM6.5.x, does bluetooth work normally on the rom you're using? (There seems to be many customized roms with bluetooth problems)
When you searched from Android, if some devices are found, do the name appears or only the address?
Stuff like that...
nice ...work
nice work thank u .
i have test the OS but there are some problem , that i cant make a call and
i cant but it on sleep mode and some time Bluetooth does'nt work .
but until now it's great to see the android work on our mobiles .
.
MusikMonk said:
Thank you all I really appreciate your help with testing.
If you guys have the time, can you also give this kernel a test:
Edit:
Oh, and can you please give me details such as:
What was the bluetooth state in WM (off/on/hidden/discoverable)?
If you're using WM6.5.x, does bluetooth work normally on the rom you're using? (There seems to be many customized roms with bluetooth problems)
When you searched from Android, if some devices are found, do the name appears or only the address?
Stuff like that...
Click to expand...
Click to collapse
i did other test
at first i use the original wm6.1
condition of test
wm bt on/discoverable ---> android don't start bt
wm bt of ---> bt start in android, only one time find other device but appears only the adress, the other device don't find the opaldroid
if i can this evening try the new kernel
Results with the new kernel
Rom used:Official HTC WWE Rom
Bluetooth state in windows mobile:Off
Bluetooth activates and can be set to discoverable but no device can find phone and phone cant find any device
VERY RARELY IN THIS STATE IT CAN FIND MY MAGIC MOUSE
Bluetooth state in windows mobile:On
Same as the one before but no rare luck here..(Bluetooth activates and can be set to discoverable but no device can find phone and phone cant find any device)
hi;
Please take a screen shot from your device and put them there!
thanks.
i did some test whit the new kernel
win 6.1 standard rom
bt off in wm---> sometimes find other device showing the adress but other device cant find opal
bt on in wm--->didn't find other device and other device cant find opal

Android 2 on the Omnia 2?

Okay, first post, I apologize if I've broke a rule. And I didn't see this question anywhere. So... Is there any way to use Android 2.0 on the Omnia II? I don't really like Windows Mobile and wish I could replace it. Thanks.
Perhaps in the near future.
Two phones have similar hardware to the Omnia II: first is the Samsung Moment and the next is the Samsung Beam.
The three share the exact same CPU and only the latter differs in RAM; the beam has 384mb ram but this is probably because it also sports a projector and I assume it is going to be a very resource intensive app.
Both the Beam and the Moment (well at least the Sprint version) will eventually have Android 2.1 on there. If someone still has an interest in this old device which seemed to have so much support and potential behind it only 4 months ago they may decide to get the software from that phone and do a few tweaks to have it running on the Omnia II.
There presently is an Android on Omnia dev but the fact is he is going to have a really hard time porting Android on a device which is quite different to anything current on the market now (the Armv6 instruction set is quite dated). Hopefully he moves onto porting instead of building from the ground up like he is doing now, though he may elect not to because he has probably done a lot of work. IF he or someone else ports it will be a very good Android phone, if it is built from the ground up i have a strong feeling it will lag and crap out worse then the Omnia 2 with Samsung BloatWiz on it right now.
=====
In my opinion Modus Windows Mobile is not the issue, it is Samsung. They have a very poorly coded user interface called "Touch-Wiz". All you need to do is go into the My Menu, Find "settings " > click "Display and Light" > click "Items on Today" > scroll down and go to the Samsung widget plus and untick the box > Now go to the very bottom and just tick "Windows Default". Click Done.
You have to wait a second now go back to your home screen, you no longer have three screens (a useless feature anyway) but everything is faster now. You can also make it look better by going back into that place and clicking "themes".
Thanks. I'll give it a try and check the forum periodically for Android-on-Omnia2 news.
I've been working on this for quite a time now. (see modaco can't post links yet)
Okay I've uploaded all the necessary files. But no time to make a manual. So please, only those who know what they are doing try it out. For the devvers: in winmo change usb mode to mass storage (my internal storage), stick in into linux, change the size of the vfat internal sd, add an ext3 partition. Make sure you chmod it. And there you go!
My plan is to setup a dedicated website with the full source, split up in to braches for the different s3c6410 devices and supported drivers. This costs money and time, my plan is to do this next week.
For those of you who showed support by donations, I would like to do something extra for you guys. I apreciate this, Please PM me if you need any help and have considered the above but can't get it to work.
Paypal:
EDIT:now it is working
rapidshare:
--Alpha Release--
Note: to accomplish booting android requires reformatting the internal sd, this might brick your phone, I only recommend it for the more advanced (linux) users. I will take no responsibility for this. This release is soley for a proof of concept purpose. For the non-devvers: you could try to see if it works from vfat, you'll have to use mmcblk0p5, I know it gets to the android screen or make .img from these files and use an initr and mount the images.
What works:
-frame buffer
-s3c6410 cpu
-internal sd
Android is now in a state where you could open up almost anything, watch a slide show But because of the TC you need to press a little below/left on what you want to click due to faulty calibration.
What is in the making:
-ALSA support
What needs to be done
-hardware keys (using haret) (then we can shuw down the phone, because often you have to reformat the partition due to corruption)
-ADB/USB connection (shouldn't be too hard)
-UART/RIL/DPRAM config (to make 3G/PHONE/text work)
The first two will speed up development, that's why they need to be appended first.
Then:
-Touch screen should be better calibrated
-optimizations/speedups (G2d, G3d, armv6, VFP) + memory layout issues should be resolved. Now only 128 mb is used.
-external SD support (the s8000 android devvers are working on this)
-BT (I don't use it so it has no priority for me)
Which devices are supported?
I think theoretically every s3c6410 omnia/jet/acer iteration should work. But I know some devices will require a small patch to change the frame buffer adress. So please report back failures/successes.
EDIT: ofcourse I will still make a manual these days for the non-devvers, first thing i do when i have time.
Click to expand...
Click to collapse
almar2 said:
I've been working on this for quite a time now. (see modaco can't post links yet)
Click to expand...
Click to collapse
Hey there Almar, how is the speed of the device? Has compiling the drivers been an ok task and what do you think of the new phones coming out soon, will they be of any use to you?
What version of Android have you installed and if it is 2.1, would you say it is at least as fast as pre-2.1 android?

[Q] Compiling PSFreedom for Blackstone?

PSFreedom's recent port to various Android devices using the msm72k chipset got me thinking. Has anyone taken a look at building it for the HD?
I currently use an X10 which unfortunately isn't supported but I have a Blackstone lying around that would be perfect. The hardware *should* be able to handle it but I have no clue how to even begin.
I can cross-compile modules for my X10 and so on but that's about it. I have no experience building a working kernel, the external module and finally making boot images for use with haret.
Anyone working on it?
ddewbofh said:
PSFreedom's recent port to various Android devices using the msm72k chipset got me thinking. Has anyone taken a look at building it for the HD?
I currently use an X10 which unfortunately isn't supported but I have a Blackstone lying around that would be perfect. The hardware *should* be able to handle it but I have no clue how to even begin.
I can cross-compile modules for my X10 and so on but that's about it. I have no experience building a working kernel, the external module and finally making boot images for use with haret.
Anyone working on it?
Click to expand...
Click to collapse
for educational purposes only..
oNNoZeLe said:
for educational purposes only..
Click to expand...
Click to collapse
Naturally.
So after some intense googling I've worked out a plan but I have some questions on compiling and assembling images. The plan goes like this:
Since I don't use the device as an actual phone I'm not bothered about losing things like making phone-calls or things like that. So I'll probably used a stripped down version of Donut or Eclair depending on whichever's the easiest.
Any recommendations on guides for compiling custom kernels, building external modules and preparing the kernel for use with haret?
I've set up toolchains for building Donut modules in the past and earlier I got a Blackstone toolchain set up from a guide over at www.androidonhtc.com but then I got stuck. Any help would be much appreciated, I've been at this way too long now.
Thanks
This would rock..
Sent from my MSM using XDA App
I would also love to see this happen.
I maybe wrong, but currently the Android releases are setup on the Blackstone it doesnt give you access to the card (for files) or USB connection (for transfer) yet as it's still in an unstable state...?
the battery issue is keeping me away from android.
usb connection is not there and access to card is not there from pc .
but access to card is there... using terminal emulator.
to check the usb config , i copied config.gz from /proc folder to /sdcard and copied it back while using windows..
so if the activsync type of connection is not there to put or get the files... that can still be done thru winmo... unless it is also hindering some other functionality that i'm not aware of
edit:
i'm using Android 2.2 (FroYo) On HTC [03 Sep 2010] (V1.6)
sunish said:
the battery issue is keeping me away from android.
usb connection is not there and access to card is not there from pc .
but access to card is there... using terminal emulator.
to check the usb config , i copied config.gz from /proc folder to /sdcard and copied it back while using windows..
so if the activsync type of connection is not there to put or get the files... that can still be done thru winmo... unless it is also hindering some other functionality that i'm not aware of
edit:
i'm using Android 2.2 (FroYo) On HTC [03 Sep 2010] (V1.6)
Click to expand...
Click to collapse
I have atleast ADB working over USB but it requires that I boot with the cable plugged in. So USB works, but I don't know to what extent.
ddewbofh said:
I have atleast ADB working over USB but it requires that I boot with the cable plugged in. So USB works, but I don't know to what extent.
Click to expand...
Click to collapse
did you try droid explorer? several things work with ADB enabled..
I have a lot of time on my hands, but no knowledge of what needs to be done in order to work out how to get this working.
Is there any system already ported that we can look at that has similar devices to the Blackstone - perhaps the HD2?
If not, if someone can advise on what needs to be worked out, I dont mind putting the time in.
DejaVu1977 said:
I have a lot of time on my hands, but no knowledge of what needs to be done in order to work out how to get this working.
Is there any system already ported that we can look at that has similar devices to the Blackstone - perhaps the HD2?
If not, if someone can advise on what needs to be worked out, I dont mind putting the time in.
Click to expand...
Click to collapse
did you check one of the other threads on "getting this to work on XDA?"
I've been on checking XDA-Dev (as well as other sites) since the release of psgroove/psfreedom for updates.
I've been watching all the other devices getting ported too (Nexus One, Bravo, Dream, Desire, Sapphire, TI-84+ (CALCULATOR!), Dingoo), but really dont know where to start for the Blackstone - which has been dishearting as the Teensy++ boards are sold out worldwide!
But surely, if a calculator can do it...!!
Supposedly, the USB Device is the same as the others (MSM72K) that have already been ported. It just needs to be written into the psfreedom code I guess and run a certain way depending on the system the Blackstone would use.
I dont think Windows Mobile has 'root access' so hence the use of Android via Haret. Although it's not stable as such, I think it should be sufficient to run this (if possible through Haret?)
Some of this may seem like complete crap - but I will be the first to admit, I dont know what I'm talking about. It's just the gist I'm getting from surfing the internet over the last few days.
From what I gather, all the (hardest?) work has been accomplished (it's proven it can work with Android!) and I'm sure the Dev's that have completed it will share their findings to help other devices to work?
Also, looking through most the forums on here, Blackstone being THE most popular, I think the port would be appreciated by a lot more people.
The reason that Blackstone is the most popular IMHO is that Windows Mobile running on it is terrible. When I got mine originally from O2, the ROM was sooo slow. The great work the Chef's do on here are appreciated by thousands as they are making the phone usable again. Bring on Adroid for this phone... IT NEEDS IT!!!
If it's pointed out what needs doing. I'll happily do it - I've flashed my phone sooo many times lately, a few more wont hurt!
It'll be Awesome!!!!
I was under the impression that Blackstone has MSM72K (reference to which I found in a very old thread.
following is the text form config.gz which uses MSM_HSUSB
so only a ROM chef can tell us which driver is used in blackstone.
We can only request all the developers on this site to look into this and guide us.
Code:
# USB Function Support
#
CONFIG_USB_FUNCTION=y
CONFIG_USB_FUNCTION_MSM_HSUSB=y
# CONFIG_USB_FUNCTION_NULL is not set
# CONFIG_USB_FUNCTION_ZERO is not set
# CONFIG_USB_FUNCTION_LOOPBACK is not set
CONFIG_USB_FUNCTION_ADB=y
# CONFIG_USB_FUNCTION_UMS is not set
CONFIG_USB_FUNCTION_MASS_STORAGE=y
# CONFIG_USB_FUNCTION_DIAG is not set
CONFIG_USB_FUNCTION_ETHER=y
CONFIG_USB_FUNCTION_RNDIS=y
# CONFIG_USB_FUNCTION_FSYNC is not set
# CONFIG_USB_FUNCTION_SERIAL is not set
# CONFIG_USB_FUNCTION_PROJECTOR is not set
# CONFIG_USB_FUNCTION_MTP_TUNNEL is not set
http://forum.xda-developers.com/showthread.php?t=777120 The HD2 get a haret Port
It doesn't work on a HTC Touch HD T8282, Won't boot. I think, as a WM6.1 phone it can't be rooted.
HD1
sunish said:
I was under the impression that Blackstone has MSM72K (reference to which I found in a very old thread.
following is the text form config.gz which uses MSM_HSUSB
so only a ROM chef can tell us which driver is used in blackstone.
We can only request all the developers on this site to look into this and guide us.
Code:
# USB Function Support
#
CONFIG_USB_FUNCTION=y
CONFIG_USB_FUNCTION_MSM_HSUSB=y
# CONFIG_USB_FUNCTION_NULL is not set
# CONFIG_USB_FUNCTION_ZERO is not set
# CONFIG_USB_FUNCTION_LOOPBACK is not set
CONFIG_USB_FUNCTION_ADB=y
# CONFIG_USB_FUNCTION_UMS is not set
CONFIG_USB_FUNCTION_MASS_STORAGE=y
# CONFIG_USB_FUNCTION_DIAG is not set
CONFIG_USB_FUNCTION_ETHER=y
CONFIG_USB_FUNCTION_RNDIS=y
# CONFIG_USB_FUNCTION_FSYNC is not set
# CONFIG_USB_FUNCTION_SERIAL is not set
# CONFIG_USB_FUNCTION_PROJECTOR is not set
# CONFIG_USB_FUNCTION_MTP_TUNNEL is not set
Click to expand...
Click to collapse
Afaik msm72k and msm_hsusb are different drivers for the same hardware. The kernel in use for the Blackstone port is 2.6.27 and it uses msm_hsusb. Newer kernels are probably different.
psfreedom-for-htc-touch-pro1-2diamond-1-2
Look at this site, you got to copy 3 things and you must have Xandroid 2.2
h**p://howtohackps3.com/psfreedom-for-htc-touch-pro1-2diamond-1-2-is-now-available/
^^ will try it once i get home
It Works !!!!
Yeah Yeah Yeah !!
good temp solution.
as u need to connect the phone to pc when android is booted.
will wait for dongle's price to fall down

Help- anyone with a rooted Tmo or sprint tab

I tried looking into the issue of verizon tabs unable to connect with BT keyboards. With the help of Maris here, we identified that there is a file that is present on Tmo tabs that is not on verizons:
/dev/bthid
We're guessing this is the HID driver that verizon is lacking, since Tmo connects with BT keyboard just fine.
however, since his tab is not rooted, he cannot copy this file to me. Can someone with a rooted Tmo or sprint copy this file (using root explorer, free off the market) and upload it to any free space or message me and mail it to me?
thanks everyone, I'll let yal know if this leads to anywhere
(I checked in my samsung verizon fascinate, it lacks this file too, and cannot connect to bt keyboard too. funny.)
This file isn't going to help you on its own. The files in /dev are really just interfaces to the kernel (they're defined by their major and minor node numbers, and have no actual content).
The file you're looking for is (on my T-Mobile Tab) /lib/modules/bthid.ko. Once you have that, you can use terminal to 'mknod /dev/bthid c 10 224' to create the associated device file.
I'll try to remember to pull this off my tab tonight for you, though IIRC even the T-Mobile Tab has some problems with bluetooth headsets that are remedied by the European firmware.
Well, I have a verizon tab too and am trying to figure this out.
The bthid.ko already existing in that directory.
When I run the mknod, I get mknod: not found.
Do I need to run it from a particular directory (sorry, major noob to this)
You probably need to root your system and install busybox to be able to do that.
I have rooted, guess I need to find busybox.
Sent from my SCH-I800 using XDA App
Well, ran mknod and it said the file already existed. I never checked first, took hyann's word for it that it was missing. No go on the connection either.
Hyann, you friend have any other differences?
ResonanceZero said:
This file isn't going to help you on its own. The files in /dev are really just interfaces to the kernel (they're defined by their major and minor node numbers, and have no actual content).
The file you're looking for is (on my T-Mobile Tab) /lib/modules/bthid.ko. Once you have that, you can use terminal to 'mknod /dev/bthid c 10 224' to create the associated device file.
I'll try to remember to pull this off my tab tonight for you, though IIRC even the T-Mobile Tab has some problems with bluetooth headsets that are remedied by the European firmware.
Click to expand...
Click to collapse
Thanks my friend, at least its worth a shot since ppl with TMO and Sprint have successfully used BT keyboard, and verizon tabs have never succeeded.
robinsmy1 said:
Well, ran mknod and it said the file already existed. I never checked first, took hyann's word for it that it was missing. No go on the connection either.
Hyann, you friend have any other differences?
Click to expand...
Click to collapse
which file do you mean? in my post, me and my friends concluded that only dev/bthid was different between the verizon tab and Tmo tab.
We searched for the system files and came up with all the files that had the name "HID" in it. However, except dev/bthid, all the others were present in the verizon tab.
below is the list:
"
/system/bin shows:
bluetoothd
there is also a btld, not sure if that relates to this
the just one calld "hd" (no hid)
/system/lib had a folder bluez-plugin and inside it is:
audio
input
/system/lib has files:
libbluedroid
libbluetooth
libbluetoothhd
Then decided to do a search for HID and astro found the following (more promising?):
/system/usr/keylayout/Broadcom_Bluetooth_HID.kl
/system/usr/keychars/Broadcom_Bluetooth_HID.kcm.bin
/lib/modules/bthid.ko
/dev/bthid
"
I still think that if I could get the dev/bthid, whatever kind of file that is, maybe it is a shot. because verizon tab pairs successfully with the BT keyboard, we know the BT function is okay. Its just lacking something, either a command, a registry, or a reference file that allows keyboard input to come through by BT.
Funny thing is, on my samsung fascinate phone, I could also pair but not connect the BT keyboard too. I think verizon is purposely blocking this feature on their phones. What the heck would that serve I do not know.
I think you are right about Verizon.
I got the bthid to by there by following the advice above to run the mknod and it did not fix the problem.
I have also tried using the hidd from another post and got the error "Can't open HIDP control socket: protocol not supported"
I am afraid Verizon might have done something in the base Bluetooth support. I do not know enough to know if that is in the kernel or a support file.
Doing some more research into linux (I know, long shot), please have your friend look in their bluetooth configuration files for possible differences.
I found some in /etc/bluetooth there may be more elsewhere, this is all I have found so far.
In linux there is an HIDD_Enabled flag, maybe there is one here too.............wishful thinking!
hyann said:
We searched for the system files and came up with all the files that had the name "HID" in it. However, except dev/bthid, all the others were present in the verizon tab.
Click to expand...
Click to collapse
"Present" doesnt mean they are the same! If I were you i'd extract all these files from a working ROM and compare them.
Regards,
Dave
I've finally gotten around to pulling off the bthid.ko from a stock T-Mobile Galaxy Tab. It's available from:
http://www.resonant.org/android/lib/modules/bthid.ko
(There's no index, but I actually copied my entire modules directory there, if you need the other files as well.)
Hope it helps your experiments.
This looks like it is the same file as the one that came with this tab too. Might be a configuration thing (hopefully).
Any chance you can pull the conf files from the /etc/bluetooth directory too?
Thanks
Sent from my SCH-I800 using XDA App
robinsmy1 said:
This looks like it is the same file as the one that came with this tab too. Might be a configuration thing (hopefully).
Any chance you can pull the conf files from the /etc/bluetooth directory too?
Click to expand...
Click to collapse
Here you go:
http://www.resonant.org/android/etc/bluetooth.zip
Thanks I will take a look.
It is a long shot, but worth a look.
These are the same too.
I pulled a tmobile stock rom from xda....gonna try to see if I can find differences but I am starting to be convinced it is blocked from the Kernel.
Any Devs out there have any insight into where the BT HID is controlled. Any input would be greatly appreciated.
Think I found it
I have been looking through the Verizon source from the Samsung site, and they were kind enough to include an output file from their compiles called config.
It looks this the did hot include the hidp in the build of the kernel, which I believe is the HID protocol.
No the key would be to compile it as a module and try to install it. Not sure where since I cannot find it on the tmobile stock I downloaded, but they may have compiled it into the kernel instead of as a module, which from the kconfig, seems to be an option.
I do not have a linux box at work so I will not be able to try to compile it until tonight.
If someone else wants to try, I would be happy to hear the results.
Also, if there are any devs who read this who might be able to provide some insight I would love to hear it as I am flying by the seat of my pants here
Thanks
Oh man while you guys havent gotten this to work it still makes me SOOO HAPPY to see people working on it. I am extremly windows knowledgable and still getting into the android game so I cant help yet (although I really want to).
It just makes me happy to know people are just as peeved about this problem as I am
This is excellent news robinsmy1! I'm really thrilled to death!!!!
Um, do you want to post the config file or at least a link, so more people could look into it? I have very limited linux programming experience (used to maintain a UNIX system) so I dont think I can help much, but I would like to take a look. And in these days, almost everything is googleable
robinsmy1 said:
I have been looking through the Verizon source from the Samsung site, and they were kind enough to include an output file from their compiles called config.
It looks this the did hot include the hidp in the build of the kernel, which I believe is the HID protocol.
No the key would be to compile it as a module and try to install it. Not sure where since I cannot find it on the tmobile stock I downloaded, but they may have compiled it into the kernel instead of as a module, which from the kconfig, seems to be an option.
I do not have a linux box at work so I will not be able to try to compile it until tonight.
If someone else wants to try, I would be happy to hear the results.
Also, if there are any devs who read this who might be able to provide some insight I would love to hear it as I am flying by the seat of my pants here
Thanks
Click to expand...
Click to collapse
I don't really have a place to host it the file. If you pm me your email address, I can email it to you.
The config file is just a dump of their answers to the Kconfig questions from what I can tell and they did not include the HIDP profile.
I have programming experience, but nothing in Linux at all. I put a VM on my W7 box with ubuntu just so I could troubleshoot this issue.
I am going to try to find time tonight to compile the kernel with the HIDP as a module and see where it puts it and try to pull it out and shove it into the tab to see if that will get it to work.
robinsmy1 said:
I don't really have a place to host it the file. If you pm me your email address, I can email it to you.
The config file is just a dump of their answers to the Kconfig questions from what I can tell and they did not include the HIDP profile.
I have programming experience, but nothing in Linux at all. I put a VM on my W7 box with ubuntu just so I could troubleshoot this issue.
I am going to try to find time tonight to compile the kernel with the HIDP as a module and see where it puts it and try to pull it out and shove it into the tab to see if that will get it to work.
Click to expand...
Click to collapse
I PMed my email to you. Thanks man.
OK
Emailed the config...let us know what you think.
A second opinion is always welcome

Categories

Resources