Database Develop

[Q] Help for a Newbie in P7

Hello ,
I got my P7 for about 4 Months now,
and I wanted to have the EMUI 3.0 and Lolipop
but I think the Original System is 4.4.2 and Emui 2
I want to ask What can I do to Root or make a ROM (Sorry I really dont know he defrance total newbie ) , but I dont want to lose the support of Google or the Google Market , what should I do , can anyone help me in that ???
give me details and tell me what to do
thanks

look at this: http://forum.xda-developers.com/asc...7en-rom-v3-0-emui-3-0-4-4-2-18-11-14-t2945104

darkzero2022 said:
Hello ,
I got my P7 for about 4 Months now,
and I wanted to have the EMUI 3.0 and Lolipop
but I think the Original System is 4.4.2 and Emui 2
I want to ask What can I do to Root or make a ROM (Sorry I really dont know he defrance total newbie ) , but I dont want to lose the support of Google or the Google Market , what should I do , can anyone help me in that ???
give me details and tell me what to do
thanks
Click to expand...
Click to collapse
If you are newbie than do nothing ! Wait for official upgrade ! Because you will cry !
Sent from my HUAWEI P7-L10

Ziolek67 said:
If you are newbie than do nothing ! Wait for official upgrade ! Because you will cry !
Sent from my HUAWEI P7-L10
Click to expand...
Click to collapse
Really ???? Why ?? Huawei is too slow in making the Updates , all now is Andoird 5 and P7 is stuck in 4.4.2

It's proberly better staying on 4.4.2 than on lolipop. Many bugs on lolipop.
Sent from my HUAWEI P7-L10 using XDA Free mobile app

darkzero2022 said:
Really ???? Why ?? Huawei is too slow in making the Updates , all now is Andoird 5 and P7 is stuck in 4.4.2
Click to expand...
Click to collapse
Ok than lest go to update.... I will waiting for yours requests for help

darkzero2022 said:
Really ???? Why ?? Huawei is too slow in making the Updates , all now is Andoird 5 and P7 is stuck in 4.4.2
Click to expand...
Click to collapse
Wow do you realize android 5 has been out officially for a week or two and pretty much every phone apart from nexus which uses the software directly from Google themselves who make android, still don't run it yet and expect to be running it in 2015.
Not even big teams that use the aosp code directly such as cyanogen or paranoid have got a stable fully functional rom out yet.
It takes time for the 3rd party developers to customize and test android for there devices once the official version gets released as they all use the final source code which only has been out 3-4 weeks.
Also no company apart from Google is much better, Samsung are still rolling out 4.4 to some of there devices with some like the s2 still on 4.2 and end of life presumably others will jump straight to lollipop from 4.3 etc.
Also on rooting what do you wish to achieve by doing so?
Rooting can be very dangerous if you don't know what your doing with devices like ours.
Take a look for example at all the posts in this forum asking to downgrade their l10's from emui 3 to 2 which they upgraded to custom versions etc without thinking and the issues they now have with boot loops and stuff.
If you want to run xposed you can find many people with similar things recently in this forum that can't get it to work.
Also rooting etc you lose the ability for any future updates via OTA and recovery and would need to manually update your device potentially bricking it every single time which bricking means you can no longer use your device and have to buy a new one.
Also are you capible on the PC with using it, command prompt Linux shell etc and doing things like installing Windows and other things.
If not then rooting is not for you.
Also do you know how to code in Linux C etc and know the workings of the Linux os, if not then there is no way you are going to make a custom rom. All you might be able to achieve is just repackaging someone else's ROM with minor edits and even then the tools to do that mainly use Linux to run as it's native windows doesn't have all the stuff Linux has natively in this regard.

Ziolek67 said:
If you are newbie than do nothing ! Wait for official upgrade ! Because you will cry !
Sent from my HUAWEI P7-L10
Click to expand...
Click to collapse
drguild said:
Wow do you realize android 5 has been out officially for a week or two and pretty much every phone apart from nexus which uses the software directly from Google themselves who make android, still don't run it yet and expect to be running it in 2015.
Not even big teams that use the aosp code directly such as cyanogen or paranoid have got a stable fully functional rom out yet.
It takes time for the 3rd party developers to customize and test android for there devices once the official version gets released as they all use the final source code which only has been out 3-4 weeks.
Also no company apart from Google is much better, Samsung are still rolling out 4.4 to some of there devices with some like the s2 still on 4.2 and end of life presumably others will jump straight to lollipop from 4.3 etc.
Also on rooting what do you wish to achieve by doing so?
Rooting can be very dangerous if you don't know what your doing with devices like ours.
Take a look for example at all the posts in this forum asking to downgrade their l10's from emui 3 to 2 which they upgraded to custom versions etc without thinking and the issues they now have with boot loops and stuff.
If you want to run xposed you can find many people with similar things recently in this forum that can't get it to work.
Also rooting etc you lose the ability for any future updates via OTA and recovery and would need to manually update your device potentially bricking it every single time which bricking means you can no longer use your device and have to buy a new one.
Also are you capible on the PC with using it, command prompt Linux shell etc and doing things like installing Windows and other things.
If not then rooting is not for you.
Also do you know how to code in Linux C etc and know the workings of the Linux os, if not then there is no way you are going to make a custom rom. All you might be able to achieve is just repackaging someone else's ROM with minor edits and even then the tools to do that mainly use Linux to run as it's native windows doesn't have all the stuff Linux has natively in this regard.
Click to expand...
Click to collapse
Thanks For your Valuable words,
I really enjoyed them and get my mind open
well I do have Good Experience in linux and Command line , C Programming actually didnt go deep with it really ,
But i think I will stick to your opinion and wait ,and while I do so I will learn more about the whole subject ,and maybe increase my knowledge in this Field . (Android Programming - the C Programming - how things work in Android , ROMS , ETC)
but would you mind telling me from where to start ???

