Database Users

HotDesk Beta 1

*** *Update
Well,
It seems like I'm an idiot - there were a few very serious issues with Beta1.1.
I have released a new beta - with the following issues fixed:
* You can actually add a new virtual screen now! Ugh.
* Vastly improved desktop player in the designer. No more crashes
* New window to show/hide/delete virtual screens in project.
* Tooltips on toolbox now read correctly.
* Miscellaneous crash fixes.
New download link:
HotDesk Beta 1.5
New screenshot:
****
Hi Everyone,
I've been working incredibly hard to get this out to you all: HotDesk Beta 1.
For screenshots, and a more thorough description, see the thread here
Not all the features I would have liked made it into this release - but I wanted to get this out so you can see the concepts behind what I'm doing. Some (albeit limited) documentation is installed with this release, as well as a shortcut (in the HotDesk folder in the Start Menu) to install the HotDesk player to your mobile device.
Also note - you will need the .net runtime version 2 installed to both your device, and to your PC.
You can download them here:
PC Version
Mobile Version
Please report any and all bugs, suggestions and issues to me, Alex Taylor - I'll accept them gladly.
** Please, please, please read the documentation before using the designer - I'm sure some of you will have suggestions to make it more intuitive than it is now
* Please note, this is a time limited (60 day) beta - I'm sure by then that there will be a new release. I just don't want this version floating around when there's a release available that fixes the bugs I'm sure exist here ..
* I have included a sample desktop (test7.desk), that you can transfer to your device as an example, and use in the designer to get you started.
* For some reason, WinZip doesn't like running this setup.exe out of the zip file directly - extract the two files first, in their folder - then run from there.

New screenshot
Hi All,
A new screenshot of the designer for you:

I'm an idiot
Ok,
There were several issues with the original beta. The product is now a lot more functional. Please download again, and try it out.

document
Greetings,
where can i find a document on how to use it.

samy.3660 said:
Greetings,
where can i find a document on how to use it.
Click to expand...
Click to collapse
Two posts above has this link. http://forum.xda-developers.com/showthread.php?t=285187

Documentation
Hi,
There is also documentation installed with the program itself (in the start menu folder). Any issues, post here (or email me) - and I'll get back to you ASAP. Thanks for taking part!

I like it. What little I got on my 8125 seemed to run without hesitation which shocked me compared to other unmentionable apps like WAD Do you have a QVGA sample to work with? Thanks and Good work.

shannoncole05 said:
I like it. What little I got on my 8125 seemed to run without hesitation which shocked me compared to other unmentionable apps like WAD Do you have a QVGA sample to work with? Thanks and Good work.
Click to expand...
Click to collapse
Glad to hear at least something works Suggestions are pouring in - and I'm coding as fast as I can. A QVGA sample is on it's way - one of the most highly requested things.
I'm also writing a TGA loader for the next beta - a lot of people seem to have TGA images from other themers, that they want to use.

Link?
Hello LordChaos,
I'd like your application, but there is a small problem: your DL link is invalid. Any alternate/updated link?

i wish you best with that.

I can confirm, DL is broken. Can you post your program again? (or anyone who has downloaded it)?

Melody [0.7 Source Uploaded]

