[TIP/GUIDE] Make your nVidia GPU work (Reposted) - Remix OS for PC

Finally got my Alienware X51 to work. It has the GTX 660 gpu.
Combine and try this boot flags and see which one works for you.
1. nomodeset
2. nouveau.modeset=0
3. nouveau.modeset=1
4. video=uvesafb
5. video=simplefb
6. i915.modeset=0
7. i915.modeset=1
My X51 works beautifully with nouveau.modeset=1 i915.modeset=0
Thanks to: winsock2 reddit user
source:
https://www.reddit.com/r/RemixOS/comments/42wylw/any_way_to_run_with_nvidia_gpu/
Click to expand...
Click to collapse
How do i enter this?
# Reboot/Boot and press ESC key to go to main grub menu
# Press E
# Highlight the line that says kernel, press E.
# Enter the above flag/flags right after "androidboot.hardware=remix_x86_64" (Use the arrow keys to go left or right)
# There should be a space between each of the flags
# Optional: go to the end of the line and type DEBUG=1
# Press Enter......Press B to boot.
Okay. I finally got the right boot flags. How do I make it permanent?
# For EFI booters, navigate to X:\RemixOS\efi\boot and edit/add the flags to your grub.cfg
# For Legacy booters, navigate to X:\RemixOS\ and and edit/add the flags to your menu.lst
* Replace X:\ with the drive letter on which you installed your RemixOS
* You can open it in any text editor...but I prefer Notepad++
* Be sure to back up your grub.cfg or menu.lst before making any changes...so that you can always fall back to a working configuration if you mess up.
Happy Remixing!!!

Thanks. This seems to work and the MXPlayer is now playing all file formats.

where do i type this?

kushsingh said:
where do i type this?
Click to expand...
Click to collapse
Check the first post....i added the steps

Is there any way to save the kernel settings so I don't need to write them every time?

skitmos said:
Is there any way to save the kernel settings so I don't need to write them every time?
Click to expand...
Click to collapse
in menu.lst file

You_KS said:
in menu.lst file
Click to expand...
Click to collapse
I'm sorry, I'm new to this. Can you be more specific on where I can find the file, and which part of it to edit, and how?

Ash110 said:
I'm sorry, I'm new to this. Can you be more specific on where I can find the file, and which part of it to edit, and how?
Click to expand...
Click to collapse
It's in C:\RemixOS (assuming C is the drive where you installed) open the file as text and you'll find the kernel line you edit at boot

Isn't this uefi? Legacy is different

Ash110 said:
I'm sorry, I'm new to this. Can you be more specific on where I can find the file, and which part of it to edit, and how?
Click to expand...
Click to collapse
Depends on whether you are using UEFI or BIOS
AmoraRei said:
Isn't this uefi? Legacy is different
Click to expand...
Click to collapse
For LEGACY, edit the file found here: X:\RemixOS\menu.lst
For EFI, edit the file found here: X:\RemixOS\efi\boot\grub.cfg
Note 1: Preferably, use Notepad++ to edit those files
Note 2: Replace X with the drive letter where you installed RemixOS

Can we change the DPI?

AmoraRei said:
Can we change the DPI?
Click to expand...
Click to collapse
Put DPI=xxx (replace with any dpi value)

freelancer81 said:
Put DPI=xxx (replace with any dpi value)
Click to expand...
Click to collapse
And where would that be found?

Fermi may working great. But Maxwell may not. Need Linux kernel 4.6
Sent from my Nexus 6P using Tapatalk

Ash110 said:
And where would that be found?
Click to expand...
Click to collapse
A little googling would have answered your question....
common DPIs are 120, 145, 160, 180, 200, 220, 240....
play around....and see which works best for your monitor/screen.

Houge_Langley said:
Fermi may working great. But Maxwell may not. Need Linux kernel 4.6
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I am not sure bro....
So for now, the only option is to try those boot flags and if it works....Great.
If it does not....we just have to wait for a better fix or upgrades to the 4.6 kernel.

