yashsingh1/xdaforums huggingface dataset:
[Xperia Z3 Original Android Development] nailyk:
Damn! I shouldn't have the right address book as I don't know who is 'bs' ;)

I read hammerhead(-caf) a lot and just figure this out, thanks. Reading the last comment make me think it is not the way he would however.

1. I don't know if he doesn't support me, he simply doesn't answer ;) The first contact I had with him was encouraging and give my a workflow (~1year ago). They are two part into customs roms: the rom and the devices.

CM-12.1 has been dropped by the rom maintainers, and cm-13.0 goes to.

The old maintainer dropped xperia devices around feb because of time and 3.10 kernel wasn't mature. AFAIK he is still active on other devices, like hammerhead.

2. It is not the way code submission work. You made a patch and upload it, then add 'reviewer'. Each project (aka github repo) have different reviewers. If reviewer accept your patch it give +2 and you got merged. Afaik for xperia devices he had the +2 right. Anyway this validation process allow patches to be into the rom guidelines. Also I never heard about a too old device. If someone is able to get device working, without changing toolchain, device get support. (AFAIK this last part is not true into android world, only customs roms. )

2. extra: Shinano & Rhine are the only msm8974 devices with 3.10 kernel. It means some part of the toolchain need to be tweaked to keep compatibility with msm8974 3.4 and 3.10 kernels. This flag had been dropped too and need a new one. The problem is here.

So you need to complies to devices & rom guidlines. Usually it is not difficult, but for our platform it is.

3. Yes, patches get merge with more difficulty into old CM version, that is why I will work only on cm14.

For all those reasons I'm slow into porting, find the best way to introduce changes other have made to get merged one day.

I hope it answers your question and I didn't digress too much :)

P.S.: I dont read it but while look for link I found this about theme support.

Rolling updates are nightly: all builds are done with current repos. If you merge a patch, it is present in tomorrow release, no stable/current or coming branches, all builds are on the line.
[Xperia Z3 Original Android Development] :
Yea, I saw that qcom_target: Remove unused sony HAL support. We need to combine some repos (common, shinan, leo, sepolicy) . And make it look like https://github.com/CyanogenMod/android_device_sony_huashan.

combine nailyk-fr/android_device_sony_common+nailyk-fr/android_device_sony_shinano+nailyk-fr/android_device_sony_leo+https://github.com/sonyxperiadev/device-sony-sepolicy= android_device_sony_leo

android_device_sony_common

android_device_qcom_common

android_kernel_sony_leo (or 8974)

hardware/sony/DASH

android_hardware_sony_thermanager

hardware/sony/thermanager

android_external_stlport
[Xperia Z3 Original Android Development] nailyk:
I don't know if thoses repo will be the hardest to merge.

atm old cm repos are:

device

platform

msm8974

common

and SonyCM are:

device

platform

common

and common are fairly different. (power HAL for example).

I will ask them tomorrow for a new guideline and the new flag. (~1h30 AM here :p)
[Xperia Z3 Original Android Development] :
I just built RR v5.8.0 for the z3, and everything seems to work except bluetooth. I need to check data though. Sensors all work. Camera takes pics, but they're blurry. And no stupid screen glitches. :) Good job man!
[Xperia Z3 Original Android Development] nailyk:
Awesome!

Bluetooth was working perfectly a few days ago and there is some commits since (device tree and kernel). I will try to diff them.

I just build a cm-caf and 3D apps are just perfect. There is a lot of difference into both HAL device-sony-common trees. I will experiment on this too.

(caf SODP)
[Xperia Z3 Original Android Development] :
I think Bluetooth didn't work because I used the wrong repo. ? I'll see if I can combine most of the repos together when I get the chance.
[Xperia Z3 Original Android Development] :
I'm pretty sure we can add the sepolicy and the Sony camera HAL into the actual Leo device tree.
[Xperia Z3 Original Android Development] nailyk:
2016-12-15 release

afaik some of you still use this one.

So new release with partial security update. Not tested.

I fairly abandon this project but feel free to submit PR to the githubs:

leo / shinano / 8974 / kernel or any other then we can review and rebuild.
[Xperia Z3 Original Android Development] Gixchi:
that is super awesome, can you please share the build link, i would like to try .
[Xperia Z3 Original Android Development] akincakiner:
is now the most things working in this one? i am still on cm12.1 but want to update to 13.
[Xperia Z3 Original Android Development] nailyk:
Please start reading here at #234 for the status.

Also this rom isn't updated for month.

