yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] SteveYoungs:
Not that I'm aware of, but the real question is... Why would you want to do that? You will have a horrible time with the proximity sensor turned off. You would have to turn off Ambient Display and DTTW to prevent "bum dialing". Every call you made / received would have to be hands free otherwise the side of your face is going to activate stuff on your screen. Imagine closing your eyes and randomly tapping and dragging your finger all over your screen, that's what your face will do during a call without the proximity sensor doing its magic.

So, even if it was possible to disable the proximity sensor, I wouldn't recommend it.
[Nexus 6  Original Android Development] Galati93:
What's the difference between 09/12 build and 10/12?
[Nexus 6  Original Android Development] SubwayJrd:
https://download.lineageos.org/shamu/changes/

You can consult that page for any changes between builds and changes that will be included in upcoming builds.
[Nexus 6  Original Android Development] Najeeb3344:
In latest build I have 2 phone apps & Flashed open gapps stock & don't have root plz remove phone app from next build
[Nexus 6  Original Android Development] Elektroschmock:
Thats not going to happen. We won't ship a ROM without a phone app.
[Nexus 6  Original Android Development] ktmom:
Just got into "settings->apps->unwanted phone app" and disable it. Make sure to set the desired phone app to default.

"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
[Nexus 6  Original Android Development] magnamentis:
Freeze it but do NOT remove/uninstall it because it will be back with each update and this could cause issues.

generally apps that come with the rom, mostly they're system apps, should be frozen once not needed, and not removed.

keep in mind that you have to set the correct defaults, this applies to any app of this kind you'd change, i.e. launcher, browser, messaging etc.

last but not least it won't make much sense to ask for rom changes if the rom is that long on the market ;) if something is generally feasible or wanted it would have happened by now ;)
[Nexus 6  Original Android Development] mrk2815:
do agre if its been in all vesion of Lineage roms tis not going ot go away just because someone thinks its not needed.not all flash gappps.
[Nexus 6  Original Android Development] runekock:
Previously, Open Gapps removed the aosp phone when it installed Google phone. But it was reported that emergency calls only work properly when aosp phone is installed.

For that reason, you should not disable the aosp dialer. Either don't install the Google dialer, or live with having both apps. If two icons bother you, some launchers will allow you to hide one.
[Nexus 6  Original Android Development] ktmom:
As long as you set the Google dialer as the default phone, emergency calls work fine. Disabling the ASOP dialer in settings -> apps will not effect the use of the dialer.

Even opengapps site mentions this.

"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
[Nexus 6  Original Android Development] runekock:
Yes, that used to be the case. But at some point it seems to have changed (but maybe only on Pie? I don't know).

See this post

https://xdaforums.com/showpost.php?p=78262771&postcount=5756

and other posts on that thread.

Anyway, if you do disable the AOSP dialer, I suggest you test an emergency call before you really need it.

As to the Open GApps website, it may not be up-to-date. The project is seriously understaffed.
[Nexus 6  Original Android Development] DarkSearinox92:
Problems

Hi guys. I don't understand why if my phone reach the 30%, appears random crashes... every time. If the battery goes under 30, of example 20, if you are trying to do something hard just like the camera, sometimes it crashes.

If you reach the 10% and the phone crashes, you'r not able to power on the phone (as if he considered the battery to 0%).

Do you have this problems?
[Nexus 6  Original Android Development] dahawthorne:
Anyone with a dying battery can have this problem. Buy a new one.
[Nexus 6  Original Android Development] DarkSearinox92:
I don't think that is a battery problem... I'll check health battery with some app <_>
[Nexus 6  Original Android Development] gettes:
It's battery. Many have had this problem. I did. Get a new battery. You'll have a like new phone and love it. An edge of dying battery causes all sorts of weird stuff to happen. Save yourself the trouble. Search battery in this forum... hundreds of posts related.
[Nexus 6  Original Android Development] Elektroschmock:
It is your battery!

Trust me, I'm an (hardware) engineer. :P
[Nexus 6  Original Android Development] teamoushy:
I was facing an issues with all roms i do try, like split screen issue for nexus 6, no one have a solution for that, some say its a motherboard issue and not all devices have it, once i changed the battery everything comes back to normal
[Nexus 6  Original Android Development] dwardo:
I agree had to change mine for that exact reason a year ago.
[Nexus 6  Original Android Development] McMannes:
I was having the same problems. Solution: battery replacement
[Nexus 6  Original Android Development] DarkSearinox92:
Thank you very much to all :) I'll buy a new battery!!! Thank you <3
[Nexus 6  Original Android Development] Najeeb3344:
Request

