Database Users

Status of the Vogue-Android Project, please read

Ok everyone,
There's been alot of movement both forward and laterally on the vogue-android project lately, and while it's all been great I'm having some concerns.
There has been alot of forking lately of the project. Different builds are great and I can't encourage that enough, but with all of the changes, and great developments being made to the rootfs and kernel we are losing alot of what made this project going great.
There's such a jumble of builds, out there right now it's getting confusing for everyone. So please guys can we move the project back to centralization?
By that I mean build threads are for system images only.
Changes to the rootfs's and kernel's are fantastic, but please can we make a new thread just for those?
As well to all the kaiser guys. Don't get me wrong I think it's great that so many of these files are working so good for you guys but can you keep development of your port to your forum, so there's less confusion for the new people? I've said it lots, if any of the kaiser guys wanna port over the builds I've ported to kaiser's go ahead, but please post them in the kaiser forum.
I'll happily keep the google code page updated with new bundles, that have been tested and confirmed stable, that page is not for specific people's work only, but for vogue/kaiser files that can be considered the standard files to use.

I support this.

well put. i feel the exact same way. i've given up till a bundle comes out cause im confused what is the newest or if it will work(not a fan of the kaiser now that they took over). I'm really hoping for more development on the android rom but im a script kiddie and no developer.. unfortunately
thanks for bringing this up

I could not agree more!
I've actually returned to running WinMo on my phone because I've become so lost in the Android project. There's so many different forks out there, and all sorts of random files being uploaded to Google Code, I have absolutely no idea what is what anymore.
It was going really well when vilord and dzo were working on it, now suddenly it seems both of them are out of it and the "vanilla" Android 1.5 builds are no longer being worked on. There hasn't been a basic "system" update in nearly a month now.
And to make matters worse, there's no clear explanation of what's what anywhere and nobody is posting proper change logs. So all these new files keep popping up with no word on what they're for and what's changed.
I just want to run Android on my phone, with no stupid skins, UI replacements or massive customizations of any kind... and I don't know how to do that anymore.
I'm not really sure why all this work seems to be focused on customizations right now anyways, when there are much more important things to work on like Bluetooth, aGPS, and a flashable ROM.

Yes, this is most definitively needed, not to stifle anyone's creativity, but to allow the maximum number of people to enjoy the project. Otherwise it's far too possible that all the various ports will just turn people off to Android, and it's far too important to allow that to happen. I've already asked mssmison to post whole, relatively stable packages so people don't get overwhelmed with all the various components and builds. Maybe a re-fresh of the packages every 2 or 3 weeks, along with the testing packages for all you brave souls to make it more user friendly.

I'm going to re-organize the google code page for vogue tonight so it should be more clear for everyone. vilord isn't out of the project, he just is moving

I've cleaned up the google code page a bit, I've depreciated some older downloads and the older bundle.

I keep all my builds separate and off the vogue-android page too keep it clean and focused on the main bundle there which is android-1.5-x. The test rootfs.imgs that I put out are only for testing purposes and are my personal experiments related to hero and they stay on vogue-hero. They do not apply to non hero builds and I try to state that in the threads I started for my other two non hero builds. I'm not supporting squashfs right now and I'm not going to be posting builds in squashfs right now. If people think that squashfs is the way to go then all images need to be in squashfs including android-1.5x builds. That would avoid the main squashfs rootfs/kernel/initrd fork thats going on with people downloading the squashfs base files. I don't support kaiser wifi builds of my hero images because they don't work for the vogue. I'll be taking down all kaiser/squashfs related files on vogue-hero until further notice and create vogue bundles of the files that work with each build.

i agree about too many different builds and files mixed together, it's really confusing to an average user like me who's sorta new to android. you devs should package up a zip with all the most stable, needed files for you specific builds so we can't mess up and download something that might not work right. myself i use my phone daily and for work, so i need stability.

