yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] Anghirrim:
Thanks for your answer.

I have been using Candy in the past (MM version) and flashed the early builds of your 7 version.

But let's say I am new there as I haven't flashed Candy for a long time and never used the Substratum app. :p

Magisk is activated and prompts for root rights when needed (see screenshot).

I don't know what I am missing there...
[ONE Original Android Development] eiwarmer:
After applying a theme sometimes it freezes. For me a reboot fixes that
[ONE Original Android Development] NoSpamDan:
I looked at the DNA Dark Theme, and I would suggest using something more simple until you know everything works. Try using Default Dark or ModernUI or Divinity for starters. Some themes, like my Swift Dark, have a drop down that appears in Substratum in which you must select your Android/ROM version. CandyRoms is currently "v7_1_OMS" in Swift Dark...

Substratum rootless - does not require root, just some Android permissions.

If you had Subs installed before this update, go to the Subs app and clear the data for it. No clue what else could be affecting you as it works fine here. :confused:
[ONE Original Android Development] NoSpamDan:
Good news... (hopefully)

[MENTION=3123828]gaja22[/MENTION], I don't often fulfill user requests, but I do like the triple location QS toggle feature. Thanks for suggesting it.

Added triple location tile, and fixed wifi connection bug (hopefully).

Candy-bacon-7.1.1.Beta.v3.0-OFFICIAL-20170328-2041.zip

Can be dirty flashed on the last version(s). Please report back if the wifi bug is fixed for those affected. Thanks.

Enjoy!
[ONE Original Android Development] Anghirrim:
Yep that was my goal. Thanks for your confirmation.

- Step 1: read a tutorial on how to use substratum (we never know, I might miss something stupid)

- Step 2: try with a theme known to work

Side note, I choose DNA Dark just to have a try after having read the XDA article about it. This is the first time I try Sub.

Edit: Tried with more simpler themes, it works... Thanks for the help!
[ONE Original Android Development] haikalzarith:
Hello I wanna ask how to enter developer mode in this ROM because I can,t enter developer mode
[ONE Original Android Development] NoSpamDan:
Noob-friendly response is: go into Settings > About phone, and tap on the Build number field 7 times...
[ONE Original Android Development] gaja22:
Jackpot, works very fine !!! Thank you !!!
[ONE Original Android Development] NoSpamDan:
Which, the tile or the wifi fix (or both)?
[ONE Original Android Development] gaja22:
I tried the tile. I don't have any issue with Wi-Fi since the previous build.
[ONE Original Android Development] suryachandranr:
Thanks [MENTION=4435460]NoSpamDan[/MENTION] for the Candy7 nightlies :):)
[ONE Original Android Development] 69gm:
Did anyone else lose Ok Google detection? It was fine all the way up to the last 2 builds.

I'm leaning toward Google making some sort of change but wanted to ask just in case.

Nah, it's always Google's fault! :laugh:
[ONE Original Android Development] NoSpamDan:
What do we have for bugs, folks? Not feature requests, but

bugs

...
[ONE Original Android Development] ziepicwaffle:
This is kinda in between. In the earlier builds, there were a few custom tiles that disappeared suddenly after a build. Sorry for not having all the details, I hope you know what I'm talking about though.
[ONE Original Android Development] 69gm:
I just tried another Rom and Okay Google detection worked.

Any thoughts or any sort of log I can send?

It worked fine before...
[ONE Original Android Development] kennymc666:
Hi there.

idk if this is a bug but developers options disappeared for me in one of the last builds. tapping build version doesnt make it appear again. still another question: does this ROM support F2FS? or do all nougat ROMs support it?

greetz

Sent from my One
[ONE Original Android Development] reinipic:
Hello, I think I have a problem too.

Latest Rom makes a few problems for me:

No developer options, no activation possible by tapping build number.After that I wiped complete system, factory reset and made a clean install with latest build and gapps.

After clean flash the developer options were enabled by default, a file manager app was included again in the rom and former Cyanogen ringtones and alarms were here again!? :confused:

Please note, thats not a critique, I am only just a little confused whats happend. Could anyone enlight me? :rolleyes:

Greets, reinipic
[ONE Original Android Development] tonyboy3:
Awsome rom! Keep going with your amazing work! ;)

