yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] pdfruth:
Ya, sorry, didn't want to spam the forum with a huge logcat.

Perhaps a bad assumption, but I presumed the "earlier logs" referenced in the message is actually referring to the SIGSEGV in libc_malloc.

Cuz, the 10 minutes just prior to that, the phone had been put to sleep by pressing the power button.

Anyway, I've cut/paste all the logcat messages since oh-hundred hours that day (just over 19 hours) to a pastebin here

A quick search of the thread indicates that this segmentation violation was happening back in Android O days too. See post #7785 here.

The backtrace in that post is almost identical to the backtrace in my reboot/crash yesterday;

Backtrace from post #7785;

03-30 12:33:53.855 F/DEBUG **(22243): backtrace:
03-30 12:33:53.855 F/DEBUG **(22243): #00 pc 00061df8 [anon:libc_malloc:97980000]
03-30 12:33:53.855 F/DEBUG **(22243): #01 pc 0000813b /system/lib/libloc_eng.so (LocEngReportXtraServer:roc() const+306)
03-30 12:33:53.855 F/DEBUG **(22243): #02 pc 00003b05 /system/lib/libloc_core.so (loc_core::MsgTask::loopMain(void*)+76)
03-30 12:33:53.855 F/DEBUG **(22243): #03 pc 0000eaa7 /system/vendor/lib/hw/android.hardware.gnss@1.0-impl.so (threadFunc(void*)+6)
03-30 12:33:53.856 F/DEBUG **(22243): #04 pc 00047e3f /system/lib/libc.so (__pthread_start(void*)+22)
03-30 12:33:53.856 F/DEBUG **(22243): #05 pc 0001b125 /system/lib/libc.so (__start_thread+32)

Backtrace from my crash/reboot yesterday;

10-28 19:43:11.493 20370 20370 F DEBUG : backtrace:
10-28 19:43:11.493 20370 20370 F DEBUG : #00 pc 00049698 [anon:libc_malloc:a4d00000]
10-28 19:43:11.493 20370 20370 F DEBUG : #01 pc 00008043 /system/lib/libloc_eng.so (LocEngReportXtraServer::proc() const+318)
10-28 19:43:11.493 20370 20370 F DEBUG : #02 pc 000039fd /system/lib/libloc_core.so (loc_core::MsgTask::loopMain(void*)+84)
10-28 19:43:11.493 20370 20370 F DEBUG : #03 pc 0000dc33 /system/vendor/lib/hw/android.hardware.gnss@1.0-impl.so (threadFunc(void*)+6)
10-28 19:43:11.493 20370 20370 F DEBUG : #04 pc 00063d03 /system/lib/libc.so (__pthread_start(void*)+22)
10-28 19:43:11.493 20370 20370 F DEBUG : #05 pc 0001df85 /system/lib/libc.so (__start_thread+32)
[Nexus 6 Android Development] dahawthorne:
Nitin, I spent half an hour looking though options and couldn't find the clock position switch. I use Nova Launcher, but with Nougat & Oreo the clock was always on the right - Nova offers rooted users the choice of hiding the clock, but not moving it.

Could you please point me to the option to move the clock from left to right?

Thank you...
[Nexus 6 Android Development] razanahi:
First post said last updated 28/10 that's why I asked as file last updated 05/10. Thanks
[Nexus 6 Android Development] xconwayx:
I just looked to try and help. I don't see it either.
[Nexus 6 Android Development] jacomail95:
Does WiFi direct work in Shamu Pie or it is me who can't enable it for some reason? I need to use my device often for screen mirroring or WiFi repeater, how I can fix this problem?

