yashsingh1/xdaforums huggingface dataset:
[Xperia Z3 Q&A, Help & Troubleshooting] Rizera:
OK, here are the results for my charging.

Up to 40%, I have recharged my phone with a Moto Maxx (Droid Turbo) Quick Charge 2.0 charger, then I changed to the stock/original Xperia Z3 "quick" charger (EP881), which I have no idea why is named "quick" charger by Sony...

Notice the Moto Maxx charger got me a 1600ma/h charging, which would charge my phone in about 2 hours. The EP881 Sony Stock charger got me around 900ma/h charging. That would led me to a total recharging time of more than 3 hours.

I still could not test different Quick Charge 2.0 chargers, but I can assure that the Moto Maxx/Droid Turbo one DOES work with the Xperia Z3.
[Xperia Z3 Q&A, Help & Troubleshooting] Entropy512:
It IS QC2.0 compatible, HOWEVER: The charging setup is such that you'll only see a benefit in cases of charging while the system is under load.

The Z3 kernel limits battery charge current to 1.5A (approximately 0.5C) regardless of what charger is attached.

If you attach a non-QC2.0 charger with a VERY high quality cable (less than 3 feet with 24 gauge wire or thicker), you'll typically see 1.5A of battery current WHEN THE SCREEN IS OFF. Even in that case, you won't see consistent 1.5A input into the battery (use CurrentWidget)

Turn the screen on and you will NOT see 1.5A of current going into the battery with a non-QC2.0 charger, as the battery power in is (Vbus input limit - system load)

However, if you have a QC2.0 charger, even with a thin USB cable that would normally lead to extremely poor charging performance, you'll see 1.5A go into the battery under almost any load condition.

TL;DR - It's QC2.0 capable but you'll only see a difference when the device's screen is NOT off. If the device is plugged in to a high-quality USB cable and the screen is off, you'll see only minimal differences.

You'll see a MASSIVE difference if you use one of these cables - http://www.amazon.com/StarTech-com-Micro-USB-Cable-UUSBHAUB3RA/dp/B001AR4NC8/ - These cables aren't particularly good for charging with a standard charger because they're thin - but that same "problem" makes them good for connecting to a phone in a car mount. (I cannot find heavier-gauge cables with a right angle connector). If you use a standard charger with them, you'll find your battery draining with Google Maps Navigation. With a QC2.0 car charger - the battery will actually charge while running Navigation.

I've confirmed QC2.0 functionality with a Tenergy wall charger, a Powermod car charger, and an Aukey external pack. The Tenergy wall charger is nice in that it has an indicator light - blue if in "standard" 5v mode, green if in 9v or 12v QC2.0 modes. Sony's stock chargers are NOT QC2.0 capable.
[Xperia Z3 Q&A, Help & Troubleshooting] Rizera:
I find it interesting that you say this, because even with the phone left untouched I can't even get 1.0A charging with the stock charger and stock usb cable. As I have shown in my post before, I get a 0.8 to 0.9A charging, and yes, the screen is off. I have not touched my phone during this time at all. What can I conclude from that? Isn't the stock usb cable good enough?

Moreover, if this limit is set the by Z3 Kernel, it is possible to edit in the stock kernel, isn't it?

Regards.
[Xperia Z3 Q&A, Help & Troubleshooting] Entropy512:
In my case, I was using a Samsung tablet charger. These actually increase their voltage slightly under load to compensate for cable losses. I forget what Sony's stock charger is rated - but if you're only seeing 0.8-0.9A, then it might be on the weak side (just like the 2012 Nexus 7 had a weak charger). I pretty much exclusively use Anker multiport power supplies and either Monoprice or Anker heavy-gauge (24AWG for Monoprice, supposedly 21 for the Anker, lower is thicker/better here) cables.

A QC2.0 charger makes the cable selection FAR less important - transferring a given wattage requires less current at 9V than at 5V, which leads to less resistive losses in the cable. Same principle as why power grids use hundreds of kilovolts for long-haul transmission lines. :)

Yes the kernel could be altered, but since the battery is nonreplaceable, few responsible developers are going to do it. Heck, sony AOSP currently disables the HVDCP service due to paranoia about ensuring that ALL battery management protection mechanisms are in place before turning it on in AOSP. (I am fairly certain they ARE all there, but I want to do some more digging.)
[Xperia Z3 Q&A, Help & Troubleshooting] danny the great:
HVDCP?what is that?so if the kernel is altered then quick charge 2.0 can be used?so now my z3 d6653 can only charge a maximum current of 1.5 A?
[Xperia Z3 Q&A, Help & Troubleshooting] Entropy512:
HVDCP - High Voltage Dedicated Charging Port - I think Qualcomm is actually attempting to get QC2.0 standardized (they're already licensing it to non-QCOM OEMs - the Galaxy S6 supports it, as does NVidia's SHIELD Tablet, NV doesn't market the capability AT ALL but it's there!), so there are lots of references to naming conventions consistent with the USB Battery Charging Standard

