Anyone knows where can we find changelog of daily builds of ubuntu touch ?
Thanx in advance
Best regards
Miki
I always look here: http://people.canonical.com/~ogra/touch-image-stats/?C=M;O=D
Thanx a lot. Great
Sent from my awesome Ubuntu Touch device using the Forum Browser app
If you want some descriptions as well, check out http://people.canonical.com/~lzemczak/landing-team/ubuntu-rtm/ (for the stable version) or http://people.canonical.com/~lzemczak/landing-team/ubuntu/vivid/ (for devel-proposed).
Does anyone try to use devel-proposed release on BQ?
Edit: if we are using the devel-proposed release, does OTA will come for each new daily build?
mousse04 said:
Does anyone try to use devel-proposed release on BQ?
Edit: if we are using the devel-proposed release, does OTA will come for each new daily build?
Click to expand...
Click to collapse
I'm actively using it on my Nexus 4. However, it's not recommended to install that channel as things break regularly and sometimes you even need to reflash your device. Do it on your own risk.
Updates come through the OTA update mechanism at least once per day. Sometimes they arrive even more often.
Thanks nikwen.
What about using the general rtm channel and not krillin rtm version? What I don't know is if the general channel is updated more often than the krilin version ?
mousse04 said:
Thanks nikwen.
What about using the general rtm channel and not krillin rtm version? What I don't know is if the general channel is updated more often than the krilin version ?
Click to expand...
Click to collapse
I am not aware of any krillin RTM version. The recommended channel is and will probably stay "ubuntu-touch/stable". Currently, it's an alias to "ubuntu-touch/ubuntu-rtm/14.09" but that is going to change in the near future when the stable builds will be based on the vivid builds.
Code:
[email protected]:~$ ubuntu-device-flash query --device=krillin --list-channelsubuntu-core/devel
ubuntu-touch/devel-proposed/krillin.en
ubuntu-touch/devel-proposed/krillin.en-proposed
ubuntu-touch/devel-proposed-customized-here (alias to ubuntu-touch/vivid-proposed-customized-here)
ubuntu-touch/ubuntu-rtm/14.09-factory-proposed
ubuntu-touch/ubuntu-rtm/devel-customized (alias to ubuntu-touch/ubuntu-rtm/14.09-customized)
ubuntu-touch/vivid-proposed-customized-here
ubuntu-touch/devel-proposed (alias to ubuntu-touch/vivid-proposed)
ubuntu-touch/rc/bq-aquaris.en
ubuntu-core/devel-proposed
ubuntu-touch/devel-proposed/ubuntu-developer
ubuntu-touch/stable/ubuntu-developer
ubuntu-touch/ubuntu-rtm/14.09-customized
ubuntu-touch/vivid
ubuntu-touch/devel (alias to ubuntu-touch/vivid)
ubuntu-touch/stable (alias to ubuntu-touch/ubuntu-rtm/14.09)
ubuntu-touch/stable/bq-aquaris.en (alias to ubuntu-touch/ubuntu-rtm/14.09)
ubuntu-touch/ubuntu-rtm/14.09
You can check out the dates of each build in a channel using the following command (the frequency for stable has changed lately):
Code:
[email protected]:~$ ubuntu-device-flash query --channel=ubuntu-touch/stable --list-images --device=krillin
11: description='ubuntu=20141212,device=20141209-cae2b5f,custom=20141119-442-21-160,version=11'
12: description='ubuntu=20141218,device=20141209-cae2b5f,custom=20141216-484-22-169,version=12'
13: description='ubuntu=20150109,device=20150107-5ffb790,custom=20141216-484-22-169,version=13'
14: description='ubuntu=20150116,device=20150113-2a2e4c5,custom=20150112-494-23-173,version=14'
15: description='ubuntu=20150129,device=20150126-cb82dc1,custom=20150127-526-24-181,version=15'
16: description='ubuntu=20150129,device=20150129-c75dcfb,custom=20150129-528-26-182,version=16'
17: description='ubuntu=20150209,device=20150209-094615f,custom=20150207-538-29-183,version=17'
18: description='ubuntu=20150219,device=20150216-fe747ac,custom=20150216-561-29-186,version=18'
19: description='ubuntu=20150219,device=20150225-b67e0b6,custom=20150216-561-29-186,version=19'
20: description='ubuntu=20150312,device=20150310-3201c0a,custom=20150216-561-29-186,version=20'
Krillin is the name for the BQ device
https://wiki.ubuntu.com/Touch/Devices
mousse04 said:
Krillin is the name for the BQ device
https://wiki.ubuntu.com/Touch/Devices
Click to expand...
Click to collapse
I know. However, there's no RTM channel which has "krillin" in its name. Therefore, I was wondering which channel you referred to.
If you're asking for the difference between the Nexus and the BQ builds, I can tell you that there aren't any besides the preinstalled scopes and applications.
The Nexus builds do not contain the new aggregator scopes yet but that applies to all channels.
Since build 193 (devel-proposed) the changelogs are empty. But I get ota updates, so I think something got broken there for the changelogs...
Sent from my awesome Ubuntu Touch device using the Forum Browser app
jonny-boy said:
Since build 193 (devel-proposed) the changelogs are empty. But I get ota updates, so I think something got broken there for the changelogs...
Sent from my awesome Ubuntu Touch device using the Forum Browser app
Click to expand...
Click to collapse
http://people.canonical.com/~ogra/touch-image-stats/vivid/20150514.changes
for todays r212 ???
checked some of my packages with
apt-cache policy <packageName>
Yup seems correct
Ah seems that they put the changes in a new subfolder, which contains the new changes now. Thanks
Sent from my awesome Ubuntu Touch device using the Forum Browser app
I am always using this changelog:
people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/bq-aquaris.en/krillin/
It is still working in dec. 2016
Related
Hello,
is there a Firefox OS image for the LG Optimus L9 P760 ?
git clone git://github.com/mozilla-b2g/B2G.git
./config
Valid devices to configure are:
- galaxy-s2
- galaxy-nexus
- nexus-4
- nexus-4-kk
- nexus-5
- nexus-s
- nexus-s-4g
- flo (Nexus 7 2013)
- otoro
- unagi
- inari
- keon
- peak
- leo
- hamachi
- helix
- wasabi
- fugu
- tarako
- tara
- dolphin
- pandaboard
- vixen
- flatfish
- flame
- emulator
- emulator-jb
- emulator-kk
- emulator-x86
- emulator-x86-jb
- emulator-x86-kk
Is there a compatible model in the list ?
Thanks
ds2k5 said:
Hello,
is there a Firefox OS image for the LG Optimus L9 P760 ?
git clone git://github.com/mozilla-b2g/B2G.git
./config
Valid devices to configure are:
- galaxy-s2
- galaxy-nexus
- nexus-4
- nexus-4-kk
- nexus-5
- nexus-s
- nexus-s-4g
- flo (Nexus 7 2013)
- otoro
- unagi
- inari
- keon
- peak
- leo
- hamachi
- helix
- wasabi
- fugu
- tarako
- tara
- dolphin
- pandaboard
- vixen
- flatfish
- flame
- emulator
- emulator-jb
- emulator-kk
- emulator-x86
- emulator-x86-jb
- emulator-x86-kk
Is there a compatible model in the list ?
Thanks
Click to expand...
Click to collapse
No, ROMs are device specific. You have to port it and add it to the list. I could attempt a port of this, I ported Firefox os to kindle fire HD, its hardware is very similar, and as long as there's a cm device tree that is ICS based or higher I should be able to attempt a build. I only haven't tried yet since my bootloader is yet to be unlocked, but I could attempt a build this weekend if you want, I just need a cm device tree.
Sent from my Amazon Tate using Tapatalk
stunts513 said:
No, ROMs are device specific. You have to port it and add it to the list. I could attempt a port of this, I ported Firefox os to kindle fire HD, its hardware is very similar, and as long as there's a cm device tree that is ICS based or higher I should be able to attempt a build. I only haven't tried yet since my bootloader is yet to be unlocked, but I could attempt a build this weekend if you want, I just need a cm device tree.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
Many thanks.
The Problem is, i get the LG in a few days.
If i have it, i try to give you the cm tree.
There is a guy that build a cm 11 rom for the LG.
http://artas182x.tk/?page_id=287
thanks
OK cool, can't wait to see how this works, its funny you mention it after the fact because a few months ago running Firefox is would have been a complete pain because sgx GPU's were having issues, I was around at the time they fixed it working on kfhd builds. Can't wait to attempt a build on this and see how it goes. Only downside is I can't personally test out the ROM. That being said i can already think of a few issues that might present themselves since the hardware is similar but only time will tell...
Sent from my Amazon Tate using Tapatalk
stunts513 said:
OK cool, can't wait to see how this works, its funny you mention it after the fact because a few months ago running Firefox is would have been a complete pain because sgx GPU's were having issues, I was around at the time they fixed it working on kfhd builds. Can't wait to attempt a build on this and see how it goes. Only downside is I can't personally test out the ROM. That being said i can already think of a few issues that might present themselves since the hardware is similar but only time will tell...
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
Hi,
sorry my english is poor, do you have now any information that you need to build a FireFox OS Image (for LG P760)?
Or do you need anything else ?
thanks
I still need to find the device tree, but I'm going to bed I have to get up for work tomorrow and its late. I'll look into it this weekend.
Sent from my Amazon Tate using Tapatalk
stunts513 said:
I still need to find the device tree, but I'm going to bed I have to get up for work tomorrow and its late. I'll look into it this weekend.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
>I still need to find the device tree,
can i find this in the ROM Package ?
or how to get the "device tree" ?
thanks
stunts513 said:
I still need to find the device tree, but I'm going to bed I have to get up for work tomorrow and its late. I'll look into it this weekend.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
may be the GIT Repo can help you
https://github.com/artas182x
https://github.com/artas182x/lge-kernel-omap4
https://github.com/artas182x/proprietary_vendor_lge/tree/cm-10.1/p760
https://github.com/TheMuppets/proprietary_vendor_lge/tree/cm-11.0/p760
Thanks, I was hoping for a cm 10.2 dev tree but I can work with cm 11, their 4.3 builds were more stable than my current 4.4 builds on kfhd, though my 4.4 builds have a ton more bugs fixed from upstream. Thanks for that I will take a look at it this weekend.
Sent from my Amazon Tate using Tapatalk
stunts513 said:
Thanks, I was hoping for a cm 10.2 dev tree but I can work with cm 11, their 4.3 builds were more stable than my current 4.4 builds on kfhd, though my 4.4 builds have a ton more bugs fixed from upstream. Thanks for that I will take a look at it this weekend.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
here is the CM 10.2 device tree (i hope so)
https://github.com/artas182x/android_device_lge_p760/tree/cm-10.2
https://github.com/artas182x/android_device_lge_p760/tree/cm-10.2-cwm
thanks
ds2k5 said:
here is the CM 10.2 device tree (i hope so)
https://github.com/artas182x/android_device_lge_p760/tree/cm-10.2
https://github.com/artas182x/android_device_lge_p760/tree/cm-10.2-cwm
thanks
Click to expand...
Click to collapse
ok thanks, thats a good part of it i think, i will have to see about putting together a manifest using that repo plus maybe a few others, last time i did this it was with a device that wasnt official at the time so i had a manifest generated for the process already that made my life easier, so i will have to do some research this time to figure out what repos i need, i can guess that one and definately the proprietary blobs. Will try to get this done sometime soon, ran out of time this weekend because i was also doing something on my domain controller to update some deployment images and the freaking power inverter for the lcd screen died...
a small update before i head to work, i managed to get it to start the compilation process now, so now comes the tedious debugging process, already hit one error about selinux attribs that needs to be set correctly so there arent duplicates, those are easy enough to fix, just thought you might want an update.
if anybody is still curious how this is going, i'm tryin got fix an issue involving the kernel not compiling, finally decided to go with using a prebuilt but iunfortunately having a hard time figuring out why defining TARGET_PREBUILT_KERNEL isnt working...
Found the Firefox OS trining manual (sort of)
stunts513 said:
if anybody is still curious how this is going, i'm tryin got fix an issue involving the kernel not compiling, finally decided to go with using a prebuilt but iunfortunately having a hard time figuring out why defining TARGET_PREBUILT_KERNEL isnt working...
Click to expand...
Click to collapse
Nt really my field of expertise, but I read the post and found something I thought might be helpful. This was a link posted by (Duckbill, I think):
http://csmg.lgmobile.com:9002/gdmsp...1&ret=1&curPage=2&searchtype=&keyword=&arg01=
It is a link to the LG South Korea portal of some kind entitled: 2013-11-04 FireFox OS Training Material. It is presented as a .zip file but when extracted with 7z, it only produces this:
[autorun]
open=LGMain.exe
icon=LGMain.exe,0
The file is larger than 5MB so I'm sure this is simply more LG encryption, although I don't really understand the implications of the instructions. On the remote chance that this is helpful, let me know how it helped.
I got a successful build, not sure if it will work but it built successfully. If you wanna test it post back and i''ll post the link soon, still have to upload it.
*** USE AT YOUR OWN RISK! I AM NOT RESPONSIBLE IF THIS SOFTWARE OR SOMETHING ELSE SUDDENLY FRIES YOUR DEVICE. ***
ok this is just a alpha build so no guarentees it will even boot and since i have the p769 with a locked bootloader i can't really test the build. Again this is for the p760 and i would like to mention if it doesnt work i wouldn tbe surprised if you get stuck at the bootloader logo while the os is actually trying to boot, if this happens i blame the hwc module, so if it does happen i believe you should have superuser access at a adb shell and you can simply run
Code:
adb shell mount -o rw,remount /system
adb shell rm /system/vendor/lib/hw/hwcomposer.p760.so
adb shell rm /system/vendor/lib/hw/hwcomposer.omap4.so
adb reboot
that might fix a not booting issue. This is a barebones build, until i know i have a build that can sucessfully build i dont bother tsing bluetooth and rild and such. I can say that since i didnt make the modifications i did last time that i'm assuming bluetooth is probably not enabled right now.
anyways i will make this a thread in the dev section when its out of testing. Here's a link to the first alpha build if you are willing to try it: http://d-h.st/5Kq
anybody going to test this? I let it sit for a few days but i was hoping to have some testers by now. Can't really debug it myself without having a actual device thats unlockable. Theoretically i might be able to run this with a 2nd init exploit, never tried setting one up on a b2g os though.
stunts513 said:
anybody going to test this? I let it sit for a few days but i was hoping to have some testers by now. Can't really debug it myself without having a actual device thats unlockable. Theoretically i might be able to run this with a 2nd init exploit, never tried setting one up on a b2g os though.
Click to expand...
Click to collapse
I can try to test it
please let me know where to download the image(s)
In the post before last. Thanks BTW.
stunts513 said:
In the post before last. Thanks BTW.
Click to expand...
Click to collapse
I have the CWM v6.0.4.5 from artas182x, and the CyanogenMod 11 from artas182x on my P760
if i do "install zip" -> "choose zip from /external_sd" -> full_p760-ota-eng.stunts513-signed.zip
assert failed: getprop("ro.product.device") == "p760" || getprop("ro.build.product") == "p760"
E:Error in /external_d/full_p760-ota-eng.stunts513-signed.zip
(Status 7)
Installation aborted.
ALL WORK HAS MOVED TO THE 3.4 BRINGUP. YES, THAT MEANS 3.4 IS BOOTING AND WIP AND THIS KERNEL IS NOW DEPRECATED! CLICK HERE TO VIEW 3.4 PROGRESS
Check latest posts for updates
As you may be aware, we've been trying unsuccessfully to boot Nvidia's 3.4 kernel for tegra 3 on grouper.
Progress has pretty much halted, as this project needs to be finished before we have any hope of 3.4 ever working.
SAUCES
-
WE ALSO HAVE A GITHUB ORGANIZATION
What is this?
An attempt to get Google's ludicrously outdated grouper 3.1 kernel up-to-date with Nvidia's 3.1 kernel.
Why?
1) It'll be, put simply, "better" than Google's out-of-date kernel (...potentially)
2) This *must* be completed before work on 3.4 goes ahead
3) Hopefully other kernels, such as franco's, could be merged with this
How?
I did a "git rev-list" of Nvidia's branch, then Google's branch, all the way back to the point where Google added grouper support (Around March 2012), then diffed the result. I've attached the files in this post: The commits in the diff which have a + next to them are Nvidia's commits, as these are not present in Google's log. I simply need to cherry-pick all 1,699 of these, and make sure to manually update the grouper board files exactly as Nvidia's dev. boards are updated (because of course grouper itself is not updated at all in Nvidia's source). Then I need to fix all the compilation errors. If I get through around 50 - 80 commits a day, and fix the compilation errors the next day, I should be finished in 2 months max. Then serious 3.4 work can begin.
Should I use it?
From a user's perspective, in all honesty, no. This is a) a WIP and b) a means to another end (3.4). Other offerings such as franco's kernel are so far more improved than Google's anyway that this will not be necessarily "better" than those simply due to a load of updates from Nvidia. What *will* make this useful is if the final product is merged, as I said, into existing kernels, thus improving those. That said, I'll never upload a new version before having tested it myself, so you can be in the very least assured that it'll boot and run.
HOWEVER it would be extremely useful if you could run this simply for testing purposes. All my trust is placed in Nvidia's commits and my own ability to fix conflicts and compilation errors. Things may go wrong and your help would be massively appreciated.
Shutupandletmeflash!!!
I'll post updates regularly as possible here. I've used agnostic as it's fantastic. The naming scheme is: Alpha whilst I'm still cherry-picking, Beta once that's done and we're testing to fix bugs, then RC once its in a stable, releasable state (there'll probably only be 1 RC, then no more work); The numbering is x.y where x indicates major release (0 is Alpha, 1 will be Beta) and y will be increment by 1 on every single release.
Credits
@sgt. meow
Nvidia
Google
Asus
@legolas93 for F2FS
@frantisek.nesveda for agnostic-kernel
Anyone else I've forgotten (sorry, it's a while since I opened the 3.4 discussion thread)
XDA:DevDB Information
linux-tegra-nv-3.1-grouper, Kernel for the Nexus 7
Contributors
HTCDreamOn, Ziyan, n1kolaa, sgt. meow
Source Code: https://github.com/Ziyann/android_kernel_asus_grouper
Kernel Special Features:
Version Information
Status: No Longer Updated
Created 2014-11-23
Last Updated 2015-06-07
FAQ
Q: Why is TricksterMod/ CPUSpy/etc. Not showing 1300MHz?
A: read this post.
GREAT! :good:
Its great to see people giving attention to an old device.
I will look forward to it.
What you forgot me
You know moral support!!
Lol J/K
Good thing you put it in original development
That will help.
So keep up the... Hmm dont know how to express it....
Your doing an beyond awesome job!
Maaayyybeeee Google will update the grouper kernel when Lollipop code will be pushed to AOSP... But I'd be suprised if the Nexus 7 even got official Lollipop.
frantisek.nesveda said:
Maaayyybeeee Google will update the grouper kernel when Lollipop code will be pushed to AOSP... But I'd be suprised if the Nexus 7 even got official Lollipop.
Click to expand...
Click to collapse
I'm sure we will get Android 5 one way or another
USBhost said:
I'm sure we will get Android 5 one way or another
Click to expand...
Click to collapse
Well, it will be official, at least according to Android Police.
http://www.androidpolice.com/2014/10/15/being-the-will-of-our-lord-duarte-the-nexus-7-2012-will-receive-the-holy-blessing-of-android-5-0-official/
frantisek.nesveda said:
Well, it will be official, at least according to Android Police.
http://www.androidpolice.com/2014/1...ve-the-holy-blessing-of-android-5-0-official/
Click to expand...
Click to collapse
USBhost said:
I'm sure we will get Android 5 one way or another
Click to expand...
Click to collapse
I appreciate your interest and support, but please, this is a development thread, and nothing to do with L whatsoever. That topic belongs here. If you want to post here a bugreport or in the very least a relevant question from a development perspective is all I ask. Thanks.
frantisek.nesveda said:
Maaayyybeeee Google will update the grouper kernel when Lollipop code will be pushed to AOSP... But I'd be suprised if the Nexus 7 even got official Lollipop.
Click to expand...
Click to collapse
I expect the kernel will be updated as it was for 4.4 from 4.3. I'm still carrying on with this, however, as of course the new kernel will still be 3.1.10. Then I can apply those updates on top of this.
P.S Did some more cherry-picking today. Mostly smooth, very few conflicts so far.
HTCDreamOn said:
I appreciate your interest and support, but please, this is a development thread, and nothing to do with L whatsoever. That topic belongs here. If you want to post here a bugreport or in the very least a relevant question from a development perspective is all I ask. Thanks.
Click to expand...
Click to collapse
Sorry, I got a little carried away with the Lollipop release. I'll test the kernel during the weekend. This is only for AOSP, or can we run it on CyanogenMod as well?
frantisek.nesveda said:
Sorry, I got a little carried away with the Lollipop release. I'll test the kernel during the weekend. This is only for AOSP, or can we run it on CyanogenMod as well?
Click to expand...
Click to collapse
Same here
the kernel should work with CM
frantisek.nesveda said:
Sorry, I got a little carried away with the Lollipop release. I'll test the kernel during the weekend. This is only for AOSP, or can we run it on CyanogenMod as well?
Click to expand...
Click to collapse
No idea... CM use CAF for Qualcomm but we're Tegra 3 so I think it should be fine. Nandroid, flash, restore if it breaks, and no harm done. I'm uploading Alpha 0.1 right now Android browser is a pain with attachments, 0.1 will be tomorrow.
HTCDreamOn said:
No idea... CM use CAF for Qualcomm but we're Tegra 3 so I think it should be fine. Nandroid, flash, restore if it breaks, and no harm done. I'm uploading Alpha 0.1 right now.
Click to expand...
Click to collapse
Awesome will test 0.1
also 0.0 booted just fine on All-F2FS CarbonROM
USBhost said:
Awesome will test 0.1
also 0.0 booted just fine on All-F2FS CarbonROM
Click to expand...
Click to collapse
0.1 uploaded. Glad it works.
0.1 running ok so far only thimg i have noticed is interactive locks at 1200mhz on all 4 cores. On demamd scales fine
gptwarrior said:
0.1 running ok so far only thimg i have noticed is interactive locks at 1200mhz on all 4 cores. On demamd scales fine
Click to expand...
Click to collapse
Interactive has never ran good on my tablet no matter what kernal.
Sent from my Nexus 7 using Tapatalk 2
gptwarrior said:
0.1 running ok so far only thimg i have noticed is interactive locks at 1200mhz on all 4 cores. On demamd scales fine
Click to expand...
Click to collapse
Thanks for pointing this out, I hadn't noticed this before but it's happening to me as well. I seem to remember a commit affecting cpufreq scaling somewhere so this could be it, but it should be easy to fix. I might stock up these smaller problems and fix them right at the end to reduce conflicts, but if its simple enough I'll fix it soonish.
In other news, Alpha 0.2 has been uploaded (first post as usual) mostly just more commits picked, but we're starting to get to the good stuff: changes to tegra3 drivers etc. And some things I can use to update grouper board files :good:
Alpha 0.2 works well here.
Snappy for a stock kernel.
Only things to report:
Max freq is 1200 with all governors.
To turn the tablet on after sleep I have to press the button a lot.
Keep up the good work!!!
Agreed with alpha 2 running smooth same as above with frequency at 1200 keep up the good work looking forward to future updates
I just installed Alpha 2 on LiquidSmooth 3.2. After the first boot, I got multiple force closes on "com.android.acore" but after a reboot everything seems to work just fine. I will use it for the next days and report any bugs I encounter.
I just tried the alpha 2 on my tilapia running a clean install of CyanogenMod 2014-10-23. On the first boot everything is fine, but after a reboot I get SystemUI FC's everytime I unlock the device and it relocks again.
When I install M-kernel a69 or alpha 1 of this kernel, everything seems to be fine. I am using Data-F2FS, if it matters somehow.
I can post a logcat or kmesg tomorrow, right now I screwed up my hackintosh bad and it doesn't even boot, so I don't have a way to access adb.
[#nexusmultitoolp1]
If you like it, you might consider donating.
DOWNLOADS
Source Code - Github
[#nexusmultitoolp2]
XDA:DevDB Information
Nexus Multitool, Tool/Utility for the Nexus 6
Contributors
photonicgeek, photonicgeek
Version Information
Status: Beta
Current Beta Version: 0.10
Beta Release Date: 2014-11-23
Created 2014-11-24
Last Updated 2014-11-24
[#nmchangelog]
Reserved for stuff. Probably.
Thanks for this! Going to make things a lot easier for people just getting their phones
Awesome news, my N6 should b arriving this week. What root method does this tool use? Custom kernel or is it using the SuperSU 2.27beta?
spunks3 said:
Awesome news, my N6 should b arriving this week. What root method does this tool use? Custom kernel or is it using the SuperSU 2.27beta?
Click to expand...
Click to collapse
Custom kernel. I think it is the better option in the long run because google can easily patch the method that Chainfire uses now. The kernel method, however, is very unlikely to be patched. This will patch whatever kernel you want to use though, so you'll be fine!
Sweet! Just wondering, do you think it would be possible to bundle in a decryption feature as well?
Not really original development
Sent from my Nexus 9 using Tapatalk
Xileforce said:
Sweet! Just wondering, do you think it would be possible to bundle in a decryption feature as well?
Click to expand...
Click to collapse
paychex said:
Not really original development
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
@Xileforce Already in there in v0.10!
@paychex
According to XDA it is! The "Original elements": Device decryption for N6 and N9, supports every single Nexus device, offers a ROM installer for compatible devices, etc.
http://forum.xda-developers.com/showthread.php?t=2112240
The following are most likely “Original Development”:
*Official releases of highly original and upstream custom ROMs (built from the ground up with significant original development within them
*Official releases/development of such original ROMs, perhaps posted by the maintainer or their nominated person.
*A significant “first” in development for a device. Significant is subjective, but it is likely something which took considerable time/effort, and is generally accepted by developers to be significant and non-trivial.
*Kernels which are built with beneficial changes that are not simply pulled from other kernels already available. Some element of original work is expected.
*Tools and utilities with a clear purpose, and which are well-made, and useful to users. They should have an element of originality, either in purpose or through significant improvement in the means of operation.
*Significant port of a ROM from one device to another, giving enhanced features or functionality to users of the target device. The port should be beneficial (a port from two virtually identical devices isn’t original development, it’s winzipping, and nobody really benefits from this, as it’s not development)
Click to expand...
Click to collapse
Thanks for the Linux support!
Cool, might have to check this out!
tried to dl latest tool kit and file isnt downloading correctly...
Delete
Ep3n3wp said:
tried to dl latest tool kit and file isnt downloading correctly...
Click to expand...
Click to collapse
What do you mean? I can't help if I don't have more info...
photonicgeek said:
What do you mean? I can't help if I don't have more info...
Click to expand...
Click to collapse
Sorry never mind... My error... Not sure how to rub/use the download on my windows comp.
Have to go read up on shell downloads or whatever... Thought it was supposed to download an .exe
Sorry
Ep3n3wp said:
Sorry never mind... My error... Not sure how to rub/use the download on my windows comp.
Have to go read up on shell downloads or whatever... Thought it was supposed to download an .exe
Sorry
Click to expand...
Click to collapse
Oh, yeah. It is Mac and Linux only. It's all good!
I'm looking forward to using this once I get my Nexus 6.
sithdroid2187 said:
I'm looking forward to using this once I get my Nexus 6.
Click to expand...
Click to collapse
When that day comes, let me know how it works!
Ive still never fully grasped how to use adb on Mac. Ive got the file downloaded and on my desktop and have terminal cd'd to the file correctly and when I enter "chmod +x Nexus-Multitool.sh" it tells me there is no such file or directory...any help is appreciated.
Photonicgeek, will this interfere with adb/fastboot packages I already have installed or will it operate separately ? (Linux)
Thanks
Edit: I no longer own this phone. Information in the OP may be outdated and/or incorrect. Please go to the new thread at http://forum.xda-developers.com/nexus-6/development/rom-cyanogenmod-13-nightlies-snapshots-t3363769
DISCLAIMER: I AM IN NO WAY RESPONSIBLE FOR ANY PROBLEMS ON YOUR DEVICES CAUSED BY FLASHING THESE BUILDS. THE UPSTREAM CODE AND BUILDING IS MAINTAINED BY THE CYANOGENMOD TEAM, NOT ME. I AM NOT ASSOCIATED WITH THEIR TEAM, I AM JUST THE THREAD OWNER.
It was a fun round of unofficial nightlies but the official upstream CM13 builder for shamu is active! Please use the new download links below to grab the official nightlies. Dirty flash seems to work fine if you go from my unofficial 11-29 build to the official 11-30 one. As mentioned in the first post, I will be ceasing my personal builds for now and leave it to the CM team.
Notes: CyanogenMod's stock kernel forces encryption of storage. Please download one of the third party kernels if you wish to avoid this. Also this thread assumes you have kept up to date with bootloaders and radio. At the time of writing, the latest is from the MRA58K release and can be downloaded here.
CyanogenMod 13.0 Nightlies: Download
Open GApps: Download (I recommend arm, 6.0, micro)
Changelog: CMX Changelog
Third party kernels:
Elite Kernel
Hells Core
XDA:DevDB Information
CyanogenMod 13.0, ROM for the Nexus 6
Contributors
djh816
ROM OS Version: 6.0.x Marshmallow
Based On: CyanogenMod
Version Information
Status: Nightly
Created 2015-11-22
Last Updated 2015-12-06
There's already a thread
http://forum.xda-developers.com/nexus-6/development/rom-cyanogenmod-13-0-android-6-0-t3231497
HipKat said:
There's already a thread
http://forum.xda-developers.com/nexus-6/development/rom-cyanogenmod-13-0-android-6-0-t3231497
Click to expand...
Click to collapse
Correct, but not nightly and as far as I can tell albinoman887 is also making fixes which implies altering of upstream code. My thread intends to serve as a purely upstream source build.
djh816 said:
Correct, but not nightly and as far as I can tell albinoman887 is also making fixes which implies altering of upstream code. My thread intends to serve as a purely upstream source build.
Click to expand...
Click to collapse
I would like to say thank you, and I believe that this ROM deserves its own thread respectfully. Since there isn't much action from that other Alpha build and if you are truly building on a nightly basis then this is much appreciated and I look forward to testing.
Thanks!
HipKat said:
There's already a thread
http://forum.xda-developers.com/nexus-6/development/rom-cyanogenmod-13-0-android-6-0-t3231497
Click to expand...
Click to collapse
A Thread with Zero Support from the Thread OP and no Nightlys , its good to see this Thread with hopfully regular updates since I currently have working in the border guarding Work and never have time for building. But what i know from @djh816 updates come many times.
Tylog said:
A Thread with Zero Support from the Thread OP and no Nightlys , its good to see this Thread with hopfully regular updates since I currently have bodybuilding in the border guarding Work and never have time for building. But what i know from @djh816 updates come many times.
Click to expand...
Click to collapse
Thanks for the support and glad to build it. Just to make sure credit is given where due, any bug fixes will be made only by the CyanogenMod team and/or any git contributors. Not sure if you'll get much support from me either but I'll certainly be glad to give any tips I find. For example, if this one specific bug rears its ugly head again, you may need to rename the SetupWizard apk inside /system/app-priv/ as that has been constantly force closing for me prior to today's build.
djh816 said:
Thanks for the support and glad to build it. Just to make sure credit is given where due, any bug fixes will be made only by the CyanogenMod team and/or any git contributors. Not sure if you'll get much support from me either but I'll certainly be glad to give any tips I find. For example, if this one specific bug rears its ugly head again, you may need to rename the SetupWizard apk inside /system/app-priv/ as that has been constantly force closing for me prior to today's build.
Click to expand...
Click to collapse
MAybe test other Gapps, i had this isues with a few cm 13 builds in combination with banks gapps , i like Banks gapps but for now not with CM13 . No support for me no problem , only 1 builds in 3 Weeks in this early stage is a problem , thats what i mean . I have at the moment zero time , i am one day in the week at home and thats time for my son and my wife
Thanks for the builds. I tried (unsuccessfully) to build my own, so this helps out a lot!
nightlies has not started yet.. looking forward..
Awesome! Thanks!
Sent from my Nexus 6 using Tapatalk
Can anyone confirm that you can write to system on this build???? Wasn't working on a build from 11.20.
Sent from my Nexus 6 using Tapatalk
mexiken said:
Can anyone confirm that you can write to system on this build???? Wasn't working on a build from 11.20.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Still is not working.. I'd love to know of a fix, if any...
mexiken said:
Can anyone confirm that you can write to system on this build???? Wasn't working on a build from 11.20.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I modified build.prop just fine.
---------- Post added at 03:10 AM ---------- Previous post was at 03:08 AM ----------
Thanks OP, for bringing this to us. Seems pretty good for such an early build. I just barely flashed it but seems great so far.
Does ad away work on this build? It wouldn't work on the previous build.
Is security disable on the ROM?
cz829x18 said:
Does ad away work on this build? It wouldn't work on the previous build.
Click to expand...
Click to collapse
Doesn't seem to just yet. As others have mentioned, no /system writing just yet.
evolishesh said:
Is security disable on the ROM?
Click to expand...
Click to collapse
Doesn't seem like it, I've tried "adb shell" with "su" after but still drops me to a "$" shell rather than "#"
Will you be adding any features or will this be more of a slim to stock cm13 builds? Also thanks for your contributions
nighthawk626 said:
Will you be adding any features or will this be more of a slim to stock cm13 builds? Also thanks for your contributions
Click to expand...
Click to collapse
No features added whatsoever If they add it upstream (included in CM) it'll be here, otherwise no. Absolutely stock. Consider me a third party buildbot slave
Very nice ROM. Just to let everyone know I just finished flashing with the Open GApps Pico and it's working fine. I know, it's bad form to use something that's not recommended.
One quick question, do we get any notification that the new nightly is ready to flash or do we just check the download site?
dlbarron said:
Very nice ROM. Just to let everyone know I just finished flashing with the Open GApps Pico and it's working fine. I know, it's bad form to use something that's not recommended.
One quick question, do we get any notification that the new nightly is ready to flash or do we just check the download site?
Click to expand...
Click to collapse
For now just the download site. I may setup something similar to the pushbullet feed Chroma has if people are interested but haven't spent the time to do it yet. New 11-23 build is up now though
Edit: Woot, looks like they fixed the system rw mounting. Hm but my test file disappeared on reboot.. maybe not yet
I am going to be working on a build of Lineage13 for our phone. Thanks to Corvus for the basic source.
Development source: https://github.com/JTS2111/device_le_le_zl1
To-Do (Will add to as I go):
-Get logs from CN users
-Patch kernel for safetynet
-Get a first stable build to give for testing
-Get logs from own phone (US)
-Finish To-Do
Long term To-Do:
-Stability and somewhat decent battery performance
-Completely CTS compatible (that'll be fun)
-Unified .zip for x727 and x720 (might borrow TS scripts)
-Security updates for at least a couple months.
As I get a stable build, I will post it here for testers. Right now, I'm setting up basic debugging for my phone to get the big crashes out of the way.
ETA: Hope to expect a experimental build by the end of the week.
jts2111 said:
I am going to be working on a build of Lineage13 for our phone. Thanks to Corvus for the basic source.
Development source: https://github.com/JTS2111/device_le_le_zl1
To-Do (Will add to as I go):
-Get logs from CN users
-Patch kernel for safetynet
-Get logs from own phone (US)
-Finish To-Do
As I get a stable build, I will post it here for testers. Right now, I'm setting up basic debugging for my phone to get the big crashes out of the way.
Click to expand...
Click to collapse
On behalf of all the owners of the Le Pro 3, thank you for taking the time to make a ROM for us :good:
Added long-term To-Do and tweaking build environment.
jts2111 said:
Added long-term To-Do and tweaking build environment.
Click to expand...
Click to collapse
Hi jts, I'm working on this fork too, just working on getting a fully automated vagrant setup. I'm working on a windows machine, and it's become painfully obvious windows 10 bash (a lovechild of ubuntu and windows 10) is garbage and doesn't work for literally anything you might need bash for. Setting up virtualbox is a pain in the ass. And at the end of the day, if you setup ubuntu, and need to change things for some other build, you might break your current build. I'll keep you posted.
robertzas said:
Hi jts, I'm working on this fork too, just working on getting a fully automated vagrant setup. I'm working on a windows machine, and it's become painfully obvious windows 10 bash (a lovechild of ubuntu and windows 10) is garbage and doesn't work for literally anything you might need bash for. Setting up virtualbox is a pain in the ass. And at the end of the day, if you setup ubuntu, and need to change things for some other build, you might break your current build. I'll keep you posted.
Click to expand...
Click to collapse
Bash on Ubuntu on Windows is only good for basic operations. And I'm actually just starting another Ubuntu VM. No old builds broken. Though its good to have someone to exchange code with.
I already have ~95% working builds of 13 & 14. I have issues with some missing sensors in 13 and camera problems in 14.1.
Sent from my ASUS_Z008 using Tapatalk
Cannot wait to try out this one. While we have two other CM roms, development progress of those seem to have stopped. I was disappointed then this happened. I thank you for those involved in it.
jrior001 said:
I already have ~95% working builds of 13 & 14. I have issues with some missing sensors in 13 and camera problems in 14.1.
Sent from my ASUS_Z008 using Tapatalk
Click to expand...
Click to collapse
Can't wait to try it
Many thanks for your work :good:
Good luck with this! Cant wait!!!
Only for a summery.
We have to get the source code for camera and the other stuff is ready? Or not so difficult?
So definetly possible to geht a stable rom
And i saw that there are more people in this thread who are working in lineage OS. Do you work togetjer? I hope so Then its easier for you all :highfive:
And a little question for a dev noop If we have lineage 13, is it a long and complete new way to delvelope lineage 14.1 or is it similar and not tooo difficult?
manuelbvb said:
Only for a summery.
We have to get the source code for camera and the other stuff is ready? Or not so difficult?
So definetly possible to geht a stable rom
And i saw that there are more people in this thread who are working in lineage OS. Do you work togetjer? I hope so Then its easier for you all :highfive:
And a little question for a dev noop If we have lineage 13, is it a long and complete new way to delvelope lineage 14.1 or is it similar and not tooo difficult?
Click to expand...
Click to collapse
Camera is fine on 13. Just some config stuff I'm fixing. I'm at the moment not working with anyone else, though it would be easier. In terms of 14.1, look at the omniROM 7.1. We would have the same issues with camera and sensors due to the lack of libs.
Also, as a status update, the ROM is very stable with CTS most likely to work with Magisk. Will post soon as I build it.
jts2111 said:
Camera is fine on 13. Just some config stuff I'm fixing. I'm at the moment not working with anyone else, though it would be easier. In terms of 14.1, look at the omniROM 7.1. We would have the same issues with camera and sensors due to the lack of libs.
Also, as a status update, the ROM is very stable with CTS most likely to work with Magisk. Will post soon as I build it.
Click to expand...
Click to collapse
The only major issue I have is with sensors currently on 13 branch. I've got a few missing I can't seem to get working proper. I'm sure there's other minor things but sensors is my only major hurdle right now.
Sent from my LeEco Le Pro3 using Tapatalk
@jts2111 and @jrior001
Which sensors are not working?
corvus said:
@jts2111 and @jrior001
Which sensors are not working?
Click to expand...
Click to collapse
Proximity and compass are the ones giving me trouble on lineage13.
Sent from my LeEco Le Pro3 using Tapatalk
jrior001 said:
Proximity and compass are the ones giving me trouble on lineage13.
Sent from my LeEco Le Pro3 using Tapatalk
Click to expand...
Click to collapse
Proximity works for me, at least the sensor is detected and it changes using any app that tests the sensors (cpuz or aide).
About orientation, I didn't test it so I can't say anything.
If you updated sources from Lineage in the last days, bear in mind that the sources could be broken.
Update: Broken VM environment and source setup. Will try to set up a new Ubuntu ENV. and get a build up soon.
Just for info...
Device tree:
https://github.com/LineageOS/android_device_leeco_zl1
Kernel:
https://github.com/LineageOS/android_kernel_leeco_msm8996
Code review:
https://review.lineageos.org/
codeworkx said:
Just for info...
Device tree:
https://github.com/LineageOS/android_device_leeco_zl1
Kernel:
https://github.com/LineageOS/android_kernel_leeco_msm8996
Code review:
https://review.lineageos.org/
Click to expand...
Click to collapse
Thank you for these infos :good:
Hope more ROMs for Le Pro 3 :fingers-crossed:
Le Pro 3 is listed here: https://devs-lab.com/lineageos-supported-device-rom-download.html#LineageOS_ROMs_for_other_devices
Which Rom did they link? Someone from here or who made this rom?
manuelbvb said:
Le Pro 3 is listed here: https://devs-lab.com/lineageos-supported-device-rom-download.html#LineageOS_ROMs_for_other_devices
Which Rom did they link? Someone from here or who made this rom?
Click to expand...
Click to collapse
It's chako67's test build (https://forum.xda-developers.com/le-pro3/development/lineageos-13-t3548926)