*** PLEASE READ CAREFULLY BEFORE INSTALLING OR FLASHING ANY SOFTWARE POSTED IN THIS THREAD ***
The software posted here is for TESTING purposes only, The Polaris Android Linux development team or any of the posters of software or links to software on this thread, take absolutely no responsibility or liability for damage caused by the result of installing or flashing software or links to software found on this thread - correctly or otherwise, you do so on the sole understanding that you do so at your own risk. A final version will be posted on completion of a version 1 kernel at which point testing and support for the kernel will be moved to a suitable thread. Please do NOT post support questions on this thread - this is a development thread ONLY.
Development work is sometimes done in the irc channel: #htc-linux. To follow the latest developements please read the daily logs which can be found at: http://irclog.iclem.net/?chan=htc-linux&day=13
Lastly, Please do not use bad language in your posts, I have my little girl with me most times and do not need her to read such things. Appreciate your understanding.
Update: We now have a few threads devoted to userspace (system images), This is a KERNEL DEVELOPMENT thread which is starting to get too big for devs to follow. The purpose of a good development thread is to serve as an archive and a blueprint for future developers and that is hard to do when you have hundreds of non-related posts. I have therefore asked the moderator to move all non-kernel posts to their appropriate threads.
-----------------------------------------------------------------------------------------------------------------------------------------------
01-09-08 - new link to files for working wifi
http://www.4shared.com/dir/19593527/3cb53c3a/sharing.html
24-07-09 - If anyone is interested in making themed system images, he's posted this link to help you learn how to do it:
http://forum.xda-developers.com/showthread.php?t=471586
19-07-09 - New kernel with changes from Vogue branch released. I am currently testing radios and resolutions. List of resolutions from kaiser thread
15-07-09 - A revival in our development as meant we are now catching up with the other devices with development on the project. Thank you to all who donated to the purchase of development Polaris that will be used by vilord, from vogue forum to help us with the project.
Current developers:
Life02 - Fixed GPS, Working on Battery issues.
Vilord - On holiday, now in possession of a Polaris. Also working on Bluetooth.
Newbie16 - Fixed Wifi - need to add irq's.
05-07-09 - New 1.5 ION build of Android for the Vogue has been reported to work well for the Polaris and can be found on the Google Vogue repository. The new 1.5 builds are noticeably also faster and smoother than previous builds. Some troubleshooting info can be found at the Androidhtc website for these builds (thanks freddycs). APN details can be found on Wikipedia - (thanks Mormy)
Things that do NOT work at present:
Bluetooth - No - Working partially for Vogue
Wifi - WORKING! *NEW* - thanks to a lot of effort by my friend Newbie16 - thanks mate
Camera - No - Working for Vogue
GPS - now working thanks to life02! - Well done my friend
---------------------------------------------------------------------------------------------------------------------
A new thread for budding designers has been set up by Venigo, (thanks matey!) who will lead the design side of the Polaris Android project (kind of makes you a little emotional thinking we're at that stage where we can start thinking about wallpapers and themes doesnt it?) Thread can be found here: Polaris Linux Android - Wallpapers, Themes and Icons
UPDATES: - Please check the WIKI for up-to-date progress updates here: Android on Polaris WIKI (Thanks excogitation)
NEW TESTING AND BUG THREAD ANNOUCEMENT:
marcelkordek has kindly started a thread for testing and bug reporting as we now have an almost usable Android image which can be found here: Polaris Android Project - Testing and Bug Reporting The thread will also be used to provide updates on the progress of the Android kernel as well as providing feedback to the devs on the latest posted images. Please ensure that the Testing and Bug Reporting thread is used for reporting user experiences and enable to keep the development thread cleaner and make life easier for the devs, whom you will all agree are doing an excellent job to support our beloved device.
18/1/09 - Working Radio with calls at last! Audio and SMS still not working but GPRS does but with a bit of fiddling.
16/1/09 - SMD code is nearly fixed by DZO, Rogro82 will be making a new image soon. Most of the development at this time is being reported in the Kaiser forum: UPDATED!!! - Google Android and Linux for KAISER!! as DZO was sent a Kaiser and he is working on the issues on it.
5/1/09 - DZO is working to bring the Kaiser and Polaris branches together so that the kernel will work on all our devices. Waiting to see what changes are made.
1/1/09 - Rogro82 uploaded a "booting" 1.0 SDK along with source files and instructions (below). Although this is very much a work-in-progress, it is the first bootable version of the 1.0 SDK for the Polaris.
11/12 - DZO and rolk worked out some changes that may help us resolve the SD Card stability issue. Dwaradzyne posted up a Zimage with the changes for testing.
CPLD Handbook
GPIO Manuals
LATEST FILES USED FOR DEVELOPMENT:
1/1/09 - Latest files are packed in this archive - to boot simply unpack to the root of your sd card and run haret (included).
A big THANK YOU to Rogro82 for getting the 1.0 SDK booting on the Polaris
Enjoy!
-----------------------------------------------------------------------------------------------------------------------------------------------
FIRST POST
I'll start with another simple question I cant find an answer to:
WHY CANT WE JUST PORT THE G1 ROM TO THE POLARIS?
#2 reserved for update
I will try to search too
I will try to put as simple as possible. Building a ROM requires combinig two parts:
1. Kernel/drivers part.
2. Applications and stuff.
In case of Windows Mobile part 1. in practice always comes from official HTC Polaris ROM. Part 2 comes from other official HTC ROM (could be other phone) and it can be modified by cooker.
We do not have a full working Polaris Android ROM, and we cannot just cook without part 1. Part 2 is available as Android sources are open.
The reason why we did not have 3d driver working on Polaris immediately after first Diamond ROM was available is that part 1. is not transferrable from one model to another.
Part 1. in Android is Linux kernel. We must get involved in Linux kernel developement for Polaris to bring Android to our phones.
why do we always want our phones to look like other phones. why cant we just be unique. we are windows mobile. TOP DOGG. i like windows mobile theme especially when its black. i like g1 but the design looks ancient. its not 2008 more like 1998
dortyboy said:
why do we always want our phones to look like other phones. why cant we just be unique. we are windows mobile. TOP DOGG. i like windows mobile theme especially when its black. i like g1 but the design looks ancient. its not 2008 more like 1998
Click to expand...
Click to collapse
absolutely agree. Copying iPhone was fun the first 2,3 months. Why not trying to develop really good apps with nice UIs and make own ideas into real interfaces for throttle launcher, M2D etc etc - posibilities are nearly endless.
i absolutely agree. i havent seen not one cool program thats actually usefull in our daily life for windows mobile not since i had a treo way back.
programs like directory; that could look at your number and tell u the owners name and adress
stuff like that. maybe tell u when zip code the call is coming from. useful programs. not the crappy programs that just try to make your phone look pretty.
thats why people go to iphone, the programs are useful in peoples daily life but not windows mobile
Here we go
ROM download :
Code:
http://rapidshare.com/files/155612986/Android_dump.rar
I think its a probleme with the boot loader and some part of the android code which isn't public
Have look here :
Code:
http://www.limofoundation.org/en/limo-press-releases/limo-foundation-statement-on-the-google-android-g1-handset.html
dortyboy said:
why do we always want our phones to look like other phones. why cant we just be unique. we are windows mobile. TOP DOGG. i like windows mobile theme especially when its black. i like g1 but the design looks ancient. its not 2008 more like 1998
Click to expand...
Click to collapse
Are you new to the mobile device world?
We are not trying to get it to "look like the G1". We are talking about using a completely different operating system.. lol.. and you are talking about a black windows mobile theme and how the hardware of the G1 looks ancient.. lol..
Oh.. and "being unique" in this case would be having Android on a non G1 phone.. that would be unique. Windows mobile is not unique.
m.schmidler said:
absolutely agree. Copying iPhone was fun the first 2,3 months. Why not trying to develop really good apps with nice UIs and make own ideas into real interfaces for throttle launcher, M2D etc etc - posibilities are nearly endless.
Click to expand...
Click to collapse
Developing apps and trying to use resource hog throttle launcher is nothing close to having a brand new stable device operating system.
m.schmidler said:
absolutely agree. Copying iPhone was fun the first 2,3 months. Why not trying to develop really good apps with nice UIs and make own ideas into real interfaces for throttle launcher, M2D etc etc - posibilities are nearly endless.
Click to expand...
Click to collapse
Maybe we can develop better apps under Android?
Look at the apps currently available for iphone - hopefully Android will get better market penetration than Windows Mobile, and, because it's open source it opens up a whole range of possibilities for developers.
I say if it can be done, it should be done!
dwaradzyn said:
I will try to put as simple as possible. Building a ROM requires combinig two parts:
1. Kernel/drivers part.
2. Applications and stuff.
In case of Windows Mobile part 1. in practice always comes from official HTC Polaris ROM. Part 2 comes from other official HTC ROM (could be other phone) and it can be modified by cooker.
We do not have a full working Polaris Android ROM, and we cannot just cook without part 1. Part 2 is available as Android sources are open.
The reason why we did not have 3d driver working on Polaris immediately after first Diamond ROM was available is that part 1. is not transferrable from one model to another.
Part 1. in Android is Linux kernel. We must get involved in Linux kernel developement for Polaris to bring Android to our phones.
Click to expand...
Click to collapse
Thanks for the idiots guide dwardzyne!
So that very clearly explains the kernel level requirement.
OK. Second question:
With regard to part 1 - Kernel/Drivers - Can we convert the vogue version since it seems to have the most work done to it? What would need to be done to it to make it work?
imfloflo said:
I think its a probleme with the boot loader and some part of the android code which isn't public
Click to expand...
Click to collapse
a boot loader :
Code:
http://www.denx.de/wiki/U-Boot/WebHome
bally3 said:
Thanks for the idiots guide dwardzyne!
So that very clearly explains the kernel level requirement.
OK. Second question:
With regard to part 1 - Kernel/Drivers - Can we convert the vogue version since it seems to have the most work done to it? What would need to be done to it to make it work?
Click to expand...
Click to collapse
Indeed kernel developement for Kaiser and Polaris is based on Vogue work. It slowed down because of SD stability issue.
dwaradzyn said:
Indeed kernel development for Kaiser and Polaris is based on Vogue work. It slowed down because of SD stability issue.
Click to expand...
Click to collapse
I believe the sd card issue has been resolved on vogue and they've moved onto other things (camera etc). but it seems like its the end of the road for the Polaris - apart from rumors that someones supposed to be sending a kaiser or a polaris to dzo for him to work from. This kind of points to that dzo is the only person on xdevs capable of working at kernel level with a kaiser or polaris?? That cant possibly be true - can it?
bally3 said:
I believe the sd card issue has been resolved on vogue and they've moved onto other things (camera etc). but it seems like its the end of the road for the Polaris - apart from rumors that someones supposed to be sending a kaiser or a polaris to dzo for him to work from. This kind of points to that dzo is the only person on xdevs capable of working at kernel level with a kaiser or polaris?? That cant possibly be true - can it?
Click to expand...
Click to collapse
He already has the knowledge... He wants to share his knowledge, if someone send him a Kaiser or Polaris, and will make it work... I thought there were plenty of users willing to send there old or half bricked kaiser or polaris... but still nobody send him one... as far as I know...
Nobody keeps nobody up to date in the kaiser thread... So I really don't know what is going on... But they still don't have a decent fix for the DMA (SD-Card read/write) problem (as far as I know).
Porting the G1 rom isn't a possibility, you first have to have drivers for our device, since we haven't got a driver to read/write to the internal memory (not the RAM), it still cannot boot .
I hope this project will really come of the ground finally... It's half way there... but still not finished (if you ask me, due to miscommunication and not working together of users, because they all want to be the first who got it working to show off with it... (so they are all working on the same piece of code, which is a waste of time if you ask me)).
Maybe one of us can contact DZO, check what he needs to continue our development. Because without the SD-Card driver we can't continue...
dubbeld00 said:
Maybe one of us can contact DZO, check what he needs to continue our development. Because without the SD-Card driver we can't continue...
Click to expand...
Click to collapse
I'll contact him, I dont think there are many users who would just send a device worth a couple of hundred euros to a complete stranger though many would tell you they would at the time. With the P3D driver their was only one person who was willing to loan a unit for development - and that was only because they were in the same country. I was asking for ages before that.
is their any other way we could help him? surely the internal workings of a polaris rom coupled with the specs could be used if dzo would do what NuShrike did on the p3d driver which was tell us to try things he worked on? I'm sure there would be willing volunteers including myself who he could talk through it on the forums or on the #android room.
I can't offer to donate my polaris as its the only mobile I have.. but I would be more than willing to try things out on my xda or provide any other help possible to get this project moving.
Hopefully one day a fully working Android will be a reality on polaris
First question : Is there any accelerometer bublle level like the incredible android one for Jave J2M Samsung S5600 (Player Star) phone ? Or anyway, is there any solution to port this app from adroid to java Mobile ? I got the source jar if anyone is interested to have a look inside. It does not lauch on my mobile, certainly due to protection and very different Android OS...
Second question :
I would like to find a way for overriding the Exe/jave/games/folder to point it to my mmc sdcard ? Is there a way to do it via nv_default.ini without bricking the phone ? A better solution would be to offer both databse update search and and thos two path in ?!
I'm really not familliar with this phone OS, so if there anyone who can tell me if this system is modifiable or modable, just let me know...
Free Bonus Question : I also have a nice HTC touch P3450, wich has been succesfully updated to the latest avaible firmware. I dont know if this phone have an accelerometer ? Can anyone tell it to me ? I don't think so because none of the apps are hanging this feature, but i'm asking it also
Hello, (first post!)
Got an HTC HD7 a few days ago in India and loving it overall.
Noticed that some text (in either emails, webpages, facebook etc) which use "indic" or "devanagri" or "hindi" (India) font show up as square blocks suggesting missing fonts.
Is there a way to add/install fonts now or do we need to wait for updates from MS?
Also, is there a kind of official location for user feedback for such things? social.microsoft.com forums will do?
Thanks,
Vishal
fonts: no.
social.microsoft.com: yes.
The Gate Keeper said:
fonts: no.
social.microsoft.com: yes.
Click to expand...
Click to collapse
Wow another incredible omission. Amazing how far backwards things have gone compared to Windows Mobile.
CSMR said:
Wow another incredible omission. Amazing how far backwards things have gone compared to Windows Mobile.
Click to expand...
Click to collapse
you're very quick to jump to conclusions... why would the end user need to install fonts? if it doesn't work in India yet it is because MS are still working on the language support. As they said already, asian countries (which include india if you know your geography) will get it mid to late 2011.
vishalrao said:
Is there a way to add/install fonts now or do we need to wait for updates from MS?
Click to expand...
Click to collapse
Developers can add any TrueType font (with Hindi or any other subsets) to their application (exactly as I did in UltiTran - will be available on market soon).
The simplest way to do this - it's an ExpressionBlend's FontManager.
The Gate Keeper said:
you're very quick to jump to conclusions... why would the end user need to install fonts? if it doesn't work in India yet it is because MS are still working on the language support. As they said already, asian countries (which include india if you know your geography) will get it mid to late 2011.
Click to expand...
Click to collapse
A constant refrain. Why would a user need x, where x is a standard feature of computing that has been in common use for decades.
If you know what a font is, you know why a user may want to install fonts. So that text in documents he views and composes can appear with those fonts.
The same goes for everything else. If you know what a file is, you know why a user may want to access files. If you know what multitasking is, you know why a user may want to have two tasks running simultaneously. And so on.
Sorry to go off on a tangent but this attitude is really dumbing down computing and may prevent the windows phone OS from ever being adequate.
of course i know what a font is. giving the end user ability to reach this sort of system wide tool though, they may as well just left us with windows mobile 6.5 rather than start from scratch.
in saying this, as i said before, MS are working on it for a uniform experience. otherwise you'll end up with some phones with some things and others without, which is what happened with windows mobile.
i'm not saying that we should dumb down the smart phones, but much of the general consumers don't really want to have to go to these lengths. that's not to say there aren't any, but if we were all like that, iPhone would definitely not have taken off.
Well, its mid past 2012, and do we have indic fonts on WP? Well, I guess they are not really bothered.
CSMR said:
A constant refrain. Why would a user need x, where x is a standard feature of computing that has been in common use for decades.
If you know what a font is, you know why a user may want to install fonts. So that text in documents he views and composes can appear with those fonts.
The same goes for everything else. If you know what a file is, you know why a user may want to access files. If you know what multitasking is, you know why a user may want to have two tasks running simultaneously. And so on.
Sorry to go off on a tangent but this attitude is really dumbing down computing and may prevent the windows phone OS from ever being adequate.
Click to expand...
Click to collapse
+1 with you on this.
WP7 to current 8 is simplified to point of being useless. I have wm6.5 to WP8 devices & can't believe how hard it is to achieve the most basic functions even with fully unlocked custom ROMs on WP7.8.
Font should be simple so people can add required support for specific fonts for things from sms to docx. Only reason many users found it all too hard back on wm6.5 is fact most people had lower level PC knowledge back then & Microsoft didn't make things any easier & know just omit features completely !
Wm6.5.5 stays my daily device & work standard platform for my company.
Dear,
times because many users from different countries or continents themselves are devoid of using a Cyanogenmod? Because often the warriors who are programming the current versions of Android on devices forgotten by companies like Samsung, who think only update the TOP line and when others leave throw them aside?
I am suffering with the same damn TOUCHWIZ and can not use a CM11 4.4.4 for the simple reason that the firmware for my device is not suitable for ROM made for his model because I have a FW MTZ BRAZIL and it only runs second programmers on a FW KPN Netherlands, and I have tested and can not make connection in my firmware at least everything works but the audio is with many problems, both the link as the call. Is it so difficult to test this FW Cyanogenmod and solve these problems instead of insisting on getting another firmware works?
I wanted to be using a CM11 and using almost 100% of what my device has to offer.
I wonder if it's so hard so find a bug of call tone that leaves his voice as if you had swallowed gas Helio, and get the speed of the music player that is is in 1.5x? Or is it easier to provide something that works only on who's programming the ROM device and eager users of that device they turn?
Hi Everyone,
I have a Samsung S8500 with Bada 2.0 installed on it. I read in the internet that it is possible to put an unoffical Android ROM on it. Obviously there are existing a lot of different roms (Zendrokat V2.3, Iczen veyron, Omni etc.)
It's very difficult to get a good overview of all versions and existing bugs.
What should work if i install android:
- making Calls, texting messages
- Wlan, 3G Internet Browsing
- WhatsApp and Snapchat (maybe skype and viber?)
- Camera
- Kalender
- no Games
Do some of these roms support this basic smartphone functions?
I also read that there is a problem with the overheating protection. Is this solved by now?
I am willed to take the risk that this whole flashing can destroy my phone, but i dont want to risk a fire in my flat or maybe a exploding battery in my pocket! Can I be sure that this doesnt happen?
Which rom would you suggest for me? Or will be a new one be released soon and i should wait for it?
Thank you
CheVeyo