yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] kingsathurthi:
Guys im new to xda, actually i tried to reply this thread but cant able to reply bcz xda says u have no permission to reply the development thread then i went to Q&A thread and replied 10 post now im happy to post in this thread, I like RR rom very much i decided to flash RR MM6.0.1 before that i want to know about BATTERY LIFE in this MM ROM :) waiting for reply guys....

thnks in advance :) :)
[ONE Android Development] zulu657:
So, in response to a reply to my previous post about the proximity sensor, I downloaded and installed the newest update using TugaPower TWRP 3.0.2.3. Strangely, it would not let me access my USB-OTG flash drive. Never had that before. So I had to download and install from the phone as no matter what method I try, I cannot connect this phone to my computer. My other OPO works fine, just something with this one.

Still no proximity sensor using C6-00241 modem. Apart from these oddities, RR is still the best. Major props to varund7726 for all of his hard work.
[ONE Android Development] Nick James:
I struggled with GPS "issues" for a long time and I too thought it was just the dev's preference (better battery vs. better location services) however, another member suggested that install an application called "GPS Test" and "clear" the AGPS. After I did this, my GPS started working again without any problems. I choose to also "update" AGPS.

I was reluctant to install any GPS application that might "fix" something that I didnt think was broken. Fact of the matter though was my GPS was not working correctly and I'm not sure what caused this error to begin with.

With all that said, I haven't had any problems with my GPS- you should totally give this a shot, you've got nothing to lose!!

Good luck!! Cheers!
[ONE Android Development] sm753:
Thanks for the suggestion. Maybe my post wasn't clear - sorry if that's the case. GPS based location *works fine* - as I just used Waze to navigate around traffic to work this morning. It's the "network" location based location where Android/Google uses...cell towers I guess? Or something to triangulate your approximate location that isn't working for me.

