yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] magnamentis:
thanks a lot for the insight :) i kill recent apps with LMT and tasker scripts but good point that you can keep it in recents. i like my recents empty but that is not based on anything tech, it's just my orderly nature LOL

indeed i did not find a way to get rid of that, perhaps it's just not possible. no clue to be honest, no big help i know :)
[ONE Android Development] Gagi77:
goo.gl/zuK7BA Have the same problem, please help me.Wifi automatically connects and disconnects.

---------- Post added at 07:55 PM ---------- Previous post was at 07:48 PM ----------

I use it MT6592 model phone.
[ONE Android Development] Okeys:
Guys,help me plz.Which modem is better?Because I have some problems with them.
[ONE Android Development] dslsd:
A difficult choice) is now raid supporters c6 and cast aside rotten tomatoes),I use C7-00011 and for my needs there is no problem no.
[ONE Android Development] koudies:
From my understanding it's really based on your location so try a few and see is my best advice. I also use c7-00011 and have no issues.
[ONE Android Development] kryshnakishore:
@ Naresh Rawat dirty flash rom again & dnt use custom kernals at all
[ONE Android Development] GIL0802:
How's that even possible ? HOW!? :eek:

---------- Post added at 02:22 AM ---------- Previous post was at 02:17 AM ----------

That's the point of this ROM. I like features a lot. Keep it up Varuun. :laugh:
[ONE Android Development] kryshnakishore:
Setting background process limit to 3.is this the code to change in build.Prop? Oneplus did this in op3 ram management

ro.sys.fw.bg_apps_limit=3
[ONE Android Development] GIL0802:
Hi there!

I love this ROM so much because it have a lot of features that i really like. So one of those features was back in march build in the camera app that i could record at 60fps, 90fps, 120fps,etc.

I would like to know what happened with that or how i can have that Apk again working on the latest ROM.

I provided a screenshot of the option on the camera app in CM13 SultanXDA.

Cheers!
[ONE Android Development] Nikhil...007:
I installed the 17th build with latest open gapps(stock) coming from cm13 snapshot, when ever i try to call someone or someone tries to call me, my phone does a random reboot. Tired of this I went back to cm 13, but still the problem exists. I changed the baseband, tried different roms, different gapps but still the problem exists.

Can anyone help me out with this?
[ONE Android Development] iPusak Gaoq™:
Have you try disabling "Prevent Accidental Wakeup" and "Ambient Display" after you flash any rom?
[ONE Android Development] Nikhil...007:
Yeah! I do, but I don't think that's what is causing the issue
[ONE Android Development] iPusak Gaoq™:
Well since you have try different rom, modem and etc then i would guess your problem could be proximity sensor (hardware) :confused:
[ONE Android Development] siama41:
After flashing 17 build. My phone seems to improve in everyway. Thanks to the builder.

But there is just one problem i could not solved.

I want to upload photos on facebook and this permissions message appears which is unable to click.

I can only click deny but not allow.

Resulting in not able to upload any photos.

Kindly help me or instruct me to solve this problem.
[ONE Android Development] lanjor:
If you install open gapps stock, set google dialer as default. Setting-app-click setting icon on upper right-default app-on phone choose google dialer (phone)
[ONE Android Development] plantator:
Click deny, next go to settings->apps search for facebook, go to permissions and grant what you need
[ONE Android Development] Sukarn:
Why have you quoted my post?
[ONE Android Development] plantator:
Mhm for real I don't know:P mayby old multi quote option, sory:P
[ONE Android Development] maxed4901:
Sorry i did not understand you. If you think you may need to use it later, then you could just disable app which will not show up in app drawer and when or if you need can reactivate... Obviously ES Explorer is much advanced in terms of functionality compared to CM file.
[ONE Android Development] siama41:
Thanks works perfectly.
[ONE Android Development] Nikhil...007:
Thanks! That worked
[ONE Android Development] MiMilz:
Are you using apps like Lux or a screen filter ? If yes, it's normal you can't click on approve, it's a security by android to prevent "tapjacking" (the fact an app display an invisible windows to make you click on something without your consent).

But you can do it by the permissions screen in apps manager, like an other user said :)

Look here, problem already solved
[ONE Android Development] paarkhi:
Yes facing same problem here but for me it happens in most of the apps
[ONE Android Development] MiMilz:
Look my previous post, just above
[ONE Android Development] paarkhi:
Thanks but I know the solution already but that's not the permanent solution , just informing the dev about the bug.

