Froyo - Vibrant Q&A, Help & Troubleshooting

I'm just curious what keeps Froyo from being put on the Vibrant. Something missing from Samsung's end? Nothing else from Google at this point I assume, since Froyo's source code has been released.

It's already in the works with CM6 and Samsung.
Samsung is probably porting TouchWiz 3.0 over to Froyo and CM is doing their stuff with porting it over.

zephiK said:
It's already in the works with CM6 and Samsung.
Samsung is probably porting TouchWiz 3.0 over to Froyo and CM is doing their stuff with porting it over.
Click to expand...
Click to collapse
Remember when camera drivers were keeping us from getting Eclair on G1/MT3G? I'm wondering if it's the same right now with Vibrant and Froyo. Are you saying everything is available and all it takes is time on the devs' end?

cigar3tte said:
Remember when camera drivers were keeping us from getting Eclair on G1/MT3G? I'm wondering if it's the same right now with Vibrant and Froyo. Are you saying everything is available and all it takes is time on the devs' end?
Click to expand...
Click to collapse
No. I don't think so, I'm not a dev so I wouldn't be sure. http://github.com/wesgarner
Haven't heard anything from WesGarner about missing drivers.

cigar3tte said:
I'm just curious what keeps Froyo from being put on the Vibrant. Something missing from Samsung's end? Nothing else from Google at this point I assume, since Froyo's source code has been released.
Click to expand...
Click to collapse
there is nothing missing but taking a custom UI that is integrated throughout the system and now modifying it to work with version 2.2 (froyo) of android is not an overnight task.
Samsung has stated that it should be released by the end of this month.

rsfaze said:
there is nothing missing but taking a custom UI that is integrated throughout the system and now modifying it to work with version 2.2 (froyo) of android is not an overnight task.
Samsung has stated that it should be released by the end of this month.
Click to expand...
Click to collapse
Would it make things easier on devs when Samsung rolls out the official Froyo OTA?

Related

[Q] Captivate Camera on the Dell Streak????

My husband has the Samsung Captivate and I love his camera application. I like how you can tap the screen to determine the focusing and metering.
I was wondering if the camera application can be ported to the Dell Streak.
I would say no but i may be wrong
i very much doubt it, but get him to pull the .apk from his phone so we can check
This is what I got off of the captivate in the system/apps folder
naedhakeber said:
This is what I got off of the captivate in the system/apps folder
Click to expand...
Click to collapse
I tried both if these, in different order too. Negative
I guess I will have to wait until the official release of the UK 2.1 or 2.2 for the US. Or the release of the kernel and custom ROMs.
thanks for trying...
naedhakeber said:
I guess I will have to wait until the official release of the UK 2.1 or 2.2 for the US. Or the release of the kernel and custom ROMs.
thanks for trying...
Click to expand...
Click to collapse
I still don't think we'll get the captivate camera working then. It probably relies on some closed source Samsung frameworks for the camera to work, or possibly even the radio. Hopefully the official release will include a much better camera though. I guess we'll have to wait and see

port the captivate froyo?