Rom was perfectly working except no camera at all. You should take a look at the lineage 14.1.
[Xperia Z3 Original Android Development] akincakiner:
i did and tryed the 2017-01-01 version. but the problem was that it was still bugy and the camera didn't work well. it's extremly bad quality and don t know why. i also tryed to download other camera stuff but didn't work as well than only bad quality. and some apps are force closed. so that's why i am still on CM12.1 it's very stable and everything works well. I thought about trying cm13 but i don t now if it's stable enough to use. i am waiting and looking for new updates around cm14.1 what you are releasing everytime. but i think i will still wait.. or is it stable enough to use it? i am a daily user
[Xperia Z3 Original Android Development] nailyk:
Yes my daily driver is still cm-12.1 too.

The cm-13.0 use the same kernel, so had same stability. But camera can't work on this cm-13.0.

I choose abandoning this cm-13.0, security upgrade cm-12.1 and focus on lineage-14.1. David is currently improving camera and reboot in call issue is about being fixed. I think this 14.1 will became usable in a few
[Xperia Z3 Original Android Development] akincakiner:
i am very exciting for the new 14.1 update. i hope it will be grade :). but the 14.1 won t be abonded right? like being supported for a while
[Xperia Z3 Original Android Development] yecomixer:
CM14.1 is Lineage OS and is built by [MENTION=6979267]nailyk[/MENTION] for the Z3 just have a look at your post
[Xperia Z3 Original Android Development] nailyk:
Customs roms are open sources.

A lot of people are working on kernel then some people (the rom cookers) provide roms. Myself5 CarbonRom, Aclegg used to provide Resurection Remix, Humerto works on Omnirom and David on LineageOS.

All this work is done on spare time so depend on the availability of everyone.

Mostly when the kernel will be stable, improving roms will be easier, and perhaps more people will be able to make roms.

Roms is also user contributing, testing, bugs reports etc. Dev can't test everything so feedbacks are important for improving. Stocks roms are almost fine but will never be upgraded. With stock rom you will mostly be up-to-date with all the available security patches but you can expect some bugs while in testing/alpha state.

Hope it answer your question :)
[Xperia Z3 Original Android Development] rve9925:
Thanks to all of you! As for camera... Is it only hope to wait for new blobs or can you do anything yourselves? Will it ever be working normally? Be honest, false hopes can be frustrating.
[Xperia Z3 Original Android Development] nailyk:
Most we can reach will be cm-12.1 quality until the full blob set are rewritten.

Camera had been improve a lot since I follow the dev work. Except darkness it is close to be usable now under certain circumstances.

Don't expect stock quality.
[Xperia Z3 Original Android Development] frabe8378910:
I'd say this is a really good decision. Let's keep CM12.1 alive and secure, as it is stable and fully functional and could drive the Z3 still for years! :D :D

If someday you Devs get CM14.1 functional and stable - before all Devs are gone crazy on all that Sony "features" - fine, time to switch. :o If not, a maintained CM12.1 is still one of the best things for Z3.... :D
[Xperia Z3 Original Android Development] akincakiner:
Totally agree!
[Xperia Z3 Original Android Development] MrFantome:
I have a question, i. e., I am a daily user and I am concern about how the upgrade from CM12.1 to Lineage 14.1 will be done, would I got to wipe my data (Meh) or would it be possible to upgrade it as an update ?
[Xperia Z3 Original Android Development] akincakiner:
First make always a backup before upgrading.

I tryed to do a normal Update without wiping chache/data. but didn't work. and than i tryed with wiping data. that did work for me
[Xperia Z3 Original Android Development] nailyk:
Funny, you are asking about cm-12.1 and 14.1 in the 13.0 thread :)

It should work. However I didn't try for a while. Maybe an option will be to pass multiples releases, maybe the 13.0 between.

As 14.1 isn't really usable yet, don't really look at this for now.
[Xperia Z3 Original Android Development] nailyk:
Sorry for this moving but looks like more relevant here ;)

If you reread the thread (around the page 12) you should find all my kernel experiments. I was able to start this rom with almost every 3.4 kernels.

IIRC stock M blobs refused to start with something like "Can't start, unauthorized". A DRM thingamajig I can't figure remain somewhere, *not into the bootloader or in the TA partition* however (experiments also in this thread), it is kernel related.

Said often I make mistake, maybe made something wrong on my first experiment, so if you are comfortable enough to experiment you could try with this cm-13.0. It is (almost) stock based, then replace with stock blobs. (maybe leave the hammerhead adreno in place to keep device booting).