I'm not using any lux or screen filters app
[ONE Android Development] MiMilz:
Ok, my bad then :)

I have no problem with this if I disable Lux, so I can't help you more ^^
[ONE Android Development] HaTrED_:
Are you using live display?
[ONE Android Development] Ztones:
Dirty flashed 17th and works great. The only issue is one random reboot (saw the 1+ logo... so that's hard right?).

I am losing some battery in airplane mode. It shows the device awake the entire time, but when I click through all the apps, only doze is reported to be awake during that time. Am I better off turning doze off or is that a "false alarm" (in that it has to be always running)?
[ONE Android Development] LPW00:
Live display still doesn't want to show itself in QS. Does anyone know how to fix it?
[ONE Android Development] plantator:
I have random reboots on lightning v23, no problems on erorcun 3.10 kernel and stock one
[ONE Android Development] paarkhi:
No sir, I do not use live display...
[ONE Android Development] saiamrock:
I dont know what happed to the random reboot seem it is kernel related

But we have same battery drain problem that keep phone awak

I use ampify and on wakelock show that i have really high contextmanagerwakelock (top of the list and marked red)

For work arround i limit its wakelock to 600 and it's done the tricks

Mine is opengapps pico, anybody facing same problem? What gapps you use?
[ONE Android Development] magnamentis:
search the receivers and switch them:

- on if they're off and on is marked as default

- off if they're on and test

- you need rom-toolbox to make it survive reboots as well as rom-updates

- keep the link bookmarked, works with "sytemupdateservice wakelocks and many others

- amplify and greenify only select apps and wakelock, i recommend to only amplify default "NLP- related wakelocks, doze takes care of the rest and in some cases limiting wakelocks has the opposite effect

http://xdaforums.com/showpost.php?p=67391296&postcount=2361
[ONE Android Development] KaszasM:
yeah have the same but you can give prems in settings, im still on slim gapps...
[ONE Android Development] Ztones:
I use open gapps pico also
[ONE Android Development] Gagi77:
goo.gl/zuK7BA Have the same problem, please help me.Wifi automatically connects and disconnects.I use it MT6592 chipset phone.
[ONE Android Development] magnamentis:
forget the network and reset it up. this is a router issue 99.9% sure. check re-keying intervals or switch re-keying off at all. reboot your router with power disconnect for at least 30" as well, if it does not help it's not doing any harm and often does the job.
[ONE Android Development] shiromau:
any chance of getting SKYPE integrated dialer from official CM 13.1 ???
[ONE Android Development] 345MMM:
Hey, can someone help me, I've just started using RR v5.7.0 and I'm having an issue with vibrator intensity setting not remaining after reboot?

Also, Kernel Adiutor isn't applying setting after boot.
[ONE Android Development] gabe13:
I didn't had any problem with vibrator intensity but I do know a quick way to solve all the bugs ;)

1.download latest cm nightly

2.download latest rr build and your gapps (the ones that you are using at the moment)

3.reboot to recovery, mount everything and wipe system, dalvik and cache

4.flash the latest cm nightly and reboot to recovery

5.make sure that everything is mounted and flash the rr build, gapps and other stuff that you use like xpossed, custom kernel etc.

6.reboot :D

I've had some rom related bugs and I did this and now the rom is smooth, fast and bug free and the best part is that you don't lose any data ;)

and for the kernel adiutor thing, try using kernel adiutor-mod app and disable the normal kernel adiutor

hope I helped :)
[ONE Android Development] Gagi77:
Thank you buddy, I have one more question, The device memory 16GB and Approximately 10GB of available memory but

In this ROM 4GB there memory.
[ONE Android Development] 345MMM:
Thanks for your help!

