yashsingh1/xdaforums huggingface dataset:
[Xperia Z3 Original Android Development] nailyk:
Sorry, i will answer you here.

That is exactly what i would to know! Thanks a lot! Yes, it is used by the blob (closed source) and by the HAL partially open. So the new 1.3.3 blobs (3.10) will never ever work on 3.4 kernel and remain the only one we can get officially.

You are right on lots of points! But as you said earlier, we (almost) don't have blobs source code so we depend on qcom and sony for that. For this reason we need to follow their guide line. Except if we find someone able to rewrite a full driver + hal for the camera.

Found where the screen flickering came from!

nailyk@rimmon2 :) % find msm/drivers/video/msm -iname "*.c" | wc -l ~/cyanogen/13.0/kernel/sony
90
nailyk@rimmon2 :) % find msm8974/drivers/video/msm -iname "*.c" | wc -l ~/cyanogen/13.0/kernel/sony
209

lol.... Only generic drivers present, and especially drivers/video/msm/mipi_novatek.c for the original lcd in almost all of our devices is missing.

But between 3.4 and 3.10 kernel the memory allocation had changed (@3.8?), so every drivers need a full rewrite. I have not enough time to do that. Another rm -rf day!

Nothing related but can be funny: while trying to 'port' the old lcd driver i found a guy which is writing an opensource adreno driver (freedreno). If we can use it, it will remove 4 or 5 blobs from the list ;)
[Xperia Z3 Original Android Development] drakonizer:
Since [MENTION=4675360]tomascus[/MENTION] has got a 3.4 kernel up and running (and also stable, from his report) the only issue seems to be the camera. As far as I know, the reason why camera doesn't work is because of the lack of new blobs. The latest stock ones are drm protected. But, since chirayudesai said that they had once gotten newer blobs to work on cm13.0 during the initial stages of development, this leads me to believe, that there might be a set of blobs (for any msm8974 device) that were part of any update (stock) and weren't drm protected for some reason. This is , of course, just a theory, and might not be valid at all. Still, I believe this could be a possible solution for camera.

I agree that 3.10 is the popular option, but the issue is, the blobs need to be constantly updated for improvement in camera quality. In other words, we're heavily dependent on closed-source parts (or we'll have to modify the HAL accordingly). Considering Google dropped support for msm8974 in AOSP Nougat, it's only a matter of time before Sony does it too. Which is why I believe, since we've come this far, investing time in the 3.4 kernel is a better option.

I also heard there are plans to switch to a 3.18 kernel soon. Which means it's almost certain that msm8974 will probably be dropped, even before we get a stable 3.10 kernel (yuga was dropped when they switched from 1.2.2 to 1.3.3).
[Xperia Z3 Original Android Development] nailyk:
I totally agree with you! And as you mention him, the maintainer which i am in touch with is chirayudesai ;) Convince him to switch to 3.4! My opinion is our best chance, for all, is an msm8974 unified sony/hammerhead. Those devices are (almost) the same! And don't forget there is qcom leaked keys and camera blobs on the net :p Anyhow i am not the decision maker...

