Database Info

[ROM][V0.51][01-nov-2010] HTC 2.1 Senseui Mod for Milestone

(99% DISCONTINUED)​
See MotoIncred/MotoFroyoSense for new versions​
MotoSense, an adaption of the HTC 2.1 SenseUI(version 1.6) from HTC Desire
Image is only compatible with this a milestone A853 , and cannot be installed on other variants of "Milestone" XT720/A854/A855 branded models (yet).
You can also follow updates on Twitter now: Dexter Picard (DexterPicard) on Twitter or
me a Red bull, and you're sure i stay up working on this mod.
LATEST RELOAD PATCH for MotoSense MotoSense v0.51 patch
Old releases :
LATEST FULL MotoSense DOWNLOAD MotoSenseV05
MotoSenseV03​
a image folder goes into /nandroid/adbrecovery on your SDCARD its required to have OpenRecovery on your phone to install this image.[/COLOR]​LATEST PATCH FOR DOWNLOAD
MotoSense v0.51 patch (see top of post)
WIPE YOUR PHONE BEFORE ANY FULL IMAGE IS INSTALLED! (Recovery menu - factory reset)
If you don't you might get constant reboots with the M logo
INSTALLATION:
Use G.O.T Recovery / Open Recovery to install this rom.
Currently require you to install a 2.36 stock rom, before you install this one.
Radio Band Requirements for different countries
Some countries require the original 3G files of your current ROM to work ie.
Canada, Brazil, Venezuela, Germany and some others countries uses a different band for 3G. If u dont backup the 4 original 3G Files and restore it over this nandroid once installed u gonna have poor signal, sms problems and HSDPA loss (even if u set apn and get conection its gonna be crappy one).
Files should be in the /system/etc/motorola/bp_nvm_default/ of your phone.
This can be done using OpenRecovery and a adb shell.
You might check this thread , if a update-nosign.zip file exists for your model. which makes it easier for you to install.
Filenames are:
File_Audio
File_Audio2
File_GSM
File_Seem_Flex_Tables
generic_pds_init​​
STATUS of the functionality in image
Working​Radio (Calls,GPRS,HSPA)
USB
Milestone bootup AC charging
Wireless
Bluetooth (limited but works, only with a few functions)​Not Working​- PINCODE (will not be able to enter any pincode or boot normal)​
Changelog history
v0.51 1-november-2010
- Finally beat the reload issue with SenseUI, it should work alot better now​
v0.5 12 august 2010
- Corrected WorldClock bottom slider icons
- update HTC Camera to support more resolutions and moto recording.
- Changed Motorola VideoCamera & VideoRecorder to work with HTC framework for optimal use of Moto Camera.
Changed Moto Gallery for proper playback of your recordings.
- SDCard is now always "on", so you will notice status is "0 bytes" when you connect to pc. No conflict with wifi anymore.
- Apps2SD support, EXT2 supported.
Use G.O.T recovery or other application to partition your SDCARD Partition no. 2 should be EXT2 formatted
(G.O.T will do this automatically)
- Apps2SD remaining space can be seen in settings -> SD & Phone storage. Look under "Internal Phone storage" which is your EXT2 partition.
- optimized internal storage space. Most apps are now in /system. leaving your with 171MB free internal storage on your milestone.
- WIPE is 100% supported but you loose the following apps, if you do.
(Dock , GreekIME , Maps , MotoCarDock , PersonalPortal , VSuiteApp , QuickOffice , teeter )​NOT SOLVED
- Reloading of Rosie (HTC Launcer)
Reason for not fixing it is that Motorola Milestone simply do not have enough memory for HTC SenseUI to run stable with only 256MB.
the launcher is very memory hungry for all its plugins and graphics.. so sorry, no fix, unless you add 256MB more memory to your phone.
- Bluetooth headset​
v0.42 29 july 2010 (MotoSensev042-update-nosign.zip - attached to this post at the bottom) (type: nosign-update.zip)
build.prop correction (hopefully solves too many sense restarts)​Keyboard light enabled​HTC Camera fix (5M pixel)​
OLD REVISION DATA DELETED, OBSOLETE and not worth writing anymore
WARNING: Use this image at your own risk and i take no responsibility if
you brick your phone.. Image has been tested on a UK milestone and works fine if all files in ADB recovery image is used.

woah, nice work buddy. just got a question, if i apply this rom to my North American Milestone, do i lose the ability to access 3g/hspa network from rogers?

is gps working

i got one guy on IRC from Canada(im from europe, so im not sure on networks you got overthere), he tried it, and it works fine for him
You should try to only flash the system+data image of it, as the cust.img contains telephone info, which might be what you need to keep.
GPS is not working atm..

im new to the motodroids , will this work on the motorola droid or just the milestone ? ive had the droid eris so im not sure if there is a difference between the droid and milestone, sorry for the dumb question,

tazzpatriot said:
im new to the motodroids , will this work on the motorola droid or just the milestone ? ive had the droid eris so im not sure if there is a difference between the droid and milestone, sorry for the dumb question,
Click to expand...
Click to collapse
there is already a senseui for Droid, look for Zeusdroid they made that image.

Dexter_nlb said:
there is already a senseui for Droid, look for Zeusdroid they made that image.
Click to expand...
Click to collapse
ok ill google it to see if i can find it , it is much easier to find eris roms , ive only had this moto droid for to dayz and im lost lol
edit well i found it but it doesnt look like its very functional , if its the one i found

tazzpatriot said:
edit well i found it but it doesnt look like its very functional , if its the one i found
Click to expand...
Click to collapse
Porting is no easy task, when its not about development, and zeusdroid actually do have some customized wireless driver.
But i managed to use the existings drivers from Milestone..
And im probably not going to do programming to make the port perfect, as that not so easy, although i got some experience.. but none within driver programming.

im really happy with the progress dext3r, this is awesome.
just curious, any ETA for GPS fix?

gemini002 said:
is gps working
Click to expand...
Click to collapse
ive just tried to fix this, and GPS will be working in the next release.
as it works now

Dexter_nlb said:
Porting is no easy task, when its not about development, and zeusdroid actually do have some customized wireless driver.
But i managed to use the existings drivers from Milestone..
And im probably not going to do programming to make the port perfect, as that not so easy, although i got some experience.. but none within driver programming.
Click to expand...
Click to collapse
i know , ive ported some roms for the eris , i understand its not easy to make it all work, trust me im not disrespecting any1

