yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] Matty1993:
Hey mate,

Devvo on the lineage port i love lineage lol what was the original you ported from i might give it a go on it aswell as the 16.0 im attempting :D,

Thats good news on the CR droid though with camera working well etc and mostly bugless

Otg was quite hard it needed to be mounted with a very precise syntax or it wouldnt pick the drive up regardless of it showing that the mount was mounted properly, weird ey haha,

Yeah my mtp is still broken aswell i got no idea ehy though, i managed to get adb sideload functional on it but :)

With changing your dpi in the OS also thats an easy one on my MT6572 it was set to 240dpi on the ****ty TN display and was just all wrong i ended up setting mine to 210 dpi and screen is adjusted amazing youll have to reboot the OS after adding it to your build.proo for the changes to take effect

Add this information without the "< >" into your build.prop at the very bottom

# <rom name> additional build properties

rom.version= <your rom version>

ro.sf.lcd_density= <your desired DPI>

debug.performance.tuning=1

debug.egl.profile=1

debug.egl.hw=1

Give that a go worked a treat for me :)

Some extras you can also try are

# Data speed tweaks

ro.ril.enable.3g.prefix=1

ro.ril.hep=1

ro.ril.hxpa=5

ro.ril.enable.dtm=1

ro.ril.gprsclass=12

ro.ril.hsdpa.category=28

ro.ril.a53=1

ro.ril.hsupa.category=9

ro.ril.def.agps.feature=1

# Enable system setting

debug.sf.hw=1

ro.HOME_APP_ADJ=1

video.accelerate.hw=1

ro.config.low_ram=true

persist.sys.scrollingcache=4

These are some other adjustments i added into my MT6572 build.prop which made a huge diff especially the data speed tweaks give these a try also
[Android Q&A, Help & Troubleshooting] Matty1993:
Might have a looksee if i can find it anywhere,

Funnily enough though the lineage 16.0 im trying to port from is from the motorola E4 woods variant exactly same cpu cortex-A53 just hoping its 64bit as it didnt mention wheather it was or wasnt unfortunately so fingers crossed,

Ill have to reopen the recovery aswell as i stored the recovery.fstab inside of the TWRP applet in Sbin so will need to pull it apart to get it,

No way I've found to modify the dpi anywhereelse but build.prop unfortunately although once entered and device has been rebooted once to initialize the changes the user will not have to do anything, if you set it in place once the build has been flashed by the user even on first boot the changes will be set to what you set, the user wont have to adjust anything,

Give the other tweaks ago aswell i found them really useful on both systems
[Android Q&A, Help & Troubleshooting] Matty1993:
Hey mate sorry for late reply works been bisy as hell haha,

My TWRP should do but i cant guarantee it is working thats one of the things ive not tested on it yet

I managed to take a look at the mount point for otg though aswell i mounted mine as

/otg /dev/block/sda1 /dev/block/sda flags=display="otg";storage;backup=0

Its very temporamental tnough only certain usb drives will work on these dont know how,

Anyhow in regards to your dpi issue,

Ive found a little trick you can try which is to actually remove the build.prop entirely and still have a functioning system all you need to do is transfer all content from the build.prop,

Open up the boot.img and place this information withing the default.prop in return as soon as the system is switched on all these changes are being made before boot, so set your desired DPI when transfering see if that works, i completely deleted my build.prop to test after system runs perfectly and all info is displaying such as model, android version etc

Only just saw your comment about the keys to sorry about that, i would suggest to use the rom keys on the build however if you experience any play store issues you can change the keys to the stock keys from the original phone firmware,

Ive actually used the 5044T 6.0 keys on the MT6572 im building 6.0 for no dramas with the play store at all no force crashes or anything and all sign in and downloads also work perfect you shouldnt have a dramas with the keys on it though hopefully,

With mine being 64 bit i dont think it actually is i think its 32bit but the internet specifically says it has 64bit architecture however i looked at the build prop there is

Cpu.abi.64=

