yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Q&A, Help & Troubleshooting] Curiousn00b:
So... Starting yesterday, about 5:00pm, my battery started charging extremely slow. I plugged my phone back up since the battery went down pretty quick at about 9:30am in the morning. It went to 30% battery and from there, I don't view if it's going up anymore. I took a screenshot at 9:42am and once closer to 10am, also taking another as I typed this. I've also tried 2 different chargers, and multiple outlets.

View attachment 2858218

View attachment 2858221

View attachment 2858222

[MENTION=2872010]rootSU[/MENTION], sorry for tagging you. You just seem to be extremely helpful, and reliable. ?
[Nexus 5 Q&A, Help & Troubleshooting] Curiousn00b:
The last screenshot, I just hit 31%... Literally changed when I clicked the battery tile.
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
When you tried multiple chargers, did you also try different USB cables?

You need to rule out if it is slowly charging or if it is draining quickly whilst charging. Try turning it off and charging.
[Nexus 5 Q&A, Help & Troubleshooting] Curiousn00b:
I attempted that yesterday when I first noticed it yesterday. I plugged it up, and left it off while I went to the market.

I left it plugged up, and I'm now at this from earlier.

View attachment 2858524

I'll attempt that now with another cable.
[Nexus 5 Q&A, Help & Troubleshooting] Curiousn00b:
I'm now at 100% after letting it charge while off.
[Nexus 5 Q&A, Help & Troubleshooting] dicecuber:
Cool

Sent from my Nexus 5
[Nexus 5 Q&A, Help & Troubleshooting] Curiousn00b:
Pointless comment.

The device is still doing doing it. Seemed to charge faster from USB earlier, but now it seems to be back where I was earlier. I'm starting to think that maybe the charging port is the messed up part of the phone.
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
This is why I asked you to charge whilst off. It rules out software as an issue if the same result is seen. If you've changed the cable AND power source, it can only really be the port.

Is it stock unrooted?? Does seem like the kernel gets involved in charging whilst off too , so if you're not stock, I would consider reverting to stock.
[Nexus 5 Q&A, Help & Troubleshooting] dicecuber:
Why cant I be happy for you?

Sent from my Nexus 5
[Nexus 5 Q&A, Help & Troubleshooting] Curiousn00b:
I swapped back and fourth between cables and reboots after returning to stock. I went to stock 4.4 and upgraded all the way through. I then noticed it started to charge faster, or the battery actually read that it was going up. I had Current Widget on my home screen which seemed to be pushing around 900MaH the whole time.

For now, it's back to normal, I believe. Thanks RootSU ~:good:
[Nexus 5 Q&A, Help & Troubleshooting] nonione:
is it back to normal?

my phone is doing the same take forever to fully charge but i dont know if its the battery or the port
[Nexus 5 Q&A, Help & Troubleshooting] Curiousn00b:
Sorry for the late reply, it I've downloaded CurrentWidget where I can see the mA output. The OEM charger seems to be pushing out at 20-300mA. I've plugged up yesterday to an old HTC cable that I have, and although it's all beat up and near its end, it's pushing out 300-600mA.

I believe the original OEM output is near 1000mA. Possible that it was my charger that was faulty. I've been using a lot of different chargers in the past week testing with the mA's.
[G3 Q&A, Help & Troubleshooting] emplox:
It seems as though everyone else can open the camera....touch the screen anywhere....and snap a picture. I don't know if my settings are weird or what's going on, but when i open my camera...i need to touch the screen to focus...then i have to actually press the shutter button at the bottom. How can i turn on touch to take a picture?
[G3 Q&A, Help & Troubleshooting] rparis:
I noticed when I switch it to 10mp and hide the setting, you can just hit the screen totake a photo
[G3 Q&A, Help & Troubleshooting] emplox:
oh wow, all i had to do was hide settings apparently. thx!
[G3 Q&A, Help & Troubleshooting] Lennyuk:
Yes hide the menu then you can.
[G3 Q&A, Help & Troubleshooting] overzeetop:
I'm glad you ran into this. My settings were hidden from the start and I assumed you always had to tap to focus+fire. I might have wondered wtf happened if I'd accidentally made the settings visible!
[G3 Q&A, Help & Troubleshooting] Quantumrabbit:
I feel really dumb... I can't get mine to take a photo at all. Screen press or camera button icon. Can anyone tell me what setting to change specifically? I've totally hidden the settings, I've changed to 10M, 3M, 13M... tried changing storage from internal to sd and back... doesn't matter what I do, I get nothing.
[Verizon LG G3] x86cpu:
I've turned on the developer options and can enable the USB Debugging option to be able to use Titanium backup. However I notice when I reboot the device it gets disabled again. Does anyone know of something/somehow to ensure it's enabled on boot?

