yashsingh1/xdaforums huggingface dataset:
[XPERIA X10 Android Development] saltorio:
My (limited) understanding is that since the bootloader is still locked, they are developing these custom ROMs on the existing 2.1 kernel that SE has put out for the X10. That means that certain core components are Android 2.1, and can't be replaced without bootloader access.

As such, it makes sense that the further an OS version is from 2.1, the more likely it is that it will require specific features not available in the 2.1 kernel.

So developing stock 2.1 for the X10 would be easiest, 2.2 would be more difficult, 2.3 even moreso, and so on.
[XPERIA X10 Android Development] nidalius:
maybe its true but developing 2.1 AOSP or 2.1 with sense take a ot of time and confir the stupid idea from SE Eclair 2.1 plus SE soft is better than Froyo ,

Creating a team will reduce time of developement and may be improve the quality of the rom build , my idea it just to say that and unify the X10 community in supporting one effective project thant wasting a lot of creativity & effort in incomplete work its easy to say the difficulty is to DOING the Job
[XPERIA X10 Android Development] nekkidtruth:
Just a little bit of insight here from someone who isn't a developer of ROMS....

I agree that combining their efforts would most likely give us better results with regards to hardware. Here's what I think may be happening. Now that they're able to create functioning ROMs, they're each taking the time to hammer out their skills. When you learn something new, you generally spend your time redoing the same thing over and over until you've got it down pat.

That being said, they're each learning more and more as they attempt new ROMs. I think once the fascination of "Hey I got a working port of *this* ROM first!" wears off, maybe they'll work together to create a fully functioning ROM. Who knows, one of them may actually sit still for a moment and finish up one of their own ROMs.

I hope that all of the developers working on different ROMs at the very least keep a line of communication open between them so as to share fixes and work arounds.
[XPERIA X10 Android Development] Astral07:
speaking of GB :)

http://xdaforums.com/showthread.php?t=911364
[XPERIA X10 Android Development] kan827:
Yes! I Agree With You!!!!
[XPERIA X10 Android Development] mezo9090:
+1

I love all the dev here, but i too just don't get it..

either i get a working camera or working wifi ? Come ON...

i hope you guys see this posts as friendly talk, we are so lucky that we have all of you here :) you all understand the need of one functional AOSP Rom 2.2, 2.3 whatever :D
[XPERIA X10 Android Development] jac0b:
I feel the same way maybe the devs should team up and create a monster ROM that works.
[XPERIA X10 Android Development] synn21588:
I agree. It's been proven time and time again, teams work better than individuals. Please unite Devs! Think of what could be accomplished :)
[XPERIA X10 Android Development] robbyf66:
I havn't even tested a ROM yet since their all incomplete, simple as that.
[XPERIA X10 Android Development] WildBit:
All the different ideas and "wishes" posted on this thread are of course appealing but until the bootloader is cracked it's practically impossible to have a fully working ROM on any other version other than the 2.1, at least from a short term perspective.
[XPERIA X10 Android Development] Kingcool88:
Correct me if im wrong, but from my understanding they started to work with 2.1 just to make it simpler to mod the code to 2.2 later.

The reason is that SE have released some code for 2.1, but of course not for 2.2. So they used SEs 2.1 code to develop the 2.1 AOSP rom. And could therefore much easier convert the code to 2.2.
[XPERIA X10 Android Development] will.m:
It seems like you guys haven't been paying attention to dev work for the x10. Maybe it's because you didn't lurk the sub-forum since the beginning or maybe you don't understand what the devs are actually doing.

The devs ARE working together. jerpelea, zdzidu, bin4ry, goro-kun, maxfron, and many others DO communicate.

What one person said about having 2.2+ functions are strictly related to the kernal and bootloaders is the final word. Sony implemented special drivers for the camera and video decoding.

Until someone writes the drivers from scratch AND unlock the bootloader, we will have less than 100% functioning 2.2+ roms.
[XPERIA X10 Android Development] hemo1001:
on that 2.3.1 HTC rom camera is working ... if they can get the BT and Wifi working it will be awesome . but i have a question . will we get the (MT) on these roms after SE release? i mean for 2.2 and 2.3
[XPERIA X10 Android Development] tuxStyle:
Yep.

Me neither.

