Database Develop

watch has been modified

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I get this message when there's no updates but when there is an update it still Let's me update. .. weird ... Anyone else
Press thx if i help you

stesteste said:
I get this message when there's no updates but when there is an update it still Let's me update. .. weird ... Anyone else
Press thx if i help you
Click to expand...
Click to collapse
maybe because of root

re-2007 said:
maybe because of root
Click to expand...
Click to collapse
Not because of that. Mine is rooted and does not say that.

stesteste said:
I get this message when there's no updates but when there is an update it still Let's me update. .. weird ... Anyone else
Press thx if i help you
Click to expand...
Click to collapse
My Galaxy Gear is giving me the same message as I try to check for updates. Has anyone found out how to update the Gear once it's been rooted/running custom roms etc.? Thanks.

Batman8 said:
My Galaxy Gear is giving me the same message as I try to check for updates. Has anyone found out how to update the Gear once it's been rooted/running custom roms etc.? Thanks.
Click to expand...
Click to collapse
fairly certain that you either wait for an updated ROM or flash a stock. i cant remember the last time any my android devices were upgraded via standard OTA type methods.

fletch33 said:
fairly certain that you either wait for an updated ROM or flash a stock. i cant remember the last time any my android devices were upgraded via standard OTA type methods.
Click to expand...
Click to collapse
Sounds good. My Gear is running the Null18 rom and I know that Null19 is available, so it sounds like I just need to flash that over mines correct? By the way, thanks so much for your quick response...much appreciated!

Batman8 said:
Sounds good. My Gear is running the Null18 rom and I know that Null19 is available, so it sounds like I just need to flash that over mines correct? By the way, thanks so much for your quick response...much appreciated!
Click to expand...
Click to collapse
actually null_20 is out now and very nice. if you just install it over your current setup there is a chance you could have issues. if you really want the best experience you should wipe everything then install. i always factory reset in TWRP then wipe cache and dalvik and then full reset again and then install new ROM but thats just me

fletch33 said:
actually null_20 is out now and very nice. if you just install it over your current setup there is a chance you could have issues. if you really want the best experience you should wipe everything then install. i always factory reset in TWRP then wipe cache and dalvik and then full reset again and then install new ROM but thats just me
Click to expand...
Click to collapse
2 Questions...when wiping everything did you loose all apps (including launchers like Nova or Apex)? Secondly, just curious if you are familiar with Kingo Root which I am trying to use on my Note 3? I happen to be updating both the phone and watch manually (since they were both rooted) and during my Note 3 updates I lost root. Now Kingo will not recognize the Note 3 at all, although the computer does so the drivers are still working. Any ideas?
Thanks.
P.S. - Nevermind. Also, just so you all know...Null_20 has a bug in Google Now that causes crashes sometimes as you boot up the Gear. The Null_21 rom has it now fixed.

CyanogenMod 12 - Discussion thread

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​ Here is a thread for the official CM12 Nightlies...
All discussion goes here.
Download the ROM here: http://download.cyanogenmod.org/?device=mako
Download the GAPPS here: http://forum.xda-developers.com/par...apps-official-to-date-pa-google-apps-t2943900
CyanogenMod Wiki: http://wiki.cyanogenmod.org/w/Main_Page
CyanogenMod Wiki - Information about Nexus 4 (a.k.a. Mako): http://wiki.cyanogenmod.org/w/Mako_Info
Latest changes: http://review.cyanogenmod.org/#/q/status:merged,n,z
Source: https://github.com/cyanogenmod

The build of our Nexus 4 failed
Hopefully tomorrow we will have a build!

The build for Vs985 is running flawlessly!

I never used cm on my nexus before, but I think time I give a try.
I'm a Brazilian without English Course, sorry and be comprehensive

Our build is pending at the moment. We'll have it soon. I am noticing the failed builds from yesterday have succeeded today. Fingers crossed xD

Looks like its starting to build. http://jenkins.cyanogenmod.com/job/android/97836/console

Build was successful! http://jenkins.cyanogenmod.com/job/android/97836/artifact/archive/cm-12-20150107-NIGHTLY-mako.zip

Anyone know how to remove apk's from the zip before flashing? Seems like the apk's are now hidden in big images.

Anyone finished flashing? Please share the experience.

wartle.S said:
Anyone finished flashing? Please share the experience.
Click to expand...
Click to collapse
Magandang (beautiful) experience! Everything seems pretty smooth. Using hellsCore kernel on top of this ROM. I haven't experienced any SoD's yet and I hope I don't lol. Have yet to find any major (or even minor) bugs just yet. But will keep playing around with it~

