Hi people, is anyone working on a port of Android for the Charmer?
Thanks
Android as directboot won't work. And booting out of WM won't work because it'll be too slow.
So sorry but I think it won't work.
But maybe Vlodeck will correct me.
As you said, the only way to run it is through WM and it doesn't necessarily have to be slow but unfortunately it will. I'm not a huge fan of porting other operating systems - it will never work properly.
I just said it is slow because WM6 or6.1 itself are slow. So also with WM5 there won't be much power left for booting an other OS. We would need at least 300MHZ or more for that. And overclocking so much would be very stupid.
Thanks for the info.
Thats overclocking is for.I wish i could cook, i like Android interface
I think we haven't been clear enoght last time. I'll summ up everything about Android on Charmer:
1) Charmer is too slow. You can't overclock it over 300MHZ and We would need at least 400MHZ to run it good.
2) You can't cook Android. It is Linux and you have to cross compile it. I'm good in Linux questions and I can compile and build a Linux from scratch but cross compiling is too hard for me too. And you'll have to change all scripts too.
3) There are no drivers for the Charmer. You'll need to write them. You can't use the Windows Mobile drivers.
4) Android doesn't support many apps if it is ported. You would have to recompile all apps. And for that you first need the code. And the code isn't aviable for the most apps.
So the answer is. YES! ANDROID WOULD WORK ON CHARMER!!!!
But we don't have the time and mans here to get it working. It would take me alone 50h to get it booting. And 150h more to analyse and rewrite the drivers. To compare: I can port a new XIP and clean up the SYS in 1h. After all tests and fixes 5h are over.
SO IT IS POSSIBLE BUT IT WOULD BE SLOW AND IT WASTES TOO MUCH TIME UNTIL IT WORKS.
So learn more about it and find 5 guys helping you. I'll help then too.
Hi Charmer users!
As an ex-charmer user, I feel like I have to tell you.
At the Universal forums, we're working a port for the Universal, that has a CPU clocked at 524 MHz at factory settings, and we tend to use it at 620 MHz OC'd, but even then it is painfully slow. Please sorry for the bad humor, but what do you think, how'd it run on a processor that is more than three times slower? I don't think you'd have too good results. Though it IS possible, to boot Android on it - as ChrBeck said - it simply doesn't worth the effort to make it work. There was a Linux port in work for the charmer when I had mine, but I guess it's dead by now. I don't want to disappoint anybody(that was done by ChrBeck anyways... just joking), but this won't work any time soon. I hope you guys and gals have a good day.
Have to say something again. We have Android working on the Kaiser too. It has a 400MHZ CPU and Android runs very good. Sometimes it hangs for some seconds but normaly it runs very quick. But anyway it won't work good on Charmer. And there are bugs in ported Android. (On Kaiser the pin field is bad for example).
So much to say about that.
Guys, apparently Linux is running on Vogue (Touch). See http://forum.xda-developers.com/showthread.php?t=382265.
As far as I know, it is based on OMAP850 too, same 200Mhz clock. Probably there are some differences in hardware so drivers need to be changed but I don't think it's hopeless...
Then start porting. Install ubuntu and crosscompile it. Start writing drivers from scratch for display and Board. And get a Haret working on Charmer. Then you'll have Android. Have fun it are 50 or more houres for such an old device. It is senseless.
But you can start I'll support you with infos as good as i can.
ChrBeck said:
Then start porting. Install ubuntu and crosscompile it. Start writing drivers from scratch for display and Board. And get a Haret working on Charmer. Then you'll have Android. Have fun it are 50 or more houres for such an old device. It is senseless.
But you can start I'll support you with infos as good as i can.
Click to expand...
Click to collapse
Just bumped into this thread -- check out Wing Linux: http://wing-linux.sf.net. It's Android and Linux for omap850-based devices, and we've gotten pretty far so far. We're running cupcake on our stable release now, but eclair is in testing. The Charmer isn't officially supported, but you might have luck with one of the other board configurations, and we're more than happy to help getting new devices running. Give it a shot! We've got an IRC channel at #wing-linux on freenode too, so feel free to pop in!
- d
I'll look into it sometime next week if I get some time.
i think WM is the best OS.the overcloking is safe?
Related
But, this is a developer kit and likely virtual CE6.
And any device hasn't WinCE 6 i think, so what is important with this..
https://www.microsoft.com/windows/embedded/default.mspx
"Choose right system for your device" sad microsoft but no one have wm 2006 device.
Is any body can give better explanation here. I'm amazed...
Isnt the embedded branch quite diffrent to the mobile branch, though?
EQUANCY: AFAIK some people (at least one) do have Crossbow working on a WM5 device. So long as you get full driver support, theoretically the OS should work on existing hardware...
V
No not completelly
Percz said:
Isnt the embedded branch quite diffrent to the mobile branch, though?
Click to expand...
Click to collapse
"There is no branch of WinCE OS's
This is a development kit and work with an emulator, You may develop pda applications in VisualBasic 2005 with this plug-in"
But i curious first of WC 2006 devices will come 2e Q'r of 2007, i find some explanation and comment about it.
And if you develop a winCE 6 application with this software... how do you publish it? for what.
vijay555 said:
EQUANCY: AFAIK some people (at least one) do have Crossbow working on a WM5 device. So long as you get full driver support, theoretically the OS should work on existing hardware...
Click to expand...
Click to collapse
but only theoretically sad you. How do you get support for unpublished operating system? I think Windows Mobile systems produced especially for devices.
Now,
If I try install Windows Mobile 2006 to my BlueAngel there is no drivers in wm2006 of Blueangel hardwares ( Bluetooth, Phonesupport etc... )
I think so..
CE 6 Has a slew of improvements, and amongst others:
* number of concurrent process increased from 32 to 32000
* mem allocation limit increased from 32MB to 2GB per process
* strict separation between user mode and kernel mode
* user mode drivers
The changes tap everywhere, including driver achitecture. I bet WM5-2003 BA drivers won't be compatible with this beast... unfortunately.
EQUANCY:
How do you get support for unpublished operating system? I think Windows Mobile systems produced especially for devices.
Click to expand...
Click to collapse
That's the whole point - IF you can get the drivers, ie if your manufacturer releases a properly made version of the OS, there's no reason why it shouldn't work on current hardware. However, like the WM5 for BA hack, it's clear that incomplete OS releases aren't perfect.
But, WM6 is working on current hardware, but it's up to the manufacturer to finalise it and release it, and somehow make some money out of their effort.
V
that's quite a few infos there brazialian joe. let's hope we get wince 6.0 to play around soon
imatrix said:
that's quite a few infos there brazialian joe. let's hope we get wince 6.0 to play around soon
Click to expand...
Click to collapse
I would love to see it, but I would want to see a 100% functionally complete release of a WM5 ROM for the BA first. We are closer than ever now, with just a few niggles pending...
Imagine everyone goes ballistic on CE 6 and completely forgets about WM5. We are SO close to a perfect ROM, with the latest Helmi releases... I hope the WM5 BA ROMs get the last pieces in place before the first WM6 devices are released, so that we can have a great upgrade in our hands, and then this forum will EXPLODE with development efforts trying to shoehorn WM6 on Wizard/Universal/TyTN/Excalibur/Artemis/etc/etc/etc...
and you forgot BA
Midget_1990 said:
and you forgot BA
Click to expand...
Click to collapse
Hey, I wrote etc/etc/etc, have you missed it?
I wanted to highlight that we now have a somewhat small enthusiast community revolving around putting WM5 on a machine which only has official support for 2003SE (but packs more than enough punch to run WM5, thank you ). With the coming of CE6/WM6, ALL machines which officially run WM5 will fall into the same state of the BA, and we will have a much bigger community trying to get CE6 run run on much wider number of devices.
I believe the way to go with CE6/WM6 in xda-developers will be to have a single ROM Kitchen effort, because there are several different machines which are more-or-less the same platform. We have a TI OMAP 850 family (wizard/artemis etc), an Intel Xscale family, (himalaya/blue angel/universal etc), Now a Samsung family starting up (TyTN), I think it will make sense to have a more unified effort to put CE 6 on all these devices. I think a ROM Kitchen which covers all different devices would save duplicated effort for all devices...
Brazilian Joe said:
We are SO close to a perfect ROM, with the latest Helmi releases...
Click to expand...
Click to collapse
this is a joke of the MONTH !! DDDDDD
Brazilian Joe said:
Hey, I wrote etc/etc/etc, have you missed it?
I wanted to highlight that we now have a somewhat small enthusiast community revolving around putting WM5 on a machine which only has official support for 2003SE (but packs more than enough punch to run WM5, thank you ). With the coming of CE6/WM6, ALL machines which officially run WM5 will fall into the same state of the BA, and we will have a much bigger community trying to get CE6 run run on much wider number of devices.
I believe the way to go with CE6/WM6 in xda-developers will be to have a single ROM Kitchen effort, because there are several different machines which are more-or-less the same platform. We have a TI OMAP 850 family (wizard/artemis etc), an Intel Xscale family, (himalaya/blue angel/universal etc), Now a Samsung family starting up (TyTN), I think it will make sense to have a more unified effort to put CE 6 on all these devices. I think a ROM Kitchen which covers all different devices would save duplicated effort for all devices...
Click to expand...
Click to collapse
well said,joe
starik said:
this is a joke of the MONTH !! DDDDDD
Click to expand...
Click to collapse
Seems some ppl don't share my view... but with every release we get more features and fixes available. In the last ROMs we achieved an incredible speed boost thanks to mamaich pagepool tweak. We still have a few issues but it is very usable as-is. The next release will integrate a few fixes in power management and wifi, and we also have an alternative bluetooth stack. There is also Connection Sharing which is replacing WModem for PCs to browse using GPRS (for AKU 3.0+). We still have the problem that MS stack has a hard time on running A2DP, and the alternative Broadcom is having issues with Headset/Handsfree, but there is ongoing effort to solve it. The application compatibility problem is something inherent to the upgrade to AKU 3.0, thus not specific to BA. What else do you want?
????!!!!!!!!!!
a "Mashed Potato" maybe? joke..
I want that WM6.0 in my BA.. perfectly!!!!!!!!!
It is a point of view
borjok536 said:
a "Mashed Potato" maybe? joke..
I want that WM6.0 in my BA.. perfectly!!!!!!!!!
Click to expand...
Click to collapse
Bro it will not rock the skyes for you I'm sure!
Remember every next generation operating system is meant for better, bigger and fater devices. So WM6 will have more benefits for the newer devices not for ours. So at some point it might be better to have AKU 4 instead of the original WM6. Remember when Microsoft released the XP. Most of the people were angry because of the slugishnes... right. OK couple of years later with better machines more mem etc. nobody was complaining. Now I got my Vista and it is OK. Not faster not slower, though I put 2G of mem. Now everibody is angry because there is no drivers, when you put it on 512MB mem (where the XP excels) it will be dead as a rock.
You got my point. It is the same with the phones. Now the phones are PC and the WM5,6,7 is the OS. It was not long time ago when the PC were 500Mhz right? Our generation phones are 200Mhz. the next ones are 500Mhz and the next gen of mem is 16GB 32GB so that's what the WM6 is meant for. So don't expect too mutch. After all the OS is combination of functionality, speed, look and reliability. Ask me if I will change my company's 50 PCs with the Vista? It will not happen untill 2 years, maybe 3! After all I just want my business runing. And if I use Windows Mobile for business, ie. sales, remote access, DB etc. I will prefer cheaper mobile devices (older is OK) but with the functionality of WM6 ie. AKU5,6,7 i dont care. So this forum will stay here for long long time and it will not stop working on AKUs for WM5 until there are devices that can not sustain WM6. Of courece it will cover WM6 with AKUs...
Cheers
tubeme said:
Bro it will not rock the skyes for you I'm sure!
Remember every next generation operating system is meant for better, bigger and fater devices. So WM6 will have more benefits for the newer devices not for ours. So at some point it might be better to have AKU 4 instead of the original WM6. Remember when Microsoft released the XP. Most of the people were angry because of the slugishnes... right. OK couple of years later with better machines more mem etc. nobody was complaining. Now I got my Vista and it is OK. Not faster not slower, though I put 2G of mem. Now everibody is angry because there is no drivers, when you put it on 512MB mem (where the XP excels) it will be dead as a rock.
You got my point. It is the same with the phones. Now the phones are PC and the WM5,6,7 is the OS. It was not long time ago when the PC were 500Mhz right? Our generation phones are 200Mhz. the next ones are 500Mhz and the next gen of mem is 16GB 32GB so that's what the WM6 is meant for. So don't expect too mutch. After all the OS is combination of functionality, speed, look and reliability. Ask me if I will change my company's 50 PCs with the Vista? It will not happen untill 2 years, maybe 3! After all I just want my business runing. And if I use Windows Mobile for business, ie. sales, remote access, DB etc. I will prefer cheaper mobile devices (older is OK) but with the functionality of WM6 ie. AKU5,6,7 i dont care. So this forum will stay here for long long time and it will not stop working on AKUs for WM5 until there are devices that can not sustain WM6. Of courece it will cover WM6 with AKUs...
Cheers
Click to expand...
Click to collapse
Blue angel has 400 mHZ
I heard that wm6 was designed to work on devices of about 200 mHZ.
I get ur point about the memory though, but we have SD cards
Hey guys, it would be better to first read about something before posting your nice but totally wrong imaginations. WinCE6 is connected with WM6 in no way. WM6 is still based on WinCE5. It is only a bit optimized and "nicefied" version of WM5.
Well its very nice to see ANDROID running on VOGUE..!!!
Can any developer help in running this on the ELF, we ELF users would really appreciate the help..!!!
MOD's please consider this as a desperate plea & don't close the thread..!!!
Thank you..!!!
Sorry, man... you guys are OMAP, not MSM. Plus with your RAM/ROM space it'd be pretty crummy performance. Half the system (the /data partition anyway) would have to reside on sd, and while android is pretty fast for us even from sd, we have twice the RAM.
So, all in all, I don't see it being practical.
I am curious sorry for being lazy and not searching around, what HTC GSM phones that didn't come native with Android are able to run android? for instance: Diamond, Nike? etc...
Thanx,
Nas
heartsurfer008 said:
Well its very nice to see ANDROID running on VOGUE..!!!
Can any developer help in running this on the ELF, we ELF users would really appreciate the help..!!!
MOD's please consider this as a desperate plea & don't close the thread..!!!
Thank you..!!!
Click to expand...
Click to collapse
This would be difficult:
1. The ELF runs the OMAP chip as mentioned. This makes it incompatible without a lot of extra work.
2. Google/HTC already did a lot of the platform setup for the MSM chips (granted dzo had to rewrite a lot of it). Having to rewrite this code is time consuming.
3. No developers have an ELF. If you can provide one, and can get a dev to champion it, you may see support. It takes a lot of trial and error (i.e. debugging) to bring Linux up on a new device. Support on the Vogue took a year.
4. The Droid technically runs an OMAP processor, but it's several generations ahead of yours.
masalma said:
I am curious sorry for being lazy and not searching around, what HTC GSM phones that didn't come native with Android are able to run android? for instance: Diamond, Nike? etc...
Thanx,
Nas
Click to expand...
Click to collapse
In our class of devices:
http://pdadb.net/index.php?m=specs&id=801&c=htc_touch_cruise_p3650_htc_polaris_100
http://pdadb.net/index.php?m=specs&id=736&c=htc_touch_dual_p5500_htc_nike_100
Both of these devices are supported by our Android tree (i.e. Myn's Warm Donut). Several people around here run on the Polaris and Nike.
Polaris I think is the better supported device. Not sure about the Nike.
The GSM on the HTC Diamond is further along than CDMA. There's active development there.
Try Wing Linux. Its Not Recent but they have managed to get android running.
The intent of this thread was to provide a consolidated answer to all of those waiting patiently (some, not so patient) for a complete Android ROM for the SE Xperia X1.
Many perceive Android as "a hacker's OS" because it is both open source, and supported on so many other HTC devices. Because of this, I suspect many of the "spectators" here (like me) incorrectly assumed that Android on Kovsky (or, any HTC smartphone) would be a straight forward affair, considering some of the amazing work done here with the Windows Mobile ROMs.
It seems, however, that creating a usable Android ROM for Xperia is far more difficult than creating WM6 ROMs? Android has been out for quite some time and there's still no widely available Android ROM for Xperia X1. It is for this reason that I've started this thread.
I'd like to hear from those that have/are working on Android about the challenges in putting together an Android ROM for Xperia X1. What has contributed to this being a difficult OS to port to Kovsky?
Is it driver support? Perhaps Kovsky has a unique selection of hardware that complicates the process? Or, has much of the effort been directed towards Haret vs. a native ROM? If so, why? Can the Haret work be merged into an effort to create an Android ROM or are these different approaches completely exclusive to one another?
Perhaps there are IP/DRM/license issues that are complicating the effort? I'd very much like to hear from ROM chef and devs working on this port.
While it may seem like a idealist perspective, I wonder if some dialog on the issues surrounding an Android port/ROM might result in greater community involvement, and ultimately a stellar Android ROM for one of HTC's most beautiful smartphones. I'm certain that interest in Android on Kovsky is very high. Are there areas where the community might be able to assist with direct hardware, financial or other contributions?
So please, sound off. I'm very interested to hear about chefs/devs experiences with Android and I'm certain there are many here that would like to hear more about this port.
I just didnt know how to tell all you told here... I really want to know because I love my x1 and I love Android.. but i can"t help
i have just check out the Kovsky project from Gitorious, but still don't know how to work on it. 'cause i don't have much knowledge about develop kernel and open source, why don't we have a tutorial thread about this?
You people asking when a Android rom is coming just about every day are so funny. First of all their are still major issues that need to be worked out. Android running from haret is not even every day usable yet so what is the freakin point of expecting a rom now or asking about it? Do you guys want a rom where you phone won't even last 2-3 hours, GPS dosen't work along with the camera etc......? We need All the issues fixed before we can even be thinking about a rom. When Android from Haret is everyday usable then lets start talking about a rom. So can we please give the Devs a break about this rom nonsense and let them work in peace, when their ready to release a Android rom they will release a Android rom.
wphoenix said:
i have just check out the Kovsky project from Gitorious, but still don't know how to work on it. 'cause i don't have much knowledge about develop kernel and open source, why don't we have a tutorial thread about this?
Click to expand...
Click to collapse
would like that too, i've only been reading for some good time about the advances, and would like very much to take part in the development of the kernel, but don't really know where to start from
Also, what Viper says its very true... the work is probably a long way from done, depending on how much help the dev's get, which is, from what i've seen, not much.
about Toe_Cutter's comment "I wonder if some dialog on the issues surrounding an Android port/ROM might result in greater community involvement, and ultimately a stellar Android ROM for one of HTC's most beautiful smartphones" ... well, yeah, i think it could... at least i hope so.
xD
cool down all your heads and lets just help in every way we can
...as (ilgreco112) does xD... cheering up isn always bad hahaha
ps: first post!! ... Hi!
Viper89 said:
You people asking when a Android rom is coming just about every day are so funny. First of all their are still major issues that need to be worked out. Android running from haret is not even every day usable yet so what is the freakin point of expecting a rom now or asking about it? Do you guys want a rom where you phone won't even last 2-3 hours, GPS dosen't work along with the camera etc......? We need All the issues fixed before we can even be thinking about a rom. When Android from Haret is everyday usable then lets start talking about a rom. So can we please give the Devs a break about this rom nonsense and let them work in peace, when their ready to release a Android rom they will release a Android rom.
Click to expand...
Click to collapse
As a dev, I bet it IS tiring hearing all the spectators asking about an Android ROM.
But what do you expect when spectators ask about the issues, and receive nothing in response?
In my original post, I chose my words very, very carefully, because if you go back and read it again, I never asked when, I only asked the why and how.
Why is it that no one can provide a response to this question? I searched the forum, and read thru dozens of posts trying to understand what this port might require, and I got nada (except several polls asking about an Android ROM, and a few more posts telling the spectators to quit asking about an Android ROM).
Anyone care to break the cycle and help the community understand the issues?
Well, the problem is that you can never guess what's required and how to achieve it. First of all, developers really know nothing about the hardware before they begin hacking it. Until you finish the job, you can't estimate the time it takes to complete. The major problem is that most of us devote just a tiny bit of our time to the porting, because there are lots of interesting things to learn and to do except it, but mostly because everyone's either studying or working (or even both).
But if you really want to know what's needed.. well
1. Fix the LCD panel (add the initialisation code)
2. Fix the power saving (that's the greatest PITA right now) and 3D (the latter should be easy and is not really critical)
3. Implement Bluetooth, FM Radio, Camera (Should not be really hard on the driver side, but rather on the RPC protocol side)
4. Fix USB (should be easy.. actually, everything's done on the device driver side, the problem seems to be with the msm usb driver itself.. just needs real debugging)
5.Make a version of rom that boots from NAND (well, once you get the LCD to work correctly it's not a problem. It actually boots very well off nand, but without LCD and USB working it's not much fun, to tell the truth)
6.Clean up the code, drop the ****ty-droid and head forwards to SHR/Maemo MER/Meego or some other real linux distro with X11 and other things
7.Write up misc stuff (like optical joystick, illumination, new keypad driver and others)
But really, it you want to help, just begin researching everything yourself and exploring wince drivers. You know, Theo de Raadt once said: "shut up and hack", and that's the only way to get things done.
full ack
@sp3dev
full ack your post. the main problems ar not at android 2.x this source we have. but the kernel an its's modules (for kovsky) are the problem.
regards
Toe_Cutter said:
As a dev, I bet it IS tiring hearing all the spectators asking about an Android ROM.
But what do you expect when spectators ask about the issues, and receive nothing in response?
In my original post, I chose my words very, very carefully, because if you go back and read it again, I never asked when, I only asked the why and how.
Why is it that no one can provide a response to this question? I searched the forum, and read thru dozens of posts trying to understand what this port might require, and I got nada (except several polls asking about an Android ROM, and a few more posts telling the spectators to quit asking about an Android ROM).
Anyone care to break the cycle and help the community understand the issues?
Click to expand...
Click to collapse
The ROM question has been answered time and again throughout various threads on xda-dev.
There is no real issue "porting" Android to kovsky. Android is a virtualized environment running on a linux
kernel and it is that kernel that has to be ported. "Android" runs 100% on kovsky with minimal modification.
So. There is only one issue with the linux kernel - that issue is when the linux kernel for kovsky
is good enough for someone to make the effort to pack up a ROM with that kernel,
a bootloader and the android system.
Now, the consensus is the kernel isn't as yet good enough for daily use -
if someone with the skills decides it is and makes a ROM, then they will
obviously do so.
The list of kernel stuff to be fixed is broadcast all over this board and asking kernel devs
to repeat themselves ad nauseum won't get it done any faster
Dear all,
Why don't we create some tutorial and advices for new developers who love X1 and Android but don't have much knowledge about Linux kernel, Gitorious...
I have cloned the Kernel repository but still don't know where to start with
I think many of us want to help too
Thanks for reading
Nice Step, i will be with you in this project and wish more devs will come with us.
Thanks
There are instructions on how to compile the kernel on the wiki:
http://wiki.xda-developers.com/inde...ngx20.thex20.Kernelx20.fromx20.thex20.Sources
I added instructions to get wifi working a week or so ago.
I too want to cook an Android dist from scratch, we will need to go back and figure out what has been done (i.e required modifications to fix the screen flip)
It will be very useful to have this info on the wiki as one may need to do it all again for future Android releases (i.e 2.2, 2.3)
edit: There is some technical info at http://www.htc-android.com/viewforum.php?f=5
I hope you can make goot work on it (fingercrossing)
I only have windows programming knowledge some C++ knowledge. So, is there anyone can tell me about the environment for develop a kernel, which knowledge do i need to focus on ^^ I still don't familiar with all those thing yet, I just want to help and i know i have to improve my knowledge for that
I like the idea of having a HOWTO, so that everyone can join in development. But i am not sure, that it is even possible. It is too big.
Downloading/cloning sourcecode, setting up build environment and cross-compiler and building a linux kernel is actually the easy part. A good guideline was postet by Tremere, and google is always your friend
Now the REAL WORK begins. Linux kernel source code is not very well documented. And the kovsky hardware specs are not documented at all. Well, some chips have been identified and datasheets where found, but many things are simple and painfull trial-and-error and may never work at all.
Then is the problem of finding the right source files in the source-tree. It helps looking into git-log and analyse changes made.
Then is the problem of data-structures and functions defined and used all over the source. There is no guide or something that explains what structure is used when and where. If you are lucky, you find some irc-chat-logs
Then is the problem that you can not debug, only add messages and stuff.
Then is the problem on how to approach, lets say GPS or Camera. You have to know about GPIOs, bus-systems, driver-models, ...
Then is the problem that one day has only 24 hours
Anyway, i would like to see, that you prove me wrong!
it's not about proving you're wrong, it's all about proving you CAN !!!! you've bring it far from the start, I dont think that the battery or camera can scare you!!!!
Vdelf I know you have worked alot on this, I put all my trust in you!!! I cant help you becaus I dont know how!!!
so I support you more than anybody because I really really want all this Xperoid to be fixed!!
vdelf said:
I like the idea of having a HOWTO, so that everyone can join in development. But i am not sure, that it is even possible. It is too big.
Downloading/cloning sourcecode, setting up build environment and cross-compiler and building a linux kernel is actually the easy part. A good guideline was postet by Tremere, and google is always your friend
Now the REAL WORK begins. Linux kernel source code is not very well documented. And the kovsky hardware specs are not documented at all. Well, some chips have been identified and datasheets where found, but many things are simple and painfull trial-and-error and may never work at all.
Then is the problem of finding the right source files in the source-tree. It helps looking into git-log and analyse changes made.
Then is the problem of data-structures and functions defined and used all over the source. There is no guide or something that explains what structure is used when and where. If you are lucky, you find some irc-chat-logs
Then is the problem that you can not debug, only add messages and stuff.
Then is the problem on how to approach, lets say GPS or Camera. You have to know about GPIOs, bus-systems, driver-models, ...
Then is the problem that one day has only 24 hours
Anyway, i would like to see, that you prove me wrong!
Click to expand...
Click to collapse
Thanks for your advices
if building the kernel is the easy part i'm a long looong way from being useful xD
probably my x86_64 bit fedora doesn't like me very much, got stuck with glibc dependencies errors or some wrong step at the arm installation... ¿could an x86 virtualized ubuntu save my day? as ive read some of the first testing was done in a debian distro, so ill try my luck with it.
damn... learning is fun... i just hope my Xperia doesn't learn how to burn while i'm playing with it xD
monovaldes said:
if building the kernel is the easy part i'm a long looong way from being useful xD
probably my x86_64 bit fedora doesn't like me very much, got stuck with glibc dependencies errors or some wrong step at the arm installation... ¿could an x86 virtualized ubuntu save my day? as ive read some of the first testing was done in a debian distro, so ill try my luck with it.
damn... learning is fun... i just hope my Xperia doesn't learn how to burn while i'm playing with it xD
Click to expand...
Click to collapse
A while ago, someone (can't remember exactly) posted a link to a linux vmware image for kovsky development -
you could start with that, although any linux system should be no problem, since there are no distro -specific
"packages" to use in this kernel development ( possibly except git )
Hell, I don't even use a VM - I have a slackware 12 install running on coLinux
under windows 7 and it works a treat!
angusmcb said:
A while ago, someone (can't remember exactly) posted a link to a linux vmware image for kovsky development -
you could start with that, although any linux system should be no problem, since there are no distro -specific
"packages" to use in this kernel development ( possibly except git )
Hell, I don't even use a VM - I have a slackware 12 install running on coLinux
under windows 7 and it works a treat!
Click to expand...
Click to collapse
well, that is a very nice alternative for users which don't like linux messing with their drives (not myself though xD)... thanks anyway
couldn't really tell which was the actual problem for me, i just got it working fine after installing an i686 distro on top of the x86_64 one
and... now comes the easy part, right? haha
will get onto studying
I've been installing Gentoo on my X1
http://wiki.xda-developers.com/index.php?pagename=Gentoo_on_HTC
The good thing about Gentoo is although the compilation takes forever (especially under an emulated ARM chroot!), it allows us to build a system from first principles and also build packages to our needs.
A lot of this has been googling for what people have done on the Xperia and other HTC devices, particularly with the Ubuntu ports.
Hopefully all the knowledge I've gained will make it real easy to get MeeGo running.
I know you guys have talked about this already, but has anyone tried to load it? Maybe a derivitive of the HD2 rom for WP7? I bet anything that it would work, it would just be a little slower.....please give some feedback for this thread
i agree the tp2 deserves a try they said we couldn't overclock now look @ us
P.S also make a CDMA version for us sprint people
I'm sure someone could get it running. Nothing is impossible.
doublen1 said:
I'm sure someone could get it running. Nothing is impossible.
Click to expand...
Click to collapse
+1 to that.
The problem is the processor architecture...
WP7 on TP2
I bet that it wouldn't matter, they say the requirements are what they are, but they can operate on lower specs, just won't operate at optimum efficiency. If the HD2 and WP7 Phones are at 1ghz, its not bad that we are at 748mhz+. I bet it will work!!! I know technical aspects, but it sucks I don't know how to actually do any of it!!!! Maybe someone should come up with a bounty
RedWolf023 said:
I bet that it wouldn't matter, they say the requirements are what they are, but they can operate on lower specs, just won't operate at optimum efficiency. If the HD2 and WP7 Phones are at 1ghz, its not bad that we are at 748mhz+. I bet it will work!!! I know technical aspects, but it sucks I don't know how to actually do any of it!!!! Maybe someone should come up with a bounty
Click to expand...
Click to collapse
Whatever, TP2 runs a Qualcomm processor ARMv6, while Snapdragon is ARMv7.
WP7 requires ARMv7.
It's not as easy as you think, guys.
can we get it
maybe lescro could chime in
No, we can NOT get WP7 ever. It's just not possible. As Jackos said, WP7 is built on ARMv7. The TP2 has an ARMv6 chipset. The ARMv6 CPU just can't execute the code in WP7. It has nothing to due with the speed of the CPU. Just like how certain Adobe software doesn't work on old AMD/Intel CPU's because they're missing the SSE2 instruction set.
EDIT: This has been stated by Da_G many times & trust me, he knows what he's talking about. Follow Da_G on Twitter.
Mod, please close this thread.
It is possible but very difficult to do. Some has to make it ARMv6 able.
WP7 on TP2
Like others said, it was impossible to OC our TP2's, and now look!!! You're right, the WP7 on an ARMv6 core would be difficult to do, but someone can do it! It's kind depressing that everyone keeps saying "never" will we have it on the TP2. If you can create a theme from throttlelauncher that does just about everything that the WP7 itself can do, I would wager that you could modify the WP7 rom to execute off of the ARMv6 core....problem is nobody wants to spend the time to do so for free, so we should come up with a bounty.
Actually when these devs tell you that the code can not run they aren't explaining (rightfully because it might fall on deaf ears) that windows ce is closed source so changing anything would require a large amount of work if the kernel can be changed at all. Its not like the linux kernel where we can go in and change things in the source code then compile. WP7 is what it is its like saying that windows 7 can run on an arm processor yeah it probably could but you would have to change the kernel which i believe only microsoft has the ability to do. Just tough it out like the rest of us until your upgrade date. Please no more WP7 on TP2 threads
is this really a question? FIRST of all, it is impossible. Second of all, there are various themes that would be more stable than any wm7 port if there was ever a dev who had some magical touch. yeah, we can overclock. but who here can safely oc to 1g? closest i get is 768. and that gets touchy.
believe me, theres no way/reason to do this. just buy a new phone
WP7 on TP2
My only problem, which is quite a personal problem, is that I am not allowed to have a camera on my phone where I work.....so this blows because they will not make any more cameraless phones. So anything to make my TP2 any better, I'm all game. Besides, I absolutely HATE on screen keyboards, no matter how accurate they are. Again, just a personal problem.
You're job will end up changing that rule. They have too, because cameraless cell are sadly a thing of the past. I don't know a single person who doesn't have a camera on their cell. As for the hardware KB, check out the HTC 7 Pro. It's a 1Ghz Snapdragon WP7 version of the TP2.
Somethings are impossible.... Overclocking is one thing but executing code compiled for a different CPU is NOT the same thing!
As others have pointed out, it's ARM v6 vs V7 and it's not a code issue - its a microcode issue - the v6 does not have the same instruction set so the code cannot execute.
Short of M$ recompiling the code (not very likely), releasing the source (even less likely) or writing a V6 interpreting shell (can you say SLOW) it ain't going to happen.
Deal with it and wait till your contract is over and get a new phone when you can
drkfngthdragnlrd said:
You're job will end up changing that rule. They have too, because cameraless cell are sadly a thing of the past. I don't know a single person who doesn't have a camera on their cell. As for the hardware KB, check out the HTC 7 Pro. It's a 1Ghz Snapdragon WP7 version of the TP2.
Click to expand...
Click to collapse
No, I am 100% Certain my work will not change that rule. They will prohibit cell phones altogether before allowing a camera. But I will check out the HTC 7 pro
if you go to wp7 forum theres alot of problems with that phone
...like any phone
but there are alot of themes for our phone
like lesscrco wp7
BTW. Why would anyone need WP7 on TP2? Imho it's good enough with WM6.5.
WP7 would only decrease the functionality and cause problems like battery life or performance.
Emulator
Emulation is possible, ask the people who wrote BOCHS or Pear PC.
However, it's absolutely not practical to go down this route. It would require an amazing amount of work for what would be a very slow WP7 device with no battery life.
The time and money spent on a project like this would be better put to improving WM6 or Android.
1milenia said:
if you go to wp7 forum theres alot of problems with that phone
...like any phone
but there are alot of themes for our phone
like lesscrco wp7
Click to expand...
Click to collapse
I bought my wife the Samsung Focus and we have absolutely no problems with it. WP7 is perfect just left stock. WP7 is probably the best PPC OS out there now.