Also the only remaining test to do is the same one, but with concept. Maybe the open sourced concept kernel can start the associated blobs.

Good luck and keep us informed :)

CC: [MENTION=4675360]tomascus[/MENTION]

P.S.: I think it is easiest to do those experiments on CM-13.0 because it is M and will not require shim to work properly.

P.S.2: tomascus: if you can provide me a q&d stock kernel I can test if a custom build stock break camera on full stock device.
[Xperia Z3 Original Android Development] tomascus:
https://github.com/tunturn/android_kernel_aries_concept

Cm14.1 branch, just import cyanogenmod Leo defconfig and make the defconfig changes I did yesterday
[Xperia Z3 Original Android Development] nailyk:
I'm confused. Aren't concept and stock two different roms?
[Xperia Z3 Original Android Development] tomascus:
Who said they aren't? Go on hangouts :)

Edit: never mind you wanted a stock kernel, not concept. Gimme 20 min
[Xperia Z3 Original Android Development] lynxeon:
So, what I need to do? It is possible to do with concept or I need the stock blobs?
[Xperia Z3 Original Android Development] nailyk:
2017-01-27 release

Nothing new, periodical build.

3.4 tomascus based.

Still CyanogenMod, not LineageOS.
[Xperia Z3 Original Android Development] akincakiner:
what do you want to know?

---------- Post added at 04:48 PM ---------- Previous post was at 04:45 PM ----------

what does the rebuild do?
[Xperia Z3 Original Android Development] nailyk:
Nothing except periodical rebuild: same sources. Goal was to provide a more up-to-date build for [MENTION=7581879]lynxeon[/MENTION] camera tests.
[Xperia Z3 Original Android Development] akincakiner:
ah okay, i though maybe something to make it more stable XD. I don t use this ROM atm but was thinking of it
[Xperia Z3 Original Android Development] sheng_zongxian:
hello [MENTION=6979267]nailyk[/MENTION] [MENTION=4550727]xkeita[/MENTION]

im still experiencing user's profile picture bug, and sometimes when i try to change wallpaper, it stopped working

the rom more stable on game they improve, i play Mobile Legends: Bang bang

sorry bad english

here is my full logs:

https://pastebin.com/G4KFg9Fe [dmesg]

https://paste.omnirom.org/view/dec6d0d4 [logcat]

my device xperia z3 d6653 variants
[Xperia Z3 Original Android Development] nailyk:
Please repost into 14.1 thread ;)
[Xperia Z3 Original Android Development] sheng_zongxian:
oopss :eek::eek: sorry
[Xperia Z3 Original Android Development] TheAvengingTITAN:
Thank You

Just want to quickly say thank you for your hard work, I really appreciate it. There are users on Z3 General who are freaking out over not receiving Nougat but it is too early for that. I have hope that Leo will pull out of this bad situation of EOL with excellent developers in the community.

Keep doing what you guys do best.

:)

Edit: Didn't see any of your guys activity on Github here so didn't know this didn't exist till I did some digging.
[Xperia Z3 Original Android Development] nailyk:
git status

:) Thanks.

Btw i found this in my today rss.

For now i work on my github and try to keep the manifest file of the op up to date. But this release is really new so it is too early to push to officials (cm/xperiadev) repos. Only twrp is on the way as soon as the boot problem is solved.
[Xperia Z3 Original Android Development] :
I figured out how some of the devs got hammerhead on Android n. I'm pretty sure I can get our z3s on official Android n, once everything is working on hammerhead.
[Xperia Z3 Original Android Development] TheAvengingTITAN:
Quick question, just like a few devices out there right now which have successfully booted up nougat on their devices, has the Z3 been able to boot up a 'prototype build' (as in a build that has features missing or broken, but boots up) or does the Z3 even have a prototype build that hasn't been tested?
[Xperia Z3 Original Android Development] :
I haven't had a chance yet to work on the z3. I've had to make some changes to my aosp 7.0 build, I decided it was easier to make a basic rom based off of n, then to keep cloning in the repos. Using the aosp mm z3 trees and stock aosp kernel, and the latest mm blobs (I can even pull the preview Android n blobs), add some cm patches, I *should* be able to get something bootable.
[Xperia Z3 Original Android Development] yecomixer:
Excellent esperare to this Android version available N to become one of his early work Testers, Greetings
[Xperia Z3 Original Android Development] tiliarou:
Any chance on considering the same work on N for the d6633/83 (dual) ? Is it a big rework or it can be adapted to dual sim easily ?
[Xperia Z3 Original Android Development] Ahmed_HM:
I would like an answer to that question too :D
[Xperia Z3 Original Android Development] Swidilator:
XDA news has posted about Sony building AOSP 7 for its devices, and they say that there are mentions of the Z3, I'd recommend you guys check it out.
[Xperia Z3 Original Android Development] yecomixer:
Sony Posts Guide on Building AOSP 7.0 Nougat for its Xperia Smartphones