But its left blank there is also only lib within my system & not lib & lib64 so ive been trying to port the rom all wrong no wonder i couldnt even get it to boot :eek: so mines deffo 32bit aswell,
[Android Q&A, Help & Troubleshooting] Matty1993:
Hey mate,

Quick question what tool did you use to compile your rom into a flashable zip, im using android script but theres something wrong with it as every zip i compile it gives error 6 im sure its in the updater binary as when i switch it out with the updater binary from LOS 14.1 it flashes no problem but can't use the updater binary from thay for flash as the perms are differnt within the updater script to what is encrypted withing the updater binary do wont boot,

Ive finally gotten LOS 16.0 unpacked switched out i think all files that will be needed to boot and run what a drama decompiling it aswell

Original file was a system.new.dat.br

I then had to extract it to a system.new.dat

Then had to extract it to system.img.ext4

Then i had to extract the system.img.ext4 just to get to everything what a mission haha

Ive never actually tried porting on newer MTK chips like these before so hopefully i can get it to boot up,

Ive swapped out from /etc

Agps_profiles_conf2.xml

Apns-conf.xml

Custom.conf

Recovery.xml

Recovery.fstab

Recovery-resource.dat

Spn-conf.xml

Trustzone.bin

Aswell as swapping out the /firmware & /mdbb folders completely from stock

Then swapped out from /lib/hw all files with the MT6737 extensions the from just the /lib directory

Libcamera_client

Libcamera_metadata

Libcameracustom

Ive then ported the boot.img using the stock kernel & f.stab

Anything you can think of that im missing so far ? Im under the assumption that as the chips are the same i wouldnt need to swap out from /lib

Lib3a.so

Libacdk.so

Libfeatureio.so

Aswell as all the audio libs aswell
[Android Q&A, Help & Troubleshooting] ollie2012:
So where are we at on rooting this phone?
[Android Q&A, Help & Troubleshooting] Matty1993:
Hey mate ill have to check those tools out as im just not having any luck with this stupid script creator its deffo the updater binary the program makes when compiling thats the issue always error 6, even if i set the EOL conversion to unix and remove all the blank spaces within the updater script which usually clears out the error 6 but not this time lol,

Did some more digging seems these are listed as 64 bit architecture but are 100% not been throgh every folder in system and tore the boot.img right apart nothing 64 bit at all, maybe it was a misprint on the device specs who knows lol

---------- Post added at 02:30 AM ---------- Previous post was at 02:24 AM ----------

Ive compiled philz touch working 100% no issues on 5044T Optus X spirit if you prefer that or alternatively ive compiled TWRP 3.1.0 for the 5044T only thing not functional on TWRP is MTP is still broken,

TWRP : TESTED WITH MAGISK V18 no problems with root at all.

url]https://xdaforums.com/android/development/recovery-t3891883[/url

PHILZ TOUCH lineage themed : TESTED WITH MAGISK V18 no problems at all

url]https://xdaforums.com/android/development/guide-optusxspirit5044d-tmt6737m-t3886631[/url

---------- Post added at 02:31 AM ---------- Previous post was at 02:30 AM ----------

Ive compiled philz touch working 100% no issues on 5044T Optus X spirit if you prefer that or alternatively ive compiled TWRP 3.1.0 for the 5044T only thing not functional on TWRP is MTP is still broken,

TWRP : TESTED WITH MAGISK V18 no problems with root at all.

url]https://xdaforums.com/android/development/recovery-t3891883[/url

PHILZ TOUCH lineage themed : TESTED WITH MAGISK V18 no problems at all

url]https://xdaforums.com/android/development/guide-optusxspirit5044d-tmt6737m-t3886631[/url
[Android Q&A, Help & Troubleshooting] ollie2012:
sorryy, I am new here,

How do i root it and put on a lite Android Rom? Android One or something?
[Android Q&A, Help & Troubleshooting] ollie2012:
Thanks for the reply, have you tried the Optus X Power/ ZTE BLADE A0605? SnapDragon 210?

Lighter and better screen than the spirit

---------- Post added at 01:01 PM ---------- Previous post was at 12:58 PM ----------