Inviato dal mio Nexus 6 con Tapatalk 2
[Nexus 6 Android Development] nitin.chobhe:
Sorry, that was my bad :( I got confused. It's not there (yet)...

The OP is not updated only when there is a new zip for download; see this post: https://xdaforums.com/showpost.php?p=77717637&postcount=9490

Nitin
[Nexus 6 Android Development] piperthedj:
I know there is an identified issue with receiving calls via TMobile USA, and to last update there was no solution. I will get a missed call notification and a voicemail where appropriate. Same thing on cell number and GV number. Last night, Google connectivity services updated and now I'm receiving calls no issue.

Anyone else?

As always Hail to the Dev's, cheers.
[Nexus 6 Android Development] nitin.chobhe:
Good to hear that. Just to re-confirm, so now, it stays to LTE even when you are on call?

Nitin
[Nexus 6 Android Development] pdfruth:
Could you take a screen-shot showing package name and version... please

Mine still switches from LTE to 3G when making/receiving calls.
[Nexus 6 Android Development] golpemortal:
I second this!!!:D
[Nexus 6 Android Development] piperthedj:
Yesterday, three different occasions; two with cell number, one with GV;, I received a call, I received notification, the device rang, I was able to connect to the call, call stayed on LTE while I was on the call, I was able to complete the call.

Requested screen shots attached.
[Nexus 6 Android Development] hankfrennig:
random "soft" reboot issue

this ROM is incredible, as previously reported. many thanks as always.

I'd been having issues with random "soft" reboots since installation but since they were so few and far between I pretty much ignored it.

what happens is system will freeze (current screen imprinted/frozen, or just goes black) for 5secs, go black for 5secs more, then initializes at lock screen. things then proceed as if device is rebooting: OTA signal/data re-initiates connection, widgets must re-load, all apps have closed and must be manually re-opened or resumed, battery reports 2-3% drain from prior to "soft" reboot. really not much of an issue for as infrequently as it happens, but kind of a pain when it does.

decided to finally report this for the sake of advancing ROM development and I've attached a zipped txt log (first time ever logging, so LMK if this is proper or not)

current setup:

flashed per OP

Magisk + modules: Viper4Android FX, Universal GMS Doze, YouTube Vanced

Titanium Backup restore (apps only, no data)

running AdAway v3.2 from apkmirror

NovaLauncher

stock kernel w/o any app intervention (i.e. KernelAuditor etc.)

this most recent instance happened to occur during PlayStore app batch update.

the other instances (5 total I can recall) not entirely certain, but pretty sure they were when I was away from home and not updating anything

LONG LIVE SHAMU!
[Nexus 6 Android Development] nitin.chobhe:
I would appreciate if you can reproduce the soft reboot with clean flash of ROM, gapps and Magisk (no magisk modules or) any other mods.

Nitin
[Nexus 6 Android Development] pdfruth:
Thanks [MENTION=1998521]piperthedj[/MENTION].

Interesting. I don't have Google Connectivity Services anywhere on my phone. I wonder how that gets install with this ROM? Which gapps did you use? I used OpenGapps nano.

Anyhow, I found Connectivity Services out on Google Play Store and installed it. Makes no difference in my case. When I make a call, the status bar changes from LTE to 3G. And in some cases, while the call is in-process, it changes from 3G to H+. As soon as the call ends, it changes back to LTE.

According to Play Store, Google Connectivity Services V E.2.5.20 (4775620) was last updated on May 18th, 2018. Puzzling, why you would just be getting an update notification now.
[Nexus 6 Android Development] deadcatsrule:
Google connectivity service is ONLY for project fi and wifi...nothing to do with your carriers LTE signal .don't you read about apps before you blindly in stall them
[Nexus 6 Android Development] deadcatsrule:
Read
[Nexus 6 Android Development] nobe1976:
Try checking the hidden menu for phone info, *#*#4636#*#*, to see if VoLTE is available for your carrier. Granted the phone is fully capable of providing this service but some carriers don't support or provision the device for it.
[Nexus 6 Android Development] rfactor117:
Thank you [MENTION=5647100]deadcatsrule[/MENTION]

Depending on your carrier your phone will switch from LTE to 3g to accept a phone call.

if you use a GV phone number incoming phone calls are on Voip and do not demand a 3g connection.
[Nexus 6 Android Development] wavedashdoc:
Yes the phone IS fully capable of VoLTE, but with Pie the IMS implementation is completely different. And "out of the box" doesn't work for any custom Pie ROM for shamu. Myself and Camcory tried to make all the changes necessary, even got the IMS registered (not released) but VoLTE shows unavailable under the IMS registration.

At this point its going to take someone who can either reverse engineer the new IMS implementation to work for our device or require new code commits to fix all the errors generated in the log. I've posted those but Java is a pain to understand where the root cause is stemming from. Please anyone, be my guest but I'm burnt out from multiple weekends worth of attempts.

Here is the log for anyone that wants to give it a go.

D/RadioInfo(2183): setImsVolteProvisioned state: on

E/RadioInfo(2183): setImsConfigProvisioned() exception:

E/RadioInfo(2183): com.android.ims.ImsException: getConfigInterface()(131)

E/RadioInfo(2183): at com.android.ims.ImsManager.getConfigInterface(ImsManager.java:1809)

E/RadioInfo(2183): at com.android.settings.RadioInfo$15.run(RadioInfo.java:1292)

E/RadioInfo(2183): at android.app.QueuedWork.processPendingWork(QueuedWork.java:258)

E/RadioInfo(2183): at android.app.QueuedWork.access$000(QueuedWork.java:49)

E/RadioInfo(2183): at android.app.QueuedWork$QueuedWorkHandler.handleMessage(QueuedWork.java:278)

E/RadioInfo(2183): at android.os.Handler.dispatchMessage(Handler.java:106)

E/RadioInfo(2183): at android.os.Looper.loop(Looper.java:193)

E/RadioInfo(2183): at android.os.HandlerThread.run(HandlerThread.java:65)
[Nexus 6 Android Development] almahix:
Any new info on getting the camera working? I've tried several camera apps and none have worked.
[Nexus 6 Android Development] fueled:
Reboot
[Nexus 6 Android Development] nitin.chobhe:
Is camera still an issue for you? [MENTION=4980030]rfactor117[/MENTION] [MENTION=5143811]eocobby721[/MENTION] do you also have this?

Nitin
[Nexus 6 Android Development] hasitCN:
reboot , until camera working
[Nexus 6 Android Development] dahawthorne:
My camera works fine on photo & video. HDR+ enabled.

Version 4.2.035.141213305 - https://www.apkmirror.com/apk/google-inc/camera/camera-4-2-035-141213305-release/

I tried later versions, but from 4.3 on they are incompatible.
[Nexus 6 Android Development] fueled:
Yes sometimes when i switchoff phone for some reason and turnback on , i have to restart the phone , then it works fine.

I have the same version
[Nexus 6 Android Development] hbenz2008:
If this happens to you often and you are rooted , download kill camera from playstore. This saves you from rebooting, u just kill the process and you are back in business
[Nexus 6 Android Development] maksimreder:
Has anyone tried running Franco kernel on this ROM?

Bliss ROM also has camera issue but until I flashed Franco kernel and used Google camera it's been bug free.

Just putting it out there to try.
[Nexus 6 Android Development] hameedf:
I have the same issue with clean flash + open gapps full + magisk v17.1 it's not reboot system, it's go to the look screen sadenly after the screen get black and all the apps restarted.
[Nexus 6 Android Development] zzenyoo:
Same here. Only common thing is Viper4Android (as a magisk module). I'll try to remove it and see.
[Nexus 6 Android Development] magnamentis:
concerning random reboots:

a) i have some every 2-3 days sinde day one on latest but not on the version before