crap need gps gunna wait until next update fak really miss sense ui

if i install this rom what happend to my apps also i have app2sd applied is this gunna be a problem???

Dexter_nlb said:
ive just tried to fix this, and GPS will be working in the next release.
as it works now
Click to expand...
Click to collapse
awesome pls release this on the weekend would love to try it out also if this is htc sense ui does it have flash lite and if it does have flash lite would the 10.1 flash that works for 2.1 roms work with this...

SplitSnake said:
im really happy with the progress dext3r, this is awesome.
just curious, any ETA for GPS fix?
Click to expand...
Click to collapse
if you know your way on a few linux commands,
then you're welcome to make it work yourself.
1 . copy the /system/lib/libgps.so from the original milestone 2.36.0 image.
2. flash motosense image.
3. mount /system
and copy libgps.so into the flashed image into /system/lib
and GPS works after a reboot.. So fixed!
of course all done from adb shell.

gemini002 said:
awesome pls release this on the weekend would love to try it out also if this is htc sense ui does it have flash lite and if it does have flash lite would the 10.1 flash that works for 2.1 roms work with this...
Click to expand...
Click to collapse
10.1 for 2.1 senseui roms are not real, it just looks like 10.1,
but the flashlite already reports that number.
and yes, flashlite works fine. tested on a few flash websites.

I have a Telus Milestone and I will consider trying this ROM at some point.
Just to crosspost from the other thread... in another thread I was told the following. Could be useful for keeping 3G.
DAGr8 said:
cmstlist , there is an easy way to retain your baseband just flash the HK sbf , then , copy paste these files and make sure you set the permissions correctly .
Probably safest to do via adb if you dont make sure you reboot ...
for the 3G baseband Hack/Swistch it 5 files from /system/etc/motorola/bp_nvm_default
File_Audio , File_Audio2 , File_GSM , File_Seem_Flex_Tables , generic_pds_init
Click to expand...
Click to collapse
So perhaps if you want to try Motosense on your Telus Milestone, then you should backup these 5 files (and take note of the permissions) before flashing the nandroid image. Then afterwards if 3G doesn't work on the Motosense image, restore the same 5 files.

