yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 XL Questions & Answers] malek777:
My battery is not good but I wouldn't say its terrible . It drains pretty quick on standby so I turned off AOD. It drains pretty quick too during usage. I don't think it's a hardware problem, more of poor optimisation. I don't think the battery on the next pixels will be much greater even with a 4000 mah battery because Google relies heavily on sending information back to its servers hence data is always working in the background. Ads are starting to pop up everywhere in most of Google's apps if youve noticed.
[Google Pixel 3 XL Questions & Answers] Paz9:
Curious what would happen if you restrict Android system in battery manager, does anyone know if it's bad in any way?
[Google Pixel 3 XL Questions & Answers] gettinwicked:
So, I checked out Accubattery, and it shows my battery health at 97%, so, maybe it's not the battery after all. I'm still getting 5+ hours SOT, but I was getting that before while having the battery last WAY longer. I actually called Google, and they want to send me a replacement, but, all my funds are tied up in a home loan, so, I can't do it until we close... End of May I'll have a replacement lol.

Thanks for your suggestion though!
[Google Pixel 3 XL Questions & Answers] zetsumeikuro:
Good luck! But sounds like you get better battery life than I do overall! I have a brand new device due to warranty circumstances and I have to charge everyday. But I am a power user so it is to be expected, but I was never impressed with the battery life on the XL 3. Overall the 3 XL has very average to subpar battery life. Their refurbished warranty devices are also a gamble, ranging from ones with mechanical defects to large scratches on the screen!
[Google Pixel 3 XL Questions & Answers] gettinwicked:
Soo, Digital Wellbeing may be the culprit, at least for me. Uncheck the usage access for DW, then restrict battery and uncheck background data. Let me know if this helps!

I updated to Q beta 3, and my battery life improved, but I then read somewhere that DW might be affecting battery life, so I did the above. Unfortunately, I didn't wait a day or two to see if Q was the reason for better battery life, so, definitely try this and let me know. I went from maybe 15-16 hours of battery life to off the charger at 6:30 and still almost 40% at 10pm. My phone showed the battery would last until about 8:30am when I went to sleep. This is where my phone was when I bought it. Anyway, hope this helps!
[MeMO Pad 7 Original Android Development] lambdadroid:
Arch Linux is an independently developed, x86-64 general-purpose GNU/Linux distribution that strives to provide the latest stable versions of most software by following a rolling-release model. The default installation is a minimal base system, configured by the user to only add what is purposely required.¹

NOTE: The Arch Linux packages are no longer updated. Consider taking a look at the postmarketOS port instead.

Introduction

With Android 5.0 (Lollipop), the ASUS MeMO Pad 7 (ME176C(X)) was updated with UEFI boot, making it possible to boot any Linux distribution on it. archlinux-me176c aims to make Arch Linux fully work on the ASUS MeMO Pad 7 (ME176C(X)). It provides additional packages and documentation for using Arch Linux on this device.

With me176c-boot, Linux can be installed in dual/multi boot configurations together with Android. Arch Linux is a minimal distribution, therefore most of the setup (partitioning, installing a desktop environment, ...) will be left up to you. However, it also allows you to customize it entirely to your liking, and configure it for any use case you can imagine.

Installation

Warning: Although the wiki article below provides many recommendations, at the end, setting up the installation will be left up to you. There is no step-by-step guide. If you have never used Arch Linux before, you may want to try it on a desktop PC or virtual machine first. You can easily brick your tablet if you don't know what you are doing!

All documentation is available in ASUS MeMO Pad 7 (ME176C(X)) - ArchWiki. As a wiki article, I encourage everyone to contribute and share their experiences with everyone else.

If you need any help or further suggestions, do not hesitate to ask in this thread!

FAQ

Can I use other Linux distributions on this tablet? Yes! However, you will need to set up more things manually. There are a few notes for this in linux-me176c: Porting - Using linux-me176c in other distributions

Source Code

Documentation: ArchWiki

Packages: archlinux-me176c (GitHub)

¹ Source: https://wiki.archlinux.org/index.php/Arch_Linux (GFDL 1.3)

XDA:DevDB Information

Arch Linux for ASUS MeMO Pad 7 (ME176C(X)), Tool/Utility for the Asus MeMO Pad 7

Contributors

lambdadroid

Source Code: https://github.com/me176c-dev/archlinux-me176c

Version Information

