Merging Sparsechunks - Verizon Motorola Droid Turbo Q&A, Help & Troublesh

I really want to fix the HDR camera bug, and I think I know how, but I need to merge the sparsechunks contained in the most recent 5.1 image. I can't seem to figure out how to do that. Can anyone enlighten me?
EDIT: Never mind. I figured it out.

TheSt33v said:
I really want to fix the HDR camera bug, and I think I know how, but I need to merge the sparsechunks contained in the most recent 5.1 image. I can't seem to figure out how to do that. Can anyone enlighten me?
EDIT: Never mind. I figured it out.
Click to expand...
Click to collapse
May I ask how you managed to do it? I need to do exactly the same thing, but for my Moto 360.

TheSt33v said:
I really want to fix the HDR camera bug, and I think I know how, but I need to merge the sparsechunks contained in the most recent 5.1 image. I can't seem to figure out how to do that. Can anyone enlighten me?
EDIT: Never mind. I figured it out.
Click to expand...
Click to collapse
What bug?
Sent from my DROID RAZR M using XDA Free mobile app

fritzhy said:
May I ask how you managed to do it? I need to do exactly the same thing, but for my Moto 360.
Click to expand...
Click to collapse
I merged them using the tool in the OP of this thread, and I removed the Motorola header and footer using the instructions in JulesJam's post: http://forum.xda-developers.com/showthread.php?t=2749797&page=5
Removing the header and footer is necessary if you want to mount the image in Linux as ext4 and modify it. Of course, that's assuming Motorola puts the header and footer into Android Wear images. I'm not entirely sure that they do.

mrkhigh said:
What bug?
Sent from my DROID RAZR M using XDA Free mobile app
Click to expand...
Click to collapse
Back in the Mofo days, there was an issue where camera apps would force close if you tried to take a picture with HDR enabled on 5.1. Setting SElinux to permissive fixed it.

TheSt33v said:
Back in the Mofo days, there was an issue where camera apps would force close if you tried to take a picture with HDR enabled on 5.1. Setting SElinux to permissive fixed it.
Click to expand...
Click to collapse
Oh, I thought you figured out how to merge the sparsechunks. Anyway, right after asking you, I found a Windows tool to do it: http://forum.xda-developers.com/showthread.php?p=50656564
I had to modify the batch scripts a bit, but it worked. So if anyone else comes here for that, there you go!

TheSt33v said:
I really want to fix the HDR camera bug, and I think I know how, but I need to merge the sparsechunks contained in the most recent 5.1 image. I can't seem to figure out how to do that. Can anyone enlighten me?
EDIT: Never mind. I figured it out.
Click to expand...
Click to collapse
There's no HDR bug on these phones. I use HDR every day for a year, since I got two Quark phones on both stock rooted ROM and custom ROM.
If you had a problem on Mofo that has nothing to do with this phone, but the fake root or something with Mofo.

ChazzMatt said:
There's no HDR bug.
Click to expand...
Click to collapse
As I mentioned previously, this old post was referring to the fact that camera apps force closed on 5.1 based roms that were flashed using mofo after taking a picture with HDR enabled. This issue was solved by myself and everyone else who made mofo-ready roms by setting SElinux to permissive. It is not relevant, and has not presented, on phones with with unlocked bootloaders. And yes, I realize that there never was anything wrong with the functioning of HDR, but everyone else was referring to it as the "HDR bug," so I kept this term to avoid confusion.

TheSt33v said:
As I mentioned previously, this old post was referring to the fact that camera apps force closed on 5.1 based roms that were flashed using mofo after taking a picture with HDR enabled. This issue was solved by myself and everyone else who made mofo-ready roms by setting SElinux to permissive. It is not relevant, and has not presented, on phones with with unlocked bootloaders. And yes, I realize that there never was anything wrong with the functioning of HDR, but everyone else was referring to it as the "HDR bug," so I kept this term to avoid confusion.
Click to expand...
Click to collapse
Sorry, I didn't see it was an old post. Didn't realize someone had resurrected it.

I'm still trying to figure out why Motorola went with sparse chunks, instead of traditional deltas.
Sent from my DROID Turbo via Tapatalk. Now with that cyanogenmod goodness.

