*** 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
Just to let all those interested know - 6 months ago I was whined at for mentioning a £80 phone that did all that I needed my Windows Mobile phone for at a fifth the price...
All were convinced it would die after 6 months - oooh look - its still working. And its probably made in the same factory as the one you are looking at that would cost £500... maybe even at Foxconn which even under German Luftwaffe rules would collectively qualify as an air ace with 13 'kills' so far of its own employees through either suicide or suspected beatings or exhaustion (all other WW1 air forces only required 5 kills, hence the boast that the German AF was twice as good..).
Sadly since there are no phones available at the moment that fit what I need from a phone in the WinMo arena I will either be buying the S4200 QWERTY flip with wifi & TV - or reinvesting in the joys of symbian with the Vivaz Pro - the best phone I ever had is still going strong - an E70 from Nokia thats 6 years old now and still lasts three days on standby. Sadly its getting a little slow in the tooth...
The only niggle I have with the TVG3 is the camera quality and also there is no one place to control data/wifi selection. Other than that its perfectly usable.
Since I had to look for JAVA applications as there are no developers for the MTK O/S system as used in both the TVG3 & the S4200 I have found a couple that are useful and may be of some interest to people here...
Firstly Snaptu - which is a java based app which works with touchscreens and can provide either apps or links to websites along with RSS newsreader feeds and a eminantly usable weather application including of all things astronomical information. This includes a very usable facebook application.
There is also a application called microcalc which is a spreadsheet which is able to accept data from excel using the *.slk extension (SYLK - symbolic link)- although to be fair this is not a complete conversion.
There recently some busy with this i know but in my eyes they don't work on it anymore.
Samsung H1 is a Linux LiMo phone.
A nice fone with not alot of apps 720p camcorder and 16GB intern memory.
But LiMo seems to be a death project...
What i wondering if some one of this site can port android for it.
Most of the users here porting android i know reason i ask it
Some info about the phone on other sites
http://www.limo-os.com/forum/viewtopic.php?f=3&t=68 some docs
http://h1.pargon.nl/wiki/index.php?title=Main_Page more info might help i guess
http://h1.pargon.nl/gitweb/gitweb.cgi more info might help i guess
http://code.google.com/p/h1droid/wiki/GetSource Source
http://gitorious.org/h1droid/ Source
http://code.google.com/p/h1droid/wiki/GetSource?tm=6 How to compile it
http://www.freelimo.tk/viewtopic.php?f=2&t=15 More And More info
What work and not work at this moment
What works?
- Touchscreen (does not support multi touch)
- Alarm & Clock
- 2D acceleration
- LCD - high resolution
- Brightness ajustment
- Sound
- 3D acceleration
- Phone
What doesn't work?
- Gravity sensor
- Camera
- Wi-Fi (in progress)
- Shutdown
- RTC
- Rotation sensor
- Power management (in progress)
- GPRS
- 3G
- Bluetooth
- GPS
I hope you can help me cuz i want android as my main system on this great phone
Right 80 views and no comments wth cmon some one know how ?
I come from PRC
Good Luck!
magicalyun said:
I come from PRC
Good Luck!
Click to expand...
Click to collapse
i can't port it reason i ask lol
Can you make the ROM available
Many of my friends here are concerned about this phone!
If you can do to help, to raise!
English is not very good sorry!
I'm waiting...............
Yes!
Please someone give a fully working android rom that works on this phone!!!
Please!!
I need it badly
ninphilius said:
Yes!
Please someone give a fully working android rom that works on this phone!!!
Please!!
I need it badly
Click to expand...
Click to collapse
Maybe end òf oct...........
Hopefully this can be a sucess, this phone deserves better than LiMo with Vdf 360.
Heard that at least the wifi is already ok.
any news on this?
magicalyun said:
I come from PRC
Good Luck!
Click to expand...
Click to collapse
from limofans.com?
Anyone tried compiling the kernel? I got 2 errors when it finished doing LC LD stuff. Didn't even know it had 16GB, what a waste!
Android on GT-I8320
It would be so great to see android running on this machine, i have a friend that just sold his phone because of this stupid LiMo. How come it's so hard to have a working version? Is it because of drivers? who are the responsible?
any news on this? such a good phone, basically an expensive paperweight as i'm using x10..
Hi there.. There's awesome news...there were released more android roms and phone calls already work, but there's work needing to be done!!
More Info for developers (Chinese forum, main forum) limofans
Portuguese Forum: samsungh1pt.freeforums
International forum: freelimo
Git repository (owner mephisto...it still has not phone calls working but he needs people to help him) gitorious h1droid
Since a user released the drives that control phone calls and etc...the project seems alive again... the latest rom is 0.3!
There's also a lot of videos on youtube!
Hi there,
I just bought this wonderful phone with those awsome specs, even better than iphone 3g for 100$...
1 day of studying Limo OS and 360 service off, I love this phone... But there are some not good things about this OS (wi-fi internet loading big pages always crashes, not working GPS becouse only 360 users can do it..). Google'd, and found that people from China, Portugal, Poland Spain, have transported Android OS v2.2 froyo to this phone, but there are not working camera, UI sensor and other things...
Looking forward to next release of H1Droid. Just read chinese forum, and found that they already have H1droid 0.4 version in those days.
Want android system so badly...
Portugal page, about h1droid 0.4: samsungh1pt.freeforums.org/portal.php [use google translate to translate in english]
Wifi is now working...stil some work needed in phone module and power managent!
GPS, Bluetooth ... not working yet!
Please contribute to this project!
is the processor on h1 fast enough for android 2.3?
It is! But it is too soon to port to android 2.3! We have to finish first the work on android 2.2!
Rom 0.6 released!
samsungh1pt.freeforums.org
Hi guys,
since Google Wave is retiring, even though it's a very interesting service, I had to search a similar service:
- One that is forum-like (make a topic, invite the right people, discuss)
- is easy to use (you can access on PC, phone, etc...)
- not in beta
- and kinda easy to work with (not necessarely "real time collaboration" just the main features)
So I found this so called Google Wave simulator called "Shareflow", I don't know if you guys heard about this one:
http://www.zenbe.com/shareflow
But apperently they have an iphone app:
http://itunes.apple.com/us/app/zenbe-shareflow/id377973788?mt=8
On another note I read about "porting", so I was wondering if someone tried to port this app from iOS to Android? Or an even important question: Does anybody found a similar service like Google Waves (preferably with an Android app).
Thanks for any feedback.
First - Sorry if this is in the wrong spot. I thought about putting it in the Nexus 7 Q&A but I figured this isn't really device specific, more OS specific.
I'm deploying about 25 Nexus 7s to a classroom in the coming week. There's the 4.2.1 update, which I'm planning on just doing through fastboot & the nexus 7 toolkit rather than waiting for each device to boot, connect to wifi, wait for updates... and that whole process.
The question I have is more around customization of the OS across those devices. I'd like to add a couple apps (Kindle / B&N) and also pre-configure the Wifi. Can I do that, then take a nandroid and apply it across all 25 devices - or will that duplicate device IDs and cause weird issues later? If that's not the best way to do this - any recommendations on the best way to handle a multi-device deployment?
Thanks!