yashsingh1/xdaforums huggingface dataset:
[Upgrading, Modifying and Unlocking] CatShitOne:
Toshiba e750 upgrade

Hi i just recently got a toshiba e750 pocket pc and i would like to know if there is a wm06 rom for the e750. Its running wm03 but i would like to get a upgrade for it
[OS Porting] hanskarakshay:
How to install it safely for moto g3
[Galaxy Note5 Accessories] Febby:
I recently got ahold of a Tronsmart 18W Quick Charge 3.0 USB Turbo Wall Charger. For the future reference it can be bought via this link below:

http://www.amazon.com/gp/product/B015ZJKWFS

I should also note that this is aquick charge 3.0 charger has passed Qualcomm inspection to their standards with Qualcomm. I reached out to Tronsmart and got a picture of the verification.

Some quick information regarding quick charge 3.0

"Quick Charge 3.0 is engineered to refuel devices up to four times faster than conventional charging. It is designed to charge twice as fast as Quick Charge 1.0 and to be 38 percent more efficient than Quick Charge 2.0."

Source - https://www.qualcomm.com/news/snapd...e-30-next-generation-fast-charging-technology

So lets begin this review.

1 - product shipping - The product arrived timely and fast but I was away on vacation so I couldn't post it as quick. It came in an all white box with the typical sealing. It's all recycling friendly so I love that. Yes you will read that in just about any review I post! Help save this planet. :)

2 - Items in box and specs of product -

Package content*

1 x Quick Charge 3.0 Charger*

1 x Quick Charge 3.0 Charging Cable*- 6 ft 20AWG

1 x Warranty Card.

Quick Charge 3.0 Ports*

Input: AC 100-240V, 50/60HZ.*

Output: DC 3.6V-6.5V/3A, 6.5V-9V/2A, 9V-12V/1.5A*

Note : only Quick Charge 3.0 compatible devices can get 27% faster charging speed compared with Quick Charge 2.0 Charger.

3 - Product pictures and modeling!

4 - product usage -

I do not currently have a quick charge 3.0 device to take advantage of this amazing 3.0 feature but as soon as I get one (hopefully galaxy s7 supports it) I will post more updated information. I tested it on my nexus 6 and o found it charges it amazingly quick. Perhaps quicker than my oem charger from Motorola? Perhaps it's all in my head? :)

The usb cable included performed much better than previous cables from tronsmart! It has a nice AWG which definitely in my opinion works long term wise.

My note 5 (gold) was able to charge fully at quick charger 2.0 speeds. Although you can't see when screen is on due to Samsungs limiting of the on screen charging rate.

It works great so far and doesn't make any humming noises like previous units bought from aukey. Mind you aukey doesn't even reply to emails. Good job for not making it an L shape charger too, Tronsmart.

5. Overall summary? If you're looking to replace a faulty 2.0 or even a tradition charger you should avoid paying $20+ at your local gas station or CVS for a slow charger when you can go on amazon and buy one of these Tronsmart quick charge 3.0 units for $16.99! Not only that but it's future proof for any new devices.

If you have any questions that you would want me to answer please feel free to post them here so that I can try my best to answer them. :)
[TouchPad Q&A, Help & Troubleshooting] tejtank:
Hello,

I'm trying to install the new Marshmallow on my hp touchpad but running into below issue:

I've tried several combination of gapss, rom using Touchpad Toolbox v42 but keep geeting error (Incompatible GAPPS/ROM versions None/6.0)

Here's what I'm trying:

Recovery

2.8.3.0 TWRP recovery with MTP support.

ROM

ev_tenderloin-6.0.1-testing-2016.01.04

ev_tenderloin-6.0.1-nightly-2016.01.03

GAPPS

open_gapps-arm-6.0-nano-20160106

BaNkS-Dynamic-GApps-6.x.x-10-20-15

I also tried installing without gapp, but TPToolBox gives error saying Gapps file is missing (or found 0 gapp file).

