yashsingh1/xdaforums huggingface dataset:
[Shield Tablet Android Development] xanthrax:
ohh... as I've suspected, the charging rate depends on what /which /how many apps are running in the background, draining the battery before having a chance to charge

I've rebooted and cleaned the caches on blisspop and measured the charging rate, looks fine as you can see below, changing kernels parameters doesn't affect it significantly so, it's related to the background processes

also, v042 looks awesome on stock, I haven't played with its settings yet but yes, greater than before

thanks pal!

sent from my Darkside of SHIELD Tablet
[Shield Tablet Android Development] BitOBSessiOn:
KSX-042 Available for CM 12.1

NOT tested by me... feedback welcome. Thnx.
[Shield Tablet Android Development] Pariahnoble:
Quick question for ya bito, did I understand correctly that the new kernels are clocked at 2.499 but still at stock voltage? I can't really notice it draining any faster @2.49 than it did [MENTION=3058039]2.2[/MENTION] (stock) but good lord it's FAST!
[Shield Tablet Android Development] BitOBSessiOn:
Yep, stock voltage, no "overvolting".
[Shield Tablet Android Development] Pariahnoble:
[MENTION=6411851]BitOBSessiOn[/MENTION] Well. Done. My shield is fast enough now, it reminds me of when I built my first pc so fast, that when you clicked to open something, if u blinked, no matter how fast you blink. The window would be open before your eyes were. AND I've been off the charger over 10 hours now, and not being very nice to my battery... Still at 57 percent. Amazing job man
[Shield Tablet Android Development] ytain:
I'm sorry to disappoint again, the KSX-042 kernel still shows discharging even when connected to charger.

Are you testing with the provided charger by Nvidia?
[Shield Tablet Android Development] xanthrax:
Yes pal, I'm testing with the Nvidia charger and cable, same results with oneplus one charger and cable

There's something in your Rom, better do a clean flash