DCP - Dedicated Charging Port (dumb wall charger)

SDP - Standard Downstream Port (PC port, limited to 500 mA)

CDP - Charging Downstream Port (PC port, allows for higher current) - Android device support for CDP detection is pretty rare, lots of kernel developers will risk damaging SDPs by simply forcing CDP behavior from an SDP

Even without kernel alterations, Quick Charge 2.0 is used - Quick Charge 2.0 is defined as delivering 9v or 12v from the wall to the device in order to deliver more power. It's up to the OEM whether to dump more of that into the battery, or simply to use it to allow for higher total system power. Without QC2.0, the Z3 can only charge at full rate in the absolute best of circumstances (screen turned off, even then it doesn't always reach 1.5A) - with QC2.0, the Z3 can charge at full speed even with the screen on.
[Xperia Z3 Q&A, Help & Troubleshooting] danny the great:
So that means I juz connect my z3 to a QC 2.0 compatible charger which is 9v and it can charge faster?i ask sony and they say quick charge is only supported in japanese version.if I connect to a QC 2.0 compatible charger,how fast will my z3 charge?
[Xperia Z3 Q&A, Help & Troubleshooting] Entropy512:
Yes, it will charge faster.

How much faster depends on what you're doing. If the device's screen is off and it's idle, only a little bit faster.

If you're running Google Maps Navigation in a car, the difference will be massive. As in "charging at a decent rate vs. discharging despite being connected to a power supply".
[Xperia Z3 Q&A, Help & Troubleshooting] Rizera:
It will charge in around 130 minutes with QC2.0, and around 210 minutes with the stock charger (EP880).

At least that's how it works for me.
[Xperia Z3 Q&A, Help & Troubleshooting] danny the great:
Ok,i will go buy a QC 2.0 charger.thx
[Xperia Z3 Q&A, Help & Troubleshooting] danny the great:
Can I use tenergy wall charger that support quick charge 2.0?how fast will it charge?
[T-Mobile, Samsung Galaxy SIII] showmeaction:
I've looked everywhere for the solution to this issue but I'm not getting anywhere.

I just did a full wipe and installed slimkat 9.0. Restored all of my apps using Titanium Backup, and all of the apps and their data restored flawlessly. Except Messenger, when I would restore the apps data and go to see a conversation, all of the conversations change order on the screen and it's as if the messages are all being deleted because it keeps on showing the preview for older conversations as the conversation order changes. Then I am left with no conversations whatsoever.

Any help would be appreciated
[T-Mobile, Samsung Galaxy SIII] serio22:
You mean the sms app? Make sure it's not set to delete messages after a certain limit per thread
[T-Mobile, Samsung Galaxy SIII] showmeaction:
I mean the messenger app, the one Google released not too long ago. You can't set the message limit
[T-Mobile, Samsung Galaxy SIII] serio22:
Do the messages show with another sms app?
[T-Mobile, Samsung Galaxy SIII] madoshields:
I'm having this exact same problem on a Droid RAZR HD running CM11. The backup is from the same phone using stock Kitkat 4.4.2. Any help?

Sent from my DROID RAZR HD
[8125, K-JAM, P4300, MDA Vario ROM Development] Mr. Vi:
Hi guys!

I started to create my own roms about a month ago. First I added only one little program to learn how to cook roms and how everything works. I went on and added some registrytweaks and still everything went fine.

But since yesterday my phone (or my stupidity?) is driving me crazy...

I grabbed a copy of .mUns ROM (thanks for your great work! [I use this rom only for own use]) and dumped its content.

The first thing I did was removing some apps which I never use. For example the Autoupdate. Then I added several applicationfiles into the dump directory, changed some registry values and finally edited the initflashfiles.dat file. I build my rom and flashed it.

Normally the phone shows the welcome screen with the text "Tap the screen to start....." after the first boot. But right now it doesn't show this text to me... I just see the welcome screen without any text... and right here I'm stuck and I don't know why! :(

Is there a problem with my initflashfiles.dat or are there some wrong values in the registry?