Let me know if there is a combo of known files that works. - Thanks
[TouchPad Q&A, Help & Troubleshooting] jcsullins:
Try using the gapps-601-base package from here:

http://xdaforums.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368

and one of the recoveries listed under "Compatible DataMedia (DM) recoveries" from the TPToolbox thread here:

http://xdaforums.com/showpost.php?p=52765140&postcount=3
[TouchPad Q&A, Help & Troubleshooting] tejtank:
Wow - Thank you!

That worked.

For anyone else in same situation, following worked for me:

ROM:

ev_tenderloin-6.0.1-nightly-2016.01.03

Recovery:

update-TWRP-jcs-dm-tenderloin-20140612b

GAPPS:

gapps-601-base-20160105-1-signed

Thanks again jcsullins
[TouchPad Q&A, Help & Troubleshooting] sdemun:
Same issue not resolved

Hello;

I am using TPToolbox-2015-01-08-v42 to try to install the following.

ROM:

ev_tenderloin-6.0.1-nightly-2016.01.17

Recovery:

update-TWRP-jcs-dm-tenderloin-20140612b

GAPPS:

gapps-601-base-20160105-1-signed

I keep getting an error that says that gapps-601-base-20160105-1-signed appears to be corrupt and the installation aborts. I have tried several times to re-download this file, I ave tried several times to wipe the data and start fully clean but still it shows the GAPPS file as corrupt. Any ideas?

Thanks
[TouchPad Q&A, Help & Troubleshooting] tejtank:
looks like the only difference from what I used is the ROM version.

I guess you can try the same Rom that I did and then later update to another nightly.

Others may have better ideas.
[Moto X General] Josephdbrewer25:
I found a website to get stock firmware files for the Moto X 2013

https://androidfilehost.com/?a=show&w=files&flid=44728
[Moto X General] sd_shadow:
I believe tomsgt uploaded those when motofirmware.center shut down
[Moto X General] Josephdbrewer25:
I'm glad tho. Just thought I'd share it
[Moto X General] smohanv:
Hi OP

Thanks for sharing.. very handy.. i had hard bricked my phone. My phone only boot in to "fastboot" mode... no recovery and nothing... This XML will help me to bring my phone back to life. Thanks again.
[Moto X General] Josephdbrewer25:
Hey, no problem. Just thought I'd share. I'm glad I found it too. I had to reflash the radio, lol. Which variant do u have?
[Moto X General] smohanv:
Mine is EU variant (UK retail). I had sent my phone to Moto service centre thinking that they would fix it. After 6 weeks they asked me to pay £14.40 and returned the phone unrepaired with the reason that my phone was rooted. Now I have to find my way of fixing it.
[Moto X General] Josephdbrewer25:
Wow. Hope that site helped, pm me if u need any help
[Moto X General] Josephdbrewer25:
Yes just found out myself the Motorola tech support sucks. For a carrier unlocked Android phone how do u find out about updates? They said contact the carrier..why when the device isn't carrier branded..

Forgive me as this is off topic
[Moto X General] smohanv:
I forgot to mention one more thing here. When the device was returned to me, the back cover was broken. The service centre didn't bother breaking the back cover. I have escalated the case and still pending with them for the past three days. **** services. I regret having selected Moto product. I recently bought Moto Style which I am now thinking that I should not have selected moto product anymore.
[Nexus 6P Q&A, Help & Troubleshooting] exSD:
How do I setup Sprint WiFi calling on a 6P?
[Nexus 6P Q&A, Help & Troubleshooting] jawmail:
You can't until Sprint allows it. Currently it only works on iphones.
[Nexus 6P Q&A, Help & Troubleshooting] dakoellis:
It definitely works in more than iPhones because I had my on my g3. There were others as well
[Teclast X98 Air 3G] stefan129:
Hi,

Does anyone know if there is a touch screen fix for air III (M5C6) in Android 5?

There seems to be a common problem where the thouch screen no longer responds and the fix is to replace the boot.img file with a modified version.

