yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Q&A, Help & Troubleshooting] n2d551:
Same issue here. Occasionally I've fixed it between kernel or Rom flashing, but never found out what I did to fix and when I'd flash again it would go back to bad quality again. Sometimes I have to stick a finger in one ear and press the phone hard into the other ear to hear anybody
[Nexus 4 Q&A, Help & Troubleshooting] kingkaiser:
Yeah, mine worked well again for a day. The next time I restarted, it was crap again, and I have no clue what I did differently...
[Nexus 4 Q&A, Help & Troubleshooting] shirsathgautam:
I also facing same issue from last few day after flashing 4.4 kit kat cm 11.2
[Nexus 4 Q&A, Help & Troubleshooting] kingkaiser:
Guys, I'm on an s3, but someone posted a file in the neatrom 4.3 thread that works. Not sure if it'll work for everyone but thought I'd let you know that a fix is out there (can't copy the link coz I'm on tapatalk)
[Nexus 4 Q&A, Help & Troubleshooting] dLeTe:
I'm a bit hesitant to flash something for the S3 onto the N4. Plus, the file in that zip you're referring to isn't one that's contained on the N4 in that directory.

Thanks for noting, though. Maybe I'll backup and try it to see.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Q&A, Help & Trouble] ariel123:
Is there a way I can share my gtab pro screen on my desktop or tv
[Galaxy Tab Pro 12.2, 10.1, 8.4 Q&A, Help & Trouble] ritchea:
http://xdaforums.com/showthread.php?t=2676137 report of MHL connection.

I've read Miracast works if your components are compatible (wifi).

"Thanks to AllShare you can also mirror your mobile device screen to the bigger HDTV via Wi-Fi Direct and the widely supported Miracast protocol - that would even allow you to play mobile games on the biggest screen in your living room. You don't need to have a Samsung TV for that to work, but it needs to have Wi-Fi connectivity and support Miracast." http://www.gsmarena.com/samsung_galaxy_tab_pro_8_4-review-1042p10.php
[8125, K-JAM, P4300, MDA Vario Software Upgrading] Vilem:
For 2 weeks now I'm trying to get my Wizard working with this nokia GPS BT and Tomtom. I updated my rom to the 2.3 and still I'm having problems.

Sometimes it works for a week and then stops working.

Is there a way to test this BT GPS to see if it is working properly ?

I tried everthing possible, all suggestions in this post.
[LG Optimus G (International)] Nite.Achilles:
I'm using Savvy ROM V4 with Stock v0.3ST from Loller79.

I let my phone drop to 8% last night and it warned me to charge it.

As soon as I plugged in the charger, the phone died.

I left the phone to charge, yet after few hours, it just showed a grey screen on the phone. It doesn't want to boot to the ROM or CWM. I can't access my CWM. So what's happening? Does anyone know?

I can only access Download Mode. It doesn't seem to charge...
[Nook HD, HD+ Q&A, Help & Troubleshooting] mattjfk1:
I got a new Nook HD+ in June. I kept it on stock, until about October, when I flashed cyanogenmod 10.1.3, then 10.2. The lag slowly became worse and worse until it was almost unuseable. I finally found a thread saying to format data and datmedia, so I did. This fixed the lag, but it started to come back. This is almost certainly a trim bug, but I know almost nothing about that (I am in middle school :)). I do not want to format again, so I don't know what to do. Right now, I am on cm11.
[Nook HD, HD+ Q&A, Help & Troubleshooting] kokercey:
If you are on CM11 then trim is enabled so it will run when certain conditions are met. I have found the easiest way is to plug it in overnight. Trim will run if the Nook is charging and has been idle for a period of time. Hope this helps
[Nook HD, HD+ Q&A, Help & Troubleshooting] mattjfk1:
Thanks!

Thanks for responding. I had daydream on, so I don't know if trim ran or not. It seems like the lag is slowly getting better, but that may be the placebo effect. Is there a way to see if trim has run or is there another way to run it? Thanks!
[Nook HD, HD+ Q&A, Help & Troubleshooting] kokercey:
There is a command line that can be run in Terminal that will check the log of the last trim run. I used it once to be sure trim ran BUT i do not remember the command. Do a search of the forum and you will find it.
[Nook HD, HD+ Q&A, Help & Troubleshooting] mattjfk1:
I'm sorry, but I can't find it anywhere. Could you find it?
[Nook HD, HD+ Q&A, Help & Troubleshooting] kokercey:
Read this thread carefully and you will find the info you are searching for. You may have to link to another thread. It's the "Teach them to Fish" thing