darkzero2022 said:
Thanks For your Valuable words,
I really enjoyed them and get my mind open
well I do have Good Experience in linux and Command line , C Programming actually didnt go deep with it really ,
But i think I will stick to your opinion and wait ,and while I do so I will learn more about the whole subject ,and maybe increase my knowledge in this Field . (Android Programming - the C Programming - how things work in Android , ROMS , ETC)
but would you mind telling me from where to start ???
Click to expand...
Click to collapse
Apologies if I came across about abit hard this forum has had allot of impatient people jumping in recently trying to run Emui 3 on l10's then asking to downgrade as you may have noticed the other teams like paranoid are already dealing with lots of people saying there to slow for not having lollipop out within a hour of aosp.
I had the same issue running a custom Minecraft server that people got really angry then refused to play and bad mouth the server if we didn't update that day when update time for us was about a week given the number of customizations we had 41 plugin's in the end, sometimes longer if there were more changes the mod and custom server devs had to deal with.
Emui 3 and lollipop has more bugs more as it's new from what I found I may start a proper consolidated emui talk thread later for those running it opposed to all the l10 when are we getting it out help me downgrade threads.
The place I think you should start is to download the source code for your version from the emui webpage and start analyzing it out of interest.
There's another Dev on here doing the same thing so you might want to contact him for info.
Also there are tools on Linux that easily let you unpack stock image files and the ext container and repack them.
That way you can see the full file structure and how a rom is packaged.
It's good just to see what's inside roms and how the first roms are usually made by a repackage before source.
I will stress the same as above that while these are starting points you would need to know what you are doing and something more hackable like a cheap nexus or or Chinese tab (about $50 USD) with easy upgradable firmware something would be better to start on.
Also grab down the android tools with eclypse for Linux, the sdk virtual device and have a play around making a app and stuff also you can edit the virtual rom safely etc.
The Linux version of the tools is far superior as you can natively mount the virtual ext cards for host file transfer and do other things which you can't under windows.
By ext above I mean the virtual partition files which are either ext 3 or 4 last time I looked.
I'm not a coder myself and I only did basic stuff in the past as I had a Chinese android 2.2 tablet the MID ones as my first device, I used a custom rom on which was just a repack with file system changes with bloat removed etc.
I looked into this out of interest and curiosity, each rom update I repacked it with the apps I used so I didn't need to reinstall them, there was probably a better (proper) way than just unpacking the ext file system from the img adding my apps in to the deploy folder and repacking.
Also I unpacked a APK weather app etc to make changes and use a custom background and others like themes to grab icons and assets this is a good start with looking at app packages and how that all works as well as making your own app in various tools eclipse for one which is the official tool but there's hundreds of android programming softwares online even to do simple stuff as make a stand alone html5 app from a webpage.
The tools on Windows I found were lacking and harder to find for the rom stuff, with Linux it was built into the system a lot of things.
What Linux is the best for doing Android stuff I don't know so that will need to be researched.
As mentioned devices can be dangerous for custom stuff especially newer ones with bootloader security, the older Chinese style ones and some others you could reflash easily from sdcard with a update.img file as they didn't contain that lock out security on boot and debugging.
I nearly bricked a few devices in the past, once having to rely on the bootloader and Android Commander a powerful tool and device terminal to mount the partition rw while in the bootloader to rename a file backI renamed as a test that caused the system to stop booting.
You can still get some tabs that do that about 50 USD on eBay etc I think.

darkzero2022 said:
Hello ,
I got my P7 for about 4 Months now,
and I wanted to have the EMUI 3.0 and Lolipop
but I think the Original System is 4.4.2 and Emui 2
I want to ask What can I do to Root or make a ROM...
Click to expand...
Click to collapse
I'd strongly advise that you wait. My experience. You can root v4.4.2 VERY easily using vroot. Wait for lollipop, honestly. Is a nightmare recovering your position if you try to move now.
Sent from my HUAWEI P7-L10 using XDA Premium HD app

[CFW][KK4.4] GomdoLight KitKat Custom Firmware Environment (System Enhancement Pack)

Hi all,
Today, I proudly present GomdoLight KitKat for KOREAN LG G / G2 / G3 / G3A / G3cat6 / Gflex / GK / Gpro / Gpro2 / LTE3 / Vu2 / Vu3 / Gpad7LTE, one of the most widely used (with 20,000+ users approximately) stock-based custom firmware in South Korea.
GomdoLight is more than 3 year old already (first version released on 19th December 2012), and is very mature.
Technically speaking GomdoLight is NOT a complete ROM, but rather a large-scale patch, which modifies official stock firmware to remove all the unnecessary components preloaded by operator/manufacturer, and reorganizes key system parts to 'basic' Android OS with manufacturer's flavor. For some devices GomdoLight's own specialized tool 'GomdoLight Sideloader' can make it possible to install GomdoLight directly over the stock firmware, even without rooting or flashing custom recovery!
GomdoLight is compatible with the following devices (BOLD indicates GomdoLight Sideloader support - no root required)
LG Optimus G: LG-F180S, LG-F180K, LG-F180L ("G")
LG G2: LG-F320S, LG-F320K, LG-F320L ("G2")
LG G3: LG-F400S, LG-F400K, LG-F400L ("G3")
LG G3A: LG-F410S ("G3A")
LG G3 Cat.6: LG-F460S, LG-F460K, LG-F460L ("G3")
LG G Flex: LG-F340S, LG-F340K, LG-F340L ("Gflex")
LG GK: LG-F220K ("GK")
LG G Pro: LG-F240S, LG-F240K, LG-F240L ("Gpro")
LG G Pro 2: LG-F350S, LG-F350K, LG-F350L ("Gpro2")
LG Gx: LG-F310L, LG-F310LR ("Gx")
LG Optimus LTE3: LG-F260S ("LTE3")
LG Optimus Vu2: LG-F200S, LG-F200K, LG-F200L ("Vu2")
LG Vu 3: LG-F300S, LG-F300K, LG-F300L ("Vu3")
LG G Pad 7.0 LTE: LG-V410 ("Gpad7LTE")
A very thorough and extensive (probably, the most extensive on entire xda) manual is provided at the download page, which contains literally everything you need to know to install GomdoLight. FAILURE TO READ THIS DOCUMENT BEFORE INSTALLING WILL ALWAYS LEAD TO VARIOUS UNEXPECTED PROBLEMS. PLEASE READ CAREFULLY. Needless to say, I WILL NOT ANSWER ANY QUESTIONS ALREADY ADDRESSED IN THIS DOCUMENT.
Due to xda forum's limits (in functionality) I am posting a link to the separate (external) DOWNLOAD PAGE. There is no way I can link to each section in the document in xda posts, since xda does not support HTML tag. However some portions of the document are also introduced here.
▶ GomdoLight Download / Manual Page
GomdoLight TUTORIALS:
Want to read the built-in user manual again?
Need help using GomdoLight Flag functions?
Installing an EasyMod package? (Sorry the tutorial is in Korean, but screenshots will help)
XDA:DevDB Information
GomdoLight KitKat, ROM for various LGE devices
Contributors
juniecho
ROM OS Version: 4.4.x KitKat
ROM Firmware Required: STOCK FIRMWARE (Firmware compatibility table available)
Based On: STOCK FIRMWARE
Version Information
Status: Stable
Current Stable Version: 4.0
Created 2015-02-26
Last Updated 2015-12-31

