Hey guys, quick question here, are all supersu zip files the same? It's a noob question, but does it matter which supersu you download? Like, do phones and tablets need a specific version or does just googling for the newest zip file to flash with a custom recovery just work everytime? Thanks!
H4X0R46 said:
Hey guys, quick question here, are all supersu zip files the same? It's a noob question, but does it matter which supersu you download? Like, do phones and tablets need a specific version or does just googling for the newest zip file to flash with a custom recovery just work everytime? Thanks!
Click to expand...
Click to collapse
the same zip should work in any device with a custom recovery.
bweN diorD said:
the same zip should work in any device with a custom recovery.
Click to expand...
Click to collapse
Thank you very much!
SuperSU is hardware agnostic.. However, it is not Android version agnostic, so make sure you download one for your version of Android
danarama said:
SuperSU is hardware agnostic.. However, it is not Android version agnostic, so make sure you download one for your version of Android
Click to expand...
Click to collapse
That's good to know! And how can you usually tell? Does the webpage usually mention which android version it's for if you read it carefully? (As you should with ANY mod) And worse case scenario, a software brick that can be recovered is the worst right?
H4X0R46 said:
That's good to know! And how can you usually tell? Does the webpage usually mention which android version it's for if you read it carefully? (As you should with ANY mod) And worse case scenario, a software brick that can be recovered is the worst right?
Click to expand...
Click to collapse
i have never seen them posted in that manner.
from my experience, a current su zip will work across at least 2 major versions, possibly more, i simply dont know the range.
im curious to hear danarama's explination too, i might learn something
H4X0R46 said:
That's good to know! And how can you usually tell? Does the webpage usually mention which android version it's for if you read it carefully? (As you should with ANY mod) And worse case scenario, a software brick that can be recovered is the worst right?
Click to expand...
Click to collapse
bweN diorD said:
i have never seen them posted in that manner.
from my experience, a current su zip will work across at least 2 major versions, possibly more, i simply dont know the range.
im curious to hear danarama's explination too, i might learn something
Click to expand...
Click to collapse
It's to do with stable versus Beta. When a New OS version comes out, e.g 5.0, then it *may* be that SuperSU needs tweaks and you have to move from stable: http://forum.xda-developers.com/showthread.php?t=1538053 to beta: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
We also had to move to Beta when 5.1 came out as there were amendments needed, however after a while those amendments made it to stable. I'm not sure where Android M sits. Whether it needs any changes from stable. If it does then people will be using the beta.
So basically, it doesn't matter what hardware you have. It only matters how new your OS is and whether any changes that may have been needed with that new OS are in stable yet or in beta. ...and afaik, all official releases (so excluding the Android M dev preview) are covered by the latest stable release. As for backwards compatibility, my assumption would be that they are, but I never keep a phone long enough to find out.
Related
if possible, please include WHY.
illdourmum said:
if possible, please include WHY.
Click to expand...
Click to collapse
I'm using the 3/7 gapps because they are the latest version provided from the CyanogenMod gapps mirror.
No idea where the 3/25 build came from. Same as the unofficial CWM 3.0.0.5 that's floating around.
^what he said
There's a 3/25 GB GApps on romrepo - http://romrepo.info/wiki/index.php?title=Main_Page
TJinWV said:
There's a 3/25 GB GApps on romrepo - http://romrepo.info/wiki/index.php?title=Main_Page
Click to expand...
Click to collapse
And the question is where did they come from? Because they certainly aren't from Cyanogen.
jasonmaloney said:
And the question is where did they come from? Because they certainly aren't from Cyanogen.
Click to expand...
Click to collapse
Ah, OK, misunderstood your initial post.
OP - I use the newest ones, lol. What the heck do you mean? Do you wanna know which .zip we flashed, or what actual google apps we use? The last gapps.zip I flashed was around 2/21, home-made .zip (because I don't use ALL the google apps). Since then I just update them form the market. I also was kindly informed that gapps are preserved in a flashover, which is why I haven't flashed a gapps.zip again. Also, the google apps are available publicly and for free on the android market, so after an update I use TB pro to "re-integrate into ROM" (which is the same basically as moving them from /data to /system).
Jason - whoa homey, chill. Gapps are free, and from GOOGLE (and most aren't even open source fyi), not aosp, you, or cyanogen. All anybody really does is put them in a .zip and make it flashable to /system. Feel free to correct me, but really, who cares.
il Duce said:
Jason - whoa homey, chill. Gapps are free, and from GOOGLE (and most aren't even open source fyi), not aosp, you, or cyanogen. All anybody really does is put them in a .zip and make it flashable to /system. Feel free to correct me, but really, who cares.
Click to expand...
Click to collapse
The difference is that I've seen several reports of people getting force closes on the Setup Wizard, and (seeing as Setup Wizard is part of the gapps) there's no way to know if that's a bug in the ROM or because they're using gapps from some other source.
EDIT: It's just a constructive response. One dev for one phone made his own variant of gapps, while the rest of the CM users are using a different set. Troubleshooting is one step easier when everyone is using the same files, especially considering they're "universal" across devices now.
jasonmaloney said:
I'm using the 3/7 gapps because they are the latest version provided from the CyanogenMod gapps mirror.
No idea where the 3/25 build came from. Same as the unofficial CWM 3.0.0.5 that's floating around.
Click to expand...
Click to collapse
i've been using the one that's been floating around, 3/25... maybe this is why i sometimes have issues with the Market.
Thanks for your input. I'll start using the official 3/07 when i upgrade from asopCMod to CM7.0.0 Stable
Introduction:
This is a restore zip for restoring/debricking a molly device (ADT-1).
The contents are as close to stock as possible, and is intended to fix broken otas.
Click to expand...
Click to collapse
File List:
update-molly-Stock-LPV79-1.zip
Click to expand...
Click to collapse
FAQ:
Will this fix my <non molly device>?
No, this rom is only for mollys, it will brick any other device.
Will OTAs work after flashing this?
Yes, that is the purpose of this
Do I need to be on a certain bootloader to use this?
No, it includes the original bootloader.
Do I need a custom recovery to flash this?
Yes, the stock recovery will not accept update zips that are not signed by google
Is this rooted?
No, the stock rom is not rooted, neither is this
My device won't finish booting after flashing.
If you were not originally on the same rom, you may need to do a factory reset to finish the process. Android does not like rom downgrades without a factory reset
Click to expand...
Click to collapse
Changelog:
Nov 3, 2014: Initial Page
Click to expand...
Click to collapse
2char
I made a gallery of it because I felt like it: Update - Imgur
Awesome! Thanks! I needed a way to restore my OTA abilities after rooting and doing some testing for someone. Did you make these yourself? And how? If you don't mind me asking. I didn't think dd would work without root.
death2all110 said:
Awesome! Thanks! I needed a way to restore my OTA abilities after rooting and doing some testing for someone. Did you make these yourself? And how? If you don't mind me asking. I didn't think dd would work without root.
Click to expand...
Click to collapse
All custom recoveries have root by default, my ADT1 isnt rooted, I did all my work though CWM.
TheManii said:
All custom recoveries have root by default, my ADT1 isnt rooted, I did all my work though CWM.
Click to expand...
Click to collapse
Duh. Didn't think of that... Haha. Thanks!
Could someone who has updated to LPX13D please post a system dump? Im needing it for an OUYA port that im working on. Thanks
It's already been posted here:
http://forum.xda-developers.com/showpost.php?p=56186872&postcount=69
death2all110 said:
It's already been posted here:
http://forum.xda-developers.com/showpost.php?p=56186872&postcount=69
Click to expand...
Click to collapse
Thanks, never would have found it there.
TheManii said:
2char
Click to expand...
Click to collapse
Thanks! Do you have to have a USB keyboard in order to move around in CWM on the ADT-1?
ScubaXsays said:
Thanks! Do you have to have a USB keyboard in order to move around in CWM on the ADT-1?
Click to expand...
Click to collapse
Yes a USB keyboard is needed to move around CWM on the ADT-1
death2all110 said:
Yes a USB keyboard is needed to move around CWM on the ADT-1
Click to expand...
Click to collapse
Thanks so much for the quick response, you're the best.
ScubaXsays said:
Thanks so much for the quick response, you're the best.
Click to expand...
Click to collapse
No problem. I had the same problem initially
death2all110 said:
Yes a USB keyboard is needed to move around CWM on the ADT-1
Click to expand...
Click to collapse
ScubaXsays said:
Thanks so much for the quick response, you're the best.
Click to expand...
Click to collapse
Yes you need a usb keyboard to use CWM currently, there may be an update in the future to enable the dev button on the back to select in cwm like it does in fastboot. Until if/when that happens you either need a keyboard or to do everything manually via adb.
I don't have a keyboard however, I did all my work/testing with only adb.
TheManii said:
Yes you need a usb keyboard to use CWM currently, there may be an update in the future to enable the dev button on the back to select in cwm like it does in fastboot. Until if/when that happens you either need a keyboard or to do everything manually via adb.
I don't have a keyboard however, I did all my work/testing with only adb.
Click to expand...
Click to collapse
Thanks for the articulate follow-up. I started to do things manually via ADB. :good:
anyone can post a complete lpx13D CWM backup , stock recovery or at least system.img
I've messed up my ADT1 and it can't seem to take the image I've found yet
@TheManii Are there any custom roms or anything like that for the ADT-1? I just got one in the mail from I assume google. I'm ready to begin , but I don't honestly know what people are interested in seeing on this device I have a madcatz mojo using all the adt-1 binaries except audio running cm-12 and android tv from this device. So if anyone is interested in that let me know please.
Unjustified Dev said:
@TheManii Are there any custom roms or anything like that for the ADT-1? I just got one in the mail from I assume google. I'm ready to begin , but I don't honestly know what people are interested in seeing on this device I have a madcatz mojo using all the adt-1 binaries except audio running cm-12 and android tv from this device. So if anyone is interested in that let me know please.
Click to expand...
Click to collapse
Hello UD,
There isn't any custom roms for the ADT-1 (So yours would be the first)
I for one would love to see a more recent build than the last OTA (LPX13D - OCT 29th) There have been rumors that we'd get the final Android Lollipop but nothing has surfaced.
How much work is involved in rolling an AOSP+ADT-1 Binaries+Android TV dependencies?
Cheers Rob.
halfluck said:
Hello UD,
There isn't any custom roms for the ADT-1 (So yours would be the first)
I for one would love to see a more recent build than the last OTA (LPX13D - OCT 29th) There have been rumors that we'd get the final Android Lollipop but nothing has surfaced.
How much work is involved in rolling an AOSP+ADT-1 Binaries+Android TV dependencies?
Cheers Rob.
Click to expand...
Click to collapse
It's possible https://www.youtube.com/watch?v=Og-GDeRhJno but I could not get all the apps correctly working the main one being playstore , but I will try again look at the android build number and build date. I basically made a google apps package based on the adt-1 this is before I had one so possibly now I can get us an aosp 5.0.2 base working the Mojo in terms of hardware is similar to the adt-1 and for me to boot 5.0 on the mojo I needed adt-1 updated tegra 4 binaries so this shouldn't be hard at all once I work out the playstore issues.
Unjustified Dev said:
It's possible https://www.youtube.com/watch?v=Og-GDeRhJno but I could not get all the apps correctly working the main one being playstore , but I will try again look at the android build number and build date. I basically made a google apps package based on the adt-1 this is before I had one so possibly now I can get us an aosp 5.0.2 base working the Mojo in terms of hardware is similar to the adt-1 and for me to boot 5.0 on the mojo I needed adt-1 updated tegra 4 binaries so this shouldn't be hard at all once I work out the playstore issues.
Click to expand...
Click to collapse
Wow that is really impressive work, The current build on the ADT-1 is flaky at best for me, i'd love to see how a more recent build performs and if it prevents me from having to do a daily reboot.
Cheers Rob.
@Unjustified Dev just got mine on Tuesday. are you thinking releasing sources on your team github. i saw that a device and kernel repository was created but they are empty.
PS: nice to talk to you again been a while.
____Update 12/01____
Since a couple of days we now have v 9.1.2.0. I haven't noticed any differences yet, but the wallpaper carousel is functioning again. They also implemented fixes for problems that I personally did not encounter. ...aaand the notifications are slightly improved! Some of them evene expand and allow for direct interaction. Breathtaking development.
Get it while it's fresh on en.miui.com.
Should you not be rooted, I can recommend installing it via XiaoMiTool. I used this to flash the last MIUI 8 Global Stable, and then got 9.1.1.0 and now 9.1.2.0 via OTA. I've read that for some people here fast charging isn't working on th 9-er Firmwares. I have had no problem with that at all. Maybe it's because you guys are rooted, or because system wasn't flashed properly? I don't know, but I feel with you...
____Update 11/16____
The MIUI9 release has since been officially announced. This XDA article sheds some light on the release. However, as of today, the ROM is still not available for download on en.miui.com.
If you don't feel like waiting for OTA hitting you, shadowxaero has provided a link to download 9.1.1.0 (NDEMIEI) in post #7.
To enable VOLTE in presumably every MIUI realease, KevinLuong has shared a great link to an explanation including an easy fix in post #2.
Update 11/17
The Firmware is officially available on en.miui.com now. Should you not be rooted, consider installing it via XiaoMiTool, which will let you chose and download the Firmware within the programs flashing dialogue (give that man a beer).
_____initial post_____
..but there is no mention of it anywhere (yet). Why is that?
It's Version 9.1.1.0 (NDEMIEI). Got it OTA on Friday night, but it isn't even yet listed on the official site. Whats up with that?
Everything seems to run great, except that VOLTE can not be activated, which I find a little weird for a stable release. Oh, and notfications are still not up to scratch in MIUI 9, which is the single most annoying thing about MIUI.
Anyone else on this ROM? Maybe with tips, tricks, htoughts or insights?
.
cartonneexpress said:
...but there is no mention of it anywhere. Why is that?
It's Version 9.1.1.0 (NDEMIEI). Got it OTA on Friday night, but it isn't yet listed on the official site. Whats up with that?
Everything seems to run great, except that VOLTE can not be activated, which I find a little weird for a stable release. Oh, and notfications are still not up to scratch, which is the single most annoying thing about MIUI.
Anyone else on this ROM? Maybe with tips, tricks, htoughts or insights?
Click to expand...
Click to collapse
It's a nightly preview pushed to some users.
http://en.miui.com/thread-951467-1-1.html explains the VoLTE thing, the dialler code enabled it for me.
Sent from my Mi MIX 2 using Tapatalk
KevinLuong said:
http://en.miui.com/thread-951467-1-1.html explains the VoLTE thing, the dialler code enabled it for me.
Click to expand...
Click to collapse
Thanks a lot! That explains, and easily fixes it!
KevinLuong said:
It's a nightly preview pushed to some users.
Click to expand...
Click to collapse
Hmm. Why would they do that? I'm not even participating in the user feedback program (at least not willingly ). Usually the nightlys they push out clearly state that they are nightlys, don't they? I saw this with the Mi 6 when it got v 9.0.1.0. In this case on Mix 2 the ROM clearly states "stable" though.
Well, I don't want to complain. I feel special now. :victory:
cartonneexpress said:
...but there is no mention of it anywhere (yet). Why is that?
It's Version 9.1.1.0 (NDEMIEI). Got it OTA on Friday night, but it isn't even yet listed on the official site. Whats up with that?
Everything seems to run great, except that VOLTE can not be activated, which I find a little weird for a stable release. Oh, and notfications are still not up to scratch in MIUI 9, which is the single most annoying thing about MIUI.
Anyone else on this ROM? Maybe with tips, tricks, htoughts or insights?
Click to expand...
Click to collapse
What ROM where you on before, MIUI 8 Global Stable?
Andy4Shurr said:
What ROM where you on before, MIUI 8 Global Stable?
Click to expand...
Click to collapse
Yes, I had Global Stable (v8.5.1.0).
It's a global stable beta (stable beta = what exactly??) according to the miui forums. There was an announcement about it. I put a link to the download in the reverse engineering thread.
I haven't actually tried it yet but I would be interested to know if it passes safetynet, I guess.
http://bigota.d.miui.com/V9.1.1.0.NDEMIEI/miui_MIMIX2Global_V9.1.1.0.NDEMIEI_232bee13eb_7.1.zip
A user provided that link on the MIUI forums. I haven't flashed it yet and I believe you need to be on the MIUI8 Stable ROM in order to flash this.
duraaraa said:
It's a global stable beta (stable beta = what exactly??) according to the miui forums. There was an announcement about it. I put a link to the download in the reverse engineering thread.
I haven't actually tried it yet but I would be interested to know if it passes safetynet, I guess.
Click to expand...
Click to collapse
Lol whoops, missed this post lol. A user on MIUI also said it passed safety net yesterday.
shadowxaero said:
http://bigota.d.miui.com/V9.1.1.0.NDEMIEI/miui_MIMIX2Global_V9.1.1.0.NDEMIEI_232bee13eb_7.1.zip
A user provided that link on the MIUI forums. I haven't flashed it yet and I believe you need to be on the MIUI8 Stable ROM in order to flash this.
Lol whoops, missed this post lol. A user on MIUI also said it passed safety net yesterday.
Click to expand...
Click to collapse
You can flash it with fastboot, but you have to convert the system to a system.img in order to do so.
duraaraa said:
It's a global stable beta (stable beta = what exactly??) according to the miui forums. There was an announcement about it. I put a link to the download in the reverse engineering thread.
I haven't actually tried it yet but I would be interested to know if it passes safetynet, I guess.
Click to expand...
Click to collapse
duraaraa said:
You can flash it with fastboot, but you have to convert the system to a system.img in order to do so.
Click to expand...
Click to collapse
Lol how does one do that?
shadowxaero said:
Lol how does one do that?
Click to expand...
Click to collapse
I used sdat2img.py
https://github.com/xpirt/sdat2img
Use that to make a system.img, flash that with fastboot.
Then flash all of the other partitions with fastboot from the unpacked zip, following the pattern of the Xiaomi fastboot updates so you know which thing needs to be flashed to what.
Kind of difficult to explain and probably not worth putting together a whole tutorial, but that's how you do it.
this build passes safetynet with Magisk 14. I also installed this over Epic rom and not over v8 stable.. works fine anyways. I did format userdata and cache from fastboot before i flashed.
cartonneexpress said:
...but there is no mention of it anywhere (yet). Why is that?
Everything seems to run great, except that VOLTE can not be activated, which I find a little weird for a stable release.....
Click to expand...
Click to collapse
Try disabling VoLTE carrier check with *#*#86583*#*# That did it for me. Make sure the little pop-up screen says disabled
No notification update no fun
Jesus when will it be officially available OTA?
Removed, was already in this thread.
Full ROM Pack Version: V9.1.1.0.NDEMIEI is available now : http://en.miui.com/download-334.html#491
whats the best way to upgrade? I am on MIMIX2Global_7.11.6 beta?
el3c said:
whats the best way to upgrade? I am on MIMIX2Global_7.11.6 beta?
Click to expand...
Click to collapse
This will most likely not work coming from the developer ROM, but try the regular manual update method:
Download the ROM and copy it to your device. Then go to settings > About Phone > System Update and chose your update package from the extended menu (three dots, top right).
Should the regular method not work, and should your device not be unlocked/rooted, then simply use the XiaoMiTool. If you follow the instructions this program works really really well, so consider donating that guy a beer or two.
.
cartonneexpress said:
This will most likely not work coming from the developer ROM, but try the regular manual update method:
Download the ROM and copy it to your device. Then go to settings > About Phone > System Update and chose your update package from the extended menu (three dots, top right).
Should the regular method not work, and should your device not be unlocked/rooted, then simply use the XiaoMiTool. If you follow the instructions this program works really really well, so consider donating that guy a beer or two.
.
Click to expand...
Click to collapse
phone is unlocked... i cant live without a native adblocker ^^
Thanks...and it seems to work with the updater app it´s in German but it says: all data will be deleted and it make a revert to global stable.
i´ve canceled that, i am not sure whats better, stay on beta and get weekly updates if i want or choose global. it s a hard decission
el3c said:
phone is unlocked... i cant live without a native adblocker ^^
Thanks...and it seems to work with the updater app it´s in German but it says: all data will be deleted and it make a revert to global stable.
i´ve canceled that, i am not sure whats better, stay on beta and get weekly updates if i want or choose global. it s a hard decission
Click to expand...
Click to collapse
I'm in the same position
Hi guys,
If you installed the Official MIUI 9.1 Stable can you please report on battery life ?
Regards.
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.
can someone explain how to flash an .img file for whatever reason i can flash all the .zip files not 1 .img is working obviously im doing something wrong
What exactly are you flashing? I've never flashed a .img file before
ghost9640 said:
can someone explain how to flash an .img file for whatever reason i can flash all the .zip files not 1 .img is working obviously im doing something wrong
Click to expand...
Click to collapse
You can really mess things up, so best to be careful and make sure you're doing it 100% correctly.
In download mode, for say radio.img it would be "fastboot flash radio NameOfRadio.img"
ghost9640 said:
can someone explain how to flash an .img file for whatever reason i can flash all the .zip files not 1 .img is working obviously im doing something wrong
Click to expand...
Click to collapse
You might consider looking up high on android. He had an auto GSI installer for all pixels up to the 4XL and tested several. Some worked amazingly well, some didn't.
brother already have nothing for pixel 5 as i can find directly im curious if im needing to flash the vbmeta after the .img flash im definetly in above my head but will stay on this i know ill find a way
ghost9640 said:
brother already have nothing for pixel 5 as i can find directly im curious if im needing to flash the vbmeta after the .img flash im definetly in above my head but will stay on this i know ill find a way
Click to expand...
Click to collapse
I just tested it on a pixel 5, using the high on android gsi installer. It worked and it was really easy. I used the Arcana gsi and it's a tiny bit buggy but I'm going to try the Corvus tomorrow. The gsi.img I found said it was the March update, so I made sure to flash the Google stock March img first.
After that, you just need to go to youtube and search for high on android auto gsi installer. Follow his instructions. I have no idea what features will work and which ones won't. If you do this, you do it at your own risk and accept all responsibility. I hope you find what you're looking for.
ghost9640 said:
brother already have nothing for pixel 5 as i can find directly im curious if im needing to flash the vbmeta after the .img flash im definetly in above my head but will stay on this i know ill find a way
Click to expand...
Click to collapse
Ok, I couldn't wait so I tried the Corvus gsi. Both of these tests were on A12 so that might influence your decision but I was pretty underwhelmed with Corvus. It was clean with zero bugs but I think there's better options in the legit custom roms available here, on XDA. If you're going for A11, you might have more features but I think a ROM build specifically for the device will always trump a GSI.
yea im good asomeone i definetly trust his opinion told me it wasnt happening anyways so this post is officialy dead but mad appreciation on getting to me fam,
AlexKarimov said:
Ok, I couldn't wait so I tried the Corvus gsi. Both of these tests were on A12 so that might influence your decision but I was pretty underwhelmed with Corvus. It was clean with zero bugs but I think there's better options in the legit custom roms available here, on XDA. If you're going for A11, you might have more features but I think a ROM build specifically for the device will always trump a GSI.
Click to expand...
Click to collapse
im really digging crdroid im going for stayboogy this Wednesday or thursday which ever day the fedex gods permitt me a day of fun
Home - Pixel Experience
Home - Pixel Experience
download.pixelexperience.org
Another for you, I'm using the plus version and aospmods, all good here.