Related
Hey all
The PocketCM keyboard isnt working with wm2003! Can anybody tell me why? I love this app, but it do not work with my device... that sucks so bad... Please mr. developer sir:
MAKE A wm2003 VERSION! PLEASE!!!
I totally agree with you! i´ve got wm2003, too... I donno why he don´t want to make a wm2003 version...
hm.. I think think many people are sad, because of this (including me!) The developer should share the source code with someone who has a wm2003 device so he could make a special version, but somebody told me he don´t want to give it to anyone.
Open source would be cool !
I own a WM2003SE device, and would love to see this app ported! the built in keyboard just doesn't cut it...
we should start a poll to find out how many people are interested in a wm2003 version!
Great Idea!!!
I've been pleading for this within the existing thread, but I don't even get a response let alone a wm2003 version!!!
I'll sign....
RR
FYI,
I had a reply from the creator. He only has a WM5 SDK installed. That generates THUMB code, that will not run on WM2003 (needs to be ARM)
But he promissed to give it another thought when the project reached final state.
Cheers
sounds like good news!
Can´t wait!
Well, I'll answer
You have to put yourself a little bit at the place of the developer: simply ask you thee basic question: how, when and why.
How?
- developing for 2003 device require (at least): a 2003 device (which I don't have), that the application is actually compatible (WM5 changes lot of stuff, some API used in the keyboard aren't the same or simply do not exist for 2003 device), a 2003 development environment (which takes time to setup) and a huge amount of time to test.
When?
- is it more interesting to develop 2 applications, maintain to application and try to make them stable, or do it later, when one version is stable? Here you have to think long term, not the simple "I want it now", but more what's the most efficient way to get a stable version for 2003, WM5 and WM6?
Why?
That seems to be the aspect your ignore the most, and for me, the most important:
- It takes me lot of time to develop my applications
- I'd like to keep them free, but I also want to get something in return, that's why I use Google Ads on my website, and I encourage donation... but that's not enough. That's also why I don't authorize people to redistribute it, I need your visits and that's why no version of the keyboard exists without time limitation.
- And most importantly: call me greedy or whatever, but what would I get in return?
For WM6 dev: I get a better app for myself, some fun developping it, and hope to get some money back.
For 2003: I don't need it, I don't get a better application, it's not fun to test and port, the fun part is already done.
So I'm simply (and honestly, it's not a trap,I'm just trying to explain my view of the things, maybe you can, considering this, explain me your view of things) asking you the question: what would be the motivation for me? considering the "glory and proud" of making it WM2003 compatible isn't really a turn on for me. Have you thought about that?
That doesn't mean I'm opposed to it, if you can put in place some "motivator", we can of course discuss it.
Well I do understand what you're saying, however from where I sit (and thats having no programming knowledge or experience!!) I'd be more than happy to pay for this app if it was ever developed, and Im sure Im not alone. (c'mon guys, back me up here!!)
The fact is, from what I've seen of this app, this looks as if it is one of the best input methods available, and believe me, I've pretty much tried em all!!
So for you to be asking for a motivator, I put to you COLD-HARD-CASH!!!
I know you're currently accepting donations, but like I said, Im sure other wm2003 users would be quite happy to pay a small fee for having this app up and running on our devices.
yes I do take into account the time and effort (and a wm2003 device) that would be needed to get this out, but seriously, is this impossible.
Even if you couldn't devote the time to it, surely there are other developers out there that (with your help, or code at least) could take this up and continue development.
Just venting my ideas bro, you've made a seemingly great app, let the rest (and im sure its a considerable community) of the non wm5/6 world share this functionality!!!
Other than that, well done on your achievements, I'll be watching the development of this very closely!!
RR
Well, from your point of view, there is no real motivation for him to port his apps for wm2003 and i really understand why. your arguments are very good...
so it´s hard for me tell you why the developer should make a wm2003 compatible version, because when i was in his position i wouldn´t do it, too...
But i will try to explain my ideas
Why:
Richierich is right when he said that it is one of the best input methods available and many people would be happy if they could use it with a wm2003 device!
How:
Share the source code with a developer with a wm2003 device (well i don´t know who this could be, but this community is very big so we can find someone)
When:
when the app works stable he could give the source code to another developer.
I´m no developer, so i have no idea about the amount of work... i just try to explain what i think about it from my point of view.
Thank you for reading.
I'm a developer myself, and trust me, if it's no longer fun. I stop doing it (unless it's work related and my boss requires me to do it).
And I'm sure, not even money (or any form of bribery) can be give enough motivation.
How about sexy gorgeous women? If you can give that, I might even do it myself!
hahaha.. just kidding guys.
I have a better idea... Howabout instead of you writing PocketCM for 03/SE, someone out there ports WM5/6 to my device
That would actually solve many of my other problems too
dito
my message needs to be longer than 10 charakters so i have to write this ****...but i just want to say "dito"
hope there will be a project of this for my imate jam.
I can understand tene (the developer), he is not interested to develop PocketCM Keyboard for WM2003 because he does not have motivation.
Well, there is nothing you can do unless he is motivated, considering this is a free application.
Maybe, you can bargain with him, and "hire" him to build the application
Ask him, how much do you need?
And then, find some people here, collect money, and pay him
That would work ... if tene is willing to be "hired".
If not (not now?), then yeah ... there are still several options:
- Ditch your WM2003 device and upgrade to a newer WM 6.0 model
- Find other onscreen-keyboard alternative, like "TouchPal" from www.cootek.com which people say it is better than PocketCM
http://forum.xda-developers.com/showthread.php?t=334437&highlight=touchpal
http://forum.xda-developers.com/showthread.php?t=335988&highlight=touchpal
Which is still FREE until Dec !
I would love to have a touch keyboard for Wm2003. there are still plenty of Wm2003 users. H4150 was one of the slimmest pda. I would love to have a touch keyboard for it....
i wait for this http://www.iwindowsmobile.com/
it´s propably similiar to pokcketCM keyboard
guys and all,
are you all unhappy of not having pocketCM 2003? well, please consider me also..
That works on my IPAQ HX4700 Win2003SE
try this. that is not easy to install but that works fine.
sorry for my english, i am french.
- edit PocketCM.reg with notepad to edit our options (language)
- Copy files on pocket pc in folder Program files
- execute regsvr_arm.exe and look for folder of pcmkeyboard and choose pcmKeyboard.dll
- The most difficult : Import PocketCM.reg into Register with a software like SKTools
http://s-k-tools.com/index.html?m_downloads.html#tools
- If the skin is not ok, who can download others on the http://www.pocketcm.com/theme.php?application=2
Hi guys, I'm new to this forum and it's a pleasure to be a new member! As a brief introduction, I'm completely new to HTC, Windows Mobile and any non-Symbian device! I've used Nokia's, Sony Ericssons & Motorola's all my life and Symbian is all I know, I think you get the picture......
Anyhow, I should be getting my HD2 within the next few days because I fell in love with it as soon as I saw it and I just want to know where to start?! This looks like the most comprehensive forum I've seen on the net and I couldn't think of a better place to start learning. I know it's a bit of a broad question and I have had a look through a number of posts to get my bearings, as such. I've seen posts about Roms, registry modifications, patches...... and it all sounds very interesting and I want to know all the functions and information I can about my new device.
Coming from the Symbian background, everything is pretty straightforward but Windows Mobile sounds a lot more technical and something I'm looking forward to learning about. Any information or tips about what I should & shouldn't do to help improve performance/tweak the device would be much appreciated and I'm a fast learner. PS I've seen this post:
http://forum.xda-developers.com/showthread.php?t=583638
and will work my way through it when I get the device, but it seems to be aimed at people with some previous experience with this platform. I'm sure you guys see these tpye of 'Help Me!' posts all the time but thanks in advance.
Hello Gargon, welcome aboard!
I too am new to these forums and I've spent a not-insignificant amount of time browsing threads on the HD2 since I made the decision to finally ditch the venerable nokia 6030 that has served me so well all these years. Being a self-confessed techie the HD2 appealed to me the very instant I first caught a glimpse of it in all its Kubrick monolithic glory and as soon as O2 release info on their tariffs I will be seriously weighing up my options.
Now, let's get down to the nitty gritty. As a disclaimer I've only been here a short while so I wouldn't be surprised if I get a few facts wrong. Hopefully someone will correct me if I do!
The HD2 is powered by Windows Mobile 6.5 edition and as you might imagine it's not too dissimilar in how it operates to the PC desktop version. You have a desktop, start menu, program files etc. with all the various settings held by the registry. The beauty of WinMo is that it is far more customisable than the iPhone OS/Symbian in that you can change pretty much everything you see and also how you interact with the device. For example, a developer on these boards has released an application which enables the vibration feature on almost every keypress whereas the default HD2 only goes so far. Another dev has released an app which changes HTC's desktop from a 3x3 grid of shortcuts to 4x4. You can even do away with HTC's superb frontend entirely and install something like SPB Mobile Shell which has a snazzy rotating cube effect desktop and many other alternative enhancements (although you will have to pay for this). And this is only the tip of the iceberg! There are thousands of applications and games out there on the internet, and with Microsoft finally getting into the appstore gig we can expect a well-stocked central repository for software sometime in the near future. Failing that, google is our friend
With the help of the talented and selfless developers here at xda-dev almost anything is possible, including the potential for changing the operating system entirely, so you can't rule out the HD2 one day running Android or WM7 somewhere down the line, however this depends on one crucial bit of software -- the Hard SPL. Without this essential bit of kit, peons such as myself are unable to reflash the device to a different operating system or even a different version of the current OS (e.g. a lite version to save valuable ROM space, or an enhanced version with greater functionality). Everything hinges on this being developed by the code masters behind the scenes however such projects require a lot of skill, time and effort and such is the support of the community here that monetary donations are pledged in gratitude for past endeavours and in the hope of new enterprise.
As for installing applications themselves, I haven't yet delved deep enough to give you a comprehensive answer, however I suspect that there are FAQs on the parent forums which will give you all the information you need. From what I can tell, applications are released in .cab format which are executed from the phone and self-install. I can't wait until I can get my grubby paws on this masterpiece and get busy pushing buttons! I'm sure I've missed a whole lot of information but my lids are getting heavy and my battery needs charging. I hope this wasn't too patronising for you and I'm sure some other people here will gladly fill you in on anything I've missed.
Welcome aboard, great first posting. Showing the threads you read already makes many people want to help you more.
If you come from Symbian, some stuff will be the same, i.e. you use icons for programs.
What differs the most is the customization possibilities and the level of deep control you have over the behaviour of your new machine.
Get to grips with Microsoft Mobile Device Center, (syncing your data).
Do you have an Exchange account or Gmail ? You can setup your device to have pushmail connectivity with GMail or Exchange.
If you don't own an Exchange Server, you can setup your own free
Custom Domain at http://domains.live.com and have your own email adress as a LIVE-ID and have pushmail with it (free).
Then, I would dig in to the many cool free applications around.
Yes, hunt for .cab files as they will install over the air (OTA) and from your device.
Another tip: When you get your device, start at the first Icon, view it, try and dig deeper in the menu's, always. Press and hold the screen/text to see if there are context menu's.
Then work your way through all the settings and icons available. It will take you about 3 days to see all the menu's and options, although the first 80% you will discover the first day
Hope you will enjoy the transition.
Hey guys
First off, this a awesome site with heaps of help. And advice which is great
Secondly I amnew here too and hopefully getting my hd2 soon. Can't wait!!
Thanks a lot for the replies guys, very informative H2D2 and thanks for the tips lucid. It's good to know that there are other people in a similar situation to myself! If anyone can post any relevant links to any apps or roms/cab files that might be useful for a first-timer then it would be much appreciated. In the meantime, I'll keep doing the research and, if I find anything myself, I'll post it here. Thanks again.
Well I'm new as well so hi everyone!
I used to have a wm phone but that was a few years ago and things have changed a lot since then... so have a bit of catching up to do. Been browsing on here the last few days and ordered the HD2 this morning.
Gargon, I'm sure you'll get used to it all in no time, I know it all looks confusing at first but really it's not that bad and I'm sure the nice people on here will help if you're stuck.
Greetings our new community members
I was in the same situation as You guys half year ago when I purchased my first WM device, the Diamond2. And now Im awaiting my HD2 already ordered
As for the Windows Mobile platform, it is the most powerful, sophisticated and versatile mobile platform ever made, and that's why it has always attracted more advanced users. But on the other hand, it is in many ways very similar to Windowses on your PCs At first you may feel a little overwhelmed of all the functions, tips, tricks, registry hacks and so on. But what's great about Windows Mobile platform, is that once you start to "feel" it, then playing around with your phone becomes extremely addictive. I remember my first week with the Diamond2, it was nothing else than playing with it, installing and testing every trick i could possibly find
Moving on to the relevant stuff:
First of all, you should equip your device with a decent file explorer, as the native WM one is a bit clunky. I recommend Resco File Explorer. Second, equip yourself with a registry editor, as you gonna need it for tweaks. Resco Explorer has a plugin for registry editing and there are even desktop PC editors which you can use when device is connected to the PC.
As for application installation, it can be performed in 2 ways:
1).cab files. These are like .sis in Symbian. You run them directly from the device just by executing them from any file manager.
2).exe files. Those can be installed from your PC when the device is connected to it. Sometimes developers make small apps for phones which are in form of exe files which are designed to run directly from the device. This is possible because every app after installation usually has its folder in Program Files where an exe file of the app itsself is stored (exactly the same as on Your PC Windows)
Moving on to the interface. One of the biggest advantages of Windows Mobile is that it enables you to change practically the whole interface with minimum effort. The native WM interface is unfortunately very old and not finger friendly, and thats why every major company designed their own interfaces. On the HD2 it is called Sense. In fact Sense is only a further developement of an interface which was called TouchFlo 3D. And one thing more you should know. Developers on this forum use the code name of this interface, which is Manila. HD2 has the latest Manila v2.5. So basically Manila=TouchFlo=Sense.
Feel free to ask any questions, everyone of us was a newbie at first I personally am very happy to see new people being attracted by new fantastic WM devices. I myself was a Nokia/Symbian fan for many years, untill half a year ago I discovered that I was living in the darkness all these years
The XDA-Developers is one of the greatest, biggest and oldest communities on the whole internet. This makes this community concrete, mature and serious. This means that members are very helpful to each other and they always communicate with a certain level of etiquette, so You surely won't hear any offensive words, swears or any vulgarisms
So enjoy your new devices and this community, as it will bring you many happy moments, i guarantee this to You
the wiki is a great tool (not much on the HD2 in there yet) but background reading on other devices is good.
As long as you're willing to take time to learn to use the search (often searching around the term you're looking for) then you'll solve issues you may have quickly as well..
several of us are happy to discuss stuff on PM as well..
and don't forget if you find something that you think others would find useful,
The WIKI is always there, to be edited at your leisure
Welcome
Very nice attitude from Gargon01 and H2D2.
You are on the right track about the winmo os.
In itself it is clunky on the surface but the structure sits on the registry database which is accessible through a registry editor.
This forum is quite unique and must be the largest of It's kind, that is, a community of smartphone developers/hackers.
I have been dropping in for 4 years but only started flashing recently after buying an HD.
The HD came with an earlier development of Touchflo and I saw rom versions on Youtube etc of more advanced versions from XDA Devs.
I took the plunge in flashing roms and have been addicted ever since.
I am running the latest version of sense on my HD but am awaiting an HD2 from clove tech on the uk for which sense was made.
There are many brilliant people in this community who generously offer their creativity, time and energy.
You are in the right place. More will be revealed.
Thanks a lot for the responses guys, exactly what me and I'm sure a lot of other new users are looking for! I'll look for the Resco File Viewer jgal, there was a similar app called Modo on Symbian that was also used for deep-file exploration/modification purposes.
Also, it's good to know that there are a lot of similarities to the desktop version of Windows. I'd like to think that I'm pretty proficient with that so I'll look forward to taking that knowledge and applying it to the HD2.
A big thanks to all the other users who have contributed to the post as well! I was pretty sure that my thread would fade away into non-existence but it's good to know that people seem genuinely interested in offering help and advice.
I should hopefully be getting the handset on Monday so I'll give it a good examination and keep you all posted should I run into any problems. Keep the tips/links coming though, my brain is like a sponge!! Cheers.
How is Android actually ported to work on the Vogue?
Are you guys literally taking the source code, changing things, compiling & releasing it?
How have you guys learned how to do it?
I'm really interested in helping out and would like to learn more, so any info is great!
Still interested. If any developers could chime in I'd really appreciate it.
Even if you just post a link to some resources I could read.
I googled...I found..
http://www.kandroid.org/android_pdk/index.html
It may be old IDK....Have fun
Thanks!
If anyone has anything else.. please post!
http://cs-alb-pc3.massey.ac.nz/vogue/
^A bit of info about how the project came to be and progressed
Thank you for the reply!
So, when it comes to myn and plemen releasing their builds, what exactly are they doing? Are they getting the source code from Google and completely customizing it, or are they customizing a source that has already been ported for the Vogue? Or... what?
To summarize:
The brunt of the porting effort is in the kernel (the heart of Linux) - a kernel which supports the Vogue hardware needed to be constructed, and the Android-specific extensions added and made to support the hardware. Martin (dzo) did most of the work on that.
Then, there are some core user-space libraries in Android which interface with the hardware and kernel (audio and radio being the big two, with lights, GPS, camera, etc. following). These also needed to be created and updated to support the Vogue hardware. Each time a new Android version comes out, these libraries tend to change and parts need to be rewritten to keep up with Android. A lot of people were and are instrumental in this process.
Then comes the questions you're asking, the "userland" pieces of the build: porters can start from an AOSP (Android Open Source Project) build, which is built ground-up from the released Android sources, a build from another phone (Tattoo, Hero, Droid, etc.), or an SDK emulator build (which is usually not preferred because SDK builds have extra debugging and are missing features for real hardware). To "port" a build, the Vogue libraries are copied in and init scripts and build properties are updated to support the Vogue's screen resolution and hardware initialization. Some porters go an extra mile and unpack, modify, and repack application data to support 320x240 better or to add new themes. For the most part, this is what people like myn and plemen do.
Builds can also be "zipaligned" (package files are aligned to match cache and block boundaries, so they're loaded faster), and image files downsized or removed to enhance speed.
I know how to do the WM stuff - and have some old kitchens. I used to be fairly involved in doing my own back in the Kaiser days, but never did publish them (there were always questions about whether it was REALLY kosher to do so)
Well, Android is Open Source (mostly) and so I'd like to get involved with it for the HD2. I'll publish here and maintain as well - if I come up with something useful.
Does anyone have a framework to start with on getting started? Is it best done from Windows (Win7 here) or do I need to build up a Linux box for this?
If it's already here (I looked around) please point me to it... or any online resource for that matter.
Mostly interested in cooking up NAND stuff....
(I build and write software - including kernel code in the FreeBSD realm, so I'm familiar with the "hows" - just need the correct pointers to the tools and bits I need along with a primer; I can take it from there.)
Thanks in advance!
I'm interested in the same kind of info, but it seems it's a secret kept somewhat close to the chest, and although there are tutorials aplenty for the end user, there is a clear lack of tuturials on how to make your own ROMs (be it WinMo, or Android). Either "chefs" don't want any more clutter and garbage around, or they don't think there is interest on such info...
Anyway, here is an article to get you started (little meat in the info, but dig around the wiki):
http://www.htc-linux.org/wiki/index.php?title=QuickDeveloperStartGuide
u Guy's even have take look to chef corner in this site
Hi All,
I'm a software developer, reasonably comfortable with compiling apps in Linux, though still got more to learn on inner workings of the full system.
I've been thinking about following the Linux from Scratch book for a while - and also about converting my Nook e-reader into a useful device for developing on when out im the sun.
I guess there are some significant challenges here - device trees and commercial secrets, perhaps some crypto keys used for signing update images to boot (I'm familiar with these problems, but not solutions or good workarounds).
What I'd really like is a good understanding of:
- what tool chain I need to setup
- What has been tried already and what the problems were
- any further help/datasheets that can get me going
I'd have posted this in the 'android development' area as the closest forum for what l'm trying to do, but apparently I'm not allowed until I've got my post count up - so I'm being forced to post in 'general'. If someone agrees and can move it, that would be great.
P.s. I have searched the xda site, but I'm not finding what I'm looking for. I'm sure it must be here somewhere, so any pointers/links on where it is would be appreciated.
SimonSimpson said:
Hi All,
I'm a software developer, reasonably comfortable with compiling apps in Linux, though still got more to learn on inner workings of the full system.
I've been thinking about following the Linux from Scratch book for a while - and also about converting my Nook e-reader into a useful device for developing on when out im the sun.
I guess there are some significant challenges here - device trees and commercial secrets, perhaps some crypto keys used for signing update images to boot (I'm familiar with these problems, but not solutions or good workarounds).
What I'd really like is a good understanding of:
- what tool chain I need to setup
- What has been tried already and what the problems were
- any further help/datasheets that can get me going
I'd have posted this in the 'android development' area as the closest forum for what l'm trying to do, but apparently I'm not allowed until I've got my post count up - so I'm being forced to post in 'general'. If someone agrees and can move it, that would be great.
P.s. I have searched the xda site, but I'm not finding what I'm looking for. I'm sure it must be here somewhere, so any pointers/links on where it is would be appreciated.
Click to expand...
Click to collapse
I have tried to get info on such things three times over 2 years for different devices, no one every seems to point me in the right direction, the most i have been able to find out is how to make compile cm and a little bit of how to customize roms, not to be a downer but i think the process is often so different for ever device and difficulties usually happen that the only people that build roms are people that have either have experience I n some form from their job, just edit existing source for cm(updating to a new version, customizing roms ect...) or have screwed with the stuff for years till the point that they just figured out alot of problems themselves. Wish a could find a good guide myself to atleast get the basic dependencies required for a device to boot together, if i could get something to boot the rest of the issues could be worked out with trial and error, boot noone on xda, Android authority, Reddit or cm's own forums goes into enough depth to make that possible.
Hi jaykoerner,
Thanks for your reply - good to know I'm not alone with my echo!
I've discovered some useful links if anyone wants to begin getting to grips with all this...
1. XDA Devs has a wiki (not sure how to find from the forum links...?)
http://forum.xda-developers.com/wiki/BN_Nook_Simple_Touch
2. There's a (atleast one) customized kernel (and probably a dev-tool chain) available on GitHub:
https://github.com/javifo/NST/tree/master/kernel -- including kernel compilation instructions
https://github.com/javifo/NST -- root of the repository.
3. Parallel to Raspberry Pi kernel compilation (so you may want to learn from that as it probably has more articles)
https://www.raspberrypi.org/documentation/linux/kernel/building.md
I'll post more when I next do something with the information (Still want to understand more on the android HAL)
Hope that helps someone!
SS.
SimonSimpson said:
Hi jaykoerner,
Thanks for your reply - good to know I'm not alone with my echo!
I've discovered some useful links if anyone wants to begin getting to grips with all this...
1. XDA Devs has a wiki (not sure how to find from the forum links...?)
http://forum.xda-developers.com/wiki/BN_Nook_Simple_Touch
2. There's a (atleast one) customized kernel (and probably a dev-tool chain) available on GitHub:
https://github.com/javifo/NST/tree/master/kernel -- including kernel compilation instructions
https://github.com/javifo/NST -- root of the repository.
3. Parallel to Raspberry Pi kernel compilation (so you may want to learn from that as it probably has more articles)
https://www.raspberrypi.org/documentation/linux/kernel/building.md
I'll post more when I next do something with the information (Still want to understand more on the android HAL)
Hope that helps someone!
SS.
Click to expand...
Click to collapse
My initial thought was that toolchain should match the underlay Linux kernel of Eclair (2.6.x.y) for us to be sure it could be run on NST. This info that I still have to search through is certainly helpful. Thanks!
SimonSimpson said:
I guess there are some significant challenges here - device trees and commercial secrets, perhaps some crypto keys used for signing update images to boot...
Click to expand...
Click to collapse
Neither the NST or the newer glows use device trees.
In the Glows this is all handled by the custom ntxconfig which allows simple configuration.
For building Android apps, you use the straight Android SDK, possibly also the Android NDK (for native code).
You'd also use the NDK for building command line utilities.
I've never built a kernel from scratch, but I have binary modified/patched them.
There is the simpler bit of patching system image ramdisks which can be conviently handled by my imgutil.exe in the signature.
If you want to do audio, you really are better off with the Glow4 (7.8") which actually supports it.