Search results

2 solutions - 1) Install Android Wear 1.5 APK and don't update 2) change the Build.prop line "ro.build.type=userdebug", to "ro.build.type=user" This isn't a bug with the ROM, just another stupid Google decision.

Oh this is awesome! Good work. I'll be joining the nightly (or rather builds until nightlies) and giving feedback starting tomorrow. Good job to yourself (and CodeworkX if he's been working on this too!)

I love my G4 and it's going to do me for the next year or so, but I detest LG's design choices. People like CodeworkX maintaining the CM13 branch for this device is the only reason its usable for me, and with CM13 it's a great phone. I think I'll be going Nexus (Pixel?) when I'm due for upgrade...

I'm curious as to how this works - e.g I thought using Android Pay on any custom ROM would cause SafetyNet to trip due to not being signed by OEM's? I only ask because I am the niche that wants an unrooted custom ROM over manufacturer customized OS, but would really like Android Pay. I currently...

Only real issue I've experienced over the last couple of months of nightlies is the needing to toggle aeroplane mode to make data work after a reboot. Not sure if this is supposed to be fixed or not, maybe I need to clean flash everything and try.

Noticed this on cmxlog. Will we be required to clean flash this build?

About the same to be honest. I saw no real difference other than the lag on stock firmware. The only thing that makes it a little better for it IMO is that CM13 has caffeine which is a toggle to stop your screen lock, so you don't have to set awkwardly long timeouts and such.

I've got a friend who is using stock firmware experiencing the same thing, if we manage to find a fix I'll be sure to let you know!

I have been using CM13 for nearly the entire time I've had my G4, and I thought I'd try the latest Stock ROM to see if the battery life was better (game optimizer, etc.) and I experienced the exact same thing. Lagging down to 2-3fps when trying to catch a pokemon sometimes, other times...

Try it? If not, no. It's probably dependent on LG framework and that ROM is literally just a debloated stock LG ROM so it wouldn't surprise me.

I believe so, but QCView requires root anyway which is probably why it works.

Sorry, I'm not a developer merely someone that tweaked it to make it display properly on CM13, I won't be supporting other ROMs. As long as the ROM has a form of case locking/unlocking there's no reason why it shouldn't work, you could always try bigboots original APK and if that works you'll...

You the man. No more crazy locking/unlocking sounds when the cover is closed, the only thing I had to do was define the symbol with a PowerManager before the first mPowerManager and it ran fine. I will say that I didn't actually add the permission you mentioned previously in to the manifest...

Edit I can't sleep anyway, so decided to give it a go. After failing with syntax for about 20 minutes, I've hit a stop with an error when trying to run 'error: cannot find symbol method goToSleep(long). Googling around people are saying it was removed from powermanager in API 21, but I'm not...

Thanks to BigBoot93's changes earlier I've been able to literally throw one number in to get QCview to display in the right place on the G4. There are literally no other changes, which isn't enough to warrant it's own thread IMO, all thanks should go to bigboot93 for making this possible and...

Well QCview and the latest builds unlock/lock play kinda ok together - nicer than before on the unofficial build which literally just gave a black screen instead of QCview. QCview now shows and actually unlocks when its not showing, however when locking the device by closing the cover it...

It's not a CM issue, it's a swiftkey issue. Source There's a couple of work-arounds in that thread, try those.

Thanks again. Hopefully it won't need much more than alignment at this rate! Codeworkx just merged changes to the CM13 G4 common files that will allow it to detect open/close of the cover, so if that plays nicely it's just getting that y axis offset so that it's aligned properly. I will wait...

Oh awesome. As an extension on that, I asked Bigboot93 for the source for qcview which they have kindly provided, so I'll be using my extremely limited knowledge to try and get that aligned and working correctly with CM13 for anyone who's looking for a little more functionality - although if I'm...

Odd, I've even tried fresh flashing a fresh build and unless the circle is already lit up or I double tap to wake it first opening the case does nothing, I even tried messing with power management options. This has a lot more potential than LG's actual quickcircle apps IMO, the way it handles...

Is yours actually waking if the circle screen is off and you open the cover? Mine only opens if the circle screen is active. If the device is locked and nothing is showing, opening the cover doesn't wake the phone. I tried using a secondary app to make the cover work, but it makes it go a bit...

Quick Circle case arrived, and while qcview works it's a little unnatural looking, especially when opening the case after it's come out. Flashed that old unofficial nightly with primitive support, it's really clean and feels very natural with the unlock comparitvely! Unfortunately the two don't...

