Related
I recently installed a new 4.3 rom and I love it except they don't include an option to disable the battery charging light. Is there anyway to disable this by editing rom files ect?
ajh305 said:
I recently installed a new 4.3 rom and I love it except they don't include an option to disable the battery charging light. Is there anyway to disable this by editing rom files ect?
Click to expand...
Click to collapse
If you are running CM 10.2, then go to System Settings...Display and lights...Battery light. Uncheck it. Not sure where it is on other roms,
gr8nole said:
If you are running CM 10.2, then go to System Settings...Display and lights...Battery light. Uncheck it. Not sure where it is on other roms,
Click to expand...
Click to collapse
I am running a ported rom called dirty unicorn. It is a pretty slick rom but it has no option to disable the battery light anywhere I have combed through every setting. So I was wondering if there is a system file I could modify to just disable it.
ajh305 said:
I am running a ported rom called dirty unicorn. It is a pretty slick rom but it has no option to disable the battery light anywhere I have combed through every setting. So I was wondering if there is a system file I could modify to just disable it.
Click to expand...
Click to collapse
i dont know about that, but there is an app called light flow that controls the led. i never tried it so i don't know its capabilities, but you could look @ it and see.
ajh305 said:
I am running a ported rom called dirty unicorn. It is a pretty slick rom but it has no option to disable the battery light anywhere I have combed through every setting. So I was wondering if there is a system file I could modify to just disable it.
Click to expand...
Click to collapse
I saw you over at that other forum! I've been going mad trying to find a solution. Try under "sound -> quiet mode" a bit of deep googling found that as a potential hiding spot for the setting. (I'm back on stock and don't want to flash DU without knowing if this can be disabled.) I poked around in the DU build.prop, and wasn't able to find anything there either.
bweN diorD said:
i dont know about that, but there is an app called light flow that controls the led. i never tried it so i don't know its capabilities, but you could look @ it and see.
Click to expand...
Click to collapse
i actually tried light flow and several other apps like that and they don't seem to be able to override the roms default.
moonrakerone said:
I saw you over at that other forum! I've been going mad trying to find a solution. Try under "sound -> quiet mode" a bit of deep googling found that as a potential hiding spot for the setting. (I'm back on stock and don't want to flash DU without knowing if this can be disabled.) I poked around in the DU build.prop, and wasn't able to find anything there either.
Click to expand...
Click to collapse
I had looked in there and have it enabled but even though notifications are disabled at night the battery light is not so thats a no go. Ive even been trying to merge the settings from a rom that had this option into the settings apk in this rom but haven't been able to get it to work. I looked in the build prop as well with no luck. I did find something in the sys/class/leds folder but it won't let me edit the charging folder even with root.
ajh305 said:
I had looked in there and have it enabled but even though notifications are disabled at night the battery light is not so thats a no go. Ive even been trying to merge the settings from a rom that had this option into the settings apk in this rom but haven't been able to get it to work. I looked in the build prop as well with no luck. I did find something in the sys/class/leds folder but it won't let me edit the charging folder even with root.
Click to expand...
Click to collapse
Those class files look really promising.
I was able to open them using ES file explorer on stock, looks like you could just modify the max_brightness one to 0, or something similar.
moonrakerone said:
Those class files look really promising.
I was able to open them using ES file explorer on stock, looks like you could just modify the max_brightness one to 0, or something similar.
Click to expand...
Click to collapse
I tried that but couldn't get the values to stick. I even tried deleting the charging folder but every operation fails.
I was able to Enable the charging light on stock using those files. Interesting that motorola has that feature kind of built-in with no front-end access.
What a bummer that it won't work for you. This weekend I think I'll flash back to DU and poke around.
moonrakerone said:
I was able to Enable the charging light on stock using those files. Interesting that motorola has that feature kind of built-in with no front-end access.
What a bummer that it won't work for you. This weekend I think I'll flash back to DU and poke around.
Click to expand...
Click to collapse
Ok let me know if it worked for you. I flashed back to Validus a few days ago I may try again this weekend as well.
Install "Light Manager" from the market. Most stable notification light app out there, best thing of all its FREE.
Problem solved.
Sent from my DROID RAZR HD using xda premium
Soon after I bought the fire HD6 I quickly realized that upon installing an alternative launcher, the device would not allow you to set that launcher as default. Today I figured out a way around this issue and put together a quick video showing all the steps. This tutorial should work for all Fire devices spanning from the Fire HD6 and HD7. Before going through the tutorial I suggest you get ADB set up and working on the computer for your Fire device. Enjoy!
https://www.youtube.com/watch?v=v6_2GoSz5N4
Help setting up ADB in Windows: https://www.youtube.com/watch?v=CyJlmTtLsIg
Following this guide will make it so you cannot use the Amazon Book app. A way around this issue would be to side-load the Kindle app. But not any Kindle app, a hacked version I made with a different signature and package name. That way your device will allow the installation and will not downgrade each boot. Download the APK below to get your books working:
https://drive.google.com/file/d/0Bx_94ujbh0qobVBJbWFyVzNzeUU/view?usp=sharing
Now you will be able to access your books.
You're awesome! Thanks! :laugh::good:
This works great, thanks!
Anyways to change the wallpaper?
D600abc said:
This works great, thanks!
Anyways to change the wallpaper?
Click to expand...
Click to collapse
No problem! I do not know how to do that yet. I hope it is plausible
Thank You! This was driving me crazy
Since Amazon "upgraded" the OS to Fire 4.x.x this has been a problem.
You are a gentleman and a scholar. Works for unrooted kindles as well.
Thank YOU!!!
RyanNerd said:
Since Amazon "upgraded" the OS to Fire 4.x.x this has been a problem.
You are a gentleman and a scholar. Works for unrooted kindles as well.
Thank YOU!!!
Click to expand...
Click to collapse
no problem (;
Could you share what exactly you changed in the hacked Kindle app? AFAIK it's a pretty old version and I'd like to have a more recent one on my Kindle. Thanks a lot either way!
crytic said:
Could you share what exactly you changed in the hacked Kindle app? AFAIK it's a pretty old version and I'd like to have a more recent one on my Kindle. Thanks a lot either way!
Click to expand...
Click to collapse
I basically just changed the package name and resigned it so that it will think it is a different app so it allows you to install it. I used apktool to decompile but had problems compiling till I removed some services from the Manifest file. I tried newer versions but could not get them to run without force closing.
Unable to set launcher
Hi, I followed your tutorial, now I am unable to see my kindle on adb devices list.
Can you please help me out with this.
pulnarayana1 said:
Hi, I followed your tutorial, now I am unable to see my kindle on adb devices list.
Can you please help me out with this.
Click to expand...
Click to collapse
try taking a look at this developer.amazon.com/sdk/fire/connect-adb.html
I set up KK Launcher as my launcher but it cannot get it to rotate to landscape mode at all. Is this a problem with other launchers you guys are using or is it just me?
argrr101 said:
I set up KK Launcher as my launcher but it cannot get it to rotate to landscape mode at all. Is this a problem with other launchers you guys are using or is it just me?
Click to expand...
Click to collapse
I use Apex and I can not get it to rotate either.
The best solution I've found so far is the app "Ultimate Rotation Control". It will allow you to manipulate the display as you see fit and even set parameters per app.
I got GEL working, but cannot set background pictures... Anyone else able to?
bilago said:
I got GEL working, but cannot set background pictures... Anyone else able to?
Click to expand...
Click to collapse
I believe this requires root.
I recently purchased a Fire HD 6 and this worked perfectly for me. Thank you for this. I chose to use Nova Launcher Prime as my default home launcher.
Sent from my SGH-T399N using Tapatalk
I forgot to revert to the stock dash before the last update (yesterday) and now I don't have ADB access. It just shows the device as 'offline' so I can't get it back to the stock dash and it's stuck at the Fire loading screen. It's the same in Windows/Ubuntu. Just a notice for anyone else to undo the custom dash before proceeding with the update.
gavin19 said:
I forgot to revert to the stock dash before the last update (yesterday) and now I don't have ADB access. It just shows the device as 'offline' so I can't get it back to the stock dash and it's stuck at the Fire loading screen. It's the same in Windows/Ubuntu. Just a notice for anyone else to undo the custom dash before proceeding with the update.
Click to expand...
Click to collapse
oh god, you scared the **** out of me for a second - I had gotten the update but had never used adb since then. tried just now, and ... nothing.
but! then I remembered, I had turned adb off on the HD, lol. turned it on and all is well.
I am running Nova launcher, and have the real launcher permanently blocked, along with a few other things:
http://forum.xda-developers.com/showpost.php?p=58360063&postcount=5
maybe your problem is something else? (or hopefully, maybe like me, just pilot error and usb debugging was turned off.)
I don't remember turning debugging off. I wouldn't have had any reason to disable it. I just assumed it was reset by the update. Either way, I had to do a factory reset to get it working again. To be honest, the custom dash was mostly a novelty. I'm happy enough with stock. Being able to use Google apps is all I'm worried about.
No body else appears to have mention having problems making widgets on your home screen. Every time I place a new widget it, just takes me to the main setting screen and on going back home there is no new widget.
I have been assuming that this is something else that requires root, but I thought I'd better check.
Thanks for kindlehack.apkill give it a try, ps use nova beta for wallpaper
Hey I know that other people have asked this sort of question before, but I was wondering if anyone can help me with setting up the Pixel/Pixel XL navigation bar animation on a none Pixel device (in my case Nexus 5X).
The reason I have started this thread is because I'm very suspicious of people when ever I see someone post a system modification for a device without explaining what they did to get there so I research things online and make my own version of they're system mod. Another reason is that asking these questions allows people to help me with my struggles and it expands everyone's knowledge on system modifications allowing everyone to create their own system mods or this same mod for their own device on any version of android.
Anyway the current things that I have found out is that the Pixel's SystemUI has a few extra files in the drawable folder (SystemUI.apk\res\drawable) they are
ic_sysbar_opa_blue.xml
ic_sysbar_opa_green.xml
ic_sysbar_opa_red.xml
ic_sysbar_opa_yellow.xml
Click to expand...
Click to collapse
they contain a information similar to these
<?xml version="1.0" encoding="utf-8"?>
<shape android:shape="oval"
xmlns:android="http://schemas.android.com/apk/res/android">
<size android:height="@dimen/opa_dot_diam" android:width="@dimen/opa_dot_diam" />
<solid android:color="#fffbbc05" />
</shape>
What this means:
Version of XML
Start of draw circle shape string
Thing
The size of the circle
Colour of the circle
End of string
Click to expand...
Click to collapse
This tells android to draw the little dots that appear when you press the home button on the Pixel. I have inported these files into my sytemui and was now wondering how to create the dots and make them move. I believe that this can be activated by finding out which file causes the home button to make that little ripple effect when you tap it and comparing it to find out what's different. So my question is at the moment is:
What file controls current home button animations (the home button ripple effect) on the Nexus 5X?
Click to expand...
Click to collapse
If any of you want the uncompressed versions of the Pixel's SystemUI and current Nexus SystemUI that I'm using then feel free too download them. (I have removed any unnecessary guff).
Edit: I think I have found the file. It's located at:
SystemUI.apk\res\layout\home.xml
Edit: I have edited the home.xml and it seems that it just cuases my SystemUI to crash. I believe this is caused by something else in the apk.
My current guess is that there is another file in the Pixels SystemUI that reads the xml file ic_sysbar_opa_colour.xml or home.xml
If anyone knows of a way I can search for those values in a large amount of xml files quickly, then please tell me.
No, It is not that simple. lots of things needs to modify, not only the res, dex code needs to patch, the one that detect the assistant and trigger the animation.
The worse thing is, if you do anything wrong, you have to use the twrp to restore the phone...
Charles_l said:
No, It is not that simple. lots of things needs to modify, not only the res, dex code needs to patch, the one that detect the assistant and trigger the animation.
The worse thing is, if you do anything wrong, you have to use the twrp to restore the phone...
Click to expand...
Click to collapse
I've edited the navigation bar in the SystemUI before without any problems. I know what you mean by resetting the phone if I mess anything up because I messed up a few things while editing the framework.apk but I haven't run into any problems with the dex file before.
Jackio987 said:
I've edited the navigation bar in the SystemUI before without any problems. I know what you mean by resetting the phone if I mess anything up because I messed up a few things while editing the framework.apk but I haven't run into any problems with the dex file before.
Click to expand...
Click to collapse
The dev that figured out how to enable the animated nav bar for the Nexus 5 posted this I hope it helps
http://forum.xda-developers.com/goo...-fake-nexus-rom-nexus-5-t3466736/post69496350
kevtrysmoddin said:
The dev that figured out how to enable the animated nav bar for the Nexus 5 posted this I hope it helps
http://forum.xda-developers.com/goo...-fake-nexus-rom-nexus-5-t3466736/post69496350
Click to expand...
Click to collapse
I noticed that someone else has done it before, (it's on page 120) link:
http://forum.xda-developers.com/goo...t/rom-fake-nexus-rom-nexus-5-t3466736/page120
Click to expand...
Click to collapse
And that inspired me to ask how it was done. Another thing is that I have a nexus 5X and he has a nexus 5 which both have different processor types (arm and arm64). I also tried flashing his zip which as you would of guessed caused my phone to crash as soon as the phone had booted up requiring me to factory reset it. I might try flashing the zip onto a phone that has an arm processor (my moto g 2nd generation running cyanogenmod 14 beta) and figure out how to export it to my Nexus. Anyway I have asked qitt the guy that made the original nav bar animation for the nexus 5 work how he did it and he still hasn't responed.
Also taking a look at it, it seems that the Pixel's SystemUI and qitt's SystemUI are almost identical with only about a 200 byte difference.
Jackio987 said:
Hey I know that other people have asked this sort of question before, but I was wondering if anyone can help me with setting up the Pixel/Pixel XL navigation bar animation on a none Pixel device (in my case Nexus 5X).
The reason I have started this thread is because I'm very suspicious of people when ever I see someone post a system modification for a device without explaining what they did to get there so I research things online and make my own version of they're system mod. Another reason is that asking these questions allows people to help me with my struggles and it expands everyone's knowledge on system modification allowing everyone to create their own system mod or this same mod for their own device on any operating system.
Anyway the current things that I have found out is that the Pixel's SystemUI has a few extra files in the drawable folder (SystemUI.apk\res\drawable) they are
they contain a information similar to these
This tells android to draw the little dots that appear when you press the home button on the Pixel. I have inported these files into my sytemui and was now wondering how to create the dots and make them move. I believe that this can be activated by finding out which file causes the home button to make that little ripple effect when you tap it and comparing it to find out what's different. So my question is at the moment is:
If any of you want the uncompressed versions of the Pixel's SystemUI and current Nexus SystemUI that I'm using then feel free too download them. (I have removed any unnecessary guff).
Edit: I think I have found the file. It's located at:
SystemUI.apk\res\layout\home.xml
Edit: I have edited the home.xml and it seems that it just cuases my SystemUI to crash. I believe this is caused by something else in the apk.
My current guess is that there is another file in the Pixels SystemUI that reads the xml file ic_sysbar_opa_colour.xml or home.xml
If anyone knows of a way I can search for those values in a large amount of xml files quickly, then please tell me.
Click to expand...
Click to collapse
I'm working on same and I'm willing to help you .. it's quite a surprise why despite so many ppl being there, none have managed to figure this one out. I'm also moderately knowledgeable about the subject so I just might be Able to help you. Can you share the systemUI.apk file for pixel?
raghavsharmaxda said:
I'm working on same and I'm willing to help you .. it's quite a surprise why despite so many ppl being there, none have managed to figure this one out. I'm also moderately knowledgeable about the subject so I just might be Able to help you. Can you share the systemUI.apk file for pixel?
Click to expand...
Click to collapse
Here you go.
I got this by flashing the Pixel's system.img onto my Nexus 5X extracting the entire system partition then re flashing android 7.1.1 beta. I have also included the .obex files in the system_other.img that comes with the Pixel's factory image.
I'm just wondering if it's as simple as changing the name of the Pixel's SystemUI, the AndroidManifest.xml, the meta-inf, the .odex and anything else related to application identification to get it working. The reason I say this is because qitt claims to have done this and I've taken a look at what he has done and it seems that there is basically no different between the Pixel's SystemUI and his in terms of file and folder layout. One problem is that qitt's SystemUI is optimized for the Nexus 5 which has a arm based processor not a arm64 one like the nexus 5x meaning that we just can't install it.
Here is qitts post
http://forum.xda-developers.com/goo...t/rom-fake-nexus-rom-nexus-5-t3466736/page120
Just create a flashable zip of systemui with animated navbar ( from 26/10 ). Try it if you want. Worked for me on 1/11 Fake Nexus. All credits to author this ROM ganachoco.
Attached Files
File Type: zip Pixel_NavBar.zip - [Click for QR Code] (11.56 MB, 856 views)
Click to expand...
Click to collapse
Jackio987 said:
Here you go.
I got this by flashing the Pixel's system.img onto my Nexus 5X extracting the entire system partition then re flashing android 7.1.1 beta. I have also included the .obex files in the system_other.img that comes with the Pixel's factory image.
I'm just wondering if it's as simple as changing the name of the Pixel's SystemUI, the AndroidManifest.xml, the meta-inf, the .odex and anything else related to application identification to get it working. The reason I say this is because qitt claims to have done this and I've taken a look at what he has done and it seems that there is basically no different between the Pixel's SystemUI and his in terms of file and folder layout. One problem is that qitt's SystemUI is optimized for the Nexus 5 which has a arm based processor not a arm64 one like the nexus 5x meaning that we just can't install it.
Here is qitts post
http://forum.xda-developers.com/goo...t/rom-fake-nexus-rom-nexus-5-t3466736/page120
Click to expand...
Click to collapse
I'm wondering how to solve the signature problem after modifying the AndroidManifest.xml?
Charles_l said:
I'm wondering how to solve the signature problem after modifying the AndroidManifest.xml?
Click to expand...
Click to collapse
I really want to just flash the files and then start editing from there but since my 5X is my personal device and if there are any stuff ups with this installation it meas that I have to factory reset my device which isn't that great if I have to do it every time I flash the file. I also don't want to make a TWRP backup and just recover from that when I'm all finished be cause every time I have done that my data partition always stuffs up basically causing me to factory reset again.
Testing this could become a slow and repetitive process
Ok I have figured out how to keep my devices data intact so I can flash the systemUI.apk over and over again without having to factory reset my device, now it's time to get this thing working.
Jackio987 said:
Ok I have figured out how to keep my devices data intact so I can flash the systemUI.apk over and over again without having to factory reset my device, now it's time to get this thing working.
Click to expand...
Click to collapse
If you keep the apk signature, when you get systemui fc, you can always replace the original apk file with TWRP, reboot and everything back to normal.
Jackio987 said:
Ok I have figured out how to keep my devices data intact so I can flash the systemUI.apk over and over again without having to factory reset my device, now it's time to get this thing working.
Click to expand...
Click to collapse
I have succeeded in porting all res and smali things to 5X's systemUI which is related to Assistant.
Process by now, the sendOpaBroadcast refuse to work.
issue:
Code:
11-11 11:58:02.915 D/AssistManagerGoogle(3038): New assistant: null
Charles_l said:
I have succeeded in porting all res and smali things to 5X's systemUI which is related to Assistant.
Process by now, the sendOpaBroadcast refuse to work.
issue:
Code:
11-11 11:58:02.915 D/AssistManagerGoogle(3038): New assistant: null
Click to expand...
Click to collapse
Do you have the new google assistant enabled?
If not then you can change your build.prop to get it working
Code:
change
ro.product.model=Nexus 5X to ro.product.model=Pixel
and add
ro.opa.eligible_device=true
somewhere into the build.prop then flash it or push it back onto the device.
This might be useful since the little circles the home buttons draws are called
ic_sysbar_opa_colour.xml
Click to expand...
Click to collapse
and the build prop tells the device that you can use opa with this line
ro.opa.eligible_device=true
Click to expand...
Click to collapse
Charles_l said:
I have succeeded in porting all res and smali things to 5X's systemUI which is related to Assistant.
Process by now, the sendOpaBroadcast refuse to work.
issue:
Code:
11-11 11:58:02.915 D/AssistManagerGoogle(3038): New assistant: null
Click to expand...
Click to collapse
Also can you tell us how to got the System UI's nav bar working, if it does work after you have changed the build.prop
Jackio987 said:
Also can you tell us how to got the System UI's nav bar working, if it does work after you have changed the build.prop
Click to expand...
Click to collapse
What did you do with build.prop, if you add a line in it to enable some settings, the setting doesn't turn off when you delete the line, you have to set the value to 0 of what you have added.
Good news, now I got the home button animation, though the four dots didn't appera.
I might need the Pixel phone user setting, if I can't override the Opa_Enabled settings.
Charles_l said:
What did you do with build.prop, if you add a line in it to enable some settings, the setting doesn't turn off when you delete the line, you have to set the value to 0 of what you have added.
Good news, now I got the home button animation, though the four dots didn't appera.
I might need the Pixel phone user setting, if I can't override the Opa_Enabled settings.
Click to expand...
Click to collapse
Here goes the build.prop from the Pixel if it helps.
Jackio987 said:
Here goes the build.prop from the Pixel if it helps.
Click to expand...
Click to collapse
Thank you but no need, after analysising Google App, I found a way to get systemUI turn on the OPA animation switch. I will start a new thread for details.
Charles_l said:
Thank you but no need, after analysising Google App, I found a way to get systemUI turn on the OPA animation switch. I will start a new thread for details.
Click to expand...
Click to collapse
Can you please make a tutorial on this so we can port it to other devices like my moto g 2014 or a nexus 6P or future updates to the nexus 5X.
Charles_l said:
Thank you but no need, after analysising Google App, I found a way to get systemUI turn on the OPA animation switch. I will start a new thread for details.
Click to expand...
Click to collapse
I worked on this for week but no luck .. if you have figured out how and do know the exact reasons, let me know..thank you
PS- don't back and restore /data all the time. Simply replace the apk and grand permissions from aroma file manager which can manipulate data from recovery itself.
Some of you may not notice, but I'm sure there are a few that do. Touch screen responsiveness on custom ROMs or GSI's for Mata is working, but is definitely not as fluid as stock.
Easiest way to tell is just typing on the keyboard and taking note of the shot delay in between touches. For me, I type fast, and this causes spelling mistakes often, because the touch screen (on a ROM or GSI.) doesn't register as it does on stock.
Next is mobile gaming. Touch seems to be a total hit and miss here, and sometimes won't work at all unless one finger is already on the screen. That's not a big deal, because a simple reboot fixes this temporarily. This was fixed a while ago here, if I recall correctly:
https://review.lineageos.org/c/LineageOS/android_frameworks_native/+/198809
Overall I am hoping to find a fix for this touch responsiveness issue. It effects a ton of aspects of this phone and prevents me from staying on ROMs, and resorting to restoring backups to use my phone properly again.
I've tried messing with the build.prop, switching kernels, checked out various forums and attempted things I probably shouldn't have tweaked with, but still have had no luck figuring this out on ROMs or GSI's. Yet on Stock everything functions properly, and touch is no issue.
Can anyone shed any light on this at all? (To clarify there are 2 issues here: general delay in touch, and touch screen not working after a while on games.)
Hi, I just flashed gsi rom yesterday and also found it more laggy than stock. I tried to search for a way to improve it but failed. Please let me know if you find a way to solve this problem.
Actually I flashed it just to make the stasus bar shorter and make it possible to disable navigation bar. I may change back to stock if I find any method to do so on it.
lovelock8353 said:
Hi, I just flashed gsi rom yesterday and also found it more laggy than stock. I tried to search for a way to improve it but failed. Please let me know if you find a way to solve this problem.
Actually I flashed it just to make the stasus bar shorter and make it possible to disable navigation bar. I may change back to stock if I find any method to do so on it.
Click to expand...
Click to collapse
Still trying different things, but so far no luck, touch remains a bit laggy. Gonna try something later though, are you currently on a GSI with Root?
In: system / usr / idc there should be some .idc files, I wonder if there are some entries on stock that aren't in GSI's or ROMs?
I dunno, just shooting in the dark here.
MoistPicklez said:
Still trying different things, but so far no luck, touch remains a bit laggy. Gonna try something later though, are you currently on a GSI with Root?
In: system / usr / idc there should be some .idc files, I wonder if there are some entries on stock that aren't in GSI's or ROMs?
I dunno, just shooting in the dark here.
Click to expand...
Click to collapse
Yes,I rooted it. I just checked idc folder of my stock room restore, there are no more but 1 less idc file in the stock rom. I copied the entire idc folder to main storage, restored the gsi room and replaced it. I don't think it makes obvious change,at least did not make the touch screen as good as the stock.
But I did flash elemental-x kernel after flashing gsi. It might have make it better? Maybe I just got used to the sensitivity of gsi but you may try to flash the kernel and replace the folder, see if any changes are noticed.
I'm running the latest HavocOS GSI build with the neutrino gemini kernel. Also using Ex Kernel Manger so the settings will stick or can be changed. No touch lag or the like on my end. Very smooth.
hx3 said:
I'm running the latest HavocOS GSI build with the neutrino gemini kernel. Also using Ex Kernel Manger so the settings will stick or can be changed. No touch lag or the like on my end. Very smooth.
Click to expand...
Click to collapse
Is the status of Havoc OS as high and wide as the stock room? Or is it just normal size as on other Android devices? Considering transfer to it.
lovelock8353 said:
Is the status of Havoc OS as high and wide as the stock room? Or is it just normal size as on other Android devices? Considering transfer to it.
Click to expand...
Click to collapse
Unfortunately, the latest build of HavocOS is from October 27th. However, you can still use the latest December firmware/security update from Essential.
There is one bug with it, at least for me and others, and it's the fingerprint sensor doesn't work for us. It doesn't show up in Settings either. It worked on previous builds, though. Not to knock the developer at all, as I appreciate the work that has been put in.
As far as the "normal size" you brought up... Are you referring to file size? If so, it's in the same ballpark as any other stock/stock-ish ROM that doesn't include gapps. I used Pico gapps, as I don't use many Google apps. Hopefully that answered your questions.
hx3 said:
Unfortunately, the latest build of HavocOS is from October 27th. However, you can still use the latest December firmware/security update from Essential.
There is one bug with it, at least for me and others, and it's the fingerprint sensor doesn't work for us. It doesn't show up in Settings either. It worked on previous builds, though. Not to knock the developer at all, as I appreciate the work that has been put in.
As far as the "normal size" you brought up... Are you referring to file size? If so, it's in the same ballpark as any other stock/stock-ish ROM that doesn't include gapps. I used Pico gapps, as I don't use many Google apps. Hopefully that answered your questions.
Click to expand...
Click to collapse
Thank you for your information!
I'm sorry I mistyped the question. Actually what I wanted to ask was the status bar, which bothered me a lot on the stock rom. I flashed to pixelexperience specially for changing the status bar height to normal (and being able to disable navigation bar completely). I don't know why it was so hard that I didn't find any way to do so on stock rom.
lovelock8353 said:
Thank you for your information!
I'm sorry I mistyped the question. Actually what I wanted to ask was the status bar, which bothered me a lot on the stock rom. I flashed to pixelexperience specially for changing the status bar height to normal (and being able to disable navigation bar completely). I don't know why it was so hard that I didn't find any way to do so on stock rom.
Click to expand...
Click to collapse
Oh, yeah, that's the other "issue" people have had with HavocOS on the PH-1. The status bar is very thin...About 50% too thin, and I don't know of any way to change it. It doesn't really bother me after getting used to it. I'll have to try out Pixel Experience, though. I do miss the fingerprint sensor working properly.
hx3 said:
I'm running the latest HavocOS GSI build with the neutrino gemini kernel. Also using Ex Kernel Manger so the settings will stick or can be changed. No touch lag or the like on my end. Very smooth.
Click to expand...
Click to collapse
Thanks for the input, pretty sure I have already tried the Oct 27th Havoc OS with Neutrino and still had those touch issues with games, but I will give it another shot in case, did you by chance modify a few things with EX Kernel Manager?
hx3 said:
Oh, yeah, that's the other "issue" people have had with HavocOS on the PH-1. The status bar is very thin...About 50% too thin, and I don't know of any way to change it. It doesn't really bother me after getting used to it. I'll have to try out Pixel Experience, though. I do miss the fingerprint sensor working properly.
Click to expand...
Click to collapse
The status bar is also thin pixelexperience if you care. Aside from the touch screen latency, I haven't noticed any other issue on this rom, so I recommend you give it a try.
Tried Havoc OS paired with Neutrino, and tweaked around with EX Kernel Manager last night for a while, but still had issues with touch on games and keyboard. Literally everything I have tried on custom installations has not helped improve touch responsiveness.
Come on, surely some random dev still lurks these forums who also notices these delays in touch. Would love to help solve this if I knew exactly where to start, and am willing to test or tweak to get this resolved.
No idea if this will help, but it's easy to try. In developer settings, find grip rejection and try toggling it on. Else, in the same place, try adjusting touch sensitivity.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
ktmom said:
No idea if this will help, but it's easy to try. In developer settings, find grip rejection and try toggling it on. Else, in the same place, try adjusting touch sensitivity.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Click to expand...
Click to collapse
Grip rejection and touch sensitivity aren't available in GSI's unfortunately, but even some ROMs that do include those settings still have delayed touches, and games eventually lose touch until you reboot on occasion.
Compared to stock, the only ROM that had touch working perfectly (like stock) was Kuran's AICP O. I suspect this has something to do with his kernel, but I am just speculating, I can't be sure on that one.
Then even on a GSI with a stock kernel I still get touch issues, so I have a feeling it has something to do either something in /system but then again, I'm still guessing.
But I appreciate the reply thank you for chiming in on this. ?
The only reason I suggested that "fix" was when I was running AOSiP Pie, that was the only way to get rid of the lag. Simply toggling the grip rejection solved the problem immediately.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
ktmom said:
The only reason I suggested that "fix" was when I was running AOSiP Pie, that was the only way to get rid of the lag. Simply toggling the grip rejection solved the problem immediately.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Click to expand...
Click to collapse
Huh, last time I was on AOSiP Pie (maybe a week ago) I still had touch issues, but hell, for some awesome customization, maybe it's time for another try on that. Thank you, by the way, I really dig that signature of yours.
MoistPicklez said:
Huh, last time I was on AOSiP Pie (maybe a week ago) I still had touch issues, but hell, for some awesome customization, maybe it's time for another try on that. Thank you, by the way, I really dig that signature of yours.
Click to expand...
Click to collapse
Throw a setprop in front of these... And reboom... See if it helps
persist.vendor.qti.inputopts.enable=true
persist.vendor.qti.inputopts.movetouchslop=0.5
rignfool said:
Throw a setprop in front of these... And reboom... See if it helps
persist.vendor.qti.inputopts.enable=true
persist.vendor.qti.inputopts.movetouchslop=0.5
Click to expand...
Click to collapse
Thanks will try this tonight.
So I'd just use:
adb shell
Then
setprop (entry here)
?
MoistPicklez said:
Thanks will try this tonight.
So I'd just use:
adb shell
Then
setprop (entry here)
?
Click to expand...
Click to collapse
Sure...
But why for you no have magisk?
rignfool said:
Sure...
But why for you no have magisk?
Click to expand...
Click to collapse
Edit: I think I may have gotten it figured, and at least narrowed down the issue. I Installed Havoc OS 10-27 again with Dec-patched-boot.img, then Neutrino Hercules over that, on both slots, changed CPU to performance and enabled touchboost, then added these lines to my build.prop and rebooted:
persist.vendor.qti.inputopts.enable=true
persist.vendor.qti.inputopts.movetouchslop=0.6
So far so good, touchscreen jank is gone, scrolling isn't bad at all, and best of all games seem way more fluid. Will continue to test it out.
Edit 2: So far so good games haven't lost touch, not even once, games are still fluid and there are literally no touch delays when gaming or typing. So either the kernel (with performance mode and touch boost on) or the entries I added to the build.prop have fixed this finally. Or both. So freakin' happy.
OB1 was the only build OnePlus released with 4K video recording on all three lenses. On OB2 and now stable, only the main camera can do 4K and you have to switch to 1080p to record with wide and telephoto lens. It's very easy to port the stock OP OB1 camera to other builds via root and only requires one reboot.
Here are the Files you'll need
EDIT: Follow new instructions below
Video proof:
https://drive.google.com/open?id=1HmcoQcFdFoeHtJiCa0N02LWHImvNFwX_
11'/26 EDIT: New features unlocked:
It's apparent that the Magisk module is not going to happen. I'd like to thank Luffitys and Amer Alrakik on Telegram for first looking into modifying the apk to make the camera edits. When this failed, I'd like to thank @elmarian756 to the Preference Manager app. He showed me it's as simple as editing .xmls in. By editing the .xmls in here, you can modify nearly every core feature of the cameras. I'd also like to thank Lord Vicky on Telegram for his hard work trying to make the Magisk module. Thanks to @Arnova8G2, we know which camera is which:
Camera ID 0: Back >>> Physical
Camera ID 1: Front >>> Physical
Camera ID 2: Telephoto >>> Physical
Camera ID 3: Wide >>> Physical
Camera ID 4: Telephoto >>> Logical better
Camera ID 5: Front >> Logical better
By editing these xmls, you'll be able to edit many core features of the OOS camera. So here goes the manual installation. It will still require root:
1) If you want 4K vid recording on all 3 sensors, delete any apk in system\priv-app\OnePlusCamera and put in a blank text document in the folder and name it whatever you want. This will remove the OP camera as a system app and reboot. You can then install v52 as a data (user) app: https://www.apkmirror.com/?post_type=app_release&searchtype=apk&s=oneplus+camera
2) Launch the camera app so it will create the shared_prefs folder with the default .xmls in it
3) Download the attached .xmls and replace the default ones in \data\data\com.oneplus.camera\shared_prefs
4) Force stop the camera app and delete its cache (not storage) for new settings to come into effect.
5) Enjoy!
v13 of the camera app is the only version that 4K60 FPS video recording can be enabled on all three sensors. The version of the app crashes a lot in this mode and why I recommend v52 without 60 FPS. I'm not sure what version it starts, but you entirely lose the ability to record video with the telephoto sensor. This is built into the apk and can not be unlocked with an xml edit, as far as I know. Macro mode works all the way up to newest (v77) apk. I believe v13 is the only version where Super Steady mode can be enabled for the telephoto lens as well as the wide angle.
I'm sure there's many combinations that I've missed, but here's what in these edits:
1) Macro mode for all three sensors (this is not even possible for 7T series.)
2) 50x zoom. It gets wavy to hold around 30x, but I just wanted to match the current GCam level.
3) Super Steady mode for telephoto sensor (v13 only (I think))
I'm sure many of you will find new features and I encourage you to use the Preferences Manager app to edit things on the fly. Please share in the threads new things you discover!!!
Happy Thanksgiving,
Doc
Interesting! Has anyone tested this on pie? I am not moving yet to 10 until some things fully work there. But this seems good!
I just done it and it works in 4k u can use all three lens
Sent from my GM1913 using Tapatalk
elmarian756 said:
Interesting! Has anyone tested this on pie? I am not moving yet to 10 until some things fully work there. But this seems good!
Click to expand...
Click to collapse
I was going to try later tonight on Pie or tomorrow...depending on time.
gokhujee said:
I just done it and it works in 4k u can use all three lens
Click to expand...
Click to collapse
What Android version?
Ok just tried this on pie. First, there is no such opcameraresources folder on system/priv app. (At least on pie OOS) I pasted the folder and replaced opcamera folder with the one provided on the OP. Gave the right permissions and Rebooted. And opcamera resources was gone and no video on other lenses tan main one. I dont know if system is erasing any changes i do somehow or this just doesnt work on pie. My two cents here
elmarian756 said:
Ok just tried this on pie. First, there is no such opcameraresources folder on system/priv app. (At least on pie OOS) I pasted the folder and replaced opcamera folder with the one provided on the OP. Gave the right permissions and Rebooted. And opcamera resources was gone and no video on other lenses tan main one. I dont know if system is erasing any changes i do somehow or this just doesnt work on pie. My two cents here
Click to expand...
Click to collapse
Thanks for trying! Is there an OnePlusCameraServices folder? Try this one with, again, 0755 permissions in the folder and 0644 on the apk
https://drive.google.com/open?id=1xZ-IsjwGp-hr6PSJ9dONQcU2oUkepzOW
docnok63 said:
Thanks for trying! Is there an OnePlusCameraServices folder? Try this one with, again, 0755 permissions in the folder and 0644 on the apk
https://drive.google.com/open?id=1xZ-IsjwGp-hr6PSJ9dONQcU2oUkepzOW
Click to expand...
Click to collapse
Sure! It would be nice if it works on pie. There IS onepluscameraservicefolder. Replaced the folders, gave right permissions and rebooted. Unfortunately, still have no video on other than main lenses.
I have two theories and this could be because of my current setup.
One is that any changes i do on system gets reverted back after reboot. Dont know why but it happened to me before when i edited build.prop (maybe xxx roms fault or some other magisk module). Only changes that sticks are the ones that i use with magisk module (and build a magisk module for this mod wouldnt be much difficult).
Or two, maybe the apps does gets installed, but options will not show on pie.
I do know that if i download the camera apk and install it normally it will replace old stock app and stick after reboot. So i tried manually and normally installing the apks from your mod this way but i didnt notice any different results either.
elmarian756 said:
Sure! It would be nice if it works on pie. There IS onepluscameraservicefolder. Replaced the folders, gave right permissions and rebooted. Unfortunately, still have no video on other than main lenses.
I have two theories and this could be because of my current setup.
One is that any changes i do on system gets reverted back after reboot. Dont know why but it happened to me before when i edited build.prop (maybe xxx roms fault or some other magisk module). Only changes that sticks are the ones that i use with magisk module (and build a magisk module for this mod wouldnt be much difficult).
Or two, maybe the apps does gets installed, but options will not show on pie.
I do know that if i download the camera apk and install it normally it will replace old stock app and stick after reboot. So i tried manually and normally installing the apks from your mod this way but i didnt notice any different results either.
Click to expand...
Click to collapse
Again, thanks for trying and feedback I'll try myself soon enough, but not tonight. I want to come back to Pie for RiCE mod anyway. I miss separation of ringtone and notification volumes
docnok63 said:
Again, thanks for trying and feedback I'll try myself soon enough, but not tonight. I want to come back to Pie for RiCE mod anyway. I miss separation of ringtone and notification volumes
Click to expand...
Click to collapse
Yes and horizon lights tweaks, screen burn in protection! I am currently running rice and xXx. Elemental x. Xposed with xprivacylua for some games and gravitybox. Not leaving soon although it looks like everything is on the works of being ported to 10 (even gravitybox).
Please let us know if you make this work on pie. Really lookimg forward to test this.
I tried to port this to Pie earlier today and couldn't get it to go. One thing weird that I noticed (and possibly a reason why?) is that even though OB1's camera version is 3.8.62, Pie automatically installed v3.8.52. I don't even see how that possible. Furthermore, once I sideloaded v62 as a system app, I can't load it as a data app (could on 10.) At least I have RiCE and substratum's Swift Black back!!! I can't wait for these to get updated to 10!!!
docnok63 said:
OB1 was the only build OnePlus released with 4K video recording on all three lenses. On OB2 and now stable, only the main camera can do 4K and you have to switch to 1080p to record with wide and telephoto lens. It's very easy to port the stock OP OB1 camera to other builds via root and only requires one reboot.
Here are the Files you'll need
1) Delete current OnePlusCamera and OPCameraResources from system\priv-app. Replace with OB1 folders of the same name.
2) Change permission of both folders to 0755. Go into OnePlusCamera folder and change OnePlusCamera.apk permissions to 0644.
3) Reboot and Profit!!!
Video proof:
https://drive.google.com/open?id=1HmcoQcFdFoeHtJiCa0N02LWHImvNFwX_
Click to expand...
Click to collapse
Man, you've made my day (night to be precise) I was waiting for it to come!! This is how it should be done from the beginning.
I decided to make a Magisk Module with the files provided and it works great for me on OOS 10. Anyone else wanna try it out?
https://drive.google.com/open?id=1V4ylaYadCK16VWWKXXaJkjF6FcJlf0Nb
bmg1001 said:
I decided to make a Magisk Module with the files provided and it works great for me on OOS 10. Anyone else wanna try it out?
https://drive.google.com/open?id=1V4ylaYadCK16VWWKXXaJkjF6FcJlf0Nb
Click to expand...
Click to collapse
Downloaded and tested, works well
Thanks
bmg1001 said:
I decided to make a Magisk Module with the files provided and it works great for me on OOS 10. Anyone else wanna try it out?
https://drive.google.com/open?id=1V4ylaYadCK16VWWKXXaJkjF6FcJlf0Nb
Click to expand...
Click to collapse
Thanks so much for this!!! It will make an already simple installation so much faster!!!
EDIT: I tried the module on Pie just to see if it would suddenly Magiskly work and, unfortunately, it did not
bmg1001 said:
I decided to make a Magisk Module with the files provided and it works great for me on OOS 10. Anyone else wanna try it out?
https://drive.google.com/open?id=1V4ylaYadCK16VWWKXXaJkjF6FcJlf0Nb
Click to expand...
Click to collapse
Is it for AA or BA? I installed and rebooted but there's still no option for wide angle for 4k video. Cleared cam storage too.
tropical cactus said:
Is it for AA or BA? I installed and rebooted but there's still no option for wide angle for 4k video. Cleared cam storage too.
Click to expand...
Click to collapse
If you're on Pie, this doesn't work. It's only for Open Beta 2 or stable 10
bmg1001 said:
I decided to make a Magisk Module with the files provided and it works great for me on OOS 10. Anyone else wanna try it out?
https://drive.google.com/open?id=1V4ylaYadCK16VWWKXXaJkjF6FcJlf0Nb
Click to expand...
Click to collapse
Props to you and the OP. Saved me asking for an end user comparison on stability
docnok63 said:
If you're on Pie, this doesn't work. It's only for Open Beta 2 or stable 10
Click to expand...
Click to collapse
Thanks. Sorry I didn't say. I'm on stable android 10. I've tried everything. I tried your files first. Didn't show up. Tried the magisk module. Didn't show up either. Rebooted and cleared camera storage. Still nothing. Very strange.
tropical cactus said:
Thanks. Sorry I didn't say. I'm on stable android 10. I've tried everything. I tried your files first. Didn't show up. Tried the magisk module. Didn't show up either. Rebooted and cleared camera storage. Still nothing. Very strange.
Click to expand...
Click to collapse
That's very strange. You're the first person that's ever said it doesn't work. Does dropping down to 1080p show all 3 lenses as it does normally? My suggestion to troubleshoot: Cut all 3 directories out of priv-app and back them up to the Downloads folder. Uninstall the Magisk module. Reboot. Install the Magisk module and reboot. See if that does it.
docnok63 said:
That's very strange. You're the first person that's ever said it doesn't work. Does dropping down to 1080p show all 3 lenses as it does normally? My suggestion to troubleshoot: Cut all 3 directories out of priv-app and back them up to the Downloads folder. Uninstall the Magisk module. Reboot. Install the Magisk module and reboot. See if that does it.
Click to expand...
Click to collapse
All three lenses show in 1080p. Once I switch to 4k, I have one lense. I have reflashed rom, did what you suggested and still nothing. I've even uninstalled gcam. Nothing. I give up.