yashsingh1/xdaforums huggingface dataset:
[LG Nitro HD] stephensonbrady:
The graphical glitch still happens intermittently. I've been having some Facebook force closing issues, occasionally the maps program doesn't work, but I think that it is related to the graphical glitch. The UI is pretty smooth overall, and i haven't had any data/sms/phone issues.
[Galaxy S III Q&A, Help & Troubleshooting] kwyj:
Has anyone else had problems with name resolution on Wifi networks?

On 3G I can browse to any site and it works fine. As soon as I connect to my Wifi network I am unable to connect to anything (websites, Play, email etc.) The only way I can connect is if I connect directly to the IP address of the site (not the DNS name). I'm getting an IP address on the Wifi network via DHCP, but have tried manually specifying IP, gateway and DNS with no luck. (I've actually tried manually specifying my own DNS, and Google's DNS server) Looking at the DNS server logs it doesn't appear that the S3 is even querying the DNS server.

Other devices on the same network (multiple iDevices, Macbook, XBox 360 etc.) all work fine.

It has worked for the past 6 or 8 weeks (as long as I've had the phone) but stopped working a few days ago. I was running stock firmware, unrooted. Since the problem appeared I have updated to the recent JB leak and XXLH1 modem but it has made no difference.

Any ideas?
[Galaxy S III Q&A, Help & Troubleshooting] kwyj:
Please ignore. I managed to resolve it but I have no idea what the original problem was or why the fix worked.

I manually changed the IP address to a different valid address within the subnet and it fixed it. The original IP address is not in use anywhere else on the network. I've now created a DHCP reservation using the new address and it's working fine.
[Samsung Infuse 4G] veeRob:
Hey, guys. Hoping some of you experts can help me diagnose what's wrong with my Samsung Infuse. I bought it off Craigslist at the end of May, and the guy had the phone with the original screen protector on it, with the original case and all accessories, so I had no reason to believe it had any problems. He told me the phone was already rooted & unlocked, which I wanted since I signed up with Straight Talk. I used it for June & July and had a host of problems, so I put on the CM10 ROM last week to see if it helped. It didn't. Here are the problems I continuously encounter:

1. When going to unlock my phone with a pattern, once in awhile it won't detect my finger-presses. Sometimes nothing shows up at all, sometimes one of the dots will highlight as I pass over it, but it won't draw. Eventually the screen turns off, and I turn it on and try it again. Usually it ends up working.

2. The battery dies much quicker than I expect it should. I tried running JuiceDefender and not running JuiceDefender, and it doesn't seem to make a difference. Even without using my phone much for anything, even with the screen off, the battery will run out before the day is out. It's like if you were driving and had a hole in your tire... seems like some sort of a leak.

3. The cell radio seems flaky. Sometimes I won't get texts on time. A lot of the time I can't access any data, which is very important as I use Google Voice for lots of my texting, so I send a text and it won't go out. Loading web pages or reloading my email shows that it is a data problem.

Those are the primary problems, and I suspect that somehow they are all related. I'm not sure if the Craigslist guy sold me a lemon, or there is some other problem that came up. I've tried multiple ROM's and disabling every app I can think of. Can anyone think of anything that would cause these problems & any way to fix it? Or do I just own a broke phone that I have to throw in the garbage?

Thanks in advance for reading!
[Samsung Infuse 4G] captemo:
a whole slew of problems can lead to a whole slew of possibilities for your issues.

first, i wasnt aware that you could do any of this on a straight talk phone, but i could be wrong. i am not the "expert" you may be looking or hoping for, though one i am sure will show up.

second, i think the response you may get is......did you go to JB straight from Gingerbread??? that will cause HUGE problems.

dd you read OP and follow to a tee??? again HUUUUGGEE problems.

the "never fail" here.....READ READ READ. feel confident as to what you are doing and follow steps one at a time. UNDERSTAND steps one at a time.

first thing that never hurts.....return to stock and start from scratch.

"super everything thread" under development.

Odin "stock-root & modded 3e rcovery.

follow all directions TO THE TTT.

if that doesnt work, you might have to get some mortar, you've got yourself a BRICK.

i know almost everyone else here is more of a expert than i am, but i do believe that is where they will tell you to start

good luck and be sure and thank the experts
[Samsung Infuse 4G] ApexPredatorBoids:
While I have no idea what you're getting at by your Straight Talk comment, as ST is little more than AT&T service that's sold through a 3rd party at a discounted rate, the fact that he's using ST may be part of his problems, at least in regards to the network issues. I'm also having an unbelievable amount of data issues on ST. ST is having some network problems that are affecting a decent amount of customers who are on their AT&T network.

One thing that the OP may want to try is this: Download DNS Changer from the Play Store, and change your primary and secondary DNS to OpenDNS1 and OpenDNS2. Or try different settings, as there are a bunch that are available. That has made at least some difference with my data connectivity issues.

Based on my own experience, having tried to go to JB directly from GB, is that if it's going to affect your radio, it's likely to completely wipe out your EFS data so you won't have ANY cellular or data networking capabilities. As stated, that's simply based on how it worked out for me, and there could easily be other side-effects that just didn't happen to show up for me.

I agree with returning completely to stock UCLB3, with the GB bootloaders. Then flash Entropy's 4.4.2012 Kernel, which will also install CWM Recovery. I'd personally reccomend Heimdall, as it seems to be somewhat simpler. Detailed information on returning to stock via Heimdall can be found in this thread:

http://xdaforums.com/showthread.php?t=1629079&highlight=heimdall+uclb3

If you use it, be sure to thank qkster for making it available. He's probably the most helpful person you're likely to find on this forum, especially where us noobs are concerned.
[Samsung Infuse 4G] dparrothead1:
I would take it back to stock and start all over.

Here is a very helpful thread.

http://xdaforums.com/showthread.php?t=1700416
[Samsung Infuse 4G] Goneeuro:
I agree with parrot head. When issues arise go back to stock. That's the best part of our phones. They are damn near impossible to really mess up. Just have to be ware of bootloader flash going wrong. If you got your gb rom from keis your good to go though.
[Samsung Infuse 4G] veeRob:
Appreciate the response, guys. I guess it doesn't hurt to try to start from scratch... AGAIN! It just seems like I'm putting an awful lot of hours into putting new ROM's and bootloaders on this phone. Going to be especially frustrating if I go through all the steps and it still doesn't fix my issues, which would mean my phone is broke. Oh well, guess I have little other choice.
[Samsung Infuse 4G] drnecropolis:
All of the issues sound related..

It shouldn't take long to drop to stock and flash up to JB.. I've bobbled and missed steps here and there and have had to return from stock more times than I care to admit.. even rooting and flashing up the ladder only take about 20 minutes if even that..

Good luck!
[Samsung Infuse 4G] veeRob:
Yes, the flashing process isn't that long, it's getting back my phone to all of my customized settings that ends up taking weeks. Home screen icon positioning, logging in to every app, system settings, etc.
[Samsung Infuse 4G] drnecropolis:
Didn't create a backup?
[Samsung Infuse 4G] veeRob:
I've always created backups with Titanium Backup, but when I restore the apps, a lot of them ask me to re-login or re-verify myself.
[Samsung Infuse 4G] veeRob:
Thanks for the advice guys.

Spent a whole day going back to stock, then CWM red, then ICS, then Jellybean. Things seem to be markedly better, but the phone still seems laggy in a few places. Is this just because it's not the latest and greatest processor?

Also, the GPS just does not work right. It's still identifying me as being in Missouri even though I'm in Nevada. Consistently. Do I just have to live with that?
[Samsung Infuse 4G] ApexPredatorBoids:
Are you still using the Trebuchet Launcher that comes built-in to the JB ROM? If so, that may be part of your lag problems. I just use ADW EX launcher. Here's an excerpt from the Paranoid Android JB OP:

As far as the GPS goes, I think Samsung just used ****ty receivers in the Infuse. My GPS isn't quite as bad as yours seems to be, but it's nowhere near as accurate or reliable as the GPS chipset in my crummy little Optimus V.
[Galaxy S III Q&A, Help & Troubleshooting] Ev0d3vil:
Is there another place where i can get stock firmwares? Hotfile is screwing up and my downloads stop halfway for no apparant reason.
[Galaxy S III Q&A, Help & Troubleshooting] JJEgan:
XDA Stock Threads .

http://samsung-updates.com/device/?id=GT-I9300

Via CHECKFUS http://fus.nanzen.se/

jje
[Galaxy S III Q&A, Help & Troubleshooting] sxi200:
+1. Checkfus is my favourite and for me it's by far the fastest download. But I must admit I rarely use it because I prefer custom roms.
[Galaxy S III Q&A, Help & Troubleshooting] hitoalloff:
unlock bootloader

how to unlock the bootloader on p6200 with link plz
[Samsung Galaxy Mini] apriores:
Sorry, I encounter too many problems when I tried to finish this project and I need to close it. Please delete it.

I apologize again.
[Samsung Galaxy Mini] chris_b0ss:
could you post some previews?
[Samsung Galaxy Mini] peter_baz:
it force closes android and status bar prosses...

my guess is that you didnt deodex...can you deodex the full rom and then mod it?
[Samsung Galaxy Mini] apriores:
I don't know how to deodex. Can you tell me how, please?

I'll post a video preview shortly with all animations.
[Samsung Galaxy Mini] peter_baz:
then how did you apply it to your phone?
[Samsung Galaxy Mini] apriores:
On my phone its working well through update and I thought it will work on any mini 2 without trouble. Sorry about that. I will search for deodexing process.
[Samsung Galaxy Mini] peter_baz:
try this http://galaxyygaming.blogspot.gr/2012/05/guide-to-deodex-stock-rom.html

or this http://xdaforums.com/showthread.php?t=598026
[Samsung Galaxy Mini] apriores:
Thanks for links!

Did you deodexed your rom?
[Samsung Galaxy Mini] peter_baz:
im dont have access to my pc for some days so im hoping on you :)