Works on G4 but seems a little glithy with the lockscreen after you open the case.

Yes, it is fixed now, just like it was fixed the last time you asked. Latest build has a bug with the pull-down toggles. I haven't experienced any other bugs in quite some time. ---------- Post added at 03:52 PM ---------- Previous post was at 03:45 PM ---------- Can confirm same behavior as...

Same behavior without the theme? Latest nightly?

Just tried flash on, off and auto on latest build, all photos saving here too.

codeworkx you failed I'm afraid, the nightlies are still incredibly stable. ;) On a side note, the extremely simple quick circle solution - I know it was in that unofficial nightly, did that ever get merged into G4 common? Trashed my poor G4's back a bit, seems I can get 3 quick circle cases...

Todays build fixed the camera issue as you said it would codeworkx :)

On latest (11/01) Nightly? Was it a clean flash or update dirty flash?

I imagine that might work, I don't really need the camera so I'm standing by in case codeworkx needs any other info to fix it.

Unfortunately that isn't the case in the latest nightly for me, shortcut, app drawer and lockscreen shortcut all give the same 'camera has stopped working' error. If you need the camera for anything, I wouldn't recommend flashing todays build, but if you don't it would be useful to see if it's...

Interesting - mine doesn't work when connected to the PC, so that's different at least :P

Hurr durr, sorry still kind of new to this. :p https://paste.ee/p/qe2qt Not gonna lie, never done the whole logcat thing before - there's probably a lot of unrelated crap in there as I sat there for a while going "hmm does this stop itself or?" Also, this could be down to me screwing around...

Not sure if just me but getting 'unfortunately camera has stopped' upon launching camera on latest nightly.

Although the answer is yes, it would be yes regardless of the handset. I think it's getting blown out of proportion ever so slightly, obviously there is a fault but we have to remember that G4 owners coming to XDA or Reddit will be an extremely small representation of G4 owners - and a lot of...

I'd recommend reading through the thread just to see what people are saying. As someone who's been monitoring it, network switching between 3G/LTE wasn't working apparently and was fixed in the last nightly however this was never something I noticed because it's not something I do. The only bug...

I think it's because originally codeworkx actually had in the OP that you should boot CM before flashing Gapps as an 'important' step. This has since been removed though, so it's safe to say that no one should be doing that anymore.

Do you ever stop coding!? :P Great work. Will the update make it into the next CM13 nightly?

http://review.cyanogenmod.org/#/c/126824/ Codeworkx you legend, I've noticed from the commits the last couple of days that you've been working really hard to get this implemented. Great work!

Been dirty flashing nightlies for a couple of weeks and didn't experience this, I've just tried removing my pin lock then renabling it and its fine on my end at least. Obviously I can't speak for a clean flash at this time though.

Been using this for a while and my alarms have never failed me for what it's worth (Y) I believe the problem was fixed quite a while ago.

Can't help but reply to this, as while it's unrelated to development as such, I feel the note it's been left on is kind of important to the thread and any potential G4 owners looking and considering CM13 for their devices might be put off by this comment. The settings app is the least of my...

Thanks. I guess as I don't use a quick circle case and I've got snap camera working fine anyway I'll just stick with official for now.

Out of interest codeworkx, would you recommend us jumping on unofficial or sticking to official? Can we still update using deltas from official with the unofficial? Sorry for the nooby questions, this is actually my first android device so just not sure whether to stick with the official build...

That's a damn shame, it seemed so promising :( Anyone have any thoughts on the new version of this vs G4 Open Camera vs Open Camera /w Camera API 2 enabled?

Would you mind testing a shot with back camera, first flash off then flash on? codeworkx think I've figured it out, flash on = pictures disappear, flash off = pictures save fine (with back camera) IIRC this was an issue with the G4 Open Cam too

Which nightly are you running? I'm on the latest and flashed original and this now twice, photos still not saving for me when using back camera, to SD or internal. Front camera works, takes pictures and saves, back just makes sound and doesn't save.

New version fixed front cam green line, however back camera still not actually saving the photos for me when choosing internal or SD. Makes the noise, just no picture saved.

Doesn't seem to be storing pictures for me. UI and speed seem great, but no pictures regardless of SD storage or Internal storage selected :( Also experiencing green line on front camera. Edit: Funnily enough it saves pictures with the front camera which has the green line :p

Gotta say, been using this as my daily driver updating daily and it feels so complete. Really great work on maintaining this codeworkx (Y)