yashsingh1/xdaforums huggingface dataset:
[Moto Maxx Android Development] Septfox:
Hmm.

It's too soon to tell, but this makes me think of another possibility: it might be the service itself causing the reboots. That would explain why it plagues some users after it starts; The Google wants to keep your device up to date, and if it finds the user on a strong connection, it might keep trying ASAP after every reboot.

Just more speculation, though...and I would think if anything were going wrong with Play Services to begin with, there'd be some pre-reboot panic in the logs that people have sent in.

*shrugs* At any rate, as always, keep us apprised of what you try and what happens :good:

Wow, dial-up speeds...it's been 15 years since I had to deal with that, it must be painful. Even 1xRTT is something like 100kbps average :eek:

I guess it's better than completely losing the connection, though.

But yes seriously, Google gets really stupid with data usage sometimes. It seems like they have absolutely zero respect for users with low data limits, judging by how many of their non-disable-able (well, without root) services use it whenever they please...

I love the abilities and services that a constant link with Google give me. I don't mind providing them with metrics in return; their services are free and very good, after all. I just wish they cared a bit more about where and when they spam data back and forth :<
[Moto Maxx Android Development] Debuffer:
Well, my device was rebooting every time, but now it's just okay and didn't reboot any time in the last 3 hours.
[Moto Maxx Android Development] quantum tao:
I also had the unable to find files problem in TWRP, they were google files too.

However i was able to fix it by running the batch operation "clear cache for user and system apps" in titanium backup.
[Moto Maxx Android Development] DarkLey:
Yeah, apparently it was happening only with OpenGapps Nano 11/23, 11/24 had already solved the issue. I did wiped data though, to make a clean installation, but after that no more errors.

