yashsingh1/xdaforums huggingface dataset:
[G2 Q&A, Help & Troubleshooting] wapem:
Hi to all ,so guys i'm interested to buy the G2 but first i have some questions for those who already have them ,reviewers are too biased and hit or miss always with any phone ,firstly i'm huge in gaming so i heard the G2 has great battery life but no one seems to make a battery test based on on gaming purely ,second thing is i'm curious about the buttons from the back ,volume and power ones , are they sturdy enough ? they don't fall down after some time or something right? the way they're placed just seem like the volume buttons might get unglued , and a big concern is about the Li Po battery which is said to be prone to explosions and catching fire if overcharged or damaged what about that anyone heard anything about G2's taking that route ? thanks .
[G2 Q&A, Help & Troubleshooting] 2001400ex:
Battery life is great, better than my RAZR maxx HD but not as good as my wife's droid Maxx. I have the Verizon version and no problems with the back buttons, actually like that combo with that and knock on. Speed is fastest phone I have used now and faster than my wife maxx, tho I'm not a huge gamer.

The only knock I have on this phone is the fingerprint magnet of the back. I prefer the carbon that the droid maxx has.
[G2 Q&A, Help & Troubleshooting] ddobes:
I really love the phone. No major complaints and it runs like a beast.

The biggest issue for me was that when paired with my car bluetooth, I could not get Pandora to stream at all. I disabled default music apps and got it to play (with no song title/artist text) but it would still pause ever so often, even multiple times during the same song. So I had to either root the phone or take it back as Pandora is my friend for about an hour each way to/from work.

Really, otherwise I had no issues with the phone. I don't think the battery is a problem for normal use. It lasts much longer then my Droid RAZR previously, and I can make it through waking up, taking it off charger, to work, normal work usage, screen brightness normal and wifi/BT/LTE all on throughout, and back home with still around 30-50% roughly. I don't know what the best battery app to benchmark would be. I do know playing Plants vs Zombies in the morning to wake up eats the battery.

Another odd thing is it gets really hot when it's flat, even though I don't see any vents or anything on the back. But again, that's during heavy PvZ action, otherwise no difference at all.

Also, I hate the Verizon typical bloatware and some of the apps/settings like QSlide are neat, but not really worth it for my usage. QuickMemo is awesome, love the knock on and knock off, which is great for meetings., and really liked the slide up menu. Also had some easy options for changing look and feel to some degree of the nav buttons.

One last thing, I still can't get used to the back buttons. It's not a major problem, I dont really use them all that much, but I still find myself struggling to feel for them or hit them. Not a worry enough to take the phone back.
[G2 Q&A, Help & Troubleshooting] stetre76:
I'm using the G2 for a bit more than two weeks now, and so far I am reall impressed by the battery life.

With my old One X I wasn't really a fan of playing, because you could literally watch the battery drain, but with the G2 I came back to playing Real Racing 3 and Angry Birds Go.

My experience is that battery life while gaming also depends on the game (of course) and the screen brightness - battery drains faster while playing Real Racing 3, but playing for an hour or so doesn't drain the battery more than 15-17%, with Angry Birds Go it's even less (approx 10%).

This leaves me with Screen-On times of 5-6 hrs > 60-90 mins of playing, emails, FB, internet, photographing, GPS tracking,... (settings: WIFI on, brightness > Auto, Data on, GPS on)

The back buttons look solid and I don't really think that they will cause a problem or fall out. But I guess that also pretty much depends on how what you're doing with your phone and how you treat it ;)
[G2 Q&A, Help & Troubleshooting] vPro97:
I'll give another perspective :)

15 minutes of Asphalt 8 drained about 8%.

There is microstutter when playing asphalt 8 but it is also occurring when playing the game on medium visual quality, so it could very well be the game.

The phone gets warm quite quickly, but I've never experienced it getting burning hot. CPU reached 70 C and battery reached 40 C.

My two cents :)
[G2 Q&A, Help & Troubleshooting] l3gacy28:
Best and most Stable ROM

Hey Everyone,

