yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy SL i9003] supergaijin:
I'm not voting due to limited selection, but here's my input:

10 developers working on 10 different ROMS is good, as mentioned before, because 1) since there IS some info sharing between all developers, things ARE improving, as was previously stated, and 2) more developers creating their own things helps give those people that want to run these ROMs more selections to choose from.

that said, I also agree that having all working on one ROM is also good, because it would be most stable, but also as mentioned before, final stability is based on original, base ROM/kernel, and coordinating specific tasks between developers that don't operate at the same time of day is quite complicated and slows things down a bit, as seen on some games I play online that have global teams developing scripts for them.

I don't expect this to happen immediately, but one thing that would help people out, if possible, would be to code things to make them interchangeable, so you're not stuck with a certain theme that's missing something from another theme that you like.

for example: have a theme coded so that any background can be chosen without modifying a file, change the notification bar without modifying a file, choose which icons will go on the notification bar without modifying a file, etc.
[Samsung Galaxy SL i9003] blaqkarma:
I ageed with Falex.... ROM developement Individually is just like sharing your Idea to all of us here.. Like my self I only do my ROM on my free time and thinkin what possibilities could make the ROM better, Learning from each other is a better why of developement.Theres no compitition against the dev's here.Even dev's ask each other for what solutions to make things happen. Workin with a solitary ROM is a bit difficult cause everybody has their own idea.. and I think many would like to have choices of their own liking..

But we understood what you want to say,but you think that a 1SUPER ROM would be build by dev's that are miles and miles apart with their own Personal life?..If that happen maybe we are looking for a longwait for having one...

Sharing what we could offer to SGSL user.I think is a good way of a forum should have...
[Samsung Galaxy SL i9003] ferap:
Is better to have 10 different flavors of an ice-cream than 1 ice-cream with all the flavors on it
[Samsung Galaxy SL i9003] anigr88:
Working in any kernel we need all dev to work on it but when it comes to custom roms let them hav the freedom to make it lavish their way and if they want to cooperate and work together its there own wish we can't force anyone ;-).
[Samsung Galaxy SL i9003] PondaRox:
you speak the truth! :D

on a really basic level, i suppose the OP is right - two heads are better than one. as far as i've seen, though, XDA (or maybe just the i9003 section) is a pretty tightly knit community; it actually feels like a family. the devs ARE helping each other when need be, and we help them by reporting bugs and such, but i think each one should be allowed to do his own thing. i've tried Gitaxian and Cranium ROMs so far, and i don't know how much more stable you want these ROMs to be (then again, i've been lucky in that i don't have the push notification problem and the GPS hasn't ever been an issue for me)

as for USB OTG and TV-out, they were working OTG together (in fact, they still are, but i don't have a lot of interest in it so i'm not following its development). you can't just put features like those in a custom ROM, it needs to be part of the base ROM. either wait until the devs can figure it out or Samsung makes them features of stock ROMs
[Samsung Galaxy SL i9003] sgsI9003:
I wish that happens soon, on checking amit's thread I get to know that he has released the code along with RC1 which no one can boot successfully after installation. Common guys be mature, RC (release candidate)should come after alpha release & beta release, why directly jump with labeling it as RC1 when no one in public has tested it & no one is able to boot.

This is exactly 1 of the problem I want to be sorted out,there should be some streamlined ways to name the rom as RC1, we need some "better" self governance & cohesiveness in rom development. I have been testing alpha & beta releases of many software both with large corporation as well single person developer,at alpha/beta stage we offer & they integrate the features, only then RC 1 comes.

Once the devs team up & identify the core requirements on which features to be build we can approach kernal developers or someone within the team can look into possibilities of making custom i9003 kernal (Amit himself can be approached)
[Samsung Galaxy SL i9003] sgsI9003:
Right analagy wrongly described.

I see rom development excatly happening like 9 women trying to give birth to a child within a month thus having miscarriage & that's excatly I am disagreeing with. I will say let 1 women conceive 1st properly then let other women help that women to give birth to a healthy child (stable rom)

No women can ever conceive alone, bear the 9 months alone, & give birth to a child alone, at "all stages" she would need different help to deliver a healthy child. The most crucial is the final birth where she needs 5-7 different specelist to help not only the women but also the new born baby.