mssmison said:
Ok everyone,
There's been alot of movement both forward and laterally on the vogue-android project lately, and while it's all been great I'm having some concerns.
There has been alot of forking lately of the project. Different builds are great and I can't encourage that enough, but with all of the changes, and great developments being made to the rootfs and kernel we are losing alot of what made this project going great.
There's such a jumble of builds, out there right now it's getting confusing for everyone. So please guys can we move the project back to centralization?
By that I mean build threads are for system images only.
Changes to the rootfs's and kernel's are fantastic, but please can we make a new thread just for those?
As well to all the kaiser guys. Don't get me wrong I think it's great that so many of these files are working so good for you guys but can you keep development of your port to your forum, so there's less confusion for the new people? I've said it lots, if any of the kaiser guys wanna port over the builds I've ported to kaiser's go ahead, but please post them in the kaiser forum.
I'll happily keep the google code page updated with new bundles, that have been tested and confirmed stable, that page is not for specific people's work only, but for vogue/kaiser files that can be considered the standard files to use.
Click to expand...
Click to collapse
+1 to this! It's getting cluttered and confusing... BUT AWESOME!

stickus said:
+1 to this! It's getting cluttered and confusing... BUT AWESOME!
Click to expand...
Click to collapse
is it looking better now on the google code page?

whatever is in that new base files package really sped up my build from zen, ill tell you that much, now my phone recieves calls too. the only thing i notice is im back to the old style button map settings for adjusting volume and waking up the phone and such?

things look a lot cleaner on the google code page now... just DL-ing the new bundle you posted and we'll see how things go from there. Glad to hear that that old button layout is back, not really a fan of the newer one.

all i know is there is no lag to my build at all now, WOW...nice work guys!

fixxxer2008 said:
whatever is in that new base files package really sped up my build from zen, ill tell you that much, now my phone recieves calls too. the only thing i notice is im back to the old style button map settings for adjusting volume and waking up the phone and such?
Click to expand...
Click to collapse
All thanks to the bundle of files go to pmos, him and no one else. I just put together the system.
The button thing was accidental, however I have had alot of problems with my camera button not working intermittantly, we are working on a way of it being user selectable at boot.

I would also agree that some sort of organization is definitely needed. I think that system image threads should be condensed or organized in some way also. Having 15 threads, each with not too much information on what the build actually is, and info on the new update on page 15... just makes it hard for everyone. New comers and people who are experienced and trying to help others.

TheKartus said:
I would also agree that some sort of organization is definitely needed. I think that system image threads should be condensed or organized in some way also. Having 15 threads, each with not too much information on what the build actually is, and info on the new update on page 15... just makes it hard for everyone. New comers and people who are experienced and trying to help others.
Click to expand...
Click to collapse
There are 5 threads for builds. One for the kernel.

welll my phone is still running good today with that new bundle that was posted last night.
im still getting used to the old style button mapping but to be honest i like it better this way.

I think this post goes in the wrong direction.
The best thing of Android is that devs from different mobiles are working toguether to improve our phones.
I´m a polaris user and in the development of android for polaris developers with different phones help a lot
What we need is an Android section as it´s being petitioned in order to develop all toguether. Of course with organization.
Let´s think as Android and not only as vogue

iseeka said:
I think this post goes in the wrong direction.
The best thing of Android is that devs from different mobiles are working toguether to improve our phones.
I´m a polaris user and in the development of android for polaris developers with different phones help a lot
What we need is an Android section as it´s being petitioned in order to develop all toguether. Of course with organization.
Let´s think as Android and not only as vogue
Click to expand...
Click to collapse
I agree but remember this is a vogue forum, so for the average user that comes here, they have a vogue. If you guys have a polaris dev get him to contact me and we'll look into making the bundles work right with your phones as well.
Again this is why I posted the poll to move the dev to another forum where we can have proper organization

ROM-Dev madness!

