yashsingh1/xdaforums huggingface dataset:
[Android General] AeonFlux1603:
Everything I'm using comes from the latest Magisk Modules. I'm using the Dolby Atmos Collective module and the AM3D Zirene module. I'm on the current Magisk Manager (v7.0.0) and the latest stable root (v18.1). I'm using the BusyBox for NDK Magisk Module, and I am running SELinux Permissive using Kernel Adiutor-Mod (available here on XDA for free). I'm running Permissive for reasons other than Dolby Atmos and AM3D, so it probably isn't required. I'm just giving you my complete setup.

Here is the support thread for AM3D Zirene, or you can find the module in Magisk in the Downloads section. https://xdaforums.com/android/apps-games/mod-zirene-sound-am3d-t3396698
[Android General] AeonFlux1603:
[MENTION=8548258]wezroot2k[/MENTION], did you get the AM3D setup going?
[Android General] wezroot2k:
NO same white screen. Still trying though maybe try an older version or something.

any ideas?
[Android General] pndwal:
[MENTION=8548258]wezroot2k[/MENTION], [MENTION=9720847]AeonFlux1603[/MENTION]

I see AM3D is first on the list of Magisk audio mods currently supported by AML, and the mod that appears in Magisk Manager, Downloads, search 'AM3D', is adapted by [MENTION=5357345]ahrion[/MENTION] & [MENTION=6037748]Zackptg5[/MENTION], so it should 'just work' with Magisk root. PW.
[Android General] AeonFlux1603:
Good to know PW. I've never used AM3D without Magisk, so that analysis makes sense. I know it's the best stand-beside audio mod I've ever used. Now I see why you are such a supporter of AML.
[Android General] pndwal:
Yeah - as with Viper, there may be iterations of AM3D for magisk by other modders, but I've found if you want trouble free motoring, and a mod that plays nicely with others on the road, choose one (or more) by these guys ( [MENTION=5357345]ahrion[/MENTION] / [MENTION=6037748]Zackptg5[/MENTION]), or that's supported by AML. I think (don't quote me - it's a while ago now) [MENTION=5357345]ahrion[/MENTION] was the one that got viper running in enforcing environment too. PW
[Android General] wezroot2k:
Man AF Still can't get it to work that white screen prob still i even did a full wipe re install the rom and magisk and still nothing. Do u remember doing anything while installing AM3D from magisk or recovery.
[Android General] pndwal:
Are you installing the Magisk module "AM3D Zirene Sound" from Magisk manager / downloads? (- sorry if its a dumb question :) .) PW
[Android General] wezroot2k:
Yes
[Android General] AeonFlux1603:
Other than running SELinux Permissive (which I do not think is necessary for AM3D), I'm not running anything except for Magisk v18.1. I am also running the BusyBox for NDK module, if that makes a difference.

Update: I just thought of something else: I am running insecure boot image support. But, if you are using the installer I put together, you should be also. Later tonight [MENTION=8548258]wezroot2k[/MENTION], after I get home, I'll take a look and see if there's anything else custom I'm doing that would make a difference.

Out of curiosity, have you updated to the most recent stock 6.0 build via OTA? I realize it's an older build, but if your /lk and tee1/tee2 partitions are not up to date that can cause some bizarre occurrences with some apps and mods.
[Android General] wezroot2k:
do u mean youthe one u posted over the other thread with the boot logo missing?

what if have the latest OTA for the 850F installed will that update the necessary partitions also?
[Android General] pndwal:
I think that was a full, but fairly early version of stock. I take it he means latest OTA update (only officially available over the air), version TB3-850F_1300031_171010_ROW.

Can possibility extract from [MENTION=7383447]MotoJunkie01[/MENTION]'s Twrp-flashable-TB3-850F_S100031_171010_ROW.zip which has OTA update incorporated, but I'm doubtful it contains partitions AF mentioned. Incidentally, on my device I can see /tee, (not /tee1, /tee2), but nothing like /lk.