( I'm wondering if it is not a 4.4 kernel switch... )
[Xperia Z3 Original Android Development] drakonizer:
I agree, but I don't think qcom blobs are going to help with our camera (which uses sony blobs). A unified hammerhead/sony kernel or device tree would be great, but no one's gonna start from scratch again after so much effort has been put into the 3.10 kernel, especially the big devs. CM has also completely switched their device trees to match the sonyxperiadev ones.

What I meant was, while CM goes their way in trying to make the 3.10 kernel stable, it's worth a shot to see if we can get the 3.4 kernel working. If we do, then there will be no stronger argument to switch to it.
[Xperia Z3 Original Android Development] nailyk:
Maybe. I start digging and seems our sensor is a sony imx220 and the most recent is those repo is imx214. The most important part on those repo is they are kitkat so stuck at HAL2.

I'm not sure. All sony xperia Zxx are deserted by cm since they use the 3.10 kernel. The only active maintainer is AdrianDC and work on SP and M (and he will get cm-14 on it!!). The other one, for xperia, is Chirayu Desai and he have no time anymore. Maybe starting a 'fresh' kernel from hammerhead will not be a big deal?

Be out of sync with cm sounds like a good idea but it is far from my original plan. My original plan was to work with the cm maintainers... Especially since there is no more real maintain of our devices on cm...

Since i use open source i reproach the fact that everyone work on his own and not together. So making another cm-but-not-quite-num84753945 doesn't sounds great for me. Obviously we need a part of unofficial to progress before the gerrit request, but that is all. I need to think more about it.

(I hope i express myself in a right way. It is not easy for me to express this kind of concept in English so please, pardon my clumsy)

P.S.: sorry drakonizer i can't thanks your post no more.

P.S.2: weird! on the imx220 product description: 'CSI-2 serial data output (MIPI-4Lane)' and i mipi is also in the lcd panel name (mipi_novatek_cmd_qhd_pt.c). Need to go further on that...
[Xperia Z3 Original Android Development] tomascus:
Yes, there's only half the files because they implemented a single display driver for all displays https://github.com/sonyxperiadev/ke....3.3_rb2.14/drivers/video/msm/mdss/somc_panel

And yes, but do you think camera will ever function properly? Who knows... So I thought we were trying to just revert the bits where they switched over to the new kernel and new camera HAL implementation
[Xperia Z3 Original Android Development] drakonizer:
If we don't have any more cm maintainers, then how do you plan on working with them? Anyway, it's up to you of course.

Also, I wanted to know, does the concept or the n preview kernel have drivers and files for other boards, like rhine? I ask this, because I recently found out that the GPE Kernel for the Z ultra had support for other rhine devices too.

And, did anyone try using the N preview blobs to get the camera working? Maybe Sony hasn't DRMified the N preview ones.

I think getting the camera to work would involve only finding the latest possible DRM-less blobs and then rewriting the HAL with minimum possible changes to get it to work. Looking at the camera wrappers for other msm8974 devices would be a good place to start.
[Xperia Z3 Original Android Development] tomascus:
No it doesn't, just the basic msm8974 dtsi files - no honami panel or any other rhine one.

But other than not having these files, the kernel is basically CAF 1.1.1 (Rhine) vs CAF 1.1.3 (msm8974pro updated) which are identical, except 1.1.1 is out of date of course
[Xperia Z3 Original Android Development] nailyk:
Not totally up to me. If i wanna work alone i will not spend time maintaining xda thread, asking freenode admin for channel, giving write access to my github account, etc... For me in 'open-source' the collaborative part is the most important. I'm currently looking how survey works on xda to request your opinion.

Sure but according to the panel documentation it need some special function, specially on init functions and frequency changes which are not offered by the common driver in 3.10

After discussing a lot with tomascus on #xperia-dev we both agree that msm8974 is an abandoned device. We look on multiple repo and aosp had drop it around 6 month ago and sonyxperiadev took the same path.

I wont misrepresent what he said so i will only talk for me: i think customs rom is our best option as we never be able to push to aosp. Plus cm-14 start to be a thing.

He heavily upgrade the kernel to include a lot of security patches. Build and run really fine on cm-12.1 for around 1 hours now on my both z3.

So i guess there is no other way now: the kernel for this cm will be this one :)

Fell free to ask for write access or send PR!

P.S.: webchat for #freexperia.
[Xperia Z3 Original Android Development] drakonizer:
That's great. I see it's a fork of the old cm 3.4 kernel. Which means it's common for all sony msm8974, and will work for my rhine device. I hope to help you guys out as much as I can. Good luck!
[Xperia Z3 Original Android Development] nailyk:
You are right, i forgot that: the idea is a (sony xperia) msm8974 kernel. Send me a xda pm or on irc with your xda nick and i give you write access.
[Xperia Z3 Original Android Development] ILikeBubbles:
I've been running the cm13 you uploaded on the 8th... Do you think the one you uploaded today (20th) will be stable enough to upgrade to? Lack of camera is more a minor annoyance but I don't think I have the patience for screen flicker haha
[Xperia Z3 Original Android Development] nailyk:
New release