Thanks!

---Eric
[Verizon LG G3] x86cpu:
Got it, need root shell of course:

- Remount /system in readwrite mode.

- Add this to /system/build.prop: persist.service.adb.enable=1

- Save, remount as read only.

- Reboot.
[Verizon LG G3] x86cpu:
Well...didn't really work...though it did, any ideas? USB debugging for me has to be manually picked each time.
[Verizon LG G3] x86cpu:
So what seems to work for me upon reboot is that I use SManager and have a script run as root at boot up:

#!/system/bin/sh

echo 1 > /data/property/persist.service.adb.enable

This seems to enable USB debugging upon each boot. The build.prop worked once, but did not seem to keep it enabled.
[Verizon LG G3] JCDinPGH:
Any chance anyone else has come up wth a different way to retain USB debugging on reboot? I just had to rebuilt my phone from scratch by restoring from stock and executing a script at boot up could potentially be fatal. I'm a linux admin so I do know what I am doing but without a unlocked bootloader and the ability to recover from a CWM backup, I'd rather not mess with the OS too much if possible.
[Verizon LG G3] tech_head:
I use Tasker with the secure plugin.

It allows turning on USB Debugging. I use it to turn on USB Debugging as a condition after boot.

Also the worst case with a script, you re-install/flash the OS.
[Verizon LG G3] JCDinPGH:
I've reinstalled my Verizon LG G3 from stock ROM twice now. The first time I rooted it with IOROOT and the USB debugging option stays enabled after reboot. The second time I rooted it with Stump root and the USB debugging option does not stay enabled after reboot. No idea what is different between them but maybe someone else can dig through and figure it out.
[Verizon LG G3] android-incredible:
I have the same problem, when I reboot the phone and open titanium backup.
[Verizon LG G3] bamemanxxa3416:
Could you share how to set this up? Thanks
[Verizon LG G3] tech_head:
Set up a task with the "secure Settings" plug in.

You are going to go into the "System Actions" and select "USB Debugging" then select the radio button to "On" then save.

Now you are going to create a profile that uses an Event.

The even will be a "System" type of event and under system you will see "device boot".

Once you have created the event add the USB Enable task you created.

This all assumes you know how to use tasker.
[Verizon LG G3] android-incredible:
problem fixed......
[Verizon LG G3] bamemanxxa3416:
Very nice instructions and thanks for taking the time
[Verizon LG G3] ericsmart:
because of stumproot, if using iosroot then problem will never appear.
[Verizon LG G3] tech_head:
Actually not true.

I used ioroot and I have the issue of USB Debug not sticking.

That's why I came up with the way to fix it in tasker.
[Verizon LG G3] ericsmart:
but, it's good to have other solution, it's all good that you guided them who have similar problem.
[Verizon LG G3] droople:
I have the same problem as you.
[Verizon LG G3] muiriddin:
tech_head thanks for giving this tasker newb enough bread crumbs that I was able to figure it out and solve the problem (and learn something in the process).
[Verizon LG G3] deathsquad737:
Real easy check usb debug,then plug phone into computer go to your folder that you have adb shift right click mouse all at once open cmd window here check Ethernet mode on phone check rsa cert when prompted type adb devices press enter then adb reboot then enter when LG logo appears unplug phone now your usb debug will always stay checked