ps: I can see developer otions in the latest build
[ONE Original Android Development] NoSpamDan:
A team member made a change to enable Developer options by default, I believe. You may only realize this on clean flashes going forward.
[ONE Original Android Development] NoSpamDan:
Same GApps package? Not sure off hand. A logcat might show something...
[ONE Original Android Development] kennymc666:
btw: thanx [MENTION=4435460]NoSpamDan[/MENTION] that you keep good old OPO alive with Candy7 and SlimROM;) two awesome ROMs! nightlies but already that stable that they can be used as daily drivers! i have to switch all the time (thanx to MultiROM) because i cant decide which one is better ;) thanx for your work!

Sent from my One
[ONE Original Android Development] tosonny:
Has this rom battery bar?
[ONE Original Android Development] 69gm:
Yeah best guess, something went wrong with either Google or Gapps. Originally I didn't do anything though. All I did was dirty flash your updates. I believe my problems started about 2 builds ago? Not sure (since your recent builds have been coming "Fast & Furious" ;)).

And before you ask, yes I tried wiping the data from Google app and I even flashed the most recent Opengapps (which may or may not be the problem as well).

Attached is the log. The way I made this was the following:

Opened CatLog and started recording

Went to homescreen and said "Okay Google". Nothing happened.

Manually started Google Assistant to confirm it was working, including getting weather update.

While on Google Assistant said, "Okay Google". Nothing again.

Went back into CatLog and saved log.

This is what I am now presenting. Not sure if it will be helpful but hoping...

Thanks!

https://www.dropbox.com/s/7drf8kqr7m5h5c5/logcat_and_device_info.zip?dl=0
[ONE Original Android Development] NoSpamDan:
Not sure, but this looks interesting...

03-30 07:35:24.025 E/SearchServiceClient( 4080): SearchServiceClient disposed and cannot be reused.
03-30 07:35:24.026 I/AttachedClient( 4080): Adding client event 121 to pending list.
03-30 07:35:24.032 I/OptInState( 4080): There is a new client and it does not support opt-in. Dropping request.
03-30 07:35:24.044 I/MicroDetectionState( 4080): Keep running hotword in interactor process
03-30 07:35:24.068 V/AssistManager( 2902): Voice closed
[ONE Original Android Development] 69gm:
That DOES look interesting.

I am now DL'ing Cosmic ROM just to test with Opengapps. Maybe if that fails, the next step is to try different gapps. I'll keep you posted.

UPDATE: Okay Google detection working fine on Cosmic ROM with Opengapps.

---------- Post added at 10:38 AM ---------- Previous post was at 10:30 AM ----------

@NoSpamDan, sorry one other thing I noticed is that when I'm restoring my phone clean flashing a new ROM, everytime I used to restore, it would give me a list of last used apps and it would, of course, say "A0001" (along with other A0001 saved app packages). Now the saved app package it thinks I'm using (so it's like it thinks that's what I'm using) says "Pixel XL". I've NEVER seen that before and I've been a flashoholic for many years now.

Does that shed any light on anything? I did look into the build.prop and it does say A0001...not Pixel XL.

I'm so confused...:confused:
[ONE Original Android Development] 69gm:
One last test I did just now...

I did a clean flash for Candy7 as a test with Opengapps. Still no "Okay Google" detection. This seems more and more likely it's ROM related since it worked fine in CosmicROM.

If you'd like me to do more testing, LMK.

Thank you [MENTION=4435460]NoSpamDan[/MENTION] for looking into this. It seems minor, but it was working fine before and seems like a step backwards...hopefully I helped find a bug!...you know...since you asked. LOL!

---------- Post added at 01:06 PM ---------- Previous post was at 12:58 PM ----------

Sorry one last post...for now...LOL!

Here is what I was talking about for the apps on fresh installs. Here is a screenshot I took when doing my Candy7 fresh install. Notice the Pixel XL?
[ONE Original Android Development] NoSpamDan:
Yes I see that, and think we reverted a commit today that was responsible for that. So the next build should have that fixed... I hope.
[ONE Original Android Development] lukacsp:
Im using your rom with great satisfaction. I installed clean rom with pico opengapps, and updated until the mar 18 build. I noticed that Google Photos stopped backup my camera images after mar 20 (last update?). The newer camera images isnt show up in the app, only edited images, camera videos and screenshots Any clue? Thanks
[ONE Original Android Development] NoSpamDan:
Google Photos is not included with the ROM. That's a GApps function. Maybe they changed the photos location on you, or our change to SnapDragonGallery did... You'll likely have to tell Google Photos what to back up, or at least confirm/verify it.
[ONE Original Android Development] NoSpamDan:
Updated magisk to v12.0, should have "OK Google" and weird PixelXL device naming issue fixed, and more. Please let me know.

Candy-bacon-7.1.1.Beta.v3.1-OFFICIAL-20170331-0729.zip

Enjoy!
[ONE Original Android Development] kennymc666:
thanx Dan for the update. developers options are back ;)