Plz add circle battery in next update if possible!
[Nexus 6  Original Android Development] dwardo:
I'm not requesting ;)... But that is the one thing I miss :)
[Nexus 6  Original Android Development] Elektroschmock:
This is a device thread. I am not accepting ROM specific requests.

I just don't have the time to work on the ROM side.

Circle battery might come back with Pie:

https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/221716

You might backport it to 15.1
[Nexus 6  Original Android Development] magnamentis:
not that i have an issue with your decisions or care about the battery icons but then i always like to understand how XDA works.

according to the screenshot i attached, what's the difference between a rom-thread and a device-thread if a thread is under "development" marked as [ROM]

always happy to learn new things after so many years, T.I.A.
[Nexus 6  Original Android Development] giannis_mathiou:
[MENTION=1386924]magnam[/MENTION]etics From what I know and I can understand, according to LineageOS standards this not something that has to be implemented on device side (kenrel and devices blobs specific) but it is something relative to LineageOS interfaces/implementation.

Maintainers are responsible about kernel/device blobs that allows each device to benefit from LineageOS features.
[Nexus 6  Original Android Development] magnamentis:
you address the wrong person, i'm not interested in any features, that was someone else. my question was entirely different and neither rom nor device specific, but about the definition of a device or rom specific thread that is under development section and marked as [ROM] - thread.
[Nexus 6  Original Android Development] Najeeb3344:
Any estimate about pie ?
[Nexus 6  Original Android Development] dahawthorne:
If you want to continue to get help in XDA you must learn to use the search function.

https://xdaforums.com/showpost.php?p=78353462&postcount=2000
[Nexus 6  Original Android Development] mrg666:
There is another mark "OFFICIAL".That means ROM follows the official repository only. When [ROM] [OFFICIAL] are used together in a device forum, the thread is device specific only. The circular battery change is for the ROM in general and that request will affect all ROMs that are [OFFICIAL]. So such a request should be discussed in the general Lineage OS forum, like this
[Nexus 6  Original Android Development] Event_Horizon:
Lineage 16 for Shamu.. baby need some boooost...
[Nexus 6  Original Android Development] dahawthorne:
Seriously...?
[Nexus 6  Original Android Development] Najeeb3344:
I Think lineage os 16 is in process very soon it will be released as official !
[Nexus 6  Original Android Development] Elektroschmock:
Could you all please stop speculating about a possible LineageOS 16.0 release for shamu!

I will let you know if there is something worth beeing announced.
[Nexus 6  Original Android Development] BootloopedMillennials:
Nevermind
[Nexus 6  Original Android Development] AmirHRC:
lineage os site have a weird problem now !!!? download page or changelog page don't work !!
[Nexus 6  Original Android Development] dbrickg:
the lineage os download site's middle name is "weird problem." just wait awhile and try again :)
[Nexus 6  Original Android Development] NewDayRising:
A simple thanks would have probably sufficed – and yes, thanks – but I did want to reply because as someone who just dove in and follows specific devices, I was unaware that there were also specific ROM discussion forums to follow. Sometimes we use things intuitively, or only follow a small part of a larger whole. I appreciate the breakdown.
[Nexus 6  Original Android Development] Dhalsim43:
Screenshots
[Nexus 6  Original Android Development] Hammerfest:
I actually have delt with 4 Nexus 6 phones where the proximity sensor doesn't work correctly, so I too would like the ability to have it disabled.

Timeouts set and such when blocked work just fine (inserted paper under it), its just a PITA to get in to do that*

, AND with it blocked its sometimes you have to hit power twice to get it to respond, no big deal there, just a pain.

Its actually a less common but still common enough issue with the N6 (thankfully I have gone through enough of them as family is blind and loves the HUGE screen!)

*for reference, the scraping and digging was on 2 of them I needed to replace parts on anyway, the other 2 have a paper inbetween screen and case :D
[Nexus 6  Original Android Development] magnamentis:
seconding everything you're saying while we who have experience like in my case 30 years of mobile computing/calling have to keep in mind that there never ever was a motorola phone that didn't cave in with some hardware before it's expected life expectancy whas reached. no matter which, one letter of the physical keyboard not working back in old times was enough to throw it.

