Related
Q&A for [ROM] [OFFICIAL] [5.0.2] [D850] Dirty Unicorns v9.0
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] [OFFICIAL] [5.0.2] [D850] Dirty Unicorns v9.0. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Flashed Dirty Unicorn and loving it so far. No LG or ATT bloatware!
re: http://forum.xda-developers.com/att-lg-g3/orig-development/rom-dirty-unicorns-v9-0-t3005553/
So far, so lovely. The only LG app I'd like to see here is the Camera. I don't think any other camera app uses the laser for faster focusing. I have tried installing the APK someone extracted from stock, but no joy.
Mr. Gunn said:
re: http://forum.xda-developers.com/att-lg-g3/orig-development/rom-dirty-unicorns-v9-0-t3005553/
So far, so lovely. The only LG app I'd like to see here is the Camera. I don't think any other camera app uses the laser for faster focusing. I have tried installing the APK someone extracted from stock, but no joy.
Click to expand...
Click to collapse
There is a ported lg camera you can use from g+ ... But its 8mp and no 4k. Its a wip. Goolgle lg camera mod google plus and I'm sure you will find it.
★2SHAYNEZ★
Any Success Stories?
I was just wondering if the Cellular and all of the radios function before flashing the Dirty Unicorn ROM for my D850.
Thanks,
Christian
Christian D said:
I was just wondering if the Cellular and all of the radios function before flashing the Dirty Unicorn ROM for my D850.
Thanks,
Christian
Click to expand...
Click to collapse
Flashed this last night and so far everything is great, Cellular data(Ater changing APN to ATT LTE), wifi, BT all working and camera seems fine. Only thing I am missing is being able to customize the navbar. I miss the little button to pull down notifications.
Not a deal breaker though. This rom is awesome!
I can't seem to find where I can make Wallet for my default tap and pay.
Dialer FC in Dirty Unicorn
Settings>More>Cellular Networks>Carrier Settings causes Dialer FC
There's a bug when playing music, seems to not want to play the next track, overall sound of the phone stops and I believe texts and phone calls start to have issues. Have to reboot the phone to get it back to normal.
Sent from my LG-D850 using XDA Premium 4 mobile app
Deleted
kingcold86 said:
There's a bug when playing music, seems to not want to play the next track, overall sound of the phone stops and I believe texts and phone calls start to have issues. Have to reboot the phone to get it back to normal.
Sent from my LG-D850 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Anyone else having this issue? Also what App is being used?
Turn off carrier provisioning by default
Click to expand...
Click to collapse
How will my service activate then ? Won't I be unable to use cellular service ?
- Perform a FULL WIPE as described below if coming from another ROM
(A full wipe is when you wipe system/data/cache/internal and/or sdcard)
Click to expand...
Click to collapse
If I do this.. how will I flash the rom ? won't it & everything else be wiped from the storage in its entirety ?
thcue said:
Anyone else having this issue? Also what App is being used?
Click to expand...
Click to collapse
I am using the music app for music. When it happens to me, like in my car occasionally, I go to song list and tap the shuffle all and it goes to the next track like it should but haven't tried another app.
As far as proximity during phone calls, if I pull the phone away from my face and push the power button on the back, the proximity sensor starts working, the screen turns off and back on when I move it to and from my face during that call.
Phoneguy589 said:
As far as proximity during phone calls, if I pull the phone away from my face and push the power button on the back, the proximity sensor starts working, the screen turns off and back on when I move it to and from my face during that call.
Click to expand...
Click to collapse
Have some issues with the proximity sensor as well. After a call, sometimes I have to push the button on the back and unlock the phone before I can hang up.
Is the rom aosp based or omni based?
not complaints.. not demands.. just observations
all I'm missing is the Nav Bar hide.. Global Expanded Desktop & Blacked Out Settings to compliment an otherwise pretty full dark mod
And I'm aware this is just an initial release.. much more to come no worries ^_^
4ndroid99 said:
Is the rom aosp based or omni based?
Click to expand...
Click to collapse
CAF aka 'Code Aurora Forum' more info See our G+
jaladhjin said:
not complaints.. not demands.. just observations
all I'm missing is the Nav Bar hide.. Global Expanded Desktop & Blacked Out Settings to compliment an otherwise pretty full dark mod
And I'm aware this is just an initial release.. much more to come no worries ^_^
Click to expand...
Click to collapse
Soon... Soon...
sooo I'm noticing my battery is in free fall
Didn't even last 5 hours from 100% screen off unused sitting on my desk at home..
I'll get some screenshots up of the battery sections.. it's strange.. all the %s don't even total 100%.. or even 50% :-/
Ambient Display
Ambient Display doesn't work for me, but it also does not turn on in my pocket. Take the good, take the bad.
Anyone with phone call proximity issues, turn off ambient display, it breaks the sensors when screen is off (known issue amongst the G3 roms). as for play music next track issues, it doesn't seem to be affecting every device, so it's not really a bug but it is being looked into
here's 2 sessions of my 100% battery to under 15% in less than 5 hours
It was sitting on my desk unused.. screen off.. location set to battery saving..
I admittedly don't know much.. & am confused not only by the huuuuuge pwn drain.. but why don't the totals = 100% ?
So, I have stumbled across this weird issue since January wherein if the proximity sensor is covered during an incoming call, the screen will remain off. What's weird is that this only happens on CM based ROMs and not on AOSP based ROMs. Of course, all full wipes and clean flashes. I have also tried flashing all the Marshmallow compatible modems available but none solved my issue. I'm using TWRP 2.8.6.0 to flash the zips.
CM based ROMs that I have tried so far;
1. Resurrection Remix M
2. Bliss ROM (both official and unofficial)
3. Marsh CM13
The older builds (December and early January) did not have this problem but of late, every CM based ROM activates the proximity sensor for an incoming call. The reason I'm posting this here is because no one else seems to have this problem and it's not specific to any one ROM.
On AOSP ROMs, everything works fine (no matter what modem I use). I have tried Darkobas ROM and I'm currently on CandySix where I don't have any issues with the proximity sensor.
Any idea why this could be happening? I miss all the customization on CM ROMs and I'm not a huge fan of Layers, so help would be appreciated.
Cheers!
This is the exact bug description:
1. when on a call, cover the proximity sensor >> screen turns off
2. while covering the sensor doubletap the screen (this is the reason for this issue!)
3. uncover the sensor >> screen stays off
The problem is that the doubletap is registered as a power button press and therefore the screen stays off.
It only happens if you accidentally touch the screen with your face, which is likely to occur on a phonecall.
I've already mentioned this in a commit and they said they know about this issue.
The needed commit needs to be ported from cm12.1.
So I guess we can only wait...
Thanks for your response, mate. But CM seems to have fixed this issue because I just flashed the 02/03 CM13 nightly and the proximity sensor works just as it should during an incoming call; no issues there.
I'm going to try flashing another ROM on top of this.
AcmE85 said:
This is the exact bug description:
1. when on a call, cover the proximity sensor >> screen turns off
2. while covering the sensor doubletap the screen (this is the reason for this issue!)
3. uncover the sensor >> screen stays off
The problem is that the doubletap is registered as a power button press and therefore the screen stays off.
It only happens if you accidentally touch the screen with your face, which is likely to occur on a phonecall.
I've already mentioned this in a commit and they said they know about this issue.
The needed commit needs to be ported from cm12.1.
So I guess we can only wait...
Click to expand...
Click to collapse
I just went through your post again and it seems that you misunderstood my issue.
Apart from the issue that you mentioned, the proximity sensor is turning off the screen even before I have answered an incoming call. So, for example, I get a call when the phone is in my pocket. When I take it out, it takes a while for the screen to turn on which is frustrating. If I don't answer the call, the screen should remain on for as long as the phone rings, irrespective of whether the proximity sensor is covered or not. But, in my case, if the proximity sensor is covered when the phone is ringing, the screen turns off. Am I being clear now?
So, after a few intense sessions of flashing different ROMs, it seems that the official CM13 nightly and CandySix are the only ROMs where the proximity sensor is not broken for incoming calls. I guess I'll be sticking with CandySix for the foreseeable future.
But I'd really appreciate if someone can identify why this is happening with all other ROMs and not with official CM13 and CandySix.
girishb said:
I just went through your post again and it seems that you misunderstood my issue.
Apart from the issue that you mentioned, the proximity sensor is turning off the screen even before I have answered an incoming call. So, for example, I get a call when the phone is in my pocket. When I take it out, it takes a while for the screen to turn on which is frustrating. If I don't answer the call, the screen should remain on for as long as the phone rings, irrespective of whether the proximity sensor is covered or not. But, in my case, if the proximity sensor is covered when the phone is ringing, the screen turns off. Am I being clear now?
So, after a few intense sessions of flashing different ROMs, it seems that the official CM13 nightly and CandySix are the only ROMs where the proximity sensor is not broken for incoming calls. I guess I'll be sticking with CandySix for the foreseeable future.
But I'd really appreciate if someone can identify why this is happening with all other ROMs and not with official CM13 and CandySix.
Click to expand...
Click to collapse
actually i think u messed up a bit mate dont mention calling ! something like screen OFF when i recieve a call from someone even when not answered or something like this ! and now getting back to your query i flash RR and CM13 by jgcaap right now just for checking ur issue and i dont have this i kept the phone on the table , called from my other phone and covered the proximity sensor with my hand ! screen was still ON .. and i should mention my RR build is a bit old ! i have been using jgcaap cm 13 from many days ! so
Well, there was only so much I could put in the title. I think my OP explains the issue clearly.
Also, can you try the latest version of RR or Bliss ROM? Because as I said, I wasn't having this issue on the older builds. I also don't have this issue on the official CM13 nightly or CandySix. I just want to find out what's causing this issue on my phone with other ROMs.
@girishb
Ok I see. The way you put it, I thought cm based roms includes stock cm13.
Regardless. The commit which fixed the proximity sensor with screen off has been merged on 02/20.
When did the other cm based roms get their last update?
AcmE85 said:
@girishb
Ok I see. The way you put it, I thought cm based roms includes stock cm13.
Regardless. The commit which fixed the proximity sensor with screen off has been merged on 02/20.
When did the other cm based roms get their last update?
Click to expand...
Click to collapse
but still that issue of phone getting locked furing call persists right ? i mean during call i get this lock sounds sometimes and i need to double tap agn to disconnect the call ! anyways im sure there is a more recent build after 20/2 for rr ! anyawys i should check and get back on taht
thepico said:
but still that issue of phone getting locked furing call persists right ? i mean during call i get this lock sounds sometimes and i need to double tap agn to disconnect the call ! anyways im sure there is a more recent build after 20/2 for rr ! anyawys i should check and get back on taht
Click to expand...
Click to collapse
Im on RR 24 and i can still see this issue. Lets see wht RR Mod comments on that.
Uh, I'm pretty sure that's a different issue. What you guys are facing is basically the screen getting locked when a call is going on, which should not happen. This issue is consistent across all ROMs that I have tried, even AOSP ones. So I don't think that's a CM issue.
My original issue is slightly different. During an incoming call, the screen should remain on for as long as the phone rings, right? If I choose to answer the call, that's when the proximity sensor should kick in and turn off the screen as I move the phone to my ear. However, in my case, if the proximity sensor is covered during an incoming call, it keeps the screen off so I can't see who's calling unless the sensor is uncovered. This should not happen. I hope this explains the issue properly.
girishb said:
Uh, I'm pretty sure that's a different issue. What you guys are facing is basically the screen getting locked when a call is going on, which should not happen. This issue is consistent across all ROMs that I have tried, even AOSP ones. So I don't think that's a CM issue.
My original issue is slightly different. During an incoming call, the screen should remain on for as long as the phone rings, right? If I choose to answer the call, that's when the proximity sensor should kick in and turn off the screen as I move the phone to my ear. However, in my case, if the proximity sensor is covered during an incoming call, it keeps the screen off so I can't see who's calling unless the sensor is uncovered. This should not happen. I hope this explains the issue properly.
Click to expand...
Click to collapse
What firmware are you on? Most proximity sensor issues are due to incompatible/old firmware.
YoshiShaPow said:
What firmware are you on? Most proximity sensor issues are due to incompatible/old firmware.
Click to expand...
Click to collapse
I have tried all modems from this topic (other than the h2os and oxygen one). I have also tried clean flashing the latest CM13 nightly before clean flashing any ROM. I also tried dirty flashing a ROM over the CM13 nightly with no luck. I used TWRP 2.8.6.0 for all of this.
What I can't seem to figure out is why I don't have these issues on the official CM13 nightly build or on CandySix ROM. All other ROMs that I have tried have this issue. If it's a firmware related issue, then shouldn't I be having this problem on all ROMs?
Any solution for this problem coz its really annoying.
I'm having the exact same problem with my phone running CyanogenOS 13.1.2-ZNH2KAS3P0-bacon. The screen doesn't turn on automatically if the proximity sensor is blocked in the beginning of the incoming call or alarm.
If someone finds a solution, please reply to my post
This is a no-frills thread.
Okay here it is.
cm_satsuki-Nega_Spork.zip
For dsds testing: cm_satsuki_dsds_test_boot.img Note: you will see the Sony Bootanimation instead of CM13, this is intentional. Also detection may take a minute or two. Provide clear reports.
For dsds model owners, flash rom clean, then in recovery reboot to bootloader and flash this test boot.img with fastboot
Code:
fastboot flash boot cm_satsuki_dsds_test_boot.img
fastboot reboot
NegaSpork
Working:
Sim [single]
Storage
NFC
Audio record fixed
The rest is the same.
What doesn't work:
Since the camera is still not "fixed" we will just say it doesn't work, deal with it.
Next on my todo list is fmradio
DSDS support is still being worked out by the project members. [see test boot image above]
NOTE: OpenGapps may bug out quickpanel/pulldown menu. This may be related to version used.
I experienced this with pico and nano. [see note below]
Click to expand...
Click to collapse
Thanks @KbaB.BroS for testing :good:
Everything from before works, cell, mobile data, nfc, etc.
Internet speeds are good.
It feels snappier than before, so smooth
The pulldown bar works, I can interact with the toggles without any force closes. If somebody complains about their devices, let them know to use OpenGAPPS. I use the mini version
Click to expand...
Click to collapse
Cyanogenmod Source
Thanks to/for
@CTXz Sources and convincing me to get a Z5P instead of another Sammy device.
Sony Kitakami Platform Developer Organization
@zacharias.maladroit For answering questions, many questions. :silly: [ still have more... xD ]
Those of you without a sense of humor, go away.
Okay current features i'm working on and stuff that works/doesn't work
UVC support enabled in kernel. probably need to build rom-side support still. libuvc avutils etc.
- This is for plugging in camera devices in conjuction with apps like LegitDashcam.
USB Gadget functionality as per pelya's work ,
- pelya/android-keyboard-gadget Use in conjuction with the include USB Keyboard app to utilize your phone as a keyboard/mousepad.
I am working my kernel source here toward net-huntery goodness.
The rest you tell me, and you tell me properly. Messages like
"waahhh my whatchamhoozit is all floompy"
are not acceptable.
This is not a random discussion thread either. Idle chatter belongs in general.
This is also NOT a discussion thread for Xposed,Viper, etc..
Thank you.
m
Notes and Updates
NOTE
I have been running this build for two days now and so far , meh it's alright.
Audio [mic] and Camera issues are definitely annoying.
SELinux is COMPLETELY disabled on this build. If You want security go back to stock.
SELinux enforcing is the goal though.
I strongly recommend using a "traditional" root os SuperSU over systemless-root.
Reasons:
Opengapps requires a factory-reset or fresh install to set up correctly!
Privacy Guard based root sucks. It forgets alot of permissions granted.
Use BETA-SuperSU-v2.52 , I wil attach below as it seems hard to find by conventional means.
Would have posted earlier but needed a smoke break *>cough<* :silly:
Updates and Notes
Reserved
Attached UPDATE-SuperSU-v2.46.zip for another option ,
since that worked the best for me in the past.
Thanks for the input. I get error: 7 to install the .zip file
any solution?
Rubensss said:
Thanks for the input. I get error: 7 to install the .zip file
any solution?
Click to expand...
Click to collapse
You need to use the recovery @moonbutt74 compiled from his other thread.
Sent from my Z5 Premium using XDA Labs
KbaB.BroS said:
You need to use the recovery @moonbutt74 compiled from his other thread.
Sent from my Z5 Premium using XDA Labs
Click to expand...
Click to collapse
Thanks , I have already installed.
@moonbutt74
Would be easier to keep the ROM as daily and test if it supported the dual sim version phones too
Apart from that, some of my observations during a small period of usage :
Pardon me if these are already mentioned.
Screen brightness doesn't reach full capacity
Speaker volume is low I think
For me, I felt the display had some slight glitches. Enabled GPU rendering in developer settings and felt it got better , can't guarantee on this though
Had to revert to stock based since sim functionality for me wasn't available ( I have a dual sim phone)
Ashray_Vk
Okay good deal, umm let me try compiling a seperate kernel package.
Yep brightness is currently HORRIBLE
I didn't notice any glitches display-wise, do you actually mean lag in some screen transitions?
I only tested with radioball and raging thunder.
The build i just tested out had full WOW, HOW THE HELL DO I TURN THIS DOWN BRIGHTNESS. :silly:
So either atm i get crappy brightness as max level which is like 75% of stock.
Or i get the nice stock brightness but the slider breaks/doesn't work.
The speaker volume is limited to where it actually should be. Use a mediaplayer that has an option for software decoding, that is a 100% [double] boost. It's not the idea to bomb out the speakers by default, each user can find their own tweak.
m
On the "daily build" thing, my upload time is horrible, so i will not be pushing out excessive/pointless builds. when i have something else fixed, then i will upload another build. Currently i'm boxing with the brightness issue and getting the mic working for audio recording.
moonbutt74 said:
Ashray_Vk
Okay good deal, umm let me try compiling a seperate kernel package.
Yep brightness is currently HORRIBLE
I didn't notice any glitches display-wise, do you actually mean lag in some screen transitions?
I only tested with radioball and raging thunder.
The build i just tested out had full WOW, HOW THE HELL DO I TURN THIS DOWN BRIGHTNESS. :silly:
So either atm i get crappy brightness as max level which is like 75% of stock.
Or i get the nice stock brightness but the slider breaks/doesn't work.
The speaker volume is limited to where it actually should be. Use a mediaplayer that has an option for software decoding, that is a 100% [double] boost. It's not the idea to bomb out the speakers by default, each user can find their own tweak.
m
On the "daily build" thing, my upload time is horrible, so i will not be pushing out excessive/pointless builds. when i have something else fixed, then i will upload another build. Currently i'm boxing with the brightness issue and getting the mic working for audio recording.
Click to expand...
Click to collapse
By screen glitches, I meant that I saw a few glitches when I scrolled down menus ( like even settings app).
Might be just my sleepy eyes too, lol. And in the beginning, everything was feeling laggy, till I enabled those GPU options in the developer settings and turned the screen off and turned it back on.
Don't rely on this data though, I hope someone else verifies this thing before you take it up as an issue .
-Ash
Ashray_Vk said:
By screen glitches, I meant that I saw a few glitches when I scrolled down menus ( like even settings app).
Might be just my sleepy eyes too, lol. And in the beginning, everything was feeling laggy, till I enabled those GPU options in the developer settings and turned the screen off and turned it back on.
Don't rely on this data though, I hope someone else verifies this thing before you take it up as an issue .
-Ash
Click to expand...
Click to collapse
No problem I'm just looking for clarification, are you talking about lag or screen tearing?
moonbutt74 said:
No problem I'm just looking for clarification, are you talking about lag or screen tearing?
Click to expand...
Click to collapse
There was lag in the beginning, no doubt. Lag was there since the boot animation itself.
Yes! Screen tearing is the term i was searching for. I felt like I saw minor issues of screen tearing along with the lag. ( especially when I scrolled down the settings )
I'm so sorry if I am not able to make things clear.
Nice. My question is does it work well with xposed? Other rom gives me random soft reboot randomly
Sent from my E6853 using XDA-Developers mobile app
Killastyle said:
Nice. My question is does it work well with xposed? Other rom gives me random soft reboot randomly
Sent from my E6853 using XDA-Developers mobile app
Click to expand...
Click to collapse
K,
right now we are working on an Alpha build, self evident in thread title. Xposed being superfluous/unecessary is not being discussed in this thread. Of course later on in the release/beta level thread it will most likely be covered.
@KbaB.BroS
On the good side got brightness and auto brightness sorted.
@Ashray_Vk , give me a bit on the dsds kernel, from what I'm understanding SS an DS were supposed to have been combined, so I am running a fresh build after resync, which on my comp will take a day :silly: adn probably not as long as the actual upload
:laugh:
m
moonbutt74 said:
K,
right now we are working on an Alpha build, self evident in thread title. Xposed being superfluous/unecessary is not being discussed in this thread. Of course later on in the release/beta level thread it will most likely be covered.
@KbaB.BroS
On the good side got brightness and auto brightness sorted.
@Ashray_Vk , give me a bit on the dsds kernel, from what I'm understanding SS an DS were supposed to have been combined, so I am running a fresh build after resync, which on my comp will take a day :silly: adn probably not as long as the actual upload
:laugh:
m
Click to expand...
Click to collapse
Normally, if I'd flash a stock based ROM which was meant for single sim, one sim would work in the dual sim models but the memory card would be not detected . sadly, that wasn't the case with cm though. Not even a single sim gets detected.
Ashray_Vk said:
Normally, if I'd flash a stock based ROM which was meant for single sim, one sim would work in the dual sim models but the memory card would be not detected . sadly, that wasn't the case with cm though. Not even a single sim gets detected.
Click to expand...
Click to collapse
you tried enabling only single SIM mode in Sony's (or other) "Stock" ROM and then flashing this ROM ?
Then at least one SIM might work - unless of course the Z5 devices handle things entirely differently
zacharias.maladroit said:
you tried enabling only single SIM mode in Sony's (or other) "Stock" ROM and then flashing this ROM ?
Then at least one SIM might work - unless of course the Z5 devices handle things entirely differently
Click to expand...
Click to collapse
Um, actually, was running rom aur and then had disabled one sim ( just because i didnt want to use that sim) and then had flashed this.
Unfortunately, not even a single sim worked in this.
Killastyle said:
Nice. My question is does it work well with xposed? Other rom gives me random soft reboot randomly
Sent from my E6853 using XDA-Developers mobile app
Click to expand...
Click to collapse
No problem with XPosed for some time here
Updated Build
CM13 Z5P E6853 Somehwere in Alpha -- Updated DragonLady
see OP , OH! and READ IT. grrrrrrr
Please verify communications are functioning, sim detection, in-call mic working etc.
Is your model SS or DS? Please state model number.
Brightnes and auto brightness should be fixed.
External storage fixed
Re-introduced kcal support in kernel
Included system apps [free, and free versions] - as we are testing , some creature comforts.
Adaway.apk
HKB.apk <--- hacker's keyboard
HKNDCTRU.apk <--- hacker's keyboard cyrillic/russian support
KernelAuditor.apk
NetworkDiscovery.apk <--- fairly useful network discovery app, find it on fdroid
NovaLauncher.apk
OpenCamera.apk
PicuriRam.apk
Quickpic.apk
Rebooter.apk
Superuser.apk <--- enable developer options and root access via that way first, then run supersu and update.
Terminal.apk < jackpal terminal
TotalCommander.apk
USB-Keyboard.apk
USBKB.apk < this one and the one above are the same app, i dun goofed.
Wifitoggle.apk
i am working a vanilla cm13 as well as my own custom build in the same turn, the custom utility in sbin is ccrypt, if you want to know how to use it, pm me and i'll give you a break down. do not use it to encrypt a block device !! single files only, and do not use a generated key, use a memorizable alpha-numeric password, else leave it alone.
m
@zacharias.maladroit WHAT HAPPENED TO PERRY !?!?!?!? :crying:
@moonbutt74
I'm sort of wiping the slate clean in several areas of my life - and that (unfortunately) was part of it :angel:
XC/KUGO/F5321 OmniROM BUILDS
MARSHMALLOW 6.0.1_r74
DOWNLOAD OFFICIAL
DOWNLOAD HOMEMADE
OFFICIAL and HOMEMADE builds are not intercompatible! You will need to do a full wipe if you are switching from one to the other.
CURRENT ISSUES ON OFFICIAL:
1. Incall speaker volume is too low (earpiece volume is fine)
2. Camera sometimes doesn't start (rare)
3. Blutooth and FM radio can't be used concurrently. If you use either you need to reboot to use the other.
4. Double tap to wake doesn't work
5. Adding fingerprints only works on initial device setup. Adding fingerprints from Settings is buggy.
CURRENT ISSUES ON HOMEMADE:
1. Incall speaker volume is too low (earpiece volume is fine)
4. Double tap to wake doesn't work
5. Adding fingerprints only works on initial device setup. Adding fingerprints from Settings is buggy.
KERNEL SOURCE: https://github.com/omnirom/android_kernel_sony_msm/tree/android-6.0
BUGS REPORT
REPORT BUGS ONLY:
- AFTER A CLEAN INSTALL
- USING STOCK OMNI KERNEL
- NO MODS OF ANY SORT
OMNI GERRIT REVIEW
https://gerrit.omnirom.org/
CHANGELOG:
https://changelog.omnirom.org/
DISCLAIMER:
No one is responsible for any damage done to your device but YOU. You've been warned.
[/CENTER]
XDA:DevDB Information
[ROM][XC][MM][6.0.1_r74]OmniROM, ROM for the Sony Xperia X Compact
Contributors
oshmoun
Source Code: https://github.com/omnirom
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Version Information
Status: Testing
Created 2016-12-19
Last Updated 2017-02-11
reserved
Been trying this out since yesterday. Nice ROM, very smooth. Its great to see an AOSP rom with 90% of functionality. Battery usage is on par with stock.
One bug that I noticed is that if bluetooth is on (regardless of whether it is connected or not), it'll keep a 'bluesleep' wakelock which preents the device from going into Deep sleep.
Edit: Another note on the deep sleep problem. Even after turning bluetooth off, the phone doesn't deep sleep. Other wakelocks (event3, event4, event6) show as keeping the phone awake. Reboot fixes it and the phone can finally deep sleep.
Are you guys still enjoying this ROM?
Thanks to oshmoun to this amazing ROM i use it every days and i prefer Android 6 for the xposed module
Fantastic rom! Finally got rid of all the crap Sony bloatware.
However two questions. The camera on the back can now only shoot 8MP photo's. I've disbled the 8MP option in the setting, but it still won't let me shoot 23MP photo's. Is there a way to fix this?
Also the fingerprint scanner doesn't seem to function. When trying to add a fingerprint, it immediately fails (registration cannot be completed). Any fix?
LeZiGue00 said:
Thanks to oshmoun to this amazing ROM i use it every days and i prefer Android 6 for the xposed module
Click to expand...
Click to collapse
speedtoucher said:
Fantastic rom! Finally got rid of all the crap Sony bloatware.
However two questions. The camera on the back can now only shoot 8MP photo's. I've disbled the 8MP option in the setting, but it still won't let me shoot 23MP photo's. Is there a way to fix this?
Also the fingerprint scanner doesn't seem to function. When trying to add a fingerprint, it immediately fails (registration cannot be completed). Any fix?
Click to expand...
Click to collapse
about the camera,you need to wipe camera data after toggling 23MP mode. You'll then see the 23MP resolution in settings.
about the fingerprints, thanks for the hint. This is a bug. Sometimes it works though, so you might get lucky if you try a lot.
also, it's cool to know people are using this rom lol
if you're interested, I can post custom HOMEMADE builds that contain some bugfixes.
Notice though that HOMEMADE builds are signed differently, and won't be compatible with OFFICIAL builds. That means you'll need a full wipe before flashing and booting.
oshmoun said:
about the camera,you need to wipe camera data after toggling 23MP mode. You'll then see the 23MP resolution in settings.
about the fingerprints, thanks for the hint. This is a bug. Sometimes it works though, so you might get lucky if you try a lot.
also, it's cool to know people are using this rom lol
if you're interested, I can post custom HOMEMADE builds that contain some bugfixes.
Notice though that HOMEMADE builds are signed differently, and won't be compatible with OFFICIAL builds. That means you'll need a full wipe before flashing and booting.
Click to expand...
Click to collapse
Definitely interested in updates. Do you know if the Bluetooth issue got fixed?
ammarr said:
Definitely interested in updates. Do you know if the Bluetooth issue got fixed?
Click to expand...
Click to collapse
ok cool. I'll post an updated HOMEMADE build.
Main bugfixes are:
1. camera doesn't randomly crash at start anymore.
2. bluetooth doesn't cause device to stay awake
3. bluetooth and fm can be used without rebooting the device inbetween (not concurrently though, using bluetooth when fm is on will disable fm for example)
EDIT: build is done, tested and all seems ok
download link in OP
Thanks for the new rom. I'm going to flash it asap and let you know how it works. Keep up the work!
Tried this out today and it works really well. I'll probably try it out as a daily this week, because the bugs seem quite minor at this stage. I'm surprised that this isn't getting more attention. Since the BT bug is fixed, I'm wondering if the same fix will work for CM13 as well?
@oshmoun Nice work! I'm not sure how OmniROM works, but what is stopping you from updating official with the same changes?
ammarr said:
Tried this out today and it works really well. I'll probably try it out as a daily this week, because the bugs seem quite minor at this stage. I'm surprised that this isn't getting more attention. Since the BT bug is fixed, I'm wondering if the same fix will work for CM13 as well?
@oshmoun Nice work! I'm not sure how OmniROM works, but what is stopping you from updating official with the same changes?
Click to expand...
Click to collapse
Hehe well I'm just doing the building. Awesome people from the Sony open devices project helped fix the bugs
Official updates for omni 6.0 only come in form of security updates, i.e when Google uploads a new revision. That's why i can't update official that simply. Although to be honest I haven't asked if there are exceptions
I've flashed the rom today and it is working very well. The fingerprint scanner now works fine, even from the settings.
Thanks!
speedtoucher said:
I've flashed the rom today and it is working very well. The fingerprint scanner now works fine, even from the settings.
Thanks!
Click to expand...
Click to collapse
Really? It still doesn't work here.
Maybe it's because you did a full wipe.
Can you try adding/removing fingerprints from settings multiple times please? If it works reliably, that'd be great
oshmoun said:
Really? It still doesn't work here.
Maybe it's because you did a full wipe.
Can you try adding/removing fingerprints from settings multiple times please? If it works reliably, that'd be great
Click to expand...
Click to collapse
I flashed the Homemade version yesterday. I too am able to add fingers after initial setup in the settings. I tried to delete a finger in order to retry but the OS shuts down and reboots.
I believe I found a bug. Homemade version.
While listening to Audio, the whole phone locks up after what seems to be random times. I've listened to audio for a few minutes then it locks. I've listened up to around 45 minutes then locks up. Never more than an hour. If it helps, I've had this occur with Google Play Music, Poweramp, and Pocket Casts apps.
To resolve this, I have to hold power and volume up (Force shut down?)
Turnilemikus said:
I flashed the Homemade version yesterday. I too am able to add fingers after initial setup in the settings. I tried to delete a finger in order to retry but the OS shuts down and reboots.
Click to expand...
Click to collapse
yeah so it's still buggy I guess. I don't think i'll be able to fix that though, sadly. However, I can confirm that the issue doesn't appear on android nougat.
Turnilemikus said:
I believe I found a bug. Homemade version.
While listening to Audio, the whole phone locks up after what seems to be random times. I've listened to audio for a few minutes then it locks. I've listened up to around 45 minutes then locks up. Never more than an hour. If it helps, I've had this occur with Google Play Music, Poweramp, and Pocket Casts apps.
To resolve this, I have to hold power and volume up (Force shut down?)
Click to expand...
Click to collapse
hmmmm, yes you are right. I was able to reproduce that. I think I know why that happens. I used another fix for mp3 playback. The solution that's used in OFFICIAL is different from HOMEMADE.
well, the good news is that android nougat requires neither lol.
Thank you for your time and the build. I've never seen OmniROM before today.
Today I've tried to add some more fingerprints. But now it fails.
I skipped the fingerprint registration during the initial installation and added 3 fingers later, but now it just fails every time.
I also encountered the audio playback issue while using Spotify today.
Hey oshmoun
I'm enjoying your Homemade!
Herzlichen Dank!
Keep on coding! :good:
It's finally here ! Oreo for R7 Plus.
https://download.lineageos.org/r7plus
Happy Flashing !
Bugs :
-Double tap to wake not working *FIXED*
-Fingerprint Sensor not working *FIXED*
-Audio stuttering at low volume
rch.aj34 said:
It's finally here ! Oreo for R7 Plus.
https://download.lineageos.org/r7plus
Happy Flashing !
Bugs :
-Double tap to wake not working
-Fingerprint Sensor not working
Click to expand...
Click to collapse
Hooray! Found it! And good to see confirmation that the Fingerprint sensor isn't working.
I can report a Bluetooth bug using Bluetooth headphones. It doesn't matter what app is used and in what environment. The sound is interrupted by a periodic, soft click, followed a nanosecond later by a split second drop off in sound. It's very quick, but noticeable.
Has anyone else noticed this?
If not, if the developer could let me know what files I need to provide to help, I'll gladly provide them
We always report the same bugs snail haha ! there's still the audio stuttering (headphones) issue but i finally found a fix , let me know if you're still having the bug.
rch.aj34 said:
We always report the same bugs snail haha ! there's still the audio stuttering (headphones) issue but i finally found a fix , let me know if you're still having the bug.
Click to expand...
Click to collapse
Haha! I also found this in the [Iron] Maiden Audio app, "Detected problem with app native libraries (libavcodec)", so there might be a codec bug there that's causing the regular dropouts on the wireless phones. It's too disruptive at the moment to tell if the other bug, with wired phones at low volumes, still exists. As I use the phone to compose, the audio issues are problematic. I love Oreo, though.
Are there any developers reading this thread, btw?
And I have issues with the screen not responding when it goes to sleep. I need to hit the power button again to sleep it again and wake it up, but I think that's already been reported.
snaily trail said:
Haha! I also found this in the [Iron] Maiden Audio app, "Detected problem with app native libraries (libavcodec)", so there might be a codec bug there that's causing the regular dropouts on the wireless phones. It's too disruptive at the moment to tell if the other bug, with wired phones at low volumes, still exists. As I use the phone to compose, the audio issues are problematic. I love Oreo, though.
Are there any developers reading this thread, btw?
And I have issues with the screen not responding when it goes to sleep. I need to hit the power button again to sleep it again and wake it up, but I think that's already been reported.
Click to expand...
Click to collapse
I fixed it by downloading a frequency generator app with background playback , set the frequency at 19Hz , and audio is perfectly fine even at 5% volume , i suppose those frequencies are harmless but that's how i fixed it.
as far as screen , double tap to wake is down but hopefully next build it's fixed along with the fingerprint sensor.
rch.aj34 said:
I fixed it by downloading a frequency generator app with background playback , set the frequency at 19Hz , and audio is perfectly fine even at 5% volume , i suppose those frequencies are harmless but that's how i fixed it.
as far as screen , double tap to wake is down but hopefully next build it's fixed along with the fingerprint sensor.
Click to expand...
Click to collapse
Frequency generator app!! Amazeballs!
snaily trail said:
Frequency generator app!! Amazeballs!
Click to expand...
Click to collapse
Yep ! Enjoy your great audio but lack of fingerprint sensor for now hahaha
rch.aj34 said:
Yep ! Enjoy your great audio but lack of fingerprint sensor for now hahaha
Click to expand...
Click to collapse
Except the sound isn't great at the moment! There's also an issue with Norton Password Manager reporting a fault in another API. I'll list it next time it appears
rch.aj34 said:
Yep ! Enjoy your great audio but lack of fingerprint sensor for now hahaha
Click to expand...
Click to collapse
Norton IDSafe has a libvault.so error that might also be non device specific. Very similar to the Bluetooth lib message
snaily trail said:
Norton IDSafe has a libvault.so error that might also be non device specific. Very similar to the Bluetooth lib message
Click to expand...
Click to collapse
Actually i tried the bluetooth in my car and it's perfect , no clicking and much more responsive than lineage 14.
rch.aj34 said:
Actually i tried the bluetooth in my car and it's perfect , no clicking and much more responsive than lineage 14.
Click to expand...
Click to collapse
Oh, bugger!
snaily trail said:
Oh, bugger!
Click to expand...
Click to collapse
I reset the phone and reinstalled 15.1 and Gapps, and the intermittent clicking has disappeared. Something obviously went wrong with the initial installation. So if anyone else has a problem with sound, retrying the fresh install might help. The low volume issue has also gone. The library errors remain for the sound and vault apps, though, so I presume they're non-device specific. And FL Studio is crashing at the end of longer recordings, not saving them in the process, which I think might also be fixed when the library error is addressed.
The wake issue isn't nearly as chronic as it was, either. In fact, I hardly notice it all now. I used the Nano version of Gapps, btw.
snaily trail said:
I reset the phone and reinstalled 15.1 and Gapps, and the intermittent clicking has disappeared. Something obviously went wrong with the initial installation. So if anyone else has a problem with sound, retrying the fresh install might help. The low volume issue has also gone. The library errors remain for the sound and vault apps, though, so I presume they're non-device specific. And FL Studio is crashing at the end of longer recordings, not saving them in the process, which I think might also be fixed when the library error is addressed.
The wake issue isn't nearly as chronic as it was, either. In fact, I hardly notice it all now. I used the Nano version of Gapps, btw.
Click to expand...
Click to collapse
Just upgraded to latest nightly and fingerpint sensor is still dead , i read everywhere that flashing firmware will solve it but no idea how to proceed without losing data.
*BUG Fixed : Double Tap To Wake now working.
rch.aj34 said:
Just upgraded to latest nightly and fingerpint sensor is still dead , i read everywhere that flashing firmware will solve it but no idea how to proceed without losing data.
*BUG Fixed : Double Tap To Wake now working.
Click to expand...
Click to collapse
Expanded desktop still causing havoc. Low audio still produces dreadful stuttering on wired headphones and fingerprint sensor still not there, but it's better. I don't know how to flash the firmware either.
snaily trail said:
Expanded desktop still causing havoc. Low audio still produces dreadful stuttering on wired headphones and fingerprint sensor still not there, but it's better. I don't know how to flash the firmware either.
Click to expand...
Click to collapse
Expanded desktop works perfectly for me. this thread looks like a pm between me and you lol. community dead but so awesome to have 8.1 on the R7 Plus haha.
rch.aj34 said:
Just upgraded to latest nightly and fingerpint sensor is still dead , i read everywhere that flashing firmware will solve it but no idea how to proceed without losing data.
*BUG Fixed : Double Tap To Wake now working.
Click to expand...
Click to collapse
Do you have a link to the information regarding firmware flashing?
rch.aj34 said:
Expanded desktop works perfectly for me. this thread looks like a pm between me and you lol. community dead but so awesome to have 8.1 on the R7 Plus haha.
Click to expand...
Click to collapse
Yep. I'm disappointed the developer hasn't a means of accepting bug reports from users.
I tried this on my r7plusf and wifi does not work. (Australia) Latest 14.1 works and has wifi region selections but 15.1 did not.
steve.rand said:
I tried this on my r7plusf and wifi does not work. (Australia) Latest 14.1 works and has wifi region selections but 15.1 did not.
Click to expand...
Click to collapse
I thought that WiFi should work regardless of the ability to select regions. Perhaps there is another problem. Maybe your persist partition was clobbered in the flashing.