Related
Hi guys, i've this version with fixed GSM problem that it won't connect to the SIM card, i've also tried to fix wifi and 3G, but when i build the framework.jar it show me a lot of errors, saying me that there are variable not defined, i've tried replacing with the framework.jar from CM9 FXP 216 and it stuck on boot, can anyone help me fixing these problems? I think that a look of Xperia S with a CM9 base it's amazing because we can have more touchpad compatibilty with farenheit's fix than in stock ROMs.
Thanks for your attention.
{Gangster}.
About the fix.
If you want i can upload the modified framework.jar to see how we can manage to fix it.
Uploaded the fix.
Here i've uploaded the fix on framework.jar, i don't have time to build a flashable CWM zip.
Here we go.
Link.
For people that don't understand what i'm doing, please visit this URL to the main ROM.
SEMC Debrand Engine for PLAY by Achotjan.
No one?
So if we flash the Rom you. Linked to and that fix it will work?
Sent from my Xperia Play (r800x)
Do you have any news about the jellybean version of semc rebrand engine that you talked to its developer about? It looks as if he's stopped working on it.
Sent from my Xperia Play (r800x)
Device: Xperia Z1 C6802/L39h
It is the latest firmware for Z1. I got this firmware from EMMA.
PLS do not ask for EMMA ID.
cause I cannot upload to the international hosts, so if someone could transport the FTF to other hosts, pls go for it!
and I will try my best to upload to SkyDrive or Google Docs.
[DOWNLOAD]
14.1.G.1.526_TW_1276_3106
Baidu：http://pan.baidu.com/share/link?shareid=1377587252&uk=1929740006
SkyDrive： http://sdrv.ms/19G3Y4n （thanks [email protected]）
Untitled Xperia Team
present
[谢绝 机锋网 转载 ]
I've uploaded it to skydrive，here's the link http://sdrv.ms/19G3Y4n
sj8023ld said:
I've uploaded it to skydrive，here's the link http://sdrv.ms/19G3Y4n
Click to expand...
Click to collapse
Nice, thanks!
macallen said:
Device: Xperia Z1 C6802/L39h
It is the latest firmware for Z1. I got this firmware from EMMA.
PLS do not ask for EMMA ID.
cause I cannot upload to the international hosts, so if someone could transport the FTF to other hosts, pls go for it!
and I will try my best to upload to SkyDrive or Google Docs.
[DOWNLOAD]
14.1.G.1.526_TW_1276_3106
Baidu：http://pan.baidu.com/share/link?shareid=1377587252&uk=1929740006
SkyDrive： http://sdrv.ms/19G3Y4n （thanks [email protected]）
Untitled Xperia Team
present
[谢绝 机锋网 转载 ]
Click to expand...
Click to collapse
Thanks for sharing and using understandable English unlike the other one.
This shall be useful after the device is available.
I'm uploading flashable zip for CWM of this fw, deodexed and some bloatware removed
For c6903 are new updates?
after too many test i finally made a patch for porting ics stock roms from arc/s (and maybe other xperia 2011 devices) to pur lovely xperia play
it will install all the things that you need for fully working rom on xperia play and deletes the cybershot camera(because it not working on our device)
installation guide:
there are 2 ways for installing
1-if the rom has armo installer
2-if it doesnt have armo installer
if it has armo installer its very easy to use this
here is the instruction
1-open rom zip and ics rom porter.zip files with winrar
2-find the device section in rom zip file
3-drag all the files inside system folder in the ics rom porter.zip to lt28i(xperia arc) folder of rom zip
4-now simply flash the rom zip ans choose xperia arc as your device and everything will be fine
if the rom doesnt have armo installer
do the same thing as i said for the the roms with armo installer but instead of draging the files to lt28i folder drag them to system folder
bugs:
1-no touchpad. i need help for this part.
2-flashable.zip is broken. i need help for this one too
3-build.prob will be replaced with xperia z v5 by markphyton so you wont see the original tweaks after the port
4-some of the roms will give bootloop because they have more space than our system partition. if some one can repartiton a kernel with more system storage it will be great
to do list:
1-making an armo zip with all build.prob form popular roms and the requested roms
2-adding touchpad fix
tested on(working):
1-anzumi : by myself
2-4.1.b.1.13(arc version by jader) : by myself
tested on(not working):
xperia ray 4.1.b.1.13 (touchscreen had some problems)
download link:
http://d-h.st/eJv
thanks to:
1-markphyton : i have taken my files from his rom
2-all the developers of xperia arc :for making roms(that gived me the idea of this patch)
3- xda: all of us know why
4-dev host : i use it for uploading my files
5-xperia play users : for not giving up
reserved
please help me for fixing the bugs
i will start working on gb and jb patch as soon as i get time
waiting for reports now
that all i can do now
if you want to help for completing this patch i need help for these things
1- someone with good knowledge in making armo installer and update.zip files
2-someone for helping me in making build.prob files of requested roms
3-(the moost ipmortant) helping me for fixing touchpads
Smokerman is good in porting roms, you should ask him for touchpad fix
I have basic knowledge of aroma installer and build.prop editing, if i can, i'll help
touchpads
@smokerman
can you help me for fixing the touchpads?
i will release an update soon
things that i changed:
1-fixed the flashable zip
2-im using 4.0.4 ics build.prob instead of xperia z rom by markphyton
jb patch is being tested now
for now i only get bootloops
but im trying to solve the problem
i aslo wanted to make an gb patch but i saw that we will get a little problem in gamepad after porting gb roms from arc
(always open game pad. you cant use touchscreen for gaming anymore in ported gb roms.)
pedyvirus said:
@smokerman
can you help me for fixing the touchpads?
Click to expand...
Click to collapse
i can help for sure..what is the rom? send me the link..i will look into it on the weekend.
well im making a patch for all of the roms
i need to know the way so i can support all the roms that xperia play users want
do you use farenheith's patch for fixing the touchpad in stock based roms?
update coming in less than 30 minutes
im doing the final test
changelog:
1-you don't need to do anything yourself now. just flash the rom + the porter package and everything is finished
2-build.prob replaced with 4.1.b.1.13 for xperia play (made by myself)
3-updated most of the files
to do list:
1-building a 410mg system partition kernel.(i really need help or this one. i don't have enough experience)
2-fixing touchpads (i really dont know how to this because i never fixed touchpads for stock based ics roms. please help me )
also i saw project lard remover script
it can remover build.prob lines
if i can remove xperia arc lines and replace them with xperia play lines most of the bugs will be fixed
but my problem is with different build.prob lines like 4.1.b.1.13 or 4.1.b.0.631 and these things
for now i will add a guide about how to make the build.prob yourself for activating the build.prob tweaks of the rom after applying my patch(for better speed)
update: i got bootloop using the new zip although its working with the old way of porting (extracting the files to the system folder)
i will release it when i fix this problem
pedyvirus said:
update coming in less than 30 minutes
im doing the final test
changelog:
1-you don't need to do anything yourself now. just flash the rom + the porter package and everything is finished
2-build.prob replaced with 4.1.b.1.13 for xperia play (made by myself)
3-updated most of the files
to do list:
1-building a 410mg system partition kernel.(i really need help or this one. i don't have enough experience)
2-fixing touchpads (i really dont know how to this because i never fixed touchpads for stock based ics roms. please help me )
also i saw project lard remover script
it can remover build.prob lines
if i can remove xperia arc lines and replace them with xperia play lines most of the bugs will be fixed
but my problem is with different build.prob lines like 4.1.b.1.13 or 4.1.b.0.631 and these things
for now i will add a guide about how to make the build.prob yourself for activating the build.prob tweaks of the rom after applying my patch(for better speed)
update: i got bootloop using the new zip although its working with the old way of porting (extracting the files to the system folder)
i will release it when i fix this problem
Click to expand...
Click to collapse
is it possible to port ics stock rom of arc to our device(xperia miro) (2012) ?????
a help would be appreciated!!! and i know @pedyvirus you can help me
I'm here to question the device owner. There are few sources around about this device. They are raw and they are as common always experimental. Does anyone need them?
Furthermore, I can sum up here any sources I or other get to find about this device or its periphery.
If you are eager to Void your Warranty please Mind and Acknowledge that every modification only affects you and your contract and noone else.
custom rom
http://forum.xda-developers.com/xperia-xa/development/f3112-f3116-cyanogemod-13-project-t3488890
Silversniper said:
I'm here to question the device owner. There are few sources around about this device. They are raw and they are as common always experimental. Does anyone need them?
Furthermore, I can sum up here any sources I or other get to find about this device or its periphery.
Click to expand...
Click to collapse
Very good thing, I'm trying to build a CM13 rom from sources and I'm not sure if I have all required sources. For now I have, kernel sources with some "vendor" files from Sony and I found all build parameters like offsets/adresses and correct cmdline (no thanks to Sony because never released or mentioned them), the device tree dumped from my device, and I will dump the vendor tree too.
Now I need the defconfig for CM (very not sure if the stock one will work) , and some files like the boardconfig and some config files. I'm using the Elephone P9000 sources for sample, almost the same device (hardware side) and source files.
If I have some time I will try to upload files to git but I never tried before (sync only)...
rrvuhpg said:
Very good thing, I'm trying to build a CM13 rom from sources and I'm not sure if I have all required sources. For now I have, kernel sources with some "vendor" files from Sony and I found all build parameters like offsets/adresses and correct cmdline (no thanks to Sony because never released or mentioned them), the device tree dumped from my device, and I will dump the vendor tree too.
Now I need the defconfig for CM (very not sure if the stock one will work) , and some files like the boardconfig and some config files. I'm using the Elephone P9000 sources for sample, almost the same device (hardware side) and source files.
If I have some time I will try to upload files to git but I never tried before (sync only)...
Click to expand...
Click to collapse
Don't need to hesitate. I'll try to put the directions I've gathered here up today so it is done.
I finished to upload my files to Github:
https://github.com/rrvuhpg
You will find the device, kernel and vendor files to build CM13 for F3112/F3116. For now it will not work, it's just to share and help. I successfully built and booted the Cyanogen recovery with the kernel from sources, the doors for porting new roms are open?? :fingers-crossed:
My next step is to finish the device tree, verify the vendor tree and build the rom
rrvuhpg said:
I finished to upload my files to Github:
https://github.com/rrvuhpg
You will find the device, kernel and vendor files to build CM13 for F3112/F3116. For now it will not work, it's just to share and help. I successfully built and booted the Cyanogen recovery with the kernel from sources, the doors for porting new roms are open?? :fingers-crossed:
My next step is to finish the device tree, verify the vendor tree and build the rom
Click to expand...
Click to collapse
cool.. if work I would like to have it on my f3111 !!
rrvuhpg said:
I finished to upload my files to Github:
https://github.com/rrvuhpg
You will find the device, kernel and vendor files to build CM13 for F3112/F3116. For now it will not work, it's just to share and help. I successfully built and booted the Cyanogen recovery with the kernel from sources, the doors for porting new roms are open?? :fingers-crossed:
My next step is to finish the device tree, verify the vendor tree and build the rom
Click to expand...
Click to collapse
Can you publish some brief preview?
Need to say the sources I had just seem to be down, so can't share them.
Through which Program are these to flash? If you're that far I can hold a look at it and may join in your development.
Verification of the Vendor Files is something I was not very good at it, not even a yolk I managed.
Silversniper said:
Can you publish some brief preview?
Need to say the sources I had just seem to be down, so can't share them.
Through which Program are these to flash? If you're that far I can hold a look at it and may join in your development.
Verification of the Vendor Files is something I was not very good at it, not even a yolk I managed.
Click to expand...
Click to collapse
For now the only preview I can publish are the CM13 boot and recovery "as is", I'm not sure if it can help but I will release them if someone want to port others MTK Roms on XA. ( Never booted any ported rom with the stock kernel, stuck at Sony logo)
Flashing is easy: the recovery with fastboot and Rom/boot in a single flashable zip on the SD.
The kernel sources are coming from 33.2.B.2.95 open source archive from Sony but built from the lastest CM13 and Google git sources.
The vendor tree from 33.2.B.2.93 dumped from my phone, only common files with the P9000 are on my git for now.
The device tree from P9000 sources (from @Deepflex git) but seem OK.
CM13 have Android 6.0.1, I don't know if the security patch is the last one but August for sure.
I'm not so far from a finished build (not mean fully bootable), for now I successfully build a full CM13 for the Elephone P9000 (the twin of the XA, I'm using it as base). It mean my "kitchen" is working Now I'm trying to identify the last proprietary files from all others stock/cm13 libs, modify make files and cross my fingers it will fully build without errors.
You can join me no problem all people are welcome because I can't do all alone
rrvuhpg said:
For now the only preview I can publish are the CM13 boot and recovery "as is", I'm not sure if it can help but I will release them if someone want to port others MTK Roms on XA. ( Never booted any ported rom with the stock kernel, stuck at Sony logo)
Flashing is easy: the recovery with fastboot and Rom/boot in a single flashable zip on the SD.
The kernel sources are coming from 33.2.B.2.95 open source archive from Sony but built from the lastest CM13 and Google git sources.
The vendor tree from 33.2.B.2.93 dumped from my phone, only common files with the P9000 are on my git for now.
The device tree from P9000 sources (from @Deepflex git) but seem OK.
CM13 have Android 6.0.1, I don't know if the security patch is the last one but August for sure.
I'm not so far from a finished build (not mean fully bootable), for now I successfully build a full CM13 for the Elephone P9000 (the twin of the XA, I'm using it as base). It mean my "kitchen" is working Now I'm trying to identify the last proprietary files from all others stock/cm13 libs, modify make files and cross my fingers it will fully build without errors.
You can join me no problem all people are welcome because I can't do all alone
Click to expand...
Click to collapse
good work , but I am noob to create rom with kitchen .. only zip edit I know
Yesterday I successfully built CM13 for XA from sources
But news are not good, the CM recovery is fully working as expected but the rom is stuck just after the Sony logo (Mediatek screen with "loading...") like on my previous attempts to port other roms. The kernel built from CM kitchen do the same... I will upload my git and my rom to see if someone have an idea on the problem. Now I will focus on the "vendor" files, but I'm not sure if it's the real problem. Can it be a locked preloader/kernel or something like that?
EDIT: I think the boot problem is related to the defconfig file from Sony kernel sources, I will try to change some settings. (the door for adding kernel features :good
rrvuhpg said:
Yesterday I successfully built CM13 for XA from sources
But news are not good, the CM recovery is fully working as expected but the rom is stuck just after the Sony logo (Mediatek screen with "loading...") like on my previous attempts to port other roms. The kernel built from CM kitchen do the same... I will upload my git and my rom to see if someone have an idea on the problem. Now I will focus on the "vendor" files, but I'm not sure if it's the real problem. Can it be a locked preloader/kernel or something like that?
EDIT: I think the boot problem is related to the defconfig file from Sony kernel sources, I will try to change some settings. (the door for adding kernel features :good
Click to expand...
Click to collapse
Love you!
I will buy this phone thanks to you :highfive:
Thank you for your work on our phone, it's very cool.
I would have helped if i could develop myself. If you need help get in touch with me i know some great devs who could maybe help you
any news @rrvuhpg ?
Yes I have some news but I want to create a dedicated thread for the CM13 project with updates, explanations and downloads to avoid off topic here. I am on holiday on next week and I will have time to work on it and give explanations. For now I'm stuck on boot because of Sony extra settings in the boot process, it's the first time I see a bootstrap and TA partition mount on a MTK device. If you know a dev for helping me passing the Sony part in the boot init it can be great :angel:
Other thing, I updated my git with parts of the update made by @Deepflex on the P9000 sources and my recent changes.
rrvuhpg said:
Yes I have some news but I want to create a dedicated thread for the CM13 project with updates, explanations and downloads to avoid off topic here. I am on holiday on next week and I will have time to work on it and give explanations. For now I'm stuck on boot because of Sony extra settings in the boot process, it's the first time I see a bootstrap and TA partition mount on a MTK device. If you know a dev for helping me passing the Sony part in the boot init it can be great :angel:
Other thing, I updated my git with parts of the update made by @Deepflex on the P9000 sources and my recent changes.
Click to expand...
Click to collapse
sorry first time I use sony ... I wish you to have nice holiday !
Hello,
this thread is only for development discussion regarding development of android for msm8974. If you have anything useful, it's the right place, however, it's not for non-dev things.
Current state of cam:
working, though, still low quality. Will be fixed on v6. (and no videocam)
if you wanna have live chat, you can join an IRC
http://webchat.freenode.net/?channels=#freexperia
placeholder
Ok. Seems I have wasted time with camera I think file which I used as a hal for nougat (camera.msm8974.so) from stock rom is not even used on stock rom, its just an aosp camera hal which is compiled by sony rom compilation! Somebody need to comfirm that please (just install stock rom 4.6.1.A.236 and remove camera.msm8974.so from system/lib/hw , try if camera working), I have no free time to install that stock rom to test that thing but I think that stock rom uses camera.qcom.so (which is not wrapper I think, its sony special camera hal), I am pretty sure that these lib is camera hal which sony uses on that rom! Somebody need to confirm!
So now i will explain all a little bit more
It is possible to get 3.4 kernel booting and working but the problem are the camera blobs for 3.4 too
All cam blobs above 4.4.4 can not used because they need drm keys but if you unlock your bootloader you will lose them
We have disscued this with all old cm maintainer and aosp devs including me as i'm one of the aosp devs
Booting 3.4 should need some hal changes in display and audio and the stock kernel need a lot of patches to get it boot on nougat
So in general 3.4 will work but we should focus on 3.10 its more efficend and if you see the progress over the last year we have done something which has no other manufacture. I fully understand all off you but we want to continue support of our devices for a long time and this is definitly easier on 3.10.
I know that sony will keep msm8974 as long as possible in the open device programm but it will end in some time because qcom discontinued the ardeno support which make it harder for all of us. I will give my best to bring msm8974 on 3.10 stable as a rock and hopefully with cam
So keep it up and help to fix the things
If you need some help or some more infos you can write me via pm or hangouts
munjeni said:
Ok. Seems I have wasted time with camera I think file which I used as a hal for nougat (camera.msm8974.so) from stock rom is not even used on stock rom! Somebody need to comfirm that please (just install stock rom 4.6.1.A.236 and remove that file from system/lib/hw , try if camera working), I have no free time to install that stock rom to test that thing but I think that stock rom uses camera.qcom.so which is not wrapper as a tomascus say, I am pretty sure that these lib is camera hal which sony uses on that rom! Somebody need to confirm
Click to expand...
Click to collapse
huh? isn't that camera.qcom.so too small to be hal? (sorry, still no device...)
munjeni said:
Ok. Seems I have wasted time with camera I think file which I used as a hal for nougat (camera.msm8974.so) from stock rom is not even used on stock rom! Somebody need to comfirm that please (just install stock rom 4.6.1.A.236 and remove that file from system/lib/hw , try if camera working), I have no free time to install that stock rom to test that thing but I think that stock rom uses camera.qcom.so which is not wrapper as a tomascus say, I am pretty sure that these lib is camera hal which sony uses on that rom! Somebody need to confirm
Click to expand...
Click to collapse
Stock uses camera. msm8974.so but it checks if drm vertity is present but we can nor rewrite the whole l drm verity on 3.4 because its closed source
SuperLamic said:
huh? isn't that camera.qcom.so too small to be hal? (sorry, still no device...)
Click to expand...
Click to collapse
I don't know but I will try in next few days when I get more free time for installing sotck rom
rcstar6696 said:
So now i will explain all a little bit more
It is possible to get 3.4 kernel booting and working but the problem are the camera blobs for 3.4 too
All cam blobs above 4.4.4 can not used because they need drm keys but if you unlock your bootloader you will lose them
We have disscued this with all old cm maintainer and aosp devs including me as i'm one of the aosp devs
Click to expand...
Click to collapse
Thats bul****! When you unlock bootloader on stock rom you still have working camera!!! WTH drm keys!
rcstar6696 said:
Booting 3.4 should need some hal changes in display and audio and the stock kernel need a lot of patches to get it boot on nougat
Click to expand...
Click to collapse
That allso is not true! Only selinux and mmap proc tunable for mmap_base ASLR is need to get it boot on nougat! For more info here you can see kernel which boots on nougat, see commits for more info! https://github.com/munjeni/android_kernel_sony_msm/commits/master
Please don't post misinformation if you are not 100% sure!
munjeni said:
Ok. Seems I have wasted time with camera I think file which I used as a hal for nougat (camera.msm8974.so) from stock rom is not even used on stock rom, its just an aosp camera hal which is compiled by sony rom compilation! Somebody need to comfirm that please (just install stock rom 4.6.1.A.236 and remove camera.msm8974.so from system/lib/hw , try if camera working), I have no free time to install that stock rom to test that thing but I think that stock rom uses camera.qcom.so (which is not wrapper I think, its sony special camera hal), I am pretty sure that these lib is camera hal which sony uses on that rom! Somebody need to confirm!
Click to expand...
Click to collapse
Camera.msm8974 is an useless lib on stock rom
Camera.qcom is Sony camera hal.
I had found out it few months ago.
munjeni said:
Thats bul****! When you unlock bootloader on stock rom you still have working camera!!! WTH drm keys!
That allso is not true! Only selinux and mmap proc tunable for mmap_base ASLR is need to get it boot on nougat! For more info here you can see kernel which boots on nougat, see commits for more info! https://github.com/munjeni/android_kernel_sony_msm/commits/master
Please don't post misinformation if you are not 100% sure!
Click to expand...
Click to collapse
If you read it again you will see that i talk about drm verity not drm keys
Test it if you want we had cm13 booting on 3.4 and it was only possible with display patches audio patches where only needed to fix some small sound issues
Chirayu desai one of the cm maintainer can confirm this.
Selinux is correct this needs to be rewritten and mmap too but i wanted to write it understandable for all guys not only for devs
The other thing about the camera hal is an info from alin but if you say he isnt correct then you will be right :good:
It could be possible that the cam will start without but not with all Features
Do what you want but i'm quite sure that you don't get a fully working cam
rcstar6696 said:
If you read it again you will see that i talk about drm verity not drm keys
Click to expand...
Click to collapse
I don't know which device you have but I speak about Honami and Amami only. On Honami and Amami unlocking bootloader have nothing to do with camera, only some small changes in picture quality can be noticed. I will definitelly go to 3.10 kernel till after camera gets working
mkdmc said:
Camera.msm8974 is an useless lib on stock rom
Camera.qcom is Sony camera hal.
I had found out it few months ago.
Click to expand...
Click to collapse
Thats what I thinking now too! Did you tested, whats happening when camera.msm8974.so gets removed, is camera working? I need confirmation on rom 4.6.1.A.236 ! Which I found camera.qcom.so uses chocobal and excal blobs, camera.msm8974.so uses nothing from that.
rcstar6696 said:
Stock uses camera. msm8974.so but it checks if drm vertity is present but we can nor rewrite the whole l drm verity on 3.4 because its closed source
Click to expand...
Click to collapse
Did you try to grep that file? For example
strings camera.msm8974.so | grep drm
You can see null results about drm
rcstar6696 said:
So now i will explain all a little bit more
It is possible to get 3.4 kernel booting and working but the problem are the camera blobs for 3.4 too
All cam blobs above 4.4.4 can not used because they need drm keys but if you unlock your bootloader you will lose them
We have disscued this with all old cm maintainer and aosp devs including me as i'm one of the aosp devs
Booting 3.4 should need some hal changes in display and audio and the stock kernel need a lot of patches to get it boot on nougat
So in general 3.4 will work but we should focus on 3.10 its more efficend and if you see the progress over the last year we have done something which has no other manufacture. I fully understand all off you but we want to continue support of our devices for a long time and this is definitly easier on 3.10.
I know that sony will keep msm8974 as long as possible in the open device programm but it will end in some time because qcom discontinued the ardeno support which make it harder for all of us. I will give my best to bring msm8974 on 3.10 stable as a rock and hopefully with cam
So keep it up and help to fix the things
If you need some help or some more infos you can write me via pm or hangouts
Click to expand...
Click to collapse
Hi
thanks for your reply. First, excuse me if i miss some point or if i'm not accurate: im new to this world. I learn cm with my z3, running my first 'mka bacon', around 1 year ago. I read a lot (xda, aosp doc, an listen the experimented devs). I agree with you that running a 3.4 kernel on aosp will be hard as it need a lot of changes but, for cm, switching to caf HAL variant need only a few variables changes. Now i am able to boot cm-13.0 and cm-14.0 on z3 without changing the build tree and this cm-13.0 is now used at daily usage.
Obliviously it doesn't change anything to camera facts.
About the 3.10 kernel, the officials cm maintainers insists a lot that i work with it but after we got a "won't fix" on the screen flickering issue it reveal the problem was a panel driver init missing, i try to fix but it is out of my knowledge, so i decide to drop the 3.10 kernel definitively as it will remain unusable for z3/z3c.
I totally get the idea of only one kernel for all devices and really agree with that. If, one day, this screen flickering issue get fixed, i will be glad to give another try and will contribute as much as i can. But for now users have an upgraded rom, almost working, with recent security patches.
About the camera, i doubt it is related to TA partition.
I just made a test with:
z3 stock .575 locked bootloader
z3 stock .200 unlocked bootloader
z3 cm-12.1
Camera on both stock z3 are working the same way.
I need to make the same test with both stock device on the same rom version now.
munjeni said:
I don't know which device you have but I speak about Honami and Amami only. On Honami and Amami unlocking bootloader have nothing to do with camera, only some small changes in picture quality
Click to expand...
Click to collapse
Drm verity are not the same as drm keys the keys are needed to get some Algorithmen to work. So this explains your lose of qualiy but drm verity is a protection to protect data and libs. On stock you have a implimenation that verfiy the loading of the carefull data and drm will be okay but these implimenation is closed source and needs to be e rewritten and this is nearly impossible because no other devices has this in a so extremly way then the sony devices
You can look into hammerhead source and you see some commits about drm verity too but hammerheads cam libs are not included in the verity
I have castor and sirius
---------- Post added at 10:00 PM ---------- Previous post was at 09:55 PM ----------
nailyk said:
Hi
thanks for your reply. First, excuse me if i miss some point or if i'm not accurate: im new to this world. I learn cm with my z3, running my first 'mka bacon', around 1 year ago. I read a lot (xda, aosp doc, an listen the experimented devs). I agree with you that running a 3.4 kernel on aosp will be hard as it need a lot of changes but, for cm, switching to caf HAL variant need only a few variables changes. Now i am able to boot cm-13.0 and cm-14.0 on z3 without changing the build tree and this cm-13.0 is now used at daily usage.
Obliviously it doesn't change anything to camera facts.
About the 3.10 kernel, the officials cm maintainers insists a lot that i work with it but after we got a "won't fix" on the screen flickering issue it reveal the problem was a panel driver init missing, i try to fix but it is out of my knowledge, so i decide to drop the 3.10 kernel definitively as it will remain unusable for z3/z3c.
I totally get the idea of only one kernel for all devices and really agree with that. If, one day, this screen flickering issue get fixed, i will be glad to give another try and will contribute as much as i can. But for now users have an upgraded rom, almost working, with recent security patches.
About the camera, i doubt it is related to TA partition.
I just made a test with:
z3 stock .575 locked bootloader
z3 stock .200 unlocked bootloader
z3 cm-12.1
Camera on both stock z3 are working the same way.
I need to make the same test with both stock device on the same rom version now.
Click to expand...
Click to collapse
Hey yes i was only talking about stock not about thr cm kernel
When did you test 3.10 the last time all display issues are normally solved if you use 1.3.3 kernel base
rcstar6696 said:
Drm verity are not the same as drm keys the keys are needed to get some Algorithmen to work. So this explains your lose of qualiy but drm verity is a protection to protect data and libs. On stock you have a implimenation that verfiy the loading of the carefull data and drm will be okay but these implimenation is closed source and needs to be e rewritten and this is nearly impossible because no other devices has this in a so extremly way then the sony devices
Click to expand...
Click to collapse
Where you found that info? Any log about it?
munjeni said:
Where you found that info? Any log about it?
Click to expand...
Click to collapse
Ask alin Jerpelea or chirayu deasi all infos i give too you are from them
For drm verity just use google :/
nailyk said:
screen flickering issue[/URL] it reveal the problem was a panel driver init missing, i try to fix but it is out of my knowledge
Click to expand...
Click to collapse
I'm oticed frezings and some strange things using that msm8994 display hal, but on my buld I have used codeaurora LA.BR.1.3.6_rb1.3 branch for display, camera and some things in media, I can confirm that display things fly, its soo smoth, video soo smooth, screen power off/on smooth... if you want to try here is it http://munjeni.myiphost.com/mynougat.tar.gz , don't forget to build kernel with script buildkernel.sh since it will install kernel headers from 1.3.3 and will build 1.3.3. kernel too. I have told jerpelea about it but no reaply about LA.BR.1.3.6
rcstar6696 said:
Hey yes i was only talking about stock not about thr cm kernel
When did you test 3.10 the last time all display issues are normally solved if you use 1.3.3 kernel base
Click to expand...
Click to collapse
Really? My last try was with the LA.BF64.1.2.2_rb4.7 branch. Great i have some waiting patches for fm and nfc! Unfortunately i half broke my original screen which make screen flickering debugging harder. I will give a try asap. Thanks for the hint!
nailyk said:
Really? My last try was with the LA.BF64.1.2.2_rb4.7 branch. Great i have some waiting patches for fm and nfc! Unfortunately i half broke my original screen which make screen flickering debugging harder. I will give a try asap. Thanks for the hint!
Click to expand...
Click to collapse
Just use nougat and everything from sonyxperiadev instruction page, its kernel 1.3.3 which is very good, extract things from mynougat.rar to android tree, build kernel with script buildkernel.sh (you will need some path modification to it), and the rest like mentioned...