is it possible to port the captivate froyo leak to our phones? or do we still need a kernel for froyo from sammy?
bdube said:
is it possible to port the captivate froyo leak to our phones? or do we still need a kernel for froyo from sammy?
Click to expand...
Click to collapse
There was a posted working ROM in the IRC last night.
shauder said:
There was a posted working ROM in the IRC last night.
Click to expand...
Click to collapse
Lol, how working?
Sent from my SCH-I500 using XDA App
i was wonderin the same, is there a link anyone here?
I don't know he said he fixed the accelerometer
http://github.com/jt1134/android_ve...053be601b619ad27de6fe120100d5de6705c9b#diff-0
shauder said:
I don't know he said he fixed the accelerometer
http://github.com/jt1134/android_ve...053be601b619ad27de6fe120100d5de6705c9b#diff-0
Click to expand...
Click to collapse
Kernel, not ROM.
frostman89 said:
Kernel, not ROM.
Click to expand...
Click to collapse
haha yea i figured reading that commit, lol guessing the froyo is a no-go as of right now
Link file says Kernel
lets hope they can get a rom made using this soon
looks like there is a kernel made
Woohoo! C'mon Froyo!
Trying to build a kernel with the new defconfig now. Will report back momentarily.
I don't know how many times this has to be brought up guys, but we wont have froyo till we have kernel source for 2.6.32. The kernel source we have working right now is 2.6.29
Just calm down and be patient, or get to work and start developing. There is only so much devs can do, and if you want a feature or something, try doing it and learn. We don't need new forums posted everyday about how you want froyo, or tv out, or ios.
fallingup said:
I don't know how many times this has to be brought up guys, but we wont have froyo till we have kernel source for 2.6.32. The kernel source we have working right now is 2.6.29
Just calm down and be patient, or get to work and start developing. There is only so much devs can do, and if you want a feature or something, try doing it and learn. We don't need new forums posted everyday about how you want froyo, or tv out, or ios.
Click to expand...
Click to collapse
TBH, I'm equally sick reading these posts. Guess what, you can say that till you're blue in the face and people will still act in ways you don't want, it's called being being excited/impatient. You kind sir/madam could save yourself some bandwidth (and apparently annoyance/frustration) by just not licking on these links.
*edit* Also, it's great to see another New Mexican on the boards *edit*
Yeah...no licking links!!!
I don't know how many times this has to be brought up guys, but we wont have froyo till we have kernel source for 2.6.32. The kernel source we have working right now is 2.6.29
Click to expand...
Click to collapse
New to this myself. Fascinate is my first smartphone. So I gather we are likely waiting for the 2.2 release from Samsung for the Fascinate? Then someone will likely take the src and remove the bloatware etc?
Is the Cyanomodgen version also waiting on this?
Main thing I want is tether and all the bloatware removed from my phone. I have not rooted and am waiting for a good reason to do so. Don't want to root then have to undo it down road or something to get some other update and risk something going wrong. Thinking of waiting for the GPS fixes to get out etc first. Really want the Cyanomod ROM for this phone.
matthewsh said:
Main thing I want is tether and all the bloatware removed from my phone. I have not rooted and am waiting for a good reason to do so. Don't want to root then have to undo it down road or something to get some other update and risk something going wrong. Thinking of waiting for the GPS fixes to get out etc first. Really want the Cyanomod ROM for this phone.
Click to expand...
Click to collapse
The root process is easy and shouldn't affect any updates. Removing certain apps could possibly affect any OTA updates - this has happened on some Motorola phones.
Rooting will allow Wireless Tether and the ability to remove bloatware. Make it easy on yourself and just MOVE apps you don't want from /system/app to your SD card so you can easily put them back when it's time to receive OTA updates.
The root process is easy and shouldn't affect any updates. Removing certain apps could possibly affect any OTA updates - this has happened on some Motorola phones.
Rooting will allow Wireless Tether and the ability to remove bloatware. Make it easy on yourself and just MOVE apps you don't want from /system/app to your SD card so you can easily put them back when it's time to receive OTA updates.
Click to expand...
Click to collapse
Thanks for the quick answer. Will this remove bing as well?
matthewsh said:
Thanks for the quick answer. Will this remove bing as well?
Click to expand...
Click to collapse
no
edit: message has to be at least 10 characters. darn.
matthewsh said:
Thanks for the quick answer. Will this remove bing as well?
Click to expand...
Click to collapse
jspidah said:
no
edit: message has to be at least 10 characters. darn.
Click to expand...
Click to collapse
Actually, we have no idea it it removes Bing or not.
Most likely it won't, but stranger things have happened, like Bing as the primary search for an Android phone.

[REQ] Droid X Multi Touch Keyboard *Font Issue Fixed*

