Recently updated to build 137 on my BLA-L09, but now every time I take a picture and try open it in the gallery it constantly shows 'Loading...' with the actual picture dimmed out in the background.
Anyone facing the same issue?
Any solutions?
I also realised the picture doesn't actually save in the DCIM folder, however only the thumbnail saves in the DCIM>cache folder as a .tmp file.
wisemanwizz said:
Recently updated to build 137 on my BLA-L09, but now every time I take a picture and try open it in the gallery it constantly shows 'Loading...' with the actual picture dimmed out in the background.
Anyone facing the same issue?
Any solutions?
Click to expand...
Click to collapse
Are you using a custom kernel?
I am using the following custom kernel...
https://forum.xda-developers.com/mate-10/development/kernel-mate-10-mate-10-pro-stock-t3744501
wisemanwizz said:
Recently updated to build 137 on my BLA-L09, but now every time I take a picture and try open it in the gallery it constantly shows 'Loading...' with the actual picture dimmed out in the background.
Anyone facing the same issue?
Any solutions?
Click to expand...
Click to collapse
ante0 said:
Are you using a custom kernel?
Click to expand...
Click to collapse
wisemanwizz said:
I am using the following custom kernel...
https://forum.xda-developers.com/mate-10/development/kernel-mate-10-mate-10-pro-stock-t3744501
Click to expand...
Click to collapse
Mm. Huawei did something in B137. I will rebrand back to C432 and check later.
thanks man, i hope its fixable, it's actually quite annoying
ante0 said:
Mm. Huawei did something in B137. I will rebrand back to C432 and check later.
Click to expand...
Click to collapse
wisemanwizz said:
thanks man, i hope its fixable, it's actually quite annoying
Click to expand...
Click to collapse
Are you using B137 from 03-29 or 04-04?
It seems the latter is some test build, because it has the required files for Face Unlock (which probably is not enabled in Settings?).
I only did a diff so far on the 2 different B137 builds, but will have to flash to find out if it can be fixable.
I'm using the 04-04 version of the B137 update.
ante0 said:
Mm. Huawei did something in B137. I will rebrand back to C432 and check later.
Click to expand...
Click to collapse
ante0 said:
Are you using B137 from 03-29 or 04-04?
It seems the latter is some test build, because it has the required files for Face Unlock (which probably is not enabled in Settings?).
I only did a diff so far on the 2 different B137 builds, but will have to flash to find out if it can be fixable.
Click to expand...
Click to collapse
wisemanwizz said:
I'm using the 04-04 version of the B137 update.
Click to expand...
Click to collapse
I'm getting the same, one way to get camera back is simply to reflash but use B137 from 03.29. I have only had time to check what camera does briefly. It can't write to /sdcard/DCIM/ for some reason.
Face Unlock works btw, just need to set prop
ro.config.face_recognition=true
Can be done in build.prop or using a Magisk Module to set it at boot.
wisemanwizz said:
I'm using the 04-04 version of the B137 update.
Click to expand...
Click to collapse
It's fixed now. I will release a fix for this version in a couple of hours.
Huawei built kernel using different sources (V10 source it seems), where it uses a new/different vcodec for images.
I compared kernel configs from 4/4 B137 kernel to 3/29 B137 and it's different.
I first tried using the config from 4/4 but it wouldn't build with BLA source (Missing codec).
Then I checked 4/4 B137 config to Honor V10 sources config (It was a little different but codec was there), then built kernel and tested.
Wifi, BT and Camera works now.
That's great! Thank you so much! I look forward to testing it! :angel::angel::angel:
ante0 said:
It's fixed now. I will release a fix for this version in a couple of hours.
Huawei built kernel using different sources (V10 source it seems), where it uses a new/different vcodec for images.
I compared kernel configs from 4/4 B137 kernel to 3/29 B137 and it's different.
I first tried using the config from 4/4 but it wouldn't build with BLA source (Missing codec).
Then I checked 4/4 B137 config to Honor V10 sources config (It was a little different but codec was there), then built kernel and tested.
Wifi, BT and Camera works now.
Click to expand...
Click to collapse
wisemanwizz said:
That's great! Thank you so much! I look forward to testing it! :angel::angel::angel:
Click to expand...
Click to collapse
Here it is: https://mega.nz/#!ZD43wBxa!qPWTiOgcuafWUX1DzZd2RFVU-eZdSn71LFFlJR3Z7Ac
This will probably break camera on other builds (I've not tested).
If you want Face Unlock root is required, you can flash this Magisk module (if you use Magisk) https://mega.nz/#!5e4VSS4L!4vbZr0Pyzm39k2Ltcxi10gcFg_bcSlj7iLosK6SLKtM
Or add the prop manually to /product/etc/prop/local.prop
ro.config.face_recognition=true
The kernel works like a charm! Thanks!
For face unlock I tried to manually edit prop & then restart the phone, I am rooted but it is not working (I do not have Magisk) maybe I am doing something wrong.
Is there any specific place I have to put the "ro.config.face_recognition=true" within the prop file - i.e. should i just paste it right at the bottom of the prop file? And also where will the facial recognition option appear once it is enabled so I can confirm?
Sorry (I'm kind of a noob) I will probably try later. :angel::angel:
ante0 said:
Here it is: https://mega.nz/#!ZD43wBxa!qPWTiOgcuafWUX1DzZd2RFVU-eZdSn71LFFlJR3Z7Ac
This will probably break camera on other builds (I've not tested).
If you want Face Unlock root is required, you can flash this Magisk module (if you use Magisk) https://mega.nz/#!5e4VSS4L!4vbZr0Pyzm39k2Ltcxi10gcFg_bcSlj7iLosK6SLKtM
Or add the prop manually to /product/etc/prop/local.prop
ro.config.face_recognition=true
Click to expand...
Click to collapse
wisemanwizz said:
The kernel works like a charm! Thanks!
For face unlock I tried to manually edit prop & then restart the phone, I am rooted but it is not working (I do not have Magisk) maybe I am doing something wrong.
Is there any specific place I have to put the "ro.config.face_recognition=true" within the prop file - i.e. should i just paste it right at the bottom of the prop file? And also where will the facial recognition option appear once it is enabled so I can confirm?
Sorry (I'm kind of a noob) I will probably try later. :angel::angel:
Click to expand...
Click to collapse
After setting that prop, doesn't mater where so just place it at the bottom, reboot and then got to Settings - Security & Privacy, you should have the Face Unlock option. If you enroll your face you can unlock phone by using the power button and looking at screen. It unlocks instantly in most cases.
Also I noticed I failed at setting a custom string to kernel that would show in Settings - About - Kernel. But it just says Unavailable now. Don't worry about it if you were wondering.
Related
I wrote this for myself but here it is in case anyone is also interested.
Google sets the wifi country code to whatever is in your sim card. If the country does not have a corresponding list of enabled 5GHz frequencies, then a lot of these frequencies get disabled. This mod simply sets the country code to US. There is no GUI or anything, just enable and restart and you're all set. Android marshmallow only. I tested it on my S7 edge and it's working fine.
Enjoy.
Edit: Added OREO 8.1 version. Testing working on Pixel 2 XL.
madmack said:
I wrote this for myself but here it is in case anyone is also interested.
Google sets the wifi country code to whatever is in your sim card. If the country does not have a corresponding list of enabled 5GHz frequencies, then a lot of these frequencies get disabled. This mod simply sets the country code to US. There is no GUI or anything, just enable and restart and you're all set. Android marshmallow only. I tested it on my S7 edge and it's working fine.
Enjoy.
Click to expand...
Click to collapse
android4.4 cannot open
madmack said:
I wrote this for myself but here it is in case anyone is also interested.
Google sets the wifi country code to whatever is in your sim card. If the country does not have a corresponding list of enabled 5GHz frequencies, then a lot of these frequencies get disabled. This mod simply sets the country code to US. There is no GUI or anything, just enable and restart and you're all set. Android marshmallow only. I tested it on my S7 edge and it's working fine.
Enjoy.
Click to expand...
Click to collapse
awesome thankx
我是一个卒 said:
android4.4 cannot open
Click to expand...
Click to collapse
did you read OP's post properly ?
There is no GUI or anything, just enable and restart and you're all set.
BytesReverser said:
did you read OP's post properly ?
There is no GUI or anything, just enable and restart and you're all set.
Click to expand...
Click to collapse
sorry,my english is poor
I've been trying to find a fix ever since i got this phone and your module fixed it with no hassle
Thank you very much
Can i have your permission to share this on Mi A1 forums and xiaomi subreddit?
berezker said:
I've been trying to find a fix ever since i got this phone and your module fixed it with no hassle
Thank you very much
Can i have your permission to share this on Mi A1 forums and xiaomi subreddit?
Click to expand...
Click to collapse
Sure thing. If I can ask you to please link to this post and not share the APK.
madmack said:
Sure thing. If I can ask you to please link to this post and not share the APK.
Click to expand...
Click to collapse
No problem
Thank you again so much
Hi!
Are you actively working on this still? and did you get around to testing it on a oneplus of any kind? I got the 5T, this does nothing on it sadly, and i'm desperate for a fix
thanks!
Amornik said:
Hi!
Are you actively working on this still? and did you get around to testing it on a oneplus of any kind? I got the 5T, this does nothing on it sadly, and i'm desperate for a fix
thanks!
Click to expand...
Click to collapse
I can't say I'm "working on it still" but whenever I have a need for it, I update it. I actually have the pixel 2 xl running latest oreo 8.1 and needed the added 5 GHz access points at work to have higher speeds (780 MBps beats 54 Mbps any day!)
Works fine here. Just make sure your xposed is working fine and that this module is loaded correctly. Reboot, profit. should work on all 8.1 ROMs given that I'm only modifying a simple framework method which should exist in all variants out there.
Hi,
thanks for the reply!
I have installed the latest Xposed, and your module (downloaded from there, not the file here) & rebooted. nothing happens. I do not see my 5GHZ when it's on the 148 and up band. When I switch it to the lower bands (38 and up) works just fine. this is driving me insane. Any chance you could help me out ?
In another post, someone offered me to replace a file, and that seemed to work for a bit, but now it has also stopped working
Link: https://forum.xda-developers.com/oneplus-5t/help/wifi-region-5ghz-question-5t-t3776003#post76220330
Thanks! appreciate any and all help.
Edit: Actually it would help to understand what it is exactly your addon is changing ? since the above file does have something that seems relevant. is this the same value being changed?
Amornik said:
Hi,
thanks for the reply!
I have installed the latest Xposed, and your module (downloaded from there, not the file here) & rebooted. nothing happens. I do not see my 5GHZ when it's on the 148 and up band. When I switch it to the lower bands (38 and up) works just fine. this is driving me insane. Any chance you could help me out ?
In another post, someone offered me to replace a file, and that seemed to work for a bit, but now it has also stopped working
Link: https://forum.xda-developers.com/oneplus-5t/help/wifi-region-5ghz-question-5t-t3776003#post76220330
Thanks! appreciate any and all help.
Edit: Actually it would help to understand what it is exactly your addon is changing ? since the above file does have something that seems relevant. is this the same value being changed?
Click to expand...
Click to collapse
Maybe use my file here instead? Not sure what's on the xposed modules repo.
madmack said:
Maybe use my file here instead? Not sure what's on the xposed modules repo.
Click to expand...
Click to collapse
Hi,
Thanks for the reply! I thought I had mentioned I already tried it, did not change anything.
Maybe if you told me which file this is editing and which value is being changed, I might be able to debug and see if it's actually changing the value it needs to.
Works fine on my xiaomi a1 !!! thx so much!!
madmack said:
I wrote this for myself but here it is in case anyone is also interested.
Google sets the wifi country code to whatever is in your sim card. If the country does not have a corresponding list of enabled 5GHz frequencies, then a lot of these frequencies get disabled. This mod simply sets the country code to US. There is no GUI or anything, just enable and restart and you're all set. Android marshmallow only. I tested it on my S7 edge and it's working fine.
Enjoy.
Edit: Added OREO 8.1 version. Testing working on Pixel 2 XL.
Click to expand...
Click to collapse
cleberjb said:
Works fine on my xiaomi a1 !!! thx so much!!
Click to expand...
Click to collapse
It would be great if you could specify which version of Android (8.0, 8.1) and which ROM (or stock).
thanks!
Amornik said:
It would be great if you could specify which version of Android (8.0, 8.1) and which ROM (or stock).
thanks!
Click to expand...
Click to collapse
Sorry my inconvenience. Works on Android 8.0 stock.
Amornik said:
Hi,
Thanks for the reply! I thought I had mentioned I already tried it, did not change anything.
Maybe if you told me which file this is editing and which value is being changed, I might be able to debug and see if it's actually changing the value it needs to.
Click to expand...
Click to collapse
Sure, editing method setCountryCode in com.android.server.wifi.WifiServiceImpl
Setting the parameter to US manually.
madmack said:
Sure, editing method setCountryCode in com.android.server.wifi.WifiServiceImpl
Setting the parameter to US manually.
Click to expand...
Click to collapse
Cool, thanks!
Just as a follow up..
1. is this com.android.server.wifi.wifiserviceimpl a file (.jar?)or db file?
2. where is it located?
3. does your fix change it every time on reboot? or is it a one time change? (meaning, does the phone update this from the SIM occasionally?)
thanks again!
Amornik said:
Cool, thanks!
Just as a follow up..
1. is this com.android.server.wifi.wifiserviceimpl a file (.jar?)or db file?
2. where is it located?
3. does your fix change it every time on reboot? or is it a one time change? (meaning, does the phone update this from the SIM occasionally?)
thanks again!
Click to expand...
Click to collapse
no man, it's a framework class that xposed can tap into and change the behavior. Take a look at the source code of Android AOSP for that class. it's not a simple file in /system that you modify. It is changed every time this method is invoked, it's how xposed works.
Lol, just goes to show how much I know about how rhis works, which is nothing
Its working with the update to 8.1 btw.
Thanks for all your work and patience!
Hello,
I took the CM13 build from CN for the x720, removed all of the Chinese apps, and added the build.props to make it work correctly for the x727 version (single sim). Tested a bit and everything seems ok. Let me know if you find any issues or have any tweaks request.
Download: cm-13.0-20161219-UNOFFICIAL-lex727-zoid_003.zip
zoid_99 said:
Hello,
I took the CM13 build from CN for the x720, removed all of the Chinese apps, and added the build.props to make it work correctly for the x727 version (single sim). Tested a bit and everything seems ok. Let me know if you find any issues or have any tweaks request.
Download: cm-13.0-20161219-UNOFFICIAL-lex727-zoid_003.zip
Click to expand...
Click to collapse
Sweet I was having issues with build prop editing so I can try this tonight. Is the us modem corrected in here or do we still need to flash that seperately?
zmanfarlee said:
Sweet I was having issues with build prop editing so I can try this tonight. Is the us modem corrected in here or do we still need to flash that seperately?
Click to expand...
Click to collapse
The modem is not included in this package.
zoid_99 said:
The modem is not included in this package.
Click to expand...
Click to collapse
Thanks. Easy enough to flash anyways
I can't seem to get it to register a fingerprint. Is there something I did wrong? I installed the stock gapps, which replaces the some aosp apps with google ones.
robertzas said:
I can't seem to get it to register a fingerprint. Is there something I did wrong? I installed the stock gapps, which replaces the some aosp apps with google ones.
Click to expand...
Click to collapse
Yes it looks like I messed something up with the fingerprint scanner. I don't use the fingerprint scanner so I didn't test it. I'll see if the original CM13 fingerprint scanner and if so I should be able to fix it.
zoid_99 said:
Yes it looks like I messed something up with the fingerprint scanner. I don't use the fingerprint scanner so I didn't test it. I'll see if the original CM13 fingerprint scanner and if so I should be able to fix it.
Click to expand...
Click to collapse
Thanks! Otherwise been a great ROM so far, exactly what I've been looking for.
zoid_99 said:
Hello,
I took the CM13 build from CN for the x720, removed all of the Chinese apps, and added the build.props to make it work correctly for the x727 version (single sim). Tested a bit and everything seems ok. Let me know if you find any issues or have any tweaks request.
Download: cm-13.0-20161219-UNOFFICIAL-lex727-zoid_003.zip
Click to expand...
Click to collapse
great rom !! Can you build in the dual-APP, like the wechat avatar in the official ROM? Thanks!
One more suggestion: if it's not a big deal, you might as well allow the processor to get to its max speed for both big and little cores.
best post ever
zmanfarlee said:
Thanks. Easy enough to flash anyways
Click to expand...
Click to collapse
Can you tell me where I can find the modem zip file for band 12?
crookdbill said:
Can you tell me where I can find the modem zip file for band 12?
Click to expand...
Click to collapse
http://forum.xda-developers.com/le-pro3/how-to/flashing-guide-roundup-leeco-le-pro-3-t3511901
zmanfarlee said:
http://forum.xda-developers.com/le-pro3/how-to/flashing-guide-roundup-leeco-le-pro-3-t3511901
Click to expand...
Click to collapse
Thank you.
OK, so the fingerprint scanner is being a pain. I can't get the service to start on boot for some reason. I can get it to start after bootup and then it works ok. I'll keep toying with it.
Hi,
I will release here my updated "boot.img" files for the Xperia XA Ultra Dual Sim.
You must have an unlocked bootloader to flash with Fastboot.
You don't need to be on the same firmware as the boot image that you want to flash.
You have to flash SuperSu again from TWRP just after flashed new boot to avoid bootloop.
All boot images have "ro.secure=0" and "ro.debuggable=1" in default.prop file
and "forcencrypt" of internal memory switched to "encryptable" in fstab.mt6755 file.
The Fastboot command is:
fastboot flash boot NAMEOFIMAGE.img
Click to expand...
Click to collapse
Follow the guide from @Yooooomi to flash new firmware on your Ultra to avoid bugs and brick: https://forum.xda-developers.com/xa-ultra/how-to/flashing-xa-ultra-flashtool-t3551319
Releases:
12/28/2016: From 36.0.B.2.109 kernel sources and Ramdisk from 36.0.B.2.109 firmware.
https://mega.nz/#!cxI3SJaC!o-aqc2gUZufDJefKaxGRxRhekEq32B1bIDB3ROxyd7Y
04/01/2017: From 36.0.B.2.146 kernel sources and Ramdisk from 36.0.B.2.146 firmware.
https://mega.nz/#!VhwRQLqR!rOqEFWeOC3IQKl4aDw7P_v0U2wmZtBPXk_MSDJMEy9k
hi
Does anyone has tested this ROM?
probably is break my devise, possible if there unbreak?
thanks all.
twhhhco said:
hi
Does anyone has tested this ROM?
probably is break my devise, possible if there unbreak?
thanks all.
Click to expand...
Click to collapse
Hi, it's not a Rom just a boot.img for unlocked bootloaders with stock kernel built from Sony open source archive.
36.2.B.2.109 boot should fix the front camera not focusing after root.
After testing I found out that the boot does have problems
Which are:
1-Screen doesn't turn off completely, it stays at a very dark state which can be noticed in extreme low light conditions and if u turn the screen back on u will notice a a static on the screen and then it functions normally.
2-system brightness level meter doesn't work but third party apps can be used to change that.
Hope that helps and u come with even better boot in the future and thank u in advance.
klengjaua said:
After testing I found out that the boot does have problems
Which are:
1-Screen doesn't turn off completely, it stays at a very dark state which can be noticed in extreme low light conditions and if u turn the screen back on u will notice a a static on the screen and then it functions normally.
2-system brightness level meter doesn't work but third party apps can be used to change that.
Hope that helps and u come with even better boot in the future and thank u in advance.
Click to expand...
Click to collapse
Hi, thank you for the feedback. I don't have any unlocked Ultra (only have a unlocked XA F3112) so I can't test new releases or try to debug anything. I don't make any changes to the kernel source code, only build the kernel and repack it in a stock ramdisk with very small changes for root, nothing more. I hope that an user will be able to fix bugs.
rrvuhpg said:
Hi, thank you for the feedback. I don't have any unlocked Ultra (only have a unlocked XA F3112) so I can't test new releases or try to debug anything. I don't make any changes to the kernel source code, only build the kernel and repack it in a stock ramdisk with very small changes for root, nothing more. I hope that an user will be able to fix bugs.
Click to expand...
Click to collapse
These are the fixes you mentioned?
Nrsoto said:
These are the fixes you mentioned?
Click to expand...
Click to collapse
Yes it's the new boot who fix the front camera bug mentioned in my PM, as you can see in the comments it fix this bug but make an other bug You can flash it if your device is a dual sim. If you try it please say us if you have the same new bug.
rrvuhpg said:
Yes it's the new boot who fix the front camera bug mentioned in my PM, as you can see in the comments it fix this bug but make an other bug You can flash it if your device is a dual sim. If you try it please say us if you have the same new bug.
Click to expand...
Click to collapse
I will do it with f3213
Nrsoto said:
These are the fixes you mentioned?
Click to expand...
Click to collapse
For those who are struggling with the front facing camera, I finally solved it without installing any kernel or modify anything from the system. Downgrade to 36.0.A.1.111 (should be the one one with service unit exchange or smth like that). Had installed gapps stock (but I suggest u don't delete the Sony camera app - Instagram and Snapchat work perfectly fine) + xposed + adoptable storage.
As a final mention my devie is F3211
sexxualization said:
For those who are struggling with the front facing camera, I finally solved it without installing any kernel or modify anything from the system. Downgrade to 36.0.A.1.111 (should be the one one with service unit exchange or smth like that). Had installed gapps stock (but I suggest u don't delete the Sony camera app - Instagram and Snapchat work perfectly fine) + xposed + adoptable storage.
As a final mention my devie is F3211
Click to expand...
Click to collapse
Sorry, how did you do it, my cel no focusing camera frontal before unlocked boot loader , you device Does the same
Nrsoto said:
Sorry, how did you do it, my cel no focusing camera frontal before unlocked boot loader , you device Does the same
Click to expand...
Click to collapse
Here's step by step what I did, I hope it will work for your device too:
1. Go to xperifirm and download the 36.0.A.1.111 firmware (service unit exchange)
2. Create a bundle on the flashtool within the firmware folder
3. Flash it
4. Happy rooting!
There is however something I have to mention about this fw: you'll probably not receive any system updates
IF U ARE A SNAPCHAT USER install Snapchat before messing the system up with xposed
sexxualization said:
For those who are struggling with the front facing camera, I finally solved it without installing any kernel or modify anything from the system. Downgrade to 36.0.A.1.111 (should be the one one with service unit exchange or smth like that). Had installed gapps stock (but I suggest u don't delete the Sony camera app - Instagram and Snapchat work perfectly fine) + xposed + adoptable storage.
As a final mention my devie is F3211
Click to expand...
Click to collapse
Since you've mentioned snapchat allow me to ask. I'm on stock and I've just received the 36.0.B.2.109 update (hings are kinda slow in Egypt).
But no matter how many updates I get, snapchat quality is terrible on the front facing shooter. It's only good when it's really sunny. Other than that it's extremely dark to the point that sometimes you can't even recognize faces ! Have you ever run into that ? If yes or no what do you recommend ?
Talal Tango said:
Since you've mentioned snapchat allow me to ask. I'm on stock and I've just received the 36.0.B.2.109 update (hings are kinda slow in Egypt).
But no matter how many updates I get, snapchat quality is terrible on the front facing shooter. It's only good when it's really sunny. Other than that it's extremely dark to the point that sometimes you can't even recognize faces ! Have you ever run into that ? If yes or no what do you recommend ?
Click to expand...
Click to collapse
I had one bug with snapchat on the same firmware you are using but it was more app related rather than a camera quality issue. every time I opened sc the image would tend to get darker (not to mention the app itself was kinda slow) and the only fix I could find is moving the app back to internal storage (but again, this was an app bug). the only thing i can tell you is experimenting with other fws until you find one that could fix your issue, otherwise sorry but i have no idea.
sexxualization said:
I had one bug with snapchat on the same firmware you are using but it was more app related rather than a camera quality issue. every time I opened sc the image would tend to get darker (not to mention the app itself was kinda slow) and the only fix I could find is moving the app back to internal storage (but again, this was an app bug). the only thing i can tell you is experimenting with other fws until you find one that could fix your issue, otherwise sorry but i have no idea.
Click to expand...
Click to collapse
I've had this issue on all firmwares up until the one i mentioned. And yeah i didn't even use my external usage yet, so it seems that im having a different issues although we both got dark images. I would try different firmwares but I dont know what sony did to make the battery much better on the recent firmware. I'll try messing around till I find the culprit.
Thanks.
Buggy with f3216...please fix
Help Downgrading to .111
So I've download the .111 service exchange unit firmware from Xpefirm, and created a bundle to flash it through flash tool, this is what I get in the attachment. What wrong am I doing here ? This is my first time dealing with Xpefirm so please guide me on what do from here
Hi !
I've tested that because I really like root and it's works for me, but I have one problem with snapchat, when I try to connect I get this message :
I don't have xposed on this phone, just the root, and if I delete the root, it's the same problem.
Have you a solution for that ?
Thank you !
Pandawa3 said:
Hi !
I've tested that because I really like root and it's works for me, but I have one problem with snapchat, when I try to connect I get this message :
I don't have xposed on this phone, just the root, and if I delete the root, it's the same problem.
Have you a solution for that ?
Thank you !
Click to expand...
Click to collapse
By deleting root, I assume you tried to delete the root app not root access itself.
You have to go back to stock rom, install snapchat, log in, root your phone and never log out.
szucsi1996 said:
Buggy with f3216...please fix
Click to expand...
Click to collapse
Hi, how is it buggy? I would like to root my f3216, thx.
Aphex33 said:
Hi, how is it buggy? I would like to root my f3216, thx.
Click to expand...
Click to collapse
i think, don't do it!
edit: Brightness adjustment not working, ui very buggy, etc.
G'day guys and girls
I haven't seen PN source code updated for a while on the r33 side, seems they are focusing on the kernel a little bit
So I merged the tags myself and add some features to the ROM
I'LL TRY TO KEEP THE THREAD UPDATED, BUT THERES NO GUARANTEE ON THAT, THE REPO WILL PROBABLY BE UPDATED, IF YOU WANT TO BUILD YOURSELF, GO TO THE REPOSITORY DOWN BELOW
PLEASE NOTICE
This version was NOT signed by the PureNexus's certificates, please do a FULL FACTORY RESET if you are from the offical build.
I'm sorry for the inconvenience, but this is compulsory
Features
Built in GAPPS (no gmail, Google News and weather and play magazines, don't find them useful since I've got outlook and other replacement)
Built in Greenify
Android 7.1.2_r33 August security level
VoLTE tested
Lineage Terminal
ElementalX 1.15 Kernel (NTFS rw, exFAT, High Brightness Mode, Digital Gain control)
USB Patch for using the phone as a USB HID keyboard/mouse see here
All PureNexus Features
Untested
Since I am in Australia, there's no actual way to test whether Wi-Fi calling works, but it should work considering Project Fi was prebuilted. Please tell me if I need to add anything.
Magisk
https://forum.xda-developers.com/apps/magisk/unofficial-google-pixel-family-support-t3639262
Goodwin_c's magisk seems to work very well, thanks @goodwin_c
Known Bugs
OK Google detection is known to be not working in some languages (eg. Japanese)
MusicFX don't seems to open
Screenshots
https://ibb.co/m9XXz5
https://ibb.co/fL0Ke5
Downloads
https://drive.google.com/file/d/0B5ns3qw5ULWhTkZMQ2dVN0Z3LUU/view?usp=sharing
Flashing - How to
Please unzip the zip file, flash using fastboot commands
fastboot flash system_a /path/to/system.img
fastboot flash system_b /path/to/system.img
fastboot flash boot_a /path/to/boot.img
fastboot flash boot_b /path/to/boot.img
GitHub Source
manifest
patched kernel
Credits
the PureNexus Project https://github.com/purenexusproject
LineageOS https://github.com/lineageos
Pelya https://github.com/pelya/android-keyboard-gadget
flar2 (aka. Aaron Segaert) https://github.com/flar2
One thing I noticed is, I couldn't get Ok Google to work. Would say this language isn't supported
Sent from my Pixel XL using Tapatalk
It's asking me to flash NZH54D Vendor image but i'm on T-Mobile shouldn't my Vendor image be NKG47S...?
BHermes211 said:
One thing I noticed is, I couldn't get Ok Google to work. Would say this language isn't supported
Click to expand...
Click to collapse
Ok Google works fine for me but I still haven't updated the vendor image. I'm worried I'm gonna screw up the rom. I'm gonna test it now after flashing the correct vendor image.
Ok vendor has been updated and everything is working fine.
why is this being made ? is PN dead ? curious since i've been using my pixel less since i got the s8+
Delete.
TheUndertaker21 said:
why is this being made ? is PN dead ? curious since i've been using my pixel less since i got the s8+
Click to expand...
Click to collapse
If the official PN doesn't have a feature that a user wants, they are within their rights to build a version that incorporates that feature.
And in most cases, if the builder marks it as Unofficial (as is the case here), they are welcome to share it others, on the understanding that no support will likely be given from the official builder.
BHermes211 said:
One thing I noticed is, I couldn't get Ok Google to work. Would say this language isn't supported
Click to expand...
Click to collapse
Hey, there, actually I'm also having this problem. What language are you using? I am using Japanese and this problem presents, I thought it was Google's problem so I didn't care, I'll try figure it out.
EDIT: fixes typo
TheUndertaker21 said:
why is this being made ? is PN dead ? curious since i've been using my pixel less since i got the s8+
Click to expand...
Click to collapse
No, they aren't dead. they seems to focusing on other things especially the kernel and they are preparing for O since all the repos are being moved to the PureNexus-Legacy repo now. So I just built myself also add things for my own use.:fingers-crossed:
Pøîñtßlåñk said:
It's asking me to flash NZH54D Vendor image but i'm on T-Mobile shouldn't my Vendor image be NKG47S...?
Click to expand...
Click to collapse
I think it's probably fine. Since I'm using the international version so I'm just flashing the NZH54D vendor
cydia2020 said:
I think it's probably fine. Since I'm using the international version so I'm just flashing the NZH54D vendor
Click to expand...
Click to collapse
Worked fine thx.
BHermes211 said:
One thing I noticed is, I couldn't get Ok Google to work. Would say this language isn't supported
Click to expand...
Click to collapse
Do you see the same thing here
Pøîñtßlåñk said:
Worked fine thx.
Click to expand...
Click to collapse
Can you get OK Google to work? What language are you on. Cheers.
cydia2020 said:
Can you get OK Google to work? What language are you on. Cheers.
Click to expand...
Click to collapse
Works fine here English.
I was using English...
Sent from my Pixel XL using Tapatalk
BHermes211 said:
I was using English...
Click to expand...
Click to collapse
Hmm, that's weird. I'll try compile the official version on my 5x and see what happens
cydia2020 said:
Hmm, that's weird. I'll try compile the official version on my 5x and see what happens
Click to expand...
Click to collapse
Thank you. I'll be more than happy to give it a try again
Sent from my Pixel XL using Tapatalk
MusicFX don't seems to open in case you're concerned.
cydia2020 said:
Hmm, that's weird. I'll try compile the official version on my 5x and see what happens
Click to expand...
Click to collapse
Question... Is there a way to remove system apps on this rom? I've tried to remove the YouTube app even with magisk installed it gives apps that are able to remove system apps root permission but in the app remover app itself it says that I'm not rooted
Below are Stock kernels with DT2W added. The kernels have been extracted from 47.2.A.11.228 firmware.
The kernels are SElinux enforcing (same as stock). They are in no way custom, all i have done is add the dtb from Iovf's .107 kernel to allow double tap 2 wake.
Some people have reported the DT2W feature requires a solid tap, and sometimes may not wake the screen instantly.
This is out of my hands, and capabilities, to do anything about.
Installation:
On stock .228 firmware:
Flash the kernel for your device in TWRP
Flash whatever Magisk.zip you prefer, and reboot. Once rebooted, install the magisk module below (DT2W_Magisk Module) and reboot.
(If you want permissive selinux, also install the Permissive module in Magisk at the same time).
eXistenZ users:
The kernels are also compatible. Same install steps apply (flash kernel, flash magisk, reboot)
If.you want to keep SElinux set to enforcing, use the DT2W_Magisk Module.
If you are using something to set SElinux to permissive for fonts (or whatever reason), you dont need the DT2W Magisk Module, only the Permissive module.
Also attached are the TWRP flashable stock .228 kernels.
Thanks to @iovf for the original kernels I pinched parts from.
Thanks to @shoey63 for the DT2W Magisk Module.
Stuck on Sony boot logo. I use the last eXistenz rom on last firmware .228
theflanker said:
Stuck on Sony boot logo. I use the last eXistenz rom on last firmware .228
Click to expand...
Click to collapse
Did you flash magisk after kernel?
theflanker said:
Stuck on Sony boot logo. I use the last eXistenz rom on last firmware .228
Click to expand...
Click to collapse
Which kernel? Single or dual?
kojak1989 said:
Did you flash magisk after kernel?
Click to expand...
Click to collapse
Yes of course, 20.0 version. Maybe I have to try 18.1. I will try and tell you.
Beetle84 said:
Which kernel? Single or dual?
Click to expand...
Click to collapse
Single
theflanker said:
Yes of course, 20.0 version. Maybe I have to try 18.1. I will try and tell you.
Single
Click to expand...
Click to collapse
Did tou do it with clean install ? If yes then you must do it with 18.1 and let eXistenZ boot once and for me iovf kernel make freezes.
theflanker said:
Yes of course, 20.0 version. Maybe I have to try 18.1. I will try and tell you.
Single
Click to expand...
Click to collapse
I use v20 on the XZP with no drama, can you try the dual sim kernel and let me know? There is no harm in using a dual kernel on a single sim phone. Thanks.
I tried these kernels, and it seems really inconsistent and finicky. However, I think I found the reason why there are so many issues with double tap to wake on the XZ1; a developer looked into implementing tap to wake and had this to say:
Myself5 said:
I roughly remember looking into this decades ago and the conclusion was that either the XZP/XZ1 kernel is super ****ed (beyond repair) or they have some sort of hardware issue causing the situations. When you used DT2W and combined it with using the power button in a specific order the touchscreen wouldn't work anymore until you turn the screen off/on again using the power button.
Click to expand...
Click to collapse
@Beetle84, do you know anyone who could look into this? It would be nice to see if this was a really bad software limitation, or just a hardware limitation.
Generic123. said:
I tried these kernels, and it seems really inconsistent and finicky. However, I think I found the reason why there are so many issues with double tap to wake on the XZ1; a developer looked into implementing tap to wake and had this to say:
@Beetle84, do you know anyone who could look into this? It would be nice to see if this was a really bad software limitation, or just a hardware limitation.
Click to expand...
Click to collapse
I think its the xz1 panel derf alot said somewhere in his LOS thread... xzp works flawlessly with dt2w, despite the above quote.
On another note, whih kernel did you try, the single or dual?
Beetle84 said:
I think its the xz1 panel derf alot said somewhere in his LOS thread... xzp works flawlessly with dt2w, despite the above quote.
On another note, whih kernel did you try, the single or dual?
Click to expand...
Click to collapse
Does that mean the XZ1 does not have the appropiate hardware for it? It's a shame if that's the case.
I used the single sim kernel, on existenz pie with the magisk module.
Generic123. said:
Does that mean the XZ1 does not have the appropiate hardware for it? It's a shame if that's the case.
I used the single sim kernel, on existenz pie with the magisk module.
Click to expand...
Click to collapse
I believe its hardware. For the xzp, the dt2w code was ported (by a different dev than iovf) from the xperia x to the xzp kernel. Im not sure if it will get any better ever. Im not positive how iovf did it.
Thanks for letting me know about which kernel you flashed, someone above bootlooped using the single sim kernel, no idea why. Its kinda hard to test myself without the xz1... A few guys tested before i uploaded them here, so I don't know what happened for him/her.
Beetle84 said:
I believe its hardware. For the xzp, the dt2w code was ported (by a different dev than iovf) from the xperia x to the xzp kernel. Im not sure if it will get any better ever. Im not positive how iovf did it.
Thanks for letting me know about which kernel you flashed, someone above bootlooped using the single sim kernel, no idea why. Its kinda hard to test myself without the xz1... A few guys tested before i uploaded them here, so I don't know what happened for him/her.
Click to expand...
Click to collapse
Is there any way you could contact iovf to ask him/her? Maybe we could see if the method you mentioned for the XZP might be able to get dt2w to work on the XZ1.
Generic123. said:
Is there any way you could contact iovf to ask him/her? Maybe we could see if the method you mentioned for the XZP might be able to get dt2w to work on the XZ1.
Click to expand...
Click to collapse
Will do
Beetle84 said:
Will do
Click to expand...
Click to collapse
Many thanks my dude.
I'm bit courious, as there has been only one person has mentioned what rom and firmware they are using, but for those that are using the the existenz rom have you tried going into the rom display settings and flipping on the dt2w switch to see if it helps..
see pic..
I tried to reflash everything with Magisk 18.1 but I have the same error.
But doesn't it work for me?
theflanker said:
I tried to reflash everything with Magisk 18.1 but I have the same error.
But doesn't it work for me?
Click to expand...
Click to collapse
No idea mate, single and dual are confirmed working. Try flashing the stock kernel, magisk and reboot
Then try the dt2w kernel, magisk and reboot.
Beetle84 said:
I think its the xz1 panel derf alot said somewhere in his LOS thread... xzp works flawlessly with dt2w, despite the above quote.
On another note, whih kernel did you try, the single or dual?
Click to expand...
Click to collapse
IIRC the Xperia XZ Premium got shipped with multiple touchscreens.
I can assure you mine is doing that, and I can provide you multiple other instances where it happened. I've been trying to use my XZP as a DD for around 2 months and had that issue nearly daily when DT2W was enabled. (Mind you, that was shortly after release though, so it's been a while).
Generic123. said:
Does that mean the XZ1 does not have the appropiate hardware for it? It's a shame if that's the case.
I used the single sim kernel, on existenz pie with the magisk module.
Click to expand...
Click to collapse
See above.
Beetle84 said:
I believe its hardware. For the xzp, the dt2w code was ported (by a different dev than iovf) from the xperia x to the xzp kernel. Im not sure if it will get any better ever. Im not positive how iovf did it.
Thanks for letting me know about which kernel you flashed, someone above bootlooped using the single sim kernel, no idea why. Its kinda hard to test myself without the xz1... A few guys tested before i uploaded them here, so I don't know what happened for him/her.
Click to expand...
Click to collapse
There is nothing that was "ported". Both devices have the code for Doubletap to wake in the kernel. It's a single matter of replacing a "false" with "true". None of that is standard code btw, so isn't it interesting that Sony put effort into adding Doubletap to wake just to disable it then?
P.S: Why are you building Dual and Single SIM variants of the kernel?
Myself5 said:
IIRC the Xperia XZ Premium got shipped with multiple touchscreens.
I can assure you mine is doing that, and I can provide you multiple other instances where it happened. I've been trying to use my XZP as a DD for around 2 months and had that issue nearly daily when DT2W was enabled. (Mind you, that was shortly after release though, so it's been a while).
See above.
There is nothing that was "ported". Both devices have the code for Doubletap to wake in the kernel. It's a single matter of replacing a "false" with "true". None of that is standard code btw, so isn't it interesting that Sony put effort into adding Doubletap to wake just to disable it then?
P.S: Why are you building Dual and Single SIM variants of the kernel?
Click to expand...
Click to collapse
Thanks for the clarification. Would it be possible for us to determine what our touchscreen manufacturers are? In your case, tap to wake is pretty glitchy. But, in @Beetle84's case, he appears to have little/no issues. It would be nice to see if different touchscreen manufacturers are at play here.