Ok I wasn't able to flash only certain parts of the nandroid backup so what I did was make 1) a full nandroid backup of the Thai firmware (leaked from GOT) on my Telus Milestone unlocked for Fido, 2) a partial nandroid backup using the options --backup --nodata --nocache --nosystem
Then 3) I flashed all of the motosense backup. Trying a first boot. Will report on whether my NAM 3G is gone.
All I get after the M boot logo is a black screen, followed by a force close notification for system. Nothing else comes up. Long-press Home and I get no recent applications. Oh wait - spoke to soon! Wow, just got the HTC lock screen. Unlocked and now I have the setup screen. Asks me to insert SIM to place calls as if I don't have one inserted. My only option seems to be to press "Skip". Okay, home screen loading up now after the tutorial.
So yeah it's not seeing any phone service and I get "Unable to start Wi-Fi". I'm going to try a second reboot. This time the Droid eye shows up promptly (BTW this is very odd to see because Milestones don't usually have that animation). The phone boots up considerably faster than on the Motorlola firmware. *This* time, I do see cell service. In fact I just got a text message. Wait it just dropped again.
Trying to search for network operators. None showing. Strange! It does see wifi though this time. As the OP implied, DHCP not coming through. Meanwhile my Fido service just came back... VERY weak. Dropped again. Normally both EDGE and 3G are quite strong at my apartment so it's odd. Is it possible this ROM has weaker RF somehow?
Ok trying to set up the APN. Noticing the keyboard doesn't light up. APN set up but still no service. Reboot #3: Yes, wifi works now. Mobile network still very weak. Briefly connected to mobile data and it was EDGE. Test phone call fades in and out. Maps manages to wifi-geolocate me.
Alright, so I'm obviously having connectivity problems and only getting 2G. Let's try flashing back the partial I took from the Thai firmware. To be continued next post.

Okay! Flashed back my partial backup from Thai 2.1. Rebooting. Droid eye comes up, glares at me a couple times, back to the homescreen. Connects to Fido. Disconnects, connects again. I am still connected via EDGE, not UMTS. I try going to *#*#4636#*#* and selecting WCDMA only - no dice.
Alright well this has been fun. But obviously I need my phone service to work so this ROM is not for me. Despite having dutifully pasted the info up above about the 5 files to backup... I neglected to do so. So it's back to the full nandroid of my Thai firmware. But one thing for sure, Sense is very pretty!
Before doing this, I made one attempt to install Superuser.apk using the app installer, and then to install Root Explorer. Root Explorer was unable to get root. Maybe if I installed Superuser via OpenRecovery it'd be happier.
Okay back to normal. Goodbye for now Sense!

Backup restored successfully. I used Root Explorer to back up the 5 files in question to SD. Then I restored MotoSense one more time, and before even booting it up the first time I applied root from OpenRecovery. This time it booted much faster. (Is there any way the stock ROM can be hacked to boot this fast? Wow.)
Again, wifi fails to start on boot #1; succeeds but no DHCP on boot #2; works on boot #3. Signed into my Google account and installed Root Explorer (previously purchased). This time Superuser pops up like it should and we're in. I entered Airplane mode. I pasted in the 5 backed up files from the Thai firmware to /system/etc/motorola/bp_nvm_default after mounting read/write. Then I made sure to fix the permissions. Rebooted without exiting airplane mode.
After reboot I disabled airplane mode. Hey, FULL SIGNAL BARS! I did it. But now it's telling me unable to start wi-fi. Let me add in the APN next. Done.
YES! The little H pops up. I'm getting 3G data! But as soon as the icon pops up, it drops out again. In any case I know I'm connected to UMTS because my cell tower ID in Maps > More > About is 1957869 which is my local UMTS tower. Test phone call is *much* clearer and signal isn't dropping anymore. One more reboot.
On the next reboot, wifi is back. Upon disabling it, the lovely "H" shows up and then flits down to "3G". Testing in browser... hmm nope. Something still missing, don't know what. One more reboot, trying again. Internet works on wifi, but not on HSPA (even though the 3G/H icon comes up).
Sanity check: Dialed *#*#4636#*#*, Phone information. Run ping test.
Ping IpAddr: Fail: IP addr unreachable
Ping Hostname (www.google.com): Fail: Host unreachable
One more sanity check: Switched to GSM only, verified in Maps>About that it's connected to a 2G cell ID (57322). Full signal bars, good call quality. So swapping the files improved both 2G and 3G voice performance.
Since I had a bit more success with this approach, I'm saving a backup for future reference, and on my rare moments of idle time I'll play with it again. But back to stock for now.

[Q] Someone want to create a thread for a Lollipop ROM?

I have created a mostly-functional build of OmniRom 5.1 (Lollipop) for the T959V
However, I don't have enough posts to post in the development section or to put in links. Does somebody want to do this for me? If so, let me know.
The current status of it is:
What works
Taking pictures (very laggy switching between FFC and rear)
RIL
SMS
Data
Recovery
Bluetooth
Wifi
Vibration
Powered-off charging animation
Flash from BML
What is definitely not working
App to SD - not working on i9000 either, complains about insufficient space fixed in git
Tv-out as Omni's aries-common has removed it
Video recording - only captures fuzz fixed in git
What is untested
Everything else
What is probably not working
Microphone mute option doesn't work during calls - not working on i9000
GPS - I actually have a T959P, not a T959V... It was released by Telus in Canada. It is a very similar device (I can run ROMs for the T959V with limited problems - ie sometimes I get wakelocks and the gps never works), it has a different GPS chipset (hence why I have no clue on the status of the GPS) and also uses different cell bands (but I can still use your guys modems but I lose access to the 850Mhz band). I have created a build specifically for the T959V as best as I can guess from teamacid and others' device trees.
Selinux is set to permissive as I don't know how to create the proper policies for the GPS.
For a download and more information, see drive.google.com*open?id=0B7vXjzo0Hj-ifm1KQWNYam9FYWdnaFlXZU5LVnVVSzJxYVU3eHlWZGR1VVNZUWk1V1QzOUk (replace "*" with "/")
Source code can be seen under my github account (username is xc-racer99 there as well) under the android-5.1 and android-5.1-t959v branches

Ooooomg ...im wait ....is amazing the new proyect .....thanks thanks

Quick update:
I've got the video record to work properly now as well as being able to move apps to the SD card.
Selinux is left!
Should I upload a build?

Sure...I have a spare phone somewhere that I can test it. Do you have a Gapps package to go along with the ROM? As far as GPS is concerned, back when Beanstalk 4.4.2 was being worked on, a patch was developed to make GPS work...I'll have to root around in my files and see if I can dig it up...I think the developer deleted all the Beanstalk threads for some reason or another.

Yeah, I took the GPS files from CM-11.0 but I can't test if they work. With regards to the Selinux portion of things, only some parts of it were being enforced in KitKat while everything is now being enforced in Lollipop. GPS was not enforced in KitKat so the policies for it were not in place.
I haven't tried any gapps on it yet but I would recommend trying any of the three from the Omni i9000 thread
forum.xda-developers.com*galaxy-s-i9000/i9000-development/rom-t3054101 (again, replace "*" with "/")
I'll upload a new build as soon as I can verify that it boots - it fixes several issues such as apps2sd and camera that weren't working in the one I already have uploaded.
Also, I'm curious as to what the command "cat /sys/class/sec/gps/hwrev" shows. In CM11, one of the GPS files check this and depending on what it shows it loads a different file. Does this mean that there are two hardware variants of the SGS4G?

Alright, new build uploaded. Follow the "link" from my first post, the build is under the Galaxy S 4G (T959V) folder. Selinux is still disabled, no extra policies have been implemented. Apps2sd and video camera should work.
For flash instructions, just do a data wipe beforehand. You should be able to flash from any CWM 5.0+ or TWRP, regardless of BML/MTD status
Been looking at the gps a bit more, seems that TeamAcid's CM11 did it slightly differently than most other KitKat roms in that it has both a gpsd and a samsung-gpsd. Do you know what beanstalk used? It would be so much easier if it didn't have the samsung-gpsd... However, we still have the funky init.d gps script which checks the hardware revision....

xc-racer99 said:
Alright, new build uploaded. Follow the "link" from my first post, the build is under the Galaxy S 4G (T959V) folder. Selinux is still disabled, no extra policies have been implemented. Apps2sd and video camera should work.
For flash instructions, just do a data wipe beforehand. You should be able to flash from any CWM 5.0+ or TWRP, regardless of BML/MTD status
Been looking at the gps a bit more, seems that TeamAcid's CM11 did it slightly differently than most other KitKat roms in that it has both a gpsd and a samsung-gpsd. Do you know what beanstalk used? It would be so much easier if it didn't have the samsung-gpsd... However, we still have the funky init.d gps script which checks the hardware revision....
Click to expand...
Click to collapse
Link shows Not Found Error 404

Sammpls said:
Link shows Not Found Error 404
Click to expand...
Click to collapse
Sorry about that, I guess i screwed it up somehow.
Try this link:
drive.google.com*open?id=0B7vXjzo0Hj-ifm1KQWNYam9FYWdnaFlXZU5LVnVVSzJxYVU3eHlWZGR1VVNZUWk1V1QzOUk replacing the "*" with a "/"
Seeing as this is my 10th post, I think I'll probably try to open an actual thread for this project. If I do, I'll post a link to it here.

Doesn't work... Why use google drive when there are others better for uploading your files.
xc-racer99 said:
Sorry about that, I guess i screwed it up somehow.
Try this link:
drive.google.com*open?id=0B7vXjzo0Hj-ifm1KQWNYam9FYWdnaFlXZU5LVnVVSzJxYVU3eHlWZGR1VVNZUWk1V1QzOUk replacing the "*" with a "/"
Seeing as this is my 10th post, I think I'll probably try to open an actual thread for this project. If I do, I'll post a link to it here.
Click to expand...
Click to collapse

Sammpls said:
Doesn't work... Why use google drive when there are others better for uploading your files.
Click to expand...
Click to collapse
I was using Google Drive as its something I have an account for already and has plenty of space on. Do you have a suggestion of a site I should use? In the meantime, a direct link to the file is https://drive.google.com/file/d/0B7vXjzo0Hj-iZ0YtQTdoTG5KVW8/view?usp=sharing Hopefully this works...

Google Drive isn't bad at all. I was suggesting that you use another cloud service for uploading the files if it didn't work. (which i didin't do a really good job telling you that)
Thanks, that link works!

Alright, I have opened a devDB thread at http://forum.xda-developers.com/gal...official-omnirom-5-1-galaxy-s-4g-sgh-t3146611
Please post anything there and do not use this thread as I will not be monitoring it.

Google drive is at least better than Mega(especially if you use non top-end devices).

Lineage OS 13 Alpha 4 (links to LOS 14.1 port and TWRP 3.1.0-0 in second post)

Not sure if you guys are seeing this over on androidforums so im posting it here too
READ THIS BEFORE PROCEEDING: I took all the latest updates and was sitting on v20k before I flashed the zip I compiled. I dont know if you have to be, but dont be surprised if things dont work if you arent where I am with your phone.
************************************* Start of dev info***************************************************
kernel sources based off of v20k: https://github.com/touchpro/android_kernel_lge_stock-v20k
all the device and vendor trees are based off of teamregular's work:
h631: https://github.com/touchpro/android_device_lge_h631
msm8916-common: https://github.com/touchpro/android_device_lge_msm8916-common-lineageos13
g4stylus-common: https://github.com/touchpro/android_device_lge_g4stylus-common
vendor: https://github.com/touchpro/android_vendor_lge
also you need a few modded hardware/qcom folders, until the kernel gets updated to play nice with caf sources:
audio-caf: https://github.com/touchpro/android_hardware_qcom_audio-caf
display-caf: https://github.com/touchpro/android_hardware_qcom_display-caf
******************************************End of dev info***************************************************
I would recommend using my TWRP here to flash it: http://androidforums.com/threads/update-twrp-3-0-3-0-built-from-source-2-18-17.1103219/
what I know works:
display
touchscreen
vibration
ril (calling and texting. i cant test data since i dont have a data plan atm)
wifi
buttons
adb
mtp
panel backlight brightness adjustment
camera
video recording
internal storage
external_SD
sound
bluetooth (file transfer, audio)
youtube/netflix (any others i didnt test but i bet they work)
wired headset sound and microphone
microphone
gps/location services
compass
rotation
flashlight and camera flash
nfc (dunno what works and what doesnt, dont have another nfc device or android pay)
notification led
what doesnt work:
double tap to wake
data (manual network selection now works, im getting closer)
maybe some other things
The rom zip:
https://www.androidfilehost.com/?fid=673368273298938085
gapps: http://opengapps.org/ (choose your package to fit your needs. just choose arm and 6.0)
THIS DOESNT COME WITH SU AND THE ONLY WORKING SU I FOUND IS SUPERSU!
Download it here: http://www.supersu.com/download
If you wish to report a bug:
Please give a detailed report of what the bug is, things that could possibly cause it (xposed, magisk, etc) and a logcat that was running while the bug occurred. This means you may have to do things to make the bug occur.
adb logcat > log.txt
And finally, ENJOY!

Also,
Lineage OS 14.1 for the h631/ms631
twrp 3.1.0-0 for the h631/ms631

Hey. I flashed this rom on my friends phone. Its a metro stylo. Everything works but cellular data. Any fix for this?

Support for H635?
This is just for the US model, right? Not for the international H635?

LOS 14.1
Stonkers said:
Hey. I flashed this rom on my friends phone. Its a metro stylo. Everything works but cellular data. Any fix for this?
Click to expand...
Click to collapse
Please elaborate, did you flash this with TWRP and it's all good? I'm still running KATANA and would like to get a little more current.
Thanks!

barguybrady said:
Please elaborate, did you flash this with TWRP and it's all good? I'm still running KATANA and would like to get a little more current.
Thanks!
Click to expand...
Click to collapse
I flashed los 14 with twrp 3.1. cellular data would not work so i restored a backup. Now bluetooth, netflix and youtube wont work in katana rom. Trying to downgrade twrp and flash metro partitions to see if i can get it working.

Any updates on this rom?
Stonkers said:
I flashed los 14 with twrp 3.1. cellular data would not work so i restored a backup. Now bluetooth, netflix and youtube wont work in katana rom. Trying to downgrade twrp and flash metro partitions to see if i can get it working.
Click to expand...
Click to collapse
any updates on this ROM?

whoshotjr2006 said:
Not sure if you guys are seeing this over on androidforums so im posting it here too
READ THIS BEFORE PROCEEDING: I took all the latest updates and was sitting on v20k before I flashed the zip I compiled. I dont know if you have to be, but dont be surprised if things dont work if you arent where I am with your phone.
************************************* Start of dev info***************************************************
kernel sources based off of v20k: https://github.com/touchpro/android_kernel_lge_stock-v20k
all the device and vendor trees are based off of teamregular's work:
h631: https://github.com/touchpro/android_device_lge_h631
msm8916-common: https://github.com/touchpro/android_device_lge_msm8916-common-lineageos13
g4stylus-common: https://github.com/touchpro/android_device_lge_g4stylus-common
vendor: https://github.com/touchpro/android_vendor_lge
also you need a few modded hardware/qcom folders, until the kernel gets updated to play nice with caf sources:
audio-caf: https://github.com/touchpro/android_hardware_qcom_audio-caf
display-caf: https://github.com/touchpro/android_hardware_qcom_display-caf
******************************************End of dev info***************************************************
I would recommend using my TWRP here to flash it: http://androidforums.com/threads/update-twrp-3-0-3-0-built-from-source-2-18-17.1103219/
what I know works:
display
touchscreen
vibration
ril (calling and texting. i cant test data since i dont have a data plan atm)
wifi
buttons
adb
mtp
panel backlight brightness adjustment
camera
video recording
internal storage
external_SD
sound
bluetooth (file transfer, audio)
youtube/netflix (any others i didnt test but i bet they work)
wired headset sound and microphone
microphone
gps/location services
compass
rotation
flashlight and camera flash
nfc (dunno what works and what doesnt, dont have another nfc device or android pay)
notification led
what doesnt work:
double tap to wake
data (manual network selection now works, im getting closer)
maybe some other things
The rom zip:
https://www.androidfilehost.com/?fid=673368273298938085
gapps: http://opengapps.org/ (choose your package to fit your needs. just choose arm and 6.0)
THIS DOESNT COME WITH SU AND THE ONLY WORKING SU I FOUND IS SUPERSU!
Download it here: http://www.supersu.com/download
If you wish to report a bug:
Please give a detailed report of what the bug is, things that could possibly cause it (xposed, magisk, etc) and a logcat that was running while the bug occurred. This means you may have to do things to make the bug occur.
adb logcat > log.txt
And finally, ENJOY!
Click to expand...
Click to collapse
Hey! Why was the "android_device_lge_g4stylus-common" included to build the ROM for h631?

Rotation doesn't work, after flash the rom it work but after a few minutes the rotation not work anymore, is there any fix?

whoshotjr2006 said:
what doesnt work:
double tap to wake
data (manual network selection now works, im getting closer)
maybe some other things
Click to expand...
Click to collapse
Hey, thanks for working on this. I'm trying to get away from Metro stock ROM, but the phone is my entire Internet connection so of course I need data Does that mean it's working for you in your local kit but not in what you uploaded? Either way, I tried manual network selection and it said "registering on MetroPCS" (or equivalent, that was last night so I don't recall precisely) for about 20-30 seconds, then it very briefly flashed a scarcely-readable error message, then bumped it with a message indicating it successfully joined. But I never get a 4G or any similar symbol in the status bar, or any data, so I wondered if there's something I can do, either to force it into submission or to help you out. Thanks again

[FIX][Update Dec 15th][BLUETOOTH FIXD]Boot AOSP-ish ROMs on James_t(Metro XT-1921-3)

After many hours of trial and error, I now understand how to get RR and Lineage to boot with latest firmware updates. NO MORE BLINKING BLACK/GREY SCREEN!
Tested with Resurrection Remix 16.1 and Lineage 15.1 (Oreo)
Simply flash the boot and vendor images to their corresponding partitions using fastboot. Find the proper images from this Tmobile firmware,. https://androidfilehost.com/?fid=11410963190603878004 This method preserves IMEI and Baseband.
Nano/pico gapps work as well. HideProps magisk module can set your fingerprint to Moto E5 Play and get around that unregistered Google sh**. I edit /vendor/etc/fstab.qcom myself with vi and inside TWRP terminal shortly after flashing vendor partition. I do this because zips and other copies held me up. All I change is forceencrypt to encryptable in the data line of the fstab. Magisk 19.3 patches for verity. Another thing I do is move /vendor/lib/libeffects.so to /vendor/lib/soundfx/libeffects.so. Doing this will keep music/audio from studdering when screen is off. Last thing, TWRP 3.3.1 formats data as ext4 by default. We want to format with f2fs or you get corrupted data messages at boot. Happy flashing!
##
I find the earliest of these metro pcs firms have a working vendor image.
https://mirrors.lolinet.com/firmware/moto/james/official/Metropcs/
I got bluetooth working today, and lots of clues where I found the fix...
####Bluetooth
Now that I can set it up from a clean install, here's the basics for Bluetooth...
You'll need files from the stock system image. You can use a backup to get these or also use simg2img with dd and 7zip, I'll make a zip installer when I have more time.
1. Copy the following files, from stock image directory "/system/etc/" to the "/vendor/etc/" directory on device
mixer_paths* (14 files)
audio_* (5 files)
media_profiles* (3 files)
Edit the file /system/etc/ld.config.26.txt
add this text to the very end of line 61 :/system/${LIB}/vnd-sp/hw
You're done! If you did everything as described, and it doesn't work, check the permissions of the files you add to vendor partition with other xml files in same directory. I did mine on the device while running, it worked in place, without rebooting device. The GSI system is new to me, however the "Same Proccess HAL(hardware abstraction layer)" voodoo can likely be configured correctly to fix screen and port other GSIs' to our device.

Any chance of getting lamens terms step by step instructions on how to do this? That is the model I have and really liked those roms when I tried unsuccessfully to make them work last year.

edit: 9/21 6pm
I think it's because mine is TMO variant.
Mattswad said:
Any chance of getting lamens terms step by step instructions on how to do this? That is the model I have and really liked those roms when I tried unsuccessfully to make them work last year.
Click to expand...
Click to collapse
Trying based on this now. I'll update you.. been trying for TOO LONG lol it's almost the same time you posted 2 days ago!
---------- Post added at 04:12 AM ---------- Previous post was at 03:45 AM ----------
I've been up all night trying to get either one to work.. I think I came close but I am stuck at a looping blank screen.
If you could step through a bit more for us? I'd REALLY love to have lineageOS on it.
mrbox23 said:
After many hours of trial and error, I now understand how to get RR and Lineage to boot with latest firmware updates. NO MORE BLINKING BLACK/GREY SCREEN!
Tested with Resurrection Remix 16.1 and Lineage 15.1 (Oreo)
Simply flash the boot and vendor images to their corresponding partitions using fastboot. Find the proper images from this Tmobile firmware,.
Nano/pico gapps work as well. HideProps magisk module can set your fingerprint to Moto E5 Play and get around that unregistered Google sh**. I edit /vendor/etc/fstab.qcom myself with vi and inside TWRP terminal shortly after flashing vendor partition. I do this because zips and other copies held me up. All I change is forceencrypt to encryptable in the data line of the fstab. Magisk 19.3 patches for verity. Another thing I do is move /vendor/lib/libeffects.so to /vendor/lib/soundfx/libeffects.so. Doing this will keep music/audio from studdering when screen is off. Last thing, TWRP 3.3.1 formats data as ext4 by default. We want to format with f2fs or you get corrupted data messages at boot. Happy flashing!
Click to expand...
Click to collapse

I have the Metro PCS version
Moto e5 Play XT1921-3

Mattswad said:
I have the Metro PCS version
Moto e5 Play XT1921-3
Click to expand...
Click to collapse
Ahh That is excellent news. I am about to take a focus supplement, and dive into trying again I'll let you know. I found a few more of MrBox23's posts and I think I MAYBE onto something.... wish me loads of luck. If it works for me I THINK it should work for you, but you might need to start with a diff image than me, or use a different boot and vendor img than I will.. not sure if I can help you find those files or not..
I'll be back later to update what I find.

Sorry I haven't been on for awhile. I'll go ahead and post my working vendor and boot images. On Google drive for download. Doing this will trash your speaker if you play music very loud at all, expect that. I do not understand how to fix it. Other than that it's a daily driver. I have been asked about encryption this and that.. You have to modify fstab.qcom within vendor partition. Also the TWRP for this device will format your data partition as ext4 while the ramdisk and init stack are configured for f2fs(if you try and boot with ext4 data, you get corrupted/encrypted data message). You have to change data partition back to f2fs in TWRP every time you format that partition. Or you could modify the TWRP image like I did to fix it permanent.
Files will be uploaded soon, make sure you understand what's involved before getting into this. I'll answer questions best I can, but this is for those who are dediced and willing to get down on some bootloops to figure it out, especially if you're not used to this sort of thing. Some magisk modules will cause bootloops, do those one at a time and gapps separately. I seriously recommend taking apart the firmware from OP and focus on getting to the aosp boot animation, THEN take care of verity/root and fstab. You're formatting data partition anyway you might as well successfuly backport the graphics first.
Vendor image TWRP backup, put this on its own with boot image. I keep it as vendor_fixed for easy reference. The fstab is already patched if you use mine.
Boot image TWRP backup, it is patched with magisk (19.4 likely) install magisk on your own anyhow. KEEP YOUR ORIGINAL VENDOR/BOOT PARTITIONS! There's stuff in there that you might want later on. Like the /vendor/etc/wifi folder for example or the pieces from the original ramdisk.
Vendor and boot with md5 sums to verify integrity.
https://drive.google.com/folderview?id=1-2KO_iRFTjLv6pyx-7Qmhi8kWZBpVIWD
Wipe everything, including internal storage(after backing up a working system).
Format data partition back to f2fs in advanced wipe options.
Get LineageOS 15.1 beta or RR you can find these here on XDA.
Flash Lineage zip its the old style zip install that copies idividual files, not an image, the boot image it installs needs to be replaced per instructions that follow.
Or flash RR system image from official repository link is found here on XDA.
If you flash a system image with TWRP you'll need to reboot back into recovery right after and resize the system partition in advanced wipe options or your system partion will be incorrect size afterwards, if flashing system with fastboot(recommended) then skip the resize instruction.
After you have a system installed, restore the vendor and boot images from the link. A good approach would be to backup your existing boot/vendor as a pair, then replace originals with downloaded images.
The first time I got this to work, I used fastboot to flash partitions, like this.... I followed instructions within Metro PCS firmware(one of those xml files has the fastboot commands, including some oem options that specify a particular mode) Then i flashed ...RR system, followed by boot/vendor images from firmware referenced in OP. I finished that with fastboot -w option, that was when it worked for me. I dealt with the fstab and boot verity patching AFTER I first saw the default Android boot animation. Once you see that plain white "android" with the slow moving left to right animation, your in. From what I can tell our device needs the older kernel within the boot image and the libs/binaries from the vendor image to get the screen working correctly. Your trading your working speaker, for a working screen. I have attempted to find exactly what it is that's different between the two, but it's over my head. Overall it's relatively stable, go easy with magisk modules, some of them will cause kernel panic(bootloop) use a recovery based magisk tool to disable offending module if this happens. Sometimes the device will not boot normally, usually this means the cache was erased(its okay) for whatever reason and I wait it out, otherwise I restore the vendor_fixd backup I made. I have not had gone back to stock ROM, however I have had to flash the vendor partition to get it booting, usualy happens if i flash a module or when updates break substratum theme.
Good luck!
Oh email me for quick response, within reason.
mrbox24 at gmail
Bonus screenshot and the TWRP 3.1.1 I modified with correct data format. If you have an sdcard with second partition it will show up as "linux" named after the chroot partition from mine.
Screenshot shows LSM kernel found here, yes it works.

mrbox23 said:
The first time I got this to work, I used fastboot to flash partitions, like this.... I followed instructions within Metro PCS firmware(one of those xml files has the fastboot commands, including some oem options that specify a particular mode) Then i flashed ...RR system, followed by boot/vendor images from firmware referenced in OP. I finished that with fastboot -w option, that was when it worked for me.
.
Click to expand...
Click to collapse
thank you for this! (and the files)
questions...
1.) Your files in your zip extract as boot.emmc.win and vendor_image.emmc.win ...
Should we rename them to boot.img and vendor_image.img before flashing?
2.) Is your file TWRP-3.1.1_JAMES_T_f2fs-data.img already fixed to format data as f2fs?
3.) where is the option in Twrp to backup vendor and boot images?
I'm almost ready to dive in...

