Related
I thought I'd post here my (and the people who helped me) progress on porting MultiROM to the HTC Nexus 9.
Contributors (so far, tell me if I miss anyone)
@Bogdacutu for his port of MultiROM on the Shield Tablet (The arm stuff)
@USBhost for testing as well as helping with the patch (patch is still WIP, more on this later)
@Tasssadar for MultiROM all together
@Unjustified Dev for his influence
Progress
Working: Multirom TWRP has been successfully compiled for flounder and has working ADB and MTP.
Partially Working WIP: MultiROM boot selector source has been ported to work with arm64. The multirom boot selector compiles for flounder in zip format and launches at device boot. However, touch does not work and there is no ADB at the moment.
Not Working WIP: The kexec hardboot patch currently does not work so the Nexus 9 is currently unable to boot another ROM other than the primary one.
Source
All sources can be found here (I know some of them may not work and may be a little messy but this is still a work in progress)
Device Tree
Kernel
MultiROM
MultiROM TWRP
Building Notes
I compile this with the CyanogenMod Device Tree. Instructionsfor building multirom can be found on the multirom wiki found here
Note: adbd and kexec-tools need to be replaced with these versions that are arm64 compatible
adbd kexec-tools
If you would like to contact me on hangouts about this, please PM me your Gmail.
Reserved
One more
I might have found a repository that may help us out with the kexec hardboot patch on arm64.
There are many commits here that relate to kexec on arm64
Very glad to hear!! Sooper work :thumbup::thumbup: :beer:
This may also pose useful for the arm64 instructions
...
Looks like kexec-tools may need to have a lot of changes for arm64.
There are the changes made on a more recent version or android tools (not the one for android/multi-rom). I think this commit may be helpful but changes would have to be made.
Re-based many of the repositories on MR64 the other day. Now I need to test....
Also, the kexec tools function for flounder is completely re-written so maybe kexec will work?
I'll have to try to test when I have a lot of free time...
Is this going to work to get Linux kexecboot working? I really would like to have Linux running natively on this tablet....
Any updates on the project?
Any news on this, hoping for developments so that progress can be made for oneplus2 and multirom?
Thanks
Hello, and whether support for Nexus 9?
@Hashbang173
What's the status of this ?
omerjerk said:
@Hashbang173
What's the status of this ?
Click to expand...
Click to collapse
I have tabled development for this until further notice.
Hashbang173 said:
I have tabled development for this until further notice.
Click to expand...
Click to collapse
Is there any deving goin on on this? I think its way too hard. kexec isnt x64 compatible. (The binary itself isnt. How will youll port hardboot ) First we will have to add x64 support to that. I have seen your commits. That isnt x64 supported too.
Please update me on this, im building on op2 if this works. Thanks <3
regalstreak said:
Is there any deving goin on on this? I think its way too hard. kexec isnt x64 compatible. (The binary itself isnt. How will youll port hardboot ) First we will have to add x64 support to that. I have seen your commits. That isnt x64 supported too.
Please update me on this, im building on op2 if this works. Thanks <3
Click to expand...
Click to collapse
I'm no dev but could this be helpful for kex ec on ARM64? https://www.spinics.net/lists/arm-kernel/msg462969.html
Hashbang173 said:
I have tabled development for this until further notice.
Click to expand...
Click to collapse
I know you've put this project on hold for the time being, but I would like to jump in on this dev-tastic venture. I got a Nexus 9 (LTE) for Christmas*, and wanted to let you know that you don't have to bear the burden of building/testing/debugging/etc. all by yourself. I am fairly well versed in the mechanics of MultiROM, and have been (and still am) a user of MR on my Nexus 7 (2013) since v28 . . and honestly, without MR on my Nexus 7, I probably wouldn't have the pen. testing abilities that have enabled me to offer those additional services to my clients (i.e., security consultation, data breach prevention, etc.).
My point is that I owe a lot to Tasssadar and the "MultiROM for Android" concept in general, so I am happy to give back in any way that I can.
The Nexus 9 has been my dream Android device ever since the rumor mill was buzzing with notions of a Nexus tablet with an ARM v8 (ARM64) based Tegra variant!!
Let me know if/when you wanna get this thing off the ground again, and I'll make myself available as much as possible.
FULL DISCLOSURE: Although I am fairly versed regarding MultiROM and it's mechanics (kexec-hardboot, modifications to TWRP, etc.), I don't have much experience when it comes to ARM v8. However, I am pretty fluent regarding desktop x64 programming applications and coding, so it shouldn't be too hard for me to wrap my head around this whole ARM v8, 64-Bit SoC/MoP revolution. If you (or anyone who knows) could fill me in on the challenges we are facing regarding kexec and hardboot in a 64-bit scenario, that'd be swell. In the mean time, I will do my best to get up to speed regarding the repos & commits you have referenced/linked up to this point.
THANK YOU FOR ALL OF YOUR HARD WORK THUS FAR, AND LET'S GET 'ER DONE MY FRIENDS!!
:fingers-crossed:
*BEST . . CHRISTMAS . . PRESENT . . EVER!!!!!!
Thanks Mom!!
They have a Multirom version working for the Nexus 6P which is an arm64 device using the kexec method. Here is the link if it helps you devs.
http://forum.xda-developers.com/nexus-6p/development/mod-multirom-v33-beta-1-t3313291
rifraf1 said:
They have a Multirom version working for the Nexus 6P which is an arm64 device using the kexec method. Here is the link if it helps you devs.
http://forum.xda-developers.com/nexus-6p/development/mod-multirom-v33-beta-1-t3313291
Click to expand...
Click to collapse
yep, I ported it to clark already, maybe I'll try porting it to flounder in the future
Multirom for yureka aka tomato (64bit snapdragon 615) is also coming today with kexec-hardboot patch. Hope other devices also get this fast
Hello fellow M9 users,
As many of you may know, AOSP 7.1.1 based custom roms have started to pop up for our device. Many of these are based on the Lineage OS sources (formerly Cyanogenmod).
There appear to be some recent commits to the device specific git repositories for our device:
https://github.com/LineageOS/android_device_htc_hima-common
https://github.com/LineageOS/android_device_htc_himaul
One major issue that all the Nougat roms currently have is the lack of a working camera. I'm not a qualified dev, so I'm making this thread to both ask for progress and search for/organize volunteer efforts. I remember that we had a similar issue with CM13 (getting the camera to work proved to be difficult and took a while). I'm wondering what the difference is between this device and other devices (since it seems that pretty much every single other HTC device has had LOS14.1 with all working features for a while now). What is stopping us from doing the same? Do we need to create a petition/pester HTC to release source code?
If there are any devs left for this phone, please reply in this thread so fellow M9 users can be kept informed and potentially help you test (or help in any other way, depending on the posters' abilities).
The last commit was one month ago and nobody has replied here, seems like development has really halted... Any idea why this happened? What makes the m9 different from the 7, 8 or 10, all of which have active development?
Maybe because stock system is already superb with sense...
*deleted*
a solution
i installed lineage os....and the camera is working fine for me. The thing you need to do is to not update the camera app. As soon you update the app it starts crashing and wont open camera. It happened with me and then i uninstalled the update and guess what camera is working fine again. We will have to wait for this fix but for the time being we have to stick with the older version of camera app.
I have Lineage OS on my M9. If you install flash OpenGapps using the stock installation, you will get an updated google camera that will crash all the time. I flashed the nano installation from OpenGapps. The stock camera from Lineage OS works well. I think the stock version from OpenGapps automatically replaces stock Lineage apps if there is a google alternative. The nano version does not replace apps.
Hello xda community,
I would like to try my hands at building Lineage OS for the Galaxy Note 4 Duos. I was a little surprised that there seems to be not even an unofficial build for it (or cyanogenmod for that matter). Is there some technical reason why it hasn't been attempted yet that is specific to the Duos?
Otherwise, I'd be happy if someone could point me in the right direction. Maybe someone who already did it for a different model could post a basic guide since I have no experience yet in this area.
Speaking of it, my current level of experience is that I have rooted and flashed roms on android phones a few dozen times, and developed a handful of apps for android. So hopefully it's not too far outside of my skill-level.
Thank you in advance.
You can take a look at Note 4 General section, a new thread was made on how to build LinageOS for the Note 4 N910F/N910G. N9100 will not support 2nd sim if im not wrong, you need a dev who want to work on this project
Try this:
https://drive.google.com/open?id=0By...llGSnVyVDVfRlE
I downloaded this from the Chinese website. The latest build is 29 April. Donno why. Give it a try.
Thank you very much, I'll give it a try when I get to it.
Btw. the url is incomplete, I'm trying the original thread.
Did it work for you? (the April 29 build )
akshayarajdayal said:
Did it work for you? (the April 29 build )
Click to expand...
Click to collapse
Kind of. Fingerprint and HDR camera don't work, which was expected, but for some reason phone calls don't work for me, I can call and receive, but there is no sound on either end. Otherwise everything seemed fine and the phone performed relatively well.
twrp-3.2.0-0-trlteduos official build release candidate!
twrp-3.2.0-0-trlteduos.img
twrp-3.2.0-0-trlteduos.tar
I've finally managed to build it from a pure omni device tree borrowed heavily from _mone's trlte twrp device tree. Chinese variant users: please test it as thoroughly as you can, including backing up and restoring with and without encryption. If it works, _mone will push it for official support.
ripee said:
twrp-3.2.0-0-trlteduos official build release candidate!
twrp-3.2.0-0-trlteduos.img
twrp-3.2.0-0-trlteduos.tar
I've finally managed to build it from a pure omni device tree borrowed heavily from _mone's trlte twrp device tree. Chinese variant users: please test it as thoroughly as you can, including backing up and restoring with and without encryption. If it works, _mone will push it for official support.
Click to expand...
Click to collapse
The links are broken
Hi there,
does anyone know a working version of LineageOS (V14.X) for our Xperia X Compact?
The last version i´ve found is not updated since April:
https://forum.xda-developers.com/x-compact/help/rom-lineageos-14-1-sonylos-7-1-binaries-t3584504
Is there a newer Version?
Kind regards,
Chris
I cannot find any either, but Omni has a working rom with official weeklies, you can maybe try that.
Edit: It's more like a monthly, though. Last build is from Nov. 20
I'm not a developer, but I've made an attempt yesterday to build LineageOS. After several build errors (and dirty (possibly horribly wrong) hacks to circumvent them), the build completed but I was unable to successfully boot the resulting zipfile (it bootloops every couple of seconds). I then flashed the kernel (boot.img) from the older LineageOS-rom that is shared on androidfilehost, and I was able to boot the rom but the simcard isn't detected, so the rom is basically useless...
It is sad that there are no people out there that can maintain a weekly build for LineageOS. If an inexperienced builder like me can build and boot a rom it really shouldn't be that hard to improve the build.
Coirpre said:
I cannot find any either, but Omni has a working rom with official weeklies, you can maybe try that.
Edit: It's more like a monthly, though. Last build is from Nov. 20
Click to expand...
Click to collapse
Thanks! Could you say anything about the differences between Lineage and Omni? Omni's website is extremely sparse - no main point of differentiation, no feature list, no installation instructions - nothing. All it says is, it's AOSP "enriched", but not how. Their wiki link goes to a github page with a Code of conduct and a License Agreement - not very useful either.
Just noticed this - https://www.lineageosroms.org/forums/forum/sony/xperia-x-compact-kugo-f5321/
Plus AOSP Oreo - https://androidfilehost.com/?fid=817906626617948176
lineageosroms.org
lineageosroms.org
any more infos about that site?
looks quite impressive with the ammount of unofficial devices.
@Tom Mix: Looks to me like a lot of pointless clicking without any actual roms being offered. Seems like a scam (although I cant figure out their revenue model)
so after long searching it finally clear to me that
- treble partition and recovery are available
- Can flash GSI/Treble rom but with quirks, e.g. bluetooth, hotspot not working
- Missing shims? Updated vendor partition?
so we need a great dev to work on it??
if great dev starts the project and start a pool for collecting $$$ as support i'll gladly donate $10us I'm sure more people will join too....
especially now that MIUI has finally released the final version https://www.xda-developers.com/xiaomi-redmi-note-3-final-miui-10-stable-update/
optionalmgrr.la said:
if great dev starts the project and start a pool for collecting $$$ as support i'll gladly donate $10us I'm sure more people will join too....
especially now that MIUI has finally released the final version https://www.xda-developers.com/xiaomi-redmi-note-3-final-miui-10-stable-update/
Click to expand...
Click to collapse
Who gonna rewrite vendor code? Its not devs work. It comes from vendor and silicon manufacturer. They knows their hardware. So they work closely with google to write vendor blobs.
Why u want treble rom? Flashing gsi doesnt give u more performance and stabilty. They are more buggy than non treble rom. Non treble rom are device specific so have less bugs.
Kenzo will get android 10 and thats enough. After that 5g phones will hit the market and all will rush for it. So dont assume kenzo will survive till 2050 if we make it treble :laugh:
5G is going to be a flop like 3D TV.
If there is official LineageOS 16.0 then it's ok, but all other ROMs are too flicky they don't even support SELinux.
All those 1000s of different ROMs are basically the same base just add on top different customizations. That's why all 9.0 ROM are SELinux permissive.
In short, too many fancy half-working stuffs without any substance. We need a substantiated deve to help us out of this mess......
optionalmgrr.la said:
5G is going to be a flop like 3D TV.
If there is official LineageOS 16.0 then it's ok, but all other ROMs are too flicky they don't even support SELinux.
All those 1000s of different ROMs are basically the same base just add on top different customizations. That's why all 9.0 ROM are SELinux permissive.
In short, too many fancy half-working stuffs without any substance. We need a substantiated deve to help us out of this mess......
Click to expand...
Click to collapse
Do u even know how selinux works.
What do u mean they dont even support selinux.? Every rom has selinux support since kitkat.
Why dont u write ur perfect selinux policy and help to this devs so that it can be enforced on pie.
And whats there in lineage official rom which other roms dont have. Lineage official has its rules which cant be met for older phones which has old vendor blobs. Difficult to get official status.
And Who really give damn about lineage official.
Other roms are more customizable and have far more better and miles ahead in features then los rom.
And what u mean by mess? Xiaomi gave mm blobs coz official miui on android 6. Then from where we will get latest code if qualcomm is not updating code for sd650.
Only stuff is broken on pie is Vilte. If u have selinux priority then use Citrus.
ok thx
Forget about project trouble for our kenzo