Status: No Longer Updated

Created 2019-04-02

Last Updated 2020-05-12
[MeMO Pad 7 Original Android Development] lambdadroid:
Reserved
[MeMO Pad 7 Original Android Development] shim80:
Hi!

Seem awesome!

Do this have a full hardware accelerated graphics support?

Is this compatible with k013 ?
[MeMO Pad 7 Original Android Development] lambdadroid:
Yes. (It has Intel Graphics just like on normal Intel PCs, and therefore OpenGL and Vulkan support is provided by Mesa.)

Yes, K013 == ME176C(X).
[MeMO Pad 7 Original Android Development] shim80:
Thanks for the answers.

Also, if wan't to go back to Android, can I do it?
[MeMO Pad 7 Original Android Development] lambdadroid:
The recommended setup is to keep Arch Linux on an external SD card. Then you can have Android and Arch Linux installed at the same time ("dual boot").
[MeMO Pad 7 Original Android Development] f35suarezj:
[MENTION=6833678]lambdadroid[/MENTION] man when running

# pacman -Sy me176c

or trying to install base packages it says

error: me176c:signature from "lambdadroid is known trust error: failed to update me176c (invalid or corrupted database (GPG signature)

when running

$ pacman-key --finger keyid

it says pub

ed25519 2017-08-10 [sc] [expired: 2019-08-17] uid [expired]

should I try an offline instalation?
[MeMO Pad 7 Original Android Development] lambdadroid:
No longer updated

The binary repository has been down for a while now - I have no plans to update the Arch Linux packages again. This is mostly because I'm no longer using Arch Linux myself on the me176c / K013.

However, as a replacement a postmarketOS port with same functionality has been around for a while. Since it's much more comfortable to install (simply through Fastboot/SD card with a large number of selectable UI interfaces) I prefer it over Arch Linux at this point. I would recommend it to anyone who would like to use a more standard "Linux" distribution on me176c / K013.
[Miscellaneous Android Development] Shobit Joura:
This is a module to simple replace fakestore with playstore and install droidguard helper in los microg forks, as many prefer microg over gapps and for an easy life they just install los microg for but los microg comes with fakestore and no droid guard helper which breaks safetnet and user cant use paid apps as yalp store/aurora store downloaded paid apps doesnt pass license verification

for making users work easy i just made this module to do all systemlessly and making ** OTA's INSTALLABLE ** and this thing ota survivable.

LINK: https://github.com/Shabinder/Replace-fakestore-with-playstore-mod-and-install-Droidguard

now we can install paid apps from playstore and can pass safetynet without any issue(add droidguard in magisk hide)

NOTE: In some cases if during safety net check droidguard stops then plz intall the apk as an update over installed app by extracting the module zip in /system/priv-apps/droidguard

For updating playstore download fdroid and add this repo in it " https://nanolx.org/fdroid/repo/?fin...6FE93D14596B381D75BE83A1D616E2D44A12654AD015"

NEED HELP OR REPORT ISSUES: WRITE TO [MENTION=666544]shabin[/MENTION]DER ON TELEGRAM

###credits: MARVIN FOR MICROG , NANOLX FOR MODDED PLAYSTORE , TECHNO SHAB(aka Shabinder) for this module.
[Miscellaneous Android Development] the_Pan:
Are there any news on this?

I tried the last version, but as already written on GitHub, it also ended in a bootloop.
[Miscellaneous Android Development] Bracher:
Unfortunately I had the same problem - ended in bootloop
[Android Studio] mgarnier:
I'm building a set of VR units for my Biology classroom and I want the devices (Moto G4) to be a single use device.

Should I teach myself Android Studio and make them COSU devices by building a custom rom?

The VR apps I will be using are free and ready to go, like Google Expeditions and such. I just need to lock down the devices so they can't do anything but run those VR apps. These kids will tinker and hack their way into anything if you give them the chance.

I'm willing to teach myself Android Studio, I'm sure it would be a fun experience, but is it necessary? Is there a more simple way?

Thanks in advance for your advice and support!
[General Questions and Answers] asifafy:
Hello, I am a blogger. I am not android developer. I want to create a app for my website. Actually I want to create apps for individual posts.

I already tried by using free apk creator online. But the problem is all those apk file have no licence and bla bla bla... How can I create it through proper way with responsive look.

Kindly help me...