I'm now trying the suggestion [MENTION=1217488]septo[/MENTION]Fox made. So far so good, disabled the service but didnt find any related receiver to disable. No reboots since last night, and also no problems while switching networks (since WiFi would probably trigger the service more often than 3g/4g)
[Moto Maxx Android Development] ChazzMatt:
One of the best posts I've read in a while. Very logical!
[Moto Maxx Android Development] karll123:
If Gapps are based on pixels seemless update process could this be the cause?
[Moto Maxx Android Development] s4shield:
My phone is now rebooting non stop. I thought if I turned it off and let it sit for an hr it would stop but it keeps doing it. :(
[Moto Maxx Android Development] DarkLey:
See my previous posts, I had the same problem
[Moto Maxx Android Development] s4shield:
Yeah I cleared the play store data and services and it stopped for now
[Moto Maxx Android Development] eddiemc12:
most of us are having the same problems,just remember that just like how marshmallow wasn't initially released for us it's the same with nougat and it's a relatively new rom even official devices are having bugs so it makes no use to keep complaining just revert to a stable rom until the developers iron things out and keep in mind that they aren't being paid for what they do and it's not a full time thing it's more like a hobby so we just have to wait.
[Moto Maxx Android Development] s4shield:
I'm not here looking for a social media outlet. I'm reporting what's happening and what i'm doing to fix it. I'm not getting any bug logs so I can't submit them. I want to help not give up and flash something else.
[Moto Maxx Android Development] DarkLey:
I had the sequential reboots problem. What I did was install another version of OpenGapps Nano (11/24 or 11/05, both are stable). I Wiped everything except my internal storage, then flashed crDroid and Gapps and started the phone. Never had the problem again. I was using OpenGapps Nano 11/23 when that happened, I think that's what caused the problem, this version is probably faulty.

[MENTION=1217488]septo[/MENTION]fox

I'm still with Update Service disabled and haven't had a reboot since yesterday. I'll wait another couple of days to see if anything happens and report back, but for now this seems to be the source of the reboots. Maybe (as someone stated on another post) the update process depends on something (maybe hardware) that Pixel has and Quark don't.
[Moto Maxx Android Development] pandimus:
Mine did the same. I went back to 11/16, which seems pretty solid. My reboots were so bad I needed to go into recovery from boot screen
[Moto Maxx Android Development] DarkLey:
No dice, got a reboot browsing my Google Drive in 4g. But it was just one.
[Moto Maxx Android Development] dougsampaio:
Anyone having problems like mine?

Can't give any logs because the phone rebooted,or course.

I did wipe everything, including internal storage, last build and open gapps (11/24), recalibrated battery via app twice.

I'll try to disable the update thing next time.
[Moto Maxx Android Development] Septfox:
...Pixel's what, now?

~some time later~

Hmm, it seems like they go for some kind of Safestrap-esque thing for the /system partition, or at least that's how it looks superficially. That's an interesting approach to updates; even if the O/S manages to bork the update, in theory the user can continue on like nothing happened and Android can try again after cleaning its mess up.

It looks like it's mostly changes to base system stuff and fastboot, though...gapps isn't mentioned in the article that I just read, and I don't think Google (let alone any other OEM) has ever distributed firmware updates through Play Services. While it could be related, I wouldn't think so, and the mechanism is probably disabled for our build anyway because...er...we're not using Pixels and don't have the extra partitions laying around. Someone who knows what they're looking at should probably check on that...

*Septfox

Anyway, like I said, don't blame me if it doesn't unbreak. It was just a theory :v

If disabling updates does at least reduce the number of reboots, though, I'd call that progress. We need to wait and see for a few days, 24 hours is a meaninglessly small sample period; not having as many reboots could simply be down to luck, due to whatever is actually causing it not being touched in that period.

-----

Instructions for anyone else who wants to try disabling updates to see if that solves anything:

Get MyAndroidTools, or whatever you want to use that can disable services and receivers; the following assumes you're using this particular app

Start it up, go to Services (top left, in the drawer)

Swipe right to get to System

Fling down and find Google Play Services

Tap the Search button at the top-right, search for SystemUpdateService

Tap the toggle to disable it; the app will freeze a moment, then crash, but the service should be disabled now

Restart the app and retrace your steps, but this time open Google Services Framework

Verify that SystemUpdateService has disabled here as well (it should have)

Hit the back button, and swipe right to pull the drawer up again

This time, tap Broadcast Receivers, and again open Google Play Services

Search for SystemUpdateService again, then long-press on one of the entries to enter multi-select mode. Tap the remaining three to select them

Tap the top-right button to disable them all at once; the app will again freeze and crash

Done.

-----

[MENTION=5747496]bhb27[/MENTION], your Aduitor only pulls logs from the current session, right?

Would it be helpful if people were to provide tombstones and/or last_kmsg output as well? Also, how about leaving a terminal open in the background (I don't know that the "stock" terminal emulator will, but the one I use runs indefinitely until closed), piping logcat output to a file; do you suppose it would run close enough to the reboot to actually catch something useful?
[Moto Maxx Android Development] immadeofpixels27:
PSA [MENTION=535343]all[/MENTION]

There is an option in developer options that keeps log buffers persistently, through reboots. It is at the very bottom of the 'debugging'. Please turn it on and stop reporting that you encountered a bug but couldn't get logs due to reboot when the possibility is there.

That is all
[Moto Maxx Android Development] Septfox:
New in Nougat? I don't see the option in RR.

If it works, that's fantastic, it should hopefully catch whatever keeps crashing and burning...or at least help point in the right direction.
[Moto Maxx Android Development] immadeofpixels27:
That's why I posted in this thread, not the RR thread; it's either new in Nougat or part of crDroid (we'll find out which when RR N is released for us).

Yes, hopefully it catches whatever is causing the reboots. :good:
[Moto Maxx Android Development] lattosimbaste:
Must be a later addition, it's not in the 7.0 20161031 crDroid build
[Moto Maxx Android Development] Nitefire77:
Ladies and gentleman. We do not need 20+ posts saying "i also am experiencing reboots"

after the 1st 2 posts its pretty well understood that reboots are a thing that happening with the rom. jumping in adding you also have them DOES NOT HELP ANY and all it does is clutter the thread making it more difficult to find posts about other issues that might be there.
[Moto Maxx Android Development] DarkLey:
I'm not experiencing reboots anymore, but Play Services keep crashing from time to time. That happened almost 24hrs after I had my last reboot, and I'm with ServiceUpdate disabled. I didnt do anything except a purchase in Play Store. I really dont know what happened but this is better than before. Anyone having something similar?
[Moto Maxx Android Development] Debuffer:
What did you do exactly?
[Moto Maxx Android Development] DarkLey:
Actually nothing that i didnt describe here already. But nvm, its not related, i had a reboot again.
[Moto Maxx Android Development] Septfox:
Could be due to the receivers still being active. Try disabling them too.

I realized last night that it's actually Checkins and event-logging that require event receivers being disabled to prevent wakelocks, but the update service and receivers probably don't appreciate being orphaned either...

Plain old app crashes can actually be helpful. Does it give you a Report button when one happens? You can press this to have the system scrape together some information about the crash. It then gives you an option to preview the contents or send.

If you preview the contents, it'll give you a box you can scroll through; should be able to find which app crashed (fairly obvious) and why/what it was trying to do. Don't bother sending the report, Google will probably ignore it.

Note: not a stab at Google, they probably just disregard reports from non-standard usage cases. If not, they'd never get anything done.

Also, if you haven't already, find the setting in Developer Options that [MENTION=5980801]immadeofpixels27[/MENTION] brought up, that turns on persistent logging. If it works and you can get a log of a crash or reboot in action, even if it doesn't tell us exactly what's wrong, every little bit of data helps.

-----

I'll probably be joining the 7.1 Cool Kid's Club on Monday, gonna be on the road all day tomorrow so I can't be dealing with random crashes/reboots. Can't guarantee that I'll be helpful, but at least I'll be able to see what you guys see and we can all crash together :good:
[Moto Maxx Android Development] neo_cyborg:
Bugs

All right. I've been using the ROM for nearly a month now and glad to say no reboots so far. But I have noticed a few bugs and app crashes which are as follows:

1) Xender file sharing via hotspot doesn't work even though hotspot switches on and the other party can discover my device through the same app

2) Bluetooth file transfer doesn't work, the system app com.android.bluetooth keeps crashing.

3) YOUTUBE: When switching quality from anything below 720p to 720p, the video gets cropped and only to top left corner portion of the video is visible. But if I switch from 1080p to 720p there is no issue.

