Related
Hi Folks,
As you know, there are lot meet ups happening in India for Honor/Huawei users, currently for Honor 6X and Honor 8 Pro only, but we may see these coming to other devices as well based on the response. It may be limited for older devices where software support is not possible but eventually newer devices like, Honor 5C, Honor 8, Honor 6X and honor 8 pro would be included (if they get more requests for 5C and 8).
In this thread, lets discuss on various points/feedback and feature request that we want to raise it to the Honor teams during meetup and eventually taken up to the R&D team for consideration to enhance the end user experience in a positive way.
Anybody attending these meet ups with Honor team can put forward these points and we wish these points will be considered to provide a happy and positive user experience.
Created a thread in Honor 6X section as well so that 6X user can fill their points there and we can refer any of these thread for unique points to proceed with.
6X thread
Good luck.
Attached is the list of point raised during Honor meet up in Chennai and compiled by our fellow member @amulbaby (Abhishek)
View attachment Points_from_Chennai_Meet-up.pdf
6X thread- https://forum.xda-developers.com/honor-6x/how-to/feature-request-feedback-upcoming-emui-t3669806
As we already discussed on other thread few of the points
removal of knuckle feature
camera lag on EMUI 5 (while opening only)
Over exposed image while using front camera
timely Kernel sources for all the device
Double tap to wake up
uniform OTA acorss all devices
Expecting for expert opinion, new points, feedback, feature request from @gopinaidu77 @venugopalu007 @PalakMi @RedSkull23 @clsA @jsbeyond @amulbaby @joe2k01 add other if I missed anyone.
Update
I have a updated one @shashank1320 , the one which I made for Mumbai.
Same has been submitted to R & D for reference.
And regarding Kernel sources, Recent removal of official firmwares which directly affect development of Custom ROMs, I have already written a brief mail describing how important it is to have a Open source environment in Android Platform and that going this way would only reduce sales numbers.
Where in house processing restricts the possibility of constant upgrades, having the sources available to developers will only help us all as developers will be able to include security patches, custom kernel compatibility, additional features of further Android iterations and not wait for the OEM to release.
What we heard from Mr. Naveen at Chennai was that due to the closed loop nature of the processor, they take a base version of Android and try to build EMUI on top with all possible optimizations and iterations , which takes time to release as other OEMs mostly have to work with Qualcomm where they get most thing pre baked .They like to keep update frequency lower than other brands owing to the same reason.
amulbaby said:
What we heard from Mr. Naveen at Chennai was that due to the closed loop nature of the processor, they take a base version of Android and try to build EMUI on top with all possible optimizations and iterations , which takes time to release as other OEMs mostly have to work with Qualcomm where they get most thing pre baked .They like to keep update frequency lower than other brands owing to the same reason.
Click to expand...
Click to collapse
Thanks for sharing.
Yes, regarding this. he conveyed the same message. Other OEMs using the SD version of processor gets the faster updated because Qualcomm directly work in collaboration with Google for new Android updates and SD models receive it quickly and other OEMs which has the custom Skin on Top of Android takes their own time to customize and tweak the new updates, test and release for public.
Also These OEMs keep the update frequency less unless there is anything major to be addressed like bugs, security concerns etc. If the OTA update given is stable and phone works fine without any user complaints then they avoid rolling out the updates to avoid any mess with the working updates.
Whatever you said is what we have heard as well.
Going by the number of inconsistencies we have on 8 pro, its high time to see a update. Easy to lose out of competitive market where people keep changing devices so often nowadays.
amulbaby said:
Whatever you said is what we have heard as well.
Going by the number of inconsistencies we have on 8 pro, its high time to see a update. Easy to lose out of competitive market where people keep changing devices so often nowadays.
Click to expand...
Click to collapse
Couldn't agree more bro. And Huawei needs to understand from user perspective. Hardware wise devices are good but if no custom development then people opt for redmi, Moto etc.
Ok. Some points from me also.
1. The current settings screen is very cluttered and the use of colorful icons makes it look childish IMO. I would suggest if going forward with the Oreo update they keep it closer to stock and reduce the clutter in settings.
Also if they can keep the notifications and QS area more stock.
Overall, more closer to stock UI.
2. Addition of equaliser and improvement in loudness over earphones.
3. A slight improvement in sharpness in rear camera. Also improvement in low light shots.
Can't think of anymore because others are already listed.
Sent from my Honor 8 pro using Tapatalk
K.khiladi said:
Ok. Some points from me also.
1. The current settings screen is very cluttered and the use of colorful icons makes it look childish IMO. I would suggest if going forward with the Oreo update they keep it closer to stock and reduce the clutter in settings.
Also if they can keep the notifications and QS area more stock.
Overall, more closer to stock UI.
2. Addition of equaliser and improvement in loudness over earphones.
3. A slight improvement in sharpness in rear camera. Also improvement in low light shots.
Can't think of anymore because others are already listed.
Click to expand...
Click to collapse
Thanks. Hope Huawei consider all these points.
We will collect and raise all to them in next meet up.
amulbaby said:
I have a updated one @shashank1320 , the one which I made for Mumbai.
Same has been submitted to R & D for reference.
And regarding Kernel sources, Recent removal of official firmwares which directly affect development of Custom ROMs, I have already written a brief mail describing how important it is to have a Open source environment in Android Platform and that going this way would only reduce sales numbers.
Where in house processing restricts the possibility of constant upgrades, having the sources available to developers will only help us all as developers will be able to include security patches, custom kernel compatibility, additional features of further Android iterations and not wait for the OEM to release.
What we heard from Mr. Naveen at Chennai was that due to the closed loop nature of the processor, they take a base version of Android and try to build EMUI on top with all possible optimizations and iterations , which takes time to release as other OEMs mostly have to work with Qualcomm where they get most thing pre baked .They like to keep update frequency lower than other brands owing to the same reason.
Click to expand...
Click to collapse
How not being agree with everything you said, it's just the same i was thinking
K.khiladi said:
Ok. Some points from me also.
1. The current settings screen is very cluttered and the use of colorful icons makes it look childish IMO. I would suggest if going forward with the Oreo update they keep it closer to stock and reduce the clutter in settings.
Also if they can keep the notifications and QS area more stock.
Overall, more closer to stock UI.
2. Addition of equaliser and improvement in loudness over earphones.
3. A slight improvement in sharpness in rear camera. Also improvement in low light shots.
Can't think of anymore because others are already listed.
Sent from my Honor 8 pro using Tapatalk
Click to expand...
Click to collapse
Good inputs there.
Just a few points from my limited knowledge:
1. Oreo as such groups settings menu into refined categories, so that is expected going forward. However, there would be some variations, which they might not agree to eliminate as it is subjective.
2. I was asked by R&D team as to what are all the immediate concerns, few days back. I had written to them set of 7-8 points including double tap to wake, Camera optimizations(front mainly), audio output betterment and interface availability for fine tuning etc. So, thats already sent across. Insisted them to send it along with the next OTA.
3. In the PDF I have attached, as well as in the Chennai meet, we pointed out how amazing the rear optics are as well as the little inconsistencies existing. Better edge detection algo for identifying spaces between two subjects separated by a short distance, general improvement were highlighted in that. They did nod for that , not sure when it would come as an update.
Nevertheless, cameras in this phone are a thing of beauty and very closely rival some entry n mid range DSLRs.
---------- Post added at 10:02 PM ---------- Previous post was at 10:00 PM ----------
shashank1320 said:
Couldn't agree more bro. And Huawei needs to understand from user perspective. Hardware wise devices are good but if no custom development then people opt for redmi, Moto etc.
Click to expand...
Click to collapse
Exactly. Atleast if xda development was active, we could see some security patches, upgrades from ported Mods n stuff, but with the removal of firmware sources, they are looking at sealing their own fate.
---------- Post added at 10:04 PM ---------- Previous post was at 10:02 PM ----------
shashank1320 said:
Thanks. Hope Huawei consider all these points.
We will collect and raise all to them in next meet up.
Click to expand...
Click to collapse
Pl. see my post above. I have covered most of them in my personal conversations with Honor India. Hope to see it being implemented soon.
K.khiladi said:
Also if they can keep the notifications and QS area more stock.
Overall, more closer to stock UI.
Click to expand...
Click to collapse
That's what I exactly think of, leave the notifications in panel and lockscreen like stock
amulbaby said:
Just a few points from my limited knowledge:
1. Oreo as such groups settings menu into refined categories, so that is expected going forward. However, there would be some variations, which they might not agree to eliminate as it is subjective.
Click to expand...
Click to collapse
Thanks and I understand that. They will surely rearrange settings because Oreo has done that.
What I actually wanted to say is that the icons used in the settings are somewhat childish. It would be great if they are somewhat more professional looking.
I can live with that QS area but Emui curves the corners of the notifications and that somewhat doesn't fit with the QS panel above which doesn't have curved corners.
So, it's sort of a mismatch. If they could remove those curved corners from notifications, would be great.
Sent from my Honor 8 pro using Tapatalk
One big point for them. DITCH THE IOS LOOK.
Sent from my DUK-L09 using XDA Labs
sniperlife:D said:
One big point for them. DITCH THE IOS LOOK.
Sent from my DUK-L09 using XDA Labs
Click to expand...
Click to collapse
I feel they have already ditched that a lot. They did a commendable job on nougat.
Sent from my Honor 8 pro using Tapatalk
K.khiladi said:
I feel they have already ditched that a lot. They did a commendable job on nougat.
Click to expand...
Click to collapse
Nah. Since EMUI 4, they are trying really hard to mimic ios. Unlike Touchwiz, ZenUI and others, they have a distinct look.
Sent from my DUK-L09 using XDA Labs
sniperlife:D said:
Nah. Since EMUI 4, they are trying really hard to mimic ios. Unlike Touchwiz, ZenUI and others, they have a distinct look.
Sent from my DUK-L09 using XDA Labs
Click to expand...
Click to collapse
Well, different opinions.
Nougat version of emui is a lot better than Kitkat and Marshmallow ones.
There's still a lot of space for improvement though
Sent from my Honor 8 pro using Tapatalk
These are a few mods that I made recently in order to improve a few bits of our device. This includes some build.prop tweaks, optimized camera libs, and VR support.
Little Mix => enabling Qualcomm Adaptive Display, Miracast (needing a lib from Pixel or Pixel 2 so if u got one DM me), and faster fingerprint detection.
Optimized Camera Libraries => really just self-explanatory, also enables 60fps and 100% quality JPEG photos.
Snappy Prop => build.prop additions, this is a collection of many to enable device features your ROM may not even have. THIS IS MOSTLY USELESS. I got bored and tried porting Snappy Prop to see it's effect that's all.
Daydream => Enables VR support and also improves thermal responsiveness.
Charging Boost => Allows fast charging at higher temperatures, still safe.
White Boot => A Watchdogs inspired bootanimation with a white background. For those Pixel lovers out there. This took 20 mins to upload. XDA is slow.
If anyone wasn't credited for something prove you made it and I'll add ya [almost] instantly to the list below.
Code:
Changelog:
Snappy Prop - removed props relating to rotation
Optimized Camera Libraries - correct placement of camera libs
Charging Boost - an actual magisk module this time :p
Thanks to:
@Miustone for build prop stuff
@ravinder0003 for the charging config
Charging boost doesn't seem to work, Magisk Manager says it's not a Magisk Module.
TemperateRoot said:
Charging boost doesn't seem to work, Magisk Manager says it's not a Magisk Module.
Click to expand...
Click to collapse
Thanks mate. I forgot to upload the Magisk Module of that one abs I uploaded the flashable :silly:
1. Flashing the 'Snappy Prop.zip' module results in a vendor image mismatch message on the screen after booting into system. The message says that 'bullhead-opm3.171019.016' vendor image should be installed. 'bullhead-opm3.171019.016' is the current installed vendor image. After disabling the module in Magisk and rebooting, the messages no longer displays.
2. Flashing the 'White Boot.zip' modules causes the screen to flash repeatedly displaying geometric shapes and messages during the boot process. Disabling the module in Magisk and rebooting, the boot process is normal displaying first the Android logo and the AICP logo before displaying the lock screen.
Flashing the other four modules, does not result in any errors or problems with the phone during the flashing, boot up, or operation of the phone.
Running AICP 13.1 bullhead+TWRP+Magisk+Open GApps+ElementalX-Kernel on the Nexus 5X LG-H790.
dynamo1950 said:
1. Flashing the 'Snappy Prop.zip' module results in a vendor image mismatch message on the screen after booting into system. The message says that 'bullhead-opm3.171019.016' vendor image should be installed. 'bullhead-opm3.171019.016' is the current installed vendor image. After disabling the module in Magisk and rebooting, the messages no longer displays.
2. Flashing the 'White Boot.zip' modules causes the screen to flash repeatedly displaying geometric shapes and messages during the boot process. Disabling the module in Magisk and rebooting, the boot process is normal displaying first the Android logo and the AICP logo before displaying the lock screen.
Flashing the other four modules, does not result in any errors or problems with the phone during the flashing, boot up, or operation of the phone.
Running AICP 13.1 bullhead+TWRP+Magisk+Open GApps+ElementalX-Kernel on the Nexus 5X LG-H790.
Click to expand...
Click to collapse
well for 1) you are correct I will try to fix this matter tomorrow morning
for 2) the flashing geometric shapes... that's the boot animation for my module it's the point of the module :silly: (if you haven't played the game WatchDogs you probably won't get the reference)
PS - nice to see you're also using AICP
LazerL0rd said:
well for 1) you are correct I will try to fix this matter tomorrow morning
for 2) the flashing geometric shapes... that's the boot animation for my module it's the point of the module :silly: (if you haven't played the game WatchDogs you probably won't get the reference)
PS - nice to see you're also using AICP
Click to expand...
Click to collapse
@LazerL0rd - Just wondering if you are going to fix the matter with the 'Snappy Prop.zip'? Also curious about what features it attempts to enable in the Nexus 5X
The other zips, excluding 'White Boot.zip', have been enabled on the phone for a week or so and no problems to report :good::good:
dynamo1950 said:
@LazerL0rd - Just wondering if you are going to fix the matter with the 'Snappy Prop.zip'? Also curious about what features it attempts to enable in the Nexus 5X
The other zips, excluding 'White Boot.zip', have been enabled on the phone for a week or so and no problems to report :good::good:
Click to expand...
Click to collapse
Nice, well as I said white boot was a boot animation changer but hey it doesn't seem to be your thing.
I'll upload a fix hopefully. Well it attempts to enable a plethora of build props and some work some don't. I've had a prop of useful options I've collected over a year and added them there. It's universal so works on any second device.
I wonder how hot your device gets in VR, though?
LazerL0rd said:
Nice, well as I said white boot was a boot animation changer but hey it doesn't seem to be your thing.
I'll upload a fix by today hopefully. Well it attempts to enable a plethora of build props and some work some don't. I've had a prop of useful options I've collected over a year and added them there. It's universal so works on any second device.
I wonder how hot your device gets in VR, though?
Click to expand...
Click to collapse
When running Daydream VR apps, the phone heats up. The center of the back feels the hottest.
With the case off the phone, I insert it into a Google Daydream View 2017 headset. With a magnesium heat sink, the headset draws the heat from the phone quite well. The VR experience on the Nexus 5X has some lag, stutter and a bit blurry at high resolution. Otherwise, it offers a feel for the VR experience.
dynamo1950 said:
When running Daydream VR apps, the phone heats up. The center of the back feels the hottest.
With the case off the phone, I insert it into a Google Daydream View 2017 headset. With a magnesium heat sink, the headset draws the heat from the phone quite well. The VR experience on the Nexus 5X has some lag, stutter and a bit blurry at high resolution. Otherwise, it offers a feel for the VR experience.
Click to expand...
Click to collapse
Ah great, I haven't had my hands on a headset yet but that's great. With an OC'd kernel and 4GB RAM mod that should be pretty good (as long as you don't have the bootloop lol.
How did you apply the heatsink?
LazerL0rd said:
Ah great, I haven't had my hands on a headset yet but that's great. With an OC'd kernel and 4GB RAM mod that should be pretty good (as long as you don't have the bootloop lol.
How did you apply the heatsink?
Click to expand...
Click to collapse
Sorry for misunderstanding. The heatsink is in the Google Daydream View headset. Also, do not have the 4GB RAM mod. My Nexus 5x phones are unmodified hardware.
As the module is now, displaying the Vendor image mismatch on boot, does it still work as intended? Can the vendor image mismatch error message be ignored? Thanks.......
---------- Post added at 06:35 PM ---------- Previous post was at 06:25 PM ----------
dynamo1950 said:
Sorry for misunderstanding. The heatsink is in the Google Daydream View headset. Also, do not have the 4GB RAM mod. My Nexus 5x phones are unmodified hardware.
As the module is now, displaying the Vendor image mismatch on boot, does it still work as intended? Can the vendor image mismatch error message be ignored? Thanks.......
Click to expand...
Click to collapse
In addition, for your info, both of my Nexus 5X phones began intermittent boot looping (sticking on Android logo at bootup) after 18 months + of usage this past January. They would need multiple hard resets using the power button to successfully boot into system.
I sent them, one at a time, to the LG Wireless repair center on RMA's. To my surprise, LG repaired each phone by replacing the main board. If I understand correctly, LG has extended its warranty to about 30 months from date of purchase to cover this kind of failure. :good:
There was no cost involved, just the one-way shipping to the repair facility. Again, I did not purchase any extended warranty at time of purchase. Both phones now work fine without that boot loop issue.
dynamo1950 said:
Sorry for misunderstanding. The heatsink is in the Google Daydream View headset. Also, do not have the 4GB RAM mod. My Nexus 5x phones are unmodified hardware.
As the module is now, displaying the Vendor image mismatch on boot, does it still work as intended? Can the vendor image mismatch error message be ignored? Thanks.......
Click to expand...
Click to collapse
Yeah it can be ignored, it's just a wild prop causing it. To be honest I don't use it myself but some people like having every "useful" prop available enabled for them. I personally use it for debugging when a port of mine doesn't work so that I know whether a prop line caused it.
dynamo1950 said:
In addition, for your info, both of my Nexus 5X phones began intermittent boot looping (sticking on Android logo at bootup) after 18 months + of usage this past January. They would need multiple hard resets using the power button to successfully boot into system.
I sent them, one at a time, to the LG Wireless repair center on RMA's. To my surprise, LG repaired each phone by replacing the main board. If I understand correctly, LG has extended its warranty to about 30 months from date of purchase to cover this kind of failure. :good:
There was no cost involved, just the one-way shipping to the repair facility. Again, I did not purchase any extended warranty at time of purchase. Both phones now work fine without that boot loop issue.
Click to expand...
Click to collapse
They didn't for me. LG declined to fix mine due to having a third party repair. I may aswell buy the 4GB RAM mainboard and use that lol.
Can you just share magisk module for miracast enablement for Nexus 6p on Oreo 8.1
Appreciate your hard work on creating these mods
ashu347 said:
Can you just share magisk module for miracast enablement for Nexus 6p on Oreo 8.1
Appreciate your hard work on creating these mods
Click to expand...
Click to collapse
Little Mix zip - that's the one you want
and thanks :laugh:
Awesome...just installed and it works. Nexus 6p ..now enabled to cast ..
LazerL0rd said:
Little Mix zip - that's the one you want
and thanks :laugh:
Click to expand...
Click to collapse
Installed with mm no issues pixel c 8.1 mm 16.4
Miracast originally worked out of the box but stopped on 8
You ever get those pixel libs?
SPL Dust said:
Installed with mm no issues pixel c 8.1 mm 16.4
Miracast originally worked out of the box but stopped on 8
You ever get those pixel libs?
Click to expand...
Click to collapse
Na, no one ever sent it to me . I'd be grateful if anyone can cause Little Mix uses a prop line to tell system to look for that lib when casting.
So far, so good
LazerL0rd said:
These are a few mods that I made recently in order to improve a few bits of our device. This includes some build.prop tweaks, optimized camera libs, and VR support.
Little Mix => enabling Qualcomm Adaptive Display, Miracast (needing a lib from Pixel or Pixel 2 so if u got one DM me), and faster fingerprint detection.
Optimized Camera Libraries => really just self-explanatory, also enables 60fps and 100% quality JPEG photos.
Snappy Prop => build.prop additions, this is a collection of many to enable device features your ROM may not even have. THIS IS MOSTLY USELESS. I got bored and tried porting Snappy Prop to see it's effect that's all.
Daydream => Enables VR support and also improves thermal responsiveness.
Charging Boost => Allows fast charging at higher temperatures, still safe.
White Boot => A Watchdogs inspired bootanimation with a white background. For those Pixel lovers out there. This took 20 mins to upload. XDA is slow.
If anyone wasn't credited for something prove you made it and I'll add ya [almost] instantly to the list below.
Code:
Changelog:
Snappy Prop - removed props relating to rotation
Optimized Camera Libraries - correct placement of camera libs
Charging Boost - an actual magisk module this time :p
Thanks to:
@Miustone for build prop stuff
@ravinder0003 for the charging config
Click to expand...
Click to collapse
Will you be well for now waiting for updates and improvements please and thank you I would like you to specify more about your SNAPPY PRO module and in depth all the modules for which they serve Since your summary is good but I need more depth if I make myself understand I hope you take it in the best way and apologies for my English I am using a translator. I'm using the modules In normal Motorola G4 with 2GB of RAM 8 cores and Android 8.0.1 with magisk root
richardontaneda88 said:
Will you be well for now waiting for updates and improvements please and thank you I would like you to specify more about your SNAPPY PRO module and in depth all the modules for which they serve Since your summary is good but I need more depth if I make myself understand I hope you take it in the best way and apologies for my English I am using a translator. I'm using the modules In normal Motorola G4 with 2GB of RAM 8 cores and Android 8.0.1 with magisk root
Click to expand...
Click to collapse
I’m probably gonna close down this thread and make individual threads for the good modules here. A lot of this was experimental learning stuff for me and it’s embarrassing even some of the dumb stuff I did. Like “Snappy Prop” lmao.
Thanks for your reply tho.
LazerL0rd said:
I’m probably gonna close down this thread and make individual threads for the good modules here. A lot of this was experimental learning stuff for me and it’s embarrassing even some of the dumb stuff I did. Like “Snappy Prop” lmao.
Thanks for your reply tho.
Click to expand...
Click to collapse
You're the one who knows better. Please, before closing this thread, provide the links for the new threads. Thanks!
Hey Folks, while working on My next Snappatch Version was i able to fix the biggest Problems on the XZ Premium which should also affect other Xperias. Here are the main Points:
-Camera Noise (Solved)
-Display Quality (Solved)
-Audio Output Quality (Solved)
-Microphone Handling (Solved)
In conlcusion:
I added and enabled some Camera Services and Functions to enhance the Quality and to allow full Google Camera Mod Support.
I added and enabled Display Services and Functions to deliver a more Natural Output besides HDR Support and Adaptive Backlight capabilities.
I added and enabled Audio Services, Functions and Libraries from Qualcomm and SONY Oreo Firmwares to enhance the Output Quality over all Sources like Videos, Music and the main System.
Last but not least better Microphone Handling. Adapted and ehanced from many Android Devices and Qualcomm Documentations to deliver better Recognition and Input Quality over both Mics on top and bottom of the Device.
Nothing against switching from Stock to AOSP anymore. The benefits of Snappatched AOSP over Stock are huge. Latest SDK, full Substratum Support, better Audio and Visual Quality (In and Output), better Performance (Shadowgun Ledgends on Ultra - 60FPS, No heat, no glitches), more freedom of UI Layouts, better App Support, faster Storage Speeds, newer Kernel, Smoother UI, Adaptive Icon Support, Pixel Features and so on. The Snappatch for the XZP is coming soon and i Hope i can raise the Interest on AOSP on Xperias with this!
Forget Stock! This is the next Level! Love My XZP now...
Stay tuned and try it by Yourself!
I hope that you are right. But i want to try it very bad want i want a good working aosp! I CANT WAIT!!!
I'm on 8142 dual SIM I'm willing to try too
:cyclops: Ufff!!! sounds amazing !!! can't wait to test it
G8142 here also. Can't wait to try this out
I think I will unlock my bootloader ?
Can't wait for some reviews
I would really like to get some advanced Feedback and compares between Stock and AOSP. RAW alone should be worth the Bootloader unlock and going away from Stock. SONY does a really great Job on the Sources for our AOSP Bases and everything runs really well compared to other Devices like from LG. One Thing that really bothers Me is the buggy TWRP on our XZP. CPU Temp isn't showing right, MTP fails 90% of the Time and AROMA has a Displaying Bug. Since the Snappatch is coming with My own crafted AROMA Installer will we face a invisible Utility, but i will make a Video showing how to easily flash the Patch anyways on our Devices (Side by Side with working AROMA on the Axon 7).
Hope @Myself5 can solve the TWRP Issues one Day, and that more Users will pay attention to him and his Work on our Forums! Thanks a lot Mate for contributing that much to our Devices, and Sorry for People like this "FartyParty" Guy! Much respect for You, i know how it feels to be on XDA sometimes...
Miustone said:
Hey Folks, while working on My next Snappatch Version was i able to fix the biggest Problems on the XZ Premium which should also affect other Xperias. Here are the main Points:
-Camera Noise (Solved)
-Display Quality (Solved)
-Audio Output Quality (Solved)
-Microphone Handling (Solved)
In conlcusion:
I added and enabled some Camera Services and Functions to enhance the Quality and to allow full Google Camera Mod Support.
I added and enabled Display Services and Functions to deliver a more Natural Output besides HDR Support and Adaptive Backlight capabilities.
I added and enabled Audio Services, Functions and Libraries from Qualcomm and SONY Oreo Firmwares to enhance the Output Quality over all Sources like Videos, Music and the main System.
Last but not least better Microphone Handling. Adapted and ehanced from many Android Devices and Qualcomm Documentations to deliver better Recognition and Input Quality over both Mics on top and bottom of the Device.
Nothing against switching from Stock to AOSP anymore. The benefits of Snappatched AOSP over Stock are huge. Latest SDK, full Substratum Support, better Audio and Visual Quality (In and Output), better Performance (Shadowgun Ledgends on Ultra - 60FPS, No heat, no glitches), more freedom of UI Layouts, better App Support, faster Storage Speeds, newer Kernel, Smoother UI, Adaptive Icon Support, Pixel Features and so on. The Snappatch for the XZP is coming soon and i Hope i can raise the Interest on AOSP on Xperias with this!
Forget Stock! This is the next Level! Love My XZP now...
Stay tuned and try it by Yourself!
Click to expand...
Click to collapse
dude send your paypal account, dinner on me <3
cant wait to see this baby up and running
Yes I agree we all should donate for all the hard work and time invested yes send me your PayPal address
Miustone said:
I would really like to get some advanced Feedback and compares between Stock and AOSP. RAW alone should be worth the Bootloader unlock and going away from Stock. SONY does a really great Job on the Sources for our AOSP Bases and everything runs really well compared to other Devices like from LG. One Thing that really bothers Me is the buggy TWRP on our XZP. CPU Temp isn't showing right, MTP fails 90% of the Time and AROMA has a Displaying Bug. Since the Snappatch is coming with My own crafted AROMA Installer will we face a invisible Utility, but i will make a Video showing how to easily flash the Patch anyways on our Devices (Side by Side with working AROMA on the Axon 7).
Hope @Myself5 can solve the TWRP Issues one Day, and that more Users will pay attention to him and his Work on our Forums! Thanks a lot Mate for contributing that much to our Devices, and Sorry for People like this "FartyParty" Guy! Much respect for You, i know how it feels to be on XDA sometimes...
Click to expand...
Click to collapse
Man this is wonderful a i cant wait for your patch,but twrp,i remember you created a patch called light patch and aroma installer on that worjs with our device,[email protected] he created carbon rom and twrp for G8141 so carbon works for us but twrp not.
madshark2009 said:
dude send your paypal account, dinner on me <3
cant wait to see this baby up and running
Click to expand...
Click to collapse
grodri19721 said:
Yes I agree we all should donate for all the hard work and time invested yes send me your PayPal address
Click to expand...
Click to collapse
That makes Me very glad and proud, Thanks Guys! Sadly can i not use PayPal, but i would really appreciate if People would Donate to My Mother. She had a Hard Time and is now caring My Grandma which is diseased. I think she would be very thankful and happy about some Donations based on My Work here. I will talk to her and if it's ok do i share her Paypal Address on My Thread or Signatur somehow. Think that would be a nice Idea if You're also ok with that!
Blackghosthm said:
Man this is wonderful a i cant wait for your patch,but twrp,i remember you created a patch called light patch and aroma installer on that worjs with our device,[email protected] he created carbon rom and twrp for G8141 so carbon works for us but twrp not.
Click to expand...
Click to collapse
Strange. I Googled a lot about this and this was always a Issues with some TWRP Recoveries. Most of the Time did it helped to use older TWRP Images but the last one gives just a Black Screen after booting into it. I will test a Copy of My old Light Patch again and take a look on whats different! Thanks for the Hint!
Miustone said:
That makes Me very glad and proud, Thanks Guys! Sadly can i not use PayPal, but i would really appreciate if People would Donate to My Mother. She had a Hard Time and is now caring My Grandma which is diseased. I think she would be very thankful and happy about some Donations based on My Work here. I will talk to her and if it's ok do i share her Paypal Address on My Thread or Signatur somehow. Think that would be a nice Idea if You're also ok with that!
Strange. I Googled a lot about this and this was always a Issues with some TWRP Recoveries. Most of the Time did it helped to use older TWRP Images but the last one gives just a Black Screen after booting into it. I will test a Copy of My old Light Patch again and take a look on whats different! Thanks for the Hint!
Click to expand...
Click to collapse
If it possible release your patch for less than 5 hours because my internet time is going to end.please.
How was RAW support achieved?
From what I've seen, this wasn't possible before because there were no drivers that enabled that with the used camera chip.
And there's still one thing missing; SloMo support. Is there a chance this can be added as well?
Blackghosthm said:
If it possible release your patch for less than 5 hours because my internet time is going to end.please.
Click to expand...
Click to collapse
I had trouble with the Camera Configs (Camera not starting anymore), but solved it and added more of them. Last remaining Problem are Issues with Google Service Audio (Music and Video not playing due to failing Audio Configs). Think i need more Time to solve this, but the release is close...
4rz0 said:
How was RAW support achieved?
From what I've seen, this wasn't possible before because there were no drivers that enabled that with the used camera chip.
And there's still one thing missing; SloMo support. Is there a chance this can be added as well?
Click to expand...
Click to collapse
It's all there on AOSP. Camera2 API is supported but not configured right (There are X Lines for the Cameras), i've seen the same on the Z1 and Z3 (https://forum.xda-developers.com/cr...ussion-development-custom-rom-t3479108/page11) some Years back, and i was sure it's all depending on this right now. Other Xperias may have the same Camera Problems since AOSP is coming with just the barely minimum of Build Properties and Configs. That's also the Case on the most other Devices and AOSP based ROM and one of the Reasons for doing My Patch. Some missing Things are causing Issues (Like Microphone Problems), and others do just bring a lack of Features (Like with the Camera and Display, Audio, etc.).
It's pretty Time intense to test all this Entries and Values but it's really worth the Time. And if i would do a OS would i start with that Things before changing the Kernel and adding ROM Features, but i can only talk for Me. Not sure how much Time ROM Devs put into building of AOSP for the own Devices, but i work for sure at least 40 Hours on One Major Release of My Patch (Including copying, flashing, testing and editing).
AROMA was also really Time Intense but i removed the Installer over Night and edited the Updater Script to flash the recommended Options without it. Here is a little List of what gets flashed:
-Original Oreo Pixel Bootanimation
-Original Oreo Pixel Ringtones, Alarms, Notifications
-HTC U 11 UI Sounds, Ringtones, Alarms, Notifications
-Prop Patch (Including many changes and Configs)
-Snappatch Core System (Including the mainly needed Content)
-Snappatch Audio System (Based on XZ Premium Oreo Stock)
-Snappatch Emojis (EmojiOne replacement Font)
-Magisk Stable V16
-Busybox with many Applets, SElinux & Magisk Support
-GApps (Barely minimum Set)
And that's it for now. It includes all of the Features of the Patch, less optional but i can ensure a great Experience with this Setup! Like said am i now about to fix the last Bugs which are Audio Config related and after that will come the Thread with the new Release. Hope You will like it Folks!
BR
Stupid xda -__-
Keep up the good work brother
I'm done for now! Release is in the next 24 Hours...
Changelog can be found here: https://docs.google.com/document/d/1ak5DsenMjuSyypPBAjQact6MhtsE2MRFlvCHLTn9uHA/edit?usp=sharing
I removed the Audio System for now due to Issues with Xperias AOSP ROMs but i'll work on it again after releasing the actual Patch. Sounds already a lot better even without the replacement Libs and Configs! Stay tuned...
Sony 8142 dual SIM ?? Please
grodri19721 said:
Sony 8142 dual SIM ?? Please
Click to expand...
Click to collapse
Yes
can't wait to have a try.
bro you've contributed a lot to our device
Thank you so much!
Hi folks
As I see Android 10 is already available for India region.
Anyone updated and can share the experience ?
There isn't much change besides the usual Andorid 10 features. Little change in the design here and there, Camera app is redesigned but no change in picture quality. Gesture navigation is available. You have a cool 'Sensors off' quick toggle which turns off the senors for your needs. Focus mode which helps you 'avoid distraction from your phone and keep your life in focus'. Probably the most important feature is Systemwide forced dark mode. Better one handed experience. Also little more fluid animations. Nothing else.
What about battery life ? Have they spoiled that or it is still good ?
pabgar said:
Hi folks
As I see Android 10 is already available for India region.
Anyone updated and can share the experience ?
Click to expand...
Click to collapse
Wrong post, you must post it on "QUESTIONS & ANSWERS" group
Futuristic_Goo said:
There isn't much change besides the usual Andorid 10 features. Little change in the design here and there, Camera app is redesigned but no change in picture quality. Gesture navigation is available. You have a cool 'Sensors off' quick toggle which turns off the senors for your needs. Focus mode which helps you 'avoid distraction from your phone and keep your life in focus'. Probably the most important feature is Systemwide forced dark mode. Better one handed experience. Also little more fluid animations. Nothing else.
Click to expand...
Click to collapse
I've updated this morning and everything is good, including battery.
pabgar said:
What about battery life ? Have they spoiled that or it is still good ?
Click to expand...
Click to collapse
Battery life is same (good). Except that systemwide dark mode would probably increase battery life.
Did someone from Germany got the Update?
And can you use good Lock Apps like navstar?
With Android 9 IT didnt Work on the m30s.
Any non indian variant who got the android 10 update?
My model number is SM-M307FN.
I mentioned this in another thread but I feel it deserves its own thread. Until 1.1.4 hit, I was really enjoying the cameras on the Nothing phone. But they really mucked up the main camera after the update. They brightened up the image and the HDR is worse now as well. Others have mentioned it in the 1.1.4 thread, and there are even more who have mentioned it in the Nothing Phone reddit forum.
I have a standard pic I take to test my smartphone cameras. It's a great picture to test the exposure and dynamic range. I take a picture of my fireplace from inside my family room. To either side of my fireplace are windows where you can see blue sky and the back yard. On 1.1.3 the pictures were BEAUTIFUL. The inside of the family room was properly exposed and the brilliant blue sky and back yard could be seen thru the windows. Now after the update to 1.1.4 the family room is too bright/overexposed and the back yard and blue sky thru the windows are totally washed out. You can barely make out the blue in the sky or any back yard detail. HDR is wonky now. This SUCKS. I left feedback on the Nothing feedback form. Hopefully they fix it.
So just yo be clear, only the HDR algorithm was affected? If it's off, is there a difference?
Same here.Washed .Oversaturated noise oversahrpened.
" If it's off, is there a difference?"
No options on/off full automatic.
Have to reported to developers?
miris83 said:
Have to reported to developers?
Click to expand...
Click to collapse
He has done so already and so should everyone else
Nyssa1104 said:
He has done so already and so should everyone else
Click to expand...
Click to collapse
Sorry, there should have been "Have you", not "Have to". I also report bugs if there is no solution in here or anywhere else but I also know the majority usually starts here and waits for someone else's reports. As I have not received the update yet, I cannot give any feedback on this.
miris83 said:
Sorry, there should have been "Have you", not "Have to". I also report bugs if there is no solution in here or anywhere else but I also know the majority usually starts here and waits for someone else's reports. As I have not received the update yet, I cannot give any feedback on this.
Click to expand...
Click to collapse
Yes I reported to the Nothing via their official feedback form located here:
Issues and New Features Form
Please fill in this form to report issues and suggest new features.
forms.gle