aka.bugle said:
thank you for this! (and the files)
questions...
1.) Your files in your zip extract as boot.emmc.win and vendor_image.emmc.win ...
Should we rename them to boot.img and vendor_image.img before flashing?
2.) Is your file TWRP-3.1.1_JAMES_T_f2fs-data.img already fixed to format data as f2fs?
3.) where is the option in Twrp to backup vendor and boot images?
I'm almost ready to dive in...
Click to expand...
Click to collapse
Yes TWRP is fixed for f2fs data, also the correct version is 3.3.1 latest for device.
Those files are ready to be RESTORED, not flashed in TWRP. You would replace files in an existing backup with those. I have a fresh backup made from from the earliest metro pcs firmware. I am about to upload. What device do you have?

mrbox23 said:
Yes TWRP is fixed for f2fs data, also the correct version is 3.3.1 latest for device.
Those files are ready to be RESTORED, not flashed in TWRP. You would replace files in an existing backup with those. I have a fresh backup made from from the earliest metro pcs firmware. I am about to upload. What device do you have?
Click to expand...
Click to collapse
Cool. thanks.. So far I have three, 1921-2 At&t (new, prepaid, bootloader unlockable so far, daily phone), an xt1921-5 unlocked bootloader, sim locked to sprint, so far been unable to get another rom to boot, and an xt1921-3 metropcs Gsm unlocked, boot loader unlocked, and now booted to lineage 15.1 thanks to you and phh. Wifi works, and gapps go seem to not crash, I did the register a non-stock rom hoop jump with google. Camera nothing but gray or crashes. Everytime it boots, clock time is wrong. haven't really tested much yet.
Really want to be able to get camera functioning, and test an At&t sim in it before switching it to my daily device. I read that the camera fix was committed to 15.1 but I'm lost as how to apply those patches even if I could find them.