4) Certain games like Psebay, Need for Speed : No Limits don't launch.

Great job on the ROM apart from these bugs. Buttery smooth and good battery life.
[Moto Maxx Android Development] immadeofpixels27:
Good observation! That problem has been pointed out a couple times before, and I myself also experience it, but we hadn't figured out that manually bumping the resolution up was the cause.

Have you changed the DPI at all? That also seems to be a common theme with this bug.
[Moto Maxx Android Development] neo_cyborg:
DPI was the same as at the time of install(411). Can dynamic gappa cause this problem?
[Moto Maxx Android Development] immadeofpixels27:
I don't think that's the culprit; I use OpenGapps and have the issue.
[Moto Maxx Android Development] Zee_dev:
Need help

Can you help e with this installation ?
[Moto Maxx Android Development] ghaem.xh:
I switch to 6.0.1 stock rom dude.this rom is good but not stable for me with many random reboots.hope for next updates
[Moto Maxx Android Development] Zee_dev:
Thanks bro u saved lot of my time, but how u upgraded to 6?

I have XT1254 with android version 5.1, how can I upgrade to 6?
[Moto Maxx Android Development] ghaem.xh:
http://xdaforums.com/showthread.php?t=3426234
[Moto Maxx Android Development] Zee_dev:
Do I need to root before this ? are there any prerequisite?

AM just trying to upgrade as I get SIM card not found error daily and I have to restart, will upgrading solve this issue ?
[Moto Maxx Android Development] ghaem.xh:
Read in first page.you must have unlocked bootloader then install custom recovery
[Moto Maxx Android Development] arizonaomnia:
Did you ever find the wallpaper?
[Moto Maxx Android Development] uveequis:
Yes. I had to do factory reset, take a screenshot of the home screen and do a reverse image search. I don't remember the source but there it is.
[Moto Maxx Android Development] arizonaomnia:
Thanks!
[Moto Maxx Android Development] sneakchic:
google services keeps stopping

Hey all,

First off, bhb27 , great rom, loving it for the most part. having some issues with your latest one though. Google play services keep crashing, even upon a fresh install where i wiped everything, including internal storage. Was also having random reboots, sometimes consecutive ones, but the battery has been going faster than it did in the 11/16 version and google play services wasnt crashing in that one.