2016-09-20 release

Big kernel upgrade, thanks to [MENTION=4675360]tomascus[/MENTION].

Seems working fine but i can't upload.... Nothing respond on androifilehost webpage :(
[Xperia Z3 Original Android Development] nailyk:
The sept 20 release will not have screen flickering issues as it is based on 3.4 kernel :)

But as the kernel as been upgraded a lot (dunno, around 80 patches) maybe new issues are presents. I just figure out the bluetooth is not working.

Also if someone (like me) had non working touchscreen (white spot acting like a mouse) here is the workaround:

adb root
adb shell mount -o remount,rw /system
adb shell cp /system/usr/idc/qwerty.idc /system/usr/idc/clearpad.idc

btw still not uploaded :rolleyes:
[Xperia Z3 Original Android Development] drakonizer:
Did you need to modify the device tree to get it to build or did you use the tree from CyanogenMod (which is in fact, based on the sonyxperiadev one)?

And what blobs did you use? Muppets or Xperiadev? If muppets, then which branch?

Sorry for all the questions, I just want less time wasted on figuring out these minor stuff.
[Xperia Z3 Original Android Development] ILikeBubbles:
Ok thank you for the update! Sadly Bluetooth is pretty important to me.. I'm just addicted to updating... I'll stick with the one from the 8th for now! Thank you for your consistent updates and quick responses!!
[Xperia Z3 Original Android Development] nailyk:
Yes device tree had a lot of modifications. Iirc i post the manifest in the op. It is a good starting point.

CyanogenMod device tree really deviate from sonyxperiadev. If you wanna just make a q&d try you need to bypass the build/core/qcom_tarket.mk (from my bad memory) and the best way for that is, iirc, unset TARGET_USE_QCOM_HARDWARE.

Also the 3.4 kernel use another HAL variant, so you need to unset BF64_VARIANT (something like that).

Sorry for this quick answer but i get back at work tomorrow and it is 22h30 :silly:

Edit:

z3.diff i'm upgrading the z3 from almost a year now so parsing my commit will be hard. This patch is basically a diff between the cm-13.0_crypto branch (kernel 3.10 used to build twrp with crypto support) and cm-13.0_3.4 branch. You will find everything you need inside.

shinano-common: https://github.com/nailyk-fr/androi...mmit/b82f537dc6427a2b40ad09de7047b95ac7991398

msm8974-common: https://github.com/nailyk-fr/androi...mmit/3cebcadf19d819d4b28109f30326e00c911d9c00 don't care about audio/* for now. Warning! Adriandc push a lot of changes in the init process. Being out of sync with it break every boot.

Again sorry for the quick answer but i really need to switch off.

if you give me some time i can propagate my change to my honami&amami forks to give a try, they just need to be sync with cm repo before.

^ [MENTION=5258151]drakonizer[/MENTION]
[Xperia Z3 Original Android Development] drakonizer:
Thank you! I'll be doing it myself over the weekend at least, but there's a lot to look at. I'd appreciate any help you can give me.
[Xperia Z3 Original Android Development] nailyk:
The 20 sept release finally uploaded! Seems androidfilehost gets a ddos :s

The same kernel works fine on the cm12.1 realease (bluetooth included). Also I forgot putting my antenna back into the device, maybe is-it related :o If you have time, take a backup of your old rom, give a try and report me back :D

Yes, really sorry but it was hard to resume one year of work into a single message ;)

I'm only on irc at the moment but i get asked for other communication solutions so i'm studying the question (obviously no google, and mostly prefer opensource solutions, client *and* server)

