Related
New RealVGA ROM Based on Ranju and Darkforce's 6.1 Roms
THING_V4.1 (WM6.1 19188)
Fixed in V41
- Flashdisk 15mb - works only on G4 (ironic eh?)
- Fixed BT Pairing - my Jabra 320S actully works for once
-- if it doesn't pair first time, reboot and try again
- Fixed Skype
- New SDBUS.DLL to hopefully improve SD card support
- USB sharing of SD cards is now fixed using a modified version of Ranju's SD card driver
Base Rom NBA file - using Ranju's V7.1
- Pagepool 5.2mb, default timeslice 1ms
- using this rom as a base causes Notes sync to work perfectly, I don't know why
- Flashdisk 15mb on G3 and G4
OS
- Darkforce V1, massively modified
- Catalog, customer feedback, welcome center, fwupdate, entertainment (games), transcriber and loads more pointless junk removed
- Many OS DLL, CPL, EXE and MUI files are now modules including powerpoint, word, excel, onenote, windows live
- IE homepage set to "about:blank". saves time and RAM every time you run IE
Drivers
- a mixture of Ranju's, JWright's and my own favourites
OEM
- modified camera OEM from Ranju 7.1
- - removed unnecessary DLLs
- - made the EXE non-modular as it's unloaded from RAM on exit anyway
- - general tidy up (initflashfiles recreated, shortcuts organised a bit)
- Storage settings supporting SDHC (default), SD and USB conectivity
- - If your card does not work on first boot, switch drivers and reboot
- - If it still doesn't work, switch back and reboot again
- - I've tried 5 cards, 2 SD, 2 SDHC and 1 miniSDHC in adaptor. All worked using this switch-reboot-switch-reboot process
- My own OEMApps collection, very small with good support for 192, 128 and 96 DPI
- RealVGA (as always)
- STK (my one with low mem footprint and now with nice icons too)
- Schap's Advance Config and VOIP Settings tools
- Jwright's Network Plugin and Network Wizard OEMs
- Performance App (over/underclock - defaults to 520mhz, no over/underclocking)
- Pimbackup 2.8 by DotFred
- Laurentuis26's pocket notepad
- GSPlayer by GreenSoftware
- ArcsoftMMS (partly modularised)
- Pocket RAR by Rarlab
- VijayCandellaLite by Vijay555
- TotalCommander2 by Christian Ghisler
- XPDF
- Today screen is kept minimal to save RAM. The standard plugins are included and can be enabled on the "settings->today" menu
- TCPMP0.81 by Coreplayer team - modified to use some plugins lifted from VTAP
- - libmad.plg replaces mp3.plg for better MP3 decoding
- - new MPEG4.plg decoder
- - general tidyup of other plugins
- - frequently-used plugins (mpeg4, ac3, mp3, intel PXA renderer etc) are now modules
- Like the SYS section, the OEM section is almost totally modular
- - OEM EXEs are not modular as they will not fit in VM
- - Some DLLs are not modules, again due to limited VM space
Notes
- RGUs have been removed from this ROM. I know this annoys rom-cookers, but it makes the ROM smaller and faster for users.
- To make up for this, I've released the exact kitchen used to build this ROM, with all the RGUs intact.
Thanks
- It should be obvious by now that I owe a lot of thanks to Ranju for his recent 7.1 release
- Just to repeat, the Base nk.nba, some drivers and the updated Camera OEM in this rom are all based on his ROM and Ranju deserves credit for that work.
- The Darkforce team deserve huge applause for their work on getting a functional 6.1 running on the Uni.
- The SYS section of this ROM is a heavily optimised version of DFT V1's SYS.
- Thanks to the developers in the "Developing and Hacking" forum, Schap, Dotfred, Vijay555 and the rest of the gang
- My fellow ROM-cooks, Laurentius26, Beasty, Ranju, Midget1990, JWrightcmps, Mo3ulla and all for sharing their work with the community
- The users who eagerly test our work and keep us pushing forward
- The ops and moderators of XDA-developers.com
- The gods - bepe and mamaich, in a class of their own
- Anyone I've forgotten - not intentional I'm just absent-minded ;-)
Important notes :-
Beasty has informed me that using the flash bulb for long periods can cause the thing to burn out - so please only use candella for short periods. If you're really worried about it, disable the lightbulb key under "settings -> buttons" and assign it to some other function or <NONE>.
Before flashing ANY cooked ROM, your phone should have the latest bootloader version and be fully unlocked and SuperCID, otherwise it may lock up or crash randomly. Do this with bepe's glorious unlock tool here:-
ftp://xda:[email protected]/Uploads/Upload/HTC_Uni_Unlock_v1.7z
Here's the ROM (please mirror it if you can) :-
ROM4.1
http://rapidshare.com/files/94351047/THING_V41.build28_ROM.7z.html
ROM4.1 128MB (no pagepool)
http://rapidshare.com/files/94358193/THING_V41.build28_ROM_128_nopage.7z.html
Kitchen4.1, extract it to C:\ :-
http://rapidshare.com/files/94356108/THING_V41.build28_Kitchen.7z.html
Note that both are compressed with 7-ZIP www.7zip.org. It's way more efficient than ZIP and it's free.
wow.
this looks amazing!
I now might need to buy me a universal again.. dropped mine off the balcony.
Will receive tytn2 tomorrow. if it sux i will try your rom! (or i might anyway)
a what kind of file is this?
WTF?
It's a 7-zip archive, freeware archiver.
http://www.7-zip.org/
Thanks thingonaspring for the kitchen link!
Can you post a dialpad screenshot? How many RAM after reboot?
Ram on reboot (all today items enabled, voicecommand disabled) is 28.71mb.
Seems to be nice, will try it when i get my new batery!
What about FlashDisk?
COOOOL
By the looks of it and if it is stable, it seems this is going to be my ROM for a while. Thanks thngonaspring without you guys we Uni owners are completely lost. Keep up the good work
There's no flashdisk in this rom, sorry. Flashdisk builds of 5.2.1908 only work on G3 hardware, as far as I've seen anyhow. I wouldn't be able to test such a ROM on my G4.
can u pls post some other link than rapid share i cant download from there for some what reason thnx, i really would like to install this and check how it works
Hiya
Mamiware's been looking over the ROM and come up with some improvements.
Firstly - a better WIFIWPA fix, I used an older one so the attached one is recommended.
It's attached is as a Cab file (install onto your device, remove \windows\startup\wifiwpa link and reboot).
And as a small patch to the kitchen, just unpack the kitchenpatch_1.zip archive over your existing DEV_UNI directory.
Lastly the kitchen patch removes a junk line that mamiware spotted in the BASEAPPS RGU file. None of the junk makes it into the registry during the build process, but it's better not to have it there.
Mirrored on vidmes.com - http://vidmes.com/Uni/ROMs/thingonaspring/Thingonaspring.Uni.WM6.2.11.1908.18508.REALVGA.v1.7z
Thanks TehPenguin!
Waiting for kitchen mirror site...
Password of the kitchen?
No password. It's not encrypted.
Can somebody mirror kitchen too, plz?
Attempting to mirror the kitchen to daddyfile.com
taking a while.....
....Urgh failed
trying again to filedrom.com.....
...urgh failed
anyone else fancy having a go? it's prety much bedtime here
Hmm...
Okay
Hi there, anyone tested the A2DP on this rom?
This topic has been floating around the forums for a long time now. For as long as chefs been cooking, they’ve been trying to cook their “perfect rom.” Well…unfortunately they can’t do it by themselves. They need some help from us…so this thread is for any and all feedback we may all have as users, to offer to our chefs in order to achieve our goal.
Keep in mind guys, we’re all different people, we all require different things. Let’s keep our thoughts realistic and respectful. We’re use to 3 types of roms….Full, Medium and Light (lite.) Let’s see if we can offer up a somewhat standard model and set of applications for each type of rom.
But not just apps….lets break this down to CE builds..OS tweaks…radio performance…visual preferences…..EVERYTHING!!!!
also (i know this is gonna cause an outbreak!....) if there are any outstanding issues you've been having with all coked roms across the board...feel free to mention....The more we're all aware of something the better the chance it will be addressed!
======================================================================================
((Results and conclusions))
-For the most part, we can all agree certain apps should not be cooked in because they're updated too often.
======================================================================================
((Topics and issues))
--------------------------------------------------------------------------------------------
*well i can't edit the poll...so we'll have to do this the hard way. So we have the "to be cooked or not" apps figured out. Next is the model in which the roms are produced. Like i said before...theres usually 3. Lite, Medium and full. We need to define the roll and specs of each and what they contain. Sound Off
--------------------------------------------------------------------------------------------
At the request of mr.dutty i've added a poll. Im not sure if i can do this, but i'll try to switch it up everyday with a new subject everyday or so.
* = current topic
almost was going to warn you to get some flame retardant clothing at first glance. However after reading a bit more it does not seem to be a bad idea, assuming it can be kept free from garbage. Ill put some thought and contribute what i can but not a bad idea.
A few things I look for in a cooked ROM -
Hardware keyboard performance: We're talking about a device that features a very nice full hardware keyboard, and roms should take this into account. I've encountered roms that have laggy keyboard entry, other weird keyboard entry problems, and some which work beautifully.
Careful which apps are cooked in: If an app is likely to get updated frequently, it's my opinion that it shouldn't get cooked into a rom (unless, of course, it's a PITA to install in the first place). There'd be no point cooking PointUI's Home into a ROM, as it gets updated a lot. Also, the legality of any cooked in App should be considered. For example, I'd love to see a rom that's got Opera Mini cooked in and ready to go as the default browser, which is a lot of fiddling around and hard work, rather than a rom that uses the NOT FREE Opera Mobile.
Screen Rotation Speed: Some ROMs have managed to achieve near instant screen rotation speeds, others have not. It'd be great to know what settings affect this, and cook them in.
Options: I hate Large Start Menu. I love the fact that you can easily turn it off without any side-effects. I love the fact that Quick Menu gets cooked in, but you have the option to not use it (I'm firmly in the "loving quick menu" camp though, at the moment).
Most important: Speed. I really don't feel like this device is performing quite as well as it could do. I think we could get there - I think there's still some exploring to do, and at some point there'll be a major breakthrough.
Maybe this thread is the start of all of that?
Thank you For starting this as this will alow us to find out from different individuals thier own opinions and also from different chefs as to how we can maximise the best performance out of this baby kaiser.
At the moment Im trying different stuffs
I don't know to much about this stuff, but in my last month of looking at these forums.. I think a lot of people use these
- Pocket Core Media Player
- SOme form of Registry Edit
- Task Manager (Detialed one, WTask i think it's called?)
- Pocket Screen
- Office (obviously)
- Note pad (love it)
- Touch Settings
- Query Analyzer (maybe not for everyone..)
- Slide 2 unlock (better to get that yourself probably now that I think about it)
- Schapps advanced config 1.1
- KaiserTweak
- Total Commander looks pretty usefull
- Some sort of FTP program
- I wish there was some app for linking HTC favorites in the cube to their contact record (give you option of calling,e mailing, etc, instead of a quick call)
Not very advanced stuff, but stuff I hav efound pretty usefull that i never knew about.
swtaltima said:
almost was going to warn you to get some flame retardant clothing at first glance. However after reading a bit more it does not seem to be a bad idea, assuming it can be kept free from garbage. Ill put some thought and contribute what i can but not a bad idea.
Click to expand...
Click to collapse
lol no worries man. i got my suit bag unzipped and waiting!
i guess i'll give it a go....
me myself...I prefer a Full rom. but it seems very unrealistic as to what’s in a full rom or not. I’ve been talking to dutty a bit about this and he wanted me to get some ideas and get back to him….so I guess this is the place to get it all together. For those of us with a tilt…we all know how fat the shipped att rom was. But the funny thing is…it wasn’t slow at all! This is what sparked my thoughts. How about…a full rom = a bloated rom! But not bad bloated….good bloated. I’m talking about any and all those little apps we all know and love. Such as….group sms…call firewall…opermini (files provided to set as main browser…I think that should be left up to the user,) tom tom...quick menu….Live search and all other live apps, all HTC current apps and dialers….ect ect. I wanted to include slide to unlock, point ui and pocket cm…but these apps are updated too often to cook in….but non the less would be great for a full rom. I believe the cooks can find a way to make a rom like this work!
For a media rom….pretty much the rom…plus all the htc goodies we’re all used to. And the the rest of the inessentials….things like flash lite…youtube already cooked in....ect ect. It should be kept clean and nice.
A lite rom?....nothing! lol…lite roms are for those of us who like to tinker ourselves or just don’t use a damn thing on the phone…so I think it should be just the os! And call it a day.
I think we need to add a poll of some sort to vote on what apps should be included in each rom so we can observe, study and compare what individuals use in thier roms and what they dont like.
dan13l said:
A few things I look for in a cooked ROM -
Hardware keyboard performance: We're talking about a device that features a very nice full hardware keyboard, and roms should take this into account. I've encountered roms that have laggy keyboard entry, other weird keyboard entry problems, and some which work beautifully.
Careful which apps are cooked in: If an app is likely to get updated frequently, it's my opinion that it shouldn't get cooked into a rom (unless, of course, it's a PITA to install in the first place). There'd be no point cooking PointUI's Home into a ROM, as it gets updated a lot. Also, the legality of any cooked in App should be considered. For example, I'd love to see a rom that's got Opera Mini cooked in and ready to go as the default browser, which is a lot of fiddling around and hard work, rather than a rom that uses the NOT FREE Opera Mobile.
Screen Rotation Speed: Some ROMs have managed to achieve near instant screen rotation speeds, others have not. It'd be great to know what settings affect this, and cook them in.
Options: I hate Large Start Menu. I love the fact that you can easily turn it off without any side-effects. I love the fact that Quick Menu gets cooked in, but you have the option to not use it (I'm firmly in the "loving quick menu" camp though, at the moment).
Most important: Speed. I really don't feel like this device is performing quite as well as it could do. I think we could get there - I think there's still some exploring to do, and at some point there'll be a major breakthrough.
Maybe this thread is the start of all of that?
Click to expand...
Click to collapse
point ui makes for a good debate....the reason i would cook it in is because it comes with its own update client. so even if an older version is cooked in....or an update is available a day after the rom is cooked....you just need to go into update and that will take care of that. but i do agree with the idea of frequently updated apps should be avoided.
the screen roatation is another one....i agree. i've seen it vary from rom to rom even within dutty's camp. maybe the cooks can unite and nail that one down.
I've been using different ROMs over the last month or so and what I normally go for is the lite ROM with all the performance updates. Then I add my own apps to it. From the ROMs that have applications cooked into it I may use 80-90% of it which I find is not good for me and I think this holds true for most, if not all users. Everyone has different taste/needs.
Maybe a ROM with just the OS and performance/optimization tweaks and leave the rest up to the users. They can find the cabs for everything so why bother to cook it in. The other thing with cooking in the apps if is if the app gets an update a new ROM is needed.
Or just cook your own ROM. There's enough info within the forums to make your own ROM and include whatever apps you want.
Maybe the focus should be on optimizing the OS and leave the apps to the choice of the user.
ecltech said:
I've been using different ROMs over the last month or so and what I normally go for is the lite ROM with all the performance updates. Then I add my own apps to it. From the ROMs that have applications cooked into it I may use 80-90% of it which I find is not good for me and I think this holds true for most, if not all users. Everyone has different taste/needs.
I think make a ROM with just the OS and performance tweaks and leave the rest up to the users. They can find the cabs for everything so why bother to cook it in. The other thing with cooking in the apps if is if the app gets an update a new ROM is needed.
Or just cook your own ROM. There's enough info within the forums to make your own ROM and include whatever apps you want.
Maybe the focus should be on optimizing the OS and leave the apps to the choice of the user.
Click to expand...
Click to collapse
I cooked a lot of roms but always stick with the full rom, Reason is i could take out 50mb of programs out of a rom and This doesnt give me that equvalent space and also performance sometimes are un-stable, thats my own opinion.
I think there is a halfway line with how much goodies you can install in a rom to please most people
ecltech said:
I've been using different ROMs over the last month or so and what I normally go for is the lite ROM with all the performance updates. Then I add my own apps to it. From the ROMs that have applications cooked into it I may use 80-90% of it which I find is not good for me and I think this holds true for most, if not all users. Everyone has different taste/needs.
Maybe a ROM with just the OS and performance/optimization tweaks and leave the rest up to the users. They can find the cabs for everything so why bother to cook it in. The other thing with cooking in the apps if is if the app gets an update a new ROM is needed.
Or just cook your own ROM. There's enough info within the forums to make your own ROM and include whatever apps you want.
Maybe the focus should be on optimizing the OS and leave the apps to the choice of the user.
Click to expand...
Click to collapse
all good points...i tend to agree with you. but lets not forget we're dealing with people who dont know how to hard slp...refuse to read through 30 pages of posts or even use teh search feature. so a full features rom will always be needed.
rzanology said:
all good points...i tend to agree with you. but lets not forget we're dealing with people who dont know how to hard slp...refuse to read through 30 pages of posts or even use teh search feature. so a full features rom will always be needed.
Click to expand...
Click to collapse
This is true. For a full featured ROM I think a based ROM might be better versus cooking in many apps. Here's a list that I think can be a good starting point for a base ROM. Some utilities, tweaks, visuals, etc. The rest can be managed by the user.
- Advanced Config
- GPS Test
- HTC Album
- HTC Camera (new version)
- NotePad
- Registry Editor
- Pocket RAR
- Office w/OneNote
- PDF Viewer
- psShutXP
- QuickGPS
- Total Commander
- NetCF 3.5
- ClearTemp
- KaiserTweak
ecltech said:
This is true. For a full featured ROM I think a based ROM might be better versus cooking in many apps. Here's a list that I think can be a good starting point for a base ROM. Some utilities, tweaks, visuals, etc. The rest can be managed by the user.
- Advanced Config
- GPS Test
- HTC Album
- HTC Camera (new version)
- NotePad
- Registry Editor
- Pocket RAR
- Office w/OneNote
- PDF Viewer
- psShutXP
- QuickGPS
- Total Commander
- NetCF 3.5
- ClearTemp
- KaiserTweak
Click to expand...
Click to collapse
agreed. can we all agree this should be a common app set?
rzanology said:
agreed. can we all agree this should be a common app set?
Click to expand...
Click to collapse
Thats almost what I got apart from pdf viewer which i left out for user preference with adobe reader
the most popular apps don't have to be cooked into a ROM. every ROM can be a light or medium with everything else added as shared backup files using Sprite or SPB Backup. in another thread, some folks expressed reservations about my idea of Backup Install Packs, but i still think it could work. and no one would be forced to use them. it's something at least worth trying.
after flashing a new ROM, the ROM cooker or someone else could install demo versions of the most popular apps (HTC apps, Resco, SPB, SBSH, Opera, Palm Messaging, Kaiser Tweak, TCPMP and the plugins, etc.) onto their devices. They can then make a backup of their devices and make that backup available to other users. Then if someone installs the identical ROM, they could simply install the entire backup of those applications to their own devices. Users can keep the apps they want and register them with their own serials. They could then uninstall the rest.
that would be my idea. keep all ROMs medium and lite and let users customize them to full status with backup install packs.
PointUI drove me nuts, was nice and pretty, but in the way. Then again, I don't like the Cube either. Perhaps if I set up the cube I'd use it more, mainly for the contacts though - I don't use WMP or HTC's, I use TCPMP.'
I love the apps Dutty has, especially WKTask with its launcher and battery bar, quickmenu is awesome (without the large setting).
PocketCM has asked that it NOT be cooked in so...
IMHO a ROM should be usable for as much user as possible.
For one person S2U2 is a must-have application, but others just don't like it.
So a stable, fast and clean ROM should be the best for everyone.
Everyone can add his favorite apps, or don't add apps if you don't like them!
Just my opinion. (Of course I always go for the LITE variant, cause I just don't use a lot of apps)
What I would like to see:
Pretty much the default set of apps and tools in the stock ROM. Some of general use like pocketrar could be integrated but not much more.
Larger page pool.
What I absoltely don't want to see:
Too many UI changes, trial versions, bloated battery status apps and such.
Basically I just want the latest radio, OS and default apps all in one.
Stuff that's not likely to get upgrades for quite some time like the flash player and flash lite could preferebly be integrated but other than that I don't like too much tweaking, I just want the latest versions of the default stuff and then I do my own modifications and tweaks from there.
thanks for setting this up!! But i agree should install from CABs
No, They're updated too often to even think about cooking into the rom!
We need 1 stable EMPTY ROM. And cabs what have been edited for working on the 1 stable empty rom.
*** 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
ROM modders/developers!
I'm the developer behind ROM Updater. It's meant to be an universal ROM updater (which means, it doesn't really care if you're on CyanogenMod or you're on the "whitelist"-free of ROM Manager). There is even a PHP script (on the website) which will automatically create incremental updates, cool feature of my app which lets both you and users save a lot of bandwidth. Please consider "adopting" it, it's free ^^
elegos said:
ROM modders/developers!
I'm the developer behind ROM Updater. It's meant to be an universal ROM updater (which means, it doesn't really care if you're on CyanogenMod or you're on the "whitelist"-free of ROM Manager). There is even a PHP script (on the website) which will automatically create incremental updates, cool feature of my app which lets both you and users save a lot of bandwidth. Please consider "adopting" it, it's free ^^
Click to expand...
Click to collapse
Nice work Elegos
Fantastic, consider me a supporter.
I think u have delivered it pretty well
Update: I've released incremental.jar and relative sources. Go to the website and check
New in version 1.8 (from version 1.7):
- Tried to fix a Null exception error, received via Market (thanks for reporting!) (please test)
- Added incremental.php and incremental.jar (plus sources) in the git repository to easily create incremental updates
- Moved common variables in a singleton (SharedData class) and more comments for easier understanding of the code and less variables around
PLEASE NOTE:
You don't have to mess up with the ROM name anymore, the program will check for the ro.build.display.id (MOD name) and ro.build.version.incremental (!!!INTEGER!!! version number), as well as ro.product.model (for future releases, in our case be sure is "Nexus One"). The repository main.json file has a new variable, "model" which is, indeed, the same of ro.product.model. Future versions of the app will make impossible to download updates not for your phone.
DEVELOPERS:
You have no excuses now ! I've talked with some other modders who say, for example, their updates are changing rather all the files, and I say you it's not true. Making some tests I saw that using incremental updates make the update 50~75% smaller, even with MIUI weekly releases. This means "bye bye" to the bandwidth problems, both for hosters and users.
Just added your page as my favorite. Will study and use it later, hehe ,need some time to know about it~~~~
So how do I set up repository for. CM7 nightlies? Do I have to enter it manually?
Sent from my Nexus One using XDA App
I'll give it a go. I have been using ROM Manager and it works very well but I was getting concerned with the bandwidth used for the CM7 nighties.
This does support CM7 nighties right?
Also, what about getting notifications when there is a new build for ClockworkMod Recovery and backup/restore options for ROMs that I keep on my phone?
Wow, as a themer, I would have to say that the idea behind this is amazing. I would love to see it adopted by everyone. I would like to be able to see what exactly has changed between updates, it would save me a lot of time personally. I commend you for your work on this. Woot
@apratomo: you need someone who sets up a CM7 nightly repo. I can't, as it would mean I should support every ROM out there, and my bandwidth is limited (I can host one ROM if you want, not 1000 ). By the way you should edit the build.prop file in order to edit the incremental value and make sure the ROM name is allways the same (display.id).
@pfran42: it supports any ROM you want, this is why I made it
It actually don't check for new recovery images, as it relies on external repositories only, I may create a different application for that though. As of backup/restore, it currently has an option to backup the current ROM wherever you want (see options). When I discover how to restore a nandroid backup via command line, I'll add that feature too.
This is a great idea, however adoption may be slow. Even though its an AWESOME idea, it may be a good idea for you host a popular ROM elegos to get the ball rolling. I'd hate to see this die...
Ok so I have to launch a poll. Problem is that:
1. In the generic Android Development forums (where this really thread should stay) is overcrowed with posts, most of them are just publicity for apps on the market.
2. I'd love to have the attention of all the android people to partecipate to the poll. Of course I MAY create a CM7 nightly repo, but it would mean daily work for me (and a lot of space on my host).
I'm working on a system that should keep a list of repositories automatically updated every time you download a ROM with the app (accepting to send anonymous data). It's ready in the git repository, I'm waiting to push it live 'cause I want to create an interface to grab that data too (a sort of list ordered by phone model).
I think that just for starting I'd love to host a Nexus One Gingerbread AOSP, just like MicroMod777's one (TBH I already have that repo online, but it's frozen at version 20 as MicroMod is focusing on CM 7 custom builds, which I dislike for its too many customizations (both CM itself and MicroMod's)). Alternatively an AOSP 2.3 with no apparent changes (i.e. maybe CM with standard launcher). Any idea?
Sometimes you just have to prove how good your ideas are, because people are lazy... good luck my friend.
Sounds interesting.
I'm going to release a "major" update: all the times a user downloads a ROM and accepted to send anonymous data, the repository, ROM name & version and phone model will be sent to a database, which will return back a list of repositories directly in the settings menu!
I've released version 1.9 and made a Enomther Nexus One repository. Enjoy!
Version 1.9.1
- Fixed an untranslated italian string
- Fixed the import of a repository URL via the repositories list (new line at end of repository)
- Made the application more solid when there are connectivity problems / no internet available (no crash anymore)
awesome work!!
have tagged the link shall go thru it...gr8 job elegos ..!! ..PeacE
Awesome ^-^
Hey guys,
it's done! The first version of our (Flemmard and me) M10Editor is released.
Check out the original thread here.
New Version
Hey,
i just released version 0.5.10.170 with a bunch of new features!
Changelog:
added possibility to zipalign apk
added possibility to "adb push"
added possibility to reboot phone
added "Quick-Save"-Feature (STRG + S)
added "Quick-Load"-Feature (STRG + L)
added "Quick-Push"-Feature (STRG + P) (keep in mind you have to save the apk first. Otherwise, pushed apk contains no changes)
added "Quick-Save&Push"-Feature (STRG + Q) (first saves current changes and then pushes the apk)
added "Quick-Reboot"-Feature (STRG + R)
added kind of sorting to properties view (known properties first)
added better log output from de/encoder
some gui enhancements
cleaned up editor-view
Clarified errormessage after decompiling m10-less apks
fixed some minor bugs
Donwload here.
Here is another new version.
Mainly fixed bugs this time. (Introduced with the last version )
Changelog
0.5.14.208
removed zip.exe/unzip.exe, now done natively
fixed lots of bugs
fixed really bad bug with zipalign (not my fault actually xD zipalign behaves a little strange...)
huge code cleanups
added some usability improvements
Download here.
Okay guys, we got a major breakthrough aaaand we have some pretty nice images for you
Here you go: (last one got corrupted due to screenshot)
Stay tuned for further imformation
Hey guys!
Here comes the new version! Biggest change is that we are now able to decompile and edit the pictures which are compiled in m10-files.
But keep in mind that this feature is in beta status atm, so please be careful while using it.
You will be able to change any pictures inside the m10-files. For example the "ring" on the lockscreen (see my previous pictures) or the backgrounds of the lockscreens.
BUT: You can only edit these files. Resizing is NOT supported right now. You WILL destroy the m10-file! Seriously!
Best way is to open up the original picture directly in your preferred image-editor (right click on picture-->Open in Explorer)
Editing images is not super easy. If you do something wrong, it's likely you will screw the apk. So please be careful.
A little tip: Most images are NOT in the normal apks but in "shared.m10" in fusion.apk. Even if they are in both apks, Sense uses often the ones from shared.m10.
Here is the full changelog:
0.5.22.313
image-files now de/encodable (!!!)
needs to be activated under "m10-files"
please keep in mind, that the m10-image compression is NOT lossless,
so please do only decode the images if you want to change them.
Otherwise the quality may decrease after a certain amount of decompile/recompile-turns
please DO NOT resize images yet. This WILL screw your apk.
Editing the image is no problem.
this feature is beta at the moment. So please be careful with it.
It is likely you will screw your apk if used without care.
added possibility to work with the program without using ADB & zipalign
added generic ADB-Window
divided property view into "Known Properties" and "Unknown Properties"
got rid of de/encoder.exe, now done via native library (you can use them via commandline nevertheless)
properties are now completely sorted
some other bugs fixed (mainly cosmetic)
Download here.
New Version
Hey guys,
i got a new version for you.
We mainly fixed an critical bug in the image decoding process.
Reminder
Dear people, please keep in mind, that this software is our own work and that we are spending hours and hours of our freetime to create this essential piece of software.
So, please consider a little donation to keep the development alive.
Every donation is much appreciated, no matter which amount.
If you want to get mentioned as a donator, just write me a PM with you confirmation code or put your xda nick in the donation.
0.5.25.321
fixed bug with decoding images
fixed a bug where changes were reverted back to normal
Download as always here.
New Version
Hey guys,
we got another new version for you.
The possible fix for the encoder failure is included together with a possibility to check whether a file can be de/recompiled without issues.
I recommend that you should always press "Check all files" prior to modifying any of the files. Once the tool told you that everything is alright, you can start modding.
You have to this only once per apk.
In later versions i may automate that.
Here's the changelog:
fixed another decoder bug
added possibility to check whether a file can be safely de/recompiled
do NOT edit files which fail in this test, this could lead to unexpected behaiviour
Reminder
Dear people, please keep in mind, that this software is our own work and that we are spending hours and hours of our freetime to create this essential piece of software.
So, please consider a little donation to keep the development alive.
Every donation is much appreciated, no matter which amount.
Get it here.