CHANGELOG for older versions
Version History:
2015. 12. 31. - Wave 4, initial release
UPDATE LEVEL: MAJOR / IMPORTANCE: VERY HIGH
CHANGELOG:
Oh god, have I abandoned this thread this long? So many changes, sorry, I can't list them all.
A lot of things are now even better than ever. Trust me.
[#GLKITKATCOMMONUPDATE]

EMERGENCY NOTICE, etc.
For some unknown reason I cannot access my DevDB variables at this time. Though G Flex is not on the list of supported devices right now, it IS supported.
* For those who have waited for a long time, sorry for being late, and thank you very much.

Will we see a port to d959 ever? If so and you need a tester pm me!
EDIT: For those wanting to try it did install, but very few bloat was actually removed and no gomdo apps were installed.

dmifsud44 said:
Will we see a port to d959 ever? If so and you need a tester pm me!
Click to expand...
Click to collapse
I'm not sure yet, but it may not be necessary. Because gomdolight is a large-scale patch mainly focusing on script-driven features, just three of system apks are overwritten:
- /system/framework/framework-res.apk
- /system/priv-app/LGSystemUI.apk
- /system/priv-app/LGCameraApp.apk
Camera should be compatible for all variants, and only the FRAMEWORK RESOURCE and the SYSTEM UI might have compatibility issue.
You can first take a Nandroid backup, and try installing GomdoLight all the way to the end over your stock firmware, and see if it boots (and operates without crashes)
For model selection just choose LG-F340K.
1) If it works well: CONGRATULATIONS! You have fully-working GomdoLight.
2) If it fails: Restore Nandroid, and reinstall GomdoLight. However this time choose the 4TH option for battery percentage indicator. (Do not change) This options leaves both framework-res and SystemUI unchanged, so it will work 100%.

juniecho said:
I'm not sure yet, but it may not be necessary. Because gomdolight is a large-scale patch mainly focusing on script-driven features, just three of system apks are overwritten:
- /system/framework/framework-res.apk
- /system/priv-app/LGSystemUI.apk
- /system/priv-app/LGCameraApp.apk
Camera should be compatible for all variants, and only the FRAMEWORK RESOURCE and the SYSTEM UI might have compatibility issue.
You can first take a Nandroid backup, and try installing GomdoLight all the way to the end over your stock firmware, and see if it boots (and operates without crashes)
For model selection just choose LG-F340K.
1) If it works well: CONGRATULATIONS! You have fully-working GomdoLight.
2) If it fails: Restore Nandroid, and reinstall GomdoLight. However this time choose the 4TH option for battery percentage indicator. (Do not change) This options leaves both framework-res and SystemUI unchanged, so it will work 100%.
Click to expand...
Click to collapse
Wheres the download?

podagee said:
Wheres the download?
Click to expand...
Click to collapse
in the download/manual page. section 10. (see the first post) be sure to read the installation guide.

I installed in my d-958, well, some force closes in the settings, app manager and gallery sometimes, but everything else, at least the main functions, works well

Maikeu Locatelli said:
I installed in my d-958, well, some force closes in the settings, app manager and gallery sometimes, but everything else, at least the main functions, works well
Click to expand...
Click to collapse
do they CONSISTENTLY force close by certain actions? or just randomly?

I'm downloading now and will test it for the D95920s firmware. T-Mobile D959 on the latest KitKat 4.4.2 D95920s. Will report back later. I need my phone till at least 4pm central time so I can reach my son but I'll flash after that.

This intrigues me. Sprint supported? I don't feel like dealing with force closes mentioned in previous post in different variant.
Sent from my LG-LS995 using Tapatalk

mattwheat said:
I'm downloading now and will test it for the D95920s firmware. T-Mobile D959 on the latest KitKat 4.4.2 D95920s. Will report back later. I need my phone till at least 4pm central time so I can reach my son but I'll flash after that.
Click to expand...
Click to collapse
good luck. if it crashes revert to stock via nandroid backup and reinstall gomdolight, this time choosing the 4th option (do not overwrite the status bar) with battery percentage indicator.

felacio said:
This intrigues me. Sprint supported? I don't feel like dealing with force closes mentioned in previous post in different variant.
Sent from my LG-LS995 using Tapatalk
Click to expand...
Click to collapse
probably. the script set is practically compatible with all current LGE devices with JB or KK. only few apks should be troublesome.
if not sure, choose not to change the status bar during installation. then it will not overwrite both framework-res and systemui.

Gonna try it on my d950
---------- Post added at 01:31 AM ---------- Previous post was at 01:17 AM ----------
Mahh nothing different.... install went perfect,so far no force closes. What is this supposed to be? I dont see any difference. I used the f340u+. Nothing special going on with this. Restoring my back up now.

podagee said:
Gonna try it on my d950
---------- Post added at 01:31 AM ---------- Previous post was at 01:17 AM ----------
Mahh nothing different.... install went perfect,so far no force closes. What is this supposed to be? I dont see any difference. I used the f340u+. Nothing special going on with this. Restoring my back up now.
Click to expand...
Click to collapse
Don't you see messages like 'GomdoLight: System starting up'?
You usually don't see visible differences after installing GomdoLight, especially on non-Korean firmware, since it does not know what apps to debloat. You would have to debloat the system yourself. However its extensive startup script set provides very unique and useful functions. These functions are explained in the simplified user manual that is automatically displayed after installing. If you did not see the manual opening, and if you do not see the startup messages either, probably something is wrong.