Specifically for Tasker, LTE signal at my office sucks - and for some reason my phone refuses to automatically drop down to 3G even though I typically only get 1 bar or "no" bars. So up/down speeds are horrible, things time out, etc. So I made a location based profile to automatically switch to 3G when I'm roughly within 1 kilometer of my office, and back on when I leave the office - it also automatically puts my phone on vibrate, etc. Similarly for home, I have it set to turn wifi on, and ringer on, etc when I'm within 1 km of home. I use network location instead of GPS (Tasker allows both) since it saves battery power (Tasker won't have to keep trying to poll my GPS position). I also like and make use of Google Now's location based cards and pop ups - for example I glance at it every morning to check traffic to work and traffic home in the evenings.

Since I switched to this ROM, Tasker is no longer able to get my network location, initially I assumed it had to do with something I blocked in Amplify, or some power saving thing - until I started reading some of this thread. I assume it's something to do with what the dev did to give us such fantastic battery life...as I know location services is one of the biggest "idle" battery drains.

Anyway these aren't really "deal breakers" or whatever - just more "quality of life" things that I've gotten accustomed to leveraging our phone's capabilities.
[ONE Android Development] dequint:
I was wondering if it would give any errors if I'd flash the Capps 13 onto it?
[ONE Android Development] matter99:
You should be fine, it's CM 13 after all
[ONE Android Development] Boss@xda:
Can't see this option [emoji21]
[ONE Android Development] nava88:
Hi, the last 5.7.2 version works like a charm but I would suggest a change or improvement for the ROM, the contacts, calculator, phone , messaging, camera, mail, webkit, etc may can switched with the google apps versions that are updated from the google play store and quite similar to the CM version of the apps.

For now I uninstall or disable the stock app and install the google versions but in my opinion the google versions are more updated that the CM13 apps.

Thanks for all your Job
[ONE Android Development] Sakti51:
Whenever I raise or down the volume, volume panel stays there longer than previous build

Any idea?
[ONE Android Development] Sukarn:
Not possible.

http://wiki.rootzwiki.com/Google_Apps#Licensing
[ONE Android Development] Micalus:
same problem here. when i pull down QS or open settings it lags like hell and gets even worse, when poweramp + audiofx/v4a is and the settings take much longer to open from QS settings button than before.

using stock kernel or boeffla kernel, with or without v4a or any other mod. not a problem with 20160719 build here as well.

Cheers

Mike
[ONE Android Development] geokilla:
What Gapps are people using now that Slim Gapps are dead?
[ONE Android Development] Nb07:
Don't because per app theming option is inside theme engine app for Capps theme engine and in RR it is through qs tile....so it may clash and give a problem.
[ONE Android Development] mustang_ssc:
Opengapps: http://opengapps.org
[ONE Android Development] danielferratti:
Use OPEN GAPPS FULL It will flash over CM apps things like: Clock, Calendar, Camera, Launcher Etc.
[ONE Android Development] varund7726:
Settings>sound>volume dialog timeout
[ONE Android Development] varund7726:
Start clean flashing then
[ONE Android Development] varund7726:
Why are you removing '/cne service? It's important for data .
[ONE Android Development] laura almeida:
Request: could you please remove inbuilt SuperSU ?

I would like to switch to --> http://xdaforums.com/android/software/mod-magisk-v1-universal-systemless-t3432382
[ONE Android Development] Sukarn:
Some built-in features require root, so that might not be possible in the near future.
[ONE Android Development] kwapa1:
[MENTION=4817632]varund7726[/MENTION]

I am having crashes at making call using bluetooth connection in the car, please see attached catlog file. It is a soft reboot I think, no 1+1 logo, just the Resurrection Remix start up animation. It is happening always, when the screen if off (phone in the pocket) & making phone call using touch screen of the car. Receiving calls, making them from the phone via bluetooth or using car touchscreen with screen on works 100% time just fine. Crashes always at screen off.

Clean flash of the latest release (07/31), no xposed, no busybox installed. Actually I have this problem in every RR release. No such problem when I was on RR Lollipop. Could you please have a look, what went wrong?

Last, but not least, (as I mentioned already before), awesome ROM, thanks for your effort! :good:
[ONE Android Development] nava88:
I will try it! Thanks!

I try with the stock option but it dont fit on the system partition so i use the full but the contacts and the dialer apk still using the AOSP version.

Thanks
[ONE Android Development] Micalus:
I did and always do a clean flash for every new version number, still UI is laggy. when pulling down QS, opening settings or scrolling down settings. and multiple other tasks takes longer or lagging.

Cheers

Mike
[ONE Android Development] nightshade29:
Very good work. I am very satisfied with this ROM. There are two things that are bugging around though, at least I cannot find a way to change it. Maybe someone could help if there is a solution.

Firstly, sometimes when I pick up the phone, the flashlight is on. The option to activate the flashlight using the power button is off, but it happens to switch it on randomly while picking up the phone.

Secondly, I do not have a "battery low" notification. I don't know why. Neither the LED, nor the notification are telling me that the battery percentage is below 15%. I cannot find other settings for this than these shown in the screenshots.

But besides if this this is a highly customizable ROM, which runs very smoothly.
[ONE Android Development] Sakti51:
Thanks for the reply

Ive tried that, it only affect once then after that it becomes longer again
[ONE Android Development] MEyo94:
Need help

hi, just installed your Rom and it is working great. But I got one huge problem, which occured also in annother ROM but got fixed with an CM update. So the bug is, when I open Snapchat, the Camera is overlapping the navigation bar (software keys) and

streching

the camera picture. This only occurs in Snapchat as far as I know and it got fixed by CM in a Version. So my question is, do you have the latest CM Version in your Rom or could you please update it, because in the newer Version of CM this error is fixed... Or can you give me a workaround for this error.

For better understanding I have an attachment and as you can see, the Picture is Streched and the Snapchat button in the bottom left and right are not able to reach.

A short offtopic question, how do you get those Multi-Line-Date for the Status bar, and overall the design like in this picutre. I found this from a guy on this thread, who posted it. Unfortunelty this guy is not active in the forum anymore, so there is no sense to contact him. (see attachment)

[IMG="Multi Line Date"]https://img.xda-cdn.com/IxnIN1ck38vkk0p2Dd1m0gFH8pc=/http%3A%2F%2Fuploads.tapatalk-cdn.com%2F20160702%2F0916fa5bc804af372dbfc6cdb0b785ea.jpg[/IMG]

Thank you for efforts and help :)

Best regards
[ONE Android Development] nava88:
The stock open gapps dont fit into the system partition, so finally I uninstall the aosp apks manually and install the google apks from the play store.