In no way my opinion is binding & I respect your choice of having several devs doing several roms. My concern is that by teh time if "ever" we have stable & fully featured rom many i9003 users may migrate to another phone due to lack of stable roms. I myself am thinking of changing my i9003 but will wait till this year end atleast.

Joomla a sucessful CMS platform had excatly thesame problemin initial days & the devs decided to change that & toady you see a great product as Joomla. This is just 1 example I am citing as I was involved in making required feature list for joomla which wasthen discussed among devs & they selected few of v1, few hard to code for v1.5, some needed the change for base code those were left for v2.

I am sure same can be implemented by i9003 devs if they see the results of the poll & agree to it, after all its the i9003 users who will use their roms.

No user...........then no use of their roms only they will use it for themselves.

Respect to all the developers for their time & effort, in no way my view are binding but I am just sharing my views & experience with community development.
[Samsung Galaxy SL i9003] sgsI9003:
That's a good suggestion & I would want the theme to be inter changeable, not sure if this can be done or there may be few issues preventing them from doing so
[Samsung Galaxy SL i9003] sgsI9003:
So what I suggest is that devs identify the core skills of each of them & then distribute the task for development of specific features that will speed up stable rom development.

Sure devs are free to work as they wish this thread is more for seeking opinion from i9003 users & the voting is clear majority is in favor of devs working together for stable rom
[Samsung Galaxy SL i9003] sgsI9003:
Calling all Rom developers

http://xdaforums.com/showpost.php?p=18166267&postcount=283
[Samsung Galaxy SL i9003] longfeng:
I know where you are coming from but if everyone is focusing on only one ROM, there is no options and friendly competition.

Even Samsung stock ROM is not super stable.

If you want someone to blame if the ROM fails, stick to stock ROM and blame Samsung.
[Samsung Galaxy SL i9003] sgsI9003:
23.38% votes for different developers develop different roms

76.62% votes for Devs should work together to make super stable rom

So the writing on the wall is clear we need devs to work together on project though they are free to work on their own too but i9003 users want & have voted for team work.
[Samsung Galaxy SL i9003] Misledz:
What your vote says and what you request is something you may not get.

- Different time zones

- Different level's of expectancy

- Collaboration won't be easy especially with different POV's each dev want's/has

- Ever heard of too many cooks spoil the brew?

If you wish to get something done, you need to meet atleast the basic requirement's, the member's. These member's cant be physically present and uploading/reuploading of 180MB constantly won't be happening. Plus the time spent to gather everyone < People finding new stuff/improvements. Also this isn't about competition, because in the end, EVERY ROM has EVERY similar feature that has been put out. Someone post's a init.d or a 14 status bar mod, and in less than an a day, everyone's custom ROM will wan't this done to not be left out of the competition, consumer's will demand the same equality so they may enjoy similar benefits or else they would shift to other options. Weather you make a single collaboration or a jungle of ROM's, there will always be 95% similarities, chances are, just the name will change, because in the end, every dev will make use of every other dev's work to make their's better, which in turn makes every ROM similar.

Sorry if this sounds rude, but this isn't happening or going anywhere. The request is another dust in the wind.
[Samsung Galaxy SL i9003] vishal24387:
@ sgs I9003

just wait for days. You will get ur super stable rom in form of CM7. Now official cyanogen team is working for us.
[Samsung Galaxy SL i9003] matapollos:
hi there!

i prefer having a great amount of different roms, where you can choose what to flash, rather than a perfect one... each and every rom is created because the developer wants this or that style and features in his or her work. Then they decide on their own to share it with us or not. We should be thankful to them ;)

Anyway, it's true that they can at least try other roms and help in the development reporting issues and giving advice!

it's my own personal opinion, so hope this doesn't bother anyone :P

cheers!

PS: and you forgot about cm7, guys!! it will be stable for sure!
[Samsung Galaxy SL i9003] sgsI9003:
I don't know much about CM7 but I am eager to see it being developed, finally the wish of community development coming true, hope other developers can come forward too to work on various features to be incorporated in CM7 rom.

Here is my latest feature list

http://xdaforums.com/showpost.php?p=18655187&postcount=14
[Samsung Galaxy SL i9003] sgsI9003:
21.11% votes for different developers develop different roms