Before I installed RR's update I did all of the above. Was hoping I wasn't the only one with this problem. :(
[ONE Android Development] kaneelias:
Using lightning Kernel and the latest build, BetterBatteryStats shows that the phone is not going into deep sleep at all. Confirmed by rolling back to 16062016 build with lightning kernel and can confirm in BetterBatteryStats that the phone is now going back into deep sleep when not in use. Will continue to test and report back.
[ONE Android Development] indhimaga:
Nice Job buddy...
[ONE Android Development] kingsathurthi:
How do I get cyanogen app themer in our RR latest build?
[ONE Android Development] bloodbath:
I'm a little confused. There seems to be some difference in instructions in this thread on the proper way to perform a clean install, which I believe this is. Other instructions I've seen say to wipe data, system, dalvik, and cache, install CM nightly, reboot into recovery, wipe data, system, dalvik, and cache again, and then install RR and Gapps. You then wipe dalvik and cache and reboot.

This second data, system, dalvik, and cache wipe isn't performed in your instructions. Is this a typo or is this how it's supposed to be done? I'm not asking to cause any debates or anything, but I am having issues with things like external speakers and "Do not disturb mode" which others don't seem to have. I've already clean installed twice and just want to be sure I'm not doing something wrong. Thanks.
[ONE Android Development] iPusak Gaoq™:
1. Download latest CM nightly, latest RR, latest Gapps and etc....

2. Reboot into recovery (TWRP 2.8.6.0, 3.0.0.0 or 3.0.2.0)

4. Factory Reset

5. Flash CM Nightly

6. Reboot into system one time

7. Reboot back into recovery

8. Factory reset

9. Flash latest RR, Gapps, SuperSU and etc

10. Clear dalvik and cache

11. Reboot into system
[ONE Android Development] gabe13:
[/COLOR]

Yes you are right about the fact that this is not clean flashing.

I had some problems with the rom after I dirtyflashed the first build of 5.7.0 on top of the 5.6.9 test build and I discovered this method of refreshing the rom and getting rid of bugs without the hussle that is implied by clean flashing( adding the account again... installing all the apps... etc)

This is a quick method that works and does not affect the data partition. ;)

give it a shot, if after you did all the instructions your problems aren't solved maybe there are some apps or xpossed modules that interfere with those features that you wanna use.
[ONE Android Development] bloodbath:
Thanks! It appears to be the same as I have read before, and performed when I installed RR.

---------- Post added at 07:17 AM ---------- Previous post was at 07:17 AM ----------

Thanks for clarifying. I will give this a try.
[ONE Android Development] Kant73:
Hi [MENTION=4817632]varund7726[/MENTION]

First thanks for your latest build (5.7.0), solve all the battery drain bugs :)

But after a clean flash, I can't enable the agressive doze mode on Greenify app, even if Doze Powersave is enable in Miscellaneous settings. The option in Greenify isn't visible :/

I installed Check Doze app and it says me that the "doze config flag" isn't enable and that my device doesn't support Doze.

Can you fix it or you think it's a Greenify bug ?

Can I check if Doze is working well by another way ?

Thanks in advance and keep it up, your tom is amazing :)

EDIT: After two reboot nothing change but after Grenifying manually an application (adding it in the "app-to-greenify list") the agressive doze mode setting appear !

So it was a Greenify bug, your rom is just perfect ;)
[ONE Android Development] Nb07:
In kernel audiotr app wherever there is vibrator intensity option, there will be a toggle on top saying apply on boot...keep that on and you should be good to go even after reboot. This toggle should be on everywhere when you change something if you want to stick it after reboot. :good:
[ONE Android Development] dharmil007:
Boot Loop

Hello Guys,

My phone has gone into boot loop.

It is stuck on RR logo since past 25mins.

I can access the Internal Storage through TWRP.

I tried the following things :

Wiped : System, Cache & Dalvik cache.

Reinstalled Resurrection Remix 5.7.0 and GApps.

The last thing I did on phone was removed a theme of PowerAmp Player.

As soon as the un-install was finished my phone restarted and was stuck on RR logo.

Dont know what the problem is.

Please can anyone help.

Thanks
[ONE Android Development] Nb07:
best way is to clean flash but if you want to give a shot then try this, take nandroid backup from twrp...after that do a clean flash of RR 5.7.0 and gapps and reboot. do the initial setup wizard setup and reboot back to recovery and just restore the data of nadroid backup and wipe dalvik and cache and reboot.
[ONE Android Development] HaTrED_:
I've been using RR lately with a very good user experience, hands down to DEV, although, after a while, once available memory starts to fill up my device starts to slow down and this behavior is very noticeable: it gives me some micro freezes and that buttery smooth experience starts to fade way...

I can "solve" this after calling recents - through OmniSwitch - and kill every other app that is alive. After that, it's a new beginning until i get less then 500MB of available memory.