juniecho said:
Don't you see messages like 'GomdoLight: System starting up'?
You usually don't see visible differences after installing GomdoLight, especially on non-Korean firmware, since it does not know what apps to debloat. You would have to debloat the system yourself. However its extensive startup script set provides very unique and useful functions. These functions are explained in the simplified user manual that is automatically displayed after installing. If you did not see the manual opening, and if you do not see the startup messages either, probably something is wrong.
Click to expand...
Click to collapse
I seen all the startups and everything. Gomdo warning of superuser, a major lag on my phone for abot 3-5 minutes of lag. It only uninstalled vutalj. I honestly havent noticed anything special. I even tried it with that status bar selection and it went through fine.

podagee said:
I seen all the startups and everything. Gomdo warning of superuser, a major lag on my phone for abot 3-5 minutes of lag. It only uninstalled vutalj. I honestly havent noticed anything special. I even tried it with that status bar selection and it went through fine.
Click to expand...
Click to collapse
gomdolight's optimizations are not much visually noticable, without drastic changes. if you expect a whole new experience this is not your type of rom.
or, you could install another stock-based rom that will bring significant changes, and install gomdolight over it (without status bar selection) to further aid with its performance.
think gomdolight as a special tool to streamline and 'properly' reorganize the stock firmware (or, stock-based roms). changes are not noticable at first sight, but they surely benefit the user somehow in the long run, and give you better control and (sometimes) superior disaster handling capabilities.
anyway, thank you for letting me know that selecting LGU+ model increases compatibility with non-Korean firmwares.

juniecho said:
gomdolight's optimizations are not much visually noticable, without drastic changes. if you expect a whole new experience this is not your type of rom.
or, you could install another stock-based rom that will bring significant changes, and install gomdolight over it (without status bar selection) to further aid with its performance.
think gomdolight as a special tool to streamline and 'properly' reorganize the stock firmware (or, stock-based roms). changes are not noticable at first sight, but they surely benefit the user somehow in the long run, and give you better control and (sometimes) superior disaster handling capabilities.
anyway, thank you for letting me know that selecting LGU+ model increases compatibility with non-Korean firmwares.
Click to expand...
Click to collapse
Okay. I will reinstall again and run it for a while to see its benefits. Thanks

podagee said:
Okay. I will reinstall again and run it for a while to see its benefits. Thanks
Click to expand...
Click to collapse
the built-in user manual explains some of its advantages... take a look at it, especially the section for what is called gomdolight flags.

UPDATE - Wave 2, revision 3
UPDATE LEVEL: MEDIUM / IMPORTANCE: HIGH
UPGRADE INSTRUCTIONS:
One-touch upgrade via 'Upgrade/Repair' option
CHANGELOG:
Improved GomdoLight Engine scripts
Faster boot time, reduced processor load during boot
Improved GomdoLight operational status notifications
Slightly improved battery efficiency
'Update Center' components updated

[ROM][AOSP][4.4/6.0/7.1] Unlegacy Android Project

The Unlegacy-Android Project​Introduction
Unlegacy-Android started out as the OMAP4-AOSP Project. It was created in late 2015 in order to maintain a clean and organized place for pure AOSP support for various OMAP4 devices, such as the Galaxy Nexus and the Samsung Galaxy Tab 2 series. Over time this evolved to support more than just these devices, but still maintains its roots of supporting "legacy" devices that no longer receive "official" updates: hence Unlegacy-Android was born.
Installation
It's important that /system needs to be unmounted before installing the ROM - some recoveries tend to leave it mounted after performing operations on it.
If you're planning to install GApps, be sure to read the second post!
Aside from these, installation and upgrading is no different than on other ROMs. As usual, 'espresso' goes for all non-3g versions, 'espresso3g' goes for all 3g versions.
Problems
- Occasional sound stuttering in some games
- No hwrotation (meaning the boot animation is landscape on p31xx). I don't consider this as a problem, as autorotation will take effect after bootup anyways... and most 7" tablets, like the Nexus 7 work this way as well.
- The 7.1 builds are experimental! Means: modem not working perfectly yet.
If you notice anything else, be sure to report it in this thread. While I'm kind of busy, I usually read the thread and acknowledge the bug reports, even if I don't reply directly to them.
Downloads
See: http://builds.unlegacy-android.org
Always use the latest TWRP, to flash Android 7.x, you must use TWRP 3.0.3-0 or newer.
Features?
There isn't much to say here - this is AOSP, if you install GApps, you pretty much get the same thing that's running on the Nexus devices. The aim of this project is to create a fast and stable ROM - although, one could use Xposed to add extra features.
As usual, feedback is appreciated
Want to support development? You can consider donating, I spent countless of hours with this
XDA:DevDB Information
Unlegacy Android Project, ROM for the Samsung Galaxy Tab 2
Contributors
Ziyan, Android-Andi
Source Code: https://github.com/Unlegacy-Android
ROM OS Version: 7.x Nougat
ROM Firmware Required: The latest bootloader for your device.
Version Information
Status: Beta
Current Stable Version: 4.4, 6.0
Created 2016-07-03
Last Updated 2017-10-22

GApps
If you want to install GApps, we recommend Open GApps Nano or BaNkS GApps.
An important note: as this is a pure AOSP ROM, installing GApps tends to be problematic: in order to try to avoid installation issues, be sure to install GApps immediately after installing the ROM, before booting the system for the first time. After the initial bootup finished, be sure to go into Settings -> Apps, and grant every permission to every Google application - most importantly, Google Play services.
In the case of an upgrade, be sure to re-install the GApps package, as upgrading wipes /system. You shouldn't need to re-set the permissions afterwards.
siealex said:
One more note. DO NOT set up your Google account until you grant all permissions, otherwise you will be stuck on the initial setup.
Click to expand...
Click to collapse
Rooting
You can flash either the latest SuperSU or OpenSource SuperUser to get rooted.

Ziyan said:
GApps
If you want to install GApps, we recommend Open GApps Nano or BaNkS GApps.
An important note: as this is a pure AOSP ROM, installing GApps tends to be problematic: in order to try to avoid installation issues, be sure to install GApps immediately after installing the ROM, before booting the system for the first time. After the initial bootup finished, be sure to go into Settings -> Apps, and grant every permission to every Google application - most importantly, Google Play services.
In the case of an upgrade, be sure to re-install the GApps package, as upgrading wipes /system. You shouldn't need to re-set the permissions afterwards.
Rooting
You can flash either the latest SuperSU or OpenSource SuperUser to get rooted.
Click to expand...
Click to collapse
Wow, i saw this rom on galaxy nexus section. Does this rom included CMA?