In Android 4.4 the file provided by mirek boot(kernel)_touch_fixed_for_mirek190_roms 4.4.img fix the issue but for Android 5 i can not find a corresponding file for Air III. The BOOT.7z file that should fix the problem does not contain a file for Air III.
[Teclast X98 Air 3G] mirek190:
I got the same problem recently on my x98 air 3g ( c5j6 ) so I have test device now and should find solution :)

I built custom kernel from source but need more work ....
[Teclast X98 Air 3G] stefan129:
Thanks mirek, great to hear that you are looking at the issue, I hope you are able to solve it :)
[Teclast X98 Air 3G] Kwasniewski:
Mirek, I have the same problem with c5j6 - touch is not working on Android 5.0

Your kernel C5jx-new.img not working too.

PS Błagam, wymyśl coś jak rozwiązać bo Android 4.4 chodzi na tym tablecie fatalnie :*
[Teclast X98 Air 3G] hbeil:
Touchscreen issue investigated

Mirek Same issue here. c5j6 worked fine under Android 5 until a few days ago and your latest ROM Version 7 did not change anything. Touch is just not there anymore. It works in windows though. The only thing I can do is hook it to the host computer and replace files. I got the boot image from Teclast. Can I just replace it on the TPad? Where?

Thanks, Hartmut , Berlin

Update. I flashed the Android partition completely with X98_Air_3g_android_5.0_mirek190_v7.0, used the included boot.img, replaced it with the C5jx-new.img , it hangs while booting, tried the boot image that Baidu provides.

with the same effect.

Booting with the original boot.img from mirek190 does start the Tpad, but without touch, I can't do much... ;)

On the bright side, I can boot into windows, and everything is fine. So for now, it is a Windows 10 only Pad.

One more update: I started the Tablet with a mouse attached. It works (now) and I can now use the tablet, but I am trying to use the settings section to activate the touchscreen. No success, when getting into the about this device section and click on hardware, settings as app is crashing. Something is fihy, but no help in sight. I wish the boot images that supposedly fix the problem would not hang...

Please, if anyone knows a fix, tell me. I am ready to send the Pad back to the manufacturer.

Last update:

I Downgraded to Mirek 4.4 and applied the fix that is out there, replacing the boot.img – everything working again

Hartmut
[Teclast X98 Air 3G] Kwasniewski:
up! anyone?
[Teclast X98 Air 3G] kvandaalen:
Same problem also on Air II

