I am probably late to the game but didn't see this anywhere so thought I would just mention - I just flashed this Gingerbread based ROM real quick http://forum.xda-developers.com/showthread.php?t=1092565 and then flashed the APK mentioned here http://www.xda-developers.com/android/skype-2-available-for-other-devices/ and made a quick test call from my netbook to my Streak - It wasn't perfect (could be due to slow network connection and not doing a clean install of the new ROM) but anyway, it did work.
So I just did a quick video call to my parents and confirmed that it works very well - I was also able to switch from the front camera to the back camera.
Asking because I don't know; What is the difference between Skype and Fring? Fring all day with my kids and seems to be the same as what you just did with your parents.
do you need gingerbread for this to work?
yes, I believe so you need gingerbread for this.
hopefully they will eventually release an app for those of us with devices still stuck on official 2.2
Fring is a cool app but I am not sure if they have a desktop version - I have only used it once on a friend's phone. Frankly I have been using Oovoo for some time now to call my parents and it has worked great, but I have MANY more contacts who use Skype and didn't feel like spending the time or energy to try and get them all to switch.
Yes - for sure you need Gingerbread - I took a stab at installing it on Streakdroid 1.9 but it was a no go. As soon as I installed the above ROM and then installed the APK it worked.
As a side note the above ROM seems to be working great - I had been planning to install DJ Steve's Gingerbread ROM but will have to wait until I have some time.
johnpmorton said:
Fring is a cool app but I am not sure if they have a desktop version - I have only used it once on a friend's phone. Frankly I have been using Oovoo for some time now to call my parents and it has worked great, but I have MANY more contacts who use Skype and didn't feel like spending the time or energy to try and get them all to switch.
Yes - for sure you need Gingerbread - I took a stab at installing it on Streakdroid 1.9 but it was a no go. As soon as I installed the above ROM and then installed the APK it worked.
As a side note the above ROM seems to be working great - I had been planning to install DJ Steve's Gingerbread ROM but will have to wait until I have some time.
Click to expand...
Click to collapse
i did on steves gingerbread....dont work. force close.
What would happen if I just change my build.prop to read version 2.3.3?
Are there other areas of the phone that confirm gingerbread?
rsalib said:
What would happen if I just change my build.prop to read version 2.3.3?
Are there other areas of the phone that confirm gingerbread?
Click to expand...
Click to collapse
My guess is it would force close - just changing the version doesn't actually make it Gingerbread so there would be compatibility issues. I will check later since I am going to be playing around with another Streak tonight.
Yep - force close.
I recently flashed CyanogenMod 7.1 on my Galaxy SII. I previously had a Galaxy S Captivate and couldnt stand being stuck with a stock rom after using CM7. One of the only complaints i have about CM 7.1 RC is that the camera app crashes, and is completely unusable. Even if this were not the case, i love the original camera app on this phone.
So my question is, and it may very well be a complete noob question, so please try not to bash me too much, but Is there any way to flash the stock camera app onto Cyanogen? Or does the new Kernel/Rom prevent a stock application from running correctly?
Thanks a lot guys,
Evan
erjohnson227 said:
I recently flashed CyanogenMod 7.1 on my Galaxy SII. I previously had a Galaxy S Captivate and couldnt stand being stuck with a stock rom after using CM7. One of the only complaints i have about CM 7.1 RC is that the camera app crashes, and is completely unusable. Even if this were not the case, i love the original camera app on this phone.
So my question is, and it may very well be a complete noob question, so please try not to bash me too much, but Is there any way to flash the stock camera app onto Cyanogen? Or does the new Kernel/Rom prevent a stock application from running correctly?
Thanks a lot guys,
Evan
Click to expand...
Click to collapse
You cannot flash stock camera into CM7 it. If it was that easy it would have been done already.
If you want to retain all the features of the camera and video part of the phone
it's best to stay away from CM7 until the DEVS decide to fix it.
I have been testing CM7 ever since I first purchased my Samsung Captivate and
now with my new SGS2 i777.
GTG's UnNamed v1.03 custom rom is the best currently available for our phones.
It achieves the full & steady 30fps according to the specifications of the phone.
The user interface cosmetically speaking is also the best there is right now.
CM7 is not ready for prime time yet especially if video recording and camera
user interface (UI) is important to you.
There are many missing features and options in the CM7's camera user interface.
CM7 still does NOT achieve the full continuous 30fps while recording video.
So home made recordings when played back will not be super smooth and will
not achieve the video standards according to the specification of the phone.
BUT it's up to you guys, if you hardly use the camera at all CM7 is great.
(personally I use my camera a lot and video recording is very important to me.)
Galnet MIUI has call recording integrated into its dialer app. Are there any other ROMs that do the same, so you don't need to use an additional app to record?
Thanks.
Have you tried to just pull the phone.apk from one of the i9100 roms that have recording built in and install it? I was thinking of trying that, but haven't gotten around to it. Besides, it didn't work that easily on i9000 -> Cappy.
edit: There is also this. Haven't tried it yet, either. http://forum.xda-developers.com/showthread.php?t=1222368
I wasn't sure if transferring the phone.apk's was possible since I'm a newbie lol.
I'll give that a script a shot. Thanks!
For anyone who may be interested, I tried the dialer mod that PuffinNugz linked to and it seems to work fine for our phones. Thanks again PuffinNugz!
I've been happily running the GEEWIZ 2.6 ROM alternately with GEEWIZ kernel and KGB kernel. No problems at all except for the Stereo Bluetooth connection to my car.
The phone works great on newer versions of my car 2009 Acura TSX and other phones work fine on my car.
Well I (via Google) finally narrowed the problem down. There is a bug in the native android 2.2 and 2.3 code that Samsung pushes right through. HTC for example fixed the code in their phones.
Google this: "Issue 9888oor A2DP sound quality". I added the word Acura as well.
Cyanogenmod 7.2 RC1 does not have this bug and the phone sounds fine on my car. Would it be possible to extract or port the A2DP code from Cyanogenmod 7 and place it into GEEWIZ or other more stock ROM's?
The reason I want to stay more stock is that I can't get SMS delivery confirmation to work in Cyanogenmod 7 or 9 or Gummy 1.0 and SMS confirmation works well in GEEWIZ 2.6.
I have tried GO and HandCent SMS clients in addition to stock and have checked all combination's of receive and sent notifications and delivery requests and reports. None work. Texts get through fine just no confirmation. Verizon to Verizon should work.
I don't have enough posts to post in the Dev/GEEWIZ thread. Can someone help or cross post please? I've read until I'm blue in the face on both of these issues. ;-)
BTW, I have 2 fascinates and both act exactly the same.
Thanks!
Zong00 said:
I've been happily running the GEEWIZ 2.6 ROM alternately with GEEWIZ kernel and KGB kernel. No problems at all except for the Stereo Bluetooth connection to my car.
The phone works great on newer versions of my car 2009 Acura TSX and other phones work fine on my car.
Well I (via Google) finally narrowed the problem down. There is a bug in the native android 2.2 and 2.3 code that Samsung pushes right through. HTC for example fixed the code in their phones.
Google this: "Issue 9888oor A2DP sound quality". I added the word Acura as well.
Cyanogenmod 7.2 RC1 does not have this bug and the phone sounds fine on my car. Would it be possible to extract or port the A2DP code from Cyanogenmod 7 and place it into GEEWIZ or other more stock ROM's?
The reason I want to stay more stock is that I can't get SMS delivery confirmation to work in Cyanogenmod 7 or 9 or Gummy 1.0 and SMS confirmation works well in GEEWIZ 2.6.
I have tried GO and HandCent SMS clients in addition to stock and have checked all combination's of receive and sent notifications and delivery requests and reports. None work. Texts get through fine just no confirmation. Verizon to Verizon should work.
I don't have enough posts to post in the Dev/GEEWIZ thread. Can someone help or cross post please? I've read until I'm blue in the face on both of these issues. ;-)
BTW, I have 2 fascinates and both act exactly the same.
Thanks!
Click to expand...
Click to collapse
No problem, I'll have a look at it for you and see if I can fix that in GeeWiz for the final release. Thanks for PMing me, by the way, I was about to post GW 2.8, but I would like to be able to include this too!
thanks
I would be happy to test any change. I'm getting used to flashing every night now. ;-)
Well, I ported over what I *thought* was everything they did in CM 7.2 and all that I managed to do was destroy the ability to pair with a device so far
I dug out my old BT audio receiver and I can certainly hear that it sounds like garbage by default. Well, it wasn't THAT bad but I do see, er hear, what you are talking about.
My concern is that my receiver is old and crappy (it is), and I may never be able to actually hear any difference. That said, I will keep trying for a while, if I can at least pair with the receiver after changing something I will pass it along to you and see if it does something useful for ya!
From what I understand the Fascinate with stock software works on older Bluetooth devices OK. I don't know that for sure because I don't have an older bluetooth device. On my car, the stock Fascinate does not have any fidelity, it produces sound via bluetooth like an AM radio with clicking sounds. When updated to Cyanogenmod 7.2, the sound is very FM like with no clicking sounds.
I appreciate the effort!
thanks,
OK, I finally got back to this. I was replacing too many modules, I toned it down a bit to just replace the bluez audio module and the a2dp module. I can absolutely hear a difference now!
It's still Bluetooth, aka not perfect, but I can crank the volume on the Fascinate up much louder before it "splats" (that's a very technical audio term) and overall it just sounds much much better.
I've attached a test version of an update-zip you can try. Should work with Clockwork Mod and/or my GeeWiz Recovery, but I've only tested with the latter of course . I will be making a more official version for GeeWiz 2.8 (I may go ahead and release a 2.8.1 with this, it's a pretty big fix -- who cares if I said there would be no more updates, right? LOL)
THANK YOU for pointing this out to me!! Let me know what you think!
Not yet
No joy -
First I tried loading the patch over fullwipe GEEWIZ 2.8 and KGB 12/31.
Next I tried loading the GEEWIZ kernel over the KGB kernel.
And finally I tried loading the full 2.8.1 system file.
The sound is still not nearly as clear as Cyanogen 7.2 RC1.
I'm sure if the new build is somewhere in the middle or not. Seems like the full fidelity is present now but the clicking sound is still present.
Cyanogen BT is as clear as a direct audio connection. At least to my old ears.
I'll revert back to 2.8 and try the audio test again.
Do you think a full wipe would help - can't imagine why.
Zong00 said:
No joy -
First I tried loading the patch over fullwipe GEEWIZ 2.8 and KGB 12/31.
Next I tried loading the GEEWIZ kernel over the KGB kernel.
And finally I tried loading the full 2.8.1 system file.
The sound is still not nearly as clear as Cyanogen 7.2 RC1.
I'm sure if the new build is somewhere in the middle or not. Seems like the full fidelity is present now but the clicking sound is still present.
Cyanogen BT is as clear as a direct audio connection. At least to my old ears.
I'll revert back to 2.8 and try the audio test again.
Do you think a full wipe would help - can't imagine why.
Click to expand...
Click to collapse
Full wipe probably wouldn't do anything for ya, no. When you say clicking, is it fairly often, or more like once per song? I get what sounds more like a skip (to me) about once per song, I didn't think it was the same complaint, but perhaps it is? If so, at least I can duplicate it, so that's good.
I'm not sure if much more can be done, the only remaining difference is the audio.conf (trivial changes) and the libbluetooth C library itself, and replacing the latter causes the Fascinate to not be able to pair. I think source would be required to properly replace that module (CyanogenMod has that particular luxury). It could be in the Java code, though. If that's the case it can still be fixed.
I'll poke around some more and see if I can do anything else for ya. I was jamming all night over bluetooth last night, honestly I didn't even know the device could do that a few days ago - LOL.
djp952 said:
Full wipe probably wouldn't do anything for ya, no. When you say clicking, is it fairly often, or more like once per song? I get what sounds more like a skip (to me) about once per song, I didn't think it was the same complaint, but perhaps it is? If so, at least I can duplicate it, so that's good.
I'm not sure if much more can be done, the only remaining difference is the audio.conf (trivial changes) and the libbluetooth C library itself, and replacing the latter causes the Fascinate to not be able to pair. I think source would be required to properly replace that module (CyanogenMod has that particular luxury). It could be in the Java code, though. If that's the case it can still be fixed.
I'll poke around some more and see if I can do anything else for ya. I was jamming all night over Bluetooth last night, honestly I didn't even know the device could do that a few days ago - LOL.
Click to expand...
Click to collapse
The clicking sound in my car occurs several times a second and its really obvious. Acura blamed the phone (Samsung) saying just that the phone wasn't compatible but I wasn't convinced until I found the Android bug ID.
I really appreciate the effort and it sounds like you fixed a problem just not my problem. ;-)
I'm considering a Galaxy III this summer but Samsung has left a bad taste in my mouth.
Let me know if you come up with anything else to try.
thanks!
Well, I spent some more time on this, and found that Samsung actually does include the BT code with their public distribution. So ... I spent some time merging that with the Cyanogenmod code that's currently available on github, and gave it a try. Short version: fail. Sounds like crap again and still skips intermittently for me. I can't replicate your more frequent skip, I'm afraid, but this was certainly a step backwards regardless.
Next I tried replacing all the modules my custom build generated with the ones from CyanogenMod 7.2 RC1. Even bigger fail, no bluetooth at all.
Using custom build with the BLUEZ modules from CyanogenMod restored the sound quality but it still skipped. Basically back where I started, so fail. I don't see the code edits they made that improve the fidelity so much, maybe they haven't committed them yet?
Last try was to set Master=true in the system/etc/bluetooth/audio.conf file on top of everything else. Still skips, but maybe a little less often? Still chalking it up as a fail.
So I think I'm not going to be able to fix this for you. There's a chance that what they did in CM 7.2 RC1 is just not posted yet and I can still make a custom set of binaries that will work, but I'm not very optimistic about it. I think what I did in GW 2.8.1 is pretty much as good as I can get it. Sorry
I did the best I could. For what it's worth, BT audio on my Fascinate is light years better than it is on my Galaxy Nexus at the moment. Not much consolation for you, but it's something I guess. The fact that I was able to generate a set of working BT binaries from source is also a good thing, even if they didn't solve anything since that means if I even stumble upon the fix it's something I can build myself!
You're welcome to try my final attempt, I've attached the .zip to this post. This is a custom BT module build with the BLUEZ modules with the ones from CM 7.2 RC1 and the master=true setting in audio.conf. I really don't think it will solve anything for you, but the only way to be sure is to try, right?
Hello.
I am using an XT910 on a 4.1.2 China kernel version which allows me to record calls (I need that as I am often driving and cannot stop to take notes yet I need vocal notes for figures, numbers, details... hence my need to be able to record calls at will... my counterpart is aware of that
I am using an app called "Sanity" and it works quite well.
I have another XT910 MAXX on a 4.1.2 JB Europe that instead does not allow call recordings and the kernel is locked so it cannot be changed.
I was trying to override this issue by using Boot Menu Manager (BMM) and installing a JBX kernel on another ROM (not the stock one) like SlimKAT, Paranoid and so on in the 4.4.2 release.
Yet neither Sanity nor any other call recorder app that I found is able to properly record a call: what I hear is either an empty file or only "white noise".
I tried downloading and installing a JBX module called "call recording" but it appears to be designed and appliable only on Samsung Galaxy S4 and/or only on Samsung designed ROMs.
So, in the end, my questions is:
Is anyone aware of any working trick or configuration to record calls with JBX kernels or some other way?
Please only tested solutions, no advice like one app or another since I already tested a bunch with no result.
Thanks a lot.