Just out of interest, if one person makes a copy of their Rom, can other people use that Recovery backup?

Or do you need to use your own backup, if private info's such IMEI are stored on it?
[Android Q&A, Help & Troubleshooting] Matty1993:
Cheers for that man ill give it a try also im liking the classys kitchen aswell all those extensions i told you i manually extracted and converted just to get to the system folder classys kitchen does it all in about 5 minutes flat youve made my life so much easier adk is ok but this is quite good for being a beta tool, however norm /system file based roms are not yet supported however MTK extractor can decompile and also compile to ext4 another good tool to add to the toolbox really alpreciate you suggesting that to me :)

With architecture yeah i think it may be like that as in the build prop there is an ro. Line reagarding 64 bit but is left blank and correct without original 64 bit libs its basically impossible to port without them,

Still compiling my lineage 16 build if i cant get it to work fimgers crossed i do though ill give the lineage 14.1 from the E3 and see if i cant shim it up to be stable enough as im legit seriously over this crappy stock firmware haha ill see if your cr droid is compatible with the 5044T aswell you might be able to extend the device support list then looks great from the screenshots i saw so far though :good:

---------- Post added at 03:31 PM ---------- Previous post was at 03:25 PM ----------

No lite rom available devlopement has only realy just started for these phones myself and [MENTION=5125635]user154[/MENTION] have developed working custom recoveries,

User154 has a CR droid rom for 5044Y variant of the phone you could try to flash to see if it will boot however if it contains a boot.img it would require the kernel being ported over to the roms boot.img and i strongly wouldnt reccomend flashing unless you have a backup just incase it dosent boot as there seems to be differentisls within our boot.imgs from comparing information on the models,

If you just want root though flash either user154 or my twrp or philz recovery format the data in twrp once booted reboot recovery and flash magisk wipe dalvik and reboot
[Android Q&A, Help & Troubleshooting] Matty1993:
Yeah really liking the classys your right about the mtk headers aswell, i use MTK extractor for boot.img and recovery.img as it unpacks them nice and neatly and kernel is still kept together in 1 file instead of kernel-offset etc etc im gonna see if i can find any 64 architecture with as close to same specs as possible and see if it possible to swap libs out from other vendors never know l, would love to see 64 bit on these, maybe they will eventually intergrate it over time and set the prerequisites for it,

Oh Guess what you can add 5044T to your device support list but should include NV ram libs must be swapped out before flashing im happy to provide mine if you want to make another to get it full suportive on 5044T as i flashed your CR droid zip, first boot took aproximately 4 minutes to boot to main screen from reboot of recovery not a bad time boot time at all :D

Your boot.img is 100% compatible even with the variable change between f.stab and others booted straight up, absolute great work mate, ill see if i can fix the dpi issue for you at first boot aswell hopefully i can work some magic for you
[Android Q&A, Help & Troubleshooting] Matty1993:
Had look saw a few that may have some compatible libs but ill have to do some more research into the specs of the devices,

Yeah i thought it would need porting for sure haha booted straight up, anyhow ill get the nvram libs to you after ive finished trying to port the 16.0 for tonight just couldnt get it to even bootloop funnily enough though i tried to do the lineage 14 from the link you provided me same diff cant even get the thing to a boot animation or even bootloop so its something im doing wrong ill be honest though im far more used to MT6571 - MT6589 mostly they have a very simplistic layout these things are a complete mess of libs and what not is there any chance you can can do me up an exact list of what you did to get the lineage os 14 booting ive got a fairly rough idea on it from but im thinking im missing some of these newer libs ive never seen or worked on before i really to get 16.0 and this 14.1 build hopefully booting :) hate asking for help ive usually got this downpacked but im just so stuck atm haha time for a coffee i think

Ill have a look at your dpi settings either a bit later on tonight or tomorrow morning though and hopefully get it sorted for you its very stable apart from thr dpi issue and no imei on 5044T very smooth aswell,

