Database Develop

[Q] Endless QPST frustration, native tether

Hello geniuses. I almost never post on XDA because I do my best to search, read, try/fail instead of asking questions but now I have one and can't find the answer- hope someone can help.
I'm trying to SIMPLY change the tethered nai address on my brother's (bored visiting the family) motorola droid (unrooted, stock AFAIK) to get his native tethering to work. I've done this multiple times before on my htc (wm6.1, 6.5, androided touch) and new Fascinate phone but his is a complete PITA.
His stats are: androud 2.2.1, baseband c_01.43.01.P kernal 2.6.32.0-g68eeef5 android [email protected]#1
Thus far, I have installed the moto usb drivers, and installed HW virtual serial port to interface with QPST (192.168.16.2, port 11008) . I can read/ write to the phone without problem EXCEPT it keeps reverting the tethered nai to [phone#]@dun.vzw3g.com. Even when I add a whole new profile, the new profile changes to add the @dun, regardless of whether it is an active profile. At first, I thought it wasn't writing at all but then finally thought to try adding a new one and it writes everything correctly EXCEPT adds the @dun to the tethered nai address.
SO, what gives? Is motorola more tightly locked down then everything else I've played with?

I'm having the exact same issue that you are having. I have no idea what could be causing it. Some friend told me to try to find the file that actually stores this data, pull it out (using adb) edit it in notepad or something and then push it back.
It actually makes sense but...if it's possible, which file could this be!?
Let's see if someone replies with a solution. In the meantime i'll keep investigating.

Dumb question, but are you guys putting the phone in diag mode (power off, hold 'T', and plug in the USB cable: the phone shouldn't acknowledge the USB cable)?
Sent from my Droid using XDA App

Bluetooth PAN tethering to an android phone - works! (CM7)

I don't have enough posts yet to put this on the developers side, but after digging through a lot of posts, I've pieced together how to tether my CM7 Nook to another android device, and figured a few folks would want to try it as well.
The particulars: On the Nook, I am running the nightly build 31 of CM7.
Whichever phone you want to use has to be rooted, and have the 'wireless tether' app installed. It also has to be able to use bluetooth PAN (as opposed to DUN). I think most android phones do, but my friends blackberry only supports DUN.
First, on the phone: Turn on Bluetooth, and then go to settings>About Phone>Status and write down the bluetooth address, which is six hex numbers separated by colons.
Next, still on the phone, launch wireless tether, and go to the settings page. Check the 'Use Bluetooth' checkbox. Make sure the 'discoverable' checkbox is ticked as well, then go back to the main screen, and press the 'press to start tethering'.
On the Nook, start bluetooth, go to bluetooth settings and scan for devices (if needed); you should see the phone appear on the 'bluetooth devices' list. Pair up with it by clicking on it. Both the Nook and the phone will pop up a PIN dialog, accept that, and you should be seeing 'Paired but not connected' status.
Next, still on the Nook, open a terminal window, and type the following commands (substitute the bluetooth address of the phone you wrote down, INCLUDING THE COLONS in place of the xx's below).
EDIT: before pand, you need root access; use the su command
pand --connect xx:xx:xx:xx:xx:xx
netcfg bnep0 up
netcfg bnep0 dhcp
setprop net.dns1 8.8.8.8
you should now have net access via the tether!
The pand is the configuration demon for the PAN protocol, and that first line ties the bluetooth phone to a network interface named bnep0
The netcfg command activates that interface, and gets an address dhcp'd to it.
and the setprop command sets the DNS (in this case to google's DNS server).
I know many have said they only have limited bluetooth range, but either they have fixed that, or I'm one of the lucky ones, I could still get data on my Nook with the phone almost 30 feet away!

Very cool. Do you notice packet slow down in data speeds the farther you are from the device.
My experience with BT audio is I could not listen to my audio file if I was more than 6" away from my device once I was 12" the signal would drop off/on.

Works well. Now to automate it.

Just did it. Works perfectly! Thanks for the tip. Wonder why the range is so much better tethering than with other accessories. Maybe because the nook is receiving instead of transmitting?
Sent from my NookColor using Tapatalk

Anyone know if this would work with an iphone?
From 1.1 Nook Color with 1.1 ghz overclock

Aw, I had pulled out my Blackberry and was looking up the Mac address before I read that it wouldn't work with Bluetooth DUN. Really cool find though!

This works fine for browsing and a few apps but most of the native apps (email, Gmail, Market, Mapps, etc) do not see a data connection.

Yes, it should work with an iphone; I think I saw some other threads talking about it, I just don't know the steps on the iphone to configure the tethering.

DUN and the blackberry; we need the DUN daemon!
Yeah, a firend of mine has a blackberry and a Nook, and was disappointed that there isn't DUN support (yet).
However, the official open source documentation mentions that there is not only the PAN daemon (pand), but also a DUN daemon, dund. It just isn't included in the cyanogen builds.
I still don't have enough posts to post to the developers side; if anyone could put a request in for dund we might be in business!
As for the range, it seems to be very dependent on what you're tethering to. The tether to the phone last night was a long distance, (the data rate did slow down a bit with distance, to answer the question above, but not badly). But, trying to link to a headset (with mixed success, still working on it), the range wasn't as good. And trying another phone, the range was pretty bad, only a couple of feet.

carrc said:
I still don't have enough posts to post to the developers side; if anyone could put a request in for dund we might be in business!
Click to expand...
Click to collapse
If you have less then 10 posts you can not start a new thread in the Dev section, but you can add a reply to an existing thread.

painter_ said:
If you have less then 10 posts you can not start a new thread in the Dev section, but you can add a reply to an existing thread.
Click to expand...
Click to collapse
I don't think this is correct. I tried to reply to the "CM7 with Honycomb features" thread, but was denied because I have less that 10 posts.
So I trolled a couple of General threads to get my count past 10.
=X=

=X= said:
I don't think this is correct. I tried to reply to the "CM7 with Honycomb features" thread, but was denied because I have less that 10 posts.
So I trolled a couple of General threads to get my count past 10.
=X=
Click to expand...
Click to collapse
I have seen people with less then 10 post in the CM development threads.
Who knows??

carrc said:
Yeah, a firend of mine has a blackberry and a Nook, and was disappointed that there isn't DUN support (yet).
However, the official open source documentation mentions that there is not only the PAN daemon (pand), but also a DUN daemon, dund. It just isn't included in the cyanogen builds.
Click to expand...
Click to collapse
This is very cool! Since I have a BB Curve, I'll have to wait until there is DUN support too, like I do with my iTouch and the BB.

Hi,
I was hoping I could use Bluetooth tethering with my non-rooted Android phone.
There is an application called 'PDANet' in the market with Bluetooth tethering, but
it only does DUN tethering. (free partly functional version, paid full function).
Easytether (market) promises Bluetooth DUN tethering in the future sometime.
In the process of trying to get Bluetooth tethering to work, I
found 'GScript Lite' in the market, very easy way to enter and run shell
scripts like the one on the original post from within Android UI. Looks like
it hasn't been updated to run on tablet, but seemed functional.
Hope this helps someone.
Peter

Has anyone had luck in getting the gmail and email app to work on a bluetooth PAN connection? I can use the web browser and some other apps like USA today but not the email apps.

carrc said:
I don't have enough posts yet to put this on the developers side, but after digging through a lot of posts, I've pieced together how to tether my CM7 Nook to another android device, and figured a few folks would want to try it as well.
The particulars: On the Nook, I am running the nightly build 31 of CM7.
Whichever phone you want to use has to be rooted, and have the 'wireless tether' app installed. It also has to be able to use bluetooth PAN (as opposed to DUN). I think most android phones do, but my friends blackberry only supports DUN.
First, on the phone: Turn on Bluetooth, and then go to settings>About Phone>Status and write down the bluetooth address, which is six hex numbers separated by colons.
Next, still on the phone, launch wireless tether, and go to the settings page. Check the 'Use Bluetooth' checkbox. Make sure the 'discoverable' checkbox is ticked as well, then go back to the main screen, and press the 'press to start tethering'.
On the Nook, start bluetooth, go to bluetooth settings and scan for devices (if needed); you should see the phone appear on the 'bluetooth devices' list. Pair up with it by clicking on it. Both the Nook and the phone will pop up a PIN dialog, accept that, and you should be seeing 'Paired but not connected' status.
Next, still on the Nook, open a terminal window, and type the following commands (substitute the bluetooth address of the phone you wrote down, INCLUDING THE COLONS in place of the xx's below).
EDIT: before pand, you need root access; use the su command
pand --connect xx:xx:xx:xx:xx:xx
netcfg bnep0 up
netcfg bnep0 dhcp
setprop net.dns1 8.8.8.8
you should now have net access via the tether!
The pand is the configuration demon for the PAN protocol, and that first line ties the bluetooth phone to a network interface named bnep0
The netcfg command activates that interface, and gets an address dhcp'd to it.
and the setprop command sets the DNS (in this case to google's DNS server).
I know many have said they only have limited bluetooth range, but either they have fixed that, or I'm one of the lucky ones, I could still get data on my Nook with the phone almost 30 feet away!
Click to expand...
Click to collapse
Thank you for posting this. I just had my NC rooted, running cm7; android 2.3.3 and am looking to get a compatible phone (I have a BB bold). I have asked in a different thread about which phone to get...but I wanted to ask you where I can find the "terminal window" you talk about? I believe I will need to do this myself (after paying $178 for the rooting).

midsouth said:
Thank you for posting this. I just had my NC rooted, running cm7; android 2.3.3 and am looking to get a compatible phone (I have a BB bold). I have asked in a different thread about which phone to get...but I wanted to ask you where I can find the "terminal window" you talk about? I believe I will need to do this myself (after paying $178 for the rooting).
Click to expand...
Click to collapse
Wait, hold on a second... you paid what for someone to root your phone? You paid anything at all, you paid too much, you can do this super easy man. Please tell me that was a typo for $1.78 because you bought the person doing your rooting a cup of coffee. Please!

There is an app/widget for BT PAN tethering now: http://forum.xda-developers.com/showthread.php?t=1032834

[HELP] Wifi & Bluetooth gone, no longer functioning (Found BT AND Wifi MAC in CP!)

[HELP] Wifi & Bluetooth gone, no longer functioning (Found BT AND Wifi MAC in CP!)
Just throwing this out there, I've actively used the hell out of my Thrill, and flashed it many times. However, the Bluetooth went out on AT&T's v20p, and Wifi went out after an OC'd crash. I was just wondering if there was some way to reset the chip itself as it seems the on/off for both do nothing, each stays permanently off now. I really want BT back, but I NEED Wifi back... Can somebody help?
I have flashed back to V20P in an effort to get both Wifi and BT working again, but still dead. I will sit on V20P for now, and hope things work eventually.
Trying to enable Wifi comes up with "Activity Wi-Fi settings (in application Settings) is not responding." leading me to believe that the hardware has to be fully reset.

Cynagen said:
Just throwing this out there, I've actively used the hell out of my Thrill, and flashed it many times. However, the Bluetooth went out on AT&T's v20p, and Wifi went out after an OC'd crash. I was just wondering if there was some way to reset the chip itself as it seems the on/off for both do nothing, each stays permanently off now. I really want BT back, but I NEED Wifi back... Can somebody help?
I have flashed back to V20P in an effort to get both Wifi and BT working again, but still dead. I will sit on V20P for now, and hope things work eventually.
Trying to enable Wifi comes up with "Activity Wi-Fi settings (in application Settings) is not responding." leading me to believe that the hardware has to be fully reset.
Click to expand...
Click to collapse
Have you tried a different firmware?

The Dark Lestat said:
Have you tried a different firmware?
Click to expand...
Click to collapse
I've tried V10K, V10D, V20A, V20P, V21D, and V21E, none of them restored the bluetooth (original issue), and so far V10K, V20P, and V21E have not restored the Wifi.
On V21E under settings, it's always showing as "Turning off..." under Wi-Fi. So it's definitely a hardware lockup. Is there anyway to do a full hardware reset on these things? I don't care about opening it, I'm not with AT&T anymore so the phone is mine, and frankly, I just want it to work.

I'm thinking of following some of the instructions for the lost IMEI, see if redoing the Communications Partition restores/fixes the BT and WiFi, I know stuff is getting corrupted when I crash while OC'd, and that's the only thing I haven't touched. I'll try it here tonight and see what I get. I still have both my WiFi and BT MAC addresses (WiFi stored in my router, BT in my computer when it was paired). So... I'll be trying that out soon as I get home today. Think it'll help?
So after fiddling around, I followed these steps from the reset your IMEI/SIM Unlock your phone thread, and started inspecting the CP payload that had to be flashed. I found a couple settings that I think people might find interesting:
1. Connect phone by USB
2. Activate USB debug mode
3. Enter 3845#*920# in dialer if that doesn’t work try 3845#*925#
4. Select Port Settings -> Select CP Image Download
5. A new device should appear at let it install
6. Open Tutty and select serial protocol. Click on open
7. Type AT if response is not OK, change port number (it is possible that when typing you don’t see any letters)
At this point, in order to check your Bluetooth MAC address, type AT%BTAD, this should display a string of 12 hex characters. IF you need to change your BT mac (such as putting it back in like I had to), use AT%BTAD=123456ABCDEF where "123456ABCDEF" is your Bluetooth MAC address (I had mine saved in my computer).
For Wireless MAC address: AT%MAC, same thing if you need to change it AT%MAC=123456ABCDEF. So far this has NOT restored my Wifi or Bluetooth, however it MAY help others who have suffered this loss. You will only need the Flash driver from that thread and tutty, so download the IMEI tool package, but don't worry about the CP unless you absolutely need it. Also, this is great to replace those MAC addresses once you flash (as they're likely wiped with the entire CP wipe).
I'm requesting some assistance with getting my Wifi and Bluetooth operational again if possible, maybe it's kernel modules, I'm not 100% sure, however, in the debug menu (3845#*<MDLNM>#) there is logging options for certain sections of the system. I'll be more than happy to provide logs if requested, I just want my Wifi and BT back and I feel like I'm onto something maybe. Here's to hoping!

Cynagen said:
I'm thinking of following some of the instructions for the lost IMEI, see if redoing the Communications Partition restores/fixes the BT and WiFi, I know stuff is getting corrupted when I crash while OC'd, and that's the only thing I haven't touched. I'll try it here tonight and see what I get. I still have both my WiFi and BT MAC addresses (WiFi stored in my router, BT in my computer when it was paired). So... I'll be trying that out soon as I get home today. Think it'll help?
So after fiddling around, I followed these steps from the reset your IMEI/SIM Unlock your phone thread, and started inspecting the CP payload that had to be flashed. I found a couple settings that I think people might find interesting:
1. Connect phone by USB
2. Activate USB debug mode
3. Enter 3845#*920# in dialer if that doesn’t work try 3845#*925#
4. Select Port Settings -> Select CP Image Download
5. A new device should appear at let it install
6. Open Tutty and select serial protocol. Click on open
7. Type AT if response is not OK, change port number (it is possible that when typing you don’t see any letters)
At this point, in order to check your Bluetooth MAC address, type AT%BTAD, this should display a string of 12 hex characters. IF you need to change your BT mac (such as putting it back in like I had to), use AT%BTAD=123456ABCDEF where "123456ABCDEF" is your Bluetooth MAC address (I had mine saved in my computer).
For Wireless MAC address: AT%MAC, same thing if you need to change it AT%MAC=123456ABCDEF. So far this has NOT restored my Wifi or Bluetooth, however it MAY help others who have suffered this loss. You will only need the Flash driver from that thread and tutty, so download the IMEI tool package, but don't worry about the CP unless you absolutely need it. Also, this is great to replace those MAC addresses once you flash (as they're likely wiped with the entire CP wipe).
I'm requesting some assistance with getting my Wifi and Bluetooth operational again if possible, maybe it's kernel modules, I'm not 100% sure, however, in the debug menu (3845#*<MDLNM>#) there is logging options for certain sections of the system. I'll be more than happy to provide logs if requested, I just want my Wifi and BT back and I feel like I'm onto something maybe. Here's to hoping!
Click to expand...
Click to collapse
What ROM are you currently on? Baseband as well.

The Dark Lestat said:
What ROM are you currently on? Baseband as well.
Click to expand...
Click to collapse
Currently running V21E baseband & Prometheus ROM v1.5, I've managed to make the phone stable again, however still no Wifi or BT. Inside CP, AT%IMEI, %BTAD, and %MAC show correct, thanks for the assist.
If I was on AT&T, this lack of Wifi would be absolute murder, but thankfully, T-Mo's got 5GB of 4G so I can still use my phone, just not half the apps (like Netflix (it checks Wifi status and locks up), or XBMC remote).

Cynagen said:
Currently running V21E baseband & Prometheus ROM v1.5, I've managed to make the phone stable again, however still no Wifi or BT. Inside CP, AT%IMEI, %BTAD, and %MAC show correct, thanks for the assist.
If I was on AT&T, this lack of Wifi would be absolute murder, but thankfully, T-Mo's got 5GB of 4G so I can still use my phone, just not half the apps (like Netflix (it checks Wifi status and locks up), or XBMC remote).
Click to expand...
Click to collapse
I would say that you should try going back to FroYo and checking those addresses again.

The Dark Lestat said:
I would say that you should try going back to FroYo and checking those addresses again.
Click to expand...
Click to collapse
I've gone back to FroYo without any change to Wifi or Bluetooth, but I'll go back to V10K and check the CP again.

Explanation
Cynagen said:
I'm thinking of following some of the instructions for the lost IMEI, see if redoing the Communications Partition restores/fixes the BT and WiFi, I know stuff is getting corrupted when I crash while OC'd, and that's the only thing I haven't touched. I'll try it here tonight and see what I get. I still have both my WiFi and BT MAC addresses (WiFi stored in my router, BT in my computer when it was paired). So... I'll be trying that out soon as I get home today. Think it'll help?
So after fiddling around, I followed these steps from the reset your IMEI/SIM Unlock your phone thread, and started inspecting the CP payload that had to be flashed. I found a couple settings that I think people might find interesting:
1. Connect phone by USB
2. Activate USB debug mode
3. Enter 3845#*920# in dialer if that doesn’t work try 3845#*925#
4. Select Port Settings -> Select CP Image Download
5. A new device should appear at let it install
6. Open Tutty and select serial protocol. Click on open
7. Type AT if response is not OK, change port number (it is possible that when typing you don’t see any letters)
At this point, in order to check your Bluetooth MAC address, type AT%BTAD, this should display a string of 12 hex characters. IF you need to change your BT mac (such as putting it back in like I had to), use AT%BTAD=123456ABCDEF where "123456ABCDEF" is your Bluetooth MAC address (I had mine saved in my computer).
For Wireless MAC address: AT%MAC, same thing if you need to change it AT%MAC=123456ABCDEF. So far this has NOT restored my Wifi or Bluetooth, however it MAY help others who have suffered this loss. You will only need the Flash driver from that thread and tutty, so download the IMEI tool package, but don't worry about the CP unless you absolutely need it. Also, this is great to replace those MAC addresses once you flash (as they're likely wiped with the entire CP wipe).
I'm requesting some assistance with getting my Wifi and Bluetooth operational again if possible, maybe it's kernel modules, I'm not 100% sure, however, in the debug menu (3845#*<MDLNM>#) there is logging options for certain sections of the system. I'll be more than happy to provide logs if requested, I just want my Wifi and BT back and I feel like I'm onto something maybe. Here's to hoping!
Click to expand...
Click to collapse
Please Explain Tutty. I get into the hidden screen and tried the download and nothing was downloaded, this is my first smartphone and do no that there is no MAC address for the bluetooth device. it is the only thing not working. Thanks in advance for the help.

[Q] Bluetooth Issues After Stopping Sixaxis Controller

Hey all, so I recently spent some time learning up on these awesome forums, and at least for getting started I decided to just modify stock 2.2, I have just really wanted to be able to play games using my ps3 controller on my nook so I thought the easiest path was to root using the Universal Rev3, and the Unknown Apps, at least to get me started. I have a bluetooth keyboard I also use with this setup for school. Okay so that's the upfront details.
My issue is that, while my bluetooth is connecting fine with everything before I run sixaxis, and my controller works (yay, i got what i wanted!) while I'm running the program, it's when I stop sixaxis and it restores my bluetooth (or says it does... or gets stuck and never says it does) my bluetooth simply can't be switched back on until after I reboot... I've completely stopped and disabled and cleared the cache on the sixaxis app... and nothing, still won't turn back on. Now this is a cadillac issue, my controller works, my keyboard works, but I just have to reset. The problem is that I know it shouldn't be this way and if it has to be, I'll survive, but if not I'd love a way to make it work right, or at the very least see if there's an option to... "respring" (I know that's an iphone thing I just didn't know if there was a faster equivalent to a reboot without having to completely turn it off and back on)?
Anyone else had this problem? Any thoughts? Any options? Thanks for your time and information, have a great day!

"t's when I stop sixaxis and it restores my bluetooth (or says it does... or gets stuck and never says it does) my bluetooth simply can't be switched back on until after I reboot..."
Obviously, its at the fault of the app, because otherwise (sixaxis not installed/used) bluetooth would function properly and no restart would be required.
Therefore, sixaxis is not ending support of the controller properly, re-enabling bluetooth support, or whatever its trying to do for the device, android version, or whatever its problem is in code.
Probably good to let the app's dev know about it and find out if they say anything.
Since root access is required, it definitely requires some deeper access to android (the deeper the more problems are likely to occur). Some code doesn't even work for all devices and they could have gone that route with their app knowingly - whether it was a necessary side effect due to the type of app they created or specifically because of a workaround of what google allows devs to do with android.
Either way it is often an app with problems as reviews show.

sandsofmyst said:
"t's when I stop sixaxis and it restores my bluetooth (or says it does... or gets stuck and never says it does) my bluetooth simply can't be switched back on until after I reboot..."
Obviously, its at the fault of the app, because otherwise (sixaxis not installed/used) bluetooth would function properly and no restart would be required.
Therefore, sixaxis is not ending support of the controller properly, re-enabling bluetooth support, or whatever its trying to do for the device, android version, or whatever its problem is in code.
Probably good to let the app's dev know about it and find out if they say anything.
Since root access is required, it definitely requires some deeper access to android (the deeper the more problems are likely to occur). Some code doesn't even work for all devices and they could have gone that route with their app knowingly - whether it was a necessary side effect due to the type of app they created or specifically because of a workaround of what google allows devs to do with android.
Either way it is often an app with problems as reviews show.
Click to expand...
Click to collapse
Hey thanks a ton for the information. I had started to suspect that but since I'm a noob here I thought it was best to ask. Will contact the developer. But hey for now if all I have to do is a reset after a gaming session to make all things right, it's not so bad. Thanks again!
EDIT: Okay, so after doing some fiddling with my own Nook HD+ it looks like the Nook itself has trouble shutting down bluetooth! When I go into my battery use bluetooth is staying on permanently after initially turning it on. The time continues to run no matter what I do or shutdown with Android Task Manger. And it appears I'm not the only one. http://bookclubs.barnesandnoble.com...Bluetooth-won-t-turn-off-Nook-HD/td-p/1462091
Also since mine is rooted and has unknown sources installed I felt like I needed a control group. So I borrowed my wifes Nook HD+ which is completely stock, no mods at all... and it does the exact same thing... This is mind boggling. Could a few people turn their bluetooth on long enough to register in their battery monitor, then turn it off, and tell me if their time is still running for the bluetooth? It would really help me identify whether this a software problem with Nook software, or it's a hardware issue that they had amongst several models and they shipped with bad parts, etc. Thanks!

gregorcarbine said:
Could a few people turn their bluetooth on long enough to register in their battery monitor, then turn it off, and tell me if their time is still running for the bluetooth? It would really help me identify whether this a software problem with Nook software, or it's a hardware issue that they had amongst several models and they shipped with bad parts, etc. Thanks!
Click to expand...
Click to collapse
It could also be this or similar: https://code.google.com/p/android/issues/detail?id=69135
Quote, "Problem: When turning off the Jawbone, it causes the Bluetooth(BT) to misbehave and not turn off nor function."
...Though that's for android 4.4.2 and nook 2.2 is android 2.2... wow that's old... that could of course be it as well - if the problem is with android, it could have been fixed in a later android version.
In the end, it doesn't appear to have to do with the device itself, but perhaps with that android version's bluetooth package or an installed app. And which android version (if any) would work for you idk. I remember people saying cm and sixaxis didn't work with bluetooth on the nook in the past, so if that's still the case, don't know that either.
I'm not sure how far back many apps are going today with android versions but something like: https://play.google.com/store/apps/details?id=org.myklos.btautoconnect&hl=en
could possibly do something(?). But, I'm just reaching there for anything in the you never know category.
But hopefully that gives a better picture as to what it could be. Sorry, I can't give an actual [working] solution, though for all I know I gave a path to the only solution.

Challange...

I have an olg Galaxy S with a complete broken screen. The phone is fully functional but theres no image on the screen. I tried to plug it on the tv to use it has a sort of tv box since I'm not willing to buy a screen because is more of it is worth.
Anyone knows a way I can activate the tv-out since only connecting the cables isn't sufficient?

Imaginati0n said:
I have an olg Galaxy S with a complete broken screen. The phone is fully functional but theres no image on the screen. I tried to plug it on the tv to use it has a sort of tv box since I'm not willing to buy a screen because is more of it is worth.
Anyone knows a way I can activate the tv-out since only connecting the cables isn't sufficient?
Click to expand...
Click to collapse
Well, that's an interesting problem.... Three ways I can think of getting around it.
1)
If you've got a linux box and can compile a ROM, the commit you'll need to revert (assuming you're building for CM) is at https://github.com/CyanogenMod/andr...mmit/ae5393e4349fe392d4d39f9b600461ea57f510ad I'm assuming you have working adb? If you were to build a zip with that commit reverted, you would still need to install the zip anyway. You could probably accomplish that using ADB sideload, but that has only been around since JB. If you're on an older ROM then you'll have to get someone to post screenshots of each recovery screen that you would need to go through and do a "blind flash" by clicking the buttons to do the selections needed....
2)
Try to manually select TV-Out to be working. You could have a look at http://android.stackexchange.com/qu...ted-under-settings-from-terminal-or-adb-shell for an idea of where to start. Not sure how to select a checkbox though...
3)
Try manually starting the tvoutserver and tvouthack. All you would need to do would be from an adb shell run "tvouthack" and "tvoutserver". Heck, you could probably even put a script in /etc/init.d and have it run automatically on boot.
One problem you might run into is that it defaults the TV type to PAL. If you need NTSC, you might be in trouble. If you got through the "compile ROM" option, then change the line
Code:
mSystem = Integer.parseInt(mPref.getString(DeviceSettings.KEY_TVOUT_SYSTEM, "2")); // Default = PAL
to
Code:
mSystem = Integer.parseInt(mPref.getString(DeviceSettings.KEY_TVOUT_SYSTEM, "1")); // Default = NTSC
Also, if you've never used the TV-Out function before, the video is sometimes on the red plug as opposed to the yellow (go figure).
Good luck!