http://xdaforums.com/showthread.php?t=2528009
[Nook HD, HD+ Q&A, Help & Troubleshooting] mattjfk1:
On that thread, I found instructions to run trim manually from Terminal. I did it and my nook was a little bit faster, but still significantly laggy than it is supposed to. I have started to think that the lag may not just be trim. Could this be true? Also, I ran Androbench and my random write was only .11 mb /s.
[Nook HD, HD+ Q&A, Help & Troubleshooting] mattjfk1:
Also, I have the MAG2GA chip. Will this affect the speed of my nook?

When I run trim from the command line, it always says that it trimmed the same number of bytes each time, even if it is just a few seconds after. Is it supposed to do this?

Thanks again for all your help!
[Verizon Samsung Galaxy S III] m4gkman:
Okay so I have a gs3 that is no longer responding to power buttons or cables or new batteries. Is it possible I can fix it? This all happened when I was trying to flash back to stock.
[Verizon Samsung Galaxy S III] landshark68:
We need quite a bit more info before we can help you out. What version of Android were you running before you tried to flash back to stock, 4.1.2, 4.3, or 4.4.2? Were you stock or running a custom ROM? What version of stock were you trying to flash, 4.1.2 or 4.3? From where did you get the stock file you tried to flash?
[Verizon Samsung Galaxy S III] m4gkman:
sorry about the lack of info I don't have the phone in front of me. I was running 4.3 using hyper drive. I tried flashing the stock 4.3 image and that's when it got stuck.
[Verizon Samsung Galaxy S III] landshark68:
Looking in the development section, I see Hyperdrive is still on 4.1.2, so if you were running Hyperdrive you were on 4.1.2. The problem may have come from flashing the 4.3 stock image on a rooted, bootlaoder unlocked phone. Were you no longer wanting to have an unlocked bootloader and run custom ROMs, because flashing the 4.3 stock image would have locked you down like that. Are you sure you flashed a stock 4.3 file? If so you would probably have to proceed as if you were already on stock 4.3 just to play it safe. This may be you best chance at regaining a functioning phone:

http://xdaforums.com/showthread.php?t=2581166

Unfortunately since you phone does no boot, there is no way to confirm if it is currently on 4.1.2 or 4.3. That would give us a definitive answer on which fix method to use.
[Verizon Samsung Galaxy S III] m4gkman:
I'm sorry for the lack of information again :/ trying to help a friend out by fixing my old phone. Basically I was having space issues with safe strap so I tried to revert to stock and then this horrible mess happened. What you said is most likely true. I looked at that guide, but if it doesn't respond to any cables or power on how can I flash things to it?
[Verizon Samsung Galaxy S III] landshark68:
If you were on safestrap, shouldn't you have had a fully stock ROM in the stock slot? Also from everything I read, you couldn't run Hyperdrive on safestap because you can only run 4.3 TW ROMs on safestrap. If you were running safestrap, that would mean you were on the 4.3 OTA of VRUCML1 and fixes for that would be your best bet, but since the phone won't power on I don't think any of the fixes here would work. Best bet may be to send it out for JTAG repair. I've seen mobile tech videos mentioned a lot for JTAG repairs.
[Verizon Samsung Galaxy S III] m4gkman:
Lol wow I'm really sorry, I've had a lot going on this week and my brain is all over the place. I was confusing my current s4 and the s3. The s3 was running regular cwm and was running Hyperdrive. I was having usual force closes and such and wanted to flash back to stock and I'm pretty sure I used the wrong file.
[Verizon Samsung Galaxy S III] landshark68:
Oh man, that sucks. Do you think you possibly used an s4 file on your s3? If so, you will definitely have to send it out for JTAG repair if you can't get any response out of it. But it can't hurt to check out that thread I linked earlier and see if the SD card method can work for you. Good luck.
[Verizon Samsung Galaxy S III] m4gkman:
so i just got back to my apartment, and i actually have the gs3 with me now. when the battery is in, nothing works or responds. however if I pull the battery and plug it in, the red led light comes on. any ideas?
[Verizon Samsung Galaxy S III] BadUsername:
Hard bricked.
[Verizon Samsung Galaxy S III] m4gkman:
I'm trying the guide right now, will post results after
[Verizon Samsung Galaxy S III] m4gkman:
It worked! you guys are amazing.
[Verizon Samsung Galaxy S III] m4gkman:
okay so now that im back to normal, is everything unrooted and everything? heres what it says in my about phone,