I am new to the LG G2 forums and will be getting an LG G2 soon. (Coming from Epic 4g Touch) I was just wondering, what ROM would you guys recommend? I want a ROM that provides really good battery life and some nice features. It doesn't need to have a plethora of features, just a few here and there. My biggest concern factors are stability and battery life. What would you guys recommend?
[Fascinate Android Development] times_infinity:
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4 (Kit Kat), which is designed to increase performance and reliability over stock Android for your device.

#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/

CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.

All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

Working

:

Assuming everything.

Not Working

:

Data is wonky.

Installation Instructions

Coming From Stock

:

Download latest CM10.1 Nightly from here, CM11 ROM and 4.4.2 GApps zips from below and copy to sdcard.

Reboot to recovery

Make a backup of current ROM setup and Data YOUR DATA WILL BE WIPED

Flash CM10.1 zip

Flash CM11 zip. Follow next step carefully

You will get a partition layout error. Flash CM11 zip again

Zip install will fail with set_metadata_recursive: some changes failed

Reboot recovery from advanced menu. Notice recovery version CWM-based Recovery 6.0.6.4

Wipe Data/Factory Reset

Flash CM11 zip one last time

Flash GApps

Reboot

Coming From CM10.1

:

Download CM11 ROM and 4.4.2 GApps zips from below and copy to sdcard.

Reboot to recovery

Make a backup of current ROM setup and Data YOUR DATA WILL BE WIPED

Flash CM11 zip. Follow next step carefully

You will get a partition layout error. Flash CM11 zip again

Zip install will fail with set_metadata_recursive: some changes failed

Reboot recovery from advanced menu. Notice recovery version CWM-based Recovery 6.0.6.4

Wipe Data/Factory Reset

Flash CM11 zip one last time

Flash GApps

Reboot

ROM Download

:

CyanogenMod 11.0 2/20/14

md5: e832432b4268255b63d5507c8a639e99

CyanogenMod 11.0 1/9/14

md5: 7c937708189ba0112d6882d724a3a695

CyanogenMod 11.0 1/4/14

md5: b7df574c383a58fac360f5dc962c69c

GApps

:

PA 4.4.2 Modular Mini GApps

ROM take a bit to boot. Be patient.

Credit to:

CyanogenMod

TeamHacksung

jt1134

Disclaimer: I will more than likely not be supporting this very actively. Just posting this to get it out there.

Also, I have not tested installation with TWRP, nor do I have the desire to. I have only tested with the convoluted CWM debacle listed above.

Enjoy!
[Fascinate Android Development] times_infinity:
TWRP Install Instructions

:

Changelog

:

repo sync'd upstream changes.

merged FascinateRIL class from https://github.com/TeamRegular/andr...mmit/6678964eac6a9443adc85ef34dad0c2e76f30d58
[Fascinate Android Development] hhp_211:
... WOW that has come out of nowhere!!! :victory:

Thank you Mr. Infinity

We haven't seen you really around here in ages,,, but VERY much appreciated!!!!

.
[Fascinate Android Development] nm3210:
Uneventful update from CM11 12/06 with TWRP, everything works well even without formating my data! It did replace TWRP with CWM 6.0.4.6, but whatever. My successful steps were as follows: boot into TWRP, clear cache, install this new CM11 1/4, reboot recovery, install CM11 1/4 again, install new gapps 4.4.2, reboot. 3G/Wifi work. Have not tested MMS, but I assume it works like it did on previous CM11 builds.

