Related
I have two Motorola 820HT Bluetooth headsets. From day one I had no problems with them. (they even worked better on the G2 than my TP2 and EVO 4g) I woke up last Friday to find the G2 trying to update. After the update every thing worked fine until I got a call at work. I listen to a LOT of music/radio/podcast etc.... anyway i was listing to some music and the phone rings, here's where the problems lies. After I hung up the ONLY way a can resume playing music though the headset is to turn them off, then turn them back on. It dose the same thing on both of them. I even tried my friends JBTH710 headset and had the same problem. I can see the numbers moving in the music player, but no audio comes out until I turn off then turn on. Has anyone else had this problem; and if so what did you do to fix it? Taking the phone back to T-mobile for a replacement (to get a phone without the update) is not a answer because without wifi calling I can't use the phone at home.
Just to be clear (I'm not the best typist in the world) If I get a call with Bluetooth parried to my phone and I want to listen to something though my headset after the call, ( it can be five hours after the call) I have to turn off the headset then turn them back on.
Thank you for any feedback that helps me or anyone with this problem solve it.
Having the same problem as you
I think I have figured it out its the new bluetooth 2.2 that was used with the OTA. I think if we can get the old one from the pre-OTA and adb push it to the system it could work. This problem has made my bluetooth radio useless in the car when I get a call and hang up it should go were it left off from the music or podcast but you can see its still playing but no sound. So always have to disconnect bluetooth and reconnect it for it to work again. So if anybody has the pre-OTA please use adb and pull the bluetooth and upload it to rapidshare or whoever you use to were I can try this and see if it fixes the problem.
My parrot evo 3k (Parrot v5.11c) won't connect with my G2. I haven't tried with original rom, but this problem exists on the Ota, CM RC3, and CM RC4. My G1 had a similar problem in some froyo builds, but I think it was fixed in RC1 or the nighties. I know it worked great from dream-sapphire 230 or so on. Can a BT from older builds be pushed in to recent builds?
Tried adb pushing the old bluetooth.apk from the first rom to the new ota and it didn't work. I think its the new radio in the ota that messed up the bluetooth from working right I think I'm going to maybe flash the old radio and see if that works. And if anyone is experiencing this issue and you have solved the problem please let us know how you did it .
Sent from my T-Mobile 7 inch space banana
any updates on this issue
G2 TMOBILE OTA BROKE UP MY BLUETOOTH.. Here is how i fixed it...
I AM SURE THAT EVERYONE ALREADY KNOWS THIS. BUT I WANT TO SAY UP FRONT.. WHENEVER YOU TRY TO ROOT YOUR PHONE AND CHANGE THE ROM, YOU RUN THE RISK OF PERMANENTLY BRICKING YOUR PHONE.
With that being said, I will start my rant.
ISSUE: I would be connected with my stereo headset listening to music. The
phone would ring an the music paused. I was able to take the call on the headset without issue. After hanging up on the call, the music would never resume on the headset. The music was streaming on the device but no music on the headset. I had to toggle Bluetooth off then back on to get it to work again. It seemed that the A2DP bluetooth connection would get corupted everytime a call was replaced or received. I tried 5 different A2DP enabled bluetooth devices and they all did the same thing. These 5 bluetooth devices all worked just fine with my Mytouch and my G1. So it definatelty was the phone. T-mobile tried to tell me that all of my bluetooth devices must have been broken. They are the thing that is broken. On my G2, I have had a lot of connectivity issues with bluetooth and wifi after that stupid OTA update.
QUICK WORKAROUND but at a price : Just go to bluetooth settings and toggle off the phone bluetooth connection but leave the media connected. You will need to take all calls on the phone handset but the music (A2DP) connection will not be broken when a call is placed or received. If you have multiple bluetooth devices, you need to change this setting for each device.
T-mobile claimed that it was the radio firmware From HTC.
T-Mobile tried to tell me that it was an HTC issue and HTC tried to tell me that it was a T-mobile issue.
HTC was correct and T-Mobile is a bunch of morons as usual.
My PERMANENT fix Listed below... 1 I rooted the phone. (Permanent Root) 2I installed Rom Manager and selected "Flash ClockworkMod Recovery" (v2.5.1.3) then I rebooted into recovery and did a backup. That will get you a backup of your stock phone. 3Next, I wiped all data on the phone (from the recovery screen) and then installed Cyanogen 6.1.1 for the G2 (CyanogenMod-6.1.1-vision) 4Rebooted into Recovery and installed google apps.
MY BLUETOOTH NOW ROCKS! WORKS PERFECTLY. The WIFIis also working flawlessly now.
A few issues you should be aware of before changing the ROM. 1 You will lose swype if you don't grab the 2 swype files from your phone right after you root. 2 Before doing ANYTHING,, go into your settings and let Google back up your Data then manually initiate a sync in settings so you know that your app data has been backed up to google, Android will pull the T-Mobile WIFI CALIING app back to the phone automatically after you install the Cyanogen mod and sign into your google account on the phone. I also read somewhere that wifi calling was included in cyanogen. So I am not sure which is the reason it ends back up on your phone with cyanogen but it does. 3 You will also need to install the google package to get all your google apps back.
..........................................................................................................
..........................................................................................................
Exactly what I did. (NO ROOM FOR MISTAKES ON THE ROOTING !!!.. BE CAREFUL, HAVE A FULLY CHARGED BATTERY, TAKE YOUR TIME AND HAVE NO DISTRACTIONS!)
Make sure that you fully read the whole Rooting Procedure 3 times before you attempt it.
ROOTING ........
I rooted from the link below.
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
There is a lot of info on the above linked page.. below are the lines from where i started and stopped. I did no more than what is in between the following start and end lines. (you can just search for the text on the page to find quickly)
STARTING FROM THE LINE: Rooting the Vision (G2/DZ) and DHD
ENDING ON THE LINE: Did it work? Here's what you're looking for:
YOUR G2 SHOULD NOW BE ROOTED AT THIS POINT BEFORE CONTINUING ON.
......................................................................................................
......................................................................................................
BACKING UP SWYPE
DOWNLOAD ASTRO FILEMANAGER FROM THE MARKET.
There are 2 files you must copy from phone memory to SD card.
These files are "Swype.apk" and "libSwypeCore.so"
The apk file is located in /system/app and
the so file is located in /system/lib
Both of these locations are in the phone memory an not the SD card.
You just copy and paste to get them to your sd card.
MAKE SURE YOU DO THIS IF YOU DON'T WANT TO LOOSE SWYPE.
BACKUP WI-FI CALLING AND QUICK OFFICE
Both files are located in /system/apps (on phone memory)
Copy the following 2 files to your SD card
WI-FI Calling install file - "MS-HTCVISION-KNT20-02.apk"
QuickOffice install file - "Quickoffice.apk"
......................................................................................................
AFTER THE PHONE HAS BEEN SUCCESSFULLY ROOTED AND YOU REMEBERED TO GRAB THE 2 SWYPE FILES
INSTALL ROM MANAGER....
Go to the market and install ROM Manager. Start Rom Manager.
Select "Flash ClockworkMod Recovery" (v2.5.1.3) when it is done installing
select "Reboot into Recovery" to make sure it works. Once in recovery highlight and select "reboot system now" After phone has booted back up, proceed with steps below.
......................................................................................................
DOWNLOAD CYANOGEN ROM 6.1.1 ......
http://forum.cyanogenmod.com/files/file/186-update-cm-611-vision-signedzip/
DOWNLOAD GOOGLE APPS FILE.....
http://forum.cyanogenmod.com/files/download/152-google-addon-hdpi-20101114/
(I would recommend only downloading this from cyanogen and nowhere else. There is a corrupt version floating around on a few different sites with the same name.)
TO INSTALL CYANOGEN MOD.....
1Connect your phone to PC and mount the SD card. Copy the cyanogen mod file and the google apps file to the root of the G2's SD card.
(update-cm-6.1.1-vision-signed.zip and gapps-hdpi-20101114-signed.zip)
2Boot your phone into Recovery
(While in recovery highlight & select with optical trackball)
3Select "backup and restore" then select "backup"
(This will backup your stock OS, Apps and Data from phone to sd card)
4Select "wipe data/factory reset" Scroll down to "Yes -- delete all user data"
5Select "install zip from sd card" then select "choose zip from sd card"
then scroll to the cyanogen mod file (update-cm-6.1.1-vision-signed.zip) and select it. When the process is complete press the back button to go back to the main recovery menu and select "reboot system now"
6You need to install the google apps now. After the phone boots up with cyanogen, reboot the phone back into recovery. Select "install zip from sd card" then select "choose zip from sd card" then scroll to the google install file (gapps-hdpi-20101114-signed.zip) and select it. When the process is complete press the back button to go back to the main recovery menu and select "reboot system now"
7Restore Swype
Copy from the SD card (it is on your SD card wherever you put it) "libSwypeCore.so" to /system/lib (which is phone memory. I used an app called RootExplorer from the market. I needed to use that to make the /system/lib directory writable. When you first start RootExplorer, the superuser app will pop up a permission box. Make sure you select "allow" or this won't work.)
Then go in astro filemanager, navigate to "Swype.apk" (it is on your SD card wherever you put it) and tap it to install.
Now you need to make Swype active..
- (from the home screen) Select "MENU" then "Settings" then "Language & keyboard"
- Tick on Swype
- Go to your text messaging app (make sure physical phone keyboard is closed)
- Tap in the text box to type a message.
- Long press on text entry box and select "Input method"
- Then select Swype
You will then have your Swype back.
8 Restore WI-FI Calling if it isn't already installed.
go in astro filemanager, navigate to "MS-HTCVISION-KNT20-02.apk" (it is on your SD card wherever you put it) and tap it to install.
9 Restore Quick Office.
go in astro filemanager, navigate to "Quickoffice.apk" (it is on your SD card wherever you put it) and tap it to install.
.........................................................................................................
WHEN YOU HAVE YOUR PHONE ALL SET UP JUST THE WAY YOU WANT, DO YOURSELF A FAVOR..... REBOOT TO RECOVERY AND RUN A BACKUP.
*************************************************
Enjoy your fixed bluetooth
Wow, what a lot of crap to fix someones mistake......
*************************************************
I just flashed a new ROM and now the Bluetooth works like it should. Gingervillian 1.5 awesome.
Sent from my HTC Vision using XDA App
I appreciate your detailed explanation! I am a complete noob. I just rooted my g2 a few days ago and trying to read as much as I can and get up to speed.
I do have a question for you as far as backing up swype and other apps. Can you just use titanium backup to back up your apps like swype, quickoffice etc? Thanks in advance.
I was thinking of doing your method mentioned above as well as using titanium backup just because I'm paranoid about losing apps/bricking my phone, etc. Trying to be as careful as possible.
(Backed up and still running stock rom on rooted g2, have installed oc kernel after backing up)
Well, I've been using InsertCoin-Vision v1.3 ROM (which in my opinion are among the bests) on my T-Mobile G2. With this ROM and with VIRTUOUS FUSION ROM by rmk I have no problems with the bluetooth A2DP.
Nevertheless, I had a A2DP bluetooth problem (reported here forums.t-mobile.com/t5/T-Mobile-G2/Post-OTA-Update-BlueTooth-issue/td-p/542367): when I connect my phone to the car stereo player (JVC AVX-33) thru bluetooth A2DP the audio cuts out and skips all the time when the music is playing (I use PowerAmp application). It happens with almost ALL ROMs, no matter if it's stock, CM6, CM7, xboarders or RMK's (Virtuous G-Lite for example)... except with the VIRTUOUS FUSION and InsertCoin-Vision (v1.2 or 1.3) !!!!
Well, I'm very happy about this fact, but I'd like to know if you could explain to me the difference between Virtuous Fusion or InsertCoin-Vision (where the problem is solved) and Virtuous G-Lite or Cyanogen7 (where the problem occurs) in terms of bluetooth libs, config, etc., that could have solved that problem.
By the way, I used to listen music with the same car stereo and my old Motorola Milestone and I had no problem at all.
Thanks in advance and excuse me to bother you with this kind of question.
Best regards,
Tiago Peixoto.
My problem is that my cars headunit will not automatically connect to my phone or visa versa. i have to manually connect the phone to the car. Its really anoying. Now that I have perm root I have been testing several ROMs and have yet to find one that will actually fix the problem mentioned throughout this post. I just installed the Virtious Unity ROM but have yet to see if the problem is gone. With the Virtious Sense ROM I still had the same problem.
@ iagocpeixoto I've had the same issue with the audio cutting in and out in the past on stock ROM. The problem was that WiFi was also enabled. Its weird but disabling WiFi will eliminate that fading in and out while listening to audio through Bluetooth.
Dear Forum members!
Today I wanted to modify the smiles in the Mms.apk system app..
when i Copied back and tried to isntall, my phone started to reboot and not come back... (I know of course I mistake
From ADB I fixed my phone but just a half success, I copyed back the original Mms.apk and changed the permissions to 644, my phone boots up normally, but I still can't install the apk.. if i try to isntall from system/app it says: Replace app.. (I dont see in any list to be installed) If I press Ok, starting to install, then says: X App not installed. In downloaded apps I see messaging with 0 kilobytes, i can remove. After this if i try to install from system/apps it dont want to replace but the same thing happens... (X App not installed) Another interesting thing. On my Sd folder I still have a copy of Mms.apk, if I enter into this directory withy any file explorer, its quit I have ftp server where i can rename to mms.app -for example. In this case the explorers are not quit But I have no chance to install like user and not like root?..
Of course i have rooted my phone and it works.
Is someone have any idea?
thanks: Karoly
Please help me
I installed to my phone a catlog to read out what happens durring the installation.. I see in the log there is no odex file in the mms.apk ... Is someone can suggest me a solution to install back my factory mms application? I really don't want to reinstall my system because of this problem. Currently I use the latest android update 4.1.2. I have too much settings and apps on the phone :S
Thank you in advance.
Greets: Karoly
If your on a stock Google ROM (Yakju?) you should be able to download the factory image and fastboot flash just the system.img & your apps & data should be fine.
Hi. Thanks your answer.
I tried to flash only the system yesterday, wipe caches and fix permissions, my datas remained, but the mms app still not works.. nothing changed. Is it possible maybe to install this apk from recovery (cwm) mode?
Im sure if i reflash everything will work but i dont want to lose my apps, so i'd like to fight for it if its possible
Sent from my Galaxy Nexus using xda app-developers app
CM 10.2
Issue:
No BT call.
Broken audio in VOIP (viber,skype,teamspeak etc). Tinyalsa would fix that, but it breaks calls. ( Read this)
Mic key (voice search) works, you need to enable: settings -> system -> hardware keys -> enable custom actions (check) and app switch set to voice search.
To get home key logn press action: settings -> system -> hardware keys -> enable custom actions (check) and home key (long press) set to Recent app switcher
When you upgrade, phone app may not work, you must remove the shourtcut, and readd. (thanks scotte9999)
Sometimes it stuck boot logo (cm,samsung,roger), or boot loop, try to remove battery and wait 4-5minutes, or flash stock ICS with odin, and try again. (report back if any of those works)
Liblight works very simple, when your lcd birghtness low buttons and keyboard light is on. You can use qwertyled or other liblight,read more.
Slow storage performance in some apps.
Camera doesnt put exif orientation to the jpeg.
Report issue, bugs
Always try it with clean (full wipe) install before post issue. Dont send PM, I wouldnt reply.
Download ( http://dualhoki.vim.hu/bubor/dev/10.2/ ) :
nightly:http://dualhoki.vim.hu/bubor/dev/10.2/nightly ( for mirror replace hostname to rpi.bubor.hu )
OLD release:http://dualhoki.vim.hu/bubor/dev/10.2/M1 ( for mirror replace hostname to rpi.bubor.hu )
Release:http://dualhoki.vim.hu/bubor/dev/10.2/RC1 ( for mirror replace hostname to rpi.bubor.hu )
Linaro test build, include usb serial console: http://dualhoki.vim.hu/bubor/dev/10.2/linaro
Bigger gapps http://dualhoki.vim.hu/bubor/dev/gapps-jb-4.3-full.zip , rom has a minimalized gapps, you might need something (for example talkback)
Changelog
20130826: first release
20130827: fix phone call
20130827-2: include tonyp's gapps package. https://github.com/tonyp/android_vendor_google
20130828: update ril.h, it should fix call issue
20130902: selinux, facelock
20130904: keyboard light
20130905: filemanager fix (total commander see storages)
20130911: phone encypt support
20130913: BT LPM support, overclock support
20130924: update cm-10.2
20130926: replace charger to the old one.
20131002: www/com key
20131007: update cm-10.2
20131014: keyboard arrow bug
20131022: disable fsync via sysfs ( echo 0 >/sys/module/sync/parameters/fsync_enabled )
20131028: torch fix (quick settings etc)
20131028 second release: vibration intensity settings -> (device) more -> Vibrator intensity
20131104 usb storage mount fix
20131109-m1: sdcard removable, dynamic_fsync, fsync_enabled removed, some sdcard performance improve
20131110-m1: fix traffic indicator arrows
20131113-m1: update gapps (gmaps, google play store), include recovery
20131126-m1: removed _ofline_ charger (probably nobody used)
20131204-rc1: update to rc1
20140225: update to CM 10.2.1
Cm 10.2 changelog
http://review.cyanogenmod.org/
Install:
I use TWRP, but CWMR would work too. Use latest modem ( UCLJ3
You need only one zip, gapps included.
Full wipe.
Install from recovery.
reserved
Can I install top of my old rom?
You always could do that, but you must do clean install when report bog.
can´t swap SDCards
edit /sysrem/build.prob and add:
Code:
# Change to 1 for swapping SD cards
persist.sys.vold.switchexternal=1
below
Code:
# Storage configuration
ro.vold.switchablepair=/storage/sdcard0,/storage/sdcard1
You can use recovery installable zip: http://dualhoki.vim.hu/bubor/dev/swap-internalsd-externelsd.zip
gyroscope fix
power off the phone (better remove battery for sure), put on a desk, power on and wait, it shoud calibrate itself.
Fix skype audio
Read this. It will break your call sound, Incoming calls work fine with ring tone on.
Slow io performance
type as root:
echo 0 >/sys/module/sync/parameters/fsync_enabled
You can place in /system/etc/init.d/S99fsync file this code, chmod 775 /system/etc/init.d/S99fsync , Settings will persist, until reinstall the rom.
Its disable fsync, what makes it faster, but you would lost date on crash. Internal sd card was 1.2M/sec, after 6.2M/sec removed in 20131109
Credits:
* tonyp https://github.com/tonyp/android_vendor_google
* Epsylon3 https://github.com/tpruvot/android_device_samsung_i9103
* kick buttowski
* Adam77Root
* yohan4ws
* gtmaster303
* The-Covenant team
* dman3285
* thegreatergood
* spyke555
That's awesome man, good work.
Sent from my SGH-I927 using XDA Premium 4 mobile app
taiber2000 said:
That's awesome man, good work.
Sent from my SGH-I927 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
how about the bluetooth headset? Is it working?
Thanks, bubor! I'm going to try it out today and report any issues I encounter.
dr.mefisto said:
how about the bluetooth headset? Is it working?
Click to expand...
Click to collapse
Read first post, BT call doesnt work, but mp3 playing with headset works.
well, sorry I really don't know how did I skept this
SIM not detected, but I can make calls and send and recive SMS
edit
No service, insert SIM and reboot
I noticed that the Phone app as well as Local and Navigation apps aren't available. I'm re-downloading the zip and will do a fresh reinstall. Steps I took to upgrade from CM10.1.2:
Using CWM
1) Copy CM10.2 zip to sdcard
2) Backup
3) Wipe data/factory reset
4) Wipe dalvik cache
5) Install CM10.2 from zip
6) Restore data (advanced restore -> restore data)
7) Reboot
All user installed apps were upgraded upon first boot. And they seem to work fine. Even Gmail and Maps works. I can receive calls, and I can make calls from the People app. But when I tap on the Phone app, a message states that the app is not installed. In addition, there is no Local or Navigation app in my app list.
Using CWM
1) Copy CM10.2 zip to sdcard
2) Wipe data/factory reset
3) Wipe dalvik cache
4) advanced/ wipe davlin cache
5) formar sistem
6) instal from sd card
7) reboot
Calls work well for me
Sent from my SGH-I927 using xda app-developers app
dEhiN said:
I noticed that the Phone app as well as Local and Navigation apps aren't available. I'm re-downloading the zip and will do a fresh reinstall. Steps I took to upgrade from CM10.1.2:
Using CWM
1) Copy CM10.2 zip to sdcard
2) Backup
3) Wipe data/factory reset
4) Wipe dalvik cache
5) Install CM10.2 from zip
6) Restore data (advanced restore -> restore data)
7) Reboot
All user installed apps were upgraded upon first boot. And they seem to work fine. Even Gmail and Maps works. I can receive calls, and I can make calls from the People app. But when I tap on the Phone app, a message states that the app is not installed. In addition, there is no Local or Navigation app in my app list.
Click to expand...
Click to collapse
you should try without restore data just pure install.
bubor said:
you should try without restore data just pure install.
Click to expand...
Click to collapse
Ok I'll try that tonight. Thanks. Last night I tried several times and each time I had the same result. I finally just did a complete wipe and restore of all from the backup I had made prior to trying the 10.2 upgrade.
dEhiN said:
All user installed apps were upgraded upon first boot. And they seem to work fine. Even Gmail and Maps works. I can receive calls, and I can make calls from the People app. But when I tap on the Phone app, a message states that the app is not installed. In addition, there is no Local or Navigation app in my app list.
Click to expand...
Click to collapse
You should read https://plus.google.com/+CyanogenMod/posts/VKPtc7DEYQy
Facelock is absent
Hello.
I'm did clean installation of this ROM and found that Facelock option in screen lock dialog is absent. Is there any way to add it? Can Gapps installation fix this issue?
And is there any way to speed up PicSphere rendering? It takes over 30 minutes for full sphere (64 photos).
Thank You.
scotte9999 said:
You should read https://plus.google.com/+CyanogenMod/posts/VKPtc7DEYQy
Click to expand...
Click to collapse
Thanks scotte9999! I thought I had checked the all apps list (app drawer) and couldn't find the phone app but I'm going to do the upgrade again and check it out.
Hey bubor, sorry I could not make a reply back "in time" in the other thread, this 2 weeks were crazy for me; I think that the request for logcat from the first build of cm10.2 is now moot. Focal works, wifi works, I have been rocking it with your build (again, dirty flashed 20130828 i live dangeourly but with my backups on the sdcard).
- Feels Barry White smooth.
- Total commander now only sees the internal SDcard by default, I can still access it manually, but it is not "mounting" in the first screen the /mnt/sdcard1 I'm currently trying to google if this is a total commander issue or related to jb 4.3 or cm 10.2. I cant even find a workaround to manually add it, yet. Anyone else using TC and is now missing the external sd in the main screen?
- Made and receive phone calls as usual, used BT for music with my headset, used the in-ear wired too (the original ones). (also I never could figure out what the button on the mic does other than it is context based),
Overall, the things I use and do with it, so far they work great.
Awesome! I thought my glide would be stuck at Android 4.2, thanks for working on this!
I'll be trying this firmware out as soon as possible.
xtacb4 said:
Hey bubor, sorry I could not make a reply back "in time" in the other thread, this 2 weeks were crazy for me; I think that the request for logcat from the first build of cm10.2 is now moot. Focal works, wifi works, I have been rocking it with your build (again, dirty flashed 20130828 i live dangeourly but with my backups on the sdcard).
- Feels Barry White smooth.
- Total commander now only sees the internal SDcard by default, I can still access it manually, but it is not "mounting" in the first screen the /mnt/sdcard1 I'm currently trying to google if this is a total commander issue or related to jb 4.3 or cm 10.2. I cant even find a workaround to manually add it, yet. Anyone else using TC and is now missing the external sd in the main screen?
- Made and receive phone calls as usual, used BT for music with my headset, used the in-ear wired too (the original ones). (also I never could figure out what the button on the mic does other than it is context based),
Overall, the things I use and do with it, so far they work great.
Click to expand...
Click to collapse
Have you tried to use the bluetooth to transfer files? Like mp3s from the Captivate Glide to another device?
EpicMikeNC said:
Have you tried to use the bluetooth to transfer files? Like mp3s from the Captivate Glide to another device?
Click to expand...
Click to collapse
Just one file, that same wednesday, I was at a new client's, I shared him an apk via BT (because the wifi was down) to a Samsung Galaxy Note, no problems at all. Have you had problems with BT file transfer?
xtacb4 said:
Just one file, that same wednesday, I was at a new client's, I shared him an apk via BT (because the wifi was down) to a Samsung Galaxy Note, no problems at all. Have you had problems with BT file transfer?
Click to expand...
Click to collapse
No, I ask because I'm planning a trip to Mexico and I need a SIM phone. I already have the Gravity 2 unlocked, but I've always been fascinated with this phone as well as the Galaxy Relay 4G. The Captivate Glide is turning into the little engine that could so I'm keeping an eye on any progress made on the ROM front for this phone.
Or for another $100 I could get a Galaxy S4 I9505 clone and just buy a bluetooth keyboard, but...kinda don't want to go that route (I'd rather get a REAL I9505). Plus the Glide is fairly cheap, under $200 at NewEgg. Its the discontinued phone that...continues.
I've been going nuts on the latest CM11 nightly 4.4.2 with the camera not being able to save its pictures to your sd card automatically and also multiple crashes...some fixes I found, writing new permissions mostly just didn't work or wouldn't stick if you rebooted.
I now have 2 different optional APK file and INSTALL fixes...1st is just the camera apk which I ripped out of the liquidsmooth cm based kitkat 4.4.2 which works flawlessly. The 2nd is a gallery apk fix that I ripped out of the slimbean 4.3.1 rom and it reinstalls the gallery apk which also has its own camera that will install along with it...both fixes work, both camera's are slightly different from each other though and function differently based on the gallery that is installed
This method requires Titanium Backup...you can get it on the play store and the free version will work just fine
HERE'S THE CAMERA APK FIX:
-backup your systems "camera" app before doing anything! don't blame me for losing the camera if something fails
-once backed up, uninstall the camera app and if using titanium backup, move the backup files to another location out of the titanium folder located in your INTERNAL storage
-download the camera zip files I made here
-extract the zip file and you'll get a folder named "camera files"...copy and paste the files inside, do not extract any of these files, to your titanium backup folder located on your INTERNAL storage
-once copied over, open up titanium backup and look for the camera apk file with a line through it and should say beneath it "1 backup"...click on it, hit restore and choose app and data, that's it! it should now be there and fully functioning
HERE'S THE GALLERY APK FIX:
-backup your systems "gallery" and "camera" apps before doing anything! I won't be held responsible if this doesn't work for some users
-once backed up, uninstall the gallery and camera apps
-download the "com.android.gallery3d_1.1.40012.apk" file I made here
-install the apk file by simply clicking on it and choosing install, it shouldn't need any special permissions but if so, refer to next step
-install the gallery apk by using a root file manager (I use root browser lite) and move the apk file to system>app, change the permissions to rw-r--r-- then select "ok" and then install it and reboot. after reboot, you should now have your gallery back and a newer camera icon that is darker gray in color with a dark blue center camera lense, open the camera app
-go to it's settings>more settings and to the right you'll now see an sd card icon, click and select the sd card and test it out!! that's it
video of using root browser lite to change permissions...in the video, it's a silent screen recorded guideline, my app was already installed, so I highlighted the options that show how to change the permissions and then when I highlighted showing "cancel/view/uninstall", if it wasn't installed the option would say "cancel/view/install"
https://www.youtube.com/watch?v=Uow9OyLVGRI&feature=youtube_gdata_player
*Newly added!!*--reinstalling sprint zone and voicemail
to install, follow the exact same steps as installing the camera/gallery apk files
-voicemail apk link: com.coremobility.app.vnotes
-sprint zone apk link: com.sprint.zone_4.6.017
if this worked for you, please post up and let us all know
giving this thread a bump...i revised the apk installation steps since redoing this process after a few updates of cm11, they fixed the camera as far as adding the option for sdcard storage but I've been getting a lot of hang ups and crashes then "unable to retrieve camera" error messages when trying to open back up, even after a reboot.
I even installed today's release of the cm11 nightly and the camera was a crashing mess over and over, so for any having these camera issues, here you go!
im wondering if i will ever be able to use the sprint voicemail. since i loaded carbon 4.4.2 and wondeing if there was any way of making it easy to make a call from your messaging by just sliding either right or left instead of tapping?
using sph-l710
villaf7420 said:
im wondering if i will ever be able to use the sprint voicemail. since i loaded carbon 4.4.2 and wondeing if there was any way of making it easy to make a call from your messaging by just sliding either right or left instead of tapping?
using sph-l710
Click to expand...
Click to collapse
yes you can! I have done this already, I installed the voicemail and sprint zone apps on my cyanogenmod 11 4.4.2 and they work...I'll make apk's for them as well and post them up, give me a few
edit...all uploaded for you my man, just do exactly the same as I noted doing for the gallery app installation, where to place it and changing the permissions, any issues post back up
Just wanted to say, tried most if not all AOSP roms and for some reason all of them freeze when switching back and forth. This is the only one that works 100%.
Thanks for the find.
ssmercurys said:
Just wanted to say, tried most if not all AOSP roms and for some reason all of them freeze when switching back and forth. This is the only one that works 100%.
Thanks for the find.
Click to expand...
Click to collapse
you're welcome and thanks for posting that it works! I kept having the same issues with the cameras on the cm11 and 10 roms, this 1 never failed me
Just a heads up, the stock camera in slimkat (4.4.2 ROM) works perfectly, the devs fixed it on that rom
Sent from my SPH-L710 using Tapatalk
noles4life50 said:
Just a heads up, the stock camera in slimkat (4.4.2 ROM) works perfectly, the devs fixed it on that rom
Sent from my SPH-L710 using Tapatalk
Click to expand...
Click to collapse
awesome, this camera apk I have listed here is from the slimbean 4.3.1 rom which is probably why it works perfectly on 4.4.2 slimkat, same devs
thanks working on att gs3 on metropcs running unnofficial Beanstalk 4.4.2 rom 20140206 release... fix "cant connect to camera" error. Thanks again
Thanks so much! I first created a backup. I used root explorer for the whole thing. I tried uninstalling via TiBu first, but it didn't actually remove the camera and gallery apks. I then tried ES File Explorer, but that requires you to set root to Apps and ADB, and I had deselected ADB some time ago.. I downloaded the apk and copied it to /system/app. I then manually deleted the two apks, changed permissions on your apk and installed. Rebooted and works wonders. Thanks!
I would like to suggest a n00b-oriented, step-by-step guide.
1. Use your favorite recovery manager and back everything up. This way, you can always go back if you mess something up.
2. Download and install Root File Explorer (Free).
3. Launch Root File Explorer. It will ask to download and install a few tools. Let it.
4. Go to where you downloaded the file (probably sdcard/Download). Hold your finger on the name and select copy.
5. Press the "Home" icon on the bottom left of the screen.
6. Click on the folder named "system" and then click on the folder named "app".
7. Select paste to copy the file here.
8. Press and hold the newly copied file, and select "Permissions".
9. Set the permission to rw-r--r--, or 0644. In other words, select "Read" for all three, and then select "Write" for Owner. Everything else should be unchecked, and hit OK.
10. Scroll down and fine GoogleGallery.apk and GoogleCamera.apk. Select GoogleGallery.apk and press uninstall. Then long press the apk and delete it. Do the same for GoogleCamera.apk.
11. Find the new apk that you just downloaded (com.android.gallery3d_1.1.40012.apk) and press it. Select install.
12. Once installed, back out of everything and reboot your device. When the device reboots it will say it is updating 1 application.
13. You are now rebooted with the new, fixed, camera. The icon is now darker, and with a blueish/purpleish lens.
14. No, none of your files have been deleted. Enjoy your working camera!
15. Check out the new options! In the extended settings, you can now click on the SD card icon and instantly select to use your internal storage or your external SD card (if present) to save your photos to!
16.Give goku2778 your Thanks!
Is there a way to disable the shutter sound?
LaRocky said:
Is there a way to disable the shutter sound?
Click to expand...
Click to collapse
unfortunately no it doesn't have that option. I did however find another camera apk that works, gonna upload that and link in here around 10am eastern time this morning.
thread bump...newly added camera only apk and revised a bit of the initial part of the guide...enjoy!!
goku2778 said:
unfortunately no it doesn't have that option. I did however find another camera apk that works, gonna upload that and link in here around 10am eastern time this morning.
Click to expand...
Click to collapse
Found this out last night, the camera that comes with the Gummy Nightly (AT&T Galaxy S3 Android Development forum) comes with a camera that has more settings and the shutter sound can be disabled via the android system settings/sound options. I don't know if the shutter sound option is always there in system settings as I didn't check the previous roms.
LaRocky said:
Found this out last night, the camera that comes with the Gummy Nightly (AT&T Galaxy S3 Android Development forum) comes with a camera that has more settings and the shutter sound can be disabled via the android system settings/sound options. I don't know if the shutter sound option is always there in system settings as I didn't check the previous roms.
Click to expand...
Click to collapse
the other camera I listed does have more options to it if you wanna give it a try, can't hurt none, actually let me try it on mine right now see about the shutter sound....
nope, shutter stays on, it just gives the option to make the power button shutter (take the pic)...sorry man, I could care less about the shutter sound myself lol if I come across another 1 i'll bump this again, maybe I can find that gummy camera apk online and test it out
goku2778 said:
the other camera I listed does have more options to it if you wanna give it a try, can't hurt none, actually let me try it on mine right now see about the shutter sound....
nope, shutter stays on, it just gives the option to make the power button shutter (take the pic)...sorry man, I could care less about the shutter sound myself lol if I come across another 1 i'll bump this again, maybe I can find that gummy camera apk online and test it out
Click to expand...
Click to collapse
Thank you, I'll have to try it out. I have verified that the Shutter Sound option (under System Settings/Sound) is not available in another rom (Liquid Smooth) so it looks like the developer has to manually add the option (not built in to the camera). And Liquid Smooth's camera settings are detailed.
LaRocky said:
Thank you, I'll have to try it out. I have verified that the Shutter Sound option (under System Settings/Sound) is not available in another rom (Liquid Smooth) so it looks like the developer has to manually add the option (not built in to the camera). And Liquid Smooth's camera settings are detailed.
Click to expand...
Click to collapse
been wanting to try that rom out myself, maybe I'll install that today and check out the camera...and then, rip it out also lol I'll bump the thread again if I do that
edit...so I've been to liquidsmooth and back lol same exact camera as the 1 I added yesterday, only differences is the system settings with more options like disabling the shutter sound. so I guess just stay on that rom for now for the shutter options, I tried lol
Trying to do this fix on beanstalk on my galaxy s3, and when I try to install, I'm getting a parsing error. Any idea when I'm doing wrong?
I've backed up and uninstalled my original camera app, and moved the first linked camera app into my system/app folder. Changed the permissions to rwrr,and then when I try to install I get the parsing error.
Gareee said:
Trying to do this fix on beanstalk on my galaxy s3, and when I try to install, I'm getting a parsing error. Any idea when I'm doing wrong?
I've backed up and uninstalled my original camera app, and moved the first linked camera app into my system/app folder. Changed the permissions to rwrr,and then when I try to install I get the parsing error.
Click to expand...
Click to collapse
weird...try this then, delete that out of the system folder, download it again and just open it and hit install, see what happens then...is this beanstalk 4.3 or 4.4? if it fails again, try the 2nd optional fix, that has been the more all around solid fix so far for both 4.3 and 4.4 roms
Gareee said:
Trying to do this fix on beanstalk on my galaxy s3, and when I try to install, I'm getting a parsing error. Any idea when I'm doing wrong?
I've backed up and uninstalled my original camera app, and moved the first linked camera app into my system/app folder. Changed the permissions to rwrr,and then when I try to install I get the parsing error.
Click to expand...
Click to collapse
Try this:
Uninstall stock camera.
Reboot.
Install goku camera apk.
Change permissions.
Convert to system app with titanium backup.
Reboot.
Hope this help
Sent from my SAMSUNG-SGH-I747 using xda premium
So, like the title says, I can't seem to access my call recording folder after updating to Android 12 last night. It appears to have removed my Oneplus dialer (installed as an apk and recording enabled through joneplus tools). The filepath itself (/storage/emulated/0/android/data/com.oneplus.communication.data/files/record/) doesn't show up in Solid Explorer, but I did have a shortcut created and when I select it I get Access Denied (attached screenshot).
I can't tell if the files are still there and just not accessible, or if they were deleted (surely not since its on the emulated SD card).
I've tried to reinstall the OP Dialer APK (several, actually), and they all say it won't install because it is not compatible with the phone. For reference, I am unrooted and unmodified, LE2125 model. I'm not new to rooting and modding, but this is my first OP phone. I've tried to keep it stock for work purposes and trying to avoid a bunch of Magisk effort to keep my work email on the phone and working.
Am I just out of luck? Is there any way to retrieve the recordings that were present before the upgrade? I assume the file directory is still there, but 'erased' from the update and will require installation of the OP dialer to show up again. But, i can't find a OP dialer APK that will install successfully on OS 12.
Any help or advice in retrieving the files would be greatly appreciated!
Mark
UPDATE:
Persistence pays off. I kept trying to find an updated OP dialer that would work on OS 12. I finally got one to install (from Techibee/Telegram) but it did not recreate the 'com.oneplus.communication.data' directory. I deleted and reinstalled Joneplus Tools, which took some work to grant the write permissions again, and it also did not recreate the directory even after enabling call recording (strangely, it seems to have enabled recording in the Google dialer instead - I'll make a separate post about that because I still need call recording). But, on a whim, I went back into Solid Explorer and recent files... LO AND BEHOLD THE CALL RECORDINGS WERE SHOWN!! So, I long-pressed a file and selected "open directory" and discovered that the OTA update to OS 12 created a \Recordings\Call Recordings\ sub-folder in my Music directory and copied all of my phone call recordings there... very strange, but I'm glad they are not gone and I can access them again to back them up before something else happens. I appreciate the response below from @Effizio01 but the issue is now resolved. As noted above, I will make a separate post about Google Dialer recording as a test call said it recorded but I cannot locate the file. Thanks for all the views and "moral support".
mawoods75 said:
So, like the title says, I can't seem to access my call recording folder after updating to Android 12 last night. It appears to have removed my Oneplus dialer (installed as an apk and recording enabled through joneplus tools). The filepath itself (/storage/emulated/0/android/data/com.oneplus.communication.data/files/record/) doesn't show up in Solid Explorer, but I did have a shortcut created and when I select it I get Access Denied (attached screenshot).
I can't tell if the files are still there and just not accessible, or if they were deleted (surely not since its on the emulated SD card).
I've tried to reinstall the OP Dialer APK (several, actually), and they all say it won't install because it is not compatible with the phone. For reference, I am unrooted and unmodified, LE2125 model. I'm not new to rooting and modding, but this is my first OP phone. I've tried to keep it stock for work purposes and trying to avoid a bunch of Magisk effort to keep my work email on the phone and working.
Am I just out of luck? Is there any way to retrieve the recordings that were present before the upgrade? I assume the file directory is still there, but 'erased' from the update and will require installation of the OP dialer to show up again. But, i can't find a OP dialer APK that will install successfully on OS 12.
Any help or advice in retrieving the files would be greatly appreciated!
Mark
Click to expand...
Click to collapse
I installed oneplus dialer compatible with a12 with recording calls enabled but when i receiving a call i have Google dialer in the screen and oneplus dialer icon at left . If i touch che oneplus icon it displayed over Google .
Sorry my bad english
mawoods75 said:
So, like the title says, I can't seem to access my call recording folder after updating to Android 12 last night. It appears to have removed my Oneplus dialer (installed as an apk and recording enabled through joneplus tools). The filepath itself (/storage/emulated/0/android/data/com.oneplus.communication.data/files/record/) doesn't show up in Solid Explorer, but I did have a shortcut created and when I select it I get Access Denied (attached screenshot).
I can't tell if the files are still there and just not accessible, or if they were deleted (surely not since its on the emulated SD card).
I've tried to reinstall the OP Dialer APK (several, actually), and they all say it won't install because it is not compatible with the phone. For reference, I am unrooted and unmodified, LE2125 model. I'm not new to rooting and modding, but this is my first OP phone. I've tried to keep it stock for work purposes and trying to avoid a bunch of Magisk effort to keep my work email on the phone and working.
Am I just out of luck? Is there any way to retrieve the recordings that were present before the upgrade? I assume the file directory is still there, but 'erased' from the update and will require installation of the OP dialer to show up again. But, i can't find a OP dialer APK that will install successfully on OS 12.
Any help or advice in retrieving the files would be greatly appreciated!
Mark
UPDATE:
Persistence pays off. I kept trying to find an updated OP dialer that would work on OS 12. I finally got one to install (from Techibee/Telegram) but it did not recreate the 'com.oneplus.communication.data' directory. I deleted and reinstalled Joneplus Tools, which took some work to grant the write permissions again, and it also did not recreate the directory even after enabling call recording (strangely, it seems to have enabled recording in the Google dialer instead - I'll make a separate post about that because I still need call recording). But, on a whim, I went back into Solid Explorer and recent files... LO AND BEHOLD THE CALL RECORDINGS WERE SHOWN!! So, I long-pressed a file and selected "open directory" and discovered that the OTA update to OS 12 created a \Recordings\Call Recordings\ sub-folder in my Music directory and copied all of my phone call recordings there... very strange, but I'm glad they are not gone and I can access them again to back them up before something else happens. I appreciate the response below from @Effizio01 but the issue is now resolved. As noted above, I will make a separate post about Google Dialer recording as a test call said it recorded but I cannot locate the file. Thanks for all the views and "moral support".
Click to expand...
Click to collapse
Hey there awaiting updtes frm ur emd, i have a call recording issue too, managed to get op dialer which support oxygen 12 but even shows the calls veing recorded but unable to locate files and also doesnt show anything in settings , is there any foolproof workaround to record calls without voiceover notification ??
Thanks