78.89% votes for Devs should work together to make super stable rom

So the writing on the wall is further favoring for the stability extended feature list.

The good thing is that now many developers are developing individual features which can be integrated in to various rom giving freedom to user.

Good start I would say, i9003 sure has a future in spite of many missing features.
[Samsung Galaxy SL i9003] fxzy:
I think if there are suddenly so many firmware appeared. I think we should choose one of them for us to develop. Just focus on one firmware just like we choose xxkb3 in the past. I think we should compare these firmwares, xxkpm xxkpn zckp9 dxkp9 pokp3 etc I can't remember.

I suggest dxkp9. As this ia south Asian firmware, we have many developers from India.
[Samsung Galaxy SL i9003] fxzy:
Really no one appreciate my idea ?
[Samsung Galaxy SL i9003] supergaijin:
I appreciate it, but I can't just test a bunch of stuff all the time. my phone is needed for work ;)

and don't forget, you're posting at a time before the Indians wake up :p
[Samsung Galaxy SL i9003] sgsI9003:
I not only support this idea but 80% users have voted that developers work on the rom collectively so we can have 1 super stable GB rom on which we can have as many variation developer wants.

After all even with so many of roms we have the same mods being integrated, only teh color/icon theme is different.
[Samsung Galaxy SL i9003] sakindia123:
i chuckled when i saw that difference b/w the time in the last 2 posts
[Samsung Galaxy SL i9003] fxzy:
Without any election, the ultimate firmware until now is already appeared. XXKPQ....
[Samsung Galaxy SL i9003] sgsI9003:
80.56% want Devs should work together to make super stable rom (Its almost happening now with many universal kernal)

bumping an old thread which is still relevant for getting stability in 9003 roms.
[Samsung Galaxy SL i9003] bscraze:
There are so many stable roms, pick from them.
[Samsung Galaxy SL i9003] emptyragnarok:
I think we all should learn development and start working on 3.0 Kernel.. we can finish it then :)
[Samsung Galaxy SL i9003] vishal24387:
I think developers should work on ddlf2. Its most stable rom for develipment. It still doesnt have 10 lockscreen mod & famous ICS theme (which is avilable for kpq). Also we should work on more lockscreens.
[Samsung Galaxy SL i9003] crk1995:
I m really missing some good themes for stock roms.
[HTC Incredible S] Blaaargh:
Will official OTA updates work on my rooted IncS? Also, before I rooted my phone, I took a backup with CWM. If I restore to that backup, will the root be undone?

Final dumb question of the day, Can I unroot and set S-ON to my phone again? If needed?
[Xperia Play Themes and Apps] Dyelon:
Anyone with an r800x have any luck getting this to actually work?

No matter what I do I constantly get the error about "null permissions" or whatever...even though BEFORE I even installed the apk I checked all the permissions and such and moved it to system apps (actually I moved it first)...

not sure what else to try
[Windows Phone 7 Software Development] shax:
This is port of Enigma Signal Meter to Windows Phone 7 devices.

Description:

Fast, small, simple and free application for Enigma 1 / Enigma 2 satellite receivers, build to help you align you satellite dish to perfection. Please, keep in mind that this application is still HIGHLY UNTESTED AND BETA. Since i don’t have actual Phone 7 device i was not able to test it properly. Use on your own responsibility. Also, please report any bugs found.

Features:

SUPPORTS ALL currently existing Enigma1 and Enigma2 receivers and images

same simple interface used for Enigma1 and Enigma2 boxes (originally they are quite different)

full background processing (running tasks will not hang application)

works remotely (just forward web port and you can connect from anywhere)

Requirements:

jailbraked phone so you can install custom XAP files

Enigma 1 or Enigma 2 based satellite receivers with running Web interface (WebIf)

Network connection between receiver and computer

Windows Phone 7 or newer

1 MB of free disk space

List of receivers it was tested and working on:

- DM500

- DM500HD

- DM600

- DM7000

- DM7020

- DM7025

- DM800

- DM800SE

- DM8000

- VU+ Uno

- VU+ Duo

- AzBox Premium

- AzBox HD Elite

- AzBox Ultra HD