Thanks in advanced.
[Vivo V9  Questions & Answers] Jeddyy:
Good day, can anyone give a gcam version compatible for vivo v9? I've been trying many version but all of it crashes. Thanks in advance :o
[Vivo V9  Questions & Answers] Scar7x:
wont work because of locked camera2api its bootloader is locked and cant be rooted also I tried oem unlock and enabling camera 2 api by adb and fastboot it still doesnt work
[General Questions and Answers] MaknaeFx:
I have an Moto C Plus / MTK XT1725

Android 7.0

Already check with Engineer mode and dont appear Camera option in Hardware Testing

Already check buildprop and the value dont appear

I dont know what more i need to do

My phone dont support Camera2Api (appears Legacy)

Please help :(
[P3300, MDA Compact III ROM Development] garymeg:
Hi is it possible that someone could post the cab file for the large start menu used in this rom?

Artemis Touch 4.02 WM6.1 WWE ROM, 5.2.19199 (Build 19199.1.0.0) (Full, Lite and Vanilla)

or a zip/rar of the files neaded to be placed in the windows folder
[P3300, MDA Compact III ROM Development] farukb:
link to a thread where you can find it with all other HTC apps...at least that's what they said:)

or a direct download here
[P3300, MDA Compact III ROM Development] Dreetje:
Installed this version on my kaiser and it didn't work?! When i installed it and rebooted my phone I tried 2 access it from the settings menu it just poped out really quickly and nothing appeared. Does anyone have a solution for thiS?
[P3300, MDA Compact III ROM Development] broadbeans:
Doesn't work on my Artemis as well. No change after reboot :-(
[P3300, MDA Compact III ROM Development] phoenix2149:
It works on my P3300 WM6 (original HTC download)

Installed CAB and direct RESET and it works
[Xiaomi Mi Mix 2S Questions & Answers] Phoque_You:
Hi,

A few days ago, I was on official Pixel experience rom. Fingerprint unlock started to don't work sometimes. I had to wake up screen with power button before using fingerprint sensor to unlock the phone.

Yesterday, my phone just stopped to react to any fingerprint unlock attempt. I thought that was a software issue, so I decided to migrate to LineageOS. That was a success. However fingerprint sensor doesn't work. Worse : fingerprint settings just disappeared in phone settings.

I would like to know if there is a way to test the hardware part. Or if anyone has gone through this before, any advice will be appreciated.

Thanks.
[Xiaomi Mi Mix 2S Questions & Answers] M1chiel:
I had the same, but I do not remember exactly how I solved it. I think by clean flashing a MIUI developer rom, booting into system, flashing twrp again, format data, and flashing my custom rom.
[Xiaomi Mi Mix 2S Questions & Answers] Phoque_You:
Thank you for your answer. Do you think I can do a full nandroid backup of my current setting, then format to install MIUI, then restore my backup so I don't lose my data?
[Xiaomi Mi Mix 2S Questions & Answers] M1chiel:
You should. I had difficulties with restoring a Nandroid backup, but that was probably related to encryption. So by removing your PIN or password it should work. I used the app Migrate to restore my data.
[Xiaomi Mi Mix 2S Questions & Answers] Phoque_You:
Thanks. I gonna try that when I get some free time ;)
[Xiaomi Mi Mix 2S Questions & Answers] Phoque_You:
OK, that was a hardware issue. Everything works fine now. The fingerprint sensor flat cable was mounted fold. This must be the reason.

If someone has the same problem, it's easy to fix it by yourself. You can find cheap tools and part on aliexpress, and disassembly videos on youtube. This took me 30min and it was the first time I opened a phone.

The last photo show the new fingerprint sensor mounted unfolded ;)
[Google Daydream VR] jigs4wkiller:
Thanks for the takeover :highfive:
[Google Daydream VR] einholzstuhl:
Oh my god,

such high prais from the gcam god himselve!

I'am fainting :crying:
[Google Daydream VR] einholzstuhl:
UPDATE! 15.10.2019

-> Daydream unlocker Beta for Android 10 released

-> Quick fix for bootloop on Android 10 addet to bug list

UPDATE! 08.10.2019

A couple people addet to the feedback list.

Daydream unlocker marked as only Android 9 and below compatible currently

UPDATE! 16.09.2019

XDA randomly adds brackets to my linked pictures wh...es