aka.bugle said:
Cool. thanks.. So far I have three, 1921-2 At&t (new, prepaid, bootloader unlockable so far, daily phone), an xt1921-5 unlocked bootloader, sim locked to sprint, so far been unable to get another rom to boot, and an xt1921-3 metropcs Gsm unlocked, boot loader unlocked, and now booted to lineage 15.1 thanks to you and phh. Wifi works, and gapps go seem to not crash, I did the register a non-stock rom hoop jump with google. Camera nothing but gray or crashes. Everytime it boots, clock time is wrong. haven't really tested much yet.
Really want to be able to get camera functioning, and test an At&t sim in it before switching it to my daily device. I read that the camera fix was committed to 15.1 but I'm lost as how to apply those patches even if I could find them.
Click to expand...
Click to collapse
I think those patches are applied at source code level. meaning it would be in a future release. My camera works running Resurrection Remix, on xt-1921-3 try copying [email protected] from stock /system/lib/hw to /vendor/lib/hw, making sure to keep permissions same as others in vendor/lib. im willing to read logs, does your att run lineage? if so, does bluetooth work?
I make custom scripts and have a custom build.prop, for example this.....
resetprop 'media.camera.ts.monotonic' 0
resetprop 'persist.camera.HAL3.enabled' 1
resetprop 'audio.deep_buffer.media' true
Those three lines are saved to a file called mediafix.sh in /data/adb/service.d to be ran at boot. it helps with media and camera issues. As well as a one line file called led-chg.sh
echo battery-charging > /sys/class/leds/charging/trigger
Which turns on the light, otherwise never used, in front of phone when charging.
I think it's important to use a/the real fingerprint from an e5 device along with other properties. To get the best out of the hardware and least error messages during boot. I go through logcat/dmesg and attempt to fix what's broken, like the camera on lineage(works without trouble on rr remix btw). I used hidepropsconf module at first and a sprint fingerprint, but later began using the one found in info.txt of firmware zip.
ill post my work in progress build.prop(hosting it with new vendor and boot images on gdrive) which noticeably improves overall performance and lends to less log errors, or lags and crashes.
I find the vendor/boot firmware here(oldest 2018) https://mirrors.lolinet.com/firmware/moto/james/official/Metropcs/ to work best. Audio is completely a loss though. My speaker is blown now and no Bluetooth unless running stock, not even the headphone jack works. All sound comes from the one speaker, even with headphones plugged in I'm at a loss with that issue.
I also modify the boot image. turns out the 1921-3(possibly others?) uses the sdk26 8.0 android ld(library config) instead of the ld.config.27.txt that matches its sdk level. in fact if i try to force the 27 lib config, the gray/black screen comes back. it boots up, i know because my charger light comes on, but no screen. Anyhow i change the os level in boot config to 8.1.0, this gets me to where i am now with only bluetooth(mixerpath/lib issues i suspect) and a couple missing ui features due to what i imagine originate from missing whitelists in /system/etc/permissions xml files.
Another thing of note is how i spoof the mac adress for wifi, this(and other things) is done by modifying the kernel command line config in boot.img. my second e5 play xt-1921-3 has a broken screen, and serves exclusively as a wifi-repeater, captive-portal, and ssh server/tunnel. i spoof the busted screen wifi mac, with an old device mac address that is still registered on xfininity wifi network. it repeats that connection to my other devices. very efficiciently at that. with 3+MiB/s average. it took some hacking but after i found out the oem partition on this device can be formatted, and removed from the ramdisk/system all together, without consequence(not to lineage, bootleggers, or rr remix that is) and be re-purposed to whatever else. its roughly 700MB in size perfect for a debian chroot with my custom wifi repeater and misc servers. running in its own dedicated internal(FAST)partition. This device, and its kernel level mac spoofing with the now almost phased out WCNSS qualcom configurable wifi firmware, is incredible. the busted screen one has been on every day non stop functioning as a repeater, router with captive portal, and dhcp service, for almost two months. it automatically connects to wifi, kills the android zygote/system server, kills its backlight and starts up a hotspot and sshserver/captive portal, all without cell service, and without any interaction.
Anyway, new mpcs files up soon.....