Bastiary said:
Wow, i saw this rom on galaxy nexus section. Does this rom included CMA?
Click to expand...
Click to collapse
No, at least not yet. I think that the big thing for this will be 3.4 in the near future - I made some very good progress with it, aside from camera not working yet, there are only minor problems remaining

Thank you for everything , dear friend ! And for the support of the old device , and what you are doing and Andi for us ordinary users .
I understand correctly , that support will only 6.0.1 Android N and we do not see , because the device and its old base ?

Az-09 said:
I understand correctly , that support will only 6.0.1 Android N and we do not see , because the device and its old base ?
Click to expand...
Click to collapse
Before every new Android release, we devs get all sorts of questions like this. I'd like to say it once and for all: there's no such thing as 'we do not see' the next versions and whatnot. People are being negative for some reason, but we always try and succeed in the end... I'm sure that if you start reading past posts, you'll find a lot of people saying that we1l never see Lollipop or Marshmallow due to the device being too old, lol.

Download link?
It just says look at the top of the page? Is it soon?
Thanks for the new ROM....keep it up!
All the best...

radz_ said:
Download link?
It just says look at the top of the page? Is it soon?
Thanks for the new ROM....keep it up!
All the best...
Click to expand...
Click to collapse
check download tab section.

Hello! The ROM with the codename "espresso" is for the version: Galaxy Tab 2 7.0 Wi-Fi P3110 / P3113 and Galaxy Tab 2 10.1 Wi-Fi P5110 / P5113. Namely we talk about all versions with codename "espressowifi"?!

pickmod said:
Hello! The ROM with the codename "espresso" is for the version: Galaxy Tab 2 7.0 Wi-Fi P3110 / P3113 and Galaxy Tab 2 10.1 Wi-Fi P5110 / P5113. Namely we talk about all versions with codename "espressowifi"?!
Click to expand...
Click to collapse
Yes, that's correct.

Dear Mr. @Ziyan,
1stable congrat and thx Sir for being ROM Maker, we would love to see you update it regularly and add these:
*feature list
*changelog
*screenshot
~Omaple~
"...stay success and keep tab 2 alive at least till 2020"

Screeshots

Astro Noid said:
Dear Mr. @Ziyan,
1stable congrat and thx Sir for being ROM Maker, we would love to see you update it regularly and add these:
*feature list
*changelog
*screenshot
~Omaple~
"...stay success and keep tab 2 alive at least till 2020"
Click to expand...
Click to collapse
no need for this, it's aosp there isn't any custom features and everybody know how aosp looks