In other order of things I detect a little bit error. The kernel auditor was updates from play store and now the settings/kernel settings make a FC settings

Enviado desde mi A0001 mediante Tapatalk
[ONE Android Development] effry:
Can you share how you reached that huge SOT? mine stops at 3h and half
[ONE Android Development] suaverc118:
What SOT?
[ONE Android Development] MEyo94:
this is not my phone, i got this picture out of this thread somewhere at page ~400 or so. Dont know anymore.
[ONE Android Development] kaneelias:
Mate I appreciate your work on this rom but you really need to stop getting so defensive when someone says anything about it that you don't agree with

I am happy being on the June 19th release and the only reason I post on this forum is to educate others with my experience and a solution to my problem in case someone else is experiencing the same.

Thanks again for your work
[ONE Android Development] CobraCommander:
Its a rule of thumb to clean flash if you're having issues with the Rom.

Moreover, you didn't provide logs or any info(using xposed or any mods) for that matter.

This really pi$$es of developers & users like me for whom its been working quiet well.
[ONE Android Development] kaneelias:
Mate, this has been working quite well for me as well. A forum is a knowledge base and that is what I am providing when I post, knowledge of my experience. If someone has a similar problem to that of what I was having then yes, do a clean flash by all means but if you do not want to, there is an alternative ie rolling back and I can confirm that that has worked for me.

Moreover, if I was using any mods I would have mentioned them, if not mentioned then I am on stock.

Furthermore, there has already been a report of the same lag by a user after a clean flash. Just because some people have issues that you don't does not mean we are idiots or inferior to those that always do a clean flash and have no issues
[ONE Android Development] CobraCommander:
Frankly that post of yours provided zero knowledge of your issue.

Provide logs for your issues rather than arguing with others.
[ONE Android Development] kaneelias:
I am not trying to argue with anyone.

My post provided the knowledge that I experienced a problem and I resolved said problem by rolling back to a previous build. That information also seemed to help another user.

I did not generate any logs because I need my phone to be usable, so I rolled back straight away.

Thanks for the feedback though. I will try and be more detailed in my posts from now on.
[ONE Android Development] DE52:
Have you enabled it here as well? I always get a notification when my battery hits 15% and also get the flashing LED as per the battery light setting as well
[ONE Android Development] varund7726:
i dont see any bluetooth error in the log
[ONE Android Development] sahor:
How can I generate a log from my phone when I am having any issue?

Enviado desde mi A0001 mediante Tapatalk
[ONE Android Development] kwapa1:
Install Catlog app for example.

Wysłane z mojego A0001 przy użyciu Tapatalka
[ONE Android Development] scoredance:
Hai. Someone can help me please? "Unfortunately, setting has stopped" is happening to me when i want to go to clock customizations. What's the problem? Thanks
[ONE Android Development] nightshade29:
Yes I did enable it in battery settings. No battery low notification / flashing LED though...
[ONE Android Development] Prashanthme:
First try clearing cache and data of settings and clock . Then it should work fine. If it doesn't re flash. Then also if it doesn't work then clean flash...
[ONE Android Development] scoredance:
thanks mate!
[ONE Android Development] Reed-Sternberg:
I don't usually get into such discussions, but I see this point very often on xda, so this is my 2 cents:

"Do a clean flash every time you have a bug, to see if it's fixed" is a clear example of 'argument from ignorance'. When we don't even know what causes what, such blind and non-evidence-based recommendations is a poor attempt not to look into the real cause. The better and more honest answer to his question is "I don't know" or "I don't have time to investigate it" or "provide more info before asking for help".

A good example of why this clean flash frenzy is mostly a myth, is any phone which receives OTA updates from the OEM, even between major OS updates, and never needs to be clean-flashed.
[ONE Android Development] littlemegaman:
Dial pad is not centered. It bugs me.
[ONE Android Development] littlemegaman:
Dial pad is not centered ????
[ONE Android Development] littlemegaman:
DialPad is not centered. Is this common with everyone else??
[ONE Android Development] House_Maniac:
Customs rom and oem updates are two different things.
[ONE Android Development] Sander9847:
It was enough to say it once!