b) i have them independently on the kernel i use, default, popcorn and franco's at the moment.

c) this implies that it's either not a kernel issue or all kernels have it in common since they have the same base, no clue which of the two.

d) only way to reduce RRs was to significantly increase voltage on popcorn Kernel, that made it happen half as often while franco kernel

. behaves perfectly out of the box as far as speed and snappiness is concerned. unfortunately franco's does not allow voltages to be tweaked

. which makes it impossible to test higher voltages with this kernel which otherwise is currently best in town ;)

some of you may be aware that the N6 has a flawed electrical system that came with a few issues like volume lowering on lower charges and an increased proneness to random reboots as well as shutdowns with aging battery at around 50% charge, all things that are voltage related and there are/were more of them.

resume would be that since RRs never totally went away it is probably either rom or app related. in case that things won't improve with next update i shall try other ways to narrow things down, problem is that those RRs are so sparse that one cannot run tests without loosing the phone for it's main purpose, one would have to install the naked rom unrooted and without third party apps and with minimal gapps and wait 2-3 days to see whether it still RRs, that's simply too long at the moment, perhaps i gonna do it once my OP6T will join my OP6 as a secondary device and i can decommission the N6 for testing purposes and/or as a spare phone

EDIT: no V4A installed here, almost forgot to mention that, hence not in common as far as V4A is concerned.

EDIT2: what i did for now is to apply performance profile across the board, this could have the opposite effect if performance is high an voltage can't cope a positive effect if frequencies and boosts are higher and voltages can cope on those levels. i'll share my observations after a few days.

just in case that this sounds counterintuitive for some, the RRs mostly happen in idle mode when the device is doing nothing and/or background tasks. under those conditions usually the used cpu frequencies are low and hence voltages that apply to certains frequencies are low. apparently upon more intense use like display on and doing some foreground work RRs are close to non-existent or at least sparse. let's see ;)
[Nexus 6 Android Development] cfrank38:
Hy,

I have a strange language problem with gapps. I installed this Ron without any problem but now some gapps have mixed languages. For example Google maps is English but my cell phone is setup in Spanish .(Mexico) I never had this behavior in any custom Rom . I'm using custom ROMs since 3 years... So I have experience in installing custom ROMs. I can't change the language of some gapps. Very strange
[Nexus 6 Android Development] Dhalsim43:
Same "problem" for me
[Nexus 6 Android Development] runekock:
Gapps issue:

https://xdaforums.com/android/software/pa-gapps-continuation-t3098071/post77915718

I believe a workaround is to install the apps in question from the play store instead of a package like open gapps.
[Nexus 6 Android Development] piperthedj:
I use gaaps nano

I didn't have a choice. It auto downloaded years ago and when I uninstall or force quit it, GV gives me issues. Not sure the correlation but there you have it.

Cheers
[Nexus 6 Android Development] rfactor117:
No issues here on camera, stock camera or Google Camera both work normal.
[Nexus 6 Android Development] bigmarv31:
Same here camera is fine I usually like open camera but always test out stock and google cam, all 3 work just fine
[Nexus 6 Android Development] Markeee:
No Camera issues here with stock gapps
[Nexus 6 Android Development] almahix:
Thanks, everyone for your camera suggestions. I tried the 4.2 camera, and it still didn't work, nor did numerous reboots. Kill camera fixed it though. Excellent suggestion.
[Nexus 6 Android Development] rfactor117:
Gapps have no bearing on camera.

You can install cameras until forever... they will just not work unless the stock camera works first

Try a reboot until the stock camera works... 5 times if necessary, then try a dirty flash. Repeat if necessary until stock camera works.

Repeat if necessary.

Hope this helps ?
[Nexus 6 Android Development] dynacopas:
I found that Kik or LINE app kill the camera. Uninstalled no camera issue at all. Both seem to cause it for some reason. Flashlight same thing
[Nexus 6 Android Development] Markeee:
According to Gapps Package Comparison page anything below stock gapps don't even contain a camera

https://github.com/opengapps/opengapps/wiki/Package-Comparison
[Nexus 6 Android Development] rfactor117:
Ummmmm yea

Nitrogen OS has a ASOP camera preinstalled.
[Nexus 6 Android Development] magnamentis:
headsup on random reboots

for those who are interested, almost punctually after about 1 day i just had another RR on Franco Kernel Performance Profile.

just wanted to report back as promised that this variant did not solve anything, in fact 1day is on the shorter end of all recent intervals, will go back to power saving on idle triggered via tasker intent command.
[Nexus 6 Android Development] ProRules:
You devs are doing god's deed!

Can't wait for a stable release ^^
[Nexus 6 Android Development] rfactor117:
Here you go for stable release.

https://androidfilehost.com/?fid=1322778262904020405
[Nexus 6 Android Development] ProRules:
Its the same download as the one that some have reported issues with right?
[Nexus 6 Android Development] rfactor117:
Do you have issues?

Or is it stable for YOU?
[Nexus 6 Android Development] ProRules:
Well its a pretty new OS.

On a no longer supported platform (nexus 6 shamu), bugs are almost inevitable at the first dozen releases, from my own experience.
[Nexus 6 Android Development] magnamentis:
there is and never has been a piece of software without bugs, depending on use case. you have to flash and see whether there are bugs for your use case, if not it's ok, if yes one has to look for a rom with other bugs ;)

flash and test and contribute, much more efficient and better for development than to discuss what's a bug and how important which bug if for whom. the last more or less perfect roms were nougat roms, even oreo roms never got perfect for this device for the reason youm mentioned and for the fact that many things are aging in such a device, batteries, kamera mechanics, buttons, internal memory is deteriorating (SD-Cards don't live for ever etc. etc.

just try it out and share your findings as well as eventual workarounds and solutions, that would be the right approach in a development thread.
[Nexus 6 Android Development] ProRules:
You know what, fk it, I am installing it =)
[Nexus 6 Android Development] esysfound:
MAC Randomization

Hi all ( 1) Is there any simple way to enable MAC randomization option in Developers Options, in the Networking section?

It seems it can be enabled as a default just by switching this to "true":

<bool name="config_wifi_support_connected_mac_randomization">false</bool>

but it requires an overlay that Pie does not allow? No idea how to do this edit in the config.xml file - Has anyone actually done this?

Maybe it could be included in the next release? It is a pretty handy way to bolster security / privacy on new networks.

Also-(2) any way to get a Screen Brightness slider back in the status window, so just by dragging across the top of the phone, brightness can be regulated. We had this in Oreo. Could replace my Display Brightness App?