So feel free to join and ask, or you can also pm me on xda your email, and i will help you as much as i can.
[Xperia Z3 Original Android Development] ILikeBubbles:
Ok I just tried both a clean and dirty flash of the rom from the 20th. There were 2 uploads though did I get the right one? One of them already had a download. I picked that one.

Anyway, I had a cursor to control and I didn't have a sim, that's all I found because I restored after that.
[Xperia Z3 Original Android Development] tomascus:
No logcat ? No dmesg? Nothing that could help us? Im guessing he forgot to add modem but I can't tell without logs
[Xperia Z3 Original Android Development] ILikeBubbles:
Ok well I'm new at testing this. What's a dmseg? And how do I get a logicat again? I just got fastboot drivers on my laptop.. I'll try again when I get home though.
[Xperia Z3 Original Android Development] nailyk:
2016-09-21 release

New release

I forget to switch back to the old blobs repo. This release sounds better.

But i don't know if the 3D acceleration is present. Also the device don't go over 50°C so i'm wondering if the 1,5GHz limit for twrp wasn't included in cm...

Bluetooth is fine. I was able to play songs through a2dp.

Also i will edit the OP soon to include a log part.

P.S.: satstat also show gsm cells, like in post#2

P.S.2: androidfilehost is still under maintenance so i temporary create a dropbox account. I don't know how reliable it is so please check md5/sha
[Xperia Z3 Original Android Development] ILikeBubbles:
Just finished setting up the rom from the 21st.. it works perfectly!! Thank you so much for all your hard work!!

Edit: I've got a question... The wifi on my z3 drops constantly... No matter what rom I have. Is there something I can do about it? I've read it's some kind or hardware problem or something but how does that work?
[Xperia Z3 Original Android Development] Cirra92:
Latest Paranoid Android for z3c has working camera on 3.10 kernel with 1.2.2 blobs, as reported. You might want to check PA repos, maybe it can help.
[Xperia Z3 Original Android Development] tomascus:
Yes, but 1.2.2 kernel branch apparently has iommu issue which causes crashing. I gotta look more into it
[Xperia Z3 Original Android Development] nailyk:
There is a more secure setup on cm for wifi than others rom: if you get out of range, wifi drop and will not reconnect until you unlock the device agin. It is a normal security feature. I can point you to a video link explaining why it is an important security feature. (in 2/3 words, portable wifi scan, fake your know wifi, on fly create open wifi with your known SSID, MitM).

Can it be that?

Not related: Does someone with the 2016-09-21 with playstore can test some security tests? I try with android vts but it is no more up-to-date.

Thanks in advance.
[Xperia Z3 Original Android Development] ILikeBubbles:
Hey I'm more than happy to do any tests you need!
[Xperia Z3 Original Android Development] nailyk:
Thanks but i can't recommend you app on play store as i don't know the catalog. I usually test with android VTS but there is no release since december.

Maybe someone else will recommend you a good vulnerability tester.
[Xperia Z3 Original Android Development] blackhawk_LA:
Do you know about mokee roms? They're a Chinese open source project, mainly based on cm if I'm not wrong. They had a pretty nice 5.1 rom for our Z3, and now download page is blank. Maybe they are working on MM too? Maybe the devs could try to get in touch with them. http://download.mokeedev.com/?device=z3
[Xperia Z3 Original Android Development] nailyk:
Hi,

i try to reread all the topic and hit the multiquote on all the post i left aside until know, i hope i don't miss too much:

Someone also ask for dual sim variant. Devices are quite the same and we now have a z3c test build. We will see what it is possible to do but in every case it is planned (for all shinano-based, btw i need testers for z2 :) on the irc chan)

Wifi hotspot should be solved on the next release.

I finally add a log part but need to add some android apps.
[Xperia Z3 Original Android Development] nailyk:
2016-10-03 release

* new release *

Wifi cause me a lot of trouble but finally get it working! I forget the screenshot of AP at home but it turn on and load the right fw so i guess it is working now.