Guys, I got a problem. Trying to make fresh install. Installation of the ROM went OK, but problem with GAPPS. It says, Insufficient space on system partition. I wiped system partition, cache, data. I'm trying to install Full modular (not stock modular) GAPPS (like always with CM11). I have never had any problems, but now? What happened? I don't want to use smaller GAPPS. I have Nexus4 8GB, and 2.5GB of free space. Any suggestions?
*Added:
Now I got. I have /system folder restricted to 1GB or smth. And I can't put anything more, even if I have a lot of free space. But maybe somehow I can repartition and make /system partition bigger?

A useful information:
CyanogenMod 12 Will Integrate Superuser Settings With The Privacy Guard System, No Separate SU App Necessary
Click to expand...
Click to collapse
http://www.androidpolice.com/2015/0...cy-guard-system-no-separate-su-app-necessary/

strongiukas said:
Guys, I got a problem. Trying to make fresh install. Installation of the ROM went OK, but problem with GAPPS. It says, Insufficient space on system partition. I wiped system partition, cache, data. I'm trying to install Full modular (not stock modular) GAPPS (like always with CM11). I have never had any problems, but now? What happened? I don't want to use smaller GAPPS. I have Nexus4 8GB, and 2.5GB of free space. Any suggestions?
*Added:
Now I got. I have /system folder restricted to 1GB or smth. And I can't put anything more, even if I have a lot of free space. But maybe somehow I can repartition and make /system partition bigger?
Click to expand...
Click to collapse
Are you on latest TWRP?

Hi,
where did you get the GAPPS for CM12?
I can just find it for CM11 [1] [2].
newpipe
[1] https://itvends.com/gapps/
[2] http://wiki.cyanogenmod.org/w/Google_Apps

newpipe said:
Hi,
where did you get the GAPPS for CM12?
I can just find it for CM11 [1] [2].
newpipe
[1] https://itvends.com/gapps/
[2] http://wiki.cyanogenmod.org/w/Google_Apps
Click to expand...
Click to collapse
http://fitsnugly.euroskank.com/?rom=banks&device=gapps
https://s.basketbuild.com/gapps
http://forum.xda-developers.com/par...apps-official-to-date-pa-google-apps-t2943900
Edit: Gapps are not ROM-dependent.

Hey guys, quick question, does cyandelta still works with cm12?

fr3quency said:
http://fitsnugly.euroskank.com/?rom=banks&device=gapps
https://s.basketbuild.com/gapps
http://forum.xda-developers.com/par...apps-official-to-date-pa-google-apps-t2943900
Edit: Gapps are not ROM-dependent.
Click to expand...
Click to collapse
Update the OP with the link of PA GAPPS and a few more info. Thanks

fr3quency said:
Are you on latest TWRP?
Click to expand...
Click to collapse
Yes, I'm on latest TWRP 2.8.3.2.

Does anyone have the 'miscellaneous' battery drain in the battery stats screen?

Aashrey99 said:
Does anyone have the 'miscellaneous' battery drain in the battery stats screen?
Click to expand...
Click to collapse
In CM12? It should be fixed: https://code.google.com/p/android-developer-preview/issues/detail?id=189#c112

Help fix lag (switched from ATT to T-mobile)

A little background: I have had my nexus 6 for 3 months. I ordered it from Motorola and was using it on ATT. A few months in I rooted my phone as was using the Franco Kernel (default settings). Everything was buttery smooth.
About three weeks ago I switch to T-Mobile and for about the past 2 weeks I have been getting horrible lag and my battery is bad (~2 hours SOT). The Lag is really frustrating. A few days ago I updated to 5.1.1 through Wugfresh's Nexus tool (the no wipe way) and re-rooted. I did not use the Franco Kernal because it doesn't work with 5.1.1. I am still experiencing a lot of lag.
What is the best way to fix this? Would it be some type or full factory reset? Is there a way to do this and re-download your data? I did a backup though Wugfreshes tool and through Titanium Backup. I am willing to go to an extreme measure because the lag is brutal. Thanks for your help!!!

Stigga said:
A little background: I have had my nexus 6 for 3 months. I ordered it from Motorola and was using it on ATT. A few months in I rooted my phone as was using the Franco Kernel (default settings). Everything was buttery smooth.
About three weeks ago I switch to T-Mobile and for about the past 2 weeks I have been getting horrible lag and my battery is bad (~2 hours SOT). The Lag is really frustrating. A few days ago I updated to 5.1.1 through Wugfresh's Nexus tool (the no wipe way) and re-rooted. I did not use the Franco Kernal because it doesn't work with 5.1.1. I am still experiencing a lot of lag.
What is the best way to fix this? Would it be some type or full factory reset? Is there a way to do this and re-download your data? I did a backup though Wugfreshes tool and through Titanium Backup. I am willing to go to an extreme measure because the lag is brutal. Thanks for your help!!!
Click to expand...
Click to collapse
see what franco you are on. Try updating to Franco 28. His Kernels do work with 5.1.1 as he's a reputable (imo) tech.
play with a couple of roms and kernels to get the one that fits your habits.