[MENTION=6939319]Hemphiz[/MENTION] found a working link to Twrp-flashable-TB3-850F_S100031_171010_ROW.zip

ROM:

https://drive.google.com/file/d/1f271tqJXL3d2thSnDa-lcNlrwMwDZxQy/view?usp=drivesdk PW
[Android General] Never_Sm1le:
This is maybe a rude request but could you support the TB3-850M too? looks like the development on 4PDA stopped and there is still bugs left.
[Android General] AeonFlux1603:
Does that TWRP flashable stock ROM also flash the bootloader and TrustZone (tee1/tee2) PW? I was wondering on that the other day. If so [MENTION=8548258]wezroot2k[/MENTION], that's exactly what you need to get your partitions all the way up to date.

If not, I may have the most recent OTA captured and saved. I can extract the partitions from it if need be.

Hell, nevermind, our TWRP backs up those partitions. One of us can simply back ours up, convert them to img files and you can install them with fastboot.
[Android General] AeonFlux1603:
Ok I made dumps in TWRP and converted to .img format. Here are the bootloader (/lk) and TrustZone (/tee1 & /tee2). In case the TWRP flashable ROM doesn't update these, you can install these via fastboot:

fastboot flash lk lk.img

fastboot flash tee1 tee1.img

fastboot flash tee2 tee2.img

https://drive.google.com/folderview?id=17Eh1tbrGF9KC3j0OMIkwvvAg6fdcQout

(These partitions are from TB3-850F_S100031_171010_ROW, the most recent stock build)

The tee2 image contains the drivers for USB OTG, which is an odd place for those.

Update: I downloaded the stock ROM that was linked earlier It appears that it flashes to the /boot and /system partitions only.
[Android General] AeonFlux1603:
If I owned the 850M I would support it. However, I have the 850F, not the 850M. Not rude at all, and I wish I could help.
[Android General] pndwal:
I'd be surprised if any custom ROMs do this. [- At times other partitions need updating for correct functioning of a ROM (baseband modem, bootloader etc), but are invariably a separate package / flash as they generally need to be done only once, but ROM may be nightly, weekly etc.] That's why I said I'm "doubtful it contains partitions AF mentioned".

