Hello everybody,
Before I jump into the compilation proces and uploading my build I want to ask everybody first if anybody is interested in a weekly build CM10.
I know that Ivendor is not changing his sources every week, but the base of CyanogenMod is under constant development, so changes in the CyanogenMod source will be up to date again.
Let me know if you're interested by replying to this thread.
Also if theres enough interest in a build with kernel 3.0 inside I'm also willing to upload this image as well.
Because already one person replied I'm willing to share my compiled image. After all it's already compiled.
This build is compiled against ivendors sources on his Github and the latest CyanogenMod sources which were available.
Of course this image is already tested on my phone and everything seems to work like it did on Ivendor's last build.
Because Ivendors sources haven't been changed, this build still has the same bugs as his build.
To be complete the following:
- Vsync doesn't work, because the current kernel doesn't support this yet.
- Panorama shots
- Also mobile internet has a little glitch, which only appears to happen if you have a Pin locked SIM.
Solutions to this are:
* Setting the phone into Airplane Mode and back to normal. This should load the needed module.
* A more clean solution is to use the patch provided at: d-h.st/BgH This patch can be applied through CWM.
- Also camera view is upside down, but this is not noticable in the final saved image. (Don't know if this is a new or already known bug I don't use camera that much).
You can download my build from: mediafire.com/?m765ok5mtly7l6h
You have to copy the links into you're adress bar, because I'm not yet allowed to post outside links.
If anyone has questions feel free to ask.
Greetings PsychoGame
a weekly build would be nice
i don´t use the 3.0 kernel because of the not working camera
i hope it changes soon
Hereby I updated my thread and put in the links to where you can download my build.
Greetings PsychoGame
PsychoGame said:
Hereby I updated my thread and put in the links to where you can download my build.
Greetings PsychoGame
Click to expand...
Click to collapse
Great idea. You can use 2 builds,one with 2.6 kernel, second with 3.x
it would be very great
Sent from my GT-I9001 using xda premium
Recently I started a new blog on Github. The idea is to publish an article with tips and android code snippets, together with a full sample project on Github. Since everything is hosted on Github, everyone can contribute to them.
Today I published a new article about communicating with Android services using ResultReceiver.
http://ramdroid.github.io/androiddev/index.html
Hey everyone,
I check regularly the commits to the Oneplus One Cyanogenmod repository via cmxlog.com.
Today I found this interesting revert: https://review.cyanogenmod.org/#/c/142559. This is the original commit, one day earlier: https://review.cyanogenmod.org/#/c/141623
The cyanogenmod sources contain some tracking metric for Trebuchet. The default launcher. The tracking code relies on the "com.cyngn.stats" - App. AFAIK it doesn't exist in cyanogenmod. I tried to check the OTA Package for CyanogenOS 13 for the Oneplus One (ref). But I couldn't extract it. So I checked the CyanogenOS 12 Package for the Oneplus One (ref). It doesn't contain the App "com.cyngn.stats", but a reference to it: "/system/etc/permissions/com.cyngn.stats.xml". Maybe someone who installed the CyanogenOS 13 OTA can check if "com.cyngn.stats" is installed? I use CyanogenMod 13 on my Oneplus One, not the official Cyanogen OS.
So, I conclude, maybe all Cyanogen OS 13 are being tracked by Cyanogen Inc via the default Trebuchet launcher. (If the app com.cyngn.stats is installed). The reverted code even contained the analytics key (com.cyanogen.ambient.analytics.key).
I also think that that this tracking isn't related to the anonymous statistics found in CyanogenMod (which you can disable). But I don't know what "com.cyngn.stats" does, if it is installed - or if it has an reference to the anonymous statistics option.
Please look at the source and tell me your opinion. Maybe I overreact. Or I miss something.
vorcers
Cyanogen spying on us?
I think for tracking bugs?
New CyanogenMod 13 snapshot build (ZNH5Y) is rolling out.
The Android ROM community isn't quite as active as it was a few years ago with Android itself becoming more feature-rich. Still, CyanogenMod is chugging along with support for a ton of devices and a reasonably fast update cycle. A new snapshot build of the Marshmallow-based CyanogenMod 13 is now official (ZNH5Y), and it will be available on the first wave of devices today.
This is a snapshot build, meaning it's the most stable build of CM you can get. Of particular note, this version of CM will include all security patches up through the August bulletin. Build ZNH5Y also includes fixes for several of the recently reported Quadrooter kernel vulnerabilities. Two of the vulnerabilities aren't accessible to the CM team, so those patches need to come from further up the chain.
If you're running the ZNH0E snapshot build, you can flash the new one on top of it. ROMs for various devices will roll out as they are ready. Today, you can expect downloads for popular devices from OEMs like OnePlus, Samsung, and Motorola, as well as most Nexus devices. The full list is available on CM's blog post, but they're all code names.
Source: http://www.androidpolice.com/2016/08/15/new-cyanogenmod-13-snapshot-build-znh5y-rolling/
CM 13.0 Release – ZNH5Y - http://www.cyanogenmod.org/blog/cm-13-0-release-znh5y
Full changelog: http://pastebin.com/ptatg6kh
cm-13.0-20160816-SNAPSHOT-ZNH5YAO0F6-bacon.zip
Link - http://download.cyanogenmod.org/get/jenkins/174518/cm-13.0-20160816-SNAPSHOT-ZNH5YAO0F6-bacon.zip
Which is better / newer ? This on ore this one cm-13.1.1-ZNH2KAS2X1-bacon-signed-704f3ea59b ?
Thanks in advance
EDIT: I discovered what is difference, this one is cyanogenmod the other one is cyanogenOs, i got wrong with the filename.
I get reboots every time I receive a phone call with clean install and the latest stock opengapps. Works fine without opengapps, now trying to get it to work without the google dialer.
Edit: ok I looked into it, I never had to do this on recent cm13 nightlies but it's necessary to set dialer as default app for phonecalls.
Spaghetti-XRY said:
Which is better / newer ? This on ore this one cm-13.1.1-ZNH2KAS2X1-bacon-signed-704f3ea59b ?
Thanks in advance
EDIT: I discovered what is difference, this one is cyanogenmod the other one is cyanogenOs, i got wrong with the filename.
Click to expand...
Click to collapse
Your are trying to compare CM with COS?
I am the proud owner of two Oneplus One devices. (TWRP 3.0.2.0)
Just dirty flashed cm-13.0-20160816-SNAPSHOT-ZNH5YAO0F6-bacon on top of the previous Snapshot version on my two devices.
DDR is wiped perfectly.
Flash process well documented (log on screen)
After Flash, do a wipe of Cache / dalvik (just to be sure)
That's all. Works well, no issues.
Again, a nice job of Cyanogen.Mod... (Some may not like them, but I (and my devices) do like them)
Hi all!
As Sony has posted instructions on how to compile Android Pie for our XZ (among others), I just wondered if anyone here has tried it?
The posted guide looks quite straight forward, but as I have no experience on using fit-repost and such I'm not sure I'm up for the challenge of taking this project on.
If tried, what could be expected to work? I know that for all previous Xperia devices, camera and wifi components has always been weak-points in AOSP-roms..
Please discuss and advice!
Regards, Static.
I'm currently trying to build android P for XZ with the guide from Sony.
I'm downloading the code ATM.
I'll give you feedback about my journey to Pie ^^
Awesome!
I'm eager to hear about your endeavors in this!
L'ily said:
Hey me too, do you have a single- or dual-SIM variant?
Click to expand...
Click to collapse
I have a single sim variant
L'ily said:
Nice, I have the F8332 so we can test on both models. I have no idea what I'm doing though and whilst an unofficial GApps 9 build is available (albeit only in Stock) it doesn't appear Sony have released the vendor images yet so even if we successfully build I'm disinclined to believe they'll boot, although I'm going to try with the last release anyway.
Click to expand...
Click to collapse
Didn't Sony released beta vendor images for kernel 4.9 ?
I thought that would be compatible with pie.
That being said, it should be bootable without it. We will just have to check the kernel version and flash the vendor image accordingly.
@L'ily and I have been trying to build Pie for F8331 and F8332 but sadly it didn't work ...
The first issue we had was with the repo syncing. On my end it took an incredible 48h (@400KB/s peak) and also failed 3 times but by relaunching it I made it to the end. My partner however had a worst yet faster time with syncing. Maybe it is due to localisation (Australia and France) . We think it is simply because the repos weren't ready. I mean they are still no vendor files for Pie.
Second issue was with building. None of us could get through it. We kept having an error (see screen shot). It seams like it is a file missing but we didn't know we're to look for it as the sync was complete.
We tried both engendering build and userdebug. Same error.
@L'ily also tried build Oreo but it didn't work either ...
If anybody has an input on what we could do we would be grateful
Cheers,
Ickule
Here is the screenshot I mentioned in my previous post.
I forgot to include it ...
Ok so I managed to get through the building process. The missing files have matching name with files in an other folder (4.4 instead of 4.9).
That being said it sadly didn't boot.
That was kind of expected if you ask me ^^'
Still I don't get why i didn't had the files in the first place ...
Any input guys ?
I'm currently trying to build Pie myself (for the 309234023492094th time in the last two days) with other errors every time I set up a new machine. But what I can say about the error with the missing kernel file is that there's a script in the sony repos that looks like it'd be building the missing file, although I'm not sure if we have to call it manually first
31, so single-sim and unfortunately, I don't have the logs anymore as I always started with fresh machines.
I'm currently checking the other forums because I'm not really satisfied with the solution of using 4.4 kernel binaries with a 4.9 build
Edit: I might have achieved something, I compiled the kernel from 4.9 sources I hope and it's now building. Fingers crossed ?
Edit 2: It boots!
I definitively agree on the fact that using 4.4 files aren't optimal for a 4.9 build ^^'
I tough of compiling the kernel before hand.
Let us know how it turns out
However I'm puzzled with 31 as being the choice for F8331. On my laptop it's 55 (engeneering build). 31 Being marlin userdebug.
Ickule said:
I definitively agree on the fact that using 4.4 files aren't optimal for a 4.9 build ^^'
I tough of compiling the kernel before hand.
Let us know how it turns out
However I'm puzzled with 31 as being the choice for F8331. On my laptop it's 55 (engeneering build). 31 Being marlin userdebug.
Click to expand...
Click to collapse
That's exactly what I did and it seemed to work
With 31, I meant F8331
Edit: I think I chose 56 or so, it was the userdebug option for F8331
Magic-Fabi said:
That's exactly what I did and it seemed to work
With 31, I meant F8331
Edit: I think I chose 56 or so, it was the userdebug option for F8331
Click to expand...
Click to collapse
So you managed to get Pie working or only compiling the kernel ?
Thanks for clarifying the 31 thing
Yes, Pie booted on my device! But no gapps or camera, for that we'll have to wait
Xperia z1 has carbon Android pie and gapps link
This may help you.
Magic-Fabi said:
Yes, Pie booted on my device! But no gapps or camera, for that we'll have to wait
Click to expand...
Click to collapse
That's awesome !
Did you dio anything special aside from the instructiosn sony gave ?
I try to build Pie and the Kernel by the books but i always seam to fail for some reason ^^'
I'm usung Ubuntu 18.04 for the building OS.
No, all I used was Sony's guide and referenced Google's build instructions for the libraries I have to install. For the missing kernel file I used their (manual!) Kernel compilation guide
I used Ubuntu 18.04 LTS as well, the only "unusual" thing I did was that I didn't install any openjdk version and even deleted the one preinstalled as they have openjdk bundled with aosp ?*
Edit: Note that you have to copy and rename the compiled kernel file in arch/arm64/boot/Image.gz-dtb to kernel-dtb-kagura in /kernel/sony/msm4.9/common-kernel. You can easily read past that as I did in the beginning
Well let's assume I had a bad syncing time or something cause I followed the very same instructions ^^'
Anyway, it seam like we still miss the vendor files from sony so ...
I'll give it another shot when they'll be out.
Just a curious thing, will GCam work on Pie like it did on AOSP Oreo?
I believe the requirement for GCam is Camera API 2 and raw support which is built into AOSP.
It surely will be compatible.