I currently have the Droid X Multi-Touch keyboard working on my Vibrant, but the only issue is the font. I know its not that big of a deal but a fix would be nice?
For those who have it, provide link for US who love the keyboard!!!
THxXXX
Supposedly its in the new Axura ROM, you could pull it out of there.
thegreatcity said:
Supposedly its in the new Axura ROM, you could pull it out of there.
Click to expand...
Click to collapse
I have already tried that method. It aprently only works on Froyo 2.2, not 2.1 and most of us are running 2.1
Bumpp
Sent from my SGH-T959 using XDA App
I also would want this for 2.1, hopefully Master can give us a hint
Sent from my SGH-T959 using XDA App
if you use it on any other device i9000/captivate the letters are fixed also on any rom for vibrant with the i9000 kernel so the issue with the kb originates from our kernel
Vibrant - Bionix Fusion 1.1 - JAC's Xmod kernel v1 - ext2 lag fix
kennyp987 said:
if you use it on any other device i9000/captivate the letters are fixed also on any rom for vibrant with the i9000 kernel so the issue with the kb originates from our kernel
Vibrant - Bionix Fusion 1.1 - JAC's Xmod kernel v1 - ext2 lag fix
Click to expand...
Click to collapse
I don't believe so. Its, more likely then not, due to a library issue, since the vibrant theme is slightly different than others.
Has anyone tried it on JI6.
blinksilver said:
I don't believe so. Its, more likely then not, due to a library issue, since the vibrant theme is slightly different than others.
Has anyone tried it on JI6.
Click to expand...
Click to collapse
Hi,
I've tried the Droid X (2.1 mod version) keyboard on all the JI series leaks, and the final OTA JI6, and the keys still render tiny, for me.
I've also tried pushing the libjni_latinime.so from a captivate rom to my phone, and still no luck, tiny keys.
So, I'm lost on anything else to try except thinking its somehow kernel related, since flashing a rom with a kernel built from i9000 source, renders the keys properly.
If I remember correctly, even in the earliest days of Vibrant modding, when flashing the very first clockwork recovery betas (the versions that actually included kernels built from i9k source and weren't simply loaded into the ramdisk the way it is now) the keys rendered properly too, can anyone confirm?
I still hope we get this fixed, since GPS is a deal breaker for me, so until we have a vibrant froyo leak to pull GPS drivers from, I'm sticking with 2.1 builds.
Anyway, cheers everyone, =)
s0niqu3 said:
Hi,
I've tried the Droid X (2.1 mod version) keyboard on all the JI series leaks, and the final OTA JI6, and the keys still render tiny, for me.
I've also tried pushing the libjni_latinime.so from a captivate rom to my phone, and still no luck, tiny keys.
So, I'm lost on anything else to try except thinking its somehow kernel related, since flashing a rom with a kernel built from i9000 source, renders the keys properly.
If I remember correctly, even in the earliest days of Vibrant modding, when flashing the very first clockwork recovery betas (the versions that actually included kernels built from i9k source and weren't simply loaded into the ramdisk the way it is now) the keys rendered properly too, can anyone confirm?
I still hope we get this fixed, since GPS is a deal breaker for me, so until we have a vibrant froyo leak to pull GPS drivers from, I'm sticking with 2.1 builds.
Anyway, cheers everyone, =)
Click to expand...
Click to collapse
11/5/2010 Forget you people
I hope someone can fix this. I absolutely love the Droid X multi-touch keyboard. Its the most accurate and fastest I've ever typed on a touchscreen QWERTY keyboard. With the keys font size fixed it'll be 10/10
Anyone, please
I tried ripped the version from the Rom itself but I get a parsing error.
nothing yet?
I've discovered only one good alternative to multi-touch keyboard. Its a Smart Keyboard. By default it slower but if you decrease multi-type delay and swipe-sensivity it will became better.
This thread is Major FAIL. Where is the fix....
Master needs to post what he did.
vinnydakid said:
Master needs to post what he did.
Click to expand...
Click to collapse
I think he want that feature to be exclusive for his roms...
eortizr said:
I think he want that feature to be exclusive for his roms...
Click to expand...
Click to collapse
I doubt it, if it was just exclusive to his rom, you could just ripe out the apk.
blinksilver said:
I doubt it, if it was just exclusive to his rom, you could just ripe out the apk.
Click to expand...
Click to collapse
Hi,
The only problem is the version is his 2.2/Axura rom isn't modified to work on 2.1, now, if someone can point me to a howto on modifying the keyboard to work on 2.1, I'd do that tonight, lol.
UPDATE:
I re-downloaded Master's newest Axura 1.0.3 and decompiled so I can diff the KeyboardView.smali files (this seems to be the file controlling the key font size) and I don't see any difference in the code between the two relating the private field that motorola use mKeyTextSize, so at this point, its beyond me, hopefully master will be kind enough to post his edit, or another dev can look into this.
Sorry, but I just don't see why the keys display fine on i9k/captivate/fascinate/etc., but tiny on the vibrant, and yet display fine on the vibrant with an i9k kernel.
Cheers, =)
s0niqu3 said:
Hi,
The only problem is the version is his 2.2/Axura rom isn't modified to work on 2.1, now, if someone can point me to a howto on modifying the keyboard to work on 2.1, I'd do that tonight, lol.
UPDATE:
I re-downloaded Master's newest Axura 1.0.3 and decompiled so I can diff the KeyboardView.smali files (this seems to be the file controlling the key font size) and I don't see any difference in the code between the two relating the private field that motorola use mKeyTextSize, so at this point, its beyond me, hopefully master will be kind enough to post his edit, or another dev can look into this.
Sorry, but I just don't see why the keys display fine on i9k/captivate/fascinate/etc., but tiny on the vibrant, and yet display fine on the vibrant with an i9k kernel.
Cheers, =)
Click to expand...
Click to collapse
He did not have to edit the smali file in the 2.2 keyboard, just the 2.1 keyboard(most likely for personal use). it works just fine since all the 2.2 roms are using a modded i9000 kernel. That said, you are bringing up a really good point, why is the kernel causing such interesting behavior.