if you succed i will try to theme it ics :D
[AT&T, Rogers HTC One X, Telstra One XL] ttinjust96:
Hi There,

does anybody have a build.prop file that is compatibile with the gameloft games? I already tried http://xdaforums.com/showthread.php?t=1714298 but it didnt work for me. im currently running CleanROM 4.5 :)

thanks
[AT&T, Rogers HTC One X, Telstra One XL] superchilpil:
You found the right one.... So I don't see any other methods
[AT&T, Rogers HTC One X, Telstra One XL] _MetalHead_:
That is the correct one. You just need to make sure you find all the instances of ro.product.model and change them. That's the problem I had at first but i found one hidden early on in the file and when I changed it it worked beautifully.
[Nexus 7 General] lionsh:
Where to get the DVB tuner

Hi,

Thanks for posting. it is very interesting.

can you post where did you buy the tuner from and the price?

the only one i could find with RTL2832U is priced at 27$ from ebay.

How can i compile the kernel modules for a different device?

thanks.
[Nexus 7 General] VonLaserface:
Very cool!

Could a similar technique could be used for ATSC here in the U.S.?
[Nexus 7 General] martintzvetomirov:
I actually have compiled all of the drivers that come with the Linux kernel as well

You can get them from here - http://dl.dropbox.com/u/24106229/all-modules.rar

