yashsingh1/xdaforums huggingface dataset:
[HTC Startrek] icecube57:
Im using my startrek with WM6.1 Pro with the battery status plugin now Homescreen ++. I have it underclocking to 143mhz 180mhz is nominal 260 is my high setpoint and 273 is my temporary boost. Its dynamic based on cpu load. Works like a champ get about 3 days charge with my extended battery. Dont know about stock battery time. Besides the phone getting a little warm its fine to overclock. Just make sure its stable at whatever speed you set it at. It will lock up immediately if its not stable 240-252 is safe and stable for most on this phone for continuous use. When underclocking you may notice scale lines appearing on the screen like it has a reduced refresh rate.
[HTC Startrek] MrSnoop:
My3125 also can keep @252mhz...

haha
[Moto G Q&A, Help & Troubleshooting] Asaad123:
I have been having this problem since I got the Moto G. All the photos in my camera roll dissapear suddenly and I am left with no images. The pictures are also not found in the internal memory of the phone. Its running stock 4.4.2 and it is the GSM variant. Is there any reason to this and is there a way to prevent it?
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] varxtis:
My dads Note 10.1 2014 edition was recently update to KitKat (4.4.2). For a long time I was excited about the upgrade as there was supposedly a feature to print to any printer on a network even if the printer itself isn't ePirnt capable. Two apps we spefically use that we'd be interested in printing from is Quickoffice and EZpdf Reader.

There is an HP printer on my dads network. It is not "ePrint" capable.

What are our options to print to this printer from the tablet, now updated to KitKat?

Please note, rooting is out of the question.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] BarryH_GEG:
It should just work. Select print from the app and this should pop-up.

Select Samsung Print and the Wi-Fi printer should be found.

The above are from N3 but my N10.1-14 works the same way.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] varxtis:
I thought that should be the case. When I originally read about it a few months ago it seemed like a matter of Update to Kitkat> download/install service plugin for hp printers> go to desired office app (in our case QuickOffice)> open document > Print.

But alas... not print option :\
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] BarryH_GEG:
Search Play. There was a HP Printer plug in yesterday. But mine worked before the update too.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] kkretch:
PrinterShare™ Mobile Print works like a charm.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] Paul1201:
Have you checked in settings to make sure the print service is enabled?

Settings>Connections>More networks>Printing
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] MikeZ:
I had the same problem at first for my canon printer on my note pro 12.2.

However you need to install the Canon Print Service. It is an app in the playstore, that once installed does not display an interface or something similar.

You'll need to go to Settings>Connections>More networks>Printing and the Enable the Canon Print service.

After that my printer works.

See also:

http://play.google.com/store/search?q=printer service&c=apps&hl=nl

Google has a cloudprinter servcie that installs the same, and indeed you'll need to enable it at the same location.

If your printer is also cloud enabled it will then popup twice in the printers list when you want to print something in an app that supports the new printing framework.

Now i have a question for you:

Can you test to see if you can reproduce my problem:

i have an another user added to my note pro.

That user does not have the option in the Connections screen to choose More Networks.

And as such can not enable the Canon printer service.

And as a result can not print to the canon printer.

For the record, the main user can print to it, so everything is installed properly.

The second user can also install the printer service, he just can not enable it....

Samsung was clueless about this, i think it is an omission in 4.4.2 ...

I hope this is/will be fixed in later versions.

Anybody any info here ?

UPDATE:

I just checked with a Nexus 7 2012 (4.4.3) and this does not have the problem since the settings menu is layed out differently.

Any other user is able to access the printer screen and thus able to switch the printer service on.

Is this Samsung specific then ?
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] varxtis:
[MENTION=5040390]kkretch[/MENTION] and [MENTION=4535612]Paul1201[/MENTION]: Thank you so much!! Both of those points fixed everything and got it to do exactly what he was hoping to do.
[Galaxy Note II Q&A, Help & Troubleshooting] number_thirty_two:
I took a Nandroid backup of my stock phone (all partitions) before I flashed a new ROM (DN3). Then I decided to return to stock ROM, so I wiped phone and restored Nandroid backup (all partitions except bootloader and recovery).

Now the phone will not boot, it just shows a logo and then a black screen. I can connect to it via ADB however.