mrbox23 said:
I think those patches are applied at source code level. meaning it would be in a future release. My camera works running Resurrection Remix, on xt-1921-3 try copying [email protected] from stock /system/lib/hw to /vendor/lib/hw, making sure to keep permissions same as others in vendor/lib. im willing to read logs, does your att run lineage? if so, does bluetooth work?
###bugle added### my Att is an xt1921-2, can't even unlock the bootloader... But 30 bucks isn't bad for a new screen and a new speaker. ###
Another thing of note is how i spoof the mac adress for wifi, this(and other things) .
Anyway, new mpcs files up soon.....
Click to expand...
Click to collapse
Years ago, I used to compile Gentoo to run on some archaic hp tablets... Now I just run Linux mint on somewhat newer hardware. This gave me a limited skillset to get an old Moto mb300 running with gingerbread and CyanogenMod. Everything worked, had them for over 4-5 years, just started really messing up over the summer. Miss the real keyboard.
Thanks so much for the tips and insights. It'll take some time to absorb everything in your post.

aka.bugle said:
Years ago, I used to compile Gentoo to run on some archaic hp tablets... Now I just run Linux mint on somewhat newer hardware. This gave me a limited skillset to get an old Moto mb300 running with gingerbread and CyanogenMod. Everything worked, had them for over 4-5 years, just started really messing up over the summer. Miss the real keyboard.
Thanks so much for the tips and insights. It'll take some time to absorb everything in your post.
Click to expand...
Click to collapse
My first "Android" phone was the HTC HD2 wich was actually a Windows phone that can boot linux from the sdcard. I came across it while learning how to get linux booting on laptops. I was fascinated with booting a mini linux on a portable device. I learned about Android and linux in that way, at the same time. Kernel, ramdisk, java machine, broadband cellular modem, and wifi radio in my pocket. I abandoned windows entirely, to this day lol