freelancer81 said:
I am not sure bro....
So for now, the only option is to try those boot flags and if it works....Great.
If it does not....we just have to wait for a better fix or upgrades to the 4.6 kernel.
Click to expand...
Click to collapse
Yes, i got this info from Phoronix News
http://phoronix.com/scan.php?page=news_item&px=NVIDIA-Blobs-In-Linux-Firmware
Sent from my Nexus 6P using Tapatalk

freelancer81 said:
A little googling would have answered your question....
common DPIs are 120, 145, 160, 180, 200, 220, 240....
play around....and see which works best for your monitor/screen.
Click to expand...
Click to collapse
Oh no! I know what DPIs are, having played around with them on my phone. Idk where to change DPI in remix OS

Ash110 said:
Oh no! I know what DPIs are, having played around with them on my phone. Idk where to change DPI in remix OS
Click to expand...
Click to collapse
ah well.....your question confused me.
anyways....if you read the previous posts, you would know where or how to put it.
to test it first, go to the grub bootloader and edit the lines to add the DPI=xxx
if you find a dpi that works great on your display, you can permanently set it in your menu.lst or grub.cfg

freelancer81 said:
ah well.....your question confused me.
anyways....if you read the previous posts, you would know where or how to put it.
to test it first, go to the grub bootloader and edit the lines to add the DPI=xxx
if you find a dpi that works great on your display, you can permanently set it in your menu.lst or grub.cfg
Click to expand...
Click to collapse
I checked my menu.lst, but I really couldn't find the dpi thing. Maybe I deleted it or something? Where is it supposed to be?

Related

I booted from my flashdrive, now I get a linux prompt