[B]2.[/B] Manual has been redone entirely
[Google Daydream VR] bschmidy10:
Thank you so much for this ♥️♥️♥️ works like a charm, but the module changes my device ID to a Google pixel, which causes apps particularly for my OnePlus to not function... Is there a way to fix this?
[Google Daydream VR] einholzstuhl:
The ID change is pretty much the point of the module which fakes a device that is Daydream compatible.

So I do not think that it would be possible for Daydream and youre One Plus apps to work at the same time.

(At least not with this method.)

Jigs4wkillers suggestion:

It could work if you edit youre One Plus apps and remove the device check from them.

My suggestion:

Only activate the Daydream module when you want to use Daydream and after use disable it.

Thanks for the feedback!
[Google Daydream VR] bschmidy10:
In the past I have just edited the build.prop to add in the vr bits and it has worked. , The problem was that every rom update would undo my work lol. Is it possible to have a module only add/fix the build.prop file and permissions and not touch device ID? Or are they locked together?

I will search for the correct build.prop file to edit to see if I can get it working without the module enabled and reply back again.

If not I will happily follow your advice to enable and disable as needed.

Thank you ??

***Update***

After researching, I see what you mean about the device ID change. It seems that certain apps require it and others work with just the vr permissions edit. You definitely have the best solution, would there be any benefit to setting to to pixel 3 xl vs OG pixel? Or not important?

And I do not expect anything , but it would be pretty great if you could make a "lite" version of this module without the device ID change or if you could tell me where to look for how to edit it myself. I was unable to find the same "handheld.core" build.prop file I used back on my OnePlus 3 (running nougat/Oreo) to change so I wasn't able to make the edits myself.

Once again, thank you very much. I can't believe there isn't more of a demand for this!

Still so frustrating Google won't just let qualified devices work properly with daydream
[Google Daydream VR] einholzstuhl:
That is because youre Build.prop got overwritten by the update propably.

You can try it the way you think it would work and report back :)

Well it is Google, they like to have exclusive features for their own devices, but I do not think that is the case for Daydream.

Iam not sure if that is still the case but (something similiar was implemented for cardboard which had resolution QR-codes):

Every Smartphone has a certain display size and resulution.

The Google Pixel has about the same size as the MiA1 so I chose that one for the module. (That was the thought behind it)

The module was intendet to be univerally compatible with any phone. So I would have to make a module for every phone in existence which would not really be worth the amount of work.

So the lite variant should be done individualy if needet.

The build.prop is located at:

/system/build.prop

You might also need to change the System.prop

You can compare the build.prop from the module directly with the one in youre device and make changes accordingly.

Daydream is very niche so that is the sad reality of it. There are almost no devices on the market which are Daydream compatible so that will probably not change any time in the future.

Thank you again for youre feedback, much appreciated!
[Google Daydream VR] bschmidy10:
Thank you ?
[Google Daydream VR] Kleva94:
First of all, thanks a lot for the module.

I had some distortions in VR on my OnePlus 7 Pro.

So I changed the values in system.prop to "Pixel 3 XL" and "crosshatch" and it got much better. Most likely because of the similar screen ratio.
[Google Daydream VR] einholzstuhl:
It might be a good idea to release more version for different screen ratios.

Thanks for the input!

Edit:

A couple more screen resolutions addet
[Google Daydream VR] redpoint73:
How did you get the module working on the OP 7 Pro? I downloaded the 2960x1440 version (seemed closest to the phone's 3120x 1440 resolution). When flashing in Magisk (19.3), it says "installation failed".

I tried flashing in TWRP (sometimes works for modules that don't install straight from Magisk), but it says "invalid zip format". So maybe not meant to flash in TWRP.

Any info on how you did it would be appreciated.
[Google Daydream VR] jigs4wkiller:
I will check the module maybe I made a mistake

Edit:

Zip reupload, please download again.
[Google Daydream VR] redpoint73:
That one worked. Installed the module anyway. Now to try the rest of the steps!

Thanks for your work.
[Google Daydream VR] pbergonzi:
Using either the Magisk module download from github or the 2160 x 1080 module from the list on google drive "This zip is not a Magisk module."
[Google Daydream VR] einholzstuhl:
Try to update Magisk to the newest version and check if Magisk is working correctly.
[Google Daydream VR] pbergonzi:
Silly me--the google drive re-zips the file to download it--I had to remove it from the initial zip to get to the folder that held the correct zip.

And the one I had downloaded from github needed to have the files removed from the unzipped folder and zipped.

Thanks for your help, and also wondering if you can make a 2340 x 1080 for the OnePlus 6t? Or if you'll tell me what to edit in one of your zips, I can make the edit myself.
[Google Daydream VR] jigs4wkiller:
It's not really necessary to use the props from a device with the same phone resolution we only added more device with different resolutions because of the user feedback.
[Google Daydream VR] pbergonzi:
Thank you.

On testing different iterations of the enabler resolution some behaved erratically--one seemed to stagger a little on the edges of things while turning, one seemed to have slightly smeared edges but was more pixellated.

Nevertheless, the experience is overall a good one, and it sure was nice sharing a roller-coaster with Santa!
[Google Daydream VR] bukeyolacan:
Where is system.prop file? And what is crosshatch setting?
[Google Daydream VR] masoodsuliman:
Hi, thank you for the guide. I followed all the steps exactly as described twice. However, when I try to launch be it will tell me to place the phone in the headset, when I do it crashes back to the app. What should I do next? Thanks

P.S. I have a one plus 7 pro

PSS. I cannot see daydream VR on the play store
[Google Daydream VR] einholzstuhl:
1. Reset the installation (Can be found in the guide)

2. Proceed to variant 2

or:

Try an alternative Magisk module (resolution)

(You can also try Pixelify in the Magisk download section, but it does not work well for me at least.)

If you did all that and it works or does not please report back!

In the Daydream Enabler:

MagiskModuleName/common/system.prop

otherwhise in:

system/build.prop

or:

system/system

Note:

system.prop is unique to Magisk and you will not find it in the Android/Linux file system.

That is the device name of the Pixel 3 XL.
[Google Daydream VR] masoodsuliman:
Thanks for the quick reply. So when I opened the daydream app, I clicked on the daydream icon, and it would then crash back to the app. So instead I just clicked on the app, I wanted to use under the app section and it worked.
[Google Daydream VR] einholzstuhl:
If I unterstand it correctly:

So the Daydream app on its own does crash if you go into VR mode.

But if you open a VR app from the app drawer VR works like it should.

I will add it to the bug list, thanks!:good:
[Google Daydream VR] masoodsuliman:
That is correct, thanks!
[Google Daydream VR] pbergonzi:
Are you sure it was VR mode and not cardboard mode?
[Google Daydream VR] einholzstuhl:
I think you mean Daydream mode instead of Cardboard mode.

But if that would be the case a notification should pop up that tells you to change into Daydream mode.
[Google Daydream VR] pbergonzi:
Oh yeah, agreed--"Daydream vs Cardboard", rather than "VR vs Cardboard."

The first time or two I tried this using another method, Daydream would crash, but still leave me with some other apps started from app rather than Daydream running in Cardboard mode, with me thinking that Daydream had worked, when in fact it had not--I was watching and performing things in Cardboard mode, which for one thing, lacked the Daydream controller but still working because of motion or gaze control.
[Google Daydream VR] pflatlyne:
I installed it as per the directions on a Nexus 6 with Lineage OS 15.1. The phone would not go past the lock pattern. It was laggy to bring it up with the power button and when it did come up it would freeze up for a second when you tried to enter the pattern then go blank. You could get it to go back to the pattern ,then it would just do it again. I went into recovery,backed up and deleted locksettings.* from /data/system and it let me in, but hung or rebooted randomly and gave errors that trebuchet was crashing. After several attempts I managed to get into magisk manager and remove the module and that at least got the phone working again.
[Google Daydream VR] einholzstuhl:
Edit: Can you give us a log please?
[Google Daydream VR] simon_6162:
To save someone an hour of their life - If you are trying this and get a prompt telling you to install the VR keyboard only to be taken to the play store where it tells you your device is incompatible, (and all daydream apps are shown as not compatible) force stop the play store app, then clear the cache and storage of it. After that all the daydream apps are listed as compatible.

(OP7 pro running OOS)
[Google Daydream VR] CombineCrab:
After installing this on my OnePlus 7 pro some of my other vr applications such as iVRy are rotated 90 degrees about an axis and some directions are inverted. Disabling it and rebooting fixed the issue.
[Google Daydream VR] CombineCrab:
I am having problems using the Unity Instant preview app while this module is enabled. The app seems to crash on the phone when started by Unity, in contrast, without the module the app works however loses support for daydream apps.