Foreword: I mean this in the most constructive way possible. While I'm not a <android> developer, it occurs to me that with the wealth of Android ROM-devs and an excellent base of testers (like myself, an unexcellent but present tester), there has to be a better way.
I love XDA-Dev as a resource, and it's been a godsend since I got my MT3G. I've had the opportunity to use some very well done builds which have been time-invested by their developers. I've learned a lot about my device, and am beginning to understand Android as a platform. Here's the beef:
Some ROM-posts are 1000+ pages long. While I could read all 1000+ pages if warranted, it's simply inefficient. What information am I after? I want to know:
Does it work on my phone?
What's the latest version?
Where's it at?
Are there any specific bugs on my phone with this build?
Who else is using this build, and what hardware are they using?
What bugs are being worked on?
What workarounds are applicable to this build?
What bugs are open and need community feedback?
etc...
Is there some sort of bug-tracking setup that could be used to facilitate this? I don't mean or intend to steer *anything* away from XDA-Developers, per se, but this current forum method doesn't seem very conducive to making forward progress.
<shrug> I know, I know, I'm a noob around here and should just work with the herd. I've seen other comments touching on some of these issues, so I thought I'd throw it out there. I apologize if it's been brought up before and shot down.
Hey, what about this? I was looking for a semi-authoritative list of Android ROMs that matched what I outlined above and came across it.
If I had the resources I'd volunteer time/materials to help the cause in that light, but being the schmuck I am (ya' know, working full time and school part time), I can't offer anything substantive. So while this might sound like a gripe, maybe it will compel someone else to make some magic happen. That, or have my account disabled
Any thoughts?

I understand where you are coming from.. but I don't find it that hard to find the rom and information I am after.. all it takes is a little time..
Why not help out by adding to the wiki?

I dont see how this has to do with development, you are just as guilty as the people you speak of.

xyzulu said:
I understand where you are coming from.. but I don't find it that hard to find the rom and information I am after.. all it takes is a little time..
Click to expand...
Click to collapse
I hear ya, it's just not a very concise method and I'm sure you've seen "what's the best build" & "will this ROM work on my phone" and "hey are there any issues with this build", etc...
xyzulu said:
Why not help out by adding to the wiki?
Click to expand...
Click to collapse
I've thought about it, and went as far as the edit screen a few times. Then it's like "aww crap, here goes a few hours...". Back to homework
Jrbourque said:
I dont see how this has to do with development, you are just as guilty as the people you speak of.
Click to expand...
Click to collapse
I think it has everything to do with development, advancement of the builds flying around here, and support of the folks that put their time into it.
Maybe you misinterpreted what I was saying, but I surely wasn't trying to assign guilt to anyone. Things are the way they are because they got that way - doesn't make it right, 'doesn't make it wrong. I just thought maybe there's a better way to support the community.
It's all good.

Jrbourque said:
I dont see how this has to do with development, you are just as guilty as the people you speak of.
Click to expand...
Click to collapse
It's this kind of attitude that is putting a lot of people off. The OP has made some very good and valid points and deserves at least a response to the points he has made, not just a one sentence put down.

[POLL] Eclair ROM ratings for users & devs 01/26/10

This post is a poll for users who like to test different ROM's to find out which one will be the "winner" over their device. Also it is used as a quick guide to find out which of the "ECLAIR ROMs" are the highest rated of the releases for users (and devs) to pick from the HUGE list of ones available rather than flashing, testing, re-partitioning, then re-flashing, etc etc.
I am not at all trying to flame, bash, or put down anyone's ROM that is less developed than others. I myself as I believe others like myself are interested in finding out which of the great ROM's released are by popular vote more exciting to use than others.
I also understand that different users have different opinions, and I as well as many others I know personally prefer totally different ROM's to use on our devices. So on that note, let everyone know of the list which ROM you believe gives you the best experience on your G1 & Mytouch3G / Dream & Magic devices by popular vote.
If I have left off any other ROM's that may be GREAT but just not posted in the poll please feel free to express the name, who it's by, and why you love it!
Thanks for your vote, I believe this will be of a lot of help to others like myself.
Hopefully this post is not considered "spam" and is more for an informational tool