The default wallpaper on first boot though im not to keen on you should set the second one in on wallpapers as default in the framework-res.apk quite nice wallpapers and the look of everything all round so far though :)
[Android Q&A, Help & Troubleshooting] Matty1993:
Hey mate got some fantastic news fixed your dpi issue and works great now i want to do some additional tweaks but i dont want to touch anything without your prior consent as this is after all your rom,

List of things i would like to change :

1. Boot animation is right out of whack due to the dpi it was originally designed for i would like to build a new one for the device to support the dpi of the device aswell as the google one isnt the best,

2. I would also like to change the default wallpaper within the framework-res also there are quite a few decent nice looking wallpapers i can choose from on device already to be set to the first wallpaper on first boot after flash,

3. I would like to experiment a little with some tweaks to the .props

4. I would like to remove your build.prop entirerly so your system will be more secure from anyone changing your rom information

Let me know if its ok to do the following to it :)

Oh ill have to find some more libs for the imei aswell came up unitially on the device but after reboot was gone again so ill see if i can find the missing libs again lol hopefully will have better luck this time

## EDIT ##

hey mate little update its just come to my attention there is no file manager on the rom and google Gapps dosent supply it from nano to micro so ill ad a cyanogen file manager to it also,

Another note i know you said you wanted 240 dpi set but it was still quite large what ive done is adjusted it to 220 dpi and it looks perfect however ill let you be the judge once i get your approval on the other stuff and get it done and zipped back up so i can upload and get it to you for your opinion

Anyhow i think ill call it a night for tonight 11:20pm here in australia :eek: so tired
[Android Q&A, Help & Troubleshooting] Matty1993:
Hey mate i just set it in the default.prop

Under the following

ro.sf.lcd_density=240

ro.sf.lcd_dpi=320

Worked a treat i also added alot of tweaks to the .prop aswell so im happy to upload it for you so you can just switch the boot.img out and zip it back up and thats it ready for flash, if you want?

Thanks so much also on the permission to make my own thread and rom varaint for 5044T from your 5044Y firmware all 5044T users will be quite happy im sure,

Still no luck on the imei issue but im close, i ran debug logs all night while i was asleep and its pinpointed it to a missing optus dependencies within /bin /lib /etc /framework so im gonna scour them today and get the imei functional on it hopefully,

Oh the bootanimation on your rom looks funny and out of whack due to whomever made the animation i unzipped it to take a look the lcd width & height were correct at 480x854 but if you open the pictures up and play them in a sequence youll see its the images causing the issue there and not the dpi or density so you may want to switch it out with one with some cleaner pics, shame i was hopeing to clean the animation up but as theyre already 480x854 any mods i make to the images will look like crap,

Ive got a nice android colourful bootanimation im gonna add to my rom, ive still not managed to change the default wallpaper though i changed it in framework-res, CRwallpapers.apk etc but it still remains so i think its hiding in another .apk somewhere ill let you know where when i find it :)

Any progress on the port list for me yet ? No rush just uber keen to get lineage 16.0 ir 14.1 up and running for us :D
[Android Q&A, Help & Troubleshooting] Matty1993:
Finally got the imei functional on 5044T with CR droid :D cheeky buggers optus are there are files with sinple names in /bin such as gas etc but one that caught my eye was yes i was thinking i had never seen this before in a /bin folder and "yesoptus" is the actual company name so i transfered that over and the serial number was now there after flash but no imei still i then had to transfer Simaliance from /framework aswell as the /armetcetc .oat then the permission from /etc/permissions over for Simaliance, aswell as the corresponding libs from /lib this brought the imei up once flashed but still calls wouldnt connect for some reason i then transfered all Volte & Vilte files from /etc /bin & /lib from stock to port & voila its now all working :D so 5044T users will indeed get a working 7.1.2 for our devices,

Ive got some theming and stuff to do so should be released in a few days or so thank you again [MENTION=5125635]user154[/MENTION] for allowing me to use your rom as a base for our T variant very much appreciative
[Android Q&A, Help & Troubleshooting] ollie2012:
Hey i dont want to port Snapdragon rom to MT handset LOL