If your device is listed as compatible somewhere here - http://www.linuxtv.org/wiki/index.php/DVB-T_USB_Devices then you may be lucky :) You just need to know which kernel module to load with insmod (see the startdvb script to see how to do it).

If it's not there or you have a different kernel version, you will need to follow https://source.android.com/source/building-kernels.html . Except for you only need to build the modules, and you need to fiddle around with the Makefiles in order to force some of the components (like the dvb-usb.ko) to be compiled as modules. Good luck!

As far as the tuner I am using, it's http://cgi.ebay.co.uk/ws/eBayISAPI.dll?ViewItem&item=120958257586 this one. I actually got it for another purpose (http://sdr.osmocom.org/trac/wiki/rtl-sdr), which if I have the time I can try to build an app to bring it to the Android as well :)
[Nexus 7 General] lionsh:
another question

Thanks for the quick reply!

I couldn't find the right *.ko file in the modules you attached (it is supposed to be af9005 and af9015, and for my other dvb-t - IT9135)

Could i bother you to upload these, since i have no idea how to compile them.

I tried using af9013.ko that you attached but with no success, most likely because i had to use af9005 instead.

I added insmod af9013.ko to your script, attached is a screenshot from my emulator:

Thanks again. Your help is much appreciated!
[Nexus 7 General] lionsh:
another question