i thought maybe this screenshot would help, i noticed it said that it couldnt find those files after each install i did lately. i've tried using open Gapps and dynamic gapps and get the same results.
[Moto Maxx Android Development] FlavioV:
Just flashed my XT1225 without issues this Saturday. Too early to say anything but it looks good so far. Didn't get a single reboot except for the first time I opened iSu.

Worth to mention that I used the stock opengapps package (OP recommends a smaller variant but I'm too lazy to install them one by one lol).
[Moto Maxx Android Development] immadeofpixels27:
liboemcrypto.so is in /system/vendor/lib/. However, renaming it didn't fix the 0013 error :(

Are you still having that issue? If not, what changed around the time it started working?
[Moto Maxx Android Development] rspaulo:
I don't have this file anywhere. Just made a search on / and nothing
[Moto Maxx Android Development] immadeofpixels27:
Well, I've attached mine for you although it won't really solve anything.

Again, do you still have the 0013 error?
[Moto Maxx Android Development] rspaulo:
Worse, extracted yours to /vendor/lib started Netflix and got a reboot
[Moto Maxx Android Development] immadeofpixels27:
Ouch. Sorry about that. [MENTION=4049545]rspaulo[/MENTION] mentioned you since you already read my post before I edited it

Erm... It goes in /system/vendor/lib/
[Moto Maxx Android Development] fgl27:
it seems that latest gapps are causing data corruption, clean yours data will not solve it, is need to format the data and that erases internal memory files so first do a backup.

AFTER???

maybe you are lost in translation, were in OP says to do that? I'm confuse

the instruction need to be fallow in this order from top to bottom, the word after is not included...
[Moto Maxx Android Development] fgl27:
that library by the name you can tell that is related to encryption and only used to encrypt the device and used when it is encrypted, if the device is not encrypted I doubt that it is in use and can affect use, can be removed if any one wanna, only thing is that encryption will be no option, but I don't even know if encryption is a option on Nougat have not tested yet.

Netflix doesn't work to all or is a regional thing?
[Moto Maxx Android Development] FlavioV:
oops my mistake lol I probably messed up when I first read the instructions (it was my first time installing a custom ROM)

but I had no issues with the latest opengapps stock. maybe there's an issue in the smaller variants?

(just saying stock worked for me I'm not necessarily recommending it)
[Moto Maxx Android Development] Tiapaola:
Rebooting

I flashed this ROM last night and my phone keeps rebooting randomly... Anyone else having this problem?

(the system is really, really fast! Good job!)
[Moto Maxx Android Development] ChazzMatt:
oh, let me search the thread for "reboot" before I ask a question discussed on almost every page.

http://xdaforums.com/search/thread/3491257?query=reboot
[Moto Maxx Android Development] mubaidr:
Well, very strange to read that a lot of users reporting reboots, well i had none, not a single one since the last 2 builds. I am also using OpenGapps 17th Nov. Is there any way i can help with the diagnose of the issue by providing logs, configuration etc ?
[Moto Maxx Android Development] fgl27:
ROM update! crDroidAndroid-7.1-20161127-quark.zip​

Recommended clean install this version

Was need to me make too many changes and too many test version to achieve this stable, I have no idea if this will dirty flash ok on the top of the old if flash this on the top of old version don't report any bugs before you clean install

Changelogs:

Device Click Here

CRDroid Android Nougat source and Quark Click Here

Download Links :

Download: ROM Click Here

Gapps:

7.1 Banks Dynamic GAPPS click here (Choose SDK25 version)

Open Gapps Click Here (Choose Platform: ARM, Android: 7.1, and a Variant smaller pack possible, Install any other gapps from play, latest gapps package from Open seem to be really bad, go to old released page and Download gaps from before November 05 recommended open_gapps-arm-7.1-nano-20161105.zip)

TWRP For Quark: TWRP Click Here

Instructions :

Download the latest build and GApps.

Reboot to recovery (recommended make a backup)

Coming from different ROM? Then Always wipe Data (without media aka without internal memory)

Wipe System and Cache

Flash the latest build* and GApps **

Reboot and profit!

* Current TWRP in all devices for all android Nougat zip will display the below message during installation don't worry about it

[COLOR="red"]E : Unknown command [log]
E : Unknown command [log][/COLOR]

** Gapps not demanding the ROM works perfect without it and there is ways to have play to work without gapps. In a ROM updates "dirty flash" if you have gapps always flash gapps again after the ROM update

Bug report are welcome, make with in the most accurate description possible, do not spare words, screens and logs, a bug that I can't understand and can't be reproduced, I can't fix.

Always start a post with a bug report with [MENTION=5747496]bhb27[/MENTION] and always attached a log .zip

BHB27 Kernel Adiutor > Logs > One click all Logs to a ZIP

** If the device Random reboot all the logs are lost so just described like I ask above without logs

Bugs without logs that are not reboots and without [MENTION=5747496]bhb27[/MENTION] will not be read, there is too much posts on the thread I don't have time to read it all, you guys can post as much as you need of course as long is things related to this thread
[Moto Maxx Android Development] URIST.LG:
Hello, do you fix reboots in this rom? THX.
[Moto Maxx Android Development] fgl27:
I don't have reboots. I don't fix problem that I can't reproduce.

try and let me know in a way I can reproduce.
[Moto Maxx Android Development] URIST.LG:
I have XT1254, this gaapps (banks_dynamic_gapps-7.x.x-20161002sdk25.zip), twpr 3.0.2-0 and new rom. I made full wipe of all. Let see
[Moto Maxx Android Development] drizzzzzz:
[MENTION=5747496]bhb27[/MENTION] you mentioned you are flashing new versions of the rom very frequently in the past. For me, the reboots don't start happening until (on average) 3 days. At this point, I just wipe the system and cache and reflash and I can get another few days from it. Do you think it's possible that you aren't getting the reboots because you aren't on the same image for a long enough time? Someone else can probably pop in here, because I can only speak from my own experience.
[Moto Maxx Android Development] fgl27:
I don't know I have no way to test that theory.

I can't make changes and don't test then, I can't stay in a same version for days hoping I will catch the exactly moment of a problem then try a fix more days and days and so on and so on, there is too many changes in a week if I don't test them after they are made I lost the chance to pin point the exactly change that cause this or that.

If you can tell me exactly how I can cause a problem after some days I bet I can cause that problem in minutes on my device, if you can't point the the exactly problem then is really hard on me.
[Moto Maxx Android Development] drizzzzzz:
I understand and appreciate the response, and I wouldn't ask you to stay on the same version just to figure this out. It was just a thought I had as to why you haven't experienced them. Honestly, I've been trying to figure out what causes it for a while. I have almost no apps installed to reduce the chance that an app is causing the reboots. It's very difficult to pinpoint because it almost always happens during idle (for me at least).
[Moto Maxx Android Development] fgl27:
Let me know if this keeps happening in latest version, as you say you wipe system and cache, if you do not change system, and have no app that does, next time try just to wipe cache maybe is some thing related on how cache is be used, at least is a better pinpoint of the problem..

Future update will constantly bring change until the OS is next to perfect to everyone, Nougat has just start there is too much to come...
[Moto Maxx Android Development] xboxbr:
I didn't find that option in today's build
[Moto Maxx Android Development] neo_cyborg:
All right. I've been using the ROM for nearly a month now and glad to say no reboots so far. But I have noticed a few bugs and app crashes which are as follows:

1) Xender file sharing via hotspot doesn't work even though hotspot switches on and the other party can discover my device through the same app

2) Bluetooth file transfer doesn't work, the system app com.android.bluetooth keeps crashing.

3) YOUTUBE: When switching quality from anything below 720p to 720p, the video gets cropped and only to top left corner portion of the video is visible. But if I switch from 1080p to 720p there is no issue.

4) Certain games like Psebay, Need for Speed : No Limits don't launch.

Are these bugs fixed in the new update? Thanks for your continued work on the ROM. :)
[Moto Maxx Android Development] quantum tao:
11/27 update, i really like the new network activity status bar icons.
[Moto Maxx Android Development] fgl27:
I don't know, you never quote me with logs I never look at them, is right there in the post you just quote...

there is too many post in this thread if you don't fallow the simple things I ask I can't help you.
[Moto Maxx Android Development] fgl27:
have you read the source changelog, or even easier look to my update post pics??? :laugh:

:good:
[Moto Maxx Android Development] quantum tao:
Verizon vvm installed on this version for me, took the normal amount of 2 attempts. TY.