the n6 has electrical flaws and in addition i never changed so many parts like cameras and batteries etc lik with this phone.

i purchased mine when it fell to 400€ and found any of my biases confirmed, but keep it because of it's gotten rare screen ratio.

so anyone has been warned and hence we can't complain. i still love this phone over all but it IS a typical motorola phone. similar to US cars, they often look great and even are great when new, but never reach the standards of a japanese or german car with few exceptions, specially with age.
[Nexus 6  Original Android Development] ThePhenomenalOne1:
Yes, I have the same issue, the display very slightly sperated from the case.

So, whenever the proximity sensor is in use the screen goes black then I have to press where the sensor is to turn it up again.

I'm going to try your paper solution

But I just wish there was a software solution to just turn it off
[MENTION=3383960]Elektroschmock[/MENTION] you know the code of LOS betther than I do.

Is there any way to disable the sensor like by editing some system file via root or anything else?

---------- Post added at 12:32 AM ---------- Previous post was at 12:32 AM ----------

Yes, I have the same issue, the display very slightly sperated from the case.

So, whenever the proximity sensor is in use the screen goes black then I have to press where the sensor is to turn it up again.

I'm going to try your paper solution

But I just wish there was a software solution to just turn it off
[MENTION=3383960]Elektroschmock[/MENTION] you know the code of LOS betther than I do.

Is there any way to disable the sensor like by editing some system file via root or anything else?
[Nexus 6  Original Android Development] Elektroschmock:
Just a small heads up for those of you who wait for LineageOS 16.0.

It seems like I have fixed the encryption issue. :D

So there's one blocker less on our road to 16.0.
[Nexus 6  Original Android Development] Najeeb3344:
Yes Off course
[Nexus 6  Original Android Development] cujo6801:
Wow just Wow.....
[Nexus 6  Original Android Development] AmirHRC:
you are the boss ????
[Nexus 6  Original Android Development] thetallguy:
Hooray! Season's Greetings to you.
[Nexus 6  Original Android Development] Albert52:
16.0

Thanks verry much for all the work you put in.
[Nexus 6  Original Android Development] Najeeb3344:
I Think it will be new year gift!
[Nexus 6  Original Android Development] 8zabi:
this commit (ext4_utils: disable ext4 64bit block support) means that if I format my data partiton under LOS 15.1 I can use encryption again?

finally no need to go back 14.1, do the format there then update to 15.1?
[Nexus 6  Original Android Development] BootloopedMillennials:
I just tried it. Encryption goes fine but TWRP still can't decrypt data.
[Nexus 6  Original Android Development] BootloopedMillennials:
Is another issue SELinux being permissive? According to this post the DU team has found a fix.
[Nexus 6  Original Android Development] David B.:
Nice! Thank you so much for your amazing work! I do have a question about this though: Do you know if TWRP decryption will work this time around?
[Nexus 6  Original Android Development] dahawthorne:
Really? Literally two posts before yours:

https://xdaforums.com/showpost.php?p=78493222&postcount=2059
[Nexus 6  Original Android Development] BootloopedMillennials:
Yea I just tested it again and TWRP isn't decrypting. DO NOT ENCRYPT.

Maybe it's only meant for Pie but........

If you read the CarbonRom thread, [MENTION=3816568]Myself5[/MENTION] implemented the encryption fix onto the rom but it is still a work in progress.
[Nexus 6  Original Android Development] mrk2815:
maybe there will need to bea new twrp for android pie going for those older devices like ours who have incription issues an that will be resolved in the new year with a new twrp update plus a new lineage 16.0 for nexus 6 shamu. .

---------- Post added at 06:11 PM ---------- Previous post was at 06:08 PM ----------

Elektroschmock, since the shamu needs some people for pie.i dont get it, there are lots of pie roms that are not perfect.when its polished by Elektroschmock [ you will say something about it.as you did when lineage 15.1 was in the stages for nexus shamu. qQUOTE=Elektroschmock;78445661]Could you all please stop speculating about a possible LineageOS 16.0 release for shamu!

I will let you know if there is something worth beeing announced.[/QUOTE]
[Nexus 6  Original Android Development] gettes:
Quick question of curiosity: Did you fix it just for Shamu or for 16.0 in general?