Is there a way to check if in fact these other partitions were updated by OTA? (- I wouldn't have thought of that.) PW
[Android General] wezroot2k:
Update: I downloaded the stock ROM that was linked earlier It appears that it flashes to the /boot and /system partitions only.

does that mean i have to flash the .img files you posted above? Or can i do OTA UPDATE?
[Android General] pndwal:
Yes, that's standard for custom ROM (which is why I was doubtful re extra partitions).

Yes, better flash img files. Simple (although I'm not sure they've actually been updated. :) -shouldn't hurt to try this though). You'd need to revert to stock ROM and stock recovery to run OTA . PW
[Android General] pndwal:
What partitions can you see in TWRP / Backup? I'm only seeing: proinfo, nvram, protect-f, protect-s, uboot, para, Boot, Recovery, logo, secro, tee, frp, nvdata, System, System Image, Cache, and Data.

Do you see /lk, /tee1 & /tee2 here, or elsewhere? Thanks, PW.

Edit: Btw, LOS14.1 February Security Patch available from 2 days ago.

(Bump Security Patch Level to 2019-02-05) PW.
[Android General] wezroot2k:
i just finished doing final OTA on the stock MM 6 firmware
[Android General] AeonFlux1603:
/Ik is "uboot" in TWRP, and tee covers both "tee1" and "tee2"". When you do backups of these in TWRP, look in the backup directory and you'll see what I mean.

However, you are much better off using fastboot to update these. I'm not against using TWRP to update partitions of this nature, but it is unorthodox. Typically, an edify script (TWRP flashable zip package) or fastboot are the most efficient ways.
[Android General] AeonFlux1603:
Sorry I read this after I responded to earlier post. Ok good, now your partitions will be all the way up to date and hopefully this fixes your AM3D glitch.
[Android General] AeonFlux1603:
Yeah [MENTION=7550078]pndwal[/MENTION] I agree. It's rare that a ROM package made for TWRP (especially custom or stock based custom) to include a partition updater in the installation script. Usually a separate updater is used for the partitions (especially gpt.bin type indexes). I'll make a partition updater today for the 850F which brings the partition table up to the most current build, in case any members need it in future.
[Android General] wezroot2k:
Well it looks like AM3D does like my 850F:crying: still get that white screen after everything i have done but i did see a glimmer i did an soft reboot and saw a bit first screen please waiting processing and status bar atop the software but it went back to the blank white screen. I extracted the apk and try to install it with that same prob.

but the info on the apk says that the problem target sdk is lollipop 5.0 so maybe the prob lies with that IDK what do you guys think?
[Android General] pndwal:
So far LOS14.1 for TB3-850F is pretty much LOS-TB3-850M_v3.zip (from 4PDA) with TB3-850F stock kernel substituted, and some tweaks to remove network function interfaces and options etc.

Seems 4PDA devs have made good progress removing bugs by version 3. What bugs do you still experience on TB3-850M? PW
[Android General] wezroot2k:
so i got the AM3D module to work but not on LOS 14.1 but on the stock rom from motojunkie so its safe to say maybe

the bug lies with the app itself and maybe the LOS.

No worries still, i tried the ICE sound module in magisks and i am ok with that setup. Sounds good too with the sound mods.

but still want to try the AM3D so still gonna try find a work around.
[Android General] AeonFlux1603:
Glad you got to try it on stock. I'm befuzzled as to why it's not working on your device on LOS 14.1. Has to be something simple. Hopefully we will figure it out.
[Android General] pndwal:
[MENTION=8548258]wezroot2k[/MENTION] [MENTION=9720847]AeonFlux1603[/MENTION]

I now have LOS14.1 on one of 2 devices. Fantastic! Thanks to you both!

Tried AM3D mod, and have the same empty / white screen problem as [MENTION=8548258]wezroot2k[/MENTION], with or without AML. Viper etc work fine.

Next, I tried this on my Y550 SD410 phone with LOS14.1, and it's the same - white / empty frozen screen. Viper is fine.

So I checked the forums, and it looks like it may actually be the majority who have this problem with recent setups! There's about 20 pages from here - I've only read a few. Something there may help:

https://xdaforums.com/android/apps-games/mod-zirene-sound-am3d-t3396698/page51 Anyway, seems likely its a deficiency with AM3D mod itself.

Not sure why it works for AF - do you have any other Magisk mods installed? PW
[Android General] Never_Sm1le:
I still saw some mention about bugs, but I'm not understand what they are because of Google translate. Besides, Can I flash this on 850M? I don't have intention of using any SIM-related service.

About the Zirene, I also see that on the thread and looks like the app cannot work reliably on android version bigger than 6, the dev also said that Zirene is too old.
[Android General] AeonFlux1603:
This ROM is intended for TB3-850F, and was ported from 850M. Whether or not it will work on the 850M is not known, so that would be an at-your-own-risk basis.

I'm using AM3D on LOS 14.1 on the TB3-850F and running it on Android 9.0 Pie on my LG V30. It may be occasionally unstable on Android versions after 6.0.1 Marshmallow, but so far I've experienced no problems. Our colleague [MENTION=8548258]wezroot2k[/MENTION] is experiencing problems installing Zirene on LOS 14.1 Nougat for 850F. We are trying to iron that out.
[Android General] pndwal:
Yes, I read about LOS14.1 TB3-850M bugs on 4pda too, but I think most are gone in ver. 3. I was just wondering what bugs you have found remaining with latest build on 850M.

Not a good idea to flash on 850M as kernel is different, which is why we had bootloops and instability before we got boot.img for 850F, so I think you will have similar problems using ROM with 850F boot.img on 850M.

However, if you really want to try this ROM, you could extract boot.img from TB3-850M LOS14.1 ROM, then flash TB3-850F ROM immediately followed by boot.img from 850M.

I see. That may be the problem then. PW
[Android General] pndwal:
Noticed [MENTION=4470081]topjohnwu[/MENTION] recommends flashing Magisk in TWRP BEFORE a custom ROM. Did you do this? - I flashed it after. - just trying to work out what's different for us. PW.
[Android General] AeonFlux1603:
I always install Magisk before I install the custom ROM, by first installing the already patched (by Magisk) boot image, then installing the system image. I'm going to rewrite my installation script to install Magisk during the ROM installation, for those members who want root. I won't remove my present unrooted ROM with GApps, but will instead include another link for the Magisk rooted version. So far -- knock on wood -- I haven't noticed any instabilities with Magisk or the modules on our LOS ROM.
[Android General] AeonFlux1603:
[MENTION=7550078]pndwal[/MENTION] what has been your overall experience with this ROM? Other than some glitches and minor instabilities, have you encountered any major bugs, crashes, force closes, kernel panic, etc.? Also, with Magisk, what has been your experience? Thank you.
[Android General] AeonFlux1603:
Yeah I have the BusyBox for NDK module and the SafetyPatch module (to pass ctsProfile in SafetyNet). I may know what is allowing it to work now -- prior to installing Dolby Atmos and AM3D, I had installed the Deuteronomy 2.1 audio library mods and audio mixers system-wide, using an Aroma installer via TWRP. Although I manually uninstalled the Deuteronomy audio mods, I am assuming that the libraries (and maybe the mixer confs??) are still installed system-wide (I'll check this with a root file explorer to confirm). It may very well be the presence of some of these system-wide audio mods which are allowing AM3D to function normally on LOS 14.1. Oddly, however, I am also running the AM3D module on my LG V30 on Lineage 16.0 Pie. On my HTC One MAXX, running on a Nougat build of Resurrection Remix, (Android 7.1.2_r21) AM3D shows a white screen when I try to open it, like the one you guys are describing.
[Android General] pndwal:
Not had much uptime at all yet, just reloaded some apps etc. Other than camera having some difficulty with 1080 video and lack of charging indication when powered down (usually boot.img related) I haven't noticed any problems really. Settings, About still reports 850M. Magisk is fine other than AM3D mod. Will post when I notice any other anomalies. Thanks for your work. PW
[Android General] AeonFlux1603:
I think I have the shutdown charging animation bug resolved, by manually placing a custom shutdownanimation.zip in the path of /system/media/shutdownanimation.zip. I'll keep you posted there. What issues are you having with 1080p video? Are you using VLC or a VLC derivative video codec pack? Thanks for your input my friend. I know you're extremely thorough and concise, so that helps me greatly with working out bug patches.
[Android General] pndwal:
That'd be good. I have that busybox too and AML and Streaming audio patch Magisk mods.

Noticed in AM3D thread someone fixed this problem (its common now) by installing Viper with vol. down option (ie without Aroma), but it didn't help me. (Viper has a number of other installation options, and he might be using a different configuration to me - I didn't try them all.) Still, sounds like its something to do with these auxiliary audio mods / libraries. PW

---------- Post added at 02:48 AM ---------- Previous post was at 02:40 AM ----------

So far just camera slow to respond, and I think loosing frames (could be playback too) when filming 1080. Sorry, these are just casual observations thus far. I was going to report when I've had time to give LOS a more thorough thrashing. :) PW
[Android General] wezroot2k:
look likes we have found the solution to he AM3D prob, mostly with that Deuteronomy 2.1 audio lib mods.

---------- Post added at 02:39 AM ---------- Previous post was at 02:34 AM ----------

Welcome to LOS 14.1 club Honored Member PW:good: looking forward to your:good:indepth analysis.

AF can you send a your contacts so in send you some files via PM.

I want you to test them.

how are the mod coming on AF.
[Android General] AeonFlux1603:
I'm knee-deep into this ROM my friend. Just like a favorite piece of clothing with a couple of rips, frayed material and a missing button, I'm sewing, patching, trimming, and adding lots of good old TLC. PW I have the latest Google Camera app successfully installed on this ROM, so I'm hoping after updating all libs and source code, and after testing, that HDR, Lens Blur, Panoramic mode, and all hi-res video and camera modes will work ok. Thanks PW for your input on bugs and instabilities. And [MENTION=8548258]wezroot2k[/MENTION], good to hear from you also.
[Android General] wezroot2k:
OK im gonna try that out now too.

ok good luck on the mods i know we don't have long to wait on a stable LOS ROM for our beloved 850F. Thanks to you AF.
[Android General] Never_Sm1le:
After about a month of using the original ported rom on my 850M, I found a few bugs.

Miracast do not work (instantly soft reboot when connected sucessfully, this is expected because our device do not support it in the first place);

become extremely sluggish when Live display works (however other night light app works normally);

and this I don't know if it's counted as a bug, but the screen is too bright even at 0% brightness.

Since this is a close port of that rom, I think these bugs would present on this as well.
[Android General] tsaibru:
Thank you for the ROM.

I install the Netflix app, it won't start.

Really appreciate your work!
[Android General] pndwal:
AF - Hope you fully over ailments. My turn now with fever, headache etc. (Stomach fine though :) )