And only because the camera and HD are not working :o
[XPERIA X10 Android Development] kokbiel:
The htc rom mentioned by you is 2.1. That thread is for 2 roms. 2.1 htc and gingerbread. So no, camera is not working on 2.2+ yet. Z got some progress making the camera atleast respond, but so far, if he implements full camera function, he looses other key functions in the rom. Not a good trade.

Sent from my x10 running 2.2
[XPERIA X10 Android Development] K12boi:
No pressrue on the devs and they can do what they please with their work. But as other have said it sounds like a great idea. Any devs care to comment on this idea?
[XPERIA X10 Android Development] CoopZor:
Will we ever be able to crack the bootloader ?

Sony is an expert at securing their stuff, look haw long it took to crack the PS3 !

Anyone with more knowledge that can say something about it ?
[XPERIA X10 Android Development] kloud_:
Hello there fellow x10 user

Its something simple... u learn to walk before u start running. The same is the case here. Developing an ASOP2. 1 help z & j to developed the Rom they are offering now and with each passing day these ROMs get better and better.

Synergy: that is something better answered by the devs themselves.

Thankful to the wonderful work being done by the devs here. Thanks a lot guys

Regards

kLouD
[XPERIA X10 Android Development] kloud_:
If you were following the bootloader cracking dev thread then u'd know that it is pretty hard for anyone to actually predict the time to crack the bootloader[may take a few days to weeks to years or in worst case scenario forever: ( ]. So all I can say is have a l'il faith and who knows we might one day see that happen sooner than later. ;)

Regards

kLouD
[XPERIA X10 Android Development] DarkX10i:
I agree, obviously we would all like 2.3, but as the bootloader has not yet been cracked, and SE havent passed on the code yet, we can only use what we have.. im sure we will get 2.3 eventually, whether the bootloader is cracked or Dev's are given the code, but until then, we just keep with the ROM's we are being given, and give full support to the Dev's for giving us these ROM's..

but yeah, it would be great to see all the Dev's come together to work on a solo project, but would like to say that you are all doing a great job with your ROM's now, keep up the good work!
[XPERIA X10 Android Development] violentgoomba:
While I like the idea of having 'one rom to rule them all' ala Cyanogen team, it's not that simple. I recognize that our devs have a common goal--they want to get a fully working rom out, but they also have different lives. Their development habits vary, I'm sure and it's hard to synchronize that when you're working with people halfway across the world. Unless of course they're doing this full time then that would guarantee steady progress as one dev can take over after another dev's shift is done.

Also, the devs will have to break it down into different specializations if they ever decide to work on one ultimate rom, and at this point, I think the devs need this alone time to understand the ins and outs of Android rom development. Because it's easier when you're working at your own pace.

MAYBE one day when we have fully working roms from each dev, they can combine their tweaks and tricks and come out with a 'one rom to rule them all' rom.

My two cents. It's a great idea, but I'm just trying to imagine how a dev would feel about something like this. I may be totally wrong of course :P
[XPERIA X10 Android Development] vengeance1990:
In regards to what has been said about the bootloader, Sony are experts at securing there stuff however, there are alot more people who own a PS3 than an X10, so although it took ages to hack, it was possible (i say was because as soon as it got release to the public sony jumped on it and patched it out)

Hopefully the devs here can crack it.

Im sure the devs do communicate although with so many different roms about, its hard to concentrate on just one, personally i would like the HTC rom for my phone but its very early beta by the looks of things and Jerpelea has many other roms to work on

but yeah i think they should team up share there resources and show sony how its done

regards
[XPERIA X10 Android Development] andd2010:
+1

i would also be uptodate and have the latest android :rolleyes: and only XDA-Devs can make it real to have it done for our X10s, before the others update officially and even before all the new smartphones with allready 2.3 come. It is not good for the mobilephone factorys, couse we would use "old" phones instead of buying the "new" ones with almost the same hardware. But for all us it is money saving and getting more functionality and more fun with our phones.:cool:

come on Devs, you will do that fine, we know, just listen to us and concentrate on Android 2.3. And in the future always an the newest OS.
[XPERIA X10 Android Development] ttf:
You want to see the bootloader cracked?, simple : just open a thread like this

"Bootloader X10, 200$ for the first able to crack it", wait a week and you're done ^^.
[XPERIA X10 Android Development] k1sr:
You are obviously new to XDA, also evident due to your current post count of 20.
[XPERIA X10 Android Development] ttf:
I'm around almost since XDA is online, many many years ago, but i post only when needed.
[XPERIA X10 Android Development] nidalius:
hehe the challenge for the root was more than 1000$ and we wait more than 2 months for that : Binary is the first hwo provide a solution ,