is anyone working on a flashable gingerbread kernel that will work with 2.2?

just wondering if there is anyone working on this, or if the source is even out yet....tmo did say that hey would have upcoming android releases within 3-5 months from release of said versions. Just curious if there are any leaks that anyone has come across.
Thanks
thachosenone said:
just wondering if there is anyone working on this, or if the source is even out yet....tmo did say that hey would have upcoming android releases within 3-5 months from release of said versions. Just curious if there are any leaks that anyone has come across.
Thanks
Click to expand...
Click to collapse
From my understanding, a gingerbread kernel will only work with a gingerbread rom.
You want a flashable 2.3 kernel modded to work on 2.2 - is that what you are asking?
Yes and no, I'm just wondering if anyone is working on a gingerbread rom for vibrants, and from what i understand, gingerbread roms won't work unless it includes a gingerbread kernel.
Sent from my SGH-T959 using XDA App
Moved of: Samsung Vibrant > Vibrant Android Development
To: Samsung Vibrant > Vibrant Q&A
Please put your questions to: Vibrant Q&A
your question: "is there a 2.3 kernel that works in 2.2?"
problem: this makes no sense. only 2.2 kernels work in 2.2. Only 2.3 kernels work in 2.3. What are you trying to ask?
Interpretation: "is anyone working on a 2.3 rom for your vibrants?"
Answer: yes. CM just upped a test version of 2.3 IN ALPHA (not the same as the ones that appeared in december), but right now it's almost exclusively i9k only (to convert the radio file takes a bit or work).
Good news for our vibrants, Krylon360 of TeamWhiskey is working on a 2.3 port himself. But the progress is going to be a while since he's the only one working on it.
hey everyone, i usually dont post, observer is more like it. but i am having touble and i hope someone could shed some light. the first issue is with the dow kernel from tw. it wont recognize my headset as a microphone headset, only plays music, and second, ffc isn't my default camera when i use messenger, fring, or qik. it works fine, except for the low light/low banding issue, havent found anything for that yet, but i digress. those programs go automatically to my back cam, not sure what i'm doing wrong. thanks in advance for the help and just wanted to say thanks to all the devs. you guys are awesome, we would be running crappy slow phone and slaves to our networks. you guys (and gals) rock.

[Q] Mic for S-voice

