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!
Related
Just saw this on the Android subreddit, wanted to share with you all! the download links for entire Xperia Z5 Family are provided in the following link:
https://plus.google.com/+EvanAndersonA/posts/72TLZMj4K5S
Bugs/Broken Features (That I've found):
- Front Camera has color problems (Similar to the CyanogenMod 13 Rom Rear Camera)
- Back Camera is flipped upside down (Very difficult to actually take pictures), but color is fine and focus seems fine (limited testing)
- No Fingerprint Sensor
The following Zip has the assert line removed from updater-script so it won't check your device before flashing. BE WARNED, if your device is not the Z5 Premium Satsuki, flashing this could break your device.
https://drive.google.com/file/d/0BwjsVhbtLaJaNTJTSDlqYlh0YXM/view?usp=sharing
DISCLAIMER: I am in no way affiliated with the development group, don't ask for updates or anything of the sort.
I get "error 7" when installing this zip
Snake07 said:
I get "error 7" when installing this zip
Click to expand...
Click to collapse
Happened to me too, its because of the twrp image we are using (Had the same problem when flashing Resurrection Remix). I removed the assert line from updater-script (hacky fix) so that you can straight up flash it (worked on mine), but make sure your device is actually Xperia Z5 Premium Satsuki. If it isn't you might risk soft-bricking your device if not worst. I will not be held responsible for any mistake.
https://drive.google.com/file/d/0BwjsVhbtLaJaNTJTSDlqYlh0YXM/view?usp=sharing
exvargos said:
Happened to me too, its because of the twrp image we are using (Had the same problem when flashing Resurrection Remix). I removed the assert line from updater-script (hacky fix) so that you can straight up flash it (worked on mine), but make sure your device is actually Xperia Z5 Premium Satsuki. If it isn't you might risk soft-bricking your device if not worst. I will not be held responsible for any mistake.
https://drive.google.com/file/d/0BwjsVhbtLaJaNTJTSDlqYlh0YXM/view?usp=sharing
Click to expand...
Click to collapse
How does the rom feel is it stable?
Does BT talk and audi work?
And does the fingerprint work?
claesr said:
How does the rom feel is it stable?
Does BT talk and audi work?
And does the fingerprint work?
Click to expand...
Click to collapse
BT Audio works fine, no stuttering at all. Can't test talk, don't have a BT headset.
Like I said fingerprint doesn't work at the moment, I think it has to do with the kernel they packaged with it. Fingerprint support might cane in a later update seeing as how the other devices with paranoid support it.
It's super stable, the animations are really fluid, I haven't hit any bugs or crashes.
It doesn't seem to support Quick Charge out of the box, might again be a kernel thing (maybe they used more or less the same one for the whole xperia family?).
I love this ROM, heavily considering staying permanently on it just to see where they take it (at least until Sony releases Nougat). It comes very light, boots in under a minute (after first boot which took maybe 10-15 minutes). Downside again is camera isn't much better than the cyanogenmod/resurrectionremix Roms (if you can take pictures upside down then you'll be fine).
It has cyanogenmod theme engine (and support for layers) which is pretty awesome, only thing is I'd recommend replacing the stock launcher as it is very limited.
That's all I can think of at the moment.
TLDR: love this ROM, best to date other than some bugs/missing features. This is more stable than the ps4 after all it's stability updates (never experienced lag).
exvargos said:
BT Audio works fine, no stuttering at all. Can't test talk, don't have a BT headset.
Like I said fingerprint doesn't work at the moment, I think it has to do with the kernel they packaged with it. Fingerprint support might cane in a later update seeing as how the other devices with paranoid support it.
It's super stable, the animations are really fluid, I haven't hit any bugs or crashes.
It doesn't seem to support Quick Charge out of the box, might again be a kernel thing (maybe they used more or less the same one for the whole xperia family?).
I love this ROM, heavily considering staying permanently on it just to see where they take it (at least until Sony releases Nougat). It comes very light, boots in under a minute (after first boot which took maybe 10-15 minutes). Downside again is camera isn't much better than the cyanogenmod/resurrectionremix Roms (if you can take pictures upside down then you'll be fine).
It has cyanogenmod theme engine (and support for layers) which is pretty awesome, only thing is I'd recommend replacing the stock launcher as it is very limited.
That's all I can think of at the moment.
TLDR: love this ROM, best to date other than some bugs/missing features. This is more stable than the ps4 after all it's stability updates (never experienced lag).
Click to expand...
Click to collapse
Nice thanks for the information i love PA roms too but i will want a little for the Fingerprint, then i will switch over
Google play store not working closes immediately tried from lucky patcher and from many other pages if there is a working one please link it thanks )
Gesendet von meinem E6853 mit Tapatalk
xElectroKingx said:
Google play store not working closes immediately tried from lucky patcher and from many other pages if there is a working one please link it thanks )
Gesendet von meinem E6853 mit Tapatalk
Click to expand...
Click to collapse
Flash OpenGAPPS after you've flashed the PA zip. Choose ARM64 and Android 6.0 on the OpenGAPPS website, the zip file size is up to you, read the description for each one until you find the one that's for you. I like to install the stock version for the "Nexus experience"
If it still doesn't work flash everything after you made a factory reset.
PS. Luckypatcher is something that's against the XDA rules, never mention it again, I'm just looking out for you. Read XDA rules for more info.
Sent from my Z5 Premium using XDA Labs
KbaB.BroS said:
Flash OpenGAPPS after you've flashed the PA zip. Choose ARM64 and Android 6.0 on the OpenGAPPS website, the zip file size is up to you, read the description for each one until you find the one that's for you. I like to install the stock version for the "Nexus experience"
If it still doesn't work flash everything after you made a factory reset.
PS. Luckypatcher is something that's against the XDA rules, never mention it again, I'm just looking out for you. Read XDA rules for more info.
Sent from my Z5 Premium using XDA Labs
Click to expand...
Click to collapse
No luck didn't work..
Gesendet von meinem E6853 mit Tapatalk
xElectroKingx said:
No luck didn't work..
Gesendet von meinem E6853 mit Tapatalk
Click to expand...
Click to collapse
Try wiping data, system, cache and dalvik then flash pa and OpenGAPPS and reboot
Sent from my Z5 Premium using XDA Labs
Solution: flash rom / flash nano gapps /wipe data / reboot
Gesendet von meinem Xperia Z5 Premium (AOSPA) mit Tapatalk
Excellent!
Installed / Rooted / Xposed
Pros:
Insanely snappy
Great battery life
Scored a 65720 on Antutu (im sure this will go up with kernel enhancements)
Bluetooth works flawlessly
Cons:
Headphones aren't detected when plugged in (Using SoundAbout as a work around)
front camera has blue hue (i read a fix was put out for the camera drivers? So maybe it will be fixed soon!)
back camera is flipped/mirrored
WannaB101 said:
Installed / Rooted / Xposed
Pros:
Insanely snappy
Great battery life
Scored a 65720 on Antutu (im sure this will go up with kernel enhancements)
Bluetooth works flawlessly
Cons:
Headphones aren't detected when plugged in (Using SoundAbout as a work around)
front camera has blue hue (i read a fix was put out for the camera drivers? So maybe it will be fixed soon!)
back camera is flipped/mirrored
Click to expand...
Click to collapse
Headphones don't work for you? Weird they work fine for me. My battery life was pretty good at the beginning, but now i only get 2-3 hours sot. No root or Xposed.
Amazing
I'm really excited to flash this ROM thus the fingerprint issue is keeping me from doing it any news about this issue?
nHorus said:
I'm really excited to flash this ROM thus the fingerprint issue is keeping me from doing it any news about this issue?
Click to expand...
Click to collapse
Not that I know of. There hasn't been any updates released (text updates in development it actual software updates) since the initial release.
exvargos said:
Not that I know of. There hasn't been any updates released (text updates in development it actual software updates) since the initial release.
Click to expand...
Click to collapse
thank you then i'll have to wait
Firstly, KICKASS ROM! A few hicksup here and there to get it running. Got the Error 7, then when I successfully flashed it, I lost my root and then eventually when I got everything working, it wasnt charging. After a couple of reboots, it is working fine. Missing the fingerprint sensor. So far, so good.
X0LARIUM said:
Firstly, KICKASS ROM! A few hicksup here and there to get it running. Got the Error 7, then when I successfully flashed it, I lost my root and then eventually when I got everything working, it wasnt charging. After a couple of reboots, it is working fine. Missing the fingerprint sensor. So far, so good.
Click to expand...
Click to collapse
Yeah this rom is pretty awesome!! If you want root you have to flash it after you flash the rom. I only wish they had a more stable update schedule.
2 issues:
Camera is completely gone (calibration is off, blue tone etc)
Doesn't charge without restarting
1 Feedback:
Fingerprint doesn't work
exvargos said:
Just saw this on the Android subreddit, wanted to share with you all! the download links for entire Xperia Z5 Family are provided in the following link:
https://plus.google.com/+EvanAndersonA/posts/72TLZMj4K5S
Bugs/Broken Features (That I've found):
- Front Camera has color problems (Similar to the CyanogenMod 13 Rom Rear Camera)
- Back Camera is flipped upside down (Very difficult to actually take pictures), but color is fine and focus seems fine (limited testing)
- No Fingerprint Sensor
The following Zip has the assert line removed from updater-script so it won't check your device before flashing. BE WARNED, if your device is not the Z5 Premium Satsuki, flashing this could break your device.
https://drive.google.com/file/d/0BwjsVhbtLaJaNTJTSDlqYlh0YXM/view?usp=sharing
DISCLAIMER: I am in no way affiliated with the development group, don't ask for updates or anything of the sort.
Click to expand...
Click to collapse
Any updates? Really want to flash this ROM but I'm waiting for the fingerprint and camera to be fixed...
just got my Phab 2 from lenovo today. trying various methods and will report if anything works.
kingoroot - no
Well just made it through my first day of using the phab 2.
Some good, some bad.
Battery life is not what I expected. 100% to 50% from 10am to 8pm. Moderate usage, Waze navigation for about 10 minutes. I came from a Huawei mate 2, so my standards are pretty high.
Some glitches setting up Bluetooth with Microsoft sync. Would not reconnect after initial setup without turning car off. Although, I will note that sync has had its own issues.
No root means no app settings, everything is too big.
The stock launcher is outrageously boring and not customizable. I could not find any real settings to adjust icon size, or even to change icons.
Now for the good:
Overall Android build is very stable and quick, no hangups with many apps running.
Display is very crisp for being a low-end model, and includes settings to adjust tone and color intensity.
Very little bloatware.
Camera is actually pretty good. Not perfect, but ok for 200$.
Plenty of good comments about 6.0, as I came from 4.3, but I'll spare the entire Android review.
But, this is what makes me never want to buy a Lenovo phone again. I called lenovo to get some basic specs on this phone that were not verified online. I went through 10 minutes of automated dialog and 5 different phone numbers. No one knew who to talk to about this phone. They're so focused on the big customers that they forgot to provide any support for what may be their biggest seller? On top of that, the guy I finally got in contact with at technical support was baffled that I would call about something other than a desktop or laptop, and did not have the information about this device on hand. This isn't a problem, as I got what I needed, but it almost seemed like no one was aware that this device was even available yet. Nothing in their support site references it, no real technical detail available, etc.
Anyways, I digress. There aren't many other 6.4inch phones available, so I can't complain too much. Overall, Im enjoying the experience. Plus, it gets attention.
Where did you get this... I've been looking to get one but haven't found a source...I'm assuming you're saying battery life is weaker than on the HAM2? Thanks again
TVCCS said:
Where did you get this... I've been looking to get one but haven't found a source...I'm assuming you're saying battery life is weaker than on the HAM2? Thanks again
Click to expand...
Click to collapse
Directly from lenovo. Yes, but the ham2 is pretty much the top tier in terms of battery life.
After a few days with it, I can go all day with Bluetooth Pandora, 2+hours straight of screen on time, 30 mins of Waze and have 40% left. I'd say it's doing pretty good for a standard phone. A few issues I've had are, the stock alarm app notification gets stuck and cannot be dismissed on occasion. A restart fixes this. Bluetooth AND Microsoft Sync have to be reset when a failed connection happens (this also occurred on my ham2, but only once every 2 months. This is once a day.) There are always 2 network icons in the notification bar for some reason.
On the up side, the camera has proven to be excellent in standard lighting. Pictures take a while to 'click.'
Touch response is very clean, will say I'm impressed with either the phones accuracy or androids ability to detect where a touch was meant.
My biggest pet peeve is also one of my favorite features. The navigation buttons are so dim that you can't see them in the daytime, but they're also so close together for such a large phone. But, this gives you plenty of room to grasp the phone without exiting an app by mistake, or bringing up a menu midst message.
Anyhow, I'll gladly answer any questions anyone has.
Thanks for the info... Lenovo doesn't have a place to order it yet for the U.S., at least that I can find.
Here ya go:
http://shop.lenovo.com/us/en/smartphones/phab-series/?menu-id=phab_series
I'm expecting mine today/Monday. Can't wait to get back into a proper-sized large phone. I've missed them since I sold my Sony Z Ultras...
Yeah I saw them on sale now, thanks. Can someone who has one please post a full Antutu benchmark score with 3D? The reports I've seen on the MTK8735 suggest a benchmark of around 31000, which isn't terribly impressive, but I'd like to see it on this device specifically. Thanks!
TVCCS said:
Yeah I saw them on sale now, thanks. Can someone who has one please post a full Antutu benchmark score with 3D? The reports I've seen on the MTK8735 suggest a benchmark of around 31000, which isn't terribly impressive, but I'd like to see it on this device specifically. Thanks!
Click to expand...
Click to collapse
Obligatory text, image attached
alaska100 said:
Obligatory text, image attached
Click to expand...
Click to collapse
Thanks much.
alaska100 said:
just got my Phab 2 from lenovo today. trying various methods and will report if anything works.
kingoroot - no
Click to expand...
Click to collapse
Any luck with rooting your phab2? I cannot find any method.
Is there any method to root lenovo phab 2?
How are the AR features? Any of them useful?
this version does not have AR features. You're looking for the Plus/Pro or w/e.
We're going to need to get a read back of the ROM from SP Flash tool to get root I think. What we really need is a TWRP build. I've tried quite a few variations for our chipset but haven't found one that even remotely boots yet.
hopefully we some others engage. i've got stuff I need to do with this phone, a few of which require root access of some kind.
Synman said:
We're going to need to get a read back of the ROM from SP Flash tool to get root I think. What we really need is a TWRP build. I've tried quite a few variations for our chipset but haven't found one that even remotely boots yet.
hopefully we some others engage. i've got stuff I need to do with this phone, a few of which require root access of some kind.
Click to expand...
Click to collapse
I hope you find a way to root phab 2. Why would they lock down the fastboot? Isn't the android open source? Slowly becoming like iOS.
fast boot isn't locked down, nor is the boot loader (once you unlock it). The problem is none of the MTK tools that I have are working like they are supposed to.
I've started a DEV thread with the stock images attached. Perhaps someone else will have better luck
Synman said:
fast boot isn't locked down, nor is the boot loader (once you unlock it). The problem is none of the MTK tools that I have are working like they are supposed to.
I've started a DEV thread with the stock images attached. Perhaps someone else will have better luck
Click to expand...
Click to collapse
My device is from Philippines. I unlocked the bootloader, but from recovery I cannot access bootloader. Device would not let me choose bootloader even though has the option, and from fastboot reboot, the device would not reboot.
the boot loader IS fast boot. Lenovo devices are notorious for allowing you one fast boot command per boot into the loader.
Synman said:
the boot loader IS fast boot. Lenovo devices are notorious for allowing you one fast boot command per boot into the loader.
Click to expand...
Click to collapse
what do you mean by one fast boot command per boot into the loader?
You can only issue a single fastboot command before having to reboot back into the boot loader to issue another.
Hello fellow Pixel users!
Just wanted to take a minute and start a small discussion with you about stuff that only works with root. Maybe you feel the same.
As an Android user from day 1, I always enjoyed the general "openness" of Android compared to other mobile OSs and used to frequently try out new custom ROMs, play with all the system UI tuner options and obviously got used to having a decent adblocker.
But ever since I got a Pixel XL, I was honestly surprised by the relatively small amount of ROMs and general lack of development on XDA regarding the Pixel phones. At least compared to previous phones I owned, with the exception of the Blackberry Classic maybe...
(Obviously I don't want to discredit the folks that ARE working on these devices. You're awesome and your work is very appreciated!)
Right now, I only use root for AdAway, Nova Launcher (for turning off the screen and locking it with a double tap) and Ex Kernel Manager (even though I never used it or changed any of the settings).
So what I really want to talk about is, what do you use root for? Or why did you unlock your bootloader? Is there something I'm missing?
TL,DR: Did you root your phone or unlock the bootloader? Why?
Yes and yes.
I will always run an unlocked bootloader. It's a security safety net. If my phone bricks, I have the option to flash factory images. I can always return to stock if something goes wrong.
Root, yes, of course. Because Android.
Pain-N-Panic said:
If my phone bricks, I have the option to flash factory images. I can always return to stock if something goes wrong.
Click to expand...
Click to collapse
Those are great points! You're absolutely right!
But what about apps or system tweaks? You said "Because Android" but how is your experience different from someone who didn't root?
paco8 said:
Those are great points! You're absolutely right!
But what about apps or system tweaks? You said "Because Android" but how is your experience different from someone who didn't root?
Click to expand...
Click to collapse
Root privileged apps- adaway, titanium backup, modded YouTube, modded Spotify, SD Maid, Substratum and a few others.
Also, custom kernel with customized color profile for a more vibrant display.
I also enjoy themeing my own device so having root is necessary for me.
I also need to root, well, BECAUSE ANDROID
Pain-N-Panic said:
Root privileged apps- adaway, titanium backup, modded YouTube, modded Spotify, SD Maid, Substratum and a few others.
Also, custom kernel with customized color profile for a more vibrant display.
I also enjoy themeing my own device so having root is necessary for me.
I also need to root, well, BECAUSE ANDROID
Click to expand...
Click to collapse
U don't need root for substratum on my 8.1 and use Andromeda add on for rootless substratum
I feel like going back to nougat and root for Xposed though...
Thanks for the suggestions!
If you ask me:
Not a fan of TB (restoring often causes problems)
or SD Maid (some cache is important and shouldn't be deleted - except for uninstalled apps),
Substratum is way too buggy for me (at least I can't seem to find a theme without bugs)
and I probably shouldn't ask about those modded apps on here, even though they sound interesting. I guess I'll have to Google that. :laugh:
After looking through Ex Kernel Manager, I can't seem to find anything that I'd want to use or fiddle with. The phone is fast enough, so no overclock. The colors are fine, so no tuning needed. And all the other stuff looks dangerous...
Where are all the awesome system UI options though? I'd love to have my clock in the center of the status bar and display battery percentage INSTEAD of the icon. I know that those are usually coded into custom ROMs but there are no 8.1 ROMs...
Oh, how I'd love to see an 8.1 DU ROM working flawlessly...
Edit: Why go back to Nougat and why use Xposed? I don't get what the big deal is about Xposed nowadays. I used it a few years ago but only because of one or two add-ons, if I recall that correctly.
I have center clock on 8.1 using a Substratum theme.
Also, you can choose to select battery percentage next to the battery icon in 8.1 battery settings.
Once source code gets released for 8.1, the SystemUI can be deodexed which will allow for 3minit battery mod to work. I believe 3minit requires root.
Reasons are getting thin aren't they. AdAway, TB, and Tasker (HBM and single tap sleep(without device admin permission thus required pin)). TB makes life easier but not a necessity. Different device wouldn't need HBM most likely. So basically it comes down to AdAway which I'm pretty sure I'd go nuts without.
TB, Tasker, lucky patcher, greenify, acr (automatic call recorder), ad away. And generally being able to mess with things.
ThePublisher said:
TB, Tasker, lucky patcher, greenify, acr (automatic call recorder), ad away. And generally being able to mess with things.
Click to expand...
Click to collapse
"Generally being able to mess with things" is the most accurate response this question for those who love Android at its core.
Pain-N-Panic said:
"Generally being able to mess with things" is the most accurate response this question for those who love Android at its core.
Click to expand...
Click to collapse
That's the technical term for it at least.
I'm down to one reason and I found out about it a few months back actually. Without it I probably wouldn't bother.
Assertive display - visibility outdoors in the freaking sun with sunglasses on? Heck yeah! The most annoying part is that it just takes two lines added to the build.prop file. If I could do this without root I sure as hell would.
Adaway
Thanks for all your answers!
This basically proves my point though in my opinion. Having a rooted Android device used to be such an open playground for fun stuff and now it's mostly just about adblockers and minor tweaks apart from a few apps that still take advantage of it like Tasker and TB.
At least the phones nowadays are fast as hell and have insane cameras. I just wish it would be more sci-fi-y if you know what I mean. Phones aren't just gadgets anymore, they're expensive pieces of hardware that seem to improve upon basic things that we could do for years.
Android updates used to have lots of cool new features with every new version number that was released and now they just seem to improve upon what they can already do and sometimes take features away or even lock them to specific phones (looking at the guy who thought it was a great idea to make stuff like "motion pictures" a feature only on Pixel 2 devices even though our device had the feature available for a day).
Guess I'll take this opportunity to spend less time messing around with tons of options and just be thankful for what they can do now. Like playing stupid gambling-like games with ps1-graphics on a device with a quad-core and 4GB of RAM. :laugh:
Am I the only one who gets turned off by games that have reviewers saying "addictive" and "great time-killer"? This thing could play GTA 4 and tons of people rather spend a hundred bucks on candy crush...
Whatever, it's all good. I guess I just have different expectations.
paco8 said:
Thanks for all your answers!
This basically proves my point though in my opinion. Having a rooted Android device used to be such an open playground for fun stuff and now it's mostly just about adblockers and minor tweaks apart from a few apps that still take advantage of it like Tasker and TB.
At least the phones nowadays are fast as hell and have insane cameras. I just wish it would be more sci-fi-y if you know what I mean. Phones aren't just gadgets anymore, they're expensive pieces of hardware that seem to improve upon basic things that we could do for years.
Android updates used to have lots of cool new features with every new version number that was released and now they just seem to improve upon what they can already do and sometimes take features away or even lock them to specific phones (looking at the guy who thought it was a great idea to make stuff like "motion pictures" a feature only on Pixel 2 devices even though our device had the feature available for a day).
Guess I'll take this opportunity to spend less time messing around with tons of options and just be thankful for what they can do now. Like playing stupid gambling-like games with ps1-graphics on a device with a quad-core and 4GB of RAM. :laugh:
Am I the only one who gets turned off by games that have reviewers saying "addictive" and "great time-killer"? This thing could play GTA 4 and tons of people rather spend a hundred bucks on candy crush...
Whatever, it's all good. I guess I just have different expectations.
Click to expand...
Click to collapse
You are right! I was also using root just for the 3 reasons you specified! Adaway is the biggest reason. There are other solutions, but nothing that reliable. And next biggest is Ex Kernel Manager to set up double tap to wake without lockscreen.
As for the motion photos, you still can get it. You need to download that version of Google Camera APK and disable updates. I am using it and it looks good. But it works only in Google Photos App. So not that useful as well!
DaSmith87 said:
I'm down to one reason and I found out about it a few months back actually. Without it I probably wouldn't bother.
Assertive display - visibility outdoors in the freaking sun with sunglasses on? Heck yeah! The most annoying part is that it just takes two lines added to the build.prop file. If I could do this without root I sure as hell would.
Click to expand...
Click to collapse
My quick reasons for bootloader unlocking and rooting mirror many of the others here:
1) Ability to flash factory images in a recovery situation.
2) Titanium Backup - although I haven't had to actually use this to recover anything other than a specific app or 2 in the past few years.
3) Adaway
4) Ability to modify build.prop to leverage native hotspot/tethering (Verizon GUDP)
I am interested in learning more about Assertive Display and the differences between it and Adaptive Brightness. My understanding is that Assertive Display works separately from Adaptive Brightness and actually adjusts the tone/color/contrast of individual display pixels to optimize viewing in bright sunlight. Theoretically, this allows you to turn down screen brightness to achieve better viewing/contrast in bright conditions. Can you provide the link to directions you used to enable Assertive Display? Also - does it play well with Adaptive Brightness - or do you need to manually tweak screen brightness to account for Assertive Display?
Thanks!
sb1893 said:
My quick reasons for bootloader unlocking and rooting mirror many of the others here:
1) Ability to flash factory images in a recovery situation.
2) Titanium Backup - although I haven't had to actually use this to recover anything other than a specific app or 2 in the past few years.
3) Adaway
4) Ability to modify build.prop to leverage native hotspot/tethering (Verizon GUDP)
I am interested in learning more about Assertive Display and the differences between it and Adaptive Brightness. My understanding is that Assertive Display works separately from Adaptive Brightness and actually adjusts the tone/color/contrast of individual display pixels to optimize viewing in bright sunlight. Theoretically, this allows you to turn down screen brightness to achieve better viewing/contrast in bright conditions. Can you provide the link to directions you used to enable Assertive Display? Also - does it play well with Adaptive Brightness - or do you need to manually tweak screen brightness to account for Assertive Display?
Thanks!
Click to expand...
Click to collapse
When I first enabled this I left my brightness at the same 50% level with the auto brightness left on. It works really well in conjunction with the normal brightness level settings. Maybe turning the brightness down could yeild better battery results but I was never one to complain by the Pixel XL's battery life.
This video from Android Authority here explains it well. I actually randomly got to the video at around midnight on YouTube a few months back. Phone wasn't rooted so I did root it in the middle of the night and followed this topic from the XDA forums to change the build.prop file. Applied the changes, rebooted phone and... Realized I have no real way to test it. Went to my kitchen's aspirator and switched the lights on, brought the phone under there super close at a very steep angle and I could still see it perfectly fine.
TL;DR - this is a great addition to the already standard brightness levels, works like magic, and hey, you can always revert if you end up not liking it.
DaSmith87 said:
When I first enabled this I left my brightness at the same 50% level with the auto brightness left on. It works really well in conjunction with the normal brightness level settings. Maybe turning the brightness down could yeild better battery results but I was never one to complain by the Pixel XL's battery life.
This video from Android Authority here explains it well. I actually randomly got to the video at around midnight on YouTube a few months back. Phone wasn't rooted so I did root it in the middle of the night and followed this topic from the XDA forums to change the build.prop file. Applied the changes, rebooted phone and... Realized I have no real way to test it. Went to my kitchen's aspirator and switched the lights on, brought the phone under there super close at a very steep angle and I could still see it perfectly fine.
TL;DR - this is a great addition to the already standard brightness levels, works like magic, and hey, you can always revert if you end up not liking it.
Click to expand...
Click to collapse
Thanks so much for the detail. I'm going to give it a whirl right now!
sb1893 said:
Thanks so much for the detail. I'm going to give it a whirl right now!
Click to expand...
Click to collapse
You're welcome! One thing I forgot to mention - don't bother with the flashable ZIP. It's more work than editing the build.prop file and it actually doesn't work on 8 and up. 7.1.2 was OK with it but I noticed it wasn't quite right on 8 when I tried to flash it even though it said it flashed with no errors.
sacthegreat said:
You are right! I was also using root just for the 3 reasons you specified! Adaway is the biggest reason. There are other solutions, but nothing that reliable. And next biggest is Ex Kernel Manager to set up double tap to wake without lockscreen.
As for the motion photos, you still can get it. You need to download that version of Google Camera APK and disable updates. I am using it and it looks good. But it works only in Google Photos App. So not that useful as well!
Click to expand...
Click to collapse
Thanks! I actually did disable auto update once I had it and still have the APK. Don't know if it works after a fresh install of 8.1 though. I guess I'll try later. Google's Motion Stills as an alternative just feels weird to me.
I think it's a neat feature though. Sometimes it really helps bring a moment back to life, more than a still picture would. Especially when it's snowing or raining.
That new AR stickers thing is also funny but it needs better content IMO. Two of the packs are basically ads for the StarWars movies and Stranger Things.
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!
I must say I'm rather impressed being the X is an older phone yet it receives the new security updates rather quickly.. Just got May's update..
yes sony , for unknown reason included X on android 8 project
lilbrat said:
I must say I'm rather impressed being the X is an older phone
Click to expand...
Click to collapse
Everything is fine, welcome to Extended support cycle from Sony. Its hardware is still great, so why not update it?
YasuHamed said:
yes sony , for unknown reason included X on android 8 project
Click to expand...
Click to collapse
What unknown? What? Is this device have some problems? Maybe its CPU overheats? Maybe it has bad drivers? Maybe it's running on MTK?
There's everything obvious - Xperia X is still a great device, and it SHOULD get every security update.
Gray47Maxx said:
Everything is fine, welcome to Extended support cycle from Sony. Its hardware is still great, so why not update it?
What unknown? What? Is this device have some problems? Maybe its CPU overheats? Maybe it has bad drivers? Maybe it's running on MTK?
There's everything obvious - Xperia X is still a great device, and it SHOULD get every security update.
Click to expand...
Click to collapse
Initially X was never part of ANdroid 8 when sony released software binaries. however it was last minute include. the line was drawn at X-perf
It feels good how finally Android 8 is running stable on X however as daily driver and with burden of social apps. X starts lagging and overheats as you said! , many functions and camera don't work.
X is not MTK device
YasuHamed said:
Initially X was never part of ANdroid 8 when sony released software binaries.
Click to expand...
Click to collapse
Lies. It was obvious from the start that it will get Oreo. Software binaries? Do you mean SODP ones?
YasuHamed said:
It feels good how finally Android 8 is running stable on X...
Click to expand...
Click to collapse
It was running great from the start. Maybe only camera was a little worse.
YasuHamed said:
...however as daily driver and with burden of social apps. X starts lagging and overheats as you said! , many functions and camera don't work.
Click to expand...
Click to collapse
That's only a problem of YOUR PERSONAL device. My X is neither lagging nor overheating even in a hot situations (tested in my bathroom with 41 gradus temperature, runs great). I don't have any problems with my X, neither all my X users I know from 4PDA. So stop telling people that Oreo is bad when YOUR device overheats and lags, please.
I suggest you to visit some local repair shops and ask them for checking your cooling system.
Gray47Maxx said:
Lies. It was obvious from the start that it will get Oreo. Software binaries? Do you mean SODP ones?
Click to expand...
Click to collapse
personal attacks aside!
on this road map xperia X and X performance was added later, sony had cut-off taken for OREO for XZ PROJECT ONLY! however later two X devices added, A post was on xda did mention last year how Sony has announced to discontinue X and Xc when it was just on 7.0 only! back then everyone was hoping that it should get atleast 7.1, if not Oreo!
https://forum.xda-developers.com/xperia-x/how-to/futur-x-t3614147 <------check yourself
also sony added X, Xp and Xc later in 2017 for Oreo! the original cutoff was til XZ project only! X family was not part of it inicially
https://blogs.sonymobile.com/2017/08/31/xperia-android-8-0-oreo/
Gray47Maxx said:
It was running great from the start. Maybe only camera was a little worse.
Click to expand...
Click to collapse
the Camera still cant record hd video more than 40 secons and shuts down due to heat.
Gray47Maxx said:
That's only a problem of YOUR PERSONAL device. My X is neither lagging nor overheating even in a hot situations (tested in my bathroom with 41 gradus temperature, runs great). I don't have any problems with my X, neither all my X users I know from 4PDA. So stop telling people that Oreo is bad when YOUR device overheats and lags, please.
I suggest you to visit some local repair shops and ask them for checking your cooling system.
Click to expand...
Click to collapse
I own two Xperia X, Black and Lime, so there goes your argument.
also its not my personal opinion and as Hardware there is NOTHING wrong with Xperia X. we are talking about software part.
I have tried my Black X with Omnirom 7.1.1 and 8.1 and the same X has
1. Amazing Batter Life
2. No overheating
3. no Lagging
4. Camera works perfect and records 4K
since you are using my modded kernels and ROOT ACCESS allows you to modify Oreo by having different modes in Magisks and/or control bloatware etc.
I would suggest you to flash oreo .2.70 right-away and use untouched for one weak with all the bells ringing and we will see
YasuHamed said:
personal attacks aside!
on this road map xperia X and X performance was added later, sony had cut-off taken for OREO for XZ PROJECT ONLY! however later two X devices added, A post was on xda did mention last year how Sony has announced to discontinue X and Xc when it was just on 7.0 only! back then everyone was hoping that it should get atleast 7.1, if not Oreo!
https://forum.xda-developers.com/xperia-x/how-to/futur-x-t3614147 <------check yourself
also sony added X, Xp and Xc later in 2017 for Oreo! the original cutoff was til XZ project only! X family was not part of it inicially
https://blogs.sonymobile.com/2017/08/31/xperia-android-8-0-oreo/
the Camera still cant record hd video more than 40 secons and shuts down due to heat.
I own two Xperia X, Black and Lime, so there goes your argument.
also its not my personal opinion and as Hardware there is NOTHING wrong with Xperia X. we are talking about software part.
I have tried my Black X with Omnirom 7.1.1 and 8.1 and the same X has
1. Amazing Batter Life
2. No overheating
3. no Lagging
4. Camera works perfect and records 4K
since you are using my modded kernels and ROOT ACCESS allows you to modify Oreo by having different modes in Magisks and/or control bloatware etc.
I would suggest you to flash oreo .2.70 right-away and use untouched for one weak with all the bells ringing and we will see
Click to expand...
Click to collapse
So do you mean nougat has much better battery than Oreo?
coconutxyz said:
So do you mean nougat has much better battery than Oreo?
Click to expand...
Click to collapse
Due to the following features I am using Oreo (XGEN) build on .2.50
1. Better Screen Resolution/Tone ( the tint in Oreo on screen is soothing to eyes as compare to N)
2. Cleartype ScreenFonts
3. Nighlight
4. Notification settings options and panel
5. Setting Menu simplified (a bit better than Nougat)
-- however these are all UI and cosmetic affects
I was happier and relaxed on the final build .252 (came dec17) android 7.1.1. I kept switching back to .252 after trying first two Oreo builds which I found horrible in terms of battery life & overheating; and its not just me, many user reported the same on various posts (in and out of XDA forums) about how after upgrading to Oreo they are facing overheating and battery drain issues. when X overheats it starts lagging.
10April18 build .2.50 (third attempt) has been quite better than its predecessor builds but still can't compete with dec17 build .252.
REMEMBER, my comparison / observation is on ROOTED Xperia-X
YasuHamed said:
Due to the following features I am using Oreo (XGEN) build on .2.50
1. Better Screen Resolution/Tone ( the tint in Oreo on screen is soothing to eyes as compare to N)
2. Cleartype ScreenFonts
3. Nighlight
4. Notification settings options and panel
5. Setting Menu simplified (a bit better than Nougat)
-- however these are all UI and cosmetic affects
I was happier and relaxed on the final build .252 (came dec17) android 7.1.1. I kept switching back to .252 after trying first two Oreo builds which I found horrible in terms of battery life & overheating; and its not just me, many user reported the same on various posts (in and out of XDA forums) about how after upgrading to Oreo they are facing overheating and battery drain issues. when X overheats it starts lagging.
10April18 build .2.50 (third attempt) has been quite better than its predecessor builds but still can't compete with dec17 build .252.
REMEMBER, my comparison / observation is on ROOTED Xperia-X
Click to expand...
Click to collapse
Yea I will for sure root all my android device so I needed some opinion on rooted device. Guess I might go back to nougat sometimes
coconutxyz said:
Yea I will for sure root all my android device so I needed some opinion on rooted device. Guess I might go back to nougat sometimes
Click to expand...
Click to collapse
i feel the same! i will go back to nougat once sony discontinue supporting X
YasuHamed said:
A post was on xda did mention last year how Sony has announced to discontinue X and Xc when it was just on 7.0 only! back then everyone was hoping that it should get atleast 7.1, if not Oreo!
https://forum.xda-developers.com/xperia-x/how-to/futur-x-t3614147 <------check yourself
also sony added X, Xp and Xc later in 2017 for Oreo! the original cutoff was til XZ project only! X family was not part of it inicially
https://blogs.sonymobile.com/2017/08/31/xperia-android-8-0-oreo/
Click to expand...
Click to collapse
I can't remember the original roadmap, but I can't trust XDA as well. So there you may be right.
UPD: You are wrong. It was included in the list from the start: proof, not updated. Wayback Machine link provided as well.
P.S. What a ridiculous source of the info - just a random guy.
YasuHamed said:
the Camera still cant record hd video more than 40 secons and shuts down due to heat.
Click to expand...
Click to collapse
Do you need my FHD 60 FPS video recorded on X without any additional cooling systems? I can provide one.
YasuHamed said:
I own two Xperia X, Black and Lime, so there goes your argument.
also its not my personal opinion and as Hardware there is NOTHING wrong with Xperia X. we are talking about software part.
I have tried my Black X with Omnirom 7.1.1 and 8.1 and the same X has
1. Amazing Batter Life
2. No overheating
3. no Lagging
4. Camera works perfect and records 4K
Click to expand...
Click to collapse
I have the same on stock Oreo, everything except the first point. OmniROM (and k4.4 in general) are more optimized.
YasuHamed said:
since you are using my modded kernels and ROOT ACCESS allows you to modify Oreo by having different modes in Magisks and/or control bloatware etc.
I would suggest you to flash oreo .2.70 right-away and use untouched for one weak with all the bells ringing and we will see
Click to expand...
Click to collapse
Nice challenge!)
I'd like to accept it, but since I was already using Oreo on locked bl (before your kernel was released for 5121), I can share some thoughts. It was running stable, maybe camera was a little bit worse than I expected. No overheat (was it because of a winter?), no lags, no anything. It was a clean and stable ROM. So...
But thanks for the idea of challenge like this. I have a guy with untouched X, so maybe he will tell something there.
over-heating
Hi Guys,
My Xperia-X is replaced in this may month in warranty.
After replaced I am feeling too much overheating.
From the first day, I have an update to latest may security update.
Now I don't know this over-heating is due to may update or again I got faulty hardware by Sony.
What about you guys do you feel over-heating especially after may update?
Hey folks, heads up June update is out and about..