I just wondered if anyone is rooting the Optus line up :P
[Android Q&A, Help & Troubleshooting] Matty1993:
Hey mate legend cheers for that :D hopefully can get the 16.0 up and functional for us eventually,

Ive ended up making mine like a hybrid between lineageOS & CRDroid as both are CM based Roms so its not looking to bad at all, still working on the default wallpaper no idea where that is yet Haha,

Yeah im quite happy bout the imei being fixed on 5044T no more ****ty stock 6.0 on the old Optus X spirit haha lol but what a hassle just to get it working im glad i went on my hunch with the "yes" file in /bin aswell i removed it to see what would happen and sure enough both the imei and serial were gone,

Yeah i did even see the mixploeree before haha i was like hang on theres no file manager then when you mentioned there was i carefully looked at all the icons,

Gotta say i dont like all most file managers but the mixploeres is now deffo in my top 2 just under ES file explorer brilliant looking ui and no lag between folders at all and with root access to system what more could a person want :)

---------- Post added at 01:33 PM ---------- Previous post was at 01:30 PM ----------

Yep me ive got the optus model,

I designed both the TWRP & Philz touch recoveries from the Optus X Spirit,

You wont be able to use user154s rom on your device you wont have an imei number,

Ive spent the day fixing it all up and restoring the imei problem but will be a few more day before its ready, rom is android 7.1.2 and is a base from user154s CRdroid rom with my own modifications to it.
[Android Q&A, Help & Troubleshooting] Matty1993:
Yeah will be great & ive gotten a 14.1 lineage build fully working & functional just need to fix the looks up a bit,

Crdroid lineage hybrid is fully stable and themeing is almost done i just have to do the wallpaper now still havent found it lol,

Yeah really liking the mixplorer, Es is far better now than it used to be i would never touch the older versions due to the security concerns with it these lastest versions are much better than previous although its true once something like tthat happens its hard to bring the name back i guess haha been using the mixplorer more than es lately
[Android Q&A, Help & Troubleshooting] Matty1993:
Hey mate,

Sorry for late reply,

Camera is working perfect and have gotten video functional but its somewhat slow so ive been trying to work that out,

Also the wifi option in settings does not work also so wifi is stuck to on can still connect to wifi but through the pull down just cant turn it off, and substratum themese is crashing so trying to fix that also,

Those are the only two major bugs ive found everything else seems to be working perfect,

im still looking for default wallpaper in Crdroid build to change and then its ready to be released as i already changed it in the framework-res ,

Oh can i ask how you entered the port info in settings also, & is it ok to change it to port by matty1993 instead on that build ?
[Android Q&A, Help & Troubleshooting] Matty1993:
Hey mate,

Yeah happy picture quality is better than stock 6.0 now, still cant figure out the slow video im getting close though ive improved it ever so slightly so is not drop dead slow haha,

Much appreciated on adding my name to the port list in settings also for CRdroid :) saved me the work of adding it and yeah thats all sweet aswell with the info im happy,

Ill set the framework and settings apk in do another debug run make sure everythings going good and then can release the Crdroid,

No luck with 16.0 lineage so far im still plotting away at it looking at the differences currently with the init.****.rc files in boot.img to see if theres variable change within uevent.d & init.rc also im also thinking that possibly my kernel dosent support 8.1 linux and sepolicy, but ill keep plotting away at it along with all the other roms :)
[Android Q&A, Help & Troubleshooting] Matty1993:
Yeah i thought id give it a go seems to be the case of the more technical things i can do but doing simple stuff just inst my fortay it seems hahaha,

Yeah dude ill see if i can find the link is for Motoral E4 woods, it should be portable as there is only lib and not lib64 etc so its deffo a 32 bit and is MT7637M also and uses the exact same arm cortex A-53 cpu its just a matter of working out how to make it boot up on it, ill find the link and pist it here anyway,

On another side not i can finally update my TWRP ive spent roughly 4 hours today porting TWRP 3.2.3-0 for our 5044's works amazingly well also which i wansnt expecting :D