z3c build also should now have a working wif. Only gps is reported as non working on z3c but i have no logs so i can't fix. And camera obviously still not working.

I will add NFC on the todo list.
[Xperia Z3 Original Android Development] josepmaria:
Thank you for your great work [MENTION=6979267]nailyk[/MENTION]

Gps working like a charm on Z3C.

NFC and camera not (obviously).
[Zenfone 5 General] ryanjms07:
[IMG="welcome"]https://img.xda-cdn.com/dLhQ36DzG0m-wf5Dxpxr6QhNqeY=/https%3A%2F%2Fimg.xda-cdn.com%2FEZ8nWdJtojZr9ZBOORpBpoSoyKw%3D%2Fhttp%253A%252F%252Fs22.postimg.org%252Falvwb8vb5%252FWelcome_To_My_Thread.png[/IMG]​

Today, i will show you how to increase size of system partition on our Zenfone.

before do this step, my phone using FW KitKat 54 with unlocked bootloader and rooted.

Just download this file, it includes clear instruction, adb/fastboot, auto installer universal adb driver.

Flash new ROM is important after you increase your system partition

FA :

it save to flash your phone into lillipop, kitkat, or jellybean

it is no damage your phone.

System Partition 2.3 GB.

MyZenfone Installed Lollipop with full Odexed:

[IMG="System partition increased"]https://s3.postimg.org/an9yo0f0z/Screenshot_2016_08_20_17_01_51.jpg[/IMG]

[IMG="thank you button"]https://img.xda-cdn.com/KyX19Z1Z_J4VuZo-T1hiXJVYs-U=/https%3A%2F%2Fimg.xda-cdn.com%2F8iyBXZYg0CAjyMoS0oNbNR3AHNk%3D%2Fhttp%253A%252F%252Fs29.postimg.org%252F4dkv3xvaf%252Fthank_you_button.gif[/IMG]​
[Zenfone 5 General] febry_valdy:
Nice tips
[Zenfone 5 General] x3kings:
how do we flash it in custom rom ?
[Zenfone 5 General] LuanHalaiko:
So what this actually do? It increase the internal memory using sd card? :B I din't understand
[Zenfone 5 General] tech_x:
Can you upload stock partition for lollipop ?

Phone not booting and i cant enter to recovery too.
[Zenfone 5 General] febry_valdy:
No, I think this tuts guide us to increase the system memory size using our internal storage.
[Zenfone 5 General] ryanjms07:
no, just reboot into fastboot mode, connect your phone, double click .bat file in your fastboot folder

it increase system partition and decrease size of data partition. it also usefull for zenfone 16/32gb internal storage.

what do you do? maybe you made a mistake.

i have tried it and succsess.

yes, you're right :good:
[Zenfone 5 General] LuanHalaiko:
Wow, I din't know that I would use this :laugh: , but this came helpfull when I was installing a heavy rom with 1gb of data
[Zenfone 5 General] guidoido004:
you should use cache partition instead and add some code to symlink cache to data so there wont be any issues with it.
[Zenfone 5 General] x3kings:
i cant find the adb and fastboot folder lol sorry
[Zenfone 5 General] LuanHalaiko:
[MENTION=4861119]ryanjms07[/MENTION] how do I get it back to normal?
[Zenfone 5 General] TechNova:
Try flashing the original partition.tbl file from asus lollipop raw fw.

---------- Post added at 10:07 AM ---------- Previous post was at 10:06 AM ----------

@ryanjms07

How did you odexed ur stock rom? Please tell me.
[Zenfone 5 General] ryanjms07:
auto odex: use lucky patcher (only app and priv-app)

manual odex: use command and file manager shich support root (app, framework, and priv-app)

after you odexing system app dont forget to remove classes.dex in apk file using rar.
[Zenfone 5 General] TechNova:
And how do i odex framework folder?
[Zenfone 5 General] Huikhor99:
Don't think it is on your phone's folder
[Zenfone 5 General] paktepu:
Nice tricks