http://www.xda-developers.com/sony-...g-aosp-7-0-nougat-for-its-xperia-smartphones/
[Xperia Z3 Original Android Development] AndroidHtc101:
I miss CM13 performance, and the dark themes so much. GL with this thanks for your efforts!
[Xperia Z3 Original Android Development] nailyk:
About the camera i made some progress. The driver part seems to start. Now i need to figure out why HAL3 doesn't work. As soon as we get some minimal camera functions it should go fast if a get some dev help.

About the fm radio I found some kernel flags which could be useful.

Any feedback on data connection?

Also my new screen arrived.... defective :rolleyes: , so not yet touchscreen testing. Does it work?

Haha! That is so me: i open a thread for cm-13.0 and cm-14.0 start the same week :p

Anyway i guess we need to get it working on cm-13.0 before starting on cm-14.0. The deal with cm-14.0 is i really doubt we can stay on 3.4 kernel and for now i really need a 3.4 kernel.

if you can check if it this z3dual it shouldn't be a big deal. This work should be fine for every shinano-based board (Z2's &Z3's) and portable really easily to rhine-boards (Z1's etc...).

If you need tests for z3 dual there is another thread about it, maybe they can make a build?

Edit:

yeah it will be difficult for nougat: msm8974 disappear on 7.0 branch.... And i can't figure out which variant we should use on codeaurora (for now cm-13.0 is based on codeaurora variant).
[Xperia Z3 Original Android Development] Urban Crown:
touch screen is working I can play VOEZ
[Xperia Z3 Original Android Development] :
Nougat is possible. I have n5 and n7 booting up 7.0. I had to throw together a special rom for 8x74. I'll start working on the z3 today.
[Xperia Z3 Original Android Development] nailyk:
All my work from the past 3 days for the camera end in 'rm -rf *'. So i decide to start from scratch for the camera.

ETA: ~5 years: reads doc, learn C/C++/JAVA etc...

In this doc, i read there is substantial changes in the HAL3 for 7.0. In particular it require direct addressing the hardware composer (see api2) which we don't have... So first need port the composer to 7.0

ETA +3 years.

What do you think about it? CM-13.0 for now? Wait a bit and CM-14.0?

Or maybe just give up for the camera (Failure is always an option :p ) ?
[Xperia Z3 Original Android Development] Swidilator:
Team Carbon seems to be doing something with N: https://github.com/CarbonROM/android_device_sony_leo/tree/cr-5.0

I can't guarantee they have made any changes other than merging the Sony branch, but perhaps as time goes on...
[Xperia Z3 Original Android Development] jimmy123322:
Don't give up... Your builds mostly stable except some features like camera... But work is great... Sorry for my english
[Xperia Z3 Original Android Development] nailyk:
Sorry, i mean giving up for the camera (i edit my post consequently, you are right). But it is really bad as z3 is my daily driver and i buy it for the camera :(

About the radio:

The change made in the 2016-08-28 release don't restore the built-in app but spiritf is working well (same results on cm-12.1).
[Xperia Z3 Original Android Development] nailyk:
Thanks i will take a look, but it seems they also use xperiadev 3.10 buggy kernel but there is a lot of interesting fork on it.
[Xperia Z3 Original Android Development] xxlsm:
[MENTION=6979267]nailyk[/MENTION]

I really like your tutorial but I would add some points:

At first you don't have to use EMMA to get the new bootloader. You are also able to use the Sony PC Companion to upgrade to the latest Android N Developer Preview in order to get the OpenDevices bootloader without the requirement of having an unlocked booloader. Therefore you can keep your origin closed TA Partition with the DRM Features. In the future you could be able to backup your TA partition on the new bootloader by an Android N root exploit. Another point ist that the bootloader upgrade is revertible. You can use the repair function of the Xperia PC Companion to downgrade to the older bootloader. Then you are also able to restore old TA Backups. Your explanation could give some users the impression that after the bootloader upgrade with EMMA they will have no possibility to move back to stock or to send the phone to Sony for warranty reasons (because of the unlocked bootloader and missing origin TA partition) and prevent them from testing your CM 13 builds :) Despite of that I really appreciate your work for the community and I hope you will get the results you want to get :).
[Xperia Z3 Original Android Development] nailyk:
What you said is really interesting, but not in the good thread :)

