Related
Hi, I'll try to keep it short, between yesterday and today, I have been researching CM13, I thought it was a really hard project, but the results look promising so far, I am not ready to release anything at the moment, but I'll let you see some screenshots. This is just a side project, and I'll keep working on AOSP. I'll update this post whenever I feel like the ROM is kind of finished.
PS: This is Android 6.0.1, EMUI is just on 6.0.0 Isn't that exciting?
http://imgur.com/a/kbybk
See you!
PS2: No PMs about this please, you'll have it as soon as it's finished
CM 13 For HUAWEI P8 Lite?
I solve art/runtime error
wow this is great,i wish you all the best in these projects !
When will be this finished? I can't wait!??❤
Sent from my ALE-L21 using XDA-Developers mobile app
just wondering something, how much space uses system from CM13 and AOSP? for example, on stock Huawei roms almost always they use 2GB+
EDIT: and anyways im asking because, i use Honor 4X/Gplay, and its the same phone that the P8 lite, except internal storage, so that's why im wondering, anyways i think i used your AOSP, that had some bugs like no signal, no wifi, etc (im not sure if you made it), the thing is that rom worked it in my phone too lol
You're just awesome dude! We are all very excited about this project. This is just awesome!
Finally someone who is making ROMs for this phone (and unlike someone doesn't say he'll delete everything "because of noobs")
Sent from my ALE-L21 using XDA-Developers mobile app
Sounds great! If you want someone who can help you testing, i can do that!
Yay, i bought p8lite 2 days ago and i love it!
Great work btw
dude this is awesome !!! so there is no more ril problem this is just great thank you very much !!!!
Hi @XePeleato first of all Good Job and second as i can see into the screenshots the RIL problem is persistent or you didn't insert the SIM . I'm following your work on github if u need someone who test the ROM call me
Spineshankumb said:
Hi @XePeleato first of all Good Job and second as i can see into the screenshots the RIL problem is persistent or you didn't insert the SIM . I'm following your work on github if u need someone who test the ROM call me
Click to expand...
Click to collapse
Hi, The SIM is there, the thing is that I need to patch the framework in order to include the Huawei Java classes that enable the RIL stack. I'll release a testing version soon, since I want to include things to test, it wouldn't make sense to upload a rom with 1 or 2 features working, there would be nothing to test
XePeleato said:
Hi, The SIM is there, the thing is that I need to patch the framework in order to include the Huawei Java classes that enable the RIL stack. I'll release a testing version soon, since I want to include things to test, it wouldn't make sense to upload a rom with 1 or 2 features working, there would be nothing to test
Click to expand...
Click to collapse
Sure! what about the camera? i think is not possible to port the Snap camera feature on HiSi
panchovix said:
just wondering something, how much space uses system from CM13 and AOSP? for example, on stock Huawei roms almost always they use 2GB+
EDIT: and anyways im asking because, i use Honor 4X/Gplay, and its the same phone that the P8 lite, except internal storage, so that's why im wondering, anyways i think i used your AOSP, that had some bugs like no signal, no wifi, etc (im not sure if you made it), the thing is that rom worked it in my phone too lol
Click to expand...
Click to collapse
Wifi worked fine on my 5.1 AOSP version, The system.img weighs roughly 800MB, I don't know exactly how much will it take, since CM13 didn't erase my internal storage.
NeedleGames said:
Finally someone who is making ROMs for this phone (and unlike someone doesn't say he'll delete everything "because of noobs")
Sent from my ALE-L21 using XDA-Developers mobile app
Click to expand...
Click to collapse
Well, sokkoban recieved a LOT of input about his roms, there were a lot of questions and stuff, it can get really annoying, these open source projects come "As is, without warranty of any kind" - quoting the GPL so actually, trying to give some decent support on this forums is really kind.
Spineshankumb said:
Sure! what about the camera? i think is not possible to port the Snap camera feature on HiSi
Click to expand...
Click to collapse
The Snap app is included, however since I haven't included the camera HAL yet, I don't know for sure if it will work.
--
I'll be off like a week or so, I have compiled my own kernel, with some CPU governors to try, and I have fixed the screen DPI so far, there's still some serious patching needed.
@XePeleato yeah it worked, but if im not mistaken, with static wifi, but interesting, if the system is 800MB i think i will be fine, thanks for all about this
This is just my mind. But i would be more happier if i got fully working cm13 marshmallow than aosp lollipop. If i was you. I would take cm as a primary mission. But do as you want. Aosp is great news too
Keep it up man!
Vika__ said:
This is just my mind. But i would be more happier if i got fully working cm13 marshmallow than aosp lollipop. If i was you. I would take cm as a primary mission. But do as you want. Aosp is great news too
Keep it up man!
Click to expand...
Click to collapse
Sure, your opinion matters. Luckily, if I apply a patch to CM, it's also valid on AOSP, the same applies for the kernel.
XePeleato said:
Hold on I said nothing about the RIL stack, I don't know if it will work or not, but that's the last thing I am going to try to fix since I don't know if I am going to be able to fix it at all.
Click to expand...
Click to collapse
holly crap I thought this problem is finally solved :/ , okey I hope it can be fixed then , good luck !!!
Great!If I port this for Honor 4C,will it work?Sorry for my bad English.
来自华为荣耀畅玩4C CHM-TL00H -天生急性子 Android 小楼阁
I was thinking: since we have an unlocked bootloader and custom roms, how hard would be to port AOSP Nougat?
There is any tecnical difficulty, like kernel version, that can block us?
Not much, I would imagine.
As far as I can tell, it'd just take a dev that's interested in putting in the effort.
Yes, this counts as my "yes, please" vote for Z00T.
I am votting with yes
I was thinking about do a try and compile it straight away, but i fear i'm not experienced enough to make something bootable
I don't think that the kernel or other thing will block it, but we got a custom ROM so late and I don't think we'll have a CM14 very soon
Cm14 should be prettt easy since we have cm 13, the point is that right now is not worth it because it's still in early stage, so a fully fledged cm13 would be more usefull.
AOSP is another talk because it's so barebone
Jhyrachy said:
Cm14 should be prettt easy since we have cm 13, the point is that right now is not worth it because it's still in early stage, so a fully fledged cm13 would be more usefull.
AOSP is another talk because it's so barebone
Click to expand...
Click to collapse
Umm, thanks for your thoughts about trying to bring N, it seem you got the answer yourself
from what i look at Z00L/T source, other than some fix and caf one, they could bring N to L/T with some borrowed libs. And looking from our source, I still found some line with L/T on it, so, yes, dev may bring N to this device, just hope that libs going to work with this devices.
But as you said, a fully fledged cm13 would be useful, using RR build for 3 days, and got the problem as they says. Plus, for me, front camera isn't working (called arclib or something, front camera effect when using asus camera, it's working fine with other camera because they didn't load that lib). Constant lag when using GPS other than "gps only" (might RR only problem). etc..
Either way, I hope that you could join the team (or, is he a one man army?) maintaining this device, fixing things come first, upgrade when everything is fine. At least "ok".
I don't know about AOSP, but many say choose CM because of CM broad compatibility layer. If that's true, then AOSP might slightly harder...
or... not really.
Sent from my ASUS_Z00RD using XDA Labs
Interesting, I'm not developer but I think this is possibke, Android 7.0 supports S410, maybe CM14 will better than AOSP.
yeah i still waiting ??
Sent from my ASUS_Z00ED using Tapatalk
Who wants to test BeanStalk 6.25 for Z00RD/Z00E?
imjohncarlo9 said:
Who wants to test BeanStalk 6.25 for Z00RD/Z00E?
Click to expand...
Click to collapse
I, but it will be possible tonight because now i working , phone at home
imjohncarlo9 said:
Who wants to test BeanStalk 6.25 for Z00RD/Z00E?
Click to expand...
Click to collapse
i will try tomorrow ...good for this ??
Sent from my ASUS_Z00ED using Tapatalk
Some news?
waiting :victory:
Waiting for some USEFUL news.
Today I try to compile it, but do not know if I aim, because I'm not a developer and I have no experience, but I try the same, stay connected, sorry for my bad english
I can't download the sources because it me give an errore i can't compile a ROM,sorry
Still waiting for news.
I tried to compile it myself, I downloaded all the sources, but since the Z00ED / RD is not officially supported by CyanogenMod, and then the repository and everything else must be manually added, I tried but I get error during compilation. Now we must wait for some developer is able to have time to complete it, because basically if you have created for the Z00L / Z00T do not see why you can not fill because they have the same processor. Sorry for my bad English
kurnalcool said:
I tried to compile it myself, I downloaded all the sources, but since the Z00ED / RD is not officially supported by CyanogenMod, and then the repository and everything else must be manually added, I tried but I get error during compilation. Now we must wait for some developer is able to have time to complete it, because basically if you have created for the Z00L / Z00T do not see why you can not fill because they have the same processor. Sorry for my bad English
Click to expand...
Click to collapse
Hi! Could this help you in some way? I don't know how, but I hope there is something usefull. This is a link to a russian forum where CM13 for ZE500KL was first posted by his original creator. Is in russian but I think you can use google translate to read the forum http://4pda.ru/forum/index.php?showtopic=766921
WHOEVER AGREES TO THE POST BELLOW PLEASE LEAVE A COMMENT TO SHOW SUPPORT FOR THE CAMERA PORT
Hello, there Sultanxda
I'm posting this post?with the hope that you'll see what I have to say.
First of all, congrats on the work you done on CM*13 and Lineage *14. Congrats on the touches you added to both.
I love the stability, the battery life on your CM*13, BUT, your camera, or CM'S camera user interface, I just dont think its that much USER FRIENDLY as OOS camera is. I have tried so many ways to get that camera ported onto this ROM and withkut success and I'm sure others have tried it too.
Through this post I am requesting a port file or an update which provides both cameras and let us choose which one we use, or use both in diff situations.
Look, man I get it, you've put work in the camera, BUT the user interface. Please allow us to use OOS camera with no issues.
I'm sure other people would appreciate it too if you would do that. That way your ROM would be the best ROK there is for OnePlus3T. The reason I left your rom ia because of the camera. The camera is one of the most important things in my phone since i capture moments, and I there are moments that I want to capture on the spot, quick and easy, moments when I want to take a quick video and by the time I bring up the video feature its too late, the moment is gone. I hope that you can underatand me of why I want the OOS camera on your rom.
WHOEVER AGREES TO THE POST BELLOW PLEASE LEAVE A COMMENT TO SHOW SUPPORT FOR THE CAMERA PORT
This rom ships with Snap and OnePlusCamera. It is 14.1 - not 13. RAW pic saving and burst mode doesn't work, but evryting else is working.
OnePlus does not use HAL3, but HAL1 with proprietary call backs to framework/av (libcameraservice) to implement some features of HAL3 to HAL1-running OnePlusCamera. Since this is neither real HAL1, nor HAL3 - and because this is proprietary - it's not easy to implement in lineageos. @vavill is working on this:
https://github.com/kxzxxx/android_device_oneplus_oneplus3t/commits/cm-14.1
On a side node: Read, understand, respect and follow the forum rules, please. Questions belong to the Q&A forum.
Jesus save this child..just bless him..
Wrong section.. In case you ask me why u need blessings..!!
arjunarora said:
Jesus save this child..just bless him..
Wrong section.. In case you ask me why u need blessings..!!
Click to expand...
Click to collapse
I think you're exaggerating there. My bad then, how do I delete the post?
benm98 said:
I think you're exaggerating there. My bad then, how do I delete the post?
Click to expand...
Click to collapse
Not at all bud.. @stephen can you please move this to the appropriate section..
nvertigo67 said:
This rom ships with Snap and OnePlusCamera. It is 14.1 - not 13. RAW pic saving and burst mode doesn't work, but evryting else is working.
OnePlus does not use HAL3, but HAL1 with proprietary call backs to framework/av (libcameraservice) to implement some features of HAL3 to HAL1-running OnePlusCamera. Since this is neither real HAL1, nor HAL3 - and because this is proprietary - it's not easy to implement in lineageos. @vavill is working on this:
https://github.com/kxzxxx/android_device_oneplus_oneplus3t/commits/cm-14.1
On a side node: Read, understand, respect and follow the forum rules, please. Questions belong to the Q&A forum.
Click to expand...
Click to collapse
Thats the ROM I previously used, but I gave up on it, I want sultan because of better bettery life and stabillity, also it has xposed, please show your support if you agree with me tough and spread the word till this gets to sultan.
benm98 said:
Thats the ROM I previously used, but I gave up on it, I want sultan because of better bettery life and stabillity, also it has xposed, please show your support if you agree with me tough and spread the word till this gets to sultan.
Click to expand...
Click to collapse
Haha, he's the maintainer of that ROM you gave up on, lol.
benm98 said:
Thats the ROM I previously used, but I gave up on it, I want sultan because of better bettery life and stabillity, also it has xposed, please show your support if you agree with me tough and spread the word till this gets to sultan.
Click to expand...
Click to collapse
I completly misunderstood your question.
If your question was: "Can I use OnePlusCamera from @nvertigo's cm-14.1 rom on @Sultanxda's cm-13.0 rom?", the answer is: no, but you can use the android 6 version.
Just copy these files from stock OxygenOS 3.x.x (you need this older version for cm-13.0):
Code:
/system/priv-app/OnePlusCamera/OnePlusCamera.apk
/system/priv-app/OnePlusGallery/OnePlusGallery.apk
/system/lib64/libfilter-sdk.so
/system/lib64/libopbaselib.so
/system/lib64/libopcameralib.so
/system/lib64/libopcamera.so
If this works, make a flashable zip of it.
A private word:
Your posting feels unfair, barefaced and offending. Where are your bug reports and/or logs? Have you asked for help? I havn't found one single word on your issues in the rom thread. You demonstrate a lack of respect for my work and real bad manner.
nvertigo67 said:
I completly misunderstood your question.
If your question was: "Can I use OnePlusCamera from @nvertigo's cm-14.1 rom on @Sultanxda's cm-13.0 rom?", the answer is: no, but you can use the android 6 version.
Just copy these files from stock OxygenOS 3.x.x (you need this older version for cm-13.0):
Code:
/system/priv-app/OnePlusCamera/OnePlusCamera.apk
/system/priv-app/OnePlusGallery/OnePlusGallery.apk
/system/lib64/libfilter-sdk.so
/system/lib64/libopbaselib.so
/system/lib64/libopcameralib.so
/system/lib64/libopcamera.so
If this works, make a flashable zip of it.
A private word:
Your posting feels unfair, barefaced and offending. Where are your bug reports and/or logs? Have you asked for help? I havn't found one single word on your issues in the rom thread. You demonstrate a lack of respect for my work and real bad manner.
Click to expand...
Click to collapse
Not home right now. I appreciate your guide, will try it when I get home. Look, lad, I didn't meat to offend, I have used your rom as my daily driver for a month since I gave up on SULTAN's because there is no OOS camera on it. I enjoyed using it, but I was missing xposed and the fact that sultan's uses Android 6 which in my opinion is more stable.
Again didn't mean to offent no one, is just the fact that sultan's offers xposed due to it being 6.0 and thats why I think battery life is better on that, since it's not as heavily loaded as 7.0 or 7.1 is.
Thanks again for the guide, looking forward to giving it a try. Also what do you mean by "If this works, make a flashable zip of it.", do you mean after I drop in the files from OXYGEN OOS to sultan's OS create a zip then flash it and then see if it works?
New build up at sx.ix5.org, use version 2018-10-30.
Changelog here: https://sx.ix5.org/changelog.html
Install guide: Flashing AOSP on Xperia XZ
XDA:DevDB Information
AOSP Pie based on Sony Open Devices Project, ROM for the Sony Xperia XZ
Contributors
local__hero, fastbooking, oshmoun
Source Code: https://git.ix5.org/felix/local-manifests-ix5/src/branch/ix5-customizations
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: .184 / .192
Based On: AOSP
Version Information
Status: Nightly
Created 2018-11-09
Last Updated 2019-05-17
Reporting bugs
Important: Read the bug list before posting. Anyone can add bugs to the list, just follow the rules.
If you have questions, ask them in this thread: Xperia XZ Pie ROMs Questions and Answers Thread
Don't make me ask you for logs every time!
I will repeat the rules again here:
Rules:
New bugs must include version where error popped up and which oem version you are using
Only reproducible errors
Should include adb logcat (linked in a pastebin service like https://del.dog)
Must include clear description what is wrong
If it is a visual/SystemUI bug, only report it here
If it is an internal bug(e.g. fingerprint crashes device), report it to the Sony bugtracker as well!
Always try to fix the bug yourself first! Then submit a pull request to Sony
Must search if error has already been reported (bug tracker, this document, dev buglist)
If you've reported the issue somewhere else already and just want to track it here as well, add a link
Before reporting a bug, always make sure to isolate it. That means, wipe everything, install only the ROM without GApps and Magisk and see if the problem still exists. Only then report the bug!
---
If you have questions, ask them in this thread: Xperia XZ Pie ROMs Questions and Answers Thread
---
In 9.11
1. Everything still works
2. Charging with plugged at screen off works
3. On gcam portrait mode and night photo gives purple glitched image
And phone seems to be faster.
Bug: 9.11 with oem v2- Clean install
- Hotspot not working
- Phone call issue - Mic and speaker not working, cannot hear anything or say anything << Listed in the bug
- Top speaker not working
Still testing.
An update
Yes, we know calling is kinda broken right now on both oem versions. Yes, we know you have problems with dualsim devices because you didn't flash the dualsim patcher. Yes, battery life isn't very good because we are testing out some increased CPU frequencies so video doesn't stutter. (you can go back to the 11-05 build which has the old CPU freqs and compare).
We're aware of a lot of these issues, and they are all tracked in the current buglist (see post #2).
Development happens mostly in the Sony open devices program, with a few heroic volunteers contributing. Right now, a lot of work is being done to get the current flagships(think XZ2, XZ3) to a semi-stable state, but work for our device is done as well.
You can check progress in the sonyxperiadev repos. E.g. recently, some changes to the telephony HAL integration have been made, see the common device repo.
Why is it taking so long to fix all this?
Sony buys many of their processors from Qualcomm. Lots of stuff in phones is proprietary and covered in patents, and you can only get the source code if you sign an NDA. So even if Sony wanted to, they could not release the source for a lot of things.
See all the files with the name "qti" in them? That's Qualcomm Technologies, Inc. See all the repos named something like "qcom-something-something"? That's Qualcomm.
When there's a problem, we have to report it to Sony, who report it to Qualcomm. This takes time already. And don't forget Qualcomm has suppliers as well, and so on and so on. The same is true for other parts, e.g. the Wi-Fi chips are from Broadcom.
Then, support for hardware stuff is on many levels. A lot of low-level drivers that are driving the hardware are on the /odm partition(the one that the oemv1/v2 blobs get flashed to). Then there is work to be done tweaking the actual hardware abstraction layer(HAL) interfaces that work with these driver blobs. Then there are kernel drivers that can go wrong and mess up. Then it can be a problem somewhere higher up in the Android frameworks. Lots of detective work.
If new blobs from Qualcomm come out, Sony itself needs to do some testing, and then releases a new oem version. It won't just magically work, we need to tweak the SODP vendor side as well. It could be as easy as changing a version to a newer one, but it could also be a lot harder. The sonyxperiadev crew knows what's needed to integrate these new blobs, but it still takes time and testing.
Qualcomm provide the a lot of the source code to work with their hardware and blobs from the higher-level Android side in their CodeAurora forum (CAF) repositories. The relevant changes then get merged into the sonyxperiadev repos and we can test if it works(or if something new is broken...).
For more info, read the Android documentation on hardware etc.
The chip in our phone, the MSM8996, is quite old already(even the SDM845 in the XZ2/3 is already quite old in processor standards). We can be luck that Qualcomm still provides support. But it's not a priority to them, they want to sell new
ones of course. That is also a reason updates can take longer.
Regarding full forced-reboot crashes:
Sadly, as of now, for some people the "/sys/fs/pstore" folder does not get populated after a crash. This is important to diagnose what happened.
You can apply this patch to force a kernel panic on every reboot, but I would recommend that you do
so only if you know what you are doing.
Regarding battery life:
Please install BetterBatteryStats
and find out what is draining the battery.
This could really help us out! But first, make sure you are not running any GApps, because the Google Mobile Services are a massive pile of battery drain.
If you absolutely have to use GApps, please run only the "pico" GApps version!
---
About the posts here:
Like 90% of posts here and in the old thread are full of people who just plain refuse to read, asking how to install or demanding someone help them out with something that has already been answered time and time again. This makes it extremely annoying for the us who have to scroll through pages of useless stuff to find the genuine bug reports. You do realize this site is literally named "xda-developers", right? If you're unclear on the concept, please read this: https://forum.xda-developers.com/showpost.php?p=16682226&postcount=2441
"This doesn't work!" - "This thing crashes!" - That gives us almost no clue what is happening. We need logs, or we can't do anything about it. I have only one phone, and I only use the stock ROM. There are a lot of nice testers who send others and me helpful bug reports, with detailed explanations in what circumstances it occured, with proper logs.
With that info, the Sony open devices team and us can actually look into issues.
So please, if something doesn't work AND we are not aware of it yet, post it to the bug list (not here!) and attach a link to a log that you uploaded, e.g. to a service like hastebin.com.
nhicko95 said:
how is battery life?
Click to expand...
Click to collapse
Test it out, please. And don't forget to report the diagnosed battery stats.
DarkPrinciple said:
I should be able to get to 12 lunch with my battery being more than 50%
Click to expand...
Click to collapse
I've tweaked for more performance right now, but you can use 11-05 to get old CPU freqs. Also, please help hunt down what is draining the battery, it's most likely too many held wakelocks, but it could be any number of things.
bihslk said:
So what is the latest and best working version of this rom?
Click to expand...
Click to collapse
It's literally in the first post.
bihslk said:
Rom is pretty OK but really annoying top speaker bug. Only lower one works.
Click to expand...
Click to collapse
That is already in the bug list. Please read the bug list before posting.
Update 2018-11-16
Some new developments are happening.
Oem binaries version 3 are out. This should give improved power management. The SODP team has also worked on getting audio handling during calls to work. A big thanks to oshmoun for his work on the audio manager. This change was introduced on the 11-15 build. The issue of no call audio when a bluetooth headset is connected is still present as of now.
Changed IRQ handling (PR by Angelo/"kholk"). This should give better battery life and maybe faster wakeup from deep sleep. But could also lead to instabilities and crashes. Send logs & pstore, see post #2. This change was introduced on the 11-15 build.
Testing kernel 4.9.137 i in progress (we are currently on .103). This means stability and security enhancements from upstream linux. Thanks to Nathan Chance who opened this pull request..
But some of those upstream changes might be incompatible with our Sony kernel, so we have to test that. Send logs & pstore, see post #2. This change was introduced in the 11-16 build. If the 11-15 and 11-16 builds are unstable, revert to an older one. But please be brave and run them for at least a day to get us logs of potential crashes.
---
optixperiaa said:
I am always confused about "flash latest stock ftf" part about roms as a newbie.. if we flash sony's ftf how can we flash rom ? isnt it overwrite ?
Click to expand...
Click to collapse
Your phone software is made up of many layers. The ROMs like omni or this AOSP-based one only modify your /system and /boot partitions.
But when you update your stock firmware via flashtool, you also update your phone modem firmware, your qnovo charging controller firmware, your lower-level bootloaders etc. That is why we instruct you to update to the latest stock firmware. You could theoretically skip flashing /system in flashtool(because it will get overwritten anyway, as you've already discovered) and directly flash a custom ROM afterwards.
When you're coming from omni, there is no need to flash stock firmware again in between, because your other partitions stay the same. Just a new /oem is needed.
viori said:
flash omni_kagura-2018-11-20_UNOFFICIAL_TESTBUILD-2
Click to expand...
Click to collapse
Again, please keep this thread about development for AOSP. The omni builds are not meant for you.
If you have trouble installing then simply don't use it.
DO NOT POST HERE FOR HELP OR YOU WILL BE REPORTED. Read everything before posting.
If you have questions, ask them in this thread: AOSP 9.0 Pie builds for F8331/F8332
The OP has requested that you do not post questions in this thread, please use the thread he states in the OP to do that.
If you have questions, ask them in this thread: AOSP 9.0 Pie builds for F8331/F8332
Click to expand...
Click to collapse
Thanks
Thread cleaned
General update
Newer builds will have selinux set to "enforcing". Most denials should have been fixed or are irrelevant. If you encounter any problems, selinux-related or anything else, please report them to the Sony bugtracker or - even better - submit a pull request to the selinux-policy repo.
Update 1: vendor blobs aren't binderized correctly atm, so no network. You can set selinux back to permissive to fix most issues atm.
The Wi-Fi hotspot has been fixed thanks to oshmoun. In newer builds, it should be using less battery.
Next thing we're going to tackle is deep sleep and battery drain. Big pain point and one of the last blockers, apart from the camera and bluetooth in-call audio.
You might have noticed that the omnirom device trees have been updated to 9.0. Nightly testing builds work fine, but they have the same issues as the AOSP-based ones.
Work is also under way to get a Pie-based TWRP recovery stable, with support for FDE encryption(this means that you will be able to back up your encrypted installations). Mounting /userdata works, but the builds are not ready for public release yet.
Update
New build up (2018-12-08)
Camera key works
Update to December security patch(12-05, r21)
Fingerprint should not crash device on enrollment any more
Allow setting lower minimum brightness
Double-tap-to-wake off by default(but can be enabled)
Plugging in charger with screen off should be fixed
Once again, I invite anyone who would like to help out or just learn a bit about building and tweaking to take a look at the sources posted here.
There will be a guide on how to build only the kernel and experiment with a custom boot.img shortly.
The build guide on sx.ix5.org for reproducing these AOSP builds should bring you up to speed, and if you need help building or just want to chat, the telegram group in post #1 is open to you.
local__hero said:
New build up (2018-12-08)
Camera key works
Update to December security patch(12-05, r21)
Fingerprint should not crash device on enrollment any more
Allow setting lower minimum brightness
Double-tap-to-wake off by default(but can be enabled)
Plugging in charger with screen off should be fixed
Once again, I invite anyone who would like to help out or just learn a bit about building and tweaking to take a look at the sources posted here.
There will be a guide on how to build only the kernel and experiment with a custom boot.img shortly.
The build guide on sx.ix5.org for reproducing these AOSP builds should bring you up to speed, and if you need help building or just want to chat, the telegram group in post #1 is open to you.
Click to expand...
Click to collapse
Great job.
I already built a custom Pie kernel about a week ago to gain better performance but the charging bug was driving me insane :crying:
I guess now's the time to go back to the mighty Pie and try building a nice and hopefully stable Marrow Kernel.
Cheers
Finally a new build is out!
I can't pass safety net on latest build.
Any ideas what should I use ?
Since modules for spoofing fingerprint simply don't work.
I tried universal safety net fix but with no avail.
V 12.15
Charging working fine. But i have problem with camera, photos are very dark.
Sometimes touch screen not working and i need to switch the screen and on again.
ov2rey said:
Sometimes touch screen not working and i need to switch the screen and on again.
Click to expand...
Click to collapse
Disable Dt2w
oem v4 is out
DahakePL said:
Disable Dt2w
Click to expand...
Click to collapse
Thank you It's work!
Layns said:
oem v4 is out
Click to expand...
Click to collapse
i am testing v4 on latest build aosp_f8331_2018-12-21-NIGHTLY-permissive.
Screen unable to display after update to oem v4
https://developer.sony.com/file/download/software-binaries-for-aosp-pie-android-9-0-kernel-4-9-tone/
ov2rey said:
Thank you It's work!
i am testing v4 on latest build aosp_f8331_2018-12-21-NIGHTLY-permissive.
Screen unable to display after update to oem v4
https://developer.sony.com/file/download/software-binaries-for-aosp-pie-android-9-0-kernel-4-9-tone/
Click to expand...
Click to collapse
I tried it works fine but the camera sucks and the sound is bad, the screen opening with double tap is running slow, the charge is a little quick
I am not responsible for anything that happens to your device.
This is a port of MIUI 10 for the op6/6t
Flash at your own risk and make sure to check what's working. Logcats would be appreciated!
Instructions:
1: Flash OxygenOS 9.0.7 twice, this is very important
2: Extract the download somewhere
3: Run the OnePlus 6t flasher (make sure phone is still in fastboot/bootloader)
4: Reboot to TWRP (fastboot boot it if it dissapeared, if you install TWRP you must install Magisk)
5: Flash or adb sideload NFC fix that is included in the download
6: Reboot and install V4A Magisk module and enable headset and speaker, this fixes audio
7: Enjoy!
Download (v3):
MOD EDIT: LINK REMOVED
What works:
Everything except stuff in what doesn't work
What doesn't work:
NFC
Flashlight toggle (3rd party apps work)
MIUI camera (3rd party apps work)
Fingerprint (top priority - @nima0003 - me)
Audio fix #2:
Credits to @dougie313
Flash viper4android module
Grab root browser
Go to vendor\lib\soundfx folder and rename or delete all files in folder
Source code: https://github.com/OnePlusOSS/android_kernel_oneplus_sdm845
Credits: @nima0003 me @ProtoDeVNan0 for the current build
Dylan Neve
Omar
What is it based on? And will you keep working on it?
dennisbednarz said:
What is it based on? And will you keep working on it?
Click to expand...
Click to collapse
Yeah, it'll be hard to do so because of school but I will. It's based off of mi 8 Dev miui (same soc)
nima0003 said:
Yeah, it'll be hard to do so because of school but I will. It's based off of mi 8 Dev miui (same soc)
Click to expand...
Click to collapse
Ah, so it doesn't use OxygenOS as a base?
I'm personally very interested in a MIUI ROM for the OP6T and seeing that someone is willing to work on it makes me pretty happy.
What about features like the mute switch and in-display fingerprint sensor?
dennisbednarz said:
Ah, so it doesn't use OxygenOS as a base?
I'm personally very interested in a MIUI ROM for the OP6T and seeing that someone is willing to work on it makes me pretty happy.
What about features like the mute switch and in-display fingerprint sensor?
Click to expand...
Click to collapse
It's uses AOSP as the base rom, I'm pretty sure alert slider doesn't work yet, hell I'm not sure it even boots yet. But if someone is able to test and it boots stable I'll get to work on those type of things.
nima0003 said:
It's uses AOSP as the base rom, I'm pretty sure alert slider doesn't work yet, hell I'm not sure it even boots yet. But if someone is able to test and it boots stable I'll get to work on those type of things.
Click to expand...
Click to collapse
My 6T is my daily driver. I may back everything up later and test it out.
Wouldn't it be easier to use OOS as the base for better performance, easier porting of features and so on? Would also make most kernels compatible.
Am I correct in assuming this supports treble? If so, I'm sure it'll make it easier to focus on 6/6t features being added rather than worrying about troubleshooting compatibility ??
champ784 said:
Am I correct in assuming this supports treble? If so, I'm sure it'll make it easier to focus on 6/6t features being added rather than worrying about troubleshooting compatibility ??
Click to expand...
Click to collapse
Yes it is treble based, but I didn't even think of the basic bootable gsi. I'll look more into this, thanks for the idea.
dennisbednarz said:
My 6T is my daily driver. I may back everything up later and test it out.
Wouldn't it be easier to use OOS as the base for better performance, easier portion of features and so on? Would also make most kernels compatible.
Click to expand...
Click to collapse
Yes that's a great idea actually, I was just worried some framework stuff would get in the way but maybe not.
nima0003 said:
Yes it is treble based, but I didn't even think of the basic bootable gsi. I'll look more into this, thanks for the idea.
Click to expand...
Click to collapse
Sure thing! We finally got treble support via lineage os for the Moto Z2 Force, which really helped keeping the device alive. Also makes flashing a TON easier, so maybe it's a good place to start
I'm downloading to test, report back in a bit.
champ784 said:
Sure thing! We finally got treble support via lineage os for the Moto Z2 Force, which really helped keeping the device alive. Also makes flashing a TON easier, so maybe it's a good place to start
Click to expand...
Click to collapse
My dad traded his z2 force for a 6t. Rom support was good but everything was messed up, camera didn't focus, no safteynet...
nima0003 said:
My dad traded his z2 force for a 6t. Rom support was good but everything was messed up, camera didn't focus, no safteynet...
Click to expand...
Click to collapse
There are workarounds, but I think it being one of the earlier devices having A/B partitions and basically being abandoned by Moto made it a task. I still have mine, but I wonder if there's something wrong with my device because I can't really flash anything beside rooted stock Rom, which leads me to think it's just a tedious device and I'd rather focus on my new 6t which is FAR superior in every way!
champ784 said:
There are workarounds, but I think it being one of the earlier devices having A/B partitions and basically being abandoned by Moto made it a task. I still have mine, but I wonder if there's something wrong with my device because I can't really flash anything beside rooted stock Rom, which leads me to think it's just a tedious device and I'd rather focus on my new 6t which is FAR superior in every way!
Click to expand...
Click to collapse
Yeah same thing happened to my Xperia xc, I could only flash stock rom, not even rooted.
Flashing failed, error: invalid zip file format.
Dark Nightmare said:
Flashing failed, error: invalid zip file format.
Click to expand...
Click to collapse
Great, thank you, working on it.
You would be my hero
It is great to see other types of roms, instead of only los type roms. Great to switch between them over time.
nima0003 said:
Yes that's a great idea actually, I was just worried some framework stuff would get in the way but maybe not.
Click to expand...
Click to collapse
Hopefully not. Lot's of people prefer stock-based ROMs specifically for the reason that they're usually more stable, almost always better performant and always better for battery (with the exception of TouchWiz). And the whole feature thing is also useful.
Lot's of people base the ROMs of Lineage as it usually has hardware specific support, but as we don't have official lineage yet and it would still be a lesser experience than a stock ROM, I strongly advocate for the OOS base.
Wish I could help out but I'm not a developer. If you need something designed, contact someone at Xiaomi, OnePlus or Google, or if you need some piece of code some person is sitting on, let me know (on Twitter or Telegram @dennisbednarz as i don't use the forum DM system).
So basically you just ported the OS and want testers? As of now, OP6T is just 3 weeks old and hardly would anyone dare to try something that says 'I highly doubt it'll work' in the OP.
Can Not installed
Sent from my ONEPLUS A6013 using XDA-Developers Legacy app