Increase system, decrease data
[Zenfone 5 General] fabricioinsider:
Repartition.tbl genuine zenfone 5

how to reverse the repartition.tbl once placed the forum here?, I do not have the original :(
[Zenfone 5 General] paktepu:
I have that, check here

http://xdaforums.com/zenfone-5/help/zenfone-5-a500cg-zenfone-6-a600cg-t3354645
[Zenfone 5 General] titanonxda:
It's not working for me with custom rom also the result is same with stock Version TW-2.22.40.540(KK,MR11.3) rom via adb sideload. Could somebody please explain to me how to do it properly? I really wanna increase my system partition on zenfone 5. Thanks!
[Zenfone 5 General] paktepu:
Is it? Can you show the parrition size after doing repartition?
[Zenfone 5 General] titanonxda:
Finally! It's working for me with cm13.1 rom. Thank you so much sir :o :fingers-crossed: :good:
[Zenfone 5 General] febry_valdy:
Can I increase the /system space without losing my current ROM?
[Zenfone 5 General] fabricioinsider:
Could you do the opposite? Decrease partition size
[Zenfone 5 General] Streaamz:
help!

I was following the instruction exactly, but when i opened the "repartition to 2 gb" file, the cache was erased then my phone turned off by itself.

Is that normal? how will it affect the system partition? Thanks in advance

---------- Post added at 03:46 PM ---------- Previous post was at 03:19 PM ----------

aaaaakkhhhh now the stock kitkat recovery says E: failed to mount /cache (invalid argument)

and I see many lines of "E: failed to mount /cache (invalid argument)"! :eek: im freaking out hereee

:crying:
[Zenfone 5 General] BORETS24:
after expand system partition data partition is empty and can not mount. Is it possible expand system partition without wipe data?
[Zenfone 5 General] DogeLordTR:
TWRP shows that system is still 1.2gb but when I change file system turn it back to ext4, my system partition increases to 2.2gb. But when I flash rom, it decreases to 1.2gb again. And in the storage screen, android shows me that system is using 3,48GB (it should be about 2,48)
[ONE Q&A, Help & Troubleshooting] :
I can't seem to find what I need anywhere on these forums. I'm currently using a custom SlimLP ROM built from sultan's sources and camera hal. I know sultan made some modifications to the flash of the opo, making it much brighter than the default settings. I've tried flashing nearly all of the good recently updated MM ROMs, and they all contain CM camera HALs. When I try to use torch, the flash is almost half as bright as my daily driver ROM. This is a feature I'm not willing to give up.

If any of you know of a ROM that has the latest security patches, uses sultan's camera hal, supports f2fs, supports layers or substratum, is compatible with lightning kernel caf, and is compatible with xposed (I need this for signature spoofing with micro g) you would save my life. I hate being on an outdated ROM which has features that seem to be absent in every MM I've tried.
[G3 Q&A, Help & Troubleshooting] sayyro:
hello everyone, just wanted to inform you

yesterday i got the flicking&Fading issue on my LG G3 D850

and what causes this is the Overheating, while i was flashing a rom, it happened, also with my OLD LG G2 while i was flashing a rom it happened due the process, so do not overheat any LG phone it's a knows problem and this is what causes it, paper solution does not work for me unfortunately
[G3 Q&A, Help & Troubleshooting] tiguy99:
Which rom were you flashing?
[G3 Q&A, Help & Troubleshooting] sayyro:
euphoria 5.1.1 . + TK FULL GAPPS + furnace-d850-aosp-20150228 Kernel

all togther

while the phone is updating system apps was like 50 of 200 it got overheated due the process and got the flickring and i knew it because same thing happened to me when i was flashing in my OLD LG G2 and i remember flashing a kernel there also ..
[G3 Q&A, Help & Troubleshooting] Mashed_Potatoes:
next time put it in the freezer lol