Astro Noid said:
Dear Mr. @Ziyan,
1stable congrat and thx Sir for being ROM Maker, we would love to see you update it regularly and add these:
*feature list
*changelog
*screenshot
~Omaple~
"...stay success and keep tab 2 alive at least till 2020"
Click to expand...
Click to collapse
Oh don't worry, I'm working extremely hard in the background almost since like a year... I know a lot about these devices (bought a P5100 specifically for testing 3G on the builds and kernels)
Feature list: well, this is AOSP, and I'd like to keep it this way. Imagine this like the stock ROM on the Nexus devices (with GApps flashed, of course).
Changelog: don't expect anything other than AOSP updates and hardware related fixes and updates - of course, I'm going to write a post each time I release an update, just like I do in the Galaxy Nexus thread however, it's unlikely that I'll add a changelog to the OP (I just don't see the usefulness in it).
Screenshots: will do, but then again, don't expect anything special. Stable and fast pure Android, that is AOSP. As a side note, it's Xposed compatible
I hope everybody likes the new shiny unified forum section! There's still a bit of a work left to do, but I think it looks great and eases maintaining the threads; blame me if you think otherwise :silly:

Thak you for your effort to keep tab 2 alive . Amazing work. Are RRO Layers compatible with this rom?

Ziyan said:
I hope everybody likes the new shiny unified forum section! There's still a bit of a work left to do, but I think it looks great and eases maintaining the threads; blame me if you think otherwise :silly:
Click to expand...
Click to collapse
Hi Ziyan,
I'm glad you mentioned this, as I thought that I was going insane this morning (or just slightly more insane than usual).
Just browsing the new "Unified" forum (to verify my subscriptions) and noticed that the "Dhollmen" threads could be clarified (just like the "Linaro" threads), for example ...
This thread: http://forum.xda-developers.com/showthread.php?t=2176563 could be titled: [KERNEL][P51xx][AOSP] Dhollmen Espresso
This thread: http://forum.xda-developers.com/showthread.php?t=2183830 could be titled: [KERNEL][P31xx][AOSP] Dhollmen Espresso
Just to avoid confusion (I freely admit that I am easily confused).
Thanks.

@mentat no need to have 2 threads, one is enough now in unified section
I also don't know what your question hast to do with this rom [emoji14]
~ All my work, news etc. on http://andi34.github.io ~

Android-Andi said:
@mentat no need to have 2 threads, one is enough now in unified section
I also don't know what your question hast to do with this rom [emoji14]
~ All my work, news etc. on http://andi34.github.io ~
Click to expand...
Click to collapse
Hi Andi,
I only suggested renaming the existing "pair" of threads (they both exist in the Unified Forum) ... Just like the "pair" of Linaro threads (that also both exist in the Unified forum).
The download links in (all four) of the threads (mentioned above) link to unique builds on AFH (for both P31xx and P51xx devices) in this forum: http://forum.xda-developers.com/galaxy-tab-2/galaxy-tab-2-unified
@Ziyan, while we're on the subject, the CandySix for P51XX thread: http://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-candysix-v1-1-t3331598 should also be moved to the new Unified forum as well (the CandySix for P31xx thread has already been moved).
Sorry for all the edits (I put the blame on OCD).
Thanks.

mentat said:
@Ziyan, while we're on the subject, the CandySix for P51XX thread: http://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-candysix-v1-1-t3331598 should also be moved to the new Unified forum as well (the CandySix for P31xx thread has already been moved).
Click to expand...
Click to collapse
Done; I guess this is it then. Like the XDA forum admin said, the best way to handle moving both threads is to move them both to this unified section, and close one of them (preferably the one with the less posts). While we could merge them into one thread, the posts would get all mixed through the other threads posts (because of the date order) and we would lose any sense of a flow in the conversation...

Minimum Custom Recovery version?
@Ziyan @Android-Andi Thanks for bringing new life to this old tabs
Is there any minimum requirement for recovery for flashing this ROM? I'm running pretty old CWM v.6.0.5.1. Is it sufficient?

ZTE Nubia Z9 Mini (NX511j) - Cam driver for international Version

Hey all,
the problme is that the international version has another cam module (13mp) than the chinese version (18mp).
Therefore the custom roms , which are always based on the chinese version and cant use the camera.
Now I need some help on how to implement the driver from the original firmware:
http://rom.download.nubia.com/Germany/Z9mini/NX511J-update.zip
Into this custom rom from mokee:
http://download.mokeedev.com/?device=nx511j
My phone is already rooted and has a custom reovery. I already tried to "zip-edit" the mokee rom and copied/replaced files from the stock rom into the mokee rom , base on this info from here and here e.g.:
Libcamalgo.so
Libcameracustom.so
Libcameraclient.so
Libcameraservice.so
Libcamerametadata.so​
and
system/lib/ libcamdrv.so
system/lib/libcamalgo.so
system/lib/libcameracustom.so
system/lib/libdpframework.so
system\etc\permissions\android.hardware.camera.xml​
and then rezipped the rom and signed the zip with the autosign tool.
This "custom" rom than could even be successfuly installed with twrp without an problem, but then didnt
get beyond the mokee boot logo.
Now my question is:
Can this be due to the fact that the stock rom is 5.02 and the custom rom/mokee is 6.01 and the drivers simply cant work due to another android version?
Am I thinking way to easy with this simple "copy/paste zip editing" and something more complex like editing the kernel has to be done?
Any tip for what to do is very appreciated, as I think I have to solve it by myself due to a lack of mass-interest in this device.

Does it support Indian version?
Sent from my NX511J using XDA-Developers mobile app

Sorry for my late reply, I've been on vacation.
I dont know if it supports the indian version. My device is the EU version I guess...
It has a different camera module whith only 13mp-

Hi!
Just replacing those files can't work. The drivers for the t4k37 camera sensor aren't built in in the mokee release.
When it boots, it only polls those Sony IMX sensors. Furthermore the librarys for the t4k37 sensor arent't in the rom.
I'vre tried to build my own mokee rom, but with no luck, got only to boot animation. The device isn't supported officialy by
Mokee any longer. As I didn't build android before, my knowledge is obviously too little for this kind of task... perhaps some
more experienced guys could help...
Also it's hard to understand what is the exact difference in the chinese, indian , international an german modells of the phone, there are little informations.

Just flashed Mokee MK51.1-nx511j-160420-HISTORY.zip and moved the appropriate libraries to the flash, it seems, that the t4k37 sensor initializes and works. Sadly there's no camera app preinstalled.
Tested with Open Camera App from Playstore. I'll now try to get the original camera app.
Libraries where taken from germans stock rom in vendor folder.

kai4065 said:
Just flashed Mokee MK51.1-nx511j-160420-HISTORY.zip and moved the appropriate libraries to the flash, it seems, that the t4k37 sensor initializes and works. Sadly there's no camera app preinstalled.
Tested with Open Camera App from Playstore. I'll now try to get the original camera app.
Libraries where taken from germans stock rom in vendor folder.
Click to expand...
Click to collapse
Hi kai4065!
Can you give me more info please. Which file list I need to replace. I need to create patch for one of localized firmware. Also may be you know where I can get last de firmware? My device was flashed with NX511J_DECommon_V1.01 now but buyed with 1.02.
Thx for any help.

falkolab said:
Hi kai4065!
Can you give me more info please. Which file list I need to replace. I need to create patch for one of localized firmware. Also may be you know where I can get last de firmware? My device was flashed with NX511J_DECommon_V1.01 now but buyed with 1.02.
Thx for any help.
Click to expand...
Click to collapse
Here's the list:
# Camera
etc/firmware/cpp_firmware_v1_4_0.fw
etc/firmware/cpp_firmware_v1_2_0.fw
etc/firmware/cpp_firmware_v1_1_6.fw
etc/firmware/cpp_firmware_v1_1_1.fw
-lib/libmm-qcamera.so
-lib/libmorpho_jpeg_io.so
-lib/libmmjpeg_interface.so
-lib/libqomx_core.so
-lib/libmorpho_memory_allocator.so
-lib/libmmcamera_interface.so
-lib/libmorpho_strobe_photo_jni.so
-lib/libmorpho_image_converter.so
-lib64/libmorpho_jpeg_io.so
-lib64/libmorpho_memory_allocator.so
-lib64/libmorpho_image_converter.so
lib/hw/camera.msm8916.so
bin/mm-qcamera-daemon
bin/mm-qcamera-app
vendor/lib/libmmcamera_faceproc.so
vendor/lib/libchromatix_ov5648_p5v18g_common.so
vendor/lib/libchromatix_skuf_ov5648_p5v23c_snapshot.so
vendor/lib/libactuator_rohm_bu64297gwz.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_preview.so
vendor/lib/libmmcamera_t4k35.so
vendor/lib/libmmcamera2_stats_modules.so
vendor/lib/libactuator_bu64291gwz.so
vendor/lib/libmmcamera2_stats_algorithm.so
vendor/lib/libjpegdhw.so
vendor/lib/libmmcamera_t4k37_qtech_f4k37ab.so
vendor/lib/libmmcamera2_c2d_module.so
vendor/lib/libmmcamera2_cpp_module.so
vendor/lib/libmmcamera2_vpe_module.so
vendor/lib/libmmcamera_ov2720.so
vendor/lib/libmmcamera_S5K4E1_13P1BA.so
vendor/lib/libchromatix_t4k35_nightmode_1.so
vendor/lib/libmmipl.so
vendor/lib/libchromatix_t4k35_common.so
vendor/lib/libchromatix_ov2720_preview.so
vendor/lib/libmmcamera_sunny_q5v22e_eeprom.so
vendor/lib/libjpegehw.so
vendor/lib/libmmcamera2_sensor_modules.so
vendor/lib/libchromatix_ov5648_q5v22e_zsl.so
vendor/lib/libchromatix_ov5648_oty5f03_common.so
vendor/lib/libmmcamera_sp1628.so
vendor/lib/libmmcamera_skuf_ov5648_p5v23c.so
vendor/lib/libmmQSM.so
vendor/lib/libactuator_bu64291gwz_t4k35.so
vendor/lib/libmmcamera_wavelet_lib.so
vendor/lib/libchromatix_t4k35_preview.so
vendor/lib/libchromatix_t4k35_hfr_120.so
vendor/lib/libmmcamera2_pproc_modules.so
vendor/lib/libmmcamera_imx132.so
vendor/lib/libmmjpeg.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_snapshot.so
vendor/lib/libchromatix_ov5648_oty5f03_default_video.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_nightmode.so
vendor/lib/libactuator_bu64291gwz_camcorder.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_common.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_default_video.so
vendor/lib/libmmcamera_tintless_algo.so
vendor/lib/libmmcamera_ov5648_oty5f03.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_video_hd.so
vendor/lib/libactuator_bu64291gwz_camera.so
vendor/lib/libchromatix_t4k35_default_video.so
vendor/lib/libmmcamera2_wnr_module.so
vendor/lib/liboemcamera.so
vendor/lib/libactuator_bu64291gwz_t4k35_camcorder.so
vendor/lib/libchromatix_ov5648_preview.so
vendor/lib/libmmcamera_ov5648.so
vendor/lib/libmmcamera_ov5648_p5v18g.so
vendor/lib/libchromatix_ov5648_q5v22e_preview.so
vendor/lib/libchromatix_t4k35_snapshot.so
vendor/lib/libchromatix_ov5648_p5v18g_preview.so
vendor/lib/libmmcamera2_isp_modules.so
vendor/lib/libchromatix_ov5648_q5v22e_snapshot.so
vendor/lib/libmm-qdcm.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_hfr_120.so
vendor/lib/libchromatix_t4k35_nightmode.so
vendor/lib/libmmqjpeg_codec.so
vendor/lib/libchromatix_ov5648_q5v22e_common.so
vendor/lib/libmmcamera2_imglib_modules.so
vendor/lib/libmmcamera_tintless_bg_pca_algo.so
vendor/lib/libchromatix_ov5648_p5v18g_default_video.so
vendor/lib/libchromatix_ov5648_q5v22e_default_video_hd.so
vendor/lib/libchromatix_ov5648_common.so
vendor/lib/libchromatix_ov5648_oty5f03_snapshot.so
vendor/lib/libmmcamera_imglib.so
vendor/lib/libmmcamera_hdr_gb_lib.so
vendor/lib/libchromatix_ov5648_p5v18g_default_video_hd.so
vendor/lib/libmmcamera2_frame_algorithm.so
vendor/lib/libmmcamera_hi256.so
vendor/lib/libmmcamera2_iface_modules.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_liveshot.so
vendor/lib/libchromatix_skuf_ov5648_p5v23c_common.so
vendor/lib/libchromatix_ov5648_default_video.so
vendor/lib/libchromatix_skuf_ov5648_p5v23c_default_video.so
vendor/lib/libchromatix_ov5648_p5v18g_zsl.so
vendor/lib/libqomx_jpegdec.so
vendor/lib/libchromatix_ov5648_snapshot.so
vendor/lib/libchromatix_ov5648_oty5f03_preview.so
vendor/lib/libmmcamera_hdr_lib.so
vendor/lib/libmmcamera_ov5648_q5v22e.so
vendor/lib/libactuator_bu64291gwz_t4k35_camera.so
vendor/lib/libchromatix_ov5648_oty5f03_zsl.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_pre4zsl.so
vendor/lib/libchromatix_ov5648_zsl.so
vendor/lib/libqomx_jpegenc.so
vendor/lib/libchromatix_ov5648_q5v22e_default_video.so
vendor/lib/libmmcamera_ov5645.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_nightmode_1.so
vendor/lib/libmmcamera2_is.so
vendor/lib64/libmmcamera2_stats_algorithm.so
vendor/lib64/libchromatix_imx214_hfr_60fps.so
vendor/lib64/libchromatix_imx219_q8n13a_common.so
vendor/lib64/libactuator_rohm_bu64297gwz_camcorder.so
vendor/lib64/libchromatix_imx214_default_video_4k.so
vendor/lib64/libchromatix_imx214_nightmode_1.so
vendor/lib64/libchromatix_imx219_q8n13a_default_video.so
vendor/lib64/libchromatix_imx219_q8n13a_liveshot.so
vendor/lib64/libchromatix_ov8858_q8v19w_common.so
vendor/lib64/libchromatix_imx234_liveshot.so
vendor/lib64/libchromatix_imx219_q8n13a_snapshot.so
vendor/lib64/libchromatix_imx234_hfr_120.so
vendor/lib64/libchromatix_ov16825_common.so
vendor/lib64/libchromatix_imx214_snapshot.so
vendor/lib64/libchromatix_imx234_snapshot_nightmode_1.so
vendor/lib64/libchromatix_imx214_liveshot.so
vendor/lib64/libchromatix_ov8858_snapshot.so
vendor/lib64/libchromatix_imx234_snapshot_nightmode.so
vendor/lib64/libchromatix_ov8858_liveshot.so
vendor/lib64/libchromatix_imx179_preview.so
vendor/lib64/libchromatix_ov8858_hfr_60fps.so
vendor/lib64/libchromatix_imx234_common.so
vendor/lib64/libchromatix_ov8858_q8v19w_snapshot.so
vendor/lib64/libchromatix_ov13850_default_video.so
vendor/lib64/libchromatix_imx219_q8n13a_preview.so
vendor/lib64/libchromatix_imx234_default_video.so
vendor/lib64/libmmcamera2_frame_algorithm.so
Probably not all files are necessary, but i was too lazy to test it out one by one. I just replaced all of them. The libs for the imx sensor probably aren't needed.
Latest german rom is V1.01, as far as I know. Never ever seen a german localized V1.02. Files above were taken from 1.01.
Just works for 5.1, as in Mokee 60.1 there's some sort of timeout when it tries to initialize the driver. Some patching would be needed, but trying to build Mokee myself
didn't resume a working ROM.

kai4065 said:
Here's the list
Click to expand...
Click to collapse
Thank you! I'll try. :good:

Just wanted to let you know,that I was sick of copying the files in every new release, so I just swapped the main camera sensor with the Sony sensor found in the Chinese model. Works like a charm.

[SOLVED] Battery drain on custom ROMs running on SO-02K(Japanese docomo model)

I'm using Xperia XZ1 Compact SO-02K (Japanese docomo model) unlocked bootloader via qUnlockTool.
I installed some custom ROMs like LineageOS 18.1, Havoc OS 4.8, 3.11.
Any ROMs doesn't go to deep sleep so the battery drain is so bad. I installed Android 11 ROMs and 10 ROMs, but both not working deep sleep.
Anyone know good solutions?

Hi,
great to see some other user from Japan with the SO-02K. I also recently installed a custom rom and had the same issues as you. The source is the NFC chip. Unfortunately the Japanese version have a different chip/driver because of the Felica services here (Felica was here in Japan well before Google was even thinking to integrate NFC in Android, so nobody to blame here, beside Google, not Sony.)
Anyway the fix is a bit ugly. However, there is help:
Download this image from here: https://forum.xda-developers.com/t/rom-lineageos-18-1-unofficial-2-0-update-2021-01-20.4047763/
Yes, this and only this. I know it has not been updated anymore, but the reason comes below.
Please check out this thread: https://forum.xda-developers.com/t/fixed-xz1-au-sov36-japan-deepsleep-on-g8341-custom-roms.4156209/
It is about the XZ1 AU version but it also applies to the compact. I summarize here to make the post complete:
Either you root the phone, which I did not do because I do not need root for anything and with root, some of my app do not work, like Spotify. So I recommend to do those steps in the TWRP. Simply mount all the partitions and go to the file manager under advanced options.
Go to folder: /vendor/lib/modules
and delete or rename file call pn553.ko
Restart your phone and it will go to deep sleep. Otsukaresama.
Now, why only this image. Because it uses the older NFC library. In all other images, this fix this not apply anymore, as the modules are not at that place. I really would appreciate if someone more experienced can point me to the nfc module drives in any newer LineageOS image.
PS: Of course NFC will never work with a custom rom (without trying yourself to find out how to make it work)
Best

mugenXperia said:
Hi,
great to see some other user from Japan with the SO-02K. I also recently installed a custom rom and had the same issues as you. The source is the NFC chip. Unfortunately the Japanese version have a different chip/driver because of the Felica services here (Felica was here in Japan well before Google was even thinking to integrate NFC in Android, so nobody to blame here, beside Google, not Sony.)
Anyway the fix is a bit ugly. However, there is help:
Download this image from here: https://forum.xda-developers.com/t/rom-lineageos-18-1-unofficial-2-0-update-2021-01-20.4047763/
Yes, this and only this. I know it has not been updated anymore, but the reason comes below.
Please check out this thread: https://forum.xda-developers.com/t/fixed-xz1-au-sov36-japan-deepsleep-on-g8341-custom-roms.4156209/
It is about the XZ1 AU version but it also applies to the compact. I summarize here to make the post complete:
Either you root the phone, which I did not do because I do not need root for anything and with root, some of my app do not work, like Spotify. So I recommend to do those steps in the TWRP. Simply mount all the partitions and go to the file manager under advanced options.
Go to folder: /vendor/lib/modules
and delete or rename file call pn553.ko
Restart your phone and it will go to deep sleep. Otsukaresama.
Now, why only this image. Because it uses the older NFC library. In all other images, this fix this not apply anymore, as the modules are not at that place. I really would appreciate if someone more experienced can point me to the nfc module drives in any newer LineageOS image.
PS: Of course NFC will never work with a custom rom (without trying yourself to find out how to make it work)
Best
Click to expand...
Click to collapse
Thanks for good solutions!
Actually, I couldn't find pn553.ko on the latest stock ROM(47.2.B.5.38), so I deleted all of NFC files in /Vendor (of cause I took /Vendor backup with TWRP.). The deepsleep little works (please check attached picture) but the battery drain is better than before.
Thanks anyway!

satokun2668 said:
Thanks for good solutions!
Actually, I couldn't find pn553.ko on the latest stock ROM(47.2.B.5.38), so I deleted all of NFC files in /Vendor (of cause I took /Vendor backup with TWRP.). The deepsleep little works (please check attached picture) but the battery drain is better than before.
Thanks anyway!
Click to expand...
Click to collapse
what files did you delete, can you help me to deep sleep?

mugenXperia said:
Hi,
great to see some other user from Japan with the SO-02K. I also recently installed a custom rom and had the same issues as you. The source is the NFC chip. Unfortunately the Japanese version have a different chip/driver because of the Felica services here (Felica was here in Japan well before Google was even thinking to integrate NFC in Android, so nobody to blame here, beside Google, not Sony.)
Anyway the fix is a bit ugly. However, there is help:
Download this image from here: https://forum.xda-developers.com/t/rom-lineageos-18-1-unofficial-2-0-update-2021-01-20.4047763/
Yes, this and only this. I know it has not been updated anymore, but the reason comes below.
Please check out this thread: https://forum.xda-developers.com/t/fixed-xz1-au-sov36-japan-deepsleep-on-g8341-custom-roms.4156209/
It is about the XZ1 AU version but it also applies to the compact. I summarize here to make the post complete:
Either you root the phone, which I did not do because I do not need root for anything and with root, some of my app do not work, like Spotify. So I recommend to do those steps in the TWRP. Simply mount all the partitions and go to the file manager under advanced options.
Go to folder: /vendor/lib/modules
and delete or rename file call pn553.ko
Restart your phone and it will go to deep sleep. Otsukaresama.
Now, why only this image. Because it uses the older NFC library. In all other images, this fix this not apply anymore, as the modules are not at that place. I really would appreciate if someone more experienced can point me to the nfc module drives in any newer LineageOS image.
PS: Of course NFC will never work with a custom rom (without trying yourself to find out how to make it work)
Best
Click to expand...
Click to collapse
hy bro, can you tell me list rom xz1 compact docomo that have pn553 ko?

bangsat69 said:
what files did you delete, can you help me to deep sleep?
Click to expand...
Click to collapse
See this:
[ROM] Havoc-OS 4.6 [OFFICIAL] [R]
Havoc-OS 4.x is based on AOSP, inspired by Google Pixel. Has a refined Material Design 2 UI crafted by @SKULSHADY. Many useful features that will blow your mind. All you can dream of and all you'll ever need. Just flash and enjoy... General...
forum.xda-developers.com