bootloader is more harder nothing is impossible i cross my finger Devs do their max for that

another point i realy appreciate the good job of devs but i am just thinking that focus in one OS could be profitable for everyone but the dev team need time to know how its work

now i enjoy the freeX10 beta4 and i regret the lack of communication & the misunderstood between zdizhu & trip : Zdizhu give us the light and Trip was able to give as camcorder i believe in U Z :)
[XPERIA X10 Android Development] k1sr:
Sure, it would be great if all the devs started working on a collaborative ROM together (similar to how they're working on cracking the bootloader); however, just like you and me, all the devs like different things, and concentrate on what they see as important, which is (of course) 100% acceptable (no one has the right to whine about what a dev hasn't done)

If you really want your dream to come true, actually start a collaborative project yourself instead of sitting here starting a thread about how it would be a nice idea - that alone isn't going to get you anywhere.

You don't need skills as a dev to do that... Set a target for donations, PM each dev and personally invite them to your project. Mange it, and don't just sit there waiting, asking why it hasn't happened yet.
[XPERIA X10 Android Development] nidalius:
you avatar represent u ;) you go directly to the point , my opinion Only Dev can lead a team , but if you want , lead the project we will support it
[XPERIA X10 Android Development] k1sr:
:) have thought about it, but I'm pretty happy with what we've got...
[Galaxy S I9000 Q&A, Help & Troubleshooting] tilallr1:
What are you using for Voice Dialing on the Galaxy S?

Here is what I want to do ...

(1) Press my bluetooth hands-free button to start up the voice dialer

(2) Phone should ask me to say a command.

(3) I tell it to "Call So and So"

(4) Phone confirms name with me

(5) I say "yes" or "no"

(6) And bingo bongo it dials the number for me.

So you notice there is no touching of the phone ... this is a must ... since where I live its illegal to do.

So far I see there are 3 programs that do voice dialing:

(1) Google Voice Command

(2) Vlingo

(3) Choice Dialer Plus

I have tried them all, but none seem to work right or do all the steps above. Any tips on getting this to work and which app is best on this phone?
[Galaxy S I9000 Q&A, Help & Troubleshooting] cyberz:
Have you tryed Cyberon Voice Commander?

I not have it, but on the net I have read which work well.

Have a good day!
[Galaxy S I9000 Q&A, Help & Troubleshooting] Hazurr:
Really....
[Galaxy S I9000 Q&A, Help & Troubleshooting] dandon_:
Hi,

I use Cyberon Voice Dialer (in spanish). It works perfectly with call control button on my Parrot hands-free, and exactly how you want it.
[Galaxy S I9000 Q&A, Help & Troubleshooting] tilallr1:
Great ... I will give it a try and see how it goes.
[Droid X General] spacecasespiff:
When I turn it on in the morning it goes into recovery mode I then select the reboot and it boots up and I'm good. I turn it off at night and charge it then when I turn it on again its in recovery mode. I was rooted and had bootstrapper but I do not have bootstrapper any more but still rooted. I deleted every file and everything that was related with bootstrapper. Please help me and I'm a noob at some of this stuff.
[Droid X General] SysAdmin-X:
Most will tell u this is a blessing z better to always boot into recovery than to ppotentially not boot at all one day. If you TRULY want to remove bootstrap completely, google "completely remove droid X bootstrap"

The process involves renaming a logwrapper file that bootstrap had renamed, and deleting the one created by bootstrap
[Droid X General] spacecasespiff:
I agree that its not a problem but still don't want it. Can you please tell me how to do what you said. I have no clue in how to do that. As simlp as possible please and thank you
[Droid X General] SysAdmin-X:
Ok... Here goes:

1) connect your phone to ur pc in charge only mode. Makr sure it is recognized by adb

A) open command prompt and type "adb devices" (hit enter, your phone should show up)

2) in the command prompt, type "adb shell" (press enter)

3) type "su" (press enter)

4) type "mount -o rw, remount /dev/block/mtdblock4 /system" (press enter)

5) type "cp /system/bin/logwrapper.bin /system/bin/logwrapper"(press enter)

6) type "adb reboot" (press enter)

Bootstrap should now be completely removed.

Note: all text in quotes is just what you should type...do not include the quotation marks when entering commands.