I am also suffering from this issue. Using a HG7N with mireks V5.0 rom with android 5.0 on a teclast Air II. Suddenly the touchscreen does not react anymore in android. In the dual boot screen and windows 10 it works perfectly. Tried installing a fix (based indeed on a new image file) but that did not help. Then installed the Mirek V7 rom (latest version for Air II) and that did not help either. :(

Hope anybody can help met getting some life back into this tablet.
[Teclast X98 Air 3G] axel_flame:
Hello. Also, as in the previous post (have problem with HG7N), I have not worked touchscreen in Android (in Windows all ok). I tried all versions of boot.img. What to do?
[Teclast X98 Air 3G] Mishka_BG:
oh! Hello,

here is special topic about my trouble. I have the same fault with touch on Teclast x98 air III (M5C5, 32 GB).Touch stopped to work under mirek 190 v7.0. I tried different version 5.1(+special kernel - boot(kernel)_touch_fixed_for_mirek190_roms 4.4) - 6.0 - 7.0. Under 4.4 kitkat (v 5.1 + kernel) I got a scaled touch response. See the attached pic.

View attachment 3628159

Blue lines show the area where I get response from touch when I tapped from right top to down and then to the left side.

I didn't try to install Windows. Are there any solution for Android? Thank you.
[Teclast X98 Air 3G] Mishka_BG:
Is it possible that after update to new BIOS 2.05 for M5C5 touch will start work? May be somebody tried.
[Teclast X98 Air 3G] stefan129:
Hi,

Anyone tried?

Mishka_BG, why not try to update, should be safe if you have M5C5. I have air III 64 (M5C6) so I'm hesitant since I do not know if it is compatible and I'm quite sure I will loose Windows.
[Teclast X98 Air 3G] Mishka_BG:
I'd like to wait for customer response first, may be I can replace the tablet by warranty.

Some people from parallel forum bricked M5C5 after flashing new BIOS 2.05. It depends on method of flashing as I understood.

Which method of flashing BIOS is working?
[Teclast X98 Air 3G] Mishka_BG:
Hello,

I flashed new BIOS 2.05 and Android 5.0 (files and manual from here: http://xdaforums.com/x98-air/general/current-best-rom-bios-x98-air-iii-32gb-t3310436)

Touch didn't start work. :(
[Teclast X98 Air 3G] Bolemo:
Up. Have an X98 Air II (HG8N) that I had on original 4.4.4 (rooted and cleaned some). Just changed ROM to Mirek190 Android 5 v7, and same problem as all of you: it boots fine, works with a keyboard or a mouse, but no touchscreen. Any fix?
[Teclast X98 Air 3G] Kwasniewski:
http://techtablets.com/forum/topic/ttt-fix-x98-air-devices-touchscreen-functionality-in-android/

Works only on stock 4.4rom for me
[Teclast X98 Air 3G] Bolemo:
Yes, the specific boot.img works for 4.4.4 versions. All we need is a boot.img for 5.0 versions.
[Teclast X98 Air 3G] xinux87:
I'm with your same problem, the touchscreen works but only the topleftcorner... any solution?
[Teclast X98 Air 3G] Mishka_BG:
The only soultions for me was using Windows 10.
[Verizon HTC One (M8)] rajivc9:
Hello guys,

I rooted my device few months ago and it was running like a charm (even though the root access was gone after the device restarts) because I don't reboot my device very often and even though the device reboots due to low charge or something i used to root it again and use my apps flawlessly. But recently, the device started rebooting just after rooting it using king root. Whenever I root it, the device reboots and root access is gone. Why is this happening? Please help :(
[LG V10 Themes and Apps] Paladin_IMS:
You obviously need root for this. You also need titanium backup, or something else to backup/freeze/uninstall system apps.

This was one of my major complaints about this phone when I first got it.

For those who don't know, after changing your DPI and rebooting, your SystemUI would constantly force close, causing an unusable device unless you have a computer nearby. And even then, if you didn't use adb before on your PC and allow your computer to be trusted on the device, you had to go as far as completely installing a new ROM. Thankfully, I managed to find a temporary solution that will no longer involve weird tasker scripts or other odd workarounds(this is still a workaround, though).

Basically, in short, the SystemUI force closes were due to the always on clock on the second screen. Even disabling the second screen while the screen is off would not fix this.

D/MiniClockView(12438): [MiniClockView] setFontData = font_default, locale=en
W/LGMiniClockService( 6273): [setFontData] fontname => font_default, locale=en
I/LGMiniClockService( 6273): [makeColorsFromPNG] fontname => font_default, locale=en, number=0
I/LGMiniClockService( 6273): [makeColorsFromPNG] width = 32, height = 1540
D/LGMiniClockService( 6273): [setFontData] font_each_num : length => 49280
E/LGMiniClockService( 6273): [setFontData] font_each_num.length is less than expected!!!
D/MiniClockView(12438): [MiniClockView] setFontData failed, retry after 200ms
D/MiniClockView(12438): [MiniClockView] initFontImage
D/AndroidRuntime(12438): Shutting down VM
E/AndroidRuntime(12438): FATAL EXCEPTION: main
E/AndroidRuntime(12438): Process: com.android.systemui, PID: 12438
E/AndroidRuntime(12438): android.view.InflateException: Binary XML file line #153: Error inflating class com.lge.signboard.clock.AlwaysOnClockView

I'm fairly incompetent when it comes to android development, so if someone else manages to fix this that would be great. I don't know where to start. However, that doesn't mean we can't just disable the app completely.

Open Titanium backup and search for "mini"

Backup the app, and then uninstall it. I'm not sure if freezing it will work as I don't have the donator version of titanium backup, so if you do and it works, please report back.

So, as for compromises, this does exactly what you expected it to be. It gets rid of the clock on the second screen when the main display is off. Not a big deal for people not using the second screen, but if you are, you're going to have to deal with it, wait for LG to fix it in the marshmallow update, or wait for someone from these forums to fix it.
[LG V10 Themes and Apps] Rhokk:
Ok I played around with this. I made a backup of this mini file and then uninstalled it. Set my entire phones DPI to 340 and restarted. Upon reboot, system Ui was 340 but all LG apps didn't work. Phone, contacts, calender, messenger, camera, and settings also didn't work. Tried using AppSettings (xposed) to set these back to 640 to get them working. Only phone and contacts would take after selecting 640 for them. Others still forced crashed.

Then I had an idea. I restored my nandroid and this time I left my DPI at 640 and only changed system UI to 340 via AppSettings ( small I know). Restarted and all LG apps work along with those core phone items also.

Second screen still works but the only thing missing it's the actual numbers for the clock. It's funny cause the 'am' 'pm' still show.

Not a perfect fix but the best one so far. God job to the OP for finding this!
[LG V10 Themes and Apps] Amd4life:
AWESOME!!!!
[LG V10 Themes and Apps] f2bacon:
I'm not sure where 340 dpi comes from. I like to set mine to 532 so when I did that and crashed system ui I found this thread. If you set app settings to have systemui and com.lge.miniclock.font.default to both be 640dpi (system default) then you cause use app settings or textdroider to change the overall dpi to whatever (532 works great and looks great too fyi) but I suggest keeping 640 on camera and any LG apps that force close. It's pretty similar to how it was on the g4.

tl;dr

use app settings to set camera / systemui / miniclock to 640dpi before you do ANYTHING else regarding dpi.
[LG V10 Themes and Apps] virus_egypt:
In the first .. i changed my DPI to 530 and working till reboot, i have to put it back to 640 and set it again to any value i need.

When i waked up i found my device reboot itself!

the System UI FC, So i plugged my device to my lap to revert the DPI to 640, but remembered that i was installed new windows 1 week ago and never connect my device to it, so the ADB need to authorize the lap in my mob!!!

as per the below screenshot:

And i can't authorize the device because i can't control my mobile, any help?
[LG V10 Themes and Apps] f2bacon:
When I had the systemui force closing I couldn't get past it, I had to restore from a nandroid backup.

Also now I'm looking at the second screen being set to 640 and it does seem a hair off compared to stock. All the stuff is there but it's misaligned. I looked it up and technically the v10 is at 513ppi so I'm gonna test that instead of 640. Do 640 for now unless you wanna test what works too. As long as systemui is at 640 the phone doesn't crash.
[LG V10 Themes and Apps] Paladin_IMS:
The point is to make the systemui also smaller, so you don't have to deal with the ginormous notification tray or anything like that. That's why I would freeze the clock instead of using app settings on the systemui. You might be able to use app settings to change the dpi of the clock to 640 but I'm not sure it applies on boot or how app settings works.
[LG V10 Themes and Apps] vnixnj:
On the T-Mobile variant, I found that as long as I set "com.lge.miniclock.font" to 640dpi using AppSettings, I can change my entire dpi to 530 without any issues. (if you go any lower than 530, the LG apps will crash with the exception of the Camera which needs to be set at 640 to not FC when fully zooming in)

The odd issue is when I choose to show Date & Time on the second screen while the main screen is off. Within the standard format of texts (weather, day, date, AM/PM, time, battery), the time (h:mm) has a noticeably larger font than that of the other texts.

The only time I was able to align the said texts was when I manually set "Android System" to 640dpi, which obviously isn't very optimal.

This leads me to think that the texts are controlled by the dpi of "Android System" with the exception of the texts showing the time, which are controlled by the dpi of "com.lge.miniclock.font", of which we can't alter the dpi without force closing constantly. Freezing "com.lge.miniclock.font" did not make a difference, but hopefully that's enough to helps some knowledgeable users to figure out further on how to fix this issue.
[LG V10 Themes and Apps] TriBeard:
I tried doing that with my T-Mobile version and I still got force closing system UI. Uninstalling that app was the only way to fix it for me
[LG V10 Themes and Apps] yugendreams:
Same here. I'm also using the T-Mobile variant.
[LG V10 Themes and Apps] R4NDR01D:
How can I get to Titanium if I'm getting System UI FC?
[LG V10 Themes and Apps] Paladin_IMS:
you don't. you use ADB to change the dpi back. if you can't do that, you need to reflash your rom
[LG V10 Themes and Apps] miromeir:
Thank you very much!!!! Thanks to you lg v10 has custom DPI.

Work for H960A
[LG V10 Themes and Apps] RussianBear:
This didn't work in my case, so I made a flashable build.prop zip from a stock fw, and presto.
[LG V10 Themes and Apps] jak989:
[MENTION=1336183]RussianBear[/MENTION]

could you provide the flashable build.prop zip please. Would be great!
[LG V10 Themes and Apps] RussianBear:
There you go. It's very simple. Find any random flashable prop online, then simply sub the one from stock Rom into that zip folder on your pc.

https://drive.google.com/file/d/0B2QhC3Ym2vatRkpJeEtyLXVTY3M/view?usp=docslist_api
[LG V10 Themes and Apps] lonelybear:
[MENTION=6374625]Paladin_IMS[/MENTION] , Can you teach me how to get the log in your first post?

I dig on the apk that cause the problem (com.lge.miniclock.font.apk) and find this in \com.lge.miniclock.font\res\drawable-xxxhdpi-v4

https://imgur.com/H17eVmB

the image is the font for the mini clock and measured 36 x 1760 in dimension.

based on your log( please specify what dpi you set when u get this error?)

I/LGMiniClockService( 6273): [makeColorsFromPNG] width = 32, height = 1540
D/LGMiniClockService( 6273): [setFontData] font_each_num : length => 49280
E/LGMiniClockService( 6273): [setFontData] font_each_num.length is less than expected!!!

It seems com.lge.signboard.apk ( the one controll the 2nd screen) expecting predefined font_each_num.length

Perhaps it is 36x1760 =>63360?

For this we need to see the log when the app loading mini clock font on native 640dpi.

If it true then we can simply tweak the image

(Easier said than done:p, already tried using modified image 27x1320 and create new folder \com.lge.miniclock.font\res\drawable-xxhdpi-v4 but failed )
[Xperia Z1 Compact Q&A, Help & Troubleshooting] Rodders_28:
My original battery was not doing very well, so I bought what the seller said was a new, genuine Sony battery.

I put it in, all seemed ok, it was definitely better than the old battery.

But if I play a game, the phone gets hot and the battery disappears pretty quick. I'm having to charge it a few times a day.

Doesn't sound like a genuine battery to me, or has my phone gone dodgy?

I put a temperature monitoring app on there, says the battery is hitting 42/44'C when playing games, is that normal?
[Galaxy Tab S2 Q&A, Help & Troubleshooting] egogz:
Hey guys, hopefully someone here can point me in the right direction. Looks like i got screwed with my Tab S2. I bought a 9.7" cellular version from someone on Kijiji (Equivalent to Craigslist in Canada) and it was working just fine. I installed some apps and was just playing around with it. About two days later it started freezing and restarting when i would play a game or watch a video. Since then it has gotten progressively worse. I boot it up and 30 seconds to a minute later it turns off on its own. I thought it may be a software issue so i did a hard reset but the problem still persists. I took it into a Samsung repair center and they said that it is a pre-production model (IMEI is 00000000000000) and they cannot help. Any ideas what i can do to repair it. I just hate the idea of having a $400 paper weight