Stigga said:
A little background: I have had my nexus 6 for 3 months. I ordered it from Motorola and was using it on ATT. A few months in I rooted my phone as was using the Franco Kernel (default settings). Everything was buttery smooth.
About three weeks ago I switch to T-Mobile and for about the past 2 weeks I have been getting horrible lag and my battery is bad (~2 hours SOT). The Lag is really frustrating. A few days ago I updated to 5.1.1 through Wugfresh's Nexus tool (the no wipe way) and re-rooted. I did not use the Franco Kernal because it doesn't work with 5.1.1. I am still experiencing a lot of lag.
What is the best way to fix this? Would it be some type or full factory reset? Is there a way to do this and re-download your data? I did a backup though Wugfreshes tool and through Titanium Backup. I am willing to go to an extreme measure because the lag is brutal. Thanks for your help!!!
Click to expand...
Click to collapse
Try wiping Cache and Dalvik in recovery. This fixed it for me as I had the same horrible lag after rooting and creating a Nandroid.

dray said:
Try wiping Cache and Dalvik in recovery. This fixed it for me as I had the same horrible lag after rooting and creating a Nandroid.
Click to expand...
Click to collapse
Thanks for the reply. Is there any guide/videos on how to do that?

Stigga said:
Thanks for the reply. Is there any guide/videos on how to do that?
Click to expand...
Click to collapse
Are you running stock or custom recovery? (TWRP, CWM etc)

dray said:
Are you running stock or custom recovery? (TWRP, CWM etc)
Click to expand...
Click to collapse
I have the twrp app but not sure which one I am running. I am new to this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I do see that option in the app - Screenshot attached

Stigga said:
I have the twrp app but not sure which one I am running. I am new to this
View attachment 3350256 I do see that option in the app - Screenshot attached
Click to expand...
Click to collapse
If you use the Nexus Root toolkit it will boot into recovery for you under advance utilities.

Have you tried a factory data reset after switching carriers?

Krunk83 said:
Have you tried a factory data reset after switching carriers?
Click to expand...
Click to collapse
I reflashed 5.1.1 and wiped my data - much better now
Sent from my Nexus 6 using XDA Free mobile app

Battery percentage showing 3800% after flashing 6.0.1/Root/LK

I just did a no-wipe flash of 6.0.1 and then rooted with NRT and flashed LK (I had it with 6.0 too) and now my battery percentage is messed up. Keeps fluctuating in the 3000s. Any ideas?
http://imgur.com/a/90iUu

I'm having the same problem here, confused

its a bug, ignore it. btw http://forum.xda-developers.com/nexus-6/help/battery-problem-6-0-1-factory-image-t3265899

It's a bug of 6.0.1... Wait for small OTA or 6.0.2

Is it a bug or just an issue with custom kernels? I expect the latter.

simms22 said:
its a bug, ignore it. btw http://forum.xda-developers.com/nexus-6/help/battery-problem-6-0-1-factory-image-t3265899
Click to expand...
Click to collapse
How long do I have to ignore it? What's causing the problem?

Amos91 said:
Is it a bug or just an issue with custom kernels? I expect the latter.
Click to expand...
Click to collapse
It's not a custom kernel - its a fresh factory image install, so stock kernel.
I'd say wait for Google to push an OTA out or another factory image.

Shadester9 said:
How long do I have to ignore it? What's causing the problem?
Click to expand...
Click to collapse
cause, no idea. but i remember the M dev preview had the same issue. some were affected, some werent. id just give it a few run throughs, maybe itll fix itself?

Well, it's not the kernel, since I have the same issue with the stock kernel with 6.0.1 and LeanKernel.

This is just bad.. I can't see how long my battery will actually last
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://imgur.com/24jDFHQ

Yeah, I think I'm going back to 6.0. This isn't worth it.

Not only battery status messed up, the Battery tab in setting is missing as well ...

antiquezip said:
Not only battery status messed up, the Battery tab in setting is missing as well ...
Click to expand...
Click to collapse
Yeah, I accessed mine by tapping the battery icon in quick settings.
Really odd for a bug like this to go unnoticed by Google.

No issues here on a clean install (including partition trims in TWRP) of 6.0.1.

Face_Plant said:
No issues here on a clean install (including partition trims in TWRP) of 6.0.1.
Click to expand...
Click to collapse
Nice! Mines still saying 3925% battery.. Mine was a fresh install from the Google dev images. Full wipe too..

MarkPH123 said:
Nice! Mines still saying 3925% battery.. Mine was a fresh install from the Google dev images. Full wipe too..
Click to expand...
Click to collapse
That's strange. Wiping everything (including internal storage) and doing a partition trim in TWRP before flashing the image fixed it for me. Are you rooted? Custom kernel?