Guess you've been pretty busy like the rest of us. Hope TB3-850F tweaks are coming along nicely. Love a progress report. Regards, PW.
[Android General] AeonFlux1603:
Yes friend, been pretty busy and simply haven't had time to do much of anything extracurricular. Thank you for the sentiment. Yes, been well for some time now, just fully occupied with life's priorities and duties.

I hate to hear you are now suffering with illness. If it's anything like the illnesses going around where I live, it's rough stuff for certain. I'm going to take time this evening to get up to speed on what's happening on our device threads.
[Android General] pndwal:
Fully appreciate the need to prioritise with these things, but happy to hear you haven't fallen of the edge. ;) Looking forward to further development as time permits.

[The main dev for my Y550 phone (I have several), [MENTION=4479868]desalesouche[/MENTION], who's largely single-handed efforts fixing commits, updating device tree, etc etc, for more than 6 years have brought us CM and other mods, and now LOS14.1 (Y550 LOS unofficial Cherry port) with LOS15.1 compiling but not yet booting, suddenly fell off the radar in Nov last year. This is unusual and concerning to the Y550 community as he was regularly active on several XDA forums, but has been missing on XDA since then. We hope he's OK.]

Anyway, take your time and take care.

Kind regards, PW
[Android General] AeonFlux1603:
Yes we certainly hope he is ok. I do not know that dev personally, but I join your concerns in light of my humanitarian nature and my love of hard working and dedicates devs.