This should be posted in the Dream/G1 Discussion board...not the G1 Android Development section...

guitarfreak846 said:
This should be posted in the Dream/G1 Discussion board...not the G1 Android Development section...
Click to expand...
Click to collapse
Thanks for the correction, however most ROM users, and Dev's don't use the Dream/G1 discussion forum and i believe the intentions of this post would fall on deaf ears.

Ive found my leo to be more entertaining than my dreams, the 2.5 sense UI rom is a beast on it too.

Seems to be pretty varied so far.....

zimphishmonger said:
Seems to be pretty varied so far.....
Click to expand...
Click to collapse
Yes it does, You can see where the most excitement is drawn from which is neat... The poll has multiple answers enabled which I input due to the fact that myself like probably others like more and enjoy more than only 1 ROM, So if you do like 2 out of the bunch or anything feel free to express it and vote for another

You spelled "ratings" wrong in the title.
Remember, first impressions last a life time.

guitarfreak846 said:
This should be posted in the Dream/G1 Discussion board...not the G1 Android Development section...
Click to expand...
Click to collapse
True indeed, this thread is not specifically dev related, but I find it to be very helpful and informative for those of us that are flashing these roms, gives the user an better idea of what to choose from when looking for a good eclair duplicate. And most users, like I, hardly ever visit the discussion board because they are so busy checking the dev forums for new releases and updates. Therefore I find this thread to be placed in a perfectly good position due to to its purpose. MODS please consider before moving.

Yay! Somebody finally picked up my idea koo well
lets see which rom is the best

This should be reset tho every like week or so, cause constant changes happen and one gets crazy awesome over night..so you should have in the title sometimes (I reset this poll on 1/27) so ppl no to see new results...

wrong info

I use [email protected] Eclair 2.1, with spanish kernel, this is the faster 2.1 ROM for Dream and Sapphire.
I´m waiting for a new update, with N1 features and G1 Dream full working.
http://www.htcmania.com/showthread.php?t=90749

Nice Idea, this poll.
But, i think, there should be also a Poll for the Functions needed, not only which Eclair ROM...
So, for me the Killerfeatures are:
WLan/WiFi working
Bluetooth working
Exchange Active Sync working (including Contacts, Calendar, E-Mail)
Sound working (also with Navigation App like Sygic, nDrive, ...)
Not so urgent, but would be nice:
Google Sync working
Tethering WiFi/USB working
Browser with Flash Support working
Camera working (Pictures & Video)
Video working
as much as possible free system memory ;-)
Of course my respect for all developers, you do great work!
I'll try ~ all Imagereleases, but i stay at the moment @The Original Rogers (modification from kb7sqi). I think it's the only one with working complete ActiveSync/BT/WiFi/Sound.

pychobj2001 said:
This should be reset tho every like week or so, cause constant changes happen and one gets crazy awesome over night..so you should have in the title sometimes (I reset this poll on 1/27) so ppl no to see new results...
Click to expand...
Click to collapse
I like your idea, it's good to always update ratings based upon how certain ROMs enhance faster or more frequent than others.

hey javolin i really think u should add jubeh's 2.1 AOSP ROM to the polls, its really something great, best eclair ROM i used to date.

the Intention ROM comes from a mature dev that doesnt act like a child. He also dosent beg for money

Ill be trying kingklick's rom next!

I don't like eclair roms anymore after I tried CSDIv1 lol....everything seems to be slow as a turtle xD

chim4ira312 said:
hey javolin i really think u should add jubeh's 2.1 AOSP ROM to the polls, its really something great, best eclair ROM i used to date.
Click to expand...
Click to collapse
I would like to add different ROMs to the list, I don't think I can edit the poll once it's posted though.