Face_Plant said:
That's strange. Wiping everything (including internal storage) and doing a partition trim in TWRP before flashing the image fixed it for me. Are you rooted? Custom kernel?
Click to expand...
Click to collapse
Ah I see, I was rooted beforehand but wiped everything for a clean slate.
So still stock recovery, stock kernel and no root.
Might have a go at TWRP partition trimming tomorrow when I've got some time to do it.

My battery indication shows 100%, did a clean install and no issues whatsover.

gee2012 said:
My battery indication shows 100%, did a clean install and no issues whatsover.
Click to expand...
Click to collapse
This is odd.
I did use NRT's 'Stock & Unroot' option.
It may have missed the kernel so I'll extract that and try flashing different parts of Android to see if I get any sense out of it or some sort of fix, or Google may figure it out before me (hopefully )

Shadester9 said:
I just did a no-wipe flash of 6.0.1 and then rooted with NRT and flashed LK (I had it with 6.0 too) and now my battery percentage is messed up. Keeps fluctuating in the 3000s. Any ideas?
http://imgur.com/a/90iUu
Click to expand...
Click to collapse
Congratulations man! You're battery should last a whole month without charging!!! Suh-weeeet!

OP3T Constant awake?

My device is constantly awake on the current build after doing a full clean flash (twice).
Something in the system is holding awake after the screen is off.
So I've tried stock OOS and CM13, and I am still getting the same wakelock so that means it is not ROM dependent, something else changed within my phone that is causing this wakelock.
I first started noticing this wakelock when I tried the offical ResurrectionRemix 7.1 from here, after flashing that ROM, I've had the wakelock on all other roms. Anyone have any ideas about how to solve this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

check with better battery stats app and post Screenshots

ForcedZucchini said:
My device is constantly awake on the current build after doing a full clean flash (twice).
Something in the system is holding awake after the screen is off.
So I've tried stock OOS and CM13, and I am still getting the same wakelock so that means it is not ROM dependent, something else changed within my phone that is causing this wakelock.
I first started noticing this wakelock when I tried the offical ResurrectionRemix 7.1 from here, after flashing that ROM, I've had the wakelock on all other roms. Anyone have any ideas about how to solve this?
Click to expand...
Click to collapse
Take it off the charger.
Sent from my OnePlus 3T using XDA Labs

Try the wakelock detector app
Sent from my ONEPLUS A3000 using Tapatalk

Attaching some wakelock screenshots. These also show that it is off the charger.

Id format everything in twrp after saving anything valuable. Then I'd install a ROM without flashing Google apps. I wouldn't even login or sign-in or install a single app after booting up. Then see if the issue is still present. If it is gone then you know it's either your apps or Google but not the ROM or phone.

954wrecker said:
Id format everything in twrp after saving anything valuable. Then I'd install a ROM without flashing Google apps. I wouldn't even login or sign-in or install a single app after booting up. Then see if the issue is still present. If it is gone then you know it's either your apps or Google but not the ROM or phone.
Click to expand...
Click to collapse
So here is what I've tried so far:
I installed stock OOS Recovery over TWRP. Through the stock recovery I sideloaded the official OOS 4.0 Nougat release and wiped the phone clean through recovery selecting the option (Erase everything (pics, vids, etc.)). I then rebooted the phone and completed set-up by skipping everything and no google sign in. I am still getting the constant wake issue.
I also noticed the following kernel wakelocks that show 99% and 69% usage respectively:
1. fusb301_otg_wl
2. 6a00000.ssusb
I found these threads around the wakelocks above.
https://forum.xda-developers.com/showthread.php?p=68634552#post68634552
^ This one suggests clearing cache on Play Services, I tried this and still not working.
https://forum.xda-developers.com/oneplus-3/help/otg-wakelock-problem-t3511310
https://forum.xda-developers.com/oneplus-3/help/6a00000-ssusb-wakelock-wld-bbs-t3463062

Just wanted to update in case anyone else has this problem. I have fixed the issue.
I flashed 3.5.4 OOS and then proceeded to install CM13. I am no longer experiencing constant wake on CM or OOS.

ForcedZucchini said:
Just wanted to update in case anyone else has this problem. I have fixed the issue.
I flashed 3.5.4 OOS and then proceeded to install CM13. I am no longer experiencing constant wake on CM or OOS.
Click to expand...
Click to collapse
Will try this. Hopefully this helps.

The problem has actually reappeared for me on OOS. Still not sure what is causing it...
Screenshot attached is me currently running OOS Nougat beta.

I've got already the same problem
ForcedZucchini said:
The problem has actually reappeared for me on OOS. Still not sure what is causing it...
Screenshot attached is me currently running OOS Nougat beta.
Click to expand...
Click to collapse
Did you solve the problem? I'm bored with this new phone. Thanks