Gang, it seems latest TQ1A.221205.011 is quite intriguing.. can't wait to update. but i wanted to know know if any side effects in the sense of root ,
Pls share if any of the modules you are experiencing issues.
E.g. Gpay, call recorder, banking, Aosp mod.etc..
bizkit_120 said:
Gangs, it seems latest TQ1A.221205.011 is quite intriguing.. can't wait to update. but i wanted to know know if any side effects in the sense of root ,
Pls share if any of the modules you are experiencing issues.
E.g. Gpay, call recorder, banking, Aosp mod.etc..
Click to expand...
Click to collapse
I'm having issues with AOPS Mods, I reinstalled the module but it doesn't solve it. Nothing really serious tho
alsansan said:
I'm having issues with AOPS Mods, I reinstalled the module but it doesn't solve it. Nothing really serious tho
Click to expand...
Click to collapse
latest canary in aosp fix all issues.
bizkit_120 said:
Gang, it seems latest TQ1A.221205.011 is quite intriguing.. can't wait to update. but i wanted to know know if any side effects in the sense of root ,
Pls share if any of the modules you are experiencing issues.
E.g. Gpay, call recorder, banking, Aosp mod.etc..
Click to expand...
Click to collapse
What makes it better than the November build? I barely notice any difference besides during the initial setup where more stuff is in Dark mode
there is no init_boot .img in the new image, so which file to patch? Boot.img?
Sh0X31 said:
there is no init_boot .img in the new image, so which file to patch? Boot.img?
Click to expand...
Click to collapse
There is an init_boot.img in the January update.
Lughnasadh said:
There is an init_boot.img in the January update.
Click to expand...
Click to collapse
So does that mean we can update using magisk again?
rob420p said:
So does that mean we can update using magisk again?
Click to expand...
Click to collapse
You can update and root with Magisk, if that's what you are asking. Same as usual.
Lughnasadh said:
You can update and root with Magisk, if that's what you are asking. Same as usual.
Click to expand...
Click to collapse
I mean I know with the last build you had to side load etc because magisk was soft bricking
rob420p said:
I mean I know with the last build you had to side load etc because magisk was soft bricking
Click to expand...
Click to collapse
I don't really know what you are talking about. Sideload what? There was nothing wrong with the December build and rooting with Magisk. You must have had other problems if that happened to you.
Or are you talking about updating via "Install to Inactive Slot" method? If so, that's always been hit or miss, mostly miss.
Lughnasadh said:
I don't really know what you are talking about. Sideload what? There was nothing wrong with the December build and rooting with Magisk. You must have had other problems if that happened to you.
Or are you talking about updating via "Install to Inactive Slot" method? If so, that's always been hit or miss, mostly miss.
Click to expand...
Click to collapse
That's exactly what I meant thank u
Related
Hello.
i have a question if there is possible to enable led control on Nexus stock M 6.01 MMB29V without TWRP and root.
Thanks and rgds.
semail00 said:
Hello.
i have a question if there is possible to enable led control on Nexus stock M 6.01 MMB29V without TWRP and root.
Thanks and rgds.
Click to expand...
Click to collapse
Without Root - yes (you can use this > http://forum.xda-developers.com/nexus-6/general/led-control-stock-xposed-t3146814
Without TWRP - no
cam30era said:
Without Root - yes (you can use this > http://forum.xda-developers.com/nexus-6/general/led-control-stock-xposed-t3146814
Without TWRP - no
Click to expand...
Click to collapse
I would not advise doing that. As the file is from 5.1.1 there is no telling what changes to the system that has been done.
zelendel said:
I would not advise doing that. As the file is from 5.1.1 there is no telling what changes to the system that has been done.
Click to expand...
Click to collapse
You are correct. I should have been more specific. Post #95 includes file download from CM13 (Android 6.0). Working fine for me on MMB29V.
cam30era said:
You are correct. I should have been more specific. Post #95 includes file download from CM13 (Android 6.0). Working fine for me on MMB29V.
Click to expand...
Click to collapse
Even then that is for that build. It may cause other issues on different builds.
zelendel said:
Even then that is for that build. It may cause other issues on different builds.
Click to expand...
Click to collapse
I agree. It could. But isn't that what we all do here about that? Modifications that are not necessarily 100% bullet proof? And looking for feedback from others who are using it..?
semail00 said:
... possible to enable led control on Nexus stock M 6.01 MMB29V without TWRP and root....
Click to expand...
Click to collapse
It seems to me that you already know the answer. You are familiar with the terms TWRP and root.
Beside the question you need to give a motive.
NLBeev said:
It seems to me that you already know the answer. You are familiar with the terms TWRP and root.
Beside the question you need to give a motive.
Click to expand...
Click to collapse
Hello,
I just wanted to see if it was possible activate led notification without changing the original system, even with some apks ( I do not know but that someone could know ). This was the meaning of my request ..... I apologize if I have not been able to explain.
rgds.
semail00 said:
Hello,
I just wanted to see if it was possible activate led notification without changing the original system, even with some apks ( I do not know but that someone could know ). This was the meaning of my request ..... I apologize if I have not been able to explain.
rgds.
Click to expand...
Click to collapse
Understood. It is nice to know the 'why' behind questions.
On my N6 I've LED control, but with a Lite rom of Danvdh and the cataclysm mod. Works good, but .......root and TWRP.
This is the new refined home for DarkRoom Development. If you submit bug reports without a log, you may be prosecuted...or executed.
Disclaimer:
If your device fails to comply with your standards of what you consider functioning, I am not liable. This is provided free of charge and does not come with a warranty. Although, if you provide a log, I can provide some sort of assurance that I will look into your issue.
Links:
Social:
Twitter - http://twitter.com/mtthwlx
Downloads:
https://drive.google.com/drive/folders/1zwaS15e4zXiSWuEU_ZOjTLBqtdzP86dL?usp=sharing
Source:
Github – https://github.com/DespairFactor/
Credits:
Essential
Google
Star Wars
Finally...
Good to see the development..
Special thanks to the members who donated f&f codes.
And @DespairFactor for quick release..
Hype.
Oof
indian84 said:
Finally...
Good to see the development..
Special thanks to the members who donated f&f codes.
And @DespairFactor for quick release..
Click to expand...
Click to collapse
ghostENVY said:
Hype.
Click to expand...
Click to collapse
LeTurntRice said:
Oof
Click to expand...
Click to collapse
There are no features yet, I am working on EAS tweaks for stock at the moment and will likely also do an HMP kernel
n00b question... What does this kernel have? Also would you be able to dive into the camera apk to help solve compression issue and color saturation since you have the phone now?
xterminater07 said:
n00b question... What does this kernel have? Also would you be able to dive into the camera apk to help solve compression issue and color saturation since you have the phone now?
Click to expand...
Click to collapse
I am about to push my changes to github, I am unaware of what the issue is or if I can help. but I can try when I have free time
Oh nice, we get to be named after Rei? Curious as to whether you intend for this to work on AOSP, LOS or stock ROMs?
ChronoReverse said:
Oh nice, we get to be named after Rei? Curious as to whether you intend for this to work on AOSP, LOS or stock ROMs?
Click to expand...
Click to collapse
Right now this is for stock oreo beta 2, will work on other stuff as I have time, but I am hoping they release stock oreo soon
OH! Does it include patches to pass Safetynet despite the unlocked bootloader as well? Would like to avoid Magisk if possible.
ChronoReverse said:
OH! Does it include patches to pass Safetynet despite the unlocked bootloader as well? Would like to avoid Magisk if possible.
Click to expand...
Click to collapse
I am adding that right now, I am testing some boot issues with one of my commits, R1 will be up for all when it is resolved
Hi,
What is the correct way to flash, boot.img then magisk. I cant remember. Blame the booze.
Thanks
R1 good to go? As its uploaded i see
Edit: Guess so as flash and passed safety net
DaveHTC200 said:
R1 good to go? As its uploaded i see
Edit: Guess so as flash and passed safety net
Click to expand...
Click to collapse
NZnewbie said:
Hi,
What is the correct way to flash, boot.img then magisk. I cant remember. Blame the booze.
Thanks
Click to expand...
Click to collapse
R2 is up now, I am working on getting AnyKernel to work and keep recovery on device if possible when flashing.
We have confirmed that the flashable zip keeps TWRP on your phone and you get to keep the kernel and your system working fine!
To root with this, flash twrp to your boot partition using fastboot, flash the kernel zip and then flash magisk.
EDIT: also confirmed to work on nougat!
Tried Rey2.zip nd booted back to twrp and the touch didnt work. Using the latest twrp as well
DespairFactor said:
We have confirmed that the flashable zip keeps TWRP on your phone and you get to keep the kernel and your system working fine!
To root with this, flash twrp to your boot partition using fastboot, flash the kernel zip and then flash magisk.
EDIT: also confirmed to work on nougat!
Click to expand...
Click to collapse
DespairFactor said:
We have confirmed that the flashable zip keeps TWRP on your phone and you get to keep the kernel and your system working fine!
To root with this, flash twrp to your boot partition using fastboot, flash the kernel zip and then flash magisk.
EDIT: also confirmed to work on nougat!
Click to expand...
Click to collapse
Is Magisk working with this kernel on Oereo B2? Magisk 14.3 caused lots of reboots, 14.6 just doesn't work (no magisk after boot).
NZnewbie said:
Tried Rey2.zip nd booted back to twrp and the touch didnt work. Using the latest twrp as well
Click to expand...
Click to collapse
Looking into it, I think flashing magisk makes touch work, will see if I can fix it within the kernel side.
gk1984 said:
Is Magisk working with this kernel on Oereo B2? Magisk 14.3 caused lots of reboots, 14.6 just doesn't work (no magisk after boot).
Click to expand...
Click to collapse
Yes it is, I have it on my device right now
Ive heard theres a fix coming for that as well(hope so)
gk1984 said:
Is Magisk working with this kernel on Oereo B2? Magisk 14.3 caused lots of reboots, 14.6 just doesn't work (no magisk after boot).
Click to expand...
Click to collapse
DespairFactor said:
I am about to push my changes to github, I am unaware of what the issue is or if I can help. but I can try when I have free time
Click to expand...
Click to collapse
The problem with the stock camera app was that it compresses images too much, they have lower the compression ratio but it is still not good enough. You can try it yourself to see what I mean. In broad day light outdoor, the images appears to be great but if you zoomed in, you will see it it just doesn't look right. The color is washed out as well, and you don't see any details. Looks like everything is smoothed out. File size is about 6 to 7mb or so. The low light shots are worst, it's about 3mb and there's more fuzzy stuff and lack of details/sharpness.
If you can dive deep into the apk to see what they set the compression to, and change that to possibly 0, and see what else needs to be changed. I spoke to Arnova8g2, who helped ported the gcam hdr+ to oneplus3/3t and he helped fixed the compression a bit on the older apk but I can't overwrite it no matter what. Let me know if you need any more info.
Hello guys and girls,
As some of you already know Android 8.1 suffers from a severe Multi-Touch Issue. This issues makes the smartphone randomly jumping between the two touching points on the screen when touching with two or more fingers.
The issue is known to google since the preview of 8.1. It isn´t only affecting pixel but most probably all devices running 8.1. The issue is also present on P.
An issue got created here: https://issuetracker.google.com/issues/70344455
There is a fix since mid march in review on google gerrit. But that didn´t make it into the april release, obviously.
To visualize the issue refer to the following videos:
https://youtu.be/wgYN5GwIgIc
https://youtu.be/2Vv584tvVyg
https://www.youtube.com/watch?v=4dnIk_5qdK8&feature=youtu.be
This is especially bad for gamers. With the recent release of PUBG this issues seems dramatic to some, less to others.
I´m no gamer but I noticed the issue on the google foto app.
This issue has nothing to do with the corners badly reacting to touches, or touch sensitivity etc.
So but now to the fix. It seems the issues is only related to resampling but not to touching specific points of the screen ( not related to crossing x and y axis).
That also explains why the issue wasn´t happening when using the touch tracking tool in dev settings but on various multi touch test apps.
The fix is on google gerrit currently under review here:
https://android-review.googlesource.com/c/platform/frameworks/native/+/640605
https://android-review.googlesource.com/c/platform/frameworks/native/+/640606
Last week I compiled myself a DU build with the changes included and I couldn´t trigger the issue at all. I found no other side effects caused by the two patches.
For now I decided to provide a Magisk Module which replaces the changed libs that fixes the issue.
I compiled the libs while doing my april build of DU. The magisk module can be found on the link a little bit down.
The download is here:
https://www.androidfilehost.com/?fid=890129502657595755
A few disclaimers here.
1. That fix should in theory work for most 8.1 devices, including the likes of pixel 1st gen, pixel 2nd gen, one plus, xiaomi which suffer from this severe issue.
1a. It works only for AOSP/LOS based roms on the essential phone. It seems like stock isn´t close enough to aosp.
2. I didn´t fix this, I just compiled the libs with the fix found on google gerrit.
3. Rom devs you are very welcome to include this fix. I found no ill consequences as of yet but I can understand google taking it slow and reviewing it longer. Maybe they will find a better fix, but as of now this is the best thing we have.
Donations:
Donations are not mandatory but very welcome.
If you like my work: http://paypal.me/freak07
this was confirmed working on the xda portal post by @crixley for the essential phone running a custom aosp/los based rom.
Big thanks to you!
Freak07 said:
this was confirmed working on the xda portal post by @crixley for the essential phone.
Big thanks to you!
Click to expand...
Click to collapse
Huge difference, including touch latency! I'm super pumped about it.
Work perfectly!!! Thank you so much!
Guys, does it work? For me I ended up in bootloop
xorwin said:
Guys, does it work? For me I ended up in bootloop
Click to expand...
Click to collapse
Omg you're right it actually causes my phone to not boot. I wiped my entire phone thinking it was some kind of module conflict and now it still wont boot.
xorwin said:
Guys, does it work? For me I ended up in bootloop
Click to expand...
Click to collapse
wind711 said:
Omg you're right it actually causes my phone to not boot. I wiped my entire phone thinking it was some kind of module conflict and now it still wont boot.
Click to expand...
Click to collapse
I bootlooped too. Flashing the stock boot image fixed it and my phone booted right to Android.
Jank4AU said:
I bootlooped too. Flashing the stock boot image fixed it and my phone booted right to Android.
Click to expand...
Click to collapse
Once I flashed the stock boot image I lost magisk so that wouldn't work.
wind711 said:
Once I flashed the stock boot image I lost magisk so that wouldn't work.
Click to expand...
Click to collapse
I wasn't worried about losing Magisk. I was trying to get my phone to boot.
@crixley what did you do to get it to work? For three of us it results in a bootloop.
Jank4AU said:
I wasn't worried about losing Magisk. I was trying to get my phone to boot.
@crixley what did you do to get it to work? For three of us it results in a bootloop.
Click to expand...
Click to collapse
I'm not on stock rom, that might be it. Should have been clear on that
crixley said:
I'm not on stock rom, that might be it. Should have been clear on that
Click to expand...
Click to collapse
Yeah, I'm on stock so you're probably right, that might be it.
Thank you soo much @Freak07 !
I installed with with magisk app as a module. Booted perfect
tomzefi said:
I installed with with magisk app as a module. Booted perfect
Click to expand...
Click to collapse
Are you on stock or custom ROM?
Jank4AU said:
Are you on stock or custom ROM?
Click to expand...
Click to collapse
Should have mentioned that. I am on resurrection remix and rooted.
Confirmed that it also bootloops on stock ROM, if you have ElementalX Kernel installed.
It seems that the stock rom isn’t close enough to aosp so this fix will only work on custom roms!
I edited the OP accordingly to the stock rom issue.
In the meantime can one of you guys on the stock rom do me a favour and check if you have libinputflinger.so and libinput.so located in system/lib and system/lib64 or if the libs are somewhere in vendor for you?
They exist both files.
hypnz said:
They exist both files.
Click to expand...
Click to collapse
It should be 4 files overall. libinput.so and libinputflinger.so have to be in system/lib and additionally in system/lib64.
but if they are in system and not in system/vendor then I have no way of fixing it atm I fear.
So after Trying different PIE GSIs, I Found a less buggy GSI rom. It's "RR-P-v7.0.3-20191112-A64-A.img" that i found on @turbolukex5 thread on this link. https://forum.xda-developers.com/pr...iscussion/gsi-expressluke-built-gsis-t4003457
basically i tested camera, BT,in call audio, Fingerprint and Mobile Hotspot. So far they work pretty nice. The only thing that doesn't work as of now is the MTP. So you need to reboot to TWRP to transfer files on storage.
If this thread is prohibited, kindly remove it. I just want to share what i found today. Thank you.
Curcepogi said:
So after Trying different PIE GSIs, I Found a less buggy GSI rom. It's "RR-P-v7.0.3-20191112-A64-A.img" that i found on @turbolukex5 thread on this link. https://forum.xda-developers.com/pr...iscussion/gsi-expressluke-built-gsis-t4003457
basically i tested camera, BT,in call audio, Fingerprint and Mobile Hotspot. So far they work pretty nice. The only thing that doesn't work as of now is the MTP. So you need to reboot to TWRP to transfer files on storage.
If this thread is prohibited, kindly remove it. I just want to share what i found today. Thank you.
Click to expand...
Click to collapse
You can use kraken kernel for fixing MTP.
heni87 said:
You can use kraken kernel for fixing MTP.
Click to expand...
Click to collapse
Thanks bro. I will try it later if you can give me the link. I cant rly find it on internet.
Curcepogi said:
Thanks bro. I will try it later if you can give me the link. I cant rly find it on internet.
Click to expand...
Click to collapse
https://github.com/SPART4NICUS/DOWN...Kernel-V3.0-universal7870-Treble-20200108.zip
Working. On. A6+ gsi
elokuba said:
Working. On. A6+ gsi
Click to expand...
Click to collapse
Yes. It will definitely work on any Device that is treble Enabled. You just need to find the Correct vendor for your device. :highfive:
heni87 said:
https://github.com/SPART4NICUS/DOWN...Kernel-V3.0-universal7870-Treble-20200108.zip
Click to expand...
Click to collapse
Thanks. I will try and report here later. As of now the only bug i got is the Camera when using flash. The shutter is not synced with the flash. You will get a dark photo when taking at night.
Curcepogi said:
Thanks. I will try and report here later. As of now the only bug i got is the Camera when using flash. The shutter is not synced with the flash. You will get a dark photo when taking at night.
Click to expand...
Click to collapse
That's basically a bug which is present in almost every GSI. Use footej/open camera from play store instead. Those will also give you back some of the manual controls if you are into that sorta thing.
heni87 said:
That's basically a bug which is present in almost every GSI. Use footej/open camera from play store instead. Those will also give you back some of the manual controls if you are into that sorta thing.
Click to expand...
Click to collapse
I already tried the kernel. I got a working MTP after reboot(bare bones, no GApps). But when i install GApps(Aroma) the rom is very sluggish and FP was broken during setup. So i did not finish the setup and i quickly reverted to stock. ?
wats bether version on a6+
Curcepogi said:
I already tried the kernel. I got a working MTP after reboot(bare bones, no GApps). But when i install GApps(Aroma) the rom is very sluggish and FP was broken during setup. So i did not finish the setup and i quickly reverted to stock. ?
Click to expand...
Click to collapse
Not sure but the guy who compiled that kernel said not to use magisk it breaks too many stuff.
heni87 said:
Not sure but the guy who compiled that kernel said not to use magisk it breaks too many stuff.
Click to expand...
Click to collapse
I did not used magisk on setup. This are my steps:
-Flashed GSI
-Flashed Kraken kernel
-rebooted and did factory reset
-Resized the system to flash GApps.
-flashed GApps aroma.
And the phone is already sluggish. Any thoughts bro?
elokuba said:
wats bether version on a6+
Click to expand...
Click to collapse
I don't have that device. But u can use CPU info or CPU Z and Treble check to know what variant is for you.
Curcepogi said:
I don't have that device. But u can use CPU info or CPU Z and Treble check to know what variant is for you.
Click to expand...
Click to collapse
Which version should i use? Arm64? Or a64 only?
tutul2336 said:
Which version should i use? Arm64? Or a64 only?
Click to expand...
Click to collapse
Same as mine. A64_a only
Curcepogi said:
I did not used magisk on setup. This are my steps:
-Flashed GSI
-Flashed Kraken kernel
-rebooted and did factory reset
-Resized the system to flash GApps.
-flashed GApps aroma.
And the phone is already sluggish. Any thoughts bro?
Click to expand...
Click to collapse
Would help you out much better if you could come at our telegram. But for now try doing everything first and reserve flashing kraken as last step also factory reset is unnecessary.
heni87 said:
Would help you out much better if you could come at our telegram. But for now try doing everything first and reserve flashing kraken as last step also factory reset is unnecessary.
Click to expand...
Click to collapse
I appreciate your efforts on this query. I will try your suggestions as soon as im available again. Thank you bro.
Curcepogi said:
I appreciate your efforts on this query. I will try your suggestions as soon as im available again. Thank you bro.
Click to expand...
Click to collapse
Anytime bud. Search us on telegram by @SM_A600X don't wanna post the invite link since a mod will eventually come and take it down.
heni87 said:
https://github.com/SPART4NICUS/DOWN...Kernel-V3.0-universal7870-Treble-20200108.zip
Click to expand...
Click to collapse
There is newer version https://github.com/SPART4NICUS/DOWNLOADS/releases/tag/RC11
any good GSI on A6+? Have you tried Havoc OS?
Just received update notification.
Notes say:
Google security patch
Stability optimizations
Does anyone have any more details?
Thanks.
Pathetic. This is the first update since August 2019 and all they do is send out a security patch. No bug fixes whatsoever. Where the Fuk is Android 10?
It feels more stable but the major bugs from 1.18 are still there.
The last update was 10/17/2019. Which bugs are you referring to? I don't have any bugs, but I don't use certain features, like gaming.
This is the reason im here . I just installed it and my phone does not work with 4G as it use to be . I cant even log to pubg and any help please
Redmagic3 said:
This is the reason im here . I just installed it and my phone does not work with 4G as it use to be . I cant even log to pubg and any help please
Click to expand...
Click to collapse
I installed the update, and everything is working so far.
Are you rooted? Is that the problem?
Have you tried clearing the cache from recovery?
You can't update your rooted phone and root doesn't work in new update.
Thank you
nabbed said:
Just received update notification.
Notes say:
Google security patch
Stability optimizations
Does anyone have any more details?
Thanks.
Click to expand...
Click to collapse
can any one provide me the boot img of this latest update v1.20
xphyle1971 said:
Pathetic. This is the first update since August 2019 and all they do is send out a security patch. No bug fixes whatsoever. Where the Fuk is Android 10?
Click to expand...
Click to collapse
nabbed said:
The last update was 10/17/2019. Which bugs are you referring to? I don't have any bugs, but I don't use certain features, like gaming.
Click to expand...
Click to collapse
Major storage bug, screen tearing when scrolling through apps, even after a factory reset and using it without Magisk the phone has the major bugs
chocolote4444 said:
Major storage bug, screen tearing when scrolling through apps, even after a factory reset and using it without Magisk the phone has the major bugs
Click to expand...
Click to collapse
I have none of those bugs. Maybe they have quality control issues, and you have a defective unit.
My phone is literally perfect. Love it.
ghostknightfire said:
You can't update your rooted phone and root doesn't work in new update.
Thank you
Click to expand...
Click to collapse
I am on root and any idea on how to install the latest update? I dont know how to unroot my phone...
Any help here is appreciated..
Aru