Transparency is disabled by default now (for everyone who's curious) because in the build.prop the "ro.config.low_ram" option is set to "true". You can set it to false to get transparency (and anything else that gets flagged as low-ram) back.
[Fascinate Android Development] ztotherad:
Can't wait to play with this! This may actually make me update to kitkat on my fascinate! Thank you sir!
[Fascinate Android Development] skepticmisfit:
whoa I haven't seen you in a long time. welcome back and whoa cm11.

you thinking of making these official?
[Fascinate Android Development] kb8no:
Unfortunately data is borked and cycles on and off. I first dirty flashed and then did a complete wipe and no difference.
[Fascinate Android Development] nm3210:
Yeah a day later I agree. You can quick toggle it to get it to work for a few minutes but it's not very consistent. Also, maybe it's the new WhisperPush or something, but I couldn't send or receive MMS at all. When receiving MMS, I would get a notification (both my SMS Popup and an actual notification) but there was no message in MMS.apk and it definitely never downloaded anything.
[Fascinate Android Development] hutchjim:
hi

whats the difference between this one and the the 12/06 cm 11.0 ? anyone know cause i coudnt get it to load i bricked twice.....thanks foor your hard work though nice...
[Fascinate Android Development] kb8no:
This one is a smoother and if data was fixed I think it would be great. Data drops drove me off this in hours. No problems flashing. Maybe you got a bad download.

12/6 was rougher and data drop plagued as well so not a DD.
[Fascinate Android Development] swapnilss:
12/6 was all good for me. I used it for almost a month without a hitch. Data worked fine too for me. Just the urge of flashing something new took over and I tried DU5 but was put off by random reboots. So switched to cm 11 1/04. Happy with it till date. Off course data is flaky but will live with it until it's rectified.
[Fascinate Android Development] times_infinity:
new build is up guys.

hopefully it fixes data.

Enjoy!
[Fascinate Android Development] swapnilss:
Running this latest build without any tweaks since yesterday. Data is stable and so is the ROM. Great work. Thanks. :thumbup::thumbup::beer:
[Fascinate Android Development] trajik78:
great work!

lots of updates going through for the device on BBQlog so still curious why the Fascinate isn't officially being updated anymore?
[Fascinate Android Development] skepticmisfit:
jt1134, the official CM maintainer for the fascinate and a couple other devices (OG Tab 7 CDMA i think), has either retired the fascinate or isn't on TeamDouche anymore.
[Fascinate Android Development] A-L31:
the performance setting and ART not stick ~
[Fascinate Android Development] hhp_211:
You might try chainfires supersu

perf settings seem buggy though. even on du

Don't know in art..
[Fascinate Android Development] A-L31:
sorry, i just found out. i use xposed frameworks. after uninstall it everything i described above is false.

ART Working (takes time to boot, i almost inpatient i think i'm on bootloop :victory: )

Performance Stick at boot ~ :silly:
[Fascinate Android Development] hhp_211:
Good to know, thanks for the update
[Fascinate Android Development] A-L31:
i can't install app to sd card.

when i restore with TiBu it stuck. when i'm download from app store it says Couldn't install on USB storage or SD Card.

is it something to do with ART or the ROM?

what i'm trying to install / restore is whatsapp wallpaper. it goes automatically to SD

anyone?
[Fascinate Android Development] kb8no:
So far, so good. Looks nice. No data drops in a few hours. All ringtones / sounds are duplicate so probably in the ROM twice somewhere.

What is the difference between Launcher and Launcher3 and which one is more desirable?

I miss fast charge. Is there a Devil kernel that works with this ROM?
[Fascinate Android Development] skepticmisfit:
Launcher3 is the open source version of the google experience launcher (from what i've seen)

here's 4.4 devil kernel (thanks hhp): http://www.androidfilehost.com/?fid=23269279319202534

this has TWRP on it and was extracted from Dirty Unicorns.. i think

---------- Post added at 01:08 PM ---------- Previous post was at 01:04 PM ----------

a combination of TiBu and ART

i've heard WhatsApp stuff doesn't work with ART at the moment. also, i tried updating TiBu on an older ICS ROM that i was using (recently) and it couldn't install the update
[Fascinate Android Development] kb8no:
Thanks to hhp. His lovely fingerprints are all over the kernel! This is great. Now I have twrp and fast charge on a a ROM that is looking to be sweet.

Is Launcher like Aosp? Is Launcher3 the better choice here?

Hey, I've been playing with Google Cloud Print this week. It is amazing if anyone hasn't tried it yet.
[Fascinate Android Development] times_infinity:
Pretty sure Launcher is the Google Experience Launcher. Launcher3 seems to be the AOSP launcher.
[Fascinate Android Development] lightningdude:
I've got the same problem trying to restore/reinstall a tts app. I'm not on ART though.
[Fascinate Android Development] SupraLance:
My first taste of KitKat... I like it. I've been using cleared out apps from TBO for a while, so appreciate the better integrated transparency.

As for Launcher & Launcher3, Launcher is actually just an extension of Google Search and comes packaged with Gapps. As such, there is no way to remove google search from each homescreen. Launcher3 is what comes with CM11 and I think it is the better choice if you just want a basic launcher with the ability to hide google search and fit more/less icon rows/columns. If you want more launcher customisability, install Nova/Apex/etc. If you want something entirely different, try Themer.
[Fascinate Android Development] Bubbadogg14:
Themes provider keeps fc'ing for me. Other than that everything else seems OK.
[Fascinate Android Development] SupraLance:
Me too...

I'd like to be able to reboot recovery from the Rom, but can't find a way. Is there still a way to enable a hidden advanced options menu in CM?

I installed the devil kernel & deviltools, but the performance setting won't stick across a reboot. Ram setting stick though.
[Fascinate Android Development] kb8no:
I'm getting repeated android.process.media errors with Devil kernel. What is that about and what to do about it.
[Fascinate Android Development] kb8no:
This ROM did not like Devil kernel with twrp. Had to go back. Is there a Devil kernel with cwm?

---------- Post added at 10:30 PM ---------- Previous post was at 10:09 PM ----------

Settings > about phone > build number. Tap it 5 or 6 times to get developer options. Then check advanced reboot. Then you can boot into recovery from ROM.

I'm having troubles with Devil kernel with twrp too. I'd say for now reinstall as per OP with cwm recovery and stock kernel. Make settings to stock kernel with Trickster. If you don't know Trickster, swipe from right to save settings for reboot.

Then wait until we figure how to get Devil kernel working. I think we need Devil with cwm. Let the smart guys help us out.
[Fascinate Android Development] kb8no:
Ummm. If you remember, the Samsung Fassy has the kernel and recovery together and they have to be flashed together. Thus if the ROM comes with a kernel you will get by necessity the recovery chosen by the ROM dev. Likewise, if you flash a new kernel it has to come by necessity with the recovery chosen by the kernel dev.

When you understand this, and understand that kitkat is finicky and requires a special upgraded recovery and won't flash or work right with just any recovery, then all the double flashing starts to make sense. The first ROM or "kernel" flash is done only to get the correct recovery on the device that will flash the desired ROM you want.

This unique design, plus the need to change it from Samsung proprietary to open source mtd, makes the Fassy different and tricky for us compared to a GNex which has none of this.

So the Dev of this ROM needs us to use a certain updated cwm to flash it correctly. If twrp worked he would have offered us the choice. So this is why I'm thinking a Devil installed with twrp is giving us complaints
[Fascinate Android Development] SupraLance:
I also rolled back to the stock kernel (be sure to unmark "Inject TWRP" before reflashing CM11, as this also reinjects Devil)

FYI, if you use Launcher3 and hide the homescreen search box, the trash can also becomes unavailable, meaning there is no way to remove anything from your homescreen without re-enabling the search box.

I don't see the options I usually use there. Any way to increase RAM? Any particular settings that are recommended for our device?
[Fascinate Android Development] kb8no:
Yes. Don't forget to unmark "inject twrp" which I also did. Good point.

Sorry, I'm useless with kernel settings and usually just use stock. Hopefully somebody else will jump in to help. I'm very keen on fast charge which is my driver to get devil working.
[Fascinate Android Development] hhp_211:
I've got some of my settings and the devil tools apk link in my 4. 4 kernels & tweaks thread

http://xdaforums.com/showthread.php?t=2600743
[Fascinate Android Development] hhp_211:
Try going into settings||storage and unmount the sd card,,,

Then when it finishes re-mount it.

Should clear that up.

that only appears to be a temp fix

edit::

I have found though if you edit the::

/system/build.prop

and set the:: ro.config.low_ram=false

it seems to clear this up

What issues are you having?

Switching the recovery portion out to be cwm with devil will have no effect on how a kernel portion operates.

They do work independent of each other but have to be installed together on the fascinate ( which is different from most every other phone)
[Fascinate Android Development] nm3210:
I had to revert back to the CM kernel as well. While I LOVED the performance of Devil, I was constantly getting the media errors and it seemed that remounting the sd card only staved off the errors for a few hours. Doing a soft-reboot (which it seemed to do by itself sometimes) would guarantee that I would have a bunch of the media errors and only remounting the sd card (or doing a full restart) would make them go away.

Beyond that I was also getting theme provider errors. Anyone else? I just disabled the apps (Themes and theme provider) in TiBU.
[Fascinate Android Development] hhp_211:
I've been running this all morning now, cm11 with devil kernel and pa-gapps-4.4.2-20140111-signed.zip

I did notice the media fc error

my unmount/remount sd card does seem to only be temporary [on du rom it only returned, seemingly at most, every other day]

it seems though if you edit the::

/system/build.prop

and set the:: ro.config.low_ram=false

it seems to clear this up AND

it also cleared up the random reboots I had early on [ have not had one since ]

and so far I am not seeing any ill effects from it

I have also set with devoltools.apk under [memory management] [swappiness] = 0% (stock is 60%) you should only be using this setting if you enable zram,, which i plan to experiment with other settings i used in du too

Themes fc is a seemingly known problem with other 4.4 ROMs/phones not just ours

and yeah I just uninstall (Themes and theme provider) in TiBU,,, never use them anyway

along with a bunch of other things in /system apps I do not use

[or to keep System ROM size down]

you can verify disk size and free space in Terminal emulator

open up and type:: df

My setup::

/system | 590.6 Mb Available | 544.3 Mb Used | 46.2 Mb Free |

I also installed chainfire's newest 1.89 superSU app and enable:: Enable su during boot,,, enable:: Trust system user

I also turn off google hotword detection [ OK Google! ]

I do get the occasional back button [ freeze ] [toggling the screen off/on with power button generally fixes this, until it returns ]

I also still have not gotten the browser to [ sync ] under my google account setting [that is no rom issue, ive had it happen before, probably clear its data... ]

At this point I would say this is a fast stable ROM

successful with Devil Kernel :good:

http://www.androidfilehost.com/?fid=23269279319202534

3.0-kernel-Devil_TWRP_4.4.2_12-29-2013-fassy.zip

.
[Fascinate Android Development] nm3210:
I've had the low_ram flag set to false from the get-go. I edited the file before pushing the zip to my sd card so I've never even booted up with it set to true. So I really don't think that's the [sole?] solution here. Maybe it's a specific app (or a certain state within an app) that's causing it? I forgot about pulling a logcat when I was having issues but I can possibly do that later. I have missed two morning alarms because of the media error, so forgive me if I'm a little cautious and pessimistic.

I am using a different GApps, however (I noticed I have a lot more free space than you are reporting, i have over 100MB free in /system). I have been flashing the pa-modular 4.4.2 2013-12-30. Maybe there's something in there doing this?
[Fascinate Android Development] hhp_211:
sorry not trying to say sole solution but I was setting things up and getting the fc's / reboots,,, the only thing I might have done before the "ro.config.low_ram=false" settings would have possibly been the 1.89 superSU, but I do remember right after was doing the [swappiness]

it did seem to clear up the random reboots I was having, but again it could be a combination of superSU too...

I just know that so far I've not experienced anything that would make me want to uninstall the devil kernel and go back to stock

I do run all my stuff with ::

Zen - I/O Scheduler

Lulzactive - Governor || Smooth Ui = Off ||

whenever possible
[Fascinate Android Development] hhp_211:
There are my system app sizes, i realize this will change by personal preferences.

The approx 50 mb free space i have seen across the last handful of ROMs I've ran, not just cm11.

Just mentioning it because i feel like i run pretty light on system apps/gapps,,, yet it still runs low
[Fascinate Android Development] Unjustified Dev:
Gee man at least let me close my thread. There shouldn't be two threads open if your going to work on this. Enjoy :) . The fascinate will see some cool stuff when I finish setting up my pc again. I only did cm-11 builds to get 4.4 going initially . Now it's time to work on some other stuff again.
[Fascinate Android Development] jkok:
(cough cough) getting brian to update dirty unicorns (cough cough)

kidding lol tell him to take his time lol but cant wait to see what is next in the Unjustified Dev line of roms :P
[Fascinate Android Development] Unjustified Dev:
You know how I roll. Vanir all day not spamming op. I gave a build of vanir since 4.2.2 cant wait for 4.4.2 . [MENTION=3943728]BDogg718[/MENTION] ill take vanir off your hands.