https://www.flickr.com/photos/skaterdave/13392301694/in/photostream/
[Verizon Samsung Galaxy S III] BadUsername:
Yup, unrooted but you're on 4.3 now.

So you need to follow everything in this thread:

http://xdaforums.com/showthread.php?t=2639337
[Verizon Samsung Galaxy S III] m4gkman:
okay, thanks a lot. looks like rooting and stuff with this will now be just like my s4
[Verizon Samsung Galaxy S III] BadUsername:
Exactly, pretty much the exact same.
[Optimus L3, L5, L7 Q&A, Help & Troubleshooting] magmaruss:
Welcome.

I unlocked and rooted my LG l5 e610 and I flashed new roms. First was a SlimKat 4.4.2 which was unstable and I change it to Legacy Carbon with Kitkat 4.4.2. In both roms I can't send text message. Appears inscription "sending" and after 5 minutes pops error. The error code number is 8. What have I do to repair it? Please help me.

Regards.

EDIT:

SOLUTION

1.Write number *#*#4636#*#*

2. Go to: "Information on the device"

3. Tap button "Refresh" next SMS Center Number

4. Delete ",145"

5. Tap button "Update"

It maybe help someone ... THREAD TO CLOSE
[Optimus L3, L5, L7 Q&A, Help & Troubleshooting] magmaruss:
I have problem again. When i reboot my device, smsc number return back to default settings. How to save this permanently?

EDIT: sorry, smsc number remains the same but it doesn't work. I must tap REFRESH and UPDATE after reboot.
[General Questions and Answers] jebus197:
Hi I have bought an LG G2 D802 from eBay for practically nothing. The only thing that was wrong with it is that the screen had been replaced by what I presume is a cheap Chinese copy and after the replacement the screen would seem to turn off randomly (particularly during calls) and could not easily be turned back on again. Otherwise the phone works fine. The only thing that doesn't work is the proximity sensor. However I presume that this is a result of the new screen. Having read around on several forums, it seems that the proximity sensor is extremely sensitive to things like screen protectors, which can obstruct, or limit or prevent the functionality of the proximity sensor entirely. I therefore concluded that the likely issue was because the proximity sensor is likely to only respond to light over a given number of polarities (dark infra-red, placed against face, something similar I presume, in daylight or bright light, nearer the blue end of the spectrum etc). This would simplify how the proximity sensor should work under a number of given scenarios.

In the end the workaround was simple. I simply opened the phone and disconnected the proximity sensor and placed a small piece of insulating tape over the sensors connectors so it couldn't inadvertently reconnected when I closed the phone. The phone is now 100% fully functional, minus the proximity sensor of course. It now just functions like any other normal smartphone. I am naturally more than pleased with this outcome, given what I paid for the phone, which itself is in otherwise mint condition.

However the question I have is that the reason the proximity sensor was included was to prevent accidental button presses when making or receiving a call, when for example the phone is pressed against one's face. However it strikes me that exactly the same functionality should be possible in software? What I am looking for then is an app that will either lock the screen (or turn it off) to prevent accidental button presses in this way while a call is in progress and that will disable itself as soon as a call is ended. I of course need to be able to easily disable it, either from the lock screen, or via the power button, so that for example when I dial an automated dialling service and they want me to press buttons to navigate their menu I can still do this.

There seems to be a few apps around that can do this, but my question is, which is the best? Which is likely to cause the fewest problems for what I want?

I have ordered a new proximity sensor from China in case the proximity sensor itself might be at fault, but really having read that this can cause several problems and is rather more 'gimmicky' than practical, I think a software solution would probably be better anyway.
[General Questions and Answers] remzej:
it should be replace with same hardware sir to be able for your device able to control it.
[General Questions and Answers] pandaman2349:
So has anyone found a fix for this problem aside from replacing the sensor itself? Maybe a build.prop or by using terminal. My phone screen wont stay on because it detects its in my pocket all the time posted screens below of useful info.
[General Questions and Answers] MosesTheTool:
If you don't have the patience to read my story, skip to the solution at the end

Guys (and girls)!, I have found the solution, it took me like 6 hours to figure this out.

I have LS980 (LG G2 ofcourse).

I replaced the screen, and I actually refurbished the screen with LOCA glue myself, it is perfect, but apparently there's an issue with the proximity sensor, due to the specific shade they use to cover the inside of the glass at the location of the proximity sensor.

After replacing the screen, the Knock ON was not working, but KNOCK OFF was working fine.

