Related
Hi there,
I noticed that its a bit tricky to configure the PPC. Somehow I think the System-Programmer (MS) thinks its nice to hide settings from user.
I like complex property tabs. MS-InternetExplorer hides everything. PocketOutlook is nearly not configureable.... Or I'm blind....
Has anyone a Linux installed on his O2-XDA? What would you say about it?
regards
McNugget
Yes PLEASE, gimme Linux on my Qtec1010
I'm serious, I would really appreciate if somebody was able to have my Qtec synchronise with Linux.
And secondly wouldn't it be easier if this whole PPC was open source, so that bugs would be solved quickly?
Has anyone tried to put Qtopia (from the Zaurus) on the Qtec? It seems that it supports the ARM-processor.
Regards & the obvious best seasons wishes to you & your beloved ...
Rik
Quote of the day:
"Linux is like a Wigwam: no windows, no gates ... apache inside."
last i heard then they opensource linux for xda were at such an early state
that there were no phone support or even gui just a console
but there are more then one of these products
maybe some of them have gotten longer
There is a lot of progress going on the Linux front. The biggest challenge is understanding the RIL ( radio Interface layer) on the HTC based devices(Most XDAs and MDAs) and writting a kernel to it.
There will be many new contenders this years as NTT DOCOMO has declared it wants Linux based phones in the Japanese market. So they will come out pretty soon.
Look at the following links:
http://gpe.handhelds.org/projects/?PHPSESSID=08727f78426b030303d6b74a11fde7a2
I have seen and made a call on a device using this OS, but could not get the code!
http://www.mizi.com/en/prod/embed/embedded_smart.htm
and for the more adventurous:
http://www.mizi.com/en/developer/s3c2410x/index_html
very informative links and nice readings
thank you very much ...
what you think might be the threat coming from Open Source solutions to the mobile market (especially phones) - do you have some reports/papers/studies on that ??
I mean, Japan and Asia has always been a niche market where many product and electronics gadgets existed but at the same time they had problems with adaptation elsewhere
regards,
monika
I have been on a client for the past month working on a special project and they did not allow me to browse outside the network( squnk works!)
I have seen and played with the linux devices from HTC and other companies, but was told they have a contractual obligation not to release the code or info on the RIL so as not to dillute the PPC and WM markets( I wonder by whom :roll:...)
Still I am trying to get one of the devices, Reverse Engineer the code and post it here... But it will be tricky, but worth it!
Does somebody know a complete image based on GNU Linux kernel and for example Qtopia for an HTC device?
Keying in a telephone number in command mode would be so l33t. :lol:
I have been messing with android on my blackstone for a while now and would love to run it on my athena, I have a copy of 1.0 android that boots that was posted ages ago on here, and have tried to no avail to boot a later version either 1.5 or 2.0.1.
I feel that its pretty close but need someone with some linux/android experience as I think the problem lies in the initrd file.
With this is mind if there is enough interested I would like to see how many people would be willing to donate to a developer/developers to get this running on the athena?
I have seen bounty threads before and they seem to work, so post if you interested in donating to the cause.
What about perfectng the wm6.5 ROM along side the Android for takers?
Thanks mate.
in all honesty i have a x7500 im actually going to sell my iphone and get a x7510 just to have them both .. if im gonna get rid of an iphone i dont think i'd be going to an android
i too am very excited about this as have android 2.1 working on Blackstone so you would like to see it om here. i am not a dev in that sense but i am happy to contribute in any way.........cash not a problem
By the looks of it not many people want android for athena? for anyone who does bear with me as I am spending a huge amount of time behind the scenes working on trying to port 2.0.1 with some help from some experts
Would find Android an interesting idea
Hello avergerpenguin,
Would be very interested in seeing this happen, I have been keeping an eye on your work for WM 6.5 but not yet had time to try flashing one of the roms but if your work on there is anything to go by then I'm sure this will be good. Is this going to be full rom for the phone or run as an app over the top of win mobile?
Oberth said:
Hello avergerpenguin,
Would be very interested in seeing this happen, I have been keeping an eye on your work for WM 6.5 but not yet had time to try flashing one of the roms but if your work on there is anything to go by then I'm sure this will be good. Is this going to be full rom for the phone or run as an app over the top of win mobile?
Click to expand...
Click to collapse
At present it is not possible to run android without winmo, however mitchy has created a rom for diamond that only loads the drivers etc needed and then autoloads android meaning that you cant get to the winmo underneath.
But firstly I need to compile a working android kernel, see what does and doesnt work and then go from there and possibly create a android only rom, but depends on functionality
I am in avengerpenguin
Id love it on the x7510
Android on Athena
I would love to have Android on my Athena, or even Maemo5
Hey Avengerpenguin, I am VERY VERY interested in Andriod on my Athena. I would love it. I am happy to make a donation to help this along if there is a real chance of us getting it going. I wish I knew how to develop so I could help out that way, too.
New Advantage user also interested in Android. I flipped my mytouch to pick up a G1 to use Android and an Advantage for everything else!
Looks like we're preparing to declare against the new dell mini 5 tablet. Its neat to see how ahead of their time these athenas really were.
Also interested in Android on Athena
Now that it looks like WinMo is a dying OS (no new versions after 6.5), I'm also interested in Android.
The new Windows Phone 7 isn't going to be based on WinMo, so I have nothing to gain by staying with Micro$oft software.
Would love to avoid buying a new phone for as long as possible. The Athena has everything I need in it; all I'd have to do is obtain new programs, which I'll have to do anyway.
I am late to the party, but ya, android would be awesome to have. I still have my athena kicking around, and would love to really use it again.
Very interest in Android
Please do this. Thanks for all your work
I'm 100% looking forward to using my Athena again if Android 2.1 can be made to work. It's a sensible OS moving forward given that wm6.5 is towards the end of its life cycle.
Cheers.
eaglesteve said:
I'm 100% looking forward to using my Athena again if Android 2.1 can be made to work. It's a sensible OS moving forward given that wm6.5 is towards the end of its life cycle.
Cheers.
Click to expand...
Click to collapse
EAGLESTEVE!
thought you had dropped off the planet, nice to see you still around
Regards
Jay
Hi Jay,
I went off and bought a Touch HD. Sold it and got a 3G, followed by a 3gs. Hence the absence. But I still have my Athena with an almost dead battary though. Each time I turn it on I'm always attracted by it's hugh and beautiful screen. Somehow I find myself unenthusiatic about using winmo applications again after using iPhone, sorry to say. That's why I hope to see Android on it. It would really Be an awesome device once again I reckon if that's done.
BTW, which is the newest and most popular ROM you guys are using these days? Might try it out for fun before Android is available for my Athena.
Cheers and good to be home.
eaglesteve said:
Hi Jay,
I went off and bought a Touch HD. Sold it and got a 3G, followed by a 3gs. Hence the absence. But I still have my Athena with an almost dead battary though. Each time I turn it on I'm always attracted by it's hugh and beautiful screen. Somehow I find myself unenthusiatic about using winmo applications again after using iPhone, sorry to say. That's why I hope to see Android on it. It would really Be an awesome device once again I reckon if that's done.
BTW, which is the newest and most popular ROM you guys are using these days? Might try it out for fun before Android is available for my Athena.
Cheers and good to be home.
Click to expand...
Click to collapse
Me personally, I have been using Lennie's 6.5 rom. I have not liked 6.5 at all before Lennie had his latest V3.00 out, and now I quite like it. I would still say that 6.1 has the edge for ease of use and speed, but Lennie's latest offering is much improved on speed and looks. We dont have many cooks left on here now, so people seem to be trying out some of the old stuff again. We seem to be getting posts from roms way-way back now. I have a G1 myself now, and very good they are to. I do like to keep up with the WM stuff still.
Guys (and girls ... if any are reading .. )
After some tinkering about (for days now) with Mango build 7720 (Thanks again YUKI + XBOXMOD!) I can confirm that the many of the issues present in Mango Beta are now gone ... Ok granted the MicroSD gets encrypted but its not meant to be removed on an original WP7! You can refer to Yuki's thread on how to unlock your MicroSD card if you don't fancy the likes Microsofts OS and want to revert back to Android .....
Now, it's a known fact that multitouch is an issue together with sound and camera. I was unable to find solutions to this issue. This thread seeks to ask / reply and hopefully implement some of the issues which remain for us to make the HD2 and hopefully run Android and WP7 natively without the abstraction layer present in the secondary bootloaders.
Question 1 - I am aware that CLK runs android only. Are the sound / camera / and multitouch issues present in WP7 also present in Android NAND roms running on CLK ?
Question 2 - How possible is it to modify CLK to run WP7 if the answer to above is NO?
Question 3 - If the issue iies in the secondary bootloader drivers (if any) ... Is there a way to modify/contribute for further development on them?
If we resolve these the HD2 would truly be a remarkable piece of hardware running virtually any OS. Presently the multitouch issue kills some of the enjoyment on WP7 ... and the source sound input gain is too high.
I really wish if we could get some serious thread going and if anyone is confident that he/she can help resolving the driver issue, feel free to pm me. I am a software developer (c#) if this can help in any way. Have been using it some years now on a daily basis. I am willing to provide my help. I hope that anyone could help along maybe we create yet another open source bootloader which does the trick.
Hoping to hear from you so we get something going ...
Regards
Al
I would really like to hear from some devs I am more than sure that the community would be very grateful.
Secondly (courtesy of warriorvibhu)
I suggest that you all Sign this Petition.. Kindly inform all fellow HD2 owners to sign it ... especially if they were impressed by WP7 on HD2.
Alcatrazx said:
Guys (and girls ... if any are reading .. )
Now, it's a known fact that multitouch is an issue together with sound and camera. I was unable to find solutions to this issue. This thread seeks to ask / reply and hopefully implement some of the issues which remain for us to make the HD2 and hopefully run Android and WP7 natively without the abstraction layer present in the secondary bootloaders.
Question 1 - I am aware that CLK runs android only. Are the sound / camera / and multitouch issues present in WP7 also present in Android NAND roms running on CLK ?
No there are some issues in camera and sound with android but is related to incomplete kernel. They are not related to each other for example no multi touch issues on android. All those issues are related to not perfect drivers hd7 is using another touchscreen panel I guess and maybe different speakers and camera. Anyway those drivers are complexed to write because we dont get source from microsoft on how to write them.
Question 2 - How possible is it to modify CLK to run WP7 if the answer to above is NO?
Theoritically yes but CLK is designed to load an linux kernel. So if we want that we need to write a complete new bootloader.
Question 3 - If the issue iies in the secondary bootloader drivers (if any) ... Is there a way to modify/contribute for further development on them?
Yes but you need to go backt to Windows 6.5 and read out the current drivers and port them to windows phone 7 properly. But you will need a JTAG for it and you must be very skilled.
If we resolve these the HD2 would truly be a remarkable piece of hardware running virtually any OS. Presently the multitouch issue kills some of the enjoyment on WP7 ... and the source sound input gain is too high.
I really wish if we could get some serious thread going and if anyone is confident that he/she can help resolving the driver issue, feel free to pm me. I am a software developer (c#) if this can help in any way.
Hoping to hear from you so we get something going ...
Regards
Al
Question
Click to expand...
Click to collapse
Hope this make some stuff clear.
You talk about a sound issue.
If your talking about the sound being too high, then a cab can be downloadeed to fix this. Doesnt limit the maximum volume, just reduces the minimum and puts bigger steps in placce.
We need an asm developer for try to fix multitouch problem... or the source code of driver...
Multi-touch is a bit better for me (don't know if the games which need two screen pressure work I didn't tried yet) but in Bing Maps and IE9 it's working most of the time.
Just hope that's will come soon, I cant wait it !
However, I also hope the Mango will worked with flash and include more apps in the marketplace.
Fisher_9511 said:
Multi-touch is a bit better for me (don't know if the games which need two screen pressure work I didn't tried yet) but in Bing Maps and IE9 it's working most of the time.
Click to expand...
Click to collapse
Its not working in any of multitouch Games.
Nice thread,curious to See the answers, definitely camera is a big issue for me, hope it get fixed soon.
Sent from my HTC HD2 using XDA App
Dont forget the need to use the "batterytrick"
good thread by the way
Unfortunately the thread won't lead to anywhere. Development on WP7/7.5 is not like development on Android. WP7 is closed source and so is the drivers.
So unless HTC themselves step in or a developer hacks new drivers up(which won't happen). We'll never see a native WP7.
We're using all the stuff that was leaked from the original LEO ROM. Also, CLK with WP7/7.5 boot support would not change this. And no, all these problems are not present in Android. But that's because the developers have more tools and open source code to work with, something we don't have.
Try to think positive man... Have you ever seen the arm listed file? We need to find a timer between the two finger... would not be so so so hard... but only hard...XD
TonyCubed said:
Unfortunately the thread won't lead to anywhere. Development on WP7/7.5 is not like development on Android. WP7 is closed source and so is the drivers.
So unless HTC themselves step in or a developer hacks new drivers up(which won't happen). We'll never see a native WP7.
We're using all the stuff that was leaked from the original LEO ROM. Also, CLK with WP7/7.5 boot support would not change this. And no, all these problems are not present in Android. But that's because the developers have more tools and open source code to work with, something we don't have.
Click to expand...
Click to collapse
Hi and thanks for the feedback. With a negative attitude the thread will lead to nowhere yes. That was what people said a year ago when they said that WP7 will never run on the HD2 but the devs ultimately got there. Thanks for answering the question re the Android drivers though.
You are RIGHT that the drivers in WP7 are closed source drivers ... so is MAGLDR. Rewriting another bootloader (if needed) which does not have all the frills of MAGLDR but which is open source could be a possibility.
I am not interested in getting into the WP7 ROM and modifying the drivers built in ... We have to use a technique similar to what they use when creating emulators by reverse engineering ... The most die hard emulators out there such as some of the Playstation emus out there were all closed source but it did not stop the devs from doing a proper emulation of the console.
I'd really appreciate if you could be more specific when you said that we are using the stuff which was leaked from the original "LEO" ROM ... as far as I know, is it not the Schubert which was leaked? Correct me if I'm wrong ... We got too far to give up just now...
Multitouch games do not work .. with the current Multitouch driver .. mainly due to the finger position bug .... This is explained in detail on youtube.
Sound is distorted because the input gain is too high ...
Let's not speak about the camera for now ... I think those are the two major issues which need to be remedied for now. Hopefully this thread will get us somewhere.
Regards
Al
Good initiative ! I hope we can make things work.
Also for those with the negative attitude...if you dont have anything good to say...dont say !
backlashsid said:
Good initiative ! I hope we can make things work.
Also for those with the negative attitude...if you dont have anything good to say...dont say !
Click to expand...
Click to collapse
Nicely said and many thanks
You talk about a sound issue.
If your talking about the sound being too high, then a cab can be downloadeed to fix this. Doesnt limit the maximum volume, just reduces the minimum and puts bigger steps in placce.
Click to expand...
Click to collapse
That is not exactly fixing the issue... It just modifies the maxima and minima ... The sound (input gain) is too high making it sound distorted from the HD2. The fix does remedy this a bit but its ... erm not really fixing the problem.
do think this would be a good idea, but its not being negative pointing out the obvious issue, its being realistic.
you see the point you made on MAGLDR and WP7 running of the HD2 is mute, and im not sure you fully understand its use, there are fundamental differences in making WP7 believe the HD2 is a native device and changing the actual drivers, you see, the SPL for the HD2 was opened up a long time ago with HSPL to be put in place which pretty much allowed us to do anything, the next critical piece was MAGLDR, which sat on top of the HSPL which gave us the potential to install android then WP, both HSPL and MAGLDR are very much programed by folk on here, they were not "hacked" or copied, they are closed source as you put it but they are built for a purpose of doing exactly what they do, enable custom ROMs, for WM, Android and WP to install. But that’s not the issue, the issue is a driver
To be clearer on the matter, IF WP7 had never been tested on the HD2 initially then we would never have had it.
The reasons for the bugs we talk about are because we have test drivers that were never supposed to see the end user. Had we not had that opportunity with the drivers on the HD2 then we would have been up the creek with it.
There are only a number of possibilities to get what we want
•HTC/OEMs go out of their way to finish the HD2 WP7 drivers and give them to use
•HTC/OEMs gives us the Relevant code and tools to do it ourselves
•We find native Windows phone devices that uses EXACTLY the same hardware which we can borrow
•Finally, the wildcard, someone who happens to know how to program for the hardware in question comes to help us.
That is it im afraid, its not being negative, you want to know what we need to do, well, there you go, the chances of HTC etc helping us are almost non-existent, finding devices with the same hardware, well i think we have more of a chance of HTC giving us them, BUT thats more to do with the very old digitiser we have, less so with the other hardware elements, so there is a possibility there.
Finding someone who can actually build a driver from the ground up? its possible, but short of putting adverts out on every developer website asking for help its not likely we will find one from this thread alone.
dazza9075 said:
do think this would be a good idea, but its not being negative pointing out the obvious issue, its being realistic.
you see the point you made on MAGLDR and WP7 running of the HD2 is mute, and im not sure you fully understand its use, there are fundamental differences in making WP7 believe the HD2 is a native device and changing the actual drivers, you see, the SPL for the HD2 was opened up a long time ago with HSPL to be put in place which pretty much allowed us to do anything, the next critical piece was MAGLDR, which sat on top of the HSPL which gave us the potential to install android then WP, both HSPL and MAGLDR are very much programed by folk on here, they were not "hacked" or copied, they are closed source as you put it but they are built for a purpose of doing exactly what they do, enable custom ROMs, for WM, Android and WP to install. But that’s not the issue, the issue is a driver
To be clearer on the matter, IF WP7 had never been tested on the HD2 initially then we would never have had it.
The reasons for the bugs we talk about are because we have test drivers that were never supposed to see the end user. Had we not had that opportunity with the drivers on the HD2 then we would have been up the creek with it.
There are only a number of possibilities to get what we want
•HTC/OEMs go out of their way to finish the HD2 WP7 drivers and give them to use
•HTC/OEMs gives us the Relevant code and tools to do it ourselves
•We find native Windows phone devices that uses EXACTLY the same hardware which we can borrow
•Finally, the wildcard, someone who happens to know how to program for the hardware in question comes to help us.
That is it im afraid, its not being negative, you want to know what we need to do, well, there you go, the chances of HTC etc helping us are almost non-existent, finding devices with the same hardware, well i think we have more of a chance of HTC giving us them, BUT thats more to do with the very old digitiser we have, less so with the other hardware elements, so there is a possibility there.
Finding someone who can actually build a driver from the ground up? its possible, but short of putting adverts out on every developer website asking for help its not likely we will find one from this thread alone.
Click to expand...
Click to collapse
ur right...man sometimes i so feel like bombarding Drew Bamford (product design HTC) emails about windows phone 7 and androi on HD2 and force him to be convinced to make drivers for us....its our right
but then again...can we really ???
backlashsid said:
ur right...man sometimes i so feel like bombarding Drew Bamford (product design HTC) emails about windows phone 7 and androi on HD2 and force him to be convinced to make drivers for us....its our right
but then again...can we really ???
Click to expand...
Click to collapse
I'd say... let's do this! If we get enough people, and those will send emails like everyday, then why not? There's nothing to lose
IF, and its a big IF, we are going to get it working better its going to need ideas like the comment from backlashsid to get unofficial support from these companies
In my humble opinion there is little chance of getting anything else working better without the support of people in the loop, essentially that means HTC and Qualcomm, but remember that by getting the HD2 running WP7 we are costing them money in lost sales, so there is little incentive for them to support us in an official capacity, what we're looking for is an insider!
it doesnt hurt hunting for new devices with the same hardware but its unlikely anyone would use old gear.
This would be nice so then we (as the community of XDA) can show off our HD2's as the beast-mode phone and bestest phone ever!
Hi guys,
I'm new to the forum, but I plan on developing ROMs with a few people, so I will probably frequent them soon.
In my Operating Systems class, I was asked to come up with ideas for a project. Well, since I'm just starting to build Android ROMs anyways, I was going to see if I could use this idea for class. I guess my question is, do you guys think this would be a good project to last a few weeks of the semester (at least)? If not, can you suggest ways that will make it longer or shorter? We would be building them for a Droid Incredible.
I have a general idea, and it seams that just getting an AOSP ROM up and running would be no problem at all, from what I read anyways. It seems like the tailoring or the importing of ROMs is what really takes time and effort.
Thanks in advance for the input.
It depends on the class skills. But it's really great idea to study Linux and low level Android features. uh.. I didn't have such interesting project during my university years ((
The only big issue is high initial level of knowledge. Also many peoples may quickly give up fighting with some unclear compile or deploy issues. It's not trivial to debug on such devices. They may quickly lost their interest. But overall this is great idea. Where are you teaching?
I'm not actually the professor, I'm a student at Saginaw Valley State University (Michigan). I'm the "Class Leader" so I told the professor that I would give him the list of ideas I had for projects.
If it's for a grade, it might be a good idea then. They may lose interest, but if their grades are on the line, I would hope they struggle through it. Plus, we are all in groups, and they can pick another project if they don't like this one.
Thanks for the info, Purler.
Does anyone know how different it would be to make a ROM for something that requires a mouse input, like the Raspberry Pi?
I'm looking into building a custom android device to be embedded in a project I'm working on. I won't need GSM/cell service, so this would be more of a 'tablet' with wifi that's the size of a phone. The first version of this project used some lower level embedded controllers, but for a better user experience (capacitive touch screen, full featured app, etc), I'm looking into using an embedded android device and having a friend (who told me to post here about this) write an app to run on it for me. This project is starting to scale, so buying a cheap tablet and tearing it apart isn't really a good option; I'll need to build something from the ground up. My problem is that I'm more of a microprocessors guy, so I don't really know where to start with this kind of hardware.
I found this thread which was a good start, but the info is like 3 years old now.
Has anyone tried to do something like this? Should I be trying to find a manufacturer who already does this type of thing to work with? If so, how do I find someone like that? If I am going to do the design myself, what kind of processors can run an Android OS? Where's a good place for learning that type of info? Are there any reference designs out there I can use to get started? Is running Android on RaspberryPi a good starting spot, or is that simply not scalable?
Thanks for the help, I hope I'm in the right spot. Apologies if not!