pretty good turnout with the voting... I think these voting ratings will also help devs in a comptetive state as well... Granted there is the "sharing is caring" attitude, but I'm sure nothing feels greater then having a large fan base that supports your rom

[Q] is it possible for android phone to use same builds used in HD2

Dear Friend Thank you for lookinf into my question.
I have an HD2 from sometime now and thanks to the dev's on XDA for android and windows i am able to continue using my phone and liking it everyday
My question is: since i am set that android is better than winmo at least for me and i am using it permanently. If i buy an android phone LIKE Desire HD or Desire, will i be able to change the roms like my touch 4G or any other rom build.
or i will be bound to specific roms and themes for it.
i like to test everything i could and enjoy trying new systems, which i am doing now on my HTC HD2. But even with the stability of android roms nowadays i think the performance will be better if it is a native android phone.
Opinions are mostly appreciated

I'm no expert in either of those phones, but almost every Android phone has a pretty active dev'ing scene. It's not that much effort to switch roms on a native Android phone, but certainly more than with an HD2.
The variety of roms will also be less I think, coming from an HTC magic the abundance of choice here quite shocked me.

You can find the answer to this exciting question, and more, by reading the forums for other phones.

Well i dont suppose .
All the HD2 build out here have custom kernels and other tweaks which have been modified according to its hardware and devices specification.
But you can surely port it to your device. MEaning you will have to modify and tweak the builds accordingly.
I aint sure though

johncmolyneux said:
You can find the answer to this exciting question, and more, by reading the forums for other phones.
Click to expand...
Click to collapse
Thanks for looking into the subject, but, i tried before asking and i could not get the proper answer for it, i found some things that was not clear to me maybe since i am not a user for that specific device. Thats why i asked, so that someone who has enough knowledge about it could help with the info.
Thanks for your effort.

rapaholic999 said:
Well i dont suppose .
All the HD2 build out here have custom kernels and other tweaks which have been modified according to its hardware and devices specification.
But you can surely port it to your device. MEaning you will have to modify and tweak the builds accordingly.
I aint sure though
Click to expand...
Click to collapse
Thanks for the info, i think you might be right about the kernels and required mods. that did shed a little light about the answer.
Thanks again for your effort

nicefellow said:
Thanks for looking into the subject, but, i tried before asking and i could not get the proper answer for it, i found some things that was not clear to me maybe since i am not a user for that specific device. Thats why i asked, so that someone who has enough knowledge about it could help with the info.
Thanks for your effort.
Click to expand...
Click to collapse
Read and ask in these forums...
Desire - http://forum.xda-developers.com/forumdisplay.php?f=594
Desire HD - http://forum.xda-developers.com/forumdisplay.php?f=754
You're asking in the HD2 forum if there are ROMs available for other phones? Sorry, but that's just a waste of everyone's time (yours in particular!) Go to the relevant forums and do lots of reading in them before asking any questions, but ask them in THE RIGHT PLACE.
Oh yeah...
Thanks for your effort.

[Q] Beta-testers needed.

Hi guys,
I am trying to develop ROMs for Android. And I have developed one. This ROM is based on the stock HTC One ROM. Getting straight to the point, I need some Beta-Testers as I don't have the device with me. Sure, I'm gonna buy it soon. But in the meantime, I don't want to waste my precious time. SO< ANYONE INTERESTED? :highfive:
Thanks in advance.

Blind builds like what you did are not encouraged because it magnifies the chances of things to go wrong since you can't test the ROM yourself. Just a not of caution

pandaball said:
Blind builds like what you did are not encouraged because it magnifies the chances of things to go wrong since you can't test the ROM yourself. Just a not of caution
Click to expand...
Click to collapse
yea. I know it is a blind build, but I didn't really do any huge modifications. Just some changes here and there. I have the build ready with me. I just need a guy to tell me surely that this build is safe to work upon further. That's because I am gonna resort to android development in future.