Sent from my One
[ONE Original Android Development] 69gm:
At first when I tried this update, "Ok Google" still didn't work. Then I decided to retrain my voice. Eureka! That did it!

Thanks for looking into this so quickly!

Those who had the same problems, try retraining your voice or clearing data from Google.
[ONE Original Android Development] NoSpamDan:
Yes, and I think it's also why my build was inexplicably in SELinux permissive...
[ONE Original Android Development] NoSpamDan:
Did you sort this out? The more I think about it, the more I think the PixelXL features commit that we recently reverted could have caused it.

That, or the time and date were off...
[ONE Original Android Development] tosonny:
Hi folks, I just have read the whole thread ...but still have some questions because I am definitely no specialist. So please don´t hit me if I ask something stupid. As you can see in my signature I have tried different roms. Right now I am on Asoip for a quite simple reason: I love that battery bar. But I am always interested in new roms (unfortunately SultanXD haven´t made a N-rom yet), so I have tried out different ones. May I ask:

1) What are the main differences between candy and for example Asoip (except of a dev who is very dedicated what is very very cool)?

2) Has this rom battery bar (couldn´t find something about that)?
[ONE Original Android Development] NoSpamDan:
I have never tried asoip, and there's no battery bar here, but there is an app called Team Battery Bar, if you need to have that... :)
[ONE Original Android Development] 69gm:
Lots of random reboots. Weird too... I don't have any last_kmsg...
[ONE Original Android Development] eiwarmer:
Dirty flash or clean flash? Substratum theme enabled and which one? Stock kernel? Any other mods? Please elaborate...
[ONE Original Android Development] wingedpanther:
no issues here
[ONE Original Android Development] Digo69:
I ever do dirty flash and no problems.

For now it's just fine.

Do a clean flash to see.
[ONE Original Android Development] lukacsp:
Cant figure it out. Finally today i removed Google Photos and then reinstalled it. All the previously missing images shown in the app, will see if its "repaired" or dont.
[ONE Original Android Development] NoSpamDan:
I can't confirm that, as I've had zero random reboots... But then again, I usually clean flash for accurate test results.

You will soon be able to hold the Up Volume button at start up to disable all OMS overlays... next build hopefully.
[ONE Original Android Development] kennymc666:
same here. not a single random reboot since im on this ROM. usually i dirty flash updates.

Sent from my One
[ONE Original Android Development] NoSpamDan:
What kind of reboots, showing kernel splash OnePlus logo, or restarting boot animation?

I would suspect theme or root activity, but could also be an app. If you are seeing the kernel splash, then you can try the Bootlog Uptime or SysLog apps. If you choose Bootlog Uptime, run it manually at least once to accept the root prompt, and set it up to automatically dump the last_kmsg log.

You can also grab last_kmsg manually:

Open an adb shell or terminal window after the RR and type:

cat /proc/last_kmsg > /sdcard/last_kmsg.txt
[ONE Original Android Development] 69gm:
Hi Dan and others,

Yes usually the ROMs seems pretty stable. I probably wouldn't even have noticed it except I had my phone mounted in my car with the GPS running. This is not unusual and I never noticed anything before. It was just yesterday that suddenly my phone would warm boot (go into boot animation) and it did so 3 times. Twice almost right after each other.

Dan, there is no last_kmsg on my phone. Otherwise that's what I would've sent. That's what I was hoping for too so that if it was some kernel panic, it would be there.

For those that say your phone is stable, I don't doubt you...however I seriously doubt you keep your eyes on it 24/7, so your phone could've rebooted without your knowledge. Like I said, if it wasn't for the fact that my phone was mounted in my car, I probably wouldn't have noticed it either. It's not like it happens in any consistent manner. That's what's weird about it.

Everything is stock except Substratum. I AM running "Default Dark" but haven't had problems before. Yes it is dirty flashed but I don't believe that to be the problem.

For now, I will keep everything AS IS and see if it happens again. Could've been just some weird fluke. IF it happens again, I am hoping a last_kmsg would be generated so I can send it. At the very least, I will remove all themes and see.