Thank you, once again, for all you do.
[Nexus 6  Original Android Development] Elektroschmock:
Only for shamu, but I guess if other devices have the same problem they could fix it the same way.
[Nexus 6  Original Android Development] Elektroschmock:
sorry double post
[Nexus 6  Original Android Development] BootloopedMillennials:
[MENTION=3383960]Elektroschmock[/MENTION]

Is there a LOS recovery? I recall reading about it on one of the LOS blog posts but can't find a download.
[Nexus 6  Original Android Development] David B.:
The TWRP issue is not an LOS bug. It's an issue with TWRP. The Nexus 6 maintainer for TWRP has not updated the device tree for it since 2016: https://github.com/TeamWin/android_device_moto_shamu

There is an issue open for it but it is being ignored by the maintainer: https://github.com/TeamWin/android_device_moto_shamu/issues/1

I would fix it myself and I am looking in to doing so, but I have never built TWRP before and I am finding the learning curve quite hard to deal with.
[Nexus 6  Original Android Development] BootloopedMillennials:
Noticed that, why I was asking if LOS recovery exists. I think the TWRP developer doesn't have a Nexus 6 anymore to troubleshoot such an issue.

Good luck, wish I could help but that's well beyond my knowledge base too.
[Nexus 6  Original Android Development] dahawthorne:
I'm not an Android dev in any way (mainframe dinosaur), but I don't follow these comments about lack of maintenance, given that there is a TWRP 3.2.3 for Shamu dated 31st July 2018. I've used it many times to back up and restore, every time flawlessly.

Please clarify for me. Thanks.
[Nexus 6  Original Android Development] BootloopedMillennials:
Let me start off by saying I'm not a developer. But maybe changes to keep it up to date aren't device specific. The TWRP main page has their changelog and when you go into the device specific page it has it's own changelog.

The last changelog on the shamu specific page is 12/1/2016

https://twrp.me/motorola/motorolanexus6.html

This is the changelog for twrp 3.2.3

https://twrp.me/site/update/2018/08/06/twrp-3.2.3-0-released.html
[Nexus 6  Original Android Development] David B.:
As far as I am aware, LOS recovery is still under development and when it is done, it will not have all of the features that TWRP has so it may not be a reasonable solution if you want features like taking backup images. One of the things I researched and was told not to do because it would cause more problems than it would fix was to try building TWRP using [MENTION=3383960]Elektroschmock[/MENTION] 's LineageOS 15.1 device tree. My thought was that if I could get it to build properly, the decryption issue would be resolved. As I said, I was told that this would not work, but I did not really get a good explanation as to why it would not work nor was I told how I could most effectively handle it.
[Nexus 6  Original Android Development] Najeeb3344:
I saw the change log of los 16 when will be installable on my nexus 6?
[Nexus 6  Original Android Development] veesix:
Be patient, first rule is never ask for ETA. After all, LOS 16 isn't available for any device yet.
[Nexus 6  Original Android Development] BootloopedMillennials:
I think this needs to be mentioned because YOU keep asking this. One of the understood, unwritten rules of xda is not to ask developers for an eta, Estimated Time of Arrival, of builds.

The work is open source, if you are desperate build it yourself. If that isn't possible, there are other Pie builds available on xda and outside it.
[Nexus 6  Original Android Development] Najeeb3344:
Sorry I'm new, I don't know the rules also I just want to get information about build
[Nexus 6  Original Android Development] Elektroschmock:
Actually it should work using https://github.com/LineageTWRP/android_bootable_recovery

But you need to set some more flags for TWRP in the device tree.
[Nexus 6  Original Android Development] David B.:
Thanks [MENTION=3383960]Elektroschmock[/MENTION] ! One problem though: I still do not know what flags would need set, and beyond that, I still have not figured out how to build TWRP. I've seen the tutorial thread here, but it's so choppy that I find it impossible to follow.
[Nexus 6  Original Android Development] espionage724:
Hi, I recently picked up a N6 again, and I'm noticing a few issues (15.1-20181231-NIGHTLY-shamu):

1. Can't access Phone information (*#*#4636#*#* -> Phone information); it crashes and displays a "com.android.phone has stopped" error. According to this thread about AOSiP, they apparently fixed it?

2. I can't activate Visual Voicemail with T-Mobile; just displays "Can't activate visual voicemail"