Hey all,
I'm working on a new mp3 player for windows mobile devices. I took inspiration from the iPod function in the iPhone. This should integrate well with the existing iPhone based themes for windows mobile devices.
I'm using .NET CF, PythonCE and flash to create the app.
Here's the youtube link of what it looks like so far:
Melody 0.8 Final Sneak Peak!
http://www.youtube.com/watch?v=fNUyIHEIv-M
Enjoy .
Chad.
To everyone who has problems with current Melody:
Just to let you guys know, I've officially stopped the development of the .NET version of melody, and I've started intense learning of C++ Win32 development. Having said this, I wont be able to support any errors or problems you might have with the .NET version, in an effort to have a native version of melody out ASAP. Once this is done, a new thread will be created. However, I have posted the source for version 0.7, and anyone is free to pick it up and even release new versions if they so desire.
You can check out the C++ implementation of Melody (PocketMelody) here:
http://forum.xda-developers.com/showthread.php?p=1689445#post1689445
Coding Team:
Thundershadow14
Chrismrulz
Dosfan (Created the scroll routine from scratch)
gingercat (Created user control for dosfan's routine)
Graphic Designer/Layout Strategist:
Youmeus
Steph99
Updates:
Source for Version 0.7 Uploaded. You're free to do whatever you'd like with it .
Requirements:
.NET Compact Framework 2
Flash Player 7 ActiveX
Pythonce (http://downloads.sourceforge.net/py...219-setup.exe?modtime=1166570322&big_mirror=0)
Your mp3 collection.
File Releases:
Melody 0.8 PRE Release
Melody 0.8
-0.81
Post will be updated, upon every new release. Thanks for this suggestion guys.
Installation Instructions:
---------------------------------------------------------------------------------------------------
Step 1: Copy cab file to your device.
Step 2: Install cab file, to either storage card, or main memory.
Step 3: Goto: Start -> Programs -> Melody
Step 4: Enjoy!
---------------------------------------------------------------------------------------------------
If you follow these instructions and it still doesn't work, you've identified a bug. If so, please let us know by posting your results on the forum.

Looks pretty cool.. next time please use a better camera though
What phone is that? Pretty snappy.

Nice...!
Can u upload this programs for us ??
Thanks for your works...!

Very well done
good work man,
do you post the files , i`d like to try that great application , and give you feedback
can you post the files now?
i have some application whid finger scroll , search for my name and you can find posts off some applications finger friendly, and after that you may contact the autors and ask for help to improve finger scroll in your app

good program
yes please...link for the application..

looks pretty good
is there going to be landscape mode with the finger scrolling?

Files
Hey guys,
Thanks for the responses, I'll post files up as soon as I get home.
@Marcos200
Thanks as well, I'll be checking out those apps ASAP.
-Chad.

It really looks pretty cool !!! great job !! can't wait !

cant wait to try will you be posting the files soon

Man, please don't become a film maker. The phone was so blurry that I am now dizzy.
All phones really need to have flush screens like the Touch so you aren't digging your finger in the corner or hit the side when scrolling on the screen.
The application looks nice, is it heavy on system resources?

maevro said:
All phones really need to have flush screens like the Touch so you aren't digging your finger in the corner or hit the side when scrolling on the screen.
Click to expand...
Click to collapse
No doubt. It took him like 5 tries to hit the X button at one point.

OMG!! faster upload it up!!!

Crap!!!
the movie i mean...the software looks promising though.

Looks promising...
any chance you could code it in native.....C+?

Seed123 said:
Looks pretty cool.. next time please use a better camera though
What phone is that? Pretty snappy.
Click to expand...
Click to collapse
i think this is a dell x30 not a ppc phone.. its a regular pda probably with the upgraded specs of 624mhz instead of 312 and its still on wm2003se no way its wm5.. i miss thesed ays but i dont miss losing my info for a depleted battery

FILES
Okay, just to answer some questions:
Coding in native C? I've done some C programming before, but doing the album art animations in C seems very near impossible for me. I'll definitely take a look at it though.
The Machine:
Yes, it's an old Dell Axim X30 High, with 620mhz. Which is why I would love to hear how it performs on phones, that usually have much slower processors. I've got some ideas for speed improvements, but looking forward to your feedback guys.
Please note though, I didn't really want to release so soon, but all the requests have made me go against what I originally thought was a good release candidate point. In other words, EXPECT BUGS! Lol. And PLEASE READ THE README file if you want things to work properly.
Download Link: http://www.sunatrise.com/iMedia_Player 0.1 Beta.zip
Thanks!
Chad.

thundershadow14 said:
Okay, just to answer some questions:
Coding in native C? I've done some C programming before, but doing the album art animations in C seems very near impossible for me. I'll definitely take a look at it though.
The Machine:
Yes, it's an old Dell Axim X30 High, with 620mhz. Which is why I would love to hear how it performs on phones, that usually have much slower processors. I've got some ideas for speed improvements, but looking forward to your feedback guys.
Please note though, I didn't really want to release so soon, but all the requests have made me go against what I originally thought was a good release candidate point. In other words, EXPECT BUGS! Lol. And PLEASE READ THE README file if you want things to work properly.
Download Link: http://www.sunatrise.com/iMedia_Player 0.1 Beta.zip
Thanks!
Chad.
Click to expand...
Click to collapse
WM6 Wizard - NET CF2
gave a DISP_UNKNOWN error.
EDIT:Noticed it needed the OpenNetCF. Downloading....

wow
what did you use to video that? Made me sick. program looks cool!

please keep up workin on this, looks quite promising.

Merlin_reloaded said:
WM6 Wizard - NET CF2
gave a DISP_UNKNOWN error.
Click to expand...
Click to collapse
Where exactly did it give that error??

HTC TouchFLO Cube Ctrl - !BETA V1.1.0 AVAILABLE! - *Full* cube control with gestures

Summary:
I'm starting this thread as a dedicated effort to enhancing the integration of the HTC TouchFLO Cube onto non-"HTC Touch" devices, without requiring a different version of touch.dll to be installed on the device via a new ROM.
Current Status:
WHAT'S DONE
Much research in learning how the cube works
Development of some theories
Development of a testing app to test theories
Proof of concept app built to prove the theories
Using FTouchFlo, I have all 4 motions assigned to the correct cube task ... and it's all working!
Slide up - open
Slide down - close
Slide right - spin right
Slide left - spin left​
Added new feature, where LR, RL, and UD finger swipes can execute other tasks if you perform them when you're not on one of the cube faces. Read Project Status 11-12 entry for details
Added an option to allow LR, RL gestures to open & spin the cube even when biotouch is not running. Not sure if this is actually the way the Elf works, but some people want it
Conversations have been started with efrost about integrating our work here directly into FTouchFlo. Talk about a speed enhancement!
Raven_coda has cracked the final piece of the puzzle!
I have implemented Raven_coda's changes, and my C# version works great ... StartUp items are sorted out now!
C++ version created ... speed is definitely improved
A few bugs fixed, a few issues addressed, and a few new features added
Beta release v1.1.0 available here:
http://rapidshare.com/files/72589345/TFloCubeCtrl_-_v1.1.0.zip -or-
Use the attachment at the bottom of this post
NOTE: This file is a zip archive, suitable for situations where you already have the HTC TouchFLO cube installed. If you have never installed TFloCubeCtrl before, then follow the TFloCubeCtrl - Installation instructions. If you're upgrading from v1.0.4, then use the TFloCubeCtrl - Upgrade instructions. You do *not* need to uninstall TFloCubeCtrl or the HTC TouchFLO cube in order to upgrade. For a complete cube installation, please check with duttythroy on his thread here: http://forum.xda-developers.com/showthread.php?t=336482.
Newer cab built by xplode available here:
http://rapidshare.com/files/75947199/HTCCube_FTouchFlo_TFloCubeCtrlv110_Config-xplode.cab
Includes HTCCube + FTouchFlo v1.4.1 + TFloCubeCtrl v1.1.0 + TouchSettings v1.22 + FTouchFloConfig. This should also include all of the patches and fixes from the attachment list. However, if you installed the previous version of xplode's cab and are experiencing issues, try the following:
If you experience 2 apps launching from the MediaHubMini using Xplode's latest cab ... then replace the MediaHubMini.exe with the "patched" version below in the attachments. Either terminate the MediaHubMini process first then overwrite, or delete the MediaHubMini (preload) link from Windows\Startup, soft reset, then overwrite the file.
If you are having issues with QuickDial not functioning properly ... then replace the QD_Bar_NoBar_HL.png image file with the replacement version in the attachments. Also you can try replacing the version of QuickDial with the patched version in attachments below. Either terminate the QuickDial process first then overwrite, or delete the QuickDial (preload) link from Windows\Startup, soft reset, then overwrite the file.
WHAT'S LEFT
The black screen issues seemed to have all but disappeared. I believe we have determined the reason they were occurring, and have solved at least a vast majority of them.
Solve any remaining beta release bugs/issues
Once the beta seems good to people, get the code to efrost for him to integrate into FTouchFlo!
Rules:
For now, this thread is intended for people who already have a working version of the TouchFLO Cube on their system.
I'd prefer to keep this thread research & development oriented. I don't want this to turn into another thread of a million posts by people who are getting cube black screens and want help.
The cube still has a few unknown nuances/dependencies ... so this thread will be most suited for people familiar with alpha version software.
This thread is about integrating the original HTC TouchFLO Cube. I don't think we need a bunch of posts about how some 3rd party app is better, or how a Flash cube turns faster. There are other alternatives, yes ... this thread is about just one of those alternatives.
More as I think of them
Structure:
Post #1 is for general info
Post #2 will be project updates
Post #3 will be announcements / additional updates
Post #4 is some project background info
Post #5 we'll reserve for a hint/tips section
The rest is up to you guys ​
Donations
Thank you to all who have donated! Every donation makes me realize that other people are also interested in this project, and helps keep me motivated to continue expanding the functionality, and answering questions!​
Props
JasonStern for his tireless research as to why QuickDial was failing on certain devices (see QD replacement image an new version attachments)
Musicman247 for providing me with files and sharing the work he has done with a true 6-sided cube
Zyphlin for pointing me to the work that Musicman247 was doing
Raven_coda, who despite being my mortal enemy at first , ended up discovering the key to breaking our dependency on the original biolauncher app!
duttythroy for creating his cab installer that started me down this path
efrost for creating FTouchFlo which makes the cube work with finger control
xplode for creating cab installers for me (even though he "hates" the cube )
techmonkie for responding to my RFI, and straightening me out re: launching/exiting
funman and Biffert for also helping me out with reference information from an actual HTC Touch users
jasjamming & Bepe for the original work on Touchflo Alpha
others ... I'm sure

Project Status
11-10-2007: Proof of concept app in C# is completed, and the four finger control functions are working! One major issue, is how to get back into the cube when biotouch is still running, but no cube app is in the foreground (like after you launch and close an app). So far, I can only get the startup animation when I start biotouch from scratch ... so the downswipe action runs the close animation, and then closes biotouch. It really seems like I should be able to call something to get a running instance of biotouch to re-execute the startup animation ... but I'll be darned if I can find it as of yet.
I'd like to get some input from users of an actual Elf or Touch Dual device. Ideally, someone who can run a process viewer app to see the processes behind the screen ... and even better if they have a tool like Remote Spy that comes with Visual Studio 2005. I think it would help me ... because right now I'm just guessing at what should be happening.
I need to figure out what pieces need to be in startup for my app to work. Basically, I've written my own version of BioLauncher ... which doesn't require biotouch to be running at all (it starts it on an upswipe). But so far, removing the ns script call from startup (bio.lnk) didn't seem to allow the biotouch animations to run. Need to do more research in this area. Everything works fine if I use my normal Touchflo Alpha install ... use the hardware button to loop through things (pre-loads all the cube apps probably), and then use my new app mapped to FTouchFlo. If none of this makes any sense to you ... read "How the TouchFLO Cube works" in Post #4.
11-10-2007 (after some sleep): I posted a message over on the Elf forum asking for some information about the behavior of the cube in certain situations. We'll see if I get any help. If anyone reading this knows of anyone with an Elf or Touch Dual (are they out?) ... then send them over to that forum, or check it out yourself and borrow their device for a bit
11-11-2007: I actually got an answer from the Elf forum techmonkie is indicating that biotouch doesn't really terminate on cube close, thereby indicating that there *has* to be a way to trigger the startup animation from a running biotouch instance. I was really starting to suspect that this was the case ... but this was the evidence I needed. Figuring this out will solve my startup woes ... and that should complete the interactivity with the cube. At that point ... I may consider a controlled alpha release, just to confirm that things are working as design on other devices. We'll have to see how things go. I'm going to refocus my investigation on triggering the open animation from a running biotouch ... but I may need some detailed analysis from an Elf ... we'll see.
11-11-2007 (update): Did I mention how much sleep this thing is causing me to lose?! Anyways, OK ... must have been the inspiration of knowing how it was actually working on an HTC Touch device, because with the info in techmonkie's response, and a little more digging into the assembly code of touch.dll to confirm, I've got the startup issues sorted out. In fact, biotouch.exe does indeed remain memory resident. There is a way to get the startup anim to run ... although I swear I tried this before, and it didn't work. The open and close animations even do a little screen fade-in. It's working quite well for me in fact! This is so sweet ... I went and downloaded a few other animations from the Elf Cube customization thread ... just to see then animate in my new fully-functional cube!
There's a few cleanup things to do for tomorrow ... and then it's on to sorting out the correct startup sequence. I'm still considering the controlled alpha release. Right now, you need to add it on top of a working cube ... which may not be bad for those that have working cubes!
11-12-2007: I had this thought earlier today ... I never really want a RL or LR swipe to bring up the cube and spin it, if the cube wasn't open before. You don't really know what page you'll land on ... unless you know where you left off last. I'm not exactly sure of the Elf's behavior on this point ... but I decided to add the ability for my cube interface to execute cube functions when the cube is open, or execute other apps if the cube is not open. For instance, I can have a RL swipe spin the cube when the cube is open, but the same gesture will launch Total Commander when I'm on the home screen I think it's pretty cool ... retains the cube interaction abilities, and still retains the "quick launch" nature of FTouchFlo gestures! Doesn't appear to slow it down much ... I'm hoping the C++ version is better anyways.
11-16-2007 (Announcement): New Announcements ... see Post #3 below.
11-20-2007: Hints, Bugs, & Issues section updated to include at least a start (prompted after yet another post about missing contacts tab in HTC Home . Development work on fixing the screen lock bug continues.
11-21-2007: Version 1.1 is under way with a few new commands available. Detect for screen lock and rotation seems to be working, and I'm hoping to fix a few of the other bugs. Also, use of link files for <App_2> parameter now work!
11-24-2007: Version 1.1 development continues. I removed the error message when using the openSpin<Direction> command and running in landscape mode. Also, I think I've fixed the "rainbow effect". Finally, I've adding another new command option: lock, which will execute the standard device lock. So some of the new commands are: minimizeAll, lock, lock-home, and somehow I'm going to work in a command to lock and suspend. Tossing around the idea of allowing screen rotation through gestures as well. So I think bugs 1 & 2, & possibly 3 are fixed, and issues 1 & 2 are adressed. A release is probably due, maybe by the end of this weekend.
11-25-2007: Version 1.1 seems complete. I've added screen rotation as well ... so the final list of new options is: lock (sub options of "home" and "suspend"), rotateDisplay (left and right), minimizeAll. I'll try to package it up in a new archive by tomorrow, after a bit more testing.
12-05-2007: Remaining issues still seem mostly centered around some devices having issues with QuickDial. I've gotten my hands on some new versions of the required apps, and am currently evaluating them. For the most part ... it looks promising that these will extend our cube functionality!

Announcements
11-12-2007: Limited Alpha Release
With this latest feature added ... and everything seeming to work perfectly on my device, I've decided to go ahead with a limited release alpha. It's just so cool ... and I know there are "Cube People" out there that wanted this just as much as me Basically, here's how it works.
You are not eligible for the alpha unless you already have the TouchFLO cube software installed and spinning to the right via FTouchFlo. Reason is that I was focused on rewriting the biotouch interface app first ... as that's the key component. There are lingering nuances to getting the TouchFLO cube apps themselves working ... but I'll be addressing that once I get past this phase. Don't worry ... I have plans on making this a simple cab installation for the whole enchilada ...
If you're interested in trying out the alpha version ... PM me, because I'd rather not have a bunch of one-line posts for people asking to test.
I'll give you the location of the zip file to download. This is alpha-ware ... so not fancy installers yet, but I guess I'll throw in a readme.txt file or something. It's pretty simple really ... assuming that you have a working cube.
Once you get things installed ... try it out. If you're having problems that seem like they might be installation/configuration issues ... then PM me about them first. I'd rather keep the posts as relevant to "general design/development" as possible.
Along the sames lines ... no need to post messages saying it works and whatnot, just PM me. Since it's not publicly available ... we don't really need pages of posts from people saying it works.
11-14-2007: Limited Alpha Release - ON HOLD
Alpha is on hold until I work through some issues ... and clear out some PM's Thank you all for your interest and feedback.
11-15-2007: Startup items are sorted out ... first beta version is on its way ... although apparently no luck in finishing that night
11-16-2007: First revision ported to C++. Need to do some testing and tweaking ... hopefully will finish tonight!
11-16-2007 (Update): Beta release v1.0.4 available here: http://rapidshare.com/files/70299288/TFloCubeCtrl_-_v1.0.4.zip. Currently just a zip archive, I may build a cab installer over the weekend, just for my app (for you that already have the cube installed). For a complete cube installation, please check with duttythroy on his thread here: http://forum.xda-developers.com/showthread.php?t=336482
11-27-2007: Beta release v1.1.0 available here: http://rapidshare.com/files/72589345/TFloCubeCtrl_-_v1.1.0.zip. This file is a zip archive, suitable for situations where you already have the HTC TouchFLO cube installed. If you have never installed TFloCubeCtrl before, then follow the TFloCubeCtrl - Installation instructions. If you're upgrading from v1.0.4, then use the TFloCubeCtrl - Upgrade instructions. You do *not* need to uninstall TFloCubeCtrl or the HTC TouchFLO cube in order to upgrade.

Background
Background:
A few weeks back, I was inspired by the work of a couple of fellows who were working on a project to get the HTC TouchFLO Cube working on other HTC devices. You've probably seen the installation cab floating around in a couple of different threads. Like many of you, I quickly became enamored with the cube ... and jumped through all of the hoops to get it working (and I was one of the lucky ones who got it working).
The original work by jasjamming and bepe provided a cube that could spin to the right via a hardware button. Then, with the release of efrost's FTouchFlo ... you could get the cube to spin right with a finger motion. It was all great, but I wanted more! Two things bothered me greatly ... you could not spin the cube left, and once you launched a program ... the only way to return to the cube would be to spin it again.
So began a intensive week-long, late-night effort to learn as much as I could about the TouchFLO Cube, and if/how we could get it do more. I am very happy to report that much progress has been made ... and it is definitely feasible that we can have finger controlled spin left, right, open, and close.
How the HTC TouchFLO Cube works
The HTC TouchFLO Cube is really the collaboration of four separate executables, and an "interface". The four executables consist of one app per each each face of the cube (ApLauncher.exe = App Launcher; MediaHubMini.exe = Music, Photos, Video; QuickDial.exe = Contacts), and an application that facilitates the animation sequences for the cube (Biotouch.exe). Now, at this point I guess I'll point out that "cube" is really a bit of a misnomer. Since there are only 3 faces to this object + top and bottom, it's really more of a pentahedron, or a triangular prism if you like the sound of that better. The "interface" part is where things get interesting. On an HTC Touch (Elf) or Touch Dual ... the "interface" that detects finger swipes and translates them into calls to the biotouch application is the main touchscreen library: touch.dll. This is where we start running into problems trying to run the cube on other devices. Without modifying the touch.dll on a given device ... there will be nothing to interpret finger swipes and communicate to biotouch. This is the point the original work by jasjamming and bepe went down the path of attempting to map a hardware button to be used to spin the cube. An executable needed to be created that would interact with biotouch in the same manner that the touch.dll file would, and trigger it to run the spin right animation. I'm not exactly sure what process these guys went through to figure this out ... but they did. From there ... it was efrosts creation of FTouchFlo that brought the next revolution. FTouchFlo is an app that allows you to map a file to be called when it detects one of the four finger swipe motions (up-down, down-up, left-right, right-left). With this, you could now map that same executable that was assigned to the hardware button to the left-right swipe action in FTouchFlo ... and now your cube spins with a finger swipe.
That's pretty much where the development stopped. I did a lot of research on this ... but pretty much all I could find from that point on was various people's input about it not working on this device, sort of working on another, etc. I simply couldn't believe that no one was pushing to enable the other cube interactions! It frustrated me to no end to know that I had a cube that was capable of spinning left, but no way to tell it to do so. So I rolled up my sleeves, read through countless pages of posts about what had been done so far, downloaded a disassembler, performed a lot analysis and theorizing ... and here we are today.

Hints, Bugs, and Issues
Hints
Problem: I installed the cube, and now my Contacts tab in HTC Home is gone!
Resolution: Delete the registry key: HKLM\Software\OEM\MASD\QuickDial
Problem: I installed the latest cab, and now I have trouble completing a gesture
Resolution: Try changing the GestureWaitingDelay in FTouchFloConfig.txt to a higher value (i.e. 50000)
Problem: I can't figure out what/how to map the cube to my hardware buttons
Resolution: Download my zip archive from post #1, and read the TFloCubeCtrl - Readme.txt file
Problem: I don't know/understand the TFloCubeCtrl options in the FTouchFloConfig.txt file
Resolution: Download the TFloCubeCtrl - Readme.txt file from the attachments in this post
Problem: I'm not very technical, and I don't know what to do
Resolution: Be patient and wait for there to be a final release. This is a beta, and is therefore not polished to the point of a one-click install
Problem: I end up activating the cube when I try to unlock in Slide2Unlock
Resolution: Add s2u2.exe to the exclude list in FTouchFloConfig.txt
Problem: My Touch Settings application has no icons for the APLauncher
Resolution: Be sure to add the AL_xxx.png icons to your Windows directory
Problem: Editing the FTouchFloConfig.txt file is confusing/difficult
Resolution: Check out the FTouchFlo Configuration Tool by schaps here: http://forum.xda-developers.com/showthread.php?t=345568
Problem: I installed the latest Xplode cab, and MediaHubMini is launching multiple apps
Resolution: It's a known issue ... try replacing your MediaHubMini.exe file with the one from the attachments in Post #1. Be sure to terminate the MediaHubMini process first, or remove the MediaHubMini (preload) link from Windows\Startup and soft-reset
Problem: I installed the latest Xplode cab, and QuickDial is not working
Resolution: It's a known issue ... try replacing your QuickDial.exe file with the "DeviceCheckPatched" one from the attachments in Post #1. Be sure to terminate the QuickDial process first, or remove the QuickDial (preload) link from Windows\Startup and soft-reset
More to follow ...
Bugs (for TFloCubeCtrl only)
When the device is locked, but the screen is still "active", an up-down gesture in FTouchFlo will still bring up the cube ... although you then can't do anything with it. (Fixed in v1.1.0)
Link files (.lnk) do not appear to work when specified as the <Command_2> parameter. (Fixed in v1.1.0)
In some non-HTC devices (Eten M600), TFloCubeCtrl is unable to detect that the QuickDial cube app is running (related to QuickDial issue listed below)
A DeviceLock issue detailed here: http://forum.xda-developers.com/showpost.php?p=1730847&postcount=453
ICE (Infinite Cube Effect) issue as detailed here: http://forum.xda-developers.com/showpost.php?p=1732668&postcount=460
PM me to report other items you think are bugs
Other Issues
When launching the cube using a RL or LR gesture, and the cube isn't already in the foreground (aka using the openSpin<Direction> command), exiting the cube using the close command causes some interesting "rainbow" effects on the today screen as the cube app closes. The rainbow colors then disappear ... but it's very strange for a split second. (Seems better to some in v1.1.0, but not solved completely)
When you have openSpin<Direction> set up in FTouchFlo and you perform a RL/LR gesture when in Landscape mode, you receive an error message indicating that Biotouch is not running. (Fixed in v1.1.0)
QuickDial app is running slow on some devices, sometimes taking 3-4 seconds to display the actual contact name/photos. Although it was never that slow for me, v2.0 of QuickDial loads even faster. Xplode's cab installer linked to on Post #1 has QuickDial v2.0
On non-HTC devices, the QuickDial app does not seem to load. For QuickDial v2.0, this is due in part to validation that the program is running on an HTC device (I'm not sure if QD v1.0 does this). JasonStern has made some progress on the QuickDial issues ... see Problem/Resolution above

Great job!

this looks great, cant wait to see the results.

Hope this helps...
Hey Kona...that darn cube is addicting!! Im one of the few also that has the cube running flawlessly on my 8525..buttonflow that is! After alot of trial and error and lots of hard resets...i got it working. First thing to do is get the cube running after a hard reset. Second I installed gullum activate cube cab..View attachment activate_cube.CAB. Not sure what it did but the only time I have to launch biotouch is after opening keyboard....not even after a SR!!! I guess it keeps biotouch running or somehow launches it automatically. Just my 2cents...

niterdr said:
Second I installed gullum activate cube cab..View attachment 57648. Not sure what it did but the only time I have to launch biotouch is after opening keyboard....not even after a SR!!! I guess it keeps biotouch running or somehow launches it automatically. Just my 2cents...
Click to expand...
Click to collapse
Just so you know ... typically a Windows Mobile cab file contains a _setup.xml file. This file is what tells the OS what steps to perform in order to install the cab file. This particular cab file puts four shortcuts into the Windows/StartUp folder. It also inputs the typical TFLOSettings into the registry ... most of which don't really apply to us, because it's touch.dll that's looking at these registry entries, and unless you've got an HTC Touch version of touch.dll, nothing is looking at those. The exception would be the Kaiser, where it does use some of those entries for the integrated TouchFlo scrolling.
I can't say specifically why this works for you ... it's a little counter to my experience, where I was finding that links to pre-load the cube apps in the startup folder were actually contributing to my black screens.
Regardless ... I can say a couple of things about this: 1) this also seems to support the fact that biotouch normally remains in memory. I wasn't sure that was the case, because the only way I could see the startup animation was running biotouch from scratch. I got response from my RFI in the Elf forums that confirms this. 2) I suspected also that the Elf pre-loads all of the cube apps, so they don't lag on the first cube rotation. I'm not really sure why this didn't seem to work on my device ... and I'll definitely be revisiting this concept when I do the analysis to determine the correct configuration for loading the cube with my new software.
Thanks for the input!

hey, i dont understand, AJE has ported the whole Biotouch on the HTC P3300..
Then what do you want to reinvent ?
Can't you see with him directly ?

Kona, you're not the only one who wants this working on a Kaiser.
My girlfriend got herself a touch and now I'm all jealous about her cube
I'm a programmer myself and I've been looking at the touch.dll from the kaiser. But I can't find the dll from the HTC Touch. Could you maybe attach it here so I can have a look at that one too. (Or link to it) I don't have the biotouch cube installed yet.
Do you have any idea if the cube should run in windows mobile emulator in visual studio ? I think i'm going to try that... less messing with my kaiser.

cAnArdtichAud said:
hey, i dont understand, AJE has ported the whole Biotouch on the HTC P3300..
Then what do you want to reinvent ?
Can't you see with him directly ?
Click to expand...
Click to collapse
To the best of my knowledge ... some people have indeed successfully created ROMs with a functioning Biotouch Cube interface (Artemis, Charmer, Wizard to name a few). But to do this, they actually replace the version of touch.dll that normally comes on the device with the version that comes with the Elf. While this is obviously a viable and functioning approach ... it can only be done through flashing a new ROM.
I wanted to pursue an option that could be installed via a cab. I also heard that trying to flash the Elf touch.dll on a Hermes was not working. Finally ... I haven't seen/heard of anyone trying to put an Elf touch.dll on a Kaiser, and writing my own biotouch interface application seemed a lot easier than learning how to cook my own ROMs.

Damn..it could be grat !!! xD

Denhomer said:
Kona, you're not the only one who wants this working on a Kaiser.
My girlfriend got herself a touch and now I'm all jealous about her cube
I'm a programmer myself and I've been looking at the touch.dll from the kaiser. But I can't find the dll from the HTC Touch. Could you maybe attach it here so I can have a look at that one too. (Or link to it) I don't have the biotouch cube installed yet.
Do you have any idea if the cube should run in windows mobile emulator in visual studio ? I think i'm going to try that... less messing with my kaiser.
Click to expand...
Click to collapse
No need to be jealous ... if you've already got the cube running, then try out my alpha release! Will run just as good as the Touch!
I sent you a PM re: the touch.dll
As for running the cube in the Windows Mobile 5 emulator ... I'm not sure. I never really tried ... and I'm not exactly sure how it works. I guess you'd have to able to install apps into the emulator environment (4 TouchFLO cube apps plus their graphics and registry entries). Anyone care to chime in about trying to do something like this in the Visual Studio device emulator?

I think i'm lucky !
i've just download your alpha and tested it.
it works great on my french kaiser .
no bug till now.i've tested it till 30 minutes.
perhaps a bit slow at the first seconds and then everythings went smoothly !!!
i don't see what could be improved !
btw, just wanted to point that i've duttythroy alpha2 installed at first and it worked on my kaiser with some modification :
i deldted apl - biotouch - hub fom windows\start up
and deleted a key in registry: quickdial
nice work !
one more question : why the time limit ?

Kona, just one suggestion. Would be great if the Cube can be rotated L-R and R-F using the D-Pad as well. I think that is far more reliable and quicker than using the finger.
Thanks for continue to work on the TouchCube as I thought it was an unfinished business.

Kona_Mtbkr said:
No need to be jealous ... if you've already got the cube running, then try out my alpha release! Will run just as good as the Touch!
I sent you a PM re: the touch.dll
As for running the cube in the Windows Mobile 5 emulator ... I'm not sure. I never really tried ... and I'm not exactly sure how it works. I guess you'd have to able to install apps into the emulator environment (4 TouchFLO cube apps plus their graphics and registry entries). Anyone care to chime in about trying to do something like this in the Visual Studio device emulator?
Click to expand...
Click to collapse
@Kona,
Do you think that this would work in the Blue Angel running WM6? I am asking simply because I do not feel like re-flashing my device.... again
Thanks!!!

megaman said:
I think i'm lucky !
i've just download your alpha and tested it.
it works great on my french kaiser .
no bug till now.i've tested it till 30 minutes.
perhaps a bit slow at the first seconds and then everythings went smoothly !!!
i don't see what could be improved !
btw, just wanted to point that i've duttythroy alpha2 installed at first and it worked on my kaiser with some modification :
i deldted apl - biotouch - hub fom windows\start up
and deleted a key in registry: quickdial
nice work !
one more question : why the time limit ?
Click to expand...
Click to collapse
Good to hear ... I hope you mean that even after the 30 mins, you still haven't had any problems.
The slowness in the first few spins of the cube is likely due to the fact that the individual apps for each cube face are not yet running, so they have to start up on the first spin. After that, it's much quicker to redisplay the cube face because those app stay memory-resident. In the installations that I've seen that use the ns script and Touchflo in the startup do not respond well when you try to "pre-init" the cube face apps in startup as well. I'm suspicious that it has something to do with this touchflo app, because in my mind, outside of preloading the cube apps, I don't know why anything other than FTouchFlo should need to be in startup. We'll see though ... I'll be working on getting a solid install from scratch soon.
And I agree ... I think dutty's alpha 2 install is a good base for me to start from (pending his approval). I'm hoping that I'll be able to rip the old parts out, and sub in my new app, and everything will work out great.

bchau said:
Kona, just one suggestion. Would be great if the Cube can be rotated L-R and R-F using the D-Pad as well. I think that is far more reliable and quicker than using the finger.
Thanks for continue to work on the TouchCube as I thought it was an unfinished business.
Click to expand...
Click to collapse
I was just thinking about what else I could try to add to my cube controller ... and spinning via dpad did cross my mind. This doesn't end up being exactly trivial, because I haven't made any mods to the actual biotouch.exe or any of the cube apps. When you're on a given face of an app ... it's that HTC app that is the foreground window. But I'm wondering if I can't register a listener for dpad events, and trigger the cube based on that. I'll put it on the wish list.
What can be done even sooner though ... is you will be able to assign any of the cube functions (open, close, left, right) to any hardware button you can assign a shortcut to. Actually, if you're familiar with link files, you can do it now ... but I'll be adding them in my next release probably too.

megaman said:
one more question : why the time limit ?
Click to expand...
Click to collapse
Oops, forgot to answer this. I added an expiration date simply because this is a very early alpha release. It hadn't yet been tested on anything other than my device ... and I didn't want someone to go crazy and burn it into their ROM.
Fear not ... I will remove the expiration date when I feel that the software is ready for a prime-time release. Although, I could be using this alpha just to get people hooked, and then complain about the vast amount of effort I put into the project and lack of donations received ... and threaten to never release a new version
Nah ... I wouldn't do that

[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?