So, my question is: Is there anything that i can do to tweak, or mitigate, this symptom?

I'm all stock, clean flashed latest build and locked my phone to 1958MHz with SmartMax. No doze, no greenify...

Every advice you guys can provide me would be nice. Does anyone noticed this or... not at all?
[ONE Android Development] nemesis253:
I'm having problems with the latest build saavn keeps getting force closed
[ONE Android Development] Sander9847:
Extract it from CM13 and install it yourself if you want it.

You might have to replace the apk in root/system/priv-app/dialer if installing normally doesn't work.
[ONE Android Development] greg285:
Hi,

Slimgapps (mini) discontinued ? any other working ones to advise ?

edit : will try opengapps full and see
[ONE Android Development] MiMilz:
Hi, http://opengapps.org/ has already been suggested some pages before ;)
[ONE Android Development] greg285:
Yes thanks thats what i tried (mini package)

..did a factory reset and .had to format system also - now stuck on RR logo..did i miss something ?

ok : nevermind ..booting now
[ONE Android Development] Timmmmaaahh!:
Yes, a 'hard' or 'cold' reboot is when you see the 1+ logo; a 'soft', 'warm' or 'hot' reboot is when you see just the RR logo.

Why were you asking support for a MediaTek SoC... twice?

If I'm not mistaken the RR installer wipes \System nonetheless but it's still good practice to handle the wipes yourself. Just wiping \System, of course, is not enough to obtain a clean flash. \Data is the main junk you want to get rid of and rebuild inside the OS by restoring backups and reconfiguring settings. It's a tedious task but you get exceedingly efficient at it after a while. Flash it like a pro, bro ^_^

I should add that I'm hardly an expert myself so if I said anything wrong anyone is welcome to correct me :)

I've been out for a while (jeez, took some time catching up!) and wanted to correct one more thing:

It is correct that a lithium-ion battery sits most comfortably between 40% and 80%, which for me wouldn't be comfortable to maintain, overnight charging is the easiest solution. It is incorrect, however, that a smartphone battery trickle charges by itself. When at 100%, the charge will stop and won't restart until hours later (if Doze is doing its job, it won't restart at all). Thank you, Mashable.

Another small thing.. Since the last testbuilds, has the flashlight been set brighter? It could be my mind playing tricks but it really seems that way to me.
[ONE Android Development] Anupam Mahato:
In latest biuld(17/06/2016)..i am facing a little bit heating problem. do anyone else here with the same opinion??

---------- Post added at 07:34 PM ---------- Previous post was at 07:16 PM ----------

Any one have any good kernel suggession with this ROM.???
[ONE Android Development] kryshnakishore:
Use default kernal only
[ONE Android Development] usvimal:
Tweak LMK, I use Low in synapse. But it means you have less apps in background so tweak, play around and see what suits you
[ONE Android Development] kryshnakishore:
How to copy sim messages to phone, any 3rd party app suggestions?
[ONE Android Development] Ztones:
So I turned off doze. Battery overnight in airplane mode improved tremendously. I'm very confused. Doze is supposed to save battery right? Is this like the affordable health care that actually costs more? Please someone explain! ?
[ONE Android Development] rolarocka:
I'm using a-gapps and it's great.

Oneplus One
[ONE Android Development] mmurphmsu:
I know location issues aren't ROM related, so does anyone have a link to gripe someone out? I tried using navigation while in the DFW area this weekend and it wouldn't work at all. I have clean flashed the latest ROM with latest mini open gapps. Had I known my gps wouldn't have worked, I would have brought another phone. Lets just say I was pissed but luckily I didn't get lost.
[ONE Android Development] magnamentis:
that means that you are using interfering battery saving tools and that you set them up in an interfering manner.

doze takes care of 99% of all the wakelock issues and comes as default, hence no work and fiddling. while with helper apps like amplify, greenify, disabling receivers and services as well as tasker profiles one can get the same result ( as to power loss in idle ) but then it's a lot of work, sometimes grown over years and the error quota and mishaps quota is rather high which can take another huge effort to find and kill.
[ONE Android Development] Ztones:
I am not using any battery saving tools. No greenify, nothing... Have tasker but no profiles relating to battery.
[ONE Android Development] Blackcrx:
I found that reflashing the firmware fixed my issue with google maps constantly giving me the "searching for satellite / location" error
[ONE Android Development] magnamentis:
then it would take logs and shots to illustrate the worse battery life with doze, it's absolutely fact that doze is a huge improvement when it comes to idle drain. if that is different for you, there MUST be a reason, even though the only thing that counts is that it works for you, while if you change rom and device as well as if you have a bunch of devices like myself, that solution would appear very inconsistent.

as mentioned, good for you that you have now better battery life but your confusion is justified, only that without further input no-one can help you getting rid of that confusion because the reason for that weird behaviour can only be spotted within detailed documentation and illustration.

enjoy as long as it lasts and think about me once it's over because lucky punches like that will always end more sooner than later.
[ONE Android Development] mmurphmsu:
Can you link me to what you flashed?
[ONE Android Development] Sriven:
I know this is a very noob question but i searched online and havent found an answer that perfectly explains the following question.

How can i flash supersu to replace the su binary that comes with the ROM?

Can i Flash supersu zip directly in the recovery to replace the su binary that comes with the ROM?

or should i first somehow uninstall the binary and then flash supersu?

Also, is it different for different ROMs and devices or all ROMs and devices can be flashed with supersu the same way?
[ONE Android Development] Ztones:
Doze may be working perfectly fine off airplane mode, I can only see what's being reported by battery stats in the morning after overnight in airplane mode, and it showed doze awake all night. I'll see if it was a fluke or can be repeated.

I'm not sure it's still the case but I know for a while this Rom came with doze default off. Why is that unless it was causing some trouble?
[ONE Android Development] Sriven:
i have a question, does amplify interfere with doze because to my knowledge, doze kickes in very late compared to amplify but i think (My own Theory) that amplify gives control to doze if there are any conflicts once it sets in. and does anyone know any forum/article which gives information about different wakelocks and the interval settings for effiency.
[ONE Android Development] suaverc118:
I was wondering if the viper tile could be added in the future builds like the audio fx tile? If. It, it's not a biggie. Thanks for the awesome builds
[ONE Android Development] Timmmmaaahh!:
You don't really need to flash anything, you can though. Just download SuperSU from the Play store and let it update binaries (also optional). If you have friends hanging around, flash it so you look cooler [emoji41]
[ONE Android Development] Sriven:
Oh, hehe thanks. I was under the impression that like xposed, installing multiple su binaries wihtout removing the previous ones can cause system conflicts and may damage the ROM. I also thought since supersu binary looks different from the CM13 binary that comes with the ROM, your method wouldnt work.

Thanks tho, I am 16 and I have been doing this since i was 13, so a LOT of my friends are already highly impressed, a small flash wouldnt impress them more xD
[ONE Android Development] HaTrED_:
I don't use Synapse but rather Kernel Adiutor that's rom bundled so i'm gonna try it's different approaches although i'm a bit confused about them:

In the meantime, i've chosen "Medium" setting... let's see! :confused:
[ONE Android Development] magnamentis:
in general they do the same thing, they limit wakelocks based on time elapsed, one generally and the other while screen is off. doze kicks in within at least half an hour, with aggressive doze mode even immediately and with android N which i'm testing on my N6 it will be more or less immediately and while moving as well. ( significant move is another key parameter of doze right now )

read googles own take on doze here: https://developer.android.com/training/monitoring-device-state/doze-standby.html

finally in short the answer, yes they do interfere and can even lead to FCs and bootloops while all this is only about proper setup, both have their place and benefit, just that one has to be a bit more careful and especially on stock google some formerly safe to limit wakelocks became very unsafe and cause a bunch of FCs when set, which is why i do not recommend to use "pre-doze" settings for amplify.
[ONE Android Development] Sriven:
So in the end, what do you recommend?

Keep amplify or uninstall it. I know it depends on the user but is it worth the battery life it provides?
[ONE Android Development] magnamentis:
deleted, was kind of redundant due to an error :)
[ONE Android Development] Sriven:
Lol your previous reply is still here
[ONE Android Development] magnamentis:
oh, then it went through while the indicator was still showing an upload, i shall delete the second one though, thanks for letting me know because i rarely go back :)
[ONE Android Development] Sriven:
Can you please tell me if amplify is worth the little battery life it provides?
[ONE Android Development] der_fahrer:
Does anyone has problems with phonecall? I cant hear any signal and also the other Person. When someone calls me i cant hear him and he me. Also phoneapp is lagging then