- Kathrein UFS 910

- IPBox 9000

- Amiko Alien

- Topfield TF 7700HD PVR

- Gigablue solo

- ClarkeTech ET9000

For best results when searching (faster response time):

- don’t search while zapped on HD channels

- don’t search while recording

- don’t search while receiver’s web interface is open in web browser

- don’t search if you have other plugins running

- generally avoid anything that slows down your receiver

DOWNLOAD

Consider donating to support my work
[Windows Phone 7 Software Development] dxdy:
nice :) krkadoni rules :)
[Windows Phone 7 Software Development] dxdy:
not working since update ROM to 7740 (Pdaimatejam Rom Wp7.5 mango 7740 v3)

Error

"Failed to open box request! The remote server returned a error. NotFound."

did anyone can test on 7740 if have E1 or E2 satellite receiver?
[Windows Phone 7 Software Development] 1milenia:
will it work on tmobile hd7
[Windows Phone 7 Software Development] 1milenia:
tried it on my hd7 7740 error pops up

does not work
[Windows Phone 7 Software Development] dxdy:
which satellite box you have?

working... found sollution.... problem is in channel list... after loading new Vento E2 channel list, ESM working again...

here is latest (06. dec) Vento E2 channel list https://rapidshare.com/files/619694541/lista.zip

here is fresh screenshot
[Windows Phone 7 Software Development] 1milenia:
how do install the new version dec 6
[Windows Phone 7 Software Development] dxdy:
this is channel list for Dreambox (not for phone)

you need settings editor (Dreamboxedit or Dreamset)
[Nook Color Q&A, Help & Troubleshooting] calixt0:
Ok My wife bought me a nook color and I'd like to make it into a tablet. I found a video on youtube that has it running cm7 on a micro SD card but then then runs the stock NC software so as to not void the warranty.

I've tried reading the nook devs, and multiple how to's but feel a bit lost. Can someone point me to

1) step by step instructions even an idiot can follow

2) a link to the different mods and how they are different

3) where these mods are found.

I'd like a way to do this using free software. One place i found to just buy the mod on an SD card and just install it. One other place gave some instruction but needed software that had to be bought (unzippers or something along that line).

thanks for any information I'm feeling a bit overwhelmed..

Shaun
[Nook Color Q&A, Help & Troubleshooting] kgptzac:
I started my NC journey by reading some good, but outdated, guide on how to do root and flash custom ROM to the NC. It took me some time to find the correct program to use.

manualnooter: http://xdaforums.com/showthread.php?t=1054027

This post has a rather detailed instruction. Note that you will be installing a custom ROM onto NC and will void warranty... but you can also flash the stock ROM back to the NC in case you need to use that warranty so you don't really lose much.

I forgot which ROM the manualnooter procedure would install, but I think the current most popular and stable ROM is cyanogenmod 7.

Unfortunately the entire procedure will take beginners more than 10 hours to have a grasp on how to do things and maybe poking around and see why some things work that way.
[Nook Color Q&A, Help & Troubleshooting] ponyboy82:
Welcome!

I've personally installed CM7 to emmc (internal memory) using these steps:

http://xdaforums.com/showpost.php?p=11452450&postcount=19

I was also using the microSD card method, and the steps below are good to follow:

http://xdaforums.com/showthread.php?t=1000957

I would recommend using the latest nightly vs a labeled "stable" release. The nightlies have a lot of improvements and are in fact very stable these days. The only thing you'll need is a microSD card, a card reader, and a little bit of patience. It's really not hard, but just make sure to follow all of the steps. If you have any more questions, feel free to ask or search previous threads
[Nook Color Q&A, Help & Troubleshooting] calixt0:
I was considering a nightly build.. the nightly builds I need to find the encore build right? (wonder why we call these units encore). Secondly I was wondering if theres an option out there that allows a plain version of gingerbread without the cm7 markation all over the place. Is there functionality in the CM7 builds that I wouldn't get with a pure gingerbread build?
[Nook Color Q&A, Help & Troubleshooting] ponyboy82:
Yeah - encore is the codename for the Nook Color. I think it came from the initials NC....encore. You can always find them at

http://download.cyanogenmod.com/?device=encore