Please try to help me. I checked the initflashfiles.dat and registryfiles several times but couldn't find any problems...

Greets, Vi

PS: If there's someone who wants to check the files, just tell me and I'll upload them.
[8125, K-JAM, P4300, MDA Vario ROM Development] mun_rus:
1) did you remove 2 bytes from iniflashfiles.dat?

2) probably you've deleted something usefull

3) did you edit hv files correctly?
[8125, K-JAM, P4300, MDA Vario ROM Development] Mr. Vi:
1) yes, I did it with WinHEX

2) I think I didn't, because I deleted the same files as I did with other Roms

3) Yes... Last line blank and Unicode. DO they need to be read-only?

Any other suggestions?

I'm just about to throw my wizard out of the windows... :-/
[8125, K-JAM, P4300, MDA Vario ROM Development] Mr. Vi:
I got it... :D

I don't know how, but I got it :)

Greets, Vi
[Galaxy Tab S Android Development] Deleted member 4405529:
Different ways of flashing

Very dirty flash:

flash rom

Dirty flash:

wipe system

wipe cache

wipe dalvik-cache

flash rom

flash gapps

Clean flash

factory reset in recovery - (without wiping /data/media) this resets your settings and deletes your installed apps

[optional for paranoids - 'cause it's done from installer-script in the process of flashing] wipe /system

wipe cache

wipe dalvik-cache

wipe data (without wiping /data/media) this resets your settings and deletes your installed apps

flash rom

flash gapps

Very clean flash

factory reset in recovery - (without wiping /data/media) this resets your settings and deletes your installed apps

[optional for paranoids - 'cause it's done from installer-script in the process of flashing] wipe /system

wipe cache

wipe dalvik-cache

wipe data (without wiping /data/media) this resets your settings and deletes your installed apps

wipe internal memory

flash rom

flash gapps

I recommend ALWAYS a "Clean flash", though myself I do many times "Dirty flash"es while testing. Whenever I run in issues, I reflash the "Clean flash" way. On the issues with Camera2 I even did "Very clean flash"es - to ensure no old data is interfering.

On many threads it is MANDATORY to have done a "Clean flash" before reporting issues. Not so here - and I want to leave it this way. But always ask yourself: how many times have I done a dirty flash? Have I tested and edited files? Is it time to "Clean flash"?

I count on users good judgment.
[Galaxy Tab S Android Development] Deleted member 4405529:
Reporting issues

Before you report an issue

Make sure you have installed the most current build.

Do a "clean flash" as described in posting #2 (do NOT flash xposed: it's not supported - see above #1). Dirty flashes are ok most of the time. But you can never know when "not most of the time" a dirty flash produces issues, so before repprting an issue it is mandatory to perform a "clean flash", just in case...

What an issue report should contain (at least)

The more detailed information is provided, the better I can iron it out. It's not possible for me to hunt down any issue that I can't reproduce or understand, the only way to undestand your issue and it's underlaying dynamic is a logcat. I don't know automagically all usecases of all users.

Detailed description of steps to reproduce the issue.

logcat, while reproducing the issue (as text)

I'll ignore all other reports, 'cause that would be just guessing and begging for information.

How to get a logcat

Go to settings->about tablet and tab build number 7 times to enable developer options.

Go to just enabled settings->developer options and enable root access as well as local terminal

open terminal from app-drawer and type:

su -
logcat -d >/sdcard/Download/logcat.txt
zip /sdcard/Download/logcat.txt

Now you have /sdcard/Download/logcat.txt.zip - this file is the oxygen to burn down your issue!

provide this logfile with your report. Alternatly you can skip the zipping step and upload the palin text file to paste.bin or dropbox or something like this.
[Galaxy Tab S Android Development] Bushcrafter:
Looking forward to your up coming updates of cm12.:good:
[Galaxy Tab S Android Development] Deleted member 4405529:
Me too... ;) Would really like to try my build.

It seems my router/3g-stick is broken:

I'm not at home at the moment. I have my development server connected to the internet via a netlink n3000 with a 3g-stick. Sinve yesterday I get connection closings. I tracked that down: I can login to my machine, but as soon as the traffic increases the n3000 reboots... First after 180 to 220 MB of traffik, at the moment after som Kb (if I "tail -n250 /var/log/messages" connection breaks du to reboot...). I'm pissed off.

I'm will be at home at end of the week - hopefully it's the stick (I have a spare one). If the router is broken I need to order a new one...