Right you are! @mrbox23 ... I've got camera on RRemix on the metro 1921-3!
I'm gonna put the lineage/no camera issue on the back burner for when I try to use your older boot/vendor img trick (boot Lineage 15.1) on the unlocked 1921-5.
(I only have a 1Mb/s dsl connection here, takes about 4-5 hours for a 1 gig file to dl)
So, for the Metro 1921-3, I can't find libeffects.so or even the soundfx folder to copy into. (studder fix)
Your script 2 files for media/camera and charge led, other than making them executable (0755? 0700?) will they be called (without any other mod) being in /data/adb/service.d ?
I think it's important to use a/the real fingerprint from an e5 device along with other properties. To get the best out of the hardware and least error messages during boot. I go through logcat/dmesg and attempt to fix what's broken, like the camera on lineage(works without trouble on rr remix btw). I used hidepropsconf module at first and a sprint fingerprint, but later began using the one found in info.txt of firmware zip.
Click to expand...
Click to collapse
I pulled one out of my Att phone that is a james xt1921-2 but has a locked bootloader, all stock ... I used #getprop ro.build.fingerprint.. not sure if i should use this, or wait to see your build.prop...
ill post my work in progress build.prop(hosting it with new vendor and boot images on gdrive) which noticeably improves overall performance and lends to less log errors, or lags and crashes.
Click to expand...
Click to collapse
All the best to you and yours in 2020. Meeeerrrry eXksMix, hic up'