Related

[App] Atrix Webtop Unlocker - ** BETA **

Being a Linux guy, all these batch files have been driving me mad
Anyways, in an effort to benefit from all the great development that has been going on around the Atrix, I started converting some of the batch files to Bash scripts, for me, and my Linux brethren to to enjoy. However, I quickly realized this was creating parallel development paths, and scripts presented limitations that were becoming hard to manage, so I decided to create an Android App. My hope is this will provide a more universal appeal, and remove host OS dependencies.
After a couple of weeks of getting up to speed on Java, I now present the “Atrix Webtop Unlocker” Android Application! This is very much a work in progress, but with feedback from the community, we will be able to improve the app to the point it will be very user friendly and useful.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
In a nutshell, this application is the Android version of Sogarth's wonderful script: http://forum.xda-developers.com/showthread.php?t=1000316
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Like all of my other projects, this is open source, and available for download at: https://github.com/mistadman/Atrix-Webtop-Unlocker, or via an apk binary download attached to this post.
I eagerly await your feedback and input!
Last, but not least, thanks goes out to--in no particular order--Sogarth, bartsplanet, godwin1981, Ririal, Fenny, and all the rest of the XDA Community! A lot of what you did heavily influenced the development of this app. Also, if I left anyone out, I apologize in advance.
***NOTE - At this time, this app requires your device to be rooted and has only been tested on AT&T v1.57.
*** So one bug I am sure some will encounter is the rotation bug. I have to make AsyncTask play nice with Activities that are destroyed during screen rotations. Fix coming soon, but in the mean time, try not to rotate the phone while running this app :-( ...Did I mention this was work in progress? LOL!
I wont have time to mess with it til Sunday, but ill test it out then and let you know how it goes.
Sent from my MB860 using XDA App
does it have to be stock launcher? I'm having issues setting up LXterminal off of Gingerblur 3.1.
Correction: Gingerblur 3.1 has some problems with it...i've done 2 flashes and tried 1.5.7 with and without 3.1 and i do notice that Webtop mode has some problems with Firefox specifically and LXterminal is missing.
Is there a chance of this working on 1.8.3?
Sent from my MB860 using XDA App
XxKILLx3RxX said:
Is there a chance of this working on 1.8.3?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
in theory it should since the webtop is the same version on 1.5.7
Mafisometal said:
in theory it should since the webtop is the same version on 1.5.7
Click to expand...
Click to collapse
Actually, it's not. There are quite a few differences between the 1.57 and 1.83 webtops. They removed a lot of binaries and changed some things around. Be wary installing this on 1.83, it'll probably break your webtop and you'll have to reflash.
Ririal said:
Actually, it's not. There are quite a few differences between the 1.57 and 1.83 webtops. They removed a lot of binaries and changed some things around. Be wary installing this on 1.83, it'll probably break your webtop and you'll have to reflash.
Click to expand...
Click to collapse
yeah you're right, i finally got it running and it broke my Firefox, File Manager, and just about every program accessible. It WILL install but it won't function properly. I was under the assumption since 1.83 didn't really affect 1.57 in any major ways besides the HSUPA unlock update that it was the same. On the version notes, it does say the same version on mine though....i don't know why they call it the same when its not.
FYI guys,
My app does not modify/touch the original /osh directory, so at the worse, you will just need to remove the /data/ubuntu.disk file, reboot, and you're back to stock Webtop. No re-flash necessary if something goes wrong.
Mafisometal said:
yeah you're right, i finally got it running and it broke my Firefox, File Manager, and just about every program accessible. It WILL install but it won't function properly. I was under the assumption since 1.83 didn't really affect 1.57 in any major ways besides the HSUPA unlock update that it was the same. On the version notes, it does say the same version on mine though....i don't know why they call it the same when its not.
Click to expand...
Click to collapse
Hmmm. What you can try is downloading the GladiAtrix3 beta I have, and pulling the domain_policy.conf from the lxterminal folder inside the zip and installing it onto your phone. See if that fixes anything. The issue is that all the versions are different, and tomoyo just says "**** no" to everything you try to run because it's not specifically allowed in the policy. The file in GA3 is from a 1.83 webtop, modified to allow awn and lxterminal to run unrestricted.
EDIT: I'll just attach the file, it's easier for everyone Let me know if it fixes anything
EDITEDIT: Make sure you're replacing the file in the loaded image, not in the stock /osh directory.
Ririal said:
Hmmm. What you can try is downloading the GladiAtrix3 beta I have, and pulling the domain_policy.conf from the lxterminal folder inside the zip and installing it onto your phone. See if that fixes anything. The issue is that all the versions are different, and tomoyo just says "**** no" to everything you try to run because it's not specifically allowed in the policy. The file in GA3 is from a 1.83 webtop, modified to allow awn and lxterminal to run unrestricted.
EDIT: I'll just attach the file, it's easier for everyone Let me know if it fixes anything
EDITEDIT: Make sure you're replacing the file in the loaded image, not in the stock /osh directory.
Click to expand...
Click to collapse
alright cool, thanks, seems like it's working great.
EDIT: Also, just so everyone knows...1.8.3 breaks webtop. I've done a few flashes from stock 1.2.6, 1.5.7, and finally 1.8.3...the sbf breaks webtop functionallity.
mistadman said:
*** So one bug I am sure some will encounter is the rotation bug. I have to make AsyncTask play nice with Activities that are destroyed during screen rotations. Fix coming soon, but in the mean time, try not to rotate the phone while running this app :-( ...Did I mention this was work in progress? LOL!
Click to expand...
Click to collapse
I didn't encounter that problem when i had it on lapdock.
Mafisometal said:
EDIT: Also, just so everyone knows...1.8.3 breaks webtop. I've done a few flashes from stock 1.2.6, 1.5.7, and finally 1.8.3...the sbf breaks webtop functionallity.
Click to expand...
Click to collapse
I've done the same thing (sbf 1.2.6 -> 1.5.7 -> root -> webtop unlocker -> 1.8.3 -> gingerblur) but I lost completly entertainment center and webtop.
Removing webtop unlocker I restored entertainment center. Reflashing gingerblur webtop over hdmi still won't work.
Ririal said:
Actually, it's not. There are quite a few differences between the 1.57 and 1.83 webtops. They removed a lot of binaries and changed some things around. Be wary installing this on 1.83, it'll probably break your webtop and you'll have to reflash.
Click to expand...
Click to collapse
I wanna say both of you and OP are correct.If you are under stock 4.1.83 webtop files,they are different from 4.1.57..But if you have done webtopmod cracked,the file will be replaced by v 4.1.57 cracked files.
godwin1981 said:
I wanna say both of you and OP are correct.If you are under stock 4.1.83 webtop files,they are different from 4.1.57..But if you have done webtopmod cracked,the file will be replaced by v 4.1.57 cracked files.
Click to expand...
Click to collapse
Well, no. The webtop mod uses your current /osh as a base. The problem is that it's making a lot of assumptions from 1.57 files. Things got changed up in 1.83, and it causes problems.
If you're talking about the webtop through HDMI mod, then we're talking about two completely different things
Ririal said:
Well, no. The webtop mod uses your current /osh as a base. The problem is that it's making a lot of assumptions from 1.57 files. Things got changed up in 1.83, and it causes problems.
If you're talking about the webtop through HDMI mod, then we're talking about two completely different things
Click to expand...
Click to collapse
I think you are correct.
so this its working on .83 ????
zen kun said:
so this its working on .83 ????
Click to expand...
Click to collapse
No...
Sent from my MB860 using XDA App
Hi,OP.
when will you release the updated version for V4.1.83?
Is this apk going to be updated? I want to test the latest version...
arvati said:
Is this apk going to be updated? I want to test the latest version...
Click to expand...
Click to collapse
I second that! I would love to have something like this for the latest version of webtop... there has been a lot of neat stuff going on with it, but everything is scattered about. I would love for someone who has knowledge in this area to pull everything together.
for the rotation issue.. in the manifest.. on the activity.. set android:configChanges="orientation" ..

Cyanogenmod 10 PORT from RAZR HD

Yo Guys
This is the CM10 build for the Motorola RAZR HD, uploaded here with the boot.img from the Atrix HD (Matt says this isn't necessary, but I'd rather give you something I've tried and worked, than something maybe broken )
Full credit to dhacker29 and Hashcode for this build.
Everything else is stock for the RAZR. Anyone and everyone should take this and help get a usable CM10 for us, and maybe get our community hopping a little!
OG Link to RAZR thread
Link to download
Google Apps
Steps:
Create new ROM slot in SS3
Install from zip
Reboot
Alright, I guess that's about it. Enjoy.
I pretty hastily uploaded this to the Dev section, if it belongs in General, don't hesitate to move it. Thanks!
ripin150 said:
-Coming Soon-
*And I don't mean soon like, I have the intention of making it, I mean soon like, I'll upload it when I'm not at school
When it's here, anyone please feel free to take it and fix it up, because my expertise level ends at getting it to boot. I'd really only recommend flashing if you Can Not wait, or if you want to spiff it up.
*Questions I can answer now*
Yes, this is the RAZR HD's build of CM10 injected with our kernel and build.prop
No, I probably wouldn't use this as my daily-driver yet
Wifi? Nope
HSPA says it's there, but signal bar is 0%. I got a text though, so I don't know how much is getting through.
This is 4.1.1
No Camera, but that's broken on RAZR too.
Again, I'm sorry for having to put this Hold thread up, but I really don't have the resources to share it all right now. See you soon.
Click to expand...
Click to collapse
Of course, giving credit to Hashcode and Dhacker29 for doing the entire thing... right? Also, you didn't need to change out the boot.img because it automatically detects it is not a developer edition and won't flash it. Build.prop doesn't matter either, it will boot either way.
Something that would be very helpful is fixing WiFi with Atrix HD libs/modules
mattlgroff said:
Of course, giving credit to Hashcode and Dhacker29 for doing the entire thing... right? Also, you didn't need to change out the boot.img because it automatically detects it is not a developer edition and won't flash it. Build.prop doesn't matter either, it will boot either way.
Something that would be very helpful is fixing WiFi with Atrix HD libs/modules
Click to expand...
Click to collapse
I didn't know about the boot.img, I was just told that it wouldn't boot for us because of the boot.img, but thanks for clarifying! And absolutely, ALL the credit goes to them, I'll put that in the op now that I'm home.
Just a question: How can we "repair" the wifi and all these things? Just replacing the files from the stock JB leak or what? I'm curious...
The OP needs to write a changelog or features working/not working. Thanks.
Sent from my MB886 using xda app-developers app
joel_sinbad said:
Just a question: How can we "repair" the wifi and all these things? Just replacing the files from the stock JB leak or what? I'm curious...
Click to expand...
Click to collapse
Just replace the updater script with the one attached to this post.
Will fix Wifi!
del
centipedes said:
doesn't work.
sits at black screen, backlight turns on for a second, then turns off. this repeats until reboot into safestrap.
Click to expand...
Click to collapse
No telling what the OP did to the ROM, as nothing but the updater script needed to be changed, yet he stated he changed a few other things.
Let's hope he hasn't abandoned the thread and is fixing it now.

[8.1] [Magisk Module] Multi-Touch Fix for 8.1 Devices running LOS/AOSP

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.

Android Q and the view from here..

As most of you all know i am an avid phone explorer. Lol. Yes corny as it sounds, but i can get all sorts of things one would not normally try to flash to flash and actually boot. Myself and proto devano (sp) are going to port this Android Q leaked image or whatever soon as we get it. For the op6 and op6t..if anyone happens to have any insight as to where to procure this, please lemme know..
i have already flashed the pixel 3 and 3xl system images and gotten them to boot on my op6t. Not the port, the firmware. My friends are aware of the progress. Calls, web, and text work. Navigation is broken but i do know how to fix it with a few bits of hackery. But its not at the top of my list as i have been source building again and trying to learn new device bring up, which i hadnt done before. ( I have built roms but always a continuation of an existing project). So this will be my next port soon as we get the image, payload.bin, etc. If u can help, great, let me know. We can bring Q to oneplus, early.
this oh WOW... sounds very exciting ?
I was just reading about Q on XDA here https://www.xda-developers.com/android-q-dark-theme-desktop-mode-permission-revamp/
I wonder if the author of the news might be of some help in getting it being that they were testing it out?
Jeffro64 said:
I was just reading about Q on XDA here https://www.xda-developers.com/android-q-dark-theme-desktop-mode-permission-revamp/
I wonder if the author of the news might be of some help in getting it being that they were testing it out?
Click to expand...
Click to collapse
Yea he helped me get the mclaren files before. I emailed him. So, we will see
fullofhell said:
Yea he helped me get the mclaren files before. I emailed him. So, we will see
Click to expand...
Click to collapse
Cool...Maybe he will help you out again. I leave tomorrow morning to go back to work offshore so I will be out of the loop until I get back. I'm already excited to see how far the progress on this phone has gone when I get back! Should get my unlock token today even though it's not really needed any more, but I figured it will be good to have if I ever decide to put the stock software back on the phone after I move to the International software. It's going to be a long hitch out there thinking about all the OP6T goodness cooking up while I'm gone LOL!
delete
liam_davenport said:
Possible Android Q GSI
https://mega.nz/#!B1pmxYwa!Gj6zHOofpGnqZmbtHsFIz5MZptnc8qvyX4pZlIxN-V0
Edit: can't post the source XDA is blocking the link as it's another forum.
Use with caution as not tested.
Click to expand...
Click to collapse
Awesome man! Thank you very much!
Man, I'd love to get the Pixel software on the 6t....call screening is a huge benefit; and the only reason my (converted to int'l) 6t is the fallback device to my P2XL. If I could get the pixel images running on this thing well - it'd be game over for my 2xl...
One can dream, right?
PhoenixPath said:
Man, I'd love to get the Pixel software on the 6t....call screening is a huge benefit; and the only reason my (converted to int'l) 6t is the fallback device to my P2XL. If I could get the pixel images running on this thing well - it'd be game over for my 2xl...
One can dream, right?
Click to expand...
Click to collapse
I am working on it, prob really is the navigation bar is derped. Patching a few things may fix it.
fullofhell said:
I am working on it, prob really is the navigation bar is derped. Patching a few things may fix it.
Click to expand...
Click to collapse
Holy Shift dude, that is fantastic news! If you need any help or testing, let me know; this would totally put my 2XL out to pasture.
liam_davenport said:
Possible Android Q GSI
https://mega.nz/#!B1pmxYwa!Gj6zHOofpGnqZmbtHsFIz5MZptnc8qvyX4pZlIxN-V0
Edit: can't post the source XDA is blocking the link as it's another forum.
Use with caution as not tested.
Click to expand...
Click to collapse
Fake. That's just AOSP master with December security patches, ie. no internal Google patches.
fullofhell said:
Yea he helped me get the mclaren files before. I emailed him. So, we will see
Click to expand...
Click to collapse
Sorry, I can't share the files publicly :crying:
MishaalRahman said:
Fake. That's just AOSP master with December security patches, ie. no internal Google patches.
Click to expand...
Click to collapse
Okay thanks for clarification will remove the link.
Hmm that stinks, it doesn't have the system dark so must be but the other stuff in the review are in this. Here's some screenies. Says Q but anyone can do that..strangely enough it works just as crappy as the Jan pixel 3 stuff I flashed..thanks anyways guys
fullofhell said:
As most of you all know i am an avid phone explorer. Lol. Yes corny as it sounds, but i can get all sorts of things one would not normally try to flash to flash and actually boot. Myself and proto devano (sp) are going to port this Android Q leaked image or whatever soon as we get it. For the op6 and op6t..if anyone happens to have any insight as to where to procure this, please lemme know..
i have already flashed the pixel 3 and 3xl system images and gotten them to boot on my op6t. Not the port, the firmware. My friends are aware of the progress. Calls, web, and text work. Navigation is broken but i do know how to fix it with a few bits of hackery. But its not at the top of my list as i have been source building again and trying to learn new device bring up, which i hadnt done before. ( I have built roms but always a continuation of an existing project). So this will be my next port soon as we get the image, payload.bin, etc. If u can help, great, let me know. We can bring Q to oneplus, early.
Click to expand...
Click to collapse
Hey...I see I am a little late to this party, but I read recently we are getting a dev preview of Q "officially." I found a link to a GSI zip and a recovery (not the mega one in this post), but there is no installation guide. I did this with P on my last phone (G5+), so I know there is a little more to the process than a simple flash. I am pretty sure I should not post the link, but PM me if you can shed any light. Thanks in advance...
hithekillswitch said:
Hey...I see I am a little late to this party, but I read recently we are getting a dev preview of Q "officially." I found a link to a GSI zip and a recovery (not the mega one in this post), but there is no installation guide. I did this with P on my last phone (G5+), so I know there is a little more to the process than a simple flash. I am pretty sure I should not post the link, but PM me if you can shed any light. Thanks in advance...
Click to expand...
Click to collapse
Message sent.
The picture in selfie is Blue.
V. 3.9
OnePlus 6T
Now that Android Q Beta 2 GSI images have been released, anyone tried to boot them on OP6T? If yes, please share your valuable feedback.
gururoop said:
Now that Android Q Beta 2 GSI images have been released, anyone tried to boot them on OP6T? If yes, please share your valuable feedback.
Click to expand...
Click to collapse
Doesn't boot
Yeah I tried both, and with 9.012 and beta 7. Gonna try with custom vendor and stuff..
And why would you port a leaked/early/beta version of system? What's the logic?

{ROM} GSI Lineage OS For Our Redmi 6!

Hi There Everyone!​First a brief: I've been a longtime XDA user, but never found the need to create an account. Now, I bought a Redmi 6 and I'm really disappointed by the development:crying:, so I thought i'd chip in a bit I don't have permission yet, so I posted this here.
As you know, till now there are NO Custom ROM's available. This is really sad, and I can't live with MIUI. So I decided to give GSI (Generic System Image) ROM's a try.
And guess what? They work! I tried installing Lineage OS 15.1 on our cereus. The rom is really fast and smooth. Here's what I found:
Working:
Wifi
Bt
Camera
Vibration
Sound
Finger Print
Bugs:
SIM detected, but no range found. RIP calls/sms/data. Looks like a problem with the raido's.
Headphones don't work
I couldn't test hotspot and gps.
Even though there is a bad bug, it still works surprisingly on this MediaTek SoC with no drivers / kernels. All we need is a little paching and we should be good to go!
Give it a try. Ill post guide on how to do this later. For now, i'm using miui cuz i wanna make phone calls
Here are screenshots:
https://ibb.co/J7FRk9K
https://ibb.co/sbNk3N4
https://ibb.co/K5KDW43
https://ibb.co/5Mfrz0d
https://ibb.co/kHCwqb2
https://ibb.co/S3X9gkv
https://ibb.co/1JYNmqp
Yes, we know. We tested this long time ago, there are pretty long discussions in twrp thread comments
What about finger print reader?
TanRayCz said:
Yes, we know. We tested this long time ago, there are pretty long discussions in twrp thread comments
Click to expand...
Click to collapse
I know, and I've read through all that. They are all buried inside TWRP threads, and not everyone knows about GSI. I made this so people know, and I'm also going to make an other thread with instructions on how to flash a GSI rom for our Redmi 6 soon (It's a little tricky getting TWRp to work and all...)
hiitsrudd said:
What about finger print reader?
Click to expand...
Click to collapse
It works! Sorry, I forgot to mention that - added it now :good: Btw, even though it works, it isn't as accurate and as fast as MIUI.
Tech_Expert said:
I know, and I've read through all that. They are all buried inside TWRP threads, and not everyone knows about GSI. I made this so people know, and I'm also going to make an other thread with instructions on how to flash a GSI rom for our Redmi 6 soon (It's a little tricky getting TWRp to work and all...)
Click to expand...
Click to collapse
I meant to say good job about putting this all together. Nice.
I just randomly remembered when i was trying this ROM some time ago. Headphones doesn't work.
(Adding this to post would be ideal)
Edit: It could also be the Pixel Experience ROM. But i don't remember.
TanRayCz said:
I just randomly remembered when i was trying this ROM some time ago. Headphones doesn't work.
(Adding this to post would be ideal)
Edit: It could also be the Pixel Experience ROM. But i don't remember.
Click to expand...
Click to collapse
Thanks! I tried LOS again, and I can confirm that headphones don't work. Added that to the post:good: Btw, do you know any GSI ROMs for Cereus that can actually make calls and work well?
Tech_Expert said:
Thanks! I tried LOS again, and I can confirm that headphones don't work. Added that to the post:good: Btw, do you know any GSI ROMs for Cereus that can actually make calls and work well?
Click to expand...
Click to collapse
All i tried was LOS and Pixel Eperience. Both are same, except PE has Android 9.0. I tried treble RR, it had really cool logo while booting, and i was really excited for RR because i never tried it. But i never made it to boot. Boot logo is looping infinitely and i tried fresh installing (With MiFlash clear) about 10 times.
Edit: Maybe if you would want to, you can give it a try https://forum.xda-developers.com/pr...0-resurrection-remix-v7-0-arm64-32-b-t3891636
Edit: I didn't understand most of it, but i could start adb logcat while booting. From all i could understand, all apps were dying and restarting all over.
https://drive.google.com/file/d/1KSfa8BcgQtEdnHQnbQ8mhGx_rDHSDD7t/view
Omni rom, android 9, works pretty good, no major bugs.
Installation instructions on screenshot in attachments.
[email protected] said:
https://drive.google.com/file/d/1KSfa8BcgQtEdnHQnbQ8mhGx_rDHSDD7t/view
Omni rom, android 9, works pretty good, no major bugs.
Installation instructions on screenshot in attachments.
Click to expand...
Click to collapse
That's nice and all, but more info would be cool. SIM works?
TanRayCz said:
That's nice and all, but more info would be cool. SIM works?
Click to expand...
Click to collapse
Yep, only USSD is broken by default. See 11) on screenshot.
Calls/sms works out of box.
Don't know about volte since my carrier doesn't support it.
[email protected] said:
Yep, only USSD is broken by default. See 11) on screenshot.
Calls/sms works out of box.
Don't know about volte since my carrier doesn't support it.
Click to expand...
Click to collapse
Speaking of, what does append persist.sys.radio.ussd.fix=true to /system/build.prop mean?
Sorry if it's something widely know im kind of a noob.
JosifBoga666 said:
Speaking of, what does append persist.sys.radio.ussd.fix=true to /system/build.prop mean?
Sorry if it's something widely know im kind of a noob.
Click to expand...
Click to collapse
Seems that mtk ussd fix breaks something on other phones. So, this is flag to enable it.
------
Ahh, you mean how to append?
Open /system/build.prop file with text editor that has root access, add line to end, save file, reboot.
Or you can do this via adb/terminal emulator:
1) su
2) echo persist.sys.radio.ussd.fix=true >> /system/build.prop
[email protected] said:
Seems that mtk ussd fix breaks something on other phones. So, this is flag to enable it.
------
Ahh, you mean how to append?
Open /system/build.prop file with text editor that has root access, add line to end, save file, reboot.
Or you can do this via adb/terminal emulator:
1) su
2) echo persist.sys.radio.ussd.fix=true >> /system/build.prop
Click to expand...
Click to collapse
But this doesn't fix ussd right?
JosifBoga666 said:
But this doesn't fix ussd right?
Click to expand...
Click to collapse
I haven't tested this, but why do you think so?
[email protected] said:
I haven't tested this, but why do you think so?
Click to expand...
Click to collapse
Since you said ussd is broken by default i thought that that wouldn't fix it.
JosifBoga666 said:
Since you said ussd is broken by default i thought that that wouldn't fix it.
Click to expand...
Click to collapse
By default — right after installing, without adding this line.
[email protected] said:
By default — right after installing, without adding this line.
Click to expand...
Click to collapse
Oh my bad. By the way I'm going to install this rom and I'll see if that line fixes ussd. Then we'll have a probably fully functional rom for the redmi 6. ****ing finally. It's about time.
JosifBoga666 said:
Oh my bad. By the way I'm going to install this rom and I'll see if that line fixes ussd. Then we'll have a probably fully functional rom for the redmi 6. ****ing finally. It's about time.
Click to expand...
Click to collapse
It doesn't work for me. Same as every single other GSI rom.

Categories

Resources