So i answered you in my unbricking? thread (it seems more related)
[Xperia Z3 Original Android Development] optimumpro:
[MENTION=6979267]nailyk[/MENTION]

I am also looking at building M with 3.4 kernel for Z1. Is the camera not working at all? One of the reasons could be the changes in /frameworks/ave/ in M and N. If 3.4 could be modiified (ported some camera features from 3.10), or frameworks/ave files are modified, the camera should work... Sony partially open camera will never fully work by design. Sony simply does not want custom roms on their devices and this together with the switch to 3.10, have killed all chances for a stable custom rom. Also, the newer stock blobs are DRM protected, so they couldn't work on custom roms... . And they don't. Shame on Sony.
[Xperia Z3 Original Android Development] nailyk:
Not working at all... The driver part of the kernel seems working (can't post a dmesg for now as i break my device one more time playing with camera stuff: bootloop ;) ) Do you use the cm toolchain?

I'm really not a dev and just start reading AOSP doc about HAL/camera/etc... so what you point is really interresting. I'm trying to downgrade all the camera stuff for 3 weeks now, according to the 3.4 kernel, but what your are suggesting is to upgrade the kernel driver to match M requirement right?

I'm still hoping: there is a lot of qcom leaked sources on the net (for kitkat) but those sources are interesting anyway. I really doubt the bad camera is caused by lost of drm. As soon as i reflash a stock rom my camera is working perfectly so there is a way to get the camera working with cm even if i need to get my digital analyzer out of my closet and sniff directly on the camera bus (ETA+10 years ;) )! From my readings my initial plan was 1. patch the blobs.

2. rewrite a working camera stuff for this 'drm' part

P.S.: if you need something about building 3.4 for honami, fell free to ping me on freenode. Btw the harder part for me was to workaround this file in the cm toolchain, until done, everything went fine :highfive:

P.S.2: when re-reading before posting i remember my z3 with locked bootloader wont boot with a replacement screen.... I need to go deeper with the DRM stuff but anyway those drm are stored somewhere, maybe we need to replace them? And what about the leaked qcom master key? Isn't this famous key?
[Xperia Z3 Original Android Development] optimumpro:
I think it should be easier to downgrade frameworks/ave/camera. Regarding blobs: I don't know how it is done on Z3, but in Z1, the only way the camera works is by using Jeallybean blobs with a camera wrapper. Starting from Kitkat, Sony began to use DRM protection for their blobs, so none would work with custom roms. In MM, Google has changed frameworks/ave/camera/, so that camera no longer works with 3.4.

I would look at the differences at frameworks/ave/camera first and see if those could be downgraded, as kernel changes might be more difficult to implement...
[Xperia Z3 Original Android Development] nailyk:
For the cm-12.1 our z3 use..... z1 blobs ;) Thanks a lot i will look at this.
[Xperia Z3 Original Android Development] optimumpro:
I don't use CM tool chain. I build my rom like this: first build - Google 4.8. Second build - Google 4.9. And the final build - HyperTool chain 5.4. And I build 3.4 kernel with Ubertc 6.0.
[Xperia Z3 Original Android Development] :
Just to give everyone a heads up. I got hammerhead fully working on aosp n, and today I got my n7 booting and working with Android n. Next device I'm working on us our z3!
[Xperia Z3 Original Android Development] TheAvengingTITAN:
http://developer.sonymobile.com/dow...hives/open-source-archive-for-mob30m-z1-3636/

Concept Developers released the Concept Kernel. Hope this helps :)
[Xperia Z3 Original Android Development] :
Yea, we've been trying to find a kernel that'll work. The 3.10 unified kernel has screen glitches, so this might be the better route to get everything working.
[Xperia Z3 Original Android Development] TheAvengingTITAN:
Great news, glad to be of help :)
[Xperia Z3 Original Android Development] nailyk:
Nice link!

#### make completed successfully (01:21 (mm:ss)) ####

(i don't built it in 1min, i encounter i lot of build problems).

I don't know if i can build a full rom this evening.

Other point, all the specific chipset seems to be deactivated: (see screenshot, copy/paste of terminal doesn't work) and it is the same on every pages. Not tried to boot it atm.

[MENTION=3771760]aclegg2011[/MENTION] [MENTION=5075064]optimumpro[/MENTION] i upload it to my git and can give you write access if you need. build succesfull for z3 with cm_shinano_leotest_defconfig