I thought Nandroid backup was a safe way of preserving phone, but it seems it cannot actually be trusted?
[Galaxy Note II Q&A, Help & Troubleshooting] bunglebp:
depends on bootloader i guess, but maybe try wipe data and preload / cache and dalvik and reflash, make sure ROM to flash is on external sdcard as may lose all data on phone
[Galaxy Note II Q&A, Help & Troubleshooting] Irwenzhao:
Having the same issue after re-partitioning my phone. My nandroid backup is about 2.3gb and it took about 200 seconds to restore. Nothing was actually restored when I booted up. (This nandroid was made to my SD-Card, wonder if that makes any difference.

N7105 rocking AOSB with AGNi kernel,

Sent from a small country named Singapore.

Click "Thanks" if I was of any help!
[Android Q&A, Help & Troubleshooting] shafaga:
Hey guys .. today i increased my RAM using some methods on the internet but RAM Expander Didn't work it says : swapon sdcard/swapfile.swp invalid argument ... so my problem is i have used . Sawpit Ram Expander and succeed but when i check my ram .. it still the same no changes & nothing happened please help me ASAP​
[Android Q&A, Help & Troubleshooting] demkantor:
Well you can add physical ram to a phone, you can flash a kernel or bootloader that reallocates some ram, but this is device specific and often takes some very intelligent programmers to make this happen.

The other way is to use virtual ram in the form of a swap partition, this will use sdcard or internal data or whatever partition you make work, function as ram, but it is slower than real ram and depending on how you use your device may make it slower altogether. I believe this is the method of increasing ram that you did, the easiest way to see if it worked is to open a terminal emulator and type

free

The final way is with compcache or zram, both squash ram and has a similar caveat to using swap as it may make things worse.

A few Google or xda searches should explain this a bit more than I have
[Android Q&A, Help & Troubleshooting] shafaga:
Thanks for your help

demkantor gonna try zram soon​
[Android Q&A, Help & Troubleshooting] shafaga:
Rooted ! :D
[Paranoid Android Features Development] JedTech:
I'd like to see Whisperpush integrated into Paranoid Android. Whisperpush allows you to send encrypted texts to other Whishperpush and TextSecure users while using any SMS application of your choice.

--pasted from a Blog entry at cyanogenmod.org
[Paranoid Android Features Development] jacc1234:
I second this. Im about to switch to CM just for the full integration of textsecure.
[Paranoid Android Features Development] RobotJune:
You can install the apk from the CM distribution and use it wherever you like. Keep in mind that it requires GApps to work. If you already use GApps then it's no problem, but if you don't... the idea of increasing your privacy and security by giving Google root access to your phone may strike you as a little odd.
[Verizon LG G2] xdabbeb:
!!! PLEASE READ THIS ENTIRE POST BEFORE PROCEEDING !!!

!!! I AM NOT RESPONSIBLE FOR ANY PROBLEMS THAT OCCUR WHILE INSTALLING/USING THIS !!!

This is kernel for the LG VS980 running stock-based firmware. My preference is a more basic/lean kernel with an emphasis on battery life, reliability and speed. As such, I'm not interested in adding addtional drivers or features. There are plenty of other devs who do a good job with that already.

Basic Features:

Based on VS98024A source

CAF interactive gov that has been tuned for this device

CAF cpu-boost with input boost enabled (currently @ ~1GHz, but can be changed via sysfs)

Tuned ondemand gov (default) that stays true to stock LG

Choice of stock QCom (default) or Showp/Bricked mpdecision

NOTE: If you want to use interactive governor, it should be paired with alternate (showp's) mpdecision or there will be a delay turning the screen on using knock-on. This can be accomplished via sysfs or in an app like trickster by turning off qualcomm's mpdec, hitting the MP-Decision Control button and turning on "enabled" and "scroff_single_core"

Removed unnecessary governors (only interactive, ondemand, performance remain)

Westwood+ (default) TCP congestion control

Row is still default I/O sched

v1.0.0-1.1.1 compiled with linaro tc v4.7.4

Full list of commits available at github

Changelog:

Version 1.1.1:

Showp's mpdec screen off single core default to off

Correct qcom thermal freq for G2

Version 1.1.0:

OIS+ updates from G Pro 2 (including updated fw)

Other commits I found while chasing down the random HDR crash.

Version 1.0.0:

Initial release

How to Install:

Back up your existing kernel using recovery or make sure you have a way to reinstall it on your device already.

Download the appropriate zip below and flash via recovery (TWRP recommended)

Downloads:

LGD Panel (99% of you want this):

xdabbeb's vs980 kk kernel v1.0.0 - MD5: 267531b33cf8668d81d6f5dbf54468a6

xdabbeb's vs980 kk kernel v1.1.0 - MD5: e9ec66ef0d420fd6b798bde6a6b6bb69

xdabbeb's vs980 kk kernel v1.1.1 - MD5: 3a33d10cb6b70ef3ef8ee755192272dc

JDI Panel:

xdabbeb's vs980 kk kernel v1.0.0 - MD5: c375cbd890ace0ee22a6b83f2912ce49

xdabbeb's vs980 kk kernel v1.1.0 - MD5: f85ed58acf0131b8f6470bb2565dae86

xdabbeb's vs980 kk kernel v1.1.1 - MD5: 169b18b5587602c41a64870eb1f994cf

Stock/Unmodified:

stock vs98024a kernel - MD5: c7bb6eff41546a40dfaa7dae0407e5fe

Devs: Feel free to include this in your roms. No need to ask, just give credit in your OP.

XDA:DevDB Information

XDABBEB's VS980 KK Kernel, Kernel for the Verizon LG G2

Contributors

xdabbeb

Kernel Special Features:

Version Information

Status: Stable

Current Stable Version: 1.1.1

Created 2014-06-04

Last Updated 2014-06-22
[Verizon LG G2] xdabbeb:
reserved
[Verizon LG G2] xdabbeb:
reserved #2
[Verizon LG G2] barrackOBAMA:
xdabbeb's vs980 kk kernel v1.1.0 - MD5: 6556b6cf3a1592df3ce3b4076012aaec

Hate to ask. But just trying to make sure.

Will this work with your Rom? I saw your comment and was just making sure this kernel went with the 24a as well.
[Verizon LG G2] jesssiii:
Is the kernel called xdabbeb_vs98024a_kernel_google_gcc.zip the same as this one here called stock?

VZW G2 (VS980)
[Verizon LG G2] Lawlrus:
Yes

Sent from my Vs980 running Mahdi Rom

---------- Post added at 05:00 PM ---------- Previous post was at 04:59 PM ----------

Yes. His ROM is 24a base, so these are 24a base kernels.

Sent from my Vs980 running Mahdi Rom
[Verizon LG G2] jasondowning85:
OFF TOPIC -- I love trailer park boys...

...Continue
[Verizon LG G2] ffejy462:
First boot and interactive is default gov... Op lists ondemand.. And no, I did not have kernel settings to set on boot.
[Verizon LG G2] xdabbeb:
If you're using my v1.1.1 rom then I had an init script doing that...which is something that can happen with any rom, really. If you want ondemand you can either switch it via an app (i.e. trickster) or just change the init script.
[Verizon LG G2] ffejy462:
I planned on giving both a whirl. Just thought I'd share.

Sent from my Nexus 7
[Verizon LG G2] LTunez:
Same kernel(s) as ROM(s)?

[MENTION=2941286]xdabbeb[/MENTION]

Maybe this is a dumb question, but if we are already running your ROM, are these newer kernels, or do they coincide with the releases of the ROM?
[Verizon LG G2] Lawlrus:
V1.1.0 is newer then the kernel baked into his 1.1.1 rom

Sent from my Vs980 running Xdabbeb's 24a v1.1.1
[Verizon LG G2] xdabbeb:
Both 1.0.0 and 1.1.0 are newer. The only difference between them (per OP) are a number of camera-related commits and I wanted to give people who weren't interested in them an option.
[Verizon LG G2] popcenator:
Very much appreciated XDABBEB. You've been an awesome developer and your work is top notch.

on the move..
[Verizon LG G2] Rodeojones:
Flashed the 1.1.0 kernel last night over the latest [MENTION=2941286]xdabbeb[/MENTION] ROM. Anyone else notice incredible lag with knock on? Really incredible. I'd tap the screen twice, I'd see the LED light up acknowledging it worked, then there'd be a two second delay before the screen would come on. Knock off worked fine. I restored my backup and the lag was gone. I did nothing to alter any kernel settings - just ran it however it came.
[Verizon LG G2] fordmanck:
I had that and then my phone completely locked up while navigating. I'm going to wait until the new ROM release comes out and fresh flash.
[Verizon LG G2] LTunez:
Flashed the 1.1.0 kernel last night, wiped Dalvik and cache, and rebooted...everything seemed fine. Rebooted this morning, and the screen was a garbled mess. It looked almost like white noise (only colored). Managed to reboot again, and the garbled mess was gone, but then I saw some vertical white lines in various places of the screen. Rebooted into recovery, wiped Dalvik and cache, and it seems ok for now, but I wonder what might be going on. Could this having anything to do with what the following thread addresses?

http://xdaforums.com/showpost.php?p=52414185&postcount=122

P.S. Not having the "knock on" lag here...
[Verizon LG G2] Lawlrus:
I can't say I've seen white lines, but I did flash a font last night and when it went to boot it looked like the lg splash was smeared, it then bootlooped until I went back into recovery and flashed a different font

The white line issue is normally not on our device because most screens are lgd not jdi.

There is a thread in the g2 android development section for a tool that checks your screen type made by bender_007.

You can try that to double check screen type.

Sent from my Vs980 running Xdabbeb's 24a v1.1.1
[Verizon LG G2] popcenator:
I unfortunately had that happen this morning. Initially it flashed and booted perfectly last night. This morning I rebooted and got the white lines, my first incident of this. According to the Panel app I do have the lgd panel.

on the move..
[Verizon LG G2] LTunez:
Thanks for the info...the tool shows mine is ldg/lgit.

Don't know if this could affect anything, but the only thing I changed this morning (since flashing the new kernel last night), was to "defrost" (in TiBU), the full version of Swiftkey (because the latest beta expired). So, that's causing the known Gapps crash on boot, but in the past, that crash hasn't seemed to affect performance or anything...hmm...
[Verizon LG G2] Lawlrus:
Not sure if it is just better battery in general, or better battery or signal in low signal area, but my battery isn't draining half as fast as it usually does.

Sent from my Vs980 running Xdabbeb's 24a v1.1.1
[Verizon LG G2] xdabbeb:
Were you running interactive gov along with the stock qcom mpdecision at the time? If so (and you want to run interactive), try turning QCom's mpdec off and turn showp's mpdec on. I'll be including updated init scripts with the next version of the rom that will handle this automatically, but if you want I can upload them as a separate flashable zip as well.

Yeah, that sounds like the lgd/jdi panel issue. Unfortunately, that app (or cat /proc/cmdline and dmesg) are just going to report what has already been passed...which will obviously just be lgd. If you really want to know which panel your device has, you would have to revert to 100% stock 24a (including bootloader, etc), root it, and then check dmesg or cat /proc/cmdline. I'll put together jdi versions of the kernels as well so you can try them out.

EDIT: Actually, I just realized that you guys hadn't mentioned which version of the kernel you were using. If it was 1.1.0, would you mind installing v1.0.0 first and tell me if the weird screen issue persists? Thanks.

Some of the changes made in these versions should help with battery life.
[Verizon LG G2] popcenator:
And I'll put together monetary versions of my thanks for your fantastic support.

on the move..
[Verizon LG G2] Lawlrus:
[MENTION=2941286]xdabbeb[/MENTION] mine happened after I got everything set up.

I rebooted into recovery to flash a font and that happened, so I'm assuming it was because of the font, because when I reflashed a different one, no lg splash issue nor bootloop.

I am on v1.1.0, so if I come across it again I'll flash 1.0.0 and try that.

Kernel is running great so far, as stated above the batteylife seems to be much better for me then on any other stock kernel I've tried. Running ondemand

Sent from my Vs980 running Xdabbeb's 24a v1.1.1
[Verizon LG G2] LTunez:
[MENTION=2941286]xdabbeb[/MENTION]

Was using v1.1.0 when the issue occurred. Just flashed v1.0.0, and will let you know if I have any issues.

FYI: Running the kernel(s) at default, as I don't have kernel tweaking apps/mods on my phone.
[Verizon LG G2] xdabbeb:
Yeah, the bootloop was certainly caused by the system font flash, but I don't think that would've caused any weird screen issue (unless that flash does something it shouldn't). If you're running it without issue, that doesn't sound like the jdi/lgd panel difference either.

For those that have had that screen issue, in addition to letting me know the version of the kernel you were using, could you also let me know whether it only happened after rebooting from recovery? It almost sounds like a clock/sync issue, and it could be triggered by that.

Thanks! Was it only when you rebooted from recovery that you noticed it the first time?
[Verizon LG G2] popcenator:
My screen issue happened on 1.1.0, I just rebooted normally, no TWRP.

on the move..
[Verizon LG G2] LTunez:
No, just a system reboot.

Ok, I may be able to help you track this down. Failed to mention this earlier (didn't think it was related), but I have now reproduced the problem (on v1.0.0 of the kernel). Thinking it's camera (specifically HDR) related. This morning (on v1.1.0) I took a picture using the HDR mode just prior to rebooting, after which the screen went haywire. Now that I'm on v1.0.0, I again tried to take a picture using HDR mode, and it wouldn't even take a picture, just kind of hung there. Rebooted, tried HDR mode again, and this time it did take the picture...rebooted, and the screen went haywire again (pixelated noise, lines, etc). Another reboot and it corrected itself.

Hope this helps! :)
[Verizon LG G2] Jimi Mack:
I also see lag from the Knock On about 1 second after the LED triggers, where the Knock Off is immediate. But I have also seen an improvement today in battery life, prior I was using the Simple kernal and enjoyed that as well.
[Verizon LG G2] ffejy462:
Issues as well. 1.1.0 version. Interactive Gov (no other changes) Xdabbeb 1.1.1 rom. Hdr freezes. Closed camera and reopened. Took a few hdr pictures. Changed mode to normal. Took a few pictures. Back to hdr. Camera frozen. You can see all options at top are grey and unresponsive. Cannot go to gallery or change to video camera.
[Verizon LG G2] Lawlrus:
In his camera thread, he said he's been having problems with the random HDR freezing. He can't pinpoint what's causing it.

These updated kernels were him trying to fix it. If I'm not mistaken

Sent from my Vs980 running Xdabbeb's 24a v1.1.1
[Verizon LG G2] xdabbeb:
Well that's just weird...not sure why that would even have an effect on it. Can you ever reboot after a HDR cam crash without seeing the screen corruption? I'm wondering if it's coincidence, or if something does get borked temporarily when that HDR problem occurs and the second reboot is what clears it. Very odd. Please do let me know if it exhibits that behavior every time.

As mentioned in my earlier reply, that is likely b/c you are using interactive with the stock QCom mpdecision. Can you confirm this? I'll put a note in the OP, but the interactive gov doesn't respond as quickly with display off and cores offline while you're using the user-space QCom hotplug solution...if you use interactive, switch over to using the alternate mpdec. It actually does an excellent job of mimicking the qcom solution, but is kernel-based, configurable, and doesn't exhibit that behavior. If you're on my rom, I'll post a zip later today that will update the init scripts to do the following:

1) no longer override the kernel and leave ondemand as default gov after boot

2) if you create a file (content of file doesn't matter) named /sdcard/interactive it will make your default gov interactive, disable qcom's mpdec, and enable showp's mpdec.
[Verizon LG G2] ffejy462:
That's why I'm reporting it in this thread. :) Some others are having white lines and reboots. I didn't have those issues with the kernel in his 1.1.1 rom, but I don't take many pictures either.
[Verizon LG G2] F1fan07:
is this what others are seeing on the 1.1.0 kernel?

is this what others are seeing on the 1.1.0 kernel?

http://xdaforums.com/showthread.php?t=2773875
[Verizon LG G2] xdabbeb:
The random HDR crash is due to a sigsegv from the G Pro 2 port. The camera thread really is the appropriate place for this, but it has already been talked to death and nothing new is to be said, really. Only the changes in v1.1.0 of the kernel here were a result of tracking down that issue...and they didn't resolve it or I certainly would've said so. The random nature of that issue along with lack of access to the symbols or source for those files has tracking it down a crapshoot. I don't believe the white lines are related to the camera as it doens't make sense, but I could be wrong.
[Verizon LG G2] ffejy462:
Ok. That's the first time I've run into it (I don't take many pictures) and in op it was stated that specific kernel changes were made to help with issue. That and I felt the camera thread was generally for people not running your rom; only the mod. Anyway, other than that, the kernel looks good (it's nearly impossible to get a good feeling about battery life with wifi-ap on). Thanks
[Verizon LG G2] LTunez:
Well, I launched the camera again, took another picture with HDR, rebooted, and it went wonky again. Cleared up after a subsequent reboot, and I haven't been able to reproduce it again...at least not yet. Maybe something else is going on to trigger this phenomenon...
[Verizon LG G2] HueyT:
I hope not as that's more likely a permanent screen damage and irreversible. The white lines are more from JDI panel mismatch (most phones US phones have LGD panels but some have JDI from Japan) with LGD kernels. To fix the white lines you have to flash JDI specific kernels.
[Verizon LG G2] Lawlrus:
No one has said anything about the black lines.

I surely don't have them running his 1.1.0 kernel

Sent from my Vs980 running Xdabbeb's 24a v1.1.1
[Verizon LG G2] Rodeojones:
I changed nothing. Just flashed the 1.1.0 kernel on top of your latest ROM. Not a big deal. Just restored my backup and all is well. I can wait for the ROM itself to be updated.
[Verizon LG G2] xdabbeb:
Yes, that would mean you're on interactive then (as I had set that as default via an init script). All you have to do is change the mpdec in an app like trickster, or I'll upload updated init scripts shortly.
[Verizon LG G2] Rodeojones:
Thanks for the response. I tend to not mess with kernel settings and keep them as is. I was obsessed with kernel tweaking back in the OG Droid days and then realized developers are much smarter than I and I should just leave things be. Guess this one time my caution was also my mistake.