Also i don't have that problem so it's probably a theme issue.
[ONE Android Development] MEyo94:
mine is also not centered, and I have no theme installed.
[ONE Android Development] nightshade29:
Where can I report issues?

I flashed clean today, still no notification LED / notification on low battery. It should work though, I switched it all on. Logcat does not say anything meaningful...
[ONE Android Development] CobraCommander:
Its not a myth its a fact. 9 out of 10 times clean flash does the trick, not saying cuz i read it on xda but from my own experience.

This rom isnt oem, there's a difference. Look it up.

You guys a clearly new here so remember this, if you have issues in future 1. Do a backup & clean flash. 2. If issue persists provide a logcat.

If you can't be bothered to provide either don't post your "knowledge base" & "2 cents" without researching about stuff being discussed.

We're done here.
[ONE Android Development] nightshade29:
Additionaly, when the battery is full, the led is. BLUE and not green as set. This surely is an important information. Below are my settings...
[ONE Android Development] Sakti51:
smooth experience on latest build!

thank you, varun!
[ONE Android Development] dharmil007:
Guys after updating to the latest version. I am getting very bad battery life. Whats the problem ? Please help me

Previously I used to get like 12-13hrs of battery life.

90% was used within 5.3 hours.

The three main causes :

1. CyanogenMod System

2. Basic Daydream

3. Kernel (Android OS)
[ONE Android Development] kaneelias:
Well said, the clean flash argument is the same as "have you tried turning it off and on again". Unfortunately it seems on this forum if you have a problem that no one else does, you are a beginner according to some people regardless of your experience. That is really disappointing, some people need to learn the definition of a forum.

Also, I am chiming in on the random flash light turning on issue as well. Still happening after a clean flash
[ONE Android Development] fradbari:
Anyone still have problems with miband bt sync?!

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Android Development] Reed-Sternberg:
Don't bother getting into arguments with folks, there are a lot of 12 yo roosters with a phone these days who try to mark a territory on the internet! You can't teach them anything until they grow up.

Be appreciative of the developer, follow his recommendations and address your questions to him directly, and ignore the rest.
[ONE Android Development] LPW00:
Which theme and font do u use?

Sorry for OT..
[ONE Android Development] Sukarn:
There's something that you two are clearly missing here:

Manufacturer ROMs get tested repeatedly for compatibility and data migration from old data to new data. System settings, data of system apps - these things are also user data.

Custom ROMs don't have this level of testing before each release, and cannot be expected to have this. It's a hobbyist scene. It's not a job where they're being paid to make changes to the code and then on top of that ensure that the new changes to the code either convert old user data to compatible data or to make sure that user data generated on old builds plays well with new features and changes.

Do not mislead others by saying clean flashing is a myth. It is not a myth. It is a necessity of custom ROMs, unless your custom ROM makes the most minor of changes from build to build.

If you've been dirty flashing from build to build, most likely you won't face any issue, but there's always the possibility that you could face issues which are created when some part of your user data is incompatible with how the ROM handles something in a new build. Something as simple as screen timeout value in your settings can cause crashes when the new build has different timeout options that don't include your old setting as one of them. Most of the times you wouldn't have any issue because you didn't tinker with that one part of the OS in that one particular way which got heavily changed in a new build.

The respectable way of reporting a bug is to:

- clean flash the latest build and see whether the problem is still there. If it isn't, then it wasn't the ROM's fault, it was caused by something you did, or it was caused by an old build (or data generated by an old build) but got fixed in the new build.

- get a full log containing the bug

These steps are necessary to save the time of these volunteer developers who only do this as a hobby, not a job. You did not buy a quality assured product. You were not promised painless bug free updates. RR is not a manufacturer ROM, and RR is not guaranteed to work correctly after a dirty flash.

You're free to dirty flash all you want, but stop misleading new users by telling them clean flashing is useless. Clean flashing is not useless. Dirty flashes are unsupported. Dirty flashes are at user-risk.

/end rant of dev of unofficial RR OTA app
[ONE Android Development] Pablete197:
i have recently flash this awesome rom, but i can't find the option that allows you to open some notifications in small windows, instead of opening the full app. Can someone tell what's its name and where i can find it? (if it still exists)