In the Sensor Box i saw that i was getting half of the light that i was supposed to (on another LS980 i was getting about 800, while on the "faulty" one i was getting 400 light.)

And also the proximity sensor was dead, it showed 0.0 and a fallen plant.

I tried putting some tape, and colored it with a permanent market between the proximity sensor and the glass, and the KNOCK ON began to work, but during calls, the screen would not shut off.

I figured, there must be some SYNC between the light the screen is getting, and the proximity sensor, so i scraped off the paint that was on the glass where the proximity sensor is, so there will be much light coming in, and IT WORKED!!

SOLUTION:

Scrape off the dark paint on the glass (inside) at the location of the proximity sensor. do it gently.

clean it with alcohol so there will be no remains of paint.

don't be shy to press the Thanks button if this worked ;)
[General Questions and Answers] keithlyn:
Thank you work great

Thank you work as described thanks
[General Questions and Answers] MosesTheTool:
Use the thanks button! :fingers-crossed:
[General Questions and Answers] lowpeezy:
I just got my screen replaced, and this is happening to me. Is this something I can do myself?
[General Questions and Answers] serilicv:
My Fix

I apologize for bad english. If anyone knows SERBIAN and want to translate beter contact me.

Before you start to scrach the touch, try this.

On LG D-802 , the ruber thing on the proximity sensor was cousing me promblems. CUT the ruber only the part atached on the light sensor and proximity and turn it around. The big hole that was once on the light sensor(Ruber) comes on the proximity...

And that fixed my proximity. Now the light sensor is covered with the small hole on the ruber and the small amount of light is passing try that hole, try spreading it with heated something.

If questions PM me.
[General Questions and Answers] Yaemish:
I think I am having the same problems with a G2. The digitizer on my girlfriend's phone broke so I replaced it with a digitizer/screen combo. No we can only turn the screen on (power button or knock) when there is a lot of light in the room. If it is dark, the screen will turn on for a second and then turn off. The screen doesn't go dark during a call either.

This problem didn't start until I installed the new screen. I scraped half the paint off but it didn't seem to make a different. I also don't have the screen completely sealed as I didn't have tape pre-cut for the shape of the phone. I wouldn't think that makes a difference but who knows.
[Moto X Q&A] glenroebuck:
Hi I have an ATT Moto X we just got updated to 4.4 from att - Our other phone is an LG Optimus Pro - both are att branded. The LOGP consistently gets much better LTE speeds than the Moto X? Sitting at home, my LOGP gets 16.9 Mbps down and 9.6 Mbps up where as the Moto X is getting 9 down and 4 up?? Literally right next to each other. ???? any ideas?
[Moto X Q&A] drago10029:
could depend on a lot of things. the apps you have installed, if you're rooted or running custom ROM, different radio. has it only been happening since the update?

Also what have you tried to do to fix it? i can make a whole big list but you should always say what you tried first.
[Android Apps and Games] elesbb:
Hello XDA Members!! :D

I love the front facing camera on my phone but hate how there is no flash on the front. Well i made an app that would allow you to shed a little light on the situation. :P

Its quite simple to use!

Find the app 3F in your app drawer and click it.

It will launch your default camera app

Now you will see a button in the center of your screen with "Ready?" in the center.

View attachment 2634333

Once you have finished setting any special effects for configurations for the camera, click the "Ready?" button.

Now your screen will seem to have a whitish film over it. You are then instructed to click the shutter button.

View attachment 2634334

Now the screen is entirely white, this is the flash. After you clicked the shutter button, there will be a red dot visible signifying where the shutter button is.

View attachment 2634335

Now all you need to do is click the red dot to take the actual picture. Once the picture is taken you can review it, however, if you hit "discard" you will need to leave the app and restart 3F to have the flash again.

But thats it! Simple!

I am gonna try to make an xposed module to further simplify this so there won't be any further setup. Simply open your camera app, and another button will appear on your screen, this button will toggle 3F. Once you hit the shutter button, it will automatically show the flash or not depending on your settings.

Hope you guys enjoy this! Hit thanks!! Donate if you feel generous! :) Thanks everyone!
[Android Apps and Games] elesbb:
Here is a with and without picture of me. I know im hideous, don't mean to make your eyes bleed!! :P

