I am attempting to port MIUI 7 to the Moto X Pure using the recently released PatchROM tool for marshmallow from MIUI's github.
I AM NOT RESPONSIBLE FOR ANYTHING BAD THAT HAPPENS DUE TO THIS ROM NOT WORKING PROPERLY
I wanted to make this thread to set up a place where I can try to work with you guys to figure out any issues that may come up, as this is not my first attempt to build this. I usually "port" Cyanogenmod or ParanoidAndroid to my devices before the official releases so I should be able to handle most basic issues myself, but I would definitely benefit from the collective XDA.
The base ROM I am starting with is CM13 from the 10/26 nightly. I will try to update as often as I can, but I am a full-time student so it will not be as often as you might hope. Hopefully it's relatively bug-less to begin with.
This phone is my daily driver, so until it is relatively functional or I can get a spare phone, progress will be impeded by this. Any logcats appreciated
RESERVED
Reserved also
Why MIUI 7 and not MIUI 8 just wondering
datchico305 said:
Why MIUI 7 and not MIUI 8 just wondering
Click to expand...
Click to collapse
The patchrom doesn't support MIUI 8 as of yet, unfortunately. When/if it releases, I will definitely attempt to move to that.
I'll test.
dkcats3 said:
The patchrom doesn't support MIUI 8 as of yet, unfortunately. When/if it releases, I will definitely attempt to move to that.
Click to expand...
Click to collapse
OK I see now well good luck I will definitely test
I too am ready to be a tester
so my build is crashing here:
Code:
Add field mSyncOnWifiSettingChanged:Landroid/content/BroadcastReceiver; into out/services/smali/com/android/server/content/SyncManager.smali
/home/david/patchrom2/tools/apktool --quiet b out/services -o out/services.jar
Exception in thread "main" brut.androlib.AndrolibException: java.util.concurrent.ExecutionException: java.lang.NullPointerException
at brut.androlib.src.SmaliBuilder.build(SmaliBuilder.java:129)
at brut.androlib.src.SmaliBuilder.build(SmaliBuilder.java:69)
at brut.androlib.Androlib.buildSourcesSmali(Androlib.java:376)
at brut.androlib.Androlib.buildSources(Androlib.java:335)
at brut.androlib.Androlib.build(Androlib.java:292)
at brut.androlib.Androlib.build(Androlib.java:268)
at brut.apktool.Main.cmdBuild(Main.java:224)
at brut.apktool.Main.main(Main.java:84)
Caused by: java.util.concurrent.ExecutionException: java.lang.NullPointerException
at java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.util.concurrent.FutureTask.get(FutureTask.java:192)
at brut.androlib.src.SmaliBuilder.build(SmaliBuilder.java:124)
... 7 more
Caused by: java.lang.NullPointerException
at org.jf.dexlib2.writer.pool.PoolClassDef.<init>(PoolClassDef.java:59)
at org.jf.dexlib2.writer.pool.ClassPool.intern(ClassPool.java:88)
at brut.androlib.src.SmaliBuilder$1.call(SmaliBuilder.java:116)
at brut.androlib.src.SmaliBuilder$1.call(SmaliBuilder.java:94)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
any ideas?
I already went through and fixed the smali rejects so Im not sure what else is missing.
If necessary, I'm also considering trying to build this based off of the stock moto rom, as it's fairly close to AOSP, however I have the feeling there would be more conflicts.
Just read the latest pages on CM-13. It's not a stable base in my opinion. Just wait for the Slim-weekly or build it yourself, as this is a really solid marsmallow Rom(together with Dirty Unicorns)
Can you provide all of the log?
ereneren564 said:
Can you provide all of the log?
Click to expand...
Click to collapse
well nevermind, i fixed it haha. it was a sloppy smali reject fix.
I will try to upload my workspace to github, and will update the original post with a link. be warned, there is a lot of messy folders, as PatchROM cant make up its mind as to whether the folders should be in all caps or not, and doesnt look in the right folders for some things so I had to copy them to the correct locations.
Here is the first build. I haven't tested yet, and I doubt it will boot. Unless you guys tell me its functioning im most likely going to manually edit the ramdisk and replace the generated boot.img.
https://www.androidfilehost.com/?fid=385035244224391883
I will make a backup and test if it boots
As will I
great ım soo happy cause ı love miui interface hihahahahhahahaha
I'll test been doing this for years lol
Sent from my XT1575 using XDA-Developers mobile app
wtf 1gb why ?
anyway ı dowloaded and test
Related
"The G2 Dream Team" (and they well deserve that name) has released not one, but TWO lollipop builds for the LG G2. Both ROMs are based on the same build tree, but one ROM is CM12 and the other is a LiquidSmooth 4.0 ROM. Despite being built from the same build tree, they carry different features. They are stable and usable for daily drivers, but they may carry some bugs, like a non-functional video playback, NFC issues for LS/VS980 but it should all be sorted out in the near future. Head over to the threads to read more!:
Liquidsmooth 4.0:
http://forum.xda-developers.com/lg-g2/development/rom-liquidsmooth-v4-0-lg-g2-t2948395
CM12:
http://forum.xda-developers.com/lg-g2/development/rom-cyanogenmod-12-0-lg-g2-t2944269
Older posts:
An increasing amount of devices have been receiving unofficial Android Lollipop 5.0 ports, like the HTC One M8 and the LG Optimus L9. Today another device can be added to the list of phones receiving a treatment with the taste of Android Lollipop, the LG G2. While there generally has been a wide contribution from the community; testing, sharing files and giving ideas, two XDA members stood out in particular in order to create the build, @ylukasy and @InfinitusDesigner. The port is still in a very early pre-alpha stage, and the bugs are barely known yet, but the ROM boots and has even been rooted! While it might be wisest to wait until an official thread has been made before grabbing your devices and start flashing, @ylukasy has already provided a download link for the ROM, and calls for people to help discover the bugs so that they can be eliminated. Please notice that the ROM might not be stable enough to be used as a daily driver, but owners of a LG G2 are officially an important step closer to having a stable Lollipop ROM!
If this post caught your interest and you're willing to take the risk, head over to the last pages in the following thread: http://forum.xda-developers.com/lg-g2/general/unofficial-cm12-nexus-5-posted-t2936398
As previously mentioned, a lot of things are not sorted out yet, and the build might not be for your device number, so make sure you read the entire thread before continuing, or simply wait untill an official thread is made.
Update:
An official thread has been posted and it can be found by following this link: http://forum.xda-developers.com/lg-g2/development/rom-android-lollipop-fast-clean-t2941922
The build is a port of the Nexus 5 ROM, and users of the ROM have been saying that the rom is very fast and fluid, calls work, camera works (although the quality is inferior), but other users have been reporting random reboots and incompatibilities with certain apps such as YouTube or WhatsApp.
by vPro97
This post will be updated regularly when new information regarding Lollipop ports surface.
Fantastic News! Will get round to trying it shortly, thanks for the link!
While I have my doubts about it being functional (or even booting) on my LS980, I'll give it a shot and see what happens.
Nice to see things moving at breakneck speeds these days.
On a side note, I just read the AnandTech review of the Nexus 6 and am happy to report that my well over a year old G2 beats it in several benchmarks so I'm pretty satisfied at the moment, especially considering I got it for free. I mean really...
In before "no build for xxxx?!?!?!?"
Anyone know how to port a d802 rom to d800?
Ready to try it out and see what happened..??
his build is from the same source the other was he doesn't deserve credit for it. it's using cm12 kernel and dev claims it's using nexus 5 port yet requires gapps and no signs of any nexus 5 code at all.
Wouldn't it be alot easier to just post the download link here?
₪LG G2₪
Zyner said:
Wouldn't it be alot easier to just post the download link here?
₪LG G2₪
Click to expand...
Click to collapse
It's not my work, and there are some steps which must be followed in order to make it work. I am just objectively informing any news regarding Android Lollipop for the LG G2.
OP has been updated.
The download link was removed before i could get the v3 version so im stuck with v2 and ive been using it as my daily (yeah it reboots every 5 minuets and i can leave wifi on or it will bootloop) But honestly thats the fun in testing this stuff out
MrNegative370 said:
The download link was removed before i could get the v3 version so im stuck with v2 and ive been using it as my daily (yeah it reboots every 5 minuets and i can leave wifi on or it will bootloop) But honestly thats the fun in testing this stuff out
Click to expand...
Click to collapse
Me too.
Is there anyone that can share privately the V3 version with me ? :fingers-crossed:
here is something better:
http://forum.xda-developers.com/lg-g2/development/rom-cyanogenmod-12-0-lg-g2-t2944269
Jam4l said:
here is something better:
http://forum.xda-developers.com/lg-g2/development/rom-cyanogenmod-12-0-lg-g2-t2944269
Click to expand...
Click to collapse
TY !
Can anyone port the Nexus 5 ROM?
Updating this thread later today if nothing gets in the way.
Hi everybody!!
I need a tester please:
I built pure AOSP for the D802 from sources of Android right now, has anybody time to test it?
It is an experimental build and I didn't test it right now, so I don't know if it is working, please make a backup from your current rom.
The build comes with an built in CWM recovery and should be with root access. It can be flashed with the same instructions like the CM 12 build.
Edit: Bootloop right now ... Anybody, can you take a logcat?
http://builds.hubdroid.com/otherroms/aosp_d802-ota-102.zip
Thank you in advance!! Please anybody who tries it: can you send me a pm?
Flo0008 said:
Hi everybody!!
I need a tester please:
I built pure AOSP for the D802 from sources of Android right now, has anybody time to test it?
It is an experimental build and I didn't test it right now, so I don't know if it is working, please make a backup from your current rom.
The build comes with an built in CWM recovery and should be with root access. It can be flashed with the same instructions like the CM 12 build.
http://builds.hubdroid.com/otherroms/aosp_d802-ota-102.zip
Thank you in advance!! Please anybody who tries it: can you send me a pm?
Click to expand...
Click to collapse
I'd love to test this for you, but I'm on Sprint LS980 Would you mind making a build for us?
iamterence said:
I'd love to test this for you, but I'm on Sprint LS980 Would you mind making a build for us?
Click to expand...
Click to collapse
Yes sure, but right now, I have to solve the bug, that the d802 wouldnt boot, so this may take some more time until I build it for other devices too.
Regards
NEED HELP
Hello guys, I'm working on a generic tree for our beloved device Honor 7, but not getting enough success, so each and every of you are invited to help me create a new device tree for AOSP 5.1 ROM or CM 12.1, so that we can taste the Stock Android too.
The benefits of these ROMs are that the device will get more fast and stable as there will be minimum apps and bloatwares installed.
So, it is a humble request, that whosoever have any knowledge about creating a tree from scratch please help me.
I have created a skeleton of the tree but it is not a success too as there are many things we still have to consider.
@sminki and @kenshiwara, we will setup an organization on GitHub so everyone can contribute there only.
Hi,
It will be wonderfull to have CM on our honor7.
Sorry mate. You haven't seen my troubles over the last few weeks then
After my H7 'died', I got a warranty replacement phone, and unlocking was proving impossible, each day was bringing more frustration and anger so i've sold it!
That's it, i'm out of the "honor" business for good (hence the "unsupported" bit on the recovery and kernel threads), but as a parting "gift", here's a few things that may help "the cause".
Sorry, the length of this post got out of control! :silly:
device tree starting point:
https://github.com/TeamWin/android_device_huawei_p8 - it's similar enough, that with a little editing and boom, we had our recovery*
https://github.com/debbiche/android_device_huawei_p8 - another fuller "tree" (wip), again the p8 is similar enough to use as a base
https://github.com/Gibbon99/android_device_huawei_hwgemini - mediapad x2 - another kirin
if you're insane, you could get the dtb files (iirc - i got these from compiling the source) and decompile, but this contains EVERYTHING, theses files are huge, many hundred kb and would take days to get the info out you need (if there is any!)
cm
have a look at codeworkx H6 git, it's the closest device you'll find that has CM actually running on it, albeit CM11 (and abandoned!)
https://github.com/codeworkx/proprietary_vendor_huawei
https://github.com/codeworkx/android_device_huawei_h60-common
other things:
osm0sis' kitchen out of the many boot image unpack/repack tools, this worked the best with huawei boot/recovery images
* with this in mind, anyone running Linux can pull apart my recovery, fix the issues in default.prop, add extra partitions to fstab and repack it. then post it for everyone else to use.
with the sh!tty way fastboot is on these phones, and the way modem binaries get patched, you're going to have to look for a way to write these in recovery (scripted with dd i imagine) so that everyone can use without having the ballache that is B100,B121,B140 etc etc to get to a version that will work with your ROM. this for me is where it's all going to hurt! (and end with bricks!)
final thing - the kernel source is terrible, it is so far removed from AOSP that simple things that you could normally just drop in, like cpu governors won't work. unless you really know C++ and how to debug it's gonna be near stock (like mine funnily enough!)
Good luck chaps :good: it's gonna be a hell of a ride!
sminki said:
Sorry mate. You haven't seen my troubles over the last few weeks then
After my H7 'died', I got a warranty replacement phone, and unlocking was proving impossible, each day was bringing more frustration and anger so i've sold it!
That's it, i'm out of the "honor" business for good (hence the "unsupported" bit on the recovery and kernel threads), but as a parting "gift", here's a few things that may help "the cause".
Sorry, the length of this post got out of control! :silly:
device tree starting point:
https://github.com/TeamWin/android_device_huawei_p8 - it's similar enough, that with a little editing and boom, we had our recovery*
https://github.com/debbiche/android_device_huawei_p8 - another fuller "tree" (wip), again the p8 is similar enough to use as a base
https://github.com/Gibbon99/android_device_huawei_hwgemini - mediapad x2 - another kirin
if you're insane, you could get the dtb files (iirc - i got these from compiling the source) and decompile, but this contains EVERYTHING, theses files are huge, many hundred kb and would take days to get the info out you need (if there is any!)
cm
have a look at codeworkx H6 git, it's the closest device you'll find that has CM actually running on it, albeit CM11 (and abandoned!)
https://github.com/codeworkx/proprietary_vendor_huawei
https://github.com/codeworkx/android_device_huawei_h60-common
other things:
osm0sis' kitchen out of the many boot image unpack/repack tools, this worked the best with huawei boot/recovery images
* with this in mind, anyone running Linux can pull apart my recovery, fix the issues in default.prop, add extra partitions to fstab and repack it. then post it for everyone else to use.
with the sh!tty way fastboot is on these phones, and the way modem binaries get patched, you're going to have to look for a way to write these in recovery (scripted with dd i imagine) so that everyone can use without having the ballache that is B100,B121,B140 etc etc to get to a version that will work with your ROM. this for me is where it's all going to hurt! (and end with bricks!)
final thing - the kernel source is terrible, it is so far removed from AOSP that simple things that you could normally just drop in, like cpu governors won't work. unless you really know C++ and how to debug it's gonna be near stock (like mine funnily enough!)
Good luck chaps :good: it's gonna be a hell of a ride!
Click to expand...
Click to collapse
Thanks, this will help enough and I was not aware of your troubles
I got a device tree working with CM12.1 and USB debugging, but Mali was a showstopper. Now I'm fighting with CM13 instead... Generally, the B313 ROM is far less hacky, but we lose the open source kernel for a while until they release one.
I will set up a GitHub tree with what I have when I get CM13 compiling again, however keep in mind that you need to patch the boot.img manually to use the closed-source B313 kernel until Huawei releases the source for that, which probably won't happen at the very least until it's fully in OTA. I'd love some help from someone who is more experienced, especially with the Mali drivers which are the worst of pains.
EDIT: I got CM13 compiling again. Let's hope for the best.
EDIT2: Mali works! Sadly, that currently depends on Huawei's libgui.so which brings in a huge chunk of Huawei's patched libraries - otherwise, it segfaults in strange places. Any ideas?
Is there any whatsapp group of honor 7.I want to join it.
udayraj99 said:
Is there any whatsapp group of honor 7.I want to join it.
Click to expand...
Click to collapse
Stop spamming
Omg I think I will never receive a Custom ROM for PLK-UL00 as they didn't release source code for that and device tree is way far
Mee too
omkarpranavxxx said:
Omg I think I will never receive a Custom ROM for PLK-UL00 as they didn't release source code for that and device tree is way far
Click to expand...
Click to collapse
As an indian user evwn i feel i made wrong choice....should have gone for one plus x
asiekierka said:
I got a device tree working with CM12.1 and USB debugging, but Mali was a showstopper. Now I'm fighting with CM13 instead... Generally, the B313 ROM is far less hacky, but we lose the open source kernel for a while until they release one.
I will set up a GitHub tree with what I have when I get CM13 compiling again, however keep in mind that you need to patch the boot.img manually to use the closed-source B313 kernel until Huawei releases the source for that, which probably won't happen at the very least until it's fully in OTA. I'd love some help from someone who is more experienced, especially with the Mali drivers which are the worst of pains.
EDIT: I got CM13 compiling again. Let's hope for the best.
EDIT2: Mali works! Sadly, that currently depends on Huawei's libgui.so which brings in a huge chunk of Huawei's patched libraries - otherwise, it segfaults in strange places. Any ideas?
Click to expand...
Click to collapse
Hello, did any of the CM compiled fully to be a flashable zip? if yes, then have you flashed it and took logcat?
Nishadan said:
As an indian user evwn i feel i made wrong choice....should have gone for one plus x
Click to expand...
Click to collapse
Yup lesson learnt snapdragon or nothing frm now on
maybe you know
I post link - http://download-c.huawei.com/downlo...oadId=62086&version=204465&siteCode=worldwide
Honor 7 Open Source（PLK-L01_Android5_0_2_EMUI3_1_kernel_EN)
Any progress?
I hope I can do something,it is nice to see cm for honor 7.
Since it has been a while that any Info came out of this thread I have to ask.. Is anyone still working the tree?
I normaly do not ask for etas but in this case it would be useful if the thread is abandoned that we could know the reasons and Problems so maybe someone else could join in with a different approach
cycovision said:
Since it has been a while that any Info came out of this thread I have to ask.. Is anyone still working the tree?
I normaly do not ask for etas but in this case it would be useful if the thread is abandoned that we could know the reasons and Problems so maybe someone else could join in with a different approach
Click to expand...
Click to collapse
I'm a bit busy to continue my work on the tree, but after my exams I will continue to work on tree with Android 6.0 source. Hope it goes well.
DigiGoon said:
I'm a bit busy to continue my work on the tree, but after my exams I will continue to work on tree with Android 6.0 source. Hope it goes well.
Click to expand...
Click to collapse
good luck with your exams
Until then you can use this
New ROM for Honor 7 PLK-L01.
DigiGoon said:
Until then you can use this
New ROM for Honor 7 PLK-L01.
Click to expand...
Click to collapse
Can we get a kitkat rom if your work with the device tree is done ? I really do miss kitkat[emoji20]
Sent from my PLK-TL01H using XDA-Developers mobile app
muhammad Shohayeb said:
Can we get a kitkat rom if your work with the device tree is done ? I really do miss kitkat[emoji20]
Sent from my PLK-TL01H using XDA-Developers mobile app
Click to expand...
Click to collapse
I will be developing AOSP 6.0, if others can give it a try then maybe we can get it.
So, i saw many comments about asking about Nougat, features and stuff... that maybe could be solved all that questions in a thread. If this is pointless, just i'll ask an admin to clean this up... but the point of this thread is solve so common questions about the newer builds of nougat.
This build is stable?
The build is very stable, but not at the point of MM. There's some less battery performance but after all: that builds are in an alpha/beta stage, so... this things could happen. But after all, it works smoothly.
Nice rom, but when you can update it? When you'll fix the bugs?
Everybody's just love when there's an update date or release date, we know it. But please, don't ask ETA. It may annoy the developer, and after all, we're human and we have things happening in real life, so maybe the real life business take over the dev's time to make changes and test it. Be patient, please
There will be a fix for video recording?
The dev's (at this date) are working on it. The known workaround that could be useful is: You can use Cameringo Lite to solve it.
CM14 ONLY: There's CMTE? Can i use themes? X feature doesn't work, what's happening?
By now, the CM people it's working and rebasing their work on the new nougat AOSP. Maybe in october (or when they have it ready) they'll implement slowly all those features. And if some feature doesn't work on the CM14 version, please, remember: that's an alpha build and CM team is working to make it work. By now it doesn't seems to work but, it's an alpha build, that thing could happen.
If you want to theme your device, you could try substratum by now.
This doesn't work on X device, please help
Reporting issues are more useful to devs if you log it. If you have an USB, search in google how to install ADB and use logcat. If you can use the device, you can install catlog, record the log and replicate the issue. After that, copy or upload the log and send it to the dev.
Hope this helps!
will u build cm14 for vee3 ?
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