Yes to service.d with those three. I ditched the camera ones though, footej or another camera is nice. Im close to figuring out what the vndk library thing.
hosting current prop setups, between resetprop in service.d and modifying build prop. other goodies too. I turned oem partition into swap space, and added permissions to priv-app xml's enabling more RR features, like hold back to kill app.

mrbox23 said:
Yes to service.d with those three. I ditched the camera ones though, footej or another camera is nice. Im close to figuring out what the vndk library thing.
hosting current prop setups, between resetprop in service.d and modifying build prop. other goodies too. I turned oem partition into swap space, and added permissions to priv-app xml's enabling more RR features, like hold back to kill app.
Click to expand...
Click to collapse
mediafix line 2... set or resetprop?
1 resetprop 'media.camera.ts.monotonic' 0
2 setprop 'persist.camera.HAL3.enabled' 1
what are these last lines in mediafix for?
16 resetprop net.dns1 1.1.1.1
17 resetprop net.dns2 1.0.0.1
and i'm guessing the deb.sh is for your wifi repeater? swap space in oem?
how is mpcs.prop called? where is its proper folder?
can you host a copy of libeffects.so ?

@mrbox23 Bluetooth working! check.

aka.bugle said:
@mrbox23 Bluetooth working! check.
Click to expand...
Click to collapse
something I just noticed here recently is that's all the audio output now. I can't test cellular calls, Hangouts only works when i restore that vendor path Back to where it was. My camera broke again to. I want to reach out to phh here or github.

Well that's a big bug, sorry. I've reverted the metro 1921-3 to stock for now, but on the positive side, I tried using your older boot/vendor imgs trick on the 1921-5 (Sprint)... and success! it boots Lineage 15.1 and bluetooth works, I haven't tried using the GSM Att Sim yet and still no camera, (I haven't tried your other camera recommendations yet.) One step closer for the 1921-5.

[Land][Ubuntu Touch][Experimental]

[Land][Ubuntu Touch][Experimental]
Changes :
Initial build for land
Fix call
Fix dualsim
Fix wlan and BT
Kernel:Added anbox support, alarm,apparmor for it
By tea
Special thanks:
rupashkek
UbportComunity
Support Groups @utland on telegram
Notes: Mount data in recovery.And make sure ur data partition not encrypted
Download links:
https://drive.google.com/file/d/1-Afwg-Qxfq7362VPN4z2Uy_K5vptepiU/view?usp=drivesdk
Source Device tree and kernel:
https://github.com/Ubports-Land

Yoooho
Thank you so much ?

Thank you so much. Will please provide small detail how to flash it on phone.
I dont understand, " Mount data in recovery"

masoomyf said:
Thank you so much. Will please provide small detail how to flash it on phone.
I dont understand, " Mount data in recovery"
Click to expand...
Click to collapse
Mount data before flash it

Very interesting... based on UBport ?

It doesn't boot.I follow every step as said.

Noru29 said:
Very interesting... based on UBport ?
Click to expand...
Click to collapse
If the system does not boot, return to TWRP and delete dalvik and cache and restart again.

Subho166 said:
It doesn't boot.I follow every step as said.
Click to expand...
Click to collapse
It's wrong sentence.. It will boot. But you are not able to boot

Then how to boot it?

tried. a new experience. Too bad there is no more variety of mobile environments, tired of aosp.

Subho166 said:
Then how to boot it?
Click to expand...
Click to collapse
Like installing every rom.. How could I know what is your issue.. You just said it doesn't boot

I followed the installation instructions. Wiped all partitions including data. Format data to remove encryption.
Checked in TWRP mount, data partition was already mounted.
So, I proceeded to flash the provided zip. It installed successfully.
Clear and dalvik/cache and reboot system.
It is now stuck on the MI logo since the last 5 minutes, not sure if it is booting or not. Any help?

Does anyone know how to add more WiFi and Bluetooth connections, I can only use the connection in the initial configuration

atomickaushal said:
I followed the installation instructions. Wiped all partitions including data. Format data to remove encryption.
Checked in TWRP mount, data partition was already mounted.
So, I proceeded to flash the provided zip. It installed successfully.
Clear and dalvik/cache and reboot system.
It is now stuck on the MI logo since the last 5 minutes, not sure if it is booting or not. Any help?
Click to expand...
Click to collapse
Try restart for 2 or more time

Working fine except VoLTE
Sorry, I didn't reply earlier.
It worked within an hour of my last post when I restarted it twice. Same thing happened on the following restart too, wouldn't boot up, would only start after every 2 unsuccessful attempts.
Anyways, the ROM is great and works perfectly fine. Data with Jio was working.
SMS and calling wouldn't work on Jio VoLTE.
WiFi, all apps, Headphone Jack, torch, Bluetooth, Camera, all worked fine.
Couldn't find a way to install android apps. Read many articles and official of anbox but just couldn't make it work. For one, since I don't have a data cable, I couldn't test adb with Ubuntu touch, since adb over network was missing.
Another thing that didn't work was adding a Gsuite/google account. The google login screen opens, but the keyboard wouldn't come out even when focusing on the text field in the web view.
I ended up typing out my credentials in the notes app and then copy pasting them in the screen.
Google refused to go ahead claiming that this was not a recognized browser!
If the VoLTE is fixed, I would use this as my daily driver! (Since I use my phone purely for work - calling, text, notes)
So, now I am back to lineageos for microg.
Thanks for wonderful work OP and devs and looking forward to an update soon. Request you to pleade get VoLTE working so that I can start contributing too.

Some screenshots
Screenshots for other users

I saw you use LOS4microg, did you try microg on this Rom too ?

Noru29 said:
I saw you use LOS4microg, did you try microg on this Rom too ?
Click to expand...
Click to collapse
MicroG cannot work on a non-android ROM. Ubuntu touch is based on the ubuntu gnu/linux software distribution and it comes with it's own SDK and notification engine.
May I ask for what purpose do you need microg?

I used microg cause I don't want google on my phone but I need my GPS and apps working.

Update pushed
Changes :
-bring Ubuntu library
-fix anbox issue on kernel
-fix anbox installer issue
-and something forgot
Download link:
https://drive.google.com/uc?id=1moH0JEAQnQd7YypTqg9sz_hfJaVDED-b&export=download