Does any of the rom's have a mic working?
I've just installed S-voice and want to test it.
Thanks
No. It's a hardware/driver issue across the board.
Sent from my rezound
try use the webos
adder101 said:
Does any of the rom's have a mic working?
I've just installed S-voice and want to test it.
Thanks
Click to expand...
Click to collapse
Some of the CM7 roms had limited success with the mic but CM9 isn't ready yet
And S-voice won't work in webos lol
cm9 has been out for like 5 months now.. i dont have any faith the mic or cam will ever work in cm9.
rkaede said:
try use the webos
Click to expand...
Click to collapse
s-voice for ics only, even then it had to be modified as its exclusive for Samsung s3.
If it worked in gb even if it was not that good, surely it could be made to work in ics.
Though the installation of s-voice was without any problems.
x000x said:
cm9 has been out for like 5 months now.. i dont have any faith the mic or cam will ever work in cm9.
Click to expand...
Click to collapse
Mic and camera are at the bottom of the pile of things to do, getting an OS that was never designed for the TouchPad is no easy thing, drivers and wrappers have to be written from scratch with no support from HP. So have faith in the developers, remember most of them are either at full time work or school/college and are offering you there work for free, maybe you could ask HP to fix the camera and mic I think they would abandon that idea faster than they abandoned the TouchPad itself.
x000x said:
cm9 has been out for like 5 months now.. i dont have any faith the mic or cam will ever work in cm9.
Click to expand...
Click to collapse
BIGSimon said:
Mic and camera are at the bottom of the pile of things to do, getting an OS that was never designed for the TouchPad is no easy thing, drivers and wrappers have to be written from scratch with no support from HP. So have faith in the developers, remember most of them are either at full time work or school/college and are offering you there work for free, maybe you could ask HP to fix the camera and mic I think they would abandon that idea faster than they abandoned the TouchPad itself.
Click to expand...
Click to collapse
Exactly what BIGSimon said. CM9 is still ALPHA. Meaning some things will not work. Not everything that is released is perfect right away. Developing ROMs isn't always an easy task. What they have done in 5 months is pretty damn great.
yeah i know that. but i seem to recall that it at least halfway worked with cm7. plus, in a short time android will have another os version, jellybean or something. and then what? will cm9 be abandoned and work start with that one? and once again, the camera and mic will be pushed back down to the bottom of the list in order to work on more essential things? seems like a endless cycle
x000x said:
yeah i know that. but i seem to recall that it at least halfway worked with cm7. plus, in a short time android will have another os version, jellybean or something. and then what? will cm9 be abandoned and work start with that one? and once again, the camera and mic will be pushed back down to the bottom of the list in order to work on more essential things? seems like a endless cycle
Click to expand...
Click to collapse
There's a big difference between Android 2.3.7 gingerbread and Android 4.0.4 ice cream sandwich which meant everything had to be re-written to work Android 5 jelly bean is more of an evolution of ICS so drivers will carry over, all the work that's been done now will mean that when JB is released the touchpad will get it a lot faster with everything working
Sent from my HTC Wildfire using Tapatalk 2
x000x said:
yeah i know that. but i seem to recall that it at least halfway worked with cm7. plus, in a short time android will have another os version, jellybean or something. and then what? will cm9 be abandoned and work start with that one? and once again, the camera and mic will be pushed back down to the bottom of the list in order to work on more essential things? seems like a endless cycle
Click to expand...
Click to collapse
JellyBean will be a minor update, it will have a version 4.1, it isn't as huge step as going from 2.3 to 4.0.
Anyway, sound is surely being worked on (developers (partially, maybe) have gotten rid of bad screen-off sound issue last week), and we will see some progress in a time. If you want a tablet with all features working out-of-the-box, i guess, you should buy another device.
The latest audiolibs seems to be working great. Too bad S-Voice is having connection problems. Anyone know how to resolve the server issues in S-Voice?
+ 1 ;-)
BuffMcBigHuge said:
The latest audiolibs seems to be working great. Too bad S-Voice is having connection problems. Anyone know how to resolve the server issues in S-Voice?
Click to expand...
Click to collapse
Do you have your device spoofed to be a galaxy s3? I think you need to that for it to work
jsgraphicart said:
Do you have your device spoofed to be a galaxy s3? I think you need to that for it to work
Click to expand...
Click to collapse
I was able to get it working by flashing this:
http://forum.xda-developers.com/showthread.php?t=1667046
Works wonderfully with the new audiolib!
Is there a flashable audiolib somewhere?
--update--
Found it
http://goo.im/devs/jcsullins/cmtouchpad/testing
Sent from my SGH-T989 using Tapatalk 2
Izeltokatl said:
Is there a flashable audiolib somewhere?
--update--
Found it
http://goo.im/devs/jcsullins/cmtouchpad/testing
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
Nighlyy 0620 has everything mic needs already included.

Categories

Resources