Thanks, sorry for my english.
[ONE Android Development] LPW00:
Long press and click on that floating window icon that shows up, should do the trick;)
[ONE Android Development] CobraCommander:
Don't waste your time mate. People like these is why xda gets bad rep.

I've been on xda for a while and seen many good threads been closed by developers because people would only complain without any proof.

Mad respect to OP for tolerating imbeciles. :good:
[ONE Android Development] nightshade29:
Disabling the V-Gestsure helps. At least for me, it doesn't go on randomly now.
[ONE Android Development] maxed4901:
LOVELY!! WELL EXPLAINED!!! Salute you sir! I think OP says to report bugs or issues with logs... having mentioned so, if a user simply drops to floor wailing at the ocean breeze, my easiest and best response would be "clean flash" lol. expecting the dev to find out from another device in another country to find bugs.. imbeciles it is... Talk to my hand.- Smelly and hairy..:angel:
[ONE Android Development] jdogzilla:
Hi all, I'm on v5.7.2 with Boeffla kernel. I'm having a strange GPS problem. I use Runtastic with GPS on to track my morning runs. Over the past 2 weeks at least (if not more), I lose GPS signal after 5-10min of using the app, and then can no longer track my pace and coordinates on the app. It seems to turn on if I turn the screen back on, but will again randomly go off later. Any suggestions on how to diagnose/solve this?
[ONE Android Development] Sukarn:
Settings > About > About Resurrection > The Drill

---------- Post added at 09:37 PM ---------- Previous post was at 09:27 PM ----------

I don't use that app, so I don't have first-hang experience with it.

Perhaps you have Greenify with aggressive doze, or some other app that triggers doze.

Try add on that app to doze whitelist which can be found at Settings > Apps > gear icon at top right > battery optimization.
[ONE Android Development] Pablete197:
anyway of doing this by just long pressing the notification?
[ONE Android Development] LPW00:
Nope
[ONE Android Development] varund7726:
Update 5.7.3

Android 6.0.1_r53->6.0.1_r61

Frameworks: Halo Color

Frameworks: HALO

Halo: Add option to Enable/Disable Halo Button in Header

SysUI: Fix Layouts of Halo Button within Expanded Statusbar

StatusbarHeader: Fix Headsup and Halo Button Animations

Halo: Reverse message bubble bg and text colors

Blur: Minor fixes

Blur: Fix Arithmetic Exception when Radius and Scale are set to 0

Blur: Major update

SystemUI: BatteryBar: Gradient color

SystemUI: Display bluetooth battery status when available

Implement Blur Statusbar personalization options

Update halo and heads up qs button

Configurable Notifications transparency

Configurable Smartbar button transparency

Fix up header button icon, position and animation

Network Traffic and Custom Logos: Fix Inverted SB icon tint when color is white

Option to set custom scrolling values

Statusbar: Gracefully adapt 3Minit Battery hook for AOSP

Add 3Minit battery mod

Option to let ADB always notify

Custom Toast Color Options

Fix FC on Seekbar in VOlume dialog and power menu Stroke & opacity

SystemUI: Add vector support to SlimRecents

Update Slim Recent App Sidebar

mountservice: Don't nuke all volumes when decrypting (Speeds up bootime by 30 % for encrypted devices)

SysUI: Add theme manager permission

Themes: Add permission to themes protected broadcasts

Instant reboot action trigger

MobileNetworkSettings: Check CarrierConfig on isWorldMode

EditPhoneNumberPreference: Prevent empty text from being set

Dynamically tell the user which vendor image is needed

Show a more descriptive message when vendor.img is out of date

Update Kernel Adiutor apk

make overlay permission check configurable

fw: enforce android.permission.PREVENT_SYSTEM_KEYS in system server

SysUI: Add RecreateStatusbar to Quick Settings Blur

SysUI: Make sure new Blur Features dont Conflict with Transparency Items

bootanimation: add multithreaded decode

framework: don't allow assist activities while not provisioned

Services: Fix a small Derp from instant reboot action

sepolicy: Let the IO prefetcher look at sdcardfs

sepolicy: Put theme service in its own context

sepolicy: More IOP rules

sepolicy: Fix MTP for sdcardfs

Translation Updates

All updates from CM
[ONE Android Development] Naresh Rawat:
Thank u varud.