Disclaimer: I take no reaponsibility if you mess up your phone. Typing these commands incorrectly CAN mess up your phone. By following thesr directions, you do so at your own risk.
[Droid X General] spacecasespiff:
One question about adb you said it will recognize it. Is it on my phone or is it something that I need to installed. That's the only thing I'm a little confused on everything else I'm good on.
[Droid X General] SysAdmin-X:
Adb is the driver interface between your computer and your phone. You will need the latest motorola drivers installed on ur computer. Adb is on your computer
[Droid X General] spacecasespiff:
Sorry for the stupid questions but is adb going to pop up on my computer when I plug my phone in or is it something im going to need to find. Again thank you.
[Droid X General] SysAdmin-X:
Here is a way to tell if you have adb drivers installed.

1) plug in your phone via usb to your computer.

2) open a command prompt. Type "adb devices" and press enter. (you don't need the quotes)

If it returns text that looks like " device 05842688788" adb is working correctly. The random numbers will be unique to your phone.
[Droid X General] Funnyface19:
actually if this continues and you have koush's droid x bootstrapper open it and click the first option and give it superuser permission and it should stop
[Droid X General] spacecasespiff:
ok i pluged in my phone and put it on charge mode now I clicked on the start botton on my computer brought up the search bar and typed in command prompt. Is that correct. I then entered adb devices and i said it was not reconized as and external device. now im not sure if that is what i was sopposed to do. I think i was expecting something to just pop up. This is the only thing that i dont know how to find. You say its on my computer but where do i find it.
[Droid X General] Funnyface19:
some people who dont know what theyre doing in the first place shouldn't start....smh just saying
[Droid X General] SysAdmin-X:
Eh... Yes and no. he wants to learb, and we all had to start somewhere.

Spacecase:

You need to download and install the android sdk. Google this and post back when you have it installed =)
[Droid X General] spacecasespiff:
So how am I going to learn how to do something if I don't start some where I just don't wake up and go " I know how to do it" no one told me about the sdk and now I know thank you. It will be tomorrow before I do any more.
[Droid X General] spacecasespiff:
I downloaded the ask and have no clue inn how to use it. I click on the ask within the file it then brings up a black menu then wants me to download all sorts of stuff. The black box is where I type in the stuff but it wont let me type anything. Is this the only way to fix my problem
[Droid X General] SysAdmin-X:
Space,

I will need some time to try and put together some steps for you.

My suggestion would be to be careful with modding your phone. I feel like you may be in a little over your head. I do not say this to belittle you, but merely out of concern. I don't want to see ur phone break on you, and you not have the means to fix it yourself, that is all.

I am glad you have a desire to learn what you want to, but be careful, as these tools can also cause more harm than good. I will try and get you some info to set you straight!
[Droid X General] spaceman4:
Can't you just use root explorer to delete the hijack file and modified logwrapper, then rename logwrapper.bin to logwrapper? Instead of using all the sdk stuff?
[Droid X General] SysAdmin-X:
Yes! If you've purchased root explorer.... So kinda has a caveat there! But definitely a recommended program if you know what you are doing with root privileges...
[Droid X General] SysAdmin-X:
Just posting a few files for a tutorial I am typing up to come later...
[Droid X General] spacecasespiff:
I know I was over my head a little and did my home work about how to fix any problems that I may encountered but didn't think that I would need to use adb. I know how far I can go and be ok now. I greatly appreciate what you are doing for me. I will get back on my computer when im done at work. I seem to have the right file downloaded so im good there. I will let you know how it goes. Again thank you. Im done messing with my phone and I find out that it runs great and is quick even with no roms or tweeks. Best phone I've owned.
[Droid X General] spacecasespiff:
Ok I have root explorer I wont tell you how I got it but it's on my phone. If its easier using that I would like to try.
[Droid X General] spaceman4:
I found these directions over at droidforums. You need to be rooted to remove the bootstrap. So if your rooted, do this.

1. Uninstall the bootsrapper app

2. Go into root explorer to system/bin

3. In top right corner tap r/w

4. Delete the file called hijack

5. Delete logwrapper

6. Rename logwrapper.bin to just logwrapper

