Visualizzazione stampabile
-
Unfortunately, i cannot get it to work. I had already copied all those files, even updated the vendor makefile to include them(some new files like libFNVfbEngineHAL.so) and recompiled the rom, no dice. Still not able to connect to camera. Logcat says something about unable to get camera vendor metadata. Baseband and other blobs work fine. Thanks for helping, I'll just have to wait for your release i guess. How is the camera quality with the new blobs?
-
Quote:
Originariamente inviato da
pchatzop
Unfortunately, i cannot get it to work. I had already copied all those files, even updated the vendor makefile to include them(some new files like libFNVfbEngineHAL.so) and recompiled the rom, no dice. Still not able to connect to camera. Logcat says something about unable to get camera vendor metadata. Baseband and other blobs work fine. Thanks for helping, I'll just have to wait for your release i guess. How is the camera quality with the new blobs?
strange, in cm13 I only done this
I also have ported the new nubia camera app (NubiaCamera_6.0_V6.0.0.85.2)
for the quality I really don't know (maybe yes, a little improvement)....I never use the camera lol
-
Maybe its a mistake somewhere in my part, and im kinda busy now to try and find it :) . I will use your fixed sources once you get it in github.
I was mostly trying to get a unified kernel source for z7 mini and max, think i got it going,just need my friend with the mini to test it on. Will get it up soon, feel free to use whatever part you like since i manually updated it to 3.4.113(pretty boring task!).
-
Quote:
Originariamente inviato da
pchatzop
Maybe its a mistake somewhere in my part, and im kinda busy now to try and find it :) . I will use your fixed sources once you get it in github.
I was mostly trying to get a unified kernel source for z7 mini and max, think i got it going,just need my friend with the mini to test it on. Will get it up soon, feel free to use whatever part you like since i manually updated it to 3.4.113(pretty boring task!).
I have updated my github (cm13.0 branch) with the new 3.89 camera blobs, I also updated the adreno and drm blobs with the bacon version and the kernel with few security patch
now I'm waiting for the november security patch before release the V15 rom zip.
-
Thank you very much paolo, this worked perfectly. Merged all the changes successfully and camera works like a charm. Hope to see the new ported nubia camera apk soon! Just a little observation, i found that antutu performance is a little bit lower(about 56-57000) with the new changes, when it was about 59-60000 before. Could it be because of the OPO graphics blobs? it could also be the memory fixes in the linux kernel, because i think i got a lower RAM score than before(7700 when i got about 9500 before).
-
release V15 in first page
in the changelog there also is the link for the new nubia camera app
-
Quote:
Originariamente inviato da
PaoloW8
strange, in cm13 I only done this
I also have ported the new nubia camera app (NubiaCamera_6.0_V6.0.0.85.2)
for the quality I really don't know (maybe yes, a little improvement)....I never use the camera lol
Can you adopt new camera for CM12?
-
Quote:
Originariamente inviato da
brooklyn2006
Can you adopt new camera for CM12?
you talk about the apk ?
maybe yes but I don't know if works with the old camera blobs
I'm thinking to release a new version of the cm12.1 with the new blobs and the source codes updated but I need some time to patch the kernel with the all security patch released in the last few months.
tomorrow I will start to work on it :)
-
yes, I talk about apk.
I tried to do the adaptation himself, but the front camera does not work. Back camera work fine.
-
Quote:
Originariamente inviato da
brooklyn2006
yes, I talk about apk.
I tried to do the adaptation himself, but the front camera does not work. Back camera work fine.
you use my cm12.1 or compiled by you/other ?
I have ported the new apk and I tried with my cm12.1 and the front camera works
you can find the apk for the cm12.1 here in the cm12.1 folder
-
Thank you Paolo for your great work! Have you noticed V15 does not work with Xposed? I saw someone reporting the same issue on another forum: boot animation stuck forever after any Xposed module is installed.
-
Quote:
Originariamente inviato da
expzte
Thank you Paolo for your great work! Have you noticed V15 does not work with Xposed? I saw someone reporting the same issue on another forum: boot animation stuck forever after any Xposed module is installed.
I stopped using Xposed long time ago :)
on xda I saw the same issue reported on nexus 6 and xiaomi mi5 so maybe the current Xposed version is not full compatible with the android 6.0.1 November patch....just wait a new version :D
-
Quote:
Originariamente inviato da
PaoloW8
you use my cm12.1 or compiled by you/other ?
I have ported the new apk and I tried with my cm12.1 and the front camera works
The same problem - after switch to fron camera FC.
I use my build, compiled on your config files, without any changes.
-
Quote:
Originariamente inviato da
brooklyn2006
The same problem - after switch to fron camera FC.
I use my build, compiled on your config files, without any changes.
I'm using the new 3.89 blobs and works
right now I have updated my github so try to sync and recompile
-
Quote:
Originariamente inviato da
PaoloW8
I stopped using Xposed long time ago :)
on I saw the same issue reported on nexus 6 and xiaomi mi5 so maybe the current Xposed version is not full compatible with the android 6.0.1 November patch....just wait a new version :D
Interesting:D I'm not an expert but I thought experts like Xposed. Would you like to share how you control app permission and wakeups between apps? I use Xprivacy and PreventRunning. Xprivacy is much better than the stock permission control. E.g. a fake location is provided to the app if you don't allow the app to access your location. And PreventRunning seems much easier and more effective than Greenify. Thanks.
-
-
Quote:
Originariamente inviato da
pchatzop
done and it seems to works :)
just download the little zip fix that I made and flash it without any wipe
CM13.0_relV15_xposedfix.zip
-
Quote:
Originariamente inviato da
PaoloW8
I'm using the new 3.89 blobs and works
right now I have updated my github so try to sync and recompile
With 3.89 blobs new camera work fine on CM12.1
-
Quote:
Originariamente inviato da
brooklyn2006
With 3.89 blobs new camera work fine on CM12.1
ehehe nice :)
-
Everything working much better in your new sources, thank you. After 3 months(since i used the OPO kernel sources for bluetooth) i got stuttering on bt playback again. It was an isolated incident and everything worked fine after a reboot, for more than 2 hours of playback(if i had to count, it happened once in a total of 30 hours of music playback). A took a look at the logcat while playing, and got an error about qcmediaplayer(music played fine, it just presented the error while changing tracks), and i remember that you commented it out in your rel v14 sources. Could it have some relevance to the issue?
-
Quote:
Originariamente inviato da
pchatzop
Everything working much better in your new sources, thank you. After 3 months(since i used the OPO kernel sources for bluetooth) i got stuttering on bt playback again. It was an isolated incident and everything worked fine after a reboot, for more than 2 hours of playback(if i had to count, it happened once in a total of 30 hours of music playback). A took a look at the logcat while playing, and got an error about qcmediaplayer(music played fine, it just presented the error while changing tracks), and i remember that you commented it out in your rel v14 sources. Could it have some relevance to the issue?
I also use the OPO kernel bluetooth driver since relV13 but the bluetooth issue has never been solved, sometime it works sometime not (just as with Nubia kernel bluetooth driver)
-
I know, but sure we can agree that the opo driver and hci_qcomm_init blob got things much more stable. My question was more about qcmediaplayer, because i saw that error in logcat. It seems like the mediaprocess want to access it but we got it removed, so throws an error.
-
Quote:
Originariamente inviato da
pchatzop
I know, but sure we can agree that the opo driver and hci_qcomm_init blob got things much more stable. My question was more about qcmediaplayer, because i saw that error in logcat. It seems like the mediaprocess want to access it but we got it removed, so throws an error.
it is irrelevant
around on the internet I found to add this line to build.prop as possible fix:
codice:
ro.bluetooth.request.master=true
you have already tried ?
-
No way to test right now, but any possible fix is welcome :). Problem is that the bug is so rare now, i could think it is fixed but and could still be there sometimes. Think that i used a2dp for 3-4 hours a week, and it happened 1st time yesterday for me since september 9th. Qcmediaplayer is truly irrelevant with bluetooth, error shows up even in normal music playing. Could you explain to me what it means? Still trying to learn about this proprietary qcmediaplayer process :) .
-
Quote:
Originariamente inviato da
pchatzop
No way to test right now, but any possible fix is welcome :). Problem is that the bug is so rare now, i could think it is fixed but and could still be there sometimes. Think that i used a2dp for 3-4 hours a week, and it happened 1st time yesterday for me since september 9th. Qcmediaplayer is truly irrelevant with bluetooth, error shows up even in normal music playing. Could you explain to me what it means? Still trying to learn about this proprietary qcmediaplayer process :) .
I don't know exactly what qcmediaplayer is (maybe QualComm mediaplayer) but I saw that in cm14.1 has been completely removed from the source code and that in many cm13.0 device tree was removed months ago so is no longer needed :)
now I'm doing some test with the build.prop line added
-
Thought so as well, and i see that in the past lots of people have that showed up that error in their logcats when they could not play online videos with sound. Maybe Cyanogen replaced this proprietary service with the CMAudioService i saw since september. Maybe it has to do with redirecting audio streams to the hexagon dsp so they could be decoded, and the CM devs found a non-proprietary way to do this.
Hope the a2dp test goes well!
-
Quote:
Originariamente inviato da
pchatzop
Hope the a2dp test goes well!
no...same issue :(
-
Hi paolo, thank you very much for keeping the development!! Can't wait for the Theme Engine on CM14! BTW, can you help me encrypt this device? Already used resize2fs for the free space for the crypto footer but still says "No master key, so not ext4enc" and "Bad magic for real block device /dev/block/platform/msm_sdcc.1/by-name/userdata" and "Not a valid ext4 superblock", help plz I can't leave home without cryptfs here :(
-
Quote:
Originariamente inviato da
Caikki
Hi paolo, thank you very much for keeping the development!! Can't wait for the Theme Engine on CM14! BTW, can you help me encrypt this device? Already used resize2fs for the free space for the crypto footer but still says "No master key, so not ext4enc" and "Bad magic for real block device /dev/block/platform/msm_sdcc.1/by-name/userdata" and "Not a valid ext4 superblock", help plz I can't leave home without cryptfs here :(
I really never tried to encrypt the device and I don't know how it works.
I'll probably have make some changes to make it work on cm13 and cm14
I'm looking info on internet
-
I already added every needed crypto driver in my kernel fork for crypto from OPO kernel, it was required to get f2fs support. It could be an fstab issue, i will take a look. Sorry Caikki that i couldn't respond in xda, but i was busy trying to port cm to nx506j(only audio left to fix, damn tfa9890 audio amp) , and looking at the bluetooth issue.
Speaking of which, i replaced bin/btnvtool with the one from bacon blobs, and i am spending the last hour and a half trying to cause the a2dp bug(i have the phone connected to my computer via a2dp). No luck yet. I disconnected the computer side, the phone side, with wifi open, with data, no dice. The damn thing keeps working correctly. Logcat does not show anything abnormal. Link takes a while to close(about 10 secs) if i forcefully close bluetooth on the computer side, but shuts down correctly and music pauses on phone side. Maybe its worth a shot, try it yourself paolo, since i wasnt getting the bluetooth bug a lot to begin with(maybe my devices play well with the buggy driver :) ). Just replace the btnvtool blob with the one from bacon.
-
Update!
Hey guys, thanks again, just to let you updated:
Paolo's CM13 beta7 CAN ENCRYPT nx505j just requiring: secure lockscreen (Pattern, PIN or Password) and resizing on TWRP dev/block/mmcblk0p23 to 6896000 blocks (ext4) for the crypto footer.
It can't decrypt data after rebooting manually BUT:
Pchatzop' Ressurection Remix CAN DECRYPT encrypted storage (Maybe CM13 V15 also?), I could change my password many times after and it is still working!! weird right?
Anyway, I already have my device encrypted and set the way I always wanted. You don't need to fix encryption if you don't want because as you can see no one encrypts their phone anyway...
Just that Pchatzop's TWRP can't find crypto footer and Paolo's TWRP finds the footer and offers Pattern/PIN/Password input, but it's unable to decrypt with either one. :( I wish I knew how to code... Hope you can try to build at least a TWRP please, I will test it anytime!
Thanks in advance for any return guys.
-
Well, you would not put it down until you nailed it! Here is my take on a twrp: https://mega.nz/#!R5hEAA4J!HddfIVvh3...pLmUYHn_Hw5Al8 . Im sure it is an fstab issue now, since my kernel decrypts encrypted storage fine. I will build an updated kernel later to try solving everything correctly. Thank you for your tests!
-
Here is a folder with all my test files for encryption. The first test twrp is bugged for f2fs, i build a new one(twrptest2) that works. I also included a kernel with some fstab changes, boots fine on my unencrypted phone, to solve the problem of needing cm13 beta7 to encrypt in the first place. If you do the necessary tests(maybe resize2fs works now, i included the crypto footer length in the twrp fstab) maybe we can have a properly working encryption without crazy workarounds :). Maybe i'll encrypt my phone too if the performance hit is not too big. Link: https://mega.nz/#F!ZxQBhLqK!1FKSAPtaZtxx28XLDA8PNw
-
Quote:
Originariamente inviato da
pchatzop
Here is a folder with all my test files for encryption. The first test twrp is bugged for f2fs, i build a new one(twrptest2) that works. I also included a kernel with some fstab changes, boots fine on my unencrypted phone, to solve the problem of needing cm13 beta7 to encrypt in the first place. If you do the necessary tests(maybe resize2fs works now, i included the crypto footer length in the twrp fstab) maybe we can have a properly working encryption without crazy workarounds :). Maybe i'll encrypt my phone too if the performance hit is not too big.
Hello there, thanks a lot!
TWRPTEST2
f2fs:
- OK format with correct crypto footer space!!
- UNKNOWN decrypt storage as I couldn't encrypt f2fs yet
ext4
- OK format and resize set four 4k blocks for the footer space!
- NOK encrypted with CM13 beta7 and couldn't decrypt yet
Ressurection Remix ROM:
f2fs
- flashed via TWRP boot.img kernel and it seems better I think, encryption process is now currently a hit or miss, sometimes it runs, most times do not (I'M ALMOST SURE ROOT ACCESS MUST BE DISABLED FOR APPS, yeah, with disabled root, encryption commands are always being called in logcat with either Default/swipe, PIN, Password or Pattern)
- when encryption runs successfully, this screen always comes after (although data stills fine and accessible after a simple reboot)
[IMG]i67.tinypic.com/142y637.jpg[/IMG]
ext4
- same as above
-
I build a new twrp adding many changes from the zuk z1 twrp tree for decryption, currently using zuk blobs to do it but i can replace the with nubia blobs if that fails. Also added a new test kernel with some fstab changes(removing encryption on userdata on sdcard, that may have caused a lot of problems). Both boot and work fine on my unecrypted phone(i spend about 3 hours trying to encrypt last night, gave up and restored everything). They are up in the folder.
-
Quote:
Originariamente inviato da
pchatzop
I build a new twrp adding many changes from the zuk z1 twrp tree for decryption, currently using zuk blobs to do it but i can replace the with nubia blobs if that fails. Also added a new test kernel with some fstab changes(removing encryption on userdata on sdcard, that may have caused a lot of problems). Both boot and work fine on my unecrypted phone(i spend about 3 hours trying to encrypt last night, gave up and restored everything). They are up in the folder.
Nope, this twrp doesnt format or resize correctly for the crypto footer nor decrypt it :(
Kernel doesn't encrypt on first try, just using terminal
Thanks again
-
link relV16 in first page
-
Hi everybody.
I'm a french user of Z7max since 2 years. My Z7Max always work as needed with 1.64 bb72. But from a few weeks, I decide ton install CM13 on my device.
After downloading CM13 V15 + TWRP then install custom recovery and flash my rom with this image, my phone is fine.
But I have an issue... I don't see the notice "Only for merge partitions" and so my device has only 2.46Gb usable on internal storage and loose about 26Gb !
So I investigate (and I see the notice :( ). I install Tigreos tools, adb. So I see that I have a partition named "grow" (26Gb)
imgur.com/S395twQ
I use the App Storage space to see all partitions details too and I have a partition mmcblk0p23, not mounted, size : 23.87Gb.
So how can I get back my 26Gb (or 24) in my phone? I tried to return on android L (1.64bb72 but I can't find all roms to upgrade after, all links are dead).
Thank you !
-
I am dealing with call echo issue for a long time.
Anyone face the same issue?
While phone call, I hear the other side very clear and well, but they most say my phone have big echo and make them noway to talk with me.
-
release V17 (first with LineageOS name) and changelog in first page