Thanks again for keeping up with this ROM. This is definitely an anomaly. Sorry I don't have much more information than I've already given. But because it DID happen, I thought I should report it, especially if anybody else was experiencing the same. If not, it looks like an isolated incident.

At any rate, I am definitely enjoying this ROM very much and appreciate the support you always give to it. :good:
[ONE Original Android Development] NoSpamDan:
The Bootlog Uptime app will log the reboots for you. Just run it through the log dump once...

Something I don't understand is why you don't have ANY /proc/last_kmsg. It is there even from last reboot on my device.

Are you using MultiROM, and if so, is Candy7 the primary ROM or a secondary?
[ONE Original Android Development] 69gm:
IC...Hmm, but what if my phone never reboots again?

Yeah I don't understand why no last_kmsg either. Believe me, I know...You want me to manually reboot and see if one gets generated? I might just for S&Gs...

No MultiROM or anything. Aside from Substratum Default Dark, everything is stock.

Meh, I wouldn't stress too much on it for now. AFAIK, it's an isolated incident. If it happens again noticeably, I'll report, hopefully with a last_kmsg....

Thanks Dan!!!

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

Just did a reboot and now I do have a last_kmsg. Don't know why I didn't before. More weirdness.

Like I said, no worries for now. I'll keep an eye on it. Hoping for the best.
[ONE Original Android Development] lukacsp:
Ok, after some days i can say the bug (new camera images not visible in Google Photos app) is still there. Can someone try it? or is it only bothers me that image backup is broken?
[ONE Original Android Development] tonyboy3:
Until now I have had 2 random reboots.

Slim launcher crashes every time I install a new app.
[ONE Original Android Development] Silverview:
Google Photos app is working as expected for me. New images appear and are backed up using both stock camera and Bacon camera. I am using March 28 build. Dirty updated the last two or three builds.
[ONE Original Android Development] gaja22:
Hello [MENTION=4435460]NoSpamDan[/MENTION] !

I've got a new mission for you to make your ROM better ! Could you add a message to confirm when we want to shut down phone, please ? It's possible on RR and Hyper Unicorns.

Thank you !
[ONE Original Android Development] NoSpamDan:
AdAway, One-handed mode, Snap updates, updated Magisk, OMS updates, may have Slim launcher FC fixed, more...

Candy-bacon-7.1.1.Beta.v3.2-OFFICIAL-20170403-1751.zip

Enjoy!
[ONE Original Android Development] lukacsp:
Thank you! I updated my phone to this, and my problem still exists. Photos i made since monday didnt show up :(

The only half solution is to delete app data, but it isnt fixing the visibility of images i will take.
[ONE Original Android Development] NoSpamDan:
Can you copy these image onto your PC and review the EXIF data to see when the system thought they were captured/created/modified/etc?

I am curious if they have some ancient date like 1972 or something...
[ONE Original Android Development] NeGriTa79:
[MENTION=4435460]NoSpamDan[/MENTION] I noticed that the BT machine when I get calls ... even though I set to show the first name and surname. when I receive calls I show me the surname, and I do not longer displays contact photos. Even on other rom I noticed this, but until version of 31/03 was fine then no more. How can I fix? Issue of the new version of Android?

Ps.: Excuse my English, but I'm using a translator!
[ONE Original Android Development] NoSpamDan:
I kind of understand you. What dialer app are you using, the native one, or Google's dialer. Also, you might check dialer and contact permissions, as well as the sync options in Settings > Accounts.
[ONE Original Android Development] lukacsp:
hi, i found this odd entry:

DateTimeDigitized: 2002:12:08 12:00:00

however,

DateTimeOriginal: 2017:04:05 17:02:50

was correct.
[ONE Original Android Development] NoSpamDan:
I wonder if Google Photos tried to beautify or optimize the images and somehow changed that Digitized date... indeed odd.
[ONE Original Android Development] NeGriTa79:
Dialer native...

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] NoSpamDan:
Get a short logcat of this happening and post it please.
[ONE Original Android Development] lukacsp:
I noticed one error(?) with this rom. I paired my car with the phone. I listening net streams with xiialive app via bt. With the previous rom from march when i pressed play button on my car receiver, xiialive started and the last entry from my playlist played automatically. Now the app isnt started at all. Do i need to re-apply permissions or something? Thanks!
[ONE Original Android Development] eiwarmer:
The drag selection on the area you want to screenshot doesn't seem to work. Maybe I'm doing something wrong?
[ONE Original Android Development] NoSpamDan:
Long press the volume down and power buttons together and hold them until the screen goes dark. Then starting at the upper right corner of the area that you like to capture drag to the lower left corner and let go...

