So I finally got CM7 (Nightly build 111 as 112 seems to make MMS stop working) to load to my Fascinate and it's been working great.
Bluetooth connects and disconnects are a thing of the past it all just works.
However since going to CM7 the Driving Mode option is gone and I cannot seem to find a way to get it back.
I've search everything I can think of so maybe I'm searching the wrong word strings?
Any help in the right direction would be greatly appreciated.
Thanks!
Related
So I recently rooted my phone and was playing with some recommended flashes (captive camera, wifi tethering). After I did this I noticed that somethings on my phone are not working. 1 the brightness option not working every time I click on it I get a force close. 2 the system volume not working and 3 the ringer volume not working either. All these options I get a force close something along the lines of application settings and I have to force close. I unrooted my phone and same thing, I reset my phone and same thing . I have the baseband version t959uvji2 I have been trying to revert to stock kernel using odin3 but no luck it doesn't do anything. Any one have any idea how I can fix those 3 settings? And an easier way to go back to stock kernel as the phone it was shipped. T-Mobile is willing to change phone or I can wait for froyo to cone out and see it that fixes the problem but any ideas or pointers would be greatly appreciated.
adinis78 said:
So I recently rooted my phone and was playing with some recommended flashes (captive camera, wifi tethering). After I did this I noticed that somethings on my phone are not working. 1 the brightness option not working every time I click on it I get a force close. 2 the system volume not working and 3 the ringer volume not working either. All these options I get a force close something along the lines of application settings and I have to force close. I unrooted my phone and same thing, I reset my phone and same thing . I have the baseband version t959uvji2 I have been trying to revert to stock kernel using odin3 but no luck it doesn't do anything. Any one have any idea how I can fix those 3 settings? And an easier way to go back to stock kernel as the phone it was shipped. T-Mobile is willing to change phone or I can wait for froyo to cone out and see it that fixes the problem but any ideas or pointers would be greatly appreciated.
Click to expand...
Click to collapse
Check the BIBLE THREAD, Everything you need is there.
30Glock said:
Check the BIBLE THREAD, Everything you need is there.
Click to expand...
Click to collapse
no offense to the person that started the BIBLE THREAD but after looking over it and all over xda forums i did not get an answer to my problem but i did manage to fix my phone:
well i finally got it to work by watching this video on you tube:
1.go to you tube
2.search for flash vibrant
3.first video should be "Flashing Firmware with Odin on Samsung Vibrant" by ZDoomentral, its a 3:00 min video
(sorry can't post direct link but i am restricted since i am a new user)
had to pay attention as to how he gets his phone into DOWNLOAD MODE, thats where i was going wrong, and just followed the directions of the video.
my phone is up and running with stock kernel and re-rooted it
I was wondering if anyone could help me figure out what I did wrong.
All of a sudden my trackball has begun to act up. Its nothing major I just figure out what I must of hit or what setting I might of changed by accident.
Whats happening is that when I try to take a picture with the trackball it opens up a bluetooth menu and I dont have a bluetooth connected to the phone. Also the trackball scrolls fine but has been having issues selecting things in recovery.
I was wondering how I can fix this and I recently switched roms was on ginger tazz sre 27 but switched to aosp tazz v4 and I figured switching roms would fix it but it didnt. Thank you for any help.
I had trackball issues with my Eris as well. I was able to find a video on youtube giving step-by-step instructions on taking the Eris apart and cleaning the trackball. It has worked fine ever since. I was amazed how dirty the inside of the phone actually was. it ran much better once reassembled.
i have the galaxy for 5 monthes now..
switched tons or ROMs and kernels.
since i tried the 2.3.5 androidmeda(i think it started there) i have a problem answering my phone.
when someone call me i can slide it right in order to answer, the phone stop the ringtone like i answered but i cant hear anything hile the other side think someone answered him as he doesn't hear the tome anymore.
i tried to go back to KG5 but i cant get rid of it.
it got better as i changed the modem(used to be on KI4) to KE4 and KG5(the rom im with right now but its not good.i can answer but it takes 5-10 seconds before i see the call screen and able to talk properly.
tryied androidmeda,cognition,batista,xpower(the used to be),villain and so. none helped so i guess its not ROM related exactly.
Maybe some data was changed (such as the opening after trying androidmeda-the white turning cube and the android character insted of the samsung s 2 pic).
i tried various MODEMS in order to solve it but no progress yet.
anyone familiar with this problem?anyway to solve it?
Sounds like a hardware problem more than a rom problem. You have tried all them custom roms do its quite odd. Id say trying to go back to a full stock rom if you haddent already and maybe test out other voice features on the phone like voice record and the google voice search thing.
Sent from my GT-I9100 using XDA App
I have some problems with incoming Bt connections... For example, trying to send a file from my pc results in a "service not found" message.
Idea of how to fix this, without using apps like Bt file transfer and similar?
Sent from my Galaxy Ace on GLSMT 2.1 with XDA app.
Issue came after istalling new V6 Supercharger version (RC4). Nobody faced the same issue?
Edit: Posting this to help who may have the same problem (or not, who cares XP). Activating Bt just as soon as the phone boots up (before all apps/scripts/etc get loaded) makes it work correctly!
...though data connection won't work this way.
Wi-Fi works but no data. To have it run I have to reboot again without Bt (nor Wi-Fi) active.
I'm still trying to get to the point, because I really don't know how to get out of this (little but annoying) trouble.
Any help would be really appreciated, since I'd been blowing my mind on it in the past 2 days... >.>
So I have run in to a bit of a snag, and though I doubt it is ROM specific, I thought I'd start by asking here to see if anyone else has run across this and might have a fix
I first noticed it when I was running ShiftAO5P 3.2, and though I didnt specifically think 3.2.1 would fix it, I tried that, and now the problem has come back.
The gist of the issue is that if I havent used my phone to talk to someone for some unspecified length of time, when I call someone, they cant hear me. I can hear them just fine, but they can't hear anything from my end. If I hang up, and call right back, then it all works fine. Also, it is fine if they call me - works right away without having to re-make the call.
Like I said, I did a complete reload to get to 3.2.1(full wipe, and even reformatted sd card), and since I suspected the tiamat kernel and the call recorder app I had been using under 3.2, I didnt reload those pieces and stuck with just the stock 3.2.1
Everything seemed OK for about the first week or so, but now it is doing the same thing again.
I am guessing it is some app, but I have no idea how to try to chase it down.
I have a logcat that I just dumped right after the problem happened, but dont really know what process to look for.
Any suggestions? TIA!!!