Short of sounding like a D-bag, what you're asking for is a little ridiculous. You sound like you're new to developing, new to the boards (Welcome btw) and don't have the device yourself. Its like asking a random person to test drive a car you just built by reading a "Build-it-yourself Car". If you had more credibility, i.e. More posts, past work, past examples of ROMs or even a list of what was "modified" in this ROM, people might step up to help.

V2IBH2V said:
Hi guys,
I am trying to develop ROMs for Android. And I have developed one. This ROM is based on the stock HTC One ROM. Getting straight to the point, I need some Beta-Testers as I don't have the device with me. Sure, I'm gonna buy it soon. But in the meantime, I don't want to waste my precious time. SO< ANYONE INTERESTED? :highfive:
Thanks in advance.
Click to expand...
Click to collapse
what's so different with your rom and the roms already out ?

ant78 said:
what's so different with your rom and the roms already out ?
Click to expand...
Click to collapse
Everyone's gotta start somewhere, even just doing this is good practice for him.
I'd test for ya op but I rely heavily on this phone and I'm s off. I'd advise any testers to be s on just to be extra safe
Sent from my Tricked out HTC One

Squirrel1620 said:
Everyone's gotta start somewhere, even just doing this is good practice for him.
I'd test for ya op but I rely heavily on this phone and I'm s off. I'd advise any testers to be s on just to be extra safe
Sent from my Tricked out HTC One
Click to expand...
Click to collapse
I do agree you have to start somewhere. But he should get his own device and test it himself. That is better than just creating something that you don't even know it works.
Some "experienced" developers sometimes don't even own the device to create a custom ROM. But the key is that they are already experienced and would know how things work. But for someone who is starting out and have very little experience, they are better off doing the tesing themselves.

I bet he is not really a dev but more like a zip dev if you know what I mean.

OP.. please understand. Your new here, you have no proven track record, your asking people to entrust a €600 device to something that you have 1. not clearly laid out in your opening post 2. have no means to test yourself 3. can not provide support if you feck up other peoples devices.
Sorry but without any past experience here your trust level is 0.
Your request is akin to a nigerian ringing me and telling me I've won a multi-million € win and all they need is my bank account, and credit card info....
At least stick around here, get the device yourself, build up your reputation, and try a few things yourself and then clearly lay out what you have done in any further thread requesting testers because blind faith only goes so far......... unless you are indeed Jesus (or a nigerian with my mulit-million pound win)...

Wow.. so we can't waste his precious time. Lol
Sent from my HTC One using Tapatalk 2

Hey hey hey! Please don't classify me as a ZIP dev..!
N yeah. Here's the change-log of my ROM(though it's not much):
1. Rooted
2. Busy-box added.
3. Changed the boot-animation a bit.
4. changed the power down animation a bit.
And' thats all.

V2IBH2V said:
Hey hey hey! Please don't classify me as a ZIP dev..!
N yeah. Here's the change-log of my ROM(though it's not much):
1. Rooted
2. Busy-box added.
3. Changed the boot-animation a bit.
4. changed the power down animation a bit.
And' thats all.
Click to expand...
Click to collapse
I think everyone has to start somewhere, but I think the people are looking at stuff like what did you change in functionality not just cosmetics. Try playing around with build prop and stuff
Sent from my HTC One using xda premium

Android The Greek said:
I think everyone has to start somewhere, but I think the people are looking at stuff like what did you change in functionality not just cosmetics. Try playing around with build prop and stuff
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Yeah, sure. I would work on this ROM further. But somebody has to test this adolescent ROM first, because it could happen that I work upon this ROM without testing it and then it would happen that it won't work. And then I could have to roll-back, only to start from scratch.
And that is why I'm asking you guys to test this out. I guarantee regular updates, fixes, etc.