7. Reboot
[Droid X General] SysAdmin-X:
Yes, these instructions will remove the last remaining bits of the bootstrap app.
[Droid X General] spacecasespiff:
Thank you as soon as I have a min I will do it.
[Droid X General] spacecasespiff:
Ok its say I can't delete or rename the logwrapper because its a read me file. Wont let me do it
[Droid X General] SysAdmin-X:
Are you trying to do it using root explorer? If so, there is a button that says Mount R/W. Hit this, and then try to delete the file.
[Droid X General] spacecasespiff:
I am using root explorer and I tap mount RW and I try to delete hijacker and the logwrapper files but still can't. Is something soposed to happen when I tap the mount RW because nothing seems to happen.
[Droid X General] SysAdmin-X:
After you tap it, the button it should change to mount R/O. If it doesnt, then your version of root explorer isnt working correctly.
[Droid X General] spacecasespiff:
It changes before I go into system and then bin but after it does not. I will try again
[Droid X General] spacecasespiff:
Ok I downloaded a different version and this one worked and just rebooted and it worked. So thank you for your time.
[Droid X General] SysAdmin-X:
=) glad to hear you are back to where you want to be. If you have any more questions let me know.
[Vibrant Android Development] Chainfire:
SGH-T959_KA5_KA5_KA5_KA5_UV_TMB

ro.build.date = 2011.01.11 20:41:48 KST

ro.build.fingerprint = Samsung/SGH-T959/SGH-T959/SGH-T959:2.2/FROYO/UVKA5:user/release-keys

http://www.multiupload.com/VTVETOO7FS

NOTICE: I do not have this device model, nor have I tested the ROM, I'm only telling you where to find it.

Donate for my efforts (see sig) or at least use the thanks button if you don't want to donate :)

Uploaded by request - krylon360
[Vibrant Android Development] Whitehawkx:
Thanks Chainfire and Krylon360. Downloading now and will post feedback. :D
[Vibrant Android Development] Master™:
God! You beat me to this part.. lol

I was half way finished uploading
[Vibrant Android Development] scrizz:
Ha, thanks CF
[Vibrant Android Development] rakeshchn:
What does Samsung has in mind when leaking all these builds:confused:
[Vibrant Android Development] ayoteddy:
sweet thankss :)
[Vibrant Android Development] presence06:
Any word yet on how this is/fixes?
[Vibrant Android Development] daddysays:
Haha, it was posted 20 min before your post, I doubt anyone has even finished downloading it yet. Test it out and let us know.
[Vibrant Android Development] dligon:
this rom is awesome it makes chocolate milk come out of your vibrant :p
[Vibrant Android Development] hurrpancakes:
No need to be rude, chill
[Vibrant Android Development] es7241:
+1 keep this thread on track
[Vibrant Android Development] Zylograth:
backing up current ROM right now, download finished, will flash and report back.
[Vibrant Android Development] lightninbug:
Lol I'm spending way too much time in the M 10 thread... here's me thinkin KA5 is another Rom that resembles the M10... o well that's what wake n bake does to you I guess.. thank you for this!
[Vibrant Android Development] Master™:
Here is what I was uploading: http://www.multiupload.com/JUEBSIFSOO

I know it doesn't matter now.. But it is better then just trashing the link I guess
[Vibrant Android Development] dligon:
ok sorry about the "smartass" comment but it just kills me when a leak comes out and the devs push it out and someone ask hows the battery etc... a few minutes after the release.:cool:
[Vibrant Android Development] Bernardos70:
I guess some think this is like a new car that comes with a mileage sticker stuck on the passenger rear window.
[Vibrant Android Development] infinitybiff:
Possible the update that samsung is sitting on and not releasing?

http://www.bgr.com/2011/01/13/samsu...for-t-mobiles-vibrant-tips-anonymous-insider/

Looks like there is no changelog available? I'll sift through it later if i have time.
[Vibrant Android Development] budney:
So this is different then the one posted in the thread below?

http://xdaforums.com/showthread.php?t=911618
[Vibrant Android Development] AgentFour20:
Another 2.2 leak !? Wow
[Vibrant Android Development] presence06:
That one was deemed fake. / JL5
[Vibrant Android Development] Brytallica:
Haptic Vibration Level Bug

I upgraded to this ROM via ODIN from JK2. The only issue I've found so far is that the haptic feedback is always very weak, regardless of how strong you set the vibration intensity. While in the Vibration intensity selection popup, if I set to the lowest level the vibrations go away and when I set it to the strongest level the vibrations are really strong as normal. After hitting OK and leaving the popup, the haptic feedback goes back to really weak.