I'm actually not sure if there is a pure gingerbread rom out there. CM7 is based on the official release of GB, and adds some nice things for the nook -- one big one is the honeycomb style soft keys at the bottom since the NC doesn't have the normal android hardware keys.
[Nook Color Q&A, Help & Troubleshooting] votinh:
For newbie, I strongly recommend installing and running CM7 off the uSD first.

Play with it for a while, get used to it, familiar with it while spending more time reading threads/posts in here then thinking about switching it to eMMC or rooted NC later.

Installing and running off uSD are much more simple and easier.

The requirement is: a good (SanDisk class 4 reported as very good) uSD, 8GB or 16GB.

Then follow this: http://xdaforums.com/showthread.php?t=1000957
[Nook Color Q&A, Help & Troubleshooting] dargocitfer:
Cyanogen has this quirky little tradition of naming the software release after the original code name of the device. The Nook Color was code named "Project Encore" (http://www.droiddog.com/android-blog/2010/10/nook-color-likely-dropping-this-week-image-leaked/) by the developers, so the NC is the Encore in CM7. (Similarly, my old Motorola Cliq is called "Morrison" and my T-Mobile G2 is called "Vision")

And Stock Gingerbread doesn't have a number of things which are very useful for Tablets, such as the taskbar "soft buttons" for back, search, home, and menu, as well as the ability to put the taskbar on the bottom, and adjust the lock screen as you see fit. CM7 has all of these, plus the ever popular "much, much more!" The CM7 developers and mods have really outdone themselves and made the Nook Color a massively useful device.
[Nook Color Q&A, Help & Troubleshooting] Aerlock:
+1 This.

Follow the instructions in that link and you should have a working microSD CM7 installation. 3 things to add to those instructions though:

1.) Try using Win32DiskImager instead of WinImage. People have had problems writing the image with WinImage. The only problem I've seen reported with Win32DiskImager is that sometimes you cannot create a good usable image of a disk greater than 4GB.

2.) If you are looking for a good usable card, get this one. It includes a good USB microSD reader to use when writing the image.

3.) This one is optional. The default SD card image writes an approximately 120MB boot partition to the microSD. With the latest nightly releases of CM7 you can run into issues if you are trying to install both CM7 and gapps at the same time. It is recommended to resize the initial partition upwards in size. Some folks put it over a GB but in my mind a few hundred MB should be fine. The most popular tool to do this with is EASUS Partition Master. I haven't personally done this since it is something that has to be done before the initial install and I had mine up and running before running into this problem.

- Aerlock
[Nook Color Q&A, Help & Troubleshooting] calixt0:
oI bought a microSD from merit line. Its an ADATA BRAND 16GB CLASS 10. it had good reviews and some places I read to stay with above a class 6 or better. I hope this doesn't cause a problem or my wife will be upset... LOL

I was watching a video on youtube about this process and they mentioned not having all the memory on the microSD available due to the partitions. they used the same partition manager to maximize the storage on the card. Will this be needed or does something happen automatically to use make all the uSD card usable?
[Nook Color Q&A, Help & Troubleshooting] votinh:
With that brand, with that speed, keep all of your fingers crossed and prayed.

And after few weeks of enjoy the CM7, if you start seeing weird things, you then can start blaming the uSD.
[Nook Color Q&A, Help & Troubleshooting] calixt0:
does it matter what version software i start with? I've been reading around and see everything from making sure that your on 1.0.1 to 1.3? I'm lost?

Also since I'm wanting to do this all on the MicroSD then this may not be an issue but I've heard some say also to log on first and make sure I sign in with barnes and noble before doing anything. is that important or not?

Lastly. does rooting or anything leave a permanent record in turn voiding warranty or can it be taken back so the factory doesn't know.
[Nook Color Q&A, Help & Troubleshooting] joej:
Rooting does not leave any records. All you need is to return to factory stock before sending in for warranty
[Nook Color Q&A, Help & Troubleshooting] calixt0:
ok I've tried the version 1.3 over and over and each time I get the same problem. after reboot it comes to the blue android on a skateboard it it just keeps running in circles. it will go black occasionally but then right back to the android on the skate board.. what might I have done wrong?

I used the installer in verygreens 1.3 posts and cm_encore_full-209 nightly build