View attachment 2634350View attachment 2634351
[Android Apps and Games] TheSmokingAndroid:
this is awesome! Do you think you will bring it to the Play Store?
[Android Apps and Games] SketchyStunts:
Awesome, thanks!
[Android Apps and Games] pakitos:
The idea is great but is not saving the pictures of my ugly face, tried it with normal camera app and Camera Awesome on CM 10.2.1 on a Galaxy S4 1337m :(

Edit: Found them at storage/emulated/0/pictures/Front Flash Pictures
[Android Apps and Games] ariespoge:
Where do the images get saved? I can't seem to find them
[Android Apps and Games] pakitos:
I found them in storage/emulated/0/pictures/Front Flash Pictures
[Android Apps and Games] cwhitney24:
Pretty cool idea man. Good job! Works great on my G2.

ÆONFLEX-4.2 Why Flash Anything Else.

---------- Post added at 08:49 PM ---------- Previous post was at 08:48 PM ----------

Anyone having issues finding pics, the app "Quickpic" is a great photo gallery replacement that finds everything on your phone. Been using it for years.

ÆONFLEX-4.2 Why Flash Anything Else.
[Android Apps and Games] -Jonny-:
For me, they save in default DCIM folder. Works well, looking forward to it being developed
[Android Apps and Games] astonmartin214:
dope it works very well
[Android Apps and Games] TheArc:
Fantastic !
[Android Apps and Games] thahim:
Nice app will give it a try.
[Android Apps and Games] red_hanks:
Nice app. Great addition to my "useful" app collection!
[Android Apps and Games] RussellAlan:
Well done. Looking forward to xposed module.
[Android Apps and Games] Mike B.:
Nice concept but unfortunately it doesn't work very well when the screen brightness is set to "auto". In a relatively dim environment, when 3F would be most useful, the screen is typically also rather dim, greatly decreasing the amount of light reaching the subject. Ideally it would be great if 3F could temporarily force maximum brightness, providing a better flash-like light. Looking forward to future enhancements... ;)
[Android Apps and Games] ezezl75:
awesome!!

This is just AMAZING! great job!
[Android Apps and Games] jacksparao:
Very good idea

Not working in my phone.. E5
[Android Apps and Games] celderic:
Very good work.
[Android Apps and Games] pakitos:
It does go to what it seems to be maximum brightness on mine. I even tested it with Screen Filter on and it was really nice.
[Android Apps and Games] elesbb:
It does set full brightness but I forgot about people with auto brightness enabled. I'll just disable that first then when my app is left I'll enable it again (only if enabled when my app was started)

Very glad to see people enjoying it! I'll have the xposed module up sometime this week hopefully. Got a bunch of school projects to do tho :\
[Nexus 7 Q&A, Help & Troubleshooting] SkOrPn:
Hello

I am wondering if anyone knows if the fstab.grouper file can be pushed into a freshly installed ROM before first boot up?

I am trying to run AOSPAL SaberMod ROM, with All-F2FS, using faux123's new 025 kernel. This kernel has the drivers built in for both ext4 and f2fs, so all I need to do to get it to work is modifying the fstab.grouper file (in the ROM) to work with f2fs partitions, before booting up for the first time. (I think)

The Problem:

I have the fstab.grouper file already pulled from the All-F2FS version of SlimKat. But I can not push it into the zip because it does not exist in the ROM zips. I assume this means its only created during the flashing process. If so, I need to replace that with the already modified version before first boot.

Am I correct so far? lol
[Nexus 7 Q&A, Help & Troubleshooting] SkOrPn:
No need for replying I figured it out.
[Nexus 7 Q&A, Help & Troubleshooting] nlabrad:
You could just flash the fstab file after flashing the rom, am i right?

What did you do?
[Nexus 7 Q&A, Help & Troubleshooting] SkOrPn:
I gave up, and that solved the problem for me... ;)
[Nexus 7 Q&A, Help & Troubleshooting] vincent2014:
But how to flash a single file?

I tried to edit this file in recovery mode. But after I reboot, this fstab.grouper was changed back again.

Strange..

Waiting for your help. thanks
[Venue Pro General] falcon26:
Is it possible to format your Venue Pro and install Windows 8.1 from a USB stick, giving you a nice fresh install?
[Venue Pro General] Suntar:
Yes you can. I redid my whole tablet with a pro version and it worked just fine. I made a system disk and even reinstalled everything back to stock. My next project is to get it to dule boot with Ubuntu.
[Venue Pro General] Haphim:
Somebody posted on a review that this wasn't possible because Dell hadn't released the touch screen drivers.

I looked at Dell's site, and I see that they have the touch screen firmware - but no mention of drivers. How did you address this?

And were there any tricky situations - or was it as simple as doing the fresh install followed by all the drivers on Dell's site?