As to our device, I hope I get more free time soon. I miss working on this project.
[Android General] CthulhuInMyBrain:
Great thanks for this rom! in 4pda still no news about camera fixing on 850M in los14...
[Android General] Rortiz2:
[MENTION=9720847]AeonFlux1603[/MENTION] is there any specific guide for port a rom for a mt8163 device. All Roms that I try to port end in bootlop.
[Android General] AeonFlux1603:
Does the 850m have a mt8163 chipset? I thought the 850m had mt8735 while the 850f has the mt6735m. Of course, there seems to be some known variants in this regard.
[Android General] pndwal:
& [MENTION=8978978]Rortiz2[/MENTION]

I hadn't heard anything re. mt8163 either, but its still confusing.

The original Lenovo box sticker for my TB3-850F says: CPU:MT8161P. (This runs at 1.3GHz without OC.)

Russian 4PDA forum gives TB3-850F Processor Type: MT8161, and for 850M gives MT8735. (http://4pda.ru/devdb/lenovo_tab3_8:850f, http://4pda.ru/devdb/lenovo_tab3_8:850m)

Kernel Auditor, Phone Tester and CPU-Z etc, all report CPU / Vendor as MT8161P, but some report both, listing hardware or SoC as MT6735, but never as MT6735m.

Build.prop also gives ro.board.platform=mt6735m, but also ro.lenovo.cpuinfo=MT8735P.

MT6735m, MT6735, MT8161P, MT8735P - it's hard to be sure whats correct, or if various different SoCs have been used in 850F, all being throttled to the lowest common denominator.

Hope all this can help somehow. (A kernel modified to allow overclocking should achieve 30% boost easily, so this would be fabulous if it could be achieved.)

Sorry, don't know of porting tutorial. PW
[Android General] AeonFlux1603:
Yes definitely puzzling. The ro.board.platform in build.prop is autogenerated by buildinfo.sh and will give you the correct chipset pretty much 100% of the time. So mt6735m is most likely the 850f chipset, also indicated by lines of code present in a decompiled stock boot image. But, the possibility cannot be ruled out -- especially given the specs listed on your retail packaging -- that there are indeed some mt8161p variants of the 850f. Likewise, with the 850m, mt8735p appears to be the common chipset. But again, after reading the Russian 4PDA blogs, there are apparently variant chipsets for 850m as well. I'm like you [MENTION=7550078]pndwal[/MENTION], and agree that there are possibly multiple chipset variants to both the 850f and 850m Lenovo Tab3 8. [MENTION=8978978]Rortiz2[/MENTION], I am also not aware of a putting guide for the chipset you mentioned. Wish I could be of more help on that.

And amen [MENTION=7550078]pndwal[/MENTION]. Even a little bit of overclock to our 1GHz clock would be wonderful. While I'm convinced it's possible, I am as of now unsure exactly how to put overclock into place.
[Android General] pndwal:
Yes. [MENTION=6864096]NATO66613[/MENTION] knows how with Qualcomm SD 410 as mentioned in discussion thread. I'm hoping he'll give some pointers there. [MENTION=5522475]limited_imagination[/MENTION] PM'd me and has similar hopes, but limited time for imagining... PW
[Android General] Rortiz2:
No no, I mean for my tablet: Aquaris M8 MT8163B. I see this rom and because the 850f have a mt8163p y tried to port it but stuck at BQ logo.
[Android General] NATO66613:
Best I can say is look up oc guides and look at same chip kernel on github
[Android General] pndwal:
Perhaps that's a yoga tab 850f variant, although the ones I can find use Qualcomm.

Our TB3-850F uses either MT6735m, MT6735, MT8161P or MT8735P as I mentioned, but neither myself nor AF have heard of mt8163p variant for TB3-850F or TB3-850M. Perhaps you could provide details. :) PW
[Android General] Rortiz2:
Sorry I wanted to say mt8163...
[Android General] pndwal:
??? :confused:

Our TB3-850F uses either MT6735m, MT6735, MT8161P or MT8735P as I mentioned, but neither myself nor AF have heard of mt8163p variant for TB3-850F or TB3-850M.

...Or mt8163 either! :(

Perhaps you could provide details of model, and complete model number... :) PW
[Android General] Rortiz2:
I think you're not understanding me. I have a tablet with MT8163 and I want to port any custom rom. I've been looking for tablets with the same processor and found this ROM. Then I tried to port it but like all the others, it did not work
[Android General] pndwal:
OK... But its NOT the same processor. :confused:

And you said "I see this rom and because the 850f have a mt8163p..." So I said

"Perhaps that's a yoga tab 850f variant..." because our 850f (TB3, not yoga) does NOT use mt8163p, or any mt8163 variant.

So which 850f has mt8163p, mt8163, or any mt8163(x) SOC?

(My guess is that your port failed as processor is COMPLETELY DIFFERENT - Ours has MT6735m, MT6735, MT8161P or MT8735P as stated. - of course, partition tables etc likely also differ.)

I'd help if I could. :( PW