3. Security & privacy -> Trust -> Android security patches; claims Vendor is out of date. The N6 doesn't seem to have a dedicated vendor partition, and as far as I can see, the last factory image was from October 1, 2017, and that's what is listed under About phone. I used the partitions from the n8i11f image though (T-Mobile-specific 7.1.1 factory image)

4. One time, my camera app wouldn't work (kept force-closing). The phone was plugged in to USB and fully charged. After rebooting the camera was fine. What would cause this?

Does anyone have any suggestions or information?

My carrier is actual T-Mobile (not a MVNO)

I've only tried this ROM with the included kernel

I flashed the radio and bootloader (I think boot as well) images from the N8I11F image (Oct 1 7.1.1 T-Mobile)

I'm coming from an iPhone with the same SIM and all functions worked fine (including visual voicemail; I de-registered from iMessage days ago)

Visual voicemail doesn't activate from the N8I11F stock image either

The 4636 dial code Phone information page works fine from the N8I11F stock image
[Nexus 6  Original Android Development] BootloopedMillennials:
This guy has a video guide, he's also a member on xda. He's building TWRP from mini omni twrp and mini lineageos twrp sources. I'm not sure it'll be wise to use either of those sources to build twrp for the shamu, the mini omni is the most up to date with a 8.1 branch.

https://www.youtube.com/playlist?list=PLRJ9-cX1yE1kzxSkdZSG_h_f-GDNmSmAl
[Nexus 6  Original Android Development] David B.:
This is excellent! Thanks for sharing! Why didn't this come up when I was searching for tutorials on YouTube? :confused:

The thing about the mini omni branch is that I have not found an up-to-date device tree for the Nexus 6 for it. Either that or I have and do not understand what I have found.
[Nexus 6  Original Android Development] BootloopedMillennials:
Why not use the LOS branch [MENTION=3383960]Elektroschmock[/MENTION] provided? Then use the up to date LOS device tree.

Edit- You'd still need to figure out the flags to set though.
[Nexus 6  Original Android Development] Elektroschmock:
You can start with something like:

#TWRP

ifeq ($(WITH_TWRP),true)

BOARD_HAS_NO_REAL_SDCARD := true

RECOVERY_GRAPHICS_USE_LINELENGTH := true

RECOVERY_VARIANT := twrp

TARGET_RECOVERY_PIXEL_FORMAT := "RGB_565"

TW_EXCLUDE_SUPERSU := true

TW_EXCLUDE_TWRPAPP :=true

TW_INCLUDE_CRYPTO := true

TW_SCREEN_BLANK_ON_BOOT := true

TW_THEME := portrait_hdpi

TW_USE_TOOLBOX := true

endif

Not shure if everything is needed.
[Nexus 6  Original Android Development] David B.:
Okay thanks! This is starting to make some sense I think. I am still not sure where I would be setting those flags though. :confused:
[Nexus 6  Original Android Development] 0sA:
Hi :)

I am using Lineage OS 15.1 since July, updating it from time to time. I moved from LOS 14.1 which was almost a perfect ROM, but doesn't have any security updates.

After using LOS 15.1 for this few months I have to say it has few disadvantages compare to LOS 14.1.

- no one hand mode

- no split screen (it appears sometime ago, if I am right)

- no burn in protection for amoled screen

- worse camera app (no split second preview after taking a photo, so I don't know if it sharp or blurred, photos are often much more blurred than in other camera app)

- wosre battery - more power consumption, shutting down while taking picture if battery is lower than 40%

- some problems with encryption - once phone can't encrypt after entering pin, some error appears and it wanted to reset all data - forcing power off and trying boot again helps (and data saved! ;)

- problem with TWRP (newest version installed) - can't pass encryption screen, it shows that I entering bad password, even if it's correct, weird. I can enter recovery, but without this encryption pass I can't make a backup.

- problems with notifications - many apps (mostly communicators) don't show theirs notifications immediately, sometimes notifications appears when I power on the screen or when I lunch app manually.

- sometimes some lag while pressing power on button - screen powers on after about a second

That's all I remember. I don't use any custom kernel or xposed framework. I am using Greenify, but some apps, that aren't greenified, have problems with notifications too.

Any suggestions? Maybe I should try other kernel or even other ROM?

Thank you in advance ;)

Wysłane z mojego Nexus 6 przy użyciu Tapatalka