double post by mistake
[Nexus 7 General] micks_address:
Hi, I was wondering about this a few weeks ago.. great to see it working.. do you know if the Sony Play TV tuner would work? I have one of those...

Cheers,

Mick

---------- Post added at 09:37 AM ---------- Previous post was at 08:49 AM ----------

Here is the driver i need... i assume i need to be able to produce a .ko file some way for it?

http://linuxtv.org/wiki/index.php/Sony_PlayTV_dual_tuner_DVB-T#Drivers
[Nexus 7 General] lionsh:
aspletec this

Hi.

In the file Martin attached with all the modules there is a module for you DVB-T, it's called dib0070.ko

Try this one.
[Nexus 7 General] micks_address:
Thanks, once i copy it to the folder with the startdvb file.. what other steps do i need?
[Nexus 7 General] lionsh:
you need to update the startdvb script to inclue ismode yourdriver.ko
[Nexus 7 General] micks_address:
I edited the startdvb file to reference the dib0070.ko but i get init failed.. i wonder doesn the nexus have enough power to power the tuner via USB?

Cheers,

Mick
[Nexus 7 General] Psych0Chimp:
You need to add the line 'insmod dib0070.ko' to startdvb.

You will probably also need to copy the 'dvb-usb-dib0700-1.20.fw' firmware file from that link you posted earlier into /etc/firmware.
[Nexus 7 General] martintzvetomirov:
OK guys, my bad! I didn't originally submit all of the files. Please, redownload again - http://dl.dropbox.com/u/24106229/all-modules.rar

I didn't compile the usb drivers, the ones that you would actually need :) Now everything should be there.

You will need dvb-usb-af9005.ko and possibly dvb-usb-af9005-remote.ko

You will need dvb-usb-dib0700.ko and the firmware from the web page you pointed me at.

It was able to properly power my tuner without external power but surely this won't be the case with all of them. That can't cause the init to fail though! Use dmesg to get more info on why this has happened.

Yes, that's right. So here's how to do it

echo "Starting DVB support"
insmod dvb-core.ko # core support for DVB
insmod dvb-pll.ko # I am not sure if this is even needed
insmod rc-core.ko # Support for remote control, some drivers won't load otherwise
insmod dvb-usb.ko # Support for usb tuners
insmod ***** # Add here your driver. If more than one needed, add another line
# if firmware is needed, make sure the firmware is in the right folder, it should be /lib/firmware, but I'm not 100% sure
# Also some devices won't need the steps below
echo "Waiting for device"
sleep 5
cd /
mkdir /dev/dvb
mkdir /dev/dvb/adapter0
cd /dev/dvb/adapter0
ln -s /dev/dvb0.frontend0 frontend0
ln -s /dev/dvb0.demux0 demux0
ln -s /dev/dvb0.dvr0 dvr0
ln -s /dev/dvb0.dvr0 dvr0.ts
chmod -R 777 /dev/dvb* # The original script doesn't have it, but try adding a -R before 777 might ease things a bit
echo "DONE!"