https://i.imgur.com/qfuKKFQ.jpg <- Here's what I get.
I downloaded release_Remix_OS_for_PC_64_B2016020201_Alpha_EFI.zip from the Official Website. Opened the tool inside, and copied the files into my USB 3.0 flash drive using it. Write speeds are higher than 20MB/s. I have a UEFI BIOS. I get the same thing on both Resilient mode and Guest mode. I selected Resilient mode on first launch and the system went through the first launch steps.
When you get to the boot choice of RemixOS remove 'quiet' from the line when TAB and then 'e' for editing it, to show what's going on @ boot time.
most time we solve this by deleting recreating data.img
I hope that helps you
ecksdeeay said:
When you get to the boot choice of RemixOS remove 'quiet' from the line when TAB and then 'e' for editing it, to show what's going on @ boot time.
Click to expand...
Click to collapse
I did that. But this is all I could take a picture of. http://i.imgur.com/7rseNNe.jpg I have no clue what any of it means.
I opened it in guest mode.
imadlatch said:
most time we solve this by deleting recreating data.img
I hope that helps you
Click to expand...
Click to collapse
I dont know how to do that. I cant seem to be able to open the ISO that was in the zip file I downloaded. However, I formatted my flashdrive and used the included tool to reinstall Remix OS. It didnt help.
on the edit line you removed 'quiet' from, put 'DEBUG=1' or just put the '1' on the DEBUG= if it's showing ? I forget if it is but it will go through like before but this time will stop twice where you have to type 'exit' for it to proceed (twice-I repeat!) maybe that'll help? or @imadlatch is more than likely correct?
ecksdeeay said:
on the edit line you removed 'quiet' from, put 'DEBUG=1' or just put the '1' on the DEBUG= if it's showing ? I forget if it is but it will go through like before but this time will stop twice where you have to type 'exit' for it to proceed (twice-I repeat!) maybe that'll help? or @imadlatch is more than likely correct?
Click to expand...
Click to collapse
Here's what I got doing that. http://imgur.com/a/SL1rQ
I never got the second exit prompt. I just got the errors in this https://i.imgur.com/sGo2EQ5.jpg image over and over.
SELinux error. When installing on hardrive the selinux command is passed to the boot line (I'm only guessing here but if you could maybe add this) 'androidboot.selinux=permissive' worth a try?...what are you using as your machine? send feedback from here http://goo.gl/kt1bwC using the Google form https://goo.gl/pcRswT
ecksdeeay said:
SELinux error. When installing on hardrive the selinux command is passed to the boot line (I'm only guessing here but if you could maybe add this) 'androidboot.selinux=permissive' worth a try?...what are you using as your machine? send feedback from here http://goo.gl/kt1bwC using the Google form https://goo.gl/pcRswT
Click to expand...
Click to collapse
androidboot.selinux=permissive is present there by default. Im using a lenovo ideapad y510P with core i7 4700MQ, 8 Gigs of RAM and dual Nvidia GT 755M.
incognitonk said:
Nvidia GT 755M.
Click to expand...
Click to collapse
Nvidia is the problem then. ...
ecksdeeay said:
Nvidia is the problem then. ...
Click to expand...
Click to collapse
Really? Oh well, guess Im gonna be playing the waiting game then.
Thanks for everything up until now.
Search as I think there are work arounds @incognitonk
incognitonk said:
https://i.imgur.com/qfuKKFQ.jpg <- Here's what I get.
I downloaded release_Remix_OS_for_PC_64_B2016020201_Alpha_EFI.zip from the Official Website. Opened the tool inside, and copied the files into my USB 3.0 flash drive using it. Write speeds are higher than 20MB/s. I have a UEFI BIOS. I get the same thing on both Resilient mode and Guest mode. I selected Resilient mode on first launch and the system went through the first launch steps.
Click to expand...
Click to collapse
Its look like its because of your nvdia GPU isssue , don't worry we have solution for this
Select resident mode , don't press enter , press tab you will get into edit mode.
At the end after space write this line - " nomodeset vga = 0x34C "
Without the quote .
Press enter , enjoy remix ☺☺
Hit thanks if it help
mdezazrock said:
Its look like its because of your nvdia GPU isssue , don't worry we have solution for this
Select resident mode , don't press enter , press tab you will get into edit mode.
At the end after space write this line - " nomodeset vga = 0x34C "
Without the quote .
Press enter , enjoy remix ☺☺
Click to expand...
Click to collapse
Thank you, It definitely did help. However the resolution is all wonky now. I have a 1080p screen. The images are all grainy and stretched out. Also, i can see the linux prompt blinking in the background. Anything I type on the keyboard will be entered there. Hence, if i type "reboot" and hit enter, the system will reboot.
I also tried the workarounds in this reddit post: https://www.reddit.com/r/RemixOS/comments/42wylw/any_way_to_run_with_nvidia_gpu/czenutg
But none of them helped either. I get the same issues; the poor resolution and the blinking prompt.
incognitonk said:
Thank you, It definitely did help. However the resolution is all wonky now. I have a 1080p screen. The images are all grainy and stretched out. Also, i can see the linux prompt blinking in the background. Anything I type on the keyboard will be entered there. Hence, if i type "reboot" and hit enter, the system will reboot.
I also tried the workarounds in this reddit post: https://www.reddit.com/r/RemixOS/comments/42wylw/any_way_to_run_with_nvidia_gpu/czenutg
But none of them helped either. I get the same issues; the poor resolution and the blinking prompt.
Click to expand...
Click to collapse
I don't know the blinking error solution , my friend also have that same problem , but there is a easy solution for resolution -
Root remix os , open any rooted browser , go to system folder , then open build.prop , edit the file , just add a line at the end
"ro.sf.lcd_density=150"
Write that line without quote , save build.prop , and change the number between 140 to 210 , see which one looks better on your monitor , have fun exploring remix ☺

remix os mouse pointer issue

well i booted up remix os on my laptop and see that the mouse pointer isnt the traditional arrow....its kind of transparent and is round!!!
plz help me to get the actual pointer on this thing>>>
Idk some people get different one which is weird. Lol you would have to use remix tool too extract system.img and find that file or root it and use a root browser
Sent from my SM-N920T using Tapatalk
If you are using a multi-touch track pad it shows the mentioned pointer. If you use a traditional mouse you get a traditional pointer.
rajarshi.banerjee00 said:
well i booted up remix os on my laptop and see that the mouse pointer isnt the traditional arrow....its kind of transparent and is round!!!
plz help me to get the actual pointer on this thing>>>
Click to expand...
Click to collapse
Tried and tested method :
Go to system/usr/idc
Open ETPS_2_Elantech_Touchpad.idc
replace the line "touch.gestureMode = spots" by "touch.gestureMode = pointer"
Now Reboot
sacredev said:
Tried and tested method :
Go to system/usr/idc
Open ETPS_2_Elantech_Touchpad.idc
replace the line "touch.gestureMode = spots" by "touch.gestureMode = pointer"
Now Reboot
Click to expand...
Click to collapse
does it mean i have 2 root?
sacredev said:
Tried and tested method :
Go to system/usr/idc
Open ETPS_2_Elantech_Touchpad.idc
replace the line "touch.gestureMode = spots" by "touch.gestureMode = pointer"
Now Reboot
Click to expand...
Click to collapse
thanks
rajarshi.banerjee00 said:
does it mean i have 2 root?
Click to expand...
Click to collapse
Either root. Or use remixtools to ecompile syatem img. And do the edits than repack the .IMG
Sent from my SM-N920T using Tapatalk
Doesn't work for me... :crying:
sacredev said:
Tried and tested method :
Go to system/usr/idc
Open ETPS_2_Elantech_Touchpad.idc
replace the line "touch.gestureMode = spots" by "touch.gestureMode = pointer"
Now Reboot
Click to expand...
Click to collapse
I have changed it but didn't work!
plz give me another solution
sacredev said:
Tried and tested method :
Go to system/usr/idc
Open ETPS_2_Elantech_Touchpad.idc
replace the line "touch.gestureMode = spots" by "touch.gestureMode = pointer"
Now Reboot
Click to expand...
Click to collapse
I had to get new version from jide.com and now everything is ok
sadegh007 said:
I have changed it but didn't work!
plz give me another solution
Click to expand...
Click to collapse

Remix OS bottom bar is solid black

Hello,
I have just installed remix os. (dual os though)
Problem is, bottom bar is solid black that means I can not use multitasking. I have to close one app to open another one. I can not also open setting etc.
What is this happening
At the first boot I had this problem too, then system automaticly rebooted and I had that bottom bar now It is again gone. I have really low notebook, has 2gigs of ram and 1.4ghz of cpi even linux freezes time to time. But so far, remix os running like a dream.
Btw, I am using 64bit version if it matters.
thanks in advance
Conixcit said:
Hello,
I have just installed remix os. (dual os though)
Problem is, bottom bar is solid black that means I can not use multitasking. I have to close one app to open another one. I can not also open setting etc.
What is this happening
At the first boot I had this problem too, then system automaticly rebooted and I had that bottom bar now It is again gone. I have really low notebook, has 2gigs of ram and 1.4ghz of cpi even linux freezes time to time. But so far, remix os running like a dream.
Btw, I am using 64bit version if it matters.
thanks in advance
Click to expand...
Click to collapse
Check the autohide settings. Settings ==> Display ==> Autohide (and right click on taskbar if you can)
HypoTurtle said:
Check the autohide settings. Settings ==> Display ==> Autohide (and right click on taskbar if you can)
Click to expand...
Click to collapse
First of all thanks for reply,
And it is not what you say, it isn't hidin problem is
Where running apps and stats should be covered with solid black, (same border)
Conixcit said:
First of all thanks for reply,
And it is not what you say, it isn't hidin problem is
Where running apps and stats should be covered with solid black, (same border)
Click to expand...
Click to collapse
I think I had what you're describing and toggling the autohide fixed it (i think there was a mismatch between the setting value and the right click value).
That being said it might be better to try the 32bit version on your device; it should be easier on resources.
I'll go one farther and say that you should not be running the 64-bit at all on that notebook. You don't have the hardware to properly support it. Upon initial installation you should have seen a pop-up telling you to make sure you are using the 32-bit version based on your hardware.
ZiQn3zZ said:
I'll go one farther and say that you should not be running the 64-bit at all on that notebook. You don't have the hardware to properly support it. Upon initial installation you should have seen a pop-up telling you to make sure you are using the 32-bit version based on your hardware.
Click to expand...
Click to collapse
I totally agree but 64 bit version is the only version that supports EFI ,
Conixcit said:
I totally agree but 64 bit version is the only version that supports EFI ,
Click to expand...
Click to collapse
I'm fairly sure replacing the system.img, kernel, initrd.img and ramdisk.img with the 32bit ones and removing the _64 from the grub.cfg will boot with efi grub... if you want to try
HypoTurtle said:
I'm fairly sure replacing the system.img, kernel, initrd.img and ramdisk.img with the 32bit ones and removing the _64 from the grub.cfg will boot with efi grub... if you want to try
Click to expand...
Click to collapse
What possibly can go wrong anyway?
It's my side OS anyway.
I'll try as soon as I reach home.
Conixcit said:
What possibly can go wrong anyway?
It's my side OS anyway.
I'll try as soon as I reach home.
Click to expand...
Click to collapse
I had the same problem, I fixed it by adding
ro.remixos.no_wallpaper=true
in build.prop where other ro.remixos options are configured
and also remove the 2 ffmpeg lines to remove blinking issue...
If you cannot open any application plug in any usb, es file explorer will appear then enable root explorer option
and navigate to /system to edit build.prop and finally edit it..
updesh94 said:
I had the same problem, I fixed it by adding
ro.remixos.no_wallpaper=true
in build.prop where other ro.remixos options are configured
and also remove the 2 ffmpeg lines to remove blinking issue...
If you cannot open any application plug in any usb, es file explorer will appear then enable root explorer option
and navigate to /system to edit build.prop and finally edit it..
Click to expand...
Click to collapse
where is exactly "build.prob" file.
I'm using Ubuntu
Conixcit said:
where is exactly "build.prob" file.
I'm using Ubuntu
Click to expand...
Click to collapse
It's within the system.img; within RemixOS it's at /system/build.prop.
But I don't think this is a fix per say - yes it seems to work for some people; but this could be due to some data hangover from a previous version with this line present.
What I would try first is simply clearing data from SystemUI (and Settings) app.
HypoTurtle said:
It's within the system.img; within RemixOS it's at /system/build.prop.
But I don't think this is a fix per say - yes it seems to work for some people; but this could be due to some data hangover from a previous version with this line present.
What I would try first is simply clearing data from SystemUI (and Settings) app.
Click to expand...
Click to collapse
Already done that. Not helps
Letme try that file editing thing
HypoTurtle said:
It's within the system.img; within RemixOS it's at /system/build.prop.
But I don't think this is a fix per say - yes it seems to work for some people; but this could be due to some data hangover from a previous version with this line present.
What I would try first is simply clearing data from SystemUI (and Settings) app.
Click to expand...
Click to collapse
Can't find that build.prob file....
Conixcit said:
Can't find that build.prob file....
Click to expand...
Click to collapse
You're dual booting with ubuntu, right?
If so then just mount the system.img and you'll see it righg there.
mkdir rossystem && mount -t ext4 system.img rossystem
or if your using a system folder then it should be just in there.
I had the same problem, I fixed it by adding in build.prop
ro.remixos.no_wallpaper=true

[MOD] [GUIDE] [ADB] Change DPI density WITHOUT root

I'm Back on XDA!
So, are you tired of the small amount of informations that you can have on your HUGE screen? You are in the right place.
WHAT DO I NEED?
First things first, you need to enable Debug usb under Developer Options (if you don't know how to enable Dev. Options this isn't your place)
After that, you need ADB installed on your computer (Windows/Linux/Mac), you can find it here [url]https://forum.xda-developers.com/showthread.php?t=2588979[/URL]
HOW TO
With Developer Options ENABLED, connect your phone to your pc and launch adb. In ADB type this command
Code:
adb shell wm density xxx
where xxx is your custom DPI value. I found that values BELOW 527 will bug your quick toggles*
*It could depend by your installed theme, Thanks to @SPIDER-7 for reporting that.
HOW DO I RETURN TO THE DEFAULTS VALUES?
Cave_diver said:
To return to the defaults just use the sliders in settings-display-display size
Click to expand...
Click to collapse
SCREENSHOTS
http://i.imgur.com/JyodBYe.png
http://i.imgur.com/fsW1Qtd.png
DISCLAIMER
I'M NOT RESPONSABLE IF THIS PROCESS CREATED A THERMAL NUCLEAR DEVICE
AND / OR TURN YOU INTO FIRESTORM.
NOT RESPONSABLE IF SOMETHING HAPPEN DURING THIS MOD OR IF
YOU DO A MISTAKE DURING THIS PROCESS
I'm Italian so don't blame me for my english.
it works just fine! Thanks, @gsadv . keep it up!
Btw, I'm on value '500 and didn't notice any bugs . will challenge my G6 with lower values .
SPIDER-7 said:
it works just fine! Thanks, @gsadv . keep it up!
Btw, I'm on value '500 and didn't notice any bugs . will challenge my G6 with lower values .
Click to expand...
Click to collapse
Bugs on quick setting may depend by themes. For me 527 is fine, next step is try to get a smaller navbar
i'm going to try 527, but what is the default value if i decided to go back?
To return to the defaults just use the sliders in settings-display-display size
Sent from my LG-H870 using Tapatalk
Cave_diver said:
To return to the defaults just use the sliders in settings-display-display size
Sent from my LG-H870 using Tapatalk
Click to expand...
Click to collapse
original size 640

[Overlay] Enable Night Light, Auto-Brightness, Ambient Display & more on Treble ROM

[Overlay] Enable Night Light, Auto-Brightness, Ambient Display & more on Treble ROM
Hello.
By default, phhusson's generic AOSP Treble ROM is bare bones. That means it does not include features such as Night Light, Ambient Display, or Adaptive Brightness. Luckily all you need is the right overlay and you can bring these features back.
I tested this on the Huawei Mate 10 Pro and everything seems to work save for the lift-to-wake gesture. I am not sure if a simple overlay can enable that, as I already target the right boolean value for it. As for Adaptive Brightness, the lux and corresponding backlight values were borrowed from the Huawei Mate 9's framework-res.
Update 2/19/18
With the release of phhusson's Android 8.1 Oreo Treble GSI, I thought I would take the time to update my overlay as well with a new feature: Always on Display. You can download the overlay from the attachment in this comment, and install it using the same set of instructions below (don't install the overlay attached in this post if you want AOD). Please read the warnings carefully. I accept no responsibility for anything you do with your phone.
Update 2/6/18
I have updated the attached framework overlay to include the following features:
WiFi automatic wakeup
Pinner service for the default camera app and critical framework files
This should work on any device that can boot phhusson's Treble ROM.
Installation Instructions
Download the attached overlay
With root, push the overlay to /vendor/overlay. Create the folder if it doesn't exist.
Run the following command in a rooted terminal or ADB shell:
Code:
chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay;chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay/framework-res__auto_generated_rro.apk
Reboot
XDA Labs adds emojis in the command for some reason. Open this thread in a browser to get the right command.
Why do you need to run that command? Without it, the overlay won't be seen as installed and isn't enabled. I'm not sure why, but according to phhusson it's an SELinux-related issue and this command fixes that.
Enjoy!
What is the code?
独影阑珊 said:
What is the code?
Click to expand...
Click to collapse
Code:
chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay;chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay/framework-res__auto_generated_rro.apk
Why?
独影阑珊 said:
Why?
Click to expand...
Click to collapse
It does not work because you have included spaces in the command that are not there.
tusko5 said:
It does not work because you have included spaces in the command that are not there.
Click to expand...
Click to collapse
Oh, thanks.
Hello, not working on mate 9, all commands OK - no output error (I added mount -o rw,remount /system and mount -o rw,remount /vendor) to copy your files, but even after reboot no new things
EDIT : after "installing" the app (click on it with a root explorer), all options are now visible but not working
how can i get the root access on the rom?
It is also not working on honor v9 .
mrassol said:
Hello, not working on mate 9, all commands OK - no output error (I added mount -o rw,remount /system and mount -o rw,remount /vendor) to copy your files, but even after reboot no new things
EDIT : after "installing" the app (click on it with a root explorer), all options are now visible but not working
Click to expand...
Click to collapse
If you install it as a regular app, it won't work. It MUST be pushed to /vendor/overlay manually, and you MUST run that command.
javawppp said:
how can i get the root access on the rom?
Click to expand...
Click to collapse
Install phhusson's SuperUser from the Play Store.
独影阑珊 said:
It is also not working on honor v9 .
Click to expand...
Click to collapse
Did you follow the steps exactly? This can't be installed like a regular app.
you did'nt read my post
I did all you wrote (I even add mount -o rw,remount /system and mount -o rw,remount /vendor) and nothing changed
AFTER that, I install the apk from /vendor/overlay using a root explorer and now the options are visible, brightness is working (I didn't saw it first), night mode is also working, ambiant display is also working but the option to turn on phone on pickup don't work.
So my bad, I didn't test it so much
MishaalRahman said:
If you install it as a regular app, it won't work. It MUST be pushed to /vendor/overlay manually, and you MUST run that command.
Install phhusson's SuperUser from the Play Store.
Did you follow the steps exactly? This can't be installed like a regular app.
Click to expand...
Click to collapse
When I try to open it as a regular app , my phone display it can not open .I am sure it be pushed to /vendor/overlay .,and I have run the commed and rebooted system at least 5 times.but it still useless.(I am sorry my English is poor.)
独影阑珊 said:
When I try to open it as a regular app , my phone display it can not open .I am sure it be pushed to /vendor/overlay .,and I have run the commed and rebooted system at least 5 times.but it still useless.(I am sorry my English is poor.)
Click to expand...
Click to collapse
You are running phhusson's AOSP Treble ROM, correct? What device?
MishaalRahman said:
You are running phhusson's AOSP Treble ROM, correct? What device?
Click to expand...
Click to collapse
Yes,My device is Honor V9.
独影阑珊 said:
Yes,My device is Honor V9.
Click to expand...
Click to collapse
Ah, okay. That is the Honor 8 Pro's Chinese version. Have you tried this ROM? https://forum.xda-developers.com/honor-8-pro/development/rom-t3714728 I was told by the dev that he included these features by default. You flash it the same way with phhusson's ROM.
MishaalRahman said:
Ah, okay. That is the Honor 8 Pro's Chinese version. Have you tried this ROM? https://forum.xda-developers.com/honor-8-pro/development/rom-t3714728 I was told by the dev that he included these features by default. You flash it the same way with phhusson's ROM.
Click to expand...
Click to collapse
Thanks,I will try it.
Took me a while to get it to work on my mate 10 pro, then realised I had to manually set the permissions on the folder, and file for it to work. Great job!
Is there a way I could edit the minimum and maximum brightness it reaches?
Thanks again
etern1ty said:
Took me a while to get it to work on my mate 10 pro, then realised I had to manually set the permissions on the folder, and file for it to work. Great job!
Is there a way I could edit the minimum and maximum brightness it reaches?
Thanks again
Click to expand...
Click to collapse
Ah, I forgot about that. I believe the folder permissions are 755 and the APK should be 644, correct? As for setting the brightness, do you want to increase the minimum and lower the maximum of the adaptive brightness?
MishaalRahman said:
Ah, I forgot about that. I believe the folder permissions are 755 and the APK should be 644, correct? As for setting the brightness, do you want to increase the minimum and lower the maximum of the adaptive brightness?
Click to expand...
Click to collapse
Yeah, that sounds right I just matched the other folders and APKs. I was hoping to decrease the minimum (so it's darker), I don't notice a big effect on my mate 10 pro.
Is there a guide for going about this? I'm interested to learn how to make these sorts of modifications myself.
Cheers
etern1ty said:
Yeah, that sounds right I just matched the other folders and APKs. I was hoping to decrease the minimum (so it's darker), I don't notice a big effect on my mate 10 pro.
Is there a guide for going about this? I'm interested to learn how to make these sorts of modifications myself.
Cheers
Click to expand...
Click to collapse
Decompile my overlay. Look in /res/values/arrays.xml. Look at "config_autoBrightnessLcdBacklightValues" array and change the first item, <item>6</item> to <item>1</item>. Build the APK, sign it, and then push.

Categories

Resources