WHATSAMATTA U ALUMNI
[Verizon LG G3] muiriddin:
the tasker approach is now disabled and deathsquad737`s approach has caused it to stay checked... Thanks!
[Verizon LG G3] droople:
Hi Guys

I found a easy way to fix it.

1) turn on USB debugging

2) Connect G3 to your PC

3) Reboot your G3 when keep connected to PC

4) Unplug

Now the debugging option will be kept.
[Verizon LG G3] frizzlefey:
That worked! the easiest solution I found. Thank you.
[Verizon LG G3] droople:
Glad to help
[8125, K-JAM, P4300, MDA Vario General] mcwarre:
I have TT6 on my K-Jam

I know that the K-Jam is not a supported device blah blah. It is sooo slow and virtually unuseable (especially changing roads on, say, a roundabout). I have soft reset and only have pocketweather running. Any ideas why it is sooo slow?? TT5 is nothing like as slow.

Cheers,

Mick
[8125, K-JAM, P4300, MDA Vario General] wizzzard:
Actually I found v6 to be faster than v5.21 on my Wizard. 5.21 crawled along with 30+second startup times and would give turn instructions after the junction. If I do feel things are getting slow I usually cold start the GPS, by removing the battery, and once it has found the satelites again it works fine. In my case it is the GPS unit not the Wizard that causes the slow down.

Things to check...

1 What ROM are you using

2 Have you considered overclocking you wizard

3 How many POIs are you displaying

4 How much resources does pocket weather take

I'm using v6 on an unclocked Molski ROM with only PocketGPS speed cameras as visible POI. I can use Mortplayer and make/take phone calls all while navigator never misses a beat.
[8125, K-JAM, P4300, MDA Vario General] mcwarre:
That solved it! It only slowed down recently - which coincided with me using poi edi and putting loads of extra poi's on the device.

Many thanks!!
[8125, K-JAM, P4300, MDA Vario General] corky:
My version 6.010 also runs so slow compared to version 5.21 on my xda mini s which is overclocked to 245mhz. It just can't keep up when going round roundabouts etc.

I only have the "warn when near poi's" enabled for the speed camera database, the seperate speeds, ie 20, 30 40 etc. Nothing is ticked in the "enable/disable poi's"

It does load up in 5 seconds compared to version 5 taking 20 seconds, but after that it's sluggish, shame really.
[Verizon LG G3] J3ff:
I'm not all that impressed by the stock resolution, need smaller icons and more room! ANyone else?
[Verizon LG G3] youngpettyboi:
I've noticed a few screen issues. I think once more apps are converted to being able to make use of this resolution, things will get better over time.
[Verizon LG G3] oneandroidnut:
you don't like the stock 5x5 grid?
[Verizon LG G3] J3ff:
No, I want t take advantage of the 2k screen, Honestly I cant even really tell the difference between stock form g3 and my S5.. the icons are huge and lots of space is wasted on the page indicator.
[Verizon LG G3] JasonJoel:
Easy enough to fix with Nova launcher...
[Verizon LG G3] kpantz:
Totally. You can make eye charts with Nova's grid. I'm enjoying the size of the icons for now, but I figure I'll tighten things up eventually.
[Verizon LG G3] chooven:
if you root you can change ro.sf.lcd_density in /system/build.prop to a lower number like 480 looks very nice. However the LG custom apps will not work.
[Verizon LG G3] tjk639:
You could change the LCD density, if you're root. That's what I did with my S4 to make things look smaller.
[Verizon LG G3] BlueHarford:
changed my DPI to 530 no issues and everything fits better. wanted to try going to 1080p to see if its a real diffrence, when why i tried everything looked too big and not as smooth
[Verizon LG G3] J3ff:
How'd you change it?
[Verizon LG G3] BlueHarford:
edit build prop. or use a dpi changer.. you need to root tho
[Verizon LG G3] jcc2z:
Well

Be careful on the DPI settings. Gotta be root, and I used a DPI changer. It worked fine. Until I couldn't get my actual phone app or contacts to work. I got around this by getting an app, but I was still having issues. I thought it was because I went thru the system and deleted a bunch of apps, accidentally deleting something important. So I did a reset. And doing a reset doesn't fix the DPI settings back. After being an idiot for a few minutes, I learned it was because of the DPI settings. Changed them back and it fixed the issue. So I've just left it alone and went with Nova. I contribute some of that ignorance to alcohol.
[Verizon LG G3] Mistertac:
I edited the build prop and rebooted and for some reason that didn't work for me so I grabbed Texdroider_DPI from the play store and set it to 530 and it worked.

Looks much better!
[Verizon LG G3] J3ff:
I did the same.. super happy with the phone now.
[Verizon LG G3] WingHater:
Did it not make your lock screen wallpapers look all screwy though? It zooms in on the wallpaper and makes a dark shadow on the top part for me. I couldn't find a way around it when lowering the dpi.
[Verizon LG G3] rahb0sse:
Interesting... as I'm reading these, I'm thinking... some of the lettering is somewhat blurry, or has a weird look to it... is that just the IPS or the fact that no one has adapted to 2k reso?
[Verizon LG G3] streetpounder:
530 is great for me. No issues so far
[Verizon LG G3] tjk639:
Yeah, the wallpaper does zoom in, and the smart notice widget gets messed up. Could probably fix it if you could resize it.
[Verizon LG G3] neckbonest:
you can use romtoolbox
[Verizon LG G3] rushless:
I would use Nova anyway, so hopefully no issues with a resolution change.
[Verizon LG G3] pb1379:
Great! No issues with the Play Store not finding applications with the new dpi setting?
[Verizon LG G3] THEbigSWEEN:
Just a cautionary tale for anyone going the route of changing DPI via build.prop... Sometimes it SUCKS not having recovery/back ups...

http://xdaforums.com/lg-g3/help/dpi-g3-t2802827/post54312052#post54312052
[Galaxy S II Q&A, Help & Troubleshooting] americanu197:
So i have my S2 with the upgraded 4.1.2 stock rom from Samsung , but rooted, and go launcher.

I have this setup for the last 2 years or so with all the go launcher upgrades.

My problems are like this:

I have not received Gmail notifications in forever i always have to check manually for mail.

Yes i tried emptying cache and app data and the label notifications are always checked for all my accounts, but still nothing.

I have used Jorte calendar for some time but had to give it up last year cause after a while it would not send me notifications on the dates i set.

Recently i tried using Caynax hourly notification app.

This program doesnt send a visual notification in the notification area but plays a little audio clip similarly to when you receive a message.

And again after using it for a few weeks it just stopped sending notifications.

I tried uninstalling and reinstalling, clearing data and the lot, settings in the app show everything is set up to send me the notifications and yet it doesnt.

I am getting some notifications, Facebook , YT and pushes , to name just a few, seem to work well enough

So if anyone has any experience with something like this please help.
[Galaxy S II Q&A, Help & Troubleshooting] americanu197:
humble bump
[Verizon Galaxy Note 3 General] rushless:
I currently have an S4 32GB, but want the extra display space, since notice web and gaming are better experiences with the Note 3. Was considering the G3, but the Qhd/801 combination is too much of a compromise for me: dimness, battery life / throttling with heavy use.

Question now is would the Note 3 be good, or better to wait for the Note 4? Current perspective:

+ Note 3 performs great and 1080p appears to be a better fit for current display tech and 28nm chipsets. Next year should be the year for Qhd with 20nm chips.

+ Note 3 is easy to root with Towelroot, so can freeze bloat and re-enable sd card writes (KitKat evil). I do NOT want to bother modding beyond that.

- Note 3 signal reception issues since the most recent update. Common issue? Been fixed if it is?

- Note 4 could be special and MAYBE the 805 has enough battery management tricks to offset some of the Qhd power draw. Plus the display will likely be more power efficient than the G3's.

- Note 4 might be locked down and not have root, take long time, or be very complex if can be rooted. Note 3 is simple NOW and I need a device with sdcard writes enabled for third party apps. This is more important to me than freezing bloat with TB.

I would normally just decide to wait, but am concerned VZW will update to kill rooting on the Note 3. I could see being happy with the Note three for two years- assuming no signal reception issues.
[Verizon Galaxy Note 3 General] fletch33:
Note 4 would be my choice without thinking twice. it always gets better and i expect too see better camera, waterproofing (big for me) better screen, etc.....

also it has been noted the Android L (coming soon) had corrected the write to SD from KK.

i do appreciate root for sure but i notice i go less and less with needing it and my list shrinks as Android moves ahead. i freeze all the unremovable stuff i dont use on N3 that cant be removed with Stock but honestly i dont have an internal SD space issue so its not for clearing space. i would do it for space as a challenge but i have plenty so who cares anymore.

as far as freezing the stuff i dont want that is forced on me i find that most of it i can disable anyway in stock and on my Tab Pro 10.1 just for curiosity i left it completely stock with only disabling a few annoying things like TripAdvisor and i have not seen a performance or battery difference from when i first got it and did all that removing etc.. i usually do

so i vote Note 4
[Verizon Galaxy Note 3 General] rushless:
If L allows card writes, I would definitely wait. Not seen that mentioned in spite of that being the number one pushback issue from users with Kitkat.
[Verizon Galaxy Note 3 General] fletch33:
here ya go
[Verizon Galaxy Note 3 General] rushless:
Yep and here is a summary:

Better Storage Framework:

In KitKat, Google introduced a few radical changes to the way storage in general and, in particular, SD Cards worked. Developers complained about the restrictive new storage framework, which broke SD Card support for a bunch of apps and overall was just more limited and not as robust. The good news is that the storage framework is getting a few enhancements in Android L which should take care of this problem for developers, granting full read/write access to directories and subdirectories, and allowing developers to group together file operations. This potentially adds more solid SD card support and may very well fix the current annoyances that developers have with the OS. Seeing as Android will be officially supporting devices with SD Cards in the future, it’s expected to see more and more robust support as the framework keeps getting better.

Looks like Android has reversed their Apple-like course. I am still ticked that ART uses 25% more storage space, but everything is give and take.
[Verizon Galaxy Note 3 General] airmaxx23:
Not to be nitpicky but if the Note 4 is like the S5 it will be water resistant, not waterproof. I won't be getting the Note 4 until I see that it can be rooted, there are just too many advantages to having a rooted device over a non-rooted device. 2¢
[Verizon Galaxy Note 3 General] changt34x:
I'd say all of your pros/cons are spot on. Just be aware that the S4 and Note 2 are generally considered Samsung's pinnacle at producing radios. I replaced my Note 3 due to signal issues, and while the replacement is a lot better, it is nowhere near as good as my Note 2 (which I went back to using during the replacement process). Several places where I thought Verizon just didn't have signal in fact turned out to be due to the phone. When I have -90dbm 3G on the Note 2, it equates to -115dbm of unusable 1X on the Note 3. You may live in a good signal environment (unlike me), but just be aware of what you may be getting into.

The S5 also has poor signal, from my experience and from others' posts, so I won't hold my breath for the Note 4.
[Verizon Galaxy Note 3 General] kinstre11:
Personally I would wait till the Note 4 is announced. It should be in September. There are many rumors about the Note 4, but so far no officially confirmed features. Android L may not come with release but would instead be an update, much like this past year with kitkat as Google may not allow another company to officially release a phone with the new Android before they do. If releases follow last year's pattern the new Nexus (or possible new Google flagship phone) would release about a month after the N4. Not to mention the rumors about the Nexus 6 with a 6 inch screen. Rumors about the Note 4 include possible form factor changes including a version with curved glass. The N4 may be overshadowed by the expected fall release of Samsung's future flagship Samsung F.

As for the N3 it is a powerful device and with root there is plenty of added potential. From everything I've read about the radios, the newer N3's actually have better signal than the original releases, however there is certainly no consensus in the community other than that most report poor signal & dl speed. We may see yet see a significant improvement in this department over the next year as Verizon continues to roll out XLTE across the country. The other benefit for N3 is our developers. While I'm sure once the N4 is released it won't be very long before root is gained and developers start to get to work, ATM we have a few dedicated devs that are looking to keep the N3 alive and feeling new for a good time to come. With an S5 port, maybe an N4 port in the future, and the upcoming Alliance rom, if you ever get to the point where you want something fresh and decide to go custom there would likely be support for at least a year after the release of N4 (maybe I'm wrong, but from talk from the devs I don't think I am).

No matter what you decide, I know that for me if I jumped the gun and a month or two later the next BIG thing came out I would probably kick myself, especially considering the price tag on our phones. Good luck deciding (or waiting lol).
[Verizon Galaxy Note 3 General] ronaldheld:
September is not that far away. Wait for the official N4 announcement and decide then.
[Verizon Galaxy Note 3 General] KennyG123:
There is a thread in the stickies to discuss upgrading and other devices

Thanks

FNSM
[One (M8) Q&A, Help & Troubleshooting] hellobbn:
My device model is HTC M8t.And I flashed the ViperOne M8 just now.But I didn't flash the boot.img in the zip file but I flashed M8T official boot.img as the viper boot can't work on my device. As a result,I can't turn on wifi and the camera app.I guess the main reason is the boot.img.So I wanna to know how to fix the problem. Many tks:)
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
Hardware like WiFi and camera not working are indicative of a kernel/ROM mismatch. Viper is probably not compatible with that kernel; and therefore not compatible with your variant.
[One (M8) Q&A, Help & Troubleshooting] hellobbn:
So what should I do to make viper compatible with my device?
[One (M8) Q&A, Help & Troubleshooting] hellobbn:
One more question, should HTC devices back up EFS before flashing ROMs?
[One (M8) Q&A, Help & Troubleshooting] hellobbn:
Anyone else?
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
You might inquire with the developer of Viper for support of your device. But if the kernels are different, it may be difficult for the dev to get it working. There isn't anything you can do to make it work, as far as I know.

---------- Post added at 10:11 AM ---------- Previous post was at 10:09 AM ----------

I've never done it when flashing ROMs on HTC devices.