How ever: sorry for making you expect a cm12 build - but it will be there as soon as I get my developing machine back to an reliable internet connection!
[Galaxy Tab S Android Development] Bushcrafter:
No problem. Hope you get it figured out when you get home!:good: We all need your expertise with cm12 so we can have the best tab s ROM in the WORLD!:laugh: :good:
[Galaxy Tab S Android Development] maxal:
+1 :good::
[Galaxy Tab S Android Development] Ts_sT:
No need to apologize. I doubt the rom development for the tab s would be anywhere close to where it is now without your work. :o

Now after approx 24 hours of hoping for a cm12 rom that will finally boot on my t805, i almost don't dare to ask if there is a slight chance it will happen this time? :confused:
[Galaxy Tab S Android Development] lionheartk:
Uh maybe someone (maybe me? I'm trying!) could compile the rom from your GIT and upload it somewhere?
[Galaxy Tab S Android Development] Moscow Desire:
Thread is closed until OP can provide a download link. At that time the OP can contact moderation team for re-opening.

MD
[Galaxy Tab S Android Development] Deleted member 4405529:
Sorry for the incinvience! Thank you for your help!

Download is up - Known Issues is updated. I will cleanup now and update git repositories.

Remember: IT'S ALPHA - for daily driver use my cm-11.0 build.

Thanx to all for their patience!!!
[Galaxy Tab S Android Development] Bushcrafter:
I will give it a try!:good: Its good to see that you got your router problems figured out!:D

Update: Just got your ROM running on the s and so far so good. How good do you expect battery life to be with this ROM?
[Galaxy Tab S Android Development] Deleted member 4405529:
I don't know. I'm using cm12 perhaps 7h h longer then you. As long as I haven't fixed gps I suppose it not too good - but I'm guessing here.
[Galaxy Tab S Android Development] Bushcrafter:
I will run it for a couple of days and see what my battery life is like. Is there anyway to get synapse to work with your kernel? Just curious.
[Galaxy Tab S Android Development] Offica:
Yay LP thanks :D will flash when it's a bit more stable:D
[Galaxy Tab S Android Development] Deleted member 4405529:
Synapse don't know anything about a kernel - UKM does. UKM does not support our device. Grep the current version of UKM (i belive there is also a git repository for it), take a look at the device files and jason scripts and modify for chagall. You can do it in a way, that settings not availibale in a given kernel are not shown. Everybody would be glad...

My time is limited and I have made the decision to use my time on cm12 for chagall - I have started the above work. I you really want to develop UKM for us all drop me a note and I will push my work to git. But first of all make yourself familar with UKM and git. Propably it would be usefull to read the UKM thread and contact the developer.
[Galaxy Tab S Android Development] maxal:
Hi, Just to say thanks for this rom and to let you know that I flashed it and have it running now on my T800 there is just a couple of minor issues SuperSU won't update and I don't have access to my external SD card.

Thanks again :):good:
[Galaxy Tab S Android Development] benjy4537:
Screenshot, wait time batery life
[Galaxy Tab S Android Development] Deleted member 4405529:
Sdcard: read issues section in OP for workaround. init.d support is broken at the moument.

What do you mean with "SuperSU won't update"? Error message? Logcat?
[Galaxy Tab S Android Development] reubenskelly1992:
Latest build is super smooth and the best yet, but I am having problems streaming BBC I played etc
[Galaxy Tab S Android Development] Bushcrafter:
No problem! Keep up the good work! We get it when we get it!:good:
[Galaxy Tab S Android Development] :
Welcome to my world....

No reason to apologize, mate - it's broken upstream.
[Galaxy Tab S Android Development] :
I have just worked out posting number three. Obviously I made a mistake. I thought on a development thread everybody knows how to get a logcat and had enough knowledge about development to know to provide reproducing steps and details.

I really like you all and I like the atmosphere in this thread. So I'm sure not providing information I need to solve an issue is not due to laziness or lack of kindness, but lack of knowledge how to do properly.

So I decided to explain why I need this imformation and how to gather them. This is the current posting number three.

JFYI: Today and tomorrow I had to work (yeah, there is a life besides providing this rom for you), so don't get impatience if I don't answer immediatly - I will as soon as possible.

Before you report an issue

Make sure you have installed the most cutrent build.

Do a "clean flash" as described in posting #2. Dirty flashes are ok most of the time. But you can never know when "not most of the time" a dirty flash produces issues, so before repprting an issue it is mandatory to perform a "clean flash", just in case...

What an issue report should contain (at least)