Sent from my Darkside of 1+1
[Shield Tablet Android Development] Pariahnoble:
Nearing 24 hours uptime @2.499ghz! Just hit 25% screens been on more less steady 11 hours of that. Something went right on this build for sure. Except.. Er *cough* hdmi *cough* (just got bug in my bum and tried it again(just re flashed again last night to see if it helped) other than that. Man u should drop a resume to nvidia. It appears they could learn a thing or 3.
[Shield Tablet Android Development] duanim:
Test 042 stock lte model and I got couples RR playing pssp broken destiny 60/60 ,the first one in performance mode max 2.4 min 51 ,intelliplug and 48% battery,the second one in ondemand same configuration and charging by the way,my battery show that is charging confirmed couples times,got the RR playing MK X.

Can somebody tell me a best configuration, I am going to reflash again KSX042 and test again.

Bitob my WiFi still have most of the times problems to connected to my network, I has to do it manually, is like is not scanning and I do have the scanning option in advanced check.

I did test the last two antutu one in performance mode max 2.4 min 51 and intelliplug and I get #59487 and the other in on demand same configuration and I get #60127, Why????.

I will appreciated is you tell me your configuration. Gracias otra vez will be expecting more from you.
[Shield Tablet Android Development] BitOBSessiOn:
Most stable config for me (no RR):

- Shield power manager: Performance/User to max

- CPU governor: Interactive

- IO sched: CFQ

Set Intelliplug off and fsync off if you get RR, but my bet is that a wrong CPU governor (ondemand...) makes system unstable because collision with stock cpu management.

Keep governor to interactive and try changing rest of parameters.
[Shield Tablet Android Development] duanim:
Thanks bitob
[Shield Tablet Android Development] eurominican:
Console mode is supposed to turn off the tablet screen and only display an image through the HDMI. I will test latest build when have a chance.
[Shield Tablet Android Development] eurominican:
Nope, doesnt work. It does mirrors the screen perfectly fine though (always have - ive used 035, 040 and 042 now).

In case it makes a difference i have an US 32GB LTE tab (wx na do) and used*BitO-KSX-042-OTA3.0-wx_na_do.zip
[Shield Tablet Android Development] BitOBSessiOn:
I assume that with nvidia stock kernel it works well, does it?
[Shield Tablet Android Development] Pariahnoble:
Hmm kinda looks like the lte model has working console. I'm on wifi. And when I hook up hdmi, the window pops for console mode, but no matter what I click (mirror or console) nothing happens. Tried a totally fresh wipe too. Xanthrax has hdmi (he posted pics) and eurominican has mirror, both on lte I beleive
[Shield Tablet Android Development] xanthrax:
I have the Wi-Fi version

Sent from my Darkside of 1+1
[Shield Tablet Android Development] eurominican:
Correct, console mode works perfect on stock kernel.
[Shield Tablet Android Development] Lltp:
Hi, my tablet (LTE RoW) is not charging when using your kernels (whatever version of it applied to a clean CM12.1/TK14 build). The complete ROMs that you (BitO) provide also exhibit this problem.

Stock and CM (May 25th only) are the only one currently working. Other ROMs or other kernels just don't acknowledge that I plugged tge tablet.

**This is not just a visual glitch**: the battery charge is decreasing when plugged to the original power plug. With CM 05252015, in the exact same conditions, I can play movies or games with the charge increasing.

I'm using the latest multirom-enabled TWRP to switch between ROMs. Each install I do is perfectly clean (I always create a **new** primary/secondary ROM first and then apply the new kernel, if needed, right away before the first boot). I also tried to perform an extra dara/cache wiping, to no avail.
[Shield Tablet Android Development] BitOBSessiOn:
Does not BitO kernel over Stock OTA 3.0 work for you...?
[Shield Tablet Android Development] Lltp:
Yes, sorry, I wasn't clear enough. I didn't try to flash your kernel over stock. The problem is with CM-based ROMs.

But the thing with stock is that nvidia is not providing anything anymore until the speaker thingy is solved and it doesn't have all the great features CM has.

The kernel of the May 25 CM ROM by Steel01 is working perfectly. Was there any change performed in power management between your kernel (even at that time) and the one in CM?
[Shield Tablet Android Development] BitOBSessiOn:
Kernel is basically the same... Same base code from Nvidia, but extended and revised with some tweaks in BitO-K, for Stock amd CM. I can be wrong, but I think charging issues are more related to something that has changed in CM framework in latest versions... or something in BitO-K production is breaking something... (any bug in 5.1 TCs...?).

One good test could be flashing KSX-042 over latest working CM build tested by you...

If I have time I will try to do some more tests in stock.

Thnx for feedback.
[Shield Tablet Android Development] Lltp:
I've just tried it over Temasek 14 as provided by you (after data, dalvik and cache wiping). No improvement unfortunately.

Is there anything I can do to help solving this?
[Shield Tablet Android Development] AgentAgrimar:
After you tap it restart it...
[Shield Tablet Android Development] BitOBSessiOn:
Can you try KS-035 over Temasek v14...?

[MENTION=3946657]xanthrax[/MENTION] made some interesting tests about charging a few posts ago.
[Shield Tablet Android Development] Pariahnoble:
You mean after I select a hdmi mode (mirror or console) reboot while still connected? I'll have to try that when I get a chance, hadn't thought of that... Thanks muchly!
[Shield Tablet Android Development] AgentAgrimar:
After you tap Console Mode, it sets a boot flag so whether HDMI is still hooked or not, it will boot appearing on TV until you hit either hit MIRROR MODE, or Exit Console Mode, unchecking that boot flag.

Also don't worry about having HDMI disconnected, it will still appear on your screen, just with a cinematic view... :laugh:
[Shield Tablet Android Development] Lltp:
No, it's not working either.

I've also tried KS-034 last month making my working CM ROM unable to charge but I did not bother then.

I'm surprised that there seems to be no problem with the WiFi version. There shouldn't be that much a difference between the powering parts of each of them.
[Shield Tablet Android Development] BitOBSessiOn:
I will revise some USB kernel config params...
[Shield Tablet Android Development] BakaPhoenix:
For stock ota 3.0 row i need to dl this one?

BitO-KSX-042-OTA3.0-wx_un_do.zip

I have the lte+wifi version.

P.s. What app you suggest to control the kernel settings?

Any suggested setting for good performance but good battery life?
[Shield Tablet Android Development] BitOBSessiOn:
Yes, it's correct, wx_un_do.

Kernel Adiutor for settings.

I recommend:

CPU Governor: Interactive

Hotplug: Intelliplug, Balanced

IO Scheduler: BFQ, for instance... ROW...

Dynamic FSync: On
[Shield Tablet Android Development] BakaPhoenix:
This kernel support usb otg?

After i flashed it won't mount my usb anymore.
[Shield Tablet Android Development] BitOBSessiOn:
AFAIK USB OTG issue appeared in latest stock OTA 3.0. Has anybody a working scenario with stock or latest CM?
[Shield Tablet Android Development] xanthrax:
USB otg works by using stick mount app from market

Sent from my Darkside of 1+1
[Shield Tablet Android Development] ytain:
I still have the same problem with charging, on KSX-42 on top of Temaseki 14.1 or other CM12.1 roms.

More observations: If I leave the screen off, after a while the led light changes to green while charging, however when I turn on the screen, the battery level reading doesn't indicate at all 100%. This most often happens after 1% or 2% battery level increase.

I'll try to download and compile the kernel to debug the charging issue.
[Shield Tablet Android Development] vile80r:
Does anyrom support wireless controllers?

Is there a custom ROM with wireless controller support? I've tried all I could find and there are some great ones, they all have no support for wireless controller. As nobody created a stock based ROM? It seems the only way. Meanwhile, what about a debloat list or script to trim the fat?
[Shield Tablet Android Development] kimber45:
Check out this thread, http://xdaforums.com/showthread.php?p=60961960, as Pariahnoble has made an awesome tutorial including a debloat list. As far as wireless controller, I cannot comment as I do not own 1.
[Shield Tablet Android Development] Lltp:
I may have found something. I've been to the setting app. I selected Storage and I tried setting the USB connection type to "Charge only". The Settings app kept crashing each time I tried.

---------- Post added at 09:55 AM ---------- Previous post was at 09:32 AM ----------

Would it also be possible, just once again, to try to release a wx_un_do image? Because the problem seems to arise precisely on LTE RoW tablets. A friend has the WiFi version and your kernels are working just right and nobody from NA seems to complain.

As I understand it, nVidia differentiate these because of the frequencies used but there might be other subtile differencies between them either in the kernel configuration or in the kernel code.
[Shield Tablet Android Development] BitOBSessiOn:
Sorry, but... which system version are you talking about.. ? Temasek... ? version..? I suspect you're talking about Temasek 14.1 although we're in Kernel thread...

I provide three different kernel versions for stock (included un_do) and two ones for cm. We are pretty sure than na_do and un_do and perfectly compatible between them...

The bug you comment is probably related with ROM framework... Have you tested any other ROM...? Can you provide a log about the crash...?

I'm working in different device trees for each model (in the future, probably also un_do), but, under my criteria, there are a lot of things pending before this.

Please, as a global excercise for everyone, let's try to use correct thread for kernel and ROM, and be more precise with the system where we are testing: ROM, versions (kernel and ROM), mods, ST model, etc... Thnx !
[Shield Tablet Android Development] Lltp:
Yes, indeed. Temasek 14.1. I really don't care about the Settings app crashing. I was wondering whether this could give a good insight on what's happening at the kernel level.

That's not difficult at all to know without a doubt. I'll check that tomorrow.

No, i did not test any other ROMs. Since I have a working CM (well with some [wifi/ui] bugs, hence my wanting to update) build which exhibits the problem with your kernel releases AND since you will most certainly not update CM framework to fit your releases, I guess the fix will have to be performed in-kernel. That's why I consider that this is a kernel problem and not a ROM problem (even though the incompatibility was most certainly triggered in the ROM). I'm not saying that you are responsible, not at all. And even if you were, I would not blame you: you are doing a great job and I really appreciate that.

I'll generate and look at the log tomorrow also.

I totally understand that. I did not want to give the impression that I am pressing you or anything. I was merely evoking the fact that there have been two different versions of the *_do ROMs and that there might be other differences than just the frequency bands. If there was any reference on XDA that you've already checked that thoroughly, I would not have talked about that. But what I see is that there seems that there are no differences.

Sorry for that. As far as I'm concerned for my last message, I've been using Temasek 14.1 as provided in your repo, without any change and I'll try to stick to that (ROMs+kernel provided by yourself) to limit the possible interactions with 3rd-party modules.

Cheers

---------- Post added at 10:35 PM ---------- Previous post was at 10:34 PM ----------

PS: BTW, I don't have 10 posts yet, so I cannot write anything in the ROM threads.

---------- Post added at 10:43 PM ---------- Previous post was at 10:35 PM ----------

PPS: an incompatibility between ROM/kernel can be fixed in either/both of them. I consider that this is a kernel problem (you probably won't revert CM changes AND why is it working for wx_na_wf then if that was CM-specific? AND hardware thing are handled at the kernel level) so that's why I posted here.

I'll come back with logs.
[Shield Tablet Android Development] berryman13:
I tried UKM+Synapse, don't even think about it guys! Stick to kernel adiuter
[Shield Tablet Android Development] BitOBSessiOn:
[MENTION=6759066]Lltp[/MENTION], first of all, thnx for testing (you and everyone here)

In my case, custom ROMs are compiled depending on specific device code trees, different for each model. My latest device trees are unstable (GPS problems, for instance in 14.1) because I'm trying to update latest nvidia code and blobs at same time I integrate other devs code. That's because we can expect different behaviour in same rom for different models (two different packages).

There are less differences in kernel config that in ROM to manage these little hw particularities between wifi and lte models...

I'm working on it, and in some revisions for next KSX, but I have not as much time as I would like... :(
[Shield Tablet Android Development] duanim:
I am back second RMA using your configuration I got today stable and running smoothly in antutu

60988
[Shield Tablet Android Development] duanim:
Excellent

Thanks again bitob
[Shield Tablet Android Development] Lltp:
Here we are. Android log are quite scarce, which is really a shame (nothing appears in logcat and I'm not sure how to increase its verbosity).

However, dmesg is far more useful! Here what I got when pluging:

palmas-usb extcon.9: vbus-irq() INT3_LINE_STATE 0x80
palmas-usb extcon.9: USB cable is attached
bq2419x 1-006b: bq2419x_irq() Irq 249 status 0x10
bq2419x 1-006b: Charging Fault: Input Fault (VBUS OVP or VBAT<VBUS<3.8V)
bq2419x 1-006b: bq2419x_irq() Irq 249 status 0x00

And upon unpluging:

palmas-usb extcon.9: vbus-irq() INT3_LINE_STATE 0x00
palmas-usb extcon.9: USB cable is detached

I hope this will help. I'll try to look into this a bit further once I retrieve the kernel sources but I can't promise anything.

PS: the code triggering this, per se, can be found there.

PPS: If I am not mistaken,

val = 0x10
BQ2419x_FAULT_CHRG_FAULT_MASK = 0x30
BQ2419x_FAULT_CHRG_INPUT = 0x10

as declared there.
[Shield Tablet Android Development] BitOBSessiOn:
I will check some USB kernel config params... I was playing with them trying to solve OTG issue and maybe it affected to charging... I will test an original config kernel...

Thnx.
[Shield Tablet Android Development] BitOBSessiOn:
As I suspected... In lastest Nvidia kernel source I can read:

Disabling QC 2.0 charging to avoid battery swelling issues.

QC = Quick Charge... Who wants a "extra-fat" battery... ???

I will check code, but I think it's safer slower charging... Question is... how much slow... ?
[Shield Tablet Android Development] Lltp:
All of it makes sense now: the "slow" charging (compared to a phone anyway) and cracks appearing on corners on some devices. They really made bad engineering choices all around. But anyway.

QC is actually an algorithm (which should be dependent on the materials used in the battery) which allow to increase the current intensity in the first minutes of charge, thus reducing charging time and allowing to reach 70-80% of the capacity in, typically, less than half an hour.

Because most of the material has not reacted yet (to store electrons), there is almost no mechanical nor electrical resistance at the beginning, so you can pour electrons in at quite a high rate. The problem is that if you try to apply such an algorithm to the wrong material or to a battery with poor design choices, you end up overcharging locally. This overcharge increases the resistances create stress and distort the material hence achieving battery swelling.

I guess, you will have to check the nVidia code for the optimal charging rate.

I'm really happy that you could identify the problem that quickly! :)
[Shield Tablet Android Development] BitOBSessiOn:
KSX-043 Available

Little changes in thermal/voltage kernel params

Ondemand and Interactive governors disabled to avoid random reboots (Interactive recommended)

Compiled with stable TC Sabermod 4.9
[Shield Tablet Android Development] BakaPhoenix:
What is the hdmi issues reported in the opening post?
[Shield Tablet Android Development] BitOBSessiOn:
It seems that in console mode screen is mirrored... Not tested by me, probably someone can give more feedback about and confirm issue in latest version.
[Shield Tablet Android Development] BakaPhoenix:
QC 2.0 stand for qualcomm quick charge 2.0 tecnology

https://www.qualcomm.com/products/snapdragon/quick-charge
[Shield Tablet Android Development] Rolodo334:
Battery not charging at all

I tried all version of the kernel for the wifi shield tablet.

The tablet don't charge at all :\

I restaured to the CM kernel

thx for the good work :)

Rolodo334
[Shield Tablet Android Development] BitOBSessiOn:
Which kernel version (and system) are you using...? No charging probs ? Thnx
[Shield Tablet Android Development] duanim:
Bitob 043 run nice and smoothy, changing to interactive and performance with same configuration same result in antutu.cfq,core performance, balance etetc.

Between 042 and 043 I got bigger score in antutu in 042 like 1000 difference, everything else are the same.

About charging is better to put on charge or connect the USB charger when you using the tab you see that is charging, no charging when I left the tab off overnite and charging and turning on to use,you see the charging symbol but is decreasing the battery.

Thanks again chevere
[Shield Tablet Android Development] BitOBSessiOn:
OTA 3.0 045 builds in Testing folder.

Little tweak to test if we can play and charge battery at same time....
[Shield Tablet Android Development] duanim:
Bitob so far so good playing for couples hours no problems ,the screen look great maybe is me.

No using intelliplug,running at 2.4 GHz max /min in performance mode,I/O bfq.

It charge to a 100% in almost 5 hours, playing intense games the battery hold almost 3.5 hours

Antutu 58890.

Thanks again
[Shield Tablet Android Development] xanthrax:
I suspect the inteliplug , I've disabled it when I've noticed that it doesn't enter deep sleep

sent from my Darkside of SHIELD Tablet
[Shield Tablet Android Development] BitOBSessiOn:
KSX-045 available

- Battery charging tuning to enable charging in high CPU use (while playing, etc...)

- NFC code enabled again

- Problematic governors disabled (ondemand, conservative).

I've tested charging while playing for about two hours... Charging seems to work fine (OTA 3.0). More feedback welcome.

NOTES:

*CM version built under BlissPop branch. It should work on CM like ROMs (CM 12.1). Testing needed to confirm.
[Shield Tablet Android Development] DizzyWeb:
On Blisspop it barely charges. No charging indicator either.
[Shield Tablet Android Development] duanim:
Got lte model and it charge perfectly while am playing games.

No RR, nothing so for the last 3 days,like I mentioned running 2.49 GHz max/min,no intelliplug.

Antutu 59897 today, after install exposed and some modules, like gravity box.

Apk that I have in my ST: kernel 045,auto killer memory optimizer , booster plus ( ram,WiFi,digitaligizer,battery plus and performance), SD maid,kernel auditor,set CPU max,secure settings,GPU OC to high,and busybox

Question: there something can be done to set YouTube to high quality video or 1080p.

Bitob I am using 045 the testing one, do I have to flash the final one.

Cheers to all
[Shield Tablet Android Development] BitOBSessiOn:
045 in Testing folder is older compilation... It should be the same, functionally talking... I've had to reconstruct all my development environment... If you can try the new one... and validate that all works fine, better... but anyway... I'm workin on 046, with other adjustments about battery charging... Duanim, you're talking about Stock OTA 3.0 rom... correct? Thnx
[Shield Tablet Android Development] duanim:
Yes Stock OTA.

I will do some test,but I don't see nothing wrong with this one,I can say 045 is so far the best for the old kernels about charging, for all my test,but we certainly don't for others models
[Shield Tablet Android Development] BitOBSessiOn:
KSX-046 available to download.

I've tested it on Stock OTA 3.0 and Bliss 3.6 in my LTE model and it seems to charge fine. I have charging indicator working in Bliss and I get 100% battery charged and green led... I've passed Antutu full while charging and battery remained 100%... Not tested playing...

Feedback from hard gamers and WiFi model owners welcome... Thnx.
[Shield Tablet Android Development] Nvjoel:
I have WIFI. Charging doesn't work, no indicator no charging like on previous versions. Also OTG not working tested with Razer Kraken USB and WD my passport. It worked on kernel used in bliss 3.4. I think no charging and OTG is caused by wrong USB connection detecting, on bliss 3.4 kernel while charging if I try to open Storage -> USB computer connection I see "USB is now disconnected" but on Bito-K it is always set to MTP and cannot change to anything other.

Sorry for my bad english.
[Shield Tablet Android Development] BitOBSessiOn:
Anyone with LTE can confirm if it works or not, please...? Thnx
[Shield Tablet Android Development] DizzyWeb:
Guess I'll be trying multirom with the stock rom... going on vacation later this week, can't have a barely charging tablet when camping...

But do hope it'll be fixed somewhere the next 3 days :P
[Shield Tablet Android Development] duanim:
Works in lte model fine
[Shield Tablet Android Development] Lltp:
It doesn't work with CM12.1 on my LTE tablet unfortunately.

I can reproduce everything Nvjoel said.
[Shield Tablet Android Development] xanthrax:
Ok, these are my results with 046 when playing Prime Defender on blissPop Wi-Fi version, original charger and cable

sent from my Darkside of SHIELD Tablet
[Shield Tablet Android Development] xanthrax:
And this is on stock rom, v046 while playing the same game

sent from my Darkside of SHIELD Tablet