What are you specifically havinga problem with?
[ONE Original Android Development] eiwarmer:
That seems to do the trick, but if you add the screenshot shortcut to the power menu and try it from there, it doesn't work. It also works if you add the screenshot shortcut as a QS tile so I just found out. So this isn't a deal breaker.
[ONE Original Android Development] bwais:
I recently fixed my device after not using it for over 6 months. This rom is amazing! I get awesome battery life, normally over 25 hours.

I just have one issue, but i am not sure if it could be hardware related? Sometimes when I press the paper button to turn the display on the hardware key lights go on and it seems digitizer is responding, but the screen backlight is off. I wait 30 seconds and press again or double tap and everything works fine... It seems to happen randomly a few times a day. If it is not hardware, which log should I be checking?
[ONE Original Android Development] NoSpamDan:
What exact build and GApps are you running, and is it the stock kernel? A logcat should be fine, but I would suggest making a backup and clean flashing to test. "Sometimes" needs to be more specific, as in "reproducible"... ;)
[ONE Original Android Development] bwais:
Stock kernel. I don't know how to get more specific than sometimes, as i don't see any pattern so far. I clean flashed the 03.31 build, had the issue there. Dirty flashed 04.03 and issue still there. I can try another clean flash

I just disabled smart lock. Just wondering if it might be related.
[ONE Original Android Development] mad.jack10:
I currently only use the circle screen off gesture for the torch and I have the rest set to do nothing.

When the screen is off and say I draw an arrow the phone still vibrates.

I'm guessing this is a bug?

Thanks
[ONE Original Android Development] Gliuk_er:
Guys, is there a way to block Quick Settings pull down on the Lock Screen?
[ONE Original Android Development] eiwarmer:
Nope, but you can disable the advanced reboot powermenu on the lock screen
[ONE Original Android Development] droidead:
What is this combination OOS+sultan can means practically? Bec no difference in camera
[ONE Original Android Development] 69gm:
I beg to differ. It's a huge difference.
[ONE Original Android Development] droidead:
With stock camera i didn't find any difference in quality.. If there's some special camera app to use with this ROM then i maybe wrong
[ONE Original Android Development] 69gm:
If you just take casual pictures, you may not notice. When you start looking at the details of the picture...like really looking at the fine details..especially of subject matter that has a lot of them, you begin to see the difference.

One obvious change (if you want hard numbers) is that Sultan's HAL allows for resolutions of 4208 x 3120. Standard is 4160 x 3120.
[ONE Original Android Development] kennymc666:
hi there

i started to experiment with other kernels and flashed franco, radioactive, ab123321 and lightning kernel (so far). the only one that worked perfectly with Candy7 was lightning kernel. the other 3 kernels worked too but the camera didnt. whats the reason for this? could anyone explain for dumb me? is it possible to flash one of these kernels with working camera? are these kernels / camera not compatible with this ROM? NoSpamDans kernel working fine (including camera) but im just wondering for experimenting purposes ;)

greetz

Sent from my One
[ONE Original Android Development] 69gm:
There are no other kernels except Lightning. This is due to Sultan's camera HAL. I believe even Dan is using Lightning in his ROM.
[ONE Original Android Development] kennymc666:
wow! thanx for the quick answer! ok, so i can stop my kernel flashing experiment on this ROM ;)

greetz

Sent from my One
[ONE Original Android Development] qaliza:
I recently had a oneplus one screen replacement. The new screen however is not as good as the original one with washed out colors and a yellowish tint.

So to fix the colors i use a kcal supported kernel and the the color app, and for the yellowish tint i just increase the color temperature in liveDisplay to 7400k.

Since there is no livedisplay in AOSP roms, is there any way to modify the color temperature?
[ONE Original Android Development] grusta:
https://play.google.com/store/apps/details?id=eu.chainfire.lumen
[ONE Original Android Development] qaliza:
Thanks a lot. Exactly what I was looking for :)
[ONE Original Android Development] shubham1120:
Any Hike messenger users here? On the latest build, it is stuck on "scanning contacts".

Is anyone else facing the same issue. Hike is working perfectly on COSMIC OS.

Regards,

Shubham