The more detailed information is provided, the better I can iron it out. It's not possible for me to hunt down any issue that I can't reproduce or understand, the only way to undestand your issue and it's underlaying dynamic is a logcat. I don't know automagically all usecases of all users.

Detailed description of steps to reproduce the issue.

logcat, while reproducing the issue (as text)

I'll ignore all other reports, 'cause that would be just guessing and begging for information.

How to get a logcat

Go to settings->about tablet and tab build number 7 times to enable developer options.

Go to just enabled settings->developer options and enable root access as well as local terminal

open terminal from app-drawer and type:

su -
logcat -d >/sdcard/Download/logcat.txt
zip /sdcard/Download/logcat.txt

Now you have /sdcard/Download/logcat.txt.zip - this file is the oxygen to burn down your issue!

provide this logfile with your report. Alternatly you can skip the zipping step and upload the palin text file to paste.bin or dropbox or something like this.
[Galaxy Tab S Android Development] zat0x:
Is it just me or is the rom a bit laggy ? Any tips ? Great rom anyway.
[Galaxy Tab S Android Development] lionheartk:
I think It's only you! Super smooth here. Try a clean flash, as explained in the OP. Maybe that helps!
[Galaxy Tab S Android Development] zat0x:
I did that. Well the only thing lagging is the app drawer while opening and closing. Low FPS.
[Galaxy Tab S Android Development] :
That's launcher/trebuchet. Which is heavy wip on cm side - could be one reason. But if you are the only one, I would guess you restored some settings the launcher doesn't play nive with.

BTW: I use nova - because of the backup issues wit trebuchet. And I clean install and backup nova often... You guess why... ;)

BTW2: running 0128 for 2d, 16h uptime, second complete discharge (to 2%) recharge cycle: no issues so far amd battery life gets sloghtly better each cycle (about 9h screen on time in my usecase).

BTW3: Issue: browser->search on page: doesn't show searchstring and arrows for next previous - same on manta, so I think it's cm. Funny: search works - pehaps just white letters on whize background... ;)
[Galaxy Tab S Android Development] lionheartk:
Well now that I've learned a thing or two (like 300 really) from nvertigo, here's the updated build finally! Dirty flashed and working on mine.

Contains all CM commits up to one hour ago (minus one problematic and useless one grrrr, thanks nvertigo!), and every commit nvertigo commented here from my last build up to now:

cm-12-20150131-UNOFFICIAL-lionheartk-chagallwifi.zip 236.3 MB

cm-12-20150131-UNOFFICIAL-lionheartk-chagallwifi.zip.md5sum 144 B

Enjoy!
[Galaxy Tab S Android Development] reubenskelly1992:
Awesome!!
[Galaxy Tab S Android Development] Bushcrafter:
Thanks to Nvertigo67 I now know how to create a logcat!:D I have attached a zip logcat of 0128. Hopefully this will help with the WiFi issue I was having.
[Galaxy Tab S Android Development] :
Great. Thanx. May you please describe your issue a little bit more detailed then "like the other". I will look tomorrow morning (I'm UTC +1).

EDIT: Or was you the one with problems directly after flashing?
[Galaxy Tab S Android Development] Bushcrafter:
I flashed 0128 and used it for a couple of days,then it started giving me a WiFi error every time I clicked on the YouTube app link.

I reflashed my saved ROM of 0125 and the problem went away. I just downloaded 0131, did a clean flash,and all seems to be okay so far.:good:
[Galaxy Tab S Android Development] lionheartk:
If you have problems with wifi and you're not using TWRP, I reccomend a full clean flash using TWRP to see if the issue goes away.
[Galaxy Tab S Android Development] Bushcrafter:
Okay I will give it a try and see what happens.
[Galaxy Tab S Android Development] :
After not finding something special to wifi, but finding some chrome beta errors I read your description again: what do you mean by "clicking on youtube link?" In which app? Whatmhappens then exactly step by step? If - I had to gues here, due to lack of information - you click on that link in chrome beta, do you see the "open with" dialog?

I can use youtube app here (I'm still on 0128, 'cause I want to do a longterm stability test) without any issues.
[Galaxy Tab S Android Development] :
I'm not quite sure, 'cause of lack of information, but I belive it's no flashing issue: then wifi should be immidetly broken...

[MENTION=5339037]Bushcrafter[/MENTION]: what is "wifi error"? Disconnect? What's exact error message and reading in wifi settings? Can you still see the ap? Does reconnecting help? If not, does deleting the ap and reconnecting help? And the questions about the steps to reproduce the problem. Begging for information sucks...