Thanks as always to Nitin.
[Nexus 6 Android Development] robowarrior217:
Alright, so I installed the ROM on few days ago and I am totally amazed by how it works on such an old device. The only thing that is somewhat conflicting with my amazing user experience of this ROM is the random reboots, it is fine when the governor is set on interactive but as soon as i enable performance mode from the EX Kernel manager app or set the governor to something like ondemand, I get pretty hefty random reboots. Is there something wrong with the current build or is this a kernel issue?
[Nexus 6 Android Development] dahawthorne:
It seems to me (I haven't done a full audit of the thread) that people talking about random reboots also mention in the same post their tinkering with the kernel or the additions/tweaks they have made with Magisk/modules.

Me, I installed the ROM, Opengapps Nano and Magisk and left it there. No modules, no kernel tweaks, nothing.

And I have no random reboots.

I totally get it that XDA is specifically for tinkerers (this is exactly why I'm in this forum), but there comes a point where you just have to ask "Do I really understand what I'm doing with these tweaks?"...
[Nexus 6 Android Development] deadcatsrule:
99% of custom ROMs work best as is right out of box ,just as the developers intended
[Nexus 6 Android Development] hankfrennig:
Viper4Android Magisk module was the culprit :confused: SMH

just have to bite the bullet until compatibility is worked out. a small price to pay.

as you were, sir

LONG LIVE SHAMU!
[Nexus 6 Android Development] nitin.chobhe:
Thanks for the confirmation. As mentioned in the past, the ROM is fully tested before release and none from the 4 guys who test have any soft or hard reboots.

When I mention this, some users start complaining that I post same reply to every reboot complaint. But I can't help it, neither can I look into each complaint; specially with all the mods and apps that are installed.

Nitin
[Nexus 6 Android Development] razanahi:
Need to add here my final feedback after installing and using this room from last 10 days. I flash ROM and stock gapp and magisk and viper. All works great no problem at all. Google phone. Google messages, Google camera, Google contacts all are my default apps and viper fx too works great. Compliments to the Nitin and developers.
[Nexus 6 Android Development] jolebaltringue:
I'm still on my own home made 8.1.0 ROM and I haven't seen that option anywhere in the source code, but anyway I implemented mac randomization with the following script, feel free to use it (needs root):

#!/system/bin/sh

svc wifi disable

ifconfig wlan0 hw ether your:real:mac:address

svc wifi enable

NEWMAC=`echo $RANDOM$RANDOM | md5sum | sed -r 's/(..)/\1:/g; s/^(.{16}).*$/\1/;'`

NEWMAC="$NEWMAC"

ifconfig wlan0 hw ether $NEWMAC

cat /sys/devices/virtual/net/wlan0/address

- I use this script without the first line but depending on your device configuration you may need it, and no worries if you don't because it'll still work.

- In the second line change "your:real:mac:address" with whatever your real mac is (find it in /sys/devices/virtual/net/wlan0/address).

- The last line is to check that it worked and that the mac got changed, because sometimes you have to run the script 2 or 3 times to have it to do its job (still didn't figure out why but I won't look into it since it's no big deal)..

I'm not sure it'll work on Pie, since as said above I'm still on Oreo, but you can give it a try, and please let me know if it works so that I'll know that I'll be able to reuse it when I build my Pie ROM.

Now, if you want to edit the <bool name="config_wifi_support_connected_mac_randomization">false</bool> it's easy.

In the source it's located in Settings (packages/apps/Settings/res/values/config.xml) .

If you don't want to compile from source then extract Settings.apk from the ROM, decompile it and find that line in res/values/bools.xml.

Edit, recompile, push to your device, done!!

Don't worry, it can't harm your phone, in the worst case scenario it won't do anything at all and if that's the case then use the above script.

Edit:

I did a bit of research:

https://source.android.com/devices/tech/connect/wifi-mac-randomization
[Nexus 6 Android Development] esysfound:
Thanks - total newb on this so how does one (safely):

1. Extract

2. Decompile

3. Recompile

4. Push over

There are some on-line apk solutions but they say it will compile / recompile to "nearly original" which gives me a nice warm feeling (not).

The actual edit of the line sounds quite easy - how does one do the rest?
[Nexus 6 Android Development] robowarrior217:
What's the point of a custom kernel then? And, I did that because on interactive mode, device was not performing good at all, even the scroll animation of the app drawer feels sluggish. Maybe you didn't notice that because you probably don't care but I do.
[Nexus 6 Android Development] nitin.chobhe:
You can flash anything that you want on your phone, but when you report something make sure that it's reproduced with stock I.e. everything is stock and no mods, no custom kernel.

And if you want to report issue with custom kernel, the right place is kernel thread.

Nitin