Related
I DO NOT OWN THE ROM.
The developer of this rom is kumajaya on MIUI forum and thanks to him for his work.
MISSION:
Embarrass Xiaomi because refuse to release Redmi 2 kernel source
BUG:
Before you install this ROM, check your device magnetic sensor. Currently YAS537 not supported!
Still under development, built from sources, no hidden sources, not a binary dirty hack ROM
The following will not be supported in this thread:
- Custom Kernels
- Mods, including CPU management mod or any strawberry mod
- Modified system files
- Xposed
If you reuse even a part of my work here, a proper credit is a must, keep it open source also a must
Download:
Cyanogen and TWRP recovery: https://goo.gl/cDJQXI
CyanogenMod 12.1 ROM: https://goo.gl/zhGZjQ and https://goo.gl/5sqZGp
For better Google experience, install TK GApps Nano: http://forum.xda-developers.com/android/software/tk-gapps-t3116347
Don't create any mirror without a permission!
Cyanogen recovery above just like a standard AOSP recovery without a lot of features compared to TWRP, but you can temporary boot it using "fastboot boot cyanogen-recovery-wt88047.img" command to check if CyanogenMod 12.1 ROM possibly working on your device variant.
Don't even try this ROM on Redmi 2A variant!
Sources:
CyanogenMod source tree: [url]https://github.com/CyanogenMod[/URL]
Kernel source: https://github.com/kumajaya/android_kernel_cyanogen_msm8916
Device specific source: https://github.com/kumajaya/android_device_wingtech_wt88047
Vendor binaries: https://github.com/kumajaya/proprietary_vendor_wingtech
Changelog:
Device specific source: https://github.com/kumajaya/android_device_wingtech_wt88047/commits/cm-12.1
Kernel source: https://github.com/kumajaya/android_kernel_cyanogen_msm8916/commits/cm-12.1-amss-1.0.2-wt88047
Vendor binaries: https://github.com/kumajaya/proprietary_vendor_wingtech/commits/cm-12.1
Credits:
Google, AOSP, Cyanogen, CyanogenMod community, Qualcomm's CodeAurora @balika011, @zwliew, @Flour_Mo
Introducing me: XDA Recognized Developer, CyanogenMod contributor
My wife, she always believed I could restore back her device in minutes
Some tools: Kate (text editor), Kompare (diff viewer and generator), qgit (git GUI)
Smarfren Indonesia for Andromax Q source code
Micromax India for Yuphoria and Yureka source code
Current status:
Boot to Android, this is my first ROM that really boot on the first try
Touchscreen works, all hardware button mapped correctly
No screen flicker, fluid graphics
Voice call and SMS works, data over WiFi and GSM works (radio config in build.prop fix previous GSM issue)
Vibration and screen rotation works
All sensors seem works including GPS and compass but light sensor still need a fine tuning
Both camera working, the author found a super clean solution
No boot animation (fixed, kernel issue) Disable splash screen break Android boot animation but if I enable it, Cyanogen recovery covered by Tux the penguin logo in the center. The workaround solution, move Tux to the top right of the screen
No sound (fixed, kernel and user space issue) This also fix slow boot because of logcat flooding. BUG: Speaker output ignore headset jack insertion, sound out from both speaker and headset
Bluetooth file transfer fail (~42MB zip, failed at 17%) WiFi file transfer way faster
FM radio works
WiFi hotspot works
YouTube and local video 720p works
LED driver working great, multi color and blink
Remember, no contribution from Xiaomi yet. That's the reason why I try to avoid "Xiaomi" string in my source as possible but Wingtech.
I use CyanogenMod resources as much as possible, including common MSM8916 device tree and kernel. Maintain device source tree and leave common part to CyanogenMod community. I'll strictly follow CyanogenMod coding style and source structure. This is about source code quality.
AGAIN, I DO NOT OWN THE ROM.
Will try it soon. And I hope Xiaomi will release the kernel like Redmi 1s.
kumajaya and zwliew are the most stable CM12.1 roms for our phone. I hope they reach 100% full working version in near future.
Thank you both!
Can you upload the changelog for the latest [30/09/15] build. Also is the YAS537 supported
How about some screenshots?
What is the point of this thread when the original poster already has one on XDA?
Sent from my Nexus 7 using Tapatalk
crzlloid said:
Can you upload the changelog for the latest [30/09/15] build. Also is the YAS537 supported
Click to expand...
Click to collapse
There is a link in my post about the changelog and the YAS537 is still not yet supported.
zwliew said:
What is the point of this thread when the original poster already has one on XDA?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Sorry, but I have already talk to kumajaya about it. Then he ask me to help him on requesting an official sub-forum for our device. Anyways, if anyone here oppose me about posting this thread, then maybe I should delete this.
wow, using this in 2020, 5 years later.
Announcing Sailfish for the Sony Xperia Z3 Compact!
This is not Android!
This should be thought of as a development experiment. It may be useful if you are a developer and want to write/port apps the the Sailfish operating system. It is not an end-user product, however, if you wish to experiment and try something different then feel free!
Please do not contact Jolla Care or Jolla Developer Care, as this is not the Jolla phone.
Special thanks to:
rss351 and locusf for the collaborative effort in porting SailfishOS to the Z3 compact
Everyone from the SailfishOS team/community, sledges and mal- in particular.
All Cyanogenmod devs, since SailfishOS uses drivers from Cyanogenmod to talk with the phone's hardware
Known issues:
Bluetooth isn't turned on, cause i've put no effort in for that so far
Camera doesn't work, cause it's not hooked up to interface.
No recovery inside hybris bootimage (you need to flash manually to return to cm/use recovery)
Sensors dont work (auto-adjust brightness, etcetera)
The Jolla account/store functionality is not enabled. This is being worked on by Jolla. In the meantime: use openrepo's warehouse (see bottom of this post)
What works:
Booting, basic usage of the OS itself (browsing, etc)
Texting, calling, data over mobile network (2g and 3g tested, 4g should work but is untested)
Wifi (both 2,4 and 5 GHz)
Power management seems to work fine (not tested much though)
Looking around and getting a feel for SailfishOS
Using your phone to develop and debug SailfishOS apps.
Installation guide/checklist:
Insert default warranty void message here. Your warranty is now void
Make a backup (just to be sure)
Depending on what you need from your phone, this may not be a rom suitable for daily driving with. But installation is non-destructive to your existing rom, so if you're curious, give SailfishOS a try
I have not tested this on locked bootloaders, but since I needed to modify the kernel, I guess that you need an unlocked bootloader.
Note this is not an official Sailfish OS build, and the Xperia Z3c is not a Jolla phone, so please don't report bugs to Jolla. If you want to report a bug, this thread is perfectly fine for that.
BEWARE: this image is NOT optimized for security. The phone boots in development mode by default. There is a root shell on telnet port 2323. This is not secure and will give anyone who wants it remote access to your phone. When the port matures this will be fixed.
The Sailfish OS image does not provide recovery, and since the Xperia Z3c does not have a recovery partition, you need a bootimage with recovery on it to flash cm/stock/sailfishos upgrade. I highly recommend using Nut's Xperia files for this. Use the boot.img from your Cyanogenmod installation.
The Sailfish OS image is based on a recent version of Cyanogenmod 12.1, so update your Cyanogenmod installation while you are at it. Use cm-12.1-20160523-NIGHTLY-z3c.zip if you encounter issues with other versions. Using another rom is not guaranteed to work, even if this rom is based on Cyanogenmod.
You can find the required zip in this Mega folder: https://mega.nz/#F!ucoRnDjD!WAHNWgxLQX5SK1Vdu8MRWw
Use your favorite recovery (but not CM's recovery since that checks for signatures, which this image does not have) to flash the zip.
If you want to return to Cyanogenmod, extract boot.img from your cm-12 zip and flash that with fastboot. Alternatively you can restore a previous backup. There is no need to re-flash Cyanogenmod because it was not removed by installing SailfishOS. You can remove the /data/.stowaways/sailfishos/ folder afterwards to reclaim disk space.
FAQ
You can find a FAQ which mentions most common user questions for SailfishOS here: http://forum.xda-developers.com/jolla-sailfish/general/qa-sailfish-n4-thread-devices-t2727330 . It's mainly aimed to the Nexus 4 and 5, but it's fairly applicable for all other ports as well.
Contributing
If you think this is awesome, and want to help fix the issues currently open: come by in #sailfishos-porters on irc.freenode.net!
Sources
You can find all used source code (may not be up-to-date to the latest image, but all key components are there) here: https://github.com/xperiasailors/
Installing OpenRepos warehouse
OpenRepos warehouse is like what F-Droid is versus Google's Play store. An unofficial, community-driven repository of open source apps.
Go to settings->developer options and set a password. Then open a terminal or connect over ssh to your phone (ssh [email protected]_of_phone).
Download the latest version of the warehouse app from here: https://openrepos.net/content/basil/warehouse-sailfishos
When you are asked to terminate packagekit anywhere in the steps below, answer yes.
Code:
$ devel-su
# zypper rr adaptation0
# zypper in <location_of_rpm_you_downloaded>
After this Warehouse app will be in your app launcher.
Impressive work! :good:
Sent from my Sony Xperia Z3 Compact using XDA Labs
Just having a go now.
Edit: just stayed on sony screen. Would it be because I came from SLiMM 1.8 ROM and not from a CM based ROM?
mrrflagg said:
Just having a go now.
Edit: just stayed on sony screen. Would it be because I came from SLiMM 1.8 ROM and not from a CM based ROM?
Click to expand...
Click to collapse
Probably, yes.
SailfishOS uses libhybris for hardware communication, which in turn uses the existing Cyanogenmod installation for drivers and proprietary blobs. But hybris is compiled against a certain Cyanogenmod version, so using other roms as a base might fail.
I've updated the TS and put the exact CM version I used in there, that should work fine.
There are any news? The project is in development?
Alexander3273 said:
There are any news? The project is in development?
Click to expand...
Click to collapse
No news, I don't spend much time on this port, every now and then I fiddle around with it an evening.
I'm currently trying to get AOSP based Sailfish port because Cyanogenmod for Z3c seems unmaintained, but progress is very slow.
Thank you for the info. Do you know when a version (sailfish port) comes out?
Hello! Thanks for your work. May i know the progress ?
it would be great to see a real "european" OS coming out of the dust...
i hate the thought that any company from the other side of the atlantic are wheels in the monster of patriot act...
@maikoool Any news about new build or something?
Yes, look here:
https://nokius.net/SFOS/scorpion/PreAlpha/
But still no Cam, no BT, No Sensors and No video playback
AFAIK is the 'scorpion' the Z3 Tablet compact, so not the Z3 compact. The base images will probably be the same.
I've recently rolled a build using AOSP 5.1 from the Sony Xperia developer pages, but my Z3c has developed an issue where the top and bottom of the screen don't function, so I cannot test properly.
Aries is device name, right? What's scorpion ?
kskarthik said:
Aries is device name, right? What's scorpion ?
Click to expand...
Click to collapse
Aries = Z3 compact, Scorpion = Z3 Tablet compact
I'm waiting eagerly to see SFOS on aries Do you know anything about our device support on jolla's list ?
I have the idea for an unified build from quite some time, but only now I'm trying to bring it to life.
Looking at LineageOS github and gerrit you can see that other devices (klte, m8) have the same stupid amount of variants, but they have merged them into one device repo.. So why can't this happen for the Note4?
Following their steps I've created an unified android_device_samsung_trlte (that includes SM-N910F/trltexx, SM-N910G/trltedt, SM-N910T/trltetmo, SM-N910W8/trltecan, SM-N910P/trltespr, SM-N910R4/trlteusc and SM-N910V/trltevzw), this proprietary_vendor_samsung and added this commit to the android_device_samsung_trlte-common that I'm currently using.
For now I'm able to use those repos to build a LineageOS-14.1 build that boots up, but w/o sim and camera being recognized.. For what I've tested (on trltexx) wifi and (strangely) bluetooth are working. Something is probably wrong with specific device blobs not being recognized/used properly.
It needs some work but I think this is a good base to start with.
trltexx/trltedt blobs are from here;
trltetmo/trltecan blobs are from here;
trltespr/trlteusc blobs are from here;
trltevzw is using trltespr blobs for now (there are no guaranteed working blobs repos for it at the moment, the only (WIP) way is to establish which are needed and extract them from hsbadr's builds).
The kernel is the same that I'm using for the not unified builds (android_kernel_samsung_trlte), at the moment testing if the klte's way of using the international variant defconfig works for us too.. other options are to add something like this commit to remove the need of a variant defconfig or merge the different defconfigs into one and use that instead.
Source:
unified_android_device_samsung_trlte
unified_android_device_samsung_trlte-common
unified_proprietary_vendor_samsung
android_kernel_samsung_trlte
I was going to share this anyway, but I'm sharing it now (even if there are still major problems) because I have a very limited free time where I can work on it, so, maybe, someone of you will join/fork/clone this project and help me out, finalizing it earlier and better (the support of experienced developers is needed and much appreciated).
I'm now going to mention the SeniorMembers/RecognizedContributors/RecognizedDevelopers that, maybe, have interest in this project.
@fattire @hsbadr @SaintZ93 @SferaDev @TheBr0ken @ZION959
If you get it to work, @_mone, I'll switch my daily builds to this unified one.
On a related matter, there seems to be a typo in the name of one of your repos: unified_andorid_device_samsung_trlte.
Let me also add @lilferraro to the list of devs, as I use his device tree to build for trltespr.
I built this and it boots, with the same issues you have (no SIM detected, camera is busted). Took a bunch of of logs. Getprop shows ro.build.fingerprint is trltetmo (which is right), ro.bootimage.build.fingerprint is trlte. Wifi and bluetooth are working. Mediaserver/libcameraservice service crashes repeatedly. I agree with you that having a unified tree for the entire Note 4 line is the way to go. I tried manually copying the blobs from /system/blobs/tmo/ to /system/lib and /system/vendor/lib but it didn't help.
what proprietary blobs did you use for sprint?
All device trees for the note 4 pie builds are up at
GitHub.com/tripLr-dev
User forum at Telegram
https://t.me/triplr_dev_users
Thanks to @_mone
And @ripee
I will do a test build of my Ubuntu Touch port using this unified repo and report back if anyone is interested. My port still needs a couple things to work but the stuff that works now should be enough to give me a good idea if it will work or not.
tigerpro357 said:
I will do a test build of my Ubuntu Touch port using this unified repo and report back if anyone is interested. My port still needs a couple things to work but the stuff that works now should be enough to give me a good idea if it will work or not.
Click to expand...
Click to collapse
Let us know what you need
Source code
GitHub.com/triplr-dev
Contact me on telegram t.me/telegram to get you in touch with testers and developers. .
I am EXTREMELY interested in a touch port.
Thanks
Also GitHub.com/underscoremone for all the older stuff
I actually have my work on github already, I am also on telegram in the ubports groups, and if you would like to help my repo is probably the best place to start (unless you prefer duplicating work) I only have sensors and the stylus left for hardware (both of which I have been trying to get working) the stylus is an issue on the ubports side but I dont understand the code enough for mir. I haven't had a chance to test the unified repo yet, but I will once I have a few minutes to actually do it.
I wonder how it work to create xda threads for Ubuntu touch, since they seem to have their own forums.
I think adding Ubuntu touch to xda would be an additional resource for users and developers.
tripLr said:
I wonder how it work to create xda threads for Ubuntu touch, since they seem to have their own forums.
I think adding Ubuntu touch to xda would be an additional resource for users and developers.
Click to expand...
Click to collapse
I agree, as all I really see on xda as far as Ubuntu Touch goes is prebuilt downloads which is good for letting people try it, but when I started I initially looked into xda but found no help. I do hope to see that change in the future though
Nice to see someone actually wanting to still develop for this device.. I love this Note4 still.
doubledragon5 said:
Nice to see someone actually wanting to still develop for this device.. I love this Note4 still.
Click to expand...
Click to collapse
Same here
We have several developers for note 4 snapdragon and exynos
T.me/triplr_dev_users
See you there
Roms
Tiny.cc/triplr
Tiny.cc/ripee
And many links in XDA for ROM threads
Post comments in XDA, and bug reports and logs in telegram
Android 10 in progress
Thanks @_mone
The lineage-17.1 thread is up!
[ROM][UNOFFICIAL][10] LineageOS 17.1 [tblte][trlte][trlteduos]
If you don't mind not having a working fingerprint sensor, or audio through the headphone jack, then Q is stable enough for daily use. As always when coming from an older rom version, it is highly recommended not to waste your time dirty flashing and just clean flash.
Q is still a work in progress, so I will still be releasing Pie builds, though maybe not as often. As in years past, once the Q bugs have been fixed up to the current Pie level, I will post about when my last Pie build will be. I will upload it to the Downloads tab located at the top of each page of this thread, and link it in the OP.
All the blah blah about "as is", you being responsible for what you choose to do and do to your device, no guarantees implied nor stated... And all the usual to install. I wont be paying much attention to bugs, however, PLEASE post them as you find them to let others know what they can expect.
This build is a ONE-OFF and you should look at the original thread by @Krizthian for possible future builds. https://forum.xda-developers.com/google-nexus-5/development/rom-crdroid-v4-0-google-nexus-5-t3767591
Special thanks to @haze_nme who provided the device and kernel for without which this build would not be possible. Please visit his post and give the thanks button a BIG slap! https://forum.xda-developers.com/showpost.php?p=76807742&postcount=315
Of course, thanks to the crDroid team for providing the ROM source itself; and making it so easy to build using LineageOS device trees.:good:
Changes from the default source:
Code:
[FONT="Verdana"] Added the MiXplorer [url]https://forum.xda-developers.com/showthread.php?t=1523691[/url]
I got the OK first too include in my unofficial ROMs that I build, visit the forum, they are very helpful for this VERY powerful file explorer. [url]https://forum.xda-developers.com/showthread.php?t=1523691[/url]
You can thank @HootanParsa for building it, and letting me include it:good: Be sure to share some thanks.
Switched over to the ResurrectionRemox launcher. I had issues with the default launcher in crDroid. Also on another device, and I think I have read some other users had the same on even more devices.
Vinyl Music Player and removed crDroid music.
It has more features but is based off the same original app in crDroid. Including a dark theme!
Just to be polite I checked with the dev to get his ok, even though its open source. It can also be fund on F-Droid
OmniClock replaces the standard deskclock. Sourced from OmniROM, so a big thanks to them. It has a nicer dark skinn also.
[/FONT]
I have only done a rudimentary test on it. I flashed PICO Gapps, and there aint much room left in the system partition.
Source: https://github.com/crdroidandroid
Device: https://github.com/hazenme/android_device_lge_hammerhead
Kernel: https://github.com/hazenme/android_kernel_lge_hammerhead
Vendor: https://github.com/TheMuppets/proprietary_vendor_lge
You can download this build, and flash at your own risk, from:
crDroidAndroid-8.1-20180614-hammerhead-v4.4-DiamondJohnDroid.zip
MD5: 25e05c3f02d34968f308ac6b4ad32b8b
Thanks a bunch, I am eager to test this out and will update once I get a chance.
Good news, love crdroid rom, downloading. , thanks
Thank you so much for taking this project, I'm waiting for updates
Greetings
Krizthian said:
Thank you so much for taking this project, I'm waiting for updates
Click to expand...
Click to collapse
I wouldnt be too grateful, it was a one-off build of a secondary/spare device I have. While I await updates to my daily devices' kernel and device tree
DiamondJohn said:
This build is a ONE-OFF and you should look at the original thread by @Krizthian for possible future builds. https://forum.xda-developers.com/google-nexus-5/development/rom-crdroid-v4-0-google-nexus-5-t3767591
...snip....
Special thanks to @haze_nme who provided the device and kernel for without which this build would not be possible. Please visit his post and give the thanks button a BIG slap! https://forum.xda-developers.com/showpost.php?p=76807742&postcount=315
...snip....
Source: https://github.com/crdroidandroid
Device: https://github.com/hazenme/android_device_lge_hammerhead
Kernel: https://github.com/hazenme/android_kernel_lge_hammerhead
Vendor: https://github.com/TheMuppets/proprietary_vendor_lge
Click to expand...
Click to collapse
Maybe I too should be looking at the commits made into @Hazenmetrees to possibly see what needs to be done against my actual device.
DiamondJohn said:
I wouldnt be too grateful, it was a one-off build of a secondary/spare device I have. While I await updates to my daily devices' kernel and device tree
Maybe I too should be looking at the commits made into @Hazenmetrees to possibly see what needs to be done against my actual device.
Click to expand...
Click to collapse
Oreo for RAZR M perhaps?
That'd be quite the display if you could get that to work, assuming that is still your daily device. I have an N5 spare as well, but the WiFi chip broke : (
4.4 is working like a champ here. Many thanks. Tried to install ElementalX 9.02 but it wouldn't take. Will investigate further soon.
Galaxyninja66 said:
Oreo for RAZR M perhaps?
That'd be quite the display if you could get that to work, assuming that is still your daily device. I have an N5 spare as well, but the WiFi chip broke : (
Click to expand...
Click to collapse
Cast your mind back. My Razr is dead! Upgrading the kernel (and the device tree) is a big task. We were very lucky for Nougat, as the XT897 was pretty damn close and it had an official LOS build. ie the device tree and kernel were basically ready to kang. As far as I know, there is no official Oreo for the xt897 and therefore, unless you spend the time and effort, there is no Oreo for the xt907/xt905/xt926 etc etc.
For now I use and build for an GT-i9506 as my daily, and I also have an N5 as a "spare", which is half dead (mic is flakey which makes a phonee useless). I build for the N5 as "practice" for the S4, and I shared the results here, as I saw the current builds were quite old; [sarcasm]and I'm such a nice guy[/sarcasm]
DiamondJohn said:
Cast your mind back. My Razr is dead! Upgrading the kernel (and the device tree) is a big task. We were very lucky for Nougat, as the XT897 was pretty damn close and it had an official LOS build. ie the device tree and kernel were basically ready to kang. As far as I know, there is no official Oreo for the xt897 and therefore, unless you spend the time and effort, there is no Oreo for the xt907/xt905/xt926 etc etc.
For now I use and build for an GT-i9506 as my daily, and I also have an N5 as a "spare", which is half dead (mic is flakey which makes a phonee useless). I build for the N5 as "practice" for the S4, and I shared the results here, as I saw the current builds were quite old; [sarcasm]and I'm such a nice guy[/sarcasm]
Click to expand...
Click to collapse
Hmmm... messed up Nexus 5 you say... maybe we can trade mother boards via mail?
eh who am I kidding my Nexus 5 is worthless to me, the modem still works making it's purpose as a backup phone fulfilled
Thank you so much!!!!!!
@DiamondJohn : thanks man
4.5 will be?
see post https://forum.xda-developers.com/showpost.php?p=77301143&postcount=50
OP request.
THREAD CLOSED
This is unofficial lineageos 16 for Motorola Clark. It is only compatible with nougat firmware - you must have the nougat bootloader and modem flashed on your device.
Tons of thanks to hashbang for all of his work
Kernel Source-
https://github.com/randomblame/android_kernel_motorola_msm8992
Device tree-
https://github.com/randomblame/android_device_motorola_clark
Current status of rom-
Daily Driver
Broken-
Camera post processing- rotation is not accounted for in hal with latest round of hacks credit to AgathosAnthropos for fixing image capture by disabling the calls to pp, hold device in landscape for photos
Tethering - it works but device will soft reboot when tethering stops
Dual sim variants are NOT supported! I do not have the hardware to test and fix at this time - bugreports appreciated
Working - everything else?
Try it yourself (Requires Nougat Firmware and as always wipe data+cache)
Latest Releases:
1/12/2020 https://www.androidfilehost.com/?fid=4349826312261700035
8/1/2019 https://www.androidfilehost.com/?fid=6006931924117928331
Don't forget to grab a compatible version of gapps for 9.0
https://opengapps.org
Once again this rom REQUIRES that the stock nougat firmware was properly flashed to work correctly... It will check before installation that you have the correct modem version installed.
*If your radio does not work you may have the wrong modem
*If you can not switch lockscreen to pin or pattern you may have the wrong modem.
*Modem flashes fail quietly sometimes please make sure you have properly flashed it before reporting issues.
Great! [emoji6]
Enviado desde mi Nexus 5X mediante Tapatalk
I'll be happy to test once there is a working rom
I've been updating op, it seems to just be getting shorter as I fix things. The rom now compiles with default manifest only needs device tree and kernel source now. something is failing quietly and preventing boot. I'm just working the problem slowly getting it sorted out.
Can't wait to see more from this
We wait impatiently.
Spent a couple more hours going through init narrowing it down failure happens just before zygote startsI currently have my pure propped up in charging position so I can work more on it it's had a hard life
Thank You so much
randomblame said:
I've been updating op, it seems to just be getting shorter as I fix things. The rom now compiles with default manifest only needs device tree and kernel source now. something is failing quietly and preventing boot. I'm just working the problem slowly getting it sorted out.
Click to expand...
Click to collapse
I have been searching and search for lineage OS roms for my XT1575 but the bootloader is Ax052 which is not supported by 14.1 Lineage. I Hope you find a fix for this.
Moto X Pure XT1575 said:
I have been searching and search for lineage OS roms for my XT1575 but the bootloader is Ax052 which is not supported by 14.1 Lineage. I Hope you find a fix for this.
Click to expand...
Click to collapse
Hi, I have the Lineague 14.2 installed. What I did to eliminate the bootloader check was to edit the uptader-script
Fixing error caused by missing taskstats kernel feature
Hi randomblame,
A quick review please, could you tell us the intended purpose of your project.
Meaning like I'm thinking it's for a "Moto X Pure 2015 (clark)" device isn't it?
Would that be for everyone on this XT1575 device which has upgraded to a stock Nougat kernel and modem?
Or could/would others benefit from it as well with your research here - other moto's?
Any and all answers - thoughts are welcome in understanding the project...
Thanks for the lady power on XDA,
RIF
This device can have a new future. Think about it !
I will look into bootloader incompatibility once I get it running seems like it shouldn't be a big deal. I'm also toying with the idea of a new kernel 3.18 seems like low hanging fruit considering Motorola was kind enough to give us good searchable git history on GitHub of both kernels and the 3.18 source for the Moto z seems to have most of the msm8992 support still. My next step is going to be a new device tree starting as bare bones as possible and populating it properly to figure out this issue. I'll throw up a PayPal link again later a less broken device would be helpful USB port is bad and this is probably the fourth screen I've installed on it but touch only works when it feels like it lol
randomblame said:
I will look into bootloader incompatibility once I get it running seems like it shouldn't be a big deal. I'm also toying with the idea of a new kernel 3.18 seems like low hanging fruit considering Motorola was kind enough to give us good searchable git history on GitHub of both kernels and the 3.18 source for the Moto z seems to have most of the msm8992 support still. My next step is going to be a new device tree starting as bare bones as possible and populating it properly to figure out this issue. I'll throw up a PayPal link again later a less broken device would be helpful USB port is bad and this is probably the fourth screen I've installed on it but touch only works when it feels like it lol
Click to expand...
Click to collapse
I'm trying to follow along with your posts best as is possible for me - but, so sorry I and as well many others are lame to understand the under-the-hood workings of Android.
Are you saying in such a way that the Moto Pure XT1575, will maybe and with your research efforts move forward to a true PIE OS possibly?
Maybe I'm reading to much into your words.
But, as I follow your posts, you'll advance us Pure device owners beyond the Nougat kernel - or at least try too?
Or yet with your efforts will this yield something like HashBang did for the XT1575 device when a Nougat OS wasn't even a thought of possibility from Motorola for us.
Back then, HashBang had worked the Nougat OS on the Marshmallow kernel and modem - I'm very green to all of this - but that's what I understood.
Still that's good none the less if that will come here from you with PIE on Nougat internals...
Beings Motorola support is dead for our device for anything future of an OS update - not to mention security patches.
If you would spell it out better as any interested XT1575 owners now could grasp the concept here in your efforts - create a buzz for a greater community following. More MXP owners to jump on board as gained support from well wishers.
Is it to early yet for that? Is there a fear that someone could steal it out from under you? Unexpected negativity, or is it just the way you wish to present this to us for the present.
I'm still going to watch and support this project with high hopes no matter what may come in the end...
Could you benefit knowledge from a LineageOS 16 for Moto Z. download?
https://www.cyanogenmods.org/forums/topic/download-moto-z-lineage-os-16-android-9/
For people like me,
Device Tree = https://source.android.com/devices/architecture/dto
and on XDA
https://forum.xda-developers.com/android/software/guide-how-to-make-device-tree-phone-t3698419
As for any active developers still left for the XT1575 a big thank you to you all, seems to me like a daunting task to crawl inside of android moreless understand things once your there...
Kernels are only loosly linked to Android versions, Google maintains the Android-common kernel repos which are usually quite far behind mainline Linux, and caf who maintains Qualcomm specific kernels are further behind in general. Literallyany feature required by Android can be backported to an old kernel I'm sure 2.6.27 could run pie but it would need so many patches it would be an unrecognizable mess. It will become progressively more of a nuisance as time goes on to keep patching up 3.10 Pie "requires" 4.4 for new devices but only needs kernel features from 3.18 which I've backported to 3.10. with each new version of Android more assumptions are made about how modern the devices kernel is and what features it has so moving to a newer kernel would be nice and like I said 3.18 seems doable but it will still be quite a bit of work.
Thank you @randomblame I was able to grasp most of that...
Maybe it's too early but, how does Googles Android security patches figure into this - if they are possible to bring us forth from Oct 2017?
Remembering I'm a laymen to the nuts and bolts of android.
I understand your post #16 - Super !
Security patch version is irrelevant when you are building from the latest source
Obnoxiously after a few builds the dedicated 250gb SSD is full and I have to make clean which takes ages, I nooped every thing but the basics didn't include telephony or wifi, ril, audio, Bluetooth GPS nfc etc and left it to build overnight will test after work trying to narrow down the problem
Surface flinger is the culprit
I have the device laying around and getting no use. Will sure donate some $$$. Seeing a los16 with all working hardware would be great.
Only got a couple hours to work on it this weekend, there is an issue where /system/vendor is not symlinked to /vendor early enough and calls for things in /vendor fail thus the issue, since we don't have a physical /vendor partition it can not be mounted immediately via the kernel. Tis annoying. I can change the calls to /system/vendor or maybe make it symlinked earlier when I get a chance