Hope this helps!

If any error message occur, type in dmesg in the terminal. This will give more information why something failed. Also to check whether you have insmoded the kernels right and after connecting the device it has been discovered, use dmesg again and look for message similar to "Found DVB device xxx in warm state"
[Nexus 7 General] lionsh:
Hi Martin,

first of all many thanks!

i used 9005,9005-remote and 9015 ko files and updated the script as follow:

echo "Starting DVB support"
insmod dvb-core.ko
insmod dvb-pll.ko
insmod rc-core.ko
insmod dvb-usb.ko
insmod dvb-usb-af9005.ko
insmod dvb-usb-af9005-remote.ko
insmod dvb-usb-af9015.ko
echo "Waiting for device"
sleep 5
cd /
mkdir /dev/dvb
mkdir /dev/dvb/adapter0
cd /dev/dvb/adapter0
ln -s /dev/dvb0.frontend0 frontend0
ln -s /dev/dvb0.demux0 demux0
ln -s /dev/dvb0.dvr0 dvr0
ln -s /dev/dvb0.dvr0 dvr0.ts
chmod -R 777 /dev/dvb*
echo "DONE!"

I receive several errors.

first i get 9015.ko file not found, i'm attaching screen shot with ls that clearly lists the file (WTF?!)

and *dvr0.ts file is also written as no such file/dir.

I even copied the .fw files for 9005 and 9015 to etc/firmware

can you take a look ,i must be missing something stupid.

also, is there a dvb-usb-IT9135.ko file?

many thanks for your contribution.
[Nexus 7 General] lionsh:
I created the files :

frontend0

demux0

dvr0

dvr0.ts

in /dev/dvb/adapter0 and now i don't get an error on running sh startdvb (except on *9015.ko being not found)

when i open droid tv and select DVB-T and some country using dvb-t i get an error of unable to determine frontend

so something still missing/wrong.

UPDATE

using dmesg i saw an error for init 9015.ko - Unknown symbol af9013_attach (err 0)

maybe the compilation of this driver was not right, since it is 9015 and not 9013?

I do hope that it's the lack og 9015.ko which is keeping me from watching DVB-T. If I had the dvb-usb-IT9135.ko file i could try a different DVB-T tuner.
[Nexus 7 General] birdster:
Loving the progress on this, for me dtv isn't what I'm looking for I would love to see a working live video input displayed on my nexus for a project I'm working on using a usb composite video in Interface the type you use to rip vhs to the computer, I'm guessing and hoping the solution is pretty much the same? Any advise and help on this please?

Thanks
[Nexus 7 General] Psych0Chimp:
Great work on this, so far I've managed to get my DVB tuner properly configured and connected!

The only issue is Droid TV seems very unstable... Are there any alternatives?

I get reboots when scanning for channels. Might try recompiling a newer version of w_scan when I get a minute.

The channels I manually added only have a signal of 20% with no picture. The signal is fine when the tuner is connected to my PC though.

Maybe the Nexus doesn't give it enough power?
[Nexus 7 General] lionsh:
Hi,

Can you state which module do you use for your DVB-T tuner?
[Nexus 7 General] Sikki:
I have an A-Link dongle that seems to be running Afatech inside. Among the things you have done, I also attached and insmodded af9013.ko and got my receiver mounted in warm state and its actually scanning the channels in DroidTV as we speak. (No luck on the first try).

I have dvb-usb-af9015, 9005, 9005-remote, af9013 and the af9015 firmware (in the etc/firmware folder).

These seemed to do the trick.
[Nexus 7 General] lionsh:
that is so strange, i tried all these combinations, including af9013.ko with no luck.

did you get an error on af9015 like i did?

i have copied the firmware also. did you d\l it from http://linuxtv.org/wiki/index.php/DVB-T_USB_Devices#DVB-T_USB_Devices?

when you ran startddvb script did you receive any errors? I get an error that the files in /dev/dvb/adapter0 are missing.

only when i create the files manually it passes, but then i can't initialize droid tv.

which kernel version do you use? i have 3.1.10 g52027f9

can you upload the files+script that you used?
[Nexus 7 General] bahathir:
Try the modules for 3.1.10-g05b777c, which I compiled specifically for your DVB-T model.

I don't have the dongle to try with, but, I hope it working fine. :)

Good luck...

Remember to put the firmware file, dvb-usb-dib0700-1.20.fw, into /system/etc/firmware/ directory, before loading the modules.
[Nexus 7 General] EeeK:
Thanks bahathir. I'm using your files and is able to start up DroidTV.

I'm now facing another problem is after selecting my country, Singapore, and clicking on the scan gave me a popup message saying "wscan failed (1)" and after clicking ok I see the following message.

ERROR: Sorry - i couldn't get any working frequency/transponder

Nothing to scan!!

Do you or anyone can help?
[Nexus 7 General] Toxicone11:
Any hope for r820t tuners? :(
[Nexus 7 General] bahathir:
Try this steps.

0) Put or make sure all *.ko files and startdvb.sh into /data/local/tmp directory.

1) Switch off the N7.

2) Connect the DVB-T dongle usng the OTG cable.

3) Switch on the N7.

4) Open terminal emulator app, example, Connectbot, and go into 'local' mode.

$ su
# cd /data/local/tmp
# sh startdvb.sh

5) Start DroidTV app

In my case, I need to plug the DVB-T dongle BEFORE loading the modules, ie "sh starttdvb.sh".

I hope the stpes work for others too.

Thank you and good luck.
[Nexus 7 General] EeeK:
Hi bahathir, thank for your reply. I tried your steps but it does not work, giving me the same result.

In DroidTV, I noticed that even after selecting my country, Singapore. It's using default as SG is not defined as shown. Could that be the cause?

I also googled and found this but it is running on ubuntu instead of android.
[Nexus 7 General] bahathir:
I also get similar output with my PCTV NanoStick T2 (290e), em28xx chipset, as we can see at my screencapture.

After the initial scanning, I exited the DroidTV, and restart the DroidTV, and I can enjoy the DVB-T test broadcast here, in my country, Malaysia.

Thank you.
[Nexus 7 General] EeeK:
Even I exited and restarted the DroidTV app, it still prompt me to scan and gave me the same error. Think I'll give up getting this to work.

Thanks alot for your help though and good luck in your general election!
[Nexus 7 General] bahathir:
Sorry my friend..I could not help you in the matter.

Hope, you get better luck with other USB DVB-T models.

Thank you.
[Nexus 7 General] kasper933:
Hove anyone tried to do it on SGS3? I never compiled kernel modules so it will be hard for me... Maybe anyone have some knowledge if it worth trying, I mean if it is possible to get working... SDR Touch is working fine...
[Nexus 7 General] bahathir:
Since your DVB-T dongle was ables to scanning the frequency, and unable to 'locked' on DVB-T broadcast, most probably, you are at very weak signal reception. If possible try again at different places/locations, such as outdoor, or get a better antenna, ie outdoor antenna.

General Election;

Thank you, and I wish peace and harmony before and after the election.

Thank you.
[Nexus 7 General] Toxicone11:
Cmon, please someone, it should be possible to make r820t work, but how? :(
[Nexus 7 General] adamz2013:
Hi, where could I get the droidtv app? is there source available?

Does it support video capture from video-in any of these usb dongles?
[Nexus 7 General] elmicha:
The source is linked in the first post of this thread. It doesn't support recording yet, and it probably doesn't know anything about analog video-in.
[Nexus 7 General] johnnyman25:
this works only on stock kernel?what about m-kernel?
[Nexus 7 General] elmicha:
m-kernel doesn't have the DVB-T modules by default. Maybe we should ask Metallice politely if he can include the modules.
